About "I/O Node Device Name - Toshiba DeviceNet nv Series Instruction Manual

4.7.2 About "I/O node device name"

Difference between "DN611A-AS" (with controller support) and "DN611A" (without controller
1
support)
When "DN611A-AS" is used, you can use a function to support registration / execution on the controller.
When "DN611A" is used, it is necessary to set and execute from the user program of the controller.
"DN611A-AS" (with controller support):
2
 I / O data access
You can use MREAD/MWRITE command (or function block).
In addition, DeviceNet I / O data can be assigned to batch I / O and data can be accessed using user
variables (variable name or IQ register:% MW11. ****).
You can also register network variables.
The following is an example of the procedure for registering network variables.
(1) Register DN611B as "DN611A-AS" in system station
(2) Register DN_X module in other station as a representative of whole slave devices.
(3) Register DevicenetLAN to Network configuration.
(4) Register DN611A-AS and DN_X in the DevicenetLAN.
(5) Register " DN611A-AS send block'' and "DN_X send block" in DevicenetLAN scan memory.
The head address of DN611A-AS send block is "128".
The head address of DN_X send block is "0".
(6) Register network variable in each send block.
 DN611B also automatically changes to RUN if the controller mode changes from HALT to RUN.
The controller firmware issues a RUN request to DN611B.
However, the device parameters of DN611B must be set with the DeviceNet Configuration Tool (ACM).
If the DeviceNet local node parameter / slave device parameter is not set in DN611B, DN611B will not be
in RUN mode even if the controller issues a RUN request.
"DN611A" (without controller support)
3
 I / O data access
You can use MREAD/MWRITE command (or function block).
I / O data in DeviceNet cannot be handled as a user variable because it cannot be assigned to batch I / O.
 DN611B does not automatically change to RUN even if the controller mode changes from HALT to RUN.
Since the controller firmware does not take any action on DN611B, it is necessary to set the own node
parameter / slave device parameter from the controller user program and issue a RUN request.
Unified Controller nv Series DeviceNet Module DN611B Instruction Manual
4.7 Setting with Engineering Tool
89