Delta Mynah PLC-5 User Manual Page 19

  • Download
  • Add to my manuals
  • Print
  • Page
    / 26
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 18
Powerful Solutions for Digital Plants
MYNAH Technologies  504 Trade Center Blvd.  Chesterfield, MO 63005  Telephone 636 681-1555  Fax 636 681-1660
www.mynah.com
18
· Stop Bits 1 or 2
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 AB 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 Allen-Bradley driver installed.
The following information will be displayed:
: : :
HwRev Hardware Revision 1.1 (or later)
SwRev Software Revision P1.0 (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
Allen-Bradley device settings.
· Verify device configuration: User must check for the proper device address is
entered. The Allen-Bradley device address is an octal-based number. This number
must be converted to a decimal number.
· Verify Dataset configuration: The RMW operations are output-only commands. Do
not configure input Dataset with RMW. The DeltaV data type also needs to match
with Allen-Bradley data types. For example, user should not match a DeltaV 16-bit
unsigned integer with a PLC-5 floating point file data. Unpredictable results will occur
if there is a mismatch between the two data types. The starting address should
always be an even number to ensure proper word boundary is assigned. For Special
Data 2, number 0 through 8 must match the default Allen-Bradley file types.
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 and
written between the foreign device into the PSIC. For input data, the values should be
changed in the foreign device and verified that the new data are correctly reported.
For output data, change the values in the controller and then verify that the values are
transferred to the foreign device.
Page view 18
1 2 ... 14 15 16 17 18 19 20 21 22 23 24 25 26

Comments to this Manuals

No comments