Rockwell Automation AutoMax ControlNet Communication Interface Module User Manual
Rockwell Automation
AutoMax ControlNet
Communication Interface
Module
(Cat. No. O-58820-2)
Major Rev. 2
User Manual
Page 2 AutoMax ControlNet Module
Important User Information
Solid state equipment has operational characteristics differing from those
of electromechanical equipment. “Safety Guidelines for the Application,
Installation and Maintenance of Solid State Controls” (Publication SGI-
1.1) describes some important differences between solid state equipment
and hard–wired electromechanical devices. Because of this difference,
and also because of the wide variety of uses for solid state equipment, all
persons responsible for applying this equipment must satisfy themselves
that each intended application of this equipment is acceptable.
In no event will Rockwell Automation be responsible or liable for
indirect or consequential damages resulting from the use or application
of this equipment.
The examples and diagrams in this manual are included solely for
illustrative purposes. Because of the many variables and requirements
associated with any particular installation, Rockwell Automation cannot
assume responsibility or liability for actual use based on the examples
and diagrams.
Rockwell Automation assumes no patent liability with respect to use of
information, circuits, equipment, or software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without
written permission of Rockwell Automation is prohibited.
Throughout this manual we use notes to make you aware of safety
considerations.
Identifies information about practices or circumstances that can lead to
personal injury or death, property damage, or economic loss.
Attentions help you:
• identify a hazard
• avoid the hazard
• recognize the consequences
Important: Identifies information that is especially important for
successful application and understanding of the product.
Microsoft is a registered trademark of Microsoft Corporation.
Windows, Windows 95 and Windows NT are trademarks of Microsoft Corporation.
ControlLogix and Data Highway Plus are trademarks of the Allen-Bradley Company, Inc.
Publication number DSMBCN-UM001B-EN-P February 2003
INTRODUCTION 9
Who Should Use This Manual? 9
Purpose of this Manual 9
Conventions Used in this Manual 9
Getting Support 10
Reference Documents 10
Requirements 10
MBCN AUTOMAX CONTROLNET MODULE 11
Overview 11
Module Overview 11
Hardware Features 13
7-Segment Display 13
OK LED 14
MAC ID Thumbwheels 14
Serial Configuration Port 14
NAP Port 15
ControlNet Connectors 15
Network Status LEDs 15
7-Segment LED Codes 16
Communication Error 18
INSTALLATION 19
Prevent Electrostatic Discharge 19
Installation and Wiring 20
Connecting to the Network 21
Troubleshooting Wiring Problems 21
QUICK START 22
PROGRAMMING THE MBCN 23
Overview 23
AutoMax ControlNet Module Page 5
Memory Overview 23
Configuring Scheduled Connections 24
Creating a Configuration 24
Configuring 1771 I/O 25
Configuring Flex I/O 26
Configuring Scheduled Data with Another MBCN 27
Configuring Scheduled Data with a PLC-5 28
Configuring Scheduled Data with a ControlLogix Processor 29
Setting the Network Properties 32
Downloading the Configuration 32
Putting the MBCN in Run Mode 32
Accessing I/O Data 32
Application Example 33
Multicast Connections 34
MONITORING MODULE OPERATION 35
Status of Each Connection 35
Operating Status 38
Summary of Registers for Monitoring Operation 39
UNSCHEDULED MESSAGING 41
Register Organization 41
AutoMax Application Programming 42
GATEWAY_CMD_OK@ Status Codes 51
Extended Status (EXT_STS) Codes for Command 0F 53
Commands from Remote Nodes 54
Differences from the M/N 57C442 Module Interface 56
VIEWING NETWORK PARAMETERS 57
Current Network Parameters 57
Pending Network Parameters 58
STATE REGISTERS 60
Module State 60
NAM State 60
Keeper State 61
Flash State 62
Serial CONFIG Port State 62
Channel State 63
DIAGNOSTIC COUNTERS 64
Publication number DSMBCN-UM001B-EN-P February 2003
Page 6 AutoMax ControlNet Module
Standard ControlNet Counters 64
Module Specific Counters 65
The Error Log 66
ACTIVE NODE LIST 67
ID AREA 68
Vendor ID 68
Device Type 68
Product Code 68
Major Revision 68
Minor Revision 68
Status 68
Serial Number 69
Product Name Length 69
Product Name 69
Current Address 70
MAC ID Switches 70
Summary of ID Area Locations 70
FIRMWARE VERSION INFORMATION 71
USING THE HOST WATCHDOG 72
UPDATING THE FIRMWARE 73
CONVERTING FROM MAJOR REVISION 1 TO 2 76
If you have access to the Reliance MBCN hardware 76
If you have an offline configuration file (*.xc) 76
SPECIFICATIONS 78
SUPPORT 79
Publication number DSMBCN-UM001B-EN-P February 2003
AutoMax ControlNet Module Page 7
Table of Figures
Figure 1 Serial Cable Wiring.......................................................................................................................14
Figure 2 LED Status Table..........................................................................................................................16
Figure 3 7-Segment LED Codes .................................................................................................................17
Figure 4 Memory Overview........................................................................................................................24
Figure 5 Connection Status Values .............................................................................................................38
Figure 6 Scanner State Table.......................................................................................................................39
Figure 7 – Adapter (Scheduled Produced Data) State Table.......................................................................39
Figure 8 Summary of Monitor Registers.....................................................................................................40
Figure 9 Summary of Unscheduled Message Registers..............................................................................41
Figure 10 Control and Status Registers.......................................................................................................42
Figure 11 Command Table..........................................................................................................................46
Figure 12 GATEWAY_CMD_OK Status Table.........................................................................................51
Figure 13 Local and Remote Status Table ..................................................................................................52
Figure 14 Extended Status Error Codes Table ............................................................................................54
Figure 15 Unsolicited PLC-5 Commands ...................................................................................................54
Figure 16 Unsolicited Basic Command Set Commands .............................................................................55
Figure 17 Current Network Parameters.......................................................................................................58
Figure 18 Pending Network Parameters......................................................................................................59
Figure 19 Module State Table.....................................................................................................................60
Figure 20 NAM State Table........................................................................................................................61
Figure 21 Keeper State Table......................................................................................................................62
Figure 22 Flash Memory State Table..........................................................................................................62
Figure 23 Serial Config State ......................................................................................................................62
Figure 24 Channel State Table....................................................................................................................63
Figure 25 Standard ControlNet Diagnostic Counters..................................................................................65
Figure 26 Module-Specific Diagnostic Counters........................................................................................66
Figure 27 Active Node Table......................................................................................................................67
Figure 28 Device Status Table ....................................................................................................................68
Figure 29 Device Status, Bits 4-7................................................................................................................69
Figure 30 ID Locations Table .....................................................................................................................70
Figure 31 Firmware Versions Table............................................................................................................71
Publication number DSMBCN-UM001B-EN-P February 2003
This introduction covers the following topics:
• who should use this manual
• the purpose of the manual
• contents of the manual
• conventions used in the manual
• getting support
Who Should Use This Manual?
Use this manual if you are responsible for designing, installing,
programming or troubleshooting systems that are based on AutoMax
Control using the MBCN ControlNet module (O-58820-2) with major
revision 2 firmware.
You should have a basic understanding of AutoMax products. You
should understand Allen Bradley PLC-5s and ControlLogix PLCs and be
familiar with using ControlNet I/O modules on the ControlNet network.
Introduction
Purpose of this Manual
This manual shows you how to install and use the MBCN ControlNet
module. It describes the procedures to install, configure, and operate the
MBCN ControlNet module.
Conventions Used in this Manual
The following conventions are used throughout this manual:
• bulleted lists, such as this one, provide information, not procedural
steps
• numbered lists provide sequential steps
• bold type is used for emphasis
courier font is used for text you should type
•
• hexadecimal numbers are shown with a trailing ‘h’, for example,
1234h
• titles for menu items, dialog boxes, etc. in software are shown in
italics
• addresses that refer to a single byte within an AutoMax register are
shown with a trailing ‘L’ or ‘H’ to indicate the low or high byte of
the register.
• T=>O means ControlNet target-to-originator; O=>T means
originator-to-target. The originator is the node that opens the
connection to the target.
• RSNetWorx means RSNetWorx for ControlNet
Page 10 AutoMax ControlNet Module
Getting Support
Refer to page 79 for information on how to obtain support for the MBCN
module.
For support on the AutoMax processor or programming software, contact
Rockwell Automation or your local distributor.
Reference Documents
For information on using RSNetWorx, refer to:
• RSNetworx ControlNet Getting Results, Publication Number 9399CNETGR, Catalog number 9357-CNETL3
For information on ControlNet, refer to one of the following:
• ControlNet Specification, available from ControlNet International,
www.controlnet.org
• IEEE 518 Guide for the Installation of Electrical Equipment to
Minimize Electrical Noise Input to Controllers
• ControlNet user manual, publication 1786-2.12
, approximate cost US$350
Requirements
RSNetWork for ControlNet version 3.21 and above includes support for
configuring the MBCN.
MBCN firmware version 1.10 and above requires RSNetWorx for
ControlNet for configuration.
The MBCN must be running firmware version 1.10 or above to be used
with ControlFlash.
To use the connection status information, you need RSNetWork for
ControlNet version 4.11 or above and firmware version 2.1 or above on
the MBCN.
Refer to page 73 for information on updating the firmware in the MBCN.
Refer to page 76 for information on converting a revision 1 MBCN to a
revision 2 MBCN in RSNetWorx for ControlNet.
Publication number DSMBCN-UM001B-EN-P February 2003
Overview
Module Overview
AutoMax ControlNet Module Page 11
MBCN AutoMax ControlNet Module
This chapter contains the following information:
• module overview
• a summary of hardware features
• a description of how the hardware works
The MBCN module makes it possible for an application running in an
AutoMax Controller to communicate with and control ControlNet I/O
devices. The MBCN can also exchange data with other processors over
the ControlNet network using scheduled produced and consumed data.
The MBCN uses the standard AutoMax memory-mapped interface to the
host processor.
All I/O data is mapped into AutoMax registers 16384-32767. You can
select the register assignment for the data for each connection or have the
register assignment created automatically when you create the I/O
configuration.
The module:
• supports up to 127 scheduled connections, up to 480 words per
connection
• supports a maximum of 16 Kbytes total input data
• maps input data into AutoMax Processor registers 16384-24575
• supports a maximum of 16 Kbytes total output data
• maps output data into AutoMax Processor registers 24576-32767
• provides global status on all originator to target (O=>T) connections
and global status on all target to originator (T=>O) connections
• provides status on each connection, in AutoMax registers 1536215614, two 16-bit words per connection. You map the location of the
status information for a connection using RSNetWorx. This requires
major revision 2 of the MBCN firmware and RSNetWorx for
ControlNet 4.11 or later. Major revision 1 of the MBCN firmware
does not support status on individual connections
You use RSNetWorx for ControlNet to configure the I/O devices being
scanned and all scheduled produced and consumed connections.
The MBCN maintains standard ControlNet diagnostic counters, as well
as additional diagnostic counters, to monitor MBCN operation and to
diagnose problems.
The MBCN maintains an active node list.
Publication number DSMBCN-UM001B-EN-P February 2003
Page 12 AutoMax ControlNet Module
The MBCN can send unscheduled messages to other nodes on the
network, and receive and respond to unscheduled messages from other
nodes, using PLC-5 PCCC commands. The MBCN emulates the
AutoMax interface on the M/N 57C442 Data Highway Plus module.
Publication number DSMBCN-UM001B-EN-P February 2003
Hardware Features
AutoMax ControlNet Module Page 13
The main hardware features of the MBCN are:
• 7-segment display
MBCN
O-58820
Fault
Code
MAC ID
OK
• OK LED
• switches to set the MBCN’s ControlNet address
• serial config port for updating the MBCN firmware
• ControlNet NAP port
• ControlNet BNC connectors
• network status LEDs
10
These are described in detail in the following sections
1
Config NAP
A
COM
B
COM
7-Segment Display
The MBCN has a 7-segment LED to indicate status. Refer to page 16 for
a summary of 7-segment display codes.
Publication number DSMBCN-UM001B-EN-P February 2003
Page 14 AutoMax ControlNet Module
6
7
8
9
OK LED
The MBCN contains a hardware watchdog that monitors operation of the
MBCN hardware and software. The hardware watchdog times out only
when there is a catastrophic hardware or firmware failure on the MBCN.
The green OK LED is on when the hardware watchdog is OK and is off
if the watchdog times out.
NOTE: The hardware watchdog is NOT the same as the host watchdog.
See page 72 for information on using the host watchdog.
MAC ID Thumbwheels
Use the two thumbwheels labelled MAC ID to set the MBCN’s address
on ControlNet. The upper thumbwheel sets the most significant digit;
the lower thumbwheel sets the least significant digit.
To maximize network efficiency and reduce network overhead, you
usually assign ControlNet addresses consecutively, starting at 1.
NOTE: 0 is not a valid address.
The MBCN reads the thumbwheels only at power-up. You must power
down and power back up for changes in the thumbwheel settings to be
recognized.
Serial Configuration Port
The thumbwheel switches must be positioned in the center of the detent.
You can verify the switch settings by displaying register 32.
The serial CONFIG port on the front of the MBCN can be used to:
• update the firmware on the MBCN
• update the FPGA (field programmable gate array) configuration on
the MBCN
Note: you normally update both using ControlFlash over ControlNet.
The serial cable for a standard PC COM port must have lines 2 and 3
swapped. It does not require any handshaking. Pins 2 and 3 are wired
the same as a PC 9-pin COM port. A cable is provided with the MBCN
when shipped in the original packaging.
1
2
3
4
5
1
6
2
7
3
8
4
9
5
Figure 1 Serial Cable Wiring
Connect to the serial port using any communication software. For
example, you can use the HyperTerminal program supplied with
Windows. The MBCN serial port supports a baud rate of 57.6 Kbaud,
with no parity, 8 data bits and 1 stop bit.
Refer to page 73 for information on updating MBCN firmware.
Publication number DSMBCN-UM001B-EN-P February 2003
NAP Port
AutoMax ControlNet Module Page 15
The MBCN has a standard ControlNet NAP port to allow a transient
node to connect to the ControlNet network.
Use the NAP port on the MBCN if you want to attach a transient node to
the network and you do not want to rewire the network. Do not connect
any node to the network using both the NAP port and a coax path at the
same time. The following figure shows how to correctly connect a
transient node.
ControlNet Connectors
Network Status LEDs
NAP Connection 1
You can also use the NAP port on the MBCN to attach the MBCN to an
existing network, by connecting to the NAP port on a node on the
existing network.
The NAP cable has 8 conductors and a shield, with RJ-45 connectors at
each end. The cables are reversed from one end of the cable to the other,
so that 1->8, 2->7, etc. Maximum cable length is 10 m.
Connect the MBCN to the ControlNet network using the standard
ControlNet BNC connectors.
There is one network status (COM) LED for each network connector.
The network status LEDs display the following states, using the priority
scheme shown. If more than one condition exists, the LEDs display the
state with the highest priority.
When using redundant cabling, both LEDs should be green. One will be
brighter; this is the active channel.
Publication number DSMBCN-UM001B-EN-P February 2003
Page 16 AutoMax ControlNet Module
The LEDs do not reflect the state of the NAP port. If you connect the
MBCN to the network via the NAP port, the two network status LEDs
flash red together.
Priority State How to view Cause
1
(highest)
2 Both steady
3 Alternating
4 Alternating
5 Steady off Channel disabled or channel
6 Flashing
7 Flashing
8 Flashing
9
(lowest)
Both steady
off
red
red/green
red/off
red/green
red/off
green/off
Steady green
Viewed
together
Viewed
Independently
Reset or no power
Failed link interface
Fatal error on MBCN
Self test
Bad node configuration, such
as duplicate address
not supported
Invalid link configuration,
such as address > UMAX
Link fault or no MAC frames
received
Temporary channel error, or
listen only
Normal operation
Figure 2 LED Status Table
7-Segment LED Codes
Value Meaning
1 NAM not attached. There are no other nodes
on the network.
2 Keeper faulted master. The MBCN schedule
needs to be updated using RSNetWorx.
3 Keeper faulted backup. The MBCN schedule
needs to be updated using RSNetWorx.
4 Keeper change
5 Keeper faulted change
6 Keeper temporary state
b Inactive. The MBCN is online but has no
scheduled connections and is not sending or
receiving messages.
Publication number DSMBCN-UM001B-EN-P February 2003
AutoMax ControlNet Module Page 17
Value Meaning
C Communication error
d One or more connections requires a schedule.
Use RSNetWorx to schedule all connections.
E Bad thumbwheel value
P Scanning in program mode
U Firmware on the MBCN is being updated
H Hardware on the MBCN is being updated.
r Module requires reset, usually after an update.
Cycle power to the rack that contains the
MBCN.
.0 Module checksum failure
.1 Local RAM data failure
.2 Local RAM address failure
.3 Local RAM FF fill failure
.4 Local RAM 00 fill failure
.5 Code copy failure
.6 Shared RAM failure
.7 Shared RAM address failure
.8 Shared RAM FF fill failure
.9 Shared RAM 00 fill failure
.A Module startup failure
.b Bootup shell activate prompt
.C Board reset failure
.d AutoMax watchdog failure
.E Power fail
.F Module hardware failure (jabber inhibit, host
watchdog). Cycle power to see if the problem
disappears. If it does not, replace the MBCN.
Off Scanning OK in run mode
Figure 3 7-Segment LED Codes
LED codes that start with a dot are hardware failures and usually indicate
that the MBCN has suffered a fatal hardware or firmware failure.
Contact technical support.
Publication number DSMBCN-UM001B-EN-P February 2003
Page 18 AutoMax ControlNet Module
Communication Error
The following are common causes for communication error ( C ) to be
displayed on the 7-segment LED:
• The MBCN couldn’t open one or more connections. Look at the
status for each connection in RSNetWorx or on the MBCN
• The MBCN has refused a connection or has returned an error to an
unscheduled message. Look at the status for each connection using
RSNetWorx or the status registers on the MBCN or look at the status
of the connections on other nodes that have connections to the
MBCN.
• The MBCN is sending unscheduled messages that are failing.
Publication number DSMBCN-UM001B-EN-P February 2003
Prevent Electrostatic Discharge
The MBCN is sensitive to electrostatic discharge.
ATTENTION: Electrostatic discharge can damage integrated circuits
or semiconductors if you touch backplane connector pins. Follow these
guidelines when you handle the module:
• Touch a grounded object to discharge static potential
AutoMax ControlNet Module Page 19
Installation
• Wear an approved wrist-strap grounding device
• Do not touch the backplane connector or connector pins
• Do not touch circuit components inside the module
• If available, use a static-safe work station
• When not in use, keep the module in its static-shield packaging
This chapter contains the information necessary to:
• install the MBCN in the AutoMax rack
• connect the MBCN to the ControlNet network
• use the MBCN serial port
• understand the MBCN LEDs
Publication number DSMBCN-UM001B-EN-P February 2003
Page 20 AutoMax ControlNet Module
Installation and Wiring
The user is responsible for conforming to all applicable local, national,
and international codes. Wiring practices, grounding, disconnects, and
over-current protection are of particular importance. Failure to observe
this precaution could result in severe bodily injury or loss of life.
To reduce the possibility of electrical noise interfering with the operation
of the control system, exercise care when installing the wiring from the
control system to the external devices. For detailed recommendations,
refer to IEEE 518.
Step 1. Stop any application tasks that may be running.
This equipment is at line voltage when AC power is connected.
Disconnect and lock out all ungrounded conductors of the AC power
line. Failure to observe this precaution could result in severe bodily
injury or loss of life.
DANGER
DANGER
WARNING
Inserting or removing a module may result in unexpected machine
motion. Power to the machine should be turned off before inserting or
removing a module. Failure to observe these precautions could result in
bodily injury.
Step 2. Turn off all power to the rack. All power to the rack as well as
all power leading to the rack should be off.
CAUTION
This module contains static sensitive components. Careless handling
can cause severe damage. Do not touch the connectors on the back of
the module. When not in use, the module should be stored in an antistatic bag. The plastic cover should not be removed. Failure to observe
this precaution could result in damage to or destruction of the
equipment.
Step 3. Take the MBCN out of its shipping container. Take it out of the
anti-static bag, being careful not to touch the connectors on the back of
the MBCN.
Publication number DSMBCN-UM001B-EN-P February 2003
Step 4. Set the MBCN’s address on the network using the thumbwheels.
Make sure the thumbwheels are centered on the detents.
Step 5. Insert the MBCN in the desired slot in the rack, making sure that
it is well seated in the rack. Use a screwdriver to secure the MBCN in
the rack.
Step 6. Connect the MBCN to the ControlNet network using the BNC
connectors on the front of the MBCN.
Step 7. Turn on power to the rack.
Connecting to the Network
Connect the MBCN to the ControlNet network like any other ControlNet
node, using a ControlNet tap to connect to the network trunkline. The
drop cable from the tap to the MBCN should be 1 m long. The
recommended trunk cable type is RG6. (It is recommended that you use
standard ControlNet network taps available through Allen-Bradley.)
The physical ends of the network trunkline should be terminated with
75-ohm terminators. There should be two and only two terminators on
the network.
AutoMax ControlNet Module Page 21
The MBCN supports redundant cabling.
Ensure that the address for the MBCN is less than or equal to the
maximum unscheduled address (UMAX) configured on the network.
NOTE: 0 is not a valid address.
If the MBCN is being used as a scanner or for scheduled I/O, make sure
the address is less than or equal to the maximum scheduled address
(SMAX) configured on the network.
To maximize efficiency on the ControlNet network, assign consecutive
node addresses to nodes on the network, with the nodes exchanging
scheduled data at the lowest addresses.
Troubleshooting Wiring Problems
If the MBCN does not go active on the network:
• Check cabling for correct wiring to the MBCN.
• Check network termination. Only the two nodes at the physical ends
of the network should have terminating resistors. There should be
two and only two terminators on the network.
• Check the network configuration. Make sure UMAX is high enough
to include this node.
• Check that you haven’t duplicated the address of another node on the
network.
• Check that the thumbwheels have been read correctly by displaying
register 32.
Publication number DSMBCN-UM001B-EN-P February 2003
Page 22 AutoMax ControlNet Module
The following steps describe the procedure for using the MBCN as a
scanner. The sections that follow describe the procedures and registers
in more detail.
Step Description Refer to
Quick Start
page:
Step 1. Use RSNetWorx to create a configuration that
contains the I/O devices the MBCN is to scan
and the scheduled produced and consumed
connections for the MBCN.
Step 2. Download the configuration to the MBCN. 32
Step 3. Check the NAM state for online. 60
Step 4. Put the MBCN in run mode. 32
Step 5. Verify you can read input data and set output
data, check connection status, and so on.
24
32,35
Publication number DSMBCN-UM001B-EN-P February 2003
Overview
Memory Overview
AutoMax ControlNet Module Page 23
Programming the MBCN
This section is a guide for configuring and programming the MBCN.
Configure the scheduled connections using RSNetWorx. The
configuration you create contains all the I/O devices to be scanned, and
all the scheduled produced and consumed connections on the MBCN, the
network parameters and the schedule for all updates.
This section starts with some general information, then describes the
MBCN memory layout in detail, with information about the interface
between your application and the MBCN, and the organization of the
tables on the MBCN.
The MBCN contains 64 Kbytes (32768 16-bit registers) of shared
memory that can be accessed through the AutoMax rack backplane by
application tasks running on an AutoMax processor. The following table
shows the general organization of the shared memory.
AutoMax Registers Description
0-63 Status and control
5 Module control register
64-7383 Unscheduled data
9216-9245 ID area
9247 Channel state
9248-9263 Active node list
9280-9292 Pending network parameters
9304-9316 Current network parameters
9336-9339 Error log
9344-9401 Diagnostic counters
9466 Serial port state
9468-9471 Revision information
9472 Module state
9473 NAM state
9474-9475 Host watchdog
9476 Keeper state
9477 Flash state
Publication number DSMBCN-UM001B-EN-P February 2003
Page 24 AutoMax ControlNet Module
AutoMax Registers Description
9478 Link timeout
15362-15614 Status for each connection
15744-15760 Overall status information
16384-24575 Scheduled receive data
24576-32767 Scheduled transmit data
Figure 4 Memory Overview
Configuring Scheduled Connections
The MBCN can act as a ControlNet scanner to scan I/O modules. As
well, scheduled connections can be configured to exchange data with
other scanner nodes on the network.
You use RSNetWorx to configure your network. The following sections
briefly describe how to configure commonly occurring devices. For
detailed information, refer to the RSNetWorx documentation and online
help.
Creating a Configuration
You can use RSNetWorx as an offline or online configuration tool. In
most cases you will use it online. The instructions that follow describe
using RSNetWorx online. They assume that RSNetWorx and RSLinx
have been installed, along with any hardware required to communicate
with the ControlNet network.
1. Run RSNetWorx.
2. Create a new configuration using the File/New command.
3. Put RSNetWorx online using the Network/Online command.
4. Select a path to the network. RSNetWorx should go online and
display the devices it finds on the network.
5. Click on the MBCN you are configuring to select it, right click on it
and select Scanlist Configuration from the menu that appears.
RSNetWorx asks whether you want to switch to Edit Mode. Click
Yes.
6. The MBCN Scanlist Configuration Tool opens. There are two tabs –
the Connection Configuration tab, which shows all the connections
for the device you are configuring, and the Connection Status tab,
which shows the status of those connections.
7. Select the Connection Configuration tab to create connections.
The device you are configuring, in this case the MBCN, is shown
highlighted. The other devices are shown as a list.
Publication number DSMBCN-UM001B-EN-P February 2003
Loading...