BlueSaab with '04 9-5 AS3 with Denso NAV

[jelleisbleij]

Just to be sure... will de BlueSaab work with my '04 9-5 AS3 headunit with Denso navigation? (Do have a CDC in the booth of my 9-5)

Thanks!

[sloth]

Nope :( it only works with the head units without navigation.

[Karlis]

I would let forum member "Ziq" to chime in. He's been working on a very similar project on his SAAB with a Navigation unit. PM him and he might give you a better insight.

[jelleisbleij]

Thanks Karlis, will PM Ziq.

[jelleisbleij]

Just received a mail from Ziq; he thinks the BlueSaab module should work with the Denso Navigation unit.
Main difference is that the SID is not used for displaying any info coming from the Denso Nav, but I don't mind that...

I guess I'll have to get a unit and find out, with al the experts on this forum we might just get it working allright :-)

[jelleisbleij]

Update; I've purchased a unit from homerisback. It's a v3.2 unit with the latest software version.

Just received it and installed it, works right away. Steeringwheel controls work, have not tested the headunit controls yet, will test those later (forgot to test them just now, will do later when I have more time).

Touchscreen does not display CDX at first, after connecting to the Bluesaab unit via bluetooth it showed up (not sure if it was because the unit was still booting, or doesn't show itself until connected to via bluetooth).
Was able to select source via touchscreen after it showed up, and I could play music right away.

Touchscreen showed disc 2, track 1 as playing (but this could be because I had disc 2 playing before I disconnected the CDX, not sure).

As expected SID does not show anything as it's not used by the headunit in this setup (Denso navigation, AS3).

Cheers

[Karlis]

Yay! Thanks for the feedback! Now we know that BlueSaab works (sort of) on cars with navigation. :) Keep us posted. We would really like to know how the module behaves on cars with NAV.

[jelleisbleij]

Coming days I'll test some more and keep you guys posted on what works or does not work as it should.

[jelleisbleij]

Ok, the unit has been working fine for a week now.
All hardware buttons work, software buttons on the HU do not do anything it seems.

But since this morning I could not connect to the Bluesaab (v3.2 with V3.6 software), unit was not being discovered by my phone.

After opening it, both bluetooth LED indicators were off.
After unplugging and plugging the unit both BT1 and BT2 (red and blue) flashed 3 times. Searched on this forum and it seems that the RN52 has gone into DFU (firmware update?) mode.

Any tips how to get it out of DFU?

Thanks.

[Seth]

Yes, that definitely sounds/looks like DFU mode. Are you sure the switch is in NORMAL mode, not DFU mode? Try switching it back and forth a few times...I'm not super happy with this switch...I've had a few that don't work 100% right (have to bump them just right to switch, etc).

If that doesn't work, then make sure that R12 (47k resistor) is good, and that R11 (22k resistor) is good...DFU mode is when GPIO3 is pulled high. But that shouldn't happen if the switch is in Normal mode (and there's even a diode to prevent GPIO3 from being pulled high but apparently that doesn't work, hence why I left the switch there).

[jelleisbleij]

Left my multimeter at work, so can't measure anything today, but I tried the switch (even desoldered it).
Reflowed both resistors. Still going into DFU mode unfortunately. Can't check if the resistors have failed, but I guess they shouldn't, or are they known to fail?

[Seth]

No, they haven't been known to fail, just thinking of why GPIO3 is being pulled high...and with switch removed, that leaves R12 pulling it to gnd...which is good (non-DFU mode)...so i'm not sure wtf is going on...a meter will def help.

can you post pictures of your pcb for us? I can try to see if anything looks out of whack...

[jelleisbleij]

Also reflowed all RN52 connections; still same result.

Pics of both sides of the pcb:

https://goo.gl/photos/yEgm2NYUtuH1H36u6
https://goo.gl/photos/j1vtoW1z7RsPWBSeA

[Seth]

Thanks for the photos. I don't see anything wrong...

And without a meter, I would try removing R11 (22k) and/or D3, and/or the switch. That will ensure that gpio3 doesn't have a way to get pulled high and into dfu mode...if that doesn't fix it...might be a worse problem...

Removing any of those components will make it impossible to upload new firmware via USB, but that's of littl consequence; new rn52 firmware is highly unlikely to be available from Microchip anytime soon.

[jelleisbleij]

I have removed the switch, R11 and D3, RN52 still goes into DFU. Monday I'll get my meter back from work and check the state of gpio3 on the RN52. Or maybe just desolder and solder back the RN52, to make sure there are not shorts anywhere.

[Karlis]

I had a similar problem long time ago (with one of first RN52 based modules I made). Turned out to be a short on RN52. I applied the flux on the pins generously and went over them with soldering iron @ 350C with a "drag" method. It has to be done quickly and with a steady hand. If everything goes well, the pins should take as much solder as they need and not more and the excess solder should stick on the iron. That way you could get clean connections.

Hope this helps.