MISTICSA DDE Server. for Microsoft Windows and InTouch Applications. User Manual Ver 3.x Rev 2.2 DR DR

Transcription

1 MISTICSA DDE Server for Microsoft Windows and InTouch Applications User Manual Ver 3.x Rev 2.2 DR DR KLINKMANN AUTOMATION P.O. Box 38 FIN Helsinki Finland tel. int fax int

2 Klinkmann Automation MISTICSA DDE Server i Table Of Contents What is DDE?... 2 Accessing a Remote DDE Item from MISTICSA... 2 Installing the MISTICSA DDE Server... 3 Connection Cables... 3 Configuring the MISTICSA Server... 6 DDE Server Settings Command... 6 Configure Comm Port Settings... 8 Board Configuration Command... 9 Saving MISTICSA Configuration File Configuration File Location Topic Definition Command Using the MISTICSA Server with InTouch Defining the Tag names Controller STATUS Item Item (Point) Naming Item Point naming summary Notes on Using Microsoft Excel Reading Values into Excel Spreadsheets Writing Values to MISTICSA Points Troubleshooting WIN.INI entries Troubleshooting menu... 28

3 Klinkmann Automation MISTICSA DDE Server 1 MISTICSA DDE Server The MISTICSA DDE Server is a Microsoft Windows NT application program that acts as a DDE (Dynamic Data Exchange) Server and allows other Windows application programs to access the data in Cyrano 200 programs running on mistic Model 200 Controllers. The MISTICSA DDE Server can access up to 255 mistic Model 200 Controllers using the Serial and(or) Arcnet interfaces. The MISTICSA DDE Server supports two interfaces (Serial and Arcnet) in order to communicate with mistic Model 200 Controllers. The Serial interface requires an OPTO 22 AC37 adapter card connected to the high speed two wire RS-485 network. The Arcnet interface requires a PC bus ARCNET adapter card (8 or 16 bit, e.g. ARCNET-PC130E Network Controller Board) based on the SMC ARCNET chip. The Server is primarily intended for use with Wonderware InTouch, but it may be used by any Microsoft Windows NT program that is capable of acting as a DDE Client.

4 Klinkmann Automation MISTICSA DDE Server 2 What is DDE? DDE is a complete communication protocol designed by Microsoft to allow applications in the Windows environment to send/receive data and instructions to/from each other. It implements a client-server relationship between two concurrently running applications. The server application provides the data and accepts requests from any other application interested in its data. Requesting applications are called clients. Some applications such as InTouch and Excel can simultaneously be both a client and server. To obtain data from another application the client program opens a channel to the server application by specifying three things: the server application name, the topic name and the specific item name. For example, in the case of Excel, the application name is Excel, the topic name is the name of the specific spreadsheet that contains the data and the item name is the specific cell on the spreadsheet. With InTouch the application name is View, the topic name is the word Tag name when reading/writing to an InTouch tag name, and the item name is a specific tag name in the InTouch Data Dictionary. When a client application sets up a link to another DDE program, it requests the server application to advise the client whenever a specific item s value changes. These data links will remain active until either the client or server program terminates the link or the conversation. They are a very efficient means of exchanging data because once the link has been established no communication occurs until the specified data value changes. InTouch uses DDE to communicate with I/O device drivers and other DDE application programs. Accessing a Remote DDE Item from MISTICSA The DDE protocol identifies an element of data by using a three-part address, including: Application, Topic and Item. Application refers to the name of the Windows program (server) that knows how to access the data element. In the case of data coming from or going to mistic Model 200 hardware, the application portion of the DDE address is MISTICSA. Topic is an application-specific sub-group of data elements. The MISTICSA Server considers each mistic Model 200 Controller to be a separate topic. The user creates a meaningful name for each Controller and uses this name as the topic name for DDE references. Note: In some cases, the term node is used interchangeably with the term topic. Item indicates a specific data element within the specified topic. With the MISTICSA Server, an item is an individual point (I/O point, variable or PID Loop data) in the Cyrano 200 program running on mistic Model 200 Controller. (The item/point names are fixed by the MISTICSA Server as described in the Item (Point) Naming section.) Note: In some cases, the term point is used interchangeably with the term item.

