Remedied from?
9400 HighLine SW V5.0
not eleiminated in 9400 StateLine SW ≤ V4.0
Eliminated function restriction
Due to a function restriction the drive automatically restarted although auto-start was inhibited after connecting to the mains (C00142=0). The drive started without a positive edge on the signal for the controller enable if the controller had already been enabled via controller enable via terminal, controller enable via data bus etc. and if the drive was in the C0183 = 141 ('Device is ready to start') state (e. g. after connecting to the mains) and a code was changed in this situation requiring a controller inhibit (e.g. cycle C2536) and there already was an active setpoint source. After revising the Firmware the drive does not start after changing a code that requires a controller inhibit (e. g. cycle C2536) until a new positive edge on the controller inhibit is set if the 'Auto-start after connecting to mains inhibited' setting (C00142=0) has been selected.
Which products are affected?
9400 HighLine SW ≤ V4.1
9400 StateLine SW ≤ V4.0
What happens?
After a parameter change, the drive restarts although the restart inhibit (C0142 = 0) is activated.
When does the problem occur?
The problem occurs when the drive is operated with activated restart inhibit (C0142 = 0). In this case, the drive starts without positive edge at the controller enable signal when
1. the controller has been enabled via the controller enable terminal, controller enable via data bus, etc. and
2. the drive is in the status C0183 = 141 (device is ready to start) (e. g. after power-on) and
3. in this situation, a code is changed which requires a controller inhibit (e. g. cycle C2536) and
4. a setpoint source has already been switched active.
In this status (C0183 = 141, device is ready to start), the new code is accepted without any further queries. After the value has been accepted, the drive directly changes to the status C0183 = 90 (device is switched on) and, if necessary, restarts with the selected setpoint.
Possible diagnostics?
The behaviour only occurs when the restart inhibit is activated (C0142 = 0). When the drive is in the status C0183 = 141 (device is ready to start) and a code is written that requires controller inhibit for being written, the drive changes to the status C0183 = 90 (device is switched on).
Short-term measures/recommendations?
Always set the controller inhibit (e.g. via the controller enable terminal, controller enable via data bus, etc.) when editing codes the values of which can only be changed when the controller is inhibited. From the attribute tables of the corresponding parameter lists you can see if controller inhibit is necessary to change the value of a certain code.
Evaluation:
With firmware V04, the auto-restart after power-on (C00142) function has been default-set to INHIBITED (C142 = 0). Experience has shown that this function is only used for a few applications.
Codes with write access only when the controller is inhibited (e.g. codes of the system block LS_DriveInterface defining the axis measuring system) are, of course, not changed when the machine is running. This means that the described behaviour will practically only occur during the commissioning phases and will thus be detected immediately.
When codes with write access only when the controller is inhibited are adapted via a data bus system (SDO access), the drive must have been set to controller inhibit before.
