Barcode (ASCII Read) Driver for DeltaV Programmable Serial Interface Card

Transcription

1 Barcode (ASCII Read) Driver for DeltaV Programmable Serial Interface Card USER MANUAL Rev. P1.55 December 27, 2016 DeltaV is a trademark of Emerson Process Management Emerson Process Management 1998, 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.

2 1 INTRODUCTION 1.1 Scope This document is the User Manual for a generic ASCII Read for Bar Code serial communication driver firmware for the Emerson DeltaV Control System; it provides information required to install, configure, and maintain the driver firmware on the DeltaV Series 2 Programmable Serial Interface Card (PSIC). The reader should be familiar with Emerson s DeltaV controller system and the bar code equipment. The section Document Format briefly describes the contents of each section of this manual. System Specifications outlines hardware and software requirements for the Driver (P1.55) firmware. Related Documents lists other documents used to prepare this manual. 1.2 Document Format This document is organized as follows: Introduction Theory of Operation Flashing Firmware Configuration Information Operational Check Electrical Interface Technical Support Describes the scope and purpose of this document. Provides a general functional overview of the Driver. Describes downloading procedures for the driver firmware on to the DeltaV PSIC. Describes procedures and guidelines for configuring the DeltaV PSIC. Provides tips and assistance to ensure PSIC is properly setup and configured. Describes the electrical interface between DeltaV and the bar code devices. Also describes the pin assignments for RS-232 communications. Describes whom to call if you need assistance.

3 1.3 System Specifications The following table lists the minimum hardware requirements for the Driver: Table 1: System Specifications Firmware Protocol Compatibility Software Requirements Driver Firmware (P1.55) Bar code data as generic ASCII text, with optional user defined prefix and suffix characters for bar code device identification. DeltaV System Software (Release 10.3 or later) installed on a hardware-appropriate Windows workstation configured as a ProPlus for DeltaV Serial Interface Port License (VE4102) if required Minimum Hardware Requirements DeltaV Series 2 Serial Module, M- or S-Series DeltaV MD, MD Plus, MX or SX Controller, Power Supply and 2 wide controller carrier and 8 wide I/O card carrier Bar Code Readers or other ASCII devices

4 2 THEORY OF OPERATION As part of the serial interface port license, a standard Modbus protocol is installed on the DeltaV PSIC prior to customization. The PSIC needs to be flash upgraded from the Modbus protocol to the ASCII Reader firmware before operation. The RS-232 communication settings must be configured properly to ensure accurate communication between the PSIC and external devices. RS-422/485 may be used directly, or through a RS-422/485 to RS-232 converter. This driver functions as a slave only. In slave mode, the PSIC waits for data to be received on its ports. A port may be connected to a single bar code reader or field device, or it may be connected to multi-dropped devices, or multiple devices through a data-concentrator. If multiple devices are connected, the incoming data is expected to contain an identifying prefix which uniquely identifies the sending device, as well as a data packet termination suffix. See Section for configuration details. The received data are reported to DeltaV via dataset registers. A fixed architecture is used in order to maximize the number of bar code devices, which can be connected to a PSIC port, while maintaining ease of data access and scan throughput. A maximum of sixteen (16) bar code devices under each PSIC port are allowed. Each device comprises a single dataset, where the received bar code information is reported. 3 Flashing the firmware

5 The driver software distribution contains 8 files. These files must be copied to the DeltaV directory (you must create the directory first) on your ProPlus Workstation. The path is: \DeltaV\ctl\ProgSerial\IOD-1141 BarCode The following shows a completed copy operation: After copy completion, you are ready to program (or upgrade) the Programmable Serial Card with the supplied custom driver software. The steps are as follows:

6 1. Click on the Start button and select DeltaV-> Installation-> Controller Upgrade Utility as shown above, and the following dialog will appear:

7 2. Select I/O Modules in the list, then click Next. 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 as shown below.

8 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 BarCode 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.

9 5. Click the Browse button and select the DeltaV path as shown below, and then click Ok. Note that the disk drive could be C or D. 6. The Select the I/O module again as shown below and then click Next. Go to Step 9.

10 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. From this dialog, select I/O Module 1. This will give you the following dialog, from which you will select the file path to where the driver software is located. This will be: \DeltaV\ctl\ProgSerial\IOD-1141 Barcode Once you are in the specified directory, select file BarCode.SDF

11 8. After selecting the.sdf file, Click on Open. This dialog will close and you will be back to the following: 9. In this dialog, Click Next again. You will get the following dialog, confirming the Controller and I/O Module to program. 10. Click Next and the I/O Module upgrade process will begin. After completion, you will receive the following dialog, indicating success.

