beautypg.com

Mbcn automax controlnet module, Overview, Module overview – Rockwell Automation AutoMax ControlNet Communication Interface Module User Manual

Page 11

background image

AutoMax ControlNet Module Page

11

Publication number DSMBCN-UM001B-EN-P February 2003

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.

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 15362-

15614, 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.