FASTECU

Docs › Help

Troubleshooting

Start here when something does not work. If it is not listed, ask on the forum and include the information described at the end.

ECU access is blocked

Open Settings › Account and press Refresh. The tab says in plain words why ECU read and write is blocked:

  • No license key: paste your key and press Activate. See Account, plans & license key.
  • Invalid key, expired trial or payment past due: sort it out on your account page, then Refresh.
  • License could not be verified for more than 7 days: connect the computer to the internet and press Refresh.

A short internet outage is tolerated for up to 7 days after the last successful check.

The adapter or port is not listed

  • Check the cable and press the refresh button of the port list if there is one. A FastECU adapter on USB is listed first.
  • Windows and J2534: the vendor's J2534 driver must be installed. FastECU is a 32-bit program and uses the usual 32-bit J2534 drivers.
  • Linux: the serial port must be readable by your user (on many distributions that means being in the dialout group). A Tactrix OpenPort 2.0 is used directly over USB.
  • Only one connection at a time: stop datalogging or the Bus monitor before using the ECU page. See Ports & adapters.
  • The FastECU wireless adapter: check Settings › FastECU Adapter and use Check status.

Wrong protocol, or the ECU does not answer

  • Check the vehicle on the Vehicle page, or the protocol in the connection card of the ECU page. The protocol has to match the ECU.
  • Trouble codes: change the Protocol dropdown. SSM1 needs a plain serial K-Line cable.
  • Check the ignition and that the battery is healthy and charged.

No definition is found for my ROM

  • Check Settings › Files › ECU definition sources: the right folders and enabled sources.
  • Type the ROM's identifier on the Definitions page and press Find maps.
  • If there is none, see Finding & defining tables.

Tables look wrong or values are strange

  • Run Check the definition against this ROM on the Definitions page.
  • Make sure the definition matches your ROM's exact version. A definition for another calibration puts tables at the wrong addresses.
  • Compare with a known good ROM in Compare ROMs.

Datalogging shows no channels, or a tab warns about missing values

  • Set the Logger definition file in Settings › Files to a RomRaider logger.xml.
  • Press ECU init in the Datalogging panel, so FastECU shows only what your ECU supports.
  • The MAF, Injectors and Dyno tabs find their values by name in the logger definition. A warning lists the ones it could not find.

Checksum shows "wrong" after editing

That is normal after any edit. In the Hex editor open Checksums and press Fix. Do not fix schemes that belong to another family.

A write failed or was interrupted

  • Do not turn the ignition off or unplug the adapter. Keep the power on and try the write again.
  • Keep your backup ROM and the log files; see below.
  • Ask on the forum. Describe exactly where it stopped.
A recovery guide for ECUs that no longer start: coming soon

This is not ready yet. Check back later, or ask on the forum.

Update problems

  • Help › Check for Updates checks again. An update is installed only if it is signed with FastECU's release key.
  • Under Settings › Updates you can choose between the Stable and Beta tracks.

What to send when you ask for help

  • Help › About FastECU has a button that copies the version, platform and update track.
  • The system log: FastECU writes one log file per start, with its own INFO, WARNING and ERROR messages. They are in the system logs folder (see Settings › Files › File locations), and only the newest ones are kept (20 by default).
  • Your ECU, the protocol you used, the adapter, and what you were doing when it failed.