-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
S.Port GPS-Time #68
Comments
When a GPS is connected, oXs transmits the date and time in Sport protocol. |
If I understand correctly the time is transfered but not available as telemetry parameter? |
@onki69 you may try setting your time zone (+/- X hours) on the transmitter, in respect to UTC time being send from gps. |
Time zone is set correctly. I will try it with another receiver (Archer M+). |
I believe, at least with RM tx16s, gps time is updated if an internal gps is present at the transmitter, not from the telemetry gps. |
Hello Mstrens, |
there is no relation between GPS time and oXs clock. |
Edit: FYI It was related to the new Ethos software. Hello Mstrens, |
I did some testing about a week ago. |
With oXs, when you ask for discovering the sensors, do you get the GPS data and time in the list of sensors? |
I'm starting to suspect that the date/time data packet from an M6 GPS module is structured a little differently and oXs or Ethos can't understand it. |
It is oXs that decodes the date and time values received from GPS in some frame types. |
I'm currently searching the net for M6N Time problems, and it looks like it's not the frame format, it's a specific setting in the M6, or it is a problem with setting the ROLLOVER-Timestamp-Complement |
I do not have anymore a GPS to test.
|
I make a test with Ver. 2.3.0_Test with FBUS Protocoll GPS Latitude = XX.1225248 degree |
Hello Mstrens, |
For dev purposes I can provide a special Ethos firmware, which will write a sport.log file with the raw S.Port stream. It helps to track such issues and know if Ethos or the custom sensor are involved |
Hello Bertrand, |
I have these issues too... |
Hello Jasc76, |
FUNJET-2023-05-20-19-07-06.csv Here is a log. At first the GPS Time is 2023 all good, but after a period with no reception it's suddenly 2015 |
Hello jasc76, |
in this plane I use: |
this might help in future |
I think that the main problem is the gps module you are using, It uses the M8 engine so no PVT messages out, @jasc76 May you try with my fork ? |
In some receivers (fake/clone) the following test
Here an extract of integration manual:
(statement about 20 second of inaccuracy is not true for fake/clones) Instead getting the time from timeutc record using the following test always return a proper date/time That's what I'm implemented in the arduino version and also in my fork. |
I was on vacation... and had little time ... it adds up :-) |
Some transmitters set the internal time when a GPS-Time-protocol is received from a sensor.
Is this something that can be added to the protocol?
Best regards
Onki
The text was updated successfully, but these errors were encountered: