Most INCAZ issues can be isolated by asking which layer failed: file import, hardware connection, acquisition setup, calibration layout, flash procedure, or GUI/installation. Keep the relevant logs, project database, A2L/HEX identifiers, and target software version together.
Installation and application start
| Symptom |
Likely cause |
Action |
incaz command is not found |
Virtual environment is not active or installation failed. |
Activate the environment and run pip install -e .; use python -m incaz.app for console output. |
| GUI does not start |
Python/Qt dependency mismatch or graphics environment issue. |
Use a supported Python release, reinstall dependencies in a clean virtual environment, and capture terminal output. |
| Demo ECU cannot start |
Port conflict or environment issue. |
Check whether port 5555 is already in use; start the simulator from a terminal and inspect the error. |
A2L, data set, and calibration
| Symptom |
Likely cause |
Action |
| A2L import fails or objects are absent |
Unsupported/malformed construct or file does not match expectation. |
Keep the original A2L, reduce to a reproducible example, and report the parser message with the relevant A2L section. |
| Characteristic editor cannot write |
Missing address/layout, read-only/fixed axis, no online connection, or access protection. |
Review A2L characteristic/axis attributes and record layout; confirm backend/page/access state. |
| Offline value appears wrong |
Wrong HEX, address, byte order, conversion, or record layout. |
Verify the matching A2L/HEX pair and compare raw bytes before assuming an editor error. |
Connection and measurement
| Symptom |
Likely cause |
Action |
| Cannot connect |
Wrong host/port/protocol, routing/firewall issue, or target not running. |
Verify network reachability and target XCP configuration independently, then compare Hardware settings with the A2L/ECU setup. |
| DAQ starts but no samples arrive |
Wrong event/raster, unsupported data type, target DAQ state, or network issue. |
Start with one known signal on one known event; inspect status/log; stop/recover target DAQ according to ECU procedure. |
| Measurements are slow or aliased |
POLLING rate is too low for the signal or wrong raster is selected. |
Use DAQ and assign the producer task/event for timing-critical signals. |
| GUI becomes busy |
Too many signals at an excessively fast raster. |
Reduce signal count, select appropriate event rates, and split the experiment into focused views. |
Flashing
| Symptom |
Action |
| Nothing to program |
Verify that the selected HEX contains segments and configured ranges overlap them. |
| Programming is rejected |
Confirm PGM access, target state, seed/key requirements, range configuration, and exact image compatibility. |
| Flash finishes but ECU does not behave as expected |
Use the target’s recovery/version-identification procedure; validate boot, A2L/HEX pairing, and reset behavior. |
Support bundle
For a reproducible support case, collect: INCAZ version/commit, operating system/Python version, A2L and HEX identifiers, database/experiment name, Hardware configuration with secrets removed, selected measurement mode/events, application log, target service/log information, and exact steps. Never place live credentials, seed/key material, vehicle identifiers, or confidential calibration data in a public issue or screenshot.
Safety reminder
Measurement and calibration can affect running systems; flashing can make an ECU unavailable. Use a simulated target first, follow your organization’s authorization and safety process, and avoid testing changes on public roads or safety-critical systems.