Modbus Plus protocol) but also a wide assortment of end devices licensed through the ModConnect Program. The MVI46-MBP module acts as an input/output module between the Modbus Plus network and the SLC backplane.

The data transfer from the SLC processor is asynchronous from the actions on the Modbus Plus network. A 4000-word register space in the module exchanges data between the processor and the Modbus Plus network.

These modules allow Rockwell Automation platforms to connect directly on

Modbus Plus networks as a peer. In addition, the modules act as slaves to processors that must read/write data from the module's memory.

Crossing all industrial boundaries, potential applications include the connection of

Rockwell Automation processors to Modicon processors, and the connection of

Modbus Plus speaking devices such as drives, relays, and power monitor hardware to the SLC backplanes.

ProSoft Technology, Inc.

February 19, 2008

Page 37 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

Single Slot - 1746 backplane compatible (Local or extended I/O rack only.

Remote rack not supported)

The module is recognized as an Input/Output module and has access to processor memory for data transfer between processor and module using

M0/M1 files

Ladder Logic is used for data transfer between module and processor

Configuration data obtained through user-defined ladder. Sample ladder file included

Specification

Backplane Current Load

Operating Temperature

Storage Temperature

Shock

Relative Humidity

Vibration

Processor

LED indicators

Debug/Configuration port (CFG)

CFG Port (CFG)

Configuration Connector

Application Ports

Modbus Plus ports

Description

800 ma @ 5V (from backplane)

0 to 60°C (32 to 140°F)

-40 to 85°C (-40 to 185°F)

30g operational, 50g non-operational

5% to 95% (non-condensing)

5 g from 10150 Hz

Compatible with Rockwell Automation SLC 5/02 M0/M1 capable processors or newer

Module status, Backplane transfer status, Application status, Serial activity and error LED status

RJ45 (DB-9M with supplied cable)

RS-232 only

RJ45 RS-232 Connector (RJ45 to DB-9 cable shipped with unit)

Dual DB9 Application ports for redundant operation

Communication o o

Baud: 57,600 (fixed)

Parity: none (fixed) o

Stop: 1 (fixed)

Modbus Plus ports o o

User-definable module memory usage

Support for the storage and transfer of up to 4,000 registers across the o o o o o o o backplane

100 word reads and writes (max. allowed)

Supports all five levels of Modbus Plus routing

Software configurable parameters Node address: 1 to 64

Global out size: 0 to 32 words

Global in size: 0 to 32 words

Module data transfer: 0 to 4,000 words

Master command count: 0 to 100 commands

Page 38 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

Function codes accepted (as a Slave): 1, 2, 3, 4, 5, 6, 15, 16

Function codes transmitted (as a Master): 3, 16

Global Data Specifications

The MBP module actively exchanges global in (32 words max. per node) and global out (32 words max.) data on the Modbus Plus network. Priority is given to these data types to provide a high speed mechanism for the transfer of control data.

Modbus Slave Mode Specifications

Supports broadcast commands from host

Communication error codes returned to ladder logic

Modbus Master Mode Specifications

Command list support of up to 100 commands

Conditional and continuous command list polling

Each command list entry is fully configurable for function register to/from addressing and word/bit count/word and byte swap

Event driven bit and register write commands (ladder logic controlled)

Supports sending of broadcast commands

Communication status error codes returned to ladder logic on a per command basis

This section provides an overview of how the MVI46-MBP module transfers data using the MBP protocol. You should understand the important concepts in this chapter before you begin installing and configuring the module.

The following discussion explains several concepts that are important for understanding the operation of the MVI46-MBP module.

Module Power Up

On power up the module begins performing the following logical functions:

1 Initialize hardware components o o o

Initialize SLC backplane driver

Test and Clear all RAM

Reset Modbus Plus Chipset

2 Wait for Module Configuration from SLC processor

3 Initialize Module Register space

4 Initialize Modbus Plus Chipset

5 Enable Global Input task

6 Enable Global Output task

7 Enable Slave Driver

8 Enable Master Driver

ProSoft Technology, Inc.

February 19, 2008

Page 39 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

After the module receives the module configuration from the processor, the

Modbus Plus chipset is enabled (presuming valid configuration values were received), and begins communicating with other nodes on the network, depending on the configuration.

Reference

Main Logic Loop

Upon completing the power up configuration process, the module enters an infinite loop that performs the following functions:

From Power Up Logic

Call I/O Handler

Call I/O Handler

Transfers data between the module and processor

(user, status, etc.)

Call CFG/DEBUG Port

Driver

Call Serial Port Driver

Rx and Tx buffer routines are interrupt driven. Call to serial port routines check to see if there is any data in the buffer, and depending on the value, will either service the buffer or wait for more characters.

Call Network Master &

Slave Drivers

Call Network Master & Slave Drivers

Generate messages and respond to messages received.

Processor Not in Run

Whenever the module detects that the processor has gone out of the Run mode

(that is, Fault or PGM), the Modbus Plus port can be shut down as prescribed in the user configuration. When the processor is returned to a running state, the module resumes communications on the network.

Backplane Data Transfer

The MVI46-MBP module communicates directly over the SLC backplane. All data for the module is contained in the module's M0 and M1 files and the input and output files. Data is moved between the module and the SLC processor across the backplane using the module's M-files. The SLC scan rate and the communication load on the module determine the update frequency of the M1 file. The COP instruction can be used to move data between user data files and the module's M0 file and the M1 file and the user files. All register data travels between the module and the processor using the M1 file. The M0 file is used for special command control of the module from the ladder logic. High-speed data transfer between the processor and the module is accomplished using the module's input and output files.

Page 40 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

The following illustration shows the data transfer method used to move data between the SLC processor, the MVI46-MBP module, and the Modbus Plus network:

As shown in the data flow diagram, all register data transferred between the module and the processor over the backplane is through the M1 file. Ladder logic must be written in the SLC processor to interface the M1 file data with data defined in the user-defined data files in the SLC. All data used by the module is stored in its internal database. The data transferred from the module to the M1 file is updated when new data becomes available from the Modbus Plus network.

The ladder logic in the SLC can control the module by using M files for command and module control.

A value of 9999 in this word (4370 of the M1 file) causes the module to perform a cold-boot operation.

All data used by the module is stored in its internal database. This database is defined as a virtual Modbus data table with addresses from 0 (40001 Modbus) to

7221 (4222 Modbus). The following illustration shows the layout of the database:

ProSoft Technology, Inc.

February 19, 2008

Page 41 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

This database is stored in the M1 file of the module and the internal database of the module. Data contained in this database is paged from the M1 file to the module. When data is received on the network for the database, it is copied to both the M1 file and the internal database. If this data is overwritten in the M1 file, it is also overwritten in the internal database. To move data from a user file to the

M1 file, use the COP instruction. This data is then copied to the module's database. To read data from the module, use the COP instruction to copy data from the M1 file to the user data file.

Configuration Data Transfer

Writing the Configuration to the MVI46-MBP

When the module performs a restart operation, it requests configuration information from the SLC processor. This data is transferred to the module in the

M1 file. When the ladder logic recognizes a value of 9000 in register 4370 of the

M1 file, it should copy all configuration information into the M1 file. After the operation is complete, the ladder logic should place a value of 9001 into the control register (4370) of the M1 file. The module will recognize the configuration completion code (9001) and configure the module using the data contained in the

M1 file.

The Reference chapter contains a complete listing of the configuration information of the M1 file, and design forms to aid in the module configuration process.

Reading the Configuration from the MVI46-MBP

Option "Y" (Transfer Module Cfg to Processor) when using the Debug port, allows the transfer of configuration data from the MVI module to the SLC. When the user presses the "Y" key, the module forms a block (M1:x.4370 = -9000) with the configuration. Ladder logic should copy the data from the M1 file to the SLC data file. The ladder logic should then move 0 to M1:x.4370 in order to clear the module.

Status Blocks

Status data is placed in the M1 file to determine the "health" of the module and the activity of the Modbus Plus network. The format of this data area is shown in the Reference chapter. Registers 4000 to 4369 in the M1 file contain the module's status data.

Command Control Blocks

Command control blocks are special blocks used to control the module or request special data from the module. The current version of the software supports eight command control blocks:

User Command Block (9002)

Command Execution Block (9003)

Command Enable/Disable Blocks (9010, 9011, 9012)

M0 Pass-Through Control (9956, 9958, 9959)

Write Configuration (9997)

Warm (9998)

Cold Boot (9999)

Page 42 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

User Command Block

This block is sent from the SLC processor to the module to execute up to six commands generated from the ladder logic using the M0 file. These commands are placed in the command queue and executed at a high priority in the module.

The format of the block used for this control process is shown in the following table:

Offset Description Length

0 9002

1 Number of commands to add

2 to 11 User Command 1

12 to 21

22 to 31

32 to 41

42 to 51

52 to 61

User Command 2

User Command 3

User Command 4

User Command 5

User Command 6

Word 1 of the block sets the number of commands present in the block. This word should be set to a value from 1 to 6. The format of each command in the block is shown in the following table:

Word Offset

Parameter

Module's Database Register Number

5 Register Address in Device

6 Spare

7 Spare

8 Spare

9 Spare

The definition of each parameter is that given in the command list description in this manual. After the module completes processing the command block, the M0 file is set with the following data:

Offset Description

0 Done Flag (0)

1 9002

2 Number of commands added to the queue

Length

Command Execution Block

This command block inserts commands from the command list into the module's command queue. The command queue is executed at a high priority. Commands with enable codes set to zero, can be executed by the module using this feature.

The format of the block sent by the processor to the module in the M0 file has the following format:

ProSoft Technology, Inc.

February 19, 2008

Page 43 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

Offset Description

0 9003

2 to 61

Number of commands to add

List of command indexes

Length

Word 1 of the block sets the number of commands listed in the block. Up to 60 commands can be sent to the command queue using this block. Words 2 to 61 contain the command indexes to be added to the queue. After the module has processed the block, the M0 file is set with the following data:

Offset Description

0 Done Flag (0)

1 9003

2 Number of commands added to the queue

Length

Command Enable/Disable Blocks

Block codes 9010, 9011 and 9012 alter the enable code for a set of commands in the module's command list. Word 1 in each block defines the number of commands to be considered by the module in the list of command indexes provided. This data is passed to the module in the M0 file.

Block 9010 disables one or more commands in the command list by setting the enable code to a value of zero. The format of the block is as follows:

Offset Description

0 9010

2 to 61

Number of commands to disable

List of command indexes

Length

Block 9011 sets the enable code for the commands in the list to a value of one.

The format of the block is as follows:

Offset Description

0 9011

1 Number of commands to enable

2 to 61 List of command indexes

Length

Block 9012 sets the enable code for the commands in the list to a value of two.

The format of the block is as follows:

Offset Description

0 9012

1 Number of commands to enable

2 to 61 List of command indexes

Length

After the command blocks are processed by the module, word zero of the M0 file will be set to a value of zero.

You can look at the enable code to determine if the enable code has changed or to see the value of the code by using the Debug port. You can restore the original command enable code forcing the module to perform a cold boot and thereby copying the new commands to the MVI46-MBP module.

Page 44 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

M0 Pass-Through Control

M0 PASS_THROUGH CONTROL (REGISTER 100)

Block Code

9956

9958

9959

Descriptions

Formatted pass-through block from function 6 or 16 with word data.

Formatted pass-through block from function 5.

Formatted pass-through block from function 15.

Formatted Pass-Through Command Blocks (Read Block)

Offset Description

100

101

102

103 to 366

9956 or 9958

Number of word registers in Modbus data set

Starting address for Modbus data set

Modbus data set

Length

264

Formatted Pass-Through Response (Write Block)

Offset Description

100 Place a zero in this word after the SLC has processed the passthrough message block.

Length

Formatted Pass-Through Command Blocks (Read Block)

Offset Description

100 9959

101 Number of word registers in Modbus data set

102

103 to 152

153 to 202

Length

Starting word address for Modbus data set

Modbus data set

Bit mask to use with the data set. Each bit to be considered with the data set will have a value of 1 in the mask. Bits to ignore in the data set will have a value of 0 in the mask.

Formatted Pass-Through Response (Write Block)

Offset Description

100 Place a zero in this word after the SLC has processed the passthrough message block.

Length

Write Configuration

This command is sent from the SLC processor to the module to force the module to write its current configuration back to the processor. This function is used when the module's configuration has been altered remotely using database write operations. The ladder logic generates the request by placing a value of 9997 in register 4370 (control register) of the M1 file. The module places all configuration data in the M1 file and places a value of 0 in the control register after completion.

The ladder logic copies the configuration data in the M1 file to the user data files.

ProSoft Technology, Inc.

February 19, 2008

Page 45 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Warm Boot

This command is sent from the SLC processor to the module's control register

(4370) in the M1 file by inserting a value of 9998 into the register. When the module recognizes this value in the control register it performs the warm-boot operation and sets the register to a value of zero.

Cold Boot

This command is sent from the SLC processor to the module's control register

(4370) in the M1 file by inserting a value of 9999 into the register. When the module recognizes this value in the control register it performs the cold-boot operation and sets the register to a value of zero.

Reference

5.2.2 Pass-Through Control Blocks

Formatted Pass Through Control Blocks

If the port on the module is configured for the formatted pass-through mode, the module will pass blocks with identification codes of 9956 = FC16, and 9958 =

FC5, and 9959 = FC15 to the processor for each received write command. Any

Modbus Function 5, 15, or 16 commands will be passed from the port to the processor using this block identification number. Ladder logic must handle the receipt of all Modbus write functions to the processor and to respond as expected to commands issued by the remote Modbus Master device. The format of the formatted pass-through control block is shown in the following tables:

Function 5

Offset Description

100 9958

101 Number if word registers in Modbus data set

102

103 to 366

Starting Address fro Modbus data set

Modbus data set

Length

264

The ladder logic will be responsible for parsing and copying the received message and performing the proper control operation as expected by the master device. The processor must then respond to the pass-through control block with a write block with the following format.

Offset Description

100 Place a zero in this word after the SLC has processed the passthrough message block

Length

This will inform the module that the command has been processed and can be cleared from the pass-through queue.

Function 6 and 16

Offset Description

100 9956

101 Number if word registers in Modbus data set

102 Starting Address fro Modbus data set

103 to 366 Modbus data set

Page 46 of 101

Length

264

ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

Offset Description

100 Place a zero in this word after the SLC has processed the passthrough message block

Length

This will inform the module that the command has been processed and can be cleared from the pass-through queue.

Function 15

When the module receives a function code 15 when in pass-through mode, the module will write the data using block ID 9959 for multiple-bit data. First the bit mask clears the bits to be updated. This is accomplished by ANDing the inverted mask with the existing data. Next the new data ANDed with the mask is ORed with the existing data. This protects the other bits in the INT registers from being affected.

Offset Description

100 9959

101

102

103 to 152

153 to 202

Number of word registers in Modbus data set

Starting word address for Modbus data set

Modbus data set

Bit mask to use with the data set. Each bit to be considered with the data set will have a value of 1 in the mask. Bits to ignore in the data set will have a value of 0 in the mask.

Length

Offset Description

100 Place a zero in this word after the SLC has processed the passthrough message block.

Length

This will inform the module that the command has been processed and can be cleared from the pass-through queue.

ProSoft Technology, Inc.

February 19, 2008

Page 47 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

The following topics describe the flow of data between the two pieces of hardware (SLC processor and MVI46-MBP module) and other nodes on the

Modbus Plus network under the module's different operating modes. Note that all four modes can operate effectively simultaneously if desired. Under most likely operating cases, the Global Input and Global Output tasks operate in conjunction with either the Master or the Slave driver.

Global Data In Mode

When the Global Data In mode is operational, the MVI46-MBP module is receiving Global Input data from up to 64 other nodes on the Modbus Plus network. Each node is capable of transferring up to 32 words, and therefore, the

MVI46-MBP module is capable of accepting up to 2048 words in this manner.

The amount of data, and which slaves to collect it from, are all user-defined through the Device Definition File. The following flow chart and associated table show the flow of data into and out of the module.

Processor Memory

User Data

Files

Status from module

Configuration

Data

Input File

Backplane Interface

Database

Addresses

Register

Data

Modbus

Addresses

40001

3999

4000

44000

44001

Status

4369 44370

4370

7089

Configuration

44371

47089

7130 47130

Input File

Data

7161 47162

Input File

Status

Configuration

MBP Memory

Global Data

Driver

Step Description

The Global In driver reads configuration data from the processor. This data includes the

Device Definition File that includes the node address data, the number of Global In words and where to put this data in the module's internal database.

During the configuration process, the Input File Map is updated out of the configuration file. The Input File Map informs the module which data registers in the internal database to feed into the module's input image. This operational mode is independent of the Global In mode but is commonly used to transfer global input data from other nodes directly to the processor.

The Global In Driver monitors Global In data from other nodes on the network. If the data matches one of the node addresses in the Device Definition File and is qualified in terms of length, etc. the data is accepted.

After the data is accepted, the data is transferred into the module's internal database. The user via configuration in the Device Definition File determines the location of the data.

As data is read from the other nodes on the network into the module, an asynchronous process moves the data from the database into the module's input image. The values to be moved are user determined via configuration of the Input File Map. Up to 32 words of data can be transferred in this fashion.

Page 48 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

Step Description

6 Status is monitored for each device in the Device Definition File that is expected to return

Global In data to the module. This status is updated on an on-going basis and is transferred to the SLC processor for processing. This data includes the node status value and a counter incremented each time global input data is received.

In order for the Global Data In mode to operate, the minimum configuration includes setting the Device Definition File and the Global Input Timeout values. If this or other data is to transfer to the SLC processor using the Input File, the

Input File Map, Input File Size, and Input File Update parameters must also be set.

It is important to understand how the Input File Map determines what data is transferred from the module to the processor. The Input File Map is a 32-word data block that selects the module's internal data registers to transfer to the Input

File. The Input File Map is copied to the module during module configuration. The structure of this data block is as follows:

Word

Input File

Input File Map

100

101

200

201

202

405

4141

4142

4143

100

101

200

201

202

Module Database

Register Data

405

The Input File Map acts as a data routing table, allowing the user to configure the source of data for the Input File data transferred to the ControlLogx processor on a high-priority basis.

3999

4000

4141

4142

4143

Configuration and

Status Data

Each scan of the module's program places the data into the input image using this Input File Map to select data out of the module's database. Any data in the module's database can be assigned to the high-speed Input File data using this map.

Global Data Out Mode

When the MVI46-MBP module's Global Output capability is enabled, up to 32 words of data can be transferred onto the Modbus Plus network by the module.

This data, typically reserved for high-speed data such as for application control data, is transmitted each time the module receives the network token.

ProSoft Technology, Inc.

February 19, 2008

Page 49 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

The number of words transferred to the Modbus Plus network is user determined through the Module Configuration Block described in the Reference chapter. The following flow chart and associated table describe the flow of data into and out of the module.

Processor Memory

User Data

Files

Status from Module

Configuration

Data

Output File

Backplane Interface

Database

Addresses

Register

Data

Modbus

Addresses

40001

3999 44000

4000 44001

Status

4369 44370

4370

Configuration

44371

7089 47090

7090

7121

Output File

Data

47091

47122

Output File

Status

Configuration

MBP Module

Global Data

Driver

Step Description

The Global Output driver reads configuration data from the SLC processor. This data consists of the number of words to be transmitted by the module each time the module has the token. In addition, timing data on the update rate for the Global Out transmission is also obtained from the configuration data.

The Global Out data image is updated from the processor through the module's output image. Based on the update rate configured by the user, the Global Out image in the

Modbus Plus chipset will also be updated.

The Global Output driver in the Modbus Plus chipset will transmit the Global Out data each time the token is received by the module.

The Global Output driver status is updated in the module's database.

To enable the Global Output Mode, set the Global Output Length parameter to a value between 1 and 32. To disable this feature, set the parameter to a value of zero. Status information about the global output data is found in the status block transferred from the module to the SLC processor.

Slave Driver Mode

Slave Driver Mode allows the MVI46-MBP module to respond to data read and write commands issued by other nodes on the Modbus Plus network. Two aspects of the module's operation must be kept in mind when considering using this mode:

1 The module supports MSTR Type 1 and Type 2 commands issued from a

Modicon processor or another device acting in a similar capacity.

2 The module is a Modbus Plus Host type of node, therefore any device wishing to read or write data from the module must be able to define a Data

Slave Input Path in the Routing Path. The module supports all 8 Data Slave

Input paths, but a Data Slave Path of 0 (zero) will cause the command to be rejected .

Page 50 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

The following flow chart and associated table show the flow of data into and out of the module.

Processor Memory

User Data

Files

Backplane Interface

Database

Addresses

Modbus

Addresses

40001

MBP Module

Register

Data storage

Register

Data

Slave

Mode

Driver

Status from Module

Configuration

Data

3999 44000

4000 44001

Status

4369 44370

4370

7089

Configuration

44371

47090

Status

Configuration

Step Description

1 A Host device, such as a Modicon PLC or an HMI application issues a read or write command to the module's node address. The Modbus Plus chipset qualifies the message before accepting it into the module.

After the module accepts the command, the data is immediately transferred to or from the internal database in the module. If the command is a Read command, the data is read out of the database and appended to the response, and if the command is a Write command, the data is written directly into the database.

After the data processing has been completed in Step 2, the response is issued to the originating node.

Several counters are available in the Status Block that permit the ladder logic program to determine the level of activity of the Slave Driver.

There are no special module configuration requirements to place the module in the Slave Operating Mode. When the module is operating in the slave mode, external devices act as masters by polling for data from the module or writing to the module. As such, the module needs to only respond to read and write commands, transferring data to/from the module's database depending on the command type.

In order for a Modicon PLC to read data from the MVI46-MBP module, a MSTR

Type 2 instruction must be entered in the Modicon's ladder program. This instruction initiates a Modbus Plus network transaction between the PLC and the module. In the configuration of the command, the programmer can specifically choose the location and amount of data to be read from the module and returned to the Modicon's memory.

The following illustration shows an example configuration for a MSTR Type 2 command.

ProSoft Technology, Inc.

February 19, 2008

Page 51 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

+---------+

enable -¦ ¦- active

¦ 40050 ¦

+---------¦

abort -¦ ¦- error

¦ 40060 ¦

+---------¦

¦ MSTR ¦- success

¦ 00020 ¦

+---------+

Contents of registers in the control block

40050 = 2 Read instruction

40051 = 0 Error code

40052 = 20 Length of the read

40053 = 50 slave register to read (module address 50)

40054 = 6 MVI46-MBP Node address to retrieve data from

40055 = 1 Slave Input Path for routing

40056 = 0 Routing Address 3

40057 = 0 Routing Address 4

40058 = 0 Routing Address 5

40060 = Destination address in the Modicon PLC for the data from the MVI46-MBP module

The MSTR 2 instruction shown in the previous example reads 20 words from the

MVI46-MBP module beginning at address 50 and places the data in the Modicon

PLC beginning at address 40060.

Note that the Slave Input Path value must be entered in order for the command to execute successfully. Valid values are from 1 to 8. Any other values will cause the command to fail.

In order for a Modicon PLC to write data to the module, a MSTR Type 1 instruction must be entered in the Modicon's ladder program. This instruction initiates a Modbus Plus network transaction between the PLC and the module. In the configuration of the command, the programmer can specifically choose the destination address and the amount of data to be written to the module from the

Modicon's memory.

The following illustration shows an example configuration for a MSTR Type 1 command.

+---------+

enable -¦ ¦- active

¦ 40001 ¦

+---------¦

abort -¦ ¦- error

¦ 40010 ¦

+---------¦

¦ MSTR ¦- success

¦ 00002 ¦

+---------+

Contents of registers in the control block

40001 = 1 Write instruction

40002 = 0 Error code

40003 = 30 Length of the write

40004 = 100 register to Write to in module

40005 = 6 MVI46-MBP Node address to write to

40006 = 1 Slave Input Path for routing

40007 = 0 Routing Address 3

40008 = 0 Routing Address 4

40009 = 0 Routing Address 5

40010 = Source of the data in the Modicon PLC to send to the MVI46-MBP module

This instruction will write 30 words (from 40010 to 40039) in the PLC to the

MVI46-MBP module's database beginning at Data Register address 100.

Note that the Slave Input Path value must be entered in order for the command to execute successfully. Valid values are from 1 to 8. Any other values will cause the command to fail.

Page 52 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

Master Driver Mode

In the Master mode, the MVI46-MBP module issues read or write commands to other devices on the Modbus Plus network. These commands are userconfigured in the module via the Master Command List received from the SLC processor or using the command control blocks. Command status is returned to the processor for each individual command in the command list status block. The module emulates the MSTR Type 1 and Type 2 commands in terms of data read and write functionality. The following flow chart and associated table describe the flow of data into and out of the module.

MBP Memory Processor Memory

User Data

Files

Backplane Interface

Database

Addresses

Modbus

Addresses

40001

Register

Data storage

Register

Data

Master

Mode

Driver

Status from Module

3999 44000

4000 44001

Status

4369

4370

44370

7089

7170

7182

Configuration

44371

47090

47171

Event Cmd

Data

47183

M0 File

Status

Master

Command List Configuration

Data

Event Cmd

Data

Command

Control

Configuration

Event Cmd

Data

Command

Queue

Step Description

The Master driver obtains configuration data from the SLC processor. The configuration data obtained includes the number of commands, the Device Definition File, and the

Master Command List. These values are used by the Master driver to determine the type of commands to issue to the other nodes on the Modbus Plus network. In addition, Event

Command control bits are available to control individual commands from ladder logic.

After configuration, the Master driver begins transmitting read and/or write commands to the other nodes on the network. If writing data to another node, the data for the write command is obtained from the module's internal database to build the command.

Presuming successful processing by the other nodes, responses are received into the

Master driver for processing.

Data received from the other nodes on the network is passed into the module's internal database, assuming a read command.

Status is returned to the SLC processor for each command in the Master Command List.

Ladder logic can alter the enable code for commands or cause the master driver to execute user commands or commands in the list by placing the commands in the command queue.

In order for the MVI46-MBP module to operate in the Master Mode (actively reading/writing data with other nodes on the network), several user configurable parameters must be received from the SLC processor. The following topics detail these configuration requirements.

ProSoft Technology, Inc.

February 19, 2008

Page 53 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

Device Definition File

An entry must be made in the Device Definition File for each node on the network that is to be addressed by the module's Master Command List. The entry in the

Device Definition File must consist of at least the Routing Path, including a valid

Data Slave Input path if the device is not a Modicon PLC .

Master Command List

In order to function in the Master Mode, the module's Master Command List must be defined. This list contains up to 200 individual entries, with each entry containing the information required to construct a valid command. This includes the following:

Command enable mode (disabled, continuous or event control)

Node Route Path: From Device Definition File (index in Device Definition File)

Command Type: Read or Write up to 100 words per command

Source and Destination Register Address: Determines where data will be placed and/or obtained

Count: Select the number of words to be transferred - 1 to 100

Event Command Control

Commands can be entered in the command list to operate either continuously or under ladder logic control. The operating mode is selected when entering the command in the Master Command List.

If a command is configured as an Event Command, the module looks to the

Event Command Control words received from the SLC processor to determine when to execute set in the M1 file. The following table describes the structure of the Control words:

Event Command Control

Database

Address

7170

7171

7172

7173

7174

7175

7176

7177

7178

7179

7180

7181

7182

Bit Offset for

Event Control

0 to 15

16 to 31

32 to 47

48 to 63

64 to 79

80 to 95

96 to 111

112 to 127

128 to 143

144 to 159

160 to 175

176 to 191

192 to 199

Name Description

Event Commands #1 to 16

Event Commands #17 to 32

Event Commands #33 to 48

Event Commands #49 to 64

Event Commands #65 to 80

Event Commands #81 to 96

Event Commands #97 to 112

Event Commands #113 to 128

Event Commands #129 to 144

Event Commands #145 to 160

Event Commands #161 to 176

Event Commands #177 to 192

Event Commands #193 to 200

This block of data consists of 13 words of bits that are mapped to individual commands in the

Master Command List.

Setting a bit will trigger the corresponding command and will set a one-shot bit for the command in the module. This bit must be reset before being set again in order for the command to execute again.

This data is transferred continuously to the module in the module's output image.

There is a one-to-one relationship between each bit in the table and a command in the Master Command List based on the bit position in the table. The following table shows this relationship:

Page 54 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

Bit Position

199

Name

Event Commands #1

Event Commands #2

Event Commands #3

Event Commands #4

Event Commands #5

Event Commands #6

Event Commands #200

Execution status can be monitored in the same fashion as other commands in the Master Command List, via the Master Command Status block.

Successful Execution

If the command was successful (Status Code = 0x01), the status will be maintained as long as the Event Command bit is set. After the enable bit is cleared, the Status Code field will go to zero (0).

Unsuccessful Execution

If the command was unsuccessful (Status Code > 0x01), the status will be maintained until the command executes successfully. The ladder logic must 'resubmit' the command (clear the enable bit and set it again) in order for the command to execute again.

Some Modbus Plus modules are equipped with a second, redundant Modbus

Plus port. A Dual Port Modbus Plus network is implemented in the following way:

The primary network connects to Port 1 on all modules.

The secondary (backup) network connects to Port 2 on all modules.

If the primary network connected through Port 1 fails (for example, if a cable is cut or disconnected), the network connected through Port 2 will become active, maintaining the connection between devices.

Important: All Modbus Plus nodes on a network must be equipped with dual ports in order to implement redundant port operation.

ProSoft Technology, Inc.

February 19, 2008

Page 55 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

Refer to the following illustration for an example of redundant port operation on a

Modbus Plus network.

Page 56 of 101 ProSoft Technology, Inc.

February 19, 2008

5.3 RS-232 Configuration/Debug Port

Modbus Plus Communication Module

This port is physically an RJ45 connection. An RJ45 to DB-9 adapter cable is included with the module. This port permits a PC based terminal emulation program to view configuration and status data in the module and to control the module. The cable for communications on this port is shown in the following diagram:

5.3.1 Disabling the RSLinx Driver for the Com Port on the PC

The communication port driver in RSLinx can occasionally prevent other applications from using the PC's COM port. If you are not able to connect to the module's configuration/debug port using ProSoft Configuration Builder (PCB),

HyperTerminal or another terminal emulator, follow these steps to disable the

RSLinx Driver.

1 Open RSLinx and go to Communications>RSWho

2 Make sure that you are not actively browsing using the driver that you wish to stop. The following shows an actively browsed network:

ProSoft Technology, Inc.

February 19, 2008

Page 57 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

3 Notice how the DF1 driver is opened, and the driver is looking for a processor on node 1. If the network is being browsed, then you will not be able to stop this driver. To stop the driver your RSWho screen should look like this:

Branches are displayed or hidden by clicking on the or the icons.

4 When you have verified that the driver is not being browsed, go to

Communications>Configure Drivers

You may see something like this:

If you see the status as running, you will not be able to use this com port for anything other than communication to the processor. To stop the driver press the "Stop" on the side of the window:

5 After you have stopped the driver you will see the following:

Page 58 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

6 Upon seeing this, you may now use that com port to connect to the debug port of the module.

Note: You may need to shut down and restart your PC before it will allow you to stop the driver

(usually only on Windows NT machines). If you have followed all of the above steps, and it will not stop the driver, then make sure you do not have RSLogix open. If RSLogix is not open, and you still cannot stop the driver, then reboot your PC.

5.4 Modbus Plus Connections

The MVI46-MBP module has one or two physical Modbus Plus connectors

(depending on hardware configuration) with a DB-9 Female plug located on the front of the module.

Modicon provides two different Modbus Plus connectors to ease installation.

These connectors are as follows:

Modicon Part Number Description

The actual cable installation and the wiring of the cable to the connectors is fully documented in the Modicon publication Modicon Modbus Plus Network Planning and Installation Guide - Pub No. GM-Modbus Plus L-001.

If the Modicon connectors are not available during installation, the following pin out applies to the DB-9 Modbus Plus port connections:

5.5 DB9 to RJ45 Adaptor (Cable 14)

ProSoft Technology, Inc.

February 19, 2008

Page 59 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

5.6 Modbus Plus Communication Port

The MVI46-MBP module has two physical Modbus Plus connectors with two DB-

9 Female plugs located on the front of the module.

This section contains a listing of the internal database of the MVI46-MBP module. This information can be used to interface other devices to the data contained in the module.

5.7.1 Module Memory Map

Overview

Access Module Address

Range

Modbus Address

Range

Description Block

R/W 0 3999 40001 Registers

4000

4070

4069

4269

44001

44071

44070

44270

Global In Update Status

Master Command Status

R/W

4270

4300

4370

4410

4299

4369

4409

4449

44271

44301

44371

44411

44300

44370

44410

44450

Misc Module Status

Global In Update Counters

Module Configuration Block 40

Global In File Map 40

Size

4000

200

R/W

O File

I File

5090

7090

7130

7170

7089

7129

7169

7221

45091

47091

47131

47171

47090

47130

47170

47222

Master Command List

Global Out Image

Global In Image

Command Event Data

640

2000

The Data Registers area holds data collected from other nodes on the network

(master read commands or global input data) or data received from the processor (write blocks). Additionally, this data area is used as a data source for the processor (read blocks) or other nodes on the network (master write commands).

Page 60 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

Detailed definition of the status data area can be found in Status Data Definition

(page 61). These areas include the following: Global In Update Status, Master

Command Status, Misc Module Status and Global In Update Counters.

Definition of the configuration data areas can be found in Configuration Data

Definition. These data areas include the following: Module Configuration Block,

Global In File Map, Device Definition, Master Command List.

The Global Out Image is a data area of 40 words. Only the first 32 words are filled with data. This data is transferred from the processor to the module on each write block command and placed on the Modbus Plus network. This data area is used for high-speed data that must be passed to other nodes on the network at a high frequency.

The Global In Image is a data area of 40 words. Only the first 32 words are filled with data. This data is transferred from the module to the processor on each block read command. Data in the block is determined by the Global In File Map data set. This data area is used for high-speed data that must be passed to the processor at the highest frequency.

The Command Event Data area controls master commands under processor control. This data area is updated on each write block transfer from the processor to the module. Each bit in the data area corresponds to a command in the master command list. When the bit is set high, the command will be issued. When the bit is clear, the command will not execute. Event command control bits apply only to commands that have a value of two for their Enable parameter in the master command list

5.7.2 Status Data Definition

This section contains a description of the members present in the MBPStat object. This data is transferred from the module to the processor approximately every second.

Global In Update Status

Address

4000 Global In Update Stat - Device #1

4001

4002

4003

Global In Update Stat - Device #2

Global In Update Stat - Device #3

Global In Update Stat - Device #4

4004

4005

4006

4007

Global In Update Stat - Device #5

Global In Update Stat - Device #6

Global In Update Stat - Device #7

Global In Update Stat - Device #8

4008

4009

Global In Update Stat - Device #9

Global In Update Stat - Device #10

10 4010 Global In Update Stat - Device #11

- - -

60 4060 Global In Update Stat - Device #61

ProSoft Technology, Inc.

February 19, 2008

Page 61 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Address

4061 Global In Update Stat - Device #62

4062

4063

Global In Update Stat - Device #63

Global In Update Stat - Device #64

64 4064

65 4065

66 4066

67 4067

68 4068

69 4069

Status Code Definitions

Code Definition

0x02

0x04

0x08 Global Update Timeout in milliseconds

0x10 Global Data Not Configured

0x20

0x40 Invalid Global Data Length

0x80

Master Command Status

4070

4071

4072

4073

4074

4075

Master Command Status: #1

Master Command Status: #2

Master Command Status: #3

Master Command Status: #4

Master Command Status: #5

Master Command Status: #6

4076

4077

4078

4079

Master Command Status: #7

Master Command Status: #8

Master Command Status: #9

Master Command Status: #10

- - -

195 4265 Master Command Status: #196

196

197

4266

4267

Master Command Status: #197

Master Command Status: #198

198

199

4268

4269

Master Command Status: #199

Master Command Status: #200

Page 62 of 101

Reference

ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

Error Code Definition

High Byte

0x00

Low Byte

0x00

0x01

0x02

0x01

0x02

0x04

0x08

0x10

0x20

Description

Normal - Driver will reset when processing command

Command has completed successfully

