ProSoft Technology MVI69-DFCM User manual

MVI69-DFCM
CompactLogix Platform
DF1 Interface Module
User Manual

Please Read This Notice
Successful application of this module requires a reasonable working knowledge of the Allen-
Bradley CompactLogixhardware and the application in which the combination is to be used.
For this reason, it is important that those responsible for implementation, satisfy themselves that
the combination will meet the needs of the application without exposing personnel or equipment
to unsafe or inappropriate working conditions.
This manual is provided to assist the user. Every attempt has been made to assure that the
information provided is accurate and a true reflection of the product’s installation requirements. In
order to assure a complete understanding of the operation of the product, the user should read all
applicable Allen-Bradley documentation on the operation of the A-B hardware.
Under no circumstances will ProSoft Technology, Inc. be responsible or liable for indirect or
consequential damages resulting from the use or application of the product.
Reproduction of the contents of this manual, in whole or in part, without written permission from
ProSoft Technology, Inc. is prohibited.
Information in this manual is subject to change without notice and does not represent a
commitment on the part of ProSoft Technology, Inc. Improvements and/or changes in this
manual or the product may be made at any time. These changes will be made periodically to
correct technical inaccuracies or typographical errors.
ProSoft Technology, Inc.
1675 Chester Avenue, 4th Floor
Bakersfield, CA 93301
[phone]
[phone] (Fax)
www.prosoft-technology.com
InRAxis a trademark of ProSoft Technology, Inc.
CompactLogixis a trademark of Allen-Bradley Company, Inc.
All other trademarks in the document are the properties of their respective owners/companies.
Copyright 2004 ProSoft Technology, Inc. All rights reserved.
MVI69-DFCM User Manual
June 24, 2004
ii

Table of Contents
Table of Contents
1PRODUCT SPECIFICATIONS.............................................................................. 1
1.1 GENERAL SPECIFICATIONS................................................................................... 1
1.1.1 Slave Functional Specifications.................................................................. 1
1.1.2 Master Functional Specifications ............................................................... 1
1.1.3 Physical....................................................................................................... 2
1.1.4 CompactLogix Interface.............................................................................. 2
1.2 HARDWARE SPECIFICATIONS ............................................................................... 2
2FUNCTIONAL OVERVIEW .................................................................................. 3
2.1 GENERAL CONCEPTS............................................................................................ 3
2.1.1 Module Power Up....................................................................................... 3
2.1.2 Main Logic Loop......................................................................................... 3
2.1.3 Backplane Data Transfer............................................................................ 4
2.2 NORMAL DATA TRANSFER .................................................................................. 5
2.2.1 Read Block .................................................................................................. 6
2.2.2 Write Block.................................................................................................. 9
2.3 SPECIAL BLOCKS ................................................................................................. 9
2.3.1 Slave Status Blocks ..................................................................................... 9
2.4 COMMAND CONTROL BLOCKS ........................................................................... 12
2.4.1 Event Command ........................................................................................ 12
2.4.2 Command Control..................................................................................... 13
2.4.3 Set Module Time Using Processor Time................................................... 14
2.4.4 Warm Boot ................................................................................................ 15
2.5 DATA FLOW BETWEEN MVI69-DFCM MODULE AND COMPACTLOGIX
PROCESSOR .................................................................................................................... 17
2.5.1 Slave Driver Mode .................................................................................... 17
2.5.2 Master Driver Mode ................................................................................. 20
3MODULE CONFIGURATION............................................................................. 23
3.1 POWER UP.......................................................................................................... 23
3.2 CONFIGURATION FILE ........................................................................................ 23
3.3 SETTING UP THE MODULE ................................................................................. 27
3.3.1 Module Data Object (DFCMModuleDef)................................................. 32
3.4 STATUS OBJECT (DFCM_STATUS) ................................................................. 34
3.5 USER DATA OBJECTS......................................................................................... 34
3.6 SLAVE POLLING CONTROL AND STATUS ............................................................ 35
3.7 DFCM SLAVE POLLING CONTROL (DFCMSLAVEPOLLINGCONTROL) ............. 35
3.8 EVENT COMMAND (DFCMEVENTCOMMAND) .................................................. 36
3.9 COMMAND CONTROL (DFCMCOMMANDCONTROL) ......................................... 37
3.10 CLOCK (DFCMCLOCK) ..................................................................................... 37
4LADDER LOGIC ................................................................................................... 39
4.1 MAINROUTINE ................................................................................................... 39
4.2 READDATA ........................................................................................................ 40
4.3 WRITEDATA ...................................................................................................... 43
iii

