The Oper8 Global Gateway runs as a console application on Windows and Linux operating systems.


The Gateway and Gateway Controller require .NET libraries to run (Article here).


Please ensure the machine is configured to autorun the Gateway application on system restart.


Hardware Requirements for an Oper8 Global Gateway

  • Minimum 2GB RAM
  • Dual core CPU
  • 200MB Disk Space (noting log files are written continuously)
  • 10/100Mbps RJ45 IP Network Interface 


For Gateways licenced to run with Unlimited sensor point licences, higher RAM, CPU and Disk Space capacity should be considered.



Log Files:

  • Gateways automatically create a new log file at midnight each day
  • Logs are stored in the ..\log subdirectory
  • Consider a maintenance activity every 12 months to remove older, unwanted log files




General Functionality Overview


Oper8 Gateway Controllers require minor configuration to effectively point them to the instance of RF Code Centerscape, and the adjacent Oper8 Global Gateway Controller.


The Gateway configuration requires:

  • The unique Gateway ID as configured in the Oper8 Gateway Controller
  • User credentials for CenterScape  (Oper8 Global recommends a dedicated user account)
  • The Licence Key and Serial Number to authorise connection to the Gateway Controller
  • CenterScape URL
  • Gateway Controller URL 


A sample gwsetup.bat (Windows based Gateways) file is provided in the ZIP download of the Oper8 Global Gateway software.


To run the Gateway simply run the Gateway application.


Once a Gateway has been configured with a correct Gateway ID, Key and Serial Number, the Gateway will connect to the Gateway Controller, verify its Key and Serial Number then download the configured sensors it is to monitor on the local network.


The initial version of the Oper8 Global Gateway can monitor any SNMP compatible device.  Future editions are planned to monitor Modbus-IP and BACNET-IP devices.


Sensor data is periodically uploaded to CenterScape using the RF Code REST API, while periodic checks are made with with the Gateway Controller to download any updated sensor profiles.  


Gateway Heartbeat updates to detect offline Gateways are managed through the Gateway Controller which in turn updates CenterScape.


Please Note:

  • Sensor Profiles can only be updated through the Gateway Controller
    • As long as the Gateway can reach the Gateway Controller, sensor profile changes are downloaded every 30 to 60 seconds
  • Ensure the Gateway application is configured to autorun on system restart.
  • Gateway ID is unique and is case sensitive when licencing the Gateway
  • Deleting then recreating a Gateway with an existing Gateway ID and License Key may likely create a new Serial number for Gateway authorisation to the Gateway Controller
  • The Gateway must be able to reach both CenterScape and the Gateway Controller
  • The Gateway must be configured with the Licence Key and Serial Number as configured in the Gateway Controller



Support:

  • Email supportdesk@oper8global.com 
  • Please include your Gateway ID, Licence Key, CenterScape version details, and relevant log files from the Gateway with the enquiry