Error Code Lookup

What it means

TDN cannot find or enable the interface Bluetooth connection.

Likely causes

• TDN app installation or permissions
• Stale phone pairing
• Interface Bluetooth needs reset

What to do

1. Reinstall TDN if needed.
2. Power the interface by USB.
3. Hold its Bluetooth button for 10 seconds until flashing.
4. Forget existing MPVI pairings and toggle phone Bluetooth.
5. Run Tools > MPVI/RTD Setup again.

What it means

The interface or software could not retrieve the required flash data.

Likely causes

• Insufficient Internet connection
• Incorrect PC date or time
• Further diagnostics required

What to do

1. Confirm a stable Internet connection.
2. Correct the computer date and time.
3. Retry once.
4. If it continues, gather the requested infolog/debug information and contact support.

What it means

TDN encountered a file, resource, or synchronization problem while preparing a write.

Likely causes

• Outdated resource files
• Stale file-sync data
• Cached file problem

What to do

1. In TDN Tools, run Resync.
2. Update resource files.
3. Retry the write once.
4. If unresolved, reset file-sync/cached resource data as documented, resync, update resources, and gather an Infolog immediately after failure.

What it means

The phone cannot see the AutoAgent wireless network.

Likely causes

• AutoAgent is not powered
• Wireless radio is not broadcasting
• Unit needs a power reset

What to do

1. Confirm a solid green power light.
2. Look for a solid blue wireless light.
3. If only green is visible, disconnect the cable at the AutoAgent box and reconnect it.
4. After green and blue are solid, search for EZLYNK_XX again.

What it means

This phone message is normally expected while connected directly to the AutoAgent network.

Likely causes

• The EZLYNK network connects the phone to the vehicle rather than providing Internet access.

What to do

1. Remain connected to EZLYNK while communicating with the vehicle.
2. Switch back to cellular data or normal Wi-Fi when the app needs cloud access, then reconnect to the AutoAgent as directed.

What it means

The AutoAgent has power but the vehicle ECM is not responding.

Likely causes

• Ignition is not in Run
• ECM was not booted before connection
• Loose OBD-II connection

What to do

1. Unplug the AutoAgent.
2. Place the ignition in Run with engine off.
3. Reconnect the AutoAgent.
4. Confirm the blue light and join EZLYNK_XX.
5. Open the app and verify Connected.

What it means

The EZ LYNK app cannot communicate with the vehicle ECM while streaming data or performing a tuning operation.

Likely causes

• Ignition is not in RUN
• Loose or damaged OBD-II connection
• Locked ECM or controller-related condition

What to do

1. Put the ignition in RUN without starting the engine.
2. Verify the EZ LYNK device is securely connected.
3. Inspect the OBD-II connection, connector, cable, and pins.
4. Retry communication.
5. Contact your tuning technician if the problem continues.

What it means

The AutoAgent rejected an incomplete profile download.

Likely causes

• Incomplete download while switching networks or using cellular data

What to do

1. Unplug the AutoAgent.
2. Connect the phone to a reliable Internet source.
3. Use the Cloud/fetch button to download the profile again.
4. Reconnect the AutoAgent and retry installation.

What it means

No technician-managed profile is currently available for the selected vehicle.

Likely causes

• Vehicle is not Lynked to the technician
• Technician has not distributed a profile
• Wrong vehicle selected

What to do

1. Open Vehicle > Technicians and confirm The Tune Shop is listed.
2. Confirm the correct vehicle is selected.
3. Contact The Tune Shop to request or verify the profile.

What it means

The tune file was created by a newer software/file format than the installed software or firmware supports.

Likely causes

• Outdated EFI Live software
• Outdated device firmware

What to do

1. Install the current official EFI Live software.
2. Update device firmware as directed.
3. Reopen or retransmit the tune file.
4. Contact The Tune Shop if the file still does not open.

What it means

Read/flash support does not always mean calibration mapping is available in the current editor.

Likely causes

• Controller mapping is not available
• Mapping may require a different EFI Live tool version
• The Tune Shop needs the read for an alternate supported workflow

What to do

1. Do not alter or replace the file.
2. Send the exact message, controller details, and read file to The Tune Shop.
3. Follow the application-specific workflow supplied by support.