Communication Errors ASCET <-> ES1000.
Error messages from the HW driver at start / stop of the experiment.
FAQ
Please select your topic:
ASCET-RP FAQ
Operation System: Configuration Rules for ES1000 Projects
Macro definition for ASCET Module in INTECRIO
An INTECRIO project contains ASCET modules that can be run in an ASCET-RP Online Experiment.
The INTECRIO build process for a project of this kind ends in an error message that looks similar to the one below:
GNU_GCC: `TRUE' undeclared (first use in this function)
Using measure points in an ASCET ETK-Bypass Project with Robert Bosch Diesel System ECUs
- Some values are not written correctly into the ETK-bypass simulation of a Robert Bosch Diesel ECU (e.g., EDC15/EDC16) in access mode DISTAB or the ECU resets at the start of the bypass.
- Reading into INCA via ETK is possible.
- All values have the memory space EXTERN and will likely have the extension “_mp” in their name which designates them as measuring points.
Different Checksums for ETK-Bypass Projects
INCA calculates different checksums for ETK-bypass projects, evern though not data was changed in the ECU.
Trigger Segment Conflicts
The trigger segment definition in the A2L-file may differ from the current trigger segment in the ETK memory. If this is the case, the triggering ETK-bypass and the measurement will not work and no signals are received from the RCU.
Possible loss of data during type conversion for hardware interface
If physical values are used in ASCET-RP, a type conversion is necessary before these values can be written to a hardware interface (CAN, LIN or ETK). In this case an overflow of the values from ASCET-RP cannot be avoided.
