Re: How-to/tutorial?
Posted by
homerisback on
Mar 31, 2016; 12:31pm
URL: http://bluesaab-forum.90.s1.nabble.com/How-to-tutorial-tp106p309.html
I checked a few things :
When module
isn't connected to car, the audio system is OK in Tech 2 and CDChanger & Telephone are missing, which is logical so far. As soon as the module
is connected, CDChanger is OK and audio system starts to appear unstable in Tech 2 (OK, missing, OK and so on...) but functionning correctly unless doesn't "see" the BlueSaab and doesn't allow switching to CDC source.
While module is connected, LEDs seem to have the right behaviour :
Power : ON
CAN1 : very fast blink
CAN2 : rare blink
BT1 & BT2 : flash alternately while waiting for a connection. Only red BT LED flashes when connected : 3 short flashes without music playing ; 1 long flash and 1 short flash when music plays on the phone.
2 of my 3 modules show the same behaviour, the third one won't light any BT LED and isn't discoverable by my phone (RN52 might be uncorrectly soldered or damaged, I presume), while other LEDs have the right behaviour (PWR & CANs).
I noticed that CAN High is connected to green wire and CAN Low to the white wire. Didnt' try to swap them yet or check if colors are the right ones...
I did a little tune on my car that involve VIN number : I swapped my MIU without turbo gauge to one with the turbo needle. To have the turbo needle moving, I had to change my VIN engine letter (from C to G) in DICE. I did divorce then mary again my audio system to keep it working and accept the new VIN. My trionic 7 still have the original VIN in memory, I didn't have to change it to keep the car running... Does the module use VIN to declare itself married to the car and emulate the CDC ?
Apart the Atmega328 which isn't "P" and this tune, I can't find any good resaon for my issue O_o'
01' 9.3 SE Conv - AS3 - Nexus 5 Android M 6.0.1 - BlueSaab v4.2 + Amp - Latest CDC repo.