Re: CAN and bluetooth issues

Posted by Karlis on Jul 19, 2016; 7:45pm
URL: http://bluesaab-forum.90.s1.nabble.com/CAN-and-bluetooth-issues-tp540p546.html

Sorry it took me a while... Here are my two cents:

1. First things first, we need to determine which BT LEDs (and in what fashion) are blinking. If they blink alternatively that means RN52 is in discoverable mode and it should show up in phones Bluetooth settings. If only one (blue) LED is blinking, that means RN52 is in connectable/non-discoverable mode. With the latest code on Github, I've enabled "1-6" button control on IHU. Since you own a 9-3, you would have to hold button SEEK+ on IHU. This will force RN52 to go into discoverable mode. SEEK long press in the middle till beep works only on 9-5s.

2. In order to check RN52 settings and reprogram it, you will need to upload RN52-BT-PRG code (link in "Software" section) to the module. Since you are running everything on v3.3 PCB, please do short the 9600 pins. That will save you a lot of headache. Once the code is uploaded and terminal is opened @ 9600 baudrate, you should see two messages: "RN52 programming mode" and "CMD". Now RN52 is ready to accept commands. Type "V" (without quotes) and you should get the version of firmware on RN52. It should be 1.16. If it is less than that, you might want to upload newest firmware on RN52 using Microchips DFU utility (basically a simple "Click", "Click" -> "Next", "Next", "OK", "Done" MS Windows application).

3. CAN comms with the car - I believe one of CAN LEDs is flashing. Though it's doing it so fast, that sometimes even I myself wonder if I have CAN comms in place or what... :). What text are you seeing on the SID? One more thing to try would be to remove whatever CD you currently have in the unit and give it another test. Yeah, I know it sounds silly, but worth trying.