Hello,
It's best to look at the screen shot to understand. I have 50Hz of RC3 and GPS data in 1 stream being sent to the Android. In RaceChrono I go to the gauges panel and both sets of data are updating correctly. But the time gauge can differ from 1 to 10 hours between the 2 and I get weird dates like 4/28/58. I don't see weird data when I look at the output from my microcontroller or through a terminal program connected to the BT. When I spot check the GPS and RC3 time codes are the same. The session directory also has the device output file included. I assume the difference between the 2 at this level will affect the merging of the data in the export? (have not confirmed this, I will)
Screen image @
https://drive.google.com/open?id=0B_iB0vrN7TEWVzBDbG1ualJnRk0 and
https://drive.google.com/open?id=0B_iB0vrN7TEWRVJRSGdkTHc2dFECan get screen shots and session directories @
https://drive.google.com/drive/folders/0B_iB0vrN7TEWMlRCZ3ZneHVrdms?usp=sharingNot sure if it's a bug in your app or an issue in my data logger code. It is reproducible. Using latest app in Play (4.7.1)
Thanks, Jeff
Comments
Solutions looking at reviewing:
- lowering the signal rate of GPS and/or RC3
- separating the GPS and RC3 to 2 separate bluetooth channels and using the RC3 count field instead of timestamp
- use bluetooth only for GPS to RC and log locally on the logger to SD card
For now the weird results are probably on my end or results of limitations of the communication channel bandwidth. Going to do some research on the Bluetooth RFCOMM channel bandwidth as well
Thanks, Jeff