mstrens
commented
1 year ago Just like in other protocols, Sport and Fbus frames contains always integers (so never numbers with decimals). It is the handset that put decimals (and some time make also some unit conversions). The handset can do it when the field has a specific ID (e.g. altitude) but not when it is a "DIY" field. For PDOP I created a DIY field that contains the value as provided by the GPS. So, if you want decimals, you have to define them in the handset (customizing the sensor)
FYI, I am currently adding Airspeed (based on a MS4525D0) and a compensated Vspeed (Vspeed based on baro alt+ airspeed). Therefore there will be some change in existing alt and vspeed (and so a new risk for bug). The code is not yet ready.
Le lundi 6 mars 2023 à 19:26:16 UTC+1, Satcomix @.***> a écrit :
Hello Mstrens, I did some tests with different GPS systems today to check the information provided by the CN manufacturer. The results were sobering. The price makes the CN quality or clones. For this I ran my FrSky X20S FBUS protocol with oXs 1.5.7 parallel to U-Center and was therefore always able to compare two GPS systems with each other. I noticed that the GPS PDOP value for oXs S.PORT/FBUS is too high, it would have to be divided by 100. (Display:146, U-Center 1.4/1.5) Would it be possible to change this? Why am I doing all these tests? Quite simply: I am writing a manual for oXs Beginners in German as a PDF file, which will also be translated into English.( for the DOC folder?) Thank you very much for your effort. Greeting, Torsten
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
Satcomix
Hello Mstrens, I did some tests with different GPS systems today to check the information provided by the CN manufacturer. The results were sobering. The price makes the CN quality or clones. For this I ran my FrSky X20S FBUS protocol with oXs 1.5.7 parallel to U-Center and was therefore always able to compare two GPS systems with each other. I noticed that the GPS PDOP value for oXs S.PORT/FBUS is too high, it would have to be divided by 100. (Display:146, U-Center 1.4/1.5) Would it be possible to change this? Why am I doing all these tests? Quite simply: I am writing a manual for oXs Beginners in German as a PDF file, which will also be translated into English.( for the DOC folder?) In the new version, I have noticed the system messages in the terminal quite often, but you had already written something about this on RCG. ADS1115 sensor I2C Addr=48 Set up Ads1115 done and OK. ADS1115 sensor I2C Addr=49 Set up Ads1115 done and OK. Start detecting baudrate gps baudrate not detected; will be set on 9600 Attention: setup on core 1 did not ended within timeout Setup1 takes 5000218 usec. Would it also be possible to divide the voltage values of V3 and V4 as well as those of ADC1 and ADC2 A0-A3 by 1000 and transfer them in this value or in mVolt instead of Volt? I cannot set the values in ETHOS like this. Thank you very much for your effort. Greeting, Torsten