Add a link to the Firmware current release download OR the repository of all firmware releases on the Wiki Firmware Upgrade page in addition to the Firmware Update Tool.

Allow voice recognition to be toggled like so:

• Via BMBT Phone Button
• Via CD53 "CD 3" double tap

• Allow HFP to be toggled
• Allow Metadata display to be toggled
• Allow Users to Toggle auto-play on connect

Sometimes the Bluetooth device will not connect

From duracellttu:

The module isn't always able to update the whole screen and leaves bits of the old menu behind.

Potential areas for improvement:

• Reduce number of messages sent to update the display
• Empty TX queue more aggressively so other modules cannot "butt in" during the screen update

With either option, the code should be optimized to run as quickly as possible.

BlueBus is writing to the screen even when the "CD Changer" is not selected.

Some scenarios include:

• Turning off the radio should display the clock. Instead, "Paused" is written.
• When the radio is on (playing actual radio stations), the BT device is paused. If you attempt to play the music on the device, the radio display changes to show the song and then shows "Paused". The radio station is no longer displayed.
• When in CDC mode and BlueBus is playing a song, it is impossible to switch to clock mode (clock button) and impossible to modify tone settings, etc. because BlueBus continues to write to the display, overwriting these modes.

I recently received my Bluebus and connected it as per youtube videos. I have discovered a few issues.

First, there is a static noise present while the head unit is powered on and the source is set to "Bluetooth" and not playing audio as well as during playback. The noise is subtle while the engine is off and much louder with the engine running.

Today, I removed the rear panel again just to double-check all the connections. Everything looks good. I noticed the ibus/power cables were routed close to the audio/remote wire of an aftermarket amp I have installed. Thinking there may be some interference, I routed the cables away from the others. Tested again. No change.

Below are a couple of videos that show the issue while the key is in position I and II:

https://youtu.be/STgPINLZzVc

https://youtu.be/DT2ywxvu06I

Second, I opted for the TCU emulator cable. The BMW OE mic does not pick up any audio. The party on the receiving end only hears static. I really do not know how to troubleshoot here since it appears to be plug and play.

Third, I tried to upgrade the firmware on my unit and the firmware tool will not connect. I tried several times with two different USB cables with no luck.

Thank you in advance for your help!

After update with moving to TEL UI buttons, which are on MID, are not switching the tracks.
The buttons on the wheel are working well, without any issues.

It seems that BlueBus is not listening for commands issues by these buttons.

(Photo from internet)

Probably it can affect those guys who don't have media buttons on the wheel.

I have a German delivered 1999 E39 M5 with Business Audio (tape) and MID.

I've noticed that the MID display is very quickly overwritten and the BlueBus is not redrawing.

Example: If I click the 'Settings' button for BlueBus, I see 'Settings HFP: On' displayed and the menu updates with Back, Edit, <, >, etc. But this is quickly replaced by the CD changer display and menu, i.e. 'CD 1-01' and '*1, 2, 3, 4, etc.'. My understanding is that the BlueBus would see that the display had been redrawn by the RAD or IKE and immediately redraw it's own text but that is not happening.

I have attached a log file, demonstrating this.

The firmware version is 1.1.14, I noticed that there is a 1.1.16, should I upgrade?

Note that I have also had some other issues such as BlueBus responding to button presses when it should not (e.g. when changing bass/treble/etc.) and a few times the radio has 'lost' the BlueBus and I can only select radio or tape. I don't know whether these issues are related so I will create separate issues when I have been able to captures logs.

The attached log file was created with 'bt', 'sys' and 'ibus' on but I had to unplug the USB and cycle the ignition after setting those initially and I don't know whether that would have affected these settings. I assume by the volume of ibus messages that it did not.

[Com COM3] (2020-09-09_160349).log

When switching to manual mode (pressing the "m" button between the prev / next buttons), the prev / next buttons should switch to rewind / fast forward. Instead of passing these commands to the bluetooth device, the buttons are non-functional. Manual mode must be turned off in order for prev / next to work again.

My 2006 E85 Z4M can play and pause tracks using the voice button on the steering wheel but it doesn't launch Google assistant on a long press. It seems that the Z4M wheel does not send the IBusMFLButtonVoiceHold command. Here is a packet capture while holding the button:

