There is a software available in HackTheIbus group download area that allows you to listen and send messages into the bus. So what you would need is the interface, that application and a spare X3 with Nav to play with ;) Once you have those, just open / close the monitor and try to listen and trace what messages are being sent in the bus. :thumbup: The easiest access to the bus is probably the cd changer cable in the center console. The tricky part is to find the extra X3.

I haven't hacked mine yet, but probably will start to explore soon. Unfortunately I don't have Nav so really cannot help in the details.

I have the X3, the nav, the Reslers I-Bus adapter, but still lack the courage and time to connect it to the car. I might be able to help in some weeks.

(Project: Mac Mini with as little changes to the car as possible)

@stepir: finally connected the kit to the car and started playing around with the BUS. Unfortunately I forgot this thread and haven't collected the codes (if any) for the screen.

Feel free to pm if you need additional info.

Update: by the way, you're supposed to be able to open and close the screen manually without destroing the motors. At least close for sure. Have you tried to pull it to open?

Have you collected any ibus logs from your x3 yet? I'm working on integrating the CID in my nav-equipped e39, but I think the CID must have a specific device address and I haven't been able to figure it out yet. Just something from start up with a few button presses would be sufficient. Thanks!

Oops, I've replied the I-BUS codes to the other thread where the guy just asked for the module to power up the screen: codes

Anyway, I've captured the relevant codes when the screen is opened and closed, but unfortunately when I re-inject them, nothing happens.

So, 46 are the buttons on the screen, much like C0 are the radio buttons and 50 are the wheel buttons. I don't see any strange "response" after these, unless it's related to the Light Control Module - that's the only kind of messages I see in between, but in my X3, 90% of the "garbage" are messages from or to the LCM, which makes it difficult to debug.

Thanks for the reply. I'll have to chew on those a bit. I have the CID set up on it's own ibus currently to try and see what messages it sends. After sending any broadcast message to wake it up, the CID sends the following messages:


46 03 80 10 D5 CID to Cluster
46 03 D0 5D C8 CID to Navigation
46 03 80 1D D8
46 03 D0 5D C8
46 03 D0 5D C8
46 03 80 1D D8
46 03 D0 5D C8
46 03 D0 5D C8
46 03 80 1D D8
46 03 80 1D D8
46 03 80 1D D8

So the 46 is a device ID beyond just the buttons. As you can see, the last three messages are aimed at the cluster and may be a ping that needs a 'keep alive' response. It's interesting that you say C0 designates the radio buttons - on the e39 with navigation, F0 designates buttons used to control the radio. If you can capture and save a full log with ibus monitor or ibus analyzer, I may be able to determine which packets are the appropriate response. Thanks.

My mistake. I meant F0.

Ah, okay, that will make it simpler.

Success!
 

It was much simpler than I thought. As it turns out, the first z4 screen I acquired was defective. I had grabbed another one off ebay for very little $$ with the intention of integrating it into my old 320i. The first one I was working with had an issue with the gearing mechanism - I could hear it spinning when the wake up message was sent, but the screen would not move on its own due to a missing/broken piece. This is an issue because the CID "knows" it's current angle or position and will not turn on the video when it's below a certain angle. There may be a way to fool the sensor, but I haven't figured it out.

After receiving the second screen today, I had it up and running in 10 minutes. I still have plenty to figure out, but it's workable as it stands right now. All that needs to be done is to send the bus wake up packet - 80 xx bf 11 01 xx and the screen will pop open and the buttons for viewing angle and open/close will start responding when pressed. Next send the following packet - 3b xx f0 4f 11 11 xx - and the video will turn on. Send the following to turn the video off - 3b xx f0 4f 01 01 xx (the screen will stay in the open position). Next up, to keep the screen responding, it needs a ping from the nav around every 18-20 seconds. The count resets everytime it's sent so every 10 seconds is probably the way to go. Here's the packet - 3b xx 46 01 xx. There may be others on the normal z4 ibus that keep the screen alive as well, but that one works fine. If it doesn't receive the keep alive packet, the screen will turn off and close until it receives the wake-up packet again. The screen internally "remembers" its last angle position and returns to it automatically when opened again.

Still a couple of things to sort out, but it's coming along.

davipt - if you still have a chance to capture some full logs from your X3 and send them, I'd appreciate it.

I currently have a carpc in my 330xi with NAV (couple of years now) and plan in installing one in the X3. On the 330xi I used a BMW modified video module. Space appears to be tighter for installation of Video module. I use CarX in the 330Xi (doesn't have all of the bells and whistles but it does the job). I have all of the pieces except for video module. Anyone install a CarPC with NAV on an X3 yet? Does Sirius talk on the IBUS?