HU & Steering Wheel buttons issue

[sloth]

Hi Guys,

I've installed my module (made by Karlis) last week and the audio is awesome, it works great.
In the beginning the buttons on the steering wheel and on the headunit (AS2) did work for a short time, and after that it didn't work for a few days. I removed the bluesaab from my bluetooth devices on my iPhone (iOS 9.3.1) and re-added it. Then it worked great for 2 days.

This morning my iPhone didn't connect by itself and when I manually connected to it the buttons didn't work anymore. The same solution of removing and adding it doesn't work now, I can still play music over the HU, it's just the buttons that don't work.

When I try to use the long-press-until-second-beep button to disconnect the connection the music keeps playing so it doesn't do anything.

Has anyone had the same issue?

And,.. What could cause the bluesaab not to connect to my iPhone, could someone else have connected to the module while it was parked overnight or does the module completely shut down when you turn the engine off?

[sloth]

After some more testing it looks like somehow the connection isn't perfect when starting the car. Whenever I switch to CD-player and then back to the CD-changer the buttons work fine again.

[Seth]

Karlis has told me that he's seen that issue as well, but I don't have that issue in my 9-3, so it must be a 9-5 related issue...he's looking into it now; look for a post from him later :)

[homerisback]

Hi,
I noticed the same behaviour in my car (9-3 2002) and sometimes I need to switch between sources to recover the buttons functionalities (steering wheel & IHU), which are sooooo great !

I tried to force disconnection by changing source just before removing car's key but it doesn't solve the issue when back into car for a new trip with awesome music from CDC

[Karlis]

So, guys, in order for me to figure out what's wrong, could you please let me know which software version are you currently running? Currently we have like three versions out there and it's hard for me to figure out who is using which. :)

[homerisback]

I'm using PCB 3.2 and CDC v2.1 may 2016, but without PWREN new features that made RN52 not starting.

[Edit] : hey, didn't see you posted a v3.0  Will try it before blaming you again for non-working features

[Karlis]

Ok, thanks! So I've posted a new software v3.0 under "Software" section which includes a brand new codebase for handling comms with RN52. Me and Seth have been testing this code for a while now and it has become our #1 choice for everyday use as it solves a lot of painful issues we were seeing before.

Long story short, I would encourage you to upgrade the software to the latest version.

[homerisback]

As I edited my previous post, I've just seen the new version ! Thanks and update is on its way...

[sloth]

I have the version you put on the module before shipping, I believe it's the march release.
hopefully I'll receive the cable tomorrow so I can do the update soon :)

Thanks!

[sloth]

I upgraded the software to 3.0 yesterday and the bluetooth connection seems to be a lot better, but after starting the car I do have to switch to another source and back to the CDC again to get the buttons working.

[Karlis]

I have the same issue. It seems it only affects 9-5s. 9-3s seem to be fine without manifesting this issue. I suspect it has something to do with the node status (6A1/6A2) message exchange or timing. I'm looking into this, but it might take some time....

[sloth]

Awesome and no worries if it takes time, switching the sources works fine.
I just press the CD button twice when I get in the car :)

[Karlis]

Ok, I think I've fixed the issue. Now we do yet another check before invoking Bluetooth connection. If two bytes of the CAN frame match the values we are looking for, only then everything will be activated (which is always true as both match).

Newest commit on Github has the fix. If anyone wants to give the code a try, you are welcome. Let me know how it goes...

[sloth]

Sorry for the late reply, in the middle of moving and "lost" my cable to upgrade the module :)
Quick question, for the last build I had to make some modifications to get it working with the old board, did you already add those modifications in this build?

Thanks!

[Karlis]

I don't think I have committed them yet. The quickest fix for boards < v3.3 is to comment out two lines in 'initialize()' function in RN52impl.cpp file.

This is how it should look like in order to work:

void RN52impl::initialize() {
    softSerial.begin(9600);
    pinMode(BT_EVENT_INDICATOR_PIN,INPUT);
    pinMode(BT_CMD_PIN, OUTPUT);
    pinMode(BT_FACT_RST_PIN,INPUT);
    //pinMode(BT_PWREN_PIN,OUTPUT);
    digitalWrite(BT_EVENT_INDICATOR_PIN,HIGH);
    digitalWrite(BT_CMD_PIN,HIGH);
    //digitalWrite(BT_PWREN_PIN,HIGH);          
}

[sloth]

Did a quick check and the first time after the update I had to reconnect to the module and then it first gave the same issue, after shutting the car down and doing another attempt it did work as I would expect. I'll do some more tests after dinner tonight.

[sloth]

Cheered too early,..
It still works as before you deployed the fix, I guess it worked yesterday because I had to reconnect the phone to the module.

[Karlis]

Ok then, I'll need to dig deep again. While doing some tests this weekend, me and Seth noticed that there's more than one status message that CD changer usually sends to IHU that we haven't implemented in our code yet (and as a matter I don't think anyone else in this field has).

Currently we send a message saying "I'm here, playing 1st disc from the magazine and I'm married to the car". We do it forever with 1000ms interval. Now, there's another one which has to be sent to IHU whenever IHU is not in CDC mode. So if IHU is not in CDC mode, but it keeps receiving messages from CD changer that the latter one is playing something, it might get confusing.

 I'm working on a code change for that and hopefully this will improve things.

[sloth]

Let me know if there is anything I can do. In the meanwhile I'm going to roll back to the old release. The latest release also forces me to connect my iPhone to the module manually almost every time I get into the car.

[Karlis]

It takes up to 5-7 seconds for the 'auto-connect' to take place. Did you set SK and SD settings on RN52 to "06"? On May 20, 2016; 3:59am you wrote that you had trouble configuring RN52. Did you resolve that?