[198472] DEBUG: IBus: RX[6]: 50 04 B0 3B 80 5F 
[198477] DEBUG: MFL OFF
[198815] DEBUG: IBus: RX[8]: A4 06 BF 70 03 00 1A 74 
[199407] DEBUG: IBus: RX[6]: 68 04 FF 02 00 91 
[199857] DEBUG: IBus: RX[6]: 50 04 B0 3B A0 7F 
[199864] DEBUG: MFL PRESS

Pressing and holding the phone button on the head unit does trigger Google assistant, just not the talk button on the steering wheel. It would be good to try out on another Z4 to confirm that it's not just a fault with my steering wheel unit and come to think of it I'm sure that the stock TCU module didn't accept voice commands on a long press either (that module was faulty and removed long ago).

Perhaps a solution is to integrate a timer? If more than 2 seconds elapses with no IBusMFLButtonVoiceHold or IBusMFLButtonVoiceRelease event then trigger BC127CommandToggleVR() and ignore the next release event.

Hello Ted,

How bad will power consumption be if we were to search for paired devices every 2 secs?

I'm thinking of a comfort entry feature where if the module detects a paired device, it send the message to unlock the door the opposite happens when paired devices are not within range.

let me know what you think.

Mike

I have built my own unit. Worked first time although I did test as I built it :) However I seem to have an issue with the BC127 module that I purchased. Possibly I have the wrong version or firmware. I bought the AptX version from Digikey with the Sierra Wireless part number "BC127-HD_1103709"

Firstly it defaults to 9600 baud, but BlueBus talks to it at 115200 looking at the TX/RX lines to the module. I modified BlueBus to talk at 9600 and I can capture the comms on a logic analyser. BlueBus seems like it might be getting a bit confused as it sends the "STATUS" command before VERSION has finished transmitting presumably as it's ~10 times slower at 9600.

VERSION returns: (hand copied from logic analyser so might not be 100% correct)

BlueCreation Copyright 2017
Melody Audio V6.1.5 HD
Build: 1496941831
Bluetooth address 20FABBxxyyzz
Profiles: A2DP AVRCP HFP SPP PBAP MAP
Codecs: SBC APTX-HD
OK

STATUS returns

STATE CONNECTED[0] CONNECTABLE[ON] DISCOVERABLE[ON] BLE[IDLE]
OK

Have I got the wrong version here? Or is it likely fixable if I can configure the module to talk at 115200 by default, which I presume shouldn't be too hard? My understanding is they are largely identical in terms of operation. However I see 6.1.1, 6.1.2, 6.1.5 and 7.1/7.2/7.3 versions all listed on the SW website.

Is it possible to add new comfort options for e38?

• fold side mirrors on car lock with lock button on the key.
• unfold side mirrors on engine start.

When Blink Option is enabled (options 3 or 5) it can glitch when user is quickly switching turn lights. Issue is not reproducing when Blink Option = 1.

Steps:

1. Turn on left blink
2. Immediately, while first blink is still on switch to the right blink.
3. Immediately, while first blink of right turn is on turn off blinking.
4. Turn on left blink

Actual result:
Left turn is blinking even when turn stick is in the middle position (at the rest).
Enabling left turn is not affecting this behavior. Only right turn can disable this blinking.

Expected behavior:
Turn signals are working as designed :D

Video 1: https://drive.google.com/file/d/11C5rW3stquAbVVfyfi1S8gaNT3GlSkAX/view?usp=sharing
Video 2: https://drive.google.com/file/d/1osLPaM-Q1jd5DugnLn4fnRuG27WQ9Qu_/view?usp=sharing

Feature request for implementation of forced bluetooth audio codec.

On bluebus.dev, there are list of different mobile devices that does not work seamlessly with BlueBus. Most of them are due to the wrong bluetooth codec, and it was a common issue for those phones.

Most of the cases, A2DP profile would use SBC codec to send over audio as it is such a commonly supported codec. The Sierra Wireless BC127 module even supports aptX which would be considered ideal for use for Samsung devices equipped with Qualcomm Snapdragon APs.
c.f. Enforcing an unsupported codec may CAUSE connectivity issues. But Sierra Wireless already built that into the firmware to have SBC codec to be used as a fallback.

Samsung devices have forced bluetooth audio codec setting under the Developer Options menu, however. Yet, the support setting of the receiver module takes priority over the sender.

Allowing users to select bluetooth audio codec would solve with connectivity, volume control, and audio quality issues.
Please consider the following codec to be supported: SBC, AAC, and aptX.

