Hi,
After too long, we are upgrading from Codesys SP6 to SP17
(3.5.6.3 -->3.5.17.1)
and we encounter some problems with our existing project.
We are using an Advantech UNO-2484G controller
One of our ethercat devices is an ACS controller (Control 2 axes).
When we use it with the default telegram settings it works fine.
but, when adding additional data to the telegram - for expample reading the position error, we lose control over the axes (can't enable motor)
after some investigation we found that after the change in the telegram there is an address mismatch between the settings on the device and the setting on the axis.
On the old version, we didn’t have the IO mapping window for every axis device (in the picture).
Picture1-1 -(Before additional data on telegram)
On the new version, when we add additional data to the PDO list, the addresses change only on that window. The device IO mapping window do not change
Picture2-1 - (Additional data added)
Picture2-2 - (Adresses change on axis)
Picture2-3 - (address didn’t change on device)
ACS engineers don't know this issue, and dont have any updated XML
We dont see that issue on other devices (for example ControlTechnique drives)
Hi,
After too long, we are upgrading from Codesys SP6 to SP17
(3.5.6.3 -->3.5.17.1)
and we encounter some problems with our existing project.
We are using an Advantech UNO-2484G controller
One of our ethercat devices is an ACS controller (Control 2 axes).
When we use it with the default telegram settings it works fine.
but, when adding additional data to the telegram - for expample reading the position error, we lose control over the axes (can't enable motor)
after some investigation we found that after the change in the telegram there is an address mismatch between the settings on the device and the setting on the axis.
On the old version, we didn’t have the IO mapping window for every axis device (in the picture).
Picture1-1 -(Before additional data on telegram)
On the new version, when we add additional data to the PDO list, the addresses change only on that window. The device IO mapping window do not change
Picture2-1 - (Additional data added)
Picture2-2 - (Adresses change on axis)
Picture2-3 - (address didn’t change on device)
ACS engineers don't know this issue, and dont have any updated XML
We dont see that issue on other devices (for example ControlTechnique drives)
Did anyone encountered any similar issue?
Thanks!
Elad
Last edit: Elad_Amira 2021-10-14