BlueBus: A fully integrated A2DP Bluetooth solution

[Cristov9000]

I just installed Bluebus in my '06 M3 Comp and its amazing (after having it for like a year and not installing it). Sound quality is great! Now I am eagerly awaiting the release of the CarPlay unit!!!! Reading this thread and watching the youtube videos of the install I was slightly confused about how to install it and what I could and couldn't leave unplugged so I thought I'd add some pics that will hopefully clear things up for people.

First picture is of what I think is a relatively unmolested area behind the trunk carpeting right as I pealed it back. The silver box on top is the telematics module for BMW assist that no longer works for an e46 and its my understanding that its just dead weight at this point. I removed it and have not noticed any issues with it being gone. The telematics module (at least on my car) had 3 connectors: the 54-pin connector on the backside (red arrow) that we are reusing for Bluebus, the black antenna hookup in the foreground, and the white/purple antenna hook up. We aren't using either antenna hook-up going forward. Of note, the telematics module weighs about 2 lbs so you get that weight savings. Also the black antenna is what connects to the sharkfin antenna on the roof, so if you are so inclined you can now remove the sharkfin antenna and the now unused cable to it for additional weight savings (it just adheres to the roof). Also note the bundle of unused connectors (other red arrow) tucked in the back. That bundle included only the 2 CD changer wires that we need for Bluebus and at least in my case was just wrapped in some foam take and stuffed in that back cavity in the quarterpanel behind the amp.

Second picture just shows the lay of the land with the telematics module removed and shows the 3 connectors we need relative to one another. It also shows that black unused antenna wire going to to the top of the rear quarter panel where it exits to then route behind the rear window trim to the sharkfin.

Last picture shows the Bluebus installed with factory hardware in place of the telematics module. Its a perfect fit. A little cable management and some felt take around the 54pin connector adapter to prevent rattles and its good to go. I hope that makes install a little clearer for some people. I counldn't be happier... well until the CarPlay module is released!

[t3ddftw]

Messed around with it yesterday and saw the same. MacOS tool still works fine. I forget my bootloader version, but I have a very early unit, if that makes a difference.

I just fixed this. It was due to a *sarcastic gasp*, wait for it, off by one bug in early bootloader versions which included an uninitialized byte as part of the XOR checksum. I added a catch for it and now it works:

[11:16:02 PM] Serial port connected
[11:16:02 PM] State: REQUESTING_BOOTLOADER
[11:16:02 PM] Attempting to enter bootloader mode...
[11:16:03 PM] Received a corrupted response from the device
[11:16:04 PM] State: AWAITING_PLATFORM
[11:16:04 PM] Platform: BLUEBUS_BOOTLOADER_1_4
[11:16:04 PM] Legacy bootloader detected, skipping CRC validation
[11:16:04 PM] State: REQUESTING_INFO
[11:16:04 PM] Firmware version: 1.4.5
[11:16:04 PM] Serial number: 65535
[11:16:04 PM] Built: 255/255
[11:16:04 PM] State: READY
[11:16:08 PM] Selected release: v1.4.32
[11:16:22 PM] Firmware downloaded
[11:16:22 PM] State: ERASING
[11:16:22 PM] Erasing flash (733 rows to write)...
[11:16:28 PM] Flash erased successfully
[11:16:28 PM] State: WRITING
[11:16:51 PM] State: STARTING_APP
[11:16:51 PM] Write complete, starting application...​

[heinzboehmer]

I’ve had some folks with bootloader 1.3 and 1.4 report this. I’ll be looking at it early next week

-Ted

Messed around with it yesterday and saw the same. MacOS tool still works fine. I forget my bootloader version, but I have a very early unit, if that makes a difference.

[t3ddftw]

i just can't update with the online tool

[14:36:27] Loaded 7 releases
[14:36:31] Could not connect to the device. Make sure it is plugged in and try again.
[14:36:57] Serial port connected
[14:36:57] State: REQUESTING_BOOTLOADER
[14:36:57] Attempting to enter bootloader mode...
[14:36:58] Received a corrupted response from the device
[14:36:58] Received a corrupted response from the device
[14:37:00] State: AWAITING_PLATFORM
[14:37:00] Platform: BLUEBUS_BOOTLOADER_1_3
[14:37:00] State: REQUESTING_INFO
[14:37:00] Firmware version: 1.3.4
[14:37:00] Received a corrupted response from the device​

I’ve had some folks with bootloader 1.3 and 1.4 report this. I’ll be looking at it early next week

-Ted

[Zekarus]

i just can't update with the online tool

[14:36:27] Loaded 7 releases
[14:36:31] Could not connect to the device. Make sure it is plugged in and try again.
[14:36:57] Serial port connected
[14:36:57] State: REQUESTING_BOOTLOADER
[14:36:57] Attempting to enter bootloader mode...
[14:36:58] Received a corrupted response from the device
[14:36:58] Received a corrupted response from the device
[14:37:00] State: AWAITING_PLATFORM
[14:37:00] Platform: BLUEBUS_BOOTLOADER_1_3
[14:37:00] State: REQUESTING_INFO
[14:37:00] Firmware version: 1.3.4
[14:37:00] Received a corrupted response from the device​

