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

RTA 460MCWI-N2E Product User Manual

Protocol gateway
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
460MCWI-N2E
Protocol Gateway
Product User Guide
Firmware Version 6.1.15
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 460MCWI-N2E and is the answer not in the manual?

Questions and answers

Related Manuals for RTA 460MCWI-N2E

Summary of Contents for RTA 460MCWI-N2E

  • Page 1 460MCWI-N2E Protocol Gateway Product User Guide Firmware Version 6.1.15 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 Hardware Platforms ............................8 Hardware – N2E ............................9 Powering the Gateway ..........................9 Hardware Use Cases for the Gateway ....................10 Mounting with a DIN Rail ..........................11 Installing ..............................11 Removing ..............................11 Accessing the Main Page..........................12 Error: Main Page Does Not Launch ......................
  • Page 4 Basics ..............................34 Requesting Data for an Individual Device ................... 34 Requesting a Group of Devices ......................35 Filtering Requests by Point Names ..................... 35 Advanced (Optional XML Data Direction Annotation) ................ 36 Example Output Format (GET) ........................ 37 Description of Format – Both XML and JSON ..................37 XML Output ............................
  • Page 5 Security Configuration ..........................57 Security Configuration-Security Levels ....................58 Security - Log In ............................59 Security - Log Out ............................ 59 Email Configuration ............................ 60 Alarm Configuration ............................ 61 Diagnostics – Alarm Status ........................63 Alarms – Active ............................63 Alarms –...

  • Page 6: Revision History

    Revision History Version Date Notes 5.2.3 1/19/17 Bug Fixes 1. BACnet/IP Server (BS) COV (Change of Value) Notifications with Binary Objects (both Input and Output) 1/25/17 5.2.4 Bug Fixes 1. BACnet/IP Server (BS) COV (Change of Value) Notifications with Binary Output Objects 5.2.5 2/16/17 Bug Fixes...
  • Page 7 Overview The 460MCWI-N2E gateway connects up to 32 Modbus TCP Servers with a Web Interface. By following this guide, you will be able to configure the 460MCWI-N2E gateway. For further customization and advanced use, please reference the appendices located on the CD or online at: http://www.rtaautomation.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 • An 8-24 VDC power source to the gateway, Red Wire = (+) Black Wire = (-). a. The unit draws a maximum 500mA @ 12V. Real Time Automation, Inc. 1-800-249-1612...

  • Page 10: Hardware Use Cases For The Gateway

    Hardware Use Cases for the Gateway 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 • Two Ethernet based protocols on the same IP Network a.

  • Page 11: Mounting With A Din Rail

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

  • Page 12: 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. 1) Insert the provided CD-ROM into a computer also on the network.

  • Page 13: 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 14: 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 15: 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 Configuring Mode:...

  • Page 16: Device Configuration

    Device Configuration The device configuration area is where you assign the device description paramter. 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 17: 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 configuringthe 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 18: Modbus Tcp/Ip Client Configuration

    Modbus TCP/IP Client Configuration Click the Modbus TCP/IP Client button to access the configuration page. 1) Select which Network Interface to use for this Modbus TCP/IP connection. 2) Delay Between Messages: Enter the length of time to delay between read and write scan line requests (ms).

  • Page 19: Modbus Tcp/Ip Client Device Configuration

    Modbus TCP/IP Client Device Configuration The bottom area of the Modbus TCP/IP Client Configuration page lets you configure up to 32 external Modbus TCP/IP Server devices. 1) To add additional Server connections, click the -Select- dropdown under Modbus TCP/IP Client Device List and select Add Generic Server option.
  • Page 20 7) Enable 0-Based Addressing: Check ONLY if the server you are connecting to begins their register numbering at 0 OR they specify that their device addresses are 0-based. 8) Bit Pack: Select the formatting of the Coil Status/Input Status. Automap will use this packing size to map coils to/from the other protocol.

  • Page 21: Configuring Read Scan Lines

    Configuring Read Scan Lines Follow these steps to manually configure Read Scan Lines. 1) Select View Read Scan Lines if not already selected. 2) Enter a Unit ID for the Client to communicate to. 3) Select a Point Type for each Scan Line. Options include: Coil Status, Input Status, Input Registers, and Holding Registers.

  • Page 22: Configuring Writes Scan Lines

    Configuring Writes Scan Lines Follow these steps to manually configure Write Scan Lines. 1) Select View Write Scan Lines if not already selected. 2) Enter a Unit ID for the Client to communicate to. 3) Select a Point Type to configure. Options include: Coil Status and Holding Registers. Note: Holding Registers do have a data type associated with them.

  • Page 23: Configuring Read And Write Scan Lines (Cont.)

    Configuring Read and Write Scan Lines (cont.) If you are configuring multiple devices click << or >> to navigate to another device. If this is the only device you are configuring, click the Save Parameters button. Below is the Scan Line Data Limit for each Point Type and the max Length Range associated to them. Note: If the first address of the Modbus TCP/IP Server device starts at 0 (Register/Coil starting addresses can be found in the Modbus TCP Server’s documentation), be sure to check the Enable 0-Base Addressing box in the gateway to ensure proper communication.

  • Page 24: 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 25 1) 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. If set to “Enable”, an optional proxy configuration section also may be configured. 2) Destination URL: Enter the web address that the gateway will POST XML/JSON data to.

  • Page 26: 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 27: 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 28: 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 29: Web Interface Data Point List Configuration: Manual Mode

    Data Point 2 => Type Float (DeviceA:Float1) Data Point 2 => Type Integer (DeviceA:Int2) Data Point 3 => Type Integer (DeviceA:Int2) Data Point 3 => Type Integer (DeviceB:Int1) Data Point 4 => Type Integer (DeviceB:Int1) Data Point 4 => Type Integer (DeviceB:Int2) Data Point 5 =>...

  • Page 30: Configuring Read And Write Data Points

    3) Generate Data Points: Once values in the number of read/write data points has been changed, click this button to them auto-generate. These new data points may be configured after they have been generated. Configuring Read and Write Data Points Follow these steps to manually configure Read and Write Data Points: 4) Select the View Read Data Points or View Write Data Points button.

  • Page 31: Web Interface Group Configuration

    Web Interface Group Configuration Click the Setup Group Names and Device Names button at the bottom of the Web Interface Configuration page to access the Web Interface Group Configuration page. NOTE: When in Auto-Configure Mode, these fields are not configurable. The Group Configuration page allows customization of each Group Name and Device Name.

  • Page 32: Requirements For Device And Group Names

    Requirements for Device and Group Names: • Name must be unique on this page. o A group name may not also be a device name. o No two group names may be the same. o No two device names may be the same. o Reserved names of “DeviceName”, “GroupName”, “dataTimeStamp”, and “Diagnostics”...
  • Page 33 NOTE: Although the names are case-insensitive, the original capitalization will be maintained and used in the XML/JSON. After a name is entered, a verification check will run on this page to determine if the entered name is “valid”. If a name is entered that fails one of the criteria described above, the “invalid” name will be automatically changed back to the last “valid”...

  • Page 34: 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 35: Requesting A Group Of Devices

    Please take note of the format: http://[IP ADDRESS OF YOUR GATEWAY]/gateway/[ENCODING]/device/[DEVICE’S NAME] The red italicized text in brackets indicates the information you need to fill in depending upon your gateway’s IP address, how you would like the data encoded (JSON or XML) and the name you gave to the requested Device when you configured your Gateway.

  • Page 36: 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 37: Example Output Format (Get)

    Example Output Format (GET) This format is used when a <web server/web client?> wants to read the data points configured in our 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 so: Description of Format –...

  • Page 38: 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 39: 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 Encoder. 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 40: The Application/X-Www-Form-Urlencoded Method

    the name attribute you should use is Enc460JSONData. Your application, scripting language or library may also 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.

  • Page 41: Example Input Format (Post)

    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 42: 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 43: Special Note For Json Strings

    "DeviceName": "Breaker", "Temperature": 100 "DeviceName": "Drive", "Temperature_Cutoff": 32, "Torque": 15.2 Special Note for JSON Strings There is an additional consideration when writing STRING data types. The gateway recognizes and will convert the standard JSON escape sequences to their ASCII equivalents when passing the STRING value to the mating protocol.

  • Page 44: 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 45: 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 46 If there are values of “- -“ on this page, it indicates that the source has not yet been validated and no data is being sent to the destination. The example below reflects the Modbus to PLC flow of data. The Modbus (right side) is the source and the PLC (left side) is the destination.

  • Page 47: Display String

    Display String Click the Display String button to view how the string data types are mapped and what the values of each string are. Here you will see how each string from each protocol is mapped to the other. To view, select the source or destination group and the String from the dropdown menu to generate the information regarding that device.

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

    Data and String Mapping – Auto-Configure The Auto-Configure function looks at both of the 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 49: 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.

  • Page 50: Data Mapping - Adding Diagnostic Information

    Data Mapping – Adding Diagnostic Information Data Mapping offers 5 different types of information in addition to any scan lines specified for each protocol. IMPORTANT NOTE: Only add Diagnostic Information AFTER both sides of the gateway have been configured. If changes to either protocol are made after diagnostic information has been added to the mapping table, it is necessary to verify all mappings.
  • Page 51 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 52 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 53: 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 54: 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 55: 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 56: 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 57: 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 58: 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 59: 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 60: 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 61: 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 62 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 63: 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 64: Alarms - Clear

    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. For duplicate emails to occur, the alarm must become active and then be cleared again. 2) Total # Alarms Active will decrement.

  • Page 65: 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 66: Diagnostics Info

    Diagnostics Info The Diagnostic page is where you can view the gateway’s translations and protocol specific status information. For protocol specific diagnostic information, refer to the next three pages. Diagnostics – Data and String Mapping The Diagnostics->Diagnostic Info->System section displays the number of translations that are enabled, for both Data and String data types, the number of mappings that have an error, and the first mapping that has an error.

  • Page 67: Diagnostics - Modbus Tcp/Ip Client

    Diagnostics – Modbus TCP/IP Client Select the Modbus TCP/IP Client in the dropdown menu on the Diagnostics Page to view breakdown of the diagnostics and common strings that are displayed on the page. You may also view individual server counters by selecting the device in the All Servers dropdown and clicking View. Additional diagnostic information can be found by clicking the Help button.
  • Page 68 LED Status - This is the Status for All Servers or the specific Server selected. 1) Solid Green (Connected) – The gateway is connected to all the Modbus TCP Servers that are configured and enabled. 2) Flashing Green (Not Connected) – No Modbus TCP Servers are configured/enabled. a.
  • Page 69 -Function Code 5: Number of write Coil Status requests sent -Point Type Used: 0x Coil Status -# of Points: 1 7) FC06 Preset Holding Register: -Function Code 6: Number of write Holding Register requests sent -Point Type Used: 4x Holding Reg -# of Points: 1 8) FC15 Force Multiple Coils: -Function Code 15: Number of write multiple Coil Status requests sent...
  • Page 70 a. Starting address of the register/status that the error was received from 6) L (Length): a. Number of points of the register/status that the error was received from Example: This Error Code indicates Error Code 2, the register was not valid. Other details are: •...

  • Page 71: 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 72 LED Status 1) Solid Green (Connected) – The gateway is servicing HTTP requests. 2) Flashing Green (First Time Scan) – Start up state. No HTTP requests have been processed, but data points are configured. 3) Flashing Red (Connected: Idle) – The gateway has not serviced a HTTP GET/POST operation within the Inactivity Period configured.
  • Page 73 1) Server Error Strings a. Parsing Errors i. [XML/JSON] Parser (line: X col: Y): Invalid DEVICE Name ii. [XML/JSON] Parser (line: X col: Y): Invalid POINT Name iii. [XML/JSON] Parser (line: X col: Y): Over/Underflow for POINT Data iv. [XML/JSON] Parser (line: X col: Y): Invalid Data type for POINT v.

  • Page 74: 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. <Update screenshot when bug 460-194 is fixed> NOTE: This page will auto-refresh every five seconds with the latest data. Clear All Values - This will only affect displayed values.
  • Page 75 -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. Successful POST (200 OK): -Number of successfully serviced HTTP POST requests. Failed GET (404 Not found): -Number of messages where either the URL request was malformed or the requested group, device, or data point was not found in the gateway.
  • Page 76 ii. [XML/JSON] Output Buffer Overflow iii. Internal POST Error (500) c. HTTP Errors i. Error 404: URL Invalid. ii. Read Request from Unauthorized IP: xxx.xxx.xxx.xxx (Has to be enabled in RTAX, so not typical) d. URL-Encoded POSTs – Will show “Invalid Post Attempt” followed by one of the following: i.

  • Page 77: Led Configuration

    LED Configuration To modify the behavior of the LEDs on the 460 gateway, navigate to Other->Setup LEDs. The LED Configuration page lets you configure the LEDs on the gateway. 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 particular Slave/Server device.

  • Page 78: Configuration Files

    Configuration Files To access the configuration files in the 460 gateway, navigate to dropdown Other->Export/Import Config. Export Configuration The export tool allows you to save your gateway configuration for backup or to be exported into another gateway. This file is named rta_cfg.rtax by default. Network settings will not be saved in this configuration since they must be unique for each gateway.

  • Page 79: 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 webpage. If this unit should fail in the future, the last configuration the gateway used is stored on the SD card and can be used for a new gateway to get the application back up and running quickly.

  • Page 80: 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 81: 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