AN-X-DCSNet Pre-release Notes

Release Firmware 1.01.0008

What's Included:

  1. AN-X-DCSNet Ethernet/IP Server (v1.1.45), the AN-X-DCSNet Ethernet/IP server has the following general capabilities:
  • Supports Scheduled and Unscheduled data connections from a ControlLogix PLC. The unscheduled data connections use PLC/5 emulation (reading/writing N registers)
  • Configuration of the scheduled data (inputs,status and outputs) is done using a csv (comma delimited) file format.
  1. DCSNet Bridging Application (v1.41.0006), this application allows for the mapping of DCSNet registers from one AN-X-DCSNet device to another. The configuration of the AN-X to AN-X application is found in the "Automation" menu of the web interface and requires the uploading of a csv (comma delimited format) file. The format of the csv file is outlined below.
  2. AUTOMAX Programming Software Server (v1.40.001), this application allows a host computer that is running the Automax programming software access to the PLC on the DCSNet network for programming and monitoring.  

DCSNet Bridging (AN-X To AN-X) Configuration Notes:

The configuration of the AN-X to AN-X communication application uses a single csv file for all AN-X-DCSNet devices that will be part of the DCSNet data bridging function. Therefore, more than one AN-X-DCSNet device is specified in the configuration file. The file documented below can be downloaded from this location. Be sure to right-click and use the "save target link" option.
A user may also choose to keep a separate file for each AN-X device that will be part of an overall AN-X-DCSNet bridging configuration.


AN-X-DCSNet Data Sharing Definition Sheet


The configuration_id line defines the numeric id for this configuration and whether to enable or disable execution of this configuration.  The primary purpose of the configuration_id (a 32 bit unsigned integer) is to make sure all AN-X-DCSNet devices have matching configurations. When an AN-X device produces data, included in that data is the configuration_id. If the consuming AN-X device does not have a matching configuration_id then the incoming data is ignored and an error occurs.

configuration_id,1,enable

The module_ip line starts the definition for one of the AN-X-DCSNet devices and specifies the IP address of that device. When this configuration is uploaded to any given AN-X-DCSNet device, the AN-X device looks for the IP address that matches its current IP address and uses that configuration.

module_ip,192.168.0.194,,,,

The produce line marks the start of all the data blocks that this AN-X device will send out on the network.

,produce,,,,

The block_id line defines one of the up to 10 blocks that can be configured in this section. The format of this line is:
    block_id,<block number 1-10>,<update type-timed,bus_scan,broadcast_data>,<rate 5-16383 mS>
The "update type" determines when this data is sent out on the network -- every x mS, at the end of a bus scan or when broadcast data has been updated. NOTE: the broadcast_data option is only valid for an AN-X-DCSNet device in SLAVE mode. If the timed type is used a numeric update time follows the update type. All other types should not have a value after the type name.

,,block_id,1,timed,50

The next lines define the up to 64 data copy entries for this block. The format of this line is:
packet offset(in registers),drop number,start register,len (in registers)
The len field is the number of 16 bit DCSNet registers to map at this packet offset. The entire block_id can have 700 registers.

,,0,0,14,6
,,6,1,0,32
,,38,2,0,660

,,block_id,2,timed,50
,,0,3,0,32
,,32,4,0,32
,,64,5,0,32

The consume line marks the start of all the data blocks this AN-X device will receive from the network.

,consume,,,,

The producer_ip line defines the IP address of the AN-X device that will provide this data block.

,,producer_ip,192.168.0.180,,

Now that we know the producer we want to consume, the block_id line provides the specific block of data we want to consume from the configured producer. The block_id line is very much like the producer block_id line with the exception of the options:
block_id,<block number>,<time out value in mS (5-16383)>

,,block_id,1,1000,
,,;packet offset,drop number,start register,len (registers)
,,0,1,32,32
,,32,2,32,32

,,producer_ip,192.168.0.184,,
,,block_id,2,1000,
,,;packet offset,drop number,start register,len (registers)
,,0,3,32,32
,,32,4,32,32

The start of the configuration for the AN-X device at IP address 192.168.0.180
module_ip,192.168.0.180,,,,
,produce,,,,
,,block_id,1,timed,5,
,,;packet offset,drop number,start register,len (registers)
,,0,1,32,32
,,32,2,0,32
,,64,3,0,32