5 Klinkmann Automation MISTICSA DDE Server 3 Installing the MISTICSA DDE Server The MISTICSA DDE Server installation package can be supplied: 1. As a self-extracting archive 05035xxx.EXE if downloaded from Klinkmann s web site (the xxx is the current (latest) version of the Server). 2. From installation on CD. 3. On two or three distribution disks (floppies). To install the MISTICSA DDE Server from the self-extracting archive, run the 05035xxx.EXE and proceed as directed by the MISTICSA Server Setup program. To install the MISTICSA DDE Server from CD or distribution disk, on MS Windows NT: 1. Insert the CD with Klinkmann Software into CD drive or insert the MISTICSA DDE Server disk into a floppy drive A: or B:. 2. Select the Run command under the Start menu. 3. Run STARTUP.EXE if installing from CD or SETUP.EXE if installing from distribution disks (floppies). 4. If installing from CD: select Protocol Servers (DDE, SuiteLink, OPC), find MISTIC SA DDE Server and click on Setup. 5. Proceed as directed by the MISTICSA DDE Server Setup program. When installation is finished, the subdirectory specified as a folder where to install the MISTICSA DDE Server will contain the following files: MISTICSA.EXE MISTICSA.HLP MISTICSA.CFG LICENSE.TXT WWCOMDLG.DLL The MISTICSA Server Program. This is a Microsoft Windows 32-bit application program. The MISTICSA Server Help file. An example configuration file. Klinkmann Automation software license file. Dynamic Link Library necessary for MISTICSA Server. To uninstall the MISTICSA Server, start Control Panel, select Add/Remove Programs and select the MISTICSA DDE Server from the list of available software products. Click on Add/Remove and proceed as directed by the UnInstallShield program. Note: The HASP key is needed for full time running of MISTICSA Server. The HASP Driver setup is performed during the Server setup. Without HASP Driver installed, the MISTICSA Server will run only 1 hour (with all features enabled). Connection Cables

6 Klinkmann Automation MISTICSA DDE Server 4 The MISTICSA DDE Server can communicate with mistic Model 200 Controllers either with Serial (RS232 or RS485) or Arcnet interfaces. In order to communicate through RS- 485 interface the AC37 super serial card should be installed on the computer or RS- 232/RS-485 converter should be used (the Server is tested with ENTRELEC RS232/RS485 converter). For communication through the Arcnet interface, the Arcnet card should be properly installed on PC and connected to the Arcnet network. If the AC37 serial card is used it should have proper jumper settings as well as the additional comm port added in the Microsoft Windows 3.xx Control Panel with corresponding base address and IRQ number settings. For Microsoft Windows NT, the Server provides additional configuration of comm ports by Com port settings... menu command. To use comm ports which are not supported by already installed Windows NT communication port driver (for example, AC37 serial card) the Use WinRT check box is to be checked in the Communication Port Settings dialog box. The following picture shows how to connect PC serial port to MISTIC controller. PC RS232 COM port MISTIC COM0 RS pin Connector 2 wire TERM YES 1 2 RXD 3 TXD 4 5 GND 1 2 TXD 3 RXD GND

7 Klinkmann Automation MISTICSA DDE Server 5 To connect the AC37 serial card the wiring diagram is the following: PC AC 37 MISTIC COM0 Super Serial Card RS485 2 wire 9 - pin connector TERM YES GND 4 DATA+ 8 DATA+ 5 DATA- 9 DATA- 3 GND 1 TX/RX+ 2 TX/RX- If RS232/RS485 converter (e.g. Entrelec) is used, the wiring diagram may be as follows: PC RS232 COM port MISTIC COM0 RS pin female 2 WIRE TERM YES ENTRELEC 1 2 TXD 3 RXD 4 5 GND K L M G A B C D E 1 TX/RX+ 3 GND 2 TX/RX- Jumper settings for ENTRELEC converter: Rt = 220 Om, R.ON/OFF, E.ON/OFF

8 Klinkmann Automation MISTICSA DDE Server 6 Configuring the MISTICSA Server After the MISTICSA Server is initially installed, a little of configuration is required. Configuring the Server automatically creates a MISTICSA.CFG file which holds all of the topic (Controllers) definitions entered, as well as the communication port configurations. This file will be placed automatically in the same directory in which MISTICSA is located unless the path where the configuration file will be placed is specified via the /Configure/Server Parameters command. To perform the required configurations, start up the MISTICSA program. If the Server starts up as an icon, double-click on the icon to open the server s window. The following will appear: To access the commands used for the various configurations, open the /Configure menu: DDE Server Settings Command A number of parameters that control the internal operation of the Server can be set. In most cases, the default settings for these parameters provide a good performance and do not require changing. However, they can be changed to the fine-tune Server for a specific environment. To change the Server s internal parameters, invoke the DDE Server Settings... command. The DDE Server Settings dialogue box will appear:

9 Klinkmann Automation MISTICSA DDE Server 7 The following describes each field in this dialogue box: Protocol Timer Tick This field is used to change the frequency at which the Server checks for work to do (at this frequency the Server tries to send one data request to PLC and receive one reply from PLC; if the send/response cycle is too long then more than one activation of Server is necessary to process it). For Windows 3.x if computer is very busy or some other MS Windows application is taking over the computer then the Server is activated more rarely than setting in the Protocol Timer Tick. Note: The default value is 50. This it the minimum value for Windows 3.x. If the value is lower than 50 entered, the Server uses 50 milliseconds. NetDDE being used Select this option if you are in network using NetDDE. Configuration File Directory This field is used to specify the path (disk drive and directory) in which MISTICSA will save its current configuration file. The MISTICSA Server will use this path to load the configuration file the next time it is started. Note: Only the path may be modified with this field. The configuration file is always named MISTICSA.CFG. Note: There is no limit to the number of configuration files created, although each must be in a separate directory. When using the MISTICSA Server with InTouch, it is a good practice to place the configuration file in the application directory. Once all entries have been made, click on OK.

