Transmission type "Asynchronous - device-profile-specific" does not work for EPM-S110

Corrected from:
EPM-S110 V1D.32

Response of the new version:
On each value change, a telegram is asynchronously sent on the PDO specified according to CANopen.
 
What happens?
A PDO is sent on an incorrect CAN identifer (not the identifier specified according to CANopen).
 
When does this behaviour occur?
The behaviour occurs if a second send PDO is required due to the station configuration (e.g. 9 DI modules) and
for these inputs, 255 is set as transmission type for the PDO (Asynchronous - device-profile-specific). 
 
Which products are affected?
All EPM-S110 of version < 1D.32
 
 

URL for linking this AKB article: https://www.lenze.com/en-de/go/akb/201400288/1/
Kontaktformular