Re: It enters CDC mode, but doesn't show up in BlueTooth

Posted by Seth on May 22, 2016; 2:45am
URL: http://bluesaab-forum.90.s1.nabble.com/It-enters-CDC-mode-but-doesn-t-show-up-in-BlueTooth-tp331p410.html

I would also check for good connections on the cdc connector (maybe on back of ihu?)...but it does sound like a poor ground somewhere. Might also wanna check for the body grounds near the ihu, and trunk. 

On May 21, 2016, at 22:42, Pilkerton [via BlueSaab Forum] <[hidden email]> wrote:

Yes, the BT1 and BT2 LEDs were flashing alternatively, indicating the RN52 was supposedly in "discoverable" mode and ready to pair. However, it never broadcast itself. After trying various things (including manually putting it into "discoverable" mode by sending it the command over serial) and still being unable to get it to broadcast, I gave up and replaced it with a fresh RN-52 from eBay which worked a treat. After using RN52-BT-PRG to adjust the default volume levels and then flashing with v3.0 firmware, everything is functional.

However, I now have the problem of the hideous noise on one channel while the engine is running. The noise is accompanied by a higher-pitched, RPM-related whine that's lower in volume. Yesterday (before I adjusted the default volume levels), it was on the right channel. Today, it's on the left channel. It's OK for listening if I crank the balance to the good channel.

Karlis, I think you mentioned in another post to check the IHU for corroded ground connections. So I would just pull the IHU from the console and inspect the connectors around back? This is a 9-3 2000 with the CDC connector located near the antenna.

---

If you reply to this email, your message will be added to the discussion below:

http://bluesaab-forum.2349123.n4.nabble.com/It-enters-CDC-mode-but-doesn-t-show-up-in-BlueTooth-tp331p409.html

To start a new topic under Hardware, email [hidden email]
To unsubscribe from Hardware, click here.
NAML