10 Klinkmann Automation MISTICSA DDE Server 8 Configure Comm Port Settings To configure the mistic serial communication port, invoke the Communication Port Settings command. The Communication Port Settings dialogue box will appear: The following describes each field in this dialogue box: Reply Timeout This field is used to enter the amount of time (in seconds) that all Controllers using the selected communication port, will be given to reply to the commands from the Server. Note: The default value of 3 seconds should be sufficient for most configurations. Baud Rate Select the Baud Rate setting which matches the setting chosen for the mistic Network. (Refer to mistic Technical Reference Manual for Baud Rate selection instructions.) Base Address This field is used to enter the selected base address of the adapter card. The Base Address must be consistent with the base address selected on the AC37 adapter card. Attention should be drawn to selecting a base address which would not conflict with other devices in the system. Note: The default values are: 3F8H for COM1, 2F8H for COM2, 348H for COM3, 340H for COM4, 248H for COM5 and 240 for COM6. AC37 serial card Specifies if AC37 super serial card is used for current port. Interrupt Specifies the IRQ number for current port. Note: Interrupt is used only for Windows NT version. On all other platforms this control is disabled.

11 Klinkmann Automation MISTICSA DDE Server 9 Use Win RT driver This Control is enabled only for Microsoft Windows NT. Checking this check box causes using the WinRT driver instead of the standard serial port driver. WinRT driver is installed automatically together with MISTICSA DDE Server. If this check box is marked you should enter the correct Interrupt number and Base Address which do not conflict with other devices. You may use WinRT device driver to communicate through the AC37 serial card. Note: Marking this check box causes writing new or updating old registry entry in the Windows NT registry for each port with the marked check box. Entry is HKEY_LOCAL_MACHINE "System\CurrentControlSet\Services\WinRT". There are available up to 25 keys in this registry. Other programs can also use WinRT device driver as well as some of the keys may be occupied. Therefore it is recommended to use this setting only for few comm ports. When all entries have been made, select Done to process the configuration for the communication port. Note: If you are running Windows NT and you have made changes in WinRT settings, the Server tries to restart the WinRT device driver. Note: In order to configure the MISTICSA in Windows NT, DDE Server requires Administrator access rights. Board Configuration Command To configure the ARCNET Network Board, invoke the Board Configuration... command. The Board definition dialogue box will appear: To modify an existing board, select the board and click on Modify. To define a new board, click on New. To remove a selected board, click on Delete. The Board Settings dialogue box will appear:

12 Klinkmann Automation MISTICSA DDE Server 10 The following describes each field in this dialogue box: Board name This field is used to enter the ARCNET Board name. Board address This field is used to enter the ARCNET card network address. Board I/O Address This field is used to enter the I/O base address of the ARCNET interface. The Board I/O Address must be consistent with the base address selected on the ARCNET adapter card. To select a necessary Board I/O Address click on the combo box button and make your choice from the list box. Attention should be drawn to select a base address which will not conflict with other devices in the system. Board Memory Segment This field is used to enter the segment address for the ARCNET chip buffers. The Board Memory Segment address must be consistent with the base memory (RAM) buffer address selected on the ARCNET adapter card. To select a necessary Board Memory Segment click on the combo box button and make your choice from the list box. Reply Timeout This field is used to enter the amount of time (in seconds) that all Controllers using the selected communication port will be given to reply to commands from the Server. Note: The default value of 1 second should be sufficient for most configurations.

13 Klinkmann Automation MISTICSA DDE Server 11 Saving MISTICSA Configuration File If the configuration file does not currently exist, or a new configuration path has been specified, the Server will display the Save Configuration dialogue box: This dialogue box displays the path where the Server is going to save the current configuration file. The path may be changed if necessary. Also, the path can optionally be recorded in the WIN.INI file by selecting the Make this the default configuration option. Doing so will allow the MISTICSA Server to find the configuration file automatically each time it is started. Configuration File Location When the MISTICSA Server starts up, it attempts to locate its configuration file by, first checking the WIN.INI file for a path which was previously specified. If the path is not present in the WIN.INI file, the Server will assume that the current working directory is to be used. To start the Server from an application directory configuration file other than the default configuration file, a special switch (/d:) is used. For example, invoke the File/Run command and enter the following: MISTICSA /d:c:\directoryname Note: There is no limit to the number of configuration files that may be created, although each must be in a separate directory.

