Which products are affected?
EPM-T110 (CAN Gateway V1.2)
EPM-T111 (CAN Gateway ECO V1.2)
What happens?
The process data identifiers of the CAN gateway do not depend on the node address set.
When does the problem occur?
The identifiers of the process data objects are calculated automatically by the CAN gateway dependent on the node address set. However, this automatic calculation is only executed when the CAN gateway has been switched on for the first time or when the default setting (I2100h=1) has been loaded. If the node address is changed again after the CAN gateway has been switched off the identifier is not recalculated. The identifier set before is accepted instead.
The compact modules (EPM-T830, EPM-T831, EPM-T832 and EPM-T833) are not affected by this function restriction.
Possible diagnostics?
Use the GDC software to check the identifiers set under the indices I1400hex and I1800hex of the CAN gateway.
Short-term measures/recommendations?
- Set the node address required before the CAN gateway is switched on for the first time.
- Alternative:
- Load the default setting of the CAN gateway (I2100 hex = 1) after the node address has been set.
Evaluation:
When the node address of the CAN gateway is set the identifiers of the process data objects PDO1 and PDO2 are preset in such a way that data can be exchanged with the process data objects CAN3 and CAN2 of a Lenze drive controller. Regarding this, the node address of the CAN gateway must be by 1 larger compared to the node address of the drive controller. This means a communication between drive controller and CAN gateway can be established without parameterising the CAN gateway.
Due to this function restriction the CAN gateway must not be switched on before the node address has been set since otherwise it is necessary to parameterise the CAN gateway. In most cases the modular I/O system is parameterised by a higher-level control.
