|
Title: Logging M-box error code 0x04 Post by: BlackT on September 09, 2020, 01:28:26 AM Engine from A6 2.7 allroad, croshflashed with M-box
Direct K-line to ECU When engine is off everything works as it schould, all tools working MElogger, nefmoto, VCDS lite But when car is started, ME7logger lost comunication, nefmoto can't connect, vcds lite also (Same cable works without problems on 1.8T ECUs ) VCDS 11.11 with different cable can connect while engine is running Code: HWNumber = 0261207143 (requested was 026120714 Is this maybe cable problem or M-box have this issue? I tryed differnet log speed, SLOW-0x11, FAST-0x01 no change Title: Re: Logging M-box error code 0x04 Post by: Blazius on September 09, 2020, 08:27:15 AM Try slow 0x00 and connect with ignition on, engine off then start , doubt it will fix it but worth a try.
Title: Re: Logging M-box error code 0x04 Post by: nyet on September 09, 2020, 08:39:37 AM You may have to run a dedicated kline, some ar harnesses are crap for some reason, or there is something on the kline that me7l doesn't like.
Title: Re: Logging M-box error code 0x04 Post by: BlackT on September 09, 2020, 08:45:35 AM You may have to run a dedicated kline, some ar harnesses are crap for some reason, or there is something on the kline that me7l doesn't like. Engine from A6 2.7 allroad, croshflashed with M-box There is only ECU on K-lineDirect K-line to ECU When engine is off everything works as it schould, all tools working MElogger, nefmoto.... Title: Re: Logging M-box error code 0x04 Post by: nyet on September 09, 2020, 11:17:24 AM There is only ECU on K-line If this is the case, you should be able to run both ME7L and the nef flasher at max baudrates to the 551M ME7.1 ECU If you cannot 1) laptop is bad/slow wrong drivers, etc 2) cable is not good (usually go or no go though) 3) k wire improperly wired (bad connection) 4) noisy ground 5) noisy voltage Does your ME7L setup work on the bench with the same ecu/cable/laptop? Title: Re: Logging M-box error code 0x04 Post by: Blazius on September 09, 2020, 04:36:06 PM FYI slow 0x00 was the only thing that fixed my 0x04 error code. Nothing else worked and can only connect with engine off and then start motor.
Title: Re: Logging M-box error code 0x04 Post by: nyet on September 09, 2020, 09:44:54 PM FYI slow 0x00 was the only thing that fixed my 0x04 error code. Nothing else worked and can only connect with engine off and then start motor. If you had to do this on a 2.7t 551M on the bench, something is wrong. If you had to do it in the car, and it has a dedicated k-line with a 551M, something is wrong. What ECU did you see this issue with? Title: Re: Logging M-box error code 0x04 Post by: BlackT on September 10, 2020, 02:59:25 AM If this is the case, you should be able to run both ME7L and the nef flasher at max baudrates to the 551M ME7.1 ECU If you cannot 1) laptop is bad/slow wrong drivers, etc 2) cable is not good (usually go or no go though) 3) k wire improperly wired (bad connection) 4) noisy ground 5) noisy voltage Does your ME7L setup work on the bench with the same ecu/cable/laptop? A few facts -VCDS lite at cable TEST show message "poor latency" -Cable is working on all 1.8T ECUs without problem( except 512 kb) it is working on 2.7BiT ME 7.1.1 also without problems -Only once I could not connect with nefmoto to MK4 VR 2.3, then i used K-commander cable and it could connect. -On this car/ecu/laptop, ME7L/nefmoto is working when engine is off First I will try to connect with K-commander cable when engine is ON with nefmoto. If it can still can't connect then probem is somewere in harness I will check connection and grounds Title: Re: Logging M-box error code 0x04 Post by: Blazius on September 10, 2020, 09:13:42 AM If you had to do this on a 2.7t 551M on the bench, something is wrong. If you had to do it in the car, and it has a dedicated k-line with a 551M, something is wrong. What ECU did you see this issue with? Ah no it was not a 2.7/me7.1 ecu but mine me7.5 018Q that is still in the car, and I am pretty sure the kline goes thru instrument, but I am just saying that was the only thing that works/worked for me. Title: Re: Logging M-box error code 0x04 Post by: nyet on September 10, 2020, 11:32:34 AM Ah no it was not a 2.7/me7.1 ecu but mine me7.5 018Q that is still in the car, and I am pretty sure the kline goes thru instrument, but I am just saying that was the only thing that works/worked for me. I guess I'm saying all of that isn't really applicable because ME7.1 is generally rock solid and can be run out to max baud with no issues (as long as the kline doesn't have anything else on it). The ECUs that have shitton of init/timing/noise problems are ME7.5 and ME7.1.1 Title: Re: Logging M-box error code 0x04 Post by: Blazius on September 10, 2020, 04:44:36 PM I guess I'm saying all of that isn't really applicable because ME7.1 is generally rock solid and can be run out to max baud with no issues (as long as the kline doesn't have anything else on it). The ECUs that have shitton of init/timing/noise problems are ME7.5 and ME7.1.1 Aye. I also dropped sample/s to 25 , mostly coz of cpu load tho. Title: Re: Logging M-box error code 0x04 Post by: nyet on September 10, 2020, 06:26:12 PM Aye. I also dropped sample/s to 25 , mostly coz of cpu load tho. Yes, separate issue! :) Can also affect ME7.1 if you log too many vars Title: Re: Logging M-box error code 0x04 Post by: BlackT on September 11, 2020, 08:18:44 AM I tryed with diferent cable, shorten K-line to 5 cm, put OBD ground at ECU ground. It helped a little but data was mess
When nyet have mention noise ground and positive, that gave me idea, when car is started altenator is also started. Then I have discconected altenator and voala, ME7L is working when engine is started. Full speed, 50 sample/second Thank you for your help I will check all grounds of engine loom, and conncetions |