Programmable Serial Interface Card Driver for …...Powerful Solutions for Digital Plants MYNAH Technologies 390-South Woods Mill Road, Suite 100 Chesterfield, Missouri 63017 Telephone
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
All rights reserved. Printed in the U.S.A. While this information is presented in good faith and believed to be accurate Mynah Technologies does not
guarantee satisfactory results from reliance upon such information. Nothing contained herein is to be construed as a warranty or guarantee, express or implied, regarding the performance, merchantability, fitness or any other matter with respect to the products, nor as a recommendation to use any product or process in conflict with any patent. Mynah Technologies reserves the right, without notice, to alter or improve the designs or specifications of the products described herein.
1.1 Scope This document is the User Manual for the Acrison MD-II Series 400 Controller serial
communication driver firmware for the Emerson Process Management (EPM) DeltaV Control System; it provides information required to install, configure, and maintain the driver firmware on the DeltaV Programmable Serial Interface Card (PSIC). The reader should be familiar with EPM’s DeltaV PSIC and connected Acrison Controllers.
The section Document Format briefly describes the contents of each section of this manual.
System Specifications outlines hardware and software requirements for the Driver firmware.
1.2 Document Format This document is organized as follows:
Introduction Describes the scope and purpose of this document.
Theory of Operation Provides a general functional overview of the Acrison Driver.
Flashing Firmware Describes flashing procedures for the Acrison Driver firmware on to the DeltaV PSIC.
Configuration Information Describes procedures and guidelines for configuring the DeltaV PSIC.
Operational Check Provides tips and assistance to ensure PSIC is properly setup and configured.
DeltaV–Field Device Electrical Interface
Describes the electrical interface between DeltaV PSIC and the Acrison Controllers.
Technical Support Describes who to call if you need assistance.
1.3 System Specifications The following table lists the minimum system requirements for the Acrison Controller Driver: Table 1: System Specifications
Firmware Driver Firmware v1.55 or later
Protocol Compatibility Communications with the Acrison Controller are
based on the following document:
PRoVOX CL6921 External Interface Card, User
Manual, November 21, 1991, Project 9145004
Specific Acrison Controller protocol manual was not
available.
Software Requirements DeltaV System Software (Release 6.2 or later) installed on a hardware-appropriate Windows workstation configured as a ProfessionalPlus for DeltaV
Serial Interface Port License (VE4102) if required.
Minimum DeltaV Hardware Requirements
DeltaV Series 2 Serial Module, M- or S-Series
DeltaV MD, MD Plus, MX or SX Controller, Power Supply, 2-wide controller carrier and 8 wide I/O carrier
DeltaV comprises an I/O sub-system, in which the PSIC is one type of card. The purpose
of the PSIC is to serially integrate third-party devices, allowing data to be read into and
written out from DeltaV.
Each PSIC has 2 communication ports that can be configured as Master or Slave, using
RS-232, RS-485 (Half Duplex), or RS-422 (Full Duplex). Various communications
parameters, such as baud rate, are configurable.
Each communication port has sixteen (16) datasets, configurable to contain data of
different types. One or more datasets can be configured to belong to a device, with a
maximum of 16 devices each with one dataset.
In this driver application, two (2) datasets will be assigned for each Acrison Feeder. This
allows a maximum of 8 Feeders per port. The driver works in Master mode only and has
the following architecture.
The PSIC driver functionality comprises a continuous scan of all configured Feeder devices. Specific preconfigured Feeder parameters are read, and the data is reported to DeltaV as Floating Point and Boolean values. In addition, DeltaV sends SP and Start/Stop commands to Feeders. The driver sends these commands out as a priority.
Feed Rate Setpoint Floating Point R/W Batch Size Setpoint Floating Point R/W Feed Rate Floating Point R Batch Fed Floating Point R Total Fed Floating Point R Motor Current Floating Point R Motor Speed Floating Point R Scale Weight (%) Floating Point R Scale Weight (lbs) Floating Point R Hopper Level Floating Point R Resolver Floating Point R Status Binary R Start Feeder Binary W Stop Feeder Binary W In this driver, a communications error is reported via a specific register in the Feeder dataset. Communications errors are generated based on the following conditions: 1. No response from a Feeder. The driver will retry the command using configured retry count and timeout time before declaring a no response error. 2. Error response from a Feeder. Specifically when a write command is sent to the Feeder, an ACK is expected if the command is accepted. The Feeder sends a NACK if it does not accept the command. 3. Invalid response from a Feeder. This error is generated if the Feeder response contains an invalid BCC checksum, or if the returned Index Code does not match the read request Index Code. On error detection, the communication error register is set to a 1. Once the error clears and communications are restored, the error register is reset to 0.
3. The above dialog will appear, listing all the available Controllers in your network. From
this dialog, select the appropriate Controller and then Click Next.
4. The following dialog will appear, listing all the I/O modules in your selected Controller.
The shown list of I/O modules is an example only. Your list will be different. Note: The first time a standard Serial card is upgraded to the Acrison Driver, the
dialog will be as shown below. When upgrading an existing Programmable Serial Card, skip Steps 5 and 6, and go to Step 7.
7. If you are upgrading an existing Programmable Serial Card, the dialog will be as shown below. From this dialog, select the Programmable Serial Card I/O Module in the list.
For example, we will select I/O Module 1. This will give you a dialog, from which you will
select the file path to where the driver software is located. This path will be: \DeltaV\ctl\ProgSerial\IOD-1156 Acrison Once you are in the specified directory, select file Acrison.SDF
4 CONFIGURATION INFORMATION The device and dataset architecture will be as follows:
4.1 Port Configuration
First, enable the port. Then click on the Advanced Tab and select Master, Retry count=1, Message Timeout=1000 and Transmit Delay as 0. Next, click on the Communications Tab and specify the Port type as RS-232. Select Baud Rate = 19200, Parity=Even, Data bits=7 and Stop Bits=1.
4.2 Device Configuration
Configure one device for each Feeder. The device address corresponds to the address configured in the Feeder.
1 Feed Rate Setpoint (See Section 4.4) R/W 2 Resolver R 3 Batch Size Setpoint (See Section 4.4) R/W 4 Feed Rate R 5 Total Fed R 6 Motor Speed R 7 Motor Current R 8 Batch Fed R 9 Hopper Level R 10 Scale Weight (%) R 11 Scale Weight (lbs) R 12 Feeder Status R Table 3a - Dataset 2 Boolean Data
Register Data Description Direction
1 Batch Complete R 2 External Volume R 3 Internal Volume R 4 Batch Delay R 5 Batch Running R 6 External Grav. R 7 Batch Mode R 8 Internal Grav. R 9 Refill On R 10 Low Level R 11 Manual Refill R 12 Auto Refill R 13 High Level R 14 Feeder Off R 15 Feeder On R 16 Not Dribble R
17 EM0 R 18 EM1 R 19 EM2 R 20 EM3 R 21 EM4 R 22 EM5 R 23 EM6 R 24 EM7 R 25 Overload R 26 Fault R 27 Deviation R 28 No Tach R 29 Empty R 30 Acri-lok R 31 No Scale R 32 Overfill R 33-48 Reserved 49 Start Feeder (See Section 4.4) W 50 Stop Feeder(See Section 4.4) W 51 Communications error R
Device dataset 1, Registers 1 and 3 are bi-directional. To send Setpoint values to a Feeder, use an ACT block to write new value into the register. Do not wire the value into the register external reference. Wiring the external reference causes the DeltaV Controller to continuously send output requests to the PSIC even though the value has not changed. This interferes with the input scan.
Feeder Start Device dataset 2, Register 49 is used to send a Start command to the Feeder. This
register behaves as a momentary pulse. Normally, the value contained in this register is 0 or FALSE. Writing a 1 or TRUE to the register triggers the driver to send a Feeder Start command. The driver then clears the value back to 0 or FALSE. This ensures a change of state can be generated so that a new command pulse may be sent.
To Start a Feeder, write a 1 to this register (using an ACT) block. Feeder Stop Device dataset 2, Register 50 is used to send a Stop command to the Feeder. This
register behaves as a momentary pulse. Normally, the value contained in this register is 0 or FALSE. Writing a 1 or TRUE to the register triggers the driver to send a Feeder Stop command. The driver then clears the value back to 0 or FALSE. This ensures a change of state can be generated so that a new command pulse may be sent.
To Stop a Feeder, write a 1 to this register (using an ACT) block.
Note - The driver will accept and send Feeder Start/Stop commands at all times, regardless of the actual state of the Feeder.
5.1 Scope The following sections provide some assistance to ensure the interface is working
properly.
5.2 Verify Hardware and Software Version Number
The user can verify that the driver has been installed using the DeltaV Diagnostics tool. The Diagnostics tool will show the Hardware Revision No. (HwRev) and the Software Revision No. (SwRev).
To begin the DeltaV Diagnostic tool select Start-> DeltaV-> Operator-> Diagnostics. In
the Diagnostics tool expand the Controller, I/O and then double click on the Programmable Serial Interface Card that has the driver installed.
The following information will be displayed: : : : HwRev Hardware Revision 1.1 (or later) SwRev Software Revision P1.55 (or later)
5.3 Verify Configuration
• Verify port configuration: The serial port must be enabled. User needs to make sure communication settings such as baud rate, parity, and number of data bits match the field device settings.
• Verify dataset configuration: The datasets configured must be as shown above.
5.4 Verify I/O Communication With Control Studio User can create I/O modules in the control studio to verify correct values are read from the PSIC. For AI and DI data, the values should be changed in the field device and verified that the new data are correctly reported in DeltaV. Similarly, verify that the AO and DO data is being written correctly from DeltaV to the field device.
5.5 Using Diagnostics
• Verify PSIC communication: Select the PSIC on Diagnostics and press the right mouse button. Select Display Real -Time Statistics from the drop down menu. If the Programmable Serial Interface Card is functioning then the user will see the Valid Responses counter and the Async and/or Sync Transactions counters incrementing. There will not be any error counting up.
• Verify port statistics: Select the Port on the Programmable Serial Interface Card and press the right mouse button. Then select Display Port Statistics form the drop down menu. Verify that the port communications statistics are being displayed properly and are counting as expected for the protocol’s functionality.
• Verify dataset values: Select a dataset and press the right mouse button. Select View Dataset Registers from the Drop down window. Verify that the dataset values are displayed as expected.
• Verify that there are no errors at the dataset level.
5.6 LED Indication
The Yellow LED for the port should be on solid when all communications on that port are valid. The Yellow LED should be blinking if there is some valid communications and some communications with errors on that port. The Yellow LED should be OFF if there are no valid communications on that port.
The electrical interface between DeltaV and Acrison Controllers conforms to the RS-232 standard. The Acrison MD-II Controller provides a set of screw terminals for connection of the RS-232 communications cable. These screw terminals provide the following RS-232 communications functions:
Terminal Number Description
30 (TXD) Transmit Data 35 (RXD) Receive Data 19 (GND) Ground Consequently, the required cable pin-out between DeltaV PSIC and the first Acrison MD-II Controller interface is as follows. The maximum length of this cable must not exceed 50ft.
The remaining Acrison Controllers are daisy chained to the first Controller using RS-485 interface on the Data Link Option Module.
For technical support or to report a defect, please give MYNAH Technologies a call at (636) 728-2000. If a defect is discovered, please document it in as much detail as possible and then fax your report to us at (636) 728-2001. You can also send us your questions via e-mail. Our address is: [email protected] Thank you for using DeltaV.
1.55 NFW NFW Jun, 2016 Initial Release 1.56 NFW NFW Sep, 2016 Modified Feeder Start/Stop commands to be triggered from
different registers. R49 is for Feeder Start and R50 is for Feeder Stop. Writing a 1 or TRUE to these registers invokes the command to be sent to the Feeder. The registers then revert back to 0 or FALSE
1.56 NFW NFW Oct, 2016 Modified RS232 cable specification showing that a null modem cable is required, i.e., cable with RxD to TxD, and TxD to RxD conductors.