AADvance The Next Step in Automation AADvance Controller Configuration Guide Issue: 07 DOCUMENT: 553633 ICSTT-RM405F-EN-P
Configuration Guide (AADvance Controller) This page intentionally left blank ii Document: 553633 ICSTT-RM405f-EN-P Issue: 07
Notice In no event will Rockwell Automation be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment. The examples given in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation does not assume responsibility or reliability for actual use based on the examples and diagrams.
Configuration Guide (AADvance Controller) Issue Record Issue Date Comments 01 Jan 2009 First Issue 01A Aug 2009 Release 1.1 Issue 01B Aug 2009 Updated issue for per review comments 02 Nov 2009 Release 1.1.1 03 July 2010 Update for CRs 04* Oct 2011 Release 1.2 05 Apr 2012 Updated Release 1.2 version with Analogue Output Module information added. 06 June 2012 Release 1.3 & 1.3.
Notes and Symbols used in this manual This symbol calls attention to items which "must" be considered and implemented when designing and building an AADvance controller for use in a Safety Instrumented Function (SIF). It appears extensively in the AADvance Safety Manual. Note: Notes are used extensively to provide important information about the product.
Configuration Guide (AADvance Controller) Forward This manual defines how to configure an AADvance controller using the AADvance Workbench to meet your SIF application requirements. Who Should Use This Manual This manual is intended primarily for System Integrators. The information contained in this manual is aimed at engineers experienced in building and setting up safety-related systems. It is expected that the users have been trained and have a thorough understanding of the intended application.
Configuration Guide (AADvance Controller) Contents Chapter 1 Introduction ............................................................................................. 1-1 Purpose and Scope ............................................................................................................................................ 1-1 AADvance Workbench and Software Development Environment ....................................................... 1-1 About The Configuration Process ...........................
Serial Port Parameters .............................................................................................................................. 4-23 Time Synchronization (SNTP) ...................................................................................................................... 4-24 Configure the Controller as an SNTP Client...................................................................................... 4-24 Configure the Controller as an SNTP Server ............................
Configuration Guide (AADvance Controller) Configuring Analogue Inputs ......................................................................................................................... 5-26 T9K_AI_COMPACT and T9K_AI_FULL (Analogue Inputs) .......................................................... 5-26 Faulted State for Analogue Inputs .......................................................................................................... 5-27 HART ..................................................
Defining The AADvance Controller as a CIP Producer .......................................................................... 8-6 Configure an AADvance Variable as a Consumer ..................................................................................... 8-8 Obtaining the Connection Status for a Consumed Variable ................................................................. 8-10 CIP within the Application Scan Cycle ..................................................................................
Configuration Guide (AADvance Controller) Create Links to Modbus Slaves .................................................................................................................... 9-33 Modbus Slave Link Identification and Control Settings .................................................................... 9-34 Configure a Modbus Slave Link for Modbus RTU.............................................................................. 9-36 Configure a Modbus Slave Link for Modbus TCP ................
Configure Analogue Output Boards ......................................................................................................... 11-14 Configure Digital Output Board................................................................................................................. 11-16 Peer to Peer Configuration Example 1..................................................................................................... 11-18 Peer-to-Peer Controller Setting Summary .................................
Chapter 1 Introduction This chapter provides a brief overview of the AADvance Workbench and this manual. In This Chapter Purpose and Scope ............................................................................................. 1-1 AADvance Workbench and Software Development Environment ........ 1-1 About The Configuration Process .................................................................. 1-3 Integrating the AADvance Controller with Other Systems .....................
Configuration Guide (AADvance Controller) CAUTION: Do not use XP Professional x64 edition Network port (10/100 Base T Ethernet) Access to a CD-ROM drive, for software installation If the application adopts the dongle licensing option for the software, the processor module will also require one free USB port. The AADvance workstation uses software that enables you to design the complete control strategy as one, then to target parts of the strategy at each controller.
Programs can be simulated and tested and tested on the computer before downloading to the controller hardware. Also provided is a set of configuration tools that enables you to define the hardware architecture in the software; set up the processor functionality; and connect application variables to the Workbench application resource program that will monitor processor and I/O module status information and report I/O channel data values to the Workbench.
Configuration Guide (AADvance Controller) The AADvance Workbench provides pre-defined I/O module status parameters for each module to which you assign application variables. Finally you connect (wire) each I/O channel to structured variables. These structured variables report input the channel status and define output data values. You define hardware redundancy in the AADvance Workbench when you define the hardware configuration.
Application Scan Model The application scan model for the AADvance controller is shown in the following illustration: Document: 553633 ICSTT-RM405f-EN-P Issue 07 1-5
Configuration Guide (AADvance Controller) Scan Times The following scan times were taken from a test system consisting of production modules. Module Scan Time T9401 Digital input module, 24V dc, 8 channel Single Dual Triple 1.23ms 1.73ms 2.08ms T9431 Analogue input module 24V dc, 8 channel Single Dual Triple 1.26ms 1.91ms 2.33ms T9451 Digital output module, 24V dc, 8 channel Single Dual 1.43ms 2.44ms AADvance Workbench Sleep Period 57.2ms Scan overhead per module 0.
Throughput time: min Avg Max = 125.1ms = 187.6ms = 250.
Chapter 2 Software Installation This chapter provides the instructions to install and license the AADvance Workbench. In This Chapter AADvance WorkbenchLicensing Options.................................................... 2-1 Install the AADvance Workbench and Utilities .......................................... 2-1 Add and Activate a New AADvance Workbench License ....................... 2-5 Updating or Upgrading an Existing License ..................................................
Configuration Guide (AADvance Controller) Installing Workbench Part Numbers: T9082U. T9082D, T9083U & T9083D Notes: You require "Admin" rights on the PC the Workbench is to be installed on. The Install CD has an Autorun, so simply inserting the CD will launch the AADvance Products Installer.
Accept the License Agreement and the installation will commence. The default is to install both the Workbench and the License Manager components; we recommend proceeding with the defaults. When the install commences you will be given the option of changing the location for the install, we recommend you accept the default settings. During the install you will be asked if you want shortcuts placed on your desktop, simply answer yes or no depending on your preference.
Configuration Guide (AADvance Controller) When the installation is complete you will be prompted to restart the computer, this must be done prior to using the Workbench. Install the License Manager on the Network License Server 1) Click on the Install AADvance Workbench button at the top of the list of the AADvance Products Installer. You must accept the License Agreement before the installation will commence. 2) Select the License Manager Only.
Add and Activate a New AADvance Workbench License You use the following AADvance License Manager window to add and activate a new Software (Disk Based) AADvance Workbench licenses. USB licenses are detected automatically. Note: You need only one set of user codes and registration keys to activate the license key, irrespective of the feature set or number of licenses ordered. To add a new license do the following: 1) From the Start menu select AADvance Licensing AADvance.
Configuration Guide (AADvance Controller) 4) The AADvance license Features options appears. 5) Select the license feature and leave the Max#of I/Os blank. When you purchase a single user license you can choose from the following feature sets: T9082 Multiscan (PRS): Single user, single controller license. T9083 Distributed (PRD): Single user, multiple controllers license. 6) A Setup Code and two User Codes appear in their respective fields. 7) Click Send.
10) Send the email. Note: If the computer does not have an email client configured, copy the text and send from another computer. The original Setup Codes and User Codes together with the new Registration Keys are returned to you in an email. 1) Check that the Setup Code and User Codes are the same as the original ones. 2) Enter the Registration Keys into their respective fields, click Proceed. The selected components appear grey in the Selected Components list. 3) Restart AADvance.
Configuration Guide (AADvance Controller) 2) Send the User Codes by email to keymaster@icstriplex.com. 3) If you are upgrading a hardware license key, leave it fitted. You will be sent the Registration Keys 1 & 2. 4) Enter these keys in the two boxes and click Proceed. Your license will be upgraded. Multi-User Floating Hardware License 1. The Licensing Error message may not be automatically displayed, but you still need to upgrade your license. 2.
Set Up a Server for Hardware Floating Licenses To set up a primary server for hardware floating licenses, do the following: 1) Insert the dongle supplied with the CD set into a USB or parallel port. 2) From the Start menu select AADvance Licensing The License Manager dialog box opens. 3) Select the Set Floating Licenses tab. 4) Set the IP Address of the primary server and a port number. 5) Select one of the two options to start the server Manual or Automatic (Automatic is recommended).
Configuration Guide (AADvance Controller) Set Access to Floating Licenses To set access a floating license, do the following: 1) From the Start menu select AADvance Licensing. The AADvance License Manager dialog box opens. 2) Select the Set Floating Licenses tab. The Primary Server Status will show Licensed. 3) Set the IP address of the primary server and the port number. 4) Click Report to claim a license. The Primary Server Status will show Licensed.
Chapter 3 Connecting the Workbench to the Controller This chapter describes the procedures for connecting the AADvance Workbench to the controller so that the application can be downloaded. In This Chapter Setting Up the Controller IP Address for AADvance Workbench Communications .................................................................................................
Configuration Guide (AADvance Controller) Double-clicking on an entry in the list lets you inspect the resource and IP address settings for a controller. There is also a Refresh button, which makes a scan of the network and creates a new list. A controller is configurable when the program enable key is present (this plugs into the KEY connector on the processor base unit) and either no application is loaded or an application is loaded but not running.
Discover Communications Fault-Finding This procedure describes how to activate communications using the Discover tool. After completing the steps, refresh the Discover tool's list of modules to test for communications. 1) Ensure that the Ethernet cable is plugged into a socket above a fitted AADvance controller – communications will not ‘pass through’ unused slots. 2) Ensure that the controller is activated by turning the locking bar. Wait for the Ready LED to go green before refreshing the Discover tool.
Configuration Guide (AADvance Controller) The AADvanceDiscover utility scans the network for controllers, and creates a list. 4) Locate the controller in the list and make sure that the status of the controller is Configurable. 5) Double-click on the MAC address in the Controller ID field. The resource and IP Address dialog box opens. 6) Enter the resource value into the Resource Number field, click Apply.
8) Refresh the screen to confirm that the new resource number is displayed in the resource field and the controller status is configurable. The Resource Number must also be configured in the application, in the Resource Properties. Configure the IP Address in the Controller When you build a new AADvance controller, or install a new 9100 processor base unit, you have to configure the IP Address stored in the controller. The procedure to configure the IP Address uses the AADvanceDiscover utility.
Configuration Guide (AADvance Controller) 6) Enter the IP Address and Subnet Mask into the fields for each Ethernet port. 7) Enter the Gateway values for each processor module, click Apply. Returning to the main window of the utility, the controller status will show In Progress and then Configurable. The controller uses the new settings.
Save and Load a Configuration When you have entered the IP Address details you can now save the configuration: 1) Click Save after you have entered your required configuration.
Configuration Guide (AADvance Controller) 2) Give the configuration a name and save it to a suitable location. To reload a saved configuration file: 1) Open the AADvanceDiscover utility 2) Double click on a MAC address to open the Configuration dialog box. 3) Select the Configuration file at the location it was saved. 4) Click Load to load the saved configuration.
Chapter 4 Configuring the Processor Modules This chapter describes the process to configure the processor modules: In This Chapter View Module Firmware Versions.................................................................... 4-1 ControlFLASH Firmware Upgrades ............................................................... 4-5 Configure Controller Type (Standard or Eurocard) ................................ 4-19 Configure the Top-level Process Safety Time (PST) ................................
Configuration Guide (AADvance Controller) 4) Click the Update button.
The window now shows your controller's current firmware version information. The information displayed is as follows: MAC Addresses - MAC addresses for the controllers. There are two addresses per controller set by the BUSP chip inserted into the processor base unit; However, 6 MAC addresses are displayed regardless if the system is a Single, Dual or Triple processor system.
Configuration Guide (AADvance Controller) The saved text file can be viewed in Notepad.
ControlFLASH Firmware Upgrades The AADvance controller supports upgrades of processor module firmware by using the ControlFLASH utility (I/O module upgrades using ControlFLASH are not currently supported in this release.) WARNING FIRMWARE UPGRADE DANGER TO A RUNNING SYSTEM Do not attempt to upgrade firmware on a running system. Control FLASH will not warn you that a system is running and you will lose control of the application when the system reboots.
Configuration Guide (AADvance Controller) The RSLinx Classic Lite software must be installed before you can install the ControlFLASH software. RSLinx software is a communications software package that you can use with a wide variety of rockwell automation applications and hardware. The ControlFLASH software uses the RSLinx Classic Lite software to communicate over Data highway Plus, DFI, DH485, ControlNet, DeviceNet and Ethernet networks.
4) Click Browse to select the location of the installation or Next to select the default location. 5) Click Next to start the installation.
Configuration Guide (AADvance Controller) ControlFLASH installs. 6) To launch ControlFLASH select the Yes I want to launch controlFLASH option, then click Close.
ControlFLASH will launch and you can now upgrade the Processor Module firmware. Upgrade the Processor Module Recovery Mode Firmware This is the recommended procedure to upgrade the processor module firmware using the ControlFLASH Utility. Note: ControlFLASH can upgrade 3 processor modules at once when installed into a 9100 base unit and they are in the Recovery Mode.
Configuration Guide (AADvance Controller) 2) Click Next. 3) Select T9110 from the list.
5) Select the firmware revision for the latest Release.
Configuration Guide (AADvance Controller) The continue message is displayed: 7) Click Yes to continue with the update A progress bar is displayed 4-12 Document: 553633 ICSTT-RM405f-EN-P Issue 07
When the progress bar reaches the end, it may take several minutes for the next screen to appear. Note: It has not locked up! Wait until the next message box appears ! You may get a "Comms error message" as AADvance processors do not automatically reboot as ControlFLASH expects them to but the firmware download should have completed correctly. 8) Click OK. Wait another couple of minutes and the same message will appear again. 9) Click OK.
Configuration Guide (AADvance Controller) The following message now appears. 10) Click OK and another error message is displayed. 11) Click OK then Cancel to Exit ControlFLASH. 12) Reboot the processor module by switching the power OFF then ON and hold in the Fault Reset button as the module reboots until the Aux LED goes amber. The processor module(s) will reboot into the Recovery Mode indicated by the following LED states on the processor module.
4) Click Browse to select the location of the installation or Next to choose the default location. 5) Click Next to confirm the installation. ControlFLASH installs and shows the progress bar. 6) Click Yes I want to launch ControlFLASH, then click Close. Upgrade Processor OS, FPGAFPGA, LSP and BUSP Firmware This procedure describes how to upgrade the processor module firmware using ControlFLASH. Note: ControlFLASH can upgrade 3 processor modules at once when installed into a 9100 base unit.
Configuration Guide (AADvance Controller) 4) Browse to the device in the RSLinx window 5) Select the firmware revision for the latest Release.
6) Check the summary details, click Finish The continue message is displayed: 7) Click Yes to continue with the update Document: 553633 ICSTT-RM405f-EN-P Issue 07 4-17
Configuration Guide (AADvance Controller) A progress bar is displayed Note: if the processor is not in the Recovery Mode the following error is displayed. Follow the procedure in Stage 1 to download the recovery Mode.
After the progress bar reaches the end, it may take several minutes for the next screen to appear. Use the View Module Firmware Versions procedure to verify that the upgrade has worked. Configure Controller Type (Standard or Eurocard) The controller can be configured as a standard AADvance controller, a Eurocard controller or a mixture of both. To configure the controller type, do the following: 1) Select the I/O Wiring icon . 2) Right click on Config1 (9000 Series Controller).
Configuration Guide (AADvance Controller) Note: Selecting Standard or Mixed will configure 48 empty IOB IO slots for I/O modules (IOB IO Bus 1 and IO Bus 2); selecting Eurocard will configure 18 empty slots on IOB IO Bus 1. Configure the Top-level Process Safety Time (PST) The PST setting defines the maximum time that the processor will allow the outputs to remain in the ON state in the event of certain internal diagnostic faults or systematic application faults.
Set PST to its Default Value You can reset the PST to its default value, do the following: 1) Select the 9110 Processor in the Equipment tree view. The 9110 Module Editor opens. 2) Select the 9110 tab. 3) Clear the entry in the Process Safety Time field. 4) Press return. The Process Safety Time will change to its default value. Configure the Processor Battery Alarm The 9110 Module Editor includes a configuration setting for the battery alarm. It can be set to Enabled or Disabled as required.
Configuration Guide (AADvance Controller) Configure the Serial Ports The AADvance controller provides up to six serial communication ports, two for each T9110 processor module present. . The serial port settings define the protocol ('type') and the data characteristics of each of the serial ports. To configure the serial ports do the following: 1) Select the Serial Ports tab. The Serial Ports Editor dialog box opens. 2) Select the communication parameters from the drop down lists, click Apply.
Serial Port Protocols The serial ports support the protocols listed in the table.
Configuration Guide (AADvance Controller) Time Synchronization (SNTP) The AADvance controller supports the Simple Network Time Protocol (SNTP) service that can circulate an accurate time around the network. It can be configured to operate as a SNTP client or server. As an SNTP client the controller will accept the current time from external Network Time Protocol (NTP) and SNTP network time servers.
Note: The first address represents that of the primary server and the second one the secondary server for each processor module. At start up the SNTP client will choose the primary server of the "lowest" slice; if no primary signal is valid the SNTP client looks for an active secondary server signal. For non-fault tolerant operation, define one SNTP server for only one processor. The other processors will automatically synchronize to it and will inherit the time.
Configuration Guide (AADvance Controller) If you select Unicast mode for a processor the controller will wait to be polled by a client and then respond with a time signal; it will not broadcast any time signals. If you select Broadcast mode for a processor the controller will regularly braodcast: it will also respond to unicast polling requests on that interface. Note: If you set a processor Broadcast IP Address to zero (0.0.0.0) it will disable the server on that interface.
Using the Controller as a Modbus Slave The AADvance controller can operate as a Modbus slave, supporting up to ten Modbus slaves on each 9110 processor module. This gives a capacity of thirty Modbus slaves for a controller with three processor modules. Note: As a Modbus slave device, the controller only transmits data upon a request from a Modbus master, and does not communicate with other slaves.
Configuration Guide (AADvance Controller) Configure the Controller Modbus Slaves You have to configure the communication parameters for each Modbus slave you implement within the AADvance controller. To configure a Modbus Slave do the following: 1) Select the Modbus Slaves tab. The 9110 Modbus Slaves Editor dialog box opens. 2) In the Name column, locate the processor and slave you wish to configure. 3) Set the Connection field, click Apply.
Note: The Port field does not apply for a serial connection, and is disabled. 5) If you set the Connection to Ethernet, do the following: Set the Protocol field, click Apply. Note:As a Modbus slave, the controller supports Modbus RTU, using a serial or Ethernet connection; and Modbus TCP, using an Ethernet connection. You can configure a combination of connections for the Modbus slaves, subject to a limitation of no more than two Modbus RTU slaves using serial communications for each processor.
Configuration Guide (AADvance Controller) Id 1 to 255 1 Port 0 to 65,535 502 Transparent Communication Interface (TCI) The AADvance controller processor module provides a Transparent Communications Interface (TCI) function. This functionality will establish a pass-through communications link between an Ethernet link to a Serial port allowing devices attached to a serial port to be communicated with and for them to reply. The controller does not tamper with or inspect the data passed over the channel.
5) Click on the S1-1 row and set the required Inactivity and Idle values. Inactivity values range from 1s minimum to 65535s maximum with a default value of 600s. After this period, if no data has flowed in either direction, the TCP connection will be closed. Note: TCP connections are also subject to the keep-alive period. Idle values range from 1ms minimum to a maximum of 1000ms with a default value of 3ms.
Configuration Guide (AADvance Controller) DiffServ Configuration This option allows you to specify the priority of IP traffic and is particularly useful for ensuring that high priority services are either not affected or less affected during periods of network congestion. When you set up this option you apply a priority value to a service and therefore differentiate it from less important services.
A tick in the box enables the DiffServ function 3) Select a Value for TCP Negotiation This option allows you to choose when the IP's ToS for TCP segments is set. Assuming that your table has applicable rules for this traffic and that AADvance is acting as a server: If the TCP negotiation value is set to "no" the ToS value will not be applied during the TCP 3-way handshake, it will only be applied once the connection is made.
Configuration Guide (AADvance Controller) Ethernet Forwarding When enabled, the "Ethernet Forwarding" feature will forward all Ethernet packets destined for a host (3rd Party Device) connected to one of the AADvance’s Ethernet ports along with any broadcast and multicast Ethernet traffic. Incoming messages on the other port will be forwarded directly to the second. The forwarded messages will be unaltered by the AADvance controller. This feature can be enabled using the AADvance Discover utility.
2) Stop the resource running. 3) From the Start button select AADvance Discover utility. 4) Locate your controller on the list displayed and make sure that it is Configurable . 5) Double click on the Controller ID (which is derived from the MAC address of the port (E1-1) in the Controller ID field. The Resource Number and IP Address dialog box opens.
Configuration Guide (AADvance Controller) 6) Select the Enable Ethernet Forwarding box so a tick appears in the box. 7) Click on the Apply button. You have now enabled the Ethernet forwarding for that processor. 8) To disable the Ethernet Forwarding repeat this procedure, de-select the Enable Ethernet Forwarding on this dialog box and click on Apply. About T9110 Processor Variables The T9110 processor module provides a number of status and control variables that are available to the application.
1) Select the Variables tab of the 9110 Processor Editor. The 9110 Variables Editor dialog box opens. 2) Select a rack, e.g. Status Registers. The editor displays a list of associated channel variables. 3) Select a Channel. 4) Click the button. The Select Variable dialog box opens. 5) From the list select an application variable to wire to the processor variable, click OK. 6) Repeat for each subsequent variable to be wired. 7) Return to the 9110 Processor Editor dialog box and click Apply.
Configuration Guide (AADvance Controller) Status Integers The variables in the rack of status integers provide information about the controller to the application. Number of Locked Input Variables Direction: input to application from controller Type: word Values: 0 to 65,535 Description: Reports the number of input variables that have been locked by the user. The upper limit of 65,535 represents the capacity of the variable; in practice, the limit is the number of variables in the application.
Processor Module B Temperature Direction: input to application from controller Type: word Values: 0 to 65,535 Description: Reports the temperature of the 9110 processor module in the given slot in degrees centigrade. Set to 0 (zero) if no processor module is present. Processor Module C Temperature Direction: input to application from controller Type: word Values: 0 to 65,535 Description: Reports the temperature of the 9110 processor module in the given slot in degrees centigrade.
Configuration Guide (AADvance Controller) Control Integers The variables in the rack of control integers enable the application to send specific information to the controller. AUX LED Colour Direction: output from application to controller Type: word Values: 0..3 (0 = off, 1 = red, 2 = green, 3 = amber) Default 0 Description: Sets the state of the LED indicator labelled 'Aux' on every 9110 processor module.
FALSE = No fault reset button is active. Default: FALSE Description: Reports that the fault reset button on any processor module has been pressed. The system health reset is triggered by pressing the button, but the value does not change to TRUE until the beginning of the next application cycle. The value remains TRUE for the duration of the cycle and then reverts to FALSE, even if the button has been held down throughout.
Configuration Guide (AADvance Controller) Processor Module B On-line Direction: input to application from controller Type: boolean Values: TRUE = The 9110 processor module in the given slot is on-line FALSE = The processor module is off-line Default: TRUE Description: Reports that a processor module within a dual or triple modular redundant configuration is present and is communicating through the inter-processor link to one or both of its peers. Reports that a simplex processor module is present.
Processor Module B Health Direction: input to application from controller Type: boolean Values: TRUE = The 9110 processor module in the given slot is healthy and its Healthy LED indicator is green. FALSE = The processor module is faulty and its Healthy LED indicator is red. Description: Reports the health status of a processor module.
Configuration Guide (AADvance Controller) Direction: input to application from controller Type: boolean Values: TRUE = power feed voltage is within specification (18 to 32V dc). FALSE = power feed is outside specification. Description: Reports the health of power feed 1 (nominal 24V dc) to the 9110 processor module in the given slot.
Processor Module A Ready Direction: input to application from controller Type: boolean Values: TRUE = The 9110 processor module in the given slot is synchronized (see description) FALSE = The processor module is out of synchronization or missing. Description: Reports that a processor module within a dual or triple modular redundant configuration is present and is synchronized with one or both of its peers. Reports that a simplex processor module is present.
Configuration Guide (AADvance Controller) FALSE = The voltage of the back-up battery is low or the battery is missing. Description: Reports the health status of the back-up battery in a processor module. Note: The battery voltage is checked at start up, then re-checked every 24 hours (elapsed time).
Control Booleans The variables in the rack of control booleans enable the application to send specific information to the controller. Unlock All Locked Variables Direction: output from application to controller Type: boolean Values: TRUE = Remove all locks. FALSE = No effect. Default FALSE Description: Removes all user locks on input and output variables. Set System Health Alarm Direction: From the application to the controller.
Configuration Guide (AADvance Controller) HART Passthrough Direction: Appliction to the controller. Type: BOOLEAN Values: TRUE = HART Passthrough is enabled and available for an Analogue Module. FALSE = HART Passthrough is disabled and not available. DEFAULT = FALSE Description: Initiates the HART Passthrough feature to support HART messages on the Analogue Input and Output Modules.
RTC Status: Day of Month Direction: input to application from controller Type: word Values: 1 to 31, or 0 (see description) Description: Reports the oldest value of real-time clock (RTC) day of the month as voted by every 9110 processor module which is present and synchronized. Only updated if the realtime clock control Boolean RTC Read is set to TRUE. If RTC Read is FALSE, the value will be 0 (zero).
Configuration Guide (AADvance Controller) RTC Status: Seconds Direction: input to application from controller Type: word Values: 0 to 59 Description: Reports the oldest value of real-time clock (RTC) seconds as voted by every 9110 processor module which is present and synchronized. Only updated if the real-time clock control Boolean RTC Read is set to TRUE. If RTC Read is FALSE, the value will be 0 (zero).
RTC Program: Year Direction: output from application to controller Type: word Values: 2,000 to 2,399 Default 0 (zero) Description: Specifies the year part of the date to be written to the real-time clock the next time the RTC control variable RTC Write is asserted TRUE. The value will be written only if the RTC control variable Year is TRUE.
Configuration Guide (AADvance Controller) RTC Program: Hours Direction: output from application to controller Type: word Values: 0 to 23 Default 0 (zero) Description: Specifies the time of day (in hours) to be written to the real-time clock the next time the RTC control variable RTC Write is asserted TRUE. The value will be written only if the RTC control variable Hours is TRUE.
Default 0 (zero) Description: Specifies the time of day (in milliseconds) to be written to the real-time clock the next time the RTC control variable RTC Write is asserted TRUE. The value will be written only if the RTC control variable Milliseconds is TRUE. RTC Control Variables The variables in the rack of RTC control variables regulate updates to the real-time clock.
Configuration Guide (AADvance Controller) RTC Control: RTC Read Direction: output from application to controller Type: boolean Values: TRUE = The controller updates RTC status values on each application cycle. FALSE = RTC status values are static (do not update). Default: [TBD] Description: Determines whether the RTC status variables (RTC status year, RTC status month, RTC status day of month, RTC status hours, RTC status minutes and RTC status seconds) will update in real time.
RTC Control: Month Direction: output from application to controller Type: boolean Values: TRUE = RTC program month will be applied by RTC Write. FALSE = RTC program month will be ignored. Default FALSE until an initial value is specified in the application. Description: Defines whether the value of the RTC program variable named Month should be applied to the real-time clock the next time the RTC control variable named RTC Write is set to TRUE.
Configuration Guide (AADvance Controller) RTC Control: Hours Direction: output from application to controller Type: boolean Values: TRUE = RTC program hours will be applied by RTC Write. FALSE = RTC program hours will be ignored. Default FALSE until an initial value is specified in the application. Description: Defines whether the value of the RTC program variable named Hours should be applied to the real-time clock the next time the RTC control variable named RTC Write is set to TRUE.
Description: Defines whether the value of the RTC program variable named Seconds should be applied to the real-time clock the next time the RTC control variable named RTC Write is set to TRUE. Note: The RTC program variable is only updated if the RTC control variable RTC Read is set to TRUE and all other RTC Control Variables are set to TRUE. RTC Control: Milliseconds Direction: output from application to controller Type: boolean Values: TRUE = RTC program milliseconds will be applied by RTC Write.
Configuration Guide (AADvance Controller) 6) Set RTC Read to be always True (the time will not be written unless this point is also True). 7) Set RTC Control elements Hours, Minutes and Seconds to be always True. 8) Use an external trigger to change RTC Write from False to True at the time you have preset in step 3.
Chapter 5 Configuring the Controller I/O This chapter describes the configuration process for defining the controller I/O hardware in the AADvance Workbench. In This Chapter About Configuring I/O Modules...................................................................... 5-1 About Configuring I/O Channels .................................................................. 5-16 Configuring Digital Inputs ...............................................................................
Configuration Guide (AADvance Controller) Example I/O Slot Configuration In the example illustrated, the modules have been configured as follows: A redundant group of analogue input modules has been configured in the first three slots. Two digital input modules are in the next two slots. There is a single digital input module. There is a group of two digital output modules. Two single digital output modules. Important Note: For Release 1.
Example Controller Configuration This example controller has two 9110 processor modules and supports 8 digital inputs and 8 digital outputs. Note: The '9801' and '9851' illustrated are simplex termination assemblies for the I/O modules and provide the connections for the field elements. This controller has the following physical layout: the two I/O modules are installed to the right of the processor base unit, which is IO Bus 1.
Configuration Guide (AADvance Controller) The slot and bus numbers must be the same as the actual physical position of the installed modules. Therefore, for this example you would allocate I/O modules as follows: A 9401 module to the empty slot 1 on IO Bus 1 A 9451 module to the empty slot 2 on IO Bus 1. Assign I/O Modules to I/O Bus Slots If you are assigning a single module you can assign the module to any empty I/O bus slot.
4) Select the required module, then move the cursor to the right and select the number of modules you require. 5) Repeat this for all the modules you want to configure. Clear an I/O Bus Slot To clear an I/O bus slot do the following: 1) Select the Equipment tab. 2) Right-click to select Clear Slot. The module will be removed from the slot. The slot will now display as Empty ready to be re-assigned a module. Note: The channel variable wiring will automatically be unwired.
Configuration Guide (AADvance Controller) Move a Module to a Different Slot To move an assigned module to a different slot do the following: 1) Select the Equipment tab. 2) Right-click to select the Move To option. 3) Move the cursor to the right and select the IO Bus 1 Position you want to move to. The module is automatically re-assigned to the selected slot. Note: The channel variable wiring will move with the module to the new slot and is automatically renumbered.
Resize a Group of Modules You can reduce the size of a redundant group of modules from a triple to a double then a double to a single module. To reduce the size do the following: 1) Select the Equipment view. 2) Right click to select Resize to 3) Select the number of modules you want to reduce or increase the size to. One module will be removed from a group to become a single module slot or added to become a group from a single slot. 4) Repeat as required.
Configuration Guide (AADvance Controller) Enable or Disable the On-line Update Feature WARNING Doing an on-line update is the responsibility of the user. It is highly recommended that an on-line change is not performed unless absolutely necessary as it could reduce the safety integrity of the system while doing the change. Also, if the changes are not carried out correctly it can stop the application.
Perform an On-line Update An on-line update changes the AADvance Workbench I/O configuration and the I/O hardware it is a two stage process.
Configuration Guide (AADvance Controller) Start Modification Are there any physical Changes ? NOTE: Physical changes to the configuration require a two step process, if this process is NOT followed the operating process may be affected.
Change application variables or the program. Add new I/O base units, termination assemblies and extra I/O modules. Delete modules from the system. Change the size of a termination assembly to change the size of the I/O module configuration. Move a module to a different slot. WARNING If you change the internal I/O configuration in the Workbench but fail to carry out the same hardware changes the application will stop and the Run LED on the affected modules will go RED.
Configuration Guide (AADvance Controller) Configure the I/O Module Process Safety Time When you configure the process safety time for an I/O module, you can choose to inherit the top-level value set for the processor or specify a value for the I/O module. To define the I/O module process safety time do the following: 1) Select a module from the I/O Bus.
The variables dialog box opens. 4) Select the variable you declared in the Dictionary. The variable is displayed in the Variable field. The status variables are automatically assigned and appear in the Wiring column with the description in the Description column. 5) Repeat steps 1 to 4 for other I/O modules.
Configuration Guide (AADvance Controller) T9K_TA_GROUP_STATUS (I/O Module Status Information) The data structure for module status information (T9K_TA_GROUP_STATUS) provides the elements detailed in the table. Note: The controller interrogates an I/O module (designated 'X' in the table) according to the physical arrangement of the module and its position in a group. A simplex module is designated as module A; a duplex module as A or B and a triplicated module as A, B or C.
.XRUN BOOL Run status Reports the run status of module X TRUE: the module is on-line and reporting channel values, or requires manual intervention (pressing the Fault Reset button) before values can be reported, otherwise FALSE .XSDN BOOL Shutdown status Reports that module X requires manual intervention (pressing the Fault Reset button) before values can be reported TRUE: the module needs manual intervention .
Configuration Guide (AADvance Controller) About Configuring I/O Channels The AADvance Workbench provides a set of variable structures to wire to I/O channels. When you declare the I/O channels variables using your own tagnames you can declare one of two types of structure (compact and full); alternatively, the primary variable can be assigned directly to the base variable type.
3) Click the button adjacent to the Channel Variable fields. 4) Choose a data structure from the three options displayed: Simple, Compact, Full. The Select Variables dialog box opens. 5) Select a named structure, click OK. 6) Repeat steps 2 to 5 for each channel you want to wire. Wire Variables to Analogue Input Channels To wire variables to analogue input channels do the following: 1) Select an analogue input module on the I/O bus.
Configuration Guide (AADvance Controller) Wire Variables to Digital Output Channels To wire variables to digital output channels do the following: 1) Select a digital output module on the I/O bus. The module status variable appears in the Variable field. 2) Select the channel that you want to wire to a variable. 3) Click the button next to the Channel Variable fields. 4) Choose a data structure from the three options displayed: Simple, Compact, Full.
Wire Variables to Analogue Output Channels To wire variables to analogue output channels do the following: 1) Select a analogue output module on the I/O bus. The module status variable appears in the Variable field. 2) Select the channel that you want to wire to a variable. 3) Click the button next to the Channel Variable fields. 4) Choose a data structure from the three options displayed: Simple, Compact, Full. The Select Variables dialog box is displayed.
Configuration Guide (AADvance Controller) T9K_DI_COMPACT and T9K_DI_FULL (Digital Inputs) The two data structures for digital input channels (T9K_DI_COMPACT and T9K_DI_FULL) provide the elements detailed in the tables. Table 6: T9K_DI_COMPACT Structure for Digital Inputs Identifier Type Description Remarks .DI BOOL Input state TRUE: input voltage above threshold T6 FALSE: input voltage below threshold T5 .
.STA USINT State Reports a state value for the channel: 1 = open circuit 2 = de-energized 3 = indeterminate 4 = energized 5 = short-circuit 6 = over voltage 7 = faulted Note: (†) Discrepancy can only be reported TRUE when two or three modules are active in a group. (††) The voltage element cannot report values below 0mV.
Configuration Guide (AADvance Controller) Threshold Values for Digital Inputs The module determines the channel state and the line fault status by comparing the channel input voltage with defined threshold values. You can define your own threshold values or use a set of default values. The values you choose for the module are inherited by each channel; you can define different thresholds for individual channels later.
Document: 553633 ICSTT-RM405f-EN-P Issue 07 5-23
Configuration Guide (AADvance Controller) Define Thresholds for a Digital Input Module To define your own threshold values do the following: 1) Select the Thresholds tab on the module editor. A set of default values is shown in the threshold fields. 2) To enter your own values select the Use Custom Thresholds box, enter your own values in the threshold fields, click Apply. 3) To restore the default values, Click Default then de-select the Use Custom Thresholds, click Apply.
Default Thresholds for Digital Inputs The default threshold values for digital inputs are for a standard (non-line monitored) 24V dc digital input channel.
Configuration Guide (AADvance Controller) Configuring Analogue Inputs You can wire analogue input channels to the following variable type and data structures: REAL (the gives a floating-point value representing 4 to 20mA) T9K_AI_Compact (provides three elements) T9K_AI_Full (six elements) The structures provide additional information about the input, such as discrepancy status. You can also configure analogue inputs to operate with HART devices, and define custom thresholds.
.CNT INT Raw count A count representing the current on the channel in units of 1/256mA 0 represents 0mA; 5,120 represents 20mA Accurate to within ± 13 counts, equivalent to ± 0.05mA .LF BOOL Line fault TRUE: state (.STA) is 1, 5, 6 or 7 FALSE: state (.STA) is 2, 3 or 4 .DIS BOOL Discrepancy TRUE: there is a discrepancy in current greater than 2% between the channels of two or three modules in a redundant configuration (†) .
Configuration Guide (AADvance Controller) HART The AADvance controller supports utilizing dedicated HART modems on each analogue input and output channel allowing HART field device status, diagnostics and process data to be integrated into the application logic, thus increasing the level of SIF diagnostics significantly. The AADvance analogue input/output modules use HART commands #03 to collect data from the field device as defined by Revision 5 of the HART specification.
AADvance uses a single dedicated Ethernet port for HART passthru communication. Supports the AADvance DTM provided by Rockwell Automation. A typical HART set up is shown below: Figure 1: Example HART Pass-through System Configuring HART HART variables can be configured on each analogue input or output channel to monitor the HART field device and to enable the HART Passthru feature.
Configuration Guide (AADvance Controller) HART Variables The two HART variables are: T9K_AI_HART to provide HART device Monitoring . T9K_AI_HART_FULL to provide HART and passthru communication monitoring. Table 10: T9K_AI_HART Data Structure Identifier Type Description AIM_HART_FULL_01.I REAL Current (mA) AIM_HART_FULL_01. V1 REAL Primary variable AIM_HART_FULL_01. U1 BYTE Primary variable units code AIM_HART_FULL_01. V2 REAL Second variable AIM_HART_FULL_01.
AIM_HART_FULL_01.I BYTE .DEVICE Device status The device status byte mimics the HART field device status. Appendix E of the HART Application Guide gives details.
Configuration Guide (AADvance Controller) Table 11: T9K_AI_HART_FULL Data Structure Identifier Type Description AIM_HART_FULL_01.I REAL Current (mA) AIM_HART_FULL_01. V1 REAL Primary variable AIM_HART_FULL_01. U1 BYTE Primary variable units code AIM_HART_FULL_01. V2 REAL Second variable AIM_HART_FULL_01. U2 BYTE Second variable units code AIM_HART_FULL_01. V3 REAL Third variable AIM_HART_FULL_01. U3 BYTE Third variable units code AIM_HART_FULL_01.
AIM_HART_FULL_01. ELAPSED DINT Elapsed time in ms. since last valid non passthrough communication AIM_HART_FULL_01. PASSTHROUGH BOOL Passthrough Communication status This element resets to zero whenever fresh data is received. The data is refreshed approximately every four seconds for a small system. This rate proportional to the system size and the number of HART devices in use, so it will be slower on larger systems. If HART Passthrough is enabled then no fresh data is received.
Configuration Guide (AADvance Controller) 8) Select the button and choose the T9K_AI_HART variable. 9) Repeat this procedure for the other channels that will use HART enabled devices. Configure HART Passthrough AAdvance can be used to provide access to HART Field Devices connected to Analogue Input and Analogue Output channels from an ASM package.
The AADvance provides a transparent connection between the asset management software and the field device. AADvance controller provides a global control variable allowing the user to control HART Passthru via the application, the AI and AO channels each provide variables for monitoring HART Passthru activity: one to monitor the elapsed time since the last non-pass-through communication (AIM_HART_FULL_xx.ELAPSED) and one to indicate that HART messages are in progress (AIM_HART_FULL_xx.PASSTHROUGH).
Configuration Guide (AADvance Controller) Configuration Procedure 1) In the Dictionary create the following variables. 2) Create a variable which will be used to enable/disable control in the application, this variable must be BOOL type with its direction set to output. 3) Create variables for each Analogue Input/Output channel connected to a HART Field Device that the AMS is required to communicate with, this variable must be the T9K_AI_HART_FULL type with its direction set as input.
6) Select the Control Booleans rack and ensure that the Channel 3 is wired to the HART_CONTROL Boolean variable. 7) Select the Analogue Input module you want to use for the HART messages and select a channel. 8) Select the HART tab. 9) Click on the Enable HART on this channel to put a tick in the box. 10) Wire the Channel to the AIM_HART_FULL variables that you set up in the dictionary.
Configuration Guide (AADvance Controller) About Threshold Values for Analogue Inputs The module determines the channel state and the line fault status by comparing the channel input current with defined threshold values. You can define your own threshold values or use a set of default values. The values you choose for the module are inherited by each channel; you can define different thresholds for individual channels later.
Define Thresholds for an Analogue Input Module To define your own threshold values do the following: 1) Select the Thresholds tab on the module editor. A set of default values is shown in the threshold fields. 2) To enter your own values select the Use Custom Thresholds box, enter your own values in the threshold fields, click Apply. Note: You can enter the values in counts (the default units) or in milliamps.
Configuration Guide (AADvance Controller) Default Thresholds for Analogue Inputs The default threshold values for analogue inputs are for a standard (non-line monitored) 24V dc analogue input channel. The default values are given in the table.
Configuring Digital Outputs You can wire digital output channels to the following variable type and data structures: BOOL (the gives the commanded state) T9K_DO_Compact (provides three elements) T9K_DO_Full (seven elements) The structures provide additional information about the output, such as line fault status and discrepancy status. Note: The controller writes its digital outputs once per application cycle; the digital output variables are also updated once per application cycle.
Configuration Guide (AADvance Controller) .CF BOOL Channel fault TRUE: module diagnostics detect a fault in the channel electronics or firmware (state = 7) .V UINT Voltage Reports the channel voltage at the output terminals, in units of millivolts and with an accuracy of ± 500mV (††) .I INT Current Reports the current for the channel in milliamps and with an accuracy of ± 2mA and ± 10% of measurement .
The State Variable for Digital Outputs The state variable for a digital output is an unsigned integer with a value from 1 to 7 representing the following: 1 = no-vfield: the field supply voltage is at or below 18V dc for that channel. Note: When the state variable is 1, the field voltage () is reported as 0mV. 2 = de-energized: the commanded state is FALSE and the channel is de-energized.
Configuration Guide (AADvance Controller) Overcurrent Protection for Digital Outputs The AADvance controller has three mechanisms to protect its digital output channels: Inrush current protection Short circuit protection for energized channels Short circuit protection for de-energized channels The controller tolerates inrush currents so that its digital outputs can energize capacitive loads without causing the controller to report a short circuit.
Faulted State for Digital Outputs A digital output channel is faulted (the state reports a value of 7) when normal operation or diagnostics tests have identified a specific fault condition. A single identified fault condition thus results in a state value of 7.
Configuration Guide (AADvance Controller) Off will disable the output channel when the module is shutdown due to a loss of communications with the processor or failure of the module. Hold Last State will force the output to remain in its last commanded state during a module shutdown. When channels go to Hold Last State other compensating measures need to be put in place during the failure and the communications must be restored within the MTTR to maintain the safety rating of the system.
Status Variables for Digital Output Modules The 9451 digital output module provides a number of status variables that are available to the application. The 9451 Variables Editor presents the variables in two collections, which it calls 'racks': Status Booleans, and Power Status Integers. Wire Status Variables to a Digital Output Module To wire a status variable to a digital output module do the following: 1) Navigate to the digital output module in the equipment tree view.
Configuration Guide (AADvance Controller) Unwire Status Variables from a Digital Output Module To disconnect a status variable from a digital output module do the following: 1) Select the Variables tab of the 9451 Module Editor. The 9451 Variables Editor dialog box opens. 2) Select the relevant rack. The editor displays a list of associated variables. 3) Select the variable to be unwired, click the X button. 4) Click Apply. The variable will be unwired.
Group Field Power Health Direction: input to application from controller Type: boolean Values: TRUE = all field power supplies for all active digital output modules in the group are within the range 18V to 32V dc inclusive FALSE = one or more field power supplies to an active module is less than 18V dc or greater than 32V dc. Description: Provides a top level indication of the health of field power supplies to active digital output modules. Note: The controller incorporates a 0.
Configuration Guide (AADvance Controller) A Module Field Power Voltage 1 Direction: input to application from controller Type: DINT Values: 0 to 48,000mV or greater (limited by capacity of DINT variable) Description: Reports the voltage from the field power supply, for the specified module and field power input. Accuracy is 500mV.
Configuring Analogue Outputs You can wire analogue output channels to the following variable type and data structures: REAL (the gives the commanded state) T9K_AO_Compact (provides three elements) T9K_AO_Full (seven elements) The structures provide additional information about the output, such as line fault status and discrepancy status.
Configuration Guide (AADvance Controller) T9K_AO_COMPACT and T9K_AO_FULL (Analogue Outputs) The data structures for analogue outputs (T9K_AO_COMPACT and T9K_AO_FULL) provide the elements detailed in the tables. Table 15: T9K_AO_COMPACT Structure for Analogue Outputs Identifier Type Description Remarks .CV REAL Command Value Demanded current. A scaled, floating-point value representing the analogue loop current. Default scaling factor is 0 to 100% representing 4 to 20mA .
.STA USINT Channel state Reports a state value for the channel: 1 = no vfield ( < 18Vdc) 2 = off (demand < 0.4mA) 3 = no load/open circuit 4 = on (demand > 0.4mA) 5 = compliance fault (demand cannot be met) 6 = reverse polarity (< -1Vdc) 7 = faulted Faulted State for Analogue Outputs An analogue output channel is faulted (the state reports a value of 7) when normal operation or diagnostics tests have identified a specific fault condition.
Configuration Guide (AADvance Controller) 1) Select the slot with the analogue output module. The module status variable name that you assigned appears in the Variable field. 2) Select the channel to configure and click the Advanced tab. The 9481/9482 Advanced Channel Settings dialog box opens. 3) Put a tick in the box labelled Use Custom Advanced Channel Settings. 4) Choose the advanced channel settings from the options.
Document: 553633 ICSTT-RM405f-EN-P Issue 07 5-55
Chapter 6 Setting Up This chapter provides an overview of the setting up process for the AADvance AADvance Workbench, including creating a new project. In This Chapter Create a New Project ....................................................................................... 6-1 Compiler Verification Tool .............................................................................. 6-2 Allocate IP Addresses for Network Communications ..............................
Configuration Guide (AADvance Controller) Compiler Verification Tool The Compiler Verification Tool (CVT) is a software utility that validates the output of the application compilation process. It is automatically enabled for resources when a project is created and when you add a resource to an existing project.
The Compiler Options dialog box is displayed. 3) If the Enable compilation verification box has a tick in it then click OK and proceed with your compilation. 4) If the box does not have a tick in it Click on the box so a tick appears. You have now enabled CVT.
Configuration Guide (AADvance Controller) Allocate IP Addresses for Network Communications The AADvance system uses Internet Protocol (IP) for all communications between the controller and the AADvance Workbench. This includes downloading the application to the controller and real-time monitoring of the system in operation. For many systems, the administrator of the local area network will allocate the address for the controller.
Configure the IP Address of the Target Controller To connect the AADvance Workbench project to the target controller you have to tell the project the IP addresses allocated to the controller. Do the following: 1) Select the Hardware Architecture view then double-click on the vertical connection between the SNCP network line and the configuration. 2) The Connection - Properties dialog box opens. 3) Enter the IP Addresses in the Value field for each of the required Ethernet network.
Configuration Guide (AADvance Controller) You have now configured the IP addresses of the configuration to match the controller.
This page intentionally left blank Document: 553633 ICSTT-RM405f-EN-P Issue 07 6-7
Chapter 7 Using the Dictionary This chapter introduces the Dictionary in the AADvance Workbench. It explains how to create and modify variables, and store them in the Dictionary. In This Chapter About the Dictionary ......................................................................................... 7-1 Properties for AADvance Variables ............................................................... 7-1 Create or Modify Variables in the Dictionary .............................................
Configuration Guide (AADvance Controller) Type: Standard IEC 61131 types as a set of pull down options: Boolean (Bool), Short Integer (SINT), Unsigned Short Integer (USINT), BYTE, Integer (INT), Unsigned Integer (UNIT), WORD, Double Integer (UDINT), Double Word (DWORD), Long Integer (LINT), Unsigned Long Integer (ULINT), REAL, Long Real (LREAL), Timer (TIME), DATE, STRING. Type also includes the standard AADvance structures and user defined structures.
Example: 'Pump on'. Modbus: Modbus address of the variable, range 1 to 65,536. SOE: Defines how Sequence of Events (SOE) is enabled for a boolean variable. SOE can trigger on a falling edge or rising edge or both. Write Access: Indicates that a variable can be written to an external client (True). The default value is False. Note: You must now set the Write Access parameter to TRUE if you need to write to that attribute. CIP: This indicates that a variable uses CIP or not.
Configuration Guide (AADvance Controller) Create or Modify Variables in the Dictionary To open the Dictionary view select the dictionary button dialog box opens. . The Variable Grid Create new variables or modify the properties of variables using this interface. You can edit the contents of individual cells or complete rows. When defining variables, you need to specify the general properties and, if required, the Modbus and SOE properties.
A blue line will highlight the first element of the first row. 2) Select the element you want to change within a row, then double-click on the element. The variable dialog box opens.
Configuration Guide (AADvance Controller) Edit the Contents of a Row in the Dictionary To edit the contents of a row in the Dictionary do the following: 1) Select line mode by clicking the button. 2) Double-click on an empty line to create a new variable; double-click on an existing line to modify a variable. A variable properties dialog box opens. 3) Make the necessary changes to the variable fields. Note: For the Type field you can also select the Select Data Types browser by clicking .
SOE Service Parameters The AADvance Workbench supports a Sequence of Events (SOE) service for boolean variables. When a Sequence of Events service is defined, use the SOE tab of the Variable dialog box to define the SOE properties: Falling-edge: the indication of whether the service detects a fall from TRUE to FALSE. When this box is checked, the falling edge will be detected; when it is not checked, the transition will be ignored.
Configuration Guide (AADvance Controller) This page intentionally left blank 7-8 Document: 553633 ICSTT-RM405f-EN-P Issue 07
Chapter 8 Using CIP over EtherNet/IP This chapter introduces CIP over EtherNet/IP, and shows how to configure the protocol within the AADvance Workbench. It explains how to create a CIP network, and then configure the exchange of data. In This Chapter CIP over EtherNet/IP......................................................................................... 8-1 Define a CIP Network.......................................................................................
Configuration Guide (AADvance Controller) Note: The CIP Protocol is intended to allow AADvance users to exchange data between AADvance controllers and the Allen Bradley Logix family controllers, using produce/consume messaging. Produce/Consume messaging does not support downloading to or for monitoring AADvance controllers. It is not recommended to use the CIP network to exchange data between AADvance controllers unless this is exclusively for non-safety data.
The AADvance Workbench inserts a network into the Hardware Architecture view. 4) Create a connection between a configuration and the newly inserted CIP network. Note: You can only connect Series 9000 and Series 8000 configurations to a CIP network. If you try to connect a CIP network to a configuration that does not support CIP (for example, a T6210 system) then the AADvance Workbench displays a warning, and the connection will not be made.
Configuration Guide (AADvance Controller) Data Types for CIP over Ethernet/IP You can use all variables with an IEC 61131-3 data type (or a type derived from an IEC 61131-3 data type) as producers or consumers with CIP over Ethernet/IP, as long as the data type is of size DINT (4 bytes / 32 bits) or larger. You can use array or structure variables, but not the member elements of an array or structure.
Parameters for CIP Producer and Consumer Varaibles Each production variable and consumption variable for CIP over Ethernet/IP communications has a set of parameters as detailed in the tables. Note: A maximum of 128 producer and 128 consumer variables can be defined.
Configuration Guide (AADvance Controller) Configure an AADvance Variable as a Producer When you configure a variable as a producer for CIP over Ethernet/IP do the following: 1) Go to the Dictionary and select a CIP produce variable that you have previously defined in the dictionary. 2) Make sure that the variable is a type that supports CIP over Ethernet/IP. 3) Open the variable properties dialog box and select the CIP tab. 4) Select Producer from the drop-down list.
3) In the Select Module dialog box select Ethernet Module. 4) Open the properties for the selected module and enter the following details: a. Enter a Name b. Enter a Description c. Enter the IP Address of the AADvance Ethernet port that is configured for CIP communications. d. In the Comm Format drop-down selector, choose None.
Configuration Guide (AADvance Controller) Configure an AADvance Variable as a Consumer When you configure a variable as a consumer for CIP over Ethernet/IP, you have to identify the producing Logix controller (it needs a name and an address), provide the name of the corresponding production variable (the remote tag name), and specify the requested packet interval. You can manage a list of producing controllers (called 'devices') from the CIP tab.
The port is the communications route from ControlLogix. The value for the port should always be 1, which specifies the ControlLogix backplane. Other numbers specify different communications routes from ControlLogix. The value for the slot is the slot number in the ControlLogix chassis where the CPU module is installed. These slots start from 0 and are numbered from left to right in the ControlLogix chassis. Click OK. 4) Click OK again to close the Producer List and return to the variable properties dialog.
Configuration Guide (AADvance Controller) Obtaining the Connection Status for a Consumed Variable Your application can obtain the connection status for a consumed variable. To do this, make sure that the variable is a member of a structure data type that has two elements: a first element of the type CONNECTION_STATUS and a second element to match the data type of the variable. Suitable pre-defined structures do not exist within the AADvance Workbench, but you can create them.
You can now examine the structure of 'T' within the Dictionary: The AADvance controller sets the values of the elements T.ConnectionState.RunMode and T.ConnectionState. ConnectionFaulted based upon the run mode of the remote Logix controller and the presence of a communications fault. CIP within the Application Scan Cycle The AADvance controller updates variables configured for CIP production with new values at the end of each application scan cycle, after the logic has been executed.
Configuration Guide (AADvance Controller) Each produced tag uses (1 + number of active consumers) connections in the controller if any of the consumers are multicast. If all consumers are unicast, then the produce tag only uses (number of active consumers) connections. Unicast is only available over Ethernet for V16 and later controllers. Each Consumed tag requires one connection in the controller.
If the produce tags are all unicast, 40 connections will be used in the controller (20 x 2), and 40 connections will be used in the ENBT. No multicast addresses will be used by the ENBT since unicast does not require a multicast address. Example 2 Consider a controller that has one CNB and 20 produce tags, two consumers each, and 10 consumed tags. There will be 70 connections used ((20 x (2+1)) + 10) in the controller. The CNB will have 50 connections, ((20 x 2) +10).
Configuration Guide (AADvance Controller) Set the RSLogix UNICAST Configuration The AADvance controller uses the Unicast mode for CIP You will need to configure the Unicast option in the RSLogix CLX configuration. Produced Variable Select a CLX configuration Produced CIP variable. Check the Allow Unicast Consumer Connections. Consumed variable For a Consumed Variable select a Consumed CIP variable. 1) Set the RPI value to 500.0 ms. (the default value is 20.0 ms).
Further Information on CIP over Ethernet/IP CIP over Ethernet/IP was created by Rockwell Automation for the Logix controller family. For further details of the protocol, such as details of produce/consume tags, check the online help for RSLogix 5000.
Chapter 9 Configuring Modbus Master This chapter describes the process to configure the AADvance controller for Modbus master. In This Chapter Modbus Master.................................................................................................... 9-2 Modbus Standards .............................................................................................. 9-2 Modbus Master Hardware and Physical Connections ............................... 9-2 Modbus Master Command Set ........................
Configuration Guide (AADvance Controller) Modbus Master The AADvance controller can be used as a Modbus master to one or more Modbus slave devices. Slave devices can include programmable logic controllers, remote devices (typically with little or no processing capability) and, more rarely, other functional safety controllers (Trusted or AADvance). The controller supports the Modbus RTU and Modbus TCP protocols, and a subset of Modbus commands.
The Modbus RTU slave devices are connected to one or more of the serial ports on the controller; a typical arrangement will use a multi-drop (RS-485) arrangement. The engineering workstation and the Modbus TCP devices are shown connected to the Ethernet ports on separate networks; alternatively these can be combined onto one network.
Configuration Guide (AADvance Controller) Modbus Master Command Set The AADvance Modbus master supports the subset of Modbus commands listed in the table.
Note: The original Modbus standard defines the address field as a four-digit field, but with a prefix which related to the data type. The areas shown hatched in the illustration show how original-style, five-digit Modbus addresses (for example, a holding register at 40,001) relate to the AADvance memory map. The addresses used for Modbus data transfer listings start at one; the first AADvance Workbench variable network address is 1 and the first coil is 00001. An address of 0 for either field is illegal.
Configuration Guide (AADvance Controller) The illustration shows the message scheduling for a master with three slaves needing four, two and three messages. The total number of messages that the master has to send in a complete poll cycle is equal to the largest number of messages scheduled for any one slave, multiplied by the total number of slaves. So, in this example the total number of messages is 4 3 = 12.
8 Slave 2 9 10 Message 1 Slave 3 Message 3 Slave 1 11 Message 4 Slave 2 12 Repeat message Slave 3 Message 2 Message 1 End of pass through slave 3 End of pass through slave 1 Repeat message Repeat message; end of poll Handling Modbus Communication Errors If a Modbus master encounters communication errors to a slave device, it suspends polling of that slave for a period of time.
Configuration Guide (AADvance Controller) Modbus Service Parameters When a Modbus service is defined, use the Modbus tab of the Variable dialog box to define the Modbus service properties: Write protected: Defines the variable direction, and whether it can be written to. Available for coils and holding registers only. Base Address: The Modbus base address of the variable. If an array is used, this field specifies the starting address of the array.
Modbus Exception Responses The AADvance controller uses the lack of a response from a slave device to detect an error on a Modbus link; also in some cases the slave can return a code for a specific exception. The Modbus protocol allows for these errors by returning an error frame to the master. The error frame consists of the original requested function code with the high bit set and a data field consisting of the specific error code.
Configuration Guide (AADvance Controller) Maximum number of messages 400 Planning for Modbus Master You have to complete three activities to use the AADvance controller as a Modbus master: Make the physical connections from the controller to the slave devices. Configure the characteristics of the serial ports (Modbus RTU only). Set up the project for Modbus master, and configure the application.
Connect a Slave Device, Full Duplex You can use a full duplex serial connection to connect a single Modbus slave device to the AADvance controller. To make the physical connection, do the following: 1) Select a suitable cable. We recommend 3-pair, overall shielded cable. 2) Remove the serial port connector from the 9100 processor base unit. 3) Make the connections shown in the illustration. Terminate the twisted pairs with a 120 resistor in series with a 68nF capacitor at the receiver ends.
Configuration Guide (AADvance Controller) Connect Multiple Slave Devices, Full Duplex You can use a full duplex serial connection to connect multiple Modbus slave devices to the AADvance controller. To make the physical connection, do the following: 1) Select a suitable cable. We recommend 3-pair, overall shielded cable. 2) Remove the serial port connector from the 9100 processor base unit. 3) Make the connections shown in the illustration.
Connect a Slave Device, Half Duplex You can use a half duplex serial connection to connect a single Modbus slave device to the AADvance controller. To make the physical connection, do the following: 1) Select a suitable cable. We recommend 2-pair, overall shielded cable. 2) Remove the serial port connector from the 9100 processor base unit. 3) Make the connections shown in the illustration. Terminate the twisted pair with a 120 resistor in series with a 68nF capacitor at both ends.
Configuration Guide (AADvance Controller) Connect Multiple Slave Devices, Half Duplex You can use a half duplex serial connection to connect multiple Modbus slave devices to the AADvance controller. To make the physical connection, do the following: 1) Select a suitable cable. We recommend 2-pair, overall shielded cable. 2) Remove the serial port connector from the 9100 processor base unit. 3) Make the connections shown in the illustration.
Configure the Serial Ports for Modbus Master When you use a serial port on the AADvance controller for Modbus master (Modbus RTU), you have to configure the serial port. In particular, you have to set the port type to suit the arrangement of the physical connection. To configure the serial port, do the following: 1) Select 9110 Processor on the Project Tree View to open the 9110 Module Editor. 2) Select the Serial Ports tab. The Serial Ports editor dialog box opens.
Configuration Guide (AADvance Controller) Serial Port Parameters Each serial port on the AADvance controller supports the set of control parameters as detailed in the table.
The identity of the serial or Ethernet port you intend to use. The AADvance Workbench provides separate editors for the Modbus master objects and for their slave links. In each editor, you will navigate between tabbed pages to reach the various configuration settings. Click Apply to save your settings before you leave a tabbed page. Note: If you alter the settings and omit to click Apply before you try to navigate away from them, the Workbench prompts you to save your changes. Click Yes.
Configuration Guide (AADvance Controller) Create a Modbus Master Object Note: You have to insert the Modbus Master Bus before you can carry out this task. A Modbus Master object provides the configuration settings you need to add a Modbus master capability to the AADvance controller. You have to create a new Modbus master object for every group of multi-drop Modbus RTU slaves that use the same serial port on the controller, and a new Modbus Master object for every Modbus TCP slave on the network.
Modbus Master Communication and Control Settings Each Modbus master object has a set of communication and control settings as detailed in the table. Note: The AADvance Workbench groups these settings together under the label 'General'.
Configuration Guide (AADvance Controller) Table 25: Modbus Master Communication and Control Settings Description Value(s) Default Protocol RTU or TCP RTU Port Type Serial or Ethernet Serial (†) Port Id S1-1 .. S3-2 Sn-1, where n identifies processor Timeout 0 to 60,000ms 1000ms Control Variable 1 to 65,536, Address or 0 to disable 0 Remarks The address of a control register (a holding register).
Configure a Modbus Master Object for Modbus RTU Note: You have to create a Modbus Master object before you can carry out this task. You have to configure the communications and control settings for a Modbus Master object for Modbus RTU when you want to use the Modbus RTU protocol. Do the following: 1) Select the Equipment tab on the Project tree view and then select the Modbus master object you want to configure. The editor for the Modbus master object opens. 2) Select the General tab.
Configuration Guide (AADvance Controller) Configure a Modbus Master Object for Modbus TCP Note: You have to create a Modbus Master object before you can carry out this task. You have to configure the communications and control settings for a Modbus Master object for Modbus TCP when you want to use the Modbus TCP protocol. Do the following: 1) Select the Equipment tab on the Project tree view and then select the Modbus master object you want to configure. The editor for the Modbus master object opens.
Choosing Names for Modbus Objects The Modbus object Name identifies a Modbus master object or slave link within the AADvance Workbench, and is included in printed reports; but it is not used by the application. We recommend that you use a different name for each object. Alternatively, accept the default name. Modbus Master Timeout The Modbus master Timeout is common to all slaves configured to a particular master.
Configuration Guide (AADvance Controller) The interval applies to all transmissions from the Modbus master, including ping messages and broadcast messages as well as regular messages to slaves, and is common to all slave links configured to a particular master. Note: Do not use the Message Wait Interval as a timing control.
Controlling a Modbus Master Object Every Modbus master object has a pair of registers (holding registers), which allow the application to control the object, and to retrieve status information. The registers are a 'control register' and a 'status register'. Each register is located at a unique address — the Control Variable Address and the Status Variable Address. The use of the registers is optional.
Configuration Guide (AADvance Controller) Modbus Ping Mode, Interval and Address The ping mode is specified individually for each slave; it defines the action the Modbus master should take if the slave fails to respond after the specified number of retries. The AADvance controller supports a Function Code 08 ping mode for Modbus RTU slaves; choose this if the slave supports it because it is a short message.
5) Check that the Ping Interval is suitable for your application. The ping interval is specified individually for each slave; it defines the maximum time between each initiation of a Function Code 08 diagnostic message. Read Holding Register Ping Mode Setting 1) Select the slave link associated with the master object set to RTU protocol. The editor for the slave link opens. 2) Select the General tab. 3) Check that the Ping Mode has been set for Read Holding Register.
Configuration Guide (AADvance Controller) The ping interval is specified individually for each slave; it defines the maximum time between each initiation of a Read Holding Register diagnostic message. Do Not Ping Setting 1) Select the slave link associated with the master object set to RTU protocol. The editor for the slave link opens. 2) Select the General tab. 3) Check that the Ping Mode has been set to Do Not Ping.
2) Select the Slave link associated with the master object. The editor for the slave link opens 3) Select the General tab. 4) Check that the Ping Mode is set to Read Holding Register. 5) Ensure that a Ping Address has been entered. 6) Check that the Ping Interval is suitable for your application. Do Not Ping Ping Mode Setting 1) Select the Equipment tab on the Project tree and then a Modbus master object that has been set up to run the TCP protocol.
Configuration Guide (AADvance Controller) 2) Select a slave link associated with a master object set to the TCP protocol. The editor slave link opens. 3) Check that the Ping Mode has been set to Do Not Ping. Restart a Link When No Ping Mode is Set When a slave module fails the master stops sending messages to it except for the ping message (if one is configured).
Restart a Slave with Ping disabled 1) Configure the salve with a Control Variable Address. This is the address of the Modbus holding register for the slave link control variable. 2) Set the Slave control register variable to a 0 (off) 3) Set the control register variable to 2 (active) The master will restart communication with the slave. Restart All Active Slaves Associated with a Master 1) Select the Master object.
Configuration Guide (AADvance Controller) Configure Statistics for a Modbus Master Object Modbus master statistics are available to the application. To use the statistics, do the following: 1) Select the Equipment tab on the Project tree view and then select the Modbus master object you want to configure. The editor for the Modbus master object opens. 2) Select the Statistics tab. The editor shows three fields. The default values disable the statistics reporting. 3) Set the Reporting Mode.
Description Value(s) Default Remarks Reporting Mode Disabled; Last Rate; Maximum Rate: Average Rate Disabled Sets the application statistic to report Data Variable Address 1 to 65,536, or 0 to disable 0 Data variable is reported in hundredths of a second Reset Variable Address 1 to 65,536, or 0 to disable 0 Write any non-zero value to the reset variable to reset the data variable to zero Create Links to Modbus Slaves A slave link represents the connection between a Modbus master object and a
Configuration Guide (AADvance Controller) Modbus Slave Link Identification and Control Settings Each Modbus slave link object has a set of identification and control settings as detailed in the tables. Note: The AADvance Workbench groups these settings together under the label 'General'.
Table 30: Modbus TCP Link Identification and Control Settings Description Value(s) Default Unit Id 0 to 255 255 IP Address 0.0.0.0 to 255.255.255.255 0.0.0.0 TCP Port 1 to 65,535 502 Retries 0 to 10 3 Control Variable 1 to 65,536, Address or 0 to disable 0 Remarks TCP port 502 is suggested for Modbus TCP devices (Modbus specification version 1.
Configuration Guide (AADvance Controller) Configure a Modbus Slave Link for Modbus RTU Note: You have to create a Modbus slave link object below a Modbus master object configured for Modbus RTU before you can carry out this task. You have to configure each Modbus RTU slave link to suit its individual slave device. Do the following: 1) Select the Equipment tab on the Project tree view and then select the slave link you want to configure. The editor for the slave link opens.
8) Specify the Slave Wait Interval (in milliseconds), or accept the default. 9) Set the Ping Mode and Ping Interval. The interval is specified in milliseconds. If you are using the Read Holding Register mode, specify the Ping Address as well; otherwise accept the default 0. 10) Click Apply. Configure a Modbus Slave Link for Modbus TCP Note: You have to create a single Modbus slave link object below a Modbus master object configured for Modbus TCP before you can carry out this task.
Configuration Guide (AADvance Controller) 8) If you intend to use the control variable, set the Control Variable Address to the Modbus address of the holding register; otherwise accept the default 0 to disable. 9) Set the Status Variable Address. 10) Specify the Slave Wait Interval (in milliseconds), or accept the default. 11) Set the Ping Mode and Ping Interval. The interval is specified in milliseconds.
Modbus Slave Commands The AADvance controller supports a subset of Modbus standard command types. Serial Port Modbus slave serial port commands are available on only the AADvance controller serial ports. Diagnostics Function: Diag Function Code = 8 Address Offset: 0 Data Type: boolean Fixed Length: 8 Varbyte length: 0 Purpose: Provides a series of tests for checking the communications system between a client (master) and a server (slave).
Configuration Guide (AADvance Controller) Read Holding Registers Function: read Function Code = 3 Address Offset: HOLDING_REG_ADDR Data Type: analogue Fixed Length: 8 Varbyte length: 0 Purpose: Reads the contents of a contiguous block of holding registers in a remote device. Read Input Registers Function: read Function Code = 4 Address Offset: INPUT_REG_ADDR Data Type: boolean Fixed Length: 8 Varbyte length: 0 Purpose: Reads from 1 to 125 contiguous input registers in a remote device.
Write Multiple Coils Function: write Function Code = 15 Address Offset: COIL_STATUS_ADDR Data Type: boolean Fixed Length: 9 Varbyte length: 6 Purpose: Forces each coil in a sequence of coils to either ON or OFF in a remote device. Write Multiple Registers Function: write Function Code = 16 Address Offset: HOLDING_REG_ADDR Data Type: analogue Fixed Length: 9 Varbyte length: 6 Purpose: Writes a block of contiguous registers (1 to 123) in a remote device.
Configuration Guide (AADvance Controller) Value Meaning Description 0 Inactive Disables the slave link Slave is neither polled or pinged 1 Standby Forces the slave link to operate in its standby mode Modbus master continues to ping the slave to make sure that communications are possible 2 Active Forces the slave link to operate in its active mode Slave is being polled for data Note: If the application sets the register to any other value, the slave link is disabled.
Add Messages for a Modbus Slave The slave link object uses a list of messages to hold the commands to send to its slave device. To create the list do the following: 1) Select the Equipment tab on the Project tree view and then select the slave link you want to configure. The editor for the slave link opens. 2) Select the Messages tab. The editor shows an empty list area, which will hold your sequence of messages. 3) Right-click anywhere within the list area and select Append New Message.
Configuration Guide (AADvance Controller) 10) The Comment field is a free text field for user notes; it is not used by the software. If desired, enter a comment. 11) Click Apply. Proceed to add and configure additional messages as needed. Select an existing message and then right-click at the left-hand end of the row; select Append New Message to add a message below the current message or Insert New Message to add a message above. Note: You can delete one or more messages together.
Modbus Slave Link Message Parameters Each Modbus slave link message has a set of parameters as detailed in the table.
Configuration Guide (AADvance Controller) Write Holding Registers Input Registers; Holding Registers Holding Registers Controlling a Modbus Message Every Modbus message that originates at a Modbus master (broadcast message or slave link message) has provision for a control (a coil), which allows the application to control whether or not the message should be sent. The coil is located at the address that is specified by the message parameter named 'Control'.
The default values disable the statistics reporting. 3) Set the Reporting Mode. 4) Set the Data Variable Address to the Modbus address of the relevant holding register. 5) Similarly set the Reset Variable Address. 6) Click Apply. Modbus Statistics Parameters Each Modbus message has a series of parameters as detailed in the table.
Configuration Guide (AADvance Controller) Remove all Slave Links You can remove all the slave links associated with a single Modbus master object. Do the following: 1) Select the Equipment tab on the Project tree view and locate the Modbus master object. 2) Right-click on the Modbus master object and select Remove All Slaves. All the slave links associated with the master are removed. Remove a Modbus Master Object You can remove an unwanted Modbus master object.
Chapter 10 SNCP and Variable Bindings AADvance provides SNCP and supports both variable bindings functionality and IXL communication over a safety control network. This chapter describes the process for setting up SNCP networks and variable bindings. In This Chapter SNCP Safety Networks ...................................................................................
Configuration Guide (AADvance Controller) SNCP Networks You can set up a single SNCP network to communicate with the target. When two controllers are set up with their IP Addresses on the same subnet, they also appear on the same physical network. This single logical network can also be used to configure variable bindings over redundant physical networks. Setting Up Single Networks When you create a project it has a default single network configuration. 1) Create a project.
The Workbench will always use the first address that you configure for the SNCP_Workbench network for communications irrespective of any other network instances that have been configured. Note: The IP Addresses shown are for information purposes only. It is recommended that you declare consumer variables in the Dictionary with the "read-only" attribute to avoid conflicts between binding and the execution of POUs. 2) Set up a second controller on the same logical network.
Configuration Guide (AADvance Controller) Config 2 set IP Address 2 = 10.44.200.20 When creating bindings for this network the SNCP_Workbench will be the only network available for selection. The SNCP_Workbench binding driver sends each binding data message over the 10.75.104.xxx and the 10.44.200.xxx networks. Loss of one of these networks will not result in a loss of binding data.
Set Up Multiple SNCP Networks Multiple logical Networks The Workbench also supports multiple redundant networks. This type of network configuration provides a dedicated logical network (which can be physically redundant) to bindings only, to prevent Safety Data from being combined with none Safety Data.
Configuration Guide (AADvance Controller) Configure a Dual Network 1) To configure a redundant dual network select both networks when creating a bound variable. The variable will be sent over both physical networks, so if one network fails the consumer will still receive the variable. Redundant Physical and Logical Networks 1) Set up two networks connected to resources 1 & 2. 2) Configure the IP Addresses as follows: SNCP_Workbench connection: IP Address 1 = 10.75.104.99, IP Address 1 10.75.
This configuration provides two logical networks and three physical networks. 3) Create a bound variable and select SNCP_1 for the binding. A bound variable configured to use SNCP_1 is sent over both physical networks and the loss of one network will not affect the consumer receiving bound variable over this network. 4) Create a bound variable and select both networks for the variable.
Configuration Guide (AADvance Controller) BindRespTimeout This timeout is used in a consumer to timeout a binding data response from a producer. Once a consumer has established a binding connection with a producer, it sends a request for binding data; this timeout value timeouts out the producer response. If no response is received, either another request (retry) is sent, or the consumer disconnects from the producer.
Secondly this timeout value is also used to check the age of binding data message received by the consumer. If a message contains data that is older than this value it is discarded. This can occur if the message is delayed due to problems with the network. The number of requests is determined by MaxAge/BindRespTimeout. To increase the number of retries you have to either increase MaxAge or decrease BindRespTimeout. BindReqTimeout This timeout is used by the producer.
Configuration Guide (AADvance Controller) 00 3) Select the Network tab and enter the values; the default recommended values: Connect TimeOut = 1000 BindResp Timeout = 1200 MaxAge = 2500 BindReqTimeout = 1000 Update Timeout = 60000 Configure Bindings You need to set up data links between resources to create binding variables. You can link resources from the Internal Bindings List Window or set up a link between resources from the Link Architecture view.
Two links are set up between the resources 4) From the menus Select Project Internal Bindings List or and alternative method is double click on a data link between the resources. The Bindings List dialog box opens. 5) Double click on the from field on the binding grid.
Configuration Guide (AADvance Controller) The Binding Dialog box opens. 6) Select the Producing variable from the drop down list and the Consuming variable from the drop down list. 7) Select the SNCP_Workbench (SNCP) from the Network Instances , click OK.
8) Select both Network instances. With this configuration the SNCP binding driver will send the variable over both physical networks and the consumer will continue receiving a variable in the event of a single network failure. You can combine both approaches by setting up dual IP addresses on the second network on the same subnet (See: the procedures in topic "Set Up Multiple SNCP Networks").
Configuration Guide (AADvance Controller) SNCP_KVB_ERR_NO_PRODUCER 0x04 At the beginning of a connection or following "BindRespTimeout" milliseconds during data exchange.
Chapter 11 Peer-to-Peer Network AADvance provides the options to set up a Peer-to-Peer network. The Peer-to-Peer protocol enables you to communicate application data between up to 40 AADvance or Trusted systems per peer network. Data can be transferred between individual systems or from one to several systems at the same time using multicast network communication. Note: The current AADvance controller only supports two Multicast IP Addtresses, one fixed address can be configured for each Ethernet port.
Configuration Guide (AADvance Controller) Peer to Peer Configuration Process Configuring the AADvance controller to communicate with a Trusted Peer to Peer network requires the same parameters as a Trusted configuration. The configuration for AADvance is arranged in a tree in the I/O Configuration view.
The peer identity gives the position of the controller's IP address in the Peer List. Peer-to-Peer Subnet Controller Configuration Configure the subnets as follows: 1) Right click on Network 4 (Peer 1) and select a subnet A SN01 subnet is set up. 2) Select the SN01 subnet. 3) Select the DPXPNC40 tab.
Configuration Guide (AADvance Controller) The subnet DPXPNC40 set up screen is displayed. 4) Enter the following data in the required fields. Network Interface - enter which processor slice (Processor A, B or C) the peer network will be configured on, i.e. which processor module the network is physically connected to. Response Timeout - Enter a value in the range 0 to 10000ms. This value sets the time allowed for the peer to acknowledge a data packet.
Refresh Timeout - Enter a value in the range 0 to 10000ms. This value sets the time that the controller will wait for its turn in the cycle to send its output data. The setting is used by both masters and slaves. The Refresh Timeout should be set to the Slave Transmit Timeout (below) x the number of peers that will be lost on a worst-case network break. The Slave Transmit Timeout should trip before the Refresh Timeout if the network is broken. This will minimise the loss of data transfer.
Configuration Guide (AADvance Controller) Set up the Peer IP Addresses and Status Variable 1) Select the Peer List tab. 2) Enter the IP Address for each peer. You must ensure that when you enter an IP Address the row number you select from the Peer column must correspond to the peer identity number; e.g. for Network 4 (peer 1) enter the IP Address in row 1 of the peer column. To configure a Multicast IP Address, enter the following IP Addresses: Port 1: 224.1.2.3 Port 2: 224.4.5.
Configure Input Boards 1) Select the input source. 2) Add an input board. Configure Analogue Input Boards 1) Select an Analogue Input board. 2) Select the DXPAI16 tab.
Configuration Guide (AADvance Controller) Refresh Timeout - Enter a value in the range 1 to 10000ms. This is the maximum number of milliseconds allowed between successive refreshes of input data before the data is declared invalid. Should the time be exceed and the data declared invalid the input data will either retain the last received value or revert to a fail-safe condition according to the Hold Last Valid Value setting.
Wire the Analogue Input Status Variables 1) Select the required row from the list shown. Select the W button to connect the status parameter to a variable. Input Data is Valid - this status variable is used to report that the input data is refreshed within the Refresh Timeout value. Refreshed by Subnet 1 to 8 - Each of these variables can be used to indicate that the data has been refreshed by subnet 1 - 8 within the Refresh Timeout value.
Configuration Guide (AADvance Controller) check box to set the variable type to REAL leave unchecked to select DINT. 4) Select the W button to connect to a variable. 5) If you need to disconnect a variable select the U button. The 128 input peer board supports 128 analogue inputs instead of 16 but is otherwise identical.
Wire Digital Input Board Status Variables 1) Select the required row from the list shown. 2) Select the W button to connect the status parameter to the required variables. Input Data is Valid - this status variable is used to report that the input data is refreshed within the Refresh Timeout value. Refreshed by Subnet 1 to 8 - Each of these variables can be used to indicate that the data has been refreshed by subnet 1 - 8 within the Refresh Timeout value.
Configuration Guide (AADvance Controller) Wire Digital Input Channel Data Variables Digital input values are received from the corresponding output of the selected output board in the sending system; the values are Boolean values. Both the specific input channel and the corresponding output channel must be connected to the same variable type. 1) Select the Data Variables tab. 2) Select a Channel row. 3) Select the W button to connect to a variable.
Configure Output Boards To configure an output for a peer network do the following: 1) Right click on Network 4 (Peer 1) 2) Select a peer number which is the target for the output data. 3) Add output boards as required.
Configuration Guide (AADvance Controller) Configure Analogue Output Boards 1) Select the board. 2) Select the DXPAO16 tab. 3) Enter the following data. Refresh Interval - Enter a value in the range 0 - 10000ms. This is the maximum time allowed between transmissions of the output data. Note: Data will be sent immediately following any change of output state. If a value of zero is specified in this field then data will be refreshed every application scan regardless of output state change.
Wire the Analogue Output Channel Variables Analogue output channels send analogue data to the corresponding analogue input channels on the peer network. 1) Select the Data Variables tab. 2) Select a Channel row. 3) Select the R check box to set the variable data type, not checked = DINT checked = REAL. 4) Select the W button to connect to a variable. 5) If you need to disconnect a variable select U button.
Configuration Guide (AADvance Controller) Configure Digital Output Board 1) Select the board 2) Select the DXPDO16 tab. 3) Enter the following data. Refresh Interval - Enter a value in the range 0 - 10000ms. This is the maximum time allowed between transmissions of the output data. Note: Data will be sent immediately following any change of output state. If a value of zero is specified in this field then data will be refreshed every application scan regardless of output state change.
2) Select a Channel row. 3) Select a W button to connect to a variable. The outputs are Boolean values. 4) To disconnect a variable select the U button.
Configuration Guide (AADvance Controller) Peer to Peer Configuration Example 1 This example uses 4 controllers connected to two subnets forming one Peer to peer network. Controllers 1, 2 and 3 are dual processor AADvance controllers and Controller 4 is Trusted. Controller 4 is designated the "master" of Network 1 Subnet 1 and Controller 1 the "master" of Network 1 Subnet 2.
Peer-to-Peer Controller Setting Summary You should follow the process described in this chapter.
Configuration Guide (AADvance Controller) Peer ID 1 Identity of this controller Response Timeout 0 Default Refresh Timeout 2000 Default Slave Transmit timeout 500 Default Enable Controller TRUE Enable Peer on this subnet Master/Slave TRUE This is a Master connection Peer 1 10.10.2.1 Controller 1, network 1, subnet 2 Peer 2 10.10.2.2 Controller 2, network 1, subnet 2 Peer 3 10.10.2.3 Controller 3, network 1, subnet 2 Peer 4 10.10.2.
Enable Controller TRUE TRUE TRUE Master Slave FALSE FALSE FALSE Peer 1 10.10.1.1 10.10.1.1 10.10.1.1 Peer 2 10.10.1.2 10.10.1.2 10.10.1.2 Peer 3 10.10.1.3 10.10.1.3 10.10.1.3 Peer 4 10.10.1.4 10.10.1.4 10.10.1.4 Peer List Peer 5 Controller 4 Controller 4 dxpnc40 - Control Rack Chassis 1 Slot 7 Network Id 1 Subnet_ID 1 Peer ID 4 Response_TMO 0 Refresh_TMO 2000 TX_DATA_TMO 500 Variable 1 TRUE Variable 2 TRUE Peers_1 rack Peer_IP_01 10.10.1.1 Peer_IP_02 10.10.1.
Configuration Guide (AADvance Controller) Dual Peer-to-Peer Net control Network Set Up - Network 1, Subnet 2 Table 40: Controllers 1,2 & 3 Controller 1 Controller 2 Controller 3 Network interface B B B Network Identity 1 1 1 Subnet Identity 2 2 2 Peer ID 1 1 1 Response Timeout 0 0 0 Refresh Timeout 2000 2000 2000 Slave Transmit Timeout 500 500 500 Enable Controller TRUE TRUE TRUE Master Slave TRUE FALSE FALSE Peer 1 10.10.2.1 10.10.2.1 10.10.2.1 Peer 2 10.10.2.
Table 41: Controller 4 Controller 4 dxpnc40 - Control Rack Chassis 1 Slot 8 Network Id 1 Subnet_ID 2 Peer ID 4 Response_TMO 0 Refresh_TMO 2000 TX_DATA_TMO 500 Variable 1 TRUE Variable 2 FALSE Peers_1 rack Peer_IP_01 10.10.2.1 Peer_IP_02 10.10.2.2 Peer_IP_03 10.10.2.3 Peer_IP_04 10.10.2.
Configuration Guide (AADvance Controller) Peer to Peer Data Summary Output Data Table 42: Controller 1 & 2 Controller 1 Controller 2 Board Type dxpao dxpao dxpdo Network identity 1 1 1 Target peer identity 2 3 4 Source data identity 1 2 1 Refresh timeout 2000 2000 2000 Minimum change before update 20 20 Variable 1 -16 Analogue Data Output Analogue Data Output Digital Data Output Input Data Table 43: Controller 2, 3 & 4 Controller 2 Controller 3 dxpai dxpai Network identit
Table 44: Controller 4 Controller 4 DATA RACK dxpdi Network Identity 1 Source Peer Identity 2 Source data identity 1 Refresh timeout 5000 Value in failed state FALSE STATUS RACK Variable 1 Boolean Data Input Input Data is Valid Input Data Valid Refreshed by Subnet 1...9 Refreshed on Subnet 1...
Glossary of Terms Glossary of Terms A asynchronous accuracy A data communications term describing a serial transmission protocol. A start signal is sent before each byte or character and a stop signal is sent after each byte or character. An example is ASCII over RS232-C. See also 'RS-232-C, RS-422, RS-485'. The degree of conformity of a measure to a standard or a true value. See also 'resolution'. achievable safe state A safe state that is achievable. Note: Sometimes, a safe state cannot be achieved.
Configuration Guide (AADvance Controller) black channel bus A communication path whose layer (i.e. cabling, connections, media converters, routers/switches and associated firmware/software, etc.) has no requirement to maintain the integrity of safety critical data transferred over it.
Glossary of Terms Compiler Verification Tool (CVT) cross reference The Compiler Verification Tool (CVT) is an automatic software utility that validates the output of the application compilation process. This process, in conjunction with the validated execution code produced by the AADvance Workbench, ensures a high degree of confidence that there are no errors introduced by the Workbench or the compiler during the compilation of the application.
Configuration Guide (AADvance Controller) expansion cable assembly field device A flexible interconnection carrying bus signals and power supplies between AADvance base units, available in a variety of lengths. Used in conjunction with a cable socket assembly (at the left hand side of a base unit) and a cable plug assembly (at the right hand side of a base unit). Item of equipment connected to the field side of the I/O terminals.
Glossary of Terms HART IEC 61131 HART (Highway Addressable Remote Transducer) is an open protocol for process control instrumentation. It combines digital signals with analogue signals to provide field device control and status information. The HART protocol also provides diagnostic data. (For more details of HART devices refer to the HART Application Guide, created by the HART Communication Foundation, and their detailed HART specifications. You can download documents from www.hartcomm.org.
Configuration Guide (AADvance Controller) L module locking screw ladder diagram The AADvance latch mechanism seen on the front panel of each module and operated by a broad, flat-blade screwdriver. Uses a cam action to lock to the processor base unit or I/O base unit. An IEC 61131 language composed of contact symbols representing logical equations and simple actions. The main function is to control outputs based on input conditions. See 'limited variability language'. LAN Local area network.
Glossary of Terms pinging project In Modbus communications, sending the diagnostic Query Data command over a link and by receiving a reply ensuring that the link is healthy and the controller is able to communicate with the master. No process data is transferred or modified. In the case of slave devices that will not support pinging then the Standby command will default to Inactive state, but no error will be returned. A collection of configurations and the definition of the linking between them.
Configuration Guide (AADvance Controller) RTU SIF Remote terminal unit. The Modbus protocol supported by the AADvance controller for Modbus communications over serial links, with the ability to multi-drop to multiple slave devices. Safety Instrumented Function. A form of process control that performs specified functions to achieve or maintain a safe state of a process when unacceptable or dangerous process conditions are detected. S SIL safe state Safety Integrity Level.
Glossary of Terms T V TA validation See 'termination assembly'. In quality assurance, confirmation that the product does what the user requires. target An attribute of a 'configuration' which describes characteristics of the AADvance controller on which the configuration will run. Includes characteristics such as the memory model and the sizes of variable types for the controller. TCP Transmission control protocol. One of the core protocols of the Internet Protocol suite.
Chapter 13 Additional Resources For more information about the AADvance system refer to the associated Rockwell Automation technical manuals shown in this document map. Publication Purpose and Scope Safety Manual This technical manual defines how to safely apply AADvance controllers for a Safety Instrumented Function. It sets out standards (which are mandatory) and makes recommendations to ensure that installations meet their required safety integrity level.
Configuration Guide (AADvance Controller) PFH avg and PFDavg Data This document contains the PFHavg and PFDavg Data for the AADvance Controller. It includes examples on how to calculate the final figures for different controller configurations. The data supports the recommendations in the AADvance Safety Manual Doc No: 553630. Regional Offices Rockwell Automation Oil and Gas Resources are available in Regional Offices worldwide.
