v1.4.2 app released to beta, and MK1 2.8.6 firmware released

83 views
Skip to first unread message

Brent Picasso

unread,
Feb 2, 2016, 1:44:02 PM2/2/16
to AutosportLabs Beta Testers
1.4.2 released to the google beta - thank you all for testing / feedback.  1.4.3 will have additional bug fixes and 1.5.0 will hold new features; 1.4.3 may occur as a release or might just get folded into 1.5.0.

We also released MK1 firmware 2.8.6 with a number of fixes seen in MK2 2.8.7.  Notably, MK1 users should use the 1.4.2 app ASAP as we've made some important fixes around config writing failures.

Blog post here: https://www.autosportlabs.com/racecapture-app-v1-4-2-and-racecapturepro-mk1-firmware-v2-8-6-released/


===1.4.2==
* Connect to the first RaceCapture device it can detect, regardless of the name provided
* Improve analysis data query performance; don't block user interface for long operations; show spinner
* Improve load time by targeting Android 4.4 / API level 19
* Add selected track name to analysis map view
* Added debugging option for API messages
* Draw GPS path correctly if no track map is loaded
* Automatically select a default channel (Speed) as needed
* Only show active channels in dashboard channel selector view
* Prevent status querying thread from multiplying when re-connect occurs
* Show a lap/color trace legend for selected laps
* Show a heatmap color legend when heatmap channels are enabled
* Make it easier to differentiate heatmap paths by drawing them at varying widths
* Add app version to status page
* Firmware update screen improvements (show reminder to save config before updating)
* Automatically extend min/max values upon importing analysis data
* Made app exit more cleanly / address exceptions on program exit

toga94m

