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 '…' (…:…) failed (attempt 1): … — 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 (forever with the default reconnectAttempts=-1); with a limit set it ends Stopped with the error gave up after N reconnect attempt(s) and is started again with the Start button in its Properties — see Driver states and the Start button.
  • unknown setting(s) '…' ignored. Known settings: … — the Settings contain a typo or a parameter name from an earlier version (e.g. reconnectTimeMs, timeoutMs); the driver/protocol ignores it and runs with the default. Rewrite it to a name from the list in the message.
  • 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.

XCP and DAQ

  • A warning like Event '…': eventExtraParams contains daqId without direction at project load — the event's Extra Params are malformed; the message states exactly what is wrong (direction="DAQ" without daqId, a segment that is not in the key="value" form, …). The affected variables stay out of communication until the event is fixed.
  • DAQ event channel N = '<name>' (info at connect) — the ECU's own name of the channel. If it is not the channel you meant, fix daqId in the event's Extra Params.
  • event '…' is configured with X ms but ECU channel N reports a nominal cycle of Y ms — the event's Period does not match the ECU's real cycle. DAQ timing always follows the ECU; adjust the Period so the configuration documents reality.
  • …fall back to polling — the slave cannot serve DAQ (no DAQ resource, seed & key protection, rejected channel, failed setup). The variables are polled instead, at the event's Period — values keep arriving, just slower. Details are in the preceding log lines.
  • DAQ overload / DAQ processing cannot keep up — the ECU (or the PC side) dropped samples; the measurement continues with the next ones. If it repeats, reduce the number of DAQ variables or the channel rate.

Matrix variables

  • An invalid Layout shows up right while editing — the field gets a red border and the error description is in the tooltip (an unknown key, yCount without xCount, a missing dataCount on an array without axes, a non-existent presentation…).
  • Protocol variable specification for variable … could not be created (… exceeding the Modbus limit of … registers …) or (… the XCP limit is 16384 bytes …) — the matrix does not fit its protocol's limit (Modbus 246 B for writing / 250 B for reading, XCP 16,384 B of data) and is not communicated; reduce the value counts or the element types, see Size limits.
  • Values do not match the device registers — check the Endianness and the section types: ushort + Big = one cell per register 1:1; byte cells share a register in pairs, ushort + Little has the bytes swapped.

Free license

  • Free license: the project has N communicated signals, the limit is 5. — with a Free license, neither the communication nor replay starts when the project has more than 5 communicated variables (variables assigned to protocols, counted across the whole project). Remove variables from Communicated, or upgrade the license. The license overview and offline behavior are described in Licensing.

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 scripting is enabled but the Python DLL path is not set… / …does not exist… (warning at application start) and Python DLL path is not configured. / Configured Python DLL path was not found. (error at runtime start) — Use Python scripts is enabled in Options → Preferences → General, but the path to python3xx.dll is missing or the file does not exist (e.g. after uninstalling Python). Fix the path or disable Python (see Installation).
  • Runtime cannot start: the project contains enabled Python script(s) (…) but Python scripting is disabled. (Replay cannot start: … in replay) — either enable Use Python scripts in Preferences or disable the listed scripts in Project Configuration → Scripts (Runtime or Replay column).
  • The project contains Python script(s), but Python scripting is disabled… — a warning only: the runtime runs, the scripts are disabled, nothing is executed.
  • The runtime does not start with an error while initializing Python even though the DLL path exists — make sure it is a 64-bit CPython 3.10 to 3.14; other versions cannot be loaded by QInsight.
  • 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 Data Log Recorder driver 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.
  • Data log file "…" could not be opened: … — the target folder from file cannot be created or written (disconnected drive, missing permission, file locked by another program). The driver stays Faulted with this message while the other drivers keep running; fix the path in Settings and start the communication again.