14 Klinkmann Automation MISTICSA DDE Server 12 Topic Definition Command The user provides each connected Mistic controller with an arbitrary name that is used as the DDE topic for all references to this PLC. The following steps are taken to define the Topic attached to the PLC: 1. Invoke the Topic Definition... command. The Topic definition dialogue box will appear: 2. To modify an existing topic, select the topic name and click on Modify. To define a new topic, click on New. To remove an existing topic, click on Delete. The MISTICSA Topic Definition dialogue box will appear: 3. Enter the Topic Name which corresponds to the DDE Topic Name (The DDE Topic Name is entered in the DDE Access Name Definition dialogue box described in the Using the MISTICSA Server with InTouch section). 4. Choose Arcnet or Serial interface with Arcnet checkbox. 5. Choose Serial comm port or Arcnet board associated with topic from combo box. 6. Set the Update Interval field to indicate the frequency the items/points on this topic will be read (polled). Default value is 1000 milliseconds. 7. When all entries have been made, click on OK to process the configuration of the topic.

15 Klinkmann Automation MISTICSA DDE Server 13 Using the MISTICSA Server with InTouch To access items/points on mistic Model 200 Controllers from InTouch, the following steps (all performed in WindowMaker) are required: To define the DDE Access Names in WindowMaker for each Controller invoke the /Special/DDE Access Name Setup command. The DDE Access Name Definition dialogue box will appear. Click on Add. The Add DDE Access Name Dialogue Box will appear: Note: If Add is selected, this dialogue box will be blank when it initially appears. Data has been entered here to illustrate the entries which are made. The following three fields are required entries when entering a DDE Access Name Definition: DDE Access Name Enter an arbitrary name which will be used by InTouch to refer to the topic (Controller). It is recommended that the name defined for the topic (Controller) in MISTICSA also is used here.)

16 Klinkmann Automation MISTICSA DDE Server 14 DDE Application/Server Name Enter the application name, MISTICSA, which is the DDE Server used to accessing the Controller. DDE Topic Name Enter the name defined for the topic in MISTICSA to identify the Controller the MISTICSA Server will be accessing. Note: This will usually be the same as the DDE Access Name, although, if desired, it may be different. However, it must be the same name used when the topics were configured in section Configuring the MISTICSA Server. Request Initial Data This option may be selected if the Server is other than a Wonderware DDE Server and the Server does not return data values immediately when a window is displayed. This option is not applicable to the MISTICSA DDE Server. Wait for Change This option should be selected when the DDE application is the MISTICSA DDE Server. Advise all Items This option may be selected if the Server is to poll for all data whether or not it is in visible windows, alarmed, logged or trended. Use of the option is not recommended. Advise only active Items Selecting this option will cause the MISTICSA Server to poll only points in visible windows and points that are alarmed, logged or trended.

17 Klinkmann Automation MISTICSA DDE Server 15 Defining the Tag names To define the Tag names associated with the new DDE Access Name, invoke the /Special/Tag Name Dictionary command (in WindowMaker). The Dictionary - Tag Name Definition dialogue box will appear: Click on New and enter the Tag Name. (The tag name defined here is the name InTouch will use. The MISTICSA Server cannot see this name.) Select the tag type by clicking on the Type button. The Choose tag type dialogue box will appear: To access MISTICSA items, the type must be DDE Discrete, DDE Integer, DDE Real or DDE Message. Select the DDE type. The Details dialogue box for the tag name will appear: Select the MISTICSA topic (Controller) by clicking on the DDE Access Name... button. The Select a DDE Access Name dialogue box will appear:

18 Klinkmann Automation MISTICSA DDE Server 16 Select the appropriate topic name and click on Done. (If the DDE Access Name has not been defined as previously described, click on Add and define the DDE topic now.) The Details dialogue box will appear displaying the selected DDE Access Name: For integers and reals fill in the Min EU, Max EU, Min Raw and Max Raw fields. These fields control the range of values which will be accepted from the server as well as the way the values are scaled. If no scaling is desired, Min EU should be equal to Min Raw and Max EU to Max Raw. Enter the MISTICSA item/point name to be associated with this tag name in the Item field in the Details box: (Refer to the Item (Point) Naming section below for complete details.)

19 Klinkmann Automation MISTICSA DDE Server 17 Where applicable, the Use Tag name as Item Name option may be selected to enter automatically the tag name in this field. Note: The tag name can only be used if it follows the conventions listed in the Item (Point) Naming section. Once all entries have been made, click on the Save button (in the top dialogue box) to accept the new tag name. To define additional Tag names click on the New button. To return to the WindowMaker main screen, select Done. Controller STATUS Item For each Controller, there is a built-in discrete item which indicates the state of communications with the Controller. The discrete item (Status) is set to 0 when communications with the Controller fails and set to 1 when communications are successful. From InTouch the state of communications with the Controller may be read by defining a DDE Discrete tag name and associating it with the topic configured for the Controller and using Status as the Item name. From Excel, the status of the communications may be read by entering the following formula in a cell: =MISTICSA topic!status

