Table of Contents Contents

Transcription

1 MACO485 Instruction DDE Manual Server Table of Contents Contents 1. Introduction Data Blocks Control Relays What is DDE? DDE Address Application Name Topic Name Item Name Getting Started Files from Distribution Diskette Copy Files Installation Procedure (Disk 1) Excel Example Files (Disk 2) Starting the Server Manually Starting the Server Automatically Command Line Parameters Configuring the MACO485 DDE Server Configure Topic Command Select A Topic Dialog Box TOPIC SETUP Dialog Box Application Name Topic Name Comm Port Update Interval Device Address (UID) Triggered Blocks MACO Model Configuring a Communication Port Select a Port Dialog Box Serial Port Setup Dialog Box Comm Port Baud Rate Transmitter Control Reply Time-out Configuring Server Parameters Configuration File Path Protocol Timer Tick Time Limit for Data to be Read from Device Internal DDE Timer Tick MACO485 Item/Point Names Model 4000/5000/6000 Item Names Model 8000 Item Names Example of MACO 8000 Temperature Modfile Listing Debugging Server Problems Log Events Log Errors Log Traffic Page 1 of 28

2 8.4 Log Heap Accesses Log Rx Data Log Tx Data Show Tx/Rx Data Show Active Topic Details Show Topic Message Queues Refresh Screen Dump Logger Troubleshooting Troubleshooting DDE Servers Communications Between InTouch and the Server Communications Between the Server and MACO MACO Areas Using the Server with InTouch Defining a DDE Tagname - Step Defining a DDE Tagname - Step Defining a DDE Tagname - Step Defining a DDE Tagname - Step Defining a DDE Tagname - Step Defining a DDE Tagname - Step Defining a DDE Tagname - Step Equipment Requirements Specifications Wiring Application Notes Barber-Colman Company offers this product as a general purpose interface. We understand that it will be used in conjunction with other software and communications products; however, we cannot guarantee that it is fully compatible with all non-barber-colman software and hardware devices. We are committed to providing technical support and assistance in the use and application of this product; however, we also recommend consulting with the technical support personnel of related software and hardware companies for assistance in the use and application of their products. Page 2 of 28

3 1. Introduction MACO485 DDE Server The MACO RS-485 DDE Server is a Microsoft Windows application which provides the capability to link the MACO 4000, 5000, 6000 and 8000 series control systems to other Windows applications via DDE (Dynamic Data Exchange). This allows Supervisory Control and Data Acquisition (SCADA) over a standard network platform. A single serial port on a computer can communicate with up to 32 MACO controlled machines on a single cable. The host computer can collect, display and store operating data, as well as transmit setpoints and change control relay states to the MACO controllers. DDE must be built into a Windows program. Hundreds of programs that support DDE already exist, such as Excel, Word, Visual Basic, Lotus 1-2-3, Quattro Pro, Ami Pro, Wonderware s InTouch TM, Iconics Genesis for WIndows TM and its associated I/O Servers. BEFORE doing any programming, check the application notes at the back of this manual section. 1.1 Data Blocks Data can be read or written to the MACO in blocks, which results in much faster access times. Up to ten blocks can be defined. Each block can have as many as 60 values and/or setpoints. The total number of values and setpoints supported per MACO is 600 (10 blocks X 60 points/block). If more than 600 parameters are required in a multi-rack MACO 4000, 5000, or 6000 system, an RS-485 module can be installed in each rack. Note: The MACO 8000 RS-485 protocol does not support single-point access. Of the 10 blocks available, up to 5 can be designated as triggered blocks. Triggered blocks are updated by the MACO only when the RLD activates the Trigger CR. This allows shotwise or event driven data acquisition. DDE Items can be accessed through triggered blocks by appending a.t to the Item Name (values and setpoints only). The DDE topic must be configured with the same number of triggered blocks as the MACO it refers to (see Configuring the MACO485 DDE Driver ). 1.2 Control Relays MACO 4000, 5000, and 6000: Before attempting to establish communication between the host and MACO, make certain the following CRs are properly set in the RLD. The following control relays should be energized as required: CR 650 Enable Remote Setpoint Change CR 651 Enable Remote Control Relay Change CR 653 Enable Remote Recipe Save CR 654 Enable Remote Recipe Read CR 655 Enable Remote Recipe Delete The following control relay should be de-energized: CR 649 Inhibit Remote Access Decide if the following CR should be energized. CR 642 Inhibit Local Setpoint Change MACO 8000: CR 2645 Remote Access Enable CR 2646 Enable Remote Setpoint Change Page 3 of 28