12 11. This completes the I/O Module upgrade process.

13 4 CONFIGURATION INFORMATION Powerful Solutions for Digital Plants This section describes the steps necessary to configure the DeltaV PSIC and the external device to obtain proper communication. 4.1 Device and Dataset Configuration The following paragraphs discuss some attributes in the device and dataset configuration: Device Address: Configure a maximum of sixteen (16) devices under each PSIC port. The driver does not use the device addresses, consequently these may be user specific Output Mode: Configure all datasets to be of type Input DeltaV Data Type: Each device will use one (1) dataset. The datasets must be configured as 1. 8-bit INT with Status; 2. 8-bit UINT with Status; or 3. String with Status DeviceDataType The driver does not use this value. Leave this value at its default setting of Data Start Address and Number of Values Configure all datasets with Starting Address as 0, and Number of values as Special Data 1-5 If a single bar code reader or device is connected to a PSIC port, then configure the Special Data registers as follows: 1 0 Default value. No prefix required 2 0 Default value. No suffix required 3 1 Report all received data verbatim 4 0 Reserved 5 0 Reserved

14 If multiple bar code readers or devices are connected to a PSIC port, incoming data must contain a prefix character to uniquely identify the sending device, and suffix character to serve as a data packet terminator. These characters help mark boundaries between data packets from different field devices, particularly if the incoming data is routed through a data concentrator. For each dataset, configure all Special data values as follows: 1 Non zero value Prefix character, e.g., for a prefix of A, enter 65. Configure 0 (default) if no prefix is expected 2 Non zero value Suffix character, e.g., for a suffix of?, enter 63. Configure 0 (default) if no suffix is expected 3 0 or 1 Flags value. Enter 0 to strip prefix and suffix characters from data before reporting to DeltaV. Enter 1 to report received data verbatim, i.e., prefix and suffix are not present or will not be stripped 4 0 Reserved 5 0 Reserved

15 5 Operational Check 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 external 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 external device and the PSIC. For input data, the values should be changed in the external device and verified that the new data are correctly reported. 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.

16 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. 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.

17 6 Electrical Interface The electrical interface between DeltaV and external devices conforms to the RS-232, or RS-422/RS-485 protocol. The RS-232 cable connecting DeltaV PSIC and external devices should not exceed 50 feet as specified by the EIA standard for RS-232 protocol. Section 6.1 shows the pin assignments for the PSIC serial terminal block for RS-232 protocol. If using RS-422/RS-485, the distance is 4000 feet. 6.1 RS-232 Pin Assignments for DeltaV PSIC Terminal Number Signal Description 1 Port 1 - Isolated Ground (GND) 2 Unused 3 Port 1 - Transmit Data (TXD) 4 Unused 5 Port 1 - Receive Data (RXD) 6 Unused 7 Port 1 - Data Terminal Ready (DTR) 8 Port 1 - Dataset Ready (DSR) 9 Port 2 - Isolated Ground (GND) 10 Unused 11 Port 2 - Transmit Data (TXD) 12 Unused 13 Port 2 - Receive Data (RXD) 14 Unused 15 Port 2 - Data Terminal Ready (DTR) 16 Port 2 - Dataset Ready (DSR) 6.2 Wiring Connections for RS-232 Communications Five terminals need to be connected between the PSIC and the external device port. Pins 3 (TXD) and 5 (RXD) need to be crossed so that the external device TXD is connected to PSIC RXD, and the external device RXD is connected to PSIC TXD. Pins 7 (DTR) and 8 (DSR) also need to be crossed in the same manner between the PSIC and the external device. Alternatively, you can jumper DTR and DSR on the PSIC terminal block. In all cases, the GND signal goes through, i.e., connect terminal block screw 1 to GND on the external device. If the external device port is 9-pin D-shell, then GND is pin 5. If the port is 25-pin D-Shell, then the GND is pin 7.

18 7 Technical Support For technical support or to report a defect, please give MYNAH Technologies a call at (636) If a defect is discovered, please document it in as much detail as possible and then fax your report to us at (636) You can also send us your questions via . Our address is: support@mynah.com Thank you for using DeltaV.

19 8 Revision History Revision Checked Approved Date Description Number By By 1.10 NFW NFW Oct, 2003 Initial Release 1.55 NFW NFW Dec,2016 Updated to use Emerson toolkit v3.02. Modified to accept incoming data packets without prefixes.