OPC Server Gateway Sample Clauses

OPC Server Gateway. The part of the Gateway that communicates with the OPC server is implemented as an OPC/COM client. The first thing that has to be done is that the client contacts the server. There are different ways of doing this depending on what kind of server you want to access. ABB:s OPC server is an out-of-process server and can be run as a local server or as a remote server. In both cases the server needs to be configured before usage, i.e. the server must be informed about what controllers it should provide data from. Local means that the server and the client are on the same machine. If the server is not running when the client is started, COM will start up the server and connect the client to it. This means that the server is not connected to any controllers and needs to be configured. If the server is running when starting a client, another client may have configured the server and COM will connect the client to the running instance of it. A remote server is located on a different machine from the client, and DCOM is used for communication. The implementation of a DCOM client is a little bit different from a COM client. There are two ways to configure the server. One way is to use the graphical user interface that is provided with the OPC server. The user interface makes it easy to select the controllers you want the OPC DA server to provide data from. The other way is to let the client configure the server directly through COM interfaces. This makes it possible for a specially written OPC/COM client to first use the COM interface to perform the configuration and then use the OPC interfaces to access the server. The Gateway that we implemented does not provide the opportunity to configure the OPC server, the configuration has to be done through the server’s user interface. The Gateway needs to be configured as well, this means that the user has to provide certain information that the program needs to work. The user gives this information in the first instance of the program. After that the OPC client part of the program contacts the OPC server and connects to it. The Gateway makes it possible to connect both to local and remote servers. The user has to specify what kind of server, local or remote, to be used as a part of the configuration. This is necessary for the program to know since the methods for connecting by COM and DCOM are different.
Sample 1
AutoNDA by SimpleDocs

Related to OPC Server Gateway

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Server Software Subject to the terms and conditions of this XXXX, Vocera grants you the non-exclusive right to (i) install and run (“Use”) the Server Software on computer systems (each, a “Server Computer”) located at End User’s Facilities in the geographic territory designated above (“Territory”); (ii) to Use the Client Software in conjunction with Authorized Client Devices and such Server Computers; and (iii) for pilot licenses for certain Software provided on a trial basis, use such Software for the limited term specified by Vocera in writing. You may Use the standard Server Software on one primary Server Computer (or a primary cluster of computers suitably configured for productive use of the Server Software). You may install backup copies of the Server Software on backup Server Computers to provide redundancy in the event of failure of the primary Server Computer(s) but, unless you have acquired additional licenses or a failover license from Vocera, you may not run such backup or additional copies concurrently with the primary copies. Vocera grants you the right to use the applicable License Key issued by Vocera only to enable Use of the Server Software in conjunction with the licensed Server Computers. Server Software may be licensed for a Subscription Term as specified in the Quote.

  • Red Hat Directory Server Use Cases Subscription Services are provided for Red Hat Directory Server only when used for its supported Use Case in accordance with the terms of this Exhibit and Table 3.1 below.

  • Web Hosting If Customer submits a Service Order(s) for web hosting services, the following terms shall also apply:

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Unbundled Copper Loop – Designed (UCL-D) 2.4.2.1 The UCL-D will be provisioned as a dry copper twisted pair (2- or 4-wire) Loop that is unencumbered by any intervening equipment (e.g., filters, load coils, range extenders, digital loop carrier, or repeaters).

  • Network Resource Interconnection Service (check if selected)

  • Servers Marco backs up the following servers only: Windows Servers, SQL servers, Exchange server, and Virtual Machines images running VMWare or Hyper V.

  • NON-NETWORK PROVIDER is a provider that has not entered into a contract with us or any other Blue Cross and Blue Shield plan. For pediatric dental care services, non-network provider is a dentist that has not entered into a contract with us or does not participate in the Dental Coast to Coast Network. For pediatric vision hardware services, a non-network provider is a provider that has not entered into a contract with EyeMed, our vision care service manager.

  • Provider Network The Panel of health service Providers with which the Contractor contracts for the provision of covered services to Members and Out-of-network Providers administering services to Members.

Time is Money Join Law Insider Premium to draft better contracts faster.