4 2. What is DDE? MACO485 DDE Server Dynamic Data Exchange (DDE) is a complete communication protocol designed by Microsoft to allow applications in the Windows environment to send or receive data and instructions to or from each other. DDE implements a client-server relationship between two concurrently running applications. The MACO RS-485 DDE Server application provides data and accepts requests from any other application interested in its data. Requesting applications are clients. Some applications such as 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 two items: the server "Application Name" and the "Topic Name." Once a channel is open, the "Item Name" in the topic can be read or written. 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 in the spreadsheet. Within Wonderware's InTouch, the Application Name is View, the Topic Name is the word Tagname when reading or writing to an InTouch tagname and the Item Name is a specific tagname 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. An advise link is an efficient means of exchanging data because once the link has been established, no communication occurs until the specified data value changes. 2.1 DDE Address 2.2 Application Name 2.3 Topic Name The RS-485 DDE Server protocol identifies an element of data using a three-part convention that includes the Application Name, Topic Name, and Item Name. The Application Name is 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 a MACO via this DDE Server, the application portion of the DDE address is MACO485. The Topic Name is used by the DDE Server to specify an application-specific subgroup of data-elements. In the case of the MACO485 DDE Server, the subgroup refers to a single MACO device. The user creates meaningful names for each MACO and uses those names as the Topic Names for all DDE conversations that reference that MACO. Note: Only one Topic Name should be defined for a single MACO. 2.4 Item Name The Item Name is the name of a specific data element within the specified topic. For the MACO485 DDE Server, the item name corresponds to a single data item (value, setpoint, control relay, etc.) on the MACO referred to by this Topic Name. Note that the term point is used interchangeably with the term item. Page 4 of 28

5 3. Getting Started MACO485 DDE Server 3.1 Files from Distribution Diskette The MACO485 DDE Server Distribution Diskettes create the following files in the C:\BCDDE directory: MACO485.EXE: The MACO485 DDE Server program. This is a Microsoft Windows application program and requires Windows 3.1 or later (the server has not been tested under Windows 3.0). MACO485.HLP: The Windows help file for the MACO485 DDE Server. 3.2 Copy Files Make a backup copy of the installation disks. 3.3 Installation Procedure (Disk 1) The MACO485 DDE Servers will run in either Windows 3.1X, Windows 95 or Windows NT. The INSTALL.EXE program assumes that it is installing on Windows 3.1X or Windows NT 3.51 therefore, it will try to set up a Program Group for the DDE Servers. Since Windows 95 does not use program groups, select NO when asked to create a Program Group. The INSTALL.EXE program creates a directory named BCDDE and copies the appropriate files to that directory. To execute the DDE Servers, go to the BCDDE directory, and run the MACO485.EXE program. The copy protection hardkey must be installed on the LPT1 parallel printer port to execute the server programs (the hardkey does not need to be installed to run the installation program). Windows 95 or Windows NT 3.51 also require a device driver which allows the DDE Server to connect to the LPT1 parallel printer port to read the HARDkey. This device driver is installed by executing the file HINSTALL.EXE. Under Program Manager, File, Run, enter A:HINSTALL.EXE/I. This will install the appropriate drivers. Shutdown and restart the system for the newly installed driver to become active. The following is a step by step guide on how to install the MACO485 DDE Server in a Windows 3.1X application. Step Action 1. Insert the Installation Disk 1 in Drive A. Note: If your 3 1/2 drive has a different drive letter, substitute that drive letter. 2. Startup Windows. 3. From the Windows Program Manager, choose Run from the File menu. 4. On the Command Line enter A:INSTALL.EXE. 5. Choose OK. 6. The install program will step you through the installation procedure and create a default directory C:\BCDDE. Page 5 of 28

6 3.4 Excel Example Files (Disk 2) The Example Disk (2) contains a read me file and demonstration example files linking the RS-485 DDE Server with an Excel spreadsheet to a sub-directory called c:\demo. Step Action 1. Insert Disk 2 into Drive A. 2. From the Windows File Manager, choose Create Directory from the File menu. 3. On the Name line enter C:\DEMO and Choose OK. 4. Determine which of the examples you wish to copy to your hard drive. A:\DEMO\ALPHA\M4KEMO1.XLS MACO From the File Manager, choose Copy from the File menu. 6. Enter the files you wish to copy, for example: From: A:\DEMO\ALPHA\M4KEMO1.XLS To: C:\DEMO 3.5 Starting the Server Manually Double click on the program icon to start the MACO485 DDE Server. Note: It is important to always start the server before the client application. 3.6 Starting the Server Automatically Windows can start the MACO485 DDE Server automatically when it starts. Windows 3.0 Enter the DDE Server s program name in the load = line in the WIN.INI file as follows: load=c:\bcdde\maco485. Note: The MACO485 DDE Server has not been tested with Windows 3.0. Windows 3.1 Step Action 1. While in the Program Manager, hold down the Ctrl key and click the MACO485 DDE icon in the MACO485 DDE Server group and drag the icon into the Startup group. 2. Open the Startup group and drag the MACO485 DDE icon in front (to the left) of any client programs that may use the MACO485 DDE Server 3. Reboot the computer and start Windows to cause the DDE Server to start automatically. When windows starts, the server will be started first, and then the client application. Note: If you do not want to start the programs in the Startup group, hold down the SHIFT key while Windows is starting and wait until the Program Manager appears. 3.7 Command Line Parameters The server configuration file path is normally saved in the WIN.INI file. However, an alternate file path can be given on the command line that will override the setting in the WIN.INI file. Page 6 of 28

7 To specify a file path for the server configuration files other than that specified in the WIN.INI file, use the following command line syntax: MACO485 /D:{filepath} ex. MACO485 /D:c:\myapp Note: There should be NO spaces between the /D: switch and the actual directory path ( c:\myapp in the above example). 4. Configuring the MACO485 DDE Server After the MACO485 DDE Server is initially installed, a small amount of configuration is required. Configuring the Server automatically creates a MACO485.CFG file which holds all of the MACO485 DDE configuration information. This file is placed in a directory specified by the user. There is no limit to the number of configuration files that can be created, although each must be in a separate directory. When using the MACO485 DDE Server with Wonderware's InTouch, it is good practice to place the configuration file in the application directory. To perform the required configuration, start up the MACO485 DDE Server. If the Server starts up as an icon, double-click on it to open up the Server s window. The following will appear: To access the commands used for configuration, open the /Configure menu: 4.1 Configure Topic Command The Configure Topic command is used to create, modify, or delete topic definitions. One topic definition must exist for each MACO that the DDE Server will communicate with. To setup the topic names, invoke the /Configure/Topic Setup... command. Page 7 of 28

8 4.2 Select A Topic Dialog Box When the /Configure/Topic Setup... command is selected for the first time, the Select A Topic dialog is displayed: If topics already exist, the Select A Topic dialog box will appear as below: Click on Cancel to abort topic configuration. Click on New to define a new topic or select an existing topic in the topic list. Click on Modify to examine or change the configuration of an existing topic. Select a topic and click on the Delete button to remove a topic. (A message box will appear prompting you to confirm the deletion.) 4.3 TOPIC SETUP Dialog Box If either the New or Modify button is clicked, the TOPIC SETUP dialog box is displayed: Note that the Block Access box should be checked for normal operation (communications will slow significantly if it is not) Application Name Displays the DDE Application Name that must be used by other Windows applications to open a DDE channel to this topic. Page 8 of 28

9 4.3.2 Topic Name MACO485 DDE Server A DDE Topic Name must be entered for each group of MACO DDE items. Each Topic Name must be unique within the scope of the MACO DDE Server (two different servers can have defined topics with the same name). Note: When communicating with InTouch, this name is used as the Topic Name in the DDE Access Name definition Comm Port Update Interval Device Address (UID) Triggered Blocks MACO Model This button is used to select which communication port will service this topic. Pressing the button will cycle through the available options (COM1-COM4). This number controls how often (in milliseconds) the items/points in this topic will be read (polled). This device address must match the address of the target MACO (1-32). The number of triggered blocks must match the number of triggered blocks specified on the MACO (0-5). Select either Models 4000/5000/6000 or a Model 8000 (the communications protocol is slightly different for the model 8000). 5. Configuring a Communication Port The Configure Comm Port Setup command is used to modify the setup of a particular communication port. Each topic must be associated with a communication port that will service it. To setup a communication port, invoke the /Configure/ Comm Port Setup... command. 5.1 Select a Port Dialog Box When the /Configure/Comm Port Setup... command is selected, the Select a Port dialog is displayed: Click on Cancel to abort port configuration. Select a port in the port list and click on Modify to examine or change the configuration of the selected port. Page 9 of 28

10 5.2 Serial Port Setup Dialog Box If one of the COMx ports is selected and the Modify button is clicked, the Serial Port Setup dialog box is displayed: 5.3 Comm Port 5.4 Baud Rate 5.5 Transmitter Control This displays the current communication port that is being configured. This group of radio buttons allows you to select one of the following baud rates: 1200, 2400, 4800, 9600, or The RS-232 serial port of a PC must be connected (through a converter box) to the RS-485 board of the MACO. RS-485 uses the same pair of wires to send and receive. When a side is sending, its transmitter is turned on; when it is receiving, its transmitter is turned off. Transmitter control is handled internally by some converters; others need to be told when to turn on and off their transmitters. Refer to the converter documentation to determine the requirements of the converter. If transmitter control internally, select the None radio button; if the converter needs to be signaled for transmitter control, select the radio button with the signal line and polarity that will turn on the transmitter of the converter. Note: Select None for Barber-Colman converter A Reply Time-out This edit box allows you to specify the amount of time the Server will wait for an expected response before generating an error and going on the next command in the queue for this port. This setting will not affect the performance of the Server when all MACOs are active (powered up) and responding (correct serial port settings). However, performance will be affected if there are MACOs connected that are not responding to commands. 6. Configuring Server Parameters 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 good performance and do not require changing, although they can be changed in order to fine tune the server for a specific application. To change the server s internal parameters, invoke the /Configure/Server Parameters command. Page 10 of 28

11 The SERVER SETUP dialog box will appear: MACO485 DDE Server 6.1Configuration File Path When configuring the server, the path (disk drive and directory) in which the MACO485 DDE Server is to save its configuration file must be specified. MACO485 uses the specified path to load the configuration file each time it is started. There is no limit to the number of configuration files created, although each must be in a separate directory. When using the MACO485 DDE Server with InTouch, it is good practice to place the configuration file in the application directory. Only the path may be modified with this field. The configuration file name is always MACO485.CFG. Whenever the configuration file is changed (saved), the old file is renamed to MACO485.CBK before the new configuration is saved. 6.2 Protocol Timer Tick This setting controls how often the Server checks for work to do. Set at 2 to 4 times the fastest rate desired to update data to or from any MACO. Note that the timer tick is based on the DOS/Windows clock tick which occurs times every second, which gives the Protocol Timer Tick a resolution of about 54 milliseconds. 6.3 Time Limit for Data to be Read from Device This setting controls the maximum time the Server will wait while trying to read values from a MACO before it reports a failure to the Client program (this is not the same as the Reply Time-out in the Serial Communication Port Setup dialog). This parameter does not affect the performance of the Server under normal operation and it is recommended that this parameter be left at the default setting. 6.4 Internal DDE Timer Tick The data entered in this field controls how often the Server performs various internal timing functions. It affects only error reporting, not normal performance and it is recommended that this parameter be left at the default setting. 7. MACO485 Item/Point Names The following information is provided for each Item Name: Point Type The MACO data type for this point. Point Name The name of the item used by a client to access a specific data element. The Item Name is presented in uppercase, however, the server is NOT case sensitive to item names. DDE Type, Read/Write Access Discrete, Integer, or Message. Use this information when defining a Tagname with InTouch. The Read/Write access indicates if the points can be written as well as read. Page 11 of 28

12 7.1 Model 4000/5000/6000 Item Names There are 2 forms of Item Name used for the MACO 4000/5000/6000. Both consist of a series of decimal or hexadecimal numbers separated by periods. The numbers together form the address used by the MACO to reference the data point. Refer to the tab sections of this manual to find the addresses associated with the data points. The first form of Item Name is: d.d.xx.xx.xx where d represents a decimal number, and xx represents a 2-digit hexadecimal number. The numbers are: d Chassis Number 1-4 d Board Number 1-12 xx Function Number <FN> xx Type, Upper <TYU> xx Type, Lower <TYL> The second form of the Item Name is different from the first only in that it combines the first two decimal numbers into a single 2-digit hexadecimal number, and prefixes the name with an H. The first digit of this number represents the chassis number; the second digit represents the board number. Together they form the Function Address: H.xx.xx.xx.xx xx Function Address <AD> xx Function Number <FN> xx Type, Upper <TYU> xx Type, Lower <TYL> Two different suffixes can be used with the item names:.t indicates the point should be in a triggered block;.s identifies the point as a Selector Switch Control Relay. Their use is indicated in the table below. The following table shows the various types of items, with both name forms for each. As above, d and x refer to decimal and hexadecimal numbers; any other characters are typed as-is. Parts of item names contained in square brackets ([]) are optional. Point Type Point Name DDE Type, R/W Access Control Relay H.xx.xx.2x.xx -or- H.xx.xx.Cx.xx Discrete, Read-Only Value H.xx.xx.0x.xx[.T] -or- d.d.xx.8x.xx[.t] Integer, Read-Only Setpoint H.xx.xx.1x.xx[.T] -or- H.xx.xx.5x.xx[.T] Integer, Read-Write String H.xx.xx.4x.xx Message, Read-Only Selector CR H.xx.xx.2x.(98-9F).S -or- H.xx.xx.Cx.(98-9F).S Integer, Write-Only Point Type Point Name DDE Type, R/W Access Control Relay d.d.xx.2x.xx -or- d.d.xx.cx.xx Discrete, Read-Only Value d.d.xx.0x.xx[.t] -or- d.d.xx.8x.xx[.t] Integer, Read-Only Setpoint d.d.xx.1x.xx[.t] -or- d.d.xx.5x.xx[.t] Integer, Read-Write String d.d.xx.4x.xx Message, Read-Only Selector CR d.d.xx.2x.(98-9f).s -or- Integer, Write-Only d.d.xx.cx.(98-9f).s Page 12 of 28

