1. Manuals
  2. Brands
  3. RTA Manuals
  4. Gateway
  5. 460PBSQT-NNPB
  6. Product user manual

RTA 460PBSQT-NNPB Product User Manual

Protocol gateway
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
460PBSQT-NNPB
Protocol Gateway
Product User Guide
Firmware Version 8.8.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 460PBSQT-NNPB and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for RTA 460PBSQT-NNPB

Summary of Contents for RTA 460PBSQT-NNPB

  • Page 1 460PBSQT-NNPB Protocol Gateway Product User Guide Firmware Version 8.8.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

    Configuring Subscribe and Publish Topics ....................34 Amazon Web Services (AWS) Configuration ................... 36 Additional AWS Requirements ........................ 37 How to FTP files into the RTA gateway ..................37 AWS IoT Core Service Setup ........................40 AWS IoT Core Service Things Configuration ................... 42 Certificate setup ..........................
  • Page 4 Send data from RTA gateway to AWS (Publish Topics) ..............51 Testing Your MQTT Connections with MQTT Explorer ................54 Send data from RTA gateway to MQTT Explorer (Publish Topic) ............55 Send data from MQTT Explorer to RTA gateway (Subscribe Topic) ........... 56 QT Publish Trigger ............................
  • Page 5 Diagnostics Info ............................87 Diagnostics Mapping ..........................87 Diagnostics – PROFIBUS Slave ........................88 Diagnostic – MQTT Client ..........................90 LED Configuration ............................92 Configuration Files ............................93 Export Configuration ..........................93 Import Configuration ..........................93 Save and Replace Configuration Using SD Card ..................95 Saving Configuration Using SD Card......................

  • 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 3. Updated Profinet Server (PS) on N34 hardware Platform 4. Updated Wi-Fi software 2/28/20 8.6.0 Bug Fixes...
  • Page 7 Version Date Notes 8.9.22 2/5/24 Features Added: 1. Added priority-based reads for client protocols 2. Added improved diagnostic timers for client protocols 3. Reduced minimum delay between messages to zero ms on client protocols 4. Added support for USB serial connections 5.

  • Page 8: Overview

    Overview The 460PBSQT-NNPB gateway Connect a PROFIBUS Master to an MQTT Broker. By following this guide, you will be able to configure the 460PBSQT-NNPB gateway. Number of ASCII devices is dependent on the Hardware and Product number of the 460 gateway.

  • Page 9: 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 10: Hardware - Nnpb

    Hardware – NNPB 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 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. When you have completed your port configuration, click the Save Parameters button. Note: The PROFIBUS port is NOT configurable. The only configuration that the PROFIBUS port requires is the Slave Address on the PROFIBUS Slave Configuration page.

  • Page 12: Mounting With A Din Rail

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

  • Page 13: 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 Accessing Browser Configuration...
  • Page 14 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 15: 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 16: 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 17: 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 18: 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 19: Profibus Slave Configuration

    PROFIBUS Slave Configuration Click the PROFIBUS Slave button to display the configuration page. 1) Enter a Device Label to identify the device on the network and within the gateway. 2) Enter a unique Slave Address for the device on the network. 3) To enable data swapping, select the required Swap Indicator.

  • Page 20: Profibus Slave Configuration

    PROFIBUS Slave Configuration The PROFIBUS Slave Configuration page lets you configure multiple input and output slots. 1) PROFIBUS only supports a total of 244 input bytes and 244 output bytes. 2) Data Size is configurable. Options include: 2, 4, 8, 16, 24 and 32 bytes. 3) Data Format sets the formatting of the data.

  • Page 21: Profibus Slave Slot Configuration: Auto-Server Mode (Default)

    PROFIBUS Slave Slot Configuration: Auto-Server Mode (Default) While in Auto-Server mode the data groups themselves cannot be edited. Auto-Server Mode looks at the other protocol and then configures the Data Groups to match. The Data Size and Data Formats will be defined after the other protocol is configured.

  • Page 22: 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 23: Profibus Slave Slot Configuration: Manual Mode

    PROFIBUS Slave Slot 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 PROFIBUS IO server Configuration page and select Manual Configure. 2) When prompted, click OK to confirm mode change or Cancel to remain in Auto-Configure Mode. 3) Once OK is clicked, there are two options for how to proceed.

  • Page 24: Setting Up The Plc- Example Using Simatic Classic Step 7

    Setting up the PLC- Example Using Simatic Classic Step 7 This is how you would set up the following example in your controller. 1) In your project, click the CPU and you should see the Hardware option in the right pane. Double click on the Hardware icon.
  • Page 25 7) When prompted to confirm installation because it cannot be undone, click Yes. 8) Click OK acknowledging that the install was successful. 9) If you navigate to the right-hand side, you will see the RTA profile under: PROFIBUS DP->Additional Field Devices->General->profichip Real Time Automation->460XXPBS Real Time Automation, Inc.
  • Page 26 10) Once found, drag the Standard icon into the network line you created in Step 9. 11) Double-click the gateway icon to open the properties window. Be sure setup the Slave address that will match the 460PBS configuration page. Real Time Automation, Inc. 1-800-249-1612...
  • Page 27 12) Expand the Standard node on the right panel to show the available modules to insert (Refer to the picture in Step 9). To match the above configuration in the 460 gateway, add one 8-byte input module, one 32- byte input module, and one 32-byte output module to your device configuration. 13) To configure the PLC to match the 460 gateway, you will need to utilize 3 slots in your PLC.

  • Page 28: Setting Up The Plc- Example Using Tia Portal

    Setting up the PLC- Example Using TIA Portal This is how you would set up the following example in your controller. 14) In your project, click the Device View tab and click your PROFIBUS card. 15) IF YOU HAVE ALREADY INSTALLED THE GSD FILE, SKIP TO STEP 9. OTHERWISE - Under Options, select Manage general station description file (GSD).
  • Page 29 17) Click … and browse to where you saved the GSD file. 18) Check the box to the left of the imported path and click Install. 19) Click Close when it was installed successfully. Real Time Automation, Inc. 1-800-249-1612...
  • Page 30 20) Click the Network View tab in your project. 21) Navigate to the right-hand side of the screen under the Hardware catalog and you will see the RTA profile under: Other field devices->PROFIBUS DP-> General-> Real Time Automation-> profichip Real Time Automation->...
  • Page 31 25) Be sure setup the Slave Address that will match the 460PBS configuration page. 26) To configure the PLC to match the RTA gateway, you will need to utilize 3 slots in your PLC. NOTE: When using a Short String Data Type, the 1 byte of each slot is reserved for the Length field.
  • Page 32 27) Expand the Head Module list under the catalog on the right panel to show the available modules to insert into the device overview slots. To insert a module, double click to add it to the next available slot. Terminology Note and Example: I addresses refer to Input, Q addresses refer to Output, %B refers to bytes and %W refers to words.

  • Page 33: Mqtt Client Configuration

    MQTT Client Configuration You can configure up to three MQTT connections. 1. Configure up to three MQTT broker devices. 2. Configure up to one Amazon Web Services (AWS) IoT Core connection. 3. Configure up to one Microsoft Azure connection. NOTE: A single AWS OR Azure connection is supported and can co-exist with up to two additional MQTT broker devices.

  • Page 34: Configuring Subscribe And Publish Topics

    4) Select which Network Interface to use for MQTT device connection. Option only available on the N2E hardware platform. 5) Enter the unique MQTT broker IP address or URL, if this value does not match, the gateway will timeout. 6) Enter TCP Port for the MQTT broker to open a connection on. If this value doesn’t match, the gateway will not open a connection.
  • Page 35 15) # of Publish Paths: Enter the number of topics to publish to the broker from the mating protocol. 16) # of JSON Name/Value Pairs: Enter the number of JSON name/value pairs to configure, each name/value pair can be associated with a single publish or subscribe path. 17) Select the publish or subscribe path each name/value pair should be associated with.

  • Page 36: Amazon Web Services (Aws) Configuration

    Amazon Web Services (AWS) Configuration You can only configure one AWS IoT Core connection with your RTA product. 1) To add an AWS connection, click the -Select- dropdown menu under MQTT Client Connection List and select Add Generic AWS Connection option.

  • Page 37: Additional Aws Requirements

    4) The private key, certificate, and root certificate will need to be FTP’d into the RTA gateway’s Flash File System. 5) The time configuration will need to be set to the current date and time to establish a connection.
  • Page 38 4) In the address bar (within the red box shown above) type ftp://xxx.xxx.xxx.xxx (IP Address of RTA gateway). a. You will then see a pop-up window, Username: ffs Password: rtarocks b. Paste the certificate and private key into this ftp session, close out the session by exiting out.
  • Page 39 5) Navigate to the RTA gateway and on the left-hand side, click the OTHER -Select- dropdown and select Utilities. 6) Once on the Utilities page click the File List button. 7) Verify that your certification and private key files appear on this page.

  • Page 40: Aws Iot Core Service Setup

    “Thing” and “Policies”. Before you can register your RTA gateway as a “thing,” we need to setup a “policy” for it. This policy will be assigned to our “thing” during the registration process and will grant it the permissions needed to access the MQTT topics that we will use to publish and subscribe messages.
  • Page 41 From the policy creation page, you add the statements that will dictate what connected devices are allowed to do. Assign a unique name to your policy and add four statements with the information listed below. Notice that when you type in the action, the field labeled “Resource ARN” will be automatically populated.

  • Page 42: Aws Iot Core Service Things Configuration

    “Create things.” A new window will open with a number of things to create, chose “Create single thing” and click the Next button. If you have multiple RTA gateways, then you’ll need to select “Create many things”. Real Time Automation, Inc.

  • Page 43: Certificate Setup

    The next setting will be the “Specify thing properties”, here you will give your “Thing” a unique name and click the Next button at the bottom. Certificate setup Here you associate your “Thing” with the certificate that will be used to authenticate it with the AWS IoT Core service.
  • Page 44 Real Time Automation, Inc. 1-800-249-1612...

  • Page 45: Attach Policies To Certificate

    “Download certificates and keys”. Download the certificate and the private key. Once downloaded, navigate back to this user guide section “how to FTP files into the RTA gateway” to load the certificate and private key into the gateway. Real Time Automation, Inc.
  • Page 46 Once you have successfully downloaded the files you will be redirected to the Things page. Within the Things page, click on the thing name you setup, in this example it would be RTA_Testing. From this page, you can view if the certificate is active and create a Device Shadow URL. Real Time Automation, Inc.
  • Page 47 Along with the certificate and private key, your RTA product will need the Device Shadow URL. Click the Device Shadows tab and click “Create Shadow”. Enter in a Device Shadow name and click the Create button. You will be redirected to the Things page where you’ll see your new Device Shadow created.
  • Page 48 Within the RTA gateway configuration Device Shadow URL, enter in “aabb11224e9ex-ats.iot.us-east- 2.amazonaws.com,” everything else is ignored. Real Time Automation, Inc. 1-800-249-1612...

  • Page 49: Testing Aws Communication

    AWS, the two files have been FTP’d into the RTA gateway, and the Device Shadow URL is configured. Using the AWS MQTT test client, you can Subscribe to a topic (data from the RTA), and you can Publish to a topic (data to the RTA).

  • Page 50: Send Data From Aws To Rta Gateway (Subscribe Topic)

    Below is how the RTA AWS IoT Core Service is setup to Subscribe data from AWS to the RTA. Within AWS, click the “Publish to a topic” tab. Enter in the topic name that is defined in the RTA gateway “Subscribe Topics”...

  • Page 51: Send Data From Rta Gateway To Aws (Publish Topics)

    Navigate to the RTA Display data and refresh the web page. You will see your data being updated. Send data from RTA gateway to AWS (Publish Topics) This example shows a PLC writing data to the RTA gateway and presenting that data to the Publish topic. Real Time Automation, Inc.
  • Page 52 In the topic filter, use a wildcard character of “#” (subscribe to all topics), and click the Subscribe button. You’ll see the subscription once the new Publish data comes in. The “RTA” is the Client ID that is configured in the MQTT device configuration of the RTA. The “Data_From_RTA_2_AWS” is the Publish Topic name configured in the AWS device configuration page of the RTA.
  • Page 53 Real Time Automation, Inc. 1-800-249-1612...

  • Page 54: Testing Your Mqtt Connections With Mqtt Explorer

    Once you launch the MQTT Explorer tool, setup a new connection. The host will be IP of your MQTT broker. Next, you can configure the RTA gateway. The broker IP address listed below is set up to be the IP of the machine where the broker is installed.

  • Page 55: Send Data From Rta Gateway To Mqtt Explorer (Publish Topic)

    Send data from RTA gateway to MQTT Explorer (Publish Topic) This example shows a PLC writing data to the RTA gateway and presenting that data to the MQTT publish topic. Write a value in “my PLC” and MQTT Explorer will subscribe to that topic.

  • Page 56: Send Data From Mqtt Explorer To Rta Gateway (Subscribe Topic)

    Send data from MQTT Explorer to RTA gateway (Subscribe Topic) The RTA gateway has a topic name of Data_From_Explorer_2_RTA that MQTT Explorer is going to be publishing to. Enter in the topic name to publish, enter in the value (our example is 2328), then click Publish.

  • Page 57: Qt Publish Trigger

    QT Publish Trigger By default, the RTA gateway will publish to the broker based on change of state. This means a new publish to the broker will occur any time a value changes. In an application where the client is being charged per publish, such as with AWS, this is not ideal.

  • Page 58: 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 59: 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 60 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 61 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 62: 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 63 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 64: 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 65: 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 66: 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 67: 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 68 4) Heartbeat 100ms Update a) The Heartbeat 100ms Update variable can be used as a heartbeat that updates once every 100ms. The variable starts at 0 on gateway startup and increments by 1 every 100ms. This can be mapped into a destination on one of the available protocols to monitor the gateways connection status.
  • Page 69 c) There are multiple ways to map the NetBmpStat. Option 1: Map the whole 32bit value to a destination. Example below shows the NetBmpStat is going to an Analog BACnet object. Using a connection of 5 Modbus Slave devices AI1 will show a value of 31.0000. Open a calculator with programmer mode and type in 31, this will represent bits 0 –...
  • Page 70 7) 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 71 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 72: 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 73: 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 74: 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 75: 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 76: 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 77 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 78: 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 79: 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 80: 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 81: 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 82: 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 83 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 84: 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 85: 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 86: 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 87: 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 88: Diagnostics - Profibus Slave

    Diagnostics – PROFIBUS Slave Select the PROFIBUS Slave in the dropdown menu on the Diagnostic page to view a breakdown of the diagnostics that are displayed on the page. Additional diagnostic information can be found by clicking the Help button. NOTE: This page will auto-refresh every 5 seconds with the latest data.
  • Page 89 LED Status: 1) Startup State (Off) – Initialization of Profibus adapter is in progress. 2) Online (Solid Green) – Connected to a Profibus controller. 3) Offline (Flashing Green) – Waiting for GSD Parameters or Configuration. 4) Parameter Error (Solid Red) – Bad GSD parameters or hardware failure. User action required. 5) Comm Timeout (Flashing Red): a) The Profibus controller has lost a connection to the gateway.

  • Page 90: Diagnostic - Mqtt Client

    Diagnostic – MQTT Client Select the MQTT Client in the dropdown menu on the Diagnostic page to view the breakdown of the diagnostics and common strings that are display on the page. You may also view the individual MQTT device counters by selecting the device in the All Devices drop down and clicking View. NOTE: This page will auto-refresh every five seconds.
  • Page 91 Solid Green (Connected): • The gateway is connected to all the MQTT devices that are configured and enabled Flashing Green (Not Connected): • No MQTT devices are configured / enabled. Go to the MQTT Client Device Configuration to configure a device Flashing Red (Not Connected): •...

  • Page 92: 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 93: 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 94 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 95: 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 96: 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. •...

This manual is also suitable for:

460pbsqt-nnpb-d

Table of Contents