1. Manuals
  2. Brands
  3. Control Data Systems Manuals
  4. Gateway
  5. Versa Router 950
  6. User manual

Control Data Systems Versa Router 950 User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Versa Router 950
User Manual
Revision: 2.4
Revision 2.4
@2019 Control Data System

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Versa Router 950 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Control Data Systems Versa Router 950

  • Page 1 Versa Router 950 User Manual Revision: 2.4 Revision 2.4 @2019 Control Data System...

  • Page 2: Table Of Contents

    5.6.1 Provisioning ..........................54 5.6.2 Joining ............................57 5.6.3 Publishing: ..........................57 USING THE MONITORING CONTRO1 SYSTEM (MCS) FOR ISA 100 WIRELESS NETWORK ..60 ................... 60 CCESS UTHENTICATION AND AVIGATION ............................61 ETWORK Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 2...
  • Page 3 6.3.9 Alert Subscription ........................112 6.3.10 Advanced Settings ......................112 6.3.10.1 Sections/variables .......................... 112 6.3.10.2 Restart/Stop ............................ 113 6.3.10.3 VR950 Settings ..........................113 6.3.11 Bulk Transfers ........................114 6.3.11.1 Adding a Bulk Transfer ........................115 Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 3...
  • Page 4 Configuring Access Points ......................157 7.3.4.1.1 Multiple Access Points ....................... 158 7.3.4.1.2 Redundant Access Points ......................158 7.3.4.2 Configuring Gateways ........................158 7.3.4.3 Configuring Devices ........................158 7.3.5 Monitoring Host ........................159 Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 4...
  • Page 5 ..............190 CCESSING FILES THROUGH COMMAND LINE INTERFACE VERSA ROUTER CONFIGURATOR .................... 190 10.1 IP U ............190 HANGING THE SING THE ERSA OUTER ONFIGURATOR APPENDIX A – COUNTRY CODES ......................194 Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 5...

  • Page 6: General Notes

    CDS. All rights are reserved in event of the grant of a patent or the registration of a utility model or design. All specifications supplied herein are subject to change without notice. Copyright © Control Data Systems SRL, 2019 Ref.no.: 003274/Revision 2.4...

  • Page 7: Index Of Tables

    Figure 5.3.4 Network ID and Join Key setup example (the Network ID found in MSC will be 2020 – hexadecimal value) Figure 5.3.5 Burst Message example Figure 5.3.6 WirelessHART Provisioning Tool Join Status Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 7...
  • Page 8 Figure 6.2.9 Neighbors Health report window (ISA 100) Figure 6.2.10 Schedule Report window-Superframes and Links (ISA 100) Figure 6.2.11 Link's related information window (ISA 100) Figure 6.2.12 Channel Statistics window (ISA 100) Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 8...
  • Page 9 Figure 6.4.7 System upgrade results window Figure 6.4.8 Custom icon window (ISA 100) Figure 6.4.9 Added icon-visibility (ISA 100) Figure 6.4.10 Interface Configuration window (ISA 100) Figure 6.5.1 Change password window Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 9...
  • Page 10 Figure 7.5.8 Edit Device Code window (HART) Figure 7.6.1 Change password window (HART) Figure 8.1.1 Login window Figure 8.1.2 User interface window Figure 8.2.1 Edge Router Firmware Upgrade window Figure 8.2.2 Activated Edge Router Firmware window Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 10...
  • Page 11 Figure 8.3.4 Network Configuration section window Figure 10.1.1 Versa Router Configurator window Figure 10.1.2 Responses window for Search Network for Versa Routers button Figure 10.1.3 Properties options window for Set VersaRouter Properties button Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 11...

  • Page 12: Document Purpose

    1 Document Purpose The purpose of this document is to offers specific information about Versa Router 950, including instructions for configuring the device’s various options and for monitoring the status of an ISA100.11a and/or WirelessHART network. The document has eight chapters which contains seven main sections, as follows: •...
  • Page 13 The device software revision related to vendor/model. Router A device that has data routing capability. Security Manager An entity in the ISA100.11a network which assigns the security keys that are required Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 13...

  • Page 14: Table 2.2 Abbreviations-User Manual

    GSAP Gateway Service Access Point Gateway Input/output (with reference to devices) Local Area Network Least Significant Bit Monitoring Control System Most Significant Bit Network Manager NSDU Network layer Service Data Unit Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 14...
  • Page 15 Packet Error Rate RSQI Received Signal Quality Indicator Service Access Point System Manager SMAP System Manager Application Process TSAP Transport layer Access Point User Application Process Versa Router Upload/Download Object User Datagram Protocol Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 15...

  • Page 16: References And Resources

    The VR950 is shown in the following picture (Figure 4.1.1): Figure 4.1.1 VR950 Not to be used in mines susceptible to firedamp, as defined in IEC 60079-0:2011 clause 4.1 Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 16...

  • Page 17: Block Diagram

    10 dBm nominal • 2.4 GHz ISM band • 16 channels • 802.15.4 physical layer • WSN antenna connectors 2x SMA type RF connectors Network management • ISA100 System Manager, Security Manager, Gateway Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 17...

  • Page 18: Mechanical Dimensions

    Physical characteristics Size: 159 mm x 130 mm x 40 mm (L x W x H) • Weight: 400g • Enclosure material: Powder coated steel. • Ingress protection: IP20 4.4 Mechanical dimensions Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 18...

  • Page 19: Connector Information

    4.6.1 Electromagnetic Table 4.3 Electromagnetic Compliance Equipment Compliance Information VN210 FCC: Part 15C FCC ID: CDSVN210ISA RED: EN 301 489-1 v2.1.1 EN 301 489-17 v3.1.1 EN 300 328 v2.1.1 Giteki: ID: 003-130207 Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 19...

  • Page 20: Safety

    EN 60079.31:2013 Explosive atmospheres – Part 31: Equipment dust ignition protection by enclosure "t" EN 60664-1:2007 Insulation coordination for equipment within low-voltage systems –Part 1: Principles, requirements and tests Pending: Certification procedures are ongoing Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 20...

  • Page 21: Quick Start Network Configuration

    The static IP configuration is available in the website Configuration section under the Network tab as seen below: Figure 5.1.1 Default admin website static IP configuration After changing the IP, press the Hard Restart button underneath to reboot the VR950 and activate the new settings. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 21...

  • Page 22: Figure 5.1.2 Ip Configuration Example Using The Admin Web Interface

    Gateway modules will scan the network and list the AN_ID, static IP address and the DHCP (dynamic) assigned IP address of each VR950 in the network. Figure 5.1.3 VR Configurator Tool Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 22...

  • Page 23: Configuring Acds Vs210 For Isa100.11 A

    2. Plug into an USB port the CDS ISA100.11a Field Tool. The Field tool should now appear under “Ports” in the Device Manager as “Silicon Labs CP210x USB to UART Bridge”. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 23...

  • Page 24: Figure 5.2.2 Cds Field Tool Com Connection

    Field Tool is connected and set the Field Tool Radio Output Power on High. 4. Press the Connect To Field Tool button and wait until the tool is connected. Figure 5.2.3 ISA Field Tool connection to Nivis Field Tool software Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 24...

  • Page 25: Provisioning

    Check Enable Simple APISupport: • Data Publication Period (interval between 2 publishes) • Attribute ID: UAP_DATA_ANALOG_2 (provides temperature readings) UAP_DATA_ANALOG_3 (provides humidity readings) Press Save. g. Move to step 3. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 25...
  • Page 26 5. Tick the line corresponding to the device being provisioned and press Next and Next again. While the status of the process is Waiting for connection, press the Reset Radio button on the VS210 device. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 26...

  • Page 27: Publishing

    1. Open the VR950’s MCS website. The newly provisioned device should appear in the Device Table as joined. 2. Under Monitoring Host, check the Autodiscover publishers, set Auto Activate to On and press the Rediscover All Publishers button. Figure 5.2.6 ISA Publishers Autodiscovery Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 27...

  • Page 28: Figure 5.2.7 Devices Publishers And Channels In Monitoring Host

    - EUI64: the device EUI, without the colons character (:); - The values for TSAPID, ObjId, AttrId, Idx1 and Idx2 are found in the Monitoring Host channel lines of the device; - MethId: will be 0; Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 28...

  • Page 29: Figure 5.2.8 Monitoring Host Help Information Figure 5.2.9 Modbus Help Information

    After each completed line, press Save; d. Press Activate after all the lines have been inserted 4. The Modbus values can be read using a Modbus client (recommended ModbusMaster from Farrellton Solar). Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 29...

  • Page 30: Configuring Acds Vs210 For Wireless Hart

    1. Go to Windows Start and open “Device Manager”. Roll down the options under “Ports (COM & LPT)”. 2. Plug the MicroLink Modem into an USB port. The Modem’s name should now appear under “Ports” in the Device Manager. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 30...

  • Page 31: Figure 5.3.2 Microlink Hart Protocol Modern Com Connection

    Figure 5.3.3 WirelessHART Provisioning tool COM Connection 4. Open the WirelessHART Provisioning Tool software. Go to Settings and under “Com Port” choose the port to which the MicroLink Modem is connected and press Apply. Under Device Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 31...

  • Page 32: Provisioning

    2 – Read Loop Current and Percent of Range 3 – Read Dynamic Variables and Loop Current 9 – Read Device Variables with Status 33 – Read Device Variables 48 – Read Additional Device Status Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 32...
  • Page 33 3. The example in Figure 5.3.5 will produce: Burst Message 0, with command 9, will contain values for the set variables (Primary Variable, Secondary Variable, Tertiary Variable and Quaternary Variable) and will be published every 60 seconds. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 33...

  • Page 34: Joining

    1. To join the device to the specified Network ID, go to Tools and press Start Assisted Join. Updates on the join status will appear in the table below. When the final status is Normal Operation Commencing, the device is fully joined to the network. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 34...

  • Page 35: Publishing

    2. Under Monitoring Host, the device’s configuration information will automatically be populated in the Burst Messages and Variables fields (the Variables information is specific to each Burst Message, so they will appear only when selecting a Message). Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 35...
  • Page 36 3. To make the published data accessible through Modbus as well, under Modbus, complete the Input Registers fields. For a quicker configuration, in a new tab with the VR’s MCS, open the Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 36...
  • Page 37 After each completed line, press Save; d. Press Activate after all the lines have been inserted. 4. The Modbus values can be read using a Modbus client (recommended ModbusMaster from Farrellton Solar). Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 37...

  • Page 38: Configuring A Honeywell Xyr6000 For Isa100.11A

    2. Plug into an USB port the CDS ISA100.11a Field Tool. The Field tool should now appear under “Ports” in the Device Manager as “Silicon Labs CP210x USB to UART Bridge”. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 38...
  • Page 39 Field Tool has been connected. 4. Press the Connect To Field Tool button and wait until the tool is connected. Figure 5.4.3 ISA Field Tool connection to Nivis Field Tool software Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 39...

  • Page 40: Provisioning

    - Network ID (can be found in the VR950’s MCS website, under Gateway, Subnet ID) - Join Key (can be found in the VR950’s MCS website, under Gateway, App Join Key) - Press Save. - Move to step d. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 40...
  • Page 41 Keep the infrared tool pointed towards the device while in the process of provisioning, until the status changes from In Progress to Provisioned. Press Next. g. Press Finish when shown the summary of the process. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 41...

  • Page 42: Publishing

    • Attribute ID: 2 • Index1: 1 • Values (HEX): 10 3. Under Monitoring Host, check the Autodiscover publishers, set Auto Activate to On and press the Rediscover All Publishers button. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 42...
  • Page 43 6. To make the published data accessible through Modbus as well, under Modbus, fill the Input Registers fields. For a quicker configuration, in a new tab with the VR’s MCS, open the Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 43...
  • Page 44 After each completed line, press Save; d. Press Activate after all the lines have been inserted. 7. The Modbus values can be read using a Modbus client (recommended ModbusMaster from Farrellton Solar). Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 44...

  • Page 45: Configuring A Yokogawa Ejx110L For Isa100.11A

    2. Plug into an USB port the CDS ISA100.11a Field Tool. The Field tool should now appear under “Ports” in the Device Manager as “Silicon Labs CP210x USB to UART Bridge”. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 45...
  • Page 46 Field Tool has been connected. 4. Press the Connect To Field Tool button and wait until the tool is connected. Figure 5.5.3 ISA Field Tool connection to Nivis Field Tool software Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 46...

  • Page 47: Provisioning

    0022:FF00:0002:1F11) b. Device Tag (a representative name for the device, up to 16 characters, e.g. YOKO_Temp_1F11) c. Network ID (can be found in the VR950’s MCS website, under Gateway, Subnet ID) Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 47...
  • Page 48 (in Figure 5.5.6, the device is a joining state). This process can take up to 5 minutes, depending on the number of devices in the network. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 48...

  • Page 49: Publishing

    Channels fields (the Channels information is specific to each Publishers, so they will appear only when selecting a Publisher). From this moment forward, the device will start publishing data, which can be found under Readings. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 49...
  • Page 50 - The values for TSAPID, ObjId, AttrId, Idx1 and Idx2 are found in the Monitoring Host channel lines of the device (as seen in Figures 7 and 8); - MethId: will be 0; - Status_byte: will be 2. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 50...
  • Page 51 After each completed line, press Save; d. Press Activate after all the lines have been inserted. 4. The Modbus values can be read using a Modbus client (recommended ModbusMaster from Farrellton Solar). Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 51...

  • Page 52: Configuring A Emerson Pt100/2Wire For Wirelesshart

    5. Go to Windows Start and open “Device Manager”. Roll down the options under “Ports (COM & LPT)”. 6. Plug the MicroLink Modem into an USB port. The Modem’s name should now appear under “Ports” in the Device Manager. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 52...
  • Page 53 Figure 5.6.3 WirelessHART Provisioning tool COM Connection 8. Open the WirelessHART Provisioning Tool software. Go to Settings and under “Com Port” choose the port to which the MicroLink Modem is connected and press Apply. Under Device Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 53...

  • Page 54: Provisioning

    2 – Read Loop Current and Percent of Range 3 – Read Dynamic Variables and Loop Current 9 – Read Device Variables with Status 33 – Read Device Variables 48 – Read Additional Device Status Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 54...
  • Page 55 Burst Message 0, with command 9, will contain values for the set variables (Primary Variable, Battery life, Percent Range, Secondary Variable and Tertiary Variable) and will be published every 4 seconds. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 55...
  • Page 56 Figure 5.6.5 Burst Message example 8. As many as 3 burst messages can be set to publish. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 56...

  • Page 57: Joining

    6. Under Monitoring Host, the device’s configuration information will automatically be populated in the Burst Messages and Variables fields (the Variables information is specific to each Burst Message, so they will appear only when selecting a Message). Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 57...
  • Page 58 7. To make the published data accessible through Modbus as well, under Modbus, complete the Input Registers fields. For a quicker configuration, in a new tab with the VR’s MCS, open the Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 58...
  • Page 59 After each completed line, press Save; h. Press Activate after all the lines have been inserted. 8. The Modbus values can be read using a Modbus client (recommended ModbusMaster from Farrellton Solar). Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 59...

  • Page 60: Using The Monitoring Contro1 System (Mcs) For Isa 100 Wireless Network

    (Figure 6.1.2). For a detailed description of the Device list, please see the Section 6.2.3. The Monitoring Control System page with the Device list is shown in the following screen capture (Figure 6.1.2): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 60...

  • Page 61: Network

    The information is refreshed automatically at regular intervals (10 seconds, 30 seconds, or 1 minute). The Dashboard series of panes are shown in the following screen capture (Figure 6.2.1): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 61...

  • Page 62: Adding A Device To The Dashboard

    5. optionally, select the slot number (up to the current slot number); if you do not select a slot number, the system automatically assigns the next available slot; 6. select the desired gauge type, then click OK to add the device to the dashboard. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 62...

  • Page 63: Deleting A Device

    The Topology page displays a graphical representation of the current network topology and also allows users to view data about contracts and devices. The graphical representation of the Network Topology is shown in the following screen capture (Figure 6.2.3): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 63...
  • Page 64 Refresh – this will generate a Request Topology command and will refresh the page. In the SubnetID drop-down list located at the top of the topology window, select a subnet to view it. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 64...
  • Page 65 The available Topology page elements and viewing options are described in the following paragraphs. Adjusting Width and Height You can adjust the size of the topology representation using the buttons for height and width. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 65...
  • Page 66 Contracts legend located at the bottom of the Topology page also indicates how the types of contracts and links are represented. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 66...
  • Page 67 Contract details section at the bottom of the page. The contract information includes the following parameters: • Contract ID – the contract identifier based on the contract owner; • Service Type – can be periodic or aperiodic; Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 67...

  • Page 68: Devices

    The Devices page features the list of devices that exist in the network, and a search form that enables you to search devices based on their EUI-64 address, tag and/or state, as shown in the following screen capture (Figure 6.2.5): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 68...

  • Page 69: Search Devices

    To search for devices based on their tag, type the tag in the Device Tag input field, and click Search. Note that the tag field is case sensitive. To delete the search parameters, click Reset. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 69...

  • Page 70: Device List

    In the Devices page you have the option of deleting an unregistered device. When you delete a device, it will be removed from the network and any related data, including previous readings, will be deleted from the database. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 70...

  • Page 71: Device Details

    DPDUs – data transmission statistics, the number of transmitted/received packages and the number of failed transmissions/receptions; • Process values – the parameters measured by the device. The Information window for the device is shown in the following screen capture (Figure 6.2.6): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 71...
  • Page 72 The default number of items displayed in a page is 10. Paging controls in the top right corner of the table also enable you to navigate through the other pages of the table. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 72...

  • Page 73: Settings

    The Signal Quality column displays the received signal quality indicator (RSQI) values and their associated labels, as shown in the following table (Table 6.1): Table 6.1 Signal Quality for Received Signal Quality Indicator (ISA 100) RSQI Signal Quality Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 73...
  • Page 74 2, the selector field indicates the address of the destination device; o if the alternative is 3, the selector is null. • Forward Limit – the maximum number of nodes that a route can include; Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 74...

  • Page 75: Registration Log

    SEC_CNFRM_Rsp – the security join confirmation response was sent to the device; • FULL_JOIN – the device is joined and configured and all information about it is available; • NOT_JOINED – the device is not joined. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 75...

  • Page 76: Neighbors Health

    The default number of items displayed in a page is 10. Paging controls in the top right corner of the table also enable you to navigate through the other pages of the table. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 76...

  • Page 77: Schedule Report

    Clicking on the number of Links will display a new page with link related information for each individual link allocated on the selected superframe, as shown in the following screen capture (Figure 6.2.11): Figure 6.2.11 Link's related information window (ISA 100) Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 77...

  • Page 78: Channel Statistics

    Channel 26 has been disabled by default for purposes of compliance in certain countries. 6.2.4.6 Channel Statistics The Channel Statistics page displays statistical information about CCA backoffs per channel, as shown in the following screen capture (Figure 6.2.12): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 78...

  • Page 79: Run Commands

    To go to a specific command, select it from the Commands drop-down list. After you generate the command, a message at the bottom of the screen will indicate its status (Command sent successfully, Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 79...

  • Page 80: Read Value

    In the following screen capture (Figure 6.2.15) is displayed the Reset Device window with the Restart Types available: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 80...

  • Page 81: Read Object Attribute

    Execute. Note that the values of the two indices are 0 by default and the value of the Committed Burst field is -15 by default. In the following screen capture (Figure 6.2.16) is displayed the Read Object Attribute window: Figure 6.2.16 Read Object Attribute window (ISA 100) Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 81...

  • Page 82: Write Object Attribute

    The Execute Object Method command is used to execute a network visible method on an object on the selected device. In the following screen capture (Figure 6.2.18) is displayed the Execute Object Method window: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 82...

  • Page 83: Network Health

    (Figure 6.2.19): Figure 6.2.19 Network Health sections (ISA 100) In the network summary section, the following information is indicated: • Network ID and Network Type – network identification data (where applicable); Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 83...

  • Page 84: Readings

    Read Value commands or by automatic Publish/Subscribe commands. The readings can be filtered by Device, Process Value, or Reading Type (Publish/Subscribe or On Demand), as shown in the following screen capture (Figure 6.2.20): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 84...

  • Page 85: Commands Log

    The commands can be filtered by Device, Command (type), or Command Status (New-command posted in database, Sent-command sent to device, Responded-device responded successfully to the command, Failed-command failed to execute). These options are depicted in the following screen capture (Figure 6.2.21): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 85...
  • Page 86 If the length of the response exceeds the size of the Response cell, click on the response link to open the Tracking Response form and view the full response, as shown in the following screen capture (Figure 6.2.22): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 86...

  • Page 87: Alerts

    Alerts consist in application messages that advise or warn the recipient of the presence of an impending or existing situation of interest. In the following screen capture (Figure 6.2.23) is shown the Alerts window: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 87...
  • Page 88 • Priority – indicates the importance of the alert, with the following ranges and associated labels, in compliance with the specification: o 0 - 2: Journal-only; o 3 - 5: Low; Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 88...

  • Page 89: Troubleshooting

    EUI-64 by default; • Timestamp – the date and time when the alert was generated; • Event – the alert type (please see the Section 6.2.9.1.). Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 89...

  • Page 90: Filters

    The Edit filters button allows you to define the filters to apply for displaying the alerts. Click the button to expand the upper section of the page, as shown in the following screen capture (Figure 6.2.25): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 90...

  • Page 91: Table 6.3 Troubleshooting Alerts-Mapping (Isa 100)

    1: Timeout (device does not respond to SM queries) warning 2: Re-join (new join request while joining) warning 3: Parent left the network during device join warning 8: Insufficient parent resources - will retry join trough another router warning Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 91...

  • Page 92: Bulk Transfers

    6.2.10 Bulk Transfers The Bulk Transfers page enables you to monitor the status of configured bulk transfers. In the following screen capture (Figure 6.2.26) is shown the Bulk Transfers Status window: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 92...
  • Page 93 Started On - the date and time the bulk transfer operation started; • Data – only for a completed transfer, click the View link to see the transferred data in hex format, as shown in the following screen capture (Figure 6.2.27): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 93...

  • Page 94: Set Country Code

    Country Code from the dropdown list and click Execute. If necessary, you can filter the device list by EIU-64 Address, Device Tag or by Revision, as shown in the following screen capture (Figure 6.2.28): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 94...

  • Page 95: Configuration

    Single Join Key (a hexadecimal value of 32 characters). After changing either values, a Hardware Restart is needed. The same join key must be provided to field devices in the provisioning phase (using FieldTool). Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 95...

  • Page 96: Backbone Router

    (Figure 6.3.2): Figure 6.3.2 Backbone Router configuration sections (ISA 100) • In the General Settings section, you must perform the following action: o specify the EUI64 address and the BBR Tag. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 96...

  • Page 97: Gateway

    BBR may need to be restarted for the changes to take effect. 6.3.3 Gateway The Gateway configuration page consists of 3 sections, as shown is the following screen capture (Figure 6.3.3): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 97...

  • Page 98: System Manager

    Gateway may need to be restarted for the changes to take effect. 6.3.4 System Manager The System Manager configuration page consists of 3 sections, as shown in the following screen capture (Figure 6.3.4): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 98...
  • Page 99 Device Timeout Interval (s) – 120 seconds, integer in range [60-65535]; timeout in seconds used by SM to detect that a device is down; Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 99...

  • Page 100: Device Management

    Click Help in the upper right corner of the window to view information and examples of the accepted data formats in all the sections. In the following screen capture (Figure 6.3.5) is shown the Device Management window: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 100...

  • Page 101: Configuring Backbones

    Save. The new BBR will be added to the backbones list. Editing a BBR To edit a BBR you must perform the following actions: 1. click on the entry that you want to edit in the backbones list; Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 101...

  • Page 102: Configuring Gateways

    After you perform any of the above operations, click Activate to load the changes into the SM. The changes will be visible in the network topology and, where applicable, in the device list. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 102...

  • Page 103: Configuring Devices

    4. if you add the Role for a range of devices, all the devices in question will have the same role; if any device in the range does not support the assigned role, the device will not join the network. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 103...

  • Page 104: Configuring A Subnet

    The Monitoring Host page enables you to configure the devices publishing settings stored in the Monitor_Host_Publishers.conf file. Click Help in the upper right corner of the window to view information and examples of the accepted data formats in all sections. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 104...

  • Page 105: Publishers

    2. click Save; the publisher will be added to the list and the changes will be saved in the Monitoring Host Configuration file. 3. add the process values to be published, by following the steps described under the Section 6.3.7.2. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 105...

  • Page 106: Channels

    Help form: TSAP ID, object ID, attribute ID, index1, index2, format, name, unit of measurement, and withstatus; 2. click Save; the channel will be added to the channels list for that specific publisher and the changes will be saved in the Monitoring Host Configuration file. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 106...

  • Page 107: Autodiscover Publishers

    The auto discover process will also be triggered upon receiving a different DATA_CONTENTVERSION than the one already known for a publisher, or by clicking Rediscover All Publishers button. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 107...
  • Page 108 Do not edit the Publisher list or Channels list while Autodiscover publishers is active. We recommend using Autodiscover publishers and Auto Activate to automate the process and avoid inconsistencies. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 108...

  • Page 109: Modbus

    Please note that mapping read-only attributes to holding registers will not make the attributes themselves writable. Adding a register line To add a register line, you must perform the following actions: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 109...
  • Page 110 In the above input register line, the analog process value is 1 byte data status + 4 bytes data. When mapping to Modbus registers, three words will be needed, as follows: o First word: 0x00 + data status in PV; o Second word: data in PV (upper); Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 110...
  • Page 111 2. click Activate, to load the new host list into Modbus; the current Modbus_gw.ini file will be overwritten. Exporting the Registers This page also enables to export the registers, by clicking Save in the Manage Host list section. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 111...

  • Page 112: Alert Subscription

    Figure 6.3.9 Section/variables window (ISA 100) These settings include the settings under the Backbone Router (see the Section 6.3.1.), Gateway (see the Section 6.3.3.) and System Manager (see the Section 6.3.4.) configuration sections. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 112...

  • Page 113: Restart/Stop

    6.3.10.3 VR950 Settings The VR950 Settings page enables you to change the network settings for the VR950. In the following screen capture (Figure 6.3.11) is displayed the VR950 Settings window: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 113...

  • Page 114: Bulk Transfers

    ISA running on top of UDO; • a CDS enhanced bulk data transfer protocol. For details about the two methods, see the document entitled: 96-00006-01 ISA100.11a GSAP Interface Specification. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 114...

  • Page 115: Adding A Bulk Transfer

    1. click the Add Bulk Transfer button; the Add form will be displayed as shown in the following screen captures (Figure 6.3.13 and Figure 6.3.14): Figure 6.3.13 Adding a Bulk Transfer window-UDO option (ISA 100) Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 115...

  • Page 116: Editing A Bulk Transfer

    EUI-64 address, in the Bulk Transfers list; the Edit form will be displayed as shown in the following screen captures (Figure 6.3.15 and Figure 6.3.16): Figure 6.3.15 Editing a Bulk Transfer window-UDO option (ISA 100) Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 116...

  • Page 117: System Status

    The Statistics page displays statistical information regarding processor and memory usage, and load average on the VR950. In the following screen capture (Figure 6.3.17) are shown the section of the Statistic page: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 117...

  • Page 118: Administration

    The Device Firmware page is dedicated to FW updates for field devices and the BBR. FW updates require technical expertise and must be planned carefully, or the devices will be unable to communicate on the Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 118...
  • Page 119 100%; • Avg Speed – the average transmission speed, calculated in packets (messages) per minute, since the beginning of the transfer; Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 119...

  • Page 120: Updating The Firmware

    To access the commands page, you must click Execute in the Device Firmware page. You will navigate to the Firmware Update page displayed in the following screen capture (Figure 6.4.2): Figure 6.4.2 Firmware Update window (ISA 100) Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 120...

  • Page 121: Canceling A Firmware Update

    To cancel an ongoing firmware update, go to the Device Firmware page. In the table displaying the ongoing operations click the icon located next to the operation you wish to delete. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 121...

  • Page 122: Firmware Files

    1. click the Upload in the Firmware files page; you will navigate to the FW details page, where the Add Firmware dialog window will open, as shown in the following screen capture (Figure 6.4.4): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 122...

  • Page 123: Editing A Firmware File

    To edit the description of a Firmware file you must perform the following actions: 1. click on the desired file in the list; the Edit Firmware dialog window will open, as shown in the following screen capture (Figure 6.4.5): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 123...

  • Page 124: System Upgrade

    2. click Start to initiate the process; 3. when the upgrade is complete, a log is displayed in the page, indicating the result of the upgrade, as shown in the following screen capture (Figure 6.4.7): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 124...

  • Page 125: Custom Icons

    To add an icon, you must perform the following actions: 1. click the Add Icon button; the Custom icon window will open, as shown in the following screen capture (Figure 6.4.8): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 125...
  • Page 126 2. you will be asked for confirmation; click OK to delete the icon or Cancel to abort the action. Note: When you delete an icon, it will be automatically replaced with the default icon for the selected device model/role in the Topology and Devices pages. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 126...

  • Page 127: Custom Settings

    4. Click Save at the bottom of the page to save the new password, which will become your current password. In the following screen capture (Figure 6.5.1) is shown the Change Password window: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 127...
  • Page 128 Figure 6.5.1 Change password window Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 128...

  • Page 129: Using The Monitoring Control System (Mcs) For Wireless Hart Network

    (Figure 7.1.2). For a detailed description of the Device list, please see the Section 7.2.3. The Monitoring Control System page with the Device list is shown in the following screen capture (Figure 7.1.2): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 129...

  • Page 130: Network

    The information is refreshed automatically at regular intervals (10 seconds, 30 seconds, or 1 minute). The Dashboard series of panes are shown in the following screen capture (Figure 7.2.1): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 130...

  • Page 131: Adding A Device To The Dashboard

    5. optionally, select the slot number (up to the current slot number); if you do not select a slot number, the system automatically assigns the next available slot; Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 131...

  • Page 132: Deleting A Device

    The registered devices are displayed on multiple levels represented as grey bands. The levels are numbered from 0 to n, where n is a natural number. The level number is indicated in the upper left Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 132...
  • Page 133 Links To show the links between devices, check the Links option located above the topology graph (this option is checked by default when the page is loaded). Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 133...
  • Page 134 Note: A device can have multiple services with the same NM or GW at the same time. The graphical representation of the Services for a selected device is shown in the following screen capture (Figure 7.2.4): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 134...

  • Page 135: Devices

    The Devices page features the list of devices that exist in the network and a search form that enables you to search devices based on their EUI-64 address, tag, and/or state, as shown in the following screen capture (Figure 7.2.5): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 135...

  • Page 136: Search Devices

    One tag can be assigned to a single device. To search for devices based on their tag, type the tag in the Device Tag input field, and click Search. Note that the tag field is case sensitive. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 136...

  • Page 137: Device List

    In this page you can see all the information available for the selected device and perform device-specific commands. The page is accessed by clicking on the device EUI-64 Address in the device list. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 137...

  • Page 138: Information

    Wireless HART network and caching the data reported by devices. The information about defined burst messages is displayed in a table with the following related information: • Name – a user friendly name assigned to the published variable; Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 138...

  • Page 139: Settings

    The settings reflect the current operation of the CDS Wireless HART stack on a device. The type of information displayed in this pane includes service, neighbor, route, and graph details, as shown in the following screen capture (Figure 7.2.7): Figure 7.2.7 Settings window (HART) Services Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 139...
  • Page 140 Source Routes, and Request Services commands will be sent to the NM. To view the command status, go Section 7.2.7. When the command is generated, a message at the top of the screen will indicate that the device information is refreshing. Graphs Neighbors Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 140...

  • Page 141: Registration Log

    7.2.4.4 Neighbors Health The Neighbors Health page provides a communication health report about the selected device’s neighbors. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 141...

  • Page 142: Schedule Report

    7.2.4.5 Schedule Report The Schedule Report page provides information about time slot and channel allocation for the selected device. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 142...
  • Page 143 Clicking on the number of links, will be display a new page with information for each individual link allocated on the selected superframe, as shown in the following screen capture (Figure 7.2.11): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 143...

  • Page 144: Run Commands

    7.2.4.6 Run Commands This Run Commands page enables you to execute device-specific commands on registered devices. In the following screen capture (Figure 7.2.12) is displayed the Run Commands window: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 144...

  • Page 145: Wh General Command

    (Command sent successfully, Command sent error); the tracking number of the command is also indicated, together with a link to the Commands Log, where you can view the response. In the following screen capture (Figure 7.2.13) is displayed the WH General Command window: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 145...

  • Page 146: Network Health

    The Network Health page provides a communication health report at network level. The page consists of two sections containing network summary statistics and device-specific communication health information, respectively, as shown in the following screen capture (Figure 7.2.15): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 146...
  • Page 147 All Tx – all the packets transmitted but the selected device (including for routing purposes); • No ACK – the number of packets that require acknowledgement and which were sent by the selected device but not acknowledged by the destination device; Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 147...

  • Page 148: Readings

    Value - the value received on that reading (shown in engineering values); • Classification - the type of variable (e.g. 64 - temperature); please consult the Wireless HART Common Table No. 21 for a comprehensive list of variables and associated classification codes; Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 148...

  • Page 149: Commands Log

    WH General Command: two bytes representing the command code, followed by one byte representing § the command return code, followed by a hex value representing the response payload (if any). Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 149...

  • Page 150: Alerts

    To search for alerts you must perform the following actions: • select the device, the alert category, priority and type (class) of alert, • Optionally, fill in the Start Time and the End Time fields, and then click Search. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 150...

  • Page 151: Configuration

    Note that the changes you perform in the settings for each separate entity will also be reflected in the Advanced Settings page and vice-versa. 7.3.1 Access Point The Access Point configuration page consists of 4 sections, as shown in the following screen capture (Figure 7.3.1): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 151...
  • Page 152 AP logs, as follows: 1 (ERROR) for error messages only; 2 (WARN) for error and warning messages; 3 (DEBUG) for error, warning and debug messages. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 152...

  • Page 153: Gateway

    Select the application and stack logging level; the numbers suggest the degree of detail provided in the GW logs, as follows: 1 (ERROR) for error messages only, 2 (WARN) for error and warning messages, Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 153...

  • Page 154: Network Manager

    Enable/Disable Compatibility Mode for the old Emerson devices starting with revision 2; o Enable/Disable Dynamic Management Bandwidth for the NM to dynamically adjust devices bandwidth. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 154...

  • Page 155: Device Management

    Click Help in the upper right corner of the window to view information and examples of the accepted data formats in all the sections. In the following screen capture (Figure 7.3.4) is shown the Device Management window: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 155...
  • Page 156 When adding a device, you have the possibility to select whether the Join Key is unique per network or per device. If the Join Key is unique per network, any device that has the correct key provisioned, regardless of its network address, will join the network. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 156...

  • Page 157: Configuring Access Points

    To delete an Access Point you must perform the following actions: select the desired Access Point in the list and click Delete; you will be asked for confirmation; click Yes to delete the AP or No to abort the action. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 157...

  • Page 158: Multiple Access Points

    2. edit the security key and/or network ID; 3. click Save to save the changes in the whart_provisioning.ini file. Deleting a device/multiple devices To delete a device/multiple devices you must perform the following actions: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 158...

  • Page 159: Monitoring Host

    Click Help in the upper right corner of the window to view information and examples of the accepted data formats in all the sections. In the following screen capture (Figure 7.3.6) is displayed the Device Management window: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 159...

  • Page 160: Burst Messages

    1/32 ms not exceed 3600s as configured through command 103; Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 160...

  • Page 161: Variables

    Command 4; required for commands 3, 9 and 33). The command number and burst message index are the same as those used in the burst message definition and are not editable in the interface; Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 161...

  • Page 162: Triggers

    1. In the trigger edit box, edit the desired parameters and click Save. The changes will be stored in the Monitor_Host_Publishers.conf” file. Deleting a trigger To delete a trigger, you must perform the following actions: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 162...

  • Page 163: Modbus

    Click Help in the upper right corner of the window to view information and examples of the accepted data formats in all the sections. In the following screen capture (Figure 7.3.7) is displayed the Modbus Server window: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 163...

  • Page 164: Mapping Registers

    Adding a register line To add a register line, you must perform the following actions: in an empty edit box, type the parameters in the order and format indicated in the Help form: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 164...

  • Page 165: Table 7.2 General Gw Information (Hart)

    When register type is gw_code_word, the gateway’s code word will be exposed to Modbus; The code word is read-only. Note: For register type gw_code_word, the <word_cnt> should be 16 or less. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 165...

  • Page 166: Advanced Settings

    This Sections/variables page enables you to change various configuration sections for applications running on VR950. These settings include the settings under the Access Point, Gateway, and Network Manager configuration sections. In the following screen capture (Figure 7.3.8) is displayed the Sections/variables window: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 166...

  • Page 167: Restart

    Note: When you restart any of the applications, the VR950 Monitoring Control System becomes inoperative for a few minutes. In the following screen capture (Figure 7.3.9) is displayed the Restart window: Figure 7.3.9 Restart window (HART) Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 167...

  • Page 168: Vr910 Settings

    The System Status page displays statistical information regarding processor and memory usage, and load average on the VR910. In the following screen capture (Figure 7.4.1) are shown the section of the Statistic page: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 168...
  • Page 169 The first five sections indicate the status (Running or Not Running), memory usage and processor usage for the Access Point, Gateway, Network Manager, Modbus, and Monitor Host processes. The following two sections display system memory and flash memory availability information. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 169...

  • Page 170: Administration

    Start to initiate the process; when the upgrade is complete, a log is displayed in the page, indicating the result of the upgrade, as shown in the following screen capture (Figure 7.5.2): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 170...

  • Page 171: Custom Icons

    Adding an icon To add an icon, you must perform the following actions: click the Add Icon button; the Custom Icon window will open, as shown in the following screen capture (Figure 7.5.3): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 171...
  • Page 172 OK to delete the icon or Cancel to abort the action. Note: When you delete an icon, it will be automatically replaced with the default icon for the selected device model/role in the Topology and Devices pages. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 172...

  • Page 173: Custom Settings

    • Model – the device model (name) as given by the vendor; • Company – the device vendor. In the following screen capture (Figure 7.5.6) is shown the Device Codes window: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 173...

  • Page 174: Adding A Device Code

    1. click the Add Device Code button located on top of the search form; the Add Device Code form will open; In the following screen capture (Figure 7.5.7) is shown the Add Device Code window: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 174...

  • Page 175: Editing A Device Code

    The system will require confirmation to perform the action. Click OK to delete the device code or Cancel to abort the action. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 175...

  • Page 176: Session

    Save at the bottom of the page to save the new password, which will become your current password. In the following screen capture (Figure 7.6.1) is shown the Change password window: Figure 7.6.1 Change password window (HART) Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 176...

  • Page 177: Web-Based Administration /Admin

    Figure 8.1.1 Login window 2. type the following credentials in the input fields: • User: admin • Password: adminadmin 3. click Login. The following screen appears, allowing access to various tasks (Figure 8.1.2): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 177...

  • Page 178: System Upgrade

    The radio FW (including the BBR), however, are backwards compatible with all releases. For this reason, the radio FW versions are not linked by the release number. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 178...

  • Page 179: Versa Router Firmware

    During the upgrade, the process log is displayed. When the operation is complete, the screen should look as shown in the following capture (Figure 8.2.2): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 179...

  • Page 180: Isa Transceiver Firmware

    1. click ISA TR Firmware and the following screen will appears (Figure 8.2.3): Figure 8.2.3 ISA Transceiver Firmware Upgrade window 2. in the dialog that appears, click Browse to locate and select the transceiver firmware file, then click Load; Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 180...

  • Page 181: Whart Tr Firmware

    8.2.3 WHart TR Firmware In order to upgrade the VR ISA radio transceiver firmware, you must perform the following actions: 1. click WHart TR Firmware and the following screen will appears (Figure 8.2.5): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 181...
  • Page 182 During the upload, the process log is displayed. When the operation is complete, the screen should look as shown below (Figure 8.2.6): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 182...

  • Page 183: Versa Router Application Website (Monitoring Control System)

    8.2.4 Versa Router Application Website (Monitoring Control System) In order to upgrade the MCS website, you must perform the following actions: 1. click Application Website and the following screen will appears (Figure 8.2.7): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 183...
  • Page 184 3. during the upgrade, the process log is displayed; when the operation is complete, the screen should look as shown in the following screen capture (Figure 8.2.8): Figure 8.2.8 Completed operation window for Application Website Upgrade Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 184...

  • Page 185: Configuration

    If the publish rate is aggressive, the result may be exceeding the available storage, or even flash corruption. We do not recommend using it on a VR production. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 185...

  • Page 186: Reset Profile

    Note: Do not change [GLOBAL].AN_ID under any circumstance. For adding a new variable, please select Custom near Variable type; the form will be empty, as shown in the following screen capture (Figure 8.3.3): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 186...

  • Page 187: Network

    • check the Update MAC option to enable the MAC edit field; • type the new MAC; • optionally, uncheck the Update MAC option to protect the field from being accidentally edited. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 187...

  • Page 188: Command-Line Configuration Interface

    10 minutes of inactivity. 9.1 Change Versa Router IP Address To change the IP of the VR to an IP in the destination network, you must type the following commands: CFG>ipconfig address <ip_val> Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 188...

  • Page 189: Udp/Tcp Port Configuration

    The default port for the Backbone Router is 20093 (in decimal). • To change the UDP/TCP port of the GW to a new port, you must type the following commands: Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 189...

  • Page 190: Accessing Files Through Command-Line Interface

    The configuration interface can be used regardless of the IP/mask/gateway settings of the VR or PC running the Configurator. The only requirement is that the two machines to be in the same LAN. Upon start, the Configurator submits the following window (Figure 10.1.1): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 190...
  • Page 191 Click the Search Network for VersaRouters button to broadcast a request in the LAN, to which all VRs will respond. The responses are shown in the top list, as shown in the following screen capture (Figure 10.1.2): Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 191...
  • Page 192 You can select one of the VR in the list and use the Set VersaRouter Properties button to change the IP, Mask and Default Gateway properties of the selected VR, as shown in the following screen capture (Figure 10.1.3). You should enter these exactly as directed by your network administrator. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 192...
  • Page 193 4. the IP address bitwise AND-ed with the one’s complement of the mask must be neither 0 nor the one’s complement of the mask; 5. the Gateway address bitwise AND-ed with the one’s complement of the mask must be neither 0 nor the one’s complement of the mask. Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 193...

  • Page 194: Appendix A - Country Codes

    VGB - VIRGIN ISLANDS, BRITISH BRN - BRUNEI DARUSSALAM BGR - BULGARIA MMR - MYANMAR (formerly Burma) BDI - BURUNDI BLR - BELARUS KHM - CAMBODIA CMR - CAMEROON CAN - CANADA Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 194...
  • Page 195 SGS - SOUTH GEORGIA AND THE SOUTH SANDWICH ISLANDS FJI - FIJI FIN - FINLAND ALA - ÅLAND ISLANDS FRA - FRANCE GUF - FRENCH GUIANA PYF - FRENCH POLYNESIA ATF - FRENCH SOUTHERN TERRITORIES Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 195...
  • Page 196 JOR - JORDAN (Hashemite Kingdom of Jordan) KEN - KENYA PRK - KOREA (Democratic People’s Republic of [North] Korea) KOR - KOREA (Republic of [South] Korea) KWT - KUWAIT KGZ - KYRGYZSTAN Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 196...
  • Page 197 CUW - CURAÇAO ABW - ARUBA SXM - SINT MAARTEN BES - BONAIRE, ST. EUSTATIUS, AND SABA NCL - NEW CALEDONIA VUT - VANUATU NZL - NEW ZEALAND NIC - NICARAGUA Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 197...
  • Page 198 SMR - SAN MARINO (Republic of) STP - SAO TOME AND PRINCIPE SAU - SAUDI ARABIA (Kingdom of Saudi Arabia) SEN - SENEGAL SRB - SERBIA (Republic of Serbia) SYC - SEYCHELLES Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 198...
  • Page 199 GBR - GREAT BRITAIN (United Kingdom) GBR - UNITED KINGDOM - CHANNEL ISLANDS IMN - ISLE OF MAN TZA - TANZANIA USA - UNITED STATES VIR - VIRGIN ISLANDS, U.S. BFA - BURKINA FASO Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 199...
  • Page 200 YEM - YEMEN (Yemen Arab Republic) ZMB - ZAMBIA (formerly Northern Rhodesia) CDS custom code CDS custom code CDS custom code CDS custom code CDS custom code CDS custom code CDS custom code Ref.no.: 003274/Revision 2.4 @2019 Control Data Systems Page 200...

Table of Contents