Open doncon94 opened 6 years ago
Currently, the code uses the time from the data file. Per the CWOP website, "the data time is taken as the time that the packet arrives at the findu.com server", so presumptuously that's why the time is fine on the findu side. I'm guessing the Mesowest servers use the timestamp for their data time, but it's curious that the data has gone in before with no issue and is now giving it fits. Currently working on changing the code to have it generate a current timestamp using the datetime package,
If the PC/Datalogger are in local time, the time in the APRS message is local with the Z appended. Can you put in logic to have the time properly with zulu? We believe this is causing us problems getting into Mesowest (and the time is wrong, regardless). Thanks!