E-Sys error codes explained

E-Sys shows an error code with a short English line. The line says what failed, rarely why. Below are the common ones with the usual causes, starting with connection problems, which are by far the most frequent.

Connection errors

C029: "Failed to open connection with the given settings."

E-Sys tried to connect with the option chosen in its Connect window and the car (or ICOM) did not take the connection.

• With Connection via gateway URL: the address is old or wrong. Car addresses on an ENET cable start with 169.254 and use port 6801.
• With an ICOM: the address or port is wrong (the gateway is normally port 50160), or the ICOM is reserved by another PC or by ISTA. Release it there.
• Another program, or an old E-Sys still running in the background, is holding the connection.

C074: "Detection of available vehicles failed!"

E-Sys's car search did not get through. Check that the network adapter is up and has an address, turn off VPN software, and allow E-Sys's Java (javaw.exe) in Windows Firewall and any security suite.

C078: "No connection established."

You pressed something that needs the car before E-Sys was connected, or the connection dropped (ignition off, cable moved, laptop went to sleep). Connect again.

C370: "No vehicle found with ID … Available vehicles: …"

With Connection via VIN, E-Sys looked for the car it remembered and it did not answer this time. Pick the car again from the list; if the list is empty, see ENET cable or ICOM.

G013: "Connection via VIN is currently not possible."

No car answered E-Sys's search, so there is nothing to pick. Ignition on, cable or ICOM connected, and if you use an ICOM choose Connection via ICOM/Ethernet instead.

C058: "Reading VIN from master failed."

E-Sys is connected but the car's main module did not tell its VIN. Usually a short connection problem or a module still waking up: wait a moment with the ignition on and try again.

Vehicle order and module list

C060: "Read FA failed! Possibly there is no FA stored in the VCM."

The vehicle order (FA) could not be read from the car. Check the connection first. On a car where the vehicle order was never written (some replaced modules), it really is missing and has to be written again.

C062: "Read FP failed! Possibly there is no FP stored in the VCM."

The same for the vehicle profile (FP), which E-Sys calculates from the vehicle order. If the FA reads fine, calculate the FP from it in E-Sys.

C043: "Detection of integration step failed."

E-Sys could not work out the car's I-step. Usually the vehicle order or module list was not read yet, or the PSdZData is older than the car. See What is PSdZData?

Coding errors

C045 / C047: "Generating of NCD for CAFs … failed!"

E-Sys could not build the coding file for a module. The usual causes: the vehicle order was not activated (press Activate FA first), the PSdZData does not contain that CAFD version, or the selected CAFD does not belong to this car.

C069: "NCD read from ECU … for CAF … failed!"

Reading a module's coding failed: the module did not answer, is asleep, or the CAFD selected does not match the module. Read the module list (SVT) again and select the CAFD under that module.

PSdZData errors

C072: "Failed to set PSdZ root to …, because it's no directory!"

E-Sys's PSdZData folder setting points to a folder that does not exist (a pack that was moved, renamed or deleted). Set the folder to where your PSdZData is now and restart E-Sys.

General

C027: "Runtime error occurred."

Something failed inside E-Sys. Press Details >> to see the actual reason, which is usually one of the problems above. Restart E-Sys if it keeps coming back.

The E-Sys MAX launcher has a car connection check that finds most connection causes for you (the cable, the address, VPN, firewall, the ICOM, an old E-Sys still running) and a problem report that collects E-Sys's logs into one file you can send us.

Questions

Where does E-Sys write its log?

In the log folder of your E-Sys data folder. The error window's Details >> button shows the full message, which is often enough. E-Sys MAX's problem report collects the logs for you.

Can a failed coding damage the car?

A coding that stops in the middle usually leaves the module with its old coding or with faults until it is coded again. Keep a charger on, keep the original coding file, and code it back if a feature misbehaves.