In Europe, radio broadcasters give regular traffic announcements. Our radios pick those up over RDS, and if the "TP" function is enabled, even in CD or AUX mode, the radio will pause playback and tune in to the radio station briefly and display the name of the radio station.

1. Currently the Bluebus overwrites the radio station name when in Bluetooth mode. For a truly OEM behaviour, this should not happen.
2. The Bluebus should pause the song during the announcement. I believe that this is not the case in the current 1.1.17.beta2 version.

Let me know if you need a log to identify the TP flag. Might be a bit tricky since one basically needs to wait until the radio station broadcasts a traffic report.

E39 with DSP and MID display. Upon hitting the power button, the lower band of the display does not clear correctly. Upper band may also continue to print "Bluetooth" if accessing bluebus through the AUDIO button (not so when thru TEL button).

The heated seat switches (part of the "SZW" Switching Center Module) on 9/98 and later E38/E39's are connected to the I/K loop. I would think, therefore, that I-bus commands could be used to turn on/off the heated seats.

Could the BlueBus recall any heated seat settings as the car is turned off, then recall them when turned back on?

Enhancement request - are there any plans to support the CD43 head unit with bluebus? This would provide an obvious upgrade path to bluebus for E32/34/36 fans I would think. I believe this the only single-DIN style head unit out there with ibus support (the C33 and C43 cassette head units are "m-bus" I believe).

Right now, the UI code and the handler are fighting to connect to a specific device. The code to handle this functionality should be moved to the handler and events should be used to trigger its connection/disconnection process.

This first line looks like a "when MFL phone is pressed THEN answer phone"

and

appears to be only an IKE print for the telephone caller maybe? it prints to IKE TEL data.... anyway I am curious if you feel like clarifying how you triggered the phone box to "on" to provide power to the microphone. Also curious how you hijacked the signal coming from the phone box.

Essentially my tentative plan is to feed my e38s microphone into the Node.js project I am using so that I can answer phone calls etc

Hello Ted,

Auto play back seems to be buggy and works 5/10 with the latest update.

When you ignition is switched, it will resume as normal for about a few seconds and then pauses.
the user has to manually resume playback.

I was able to capture a log.

AUTORESUME NOT WORKING.txt

Regards,
Mike

1. Add door locking functionality to the current unlocking functionality.

2. Display inbound caller ID.

3. Find a place to display coolant temp?

Originally posted by tabora

• I've noticed that the R/T button, if inadvertently pressed in BlueBus mode, disables the track U/D buttons. Is it possible to either completely disable the button or better yet make it do something useful like function as a Mode button? I understand that it functions on the same wire as the pause/voice command button, just at a different resistance.

Hitting the R/T button should actually kill those controls regardless of audio mode. See, since the BlueBus is emulating the factory telephone module, the MFL is acting like it would with the OE TCU in place and is directing commands to the TEL module rather than the RAD. I cannot send a mode button press to a Business CD radio, but what I can and should do is emulate the OE functionality and start scrolling your contacts on the radio so you can select someone to call.

Thanks!
-Ted

Hi

I'm in the process of building one from your design. I have the parts and PCBs on the way, but decided to make sure I could also compile the firmware since there's a fair chance I can contribute there.

I'm running MPLAB X IDE v 5.20 and XC16 v1.60 (free version) on Windows. Of significance it appears the project originally/still uses XC v1.35 for the bootloader and XC v1.36 for the application. Not sure if that might cause an issue.

Bootloader appears to compile just fine but the application gives errors about some UART interrupt sections/symbols and a couple of others. I'm not experienced with PICs or XC16 in particular so thought it might be easier to just ask since it mostly works.

This is fairly clean installation of MPLAB IDE X and XC16. It did give an intial warning about the toolchain not being specified in the project but seemed to figure it out and the bootloader compiled just fine:

warning: Configuration "bootloader" builds with "XC16", but indicates no toolchain directory.
info: Configuration "bootloader" will build with toolchain "XC16" at "C:\Program Files\Microchip\xc16\v1.60\bin".
warning: Configuration "application" builds with "XC16", but indicates no toolchain directory.
info: Configuration "application" will build with toolchain "XC16" at "C:\Program Files\Microchip\xc16\v1.60\bin".

application build output