13 7.2 Model 8000 Item Names MACO485 DDE Server Item names for the Model 8000 are similar to the Models 4000/5000/6000, with a few exceptions. First, only the second form of naming is used (H.xx.xx.xx.xx); and the MACO 8000 documentation uses different names to refer to the numbers making up the address: xx xx xx xx Module Address Parameter Type Parameter Description Parameter Number Second, control relays names are different: H.xx.CR.xx.x The hexadecimal numbers in this name are: Module Address, control relay byte, and bit number in the control relay. Bit number is a single digit, 0-7. Third, Selector Control Relay and String point types are not available from the Model The following table shows the various types of items, with the name forms for each. As above, d and x refer to decimal and hexadecimal numbers; any other characters are typed as-is. Parts of item names contained in square brackets ([]) are optional. Point Type Point Name DDE Type, R/W Access Control Relay H.xx.CR.xx.x Discrete, Read-Only Value H.xx.xx.0x.xx[.T] Integer, Read-Only Setpoint H.xx.xx.1x.xx[.T] -or- H.xx.xx.5x.xx[.T] Integer, Read-Write Get the I/O point configuration information from the MACO 8000 modfile listing. In order to view the modfile listings of your system, you must have the disk that holds your modfile screens. You can obtain a printed copy of the listing by means of the MODLIST.EXE program on the screen editor utilities diskette. Page 13 of 28