No response received - Is addressed unit online program access denied exception response received invalid node type in routing path slave rejected the Modbus command - invalid input path?? initiated transaction forgotten by slave

0x40

0x80

0x04 unexpected master output path received unexpected response received

0x01

0x02

Invalid Configuration for Command

Invalid Command Type - 1 = Write, 2 = Read , All other error

0x04

0x08

0x10

0x20

0x40

0x80

Miscellaneous Module Status

ProSoft Technology, Inc.

February 19, 2008

4270

4272

4273

4274-L

4275-H

4275-L

4276-H

4276-L

4277

4278

4279

4280

4281

4282

4283

4284

4285

4286

4287

Module Status - Software Reset Response

Token Pass Counter

Token Rotation Time in milliseconds

Communication Retry Counter

No Response Received Error Counter

Good Received Packet Success Counter

Unexpected Path Error Counter

Exception Response Received Error Counter

Data master output path 1 & 2 counter

Data master output path 3 & 4 counter

Data master output path 5 & 6 counter

Data master output path 7 & 8 counter

Data slave output path 1 & 2 counter

Data slave output path 3 & 4 counter

Data slave output path 5 & 6 counter

Data slave output path 7 & 8 counter

Global Out Update Status

Global Out Update Counter

Data transfer read counter

Page 63 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

4288

4289

4292

Data transfer write counter

Data parse counter

Data transfer error counter

Reference

4297

4298

4299

MBP Update Processing Time

Global In Update Time

Global Out Update Time

Module Status Values

Normal Operation

Code Description

Interface Crash Codes

Code Description

0x01

0x02

2-second interface timeout

Bad interface opcode

0x04

0x05

0x06

0x07

0x08

0x09

0x0A

0X0B

Interface test error

Interface x-fer done error

Bad interface path

Bad interface state

Bad interface length

Global data length error

Global data address error

Global data not present

Fatal Crash Codes

Code Description

0x81

0x82

PROM checksum error

Internal RAM data test error

0x83

0x84

0x85

0x86

0x87

0x88

0x89

0x8A

0X8B

0X8C

0X8D

External RAM data test error

External RAM address test error

Bad confidence test index

External Int0 event error

External Int1 event error

DMA Int0 event error

Comm. Int event error

Xmit-no good event error

No response timeout MAC State

No response timeout MAC idle

Receive OK MAC state

Page 64 of 101 ProSoft Technology, Inc.

February 19, 2008

Code Description

0X8E Transmit OK MAC state

0X8F

0X90

0X91

No receive buffer free

Bad input transfer length

Reserved rev buffer error

0X92

0X93

0X94

0X95

0X96

0X97

0X98

Bad trans control state

Bad word request bit

Node queue overflow

Bad data queue error

Empty data path error

Bad path search index

Bad data slave path

Peer Status Codes

Code Description

Monitor link operation

Normal link operation

Never getting token

Global Out Update Status

Code Description

Modbus Plus Communication Module

0x08

0x10

0x40

Global update timeout (not transmitted in 500 milliseconds)

Global data not configured (length set to zero)

Invalid Global Data Length (Length > 32 words)

Global In Update Counters

4300

4301

4302

4303

4304

4305

4306

Global In Update Counter - Device #1

Global In Update Counter - Device #2

Global In Update Counter - Device #3

Global In Update Counter - Device #4

Global In Update Counter - Device #5

Global In Update Counter - Device #6

Global In Update Counter - Device #7

4307

4308

4309

4310

Global In Update Counter - Device #8

Global In Update Counter - Device #9

Global In Update Counter - Device #10

Global In Update Counter - Device #11

- - -

60 4360 Global In Update Counter - Device #61

ProSoft Technology, Inc.

February 19, 2008

Page 65 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

4361

4362

4363

Global In Update Counter - Device #62

Global In Update Counter - Device #63

Global In Update Counter - Device #64

Reference

This section contains listings of the MVI46-MBP module's database that is related to the module's configuration. This data is available to any node on the network.

General Configuration

Address

Modbus

Address

Parameter Description

4370 44371 Module Command

Word

4371 44372 Local Modbus

Plus Node

Address (1 to 64)

4372 44373 Global Output File

Length (0 or 1 to

32)

4373 44374 Global Out

Update Timing

4374 44375 Input File Length

(0 or 1 to 32)

This register controls the module from a remote device. The value placed in the register will be processed and then set to zero after the function requested has been performed. The following function codes are currently supported:

9997=transfer module configuration to processor,

9998=warm boot module and 9999=cold boot module.

This value defines the Modbus Plus Node Address for the module. A valid node address must be entered for the module to operate, and the address must be unique on the network. Valid values are between 1 and 64, inclusive.

This value defines the number of Global Output words to be placed on the Modbus Plus network. If the value is set to 0, no global output data will be placed on the network. Values of 1 to 32 represent the number of words to be used by the module.

This data must be transferred from the processor to the module.

This parameter determines the frequency of update of the Global Output Data from the processor to the Modbus Plus Chipset. This value should be set to zero to provide the fastest possible update of this data from the processor to the network. Valid values for this parameter are 0 to 65535 milliseconds.

This value defines the number of words to be transferred by the module to the processor in the

In File section of the input image. Valid values for this parameter are 0 to 32. For most applications, a value of 32 is used.

Page 66 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

Address

Modbus

Address

Parameter Description

4375 44376 Input File Update

Timing

4376 44377 Global In Update

Timeout

This parameter is not used by the MVI46-MBP module as the In File data is updated with each new input image sent to the processor.

This value defines the timeout period (0 to 65535 milliseconds) for receiving Global Input Data from other nodes on the network. After the timeout period has been exceeded, the Timeout Error will be returned in the Global In Update Status data set. A value of 0 will result in the default value of

1000 milliseconds (1 second).

4377 44378 Spare

4378 44379 Spare

4379 44380 Spare

4380 44381 Number of Nodes

Defined in the

Device Definition

File

4381 44382 Number of Master

Commands

4382 44383 Number of Master

Data Paths

Maximum

4383 44384 Master Command

Timeout Preset

4384 44385 Read Block Start

4385 44386 Read Block

4386 44387 Read Block

Maximum Count

4387 44388 Write Block Start

This value specifies the number of devices to consider in the Device Definition Table. Valid range for this parameter is 0 to 64 inclusive. These node definitions are used by several modes of operation of the module.

This parameter specifies the number of commands to be processed in the Master

Command List. The module will only process this many commands starting with the first one in the list. If the value is set to zero, the Master

Command Mode will be disabled. Valid values for this parameter are 0 to 200.

This value defines the number of Master Data

Paths that will be made available to the module's

Master Mode Driver by the Modbus Plus Chipset.

Valid values for this parameter are 1 to 8. A value of zero will result in the default value of 8.

This parameter defines the number of milliseconds

(0 to 65535) to wait for a response to a master command issued by the module on the network. If a timeout condition exists for a command, it will be reflected in the Master Command List Status data area. A value of 0 will result in a value of 1000 (1 second) for the parameter.

This parameter specifies the module's start address where data will be read from and transferred to the processor. Valid values for this parameter are 0 to 3999. This is a read-only value and can only be set in the processor.

This parameter specifies the number of registers to transfer from the module's database to the processor. This is a read-only value and can only be set in the processor.

This read-only value specifies the number of blocks of 200-word data are to be transferred from the module to the processor.

This read-only parameter specifies the starting register in the module's database where data will be transferred from the processor to the module.

ProSoft Technology, Inc.

February 19, 2008

Page 67 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

Address

Modbus

Address

Parameter Description

4388 44389 Write Block

4389 44390 Write Block

Maximum Count

4390 44391 Block Transfer

Failure Count

This read-only parameter specifies the number of registers to set in the module's database from the processor.

This read-only value specifies the number of blocks of 200-word data are to be transferred from the processor to the module.

This read-only parameter specifies the number of successive transfer errors must occur before the

Modbus Plus network communications ceases. If the value is set to zero, communications will never be disabled. A value from 1 to 65535 indicates the number of successive errors that will result in the communications shutdown.

4391 44392 Spare

- - -

4409 44410 Spare

These registers are not assigned for use in the

MVI46-MBP database

Global In File Map

Address

Modbus

Address

Parameter Description

Input File Data.

1 Module's database register address for Word 1 of

Input File Data.

2 Module's database register address for Word 2 of

Input File Data.

- -

Input File Data.

31 Module's database register address for Word 31 of

Input File Data.

4442 44443 Spare

- -

4449 44450 Spare

Page 68 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

Device Definition

The Device Definition table consists of 64 blocks of data with each block containing the information for a single device to interface with on the network.

The following table describes the starting addresses of each block of data.

Parameter Description DB

Address

4450

Modbus

Address

44451

4460

4470

4480

4490

4500

4510

4520

4530

4540

4550

4560

4570

4580

4590

4600

4610

4620

4630

4640

4650

4660

4670

44461

44471

44481

44491

44501

44511

44521

44531

44541

44551

44561

44571

44581

44591

44601

44611

44621

44631

44641

44651

44661

44671

Device Def ID 0

Device Def ID 1

Device Def ID 2

Device Def ID 3

Device Def ID 4

Device Def ID 5

Device Def ID 6

Device Def ID 7

Device Def ID 8