CLEAN SUCCESSFUL (total time: 30ms)
make -f nbproject/Makefile-application.mk SUBPROJECTS= .build-conf
make[1]: Entering directory 'C:/Users/ShonkyCH/Projects/BlueBus/repo/firmware/application'
make  -f nbproject/Makefile-application.mk dist/application/production/application.production.hex
make[2]: Entering directory 'C:/Users/ShonkyCH/Projects/BlueBus/repo/firmware/application'
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   lib/bc127.c  -o build/application/production/lib/bc127.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/lib/bc127.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   lib/eeprom.c  -o build/application/production/lib/eeprom.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/lib/eeprom.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   lib/i2c.c  -o build/application/production/lib/i2c.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/lib/i2c.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   lib/char_queue.c  -o build/application/production/lib/char_queue.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/lib/char_queue.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   lib/event.c  -o build/application/production/lib/event.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/lib/event.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   lib/config.c  -o build/application/production/lib/config.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/lib/config.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   lib/ibus.c  -o build/application/production/lib/ibus.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/lib/ibus.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   lib/log.c  -o build/application/production/lib/log.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/lib/log.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   lib/utils.c  -o build/application/production/lib/utils.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/lib/utils.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   lib/pcm51xx.c  -o build/application/production/lib/pcm51xx.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/lib/pcm51xx.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   lib/uart.c  -o build/application/production/lib/uart.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/lib/uart.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   lib/sfr_setters.s  -o build/application/production/lib/sfr_setters.o  -c -mcpu=24FJ1024GA606  -omf=elf -DXPRJ_application=application  -legacy-libc  -Wa,-MD,"build/application/production/lib/sfr_setters.o.d",--defsym=__MPLAB_BUILD=1,-g,--no-relax
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   lib/timer.c  -o build/application/production/lib/timer.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/lib/timer.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   lib/wm88xx.c  -o build/application/production/lib/wm88xx.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/lib/wm88xx.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   ui/cli.c  -o build/application/production/ui/cli.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/ui/cli.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   ui/bmbt.c  -o build/application/production/ui/bmbt.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/ui/bmbt.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   upgrade.c  -o build/application/production/upgrade.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/upgrade.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   ui/mid.c  -o build/application/production/ui/mid.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/ui/mid.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   ui/cd53.c  -o build/application/production/ui/cd53.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/ui/cd53.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   main.c  -o build/application/production/main.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/main.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   handler.c  -o build/application/production/handler.o  -c -mcpu=24FJ1024GA606  -MMD -MF "build/application/production/handler.o.d"      -mno-eds-warn  -g -omf=elf -DXPRJ_application=application  -legacy-libc    -O1 -msmart-io=1 -Wall -msfr-warn=off  
"C:\Program Files\Microchip\xc16\v1.60\bin\xc16-gcc.exe"   -o dist/application/production/application.production.elf  build/application/production/lib/bc127.o build/application/production/lib/char_queue.o build/application/production/lib/config.o build/application/production/lib/eeprom.o build/application/production/lib/event.o build/application/production/lib/i2c.o build/application/production/lib/ibus.o build/application/production/lib/log.o build/application/production/lib/pcm51xx.o build/application/production/lib/sfr_setters.o build/application/production/lib/timer.o build/application/production/lib/uart.o build/application/production/lib/utils.o build/application/production/lib/wm88xx.o build/application/production/ui/bmbt.o build/application/production/ui/cli.o build/application/production/ui/cd53.o build/application/production/ui/mid.o build/application/production/main.o build/application/production/handler.o build/application/production/upgrade.o      -mcpu=24FJ1024GA606        -omf=elf -DXPRJ_application=application  -legacy-libc    -Wl,--local-stack,,--defsym=__MPLAB_BUILD=1,,--script="application.gld",--stack=16,--check-sections,--data-init,--pack-data,--handles,--isr,--no-gc-sections,--fill-upper=0,--stackguard=16,--no-force-link,--smart-io,-Map="dist/application/production/application.production.map",--report-mem,--cref,--warn-section-align,--memorysummary,dist/application/production/memoryfile.xml 
nbproject/Makefile-application.mk:415: recipe for target 'dist/application/production/application.production.hex' failed
 Link Error: Could not allocate section '.aivt._AltU1TXInterrupt' at 0x182c
 Link Error: Could not allocate section '.aivt._AltU2TXInterrupt' at 0x1852
make[2]: Leaving directory 'C:/Users/ShonkyCH/Projects/BlueBus/repo/firmware/application'
 Link Error: Could not allocate section '.aivt._AltU3TXInterrupt' at 0x18ba
