Pages: [1]
Author Topic: Immo 3 ECU-Cluster adaptation issue  (Read 2991 times)
JaYS4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 6


« on: November 03, 2020, 02:42:20 PM »

Hi everybody,
First of all, thanks a lot for all the sources, tools and knowledge shared by this forum and its members.
it is an incredible source of knowledge which allowed me to start on the electronic part of my personal project (nothing crazy for now, unfortunately, as I still have to learn many things).
I swapped a 2000 sedan 2.8 V6 (APR) with a totally refurbished 98' 2.7TT AGB engine, and converted the AGB harness to the car.

After many hours spent on the s4Wiki and here, I decided to buy a M-Box from ebay to replace the C-box that came with the 2.7TT.
I dumped ECU and 95040, did the same with the v6 box, and with the V6 cluster (which seems to be a replacement part, with immo 3), to try to make all work together.

I put the maps needed for an EU AGB with a Bosch MAF (pulled from a C-Box dump, and compared it to Mbox already adapted to Bosch MAF), corrected ESKONF, and flash it back to my M-box.
I then tried to start the car, which did nicely, but engine died after a 3s delay... VCDS showed a "18058 - Powertrain Data Bus: Missing Message from Instrument Cluster".
I followed the adaptation instructions provided by Ross Tech for both ECU and cluster, but I can't access channel 50 neither on one nor the other...

I tried the channel 60 adaptation to switch from 0 value to 1025 with no success. (original V6 ECU was with Immo2, according to eepromtool). 
VCDS now shows a 01177 49-00 "No communications", and Motor still dies after 3s.

Using the very handful tools provided by you guys, I managed to take a look into the M-box 95040 (which btw contains a tuner tag "NEFMTO"), and to compare it to the V6 ecu eeprom paired with the cluster, and the cluster eeprom:
- MBox and V6 box has the same SKC, 65535;
- MBox and V6 box has the same Immo ID, XXXXX...XX;
- Mbox and V6 box has the same Cluster code: 00 00 00 00 00 00
- Mbox has a VIN, while V6 box is set to XXXXXX...

So I mixed all of this, and cooked my own 95040: set SKC with the value used in cluster; set the cluster code to the value set in the cluster; changed the VIN to X only and let the immo ID to X only too. EEpromtool was showing "Immobiliser: error, set immo", so I turned it off.

But again, no luck, same messages and engine dies after 3sec...

I'm missing something as I'm a noob, and this time I can't manage to find any clue over the forum or the internet. That's why I'm posting: I need advices from the community on what to try now.  Sad

My goal at the moment is to start the car so that it can drive. I'll have more tune to do later, but I want to get rid of all the little problems before...
For interested people, my project setup for now: entirely refurbished engine, brand new RS4 turbos, A6 allroad plenum, full inox exhaust line, FMIC. Waiting to install my 630cc Siemens injectors and my fuel pump. RS4 B7 rear brakes, and trying to find 8 pots calipers for the front.

Thanks ! and sorry for this long post.

J



Logged
BlackT
Hero Member
*****

Karma: +79/-40
Offline Offline

Posts: 1425



« Reply #1 on: November 03, 2020, 04:07:06 PM »

M-box doesen't have immo. You car is have other issue. Try unplug MAF then start car
Logged
JaYS4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 6


« Reply #2 on: November 03, 2020, 04:57:39 PM »

Yeah, I know for immo and M-box, but I forgot to mention: I had the same results with a K-box immo off (This k-box is working as I used it on 2 different RS4 B5).
Before the swap, the engine was running perfectly fine.

Eepromtool displayed an error about Immobilizer, that's why I set it to immo-off. But maybe this is a normal status for M-box...
I can flash back "original" 95040 bin with cluster's SKC, VIN, IMMO ID, and cluster code.

I even tried to put back the original V6 box: the car starts and idles almost perfectly.

Another thing: when I try to log in motor module with VCDS, I have some communications problems right after pressing Enter, and I loose connection. I can hear the cluster's relay click in and click out repeatedly, and can't use VCDS anymore. I must turn off and on the car again. (I'm using a FT232R cable with VCDS)





Logged
_nameless
Hero Member
*****

Karma: +342/-466
Offline Offline

Posts: 2800



« Reply #3 on: November 03, 2020, 09:33:00 PM »

stop cross flashing threw port and bench flash it
Logged

Giving your mom a tuneup
JaYS4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 6


« Reply #4 on: November 04, 2020, 04:25:31 AM »

All the flash are done on my bench, and tools provided by the forum (Nefmoto, ME7Check, eepromtool...).
I used Tuner pro and HxD for editing.

You car is have other issue. Try unplug MAF then start car
This made me check again what I had done with the wiring: I am missing the ECU wire 30 to T32 / 6, I forgot it because I had no idea where it was going when I modified the harness, and the only description I found for it was" Tank warning OBD 2". I wasn't too worried that I didn't wired it, hoping to have a DTC in the worst case.

I'm going to double check the quality of the connection between ecu 43 and T32a/5 too

Edit: I don't really believe in a wiring issue tbh, when I plug the original V6 box, the car starts and idles without any problem... (with missing wire on ecu pin 30). I'll give it a try anyway
« Last Edit: November 04, 2020, 07:01:38 AM by JaYS4 » Logged
JaYS4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 6


« Reply #5 on: November 05, 2020, 03:47:05 PM »

Did some other tests lately:
- 17 instr Channel 22 shows 0 for ECU communications, ECU is not seen by any module (ABS for example, same error 01177 49-00)
- Reverted my ECU 95040 to "original" one (on my bench, in boot mode), as I've seen on another forum that Immo off could prevent the ECU to be detected by the Cluster and show a "no communications" error
- Tried the code "1029" in 17-instr Adaptation channel 60 (instead of 1025 or 0) - I can't find any documentation on available values for this channel other than Ross Tech's
- plugged the ECU 30 pin to T32/6, now channel 22 tells me I'm not allowed to start the engine

I pulled my cluster and Mbox out of the car, and plug them together on my bench. I have the same results. When I try to log into the engine module, connection fails ans I loose the session. The relay in the cluster clicks in loop, and I can't connect anymore to the VCDS engine module (but I can connect to the cluster). Same thing if I directly connect the computer and the ecu.

Could it be something wrong in the ECU bin?  

Cluster is a 8D0 920 932GX D17 from 2007 (according to the sticker on it). Trying to make it work together with a 8D0907551 M




« Last Edit: November 05, 2020, 04:18:13 PM by JaYS4 » Logged
JaYS4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 6


« Reply #6 on: November 07, 2020, 01:22:35 PM »

Hi, I finally sorted it out, I had to use the CW_CAN_R tweak, has the channel 60 adaptation had no effect.
The car might have originaly been an Immo2 car, the cluster is a replacement one with immo3, so I foolishly believed that with a M box, it would just be plug n' play.

I have some DTCs to take care about, but it starts and idles like a charm. Still have the 01177 49-00 DTC in cluster.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.03 seconds with 17 queries. (Pretty URLs adds 0.001s, 0q)