Jump to content

t3ddftw

Members
  • Content count

    6
  • Joined

  • Last visited

  • Feedback

    N/A

About t3ddftw

  • Rank
    Newbie
  • Birthday 03/07/1991

Profile Information

  • Gender
    Male
  • Location
    Las Vegas, NV

Garage

  • Garage
    2006 BMW M3
  1. The BlueBus doesn't yet have a rich feature-set. At it's core, it's already fully integrated with the IBus and writes menus / metadata to the Navigation Screen, the CD53 Display and the MID. Beyond those standard features, the module does the following: 1. Allows you to use 3/5 blink "one touch" blinkers 2. Allows full playback control using the OE buttons I'm currently working on adding support for hardware TCU emulation, so that calls can be made/received without needing to be in "Bluetooth" mode, just like the OE system. Thanks for the support! I don't have an official roadmap right now, but I have the following features in mind right now: 1. PDC Readouts 2. Full TCU emulation, with phonebook access and all UI accoutrements 3. "Welcome Home" lights, similar to the Intravee. 4. Support for speech recognition so you can, for example, roll down the windows via voice command 5. Trip logging 6. Warning when engine is over-revved while cold 7. Max Acceleration / Max Braking, similar to the Intravee. Far into the future, I would also love to make a small add-on adapter that would interface with the CANBUS and the IBus and provide DTCs/Engine Data to the BlueBus so that it can be displayed to the user. I'll start working on the PDC stuff as soon as I finish the MID support and the Rev C. board. The modules are pretty cheap on eBay, so I'll pick one up with some sensors and get to figuring out what makes it tick Thanks! -Ted
  2. Some of them shamelessly ported from the Intravee :l. On the other hand, the whole thing is open source: https://github.com/tedsalmon/BlueBus/blob/master/firmware/application/lib/ibus.c Oh, yes, this is my project!
  3. t3ddftw

    Writing to the Nav Screen

    FYI, For anyone who stumbles upon this in the future, the correct messages are: 0x68, <len>, 0x3B, 0xA5, 0x63, 0x01, <index: 0x40 + Index number (1-5)>, <Text>, <CRC> Then Update the screen: 0x68, 0x06, 0x3B, 0xA5, 0x63, 0x00, 0x00, 0x93 As previously stated, you need an MKIV Nav with software version > 40. Note that you can write up to 38 characters per line in this mode. Thanks! -Ted
  4. t3ddftw

    Writing to the Nav Screen

    Richard, Thanks for the reply! I actually have the all the messages to write to the different fields down, as seen below. I realize that the "static" mode won't work on the unit pictured, but the unit in my car is a MKIV with the newest software revision (from 2008), so I'll test it there once I figure out what the secret sauce is. Hmm, it sounds like you're saying I may be able to write more than the 14 characters to an index field, then send another command to switch it to "static" display mode, where the extra characters will be displayed -- is that right? Another question; Am I correct in assuming that the static display mode only supports a max of 32 characters, due to the protocol only allowing 32 data bytes per packet? Thanks! -Ted
  5. t3ddftw

    Writing to the Nav Screen

    I think I may have found it -- is it this? 68 21 3B D4 03 1A <00 - 07> <Text> <CRC> It doesn't seem to do anything on my MKIII unit with software 3-1/31, but I'll try my MKIV unit later. I see that the static now playing screen is an MKIV-only feature, so this makes sense. I was still unable to get this to work on my MKIV unit :/.
  6. t3ddftw

    Writing to the Nav Screen

    Hello, Kind of unrelated, but does anyone know what I-Bus message is used to write the text to the Static"Now Playing" screen (center of the Nav screen). For example: Thanks! -Ted
×