Table of Contents
5DIAGNOSTICS AND TROUBLESHOOTING .................................................. 51
5.1 READING STATUS DATA FROM THE MODULE ..................................................... 51
5.2 LED STATUS INDICATORS ................................................................................. 51
5.3 CLEARING A FAULT CONDITION ........................................................................ 52
5.4 TROUBLESHOOTING ........................................................................................... 52
5.5 USING THE CONFIGURATION/DEBUG PORT ........................................................ 54
5.5.1 Required Hardware .................................................................................. 54
5.6 REQUIRED SOFTWARE........................................................................................ 54
5.7 USING THE PORT .......................................................................................... 55
5.7.1 Menu Options............................................................................................ 55
5.7.1.1 A = Data Analyzer ................................................................................ 55
5.7.1.2 B = Block Transfer Statistics ................................................................ 58
5.7.1.3 C = Module Configuration.................................................................... 58
5.7.1.4 D = Database View ............................................................................... 59
5.7.1.5 E and F = Master Command Errors (Ports 1 and 2) ............................. 60
5.7.1.6 I and J = Master Command List (Ports 1 and 2)................................... 61
5.7.1.7 O and P = Slave Status List (Port 1 and 2) ........................................... 62
5.7.1.8 R = Receive Module Configuration...................................................... 62
5.7.1.9 S = Send Module Configuration ........................................................... 62
5.7.1.10 T or U = DF1 Override File Map List for Port 1 or Port 2 ............... 62
5.7.1.11 V = Version Information................................................................... 63
5.7.1.12 W = Warm Boot Module .................................................................. 63
5.7.1.13 1 and 2 = Communication Status (Ports 1 and 2) ............................. 63
5.7.1.14 6 and 7 = Port Configuration (Ports 1 and 2).................................... 64
5.7.1.15 Esc = Exit Program ........................................................................... 64
6CABLE CONNECTIONS ...................................................................................... 65
6.1 DF1 COMMUNICATION PORTS ........................................................................... 65
6.1.1 Connecting the Cable to the Connector.................................................... 65
6.2 RS-232 CONFIGURATION/DEBUG PORT............................................................. 67
APPENDIX A – DFCM DATABASE DEFINITION .................................................. 69
APPENDIX B – STATUS DATA DEFINITION ......................................................... 71
APPENDIX C – CONFIGURATION DATA DEFINITION...................................... 73
APPENDIX D – DFCM COMMAND CONTROL...................................................... 83
APPENDIX E – COMMAND ERROR LIST VALUES ............................................. 85
APPENDIX F - UPLOADING AND DOWNLOADING THE CONFIGURATION
FILE ................................................................................................................................. 87
DOWNLOAD A CONFIGURATION FILE TO YOUR PC........................................................ 87
UPLOADING THE CONFIGURATION FILE TO THE MODULE .............................................. 92
APPENDIX G – COMMAND FUNCTION CODES .................................................. 97
iv

Table of Contents
SUPPORT, SERVICE, AND WARRANTY .............................................................. 107
v