nbproject/Makefile-application.mk:90: recipe for target '.build-conf' failed
 Link Error: Could not allocate section '.aivt._AltU4TXInterrupt' at 0x18c6
make[1]: Leaving directory 'C:/Users/ShonkyCH/Projects/BlueBus/repo/firmware/application'
 Link Error: Could not allocate section '.aivt._AltAddressError' at 0x1806
 Link Error: Could not allocate section '.aivt._AltStackError' at 0x180a
nbproject/Makefile-impl.mk:39: recipe for target '.build-impl' failed
 Link Error: Could not allocate section '.aivt._AltMathError' at 0x180c
 Link Error: Could not allocate section '.aivt._AltNVMError' at 0x1808
 Link Error: Could not allocate program memory

Info: Loading file: ./application.gld
make[2]: *** [dist/application/production/application.production.hex] Error 255
make[1]: *** [.build-conf] Error 2
make: *** [.build-impl] Error 2

BUILD FAILED (exit value 2, total time: 5s)

Any idea?

Thanks

After installing, the bluebus displayed as "CDC 7-01" on the board monitor (no nav), none of the buttons were operable and therefore I could not get it to pair with the phone.

Tried connecting the bluebus to both PC and Mac and could not get the device to connect (green LED on)

Any help appreciated :)

Whenever comfort blinkers are on (and only when those are specifically blinking) the dash brightness control and the headlight level adjustment control are no longer controllable for a period of time after the last blink.

However if the blink is only once or its set to the second detent (so fixed on) then it functions as normal.

Running 1.1.16 on an E46 Pre-LCI with the Blaupunkt Head Unit (Car has no auto-headlights and no Xenons)

Hi, I have a few things I would like to do that should be controlled via a menu and as such I was wondering if it would be possible to get rs232 out of the board or some form of GPIO so that everything could be in one module. Another hope of mine would be to be able to have features like mod light except actually in the menu and visible for navigation users. I would be happy to work on coding such features in, I just want it all to be clean and on a single module.

Another project, which is the reason I REALLY want this is I am trying to add dynamic backup lines to my e39, and need a way to constantly poll the steering wheel angle and due to the bus not having much bandwidth, it would be useful to be able to control everything from a single module.

• Add Diagnostic recognition for MKII units
• Allow Non-SW40+ Units to display data under the Dashboard

Hello Ted, I have noted several issues with my BlueBus in my Z4M...; let me list them below.

1. The settings menu is not persistent, the bluebus continues to return to the main page, to adjust settings you need to do it very quickly before it kicks you out. This means the settings need to be adjusted quickly and blindly

2. When autoplay is off, the bluebus constantly pauses music, if enabled, you cannot pause it. Also, you can perceive audio coming up and down as the system pauses and then auto-plays again.

3. When connected to the phone and streaming musing, if I try to use the AUX mode to reproduce music, it is as if the phone stays in Bluetooth mode and paused, so no sound comes out.

4. When in Bluetooth, the clock button does not display the time, even when metadata is off

5. When the car is turned off (key in 0 position) the musing stops, but the radio display remains on, I have not timed for how long until it goes to sleep.

I captured some videos, but they are too large...

After getting the BlueBus wired into my E39 (2003 540i) noticed a couple of small improvements that can be made for Non-Nav E39 support:

• The BlueBus outputs into the spot on the MID where the clock and OBC data gets output and seems like it's competing with those functions for display space.
  
  On occasion the display flashes and then goes back to showing the clock and then flashes again and shows all the BlueBus text
• Is there a way to pass caller ID or address book through the HFP? I upgraded from a dead Bluetooth TCU which had support for both.
• Completely left field, but would be cool if the BlusBus could utilize the SOS/Wrench buttons as quick dials

As per the title, could it be possible to also unlock the rear hatch in the BMW z4 coupe along with the side doors when powering the car off?

Starting from up 14.2 on iOS iphone users can't disable headphone safety feature.
Whats impacted: when volume on Bluetooth device is set to max - iOS will reduce it to 50% from time to time to prevent ear damage. Users can't control it anyhow.

Suggestion: Is it possible for Bluebus to handle listen change event and set it back to max when the setting is enabled.

I'm always setting phone volume to max and controlling actual volume by car media controls.

Would be awesome if it's possible to get a volume change event without need to constantly raise the volume to max

