Rockwell Automation AutoMax ControlNet Communication Interface Module (Cat. No. O-58820-2) Major Rev.
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 SGI1.1) describes some important differences between solid state equipment and hard–wired electromechanical devices.
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 7-Segment Display OK LED MAC ID Thumbwheels Serial Configuration Port NAP Port ControlNet Connectors Network Status LEDs 7-Segment LED Codes Communication Error 13 INSTALLATION 19 Prevent Electrostatic Discharge 19 Installation and Wiring 2
AutoMax ControlNet Module Page 5 Memory Overview 23 Configuring Scheduled Connections Creating a Configuration Configuring 1771 I/O Configuring Flex I/O Configuring Scheduled Data with Another MBCN Configuring Scheduled Data with a PLC-5 Configuring Scheduled Data with a ControlLogix Processor 24 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
Page 6 AutoMax ControlNet Module Standard ControlNet Counters Module Specific Counters The Error Log 64 65 66 ACTIVE NODE LIST 67 ID AREA 68 Vendor ID Device Type Product Code Major Revision Minor Revision Status Serial Number Product Name Length Product Name Current Address MAC ID Switches Summary of ID Area Locations 68 68 68 68 68 68 69 69 69 70 70 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 ac
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 .................................................................................................................
Introduction 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.
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.
AutoMax ControlNet Module Page 11 MBCN AutoMax ControlNet Module Overview This chapter contains the following information: • module overview • a summary of hardware features • a description of how the hardware works Module Overview 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.
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.
AutoMax ControlNet Module Page 13 Hardware Features The main hardware features of the MBCN are: MBCN O-58820 Fault Code OK MAC ID 10 • 7-segment display • 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 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.
Page 14 AutoMax ControlNet Module 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.
AutoMax ControlNet Module Page 15 NAP Port 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.
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.
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 .
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.
AutoMax ControlNet Module Page 19 Installation 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.
Page 20 AutoMax ControlNet Module Installation and Wiring DANGER 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.
AutoMax ControlNet Module Page 21 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.
Page 22 AutoMax ControlNet Module Quick Start 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 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. 24 Step 2. Download the configuration to the MBCN. 32 Step 3. Check the NAM state for online. 60 Step 4.
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.
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.
AutoMax ControlNet Module Page 25 8. To create a connection to another device, right click on that device in the list and select Insert Connection from the menu that appears. 9. To create a target on the MBCN to which another device can connect, right click on the MBCN and select Insert Target for Connections from the menu. The following sections provide simple examples of how to create connections for specific types of devices.
Page 26 AutoMax ControlNet Module Creating Connections to Analog I/O Modules Note: You must always create a connection to the discrete I/O in the chassis, even if you are interested only in the analog modules in the chassis. 1. Right click on the analog module and select Insert Connection. 2. Set the Connection Name to Discrete Exclusive Owner. 3. Set the Requested Packet Interval to the desired update rate. The RPI must be greater than or equal to the network update time (NUT). 4.
AutoMax ControlNet Module Page 27 not occupied by discrete modules. For example, if the highest slot occupied by an output module is slot 7, you can reduce the output size from 8 to 7. 5. RSNetWorx assigns the Input Address, Output Address and Status Address automatically if Enable automatic addressing on insert is turned on. If you want to manually assign these addresses, enter the values 6. You can set how output modules behave on lost communications or in program mode on a slot by slot basis.
Page 28 AutoMax ControlNet Module 3. Set the Requested Packet Interval to the desired update rate. The RPI must be greater than or equal to the network update time (NUT). 4. Set the input size to the number of words of data you want to receive from the destination MBCN. 5. RSNetWorx assigns the Input Address, Output Address and Status Address automatically if Enable automatic addressing on insert is turned on. If you want to manually assign the addresses, enter the values. 6.
AutoMax ControlNet Module Page 29 3. Set the Connection Name to Consume Data From. 4. RSNetWorx assigns the Producer ID automatically. If necessary, change the value. 5. Set the Requested Packet Interval to the desired update rate. The RPI must be greater than or equal to the network update time (NUT). 6. Set the Input Size to the number of words of data you wish the MBCN to produce. 7.
Page 30 AutoMax ControlNet Module 8. For the Data Type, select the user-defined data type you created earlier. 9. For Tag Type, check Produced and set the number of consumers to an appropriate value (at least 1 but more if other nodes will be consuming this data). 10. Click the OK button. Save your program and download it to the ControlLogix processor. In the RSNetWorx Scanlist Configuration for the MBCN: 1. Right click on the ControlLogix processor and select Insert Connection. 2.
AutoMax ControlNet Module Page 31 10. Set the Node to the MBCN address on the ControlNet network. 11. Click Finish. Use the following steps to create a consumed tag in RSLogix 5000: 1. Expand the Data Types item in the tree, right click on User-Defined, and select New Data Type... In the dialog box that appears: 2. Give the new type a name, for example, ConsTagType, and optionally a Description. 3. Create members for the data type. The first member should be a DINT (this entry contains status information).
Page 32 AutoMax ControlNet Module 5. RSNetWorx assigns the Input Address, Output Address and Status Address automatically if Enable automatic addressing on insert is turned on. If you want to manually assign these addresses, enter the values. 6. Click OK to accept the connection.
AutoMax ControlNet Module Page 33 There is usually some header information included with the data for each connection. The amount varies with the type of device the MBCN is connected to. RSNetWorx displays input and output sizes in the form 9(6). This means that the connection uses 9 words in total, with 6 words of data and 3 words of header.
Page 34 AutoMax ControlNet Module 0200 IF NAMSTATE% = 12 THEN GOTO 300 \!ATTACHED 0210 DELAY 1 TICKS 0220 GOTO 200 \! WAIT FOR ONLINE 0300 CN_RUN@ = 1 \! PUT THE MBCN IN RUN 0400 OUT_WRD_0% = INP_WRD_0% \!COPY INPUT WORD 0410 IF OUT_WRD_1% > 10000 THEN OUT_WRD_1% = 0 \! LOOP 0420 OUT_WRD_1% = OUT_WRD_1% + 1 \!INCREMENT OUTPUT 0430 DELAY 1 TICKS 0500 GOTO 400 32767 END Multicast Connections To create listen-only or input-only connections to devices to consumed data, use the previous procedures but s
AutoMax ControlNet Module Page 35 Monitoring Module Operation There are various registers on the MBCN that can be used to monitor the operating status. Status of Each Connection You can use RSNetWorx to view the status of each connection. Start the Scanlist Configuration for the MBCN and click on the Connection Status tab. RSNetWorx displays Success for connections that are operating correctly or gives an explanation for connections that are not.
Page 36 AutoMax ControlNet Module General Status, hex Extended Explanation Status, hex 01 0115 Product Type in the key segment did not match the device 01 0116 Major or Minor Revision information in the key segment did not match the device 01 0117 Invalid Connection Point. Could be the wrong device type, device mismatches with scheduled produced and consumed connections, etc.
AutoMax ControlNet Module Page 37 General Status, hex Extended Explanation Status, hex 03* n/a Invalid connection number specified by the Get_Connection_Data service. This is also returned by the Search_Connection_Data service if the specified connection is not found. 04 Zero Based Word Offset Segment Type in path is invalid. The Extended Status shall be the word offset (0 based) to the word in the path where the error occurred. The offset starts at the first word after the path size.
Page 38 AutoMax ControlNet Module General Status, hex Extended Explanation Status, hex 15 n/a Too much data was received. 25 0114 Either the Vendor Id or the Product Code in the key segment did not match the device. Used if the Key Segment was contained in the path. 25 0115 Product Type in the key segment did not match the device. Used if the Key Segment was contained in the path. 25 0116 Major or Minor Revision information in the key segment did not match the device.
AutoMax ControlNet Module Page 39 If bit 3 is set, one or more originator instances does not have a schedule. Run RSNetWorx and schedule the network by enabling edits and doing a save. Scanner State Register 15754 shows the current scanner state. Value Scanner State 0 Idle 1 Active, in program mode 2 Active, in run mode Figure 6 Scanner State Table This register is read-only. The state is Idle only when you are downloading a configuration.
Page 40 AutoMax ControlNet Module AutoMax Registers 15755 Name Description AdapState Current adapter state Figure 8 Summary of Monitor Registers Publication number DSMBCN-UM001B-EN-P February 2003
AutoMax ControlNet Module Page 41 Unscheduled Messaging The MBCN supports unscheduled messaging to other nodes on the ControlNet network. It emulates the interface of the M/N 57C442 Data Highway Plus module. It uses PCCC commands to communicate with other nodes on the network. This section describes how the messaging interface is organized in the MBCN and provides examples of how the MBCN is accessed by the application software.
Page 42 AutoMax ControlNet Module R/W Register Description R/W 22 Response Poll period, in units of 1/8 second. This register is used by the GATEWAY_CMD_OK@ function to compute the time interval to poll for command complete. The default value is 1, which corresponds to a response polling period of 0.125 seconds. R/O 32 Node address (1-99). The value comes from the thumbwheel switches on the faceplate and is updated only on power-up.
AutoMax ControlNet Module Page 43 The format for the IODEF statement (used only in V2.1 and earlier) is as follows: nnnn IODEF variable_name [SLOT=slot number, & REGISTER=register number, BIT=bit number] where: • nnnn = configuration task line number • variable_ name = integer or boolean variable. Double integer variables can be used but should be avoided because of the possibility that all 32 bits will not transfer in one operation.
Page 44 AutoMax ControlNet Module Application Programming Read and write commands from the MBCN are initiated from a BASIC application task by executing the GATEWAY_CMD_OK@ function: GATEWAY_CMD_OK@(status%, cmd_code%, slave_node%, & slave_reg$, master_var!, num_regs%) where: • status is an integer variable representing the location where the status resulting from the operation is stored. Refer to page 51 for a list of status values.
AutoMax ControlNet Module Page 45 NOTE: If more than four tasks try to initiate messages at the same time, error code '22' is returned to the additional tasks attempting accesses. If you are using AutoMax Programming Executive software version 2.1 or earlier, any required registers must be defined using IODEFs in the configuration task. If you are using AutoMax Programming Executive software version 3.0 or later, these registers are defined using the Variable Configurator within the Programming Executive.
Page 46 AutoMax ControlNet Module Commands Initiated by the Module The commands described in figure 13 can be used by the AutoMax Processor in the GATEWAY_CMD_OK@ function to initiate a command on the MBCN.
AutoMax ControlNet Module Page 47 Command 4, Word Range Write, transfers a block of data from the specified AutoMax registers on the module to the target registers at the destination address. The data must already exist in the registers on the module. Data can be transferred from any file in the PLC-5 data image area. The data is stored in the specified registers on the module. A maximum of one file (1000 registers) can be transferred in a single request. The transfer cannot cross file boundaries.
Page 48 AutoMax ControlNet Module 20 LOCAL DST% \! The address of the destination node & on the local ControlNet network \! The location where the status & resulting from the operation is stored \! The number of registers to be & transferred \! The PCCC command sent by the module 21 LOCAL STS% 22 LOCAL SZE% 23 30 31 32 33 40 LOCAL CMD% DST% = 3 STS% = 0 SZE% = 100 CMD% = 3 IF NOT GATEWAY_CMD_OK@(STS%, CMD%, DST%, "N7:0", & VARPTR!(B3BASE%), SZE%) THEN 20000 \! process errors & at line 20000 Example 2: C
AutoMax ControlNet Module Page 49 module to be read from \! The address of the destination node & on the local ControlNet network \! The location where the status & resulting from the operation is stored \! The number of registers to be & transferred \! The PCCC command sent by the module 20 LOCAL DST% 21 LOCAL STS% 22 LOCAL SZE% 23 30 31 32 33 40 LOCAL CMD% DST% = 3 STS% = 0 SZE% = 100 CMD% = 6 IF NOT GATEWAY_CMD_OK@(STS%, CMD%, DST%, "N7:0", & VARPTR!(B3BASE%), SZE%) THEN 20000 \! process errors & at l
Page 50 AutoMax ControlNet Module 20 LOCAL DST% 21 LOCAL STS% 22 LOCAL SZE% module to be read from \! The address of the destination node & on the local network \! The location where the status & resulting from the operation is stored \! The number of registers to be & transferred \! The PCCC command sent by the module 23 LOCAL CMD% 30 DST% = 7 31 STS% = 0 32 SZE% = 3 33 CMD% = 5 40 IF NOT GATEWAY_CMD_OK@(STS%, CMD%, DST%, & "N7:0,N7:2,N7:4", VARPTR!(B3BASE%), SZE%) & THEN 20000 & \! process errors at li
AutoMax ControlNet Module Page 51 20 LOCAL DST% 21 LOCAL STS% 22 LOCAL SZE% \! The address of the destination node & on the local network \! The location where the status & resulting from the operation is stored \! The number of registers to & be transferred \! The command sent by the module 23 LOCAL CMD% 30 DST% = 7 31 STS% = 0 32 SZE% = 100 33 CMD% = 2 40 IF NOT GATEWAY_CMD_OK@(STS%, CMD%, DST%, "1234", & VARPTR!(N7BASE%),SZE%) THEN 20000 \! process errors & at line 20000 GATEWAY_CMD_OK@ Status Codes
Page 52 AutoMax ControlNet Module Code, hex Description 11 Destination memory full, cannot accept command now 12 Destination did not acknowledge command 13 Network contention, possible duplicate node or bad cabling 14 Local port is disconnected, or no other node found 15 Timeout waiting for a reply message 16 Duplicate node detected 17 Node is offline 18 Hardware fault 1D Transaction number mismatch 1E Duplicate transaction number 31 Illegal command or format 32 Host is malfunctionin
AutoMax ControlNet Module Page 53 Extended Status (EXT_STS) Codes for Command 0F If the value in the upper byte of the GATEWAY_CMD_OK@ "status" parameter variable is 3F, then there is a value in the upper byte of the extended status register (register 33 on the module) that supplies further information. The following table shows possible values for the extended status error code.
Page 54 AutoMax ControlNet Module Code, hex Description 16 Scanner not able to communicate with 1771 rack adapter 17 Adapter cannot communicate with module 18 1771 module response was not valid 19 Duplicated label 1A File is open; another node owns it 1B Another node is the program owner 1C-FF (not used) Figure 14 Extended Status Error Codes Table Commands from Remote Nodes The module responds to the following incoming commands from remote nodes: Command Function Description 0F 68 Typed
AutoMax ControlNet Module Page 55 Basic Command Set Commands Command Function Description 02 N/A Protected Bit Write 00 N/A Protected Write 05 N/A Unprotected Bit Write 01 N/A Unprotected Read 08 N/A Unprotected Write Figure 16 Unsolicited Basic Command Set Commands The commands shown write directly to or read directly from file N7 on the module. The address field is used as an offset into the file. If the address does not exist, the module returns an error.
Page 56 AutoMax ControlNet Module Differences from the M/N 57C442 Module Interface If you are modifying an existing application for the 57C442 Data Highway Plus module to work on the ControlNet module, you should be aware of the following differences between the interface on the two modules. • There is no global data on ControlNet. • There are fewer integer files on the ControlNet module. The ControlNet module has three integer files (N7-N9). The Data Highway Plus module has twelve (N7-N18).
AutoMax ControlNet Module Page 57 Viewing Network Parameters The network parameters include the network update time (NUT), the maximum scheduled address (SMAX), the maximum unscheduled address (UMAX), and the network redundancy (channel A only, Channel B only, or both). There are additional network parameters that depend on the devices on the network, the network media type and length, and so on. The MBCN has tables that contain the values assigned.
Page 58 AutoMax ControlNet Module Name Register Description CurTuiUniqueID 9314-9315 Keeper CRC. This is the last Table unique ID (TUI) value (heard from valid TUI from the network). CurTuiStatus 9316 TUI Status of last good TUI from network. If bit 0 is set, it indicates that channel B is configured; if bit 1 is set, it indicates that channel A is configured. Refer to the ControlNet specification for the remaining bits.
AutoMax ControlNet Module Page 59 Name Register PndTuiStatus 9292 Description TUI Status that the MBCN will send if it becomes the master keeper after the network change is complete.
Page 60 AutoMax ControlNet Module State Registers The MBCN maintains several registers that indicate the state of various operations on the MBCN. Module State The Module State register (9472) indicates the current overall state of the MBCN. It can have one of three values.
AutoMax ControlNet Module Page 61 Name Value Meaning NAM_SEND_ALIVE 07h Transitional state in going online NAM_WATCH 08h Transitional state in going online NAM_LISTEN 09h Transitional state in going online NAM_ATTACHED 0Ch Online Figure 20 NAM State Table The state must be NAM_ATTACHED to send messages and scan I/O. All other states are intermediate states as the MBCN becomes attached to the network. An application should check the NAM state before it starts accessing data.
Page 62 AutoMax ControlNet Module Name Value 7-Segment LED KPR_STE_NET_CHANGE_FAULTED_MASTER KPR_STE_DISABLED 12 5 FFh N/A Figure 21 Keeper State Table To scan I/O, the keeper state must be KPR_STE_BACKUP or KPR_STE_MASTER. Unscheduled messaging and scheduled produced (target) connections will work in other keeper states. Faulted states (faulted master or faulted backup) mean the keeper configuration on the MBCN doesn’t match the network. Run RSNetWorx and reschedule the network.
AutoMax ControlNet Module Page 63 Channel State The Channel State register (9247) shows the state of each channel LED on the MBCN. Bits 0 to 2 show the status of channel A. Bits 3 to 5 show the status of channel B. For detailed information, refer to the ControlNet Specification, part 10, section 240, table 10-224. “Railroad” indicates the 2 LEDs are flashing alternately, like a railroad signal.
Page 64 AutoMax ControlNet Module Diagnostic Counters The MBCN maintains two sets of diagnostic counters: • the standard ControlNet diagnostic counters • additional diagnostic counters specific to the MBCN These counters can be used to monitor MBCN operation and to diagnose problems. The counters all roll over to 0 when they reach their maximum value. To clear the counters, write a non-zero value to register 4.
AutoMax ControlNet Module Page 65 Name Location Description with the network, configured length doesn’t match the actual length, unconfigured repeaters, etc. RxAbort 9357 Frame Received – Aborted Lonely 9358 The MBCN did not hear anyone else on the network for 1.
Page 66 AutoMax ControlNet Module Name Location Description ReplySentOk 9385 High Level Replies Sent OK ReplyRecdOk 9386 High Level Replies Received OK DuplMsgsRecd 9387 Duplicate Messages Received (and ignored) AckTout 9388 UCMM Acknowledge Timeouts TxFail 9389 High Level Transmit Failures, the MBCN tried 3 times to send a message, there was no acknowledge, no reply UndelivReply 9390 High Level Reply could not be delivered ConnTimeout 9391 Connection TimeOuts MsgsIgnored 9392 Mess
AutoMax ControlNet Module Page 67 Active Node List The MBCN maintains a list of active nodes on the network in the ActNodeTable table, registers 9248-9263, one bit per node. The low bit of register 9248 corresponds to node 0, and so on. The bit is set if the node is transmitting frames on the network. It is cleared if a node misses the opportunity to send 10 times in a row. The following table shows the locations of the bytes for each node in the active node list.
Page 68 AutoMax ControlNet Module ID Area The ID area contains information that identifies the MBCN on the network, and the current device status. The combination of vendor ID, device type, product code, and revision makes up the device's “electronic key”. Vendor ID Register 9216 contains the vendor ID. The vendor ID is assigned by ControlNet International. The vendor ID for the MBCN is 5 (Reliance). Device Type Register 9217 contains the device type.
AutoMax ControlNet Module Page 69 7 6 5 4 Description 0 0 0 0 Self test 0 0 0 1 Firmware update in progress 0 0 1 0 Communication fault.
Page 70 AutoMax ControlNet Module Current Address Register 9244 contains the value read from the thumbwheels at power-up. If you change the thumbwheels after power-up, the value in this register does not change. MAC ID Switches Register 9245 contains the value read from the thumbwheels at powerup. If you change the thumbwheels after power-up, the value in this register does not change.
AutoMax ControlNet Module Page 71 Firmware Version Information The MBCN firmware consists of two components: • The PGA configuration portion performs the low-level ControlNet operations on the network • The firmware portion is responsible for higher level operations such as ControlNet objects, managing message queues, etc. An application can use the following registers to determine the versions of firmware running on the MBCN.
Page 72 AutoMax ControlNet Module Using the Host Watchdog The host watchdog is a feature you can use to ensure that the MBCN stops if the host application stops running. When you enable the host watchdog, the host AutoMax must check in with the MBCN more frequently than the watchdog period. To enable the host watchdog, write the watchdog time in milliseconds to register 9474, WdTime. The watchdog time can range from 1 to 65534, corresponding to times of 1 ms to 65.534 seconds.
AutoMax ControlNet Module Page 73 Updating the Firmware You can update the firmware on the MBCN using either of two methods: • using ControlFlash over ControlNet. In order to use this method, the MBCN must be running firmware version 1.10 or above. If the firmware version is an earlier one, you must first upgrade the firmware using the serial port, after which you can use ControlFlash for the updates • using the serial port on the MBCN The usual method is to use ControlFlash.
Page 74 AutoMax ControlNet Module 2. When the AutoMax is powering up, the 7-segment LED flashes some numbers, then displays ‘.b’ for 4 seconds. While it shows ‘.b’, press the exclamation mark (!) key in your communication software to tell the MBCN that you want to download firmware. 3. The 7-segment display changes to ‘A’ to tell you the MBCN is in system configuration mode.
AutoMax ControlNet Module Page 75 PGA Config Write Successful **** Cycle Power **** 5. Cycle power on the MBCN so that it uses the new firmware.
Page 76 AutoMax ControlNet Module Converting from Major Revision 1 to 2 If you have a network configuration in RSNetWorx that contains a Reliance MBCN (major revision 1) and want to convert that device to a Reliance MBCN (major revision 2), perform the following steps: If you have access to the Reliance MBCN hardware 1. Flash upgrade the Reliance MBCN (major revision 1) to a Reliance MBCN (major revision 2). 2. Open RSNetWorx for ControlNet. 3. Select File > New. 4. Select Network > Online.
AutoMax ControlNet Module Page 77 6. Select Device > Scanlist Configuration. Notice that the status columns are not displayed. 7. Double-click a connection. On the Connection Properties, note that three dashes are shown in the Status address field. 8. In the Status address field, specify the desired status offset and click OK. 9. Repeat steps 7 and 8 for each connection. 10. Select File > Save. 11. Close the Scanlist Configuration Tool. 12. Select Device > Scanlist Configuration again.
Page 78 AutoMax ControlNet Module Specifications The MBCN is a standard AutoMax module with the following specifications: Parameter Specification Module Location AutoMax chassis Function AutoMax ControlNet communication module Dimensions Height: 29.85 cm (11.75 inches) Width: 3.18 cm (1.25 inches) Depth: 18.73 cm (7.375 inches) Weight: 0.
AutoMax ControlNet Module Page 79 Support Local Drive Solutions Contact Directory New England Ph. 508.357.8431 Fax 508.485.5059 Boston MA Southeast Ph. 770.277.0277 Fax 770.682.6491 Atlanta GA Gulf Coast Ph. 281.233.0300 Fax 281.233.0101 Houston TX West Coast Ph. 626.969.7647 Fax 626.334.8320 Los Angeles CA Eastern Ph. 732.225.1360 ext 110 Fax 732.225.7833 Edison NJ Carolinas Ph. 704.525.1455 Fax 704.525.9025 Charlotte NC Midwest Ph. 630.860.1090 Fax 630.787.0309 Chicago IL St. Ph. Fax St.
www.rockwellautomation.com Corporate Headquarters Rockwell Automation, 777 East Wisconsin Avenue, Suite 1400, Milwaukee, WI, 53202-5302 USA, Tel: (1) 414.212.5200, Fax: (1) 414.212.5201 Headquarters for Allen-Bradley Products, Rockwell Software Products and Global Manufacturing Solutions Americas: Rockwell Automation, 1201 South Second Street, Milwaukee, WI 53204-2496 USA, Tel: (1) 414.382.2000, Fax: (1) 414.382.