Product Specifications
1 Product Specifications
The MVI69-DFCM (“DF1 Communication Module”) product allows Allen-Bradley
CompactLogixI/O compatible processors to easily interface with other DF1 protocol
compatible devices. Compatible devices include not only Allen-Bradley PLC's (which all
support the DF1 protocol) but also a wide assortment of end devices.
1.1 General Specifications
The MVI69-DFCM module acts as a gateway between the DF1 network and the Allen-
Bradley backplane. The data transfer from the CompactLogixprocessor is
asynchronous from the actions on the DF1 network. A 5000-word register space in the
module is used to exchange data between the processor and the DF1 network.
Some of the general specifications include:
• Support for the storage and transfer of up to 5000 registers to/from the
CompactLogix processor's controller tags
• Module memory usage that is completely user definable
• Two ports to emulate any combination of DF1 master or slave device
• Configurable parameters include:
Protocol : Full- or half-duplex
Termination Type BCC or CRC
Local Station ID 0 to 254
Baud Rate : 110 to 115,200
Parity : None, Odd and Even
Stop Bits : 1 or 2
RTS On and Off Timing : 0 to 65535 milliseconds
Minimum Response Delay : 0 to 65535 milliseconds
Use of CTS Modem Line : Yes or No
ENQ Delay 0 to 65535 milliseconds
Response Timeout 0 to 65535 milliseconds
Retry Count 0 to 10
• Address 255 is used for broadcast messages.
1.1.1 Slave Functional Specifications
The MVI69-DFCM module accepts DF1 commands from an attached DF1 master unit. A
port configured as a virtual DF1 slave permits a remote master to interact with all data
contained in the module. This data can be derived from other DF1 slave devices on the
network through a master port or from the CompactLogix processor.
1.1.2 Master Functional Specifications
A port configured as a virtual DF1 master device on the MVI69-DFCM module will
actively issue DF1 commands to other nodes on the DF1 network. One hundred
commands are supported on each port. Additionally, the master ports have an optimized
polling characteristic that will poll slaves with communication problems less frequently.
The CompactLogix processor can be programmed to control the activity on the port by
ProSoft Technology, Inc. 1
MVI69-DFCM User Manual
June 24, 2004