[Flow]

FYI, I rolled out the online releases portion of the new firmware tool, so you can keep up with and easily load the newest version right from the website.

https://www.bluebus.dev/firmware

I used your online tool to update mine, and it was a breeze, thank you very much for that new solution !

[heinzboehmer]

FYI, I rolled out the online releases portion of the new firmware tool, so you can keep up with and easily load the newest version right from the website.

https://www.bluebus.dev/firmware

Woah, cool!

Can't wait to be flashing my BlueBus on the side of the road with my phone cause I wrote some dumb bug into the FW

[t3ddftw]

FYI, I rolled out the online releases portion of the new firmware tool, so you can keep up with and easily load the newest version right from the website.

https://www.bluebus.dev/firmware

[Flow]

Just updated the firmware to bluebus_1_4_32.hex
Tried a couple of times to use the blinker, and it all worked well. It didn't blink continuously like it did before, but blinked 3 times and then shut off.
All good, thank you for the support t3ddftw !

[Flow]

Thanks for the information and update !
I'll try it sometime soon

[t3ddftw]

Oh Sorry Ted t3ddftw

No worries; thanks for trying to grab my attention

[0-60motorsports]

Oh Sorry Ted t3ddftw

[t3ddftw]

I did not buy the adapter, hhmmm might want to message tedbm3 directly.

Thanks for the @ but wrong username !

Hi everyone,
I’m running BlueBus in an E46 330Ci Cabrio (EU car, no factory telephone pre-wire).
I’d like to use the full telephone path (hard MUTE/TEL-ON + Tel Audio ±) in addition to the normal CDC T-harness, so that calls interrupt regardless of the current source—i.e., like the OEM ULF behavior.
Is there a custom plug-and-play adapter loom that:

• plugs into the BlueBus 6-pin telephone header, and
• breaks out the four radio lines to the back of the head unit, plus
• provides two wires for the OEM microphone from the steering-column grille?

Kind regards

Yes, I make these to order for $25 USD.

I'm on the latest firmware and I'm noticing that my clock keeps changing to AM, even if i go in and change it to PM, if i stop and start the car, the nav shows AM time? Anyone else seeing this?

What firmware version are you on? 1.4.32 is the latest beta, and I think 1.4.0+ fixes this issue.

set to 24H

Before ordering, I was hoping someone can confirm current Bluebus does not prompt for a pin when attempting to pair.

I’m looking to use a CarPlay screen that won’t recognize a pin request at pairing.

Thanks in advance.

I don't think so

No prompt for pin on mine.

Correct, no pin is required.

Quick question for you guys out there running this solution.
I activated the triple blink option but sometimes it seems to fail and the blinker keeps going forever.
I can activate the opposite side blinker but when I cancel it, the initial side starts blinking again

Anyone experienced this ? Is there a solution ?

I had something similar happen exactly once after I changed to the triple blink, wasn't sure if it was related or not. I bumped the stalk the opposite way when trying to cancel the blinker. It kept blinking until I fully turned the blinker on and then off.

Funny I recently also started having this issue. And randomly sometimes doesn't connect.

Thanks for your feedback !
I guess I am not the only one who experienced that.

terra agreed, but I am not sure my LCM is triple-blink capable. I must say I haven't looked into it. It's a bit too involved from what I gathered quickly. I'll maybe save that for later.

This was fixed recently in 1.4.20+
Here is the latest beta:

https://t3ddftw.s3.us-east-2.amazonaws.com/BlueBus/firmware/bluebus_1_4_32.hex

There's also a new firmware tool that runs straight in your browser: https://www.bluebus.dev/firmware

Here for an update on the CarPlay module t3ddftw

It was going well until Texas Instruments discontinued the DIT4096, so I am being forced to iterate the prototype hardware. I shifted to BlueBus firmware improvements for now as I'd like to get a bunch of features and bugfixes out so I can focus on the AA/CarPlay solution.

Also, today was the first time I saw an update on this thread, so if I don't respond, please shoot me an email at [email protected]

-Ted

[terra]

Thanks for your feedback !
I guess I am not the only one who experienced that.

terra agreed, but I am not sure my LCM is triple-blink capable. I must say I haven't looked into it. It's a bit too involved from what I gathered quickly. I'll maybe save that for later.

If it's the car in your sig, it should be capable with a flash https://nam3forum.com/forums/forum/s...blink-and-more

If it's an older car, would have to grab one of the newer LCMs and then do the above.

I'd argue it's less involved than most of the mechanical stuff that we don't blink an eye at

[repoman89]

Here for an update on the CarPlay module t3ddftw