unread,
Feb 2, 2016, 8:00:44 PM2/2/16
to AutosportLabs Beta Testers
Yay for MK1! So here's what happened tonight... updated the MK1 to 2.8.6 with no troubles; older app on Windows connects by USB and identifies firmware at 2.8.6   However I can't get the tablet (beta now updated to 1.4.2 {thanks for adding version# to Status/Application!} ) to connect to the bluetooth dongle anymore. I restarted the tablet, un-paired and re-paired, but the dongle won't stop blinking. All my BT devices are scanned by the app by name (used to be COM ports, not device names) but nothing connects.  The device (on the tablet) is called RaceCapturePro - should it be named something else for the detection to work?

5 minutes later (after typing) I see the dongle's LED is now steady, but the app still won't connect to it. The app's "System Status" tab only offers Application - no other options, though I guess that makes sense if it can't talk to the hardware.

Unplugged MK1 from USB on laptop, powered by120VAC adapter; restarted tablet. Ensured BT is active on tablet, start 1.4.2 app again.. App continues cycling thru my BT devices (Toshiba, EFI ANALYTICS, Targus Speaker, OBDII, MCM (audio device), iBT-GPS, laptop, RaceCapturePro)

During this scan, the dongle's LED will light steady for a half-second at a time as the app scans potential partners, then goes back to blinking. A few minutes later I realized this was because my laptop was trying to pair to the RCP dongle.. so I shut off laptop bluetooth and the dongle doesn't stop blinking anymore. Still won't connect..... does the MK1 dongle behave differently from the MK2 bluetooth connection?

tom


On Tuesday, February 2, 2016 at 1:44:02 PM UTC-5, Brent Picasso wrote:
1.4.2 released to the google beta - thank you all for testing / feedback.  1.4.3 will have additional bug fixes and 1.5.0 will hold new features; 1.4.3 may occur as a release or might just get folded into 1.5.0.

We also released MK1 firmware 2.8.6 with a number of fixes seen in MK2 2.8.7.  Notably, MK1 users should use the 1.4.2 app ASAP as we've made some important fixes around config writing failures.


toga94m

unread,
Feb 2, 2016, 8:02:07 PM2/2/16
to AutosportLabs Beta Testers
Oh of course............... once I post, the hardware has finally connected and downloaded the RCP MK1 configuration......... looks good. More testing...

tom

toga94m

unread,
Feb 2, 2016, 8:17:05 PM2/2/16
to AutosportLabs Beta Testers
Okay - what???  Header from logfile off SD card :

"Interval"|"ms"|0|0|1,"Utc"|"ms"|0|0|1,"Battery"|"Volts"|0.0|20.0|1,"AccelX"|"G"|-3.0|3.0|25,"AccelY"|"G"|-3.0|3.0|25,"AccelZ"|"G"|-3.0|3.0|25,"Yaw"|"Deg/Sec"|-300.0|300.0|25,"Latitude"|"Degrees"|-180.0lazy dog
180.0lazy dog
10,"Longitude"|"Degrees"|-180.0lazy dog
180.0lazy dog
10,"Speed"|"MPH"|0.0|150.0|10,"Distance"|"Miles"|0.0|0.0|10,"Altitude"|"Feet"|0.0|4000.0|10,"GPSSats"|""|0|20|10,"GPSQual"|""|0|5|10,"GPSDOP"|""|0.0|20.0|10,"LapCount"|""|0|0|10,"LapTime"|"Min"|0.0|0.0|10,"Sector"|""|0|0|10,"SectorTime"|"Min"|0.0|0.0|10,"PredTime"|"Min"|0.0|0.0|5,"ElapsedTime"|"Min"|0.0|0.0|10,"CurrentLap"|""|0|0|10

Looks like remnants of a test in /src/sdcard/sdcard.c  based on searching the git...

tom

toga94m

unread,
Feb 2, 2016, 9:00:21 PM2/2/16
to AutosportLabs Beta Testers
Maybe a buffer overflow in  modp_ftoa()  when sending -180.0 to the header, with precision of 6??  The values of -300 and 300 for deg/sec work, but they're at precision of 1.  6 digits of precision plus decimal plus 3 digits plus sign ends up at 11 characters, so should char buf[11] in appendFloat()  be increased a few chars?

tom

Brent Picasso

unread,
Feb 2, 2016, 9:08:28 PM2/2/16
to toga94m, AutosportLabs Beta Testers

Hi tom, can you post your config here so we can repro? Thanks :)

Brent Picasso
Autosport Labs
Technology for Race and Street

--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-...@googlegroups.com.
To post to this group, send email to autosportlabs...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/autosportlabs-beta-testers/304b8311-8b22-495d-a9ff-0f12eab5dd6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Brent Picasso

unread,
Feb 2, 2016, 9:14:28 PM2/2/16
to toga94m, AutosportLabs Beta Testers

Nvm, looks like we reproduced it here.

Brent Picasso
Autosport Labs
Technology for Race and Street

toga94m

unread,
Feb 2, 2016, 9:17:01 PM2/2/16
to AutosportLabs Beta Testers, pint...@gmail.com
I didn't change anything in the config after flashing up to 2.8.6 ... Should that be a standard step: wipe & redo config after a reflash? Here's what i just saved out from the MK1, using the older windows app.

tom


On Tuesday, February 2, 2016 at 9:08:28 PM UTC-5, Brent Picasso wrote:

Hi tom, can you post your config here so we can repro? Thanks :)

Brent Picasso
Autosport Labs
Technology for Race and Street

On Feb 2, 2016 6:00 PM, "toga94m" <pint...@gmail.com> wrote:
Maybe a buffer overflow in  modp_ftoa()  when sending -180.0 to the header, with precision of 6??  The values of -300 and 300 for deg/sec work, but they're at precision of 1.  6 digits of precision plus decimal plus 3 digits plus sign ends up at 11 characters, so should char buf[11] in appendFloat()  be increased a few chars?

tom

On Tuesday, February 2, 2016 at 8:17:05 PM UTC-5, toga94m wrote:
Okay - what???  Header from logfile off SD card :

