Favorite Tracks Disappear on RCP Mk3

Sawdust · Post by **Sawdust** » Sat Feb 16, 2019 3:33 pm

Has anyone else had an issue with RCP Mk3 where their favorite tracks are missing when they boot/reboot RCP?

Steps:
1. Power on RCP via USB to computer
2. Open RCP App on computer
3. Go to Setup and Favorite Tracks are missing
4. Open saved config file from computer
5. Favorite Tracks reappear
6. Write configuration
7. Close RCP App
8. Uplug USB from RCP, wait 10 seconds
9. Power on RCP via USB to computer
10. Open RCP App on computer (or tablet)
11. Favorite Tracks are missing

I've only noticed this recently when bench testing 1.14.6 app and 2.14.0 firmware versions. However now when I revert back to app 1.13.1 (on PC) with firmware 2.13.5 I get the same behavior.

I have even manually added the tracks back several times from both the PC, Android tablet and a Fire HD tablet with app versions 1.14.4 beta and now 1.14.6 with 2.14.0 firmware.

I've tested with the following combinations:
App 1.14.6 (win7 PC) with firmware 2.14.0
App 1.14.6 (win7 PC) with firmware 2.13.5
App 1.13.1 (win7 PC) with firmware 2.13.5
App 1.14.4.beta (win7 PC) with firmware 2.13.5

Android & FireHD App 1.14.4 with firmware 2.14.0
Android & FireHD App 1.14.4 with firmware 2.13.5
Android & FireHD App 1.14.6 with firmware 2.14.0

Since I started the habit of saving my config files after I write them to RCP, I can see that the track "sf" entries are in my saved .rcp files. But I don't know how to determine if they are making it to the RCP Mk3 hardware. I suspect they are since when I boot and connect to RCP, the autodetect track comes up with Watkins Glen (top status bar) even though no tracks are displayed in the list. Strangely, Lime Rock Park is closer to my location, but I always add the Glen as my first Favorite.

Post by **brentp** » Mon Feb 18, 2019 10:15 pm

Make sure on the device you're testing that your presets and track maps are updated from the cloud. They may be hidden because the app does not have a reference to those tracks, because those items in the database are missing.

Just press the cloud update button for the list of tracks and see if that resolves it.

Sawdust · Post by **Sawdust** » Tue Feb 19, 2019 7:45 pm

Hi Brent,

Using the 1.14.6 app on win 7, I just did the following:

Connected the RCP via USB, went to add a track, hit the cloud update button, closed the dialog and the tracks did not show up.

Next I reloaded my previously saved config file and the tracks reappeared. Rebooted the RCP, tracks disappeared.

Downgraded the RCP firmware back to 2.13.5, reloaded my 2.13.5 config file, tracks appeared, wrote config to RCP, rebooted RCP, tracks disappeared.

I'll try completely uninstalling the RCP app from one of my Android devices, reinstall and repeat some testing.

I hope playing with the 1.14.4 beta app with 2.14.0 firmware didn't corrupt something in the RCP unit...

Post by **brentp** » Tue Feb 19, 2019 7:54 pm

Thanks, we will try to reproduce what you're seeing. We'll reply here.

Sawdust · Post by **Sawdust** » Sat Feb 23, 2019 5:51 pm

Hi Brent,

I've downgraded my RCP to 2.13.5 and did some additional testing today with app 1.13.1 on my Win 7 PC. I wrote up step by step procedure of what I'm doing and copying the application log to text files along the way. Is it ok if I e-mail you the logs as well as my config file?

Long story short, after I boot the RCP, add a track, and write the configuration, I see the following at the bottom of the application log:

Code: Select all

...snip...
&#91;RcpConfig   &#93; Config version 2.13.5 Loaded
&#91;TelemetryManager&#93; on_cell_enabled&#58; True
&#91;TelemetryManager&#93; Got new device id
&#91;RcpConfig   &#93; Config version 2.13.5 Loaded
&#91;TrackManager&#93; refreshing tracks
&#91;TrackManager&#93; Fetching venue data&#58; https&#58;//podium.live/api/v1/venues?start=0&per_page=100
&#91;TrackManager&#93; Fetching venue data&#58; https&#58;//podium.live/api/v1/venues?per_page=100&start=100
&#91;TrackManager&#93; Fetching venue data&#58; https&#58;//podium.live/api/v1/venues?per_page=100&start=200
&#91;TrackManager&#93; Fetching venue data&#58; https&#58;//podium.live/api/v1/venues?per_page=100&start=300
&#91;TrackManager&#93; Fetching venue data&#58; https&#58;//podium.live/api/v1/venues?per_page=100&start=400
&#91;TrackManager&#93; fetched list of 425 tracks
&#91;TrackConfigView&#93;  adding track <autosportlabs.racecapture.tracks.trackmanager.TrackMap object at 0x0779D7F0>
&#91;RCPAPI      &#93; Message rx worker exception&#58; u'&#123;"s"&#58;&#123;"t"&#58;329000""d"&#58;&#91;329044,1550939533713,0,4.98,-0.32,-0.05,1.04,0,0,-0,0,42.581882,-73.816925,0.0,197.2,9,2,1.7,0.0,0,0.0,-1,0.0,0.0,0.0,0,67108863&#93;&#125;&#125;' | Expecting ',' delimiter&#58; line 1 column 17 &#40;char 16&#41;
&#91;RCPAPI      &#93; Read message timeout waiting for addTrackDb
&#91;RCPAPI      &#93; POKE
&#91;RCPAPI      &#93; Message rx worker exception&#58; u'&#123;"addTrackDb"&#58;&#123;"rc"&#58;-99&#125;&#125;' | Set changed size during iteration
&#91;RCPAPI      &#93; rx message did not match expected name setWifiCfg; addTrackDb
&#91;RaceCaptureApp&#93; Config written