20 Klinkmann Automation MISTICSA DDE Server 18 Item (Point) Naming Within the MISTICSA Server, item/point naming depends on Cyrano 200 program tag names available on mistic Model 200 Controller. Generally these item names may be described as: ITEM_NAME for mistic Controller global settings. or P item name S where: item name - Cyrano 200 program tag name which always must be included in ; P - item name prefix, e. g. one character before first and represents item type; S - optionally used item name suffix, e. g. one character after second and shows item subtype. Both prefixes and suffixes may be written in upper case or lower case letters. These are item/point types possible in MISTICSA Server: 1) PROGRAM_STATE; DDE Type - DDE Integer; read/write; Reading this item returns current state of running program in mistic Controller. There are the following valid return values from the Controller: negative value - Error on mistic Controller 0 - Program is stopped. 1 - Program is running. writing this point stops or starts program on mistic Controller depending of written value. If written value is 0 then program stops. All other values starts up the program. Example: PROGRAM_STATE. 2) ERRORS; DDE Type - DDE Integer, This item returns number of errors in mistic Controller queue. Writing 0 to this item causes clearing all errors in mistic Controller. Any other written value is not valid and warning message are logged in logger window. Example: ERRORS. 3) FREE_MEM; DDE Type - DDE Integer, read only. This item returns amount of free memory on mistic Controller. Example: FREE_MEM. 4) EPROM_VERSION; DDE Type - DDE Message, read only. This item gets string containing EPROM set version. Example: EPROM_VERSION. 5) FILE_NAME; DDE Type - DDE Message, read only. This item gets string containing filename of downloaded file. Example: FILE_NAME.

21 Klinkmann Automation MISTICSA DDE Server 19 6) TIME_STAMP; DDE Type - DDE Message, read only. This item gets string containing timestamp of downloaded file. Example: TIME_STAMP. 7) DATE_STAMP; DDE Type - DDE Message, read only. This item gets string containing datestamp of downloaded file. Example: DATE_STAMP. 8) MONTH; DDE Type - DDE_Integer, read only. This item gets current month on mistic Controller. Example: MONTH. 9) DAY; DDE Type - DDE_Integer, read only. This item gets current day on mistic Controller. Example: DAY. 10) YEAR; DDE Type - DDE_Integer, read only. This item gets current year on mistic Controller. Example: YEAR. 11) HOURS; DDE Type - DDE_Integer, read only. This item gets current hour on mistic Controller. Example: HOURS. 12) MINUTES; DDE Type - DDE_Integer, read only. This item gets current minute on mistic Controller. Example: MINUTES. 13) SECONDS; DDE Type - DDE_Integer, read only. This item gets current second on mistic Controller. Example: SECONDS. 14) FORTH; DDE Type - DDE_Message, write only. This item executes FORTH style string on mistic controller. After response this item contains returned data interpreted as null terminated string. Example: FORTH = computes 5+11 on controller and returns string ) Task Status Bits; item/point name - R chart name DDE Type - DDE Integer, read only; chart name is the chart name in Cyrano 200 program. This item gets chart status setting the following bits: nothing - means chart is stopped. 0 - chart is running. 1 - chart is suspended. 2 - chart is in trace mode. 3 - chart is in break mode error indicator. Example: R POWERUP.

22 Klinkmann Automation MISTICSA DDE Server 20 16) Task Status String; item/point name - R chart name S DDE Type - DDE Message, read only; chart name is the chart name in Cyrano 200 program. This item gets chart status representing string. Example: R POWERUP S. 17) Chart Variable; item/point name - C chart name DDE Type - DDE Integer, read only; chart name is the chart name in Cyrano 200 program. This item gets chart state: I/O driver starting running. 0 - stopped. 1 - suspended. 2 - step mode. 3 - break. Example: C POWERUP. 18) Chart Variable String; item/point name - C chart name S; DDE Type - DDE Message, read only; chart name is the chart name in Cyrano 200 program. This item gets string as described above. Example: C POWERUP S. 19) Board Enable Disablem/point name - E board bame ; DDE Type - DDE Discrete, read/write; board name is the digital or analogue board name in Cyrano 200 program. This item returns 0 if board is disabled and returns 1 if board is enabled. Example: E DIGITAL_00. 20) Digital Brick External Status; item/point name - B board name ; DDE Type - DDE Integer, read only; This item in lowest bits (0 to 15) contains status (0 - OFF, 1 - ON) of each digital brick (board) external state of channel ; board name is the board name in Cyrano 200 program Example: B DIGITAL_00. 21) Digital Brick Internal Status; item/point name - $B board name, DDE Type - DDE Integer; read only; This item in lowest bits (0 to 15) contains status (0 - OFF, 1 - ON) of each digital brick (board) internal state of channel ; board name is the board name in Cyrano 200 program Example: $B DIGITAL_00. 22) Digital External Point; item/point name - D item name, DDE Type - DDE Discrete; read/write; This item contains external status (0 - OFF, 1 - ON) of digital brick channel; item name is the point name in Cyrano 200 program. Example: D DIGITAL_POINT14.

