qenex.net
ENCS

Troubleshooting

The first step with any problem: look into the Logs window. The output of Python scripts (print) is separate, in the Script-Logs window.

The device does not connect

  • TCP client connection to …:… failed or timed out (1/3) — the driver cannot reach the device. Check the IP address and port in Settings, the firewall, and that the device is listening. The driver retries; after the attempts are exhausted it stops with reached maximum reconnection count.
  • For PEAK CAN, check deviceId (the hex adapter ID) and bitrate — it must match the bus speed.

Values do not reach the variables

  • Check that both the driver and the protocol are Enabled.
  • The variable must be assigned to the correct source (driver + protocol) and have the correct identifier (signal name, CAN ID…).
  • The protocol must match the driver's data type (see Linking a driver and a protocol).
  • A quick check without workspaces: Tools → Watch → Variables.

Replay

  • Stop runtime before starting replay. — playback cannot start while the communication is running; Disconnect first.
  • Import a data log before starting replay. — use the Import button first.
  • Replay seek is available after the data log is fully loaded. — moving along the timeline works only after the record is fully loaded (and paused).
  • Replay log file "…" not found. — the file from Settings does not exist.

Python scripts

  • Python DLL path is not configured. / …was not found. — set the path to the Python DLL in Options → Preferences → General.
  • script "…" timed out after N ms. — the script exceeded its Timeout.
  • Periodic script "…" has invalid period/unit setting. — check the Parameters (period=500;unit=ms).
  • …exceeds 70% of the call period; skipping next N call(s). — the script is too slow for its period; increase the period or speed the script up.
  • The script "prints nothing" — look for print output in Script-Logs, not in Logs.

Logging

  • The log is not being written — check that the project contains the FileDataLoggerDriver with Enabled and that the variables have Log to FileDataLogger checked.
  • …dropped a record because the log stream was closed. — a write after stopping; harmless during a regular Disconnect.