BlueBus: A fully integrated A2DP Bluetooth solution

[t3ddftw]

bump!

Still being worked on, but not much progress has been made lately. Honestly, I am spread very thin at the moment, especially since I am now also manufacturing the unit myself. I am actively trying to work on cutting my day job hours so I can focus on expanding this into an actual business.

Yeah this happens to me on occasion. Usually resolved by manually closing and restarting the app on my iPhone. I really only use Spotify.

I've never narrowed down if it's a phone or BlueBus issue.

My V1 Bluebus likes doing that, not just in the situation you describe, but simply when you connect the phone.

I can’t spot a pattern, sometimes it connects and plays music just fine, sometimes it won’t produce any sound despite being connected.
Only way to fix it is to switch Bluetooth off and back on on the iPhone and reconnect.

Maybe it’s an iPhone issue. We have the problem with both my girlfriend’s iPhone 12 and my 13 Mini.
That Bluebus is now in my parents’ E39 and so far they’ve not complained about pairing issues. They use Android (Samsung).

My V2 so far has had none of these issues. It also appears to connect faster.

This is super weird. I have had it happen on the bench as well and resorted to replacing the Bluetooth module, which seemed to fix it. However, that could've been anything else too since it's such an inconsistent issue.

-Ted

[Der_Spanier]

I tried searching through the thread, but the search isn't the best, or maybe it's my skills. Has anyone had the issue of, after turning off the car, then getting back in, say 5 mins later (fueling up at a gas station) my iPhone 14 Pro will connect to the bluebus and show the audio metadata but not produce any sound? Thanks in advance! t3ddftw

My V1 Bluebus likes doing that, not just in the situation you describe, but simply when you connect the phone.

I can’t spot a pattern, sometimes it connects and plays music just fine, sometimes it won’t produce any sound despite being connected.
Only way to fix it is to switch Bluetooth off and back on on the iPhone and reconnect.

Maybe it’s an iPhone issue. We have the problem with both my girlfriend’s iPhone 12 and my 13 Mini.
That Bluebus is now in my parents’ E39 and so far they’ve not complained about pairing issues. They use Android (Samsung).

My V2 so far has had none of these issues. It also appears to connect faster.

[duracellttu]

I tried searching through the thread, but the search isn't the best, or maybe it's my skills. Has anyone had the issue of, after turning off the car, then getting back in, say 5 mins later (fueling up at a gas station) my iPhone 14 Pro will connect to the bluebus and show the audio metadata but not produce any sound? Thanks in advance! t3ddftw

Yeah this happens to me on occasion. Usually resolved by manually closing and restarting the app on my iPhone. I really only use Spotify.

I've never narrowed down if it's a phone or BlueBus issue.

[sev]

Just curious if there's any update on your CarPlay module - thanks! t3ddftw

bump!

[t3ddftw]

I tried searching through the thread, but the search isn't the best, or maybe it's my skills. Has anyone had the issue of, after turning off the car, then getting back in, say 5 mins later (fueling up at a gas station) my iPhone 14 Pro will connect to the bluebus and show the audio metadata but not produce any sound? Thanks in advance! t3ddftw

What color is the LED on your BlueBus? I've only ever seen something like this happen on the V1 units (with green LED).

-Ted

[nextlvel]

I tried searching through the thread, but the search isn't the best, or maybe it's my skills. Has anyone had the issue of, after turning off the car, then getting back in, say 5 mins later (fueling up at a gas station) my iPhone 14 Pro will connect to the bluebus and show the audio metadata but not produce any sound? Thanks in advance! t3ddftw

[Der_Spanier]

What PSUEng said is correct -- IHKAs made after 09/2003 do not have this bug. The problem is that the LSZ I/O status response message, to make the comfort blinkers work, is longer than they programmed the IHKA to accept which results in undefined behavior.

Thanks Ted!

Sounds like there’s no other way to fix this other than to replace the IHKA. Edit: ordered a new module with the latest part number (64116956319, SW version 19.0, build date 02/2005). That should fix the problem. The middle part of the dash will get quite the upgrade thanks to the Bluebus... first a 2007-built CD53, now a 2005 IHKA.

Today I changed the VO to reflect all the spec changes. It has fixed an issue I was having with the CD53 I got, so it wasn’t a complete waste of time, but the climate control issue is still very much present.

[fuddy]

The comfort blinkers are up there as one of my favorite features.

It saved me the trouble of sourcing another LCM

[fuddy]

What PSUEng said is correct -- IHKAs made after 09/2003 do not have this bug. The problem is that the LSZ I/O status response message, to make the comfort blinkers work, is longer than they programmed the IHKA to accept which results in undefined behavior.



Does it have the oval mirror or the mirror with the SOS button? If it has the SOS button, then the connector is probably already connected to the BMW Assist Module (TCU):




Thanks!
-Ted

Ah, yeah I have the SOS mirror. I see I can remove the TCU completely and connect the cables to the bluebus.

[///Marecki]

The comfort blinkers are up there as one of my favorite features.

[PSUEng]

If it helps anyone out since it may be that the earlier versions of the updated IHKA may not work (if I read Ted's comment correctly), here is a photo of my original unit from my 12/2002 built coupe (background) and the replacement IHKA (foreground). Note the date stamp info on the updated unit. Zero issues since upgrading. I pulled this one apart and cleaned the temp sensor and I think it actually functions better than my original unit.

[t3ddftw]

I need to do this as mine has this issue. Do you happen to know if M3's have a specific control unit compared to non-M's?

Nope; they are also fully plug and play across all MYs. Grab one from a facelift car at the junkyard and send it

-Ted

[ejendow]

Correct. Most, but not the very early, facelift IHKAs (with the buttons beside the LCD) do not have this issue..

-Ted

I need to do this as mine has this issue. Do you happen to know if M3's have a specific control unit compared to non-M's?

[t3ddftw]

Similarly, it would fix the error if I install an IHKA from 09/2003 in my 2002

Correct. Most, but not the very early, facelift IHKAs (with the buttons beside the LCD) do not have this issue..

-Ted

[Andy2424]

The I/K-Bus spec says that the maximum frame size is 32 bytes, but being that so many different OEMs were part of making modules for these cars, they didn't all understand or care about that "limitation". Of course, the guy who sat down and wrote the code for the IHKA DID read that and probably just `memcpy(frame, buffer, sizeof(buffer));`

Similarly, it would fix the error if I install an IHKA from 09/2003 in my 2002