23 Klinkmann Automation MISTICSA DDE Server 21 23) Digital Internal Point; item/point name - $D item name, DDE Type - DDE Discrete; read/write; This item contains internal status (0 - OFF, 1 - ON) of digital brick s channel; item name is the point name in Cyrano 200 program. Example: $D DIGITAL_POINT14. 24) Digital Point External Integer Feature; item/point name - D item name I, DDE Type - DDE Integer; read/write; this item contains integer external feature value of digital brick s channel; item name is the point name in Cyrano 200 program. Example: D DIGITAL_POINT14 I. 25) Digital Point Internal Integer Feature; item/point name - $D item name I, DDE Type - DDE Integer; read/write; This item contains integer internal feature value of digital brick s channel; item name is the point name in Cyrano 200 program. Example: $D DIGITAL_POINT14 I. 26) Analog External Point; item/point name - A item name, DDE Type - DDE Real; read/write; This item contains external analogue value for analogue brick s channel; item name is the channel name in Cyrano 200 program. Example: A ANALOG_POINT05. 27) Analogue Internal Point; item/point name - $A item name, DDE Type - DDE Real; read/write; This item contains internal analogue value for analogue brick s channel; item name is the channel name in Cyrano 200 program. Example: $A ANALOG_POINT05. 28) Analogue Board External Status; item/point name - A board name n; DDE Type - DDE Real; read only; This item reads all channels of analogue brick and contains external value of one channel; board name is the analogue board name in Cyrano 200 program; n is the channel number of specified analogue board. Example: A ANALOG_ ) Analogue Board Internal Status; item/point name - $A board name n; DDE Type - DDE Real; read only; This item reads all channels of analogue brick and contains internal value of one channel; board name is the analogue board name in Cyrano 200 program; n is the channel number of a specified analogue board. Example: $A ANALOG_ ) Integer Variable; item/point name - I item name, DDE Type - DDE Integer; read/write; This item contains integer variable value; item name is the variable name in Cyrano 200 program. Example: I.TEMPERATURE_ALARM.

24 Klinkmann Automation MISTICSA DDE Server 22 31) Float Variable; item/point name - F item name, DDE Type - DDE Real; read/write; This item contains float variable value; item name is the variable name in Cyrano 200 program. Example: F PRESSURE. 32) Timer Variable; item/point name - T item name, DDE Type - DDE Real; read/write; This item contains timer variable value; item name is the variable name in Cyrano 200 program. Example: T TIMER. 33) String Variable; item/point name - S item name, DDE Type - DDE Message; read/write; This item contains string variable value; item name is the variable name in Cyrano 200 program. Example: S DATE/TIME_STRING. 34) Integer Table Element; item/point name - Index table name I, DDE Type - DDE Integer; read/write; This item contains one element from the Cyrano 200 program integer table; Index represents the address in the table and may contain any nonnegative number including 0 as well as less then table size in the Cyrano 200 program; table name is the numeric table name in the Cyrano 200 program. Example: 0 ALARMS I. 35) Float Table Element; item/point name - Index table name F, DDE Type - DDE Real; read/write; This item contains one element from the Cyrano 200 program float table; Index represents the address in the table and may contain any nonnegative number including 0 and less then table size in the Cyrano 200 program; table name is the numeric table name in the Cyrano 200 program. Example: 7 ALARMS F. Note: The Integer Table Elements and Float Table Elements described in 10) and 11) allow the fastest way of polling the data from Mistic controllers. The whole table (or portions of 32 elements if table size exceeds 32 elements) can be read at one Protocol Timer Tick. Therefore we recommend to use these items to poll numeric values from Cyrano 200 program. 36) String Table Element; item/point name - Index item name S, DDE Type - DDE Message; read/write; This item contains one element from the Cyrano 200 program string table; Index represents the address in the table and may contain any nonnegative number including 0 and less then table size in the Cyrano 200 program; item name is the string table name in the Cyrano 200 program. Example: 15 MESSAGES S.

25 Klinkmann Automation MISTICSA DDE Server 23 Note: Do not check the indexes of arrows. If index exceeds the maximal table size, item refers to the last table element. 37) PID Loop External Input; item/point name - P pid name N, DDE Type - DDE Real; read/write; This item contains PID Loop external input value; pid name is the PID Loop name in Cyrano 200 program. Example: P TEMPERATURE_PID N. 38) PID Loop Internal Input; item/point name - P item name N, DDE Type - DDE Real; read/write; This item contains PID Loop internal input value; item name is the PID Loop name in Cyrano 200 program. Example: $P TEMPERATURE_PID N. 39) PID Loop External Output; item/point name - P item name O, DDE Type - DDE Real; read/write; This item contains PID Loop external output value; item name is the PID Loop name in Cyrano 200 program. Example: P TEMPERATURE_PID O. 40) PID Loop Internal Output; item/point name - $P item name O, DDE Type - DDE Real; read/write; This item contains PID Loop internal output value; item name is the PID Loop name in Cyrano 200 program. Example: $P TEMPERATURE_PID O. 41) PID Loop External Setpoint; item/point name - P item name S, DDE Type - DDE Real; read/write; This item contains PID Loop external setpoint value; item name is the PID Loop name in Cyrano 200 program. Example: P TEMPERATURE_PID S. 42) PID Loop Internal Setpoint; item/point name - $P item name S, DDE Type - DDE Real; read/write; This item contains PID Loop internal setpoint value; item name is the PID Loop name in Cyrano 200 program. Example: $P TEMPERATURE_PID S. 43) PID Loop External Proportional Constant; item/point name - P item name P, DDE Type - DDE Real; read/write; This item contains PID Loop external proportional (gain) constant value; item name is the PID Loop name in Cyrano 200 program. Example: P TEMPERATURE_PID P.