Start register of device definition block for device index 0

Start register of device definition block for device index 1

Start register of device definition block for device index 2

Start register of device definition block for device index 3

Start register of device definition block for device index 4

Start register of device definition block for device index 5

Start register of device definition block for device index 6

Start register of device definition block for device index 7

Start register of device definition block for device index 8

Device Def ID 9 Start register of device definition block for device index 9

Device Def ID 10 Start register of device definition block for device index 10

Device Def ID 11 Start register of device definition block for device index 11

Device Def ID 12 Start register of device definition block for device index 12

Device Def ID 13 Start register of device definition block for device index 13

Device Def ID 14 Start register of device definition block for device index 14

Device Def ID 15 Start register of device definition block for device index 15

Device Def ID 16 Start register of device definition block for device index 16

Device Def ID 17 Start register of device definition block for device index 17

Device Def ID 18 Start register of device definition block for device index 18

Device Def ID 19 Start register of device definition block for device index 19

Device Def ID 20 Start register of device definition block for device index 20

Device Def ID 21 Start register of device definition block for device index 21

Device Def ID 22 Start register of device definition block for device index 22

ProSoft Technology, Inc.

February 19, 2008

Page 69 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Address

4680

Modbus

Address

44681

Parameter Description

4690

4700

4710

4720

4730

4740

4750

4760

4770

4780

4790

4800

4810

4820

4830

4840

4850

4860

4870

4880

4890

4900

4910

4920

4930

44691

44701

44711

44721

44731

44741

44751

44761

44771

44781

44791

44801

44811

44821

44831

44841

44851

44861

44871

44881

44891

44901

44911

44921

44931

Reference

Device Def ID 23 Start register of device definition block for device index 23

Device Def ID 24 Start register of device definition block for device index 24

Device Def ID 25 Start register of device definition block for device index 25

Device Def ID 26 Start register of device definition block for device index 26

Device Def ID 27 Start register of device definition block for device index 27

Device Def ID 28 Start register of device definition block for device index 28

Device Def ID 29 Start register of device definition block for device index 29

Device Def ID 30 Start register of device definition block for device index 30

Device Def ID 31 Start register of device definition block for device index 31

Device Def ID 32 Start register of device definition block for device index 32

Device Def ID 33 Start register of device definition block for device index 33

Device Def ID 34 Start register of device definition block for device index 34

Device Def ID 35 Start register of device definition block for device index 35

Device Def ID 36 Start register of device definition block for device index 36

Device Def ID 37 Start register of device definition block for device index 37

Device Def ID 38 Start register of device definition block for device index 38

Device Def ID 39 Start register of device definition block for device index 39

Device Def ID 40 Start register of device definition block for device index 40

Device Def ID 41 Start register of device definition block for device index 41

Device Def ID 42 Start register of device definition block for device index 42

Device Def ID 43 Start register of device definition block for device index 43

Device Def ID 44 Start register of device definition block for device index 44

Device Def ID 45 Start register of device definition block for device index 45

Device Def ID 46 Start register of device definition block for device index 46

Device Def ID 47 Start register of device definition block for device index 47

Device Def ID 48 Start register of device definition block for device index 48

Page 70 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

45031

45041

45051

45061

45071

45081

Modbus

Address

44941

44951

44961

44971

44981

44991

45001

45011

45021

5030

5040

5050

5060

5070

5080

Address

4940

4950

4960

4970

4980

4990

5000

5010

5020

Parameter Description

Device Def ID 49 Start register of device definition block for device index 49

Device Def ID 50 Start register of device definition block for device index 50

Device Def ID 51 Start register of device definition block for device index 51

Device Def ID 52 Start register of device definition block for device index 52

Device Def ID 53 Start register of device definition block for device index 53

Device Def ID 54 Start register of device definition block for device index 54

Device Def ID 55 Start register of device definition block for device index 55

Device Def ID 56 Start register of device definition block for device index 56

Device Def ID 57 Start register of device definition block for device index 57

Device Def ID 58 Start register of device definition block for device index 58

Device Def ID 59 Start register of device definition block for device index 59

Device Def ID 60 Start register of device definition block for device index 60

Device Def ID 61 Start register of device definition block for device index 61

Device Def ID 62 Start register of device definition block for device index 62

Device Def ID 63 Start register of device definition block for device index 63

Device Definition Block Format

The structure of the data in each block is described in the following table:

Address

Modbus

Address

Parameter Description

These values determine the network route that a message will use to get from the module to a node on the network. The values are entered directly into the Modbus Plus message. Note the following:

PLCs: When addressing these devices, the last non-zero byte in the routing list specifies the network node address. For example, to reach node 7 on the network, enter 7, 0, 0, 0, 0.

ModConnect Type Devices : When addressing these devices (including other MVI46-MBP modules), the next-to-last non-zero values specifies the node address and the last non-zero value specifies the slave data path to use (1 to 8).

If the slave path is set incorrectly the message will fail. For example, to reach slave path 1 on node 6, enter values of 6, 1, 0, 0, 0.

ProSoft Technology, Inc.

February 19, 2008

Page 71 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

Address

Modbus

Address

Parameter Description

4456 44457

Type This parameter is ignored in the current version of the software. It may be required in future releases to customize communication for non-compliant devices.

Global In Length This parameter sets the length of global data accepted from the specified node. If a value of zero is entered, no global data will be accepted from this node. A value of 1 to 32 indicate that global data is to be expected from the module and the length of data to accept is set in this parameter.

4457 44458 Global In Storage

Address

This parameter specifies the starting address in the module's database where the received global data will be placed. Valid locations are from 0 to

3999.

4458 44459 Spare

4459 44460 Spare

Master Command List

The next data set present in the module's database is the master command list.

Each command requires a block of ten registers in the database to describe the command. There are 200 commands that can be defined in the module.

Therefore, this data occupies 2000 registers. The starting locations for the commands is shown in the following table:

Address

5090

5100

5110

5120

5130

7080

Modbus

Address

45091

45101

45111

45121

45131

Parameter Description

Cmd # 0

Cmd # 1

Cmd # 2

Cmd # 3

Cmd # 4

5140 45141 Cmd # 5

- -

7060

7070

47061

47071

Cmd # 197

Cmd # 198

47081 Cmd # 199

Start of command block for command # 0

Start of command block for command # 1

Start of command block for command # 2

Start of command block for command # 3

Start of command block for command # 4

Start of command block for command # 5

Start of command block for command # 197

Start of command block for command # 198

Start of command block for command # 199

The data structure associated with each command block is described in the following table:

Page 72 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

Address

Modbus

Address

Parameter Description

5090 45091 Enable

5091 45092 Module's

Database

This parameter is used define if the command will be executed or will be disregarded. The following values are valid: 0=Disables the command and it will not execute; 1=The command will be considered for execution each scan of the command list and will be controlled by the PollInt parameter; and 2=The command will only execute if the event control bit for the command is set.

This parameter specifies the starting internal register address to be associated with the command. Valid entry for this parameter is 0 to

3999. seconds to wait between the execution of continuous commands (Enable=1). This poll interval command can be used to lighten the communications load on a busy network. Valid entry for this parameter is 0 to 65535. be considered by the command. Valid entry for this parameter is 1 to 100.

Code This parameter is not implemented in the current version of the software but will be used in the future to swap the bytes of word and double-word values when floating-point data is required. device defined in the device definition table

(Device[ ] in the MBPlusModuleDef object). The index defined in this parameter sets the route path defined for the device in the Modbus Plus message.

5097 45098 Register Address in Device performed by the command. Valid entries are 3=

Read register data from a node and 16= Write register data to a node.

This parameter defines the starting address in the device being considered by the command. Values entered in this field are dependent on the node's database definition. Refer to the specific manufacture's database definition for the device to determine the location of the data to be interfaced.

5098 45099 Spare

5099 45100 Spare

ProSoft Technology, Inc.

February 19, 2008

Page 73 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

Global Output Data transmitted from the MVI46-MBP module to the network is located at registers 7090 to 7121 in the module's database. This data is globally broadcast to all active nodes on the network.

Destination nodes can be configured to accept or ignore incoming data from specific source nodes. Data is transferred from the processor to the module in each new output image block. The following table shows the database registers used by this data.

Global Out Image

Address

Modbus

Address

Ox Output

Table Offset*

7090 47091 O:x.0

7091 47092 O:x.1

7092 47093 O:x.2

7093 47094 O:x.3

7094 47095 O:x.4

- - -

7121 47122 O:x.31

Parameter Description

Global Out 0

Global Out 1

Global Out 2

Global output data for module word # 0

Global output data for module word # 1

Global output data for module word # 2

Global Out 3

Global Out 4

Global output data for module word # 3

Global output data for module word # 4

Global Out 31 Global output data for module word # 31

7122 47123

7123 47124

7124 47125

7125 47126

7126 47127

7127 47128

7128 47129

7129 47130

* x = the slot number in the chassis where the module is installed.

The MVI46-MBP module transfers up to 32 words of data in each new input image block sent to the processor. Incoming data from each source node can be indexed into up to eight fields for delivery into separate data destinations in the receiving node. Nodes configured for global input can request up to 32 words from each node up to a maximum of 500 words.

The data used to construct is block is determined by the Input File Map data set.

The data transferred to the processor is located in the module's database at registers 7130 to 7161. The following table describes the register locations for this data in the module's database:

Page 74 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

Global In Image

Address

Modbus

Address

Ix Input Table

Offset*

Parameter Description

In File Word 0

In File Word 1

In File Word 2

In File Word 3

In File Word 31

Data from Input File Map index 0 for word 0

Data from Input File Map index 1 for word 1

Data from Input File Map index 2 for word 2

Data from Input File Map index 3 for word 3

Data from Input File Map index 31 for word 31

7162 47163

7163 47164

7164 47165

7165 47166

7166 47167

7167 47168

7168 47169

7169 47170

* x = the slot number in the chassis where the module is installed.

5.7.6 Command Event Data

The command event data controls the master command list. If a command is set to be controlled by events, then the status of the bits contained in this data set enable the command for a single instance. Each bit in the event data set is associated with an individual command. When the bit is set, the command will be issued once. The bit must be cleared and set again for the command to be issued again. The first thirteen words of data area associated with the event command data set contain these control bits. The remainder of the data area holds data associated with each event. The following table describes the event data area:

Command Event Control

7175

7176

7177

7178

7179

7180

Address

7170

7171

7172

7173

7174

Modbus

Address

47171

47172

47173

47174

47175

47176

47177

47178

47179

47180

47181

Parameter Description

Event Control Word #0 Event control bits for commands 0 to 15

Event Control Word #1 Event control bits for commands 16 to 31

Event Control Word #2 Event control bits for commands 32 to 47

Event Control Word #3 Event control bits for commands 48 to 63

Event Control Word #4 Event control bits for commands 64 to 79

Event Control Word #5 Event control bits for commands 80 to 95

Event Control Word #6 Event control bits for commands 96 to 111

Event Control Word #7 Event control bits for commands 112 to 127

Event Control Word #8 Event control bits for commands 128 to 143

Event Control Word #9 Event control bits for commands 144 to 159

Event Control Word #10 Event control bits for commands 160 to 175

ProSoft Technology, Inc.

February 19, 2008

Page 75 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

7200

7201

7202

7203

7204

7205

7206

7192

7193

7194

7195

7196

7197

7198

7199

7185

7186

7187

7188

7189

7190

7191

Address

7181

7182

7183

7184

7214

7215

7216

7217

7218

7219

7220

7221

7207

7208

7209

7210

7211

7212

7213

Page 76 of 101

47201

47202

47203

47204

47205

47206

47207

47193

47194

47195

47196

47197

47198

47199

47200

Modbus

Address

47182

47183

47184

47185

47186

47187

47188

47189

47190

47191

47192

47215

47216

47217

47218

47219

47220

47221

47222

47208

47209

47210

47211

47212

47213

47214

Parameter Description

Reference

Event Control Word #11 Event control bits for commands 176 to 191

Event Control Word #12 Event control bits for commands 192 to 199

Event Done Word #0

Event Done Word #1

Event done bits for commands 0 to 15

Event done bits for commands 16 to 31

Event Done Word #2

Event Done Word #3

Event Done Word #4

Event Done Word #5

Event done bits for commands 32 to 47

Event done bits for commands 48 to 63

Event done bits for commands 64 to 79

Event done bits for commands 80 to 95

Event Done Word #6

Event Done Word #7

Event Done Word #8

Event Done Word #9

Event Done Word #10

Event Done Word #11

Event Done Word #12

Event done bits for commands 96 to 111

Event done bits for commands 112 to 127

Event done bits for commands 128 to 143

Event done bits for commands 144 to 159

Event done bits for commands 160 to 175

Event done bits for commands 176 to 191

Event done bits for commands 192 to 199

Event Err Word #0

Event Err Word #1

Event Err Word #2

Event Err Word #3

Event Err Word #4

Event Err Word #5

Event Err Word #6

Event Err Word #7

Event Err Word #8

Event Err Word #9

Event Err Word #10

Event Err Word #11

Event Err Word #12

Event One Shot #0

Event One Shot #1

Event error bits for commands 0 to 15

Event error bits for commands 16 to 31

Event error bits for commands 32 to 47

Event error bits for commands 48 to 63

Event error bits for commands 64 to 79

Event error bits for commands 80 to 95

Event error bits for commands 96 to 111

Event error bits for commands 112 to 127

Event error bits for commands 128 to 143

Event error bits for commands 144 to 159

Event error bits for commands 160 to 175

Event error bits for commands 176 to 191

Event error bits for commands 192 to 199

Event one shot bits for commands 0 to 15

Event one shot bits for commands 16 to 31

Event One Shot #2

Event One Shot #3

Event One Shot #4

Event One Shot #5

Event One Shot #6

Event One Shot #7

Event One Shot #8

Event One Shot #9

Event One Shot #10

Event One Shot #11

Event One Shot #12

Event one shot bits for commands 32 to 47

Event one shot bits for commands 48 to 63

Event one shot bits for commands 64 to 79

Event one shot bits for commands 80 to 95

Event one shot bits for commands 96 to 111

Event one shot bits for commands 112 to 127

Event one shot bits for commands 128 to 143

Event one shot bits for commands 144 to 159

Event one shot bits for commands 160 to 175

Event one shot bits for commands 176 to 191

Event one shot bits for commands 192 to 199

ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

This section contains forms that aid in the design of applications using the

MVI46-MBP module:

Global Input File Map

N20 Word Description Value

0 Module Command Word

1 Local Modbus Plus Node

Address (1 to 64)

2 Global Output File Length (0 or 1 to 32)

3 Global Out Update Timing

4 Input File Length (0 or 1 to

32)

Input File Update Timing

Global In Update Timeout

Spare

10 Number of Nodes Defined in the Device Definition File

11 Number of Master

Commands

12 Number of Master Data

Paths Maximum

13 Master Command Timeout

Preset

14 Spare

Spare

19 Spare

20 Block Transfer Failure

Count

Spare

ProSoft Technology, Inc.

February 19, 2008

Word Description

Global In Source Addr

Value

Page 77 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

N20 Word Description

Spare

Value

Spare

Module Command Word

9000: Module Configuration Request

9001: Module Configuration Ready

9997: Read Configuration from M1 File

9998: Warm Boot Module

9999: Cold Boot Module

Word Description

Global In Source Addr

Not Used

Reference

Device Definition Configuration

N21 0 1 2 3 4 5 6 7 8 9

SLC

Address

0 to 9

10 to 19

20 to 29

30 to 39

40 to 49

50 to 59

60 to 69

70 to 79

80 to 89

90 to 99

100 to 109 10

Device

Number

110 to 119 11

120 to 129 12

130 to 139 13

140 to 149 14

150 to 159 15

160 to 169 16

170 to 179 17

Route

Route Route Route Device

3 4 5 Type

Global

Length

Global

Dest

Not Not

Used Used

Value

Page 78 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

N21 0 1 2 3 4 5 6 7 8 9

SLC

Address

Device

Number

180 to 189 18

190 to 199 19

200 to 209 20

210 to 219 21

220 to 229 22

230 to 239 23

240 to 249 24

Route

Route Route Route Device

3 4 5 Type

Global Global

Length Dest

Not

Used

Not

Used

N22 0 1 2 3 4 5 6 7 8 9

SLC

Address

0 to 9

10 to 19

20 to 29

30 to 39

40 to 49

50 to 59

60 to 69

70 to 79

80 to 89

90 to 99

100 to 109 35

Device

Number

110 to 119 36

120 to 129 37

130 to 139 38

140 to 149 39

150 to 159 40

160 to 169 41

170 to 179 42

180 to 189 43

190 to 199 44

200 to 209 45

210 to 219 46

220 to 229 47

230 to 239 48

240 to 249 49

Route

Route Route Route Device

3 4 5 Type

Global Global

Length Dest

Not

Used

Not

Used

ProSoft Technology, Inc.

February 19, 2008

Page 79 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

N23 0 1 2 3 4 5 6 7 8 9

SLC

Address

0 to 9

10 to 19

20 to 29

30 to 39

40 to 49

50 to 59

60 to 69

70 to 79

80 to 89

90 to 99

100 to 109 60

110 to 119 61

120 to 129 62

130 to 139 63

Device

Number

Route

Route Route Route Device

3 4 5 Type

Global

Length

Global

Dest

Not Not

Used Used

Master Command List

SLC

Address

Cmd Enable DB

Code Address

Poll

Interval

Reg

Count

0 to 9 0

10 to 19 1

20 to 29 2

30 to 39 3

40 to 49 4

50 to 59 5

60 to 69 6

70 to 79 7

80 to 89 8

90 to 99 9

100 to 109 10

110 to 119 11

120 to 129 12

130 to 139 13

140 to 149 14

150 to 159 15

160 to 169 16

170 to 179 17

180 to 189 18

190 to 199 19

200 to 209 20

Swap

Code

Device

Index

Func

Code

Dev

Reg

Page 80 of 101

Spare Spare

ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

SLC

Address

Cmd Enable DB

Code Address

Poll

Interval

Reg

Count

210 to 219 21

220 to 229 22

230 to 239 23

240 to 249 24

Swap

Code

Device

Index

Func

Code

Dev

Reg

Spare Spare

SLC

Address

Cmd Enable DB

Code Address

Poll

Interval

Reg

Count

0 to 9 25

10 to 19 26

20 to 29 27

30 to 39 28

40 to 49 29

50 to 59 30

60 to 69 31

70 to 79 32

80 to 89 33

90 to 99 34

100 to 109 35

110 to 119 36

120 to 129 37

130 to 139 38

140 to 149 39

150 to 159 40

160 to 169 41

170 to 179 42

180 to 189 43

190 to 199 44

200 to 209 45

210 to 219 46

220 to 229 47

230 to 239 48

240 to 249 49

Swap

Code

Device

Index

Func

Code

Dev

Reg

Spare Spare

ProSoft Technology, Inc.

February 19, 2008

Page 81 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

SLC

Address

Cmd Enable DB

Code Address

Poll

Interval

Reg

Count

0 to 9 50

10 to 19 51

20 to 29 52

30 to 39 53

40 to 49 54

50 to 59 55

60 to 69 56

70 to 79 57

80 to 89 58

90 to 99 59

100 to 109 60

110 to 119 61

120 to 129 62

130 to 139 63

140 to 149 64

150 to 159 65

160 to 169 66

170 to 179 67

180 to 189 68

190 to 199 69

200 to 209 70

210 to 219 71

220 to 229 72

230 to 239 73

240 to 249 74

Swap

Code

Device

Index

Func

Code

Dev

Reg

Spare Spare

SLC

Address

Cmd Enable DB

Code Address

Poll

Interval

Reg

Count

0 to 9 75

10 to 19 76

20 to 29 77

30 to 39 78

40 to 49 79

50 to 59 80

60 to 69 81

70 to 79 82

80 to 89 83

90 to 99 84

100 to 109 85

Swap

Code

Device

Index

Func

Code

Dev

Reg

Spare Spare

Page 82 of 101 ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

SLC

Address

Cmd Enable DB

Code Address

Poll

Interval

Reg

Count

110 to 119 86

120 to 129 87

130 to 139 88

140 to 149 89

150 to 159 90

160 to 169 91

170 to 179 92

180 to 189 93

190 to 199 94

200 to 209 95

210 to 219 96

220 to 229 97

230 to 239 98

240 to 249 99

Swap

Code

Device

Index

Func

Code

Dev

Reg

Spare Spare

SLC

Address

Cmd Enable DB

Code Address

Poll

Interval

Reg

Count

0 to 9 100

10 to 19 101

20 to 29 102

30 to 39 103

40 to 49 104

50 to 59 105

60 to 69 106

70 to 79 107

80 to 89 108

90 to 99 109

100 to 109 110

110 to 119 111

120 to 129 112

130 to 139 113

140 to 149 114

150 to 159 115

160 to 169 116

170 to 179 117

180 to 189 118

190 to 199 119

200 to 209 120

210 to 219 121

Swap

Code

Device

Index

Func

Code

Dev

Reg

Spare Spare

ProSoft Technology, Inc.

February 19, 2008

Page 83 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

SLC

Address

Cmd Enable DB

Code Address

Poll

Interval

Reg

Count

220 to 229 122

230 to 239 123

240 to 249 124

Swap

Code

Device

Index

Func

Code

Dev

Reg

Spare Spare

SLC

Address

Cmd Enable DB

Code Address

Poll

Interval

Reg

Count

0 to 9 125

10 to 19 126

20 to 29 127

30 to 39 128

40 to 49 129

50 to 59 130

60 to 69 131

70 to 79 132

80 to 89 133

90 to 99 134

100 to 109 135

110 to 119 136

120 to 129 137

130 to 139 138

140 to 149 139

150 to 159 140

160 to 169 141

170 to 179 142

180 to 189 143

190 to 199 144

200 to 209 145

210 to 219 146

220 to 229 147

230 to 239 148

240 to 249 149

Swap

Code

Device

Index

Func

Code

Dev

Reg

Spare Spare

SLC

Address

Cmd Enable DB

Code Address

Poll

Interval

Reg

Count

0 to 9 150

10 to 19 151

20 to 29 152

30 to 39 153

40 to 49 154

Swap

Code

Device

Index

Func

Code

Page 84 of 101

Dev

Reg

Spare Spare

ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

SLC

Address

Cmd Enable DB

Code Address

Poll

Interval

Reg

Count

50 to 59 155

60 to 69 156

70 to 79 157

80 to 89 158

90 to 99 159

100 to 109 160

110 to 119 161

120 to 129 162

130 to 139 163

140 to 149 164

150 to 159 165

160 to 169 166

170 to 179 167

180 to 189 168

190 to 199 169

200 to 209 170

210 to 219 171

220 to 229 172

230 to 239 173

240 to 249 174

Swap

Code

Device

Index

Func

Code

Dev

Reg

Spare Spare

SLC

Address

Cmd Enable

Code to 175

Address

Poll

Interval

Reg

Count

Swap

Code

Device

Index

Func

Code

Dev

Reg

Spare Spare

100 185

110 186

120 187

130 188

140 189

150 190

ProSoft Technology, Inc.

February 19, 2008

Page 85 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

Reference

SLC

Address

Cmd Enable DB

Code Address

Poll

Interval

Reg

Count

160 191

170 192

180 193

190 194

200 195

210 196

220 197

230 198

240 199

Swap

Code

Device

Index

Func

Code

Dev

Reg

Spare Spare

User Command List

SLC Address Cmd DB

Reg

Count

Swap

Code

0 to 9

10 to 19

20 to 29

30 to 39

40 to 49

50 to 59

60 to 69

70 to 79

80 to 89

90 to 99

100 to 109 10

110 to 119 11

120 to 129 12

130 to 139 13

140 to 149 14

150 to 159 15

160 to 169 16

170 to 179 17

180 to 189 18

190 to 199 19

200 to 209 20

210 to 219 21

220 to 229 22

230 to 239 23

240 to 249 24

Dev

Index

Func

Code

Dev

Reg

Page 86 of 101

Spare Spare Spare Spare

ProSoft Technology, Inc.

February 19, 2008

Modbus Plus Communication Module

5.9.1 How is data transferred between the SLC and the MVI46-MBP?

The transfer of data is performed using the module M0 and M1 files across the backplane. So the M1 file is a copy of the module internal database and the M0 file is used for module control from ladder logic.

5.9.2 How many registers can be used for user data?

The first 4000 registers (0 to 3999) can be used to store user data.

5.9.3 How is new configuration data written to the MVI46-MBP module?

The SLC data files should be used to store the configuration data. When the module performs a restart operation (either through a cold boot or warm boot) it will request configuration data to the SLC by moving a value of 9000 to register

4370 of M1 file. When this happens, the ladder logic should copy the configuration data to the module (general configuration, global in file map, device definition and master command list). After the configuration data is copied, the ladder logic should place a value of 9001 to register 4370 of M1 file in order to flag the end of the operation.

5.9.4 How is the current module configuration copied to the SLC memory?

The user should select option 'Y' (Transfer module cfg to processor) using the debug terminal to initiate the transfer. At this point, the module sets a value of -

9000 to word 4370 of the M1 file. Ladder logic must recognize this value and the move the configuration data from the M1 file to the SLC data file (general configuration, global in file map, device definition and master command list). The order of the registers is the same as defined the Reference chapter - Memory

Definition. After the data is copied to the SLC memory, the ladder logic must move a value of 0 to word 4370 of the M1 file in order to flag the end of the operation.

5.9.5 Why do I get an error code 3 every time I try to send configuration data from the module to the processor and no data is moved?

Look at the ladder logic and make sure the ladder logic moves a value of 0 to word 4370 of the M1 file in order to flag the end of the operation.

ProSoft Technology, Inc.

February 19, 2008

Page 87 of 101

MVI46-MBP ♦ SLC Platform

Modbus Plus Communication Module

5.9.6 Is it possible to create and send commands from the ladder logic?

Reference

Yes. You can create your own commands in the SLC memory and send these commands using block 9002. Up to 6 commands can be sent at each scan using block 9902.

5.9.7 Is it possible to disable and enable commands in ladder?

Yes. The user can disable or enable commands that are configured in the Master

Command List using ladder logic. Block 9010 disable commands (enable code

=0), block 9011 enable commands (enable code =1) and block 9012 enable commands (enable code = 2). Up to 60 commands may be enabled/disabled using these blocks.

Another way to enable commands is by using the ladder logic to send a command execution block (block 9003). This block puts commands that are configured in the Master Command List on a high priority basis in the command queue even if these commands are disabled.

Refer to the user manual for information on how to use blocks 9010, 9011, 9012 and 9003.

5.9.8 After I disable (or enable) a specific command, how do I check the status of the command?

Use the debug port to view the Master Command List to determine if the command is currently disabled or enabled.

5.9.9 What happens if the MVI46-MBP module performs a

COLDBOOT or WARMBOOT after commands have been disabled by the ladder?

The new ENABLE code for each command will be sent to the module.

5.9.10 Does the MVI46-MBP operate as a Master and Slave simultaneously?

Yes. If the module starts receiving commands on the MBP port, it starts to operate as a Slave. If the MVI46-MBP sends commands, it operates as a Master.

Therefore, no specific configuration is required to set the module as a Master or

Slave.

Page 88 of 101 ProSoft Technology, Inc.

February 19, 2008