"Interval"|"ms"|0|0|1,"Utc"|"ms"|0|0|1,"Battery"|"Volts"|0.0|20.0|1,"AccelX"|"G"|-3.0|3.0|25,"AccelY"|"G"|-3.0|3.0|25,"AccelZ"|"G"|-3.0|3.0|25,"Yaw"|"Deg/Sec"|-300.0|300.0|25,"Latitude"|"Degrees"|-180.0lazy dog
180.0lazy dog
10,"Longitude"|"Degrees"|-180.0lazy dog
180.0lazy dog
10,"Speed"|"MPH"|0.0|150.0|10,"Distance"|"Miles"|0.0|0.0|10,"Altitude"|"Feet"|0.0|4000.0|10,"GPSSats"|""|0|20|10,"GPSQual"|""|0|5|10,"GPSDOP"|""|0.0|20.0|10,"LapCount"|""|0|0|10,"LapTime"|"Min"|0.0|0.0|10,"Sector"|""|0|0|10,"SectorTime"|"Min"|0.0|0.0|10,"PredTime"|"Min"|0.0|0.0|5,"ElapsedTime"|"Min"|0.0|0.0|10,"CurrentLap"|""|0|0|10

Looks like remnants of a test in /src/sdcard/sdcard.c  based on searching the git...

tom

On Tuesday, February 2, 2016 at 8:02:07 PM UTC-5, toga94m wrote:
Oh of course............... once I post, the hardware has finally connected and downloaded the RCP MK1 configuration......... looks good. More testing...

tom

