MATLAB: SImulink Real-Time EtherCAT Async SOE Error code EC_E_ERROR+0x104 ERROR SoE: Response IDN not identical with the requested IDN

0x104asyncethercatslrtsoe

I have multiple EtherCAT Async SOE blocks downloading data, each to a different IDN, but these blocks are all enabled at the same time. In the model the enable signal for the blocks was held high (on) for some length of time, so the blocks continued to repeat sending data. After successfully sending the data multiple times, there came a point where an error was thrown

Error code EC_E_ERROR+0x104 ERROR SoE: Response IDN not identical with the requested IDN

When I use only one download block at a time, they don't seem to get this error even when the enable is held high for many sample times. Is it is intended that multiple Async blocks are able to execute concurrently, or whether they should be managed to execute sequentially?

Best Answer

If you are exchanging data through several different IDNs with the same EtherCAT device, we would recommend against doing that concurrently. Each download request needs to be processed by the device, so doing multiple at once may lead to issues. If you are talking to different devices on the same network on the other hand, that should not be an issue. Overall, we suggest avoiding the issue by not leaving the enable signals on. Instead, you can send pulses of enable signals only when the data actually needs to be updated.

Related Solutions

MATLAB: SLRT EtherCAT Async SOE download behavior edge triggered or continuous send of data

The EtherCAT Async SOE download block will keep sending data as long as the enable signal is kept on. If you would like to send data just once then you can enable it with a single sample time pulse. It does take ~3 cycles for the data to be sent out but you only need to send one enable pulse to initiate the send process.

MATLAB: Do I receive an error when simulating a model with a Stateflow chart inside a triggered subsystem in R2015b

The issue was seen in R2015b because, as the error message says, we need to insert a hidden buffer if driven by Stateflow Charts. In the case where the input is not a bus, the buffer insertion happens silently and Simulink takes care of everything. However, when the input is a virtual bus, Simulink is unable to insert a buffer (because we need to carry out Bus Expansion, and the place where we do buffer insertion is too late). Therefore, we error out letting the user know that a buffer was needed here but Simulink could not insert it, so please insert one to remove the error.
Starting from R2016a, Simulink is able to insert buffers even in cases of virtual buses.

Best Answer

Related Solutions

MATLAB: SLRT EtherCAT Async SOE download behavior edge triggered or continuous send of data

MATLAB: Do I receive an error when simulating a model with a Stateflow chart inside a triggered subsystem in R2015b

Related Question