After rebooting the RCP again, letting it connect to telemetry, I copied out the application log again and see the following at the bottom (IMEI number removed):

Code: Select all

...snip...
&#91;RcpConfig   &#93; Config version 2.13.5 Loaded
&#91;TelemetryManager&#93; on_cell_enabled&#58; True
&#91;TelemetryManager&#93; Got new device id
&#91;RCPAPI      &#93; Message rx worker exception&#58; u'&#123;"status"&#58;&#123;"system"&#58;&#123;"model"&#58;"RaceCapture/Pro MK3","ver_major"&#58;2,"ver_minor"&#58;13,"ver_bugfix"&#58;5,"serial"&#58;"2F0022001751343034323934","git_info"&#58;"2.13.5","release_type"&#58;"official","uptime"&#58;n9873&#125;,"GPS"&#58;&#123;"init"&#58;1,"qual"&#58;2,"lat"&#58;42.582024,"lon"&#58;-73.816956,"sats"&#58;8,"DOP"&#58;2&#125;,"cell"&#58;&#123;"init"&#58;4,"IMEI"&#58;"XXXXXXXXXX","sig_str"&#58;19,"number"&#58;"Not available","state"&#58;"registered"&#125;,"telemetry"&#58;&#123;"status"&#58;1,"state"&#58;"connected","dur"&#58;21164&#125;,"bt"&#58;&#123;"init"&#58;1&#125;,"logging"&#58;&#123;"status"&#58;0,"dur"&#58;0&#125;,"track"&#58;&#123;"status"&#58;2,"valid"&#58;true,"trackId"&#58;1427688095,"inLap"&#58;0,"armed"&#58;0&#125;,"imu"&#58;&#123;"init"&#58;true&#125;,"wifi"&#58;&#123;"active"&#58;true,"initialized"&#58;true,"ap"&#58;&#123;"active"&#58;true&#125;,"client"&#58;&#123;"active"&#58;true,"connected"&#58;false&#125;&#125;&#125;&#125;' | No JSON object could be decoded

&#91;RCPAPI      &#93; Message rx worker exception&#58; u'&#123;"status"&#58;&#123;"system"&#58;&#123;"model"&#58;"RaceCapture/Pro MK3","ver_major"&#58;2,"ver_minor"&#58;13,"ver_bugfix"&#58;5,"serial"&#58;"2F0022001751343034323934","git_info"&#58;"2.13.5","release_type"&#58;"official","uptime"&#58;102886&#125;,"GPS"&#58;&#123;"init"&#58;1,"qual"&#58;2,"lat"&#58;42.58202""lon"&#58;-73.81694,"sats"&#58;10,"DOP"&#58;1&#125;,"cell"&#58;&#123;"init"&#58;4,"IMEI"&#58;"XXXXXXXXXX","sig_str"&#58;19,"number"&#58;"Not available","state"&#58;"registered"&#125;,"telemetry"&#58;&#123;"status"&#58;1,"state"&#58;"connected","dur"&#58;84176&#125;,"bt"&#58;&#123;"init"&#58;1&#125;,"logging"&#58;&#123;"status"&#58;0,"dur"&#58;0&#125;,"track"&#58;&#123;"status"&#58;2,"valid"&#58;true,"trackId"&#58;1427688095,"inLap"&#58;0,"armed"&#58;0&#125;,"imu"&#58;&#123;"init"&#58;true&#125;,"wifi"&#58;&#123;"active"&#58;true,"initialized"&#58;true,"ap"&#58;&#123;"active"&#58;true&#125;,"client"&#58;&#123;"active"&#58;true,"connected"&#58;false&#125;&#125;&#125;&#125;' | Expecting ',' delimiter&#58; line 1 column 234 &#40;char 233&#41;

Is there a chance that using the 1.14.4.beta and 2.14.0 firmware corrupted my internal track DB?

Post by **brentp** » Sat Feb 23, 2019 6:11 pm

Hi,

We're reviewing this today, actually and will see if we can reproduce it. Feel free to send any logs and steps to [email protected] if you don't want to attach here as a .zip.

We will post here with any findings.

If through your testing you need to do a factory reset, we've updated the troubleshooting guide here with instructions on how to do it from the command line:
https://wiki.autosportlabs.com/RaceCapt ... aceCapture

Thanks,

Sawdust · Post by **Sawdust** » Tue Feb 26, 2019 12:42 am

Update to those interested, this has been resolved.

In my config I had a test script for the ShiftX2 lights. As suggested by Brent, I removed it. After rebooting the RCP, re-added the tracks, rebooted the RCP and the tracks displayed as expected in both the Win 7 app and on a FireHD 8 tablet.

Yes, I'm kicking myself for forgetting about the script, should have cleared that sooner when troubleshooting. Especially since I don't have the lights wired up yet...

Thanks again Brent for looking into this!

Post by **brentp** » Tue Feb 26, 2019 1:12 am

Hi,

Happy to help; however there is still a bug since you should be able to update tracks when a script is loaded. I emailed you a test firmware which should resolve it.

If it does, it will appear in the official 2.15.0 firmware release.

Thanks,

Sawdust · Post by **Sawdust** » Tue Feb 26, 2019 1:56 am

Confirmed that the new firmware works, it maintained both my saved tracks as well as the ShiftX2 test script.

As directed, I flashed from 2.13.5 to the provided firmware, reloaded my previous config file that had tracks and the script, rebooted the RCP and all the tracks as well as the script show up as expected. Tests done with the 1.13.1 Win 7 app.

Post by **brentp** » Tue Feb 26, 2019 2:00 am

Thanks so much for helping us test! The fix will show up in the 2.15.0 firmware, due out this week, if final testing goes as planned.