USB connectivity vs Windows app version

[toga94m]

I know I've got a reputation here as "that guy with the antique tablet".. I've moved on, have a Kindle now that works great over Bluetooth. :) Today's issue is hardwired Windows vs the app. Laptop is Win8.1, 12GB RAM, Core i7 processor.

I've got a MK1 with latest 2.8.7 firmware, and have been working on a CAN script with megasquirt ECU. I've found that newer apps on Windows don't easily find the RCP hardware, even though it's hardwired to/powered by a USB port (configured as a COM port). This isn't related to Bluetooth - not trying to connect that way to the laptop. MK1 config does have bluetooth enabled though, but no bluetooth device is running the app, and the bluetooth dongle LED continues to blink (no connection).

Device manager says COM10 is RaceCapture/Pro   

driver is ver 6.0.2600.1 from 3/26/2007 autosportlabs.net

Device manager says COM 6, 7, and 9 are "Standard serial over Bluetooth link"

App ver 1.4.2 - works fine, detects & connects immediately, "Reading configuration" progress bar, downloads config and starts running no problem.

App ver 1.5.3 - tries several COM ports (6, 7, 9, 10), might say "Reading config" and identify the firmware as 2.8.7, but after that I immediately get the popup saying "Could not read configuration:" From then on it only tries one of the four COM ports - might be COM7 one time, or COM9 the next... but it's not iterating the 4 ports that 1.5.3 finds.

App ver 1.6.0 - same as 1.5.3

After failing on 1.5.3 or 1.6.0, I can relaunch 1.4.2 without pulling the USB cable (still powering the MK1) and it reconnects immediately. I just downloaded and installed 1.5.3 tonight as a test. I also have 1.4.1 and 1.3.13 on this laptop, and they connect happily thru COM10 like 1.4.2

However............. if I turn off Bluetooth on the laptop (disabling those COM ports from the inventory, now device manager only shows COM10) 1.4.2 and 1.6.0 will both connect quickly to the wired USB port. But............ I wouldn't think I'd have to shut off bluetooth for the app to find the wired RCP - it worked fine up thru 1.4.2

tom

[Brent Picasso]

Hi Tom,

Your last part is key - we've never tested it with BT on Windows as we always intended it to be via USB.  The communications for streaming is subtly different with Bluetooth vs USB and that's why it's likely hanging up when it tires to connect via Bluetooth. 

-Brent

--
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/34b830e5-0fb5-4d21-9190-b2190d855022%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Brent Picasso

Autosport Labs

Technology for Race and Street