On Tuesday, February 2, 2016 at 8:00:44 PM UTC-5, toga94m wrote:
Yay for MK1! So here's what happened tonight... updated the MK1 to 2.8.6 with no troubles; older app on Windows connects by USB and identifies firmware at 2.8.6   However I can't get the tablet (beta now updated to 1.4.2 {thanks for adding version# to Status/Application!} ) to connect to the 

--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-testers+unsub...@googlegroups.com.
newmk1-286config.rcp

Andrew Stiegmann

unread,
Feb 2, 2016, 9:32:45 PM2/2/16
to toga94m, AutosportLabs Beta Testers
Hey Tom,

   Your analysis is spot on.  There is a buffer overflow happening in the modp_ftoa function.  The precision is 6 and the length of the value is 12, thus no null terminator and thus the overflow.  I'm putting together a fix now.  Issue is tracked here: https://github.com/autosportlabs/RaceCapture-Pro-firmware-mk1/issues/9

To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-...@googlegroups.com.

To post to this group, send email to autosportlabs...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/autosportlabs-beta-testers/3a5c96ec-4c37-48f0-80b9-e37edc415e4a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--


toga94m

unread,
Feb 2, 2016, 9:43:41 PM2/2/16
to AutosportLabs Beta Testers, pint...@gmail.com
Thank the "lazy dog" - he makes a buffer overflow a lot easier to spot. :)

Side note - I did a serial port 'resetConfig' and more logging, and same behavior.. I've got a copy of the new/default config, and logfile, but won't bother uploading it if you're content with the root cause.

tom
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-testers+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-testers+unsub...@googlegroups.com.

To post to this group, send email to autosportlabs...@googlegroups.com.



--


toga94m

unread,
Feb 2, 2016, 9:52:13 PM2/2/16
to AutosportLabs Beta Testers, pint...@gmail.com
Side note ... my search found two places in the source where the function is defined. I'm assuming the makefile only brings in one of them?

lib_lua/src/modp_numtoa.c 
src/util/modp_numtoa.c 

Andrew Stiegmann

unread,
Feb 2, 2016, 10:26:59 PM2/2/16
to toga94m, AutosportLabs Beta Testers
Hey Tom,

   Attached is a build with the fix.  There is still another outstanding issue tracked at https://github.com/autosportlabs/RaceCapture-Pro-firmware-mk1/issues/11 but its less severe.  Its still a zip file... it just has that suffix to fool GMail.

To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-...@googlegroups.com.

To post to this group, send email to autosportlabs...@googlegroups.com.



--


--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-...@googlegroups.com.

To post to this group, send email to autosportlabs...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/autosportlabs-beta-testers/98e6185e-4c82-443a-8524-5140a3f92828%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--


RaceCapturePro_MK1_2.8.7.zip.stupidGmail

toga94m

unread,
Feb 2, 2016, 11:08:12 PM2/2/16
to AutosportLabs Beta Testers, pint...@gmail.com
once I came back and looked at the topic, and found the upload, I grabbed & reflashed. Headers cured.

"Interval"|"ms"|0|0|1,"Utc"|"ms"|0|0|1,"Battery"|"Volts"|0.0|20.0|1,"AccelX"|"G"|-3.0|3.0|25,"AccelY"|"G"|-3.0|3.0|25,"AccelZ"|"G"|-3.0|3.0|25,"Yaw"|"Deg/Sec"|-300.0|300.0|25,"Latitude"|"Degrees"|-180.0|180.0|10,"Longitude"|"Degrees"|-180.0|180.0|10,"Speed"|"MPH"|0.0|150.0|10,"Distance"|"Miles"|0.0|0.0|10,"Altitude"|"Feet"|0.0|4000.0|10,"GPSSats"|""|0|20|10,"GPSQual"|""|0|5|10,"GPSDOP"|""|0.0|20.0|10,"LapCount"|""|0|0|10,"LapTime"|"Min"|0.0|0.0|10,"Sector"|""|0|0|10,"SectorTime"|"Min"|0.0|0.0|10,"PredTime"|"Min"|0.0|0.0|5,"ElapsedTime"|"Min"|0.0|0.0|10,"CurrentLap"|""|0|0|10
18630,1454472354655,,-0.05,-0.04,0.99,1.7,,,,,,,,,,,,,,,
20880,1454472356905,,-0.05,-0.03,0.99,1.7,43.082993,-73.773033,0.21,0.0,84.1,9,1,1.2,0,0.0,-1,0.0,0.0,0.0,0
20920,1454472356945,,-0.05,-0.03,0.99,1.7,,,,,,,,,,,,,,,
20960,1454472356985,,-0.05,-0.03,1.0,1.7,,,,,,,,,,,,,,,
20980,1454472357005,,,,,,43.082993,-73.773033,0.21,0.0,84.1,9,1,1.2,0,0.0,-1,0.0,,0.0,0
21000,1454472357025,,-0.05,-0.03,1.0,1.7,,,,,,,,,,,,,,,
21040,1454472357065,,-0.05,-0.03,1.0,1.7,,,,,,,,,,,,,,,
21080,1454472357105,,-0.05,-0.03,1.0,1.7,43.082993,

That was quick!

tom
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-testers+unsub...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-testers+unsub...@googlegroups.com.

To post to this group, send email to autosportlabs...@googlegroups.com.



--


--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-testers+unsub...@googlegroups.com.

To post to this group, send email to autosportlabs...@googlegroups.com.



--


Andrew Stiegmann

unread,
Feb 3, 2016, 10:36:26 AM2/3/16
to toga94m, AutosportLabs Beta Testers
Excellent.  Thanks for letting us know Tom.  Brent or I will post when a new release gets spun.

To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-...@googlegroups.com.

To post to this group, send email to autosportlabs...@googlegroups.com.



--


--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-...@googlegroups.com.

To post to this group, send email to autosportlabs...@googlegroups.com.



--


--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-...@googlegroups.com.

To post to this group, send email to autosportlabs...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/autosportlabs-beta-testers/420f474e-f037-49f7-9593-405da4b499f7%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--


toga94m

unread,
Feb 15, 2016, 10:04:36 PM2/15/16
to AutosportLabs Beta Testers
Following up here because I first saw this issue on 1.4.2, and it's still in 1.4.3.

The app on my old ME172X Android tablet doesn't easily connect to RCP 2.8.6 or 2.8.7 - takes a lot of scanning/retrying before it finally hooks up. Here's the tail of the app log after it finally connected tonight. Maybe there's a timeout that got tightened up since a previous app version? As a n00b I have a lot more trouble chasing python source, compared to firmware source...
 +==1.4.2==
 +* Connect to the first RaceCapture device it can detect, regardless of the name provided
 +

[AndroidComms] detected ports: MCM,BECAUSERACECAR,RaceCapturePro
[RCPAPI      ] Searching for device on all ports
[RCPAPI      ] Trying MCM
[AndroidComms] Opening connection MCM
[AndroidComms] after open
[RCPAPI      ] attempting to recover connection
[RCPAPI      ] Giving up on MCM
[AndroidComms] close
[RCPAPI      ] Trying BECAUSERACECAR
[AndroidComms] Opening connection BECAUSERACECAR
[AndroidComms] after open
[RCPAPI      ] attempting to recover connection
[RCPAPI      ] Giving up on BECAUSERACECAR
[AndroidComms] close
[RCPAPI      ] Trying RaceCapturePro
[AndroidComms] Opening connection RaceCapturePro
[AndroidComms] after open
[RCPAPI      ] attempting to recover connection
[RCPAPI      ] Giving up on RaceCapturePro
[AndroidComms] close
[RCPAPI      ] Did not find device
[AndroidComms] close
[RCPAPI      ] auto detect finished. port=None

[RCPAPI      ] Starting auto-detect
[AndroidComms] detected ports: MCM,BECAUSERACECAR,RaceCapturePro
[RCPAPI      ] Searching for device on all ports
[RCPAPI      ] Trying MCM
[AndroidComms] Opening connection MCM
[AndroidComms] after open
[RCPAPI      ] attempting to recover connection
[RCPAPI      ] Giving up on MCM
[AndroidComms] close
[RCPAPI      ] Trying BECAUSERACECAR
[AndroidComms] Opening connection BECAUSERACECAR
[AndroidComms] after open
[RCPAPI      ] attempting to recover connection
[RCPAPI      ] Giving up on BECAUSERACECAR
[AndroidComms] close
[RCPAPI      ] Trying RaceCapturePro
[AndroidComms] Opening connection RaceCapturePro
[AndroidComms] after open
[RCPAPI      ] attempting to recover connection
[RCPAPI      ] Giving up on RaceCapturePro
[AndroidComms] close
[RCPAPI      ] Did not find device
[AndroidComms] close
[RCPAPI      ] auto detect finished. port=None

[RCPAPI      ] Starting auto-detect
[AndroidComms] detected ports: MCM,BECAUSERACECAR,RaceCapturePro
[RCPAPI      ] Searching for device on all ports
[RCPAPI      ] Trying MCM
[AndroidComms] Opening connection MCM
[AndroidComms] after open
[RCPAPI      ] attempting to recover connection
[RCPAPI      ] Giving up on MCM
[AndroidComms] close
[RCPAPI      ] Trying BECAUSERACECAR
[AndroidComms] Opening connection BECAUSERACECAR
[AndroidComms] after open
[RCPAPI      ] attempting to recover connection
[RCPAPI      ] Giving up on BECAUSERACECAR
[AndroidComms] close
[RCPAPI      ] Trying RaceCapturePro
[AndroidComms] Opening connection RaceCapturePro
[AndroidComms] after open
[RCPAPI      ] attempting to recover connection
[RCPAPI      ] Giving up on RaceCapturePro
[AndroidComms] close
[RCPAPI      ] Did not find device
[AndroidComms] close
[RCPAPI      ] auto detect finished. port=None

[RCPAPI      ] Starting auto-detect
[AndroidComms] detected ports: MCM,BECAUSERACECAR,RaceCapturePro
[RCPAPI      ] Searching for device on all ports
[RCPAPI      ] Trying MCM
[AndroidComms] Opening connection MCM
[AndroidComms] after open
[RCPAPI      ] attempting to recover connection
[RCPAPI      ] Giving up on MCM
[AndroidComms] close
[RCPAPI      ] Trying BECAUSERACECAR
[AndroidComms] Opening connection BECAUSERACECAR
[AndroidComms] after open
[RCPAPI      ] attempting to recover connection
[RCPAPI      ] Giving up on BECAUSERACECAR
[AndroidComms] close
[RCPAPI      ] Trying RaceCapturePro
[AndroidComms] Opening connection RaceCapturePro
[AndroidComms] after open
[RCPAPI      ] Message rx worker exception: 715,0,-0.14,0.0,0.99,0.9,123]}} | <type 'exceptions.Exception'>
[RCPAPI      ] Found device version RCP 2.8.7 (s/n# ) on port: RaceCapturePro
[DataBusPump ] Sample Meta is stale, requesting meta
[RCPAPI      ] sending meta
[DataBusPump ] sample_worker starting
[RCPAPI      ] auto detect finished. port=RaceCapturePro
[StatusPump  ] status_worker starting
[RCPAPI      ] Execute Sequence begin
[DataBusPump ] Async sampling detected
[DataBusPump ] sample_worker exiting
[RcpConfig   ] Config version 2.8.7 Loaded
[RCPAPI      ] Execute Sequence complete

tom


On Tuesday, February 2, 2016 at 8:02:07 PM UTC-5, toga94m wrote:

Brent Picasso

unread,
Feb 15, 2016, 10:19:00 PM2/15/16
to toga94m, AutosportLabs Beta Testers

Yes. The beta scans through all available BT devices. I would assume it would connect faster if you unpaired the other bluetooth devices,  correct?

There's an issue on track for 1.4.4 to remember the last connected BT name.

Brent Picasso
Autosport Labs
Technology for Race and Street

--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-...@googlegroups.com.
To post to this group, send email to autosportlabs...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/autosportlabs-beta-testers/1735b4dd-82c6-422f-8015-2ffb1b989c5c%40googlegroups.com.

toga94m

unread,
Feb 15, 2016, 11:03:03 PM2/15/16
to AutosportLabs Beta Testers, pint...@gmail.com
I've already pared the tablet down to three paired BT devices, and it enumerates & scans all three nicely. Just won't connect, or eventually does slowly.

More followup... I'm having similar trouble on my Win8 laptop over bluetooth as well. No trouble connecting to the bluetooth COM port via putty - it hooks up instantly and starts spewing telemetry data at my console. But trying to get either 1.4.1 or 1.4.2 app to connect over bluetooth just doesn't happen. I'm thinking the RCP MK1 is so busy sending telemetry that it doesn't see/respond to the "hi there" from the app, before the app gives up and moves on. When trying from the Win8 app, I see the MK1 bluetooth dongle go solid for a second during the scan, then it goes back to blinking. So it seems to be a protocol/negotiation issue rather than a hardware hookup issue. 1.4.1 and 1.4.2 both hook up instantly when connected by USB cable. 

How much junk rejection does the app allow before giving up on finding a valid response to its "hello there"? If the telemetry buffer has to drain before the "I'm here" response is sent, the app might give up too soon?

I tried a few configuration changes -

I turned off Background Streaming and wrote the config, moved USB from laptop to AC power and tried again - no help
I turned off Bluetooth Adapter and wrote the config, moved USB from laptop to AC power and tried again - no help.
I turned on Bluetooth Adapter and wrote the config, moved USB from laptop to AC power and tried again - no help. 
I turned off laptop bluetooth and turned on tablet bluetooth, powercycled rcp mk1 and tried 1.4.3 app - no go.
Restart tablet which resets Bluetooth. Tried the 1.4.3 app again... and after 3 minutes of trying, it finally hooks up. Dashboard screen of green numbers updates continually as expected. Until all my shaking made the USB (power) cable fall out and it dropped connection. But it resumed within 15 seconds when power came back.

tom
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-testers+unsub...@googlegroups.com.

Justin Lee

unread,
Jul 13, 2016, 9:41:46 AM7/13/16
to AutosportLabs Beta Testers
Is RaceCapturePro_MK1_2.8.7 the current most updated release we should be using on the MK1?  Should we still be using it with the 1.4.2app?

Thanks,
Justin

Brent Picasso

unread,
Jul 13, 2016, 12:14:32 PM7/13/16
to Justin Lee, AutosportLabs Beta Testers
Hi Justin,

the currently latest app (1.6.0) works with the latest MK1 firmware (2.8.7). 

The latest app and firmware images can be downloaded from here: http://podium.live/software 

Thanks!

--
You received this message because you are subscribed to the Google Groups "AutosportLabs Beta Testers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to autosportlabs-beta-...@googlegroups.com.

To post to this group, send email to autosportlabs...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/autosportlabs-beta-testers/84508a5b-86e9-4ff0-961f-cf7731e5a7c6%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Reply all
Reply to author
Forward
0 new messages