I usually start my session before I leave my pit area (then put on my gloves). Next, I usually grid up in hot pit and shut the main power off (so that my lightweight Li battery does not drain sitting in the grid), so the bike does not sit and idle too long. Then when I switch the main power back on, the RC does not reconnect to the RaceDAC. Would it be possible to have RC try to re connect if it looses the RC data stream? Otherwise I get a full session with no RaceDAC data?
Maybe this is addressed in the new pay feature, as I have not updated the software on my old data logger phone (that is basically a wifi tablet now) just yet? Another question is do I have to buy the add-on pack for each device? or just once for my google play account?
Comments
Since RaceChrono v3.10, it disconnects and reconnects any device that does not output any data for 15 seconds, so there should be a reconnect after a while. Let me know if this doesn't work on the latest version, so I can investigate this further.
As is standard in Android applications, the purchased item will work on all of your devices with same Google Play account. Also the Pro version will work similarly.
Do you think that it is an issue with the time stamp form the RaceDAC starting over again? and RaceChrono is looking for the next value of the time stamp and not seeing it or something like that?
PS, the single upgrade purchase worked on both phones! Thanks!
If your DroidX has a version that has the Upgrade screen, then it should be the latest. The Pro and Free versions are updated in tandem. Phones with Android 2.2 will receive an older version (v2.46).
I will test this this coming weekend.
"AT
ATS0
ATL5
AT
AT"
With no further output, for many minutes (I waited 3-5 min). This is consistent with the RaceChrono behavior of connecting to the RaceDAC and then not receiving any data from it, when it connects too quickly.
If I then type "DAC" with an enter key that follows it (a line feed or what ever putty inserts to send a command) at any point after I get those strings, it sets off logging data with the typical RC formatting.
Is there a way that you could test for these conditions and send the "DAC(whatever the proper EoL character should be)" to set it off data logging? I have many a track session fail to collect data be cause I killed the main power (to turn off radiator fans and what not so that it does not kill my battery while sitting in hot pit out)....
Let me know if you need anything from me. I am happy to test any thing else out to help move this along.
As always THANKS FOR ALL YOUR HARD WORK!
TAD
Could you check the firmware version?
Go to CMD mode and type ID and hit enter.
>ID
Firmware id #M = 1.0m build 091013
Firmware update is available, and info sent via mail to you.
aol, I will let you know if updating the firmware works.
Thanks to both of you for the hard work!
I would really like to thank RaceDAC for helping out with getting the update sorted out on my device.
Thanks to both of you for all your great work!!!