Posts: 473 Threads: 105 Likes Received: 54 in 41 posts Likes Given: 33 Joined: Aug 2018 Reputation: 0 15-Dec-2019, 08:25 AM (This post was last modified: 15-Dec-2019, 11:04 AM by sim_tcr.) I am new to taranis. I setup iNavFlight/LuaTelemetry on x9 lite. And it all come up fine on Taranis. Issue is, Whenever I arm, it warms me "Battery critical and Battery left 0%" Fuel is always shows as 0%. What I am doing wrong? Thanks. • Posts: 12,098 Threads: 125 Likes Received: 3,739 in 2,836 posts Likes Given: 99 Joined: Feb 2017 Reputation: 388 Warning from radio or INAV OSD? And does it continues? • Posts: 473 Threads: 105 Likes Received: 54 in 41 posts Likes Given: 33 Joined: Aug 2018 Reputation: 0 (15-Dec-2019, 08:43 AM)voodoo614 Wrote: Warning from radio or INAV OSD? And does it continues? Warning is from radio and osd looks fine. And yes it continues from the beginning of flight through out end. • Posts: 12,098 Threads: 125 Likes Received: 3,739 in 2,836 posts Likes Given: 99 Joined: Feb 2017 Reputation: 388 On the radio, you need to probably set logic switch. https://oscarliang.com/taranis-logical-s...age-alarm/ • Posts: 473 Threads: 105 Likes Received: 54 in 41 posts Likes Given: 33 Joined: Aug 2018 Reputation: 0 Here is a video taken where I am trying to explain the issue. • Posts: 21,408 Threads: 595 Likes Received: 9,037 in 6,688 posts Likes Given: 1,428 Joined: Jun 2018 Reputation: 796 The "Fuel" value for the amount if current drawn from the LiPo since the quad was armed. As this value is showing zero then that is likely the reason you are getting "Critical Battery" warnings. Have you set up your current sensor and set the correct capacity for the LiPo in iNav? • Posts: 473 Threads: 105 Likes Received: 54 in 41 posts Likes Given: 33 Joined: Aug 2018 Reputation: 0 (15-Dec-2019, 10:25 AM)SnowLeopardFPV Wrote: The "Fuel" value for the amount if current drawn from the LiPo since the quad was armed. As this value is showing zero then that is likely the reason you are getting "Critical Battery" warnings. Have you set up your current sensor and set the correct capacity for the LiPo in iNav? Yes I have, it’s virtual current sensor I am using. OSD Amperage and mah used is pretty accurate. • Posts: 473 Threads: 105 Likes Received: 54 in 41 posts Likes Given: 33 Joined: Aug 2018 Reputation: 0 I think the issue is since Fuel is never read, tarnis think battery as empty and warning. • Posts: 473 Threads: 105 Likes Received: 54 in 41 posts Likes Given: 33 Joined: Aug 2018 Reputation: 0 Issue resolved. Some time back I had renamed the sensor name from Fuel to Mah in Telemetry screen. That must have caused it. So I deleted all sensors and rediscovers them all. That resolved the issue. • Posts: 21,408 Threads: 595 Likes Received: 9,037 in 6,688 posts Likes Given: 1,428 Joined: Jun 2018 Reputation: 796 15-Dec-2019, 11:14 AM (This post was last modified: 15-Dec-2019, 01:03 PM by SnowLeopardFPV. Edit Reason: Added "EDIT" line. ) OK, that's great news. I guess the LUA script is looking for a sensor with the name "Fuel" and because you renamed it, the LUA script could no longer find a sensor with that name. Out of interest, in the actual sensor discovery page against the model (not the LUA script page), does the Fuel value start at 0% and go UP (1%, 2%, 3% and so on) the longer the LiPo is left plugged in, or does the value start at 100% and go down? I've never use the Fuel value on my transmitter, but in the sensor discovery page on mine, the value starts at 0% and goes up rather than starting at 100% and going down. Maybe the LUA script itself reverses the values and shows the latter (100% down to zero). EDIT: Don't worry. I found the answer. The "Fuel" percentage sensor value always counts up from 0%, and in fact it can exceed 100% if you don't set the Battery Capacity in Betaflight/iNav to match the capacity of the LiPo you are using. I guess the iNav LUA scripts are just reversing the value with a real Fuel sensor value of 0% being translated to 99%, a real Fuel sensor value of 1% being translated to 99%, and so on down to 0%. • Posts: 473 Threads: 105 Likes Received: 54 in 41 posts Likes Given: 33 Joined: Aug 2018 Reputation: 0 (15-Dec-2019, 11:14 AM)SnowLeopardFPV Wrote: OK, that's great news. I guess the LUA script is looking for a sensor with the name "Fuel" and because you renamed it, the LUA script could no longer find a sensor with that name. Out of interest, in the actual sensor discovery page against the model (not the LUA script page), does the Fuel value start at 0% and go UP (1%, 2%, 3% and so on) the longer the LiPo is left plugged in, or does the value start at 100% and go down? I've never use the Fuel value on my transmitter, but in the sensor discovery page on mine, the value starts at 0% and goes up rather than starting at 100% and going down. Maybe the LUA script itself reverses the values and shows the latter (100% down to zero). EDIT: Don't worry. I found the answer. The "Fuel" percentage sensor value always counts up from 0%, and in fact it can exceed 100% if you don't set the Battery Capacity in Betaflight/iNav to match the capacity of the LiPo you are using. I guess the iNav LUA scripts are just reversing the value with a real Fuel sensor value of 0% being translated to 99%, a real Fuel sensor value of 1% being translated to 99%, and so on down to 0%. When I plugin battery, it would show as some percent (72% for eg.) After some time, it would keep going down. And yes, in INAV i have set my battery capacity. • |