FrSkyRC / ETHOS-Feedback-Community

Feedback & suggestions are welcomed here for ETHOS by FrSky
191 stars 85 forks source link

GPS Altitude incorrect #2390

Closed williajgr closed 1 year ago

williajgr commented 1 year ago

gps altitude being reported incorrectly in ethos. I am getting -98 ft for my house when it should be about 400ft. i get 400 ft when i use my horus x10 se on the same model. i get the right variation just off 500 ft.

williajgr commented 1 year ago

I am using release 1.4.6

strgaltdel commented 1 year ago

determination of the vertical position is always the most unreliable value with GPS due to physical conditions (VDOP) and is subject to greater fluctuations. Only with a higher number of received sats does the value become reasonably stable.

The problem is not likely to be on Ethos side, but on the then actual reception situation.

Was the almanac already up to date when the worse value was displayed? How many sats were received in situation A, how many in situation B? what was the PDOP / HDOP or even better VDOP value? (if available: oXs GPS can output several parameters on SPort). Without such information, no comparison can be made. Such differences can occur with one and the same GPS within minutes, especially at the beginning, when its almanac must be updated which can last about 15..30 Minutes

Was the module left in the same place for about 15..20 minutes (or longer) in good reception conditions and then briefly and repeatedly changed back and forth to receive again for 20 minutes each time? This is the only way to roughly determine whether the error moves with the operating system or whether it is (very likely) a typical GPS "dilution of precision" problem.

Alternatively, you can read out U Blox GPS modules directly via FTDI adapter directly by means of software on the PC and get exact values for comparisons.

williajgr commented 1 year ago

sorry all of that is true but, i hook up the model to my open tx transmitter then hook it up to my ethos transmitter (same place and time) and get different answers and always 500 ft difference. -98 and 400. and i happen to know 400 is the right height for my house..

strgaltdel commented 1 year ago

I made a crosscheck: X18 (1.4.6) bound to an X8r with oXs GPS, waited app. 30..40 Minutes after first fix so that the GPS was "up to date" with stable coordinates and Altitude number of Sats: 11

than i switched off the X18, switched on my X12 running otx, set the X12 into bind mode and performed a very short power cycle of the Rx in order to get him into bind mode, so the GPS had no "real chance" to loose his volantile data (which are buffered for a short time)

I had definitely the same Altitude between oTx & Ethos by using an openXsensor GPS

williajgr commented 1 year ago

i am using the FrSky GPS ADV Sensor.

Satcomix commented 1 year ago

Hello everyone, I also work a lot with openXsensor_on_328P or oXs_on_RP2040. The GPS altitude information varies from protocol to protocol. With my FrSky X20S I see the relative altitude under GPS_Alt and when I change the protocol to HOTT I see the absolute altitude above sea level from the GPS. I only noticed the relative altitude with Ethos 1.4.6, until then I thought it was the absolute GPS MSL altitude. Perhaps in the future there is an option in the Telemetry GPS Sensor menu to switch between the relative and/or absolute altitude, or to display both. Thank you for the work so far. br, Torsten

strgaltdel commented 1 year ago

i was testing near msl, that would explain a lot. differences between ethos / otx less then 20m

so, yes, user options to choose between relative/absolute values would be fine

williajgr commented 1 year ago

that seams about right. if ethos is reading relative alt and open tx is reading absolute alt. Both have merit. would be nice to be able to pick which one to have..

Satcomix commented 1 year ago

Hello everyone, The way I see it, it's not an error in the Ethos system, but a matter of presentation in the Ethos interface. So it should be a feature request to show the GPS Altitude value as either a relative and/or absolute value. You could do it with free IDs from the DIY sensor area. The developers could express themselves on this topic. Best regards, Torsten

williajgr commented 1 year ago

I would like to see the option. Not sure which one i would pick if i had the option. But the gps module does get a different answer than it did in any other os.

williajgr commented 1 year ago

any comments from the developers?

williajgr commented 1 year ago

did this issue die no comment from the developers????

Satcomix commented 1 year ago

It would be a very useful supplement with GPS MSL for one or the other model builder. greetings, Torsten

williajgr commented 1 year ago

what do you have to do to get the devs to comment?

github-actions[bot] commented 1 year ago

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days.