06-13-2025 04:25 AM
Hello, we are trying to establish a connection between LabVIEW and ETAS INCA using ASAM protocol and the MC ECU toolkit.
We are using the following code:
(Everything behind the ECU connect.vi is not relevant. There is just some testing of actually getting the Char names out of the A2l file, wich works, but the constant connection between INCA and LabVIEW fails.)
(First we give the path of the A2L, then open via XCP:TCP and then give IP-adress and port Number of the second testbench pc wich is running INCA)
(ECU Mode is set to 0)
The problem lies in the ECU connect .vi. There we get the error code -301096, which indicates that we are not getting a response from the ECU.
Normally, we have no problems accessing the ECU via INCA on this test bench. In addition, no error is reported in the previous blocks and the connection via XCP/TCP, IP address and port works. A received IP address is also displayed in Inca itself.
The connection is build in this order: Labview <--> INCA <--> ECU
Our connection is based solely on Ethernet and has no XCP/CAN interface.
The goal is to read and write the characteristics of the ECU in order to establish a repeatable test for the motor.
Does anyone have an idea how to resolve this error code?
06-13-2025 07:12 AM
To my knowledge, the NI ECUMC Toolkit is equivalent to the ETAS INCA for XCP communication with ECU. It is either you use INCA or ECUMC to connect to the ECU. I don't understand how you connect Labview <--> INCA <--> ECU, but use ECUMC in the LabVIEW code.