As discussed on NA M3 Forum, hack something into the BlueBus's firmware so that every time the car turns on, the BlueBus optionally gets the time off of the phone it connects to and sets the car's time.

Any metadata with Cyrillic symbols is displayed as Unknown Artist/Title/Album.
It would be great to have proper support for this.

Here are some notes I put together for the CD53 UI. Maybe it will help with the documentation?

CD53

Button 1: Play / Pause
Button 2: Unknown
Button 3: Unknown
Button 4: Unknown
Button 5: Shows BT device name (* = connected)
Button 6: Pairing on / off
Left action button (RND): Random mode
Right action button : Unknown
Left triangle: Previous track
M Button: Manual mode
Right triangle: Next track

Notes:

• BlueBus will automatically pause the music source when the radio is turned off
• When turning on pairing mode, any existing Bluetooth connection is terminated
• Manual mode does not work. While in manual mode, prev / next track buttons do nothing
• RND currently turns on but can't be turned off. When on, prev / next track buttons do nothing

• Allow HFP to be toggled
• Allow Metadata display type to be toggled
• Allow Users to Toggle auto-play on connect

FW: 1.1.16

-Shows on positions 4,5,6: no disc status

-When using siri you hear audio switching (plops,tiks) only when using coax digital option

I updated the firmware in my BlueBus to 1.1.13 yesterday, and today I noticed that the orange display at the bottom of the instrument panel (between speedometer and tach) was on when the car was parked in the garage. The odometer and trip odometer come on for 1:16 (one minute, 16 sec) then go out for 12 sec, then the cycle repeats - endlessly. I’m thinking it will certainly effect the battery over time.
Anyone else seeing this?
Could this have something to do with the BlueBus pulling coolant temp from the IBUS, even when the car is off?

If random mode is entered (RND button), the prev / next buttons no longer work. It is also not possible to exit random mode by pressing the button again. A workaround is to turn the radio off and back on or otherwise exit and reenter CDC mode.

From duracellttu:

The BT device does not resume playback after a call has been received.

Hi Ted,

i've realized that Bluebus overrides the signal of my TV Modul. I'd like to use the TV Modul to connect it to an CarPlay adapter and use the Bluebus Bluetooth connection for Voice Controls and Audio. This would be the perfect 2021 tech update while maintaining the 100% OEM look.

In reverse it works fine and my camera overrides the screen as designed.

The setup in my 2001 E38: BM54 / Bluebus / 16:9 / MK4 / TV-Modul / Reverse Camera

Any thoughts on this?

Best regards,
Tim

Use the Talk button on the MFL to trigger voice recognition.

For BMBT users, also map the phone button to this functionality.

For CD53 users, map the number "3" to this option.

cc @dutchhome

Would HFP working properly if I will connect an external microphone to the bluebus without connecting anything to the bluebus telephone connector?
Working properly - sound goes via car stereo and voice captured by the external microphone

Hi Ted,
A couple of bugs:
I have updated to 1.1.16 and noticed that now 1: I cannot select television mode. -it jumps straight back to cdc/ Bluetooth screen.
2: the caller ID has stopped displaying correctly. - it shows “00z” or similar random characters.
3: I’ve never been able to get the coolant temp to display with any firmware version so far.
4: also the phone call volume still seems to jump very high a significant amount when a call comes in. This has improved after the 1.1.16 update but still requires turning the volume down to a bearable level during the call, to then turn it up again when the music returns after the call has ended.

my setup:
2004 E46 with Mk4 Nav, BM54 radio, Television module with DVB card mod, Hi-Fi amp.

Thanks

Users are intermittently reporting low outgoing volume. Likely a steady problem, but some users do not complain so microphone is partially working.

Microphone is 84318380338
Head unit is 65. 12-6 961 215

Late head unit is retrofitted into an early (3/01) wagon.

Not sure if this is related to my homebuilt unit

Melody 7.3 HD firmware.
Latest github application firmware.
E46 i.e. analog audio
Galaxy S8+ (I know this is noted as a potential issue but works fine otherwise so far for me - no dropouts or pauses apart from this)

When skipping, the sound briefly drops out on the previous song.
Then it plays a bit more (maybe 0.5s) of the previous song and then switches to the next song.

I don't think this is normal as it's quite disconcerting/annoying. If the little drop out was slightly later as the tracks changed, I think that would be better. Is that what the dropout is for but somehow the timing is off?