KEPServerEX V5 Help - Omron
KEPServerEX V5 Help 2015 Kepware, Inc.
KEPServerEX V5 Help2Table of ContentsTable of Contents2Introduction9System Requirements10Server Summary Information10Components11Process Modes12Interfaces and Connectivity13OPC DA13OPC AE13OPC UA15OPC .NET15DDE16FastDDE/SuiteLink16iFIX Native Interfaces16Thin-Client Terminal Server17Accessing the Administration Menu18Settings19Settings - Administration20Settings - Configuration21Settings - Runtime Process22Settings - Runtime Options23Settings - Event Log24Settings - ProgID Redirect26Settings - User Manager28Navigating the Configuration32Project Properties35Project Properties - Identification35Project Properties - OPC DA Settings35Project Properties - DDE38Project Properties - FastDDE/Suitelink40Project Properties - iFIX PDB Settings41Project Properties - OPC UA42Project Properties - OPC AE44Project Properties - OPC HDA46Project Properties - OPC .NET47Server Options48Options - General48Options - Runtime Connection49Basic Server Components50What is a Channel?50www. kepware.com
KEPServerEX V5 Help3Channel Properties - General50Channel Properties - Communications52Additional Ethernet Encapsulation Settings57Channel Properties - Communication Serialization59Channel Properties - Network Interface60Channel Properties - Write Optimizations61Channel Properties - Device Discovery63Channel Properties - Advanced64What is a Device?65Device Properties - General65Device Properties - Scan Mode68Device Properties - Ethernet Encapsulation69Device Properties - Timing70Device Properties - Auto-Demotion72Device Properties - Time Synchronization73What is a Tag?75Tag Properties - General75Multiple Tag Generation78Tag Properties - Scaling81Dynamic Tags82Static Tags (User-Defined)84What is a Tag Group?84Tag Group Properties84What is the Alias Map?85Alias Properties86What is the Event Log?87Event Log Display87Event Log Page Setup89Tag Management90CSV Import and Export90Automatic OPC Tag Database Generation92System Tags96Property Tags106Statistics Tags107Modem Tags109Communication Serialization Tags111Communications Management113Using a Modem in the Server Project113Phonebook Tags115Phone Number Tags116Modem Auto-Dial117Built-In Diagnostics119OPC Diagnostics Viewer119www. kepware.com
KEPServerEX V5 Help4OPC Diagnostic Events122Communication Diagnostics128iFIX Signal Conditioning OptionsProject Startup for iFIX Applications131136Designing a Project137Running the Server137Starting a New Project137Adding and Configuring a Channel138Adding and Configuring a Device139Adding User-Defined Tags141Browsing for Tags144Generating Multiple Tags145Adding Tag Scaling149Saving the Project150Testing the Project151New Channel - Identification157New Channel - Device Driver157New Channel - Communications158New Channel - Modem Auto Dial159New Channel - Connection Behavior160New Channel - Summary161New Device - Name162New Device - Model163New Device - ID163New Device - Scan Mode165New Device - Timing165New Device - Summary166How Do I.167How To. Allow Desktop Interactions167How To. Create and Use an Alias168How To. Optimize the Server Project170How To. Properly Name a Channel, Device, Tag, and Tag Group171How To. Resolve Comm Issues When the DNS/DHCP Device Connected to the Server isPower Cycled171How To. Use an Alias to Optimize a Project173How To. Use DDE with the Server174How To. Use Dynamic Tag Addressing175How To. Use Ethernet Encapsulation175How To. Use Net DDE Across a Network177How To . Work with Non-Normalized Floating Point Values177Device Demand Poll179Message Descriptions180General Operation System Messageswww. kepware.com180
KEPServerEX V5 Help5Dialing phone number on line modem name .180Dialing aborted on modem name .180Dialing on line modem name canceled by user.181Failed to open modem line modem name [TAPI error].181Hardware error on line modem name .181Incoming call detected on line modem name .181Line modem name connected.182Line modem name connected at baud rate baud.182Line modem name disconnected.182Line modem name is already in use.182Line dropped at remote site on modem name .182Modem line closed: modem name .183Modem line opened: modem name .183Modem to Modem DCE: connection parameters .183MODEMSETTINGS unavailable.184No comm handle provided on connect for line modem name .184No dial tone on modem name .184Remote line is busy on modem name .184Remote line is not answering on modem name .185Socket error code occurred on device name . Operation operation name failed because reason .185TAPI configuration has changed, reinitializing.185TAPI line initialization failed: modem name .185The phone number is invalid phone number .186Unable to apply Modem Configuration on line modem name .186Unable to dial on line modem name .186Unable to start Net DDE.186iFIX Messages187Attempt to add iFIX PDB item item name failed.187Failed to enable iFIX PDB support for this server [OS error n].187Unable to enable iFIX PDB support for this server.187Unable to read tag name on device channel name/device name .188Server Administration Messages188Cannot export user information until all passwords have been updated.188Password for user name has been changed.188Password for user 'Administrator' was reset by Windows user .189Password reset for user 'Administrator' failed. Windows user is not a Windows administrator.189Permissions definition has changed on user group name .189User name has been created as a member of user group name .189User name has been disabled.190User name has been enabled.190User name has been renamed to new name .190User name moved from user group old group to new group .190User group name has been created.190User group name has been disabled.191www. kepware.com
KEPServerEX V5 Help6User group name has been enabled.191User group name has been renamed to new name .191User information replaced by import from file name .191Server Configuration Messages192 device name device driver loaded successfully.192 driver name device driver unloaded from memory.192 driver name device driver was not found or could not be loaded.193 Driver name driver does not currently support XML persistence.193 Plug-in plug-in was not found or could not be loaded.193 COM/Modem ID is already in use by channel channel name .194 COM/Modem ID is already in use on virtual network .194 Virtual network already contains a shared connection.194A client application has enabled/disabled auto-demotion on device device name .194A connection share pairing on COM/Modem ID is not supported by drivers driver name and driver name .195Closing project project name .195Created backup of project project name to file location .195Error importing CSV tag record record number : tag name is not a valid tag group name.195Error importing CSV tag record record number : tag name is not a valid tag name.196Error importing CSV tag record record number : Missing address.196Error importing CSV tag record record number : Tag or group name exceeds 256 characters.196Failed to reset channel diagnostics.196Failed to retrieve Runtime project.197Invalid Ethernet encapsulation IP IP address .197Invalid or missing modem configuration on channel channel name , substituting modem .197Invalid XML document XML name .197Maximum channel count exceeded for the lite version driver name driver license.198Maximum device count exceeded for the lite version driver name driver license.198Maximum Runtime tag count exceeded for the lite version driver name driver license.198Modem initialization failed on channel channel name .199Opening project project name .199Project containing custom access control permissions cannot be saved as XML.199Required schema file schema name not found.199Runtime project update failed.200Starting OPC diagnostics.200Stopping OPC diagnostics.200Unable to add channel due to driver-level failure.200Unable to add device due to driver-level failure.201Unable to backup project file to file path .201Unable to begin device discovery on channel channel name .201Unable to launch OPC Quick Client [Path: path OS error: error ].202Unable to load driver DLL driver name .202Unable to load the driver name driver because more than one copy exists ( driver name and driver name ).202Unable to use network adapter adapter on channel channel name . Using default networkadapter.202www. kepware.com
KEPServerEX V5 Help7Validation error on tag name : Invalid scaling parameters.Server Runtime Messages203203 Driver name device driver was not found or could not be loaded.204 Server name server started.204 Server Runtime successfully configured to run as a system service.204 Server runtime successfully removed from the service control manager database.205Access denied to user name requesting permission on object path .205Attempt to add DDE item item name failed.205Attempt to add FastDDE/SuiteLink item tag name failed.205Attempt to add OPC client item item name failed.206Attempting to automatically generate tags for device device name .206Auto generation for tag tag name already exists and will not be overwritten.206Auto generation produced too many overwrites, stopped posting error messages.207Cannot delete object path because it belongs to a client access policy defined under user group user group name .207Channel diagnostics started on channel channel name .207Channel diagnostics stopped on channel channel name .207Completed automatic tag generation for device device name .208Configuration session assigned to user name as default user has ended.208Configuration session assigned to user name demoted to read only.208Configuration session assigned to user name promoted to write access.208Configuration session started by user name .208Configuration TCP/IP port number changed to port number .209Data collection is enabled/disabled on device device name .209DDE client attempt to add topic topic failed.209Delete object item name failed.209Demo timer started. Days hours minutes seconds .210Demo timer updated. time remaining .210Demonstration time period has expired for feature name .210Device device name has been auto-demoted.211Device device name has been auto-promoted to determine if communications can be reestablished.211Failed to upload project XML.211FLEXnet Licensing Service must be enabled to process your license. Runtime references are limitedto demo operation.212Module module is unsigned or has a corrupt signature. Runtime references are limited to demooperation.212Move object group to group failed.212Move object object failed.212No device driver DLLs were loaded.213Runtime project replaced from project location .213Simulation mode is disabled on device device name .213Simulation mode is enabled on device device name .213Starting driver name device driver.214Starting plug-in name plug-in.214Stopping driver name device driver.214www. kepware.com
KEPServerEX V5 Help8Stopping plug-in name plug-in.214The tier information for feature feature is invalid.214Unable to generate a tag database for device device name . Reason: reason 215Unable to generate a tag database for device device name . The device is not responding.215Unable to load project project name .215Unable to write to item item name .215Update of object object failed.216Write request rejected on item reference item name since the device it belongs to is disabled.216Write request rejected on read-only item reference item name .216Index218www. kepware.com
KEPServerEX V5 Help9CONTENTSIntroductionInterfaces and ConnectivityAccessing the Administration MenuNavigating the ConfigurationBasic Server ComponentsTag ManagementCommunications ManagementBuilt-In DiagnosticsDesigning a ProjectHow Do I. ?Error DescriptionsNote: For information regarding product licensing, refer to the License Utility help file. To access the help filethrough the server Configuration menu, click Help Server Help License Utility. To access the help file throughthe server Administration menu, right-click on the KEPServerEX icon in the System Tray and then select Help License Utility.Help version 1.378IntroductionThis software based server is designed for accurate communications, quick setup and unmatchedinteroperability between client applications, industrial devices and systems. The server provides a wide range ofplug-in device drivers and components that suit most communication needs. The plug-in design and single userinterface provides consistent access from standards-based applications (such as OPC) and non-standards basedapplications with native interfaces.www. kepware.com
KEPServerEX V5 Help10System RequirementsThe server has minimum system requirements for both software and hardware. These requirements must be metin order for the application to operate as designed.This application supports the following Microsoft Windows operating systems:lWindows 8lWindows 7 Professional, Enterprise, and UltimatelWindows Vista Business, Enterprise, and UltimatelWindows Server 2012 / 2012 R2lWindows Server 2008 / 2008 R2lWindows Server 2003 (Service Pack 2)lWindows XP Professional (Service Pack 2)Note: When installed on a 64-bit operating system, the application will run in a subsystem of Windows calledWOW64 (Windows-on-Windows 64 bit). WOW64 is included on all 64-bit versions of Windows and is designedto make differences between the operating systems transparent to the user.This application requires the following hardware at a minimum:l2.0 GHz Processorl1 GB installed RAMl180 MB available disk spacelEthernet CardServer Summary InformationThe server provides basic summary information about itself and the drivers/plug-ins that are currently installed.About the ServerThe server version is readily available for review and provides a way to find driver-specific information. Toaccess, click Help Support Information in the server Configuration. To display the version information of allinstalled components, click Versions.Component Version InformationThe Version Information window displays all installed drivers and plug-ins along with their version numbers. Fordriver-specific information, select a component and then click Summary.Driver Informationwww. kepware.com
KEPServerEX V5 Help11The Driver Information window provides a summary of the driver's default settings. For example, each driverdisplays its maximum number of supported channels.Descriptions of the information available is as follows:llllSummary provides the driver name and type, the maximum number of supported channels, and thenumber of models in the driver.COMM Defaults displays the driver's default settings, which may or may not match the settings of thedevice being configured.Driver flag definitions displays the driver library functions and indicates whether they have beenenabled in the driver.Model Information displays device-specific addressing and features. It lists the name for eachsupported model in addition to its addressing values and other features.ComponentsThe server implements client/server architecture. The components include Configuration, Runtime,Administration, and Event Log.ConfigurationThe Configuration is the client-user interface that is used to modify the Runtime's project. The Configuration canbe launched by multiple users and support remote Runtime configuration.CSV Import and ExportThis server supports the import and export of tag data in a Comma Separated Variable (CSV) file. When usingCSV import and export, tags are created quickly in the desired application. For more information, refer toCSV Import and Export.RuntimeThe Runtime is the server component that starts as a service by default. Clients can connect to the runtimeremotely or locally.AdministrationThe Administration is used to view and/or modify settings and launch applications that pertain to usermanagement and the server. By default, the Administration is started and sent to the System Tray when a useraccount logs onto the operating system.Event LogThe Event Log service collects information, warning, error, and security events. These events are then sent to theConfiguration's Event Log window for viewing. For more information, refer to What is the Event Log?www. kepware.com
KEPServerEX V5 Help12Process ModesThe Runtime's process mode can be changed while the server is running; however, doing so while a client isconnected interrupts the connection for a short period. The modes of operation are System Service andInteractive.System ServiceBy default, the server is installed and runs as a service. When System Service is selected, the Runtime does notrequire user intervention and starts when the operating system opens. This provides user independent access tothe server by the clients.InteractiveWhen Interactive is selected, the Runtime remains stopped until a client attempts to connect to it. Once started, itruns until all clients have disconnected and then shuts down. The Runtime also shuts down if the user accountlogs off the operation system.Note: The Runtime's process mode may be changed to meet client applications' needs through theAdministration settings dialogs.System Service is required for the following conditions:lWhen iFIX is required to run on an operating system while UAC is enabled.Interactive is required for the following conditions:lWhen a communication interface (such as DDE) must exchange information with the user desktop andthe server is installed on Windows Vista, Windows Server 2008, or later operating systems.See Also:Settings - Runtime ProcessHow To.Allow Desktop Interactions.www. kepware.com
KEPServerEX V5 Help13Interfaces and ConnectivityThis communications server simultaneously supports the client/server technologies listed below. Clientapplications can use any of these technologies to access data from the server at the same time. For moreinformation on a specific interface, select a link from the list below.OPC DAOPC AEOPC UAOPC .NETDDEFastDDE/SuiteLinkiFIX Native InterfacesThin-Client Terminal ServerOPC DASupported Versions1.0a2.05a3.0Overview"OPC" stands for Open Productivity and Connectivity in industrial automation and the enterprise systems thatsupport industry. It is a client/server technology where one application acts as the server (providing data) andanother acts as a client (using data).OPC is composed of a series of standards specifications: OPC Data Access (DA) is the most prolific standard. OPCDA is a widely accepted industrial communication standard that enables data exchange between multi-vendordevices and control applications without proprietary restrictions. An OPC server can communicate datacontinuously among PLCs on the shop floor, RTUs in the field, HMI stations, and software applications on desktopPCs. OPC compliance makes continuous real-time communication possible (even when the hardware and softwareare from different vendors).OPC Data Access 1.0a was the original specification developed by the OPC Foundation in 1996. Although itcontinues to be supported by many of the OPC client applications in use today, OPC Data Access 2.0 EnhancedOPC better utilizes the underlying Microsoft COM technology. OPC Data Access 3.0 is the latest version of the OPCDA interface.See Also:Project Properties - OPC DA SettingsProject Properties - OPC DA ComplianceOPC AESupported Versions1.01.10www. kepware.com
KEPServerEX V5 Help14OverviewOPC Alarms & Events (AE) is a specification developed by the OPC Foundation to standardize the way that alarmand event information is shared among systems. Using the standard, AE clients can receive alarms and eventnotices for equipment safety limits, system errors, and other abnormal situations.Simple EventsSimple Events include the server events displayed in the Event Log (such as information, warning, error, andsecurity events). The server supports the following filtering opti
KEPServerEX V5Help TableofContents TableofContents 2 Introduction 9 SystemRequirements 10 ServerSummaryInformation 10 Components 11 ProcessModes 12 InterfacesandConnectivity 13 OPCDA 13 OPCAE 13 OPCUA 15 OPC.NET 15 DDE 16 FastDDE/SuiteLink 16 iFIXNativeInterfaces 16 Thin-ClientTerminalServer 17 AccessingtheAdmin
5.Using Kepware’s OPC Quick Client. Kepware provides an OPC client application for testing purposes with each installation of KEPServerEX. For more information, refer to the OPC Quick Client help documentation. Title: KEPServerEX
The Simulation Driver Demo project will be used for all examples in this tutorial. Start KEPServerEX and load the Simulation Driver Demo project. Once . Rockwell Software’s FactoryTalk View Studio . Title: KEPServerEX Client Connectivity Guide for Rockwell Software’s FactoryTalk View Studio
signature files. Turn off any unused services on the host machine. To reduce the attack surface, avoid co-hosting KEPServerEX with any other applications. 3.2 User Management Create a Windows user separate from the Administrator account to configure, manage, and run KEPServerEX. Manage the Administrator account according to Windows best practices.
Hartmann Tensoval Duo Control II Omron HEM-7420 Transtek TMB-1776 Hingmed WBP-02A Hospital Omron HEM-9600T Welch Allyn ProBP 2000 iHealth CardioMed (ABP100) Omron HEM-9601T Withings BP-800 InBody BP170 Omron HEM-9700T Yuwell YE680B InBody BPBIO250 Omron M3 (HEM-7200-E) Yuwell YE690A # 1-Star Blood Pressure Monitors # A&D TM-2420 Microlife BP A100
14 Omron E3Z-LS Photoelectric Switch 15 2 Omron Photoelectric Switch 16 2 Omron Photoelectric Switches 17 3 Omron Proximity Switches 18 Omron Photoelectric Sensor 19 Quantity Pneumatic Fittings, to 3 tubs 20 Quantity various Air Filters, to Bosch, Schroder,
The Klinkmann OMRON Tag Creator is an add-on module for Wonderware InTouch WindowMaker, used to expand the functionality and capability of InTouch at design time. The Omron PLC programs created by the OMRON CX-Programmer Windows
HEM-7322U-E_A_M10_131029.pdf Model M6 Comfort IT Výrobce Zástupce pro EU OMRON HEALTHCARE EUROPE B.V. Scorpius 33, 2132 LR Hoofddorp, NIZOZEMSKO www.omron-healthcare.com Výrobní závod OMRON HEALTHCARE UK LTD. Opal Drive, Fox Milne, Milton Keynes, MK15 0DG, U.K. Pobočka Distribuce a servis pro ČR OMRON MEDIZINTECHNIK
Topographical Anatomy A working knowledge of human anatomy is important for you as an EMT. By using the proper medical terms, you will be able to communicate correct information to medical professionals with the least possible confusion. At the same time, you need to be able to communicate with others who may or may not understand medical terms. Balancing these two facets is one of the most .
