Chip-Tools
Chip-Tools

Troubleshooting connection problems and sending log files to Abrites support

Moto Interface Classic Diagnostics Basic ⏱ 15-30 min 8 steps

The most common problem with the bike software is not being able to open a diagnostic session with the ECU, or an error during key learning. This guide lists the causes to check and explains how to retrieve the log files to attach to a support request.

Required licences

Hardware / cables

  • AVDI
  • programmatore transponder TAG

Procedure

  1. If a connection error message appears after selecting the vehicle and the module, first of all check that the AVDI is connected to the computer.
  2. Check that the diagnostic connector is properly seated on the vehicle and that the cable is the one specified for that model.
  3. If the error appears during "Key learning", check that the transponder programmer is connected to the AVDI: that is the usual cause of that specific error.
  4. Bear in mind that module support can vary by model year: the full list of supported models is published on www.abrites.com.
  5. To collect the logs go to Start -> Programs -> ABRITES software for IDxxxxxx -> Log Files, where IDxxxxxx is your AVDI ID; alternatively open the second page of the "Quick Start" menu and click the "LOG" icon.
  6. In the log folder open the "BIKE" subfolder.
  7. Copy the ".log" files matching the date and time when the problem occurred.
  8. Attach those files to an e-mail to support@abrites.com describing the problem: without logs, support cannot trace the cause of the communication failure.

Reference screenshots

Troubleshooting connection problems and sending log files to Abrites support — 1Troubleshooting connection problems and sending log files to Abrites support — 2Troubleshooting connection problems and sending log files to Abrites support — 3
Source: Manuale Abrites Diagnostics per moto, snowmobili e moto d'acqua (bikes), cap. V Troubleshooting steps (p.28-30) · ⏱ estimated time 15-30 min
← All Abrites guides

More guides Moto