AdBlue return pipe failure during detection mode. - This fault can cause an engine derate to +/- 60% of the maximum torque
Possible cause - AdBlue return pipe frozen / blocked - Ventilation valve defective - AdBlue pressure sensor defective (inside EAS unit) So the system concludes that the adblue return tube is damaged. Error generated during the control phase. Usually it is the system that activates the pump for a short time and observes the increase in adblue pressure. If the system cannot see, for example, the drop in adblue pressure after opening the bleed valve, it concludes that the return tube is damaged. The pressure sensor may be faulty [which I doubt]. In general, an error generated by the wrong signal from the Adblue pressure sensor inside the EAS module.
I replaced the ad-blue filter, also the mesh filter. I blown the return line into the tank and it is unobstructed. Excluding malfunction of the pressure sensor ad-blue, can the bleed valve be damaged? During the leak check test during the phase of ad-blue return to the tank its opening was at 0%. At the same time, what was strange, the pressure dropped to 120 mbar. The second thing. I also did a dosing measurement test. Its result was the lack of dosing, as if the dosing module did not get a signal to open at all. I could not hear the characteristic ticking only air. I think no other errors. Maybe this error 61-3 caused the system to switch off before dosing errors could occur. Unfortunately, there was not enough time for further diagnostics because the car had to drive (because the power was not limited).
The car returned now error 61-255. I removed the dosing module, resistance on the injector pins 15.3 ohms, washed out with air. I did the dosing amount test, the injector gave about 150 milliliters, which is normal. I deleted the error. Now the ECU is clean. exactly this error applies because in jalteszt there is a very general description. Is it difficult to deduce anything?
There is no such error code as 61-255. The closest is 61-2 where the 255 terminal is FMI (Failure mode indicator). Daf does not show error codes for code 61 up to the third byte but only ends at the first, i.e. only 61-1, 61-2 and 61-3 are exactly. Form 255 probably means the type of fault, where the first byte - 2 means No pressure build-up in AdBlue pipes during detection mode a terminal 55 must mean one of the forms of the test that the system failed during the diagnosis phase (e.g. after 4 seconds of operation of the adblue pump, it recorded so much pressure and it should do a lot more). Have you checked the mesh filters in the adblue tank dragon and at the EAS module inlet? The tube from the dragon to the adblue module is not bent?
there are occasional warning messages on the board regarding the exhaust system. the message appears for a few seconds and disappears 2-3 times a week. and the next thing that came to my mind after changing the filters was to clear the system. Errors 115, 70, 108 and 17 appear errors occur only at idle. Euro car 5, 2014 mileage of 360,000 km.
The discussion revolves around the Daf XF 105 experiencing an Ad-blue error, specifically code 61-3. This error indicates a potential failure in the AdBlue return pipe, which can lead to significant engine derate. Possible causes include a frozen or blocked return pipe, a defective ventilation valve, or a faulty AdBlue pressure sensor within the EAS unit. Users have shared their troubleshooting steps, including replacing filters, checking for blockages, and testing the dosing module. One user noted a subsequent error code 61-255, which was clarified to be a misinterpretation, as only codes 61-1, 61-2, and 61-3 are valid. Recommendations include checking mesh filters and ensuring proper pressure build-up in the AdBlue system. Summary generated by the language model.
