I've encountered strange problem. We're using MK2 Pro module with bluetooth and telemetry modules, connected via CAN to EmuMaster ECU. Everything was working correctly - I've written CAN integration script based on examples on wiki and configured everyting - until today. Data from the CAN is not logged, and it's not sent to smartphone via bluetooth, UNLESS I connect RCP to my PC via USB. If i connect USB and switch on 12V power - everything is OK, even after disconnecting USB. If I just plug 12V on, the GPS, telemetry and bluetooth modules are all working, but there's no CAN data. To bo honest, I have no idea what's going on.
One more thing I've noticed is that there are new informations in RCP app - "131unexpected id", and there was also "168unexpected id".
You can download RCP config file from here: https://drive.google.com/file/d/0B_NVb0 ... sp=sharingLogging started
open rc_16.log
flush file buffer
flush file buffer
GPS: provisioning attempt
GPS: probing baud rate 921600
success
BT: Init complete
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
131unexpected id
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
131unexpected id
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
131unexpected id
GPS: module detected at 921600
GPS: Configuring NMEA messages: win
GPS: configure message type: win
GPS: configure navigation data message interval: 168unexpected id
win
GPS: Configuring Gnss Navigation Mode: 168unexpected id
win
GPS: Disable NMEA messages: 168unexpected id
win
GPS: provisioned
I would really appreciate any hints. We're on Shell Eco-Marathon right now, and we're unable to log anything
//edit: i've also uploaded new firmware to RCP - nothing has changed.
//edit2: Update - RCP doesn't need connection to PC, it just needs power via USB - for example from power bank. I think that there might be a problem with voltage regulator - I can't think of any other explanation.