Xoutpost.com

Xoutpost.com (https://xoutpost.com/forums.php)
-   Bluetooth (https://xoutpost.com/electronics/bluetooth/)
-   -   TCU in a RHD 2001 E53 - no bluetooth (https://xoutpost.com/electronics/bluetooth/81030-tcu-rhd-2001-e53-no-bluetooth.html)

dlclarke 05-05-2011 03:33 AM

Might be a bit longer on getting the logs, waiting for my NavCoder registration to arrive ;) I can then change the VIN number, try all the above, check for faults and report back.

big bob 05-05-2011 03:37 AM

Jochen will be most interested in using INPA to stimulate a EU TCU and learn the commands for Navcoder. I have a semi on thinking about it too. I hope there are loads of options :)

dlclarke 05-05-2011 03:59 AM

Quote:

Originally Posted by big bob (Post 822451)
Jochen will be most interested in using INPA to stimulate a EU TCU and learn the commands for Navcoder. I have a semi on thinking about it too. I hope there are loads of options :)

Are we going to want NavCoder logs at the same time as poking it with an IPNA stick? If so I better build another interface :) I have NavCoder on my Mac and IPNA on a dedicated IBM X31

big bob 05-05-2011 04:03 AM

Quote:

Originally Posted by dlclarke (Post 822453)
Are we going to want NavCoder logs at the same time as poking it with an IPNA stick? If so I better build another interface :) I have NavCoder on my Mac and IPNA on a dedicated IBM X31

I would say not yet. The reason why is that INPA is a full on DOS attack on the data bus.

The Navcoder log you would generate would be horrendous.

What Jochen really needs is a small log of you performing just one function, say clearing the paired phones, then another of the pairing etc etc. It makes it much easier to decipher.

First let's get a poke around with INPA and see what options are available.

big bob 05-05-2011 04:11 AM

As for building a second interface, you have three ways to go. You could get a Resler interface, I've seen £10 iBus interfaces on eBay, or get a new USB-KKL adaptor on back order from China.

Is your car pre or post 09/2001?

dlclarke 05-05-2011 04:14 AM

OK, will do, I know that IPNA won't see it until I change the VIN, so as soon as Jochen sends me my serial number I will change it then snoop around with IPNA and see what it turns up on the TCU. Then see what would be best to do first from there. I have a genuine Ross-Tech VAG-COM cable as well, I will see if it will work as a NavCoder interface just in case.

dlclarke 05-05-2011 04:17 AM

Quote:

Originally Posted by big bob (Post 822455)
As for building a second interface, you have three ways to go. You could get a Resler interface, I've seen £10 iBus interfaces on eBay, or get a new USB-KKL adaptor on back order from China.

Is your car pre or post 09/2001?

Its pre, but doesn't have the big round connector, but does have the round radio pins

Neither computer has a serial port and but I have a bunch of USB to serial adapters that are very good, so could whip up a quickie for NavCoder from the schematic in the NavCoder download if I had to... Knew I should have bought 2x USB-KKL cables ;)

big bob 05-05-2011 04:26 AM

Couple of options for another interface.
BMW IBUS I-BUS to RS232 Interface / Adapter Cable | eBay UK

http://cgi.ebay.co.uk/BMW-IBUS-I-BUS...ht_1977wt_1139

dlclarke 05-05-2011 04:38 AM

Quote:

Originally Posted by big bob (Post 822458)

Thanks for the suggestion, I have another one of these on the way:

NEW FTDI FT232RL KKL USB OBD ODB OBDII OBD2 INTERFACE - eBay (item 370453504187 end time Jun-03-11 07:26:12 PDT)

1 transistor, 2 resistors and reprogram the uART and I have another hybrid i-bis and IPNA/Carsoft cable. I installed a wee socket in the last one and installed a plug on a lead permanently in the boot that matched. Its the devil I know.

I suspect that my CAN-BUS cable will work with NavCoder, will test it and see.

dlclarke 05-06-2011 02:37 AM

log file, nothing much there
NavCoder v2.8.350 - Scan Results
File written 5/6/2011 6:16:33 PM

Single Module scan conducted on 5/6/2011 6:16:26 PM

--------------------------------------------------
Following devices were found and are communicating:

TCU Telematics Control Unit
Part number 9 129 850, version HW 50, SW 34, made by Continental on 18/06 (May 2006)
Diagnostic index 21, Bus index 12, Coding index 05
Stored Fault Codes: 1 [--]

--------------------------------------------------
Summary of stored Fault Codes:

Module Qty Fault Codes
TCU 1 --
--------------------------------------------------



Have now recoded the TCU to my correct VIN with NavCoder and will take a run at the above procedures. IPNA sniff around and screen shots in the morning


All times are GMT -4. The time now is 12:28 AM.

vBulletin, Copyright 2026, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.6.0
© 2017 Xoutpost.com. All rights reserved.