A hardware configuration tells INCAZ how to reach an XCP slave and how acquisition should operate. It belongs to the imported project in the database, so an experiment can be reopened with its expected connection settings.
Open the hardware dialog
Select the project in the database, then choose Hardware → Configure…. When an A2L contains IF_DATA XCP transport information, INCAZ uses it as a starting point. Always review the values against the actual target.
Connection fields
| Setting | Meaning | Practical guidance |
|---|---|---|
| Protocol | XCP on Ethernet UDP or TCP. | Use the transport supported by the ECU/A2L. TCP is connection-oriented; UDP may be used by lean or high-throughput implementations. |
| Host | ECU IP address or hostname. | Confirm PC and ECU are on a reachable network. Use loopback only with the demo ECU. |
| Port | XCP transport port. | Use the port declared by the target/A2L or supplied by the ECU integration team. |
| IPv6 | Use IPv6 transport addressing. | Enable only when the target network is configured for it. |
| Connect timeout | Connection timeout in seconds. | Increase cautiously on slow gateways; fix routing/firewall issues rather than masking them with a very long timeout. |
| Seed & Key DLL | Optional access-unlock library. | Provide only a trusted DLL supplied for the exact ECU/security configuration. It can be needed before calibration or programming. |
Acquisition mode
Choose POLLING or DAQ in the same Hardware dialog. The selection applies to the project/session and changes how INCAZ reads measurement variables.
POLLING: master-driven reads
- INCAZ cyclically reads selected variables at the configured poll rate.
- Works with XCP slaves that do not support dynamic DAQ.
- Simple to set up and useful for low-rate service/calibration signals.
- Fast signals can alias or consume bandwidth/ECU time; it is not a replacement for ECU-synchronous acquisition.
DAQ: slave-driven event rasters
- The ECU sends samples from its own event channels/task rasters.
- Each variable can be assigned to a DAQ event/raster in the Measure Table or scope assignment.
- Better for fast, periodic signals because sample timing follows ECU tasks.
- Requires compatible DAQ support, supported data types, and correctly declared/selected event channels.
DAQ event selection
INCAZ reads declared XCP events from the A2L when available. Assign a deliberate raster per variable. For unassigned variables, INCAZ selects a cyclic event close to 10 ms rather than blindly selecting the fastest event. This avoids accidentally assigning many signals to a microsecond task and flooding the PC or ECU.
DAQ timestamps
Enable slave DAQ timestamps only when the ECU provides a useful clock/timestamp configuration. For cyclic events, INCAZ keeps samples aligned to the nominal raster grid; packet arrival time alone can be distorted by network buffering and transport bursts.
Safe connection sequence for a real ECU
- Verify IP route, physical Ethernet, and target power before opening INCAZ.
- Import the matching A2L and load the correct project/database.
- Start with a small POLLING measurement set or a low-rate DAQ raster.
- Confirm live values are plausible before starting calibration or recording.
- Use access unlock only when authorised and required.
- Stop measurement cleanly before changing hardware configuration, target power, or flash state.