Codes
Communication−relevant Lenze codes
14
l
131
EDSMF2178IB EN 3.0
C1857/C2357:
Monitoring time
Code Subcode Index
Possible settings
Data type
Lenze Selection
C1857
/1: CAN−IN1
/2: CAN−IN2
/3: CAN−IN3
/4: BUS−OFF monitoring time
/5: AIF monitoring time
/6: Sync Rx monitoring time
22718 =
0x58BE
/1 ... /5:
3000 ms
/6: 0 ms
0 [1 ms] 65535 FIX32
C2357 22218 =
0x56CA
) Note!
ƒ The monitoring time starts with the arrival of the first telegram.
ƒ C1857/x = 0: Monitoring deactivated.
ƒ C2357/x = 0: Monitoring deactivated.
CAN−IN1 ... 3 (C1857/1 ... 3, C2357/1 ... 3)
The "monitoring time" describes the period of time in which new process input data must
arrive with the CAN−IN1 ... 3 identifiers. If the time entered is exceeded, it is possible to set
a corresponding reaction under code C1882/C2382.
BUS−OFF (C1857/4, C2357/4)
Even if the node changes to the state BUS−OFF, it is possible to set a time (in ms) in which
a reaction can take place. A monitoring response can be set under code C1882/C2382.
AIF monitoring time (C1857/5, C2357/5)
Time during boot−up for detecting a basic device. If no basic device is detected, an
emergency telegram (^ 87) will be sent on the CAN bus after this time.
Sync monitoring time (C1857/6, C2357/6)
Monitoring time for a received, cyclic sync telegram.
Relation to CANopen
ƒ The object I−1006 (Communication Cycle Period) has a direct influence on the
subcodes C1857/6 or C2357/6. A new value in the code deletes bit 30 of the object
I−1005 (COB−ID SYNC message).
ƒ The objects I−1400/5 ... I−1402/5 (TPDO Event Timer) have a direct influence on the
subcodes C1857/1 ... 3 or C2357/1 ... 3. Newly entered values in the objects
I−1400/5 ... I−1402/5 are also transferred to the subcodes C1857/1 ... 3 or
C2357/1 ... 3.
To Next Page
Loading...
