MAN TGX 440 - Error EDC 03819-04, DIAG 02061-08, INST 08135-04

Hello,

I need error descriptions as above. In addition, there is information about the malfunction of the AdBlue system and information in the GDK / PDF FNr diagnostics. I am surprised that there is no error in GDK / PDF, but I have not driven the vehicle yet and I do not know if it cuts off the power or not. After turning off the vehicle and restarting the bugs, they are silent, only after a while they show up.

I would like to add that the errors caught fire after about 50 hours of downtime and turning the ignition switch, I wanted the car to burn out so that the battery would charge a little (I'm on the road) and they popped up right away ...

Thank you very much for the error descriptions and any hint.

I would like to add that the AdBlue level indicator is at zero and every now and then it will jump up and down again ...

Good morning.
If it is possible, I will stick to the topic. Errors similar to the above EDC 03819-08, INSP 08135-04. I only found a problem with Ad Blue.
Can anyone help?

EDC 03819-04 - CAN side 3 - no signal

DIAG 02061-08 - CAN signal from the exhaust from the control unit - distorted signal
INST 08135-04 - AdBlue tank information error Filling level - no signal

You have a problem with the beam rubbing somewhere and therefore the sensor works once and then fails. Trace the electrical wiring starting with the adblue tank

I hook up I have the same problem does someone know where it can not connect ???

EDC 03819 CAN 3 module (CAN additional exhaust gas treatment Master-Slave). - The shutdown status by the CAN3 module In the case of EDC7 C32 Master-Slave with MAN AdBlue A-CAN (CAN additional exhaust gas treatment), it is connected to pin 25 (wire 191) and pin 32 (wire 192) of the Master controller, and OBD -CAN to pin 25 (wire 185) and pin 32 (wire 186) of the Slave controller CAN connection with OBD-DCU15 plug socket, AdBlue fill sensor and NOx sensor (version P362V25 with joint CAN exhaust gas and OBD-CAN) pin plus B25 pin minus B32 set value 115-125 ohm.

And it is better to write to check the orange plug, which is at the height of the right tank, closer to the frame, if there is no problem there, with voltage - green pins, maybe it is worth replacing the adblue tank fill sensor from the bottom?
Unplugging and reconnecting the plug - the cube from the adblue pump also works wonders - it has been tested many times - which does not mean that the entire plug can be replaced, as well as the wiring. Good luck.

It was a provocation

Why, you need to help because your friend will leave a lot of money on the site, and who will bring us potatoes and chicken breasts cheaply?

the dragon and the plug are ok, I unplugged another tank and nothing else. there must be a short circuit somewhere because the clock is blinking, I will continue to look for a service

Sorry! I did not mean any maliciousness, this is a detailed description of the EDC error, the colleague will be able to check the wires with a meter by the cable numbers and where the problem is in the harness, no one can indicate 100 percent, sometimes an ordinary accident helps, and sometimes a good one eye.

no need to apologize, I understand everything, description is ok, I am also without any malice,

When measuring the wires, we must remember, of course, to disconnect all components on the CAN bus, i.e. ... NoX, EDC, Adblue tank and Adblue pump / controller .
A sensitive point for corrosion and the lack of connections are the bridges for the CAN bus and the power supply of these components, which are thoughtlessly placed in the bundle, in the frame above the plug of the NoX sensor. Correct me if I confuse the locations.
Before wiring measurements, you can start by disconnecting the NoX sensor, as it itself may interfere with the CAN.

Hello,

I'm sorry that I was silent for so long, but I had a bit of a headache.

So yes, in my case the AdBlue fluid level sensor needs to be replaced. But, that's right, there is BUT ... The mechanic said that we will drop some liquid from the tank, halfway down, and we'll see what happens. After dropping the liquid from the tank to 40 liters, i.e. halfway, and after restarting the system, everything works, AdBlue is consuming normally, no errors.

I suspect that when I pour more than half, it causes mistakes again, but for now, I will not check it. In 2 weeks, when I come back to Poland, I will pour it under the cork and see what will happen.

Despite this combination, I have a sensor to replace 90%, apparently when the float rises higher, something fails ...

In my opinion, your mechanic is wrong, because the sensor is a sonar and it either works or not, and so if you checked the entire beam and you are sure that it is ok - check what the controller sees in the pump, i.e. how many liters is the tank programmed - at my company after such games, with the replacement of 3 sensors with a beam opened 5 times and a change of the tank, I suggested to my colleague a preview of the parameters - he was more astonished when I rode up from the side with the other man, I unplugged the orange plug - the one behind the venting of the right tank (diesel) and connected to another indicator showed a full tank. disconnect the plug from the pump and reconnect.

I have the same problem, EDC 03819, a colleague connected the computer. MANA, there is no CAN signal, he does not see any element from the adblue system, he connected a new adblue level sensor, the same, says that the can signal cable is worn somewhere, but where to look? ripping the entire bundle defeat, maybe someone knows the cable number, yesterday I checked the Nox sensor harness, adblu pumps, they look ok (no cable "came out" from the conduit) I found 1 frayed pink cable 40 134 - it was in a thick conduit in the bundle on the right side the cabin that goes from the cabin, next to the radiator into the frame and on, the cable is soldered, the heat-shrinkable shirt, but still the same. It turns out that something else has been released somewhere, but I do not know where to look. Maybe you can suggest something.

Hello,

Gentlemen, after cutting the plug at the AdBlue tank, everything returned to normal.

Regards

Gentlemen, after cutting the plug at the AdBlue tank, everything returned to normal.
- I will never believe it.

Fast_international wrote:

Hello,

Gentlemen, after cutting the plug at the AdBlue tank, everything returned to normal.

Regards

Sorry, I meant after unplugging and reattaching, not cutting out.

Sorry for the typo

Refers to error ecc3819, Man TGX D26, AdBlue worked until the end of normal, the sensor shows the level of AdBlue, some voltage is on the orange plug. In desperation, I thought I would gain some time to repair, I connected the AdBlue modulator to cables 191 and 192 in the box under the hood by the driver's legs. Unfortunately, it just doesn't throw the error about exhaust aftertreatment, but I continue to have a problem with CAN and error 3819. electrical and engine failure on the dashboard.
Does this somehow narrow down the search for a cable break? I've looked externally through the cable junctions, I haven't noticed anything, and overall I don't know how to go about it. The cable junctions are not split, you have to cut it all? Any good advice
Thanks in advance for the hints.

At the same m/w time a trailer ABS error popped up, I thought it was a different tale trailer fault but it's a tractor ebs connection error with can ! Autocom error 249-modul ebs does not send can signal , 198- speed front axle no information , 199- can bus signal village, 91- can signal EBC1 , so it is falling apart all over.

Start with diagnostics, see what signals are missing and where, eliminate whether the problem is cables or something else.

SPN 8135 CAN data bus message from exhaust
cleaning system control device
Monitoring strategy
Monitoring CAN data bus message from exhaust aftertreatment system control device
Customer reception/description of symptoms
- Information from the instrument cluster is available on a limited basis
Failure Mode Identification (FMI)
FMI 4 No signal
Display indication
Priority 5 Text
indication
---.
Control device conditions
Setting conditions
The A407 instrument cluster does not receive the CAN data bus message from the control device of the
exhaust gas cleaning system
Resetting conditions
The CAN data bus message is received and is reliable
Cause
Possible causes
► The electrical wires and plug connectors of the CAN data bus between the control device of the
exhaust gas cleaning system and the A407 instrument cluster are damaged or disconnected
Checks
Possible check steps
► Turn on the ignition, read the diagnostic memory of the entire vehicle using the MAN-cats application and
check the entries in the diagnostic memory
Check the software version and compatibility of the exhaust aftertreatment control device and
the A407 instrument cluster
Check the electrical wires and CAN data bus plug connectors between the
exhaust aftertreatment control device and the A407 instrument cluster for a short circuit to the
positive power terminal, to ground and between the High/Low wires, as well as for damage,
breakage, transition resistance, change in cross section, corrosion, correct connection and loose
contacts
SPN_8135_CAN-Datenbusbotschaft von Steuergerät
Abgasnachbehandlung_INS-Cluster-CONTI : 2022-01-26 : 2/2
Measure
Possible remedy
► Repair or replace electrical cables and plug connectors as necessary
Note
Additional information/advice
► Note SPN-related documents and technical information, if available
► Control device monitoring functions have detected a missing CAN data bus message.
The cause is probably on the side of the CAN bus message transmitter or in the wiring
of the vehicle. Therefore, read the diagnostic memory of the entire vehicle and check the entries in the
diagnostic memory of the CAN data bus message sender
► Consider the system description "CAN-Controller Area Network"
► Observe the vehicle wiring diagrams during the check

Added after 46 [seconds]:

SPN 8135 CAN message - information -. Central on-board computer
Monitoring strategy
Monitoring of CAN signals
Customer reception/description of symptoms
- Warning light yellow
- Control light yellow
- Buzzer
Failure Mode Identification (FMI)
FMI 4 No signal
Display indication
Priority 5 Text
indication
-. Central fault light illuminates steadily in yellow during driving and
stopping
Cause
Possible causes
► Message "Tank Information1" does not display
Checks
Possible check steps
► Check AdBlue and EDC control device
► Check tank fill level with MAN-cats® II.