BMW F31 320d K-CAN 2013: Upgrade & Tuning

Hello,

I have a BMW F31 from the year 2013 with a navigation system. On the iDrive, I can access CAN-high, CAN-low, 12V, and GND. I downloaded the can tool software and purchased an interface.

'I've tested it on a Golf 5 and an E60 530d, and it worked without any problems. Unfortunately, I'm not getting any data from the F31. Does anyone have any ideas about what might be causing this? The connection seems to be correct; I've checked it multiple times.'

Thank you for your help.

Regards,
- Kuna -

Whatever the reason, the link to the CAN interface has been deleted, never mind.

I found the error. The pinout information I found online was incorrect. There is a 4-pin blue connector on the i-Drive controller with the following pin configuration:
Pin 1, red/yellow wire = 12V.
Pin 2, brown/black wire = GND (Ground).
Pin 3, color orange/green = CAN-high.
Pin 4, green wire = CAN low.

I connected the aforementioned interface to the can tool. The shop also sells adapter cables for connecting, so I didn't have to cut anything. Then I set the can tool to 100 kbit/s, and I could see the message in the trace. Now I'm going to start analyzing the messages. Has anyone already obtained some IDs from an F31?

Quote:

The link to the CAN interface has been deleted, regardless.

Because posting links to shops is not relevant to your problem?

Either the connection is incorrect or the bitrate is set incorrectly.

Best regards,

If the IDs are the same as those used in the E90, try using '1B8'. That's the ID for the iDrive system.

Unfortunately, those are not the same IDs.

Unfortunately, those are not the same IDs.

Then take a look at these IDs (maybe they will work).
0x264: I-Drive rotations.
0x267: iDrive buttons.

Regards,
Andi.

'Thanks, those are the correct IDs, great. Do you have any more?'

Yes.

Are you looking for something specific?

Right now, I'm spontaneously thinking of the value 0x12F, which I use for class 15.
Otherwise, I have the usual IDs that you typically need.
- PDC
- Rearview camera module.
- Transmission
- Light
- Speed
etc.

But feel free to try identifying the IDs yourself. And if you're looking for a specific one and can't find it, you can ask about it here.

Regards,
Andi.

Hi,
Could someone please provide me with the data for ID 12F?
ID 12F
DLC?
Data?

Sure, I'd be happy to help. Please provide the text you would like me to translate from German to English.

'Thank you.'

Hi,
Could someone please provide me with the data for ID 12F?
ID 12F
DLC?
Data?
thank you

12F 8 FB 22 88 1D F1 05 30 86 // D3 = Class 15: 1D = off, 1C = on

Unfortunately, that's all I have, as I only need Kl15.

Regards,
Andi.

Thank you, Andy.
However, it unfortunately didn't work out the way I had hoped.
I'm working on a residual bus simulation for a gear selector switch.
I know which IDs are needed, but unfortunately, I don't have a suitable vehicle.
available for reading. Could you please send me the following messages?

Message | ID | DLC | DATA | Recipient | Sender
LCD Brightness Control: 0x393 GWS KOMBI
Dimming: 0x202 GWS FRM
Data Display: Gear Strand = 0x3FD, GWS, EGS.
Data: Powertrain 2 0x3F9 GWS DME/DDE
Clamps 0x12F GWS CAS
Vehicle Status: 0x3A0; GWS: JBE.
Relative time: 0x328. GWS: KOMBI.


More messages would also be helpful to obtain the checksums, or for implementing 'alive' counters.

Regards,
dennis

Can you also just connect the iDrive controller so that you only get the two codes?

I'm also interested in whether the iDrive controller can function outside of the car, or if it requires additional commands to initialize.

Are the IDs for the iDrive touch controller the same?
Are there any additional IDs for touch input?

I would also like to know if the iDrive controller can function outside of the car, or if it requires additional commands to initialize.

The controller only activates if the correct messages are sent on the bus; the same applies to the CID. If the correct message is not received within 4 seconds, for example, the CID will reset.

I would also like to know if the iDrive controller can function outside of the car, or if it requires additional commands to initialize.

The controller only activates if the correct messages are sent on the bus; the same applies to the CID. If the correct message is not received for 4 seconds, for example, the CID will rotate.

'ViRuS2k, I sent you a complete trace via private message. You can try to see if that helps the i-Drive stay on for a bit longer.'

I'm just curious to see how long this particular email will stay in my outbox this time.

Regards,
Andi.

Hello.

I have a (ZBE_LOW) device here and I've tried out some signals with it.

The only things I've found so far are 0x202, 2, 0xEF, and 0xFF.
This controls the lighting of the controller.

If no signal is received for a certain period of time, the lighting will turn off again.
Unfortunately, it doesn't respond to any key presses.
But at least this shows that the controller is responding.

I also disassembled the controller and saw that the CAN receiver sends a "wake-up" signal to the 5V voltage regulator.
Therefore, something must be done to the bus; otherwise, the voltage regulator will switch off again.

Has anyone managed to wake up the iDrive controller and get it to talk yet?