Pulling a log from my E38's ULF?

[Exwoodchuck]

I'm working with Motorola in an attempt to find out why a # of Android phones don't play nice with BMW ULF's. I've got NavCoder, INPA and DIS up and running fine.

Question--
- which sw tool should I use to pull a log of IBUS traffic from my ULF?
- I don't see my ULF listed in NavCoder-- is it called TEL there?

Trying to find out why Android phones pair fine, then connect/disconnect/connect/disconnect before they give up, and never prompt to upload the Contacts to the car's ULF.

Thanks!

[joako]

To answer your question NavCoder will do a fine job with logging the I-bus, but I don't think that will get you anywhere.

I think the best place to look would be debugging the bluetooth stack on the phones.

You'll see many BMW modules marked as TEL, no worries if you don't see a ULF.

[Exwoodchuck]

I agree- the phone's BT stack will tell the real story, but Motorola wants to see the car's data if possible.

Thanks for the info!!!

NavCoder doesn't tell a whole lot of whats going on in the ULF -- I logged a BT pairing, key off, key on/start cycle to see what it'd generate.

I see where it connected-
3/16/2011 5:08:56 PM.359: TEL --> ANZV: Telephone indicators: All_off
And then where it disconnected-
3/16/2011 5:09:13 PM.750: TEL --> ANZV: Telephone indicators: Red


Nothing jumps out in-between those 2 events as to *why* its dropping though.

[joako]

Yes, but how do you enter debug mode in the ULF to log the Bluetooth?

Like I said I-bus log isn't going to be helpful. The entire module is self-contained it will connect to whatever phone and output the control messages over I-bus and the audio, etc over dedicated cables. What you want to know is all happening internal to the module which will require some sort of test/debug toolkit to do that :(

Maybe you can hope with Motorola TCU it works?