Interrupt Messages Switch File

Data I/O Type Filter File

This file contains a list of the Yokogawa data types that are permitted to be updated in the DCS data by the interface’s output tags. When the interface initialises itself it reads this file to determine which Yokogawa data types it should update in the DCS. The file is distributed with ten data types:

Each of these data types are on a different line in the file. There are ten data types that can be retrieved from the gateway but not all of these need be included in the file. If a particular data type does not appear in this file, Yokogawa points of that type will not be updated in the DCS.

Note: Precision and overflow may be lost because the length of the output data is dependant on the actual tags.

Digital State String Translation File

This file contains translation strings for Yokogawa digital states. When the interface initialises itself it searches for this file. The file has the following format:

As the interface reads the file it creates a table to use for lookup while the interface is running. The file need not contain all digital states that will be used—only those that are deemed necessary by the PI system manager. The <DCS_State_String> represents the digital state string as it is received from the DCS. The <Custom_State_String> represents a digital state string in the PI2 digital state table or a PI3 digital state set. For example,

When the interface receives a digital state string from the DCS it translates it using this table to a custom state string and send it to PI. See the description of the “/dt” argument on page 17 for more information about translating PI digital states to PI digital codes.

The purpose of this file is to be able to give Yokogawa digital state strings a more meaningful name in PI. It is also useful for translation to different languages where the DCS does not use the same language as the PI system users.

If the file cannot be found, the interface continues without it, logging a message similar to:

Communication Testing Programs

Filenames: Apisnap.exe, Ci-Test.exe

Before attempting to run the interface, a connection test should be done individually to both PI and the gateway. If a test program is run that makes reference to only one system, any problems that occur with the communication will be specific to the system being connected to; thus problems can be found and corrected more efficiently. Once connection has been established and confirmed using the test programs described below, the connection specifications for both PI and the gateway that have been set up will function equally well for the interface.

Testing the Connection to PI

PI is supplied with a test program, Snap.exe (PI2) or ApiSnap.exe (PI3), which makes a connection only to PI, eliminating any potential problems connecting to the gateway. For more information about this program see the PI2 System manual, Part I, section 3.6.1 or the PI Data Archive for Windows NT and Unix manual.

Testing the Connection to the Yokogawa Gateway

The interface is supplied with a program, Ygi_Test.exe that connects only to the gateway. This test program connects to the gateway in exactly the same way as the interface does. It eliminates PI from the equation during any connection problems that may occur because it makes no reference to the PI system.

If using TCP/IP with an ECGW3 gateway that has the ability to communicate in binary mode, use the Ygi_TestB.exe program if it is intended that the interface use this binary mode (see “/b” argument of the interface startup file on page 16). Commands are input into the binary test program in the same way as with the text-based test program. The program will do the necessary conversion to binary.

The programs are run from a VMS terminal using the RUN command or from a Windows NT MS-DOS command prompt.

When started, the program will prompt for a protocol. Depending on the protocol, the interface will ask for connection details. For TCP/IP it will ask for a host name and a port number. These should be entered the same as they are defined using the “/gw” and “/port” arguments (see pages 18 and 20) in the interface startup file. Following is an example of this:

*** Yokogawa Gateway Interface Test Program ***

Protocol (0:TCP/IP, 1:TTY) ->

0
Host Name ->
localhost
Port No (Space:Default 31000) ->
31000
Input Command
(Option) #A: Show ASCII Code
#N: Return Normal Mode
NULL: Exit
->
G01 TG 2 FIC-001,PV FIC-002,PV
A01 TG 2 120.1 10.5
...

Note: IF TCP/IP is used, the PING command may be used to verify a physical connection to the gateway.

Directory: interfaces
interfaces -> Pi interface for Siemens Spectrum Power tg (Linux)
interfaces -> Citect Interface
interfaces -> Interface to the pi system
interfaces -> How to Contact Us
interfaces -> How to Contact Us
interfaces -> Emerson Deltav batch Interface

Download 344.12 Kb.

Share with your friends: