Hw 80A V4 - Spirit Pro - jeti DS12 - no Telemetry data shown
Hello, I assume wiring is ok, jeti Integration works - spirit`s Telemetry sensor is visiable as well - but no telemetry data transfered from spirit to jeti. Latest FW at HobbyWing and Spirit is in place. Did a test with another Telemetry uni cable as well - all time the same . Connected to primary Sat Port thanks in advance siggi
Hello,
probably you are using esc firmware for vbar.
Or maybe motor is disconnected.
probably you are using esc firmware for vbar.
Or maybe motor is disconnected.
Spirit System developer
I am not sure I would be “happy” to spend that much more if the ESC I have can be made to work....
Remember that RPM comes from a different location than the current and pack voltage - that alway get some people.
If you are able to see the pack voltage (not receiver voltage) then you should see current values when the heli is operating. There is a bit of deadband, a initial period if you would, where no value is shown until a constant value is available and then you will see the values for current and current consumption populate.
Remember that RPM comes from a different location than the current and pack voltage - that alway get some people.
If you are able to see the pack voltage (not receiver voltage) then you should see current values when the heli is operating. There is a bit of deadband, a initial period if you would, where no value is shown until a constant value is available and then you will see the values for current and current consumption populate.
Hi yufasa,yufasa wrote:I am not sure I would be “happy” to spend that much more if the ESC I have can be made to work....
normally I would agree with you, but I had to give almost 300% correction in the Spirit to get a reasonably suitable capacity and 150A current peaks were logged - in a 500 with a 10 minute flight ...
Regards, Michael
I just got back from the field and have not set up any telemetry alerts but i did set up logging...will take a look to see what my HW did with the new RS FBL...
Most of the flights were in testing different rescue modes for a video I am working on so was not focused on getting max flight time.
Most of the flights were in testing different rescue modes for a video I am working on so was not focused on getting max flight time.
i am using several different 6S/12S Hobbywings in my helis... among them 2 x 80a v4. earlier both (now still one) running on j-log s32 for telemetry, the other on Spirit 2. the one on Spirit is on 171% correction and was on +/- the same before with j-log. the 2nd one is needing ~190% with j-log (can only be set by tweaking setup files with binary edit, max is 63%) to be more/less exact. so this seems to be not the big exception with Hw80av4.... and let's not talk about fet temps telemetry on this one 
problem seems to be on the lower Amps measurement... because now - with the correction - you are getting crazy high peaks (182,4A on my Logo 400SE
)... they do by far not match what the program box is telling you (100-110A max). but the mAh used is usable then.... so for me it is clear: the 80A's measurement of the higher current & peaks seems OK and is "bent" by correction factor... but the 80A's lower amps measurement is really needing those high corrections.
nb: all my other Hw Escs are in the region of 3% to max. 10% correction and the result is spot on <1% when recharging... same for temps telemetry... working as expected. just checked with program box after flight vs. telemetry.
nb2: yge65lvt's telemetry is spot on out of the box.
problem seems to be on the lower Amps measurement... because now - with the correction - you are getting crazy high peaks (182,4A on my Logo 400SE
nb: all my other Hw Escs are in the region of 3% to max. 10% correction and the result is spot on <1% when recharging... same for temps telemetry... working as expected. just checked with program box after flight vs. telemetry.
nb2: yge65lvt's telemetry is spot on out of the box.
cheers
Michael
Michael
