User's Guide
Table Of Contents
- 1 Introduction
- 2 References
- 3 Terms and Definitions
- 4 Support
- 5 Hazardous Location Requirements
- 6 Operating Conditions
- 7 General Safety
- 8 Radio and Electromagnetic Compatibility
- 9 VP Series 2000 Components
- 10 ISA100.11a Provisioning
- 11 Hardware Installation
- 12 Configuration
- 13 Operation
- 14 Maintenance
- 15 Security Hardening Guidelines
EVR-VPXDOC-0036 VP Series 2000 User Guide
Version 1.09
Proprietary & Confidential - Copyright © 2018 Divigraph (Pty) Ltd. All Rights Reserved
Page 26 / 36
12 Configuration
Configuration of VP Series 2000 devices are network infrastructure vendor dependant. VP Series
2000 device data is generally published using either Modbus or OPC. Publication of this data is
network infrastructure vendor dependant as well. Capability files are provided to enable configuration
of VP Series 2000 devices as well as to enable publication of device data.
Note!
Refer to the applicable vendor documentation to configure devices and setup data
publication.
12.1 Capability Files
Capability files provide an industry standard method of interpretation of device capabilities. The
purpose of a capability file (CF) is to provide a human-readable document which contains the
information required for the host system to interpret the block instantiation capability of a device,
number of possible objects present in a device as well as the default values of the block attributes.
VP Series 2000 device capability files contain information about the capabilities of VP Series 2000
sensors and repeaters.
Note!
Not all host systems require a CF.
Refer to the applicable vendor documentation to determine how to utilise VP Series 2000
capability files if required.
12.2 Data Publishing
Data publishing is a function of the network infrastructure. Depending on the network infrastructure
vendor, data may be published using Modbus or OPC. Modbus is generally an unlicensed method to
publish data while OPC generally requires additional licensing. OPC data mapping and management
is generally simpler than that of Modbus.
Note!
Refer to the applicable vendor documentation to determine whether Modbus or OPC data
publication is available.
12.2.1 Modbus
Most network infrastructure vendors make use of Modbus TCP to publish data. Refer to the vendor
specific documentation for additional information about which Modbus interfaces are available and
how to map VP Series 2000 data to applicable Modbus registers.
12.2.2 OPC
Modbus register data can be published using OPC by means of an OPC server interface on a network
infrastructure host system. This may require a 3
rd
party OPC server interface. Refer to the OPC server
interface documentation for additional detail on how to map Modbus registers to the OPC server.