RaceCapture/Pro MK2 v2.7.1

[sigtrm]

Hi, I have several problems with new Mk2,

1) I cannot upgrade firmware to 2.5.7

Failed to Load Firmware
Unable to locate bootloader.
https://www.dropbox.com/s/91u16ckflzayeri/btl.png?dl=0

2) Cannto establish GSM data connection, led is blinkling slowly, ie. searching/connecting. Software lacks any kind of diagnostic info for GSM, as Cellural signal strength for example.
(sim is PIN free, works in regular mobile phone. PLUS GSM Carrier, Poland, Europe)

3) I have problems connecting to device, after some time it shows: Could not detect RaceCapture/Pro, only pc restart helps.(replugging restarting app doesnt work)

[brentp]

Hi,

Thanks for posting. First, let's get you updated on the firmware. Assuming you have the windows drivers installed, try following the "Alternate Method" steps for installing firmware, documented here:

http://autosportlabs.net/RaceCapturePro ... 2_Firmware

Let us know your progress; After we get firmware updated we can diagnose your GSM service in Poland.

[brentp]

Hi,

We just updated the RaceCapture app to 1.2.1 which has improvements around auto-redetection as well as some windows-specific changes to make firmware updating more robust. Could you try flashing firmware with the latest app when you have a chance?

http://autosportlabs.net/RaceCapturePro_Downloads

[sigtrm]

Hi,

We just updated the RaceCapture app to 1.2.1 which has improvements around auto-redetection as well as some windows-specific changes to make firmware updating more robust. Could you try flashing firmware with the latest app when you have a chance?

http://autosportlabs.net/RaceCapturePro_Downloads

Hi, thanks for fast reply, I did not expect that so I did not even bother to check forum over the weekend.

Alternate method upgrade went w/o problems.
Regarding GSM, Telemetry status LED is in searching/connecting state still.

[brentp]

Ok, great. Thanks for the update.

We're working on a 'system wide' status page that will show what's going on with the system. In the meantime, there is a system log you can monitor.

Go to configuration / scripting. There, change the drop-down box to 'debug', then check the box 'poll logfile'. Do this while trying to connect. Can you copy/paste the logfile to a reply here?

Also, can you share what APN settings and what telecom service you are using? If you call their tech support they may be able to tell you what APN setting you should use.

[sigtrm]

Ok, great. Thanks for the update.

We're working on a 'system wide' status page that will show what's going on with the system. In the meantime, there is a system log you can monitor.

Go to configuration / scripting. There, change the drop-down box to 'debug', then check the box 'poll logfile'. Do this while trying to connect. Can you copy/paste the logfile to a reply here?

Also, can you share what APN settings and what telecom service you are using? If you call their tech support they may be able to tell you what APN setting you should use.

I have tried various APN Settings, my Carrier Plus GSM has a few of them and none of those work, althought internet/internet APN settings works in all my M2M devices, like sierra wireless modems.a

Code: Select all

GPS: corrupt frame 
cellWrite: ATZ
Failed to init cell connection
device not connected. retrying..
init cell connection
cellWrite: +++
cellWrite: AT+CIPCLOSE
GPS: corrupt frame 
cellWrite: ATZ
cellWrite: ATZ
cellWrite: +++
cellWrite: AT+CIPCLOSE
GPS: corrupt frame 
SIM900: power cycling
cellWrite: AT
GPS: corrupt frame 
GPS: corrupt frame 
cellWrite: ATZ
cellWrite: ATZ
cellWrite: +++
cellWrite: AT+CIPCLOSE
SIM900: power cycling
cellWrite: AT
cellWrite: ATZ
cellWrite: ATZ
Failed to init cell connection
device not connected. retrying..
init cell connection
cellWrite: +++
cellWrite: AT+CIPCLOSE
GPS: corrupt frame 
GPS: corrupt frame 
cellWrite: ATZ
GPS: corrupt frame 
cellWrite: ATZ
cellWrite: +++
cellWrite: AT+CIPCLOSE
SIM900: power cycling
cellWrite: AT

[sigtrm]

some more logs from viewLog command.

BTW, I believe not all terminal commands are implemented? bc showTasks returns nothing.
My mistake, it works. Can I access some internals via terminal?

Code: Select all

RaceCapture/Pro MK2 > viewLog
Starting logging mode.  Hit "q" to exit
=timebase sr
Start OBD2 task
running lua script len(21)...done
lua memory usage: 5Kb
IMU init result=0
GPS: provisioning attempt
GPS: probing baud rate 921600
BT provision success
BT device initialized
GPS: probing baud rate 9600
GPS: module detected at 9600
Configuring GPS baud rate to 921600: fail
GPS: Error provisioning - could not configure baud rate
GPS: provisioning attempt
GPS: probing baud rate 921600
GPS: module detected at 921600
Configuring GPS update rate to 50: fail
GPS: Error provisioning - could not configure update rate
GPS: provisioning attempt
GPS: probing baud rate 921600
GPS: module detected at 921600
GPS: Configuring NMEA messages: fail
GPS: Error provisioning - could not configure NMEA messages
GPS: provisioning attempt
GPS: probing baud rate 921600
GPS: module detected at 921600
GPS: Configuring NMEA messages: win
GPS: provisioned
Failed to init cell connection
device not connected. retrying..
Failed to init cell connection
device not connected. retrying..

[brentp]

Are you powering over 12v while attempting telemetry connection? You need a 12v power supply when connecting via telemetry; USB power alone is insufficient.

See the full telemetry guide here: http://autosportlabs.net/RaceCapturePro ... _Telemetry

[sigtrm]

Are you powering over 12v while attempting telemetry connection? You need a 12v power supply when connecting via telemetry; USB power alone is insufficient.

See the full telemetry guide here: http://autosportlabs.net/RaceCapturePro ... _Telemetry

Thanks brentp, I should RTFM