Description
When an AKD is a slave node on a fieldbus (for example an AKD is connected to an EtherCAT master)and WorkBench is simultaneously connected to an AKD via a service channel, then you have several options on how you would like the AKD to respond to commands from each of the channels.
When the fieldbus is operational the AKD uses the FBUS.PROTECTION parameter to allow the user to select how commands from WorkBench, or any other device sending commands to the drive through a service channel, should be handled. WorkBench can use either of two service channels: Telnet or ASCII SDO. Both service channels are affected identically by FBUS.PROTECTION.
The following table shows the available options. If the fieldbus is not connected or not started, then parameters executed through a service channel will not be blocked.
| Value | Description |
|---|---|
| 0 |
Motion and Tuning Commands Allowed - Commands that would interfere with motion are allowed. Gain and IO configuration changes are allowed. |
| 1 |
Block Motion but Allow Tuning Commands - Commands that would interfere with motion are blocked. Gain and I/O configuration changes are allowed. |
DRV.HELP will include the [Blocked] attribute to indicate whether a parameter is being blocked. For example, if FBUS.PROTECTION is 0 and the network is operational, the following help will be shown.
-->DRV.HELP DRV.EN
Help for: DRV.EN [ActionCommand] [Blocked]
-->
If you attempt to execute a blocked parameter the following error would display.
-->DRV.EN
Error: [0008] Command blocked.
All write or command functions of a parameter will be blocked by FBUS.PROTECTION. FBUS.PROTECTION will not block the read function of any parameter.
When the fieldbus is operational, FBUS.PROTECTION is always blocked, but can be edited through the fieldbus. This ensures that the protection level can only be modified by the fieldbus when it is in control.
If a parameter is blocked through telnet, it will be accessible through the fieldbus. For example, SDO's in the case of CANopen or EtherCAT.
Parameters Affected by FBUS.PROTECTION
This table shows how the blocked attribute affects the following parameters in each state of FBUS.PROTECTION. This table is true only if FBUS.STATE = 5 (operational).
| FBUS.PROTECTION | 0 - Block Nothing | 1 - Block Motion Commands |
|---|---|---|
| DRV.EN DRV.DIS |
[Blocked] | |
| FBUS.PROTECTION | [Blocked] | |
| DRV.OPMODE DRV.CMDSOURCE |
[Blocked] | |
| DRV.STOP DRV.CLRFAULTS |
[Blocked] |
General Information
|
Type |
R/W Parameter |
|
Units |
N/A |
|
Range |
0 to 1 |
|
Default Value |
0 |
|
Data Type |
Integer |
|
Start Version |
M_01-08-00-000 |
Variants Supported
| Variant | Supported |
|---|---|
| AKD Base | Yes |
| AKD with Position Indexer | Yes |
| AKD EtherCAT | Yes |
| AKD CANopen | Yes |
| AKD BASIC | No |
| AKD SynqNet | Yes* |
| AKD EtherNet/IP | Yes |
| AKD PROFINET | Yes |
| AKD Sercos® III | Yes |
| AKD-N | Yes |
| AKD-C | No |
*In SynqNet, a parameter may be available in the firmware but have no effect on the system. See SynqNet Supported Parameters.
Fieldbus Information
If your drive type is listed as supported but no index, address, or instance number is listed, then this parameter is accessible through WorkBench, but not over your fieldbus type.
| Index/Subindex | Object Start Version |
|---|---|
| 3498h/0 | M_01-08-00-000 |
| Fieldbus | Address | Attributes | Signed? |
|---|---|---|---|
|
PROFINET |
2871 | Byte | No |
| Sercos® III | 2 Octets |
| Instance | Data Size | Data Type |
|---|---|---|
| 872 | 1 Byte | Integer |
| Register Address | Is 64 bit? | Attributes | Signed? | Object Start Version |
|---|---|---|---|---|
|
1742 |
No | 8 bit | No | M_01-08-00-000 |