,,block_id,2,timed,5,
,,0,3,0,32
,,32,4,0,32
,,64,5,0,32

,consume,,,,
,,producer_ip,192.168.0.194,,
,,block_id,1,1000,
,,;packet offset,drop number,start register,len (registers)
,,0,1,0,6
,,6,2,0,32

The start of the configuration for the AN-X device at IP address 192.168.0.184
module_ip,192.168.0.184,,,,
,produce,,,,
,,block_id,1,timed,50,
,,;packet offset,drop number,start register,len (registers)
,,0,1,0,32
,,32,2,0,32
,,64,3,0,32

,,block_id,2,timed,50,
,,0,3,0,32
,,32,4,0,32
,,64,5,0,32


ControlLogix Scheduled Data Copy Table Notes:

As mentioned earlier, the data that can be mapped to a ControlLogix PLC's I/O areas via scheduled data connections is controlled by a comma delimited text file. Below is the example file:

; QTS-AN-X-DCSNet Configuration,,,

; Enet Ofs,Drop,Start Reg,Len
; where:
; Enet Ofs - word offset (16-bit words) into the PLC I/O data table
; Drop      - DCSNet drop number
; Start Reg- Starting DCSNet Register Number
; Len - length in 16 bit registers
;

;This is the output data from the PLC
;PLC Output word 0 to 7 is mapped to drop 0, register 32 to 39
;PLC Output word 8 to 37 is mapped to drop 2, register 32 to 62
DataOutput,,,
0,0,32,6
8,2,32,31
Run,2,63,

;This is the input data to the PLC
;Drop 0, register 14 to 19 are mapped to PLC Input word 0 to 6
;Drop 2, register 0 to 15 are mapped to PLC Input word 7 to 21
DataInput,,,
0,0,14,6
7,2,0,15

;This is the status input to the PLC
StatusInput
0,0,4,4,,; Active Drop List
4,0,14,6,,; Diagnostic Counters

The copy table provides a means of mapping up to 250 DCSNet registers to the PLC 's input data table and 248 PLC output words to DCSNet registers.
Note:

Each copy table ( DataInput and  DataOutput) can have a maximum of 64 copy entries. You can not map each individual word of a PLC's data table to different DCSNet registers. A maximum of 64 "blocks" of registers can be mapped.

AN-X-DCSNet LED Information:

Boot Sequence LED States

  1. boot code starts up - fast flashing RED
  2. boot code loads a kernel - solid RED
  3. configuration mode loads - RED code 2 - in configuration mode the process stops here.
  4. production mode loads - solid GREEN for ok - in production mode the process stops here.

Configuration Mode Start-up Errors
During the start-up sequence of the configuration mode, some errors may happen. The following table notes those errors:

Error Condition LED State
dhcp fails RED code 3
other script and system application loading errors slow flashing RED

Production Mode Start-up Errors
Here are the start-up error codes for production mode. The only big difference is that these errors cause the an-x to reset into configuration mode and therefore these codes are only active for a short time. The an-x error record is written during these errors; therefore, getting the reason for the reboot to configuration mode requires the use of the anxinit program.

Error Condition LED State
dhcp fails RED code 3
other script and system application loading errors slow flashing RED

AN-X Application LED Codes

Since all these application run concurrently, the user must view the error log to determine the specific application that is causing an LED error code.

AN-X-DCSNet Programming Software Server (anxdcsnet)

Error Condition LED State
reconfiguration failed (set drop and depth) fast RED flash
fatal application error RED code 4
application crashed - memory access violation RED code 5
application crashed - illegal instruction RED code 6
application crashed - unknown reason RED code 7

AN-X-DCSNet AN-X-to-AN-X Software Server (xanxdcsd)

Error Condition LED State
configuration failed (csv file parse failed) fast RED flash
ethernet connection problems (timeout on consumer, error on producer) single RED flash
fatal application error RED code 4
application crashed - memory access violation RED code 5
application crashed - illegal instruction RED code 6
application crashed - unknown reason RED code 7

AN-X-DCSNet AN-X Ethernet/IP Software Server (AnxDcsEnetIp)

Error Condition LED State
configuration failed (csv file parse failed)
fast RED flash
addressing or ethernet network connection errors single RED flash
fatal application error RED code 4
application crashed - memory access violation RED code 5
application crashed - illegal instruction RED code 6
application crashed - unknown reason RED code 7