RTA 460MRSWI-N2E Product User Manual
  1. Manuals
  2. Brands
  3. RTA Manuals
  4. Gateway
  5. 460MRSWI-N2E
  6. Product user manual

RTA 460MRSWI-N2E Product User Manual

Protocol gateway
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
460MRSWI-N2E
Protocol Gateway
Product User Guide
Firmware Version 8.7.22
Real Time Automation, Inc.
1
1-800-249-1612

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 460MRSWI-N2E and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for RTA 460MRSWI-N2E

Summary of Contents for RTA 460MRSWI-N2E

  • Page 1 460MRSWI-N2E Protocol Gateway Product User Guide Firmware Version 8.7.22 Real Time Automation, Inc. 1-800-249-1612...
  • Page 2 Trademarks CompactLogix, ControlLogix, & PLC-5 are registered trademarks of Rockwell Automation, Inc. EtherNet/IP is a trademark of the ODVA. MicroLogix, RSLogix 500, and SLC are trademarks of Rockwell Automation, Inc. Microsoft, Windows, and Internet Explorer are registered ® trademarks of Microsoft Corporation. BACnet is a registered trademark of American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE).

  • Page 3: Table Of Contents

    Revision History ............................6 Overview ............................... 7 Hardware Platforms ............................8 Hardware – N2E ............................9 Powering the Gateway ..........................9 Port Configuration ........................... 11 RS232 pinouts: ............................11 RS485 pinouts: ............................11 RS422 pinouts: ............................12 Mounting with a DIN Rail ..........................13 Installing ..............................
  • Page 4 Group by Device (Default Method) ......................32 Group by Data Type ..........................32 Web Interface Data Point List Configuration: Manual Mode ..............33 Configuring Read and Write Data Points ....................33 Web Interface Group Configuration ....................... 35 Requirements for Device and Group Names: ..................37 Web Interface: XML/JSON Data Format .....................
  • Page 5 String Mapping – Explanation ........................64 Mapping – Auto-Configure Mode to Manual Configure Mode ..............65 Mapping – Manual Configure Mode to Auto-Configure Mode ..............66 View as Text ..............................67 Data Mapping ............................67 String Mapping ............................67 Base Triggering – Data Validiation Triggering ..................68 Security Configuration ..........................

  • Page 6: Revision History

    Revision History Version Date Notes 8.4.5 11/18/2019 Features Added 1. Released OPC UA Server (US) Protocol 2. Ability to now Import/Export Template Files with out an FTP session. Bug Fixes 1. Updated Profinet Server (PS) on N34 hardware Platform 2. Updated Wi-Fi software 2/28/20 8.6.0 Bug Fixes...

  • Page 7: Overview

    Overview The 460MRSWI-N2E gateway connects a Modbus RTU Master with a Web Interface. By following this guide, you will be able to configure the 460MRSWI-N2E gateway. For further customization and advanced use, please reference the appendices located on the CD or online at: http://www.rtautomation.com/product/460-gateway-support/.

  • Page 8: Hardware Platforms

    Hardware Platforms The 460 Product Line supports a number of different hardware platforms. There are differences in how they are powered, what serial settings are supported, and some diagnostic features supported (such as LEDs). For these sections, be sure to identify the hardware platform you are using. To find which hardware platform you are using: 1) Look on the front or back label of the unit for the part number.

  • Page 9: Hardware - N2E

    Hardware – N2E Powering the Gateway The following steps will allow you to properly and safely power the gateway. Warning: Improper wiring will cause unit failure! Use the Screw Terminal’s power connection! 1) Connect a 12-24 VDC power source to the gateway, Red Wire = (+) Black Wire = (-). a) The unit draws 8 VDC 900mA (7.2W) Max b) The unit draws 35 VDC 900mA (31.5W) Max c) The gateway has a voltage operating range from 8-35 VDC, 24 VDC is recommended.
  • Page 10 Hazardous Environment Power & Installation Instructions This equipment is suitable for use in Class I, Division 2, Groups A, B, C and D, or non-hazardous locations only. WARNING – EXPLOSION HAZARD - Do not disconnect equipment unless power has been removed or the area is known to be non-hazardous.

  • Page 11: Port Configuration

    Port Configuration The Port Configuration page is where you set port specific parameters. These settings must match the settings of the device(s) that you are connecting to. Only 1 mode can be configured for this hardware. Below are the wiring pinouts for each mode. When you have completed your port configuration, click the Save Parameters button.

  • Page 12: Rs422 Pinouts

    RS422 pinouts: Real Time Automation, Inc. 1-800-249-1612...

  • Page 13: Mounting With A Din Rail

    1) Mount your DIN Rail. 2) Hook the bottom mounting flange under the DIN Rail. 3) While pressing the 460MRSWI-N2E against the rail, press up to engage the spring loaded lower clip and rotate the unit parallel to the DIN Rail.

  • Page 14: Accessing The Main Page

    Accessing the Main Page The following steps will help you access the browser based configuration of the gateway. By default, DHCP is enabled. If the gateway fails to obtain an IP address over DHCP it will Auto IP with 169.254.X.Y. For more information on your Operating system network setting refer to the Access Browser Configuration Doc on the CD or download from our support web site.

  • Page 15: Error: Main Page Does Not Launch

    Error: Main Page Does Not Launch If the Main Page does not launch, please verify the following: 1) Check that the PC is set for a valid IP Address a. Open a MS-DOS Command Prompt b. Type “ipconfig” and press enter c.

  • Page 16: Committing Changes To The Settings

    Committing Changes to the Settings • All changes made to the settings of the gateway in Configuration Mode will not take effect until the gateway is restarted via the webpage. Changes will not be stored if the gateway’s power is removed prior to a reboot.

  • Page 17: Main Page

    Main Page The main page is where important information about your gateway and its connections are displayed. Mode (orange box below): Running Mode: Protocol communications are enabled Configuration cannot be changed during Running Mode. If changes are needed, click the Configuration Mode button shown in the green box below...

  • Page 18: Device Configuration

    Device Configuration The device configuration area is where you assign the device description parameter. Changes can only be made when the gateway is in Configuration Mode. Once you are done configuring the Description, click the Save Parameters button. Real Time Automation, Inc. 1-800-249-1612...

  • Page 19: Network Configuration

    Network Configuration The network configuration area is where you assign the IP address and other network parameters. Changes can only be made when the gateway is in Configuration Mode. Once you are done configuring the Network Settings, click the Save Parameters button. If you are changing the IP Address of the gateway, the change will not take effect until the unit has been rebooted.
  • Page 20 Network Interface Options The N2E hardware has two different Network Interface options, Independent and Switch Mode. Below, you can find the different use cases that each interface option allows for. Independent Mode 1) Two Ethernet-based protocols on the same IP Network a) Ethernet Port 1 used OR b) Ethernet Port 2 used OR c) Ethernet Port 1 &...

  • Page 21: Modbus Rtu Slave Configuration

    Modbus RTU Slave Configuration Click the Modbus RTU Slave button to access the configuration page. 1) Serial Port: Select which serial port is being used for communication. This port must be configured on the Port Configuration page. If it has not yet been configured, it will display Disabled after the Port descriptions in this dropdown.

  • Page 22: Modbus Rtu Slave Configuration-Data Groups

    Modbus RTU Slave Configuration-Data Groups The bottom area of the Modbus RTU Slave Configuration page lets you configure up to 100 data groups for both Read/Write. There are three ways to configure this protocol: 1) Auto-Configure Group by Device (Default) 2) Auto-Configure Group by Data Type 3) Manual Mode NOTE: You may go back and forth between modes, but when reverting from Manual Mode to either of...

  • Page 23: Auto-Configure Group By Device Vs. Auto-Configure Group By Data Type

    Auto-Configure Group by Device vs. Auto-Configure Group by Data Type There are two different methods for Auto-Configure: Group by Device or Group by Data Type. There are a couple of rules to keep in mind when using Auto-Configure Mode: 1) If the other protocol inside the gateway is a server, slave, or adapter protocol, then there are no differences between the Auto-Configure modes.

  • Page 24: Modbus Rtu Slave Data Group Configuration: Auto-Configure

    Modbus RTU Slave Data Group Configuration: Auto-Configure While in either of the two Auto-Configure modes, the # of Data Groups and the actual Data Groups themselves cannot be edited. Auto-Configure Mode looks at the other protocol and then configures the data groups to match.

  • Page 25: Modbus Rtu Slave Data Group Configuration: Manual Mode

    Modbus RTU Slave Data Group Configuration: Manual Mode 1) To transition from either of the two Auto-Configure modes to Manual Configure Mode, click the dropdown at the top of the Modbus RTU Slave Configuration page and select Manual Configure. a) When prompted, click OK to confirm mode change or Cancel to remain in Auto-Configure Mode. 2) Once OK is clicked, there are two options for how to proceed.

  • Page 26: Configure Read And Write Data Groups

    Configure Read and Write Data Groups Follow these steps to manually configure read data groups. 1) Select View Read or View Write Data Groups if not already selected. 2) Select a Point Type for each Scan Line. Options include: Coil Status, Input Status, Input Registers, and Holding Registers.

  • Page 27: Web Interface Configuration

    Web Interface Configuration Click the Web Interface button to access the configuration page. 1) Select which Network Interface to use for the web interface. 2) Enter a Device Label to identify the device within the gateway. 3) Inactivity Timeout: If the gateway has not received any messages within the entered time interval, in seconds, then the gateway will change the status of its connection to be “Idle”.

  • Page 28: Automatic Data Transfer To User Host (Used As A Web Client)

    Automatic Data Transfer to User Host (Used as a Web Client) This section configures the gateway when it is operating as a web client, uploading XML/JSON data cyclically to an external, user-operated web server. This feature is optional. Disable/Enable: If set to “Disable”, the gateway will operate only as a web server and will not initiate a connection with an external user-operated web server.

  • Page 29: Operation Mode

    Operation Mode Mark Data New on Change of State (COS) When data comes into the RTA gateway, it will be sent over to the matting protocol only if the data has a different value. Example for 460ETCWI Operator sends “HelloWorld”...

  • Page 30: Web Interface Data Point List Configuration

    Web Interface Data Point List Configuration The bottom area of the Web Interface Configuration page allows configuration of 1000 data points in each direction. NOTE: Due to the limited number of internal mappings inside the gateway, though each direction in the web interface may be configured for up to 1000 data points, there is an overall limit, between the read and write direction, of 1000 data points total.

  • Page 31: Web Interface Data Point List Configuration: Auto-Configure (Default)

    Web Interface Data Point List Configuration: Auto-Configure (Default) While in either of the two Auto-Configure Modes, the number of data points and the actual data points themselves cannot be edited. Auto-Configure Mode looks at the other protocol and then configures the data point list within the web interface to match.

  • Page 32: Auto-Configure Group By Device Vs. Auto-Configure Group By Data Type

    Auto-Configure Group by Device vs. Auto-Configure Group by Data Type There are two different methods for Auto-Configure: Group by Device or Group by Data Type. NOTE: When using Auto-Configure with the web interface, the difference between the two methods is subtle. The # of Read Data Points and the # of Write Data Points will be the same regardless of which Auto-Configure method is chosen.

  • Page 33: Web Interface Data Point List Configuration: Manual Mode

    Web Interface Data Point List Configuration: Manual Mode 1) To transition from either of the two Auto-Configure Modes to Manual Configure Mode, click the dropdown at the top of the Web Interface Configuration page and select Manual Configure. a) When prompted, click OK to confirm mode change or Cancel to remain in Auto-Configure Mode. 2) Once OK is clicked, there are two options on how to proceed: 3) To keep the data points that are already configured, press OK.
  • Page 34 1) The dropdowns next to Filter View By allow the data points table to be filtered so that only the data points assigned to a specific group or device are displayed. Reference the Web Interface Group Configuration for more explanation. a) To remove the applied filter, select All from the dropdown.

  • Page 35: Web Interface Group Configuration

    5) In addition, the name field will be highlighted in red and hovering the mouse on that error message gives information on why that name was “invalid”. See screenshot below: 6) Select a Type for each data point. The Auto-Configure method will choose the best data type for that point, but the user may modify.
  • Page 36 Below is an example of how someone would use this. Let’s say a building has 3 floors. You’re looking to monitor water temp from all boilers, runtime from all generators, air temp from AC’s and speed from the exhaust fans. The first image shows how you would configure the data points.

  • Page 37: Requirements For Device And Group Names

    Requirements for Device and Group Names: 1) Name must be unique on this page. a) A group name may not also be a device name. b) No two group names may be the same. c) No two device names may be the same. d) Reserved names of “DeviceName”, “GroupName”, “dataTimeStamp”, and “Diagnostics”...
  • Page 38 8) When done making changes, click the Save Parameters button. Real Time Automation, Inc. 1-800-249-1612...

  • Page 39: Web Interface: Xml/Json Data Format

    Web Interface: XML/JSON Data Format 1) XML – For simplicity, the web interface uses a “flat” XML encoding format. The root XML element is always <Devices> followed by one or more <Device> elements, which will in turn contain name-value pairs with the data relevant to that device. 2) JSON –...

  • Page 40: Requesting Data For An Individual Device

    Requesting Data for an Individual Device To request data for an individual device that you have configured within the gateway, you simply need to specify the way you would like the data for the device encoded as well as the name you supplied for it.
  • Page 41 Note that the string of data point names to filter by begins with a question-mark (‘?’) after the group name and each name is separated by an ampersand (‘&’). The ordering of the points’ names does not matter. Real Time Automation, Inc. 1-800-249-1612...

  • Page 42: Advanced (Optional Xml Data Direction Annotation)

    The format is the same if you are filtering within a specific device. For instance, to request the same points encoded as XML within a single Device named “Breaker1”, the URL to use would be: http://192.168.0.1/gateway/xml/device/Breaker1?Temperature&Tripped_State PECIAL ONSIDERATIONS WHEN ILTERING BY OINT AMES Normally if you make a request for a group or device name that does not exist, the...

  • Page 43: Description Of Format - Both Xml And Json

    Example Output Format (GET) This format is used when a <web server/web client> wants to read the data points configured in the gateway. We are outputting the data to <web server/web client> through a HTTP GET operation. NOTE: The gateway outputs both the read data points and the write data points configured. As an example, say the gateway is configured for two different breaker groups as shown below: Description of Format –...

  • Page 44: Xml Output

    XML Output The output to the request for http://IPADDRESS/gateway/xml will be like the following: <Devices> <Device> <GroupName>Breaker_Set_A</GroupName> <DeviceName>Breaker_1A</DeviceName> <dataTimeStamp>2016-07- 04T21:06:50</dataTimeStamp> <Power>237</Power> <Current>344</Current> </Device> <Device> <GroupName>Breaker_Set_A</GroupName> <DeviceName>Breaker_2A</DeviceName> <dataTimeStamp>2016-07- 04T21:06:50</dataTimeStamp> <Current_A>37502</Current_A> <Current_B>8296</Current_B> <Current_C>36446</Current_C> <Watts>1002</Watts> </Device> </Devices> JSON Output The output to the request for http://IPADDRESS/gateway/json will be like the following: "GroupName":...

  • Page 45: Writing Data To The Gateway

    Writing Data to the Gateway All data writes to the 460WI use the HTTP POST method. There are two primary ways through which you can post data to the 460WI. The first is using the application/x-www-form-urlencoded standard post format. The second method is to use the multipart-form data post format to post JSON or XML to the 460WI and is most easily thought of as simply uploading an XML or JSON file to the 460WI.
  • Page 46 your data, the name attribute you should use is WI460XMLData and if you are using JSON, the name attribute you should use is WI460JSONData . Your application, scripting language or library may also Real Time Automation, Inc. 1-800-249-1612...

  • Page 47: The Application/X-Www-Form-Urlencoded Method

    have a “filename” parameter or argument. This is ignored by the 460WI when processing an incoming POST. Additionally, it is important to use the correct URL when posting data to the Encoder using the multipart/form method. For XML, use the following URL: http://[Gateway’s IP]/gateway/xml For JSON, use the following URL:...

  • Page 48: Minimum Xml Input

    Example Input Format (POST) This format is used when an external web client writes XML/JSON data to the gateway through a HTTP POST operation. The input format is the same as the output format except that the GroupName and dataTimeStamp may be omitted. If they included, they are ignored. Important Notes: •...

  • Page 49: Special Note For Xml Strings

    <Devices> <Device> <DeviceName>Breaker</DeviceName> <Temperature>100</Temperature> </Device> <Device> <DeviceName>Drive</DeviceName> <Temperature_Cutoff>32</Temperature_Cutoff> <Torque>15.2</Torque> </Device> </Devices> Special Note for XML Strings There is an additional consideration when posting data points with the STRING data type. “Unsafe” XML characters, such as “<” and “&” that might appear in STRING data should be converted to their respective XML entity-references.

  • Page 50: Expanded Json Input

    Expanded JSON Input The following example is slightly more complicated and writes one data point to one device and two data points to a different device. Expanding on this pattern, it is possible to write to every writable data point of every device configured in the gateway with a single JSON write. "DeviceName": "Breaker", "Temperature": 100 "DeviceName": "Drive",...

  • Page 51: Mapping - Transferring Data Between Devices

    Mapping - Transferring Data Between Devices There are 5 ways to move data from one protocol to the other. You can combine any of the following options to customize your gateway as needed. Option 1 – Data Auto-Configure Mappings: The gateway will automatically take the data type (excluding strings) from one protocol and look for the same data type defined in the other protocol.

  • Page 52: Display Mapping And Values

    Display Mapping and Values The Display Data and Display String pages are where you can view the actual data for each mapping that is set up. Display Data Click the Display Data button to view how the data is mapped and what the values of each mapping are. Here you will see how each data point (excluding strings) is mapped.
  • Page 53 This page is very useful when verifying that all data is mapped somehow from one protocol to another. If a data point is not mapped, it will display on this page in a yellow highlighted box. The Display Data page will display up to 200 mappings per page, simply navigate to the next page for the additional mapping to display.
  • Page 54 To view the actual data mappings, click the Edit Mapping button. For more details, see the Data Mapping-Explanation section. To view the data mappings purely as text, click the View as Text button. For more details, see the View Data Mapping as Text section. Real Time Automation, Inc.

  • Page 55: Display String

    Display String Click the Display String button to view what the values of each Parsing and/or Concatenating strings are, you can also click on the Edit Mapping to view the mapping of each string. To view the source or destination groups from a string, click the dropdown menu to generate the information regarding that device.
  • Page 56 If there are values of “Data Not Valid “on this page, it indicates that the source has not been validated yet and no data is being sent to the destination. NOTE: You can view the whole string data by clicking on Diagnostics Info drop down and navigating to ASCII Diagnostics page.

  • Page 57: Display String Use Case

    Display String use case Sending a message of “RTA,Support,Rocks” from an ASCII device to the RTA unit. The ASCII Parsing Configuration would look like my example below. There are more detailed examples of what all the fields represent in the ASCII Parsing section.

  • Page 58: Data And String Mapping - Auto-Configure

    Data and String Mapping – Auto-Configure The Auto-Configure function looks at both protocols and will map the data between the two protocols as best as it can so that all data is mapped. Inputs of like data types will map to outputs of the other protocols like data types first.

  • Page 59: Data Mapping - Explanation

    Data Mapping – Explanation Below are the different parts that can be modified to make up a data mapping. 1) Enable (red box above): Check to enable mapping. If not checked, this mapping is skipped. 2) Source Field (yellow box above): a) Group - Select the data group you set up in the protocol config to use for this mapping.

  • Page 60: Data Mapping - Adding Diagnostic Information

    The gateway operates at 200 ticks per second. This equates to one tick every 5ms. Thus, mapping this to a destination will give easy confirmation of data flow without involving one of the two protocols. If data stops on the destination end, then the RTA is offline. Real Time Automation, Inc.
  • Page 61 4) XY_NetBmpStat a) If a protocol is a Client/Master, there is a Network Bitmap Status that is provided on the Diagnostics Info page under the Variables section. b) Since a Client/Master may be trying to communicate with multiple devices on the network, it may be beneficial to know if a Server/Slave device is down.
  • Page 62 5) Status_XY a) There are two Statuses provided, one for each protocol. This gives access to the overall status of that Protocol. Each Bit has its own meaning as follows: Common Status: 0x000000FF (bit 0-7)1 byte Hex: Bit Position: Decimal: Explanation: 0x00 if we are a Slave/Server...
  • Page 63 Non-Recoverable Faults 0xFF000000 (bit 24-31)4 byte Hex: Bit Position: Decimal: Explanation: 0x01 16,777,216 nonrecoverable fault – task fatal err 0x02 33,554,432 nonrecoverable fault – config missing 0x04 67,108,864 nonrecoverable fault – bad hardware port 0x08 134,217,728 nonrecoverable fault – config err 0x10 268,435,456 Configuration Mode...

  • Page 64: String Mapping - Explanation

    String Mapping – Explanation Below are the different parts that can be modified to make up a string mapping. String data types can only be mapped to other string data types. There is no manipulation that can be done on the string. 1) Enable (red box above): Check to enable mapping.

  • Page 65: Mapping - Auto-Configure Mode To Manual Configure Mode

    Mapping – Auto-Configure Mode to Manual Configure Mode To transition from Auto-Configure Mapping Mode to Manual Configure Mode, click the dropdown at the top of the Mapping Configuration page and select Manual Configure. After you click this button, you will be prompted to confirm if this is really what you want to do. Click OK to proceed to Manual Configure Mode or click Cancel to remain in Auto-Configure Mappings Mode.

  • Page 66: Mapping - Manual Configure Mode To Auto-Configure Mode

    Mapping – Manual Configure Mode to Auto-Configure Mode To transition from Manual Configure Mode to Auto-Configure Mapping Mode, click the dropdown menu at the top of the Mapping Configuration page and select Auto-Configure Mappings. Click OK to proceed to delete all current mappings and go back to Auto-Configure Mappings Mode. Click Cancel to keep all mappings and remain in Manual Configure Mode.

  • Page 67: View As Text

    View as Text Data Mapping The View as Text page displays the point to point mapping(s) you set up in the Data Mapping section. This will also display any manipulation(s) that are configured. Each line on this page will read as follows: ->...

  • Page 68: Base Triggering - Data Validiation Triggering

    Note: # is an internal reference to the Server/Slave number you are settings up. ex. RTA Server/Slave products can only be Trigger 1 and Handshake 1 since we are only 1 device. If RTA is a Master/Client, then you can have a Trigger# for each server/slave connected too.
  • Page 69 3) Within the Data Mapping page manually add 2 additional mappings. 4) The first mapping is going to be the Data Validation Triggering. AO21 will write to the RTA, MC Trigger 1 will mark data invalid. 5) The second mapping, the MC Handshake will increment that all data is validated and write to AI21 “all data is validated”.

  • Page 70: Security Configuration

    Security Configuration To setup security on the 460 gateway, navigate to Other->Security Configuration. You can configure Security for 3 administrators, 5 users, and 1 guest. THIS IS A TOTAL SECURITY FEATURE The security feature offers a way to password protect access to diagnostics and configuration on the network.

  • Page 71: Security Configuration-Security Levels

    Security Configuration-Security Levels Each webpage in the gateway can have a separate security level associated with it for each user. Security Levels: 1) Full Access: Capability to view and configure a web page. 2) View Access: Capability to view a web page, but cannot configure parameters. 3) No Access: No capability of viewing the web page and page will be removed from Navigation.

  • Page 72: Security - Log In

    Security - Log In Username: Name of the user to login. Password: Password of the user to login. Log In: If login is successful, the user will be redirected to the Main Page. Send Password to Email: Sends the specified User’s Password to the email configured for that user. Display Hint: Displays the hint specified for the User if one was set up.

  • Page 73: Email Configuration

    Email Configuration To setup e-mails on the 460 gateway, navigate to Other->Email Configuration. You can configure up to 10 email addresses. 1) SMTP Mail Username: The email address that the SMTP server has set up to use. 2) SMTP Mail Password: If authentication is required, enter the SMTP Server’s password (Optional). 3) SMTP Server: Enter the Name of the SMTP Server or the IP Address of the Server.

  • Page 74: Alarm Configuration

    Alarm Configuration To setup alarms on the 460 gateway, navigate to Other->Alarm Configuration. 1) Alarm Delay upon Powerup: At Powerup, the gateway will have values of ‘0’ stored for all data. This may cause alarms to trigger before these values are updated by the mating protocols. Set this field to provide needed time to update fields before considering values for alarms.
  • Page 75 5) In the Clear Error Section: a. Select the Clear Error Operation. Available options are <, >, <=, >=, !=, ==, and Change of State (COS). This is the operation that will be used to compare the Data Point value against the Error Value to determine if the alarm needs to be cleared.

  • Page 76: Diagnostics - Alarm Status

    Diagnostics – Alarm Status Alarm Status will only display under the Diagnostic menu tab if at least 1 Alarm is enabled. 1) # Alarms Enabled: This is a count of enabled alarms. 2) # Alarms Active: This is how many alarms are presently active (set). 3) Last Active Alarm: This is the last alarm that the gateway detected.

  • Page 77: Alarms - Clear

    5) Last Active Alarm field will be populated with details on what triggered the alarm. Alarms – Clear When an alarm is cleared, the following will occur: 1) A one-time notification will be sent to the email associated with the alarm. a.

  • Page 78: Change Of State (Cos) Configuration

    Change of State (COS) Configuration To access the configuration files in the 460 gateway, navigate to dropdown Other->COS Configuration. The gateway, by default only writes when data has changed. The gateway also waits to write any data to the destination until the source protocol is successfully connected. Default values should fit most applications.

  • Page 79: Diagnostics Info

    Diagnostics Info The Diagnostics page is where you can view both protocols’ diagnostics information, # of Data Mappings, # of String Mapping and # Alarm Mappings. For protocol specific diagnostic information, refer to the next few pages. Diagnostics Mapping This section displays the number of mappings that are enabled, Data Mapping and String Mapping will show the # of Errors and First Errors.

  • Page 80: Diagnostics - Modbus Rtu Slave

    Diagnostics – Modbus RTU Slave Select the Modbus RTU Slave in the dropdown menu on the Diagnostics Page. Additional diagnostic information can be found by clicking the Help button. NOTE: This page will auto-refresh every five seconds with the latest data. Clear All Values - This will only affect displayed values.
  • Page 81 LED Status: 1) Connected and Running (Solid Green) – The gateway is connected to a Modbus RTU master and communicating as expected. 2) Not Connected (Flashing Green) – The gateway has never been connected to a Modbus RTU master. 3) Fatal Error (Solid Red) – The port configured does not match the port configured within the Modbus RTU configuration page.
  • Page 82 7) FC15 Force Multiple Coils – Modbus Function Code 15: Number of Write Multiple Coil Status requests received. 8) FC16 Preset Multiple Registers – Modbus Function Code 16: Number of Write Multiple Holding Register requests received. 9) FC23 Read/Write 4X Register – Modbus Function Code 23: Number of Read/Write Holding Registers requests received.

  • Page 83: Diagnostics - Web Interface

    Diagnostics – Web Interface Select Web Interface in the top dropdown menu on the Diagnostics Page to view a breakdown of the diagnostics that are displayed on the page. NOTE: This page will automatically refresh every five seconds with the latest data. Clear All Values - This will only affect displayed values.
  • Page 84 Variables 1) Successful GET (200 OK): a) Number of successfully serviced HTTP GET requests. In the case of a GET using a point name filter, at least one of the points in the list was found. 2) Successful POST (200 OK): a) Number of successfully serviced HTTP POST requests.
  • Page 85 Common Error Messages: The error message will alert if the message is for an XML or a JSON message. It will also indicate which line (x) and column (y) of the encoded data message contained the error and the reason why it triggered an error.

  • Page 86: Led Configuration

    LED Configuration To modify the behavior of the LEDs on the 460 gateway, navigate to Other->Setup LEDs. Each LED may be set to Disabled, Protocol 1, or Protocol 2. If either protocol is a master/client, you may set the LED to represent either all slaves/servers configured in the gateway or a slave/server device. To select a slave/server device: 1) Select the protocol in the left dropdown menu.

  • Page 87: Configuration Files

    Configuration Files To access the configuration file in the 460 gateway, select the dropdown Other->Export/Import Config. Export Configuration The Export Configuration allows you to save your configuration file for backup or to be imported into another gateway. This file is named rta_cfg.rtax by default. Upon clicking the Save Configuration to File button, you will be prompted to select a location to save the file.
  • Page 88 If it encountered an error while trying to load the saved configuration, the gateway will indicate the first error it found and a brief description about it under the Load Configuration button. Contact RTA Support with a screenshot of this error to further troubleshoot.

  • Page 89: Save And Replace Configuration Using Sd Card

    Save and Replace Configuration Using SD Card Saving Configuration Using SD Card This function saves the gateway’s configuration automatically to an SD Card each time the gateway is rebooted via the Restart Now button on the web page. If this unit should fail in the future, the last configuration stored on the SD card and can be used for a new gateway to get the application back up and running quickly.

  • Page 90: Intelligent Reset Button

    Intelligent Reset Button If the IP Address of the gateway is forgotten or is unknown, there is an easy way to recover the IP Address using a reset button on the hardware. 1) On the front of the gateway below the Power LED, there is a small pinhole. Using a paperclip, press the button through this pinhole and hold the button for at least 5 seconds.

  • Page 91: Utilities

    Utilities To access the Utilities page in the 460 gateway, navigate to Other->Utilities. The Utilities screen displays information about the gateway including Operation Time, File System Usage, Memory Usage, and Memory Block Usage. Here you can also: • View the full revision of the software. •...

Table of Contents