26 Klinkmann Automation MISTICSA DDE Server 24 44) PID Loop Internal Proportional Constant; item/point name - $P item name P, DDE Type - DDE Real; read/write; This item contains PID Loop internal proportional (gain) constant value; item name is the PID Loop name in Cyrano 200 program. Example: $P TEMPERATURE_PID P. 45) PID Loop External Integral Reset Rate; item/point name - P item name I, DDE Type - DDE Real; read/write; This item contains PID Loop external integral reset rate value; item name is the PID Loop name in Cyrano 200 program. Example: P TEMPERATURE_PID I. 46) PID Loop Internal Integral Reset Rate; item/point name - $P item name I, DDE Type - DDE Real; read/write; This item contains PID Loop internal integral reset rate value; item name is the PID Loop name in Cyrano 200 program. Example: $P TEMPERATURE_PID I. 47) PID Loop External Derivative Rate; item/point name - P item name D, DDE Type - DDE Real; This item contains PID Loop external derivative rate value; item name is the PID Loop name in Cyrano 200 program. Example: P TEMPERATURE_PID D. 48) PID Loop Internal Derivative Rate; item/point name - $P item name D, DDE Type - DDE Real; This item contains PID Loop internal derivative rate value; item name is the PID Loop name in Cyrano 200 program. Example: $P TEMPERATURE_PID D. 49) PID Loop External Status; item/point name - P board name ns, DDE Type - DDE Real; read only; This item reads all PID Loops from specified entire analogue board; where: board name - analogue board name in Cyrano 200 program. n - PID Loop number in analogue brick. Number can vary from 0 to 7. s - can be one of following values: N - means PID Loop input. O - means PID Loop output. S - means PID Loop setpoint. Example: P TEMPERATURE_PID 3N. Note: Writing PID Loop may cause Mistic Controller hang up with some versions of downloaded firmware!

27 Klinkmann Automation MISTICSA DDE Server 25 Item Point naming summary. Item point name DDE Type Access Description PROGRAM_STATE Integer R/W PLC program state ERRORS Integer R/W Number of errors on PLC FREE_MEM Integer RO Free memory on PLC EPROM_VERSION Message RO PLC EPROM version FILE_NAME Message RO PLC program name TIME_STAMP Message RO PLC program time stamp DATE_STAMP Message RO PLC program date stamp MONTH Integer RO Month on PLC DAY Integer RO Day on PLC YEAR Integer RO Year on PLC HOURS Integer RO Hours on PLC MINUTES Integer RO Minutes on PLC SECONDS Integer RO Seconds on PLC FORTH Message WO FORTH command R chart name [S] Integer [Message] RO Chart status C chart name [S] Integer [Message] RO Chart variable E board name Discrete R/W Board enable disable flag ($)B board name Integer RO External (Internal) Digital brick status ($)D item name [I] Discrete [Integer] R/W External (Internal) Digital item point ($)A item name Real R/W External (Internal) Analog item point ($)A board name n Real RO External (Internal) Analog board channel I item name Integer R/W Integer variable F item name Real R/W Float variable T item name Real R/W Timer variable S item name Message R/W String variable n table name I Integer R/W Integer table n table name F Real R/W Float table n table name S Message R/W String table [$]P pid name N Real R/W External (Internal) PID loop input [$]P pid name O Real R/W External (Internal) PID loop output [$]P pid name S Real R/W External (Internal) PID loop setpoint [$]P pid name P Real R/W External (Internal) PID loop proportional constant [$]P pid name I Real R/W External (Internal) PID loop integral reset rate [$]P pid name D Real R/W External (Internal) PID loop derivative rate P board name nn Real RO External PID loop No. n input P board name no Real RO External PID loop No. n output P board name ns Real RO External PID loop No. n setpoint

28 Klinkmann Automation MISTICSA DDE Server 26 Notes on Using Microsoft Excel Data from MISTICSA topics (Controllers) may be accessed from Excel spreadsheets. To do so, enter a formula like the following into a cell on the spreadsheet. =MISTICSA topic!item Sometimes, Excel requires the topic and/or item to be surrounded by apostrophes. In the formula, topic must be replaced with one of the valid topic names defined during the Server configuration process. Replace item with one of the valid item names described in the Item (Point) Naming section. Reading Values into Excel Spreadsheets Values may be read directly into Excel spreadsheets by entering a DDE formatted formula into a cell, as shown in the following examples: =MISTICSA mist1! B DIGITAL_00 =MISTICSA controller3! F PRESSURE =MISTICSA mistic200! P TEMPERATURE_PID n Note: Refer to the Microsoft Excel manual for complete details on entering Remote Reference formulas for cells. Writing Values to MISTICSA Points Values may be written to MISTICSA Server from Microsoft Excel by creating an Excel macro that uses the POKE command. The proper command is entered in Excel as follows: channel=initiate("misticsa","topicname") =POKE(channel,"itemname", Data_Reference) =TERMINATE (channel) =RETURN() The following describes each of the above POKE macro statements: channel=initiate("misticsa","topicname") Opens a channel to a specific topic name (defined in the Server) in an application with name MISTICSA (the executable name less the.exe) and assigns the number of that opened channel to channel. Note: By using the channel=initiate statement the word channel must be used in the =POKE statement instead of the actual cell reference. The "applicationname" and "topicname" portions of the formula must be enclosed in quotation marks. =POKE(channel,"itemname", Data_Reference) POKEs the value contained in the Data_Reference to the specified item name (actual Cyrano 200 program tag name) via the channel number returned by the previously executed INITIATE function. Data_Reference is the row/column ID of the cell containing the data value. For "itemname", use some of the valid item names described in the Item (Point) Naming section.

29 Klinkmann Automation MISTICSA DDE Server 27 =TERMINATE(channel) Closes the channel at the end of the macro. Some applications have a limited number of channels. Therefore they should be closed when finished. Channel is the channel number returned by the previously executed INITIATE function. =RETURN() Marks the end of the macro. The following is an example of Excel macro used to poke value from cell B2 to topic Mist2 item A ANALOG_POINT05 : PokeMacro -Ctrl a =INITIATE("MISTICSA","Mist2") =POKE(A2,"A""ANALOG_POINT05""",B2) =ON.TIME(NOW()+0.01,"TerminateDDEChannel") =RETURN() TerminateDDEChannel =TERMINATE(A2) =RETURN() Note: Refer to the Microsoft Excel manual for complete details on entering Remote Reference formulas for cells.

30 Klinkmann Automation MISTICSA DDE Server 28 Troubleshooting WIN.INI entries The first time you run the MISTICSA Server configuration, most of the items in the following list will appear automatically in the WIN.INI file. Usually it is in the C:\WINDOWS directory. It is an ASCII file and can be altered manually if you wish with any text editor, e.g. MS Windows Notepad (do not use a program that formats text, such as MS Word or Write unless the file is saved as DOS text). The following is a typical entry for the MISTICSA Server: [MISTICSA] WinIconic=0 is set to 1 if server runs minimised. WinFullScreen=0 is set to 1 if server runs maximised. WinTop=126 WinLeft=548 WinWidth=414 WinHeight=144 ProtocolTimer CPUTiming varies delay performing way. May be 0 or 1. Default is 1; ValidDataTimeout default value RequestTimer ShowSend is equal to Troubleshooting menu Show Send. ShowReceive is equal to Troubleshooting menu Show Receive. Verbose is equal to Troubleshooting menu Verbose. DebugMenu Shows or hides Troubleshooting menu. Troubleshooting menu The following debugging choices are appended to the Server s System Menu (the menu that appears when you click on the - box in the upper left hand corner of the Server s window): Suspend Protocol / Resume Protocol - these choices permit you to turn protocol processing on and off, that allows you to suspend access to the Converter(s). Show Send - if checked then all outgoing data is displayed in hexadecimal format. Show Receive - if checked then all incoming data is displayed in hexadecimal format. Show Errors - if checked then all information about errors is displayed. Verbose - if checked then all information about warnings is displayed. Dump - logs all information about opened ports, active topics and data items. Dump Screen - Displays information about opened ports, active topics and messages in servers main window. Clear Screen - Clears server's main window. Can be used on slow computers to increase performance. All debug is displayed via the Wonderware Logger, which must be active for these commands to work. Warning: if you check Show Send and/or Show Receive then the debug output grows very fast.

31 Klinkmann Automation MISTICSA DDE Server 29 KLINKMANN AUTOMATION MISTICSA DDE Server Revision History Dec 93 Rev 1.0 First Release Apr 94 Rev 1.1 Grammatical bugs corrected Feb 95 Rev 1.2 Table read/write added TSR removed Sep 96 Rev 2.0 NT version added. New DDE items/points added. ARCNET support changed. Data reading performance improved. Aug 97 Rev 2.1 Windows 95 support added. Manual file name changed. Mar 2002 Rev 2.2 Installation from CD information added.