Product Specifications
actively selecting commands from the command list to execute or issuing commands
directly from the ladder logic. The CompactLogix processor also has the ability to control
the scanning of slaves on the port.
1.1.3 Physical
This module is designed by ProSoft Technology and incorporates licensed technology
from Allen-Bradley (CompactLogix backplane technology).
• CompactLogix Form Factor - Single Slot
• Connections :
o RJ45 connectors for DF1 support of RS-232, RS-422 or RS-485
interfaces
o 1 – RJ45 RS-232 Configuration Tool Connector
1.1.4 CompactLogix Interface
• Operation via simple ladder logic
• Complete monitoring of module through RSLogix 5000 software
• CompactLogix backplane interface via I/O access
• All data related to the module is contained in a single controller tag with defined
objects to ease in the monitoring and interfacing with the module
1.2 Hardware Specifications
The MVI69-DFCM module is designed by ProSoft Technology and incorporates licensed
technology from Allen-Bradley (CompactLogix backplane technology).
Current Loads 800 mA @ 5V (from backplane)
Operating Temperature 0 to 60°C
32 to 140°F
Storage Temperature -40 to 85°C
-40 to 185°F
Relative Humidity 5 – 95% (w/o condensation)
DF1 Port Connector Two RJ45 connectors (RJ45 to DB9 cable
shipped with unit (supporting RS-232, RS-
422 and RS-485 interfaces (RJ45 to DB9
cables shipped with unit.
Configuration Connector RJ45 RS-232 Connector (RJ45 to DB9
cable shipped with unit.
2ProSoft Technology, Inc.
MVI69-DFCM User Manual
June 24, 2004

Functional Overview
2 Functional Overview
This section provides a functional overview of the MVI69-DFCM module. A thorough
understanding of the information contained in this document is required for successful
implementation of the module in a user application. If you are not familiar with the data
transfer and DF1 protocol operations, read this document before setting up the module.
2.1 General Concepts
The following discussion covers several concepts that are key to understanding the
operation of the MVI69-DFCM module.
2.1.1 Module Power Up
• On power up the module begins performing the following logical functions:
• Initialize hardware components
o Initialize CompactLogix backplane driver
o Test and Clear all RAM
o Initialize the serial communication ports
• Read module configuration from the Compact Flash
• Initialize Module Register space
• Enable Slave Driver on selected ports
• Enable Master Driver on selected ports
Once this initialization procedure is complete, the module will begin communicating with
other nodes on the network, depending on the configuration.
2.1.2 Main Logic Loop
Upon completing the power up configuration process, the module enters an infinite loop
that performs the following functions:
Call I/O Handler
- Trans fers data between mo dule a nd processor
(user, status, configuration, etc.)
Call Serial Port Driver (Configuration/Debug Port)
- Rx and Tx buffer routines are interrupt driven
- Call to serial port routines checks 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 I/O Handler
Call Cfg/ Dbg Port
Driver
Call DF1 Driver
- If DF1 Master Port, poll slaves using command list
- If DF1 Slave Port, respond to commands received
From Power Up Logic
Call DF 1
Driver
Call I/O Handler
- Trans fers data between mo dule a nd processor
(user, status, configuration, etc.)
Call Serial Port Driver (Configuration/Debug Port)
- Rx and Tx buffer routines are interrupt driven
- Call to serial port routines checks to see if there is any data
in the buffer, and depending on the val ue will either service
the buffer or wait for more characters
Call I/O Handler
Call Cfg/ Dbg Port
Driver
Call Cfg/ Dbg Port
Driver
Call DF1 Driver
- If DF1 Master Port, poll slaves using command list
- If DF1 Slave Port, respond to commands received
From Power Up Logic
Call DF 1
Driver
Call DF 1
Driver
ProSoft Technology, Inc. 3
MVI69-DFCM User Manual
June 24, 2004

Functional Overview
2.1.3 Backplane Data Transfer
The MVI69-DFCM module is unique in the way that the CompactLogix backplane is
utilized. Data is paged between the module and the CompactLogix processor across the
backplane using the module's input and output images. The update frequency of the
images is determined by the scheduled scan rate defined by the user for the module and
the communication load on the module. Typical updates are in the range of 2 to 10
milliseconds.
The data is paged between the processor and the module using input and output image
blocks. You can configure the size of the blocks using the Block Transfer Size parameter
in the configuration file. You can configure blocks of 60, 120, or 240 words of data
depending on the number of words allowed for your own application.
This bi-directional transference of data is accomplished by the module filling in data in the
module's input image to send to the processor. Data in the input image is placed in the
Controller Tags in the processor by the ladder logic. The input image for the module may
be set to 62, 122, or 242 words depending on the block transfer size parameter set in the
configuration file.
The processor inserts data to the module's output image to be transferred to the module.
The module's program extracts the data and places it in the module's internal database.
The output image for the module may be set to 61, 121, or 241 words depending on the
block transfer size parameter set in the configuration file.
The following diagram displays the data transfer method used to move data between the
CompactLogix processor, the MVI69-DFCM module and the DF1 network.
DF1
Port
Drivers
Master
Driver
Logic
Slave
Driver
Logic
Module’s
Internal
Database
MVI69-DFCM Module
To DF1
Network
Ladder
Logic
Transfers
Data from
module’s input
image to data
areas in the
processor
Processor
Controller Tags
Or User Files
Processor
Ladder
Logic
Transfers
Data from
Processor
data areas
to output image
Input Image
Output Image
Backplane Driver
Status
Read Data
Write Data
Special Control
Blocks
DF1
Port
Drivers
Master
Driver
Logic
Master
Driver
Logic
Slave
Driver
Logic
Slave
Driver
Logic
Module’s
Internal
Database
MVI69-DFCM Module
To DF1
Network
Ladder
Logic
Transfers
Data from
module’s input
image to data
areas in the
processor
Processor
Controller Tags
Or User Files
Processor
Ladder
Logic
Transfers
Data from
Processor
data areas
to output image
Input Image
Output Image
Backplane Driver
Status
Read Data
Write Data
Special Control
Blocks
As shown in the diagram above, all data transferred between the module and the
processor over the backplane is through the input and output images. Ladder logic must
be written in the CompactLogix processor to interface the input and output image data
4ProSoft Technology, Inc.
MVI69-DFCM User Manual
June 24, 2004

Functional Overview
with data defined in the Controller Tags. All data used by the module is stored in its
internal database. The diagram below displays the layout of the database:
5000 registers for user data Register
Data
Status
and
Config
Module’s Internal Database Structure
0
4999
5000
7999
3000 words of configuration
and status data
Data contained in this database is paged through the input and output images by
coordination of the CompactLogix ladder logic and the MVI69-DFCM module's program.
Up to 242 words of data can be transferred from the module to the processor at once.
Up to 241 words of data can be transferred from the processor to the module. The read
and write block identification codes in each data block determine the function to be
performed or the content of the data block. The block identification codes used by the
module are listed below:
Block Range Descriptions
-1 Status Block
0 Status Block
1 to 999 Read or write data
1000 Event Port 1
2000 Event Port 2
3000 to 3001 Port 1 slave polling control
3002 to 3006 Port 1 slave status
3100 to 3101 Port 2 slave polling control
3102 to 3106 Port 2 slave status
5000 to 5006 Port 1 command control
5100 to 5106 Port 2 command control
9972 Set module time using received time
9973 Pass module time to processor
9998 Warm-boot control block
9999 Cold-boot control block
Each image has a defined structure depending on the data content and the function of
the data transfer as defined in the sections below:
2.2 Normal Data Transfer
Normal data transfer includes the paging of the user data found in the module's internal
database in registers 0 to 4999 and the status data. These data are transferred through
read (input image) and write (output image) blocks. The structure and function of each
block is discussed in the following sections:
ProSoft Technology, Inc. 5
MVI69-DFCM User Manual
June 24, 2004

Functional Overview
2.2.1 Read Block
These blocks of data are used to transfer information from the module to the
CompactLogix processor. The structure of the input image used to transfer this data is
shown below:
Offset Description Length
0 Read Block ID 1
1 Write Block ID 1
2 to (n+1) Read Data n
where
n= 60, 120, or 240 depending on the Block Transfer Size parameter (refer to the
configuration file).
The Read Block ID is an index value used to determine the location of where the data will
be placed in the CompactLogix processor controller tag array of module read data. The
number of data words per transfer depends on the configured Block Transfer Size
parameter in the configuration file (possible values are 60, 120, or 240).
The Write Block ID associated with the block is used to request data from the
CompactLogix processor. Under normal, program operation, the module sequentially
sends read blocks and requests write blocks. For example, if three read and two write
blocks are used with the application, the sequence will be as follows:
R1W1-->R2W2-->R3W1-->R1W2-->R2W1-->R3W2-->R1W1-->
This sequence will continue until interrupted by other write block numbers sent by the
controller or by a command request from a node on the DF1 network or operator control
through the module's Configuration/Debug port.
The following example shows a typical backplane communication application.
Assume that the backplane parameters are configured as follows:
Read Register Start: 0
Read Register Count: 480
Write Register Start: 480
Write Register Count: 480
The backplane communication would be configured as follows:
6ProSoft Technology, Inc.
MVI69-DFCM User Manual
June 24, 2004

Functional Overview
Database address 0 to 479 will be continuously transferred from the module to the
processor. Database address 480 to 959 will continuously be transferred from the
processor to the module.
The Block Transfer Size parameter basically configures how the Read Data and Write
Data areas are broken down into data blocks (60, 120, or 240).
ProSoft Technology, Inc. 7
MVI69-DFCM User Manual
June 24, 2004

Functional Overview
If Block Transfer Size = 60:
If Block Transfer Size = 120:
8ProSoft Technology, Inc.
MVI69-DFCM User Manual
June 24, 2004

Functional Overview
If Block Transfer Size = 240:
2.2.2 Write Block
These blocks of data are used to transfer information from the CompactLogix processor
to the module. The structure of the output image used to transfer this data is shown
below:
Offset Description Length
0 Write Block ID 1
1 to n Write Data n
where n= 60, 120, or 240 depending on the Block Transfer Size parameter (refer to the
configuration file).
The Write Block ID is an index value used to determine the location in the module's
database where the data will be placed. Each transfer can move up to 200 words (block
offsets 1 to 200) of data.
2.3 Special Blocks
2.3.1 Slave Status Blocks
Slave status blocks are used to send status information of each slave device on a master
port. Slaves attached to the master port can have one of the following states:
ProSoft Technology, Inc. 9
MVI69-DFCM User Manual
June 24, 2004

Functional Overview
State Description
0 The slave is inactive and not defined in the command list
for the master port.
1 The slave is actively being polled or controlled by the
master port and communications is successful.
2 The master port has failed to communicate with the slave
device. Communications with the slave is suspended for
a user defined period based on the scanning of the
command list.
3 Communications with the slave has been disabled by the
ladder logic. No communication will occur with the slave
until this state is cleared by the ladder logic.
Slaves are defined to the system when the module initializes the master command list.
Each slave defined will be set to a state of one in this initial step. If the master port fails
to communicate with a slave device (retry count expired on a command), the master will
set the state of the slave to a value of 2 in the status table. This suspends
communication with the slave device for a user specified scan count (Error Delay Count
parameter in the configuration file). Each time a command in the list is scanned that has
the address of a suspended slave, the delay counter value will be decremented. When
the value reaches zero, the slave state will be set to one.
In order to read the slave status table, you should refer to the sample ladder logic. The
ladder logic must send a special block to the module to request the data. Each port has
a specific set of blocks to request the data as follows:
BLOCK ID DESCRIPTION
3002 Request status for slaves 0 to 59 for Port 1
3003 Request status for slaves 60 to 119 for Port 1
3004 Request status for slaves 120 to 179 for Port 1
3005 Request status for slaves 180 to 239 for Port 1
3006 Request status for slaves 240 to 255 for Port 1
3102 Request status for slaves 0 to 59 for Port 2
3103 Request status for slaves 60 to 119 for Port 2
3104 Request status for slaves 120 to 179 for Port 2
3105 Request status for slaves 180 to 239 for Port 2
3106 Request status for slaves 240 to 255 for Port 2
The format of these blocks is as shown below:
Write Block – Request Slave Status
Offset Description Length
0 3002 – 3006 or 3102 – 3106 1
1 to n Spare n
n=60, 120, or 240 depending on what is entered in the Block Transfer Size parameter
(see the configuration file).
10 ProSoft Technology, Inc.
MVI69-DFCM User Manual
June 24, 2004

Functional Overview
The module will recognize the request by receiving the special write block code and
respond with a read block with the following format:
Read Block – Read Slave Status
Offset Description Length
0 3002-3006 or 3102-3106 1
1 Write Block ID 1
2-61 Slave Poll Status Data 60
62 to n Spare (if present)
The sample ladder logic shows how to override the value in the slave status table to
disable slaves (state value of 3) by sending a special block of data from the processor to
the slave. Port 1 slaves are disabled using block 3000, and Port 2 slaves are disabled
using block 3100. Each block contains the slave node addresses to disable. The
structure of the block is displayed below:
Write Block – Disable Slaves
Offset Description Length
0 3000 or 3100 1
1 Number of slaves in block 1
2 to 61 Slave indexes 60
62 to (n+1) Spare
n=120, or 240 (if configured)
The module will respond with a block with the same identification code received and
indicate the number of slaves acted on with the block. The format of this response block
is displayed below:
Read Block – Disable Slaves
Offset Description Length
0 3000 or 3100 1
1 Write Block ID 1
2 Number of slaves processed 1
3 to (n+1) Spare
n=60, 120, or 240 (if configured)
The sample ladder logic explains how to override the value in the slave status table to
enable the slave (state value of 1) by sending a special block. Port 1 slaves are enabled
using block 3001, and Port 2 slaves are enabled using block 3101. Each block contains
the slave node addresses to enable. The format of the block is displayed below:
Write Block – Enable Slaves
Offset Description Length
0 3001 or 3101 1
1 Number of slaves in block 1
2 Slave indexes 1
ProSoft Technology, Inc. 11
MVI69-DFCM User Manual
June 24, 2004

Functional Overview
3 to n Spare
n=60, 120, or 240 depending on what is entered in the Block Transfer Size parameter
(see the configuration file).
The module will respond with a block with the same identification code received and
indicate the number of slaves acted on with the block. The format of this response block
is displayed below:
Read Block – Enable Slaves
Offset Description Length
0 3001 or 3101 1
1 Write Block ID 1
2 Number of slaves processed 1
3-n Spare
n=60, 120, or 240 depending on what is entered in the Block Transfer Size parameter
(see the configuration file).
Important: The slaves are enabled by default. Therefore, this block should only be used
after Block 3000 or 3001 to re-enable the slaves.
2.4 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 five command
control blocks: event command control, command control, transfer time, warm boot and
cold boot.
2.4.1 Event Command
Event command control blocks are used to send DF1 commands directly from the ladder
logic to one of the master ports. The format for these blocks is displayed below:
Write Block – Event Command
Offset Description Length
0 1000 or 2000 1
1 Internal DB Address 1
2 Point Count 1
3 Swap Code 1
4 Node Address 1
5 Function Code 1
6 Parameter #1 1
7 Parameter #2 1
8 Parameter #3 1
9 Parameter #4 1
10 to n Spare
n=60, 120, or 240 depending on what is entered in the Block Transfer Size parameter
(see the configuration file).
12 ProSoft Technology, Inc.
MVI69-DFCM User Manual
June 24, 2004

Functional Overview
The block number defines the DF1 port to be considered. Block 1000 commands are
directed to Port 1, and block 2000 commands are directed to Port 2. The parameters
passed with the block are used to construct the command. The Internal DB Address
parameter specifies the module's database location to associate with the command. The
Point Count parameter defines the number of registers for the command. The Swap
Code is used to change the word or byte order. The Node Address parameter is used
to define the device on the DF1 network to consider. The Function Code parameter is
one of those defined in the ProSoft DF1 Command Set documentation. The parameter
fields in the block should be completed as required by the selected function code. Each
command has its own set of parameters. When the block is received, the module will
process it and place the command in the command queue. The module will respond to
each event command block with a read block with the following format:
Read Block – Event Command
Offset Description Length
0 1000 or 2000 1
1 Write Block ID 1
2 0=Fail, 1=Success 1
3 to n Spare
n=60, 120, or 240 depending on what is entered in the Block Transfer Size parameter
(see the configuration file).
Word two of the block can be used by the ladder logic to determine if the command was
added to the command queue of the module. The command will only fail if the command
queue for the port is full (100 commands for each queue) or the command requested is
invalid.
2.4.2 Command Control
Command control blocks are used to place commands in the command list into the
command queue. Each port has a command queue of up to 100 commands. The
module services commands in the queue before the master command list. This gives
high priority to commands in the queue. Commands placed in the queue through this
mechanism must be defined in the master command list. Under normal command list
execution, the module will only execute commands with the Enable parameter set to one
or two. If the value is set to zero, the command is skipped. Commands may be placed in
the command list with an Enable parameter set to zero. These commands can then be
executed using the command control blocks.
One to six commands can be placed in the command queue with a single request. The
format of the block is displayed in the following table:
Write Block – Command Control
Offset Description Length
0 5001-5006 or 5101-5106 1
1 Command index 1
2 Command index 1
3 Command index 1
4 Command index 1
ProSoft Technology, Inc. 13
MVI69-DFCM User Manual
June 24, 2004

Functional Overview
5 Command index 1
6 Command index 1
7 to n Spare
n=60, 120, or 240 depending on what is entered in the Block Transfer Size parameter
(see the configuration file).
Blocks in the range of 5001 to 5006 are used for Port 1, and blocks in the range of 5101
to 5106 are used for Port 2. The last digit in the block code defines the number of
commands to process in the block. For example, a block code of 5003 contains 3
command indexes that are to be used with Port 1. The Command index parameters in
the block have a range of 0 to 99 and correspond to the master command list entries.
The module responds to a command control block with a block containing the number of
commands added to the command queue for the port. The format of the block is
displayed below:
Read Block – Command Control
Offset Description Length
0 5000-5006 or 5100-5106 1
1 Write Block ID 1
2 Number of commands added to
command queue
1
3 to (n+1) Spare
n=60, 120, or 240 depending on what is entered in the Block Transfer Size parameter
(see the configuration file).
2.4.3 Set Module Time Using Processor Time
This block can be used to update the module’s internal clock (date and time).
Write Block – Set Module Time
Offset Description Length
0 9972 1
1 Year (0-9999) 1
2 Month (1-12) 1
3 Day (1-31) 1
4 Hour (0-23) 1
5 Minutes (0-59) 1
6 Seconds (0-59) 1
7 to n Spare
n=60, 120, or 240 depending on what is entered in the Block Transfer Size parameter
(see the configuration file).
14 ProSoft Technology, Inc.
MVI69-DFCM User Manual
June 24, 2004