telemetrty completely broken

[williajgr]

I don't get half of the telemetry numbers and most of them are wrong. what level of firmware works for telemetry? 5.1???? i think it got messed up between 5.1 and 5.4 i don't dare try 5.6 This is crazy

[Richrfl]

I apologize, but I have to make a retarded question: What GPS are you using Will? I have two planes using the FrSky's GPS, and one using a DIY (https://github.com/RealTadango/FrSky/tree/master) and with the exception of the latency, I have no problem whatsoever with any of them.

[williajgr]

frsky gps

[williajgr]

2 screen shots.Sent from my iPhoneOn Apr 25, 2024, at 10:47 AM, Richard @.***> wrote: I apologize, but I have to make a retarded question: What GPS are you using Will? I have two planes using the FrSky's GPS, and one using a DIY (https://github.com/RealTadango/FrSky/tree/master) and with the exception of the latency, I have no problem whatsoever with any of them.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[Richrfl]

Didn't get your screenshots. Anyway, two more questions. I guess your GPS is the ADV, (I was never able to have the previous version running at all with Ethos).? Second question do you have any other sensor connected to the SPort? if that is the case, did you try to check the operation with the GPS alone in the SPort?

[bsongis]

The attachments cannot be sent by email. We haven't received them

[williajgr]

The screen shots are in your note.  Yes it is the advanced version but I have used the old version with success.  I also have a fas100 advanced sensor.Sent from my iPhoneOn Apr 25, 2024, at 12:53 PM, Bertrand Songis @.***> wrote: The attachments cannot be sent by email. We haven't received them

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[williajgr]

sorry i didn't know they couldn't be sent by email. two different sensors not behaving

[bsongis-frsky]

Do I read correctly? It seems that in your first screenshot you have a "Custom" calculated sensor. It takes H.pressure which is 22 PSI, removes 14 and it gives 151871 PSI ?

[bsongis-frsky]

I think I understand your issue with this sensor. I have replicated it on simulator. 1) I change the unit of the H.pressure sensor, now it is PSI instead of Pa 2) In my calculated sensor, the unit internally used is the native unit of the H.Pressure So it calculates 800 - 14 = 786 (instead of 0.12 - 14) Then comes the digits + unit, so 786PSI is displayed

[bsongis-frsky]

~@mawzthefinn I wonder if we don't have the same problem in Logic Switches: i.e. you have a Pressure sensor, and you change its unit, then you compare it to a constant value to raise an alert. I am almost sure that there we also use the "native" unit, not the one that the user has chosen~

It works. It is even very powerful, because by using the native unit, when you change the unit of the sensor, you don't have to change your logic switch!

1) Here is the LS

2) I change the unit

3) Here is the screenshot of the LS, it is kept good

[williajgr]

No it works fine in the logic switches.  The only reason I am using the calculated is because the frsky pressure sensor reports 14Psi (one atmosphere)when there is no pressure. Just wanted it to say 0.Sent from my iPhoneOn Apr 26, 2024, at 4:20 AM, Bertrand Songis @ FrSky @.***> wrote: @mawzthefinn I wonder if we don't have the same problem in Logic Switches: i.e. you have a Pressure sensor, and you change its unit, then you compare it to a constant value to raise an alert. I am almost sure that there we also use the "native" unit, not the one that the user has chosen

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[bsongis]

Do you know if it has been broken in 1.5.0 release? Or it was already not correct in 1.4.X?

[williajgr]

Never had a problem before.  Could have broken in 1.5Sent from my iPhoneOn Apr 26, 2024, at 1:05 PM, Bertrand Songis @.***> wrote: Do you know if it has been broken in 1.5.0 release? Or it was already not correct in 1.4.X?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[bsongis-frsky]

I have just tested, 1.4.X have exactly the same behaviour

[williajgr]

I may have upgraded from an earlier one.Sent from my iPhoneOn Apr 29, 2024, at 11:14 AM, Bertrand Songis @ FrSky @.***> wrote: I have just tested, 1.4.X have exactly the same behaviour

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[i3dm]

turbin sensors from Lior Zahavi

all my sensors work well with all Ethos versions.