help getting strarted please

[Hutchie]

Hi,

I've eventually got around to installing my RCP and Bluetooth module just using standard GPS & accelerometer stuff - oh and an RPM input for now.

However, when I tried to save my configuration after 96% complete it kept displaying an "Unknown Error" error message.

I couldn't figure out how to validate what version of the firmware is installed so I just thought I'd update to the latest anyway (I'm using RaceAnalyzer 1.1.14).

I loaded the bootloader drivers OK but when I tried to flash the update it started ok but just sat on waiting for USB device with the dots just incrementing. I've tried rebooting the machine etc. but still just keeps getting stuck at the same point.

Interestingly, if I look for the COM port, I can no longer see anything - the "Ports" has completely vanished from the Device Manager.

Anyone able to help pleeeeease!

Many thanks in advance.

Phil.

[Hutchie]

I've managed to resolve this using another PC (which is old and running Windows XP).
Out of interest, what had happened was:

1) It turns out that I installed the wrong drivers initially - I used the ones for the latest version of the firmware but my RCP came with 1.1.10 installed! - I assume this is what gave me the error trying to read the configuration.

2) I don't know what went wrong with the flasher etc. but it's possible I might have installed the bootloader drivers without the RCP connected - and even if it was connected, could the fact that the wrong version of the other drivers were installed have caused the hanging on "waiting for device to appear on USB" problem?

Anyway, I managed to update the firmware on my other PC having established all of the above, then when connecting RCP to my original Laptop I was asked to update the drivers - which I did and all now works - I can also see the Ports again on my lap top (which is running windows 7).

[rlogan]

I have the same issue...I guess I will have to try a new computer. I assumed that since I just bought mine in the last month that it was using the later driver...I guess I was wrong.

[Hutchie]

Hi Riogan,

I hoped there might have been a better explanation forthcoming, but if my experience helps then that's good?
It just seems possible that the new driver is not backwardly compatible with old firmware -mabe if you get the wrong mix of newer driver and older firmware the whole thing goes screwey. I don't know if your best off installing old drivers first in the hope that an older driver/ newer firmware combination may be more tolerant - just my amateur musings!
Good luck!!

[andylaurence]

It says on the downloads page that you should use the older drivers for the older firmware, so if your RCP is running 1.1.x, then you install the old drivers to update it to 1.2.x. That's what I did and it updated the firmware OK. I then couldn't connect to the RCP because I had the old drivers and the new firmware, so I installed the later drivers and it all burst into life.