09-22-2022 06:31 AM
I have a third party EtherCAT slave that support the assignment of Sync Manager at runtime.
In the EtherCAT standard the object 1C13h establishes the PDO assignment of Sync Manager 3.
As for the object relating to the Sync Manager 3, it allows you to assign up to a maximum of 3 PDO Mapping objects.
The first Sync Manager 3 is assigned to PDO mapping 1A02h by the SM token associated with the TxPDO selected in the ESI xml file.
I can read object 1C13h sub 1 and the value is correctly 1A02h.
I want to assign the second Sync Manager 3 to the PDO Mapping object 1AF0h (the 241-th Transmit PDO Mapping).
The 1AF0h transmit PDO mapping is defined in the ESI xml file and I am able to verify the mapping by reading the object1 AF0h from sub 0 to sub 3.
To assign the second Sync Manager 3 to the object 1AF0h, in PreOP, I write the value 1AF0h to the object 1C13h sub 2.
Unfortunately the writing fails en return the Error -2147138467, possible reason(s):
An SDO request sent by the master has been aborted by the slave device due to incorrect initial commands or incorrect PDO selection. Check the configuration of the slave device on the device's property page and ensure that the configuration is correct.
I have check that PDO and SDO objects are correct.
I missed something in the procedure?
Is the assignment of Sync Manager at runtime supported by LabVIEW?
11-19-2024 06:57 AM
I have the same problem. Any news on that?