14 7.2.1 Example of MACO 8000 Temperature Modfile Listing MACO485 DDE Server Temperature Version-1 Revision-1 Decimal Data 92 Configurations MOD PT PD PN LABEL Alt Pol Mas Bgp VDec Dec Llimit Hlimit Z 1 Temp Deg F N N N N N Z 2 Temp Deg F N N N N N Z 3 Temp Deg F N N N N N Z 4 Temp Deg F N N N N N Z 1 SetPt Deg F N N N N N Z 2 SetPt Deg F N N N N N Z 3 SetPt Deg F N N N N N Z 4 SetPt Deg F N N N N N Zone 1 Pb Deg F N N N N N Zone 2 Pb Deg F N N N N N Zone 3 Pb Deg F N N N N N Zone 4 Pb Deg F N N N N N Z 1 Reset Cnst F N N N N N Z 1 Reset Cnst F N N N N N Z 1 Reset Cnst F N N N N N Z 1 Reset CnstF N N N N N Temperature Version-1 Revision-1 Decimal Data 47 Control Relays: (The following columns illustrate the byte# and bit designations of the CRs. They are not part of the MODFILE.) MOD ADDR LABEL (Byte #) (PT) (Bit#) (PD) AUTO COMP ENABLE INTEGRAL = ZERO Z5 ALARM/MANUAL ENABLE OUTPUTS Z1 AUTO/MANUAL Z2 AUTO/MANUAL Z3 AUTO/MANUAL Z4 AUTO/MANUAL HBO ALARM AUTOCOMP ACTIVE DEV POS ALARM DEV MINUS ALARM TEMP LOW ALARM TEMP HIGH ALARM T/C BREAK ALARM T/C BREAK ZONE T/C BREAK ZONE T/C BREAK ZONE T/C BREAK ZONE HBO ALARM ZONE HBO ALARM ZONE HBO ALARM ZONE HBO ALARM ZONE4 2 7 Page 14 of 28

15 8. Debugging Server Problems The MACO485 DDE Server has a number of debugging options to help track down problems. Many of these options use the Wonderware Logger to record error messages. 8.1 Log Events 8.2 Log Errors 8.3 Log Traffic 8.4 Log Heap Accesses 8.5 Log Rx Data 8.6 Log Tx Data 8.7 Show Tx/Rx Data With this option checked, a message is sent to the WonderWare Logger (WWLOGGER) any time a new value for an active item is set by the server. Under most circumstances this should be disabled as it will slow down the server s operation considerably. It is normally used only for troubleshooting. With this option checked, a message is sent to the WonderWare Logger (WWLOGGER) any time an error occurs, including communication errors, error responses from the MACO, and errors related to topic and item naming. This is best method for determining errors; it is recommended that this option be left on. With this option checked, a message is sent to the WonderWare Logger (WWLOGGER) to display server DDE protocol call traffic. Under most circumstances this should be disabled as it will slow down the server s operation considerably. It is normally used only for troubleshooting. With this option checked, messages are sent to the WonderWare Logger (WWLOGGER) that deal with the internal workings of the Server and how it makes use of the memory heap. This option is used for software debugging and should be left off unless instructed by Technical Support to enable it. With this option checked, a formatted message is sent to the WonderWare Logger (WWLOGGER) containing the response packet received from a MACO. This option should normally be left off. With this option checked, a formatted message is sent to the WonderWare Logger (WWLOGGER) containing the command packet sent to a MACO. This option should normally be left off. Displays the same information as Log Rx Data/Log Tx Data, but displays it in the Server Window. Page 15 of 28

16 8.8 Show Active Topic Details The Server Window always displays the names of all active topics. Enabling this menu item will cause additional topic information to be displayed, including: MACO address, Number of triggered blocks, Number of active symbols (items), Number of total symbols. 8.9 Show Topic Message Queues Enables a summary display in the Server window of all pending message queues This option should normally be left off Refresh Screen 8.11 Dump Logger With this command selected, the Server window is refreshed (redrawn). The client area is used to display a summary of all active topics, current state, and a variety of other useful information. With this command selected, detailed information for all active topics, symbols (items), and pending messages is sent to the WonderWare Logger (WWLOGGER). This command is generally only used for troubleshooting. 9. Troubleshooting 9.1 Troubleshooting DDE Servers This section provides some simple steps that can be taken to ascertain and correct communication problems. The problems described here represent the most probable causes of communication failure. Since it is not possible to cover every possible source of conflict, after reading this section, if you still cannot establish communications, call Barber-Colman Technical Support ( ) Communications Between InTouch and the Server This section explains the most common error situations that can occur when attempting to establish a DDE conversation between InTouch and a DDE Server. All I/O drivers used by InTouch are separate Windows applications called DDE Servers. These programs respond to DDE requests made by other applications. The requesting applications are called clients. When WindowViewer requires the status of a DDE item, it opens a channel with the DDE Server and requests it to advise WindowViewer whenever the DDE item changes. The DDE Server automatically handles all of the messages to and from the I/O device. The client application simply tells the DDE Server what data element or I/O point to read or write. The DDE Server then automatically updates the client upon any change of that data value. We highly recommend that you always start the DDE Server before starting WindowViewer. If WindowViewer attempts to establish a channel with a DDE Server that is not running, the Initiating DDE Conversation message box will appear for each uninitiated DDE conversation. Page 16 of 28

17 When this dialog box appears, note the information on the second line. This information indicates that at least one DDE tagname in WindowMaker is linked to a DDE Access Name that defines the Application Name and Topic Name specified in the second line. When the WindowViewer program was started, it immediately looked for the specified DDE Server Application Name and Topic Name. It could not find this application and/or topic and is notifying you that communications cannot be established. Three situations commonly cause the dialog box to appear: The server is not running The DDE Server application is not running. Verify this by opening the Windows Task List (press Ctrl+Esc keys) and check the list of currently running applications for the DDE Server s program name. The server s program name is misspelled in the DDE Access Name definition The server is running, but its name is misspelled in one or more DDE Access Name definitions. The name entered in the DDE Access Name definition must be the DDE server s actual name (less the.exe extension) as seen in the Windows File Manager. The topic is not defined in the server or it is misspelled Let s assume the servers name is spelled correctly and is running. WindowViewer is now looking for a topic defined in the server as TEST. To check the Topic Name, close WindowViewer (the server cannot be configured if WindowViewer is running) and open the server s program window. Invoke the /Configure/Topic Setup... command. Is there a topic defined as TEST listed in the topic list? Is it spelled exactly the same (including spaces, etc.) as it is in the DDE Access Name definition? Note: Make sure there are no blank spaces after the Topic Name in both the server and in the DDE Access Name definition in WindowMaker. Once all above is checked, restart WindowViewer and switch to the server s program window. Data should now appear in the window. This data indicates that WindowViewer and the server are communicating. The data indicates read and write messages that the server is attempting to send to the device. These are not error messages, but status messages (the level of detail is determined by the options checked in the Debug menu). If no data appears in the server s window, check the WWLogger for error messages. The most probable error message would be: Error for DDE Message ApplicationName TEST!<null> ( item ) Advise failed - This error message indicates that the Item used on a tagname is unrecognized by the server. InTouch tagnames use specific naming conventions when accessing data from a server. Typically, the item naming conventions the server uses are consistent with the names used by the equipment manufacturer. Page 17 of 28

18 9.1.2 Communications Between the Server and MACO This section addresses how to achieve communications between the DDE Server and the MACO. When attempting to establish communication between the DDE Server and your MACO, if no data appears in the server s window and the points defined in the WindowViewer window are not updating, check the WWLogger for error messages. For example, one of the most common error messages is: Port x response timeout This message indicates a problem between the server and the MACO. In most cases, either the server is not communicating through the communication port or the MACO is not responding. The first thing to is to ensure that the communication port connected to the MACO is the communication port configured for use by the server s topic definition. Then verify that the communication port is operating correctly in Windows. Note: A common misconception is that if you are able to connect to the MACO with a DOS program, the port will work properly in Windows. Remember that Windows is a different environment than DOS. To verify that the communication port is working properly in Windows, shut down the server and start the Windows Terminal program. Configure the Terminal program to use the same communication port at known settings (baud rate, parity, etc.). Then use a null modem cable to connect to another computer s port that is also running a Terminal like program with the same settings and see if characters can be sent between the two computers. If you do not have two computers and the computer you are using has another port, start two Terminal programs (each set to their own port) and try communicating between them. Or, if you have an external modem, connect the modem to the communication port in question and see if you can dial out with it. If the communication port does not appear to work, check your environment files (AUTOEXEC.BAT, CONFIG.SYS, SYSTEM.INI and WIN.INI). Look for suspicious programs or drivers that might be taking control of the port or its interrupt before the server is loaded. Always try to keep your environment files as simple as possible. If in doubt, remark it out. Note: When using an AT type computer, two devices cannot share interrupts (IRQs). Make sure the communication port you are using has a unique IRQ assigned to it. 9.2 MACO Areas If the communication port checks out, look for problems on the MACO side. Potential problems in this area could be, but are not limited to cabling, mismatched UID numbers, Baud Rate, faulty MACO port, etc. If you have completed all these steps and are still unable to communicate with the MACO, call Technical Support. 10. Using the Server with InTouch Wonderware InTouch can access items/points in a Barber-Colman MACO by creating DDE type tagnames in its Tagname Data Dictionary and associating those tagnames with a DDE Access Name containing the Topic Name defined in the MACO485 DDE Server for the MACO. Page 18 of 28

19 The following steps will walk you through the steps involved in defining a DDE tagname. All steps are performed in WindowMaker. Note: Barber-Colman does not provide application support of Wonderware InTouch or others applications software. Application Note Problems have been seen using the RS-485 DDE Server with WonderWare for recording setpoint changes made at the MACO. Either of the following two solutions should resolve the problem: In WonderWare, change the default setting of When to Advise Server in the DDE Access Name menu from Advise Only Active Items to Advise All Items. This will place all items in the scan list, and not cause the DDE server to re-download a menu block to the network module producing the setpoint change problem. Setup tags which are required for setpoint logging in a triggered block. This is done by adding T to the end of the tag name. Other tags which are on-demand scanned would be allocated to separate non-triggered blocks by the DDE server. The key element is that setpoint logging requires that the items are always scanned, therefore the triggered blocks are never modified Defining a DDE Tagname - Step 1 To define a new tagname, start WindowMaker and open the Special menu. Click on the Tagname Dictionary... command Defining a DDE Tagname - Step 2 The Dictionary - Tagname Definition dialog box appears. Click on the New button. Page 19 of 28

20 Note: If this is the first time the database has been accessed, the definition for the internal tagname Access Level will be displayed. Once a tagname has been defined and the Data Dictionary is again accessed, the data on file for the previously accessed tagname will automatically be displayed when the dialog box appears Defining a DDE Tagname - Step 3 The tagname to be defined for the DDE item in the database is now entered in the Tagname field. Tagnames can be up to 32 characters long. The first character must be A-Z or a-z. The remaining characters can be any combination of A-Z, a- z, -,?, #, $, %, _, or &. For this example we will define a Tagname that will be used to display an integer value retrieved from a MACO, so enter IntValue as the Tagname. Click on the Type... button to select the type for the tagname Defining a DDE Tagname - Step 4 The Choose tag type... dialog box will appear. Select the appropriate DDE type for the tagname. (The type is selected according to tagname s usage. For example, if the tagname is to read/write a value representing a signed or unsigned integer, its type would be a DDE Integer.) In this case, click on DDE Integer type to close the Choose tag type... dialog box. Page 20 of 28

21 10.5 Defining a DDE Tagname - Step 5 The Dictionary - Tagname Definition dialog box will reappear along with the Details dialog box for the DDE Type selected: NOTE: If the Details dialog box does not appear, click on the Details radio button at the top of the Dictionary - Tagname Definition dialog box. Once all details have been entered, click on the DDE Access Name... button Defining a DDE Tagname - Step 6 Each DDE type tagname must be associated with a DDE Access Name that defines the application name and Topic Name from/to which the tagname will read/ write its value. To define a new DDE Access Name click the Add... button. Page 21 of 28

22 10.7 Defining a DDE Tagname - Step 7 The Add DDE Access Name dialog box will appear. This dialog box is used to enter the application name and Topic Name to be associated with the specified DDE Access Name. DDE Access Name - Enter an arbitrary name that will be used by InTouch to refer to this DDE Access Name, e.g. TEST (use the same name defined for the topic in the DDE server). DDE Application/Server Name - Enter the actual program name for the server program from which the data value will be acquired. For the MACO485 DDE server, enter MACO485. Note: Do not enter the.exe extension portion of the program name. DDE Topic Name - Enter the Topic Name to be accessed. When InTouch is communicating with a DDE Server, the Topic Name is always the exact name defined for the topic in the DDE Server program, including blank spaces. Request initial data - Select this option only if the server program does not return data values immediately when a window is displayed. Wait for change - This is the option that should normally be selected for the MACO485 DDE Server. Advise all items - Select this option if the server program is to poll for all data whether or not it is in visible windows, alarmed, logged, trended, or used in a script. Selecting this option will impact performance, therefore its use is not recommended. Advise only active items - Select this option to cause the server program to poll only points in visible windows and points that are alarmed, logged, trended, or used in any script. This option is recommended. Once all entries have been made, click on the OK button to close the dialog box and accept the new DDE Access Name. Page 22 of 28

23 11. Equipment Requirements MACO485 DDE Server PC Hardware PC Software Hardware MACO 4000, Hardware IBM or compatible 386/486 equipped with a minimum of 2MB RAM. May require more memory to run other Windows programs simultaneously. Microsoft Windows (Version 3.10 or later), Windows for Workgroups, Windows 95, or Windows NT Barber-Colman RS-232 to RS-485 converter part #... A RS-485 Host Communication Kit X (Requires digital communications motherboard and cables) Communications Motherboard... A X-1-00 MACO 4000,5000,6000 Firmware Required OR MACO 8000 Data Handler v20.76 or higher Sequence v03.46 or higher Note: Exercise care when placing a RS-485 board into an existing MACO system. MACO 4000, 5000 and 6000 Series Controllers manufactured before April 30, 1996 may not support the RS- 485 option without modification. Sequence A X or later A X/A (all compatible) or any sequence/hydraulic with 7132 on the chip in location U14 Not in rack slot 3 in MACO 4000, 4000,k 6000 systems shipped prior to 4/96. SPC/Network Module (Firmware v01.14 or highter)... Model 80SA (Contact your Barber-Colman Representative or Barber-Colman direct at for price and availability.) 12. Specifications Communications Speed Maximum Connections Maximum speed 19.2kb Minimum polling interval of 55 milliseconds. Thirty-two MACO connections per serial port. Number of Variable Total number of values and setpoints supported per MACO at one time is 600 (10 blocks X 60 points/block). Devices Supported Accessible Point Types Any MACO 4000, 5000, 6000 or 8000 series controller. MACO 4000, 5000, 6000 MACO 8000 Setpoints R/W Setpoints R/W Values R Values R Control Relays R/W Control Relays R ASCII Strings R Selector Switches R/W Genesis is a registered trademarks of Iconics. InTouch and NetDDE are registered trademarks of Wonderware Software Development Corporation. Windows and Excel are registered trademarks of Microsoft Corporation. Page 23 of 28

24 13. Wiring MACO 4000, 5000 and 6000 MACO485 DDE Server Host RS-232 Port 25 pin E F H 25 Pin -vs- 9 Pin Host RS-232 Port 9 pin E F 3 H RS-232/RS-485 Converter A MACO NODE MACO NODE 2 1 DATA (+) 2 DATA (-) 3 ISOCOM 4 SHIELD MACO NODE X RS-485 Host Communication Kit (1 per MACO) MACO 8000 Host RS-232 Port 25 pin E F H 25 Pin -vs- 9 Pin Host RS-232 Port E 9 pin F 2 3 H RS-232/RS-485 Converter A MACO 8000 SPC/Network Module NODE MACO 8000 SPC/Network Module NODE Ω 1/2 W resistor on last node MACO8000 SPC/Network Module NODE X Note: Do not run digital cables together with power cables. Connect shield as shown. On the converter, J2 should be open and the hardware jumpers set to AUTO and 2MS position. Page 24 of 28

25 14. Application Notes MACO485 DDE Server During a block request (such as a recipe transfer), an error will occur if the host makes a control relay request, ASCII string request or an individual setpoint/value request. These functions MUST be disabled during any block requests (depending on the application, this could require a new recipe transfer screen without ASCII strings or control relay requests). The host CANNOT directly read or write to recipe 0 (zero). This problem can be resolved by first transferring recipe 0 to another recipe location and then reading or writing that recipe to or from recipe 0. The host CANNOT access recipes on a cartridge. The host CANNOT access operator station files (*.OBJ files). The host CANNOT access operator station setpoints or values. Momentary pushbuttons sent from the host DO NOT function properly and MUST NOT be used. Page 25 of 28

26 Page 26 of 28

27 Page 27 of 28

28 Barber-Colman Company Industrial Instruments Division 1354 Clifford Avenue Phone: P.O. Box 2940 FAX: (815) Loves Park, IL U.S.A Copyright 1998 Barber-Colman Company. April 1998 Page 28 of 28