KEPServerEX5 Help © 2009 Kepware Technologies
1 KEPServerEX5 Help Table of Contents 1 Getting Started ................................................................................................................................... 6 KEPServerEX .......................................................................................................................................................... 6 Introduction .........................................................................................................................................
Contents 2 Channel Properties ......................................................................................................................................................... - Manual RTS Flow Control 54 Channel Properties ......................................................................................................................................................... - Modem 55 Channel Properties ..............................................................................................
3 KEPServerEX5 Help OPC Settings .......................................................................................................................................................... Options 103 OPC Compliance .......................................................................................................................................................... Options 104 DDE Options......................................................................................................................
Contents 4 Rejecting......................................................................................................................................................... attempt to move referenced object '- ' 137 Runtime......................................................................................................................................................... project replaced from '' 137 Simulation .................................................................
5 KEPServerEX5 Help General Operation .......................................................................................................................................................... System Error Messages 151 General ......................................................................................................................................................... Operation System Error Messages 151 , Error control ..............................................................................
KEPServerEX5 Help 6 CONTENTS Introduction Connectivity Server Administration Tag Management Communications Management Built-In Diagnostics Basic Server Components Designing a Project Server Options Project Preferences Error Descriptions How do I. . . ? Note: For information regarding product licensing, refer to the License Utility help file. To access through the server Configuration menu, click Help | Contents | License Utility.
7 KEPServerEX5 Help in order for the application to operate as designed. This application supports the following Microsoft Windows operating systems. Windows Server 2008* Windows Vista Business/Ultimate* Windows Server 2003 SP2* Windows XP SP2* Windows 2000 SP4 *When installed on a 64 bit operating system, the application will run in a subsystem of Windows called WOW64 (Windows-on-Windows 64 bit).
KEPServerEX5 Help 8 maximum number of supported channels. The information available is as follows. Summary provides the driver name and type, the maximum number of supported channels and the number of models in the driver. COMM Defaults displays the default settings for the driver. The default settings may or may not match the settings of the device or devices being configured.
9 KEPServerEX5 Help OPC client applications in use today still support this original specification, OPC Data Access 2.0 enhanced OPC to better utilize the underlying Microsoft COM technology. Most OPC client applications support version 2.0 of the OPC specification. OPC Data Access 3.0 is the latest version of the OPC DA interface. Dynamic Data Exchange (DDE) The DDE format CF_Text is the standard DDE format as defined by Microsoft. All DDE aware applications support the CF_Text format.
KEPServerEX5 Help 10 When Interactive is selected, the Runtime will remain stopped until a client attempts to connect to it. Once started, it will run until all clients have disconnected and then shutdown. The Runtime will also shutdown if the user account logs off the operation system. Note: The Runtime's process mode may be changed to meet client applications' needs through the Administration settings dialogs.
11 KEPServerEX5 Help Adding and Editing User Accounts The Administrator can create additional user accounts by clicking on the New User icon in the User Properties dialog. Similarly, existing user accounts can be edited by selecting the account and either double-clicking on it or by pressing the Edit User icon. To delete a user account, select it and then press the Delete User icon.
KEPServerEX5 Help 12 desktop. When User Management is enabled, this console requires a valid user login in order to be accessed. Administration The Administration tab is used to configure the Runtime Administration's actions. When Auto Launch is checked, the Administration will start automatically and an icon will appear in the System Tray.
13 KEPServerEX5 Help Connection For security reasons, users cannot just connect to the Runtime. Thus, the Communicate using port parameter allows users to specify a TCP/IP port which the Runtime will open and then listen to for console connections. Session Management Users can manage the connection sessions so that resources aren't being used where they aren't needed. Descriptions of the selections are as follows.
KEPServerEX5 Help 14 Descriptions of the parameters are as follows. Process Mode: This parameter is used to specify whether the server will be running as System Service or Interactive. By default, the server installs and runs as System Service. Changing this setting causes all clients, both Configuration and process, to be disconnected and the server to be stopped and restarted. High Priority: This parameter is used set the server process priority to high. The default setting is normal.
15 KEPServerEX5 Help Descriptions of the parameters are as follows: OPC Connection Security: This parameter allows users to select authentication and also launch and access security requirements through the DCOM Configuration Utility. In addition, users can both specify the level of security to implement and restrict access for certain users and/or applications.
KEPServerEX5 Help 16 are logged into it. Descriptions of the parameters are as follows. Preserve log on disk: This parameter enables the use of a disk-based log file. When enabled, all events in the server will be maintained on disk from one run to the next. If disabled, the server's event logging system will be recorded in memory and no disk log will be generated. When disabled, the event log contents will be emptied each time the server is run.
17 KEPServerEX5 Help Descriptions of the parameters are as follows. Cache Lifetime: This parameter is used to determine how long the server will keep the resolved addresses from host names. The server caches network addresses that it has resolved from host name requests for a period of time to improve performance when the same address is requested repeatedly. The period is 30 to 7200 seconds. The default is 30 seconds.
KEPServerEX5 Help 18 Property Tags Tag Properties are available as additional tags that can be accessed by any Data Access client by appending the property name to any fully qualified tag address. When using an OPC client that supports item browsing, users can browse tag properties by turning on Include tag properties when a client browses the server under OPC Settings. See Also: OPC Settings Options.
19 KEPServerEX5 Help automatically generated. Descriptions of the selections are as follows. Do not generate on startup, the default condition, prevents the driver from adding any OPC tags to the tag space of the server. Always generate on startup causes the driver to evaluate the device for tag information and to add OPC tags to the tag space of the server every time the server is launched.
KEPServerEX5 Help 20 The Add generated tags to the following group was left blank. "MyGroup" was entered in the Add generated tags to the following group field. Allow Automatically Generated Subgroups The Allow automatically generated subgroups setting controls whether or not the server automatically creates subgroups for the automatically generated tags. Checked (default) The server will automatically generate the device's tags and organize them into subgroups.
21 KEPServerEX5 Help The server will automatically generate the device's tags in a simple list without any subgrouping. In the server project, the resulting tags will be named with the address value. For example, the tag names will not be retained during the generation process. The image below shows how the tag names were created using the tag's address.
KEPServerEX5 Help Channel-Level System Tags / Serial Channel-Level System Tags / Ethernet Device-level System Tags / Serial and Ethernet Application-Level System Tags Syntax Example: .._System._ActiveTagCount Tag Description _ActiveTagCount The _ActiveTagCount is a tag that indicates the number of tags that are currently active in the server. Class: Status Tag This is a Read Only tag.
23 KEPServerEX5 Help adapters available for use on this PC. The string returned will contain all of the NIC names and their IP assignments. A semicolon will separate each unique NIC in order to allow the names to be parsed within an OPC application. For a serial driver this tag will only be used if Ethernet Encapsulation is selected. This is a Read Only tag.
KEPServerEX5 Help RTS mode. The _RtsLineRaise is defined as a long value. The valid range is 10 - 2550 milliseconds. The Manual RTS mode has been designed for use with radio modems. This is a Read/Write tag. _RtsLineDrop Class: Parameter Tag The _RtsLineDrop tag is a tag that allows the RTS Line to be lowered for a user-selected period of time after the driver attempts to transmit a message. This tag will only be effective for drivers that support Manual RTS mode.
25 KEPServerEX5 Help Encapsulation is selected. This is a Read Only tag. _NetworkAdapter Class: Parameter Tag The _NetworkAdapter tag is a tag that allows the current NIC adapter in use by the driver to be changed on the fly. As a string tag, the name of the newly desired NIC adapter must be written to this tag in string format. The string written must match the exact description of the desired NIC in order for the change to take effect.
KEPServerEX5 Help applies to all drivers equally. This is a Read/Write tag. _InterRequestDelay The _InterRequestDelay is a tag that allows the time interval between device transactions to be changed on the fly. The _InterRequestDelay is defined as a Long data type. The valid range is 0 to 30000 milliseconds. This parameter tag only applies to drivers that support this feature. _EncapsulationIp The _EncapsulationIp tag allows the IP of a remote terminal server to be specified and changed on the fly.
27 KEPServerEX5 Help request timeouts and retries without a response. See Also: Device Properties - Timing. This is a Read Only tag. _Simulated Class: Status Tag The _Simulated tag is a Boolean tag that provides feedback about the simulation state of the current device. When Read as TRUE, this device is in a simulation mode. While in simulation mode, the server will return good data for this device but will not attempt to communicate with the actual physical device.
KEPServerEX5 Help 28 The _System branch found under the DeviceName branch is always available. If referencing a system tag from a DDE application given the above example and the DDE defaults, the link would appear as follows: = |_ddedata!Channel1.Device1._System._Error The _Enabled tag provides a very flexible means of controlling the OPC applications.
29 KEPServerEX5 Help _Address The _Address property tag indicates the current address for the tag it is referencing. _Description The _Description property tag indicates the current description for the tag it is referencing. _RawDataType The _RawDataType property tag indicates the raw data type for the tag it is referencing. _ScalingType The _ScalingType property tag indicates the scaling type (None, Linear or Square Root) for the tag it is referencing.
KEPServerEX5 Help 30 configured timeout and retry count for the device. This tag is formatted as an unsigned 32 bit integer and will eventually rollover. This tag is Read Only. _FailedWrites The _FailedWrites tag contains a count of the number of Writes this channel has failed to complete since the start of the application or since the last time the _Reset tag was invoked.
31 KEPServerEX5 Help The _Statistics branch found under the Channel branch will only appear when diagnostics are enabled for the channel. In order to reference a Diagnostics Tag from a DDE application given the above example and the DDE defaults, the link would appear as follows: = |_ddedata!Channel1._Statistics._SuccessfulReads The values of the Diagnostics Tag can also be viewed directly in the server by using the Channel Diagnostics window.
KEPServerEX5 Help Attempting to issue a dial command while the Mode tag is set to 2 (incoming call only) will generate an error. _DialNumber The DialNumber tag shows the phone number that is actually dialed, after any dialing preference translations have been applied (such as the addition of an area code). This tag is intended for debugging purposes. It can provide useful feedback to an operator if phone numbers are entered manually.
33 KEPServerEX5 Help Canonical format is the following: +[space]()[space] example: +1 (207) 846-5881 Note: The country code for the U.S. is 1. If the number is not in canonical form, dialing preferences will not be applied. The number will be dialed exactly as it is entered. Users can also enter a Phonebook tag name instead of a phone number. In this case, the current value of the phonebook tag will be used.
KEPServerEX5 Help 11 Calling 19 Answering 34 Last Event Values LastEvent Reason for Change -1 [no events have occurred yet] 0 Initialized with TAPI 1 Line closed 2 Line opened 3 Line connected 4 Line dropped by user 5 Line dropped at remote site 6 No answer 7 Line busy 8 No dial tone 9 Incoming call detected 10 User dialed 11 Invalid phone number 12 Hardware error on line caused line close Last Event String Values LastEvent StringLastEvent -1 [no events
35 KEPServerEX5 Help assigned IP address. The list of available NICs will include both unique NIC cards and NICs that have multiple IPs assigned to them. The selection will also display any WAN connections that may be active (such as a dialup connection). Ethernet Encapsulation The Ethernet Encapsulation mode has been designed to provide communications with serial devices connected to terminal servers on the Ethernet network.
KEPServerEX5 Help 36 Configuring the Initiating Modem This server uses the Windows TAPI interface to access modems attached to the PC. The TAPI interface was designed to provide Windows programs a common interface that could be accessed by a range of modems existing in a PC. A set of drivers for the Windows OS, which are provided by the modem's manufacturer, must be installed before the server can use the modem in a project. The Windows Control Panel can be used to install new modems.
37 KEPServerEX5 Help 1. Load the direct connect project and then double-click on the Channel Name. This will invoke the current direct connect settings for Baud Rate, Parity and etc. 2. Select the Use Modem checkbox. The settings on this page should now become unavailable. 3. Next, click on the Modem tab to display the list of modems available on the computer.
KEPServerEX5 Help 38 To add a new phonebook tag, simply click on the New Phonebook icon to display the Phone Number dialog. Example A phonebook tag name was created for 'Site1.' Syntax Example: .._Phonebook.Site1 Tag Name Description Access Instead of specifying a telephone number by directly writing to the PhoneNumber tag, a phonebook tag can be used.
39 KEPServerEX5 Help good idea, some OPC client applications may have a limited display window when browsing the tag space of an OPC server. The phonebook tag name is part of the OPC browse data. Phonebook tag names must be unique within a given device. The Number parameter is used to enter the phone number that will be dialed when the tag is invoked from an OPC client application. A string of up to 64 digits can be entered. The Description parameter is used to attach a comment to this tag.
KEPServerEX5 Help 40 OPC Diagnostic Features The Find Dialog can be used to search for specific text within the diagnostics view. This aids in the debugging of a particular issue by allowing users to search for key information transferred between the client and server. For example, all actions on a particular Item ID or group name can easily be found using the search functionality.
41 KEPServerEX5 Help Each method (such as, GetErrorString) of every OPC Data Access 1.0, 2.0 and 3.0 interface (such as, IOPCCommon) supported by the server is available as a filter. Users can select a method by clicking the checkbox to the left of the method name. Additionally, users can select all methods of an interface by double-clicking the interface name. By default, all methods for all interfaces are selected. Note: Filter changes apply only to new events captured.
KEPServerEX5 Help 42 Since diagnostic information affects memory/file storage, users can decide the maximum number of OPC diagnostic events that should be captured at any specific time by modifying the Maximum number of diagnostics to capture. This value only pertains to the number of events and does not include the number of details, as the detail count for a particular event could be potentially very high. The range for this setting is 1000 to 30000. The default value is 5000.
43 KEPServerEX5 Help ability to set and query a Locale ID which would be in effect for the particular client/server session. That is, the actions of one client do not affect other clients. GetErrorString - Returns the error string for a server specific error code. The expected behavior is that this will include handling of Win32 errors as well (such as RPC errors). GetLocale ID - Returns the default Locale ID for this server/client session.
KEPServerEX5 Help 44 node (e.g. the units in a cell). QueryOrganization - Provides a way to determine if the underlying system is inherently flat or hierarchical and how the server may represent the information of the address space to the client. Flat and hierarchical spaces behave somewhat different. If the result is flat then the client knows that there is no need to pass the Branch or Leaf flags to BrowseOPCItem IDs or to call ChangeBrowsePosition.
45 KEPServerEX5 Help can be obtained from Read cache for those items and whether or not they are included in the IAdvise subscription to the group. Deactivating items will not result in a callback, since by definition callbacks do not occur for inactive items. Activating items will generally result in an IAdvise callback at the next UpdateRate period. SetClientHandles - Changes the client handle for one or more items in a group.
KEPServerEX5 Help 46 'queued' and the function will return immediately so that the client can continue to run. Each operation is treated as a 'transaction' and is associated with a Transaction ID. As the operations are completed, a callback will be made to the IAdvise Sink in the client (if one has been established). The information in the callback will indicate the Transaction ID and the error results. By convention, 0 is an invalid Transaction ID.
47 KEPServerEX5 Help IDataObject connections as in the past. EnumConnectionPoints - Creates an enumerator for the Connection Points supported between the OPC Group and the Client. FindConnectionPoint - Finds a particular connection point between the OPC Group and the Client. IconnectionPoint (Group) - Establishes a call back to the client. Advise - Establishes an advisory connection between the connection point and the caller's sink object.
KEPServerEX5 Help 48 Note: The Diagnostic Window operates in a modeless form that allows it to exist while other dialogs in the server are open. Diagnostic Controls Descriptions of the Diagnostics Controls are as follows. Pause captures and freezes the protocol data in the Diagnostics Window. The Diagnostics Tags will continue to be updated. Reset clears only the contents of the protocol view and does not affect the Diagnostics Tags.
49 KEPServerEX5 Help effect in the protocol view. Remember to display the diagnostic window before accessing any parameter dialogs. Once the diagnostic window is displayed, various communication and device settings in the channel and device can be modified to see the effect on the communications stream. If a communications problem persists, right-click in the diagnostic window to invoke the context menu.
KEPServerEX5 Help 50 keep in mind that it can affect the speed of update if the size is set to large. Larger font sizes also prevent users from being able to see a usable amount of the protocol. Basic Server Components For more information on a specific server component, select a link from the list below.
51 KEPServerEX5 Help identical communication parameters; for example, two serial drivers cannot use COM1. For the correct communication parameters of a particular device, refer to both the manufacturer's and the driver's help documentation. Note: Flow Control settings for serial drivers are primarily used when connecting RS422/485 network devices to the RS232 serial port via a converter.
KEPServerEX5 Help 52 Note: With the server's online full-time operation, these parameters can be changed at any time. This includes changing the channel name in order to prevent clients from registering data with the server. If a client has already acquired an item from the server before the channel name is changed, the items will be unaffected.
53 KEPServerEX5 Help Report Comm. Errors turns the reporting of low level communications errors On or Off. When enabled, lowlevel errors (such as parity, framing and overrun errors) are posted to the event log when they occur. When disabled, these same errors will not be posted even though normal request failures will be. Use Ethernet Encapsulation: Many serial drivers also support Ethernet Encapsulation mode, which uses an Ethernet based serial port gateway instead of the normal PC based serial port.
KEPServerEX5 Help 54 By selecting a specific NIC interface, users will be able to force the driver to send all Ethernet communication through the specified NIC. When a NIC is selected, the normal operating system bind order is completely bypassed. This ensures that users have control over how the network operates and thus eliminates any guesswork.
55 KEPServerEX5 Help For those drivers that support it, the RTS Manual selection enables the setting of three timing parameters. These settings will only appear if the driver in use supports RTS Manual. Raise the RTS line controls how long the RTS line will be high before any data is transmitted from the communications port. The time entered is in milliseconds and has a valid range of 0 to 2550 milliseconds. The default is 10 milliseconds.
KEPServerEX5 Help 56 Note: With the server's online full-time operation, these parameters can be changed at any time. Utilize the User Manager to restrict access rights to server features and prevent operators from changing parameters. Channel Properties - Write Optimizations As with any OPC server, writing data to the device may be the application's most important aspect. The server's objective is to ensure that the data written from the OPC client application gets to the device in a timely fashion.
57 KEPServerEX5 Help 1. Write all values for all tags 'Write all values for all tags' forces the server to attempt to Write every value to the controller. In this mode, the server continues to gather OPC Write requests and add them to the server's internal Write queue. Then, the server processes the Write queue and attempts to empty it by writing data to the device as quickly as possible. This mode ensures that everything written from the OPC client applications will be sent to the target device.
KEPServerEX5 Help 58 enhancements before they are used in a production environment. Channel Properties - Ethernet Encapsulation Ethernet Encapsulation mode has been designed to provide communication with serial devices connected to terminal servers on the Ethernet network. A terminal server is essentially a virtual serial port. The terminal server converts TCP/ IP messages on the Ethernet network to serial data.
59 KEPServerEX5 Help The Network Adapter parameter's drop-down list is used to select the network adapter. The IP Address parameter is used to enter the four-field IP address of the terminal server to which this device is attached. IPs are specified as YYY.YYY.YYY.YYY The YYY designates the IP address: each YYY byte should be in the range of 0 to 255. Each channel will have its own IP address.
KEPServerEX5 Help 60 Adding a Device Devices can be added using the New Device Wizard both at the initial setup and afterwards. To do so, click Edit | New Device. Users will be prompted to enter the Device Name, which is user-defined and should be logical for the device. This will be the browser branch name used in OPC links to access the device's assigned tags. Users will also be prompted to enter a Network ID, which is a number or string that uniquely identifies the device on the device's network.
61 KEPServerEX5 Help Figure 2 - Ethernet Device Properties Device Names Device Names, which are logical user-defined names for the device, can be up to 256 characters long. The same names can be used on multiple channels. While long descriptive names are generally a good idea, some OPC client applications may have a limited display window when browsing the tag space of an OPC server. The device name and channel name will become part of the browse tree information as well.
KEPServerEX5 Help 62 parameter can be used to disable a physical device for servicing. After a device has been disabled, no communications will be attempted. From a client standpoint, the data will be marked as invalid and Write operations will not be accepted. This parameter can be changed at any time either through the menu selection or by accessing the device's System Tags. Simulate Device This parameter is used to place the device into a simulation mode.
63 KEPServerEX5 Help Device-level Ethernet Encapsulation Settings Descriptions of the parameters are as follows. IP Address: This parameter is used to enter the four-field IP address of the terminal server to which the device is attached. IPs are specified as YYY.YYY.YYY.YYY The YYY designates the IP address: each YYY byte should be in the range of 0 to 255.
KEPServerEX5 Help 64 Connection Timeout This parameter, used primarily by Ethernet based drivers, controls the amount of time required to establish a socket connection to a remote device. The device's connection time often takes longer than normal communications requests to that same device. The valid range is 1 to 30 seconds. The default is typically 3 seconds, but can vary depending on the driver's specific nature. If this setting is not supported by the driver, it will be disabled.
65 KEPServerEX5 Help will override the normal polling frequency of tags associated with the device, as well as one-shot Reads and writes. This delay can be useful when dealing with devices with slow turnaround times and in cases where network load is a concern. Configuring a delay for a device will, however, affect communications with all other devices on the channel. Thus, it is recommended that users segregate any device that requires an inter-request delay to a separate channel if possible.
KEPServerEX5 Help 66 be attempted during the off-scan period. The default setting always sends write requests regardless of the demotion period. If users choose to discard writes, the server will automatically fail any write request received from a client and will not post an "Unable to write..." message to the server event log. Note: Users can determine when a device is off-scan by monitoring its demoted state by using the _AutoDemoted System Tag.
67 KEPServerEX5 Help driver being used. To determine how an address should be entered, use the Hints button next to the Address Parameter. The address entered can be up to 128 characters in length. Once an address has been entered, it can be tested by using the Check Address button, which will then attempt to validate the address with the driver. If the driver accepts the address as entered, no message will be displayed. A popup will inform of any error.
KEPServerEX5 Help 68 connect, the server will create a virtual tag for that location and will start scanning for data automatically. To specify an optional data type, append one of the following strings after the '@' symbol: Byte Char Short Word Long DWord Float Double BCD LBCD String If the data type is omitted, the driver will choose a default data type based on the device and address that is being references.
69 KEPServerEX5 Help Note: User-defined tags support scaling. Tag Scaling This server supports Tag Scaling, which allows raw data from the device to be scaled to an appropriate range for the application. To enable Tag Scaling, select either Linear or Square Root. Scaling cannot be enabled if None is checked. The formula for both Tag Scaling types are shown in the table below.
KEPServerEX5 Help 70 data. When this occurs, the scaled value is also forced outside of the established range. To prevent this from occurring, the High and Low Clamps can be used to constrain the scaled value to the range specified. Units The server also allows a unit's string to be assigned to a scaled tag. The units' string can be up to 32 characters long. Negate scaled value This parameter forces the resulting value to be negated before being passed to the client.
71 KEPServerEX5 Help To add a new tag group to the project, right-click on either an existing device or tag group branch and select New Tag Group from the context menu. Alternatively, click on either an existing device or tag group branch and then click the New Tag Group icon on the toolbar. When adding a new tag group to the project, users will be presented with the following dialog. www.kepware.
KEPServerEX5 Help 72 Tag groups can be added at any level from the device-level down, and multiple tag groups can be nested together to fit the application's needs. As seen in the OPC Quick Client dialog above, the fully qualified OPC item path is "Channel1. Device1.Machine1.Cell1.Tag1". For this OPC item, "Machine1" and "Cell1" segments are nested tag groups. Note: With the server's online full-time operation, these parameters can be changed at any time.
73 KEPServerEX5 Help To delete manually created aliases, click . To import an alias map as a .CSV file, click . To export an alias map as a .CSV file, click . Note: Check or uncheck the Show aliases for system generated groups check box in order to show or hide the server created aliases. See Also: How to Create and Use an Alias Alias Properties The Alias Map allows a way to assign simple alias names to complex tag references that can be used in client applications.
KEPServerEX5 Help 74 Topic update rate found in many DDE only servers. The valid range is 0 to 99999990 milliseconds. The default is 0 milliseconds. When set to 0 milliseconds the server will observe the DDE scan rate set at the individual tag level using the Tag Properties dialog. Once the desired path has been selected and the DDE scan rate has been set, click OK to complete the alias. To enter more alias map elements, return to the Alias Map dialog.
75 KEPServerEX5 Help Note: Now that the server is running, a project may be created. Starting a New Project This server must be configured to determine what content it will provide while operating. For a server project, the content that is determined will define channels, devices, optional tag groups and tags. These factors exist in the context of a project file. As with many applications, users can define a number of project files and save and load them as needed.
KEPServerEX5 Help 76 New Channel by Edit | Add Channel New Channel by Context Menu 2. For simplicity, leave the channel name "Channel1." 3. Select the communications driver that will be applied to this channel. For this example, choose the Simulator driver from the driver selection drop-down menu. Note: For this driver, the Next dialog is the Channel Summary.
77 KEPServerEX5 Help Important: A a small red "x" should be visible below the channel icon. This denotes that the channel does not contain a valid configuration because no devices have been added yet. Note: This server supports the use of multiple channels. As channels are added to the project, users can specify either the same communications driver or different communications drivers.
KEPServerEX5 Help 78 New Device by Context Menu 2. For simplicity, leave the device name "Device1." Note: The number of dialog pages in the Device Wizard depends on the driver being used in the application. 3. Click Next to proceed to the next dialog. Then, select either a 16 bit or 8 bit register size for the device being simulated. In other device drivers, users would select a device model. For this example, however, choose the 16 bit device size. 4.
79 KEPServerEX5 Help 5. To complete the addition of the device, click Next | Finish. Note: The server is now ready to start providing data to OPC clients. With the server's online full-time mode of operation, the server can start providing OPC data immediately. At this point, however, the configuration can potentially be lost since the project has not yet been saved. Before saving, users can add tags to the server. See Also: Adding User-Defined Tags.
KEPServerEX5 Help 80 Add Tag by Edit | New Tag Add Tag by Context Menu 3. Edit the controls to match the following content (as shown in the Tag dialog image). Tag Name: MyFirstTag Address: R000 Description (Optional): My First Simulator Tag Data Type: Word Client Access: Read/Write Scan Rate: 100 milliseconds* *This does not apply for OPC tags. Note: The Address, Data Type and Client Access fields depend on the communications driver being used.
81 KEPServerEX5 Help For additional information, click the Help button in the Hints dialog. This invokes the driver specific help documentation at the page that covers data addressing for the device currently selected. 4. Commit the tag to the server by pressing Apply in Tag Properties. The tag should now be visible in the Tag View area of the server. If only one tag needed to be added, users would be finished at this point. For this example, however, a second tag needs to be added for use in Tag Scaling.
KEPServerEX5 Help 82 Adding Tag Scaling When defining a new tag in the server, users have the option of applying tag scaling, which allows raw data from the device to be scaled to an appropriate range for the application. There are two types of scaling: Linear and Square Root. For more information, refer to Tag Scaling. Note: The image below uses the second tag previously developed in this example. The Tag Properties dialog should appear as shown below. 1.
83 KEPServerEX5 Help 2. In this example, Linear Scaling has been selected. The raw value range allows users to specify what they expect to receive as a data range from the actual device. The scaled data type also allows users to specify how the resulting scaled value is presented to the OPC client application. The scaled value range is used to specify the desired range in engineering units for the resulting value.
KEPServerEX5 Help 84 clicking File | Save. Users can overwrite the existing project or save the edits as a new project. They are also given the option of loading the new project as the default Runtime project. When editing projects offline, users have the option to save to the same project or to save as a new project. Once completed, users can click Runtime | Connect and then load the new project as the default Runtime project.
85 KEPServerEX5 Help Establishing a Connection 3. Next, establish a connection by clicking Edit | New Server Connection. Alternatively, right-click and select New Server Connection from the Context Menu or click the New Server icon on the toolbar. Selecting New Server Connection by all of these methods will invoke the OPC Server Selection dialog, which is used to make connections with an OPC Server either locally or remotely via DCOM. Connect to Server by Edit | New Server Connection www.kepware.
KEPServerEX5 Help 86 Connect to Server by the Context Menu Note 1: By default, the Server Selection dialog is configured with the Prog ID of the server. The name listed in the server connection dialog is called the Prog ID of the server. OPC clients use this name to reference a specific OPC server. The server connection dialog should appear as shown below. Note 2: Once a connection is made, two things may happen. If the server is running, the OPC Quick Client will simply make a connection to the server.
87 KEPServerEX5 Help Adding a Group by Toolbar Icon Adding a Group by Context Menu 5. For the purposes of this example, edit the Group Properties parameters so that they match the following image. Note: The Update Rate, Percent Dead Band and Active State parameters control when and if data will be returned for the group's tags. The Update Rate determines how often data will be scanned from the actual device. It determines how often data will be returned to the OPC client as a result of that scan.
KEPServerEX5 Help 88 to eliminate or reduce noise content in the data by only detecting changes when they exceed the percentage change that has been requested. The percent change is a factor of the data type of a given tag. The Active State is used to turn all of the tags in this group either on or off. The Group Name is used for reference from the client and can actually be left blank. 6. Press OK to commit the group when finished. Accessing Tags 7.
89 KEPServerEX5 Help Client should appear as shown below. The first tag, "MyFirstTag," should contain a changing value. The second tag should be zero at this point. If users only needed to test the reading of an OPC item, they are now finished. If, however, users desired to change an OPC item, they can use one of the write methods to send new data to the OPC item.
KEPServerEX5 Help 90 . If no new data has been entered, clicking OK will not send data to the server. Conclusion At this point, all of the basic steps involved in building and testing an OPC project have been discussed. Users are encouraged to continue to test various features of both the server and the OPC Quick Client for greater understanding and comprehension. For more information on the OPC Quick Client, refer to its help documentation.
91 KEPServerEX5 Help Since the server supports the use of simultaneous multiple communications drivers, users can add a number of channels to the project. It is not necessary to select a different communications driver for each channel. Many of the communications drivers available for the server support operation on either multiple communications ports or across multiple network connections.
KEPServerEX5 Help 92 For Serial based drivers, the Communications dialog is used to set the Serial Port, Baud rate, Data bits, Parity, Stop bits and RTS/DTR Flow Control. Note: The dialog's additional options allow users to select and use dial-up Modem support or Ethernet Encapsulation for connecting to devices via Serial to Ethernet terminal servers. For more information, refer to Using a Modem in the Server Project and Device Properties - Ethernet Encapsulation.
93 KEPServerEX5 Help New Device - Name A Device Name can be the same from one channel to the next; however, each device under a channel must have a unique name. The Device Name is a user-defined logical name for the device that can be up to 256 characters long. While long descriptive names are generally good, some OPC client applications may have a limited display window when browsing the tag space of an OPC server. Note: The device name and channel name are part of the browse tree information. www.
KEPServerEX5 Help 94 Note: Within an OPC client, the combination of channel name and device name would appear as ChannelName. DeviceName. New Device - Model The Model parameter is used to select the device model associated with the Device ID. The Model selection drop-down menu's contents will vary depending on the chosen communication driver. If a driver does not support model selection, this option will be unavailable.
95 KEPServerEX5 Help Note: With the server's online full-time operation, these parameters can be changes at any time. If the communications driver supports multiple device models, the model selection can only be changed if there are currently no client applications connected to the device. Since the device is being added at this time, any model can be selected. Utilize the User Manager to restrict access rights to server features and prevent operators from changing parameters.
KEPServerEX5 Help 96 If the communications driver is either Ethernet-based or supports an unconventional station or node name, the dialog shown below may be displayed. In this case, the Device ID is a TCP/IP ID. TCP/IP or UDP IDs consist of four values separated by periods. Each value has a range of 0 to 255. Some Device IDs are string based. Note: Depending on the communications driver being used, there may be more parameters that need to be defined in the New Device - ID dialog.
97 KEPServerEX5 Help Note: With the server's online full-time operation, these parameters can be changed at any time. Any changes made to the Device ID will take effect immediately. Utilize the User Manager to restrict access rights to server features and prevent operators from changing parameters. New Device - Timing Device Timing parameters allow a driver's response to error conditions to be tailored to the application's needs.
KEPServerEX5 Help 98 Server Options General Options The server's online full-time mode of operation places some special requirements on the server as well as the operator. Most parameters can be changed in the server at any time. This, although helpful, can cause many problems for OPC applications. To prevent an operator from making a change that might disrupt the server's ability to provide data to client applications, the server has warning pop-ups.
99 KEPServerEX5 Help Descriptions of the General Options dialog parameters are as follows. Immediately attempt to establish a Runtime connection on start: This parameter is used to specify whether the configuration tool will connect to the Runtime when started. It is checked by default. If it is unchecked, users must manually connect.
KEPServerEX5 Help 100 invoked by a client application. If the server were to shut down without warning, those changes could be lost. To prevent this from occurring, the server has provided exit options. The exit options allow the exit strategy of the server to be tailored to the application. See Also: OPC Settings Options. There are four exit strategies. 1. Ask to save (with timeout) presents a save project dialog to the operator. The operator, if present, can decide whether or not to save the changes.
101 KEPServerEX5 Help Event Log Display The Event Filter helps users tailor the Event Log's contents to meet the application's reporting requirements. There are currently three types of messages that can be recorded in the event log: General Messages, Warnings and Errors. General messages include server startup and shutdown messages; Warnings include messages such as device not responding; Errors include messages such as the rejection of bad OPC item request.
KEPServerEX5 Help 102 Descriptions of the parameters are as follows. The Margin parameter sets the distance from the edge of the Event Log printed page to the top, bottom, left and right. All margin settings are entered in inches. The Fonts parameter selects a font to be used as the header and footer text, as well as for the actual Event Log records. Only fixed space fonts will appear in the Fonts dialog. To change a font, simply click on the change button.
103 KEPServerEX5 Help being reimported). Note: A new configuration file will be created in the same folder as the server project file, containing the name _FIX.ini. 3. Depending on how long it takes to read an initial value for all the items in the project, it may be necessary to delay the start of SAC processing to allow the server enough time to retrieve all initial updates before the iFIX client requests data from the server.
KEPServerEX5 Help 104 Descriptions of the parameters are as follows. When enabled, Enable OPC 1.0 allows the server to accept OPC client connections from OPC clients that support the 1.0 specification. The 1.0 operation is enabled by default. When enabled, Enable OPC 2.0 allows the server to accept OPC client connections from OPC clients that support the 2.0 specification. The 2.0 operation is enabled by default. When enabled, Enable OPC 3.
105 KEPServerEX5 Help meet the needs of rare OPC clients. Normally these options will not need to be adjusted for a majority of the OPC client applications users will encounter. The OPC compliancy dialog appears as shown below. Descriptions of the parameters are as follows. Perform the following operations is the master enabling switch for the options present in the list box. When enabled, the server will set all options to conform to OPC compliancy. This setting is not enabled by default.
KEPServerEX5 Help 106 1,200 would be converted to One Thousand - Twelve Hundred if converted using English metrics, but would be One and Two-Tenths if converted using German metrics. Thus, if German software is running on an English OS, users need to determine how the comma will be handled. This setting allows for such flexibility. By default, and due to historical implementation, the server respects the Locale ID of the operating system.
107 KEPServerEX5 Help DDE, enabling it will cause the server to automatically register its share names and start the Net DDE service manager. DDE shares will be removed when the server shuts down. See Also: How To.. Use Net DDE. Service Name This parameter allows users to change how the server appears as an application name to DDE clients. This name will initially be set to allow compatibility with the previous versions of the server.
KEPServerEX5 Help 108 Note: In order for both proper FastDDE/SuiteLink operation and for this page to be displayed in the server's File | Project Properties menu, the Wonderware FS2000 Common Components (or the InTouch Runtime Component version 8.0 or higher) must be installed on the PC. General Enable FastDDE/SuiteLink This parameter allows users to enable or disable support of the Client/Server protocols. When a Wonderware product is installed on the PC, this setting will be enabled by default.
109 KEPServerEX5 Help iFIX process database (PDB) tags and the server tags. To access this tab, click File | Project Properties. Note: The iFIX PDB Settings dialog will only be displayed in Project Properties if iFIX is installed on the computer. Note: It is recommended that users keep the default values for each field. Users should also ensure that the settings meet the application's requirements. General Enable connectivity to iFix PDB.
KEPServerEX5 Help 110 idle tags on a 15 second cycle, a tag may not get set inactive at precisely this time from its last Read; it could be up to 15 seconds longer depending on when the last read occurred in the check cycle. If iFIX requests data from a tag that has been previously deactivated, the server will reactivate the tag and resume polling the hardware. This feature is disabled by default upon driver install. Once this feature is enabled, however, it becomes applied to all projects.
111 KEPServerEX5 Help examined for a value greater than 9 (A-F hex). If a hexadecimal value between A and F is found, a range alarm is generated, indicating the value is not within BCD range. Otherwise, the value is scaled with the following algorithm: Result=((Raw_value/999) * Span_egu) + Lo_egu. Read Algorithm Variables Lo_egu - the database block's low engineering value. Span_egu - the span of the engineering values. Raw_value - the value stored in the field device's register.
KEPServerEX5 Help alarm state, or OK. Result=(((InputData - Lo_egu)/Span_egu) * 255) + .5. Write Algorithm Variables Lo_egu - the low engineering value. Span_egu - the span of the engineering values. InputData - the database block's current value. Result - the value sent to the process hardware. 8BN Signal Conditioning Description 8-bit binary number. Input Range 0 - 255. Scaling Scales 8-bit binary values to the database block's EGU range. Ignores the most significant byte.
113 KEPServerEX5 Help most significant bits are ignored. Read Algorithm Reads from a 16-bit register using the following algorithm: Result =((Raw_value/4095) * Span_egu) + Lo_egu. Read Algorithm Variables Lo_egu - the database block's low engineering value. Span_egu - the span of the engineering values. Raw_value - the value stored in the field device's register. Result - the scaled value stored in the database block.
KEPServerEX5 Help 14AL Signal Conditioning Description 14-bit binary number. Input Range 0 - 16383. Scaling Scales 14-bit binary values to the database block's EGU range. Read Algorithm Reads from a 16-bit register using the same algorithm as 14BN, and returns a status indicating whether the value is out of range and in an alarm state, or OK. Result=((Raw_value/16383) * Span_egu) + Lo_egu. Read Algorithm Variables Lo_egu - the database block's low engineering value.
115 KEPServerEX5 Help Write Algorithm Writes to a 16-bit register with alarming using the same algorithm as 15BN, and returns a status indicating whether the value is out of range and in an alarm state, or OK. Result=(((InputData - Lo_egu)/Span_egu) * 32767) + .5. Write Algorithm Variables Lo_egu - the low engineering value. Span_egu - the span of the engineering values. InputData - the database block's current value. Result - the value sent to the process hardware.
KEPServerEX5 Help 116 Result =((Raw_value/32000) * Span_egu) + Lo_egu. Read Algorithm Variables Lo_egu - the database block's low engineering value. Span_egu - the span of the engineering values. Raw_value - the value stored in the field device's register. Result - the scaled value stored in the database block. Write Algorithm Writes to a 16-bit register using the following algorithm: Result =(((InputData - Lo_egu)/Span_egu) * 32000) + .5. Write Algorithm Variables Lo_egu - the low engineering value.
117 KEPServerEX5 Help What is the Alias Map? Note 1: For possible additional syntax, refer to the DDE client's specific help documentation. Note 2: For information on how to connect to remote applications using DDE, refer to Using Net DDE Across a Network. How To... Use Net DDE Across a Network DDE provides a way to share data between Windows applications as long as they exist on the same machine.
KEPServerEX5 Help 118 an array of data values, the text string written should have this delimiter format. When poking to an array tag in either format, the entire array does not need to be written, but the starting location is fixed. If attempting to poke data in an array format to a tag that was not declared as an array, only the first value in the array will be written. If attempting to poke more data than the tag's array size, only as much data as the tag's array size will be written.
119 KEPServerEX5 Help 2. Click on the New Alias icon, which appears as . 3. In the tree browse where the tag that will be referenced is located, select the desired device name or group name. The fully qualified path for the tag item will be shown in the grayed Mapped to.. field. 4. Next, enter an alias name that will represent this complex tag reference. It is this alias name that now can be used in the client application to address the tag found in the server (instead of the path).
KEPServerEX5 Help 120 = |Mac1Cell2!ToolDepth Note 1: If Net DDE is enabled, the Alias Map entries will be registered as DDE shares for use by remote applications. The names given to each Alias Map entry must not conflict with any existing DDE shares already defined on the server PC. See Also: How to Use Net DDE Across a Network . Note 2: If the error message "DDE client attempt to add a topic (?) failed.
121 KEPServerEX5 Help Note: The server will validate any request for items against the Alias Map before responding back to the client application with an error that the item does not exist. How To... Optimize the Server Project Nearly every driver of this server supports at least 100 channels; meaning, 100 COM/Serial Ports or 100 source sockets for Ethernet communications. To determine the number of supported channels available for each device, refer to the Driver Information under Server Summary.
KEPServerEX5 Help 122 Each device has now been defined under its own channel. In this new configuration, a single path of execution is dedicated to the task of gathering data from each device. If the application has fewer devices, it can be optimized exactly how it is shown here. The performance will improve even if the application has more devices than channels. While 1 device per channel is ideal, the application will still benefit from additional channels.
123 KEPServerEX5 Help How To... Use Ethernet Encapsulation The Ethernet Encapsulation mode has been designed to provide communications with serial devices connected to terminal servers on the Ethernet network. A terminal server is essentially a virtual serial port that converts TCP/IP messages on the Ethernet network to serial data. Once the message has been converted to a serial form, users can connect standard devices that support serial communications to the terminal server.
KEPServerEX5 Help 124 Note: For unsolicited drivers that support Ethernet encapsulation, users will have to configure the port and the protocol settings at the channel-level. This will allow the driver to bind to the specified port and process incoming requests from multiple devices. An IP address is not entered at the channel since the channel will accept incoming requests from all devices. Ethernet Encapsulation can be used over wireless network connections such as 802.
125 KEPServerEX5 Help Ethernet operation. When a new device is added to the channel, the Ethernet Encapsulation settings can be used to select an Ethernet IP address, an Ethernet Port number and the Ethernet protocol. How To... Resolve Comm Issues When the DNS/DHCP Device Connected to the Server is Power Cycled Certain drivers support DNS/DHCP resolution for connectivity. These devices also allow users to assign unique Domain/ Network names for identification purposes.
KEPServerEX5 Help Module '' is unsigned or has a corrupt signature Move object '' to '' failed No device driver DLLs were loaded Rejecting attempt to delete referenced object '- ' Rejecting attempt to move referenced object '
- ' Runtime project replaced from '' Simulation mode is '' on device '' Starting '' device driver Starting '' plug-in Stopping '' device driver Stopping '
127 KEPServerEX5 Help Unable to load driver DLL '' Unable to load the '' driver because more than one copy exists ('' and '' Unable to use network adapter '' on channel ''.
KEPServerEX5 Help 128 Attempt to add OPC client item '- ' failed Attempting to automatically generate tags for device '' Auto generation for tag '' already exists and will not be overwritten Auto generation produced too many overwrites, stopped posting error messages Completed automatic tag generation for device '' Configuration session assigned to '' as Default User has ended Configuration session assigned to '' demoted to Read Only Confi
129 KEPServerEX5 Help Note: Every attempt is made to ensure backwards compatibility in the server so that projects created in older versions may be loaded in newer versions. However, since new versions of the server and driver may have properties and configurations that do not exist in older version, users may not be able to open or load a project created in a newer version of the server in an older version.
KEPServerEX5 Help 130 adding the item from the client. 4. If attempting to add an item but used incorrect syntax: Correct the syntax and try again. Attempt to add FastDDE/SuiteLink item '' failed Error Type: Error Source: Runtime Possible Cause: 1. The user attempted to add an item from a FastDDE/Suitelink client that was not a static tag in the server. 2. The user attempted to add an item from a FastDDE/Suitelink client that had incorrect syntax. Solution: 1.
131 KEPServerEX5 Help Source: Runtime Possible Cause: Although the server is regenerating tags for the tag database, it has been set not to overwrite tags that already exist. Solution: If this is not the desired action, change the setting in the Database Creation Properties dialog.
KEPServerEX5 Help 132 Source: Runtime Possible Cause: The connected user has been idle for more than 15 minutes, and so the server automatically demoted them. Solution: When connected with the Configuration, do not leave the connection idle if in write access mode. Configuration session assigned to '' promoted to Write Access Error Type: Information Source: Runtime Possible Cause: A user that was connected to the Runtime with Write Access has disconnected or demoted due to being idle.
133 KEPServerEX5 Help Information Source: Runtime Possible Cause: 1. A client application has programmatically Enabled/Disabled Data Collection for the specified device. 2. The user's Configuration has Enabled/Disabled Data Collection for the specified device. Solution: N/A. DDE client attempt to add topic '' failed Error Type: Error Source: Runtime Possible Cause: An attempt was made by a DDE client to add or reference a topic that does not exist. Solution: 1.
KEPServerEX5 Help 134 Demo timer updated. '
135 KEPServerEX5 Help Device '' has been auto-demoted Error Type: Warning Source: Runtime Possible Cause: Communications with the specified device have failed. The device has been demoted from the poll cycle. Solution: 1. If the device fails to reconnect, investigate the reasons behind the communications loss and then correct it. 2. To stop the device from being demoted, diasbled Auto-Demotion.
KEPServerEX5 Help 136 Possible Cause: The user is attempting to license a driver or component without the Runtime enabled and running. Solution: Start the Runtime Service and then re-attempt licensing. Module '' is unsigned or has a corrupt signature. Runtime references are limited to demo operation Error Type: Warning Source: Runtime Possible Cause: Runtime attempted to validate a license certificate and failed. Solution: 1. Ensure that the license subscriptions are updated. 2.
137 KEPServerEX5 Help Rejecting attempt to delete referenced object '- ' Error Type: Warning Source: Runtime Possible Cause: An attempt was made to remove an object from the server that is being referenced from some other place. Solution: Remove the reference and then re-attempt to remove the object. Rejecting attempt to move referenced object '
- ' Error Type: Warning Source: Runtime Possible Cause: An attempt was made to move an object and failed.
KEPServerEX5 Help 138 Starting '' device driver Error Type: Warning Possible Cause: The server successfully loaded and started a driver that will be used in the running project. Starting '' plug-in Error Type: Information Source: Runtime Possible Cause: The server started and successfully loaded the plug-in for use. Solution: N/A.
139 KEPServerEX5 Help Solution: Contact the OEM/Vendor for more information and support. Unable to generate a tag database for device ''. Reason: '' Error Type: Warning Source: Runtime Possible Cause: The server attempted to generate tags for the specified device and failed with the specified reason. Solution: Correct the reason of failure and then retry the tag generation. Unable to generate a tag database for device ''.
KEPServerEX5 Help 140 Source: Runtime Possible Cause: The client application sent a write to an item and it was rejected. Solution: 1. The tag may have Read/Write access in the server even though the device only allows reads. Verify that the item is Read Only and change the access Writes in the server. Additionally, change the action in the connected client application. 2. The server may have timed-out in demo mode. Save and then restart the server.
141 KEPServerEX5 Help Server Configuration Error Messages The following error/warning messages may be generated. Click on the link for a description of the message.
KEPServerEX5 Help 142 '' device driver unloaded from memory Error Type: Information Source: Configuration Possible Cause: The driver was unloaded from the server's memory space because it was no longer needed. Solution N/A. '' device driver was not found or could not be loaded Error Type: Error Source: Configuration Possible Cause: An attempt was made to load a project with a channel using the specified driver which could not be found or loaded. 1.
143 KEPServerEX5 Help Solution: Re-run the server install and select the specified plug-in for installation. A client application has '' auto-demotion on device '' Error Type: Information Source: Configuration Possible Cause: A client application that is connected to the server has enabled or disabled Auto Demotion on the specified device.
KEPServerEX5 Help 144 This message indicates that two Channel Wizard pages were created with the same ID. Solution: Contact Technical Support. Error importing CSV tag record '': '' is not a valid tag group name Error Type: Warning Source: Configuration Possible Cause: A tag group has been imported in the CSV file that is incorrectly formatted. Solution: Correct the syntax in the CSV file and then re-import. Note: Tag group names may not start with '_' (Underscores), '.
145 KEPServerEX5 Help Error importing CSV tag record '': Tag or group name exceeds 256 characters Error Type: Warning Source: Configuration Possible Cause: A tag or tag group has been imported from a CSV file that has a name exceeding the 256 character limit. Solution: Correct the specified name in the CSV file and then re-import. Note: The tag record is calculated from the List of tags in the CSV file, beginning with the first item listed.
KEPServerEX5 Help 146 The IP address that is specified for a device on an Ethernet Encapsulated channel is not a valid IP address. Solution: Correct the IP in the XML file and then re-load the project. Note: This error occurs when loading XML formatted projects. These projects have usually been created or edited with a third party XML software.
147 KEPServerEX5 Help Maximum device count exceeded for the lite version '' driver license Error Type: Warning Source: Configuration Possible Cause: The specified driver was activated with a lite license, which limits the number of devices that can be configured. Solution: 1. Verify the number of devices authorized by the license. Then, correct the project design to use only that number of channels. 2.
KEPServerEX5 Help 148 The specified project was opened. Solution: N/A. Required schema file '' not found Error Type: Error Source: Configuration Possible Cause: A project formatted with XML was loaded but the specified schema file was not found in the schemas folder. Solution: Re-run the server install and make sure that all the drivers are updated. This will re-install any missing schema files.
149 KEPServerEX5 Help Possible Cause: OPC Diagnostics capturing were stopped by a connected Configuration. Solution: N/A. Unable to add channel due to driver-level failure Error Type: Error Source: Configuration Possible Cause: An attempt was made to add a channel to the server and it failed due to issues in the driver. Solution: 1. Refer to the additional messages that will be posted with information on the driver-level error. 2. If necessary, contact Technical Support for additional help.
KEPServerEX5 Help 150 Possible Cause: The server was unable to back up the server project to the specified file location. Solution: 1. Ensure that the destination file is not locked by another application. 2. Ensure that the destination file, along with the folder where it is located, have Read/Write access. Note: This error is most likely due to Read/Write access permissions.
151 KEPServerEX5 Help Solution: Contact Technical support and verify which version should be installed for the version of the server being run. Remove the driver that is invalid and then restart the server and load the project. Unable to use network adapter '' on channel ''. Using default network adapter Error Type: Warning Source: Configuration Possible Cause: The network adapter specified in the project does not exist on this PC.
KEPServerEX5 Help Line dropped at remote site on '' Modem line closed: '' Modem line opened: '' Modem to Modem DCE: '' MODEMSETTINGS unavailable No comm handle provided on connect for line '' No dial tone on '' Remote line is busy on '' Remote line is not answering on '' TAPI configuration has changed, reinitializing...
153 KEPServerEX5 Help N/A. , Software flow control Error Type: Information Source: TAPI Manager Possible Cause: Software Flow control has been set in the Modem Configuration dialog. Solution: N/A. Dialing '' on line '' Error Type: Information Source: TAPI Manager Possible Cause: TAPI manager is dialing the specified number for the server. Solution: N/A.
KEPServerEX5 Help 154 Failed to open modem line '' [TAPI error] Error Type: Error Source: TAPI Manager Possible Cause: TAPI attempted to open the modem line for the server and encountered an error. Solution: Correct the specified error. Then, re-attempt to open the modem line. Hardware error on line '' Error Type: Warning Source: TAPI Manager Possible Cause: A hardware error was returned after a request was made for a tag in a device that will be connected to the modem.
155 KEPServerEX5 Help Solution: None available. Line '' connected at '' baud Error Type: Information Source: TAPI Manager Possible Cause: The modem connected to the dialed modem at the specified rate. Solution: N/A. Line '' disconnected Error Type: Information Source: TAPI Manager Possible Cause: TAPI manager has disconnected the modem for the server. Solution: N/A.
KEPServerEX5 Help 156 Solution: N/A. Modem line closed: '' Error Type: Warning Source: TAPI Manager Possible Cause: The modem line was closed by the TAPI manager. Solution: This message is normally posted when a project is stopped and the driver no longer needs the modem line. Modem line opened: '' Error Type: Warning Source: TAPI Manager Possible Cause: The modem line was opened by the TAPI manager.
157 KEPServerEX5 Help If the modem was recently installed, try stopping and restarting the server. The PC may need to be rebooted in order for the modem settings to become available. No comm handle provided on connect for line '' Error Type: Warning Source: TAPI Manager Possible Cause: An attempt was made to connect to the modem line with no specified COMM handle. Solution: Make sure the modem is both installed and initialized correctly.
KEPServerEX5 Help 158 Solution: 1. Hang up and then try again later. 2. Verify that the remote modem is configured to answer calls. TAPI configuration has changed, reinitializing... Error Type: Information Source: TAPI Manager Possible Cause: The TAPI Line configuration has changed. TAPI is now reinitializing the modem with the changes. Solution: None available.
159 KEPServerEX5 Help TAPI Manager was unable to apply to Configuration changes to the server. Solution: 1. Verify the cabling to the modem. 2. Verify that the modem is set to accept Configuration changes. 3. Verify that the modem is not being used by another application. Unable to dial on line '' Error Type: Information Source: TAPI Manager Possible Cause: The server is unable to have the modem dial the number because the modem is not in a state that allows dialing.
KEPServerEX5 Help 160 The server was not able to add the NIO interface. Solution: The server could be in use by a client application. In this case, changes (such as, new interfaces) can be disabled. Failed to enable iFIX PDB support for this server [OS Error = n] Error Type: Information Source: NIO Possible Cause: The server was unable to access the registry to enable the NIO interface. Solution: This error generally concerns user account access rights.
161 KEPServerEX5 Help Index -BBasic Server Components Built-In Diagnostics 39 -_- 50 -C- _ Error control 152 _ Forced error control 152 _ Hardware flow control 152 _ Software flow control 153 -<'' device driver loaded successfully 141 '' device driver unloaded from memory 142 '' Server Started 129 '' successfully configured to run as a system service 129 '' successfully removed from the service control manager database 129 -AA c
Index Device '' has been auto-demoted 135 Device '' has been auto-promoted to determine if communications can be re-established 135 Device Properties - Auto-Demotion 65 Device Properties - Ethernet Encapsulation 62 Device Properties - General 60 Device Properties - Timing 63 Dialing '' on line '' 153 Dialing aborted on '' 153 Dialing on line '' cancelled by user 153 Duplicate Channel Wizard page ID '' detected 143 Dynami
163 KEPServerEX5 Help -M- -P- Maximum channel count exceeded for the lite version '' driver license 146 Maximum device count exceeded for the lite version '' driver license 147 Maximum runtime tag count exceeded for the lite version '' driver license 147 Modem initialization failed on channel '' 147 Modem line closed: '' 156 Modem line opened: '' 156 Modem Tags 31 Modem to Modem DCE: '' 156 MODEMSETTINGS
Index Stopping '' device driver 138 Stopping '' plug-in 138 Stopping OPC diagnostics 148 System Requirements 6 System Tags 21 -TTag Group Properties 70 Tag Management 17 Tag Properties 66 Tag Scaling 69 Tag Selection 70 TAPI configuration has changed_ reinitializing...