[dave658]

Hi guys,

sorry to hijack this thread a little, but it is relevant, and with such a wealth of canbus experience on here, I thought I might try to pick your brains.

I'm not trying to drive the instrument panel, but I am trying to use the iDrive controller (CON) as an device on a project vehicle (non BMW, don't shoot me !) that I am working on.

CON is the only iDrive component I am using, so there is nothing to respond to CAN packets unless I program it that way.

When I first power on the CON, it lights up, and I see a current draw of around 28mA. I then see the following packets on the bus

ARBID DLC DATA
4E7 8 6701FEFFFFFFFFFF
5E7 8 99E1FE0006FFFFFF
4E7 8 6702FEFFFFFFFFFF
4E7 8 6701FEFFFFFFFFFF
4E7 8 6702FEFFFFFFFFFF
4E7 8 6701FEFFFFFFFFFF
4E7 8 6702FEFFFFFFFFFF
4E7 8 6701FEFFFFFFFFFF
4E7 8 6702FEFFFFFFFFFF
4E7 8 6701FEFFFFFFFFFF
5E7 8 99E1FE0106FFFFFF
4E7 8 6714FEFFFFFFFFFF

After this I get no further packets, the lights turn off and power consumption drops to around 2mA.

I am guessing that CON is expecting a reponse to what it is sending out, and after a few attempts, gives up and goes into shutdown.

Does anyone have any more information on the CON protocol or would be in a position to put a scanner on the bus and try to filter out what responses CON is expecting from amongst the other packets.

Thanks very much for any information anyone can offer