Altivar 61 - error

Profiles
Functional profiles supported by the Altivar 61
I/O profile
Using the I/O profile simplifies PLC programming.
The I/O profile is commonly used for control of the terminals and display terminal. It is also supported by the Altivar 61 for network control.
The drive starts up as soon as the run command is sent.
The 16 bits of the control word can be assigned to a function or a terminal input.
This profile can be developed for simultaneous control of the drive via:
• The terminals
• The Modbus control word
• The CANopen control word
• The network card control word
• The "Controller Inside" control word
The I/O profile is supported by the drive itself and therefore in turn by all the communication ports (integrated Modbus, CANopen and the
Ethernet, Fipio, ModbusPlus, Modbus, Uni-Telway, Profibus DP, DeviceNet, and INTERBUS communication cards).
DSP402 profile
The drive only starts up following a command sequence.
The control word is standardized.
5 bits of the control word (bits 11 to 15) can be assigned to a function or a terminal input.
The DSP402 profile is supported by the drive itself and therefore in turn by all the communication ports (integrated Modbus, CANopen and
the Ethernet, Fipio, ModbusPlus, Modbus, Uni-Telway, Profibus DP, DeviceNet, and INTERBUS communication cards).
The Altivar 61 supports the DSP402 profile’s "Velocity mode".
In DSP402 profile, there are 2 modes that are specific to the Altivar 61 and characterize command and reference management
(see section “Command/reference switching”, page 33):
• Separate mode [Separate] (SEP)
• Not separate mode [Not separ.] (SIM)
ODVA (Open DeviceNet Vendor Association) profile
The drive starts up as soon as the run command is sent.
The control word is standardized.
The ODVA profile is supported by the DeviceNet communication card.
11