organic response 86296 IoT Gateway Instruction Manual

June 6, 2024
organic response

organic response 86296 IoT Gateway logo

organic response 86296 IoT Gateway

organic response 86296 IoT Gateway product

Installation Instructions

Preliminaries: Laying of power & ethernet cables to the installation location must be carried out and planned prior to IoT gateway installation. The location of gateways plays a very important role for the connectivity of the network. An IoT gateway must be placed in a location1 & manner where it can meet or exceed the following;

  • The maximum distance from one or more nodes on a mesh of nodes should not exceed 5 meters.2
  •  Each IoT gateway to supports a maximum of 150 backpacks.
  •  If multiple gateways need to be installed, they should not be collocated such that all nodes would have a similar path to all gateways.
  •  Care must be taken as IoT gateway support ethernet connection of CAT5e or higher and there is a limit on the allowable length of cables that can be run from a network switch. Consult relevant standards for this length allowance.
  •  The installed gateways must be accessible and marked on floor plans in order to ensure future troubleshooting.
  •  The gateway ID must be noted as installed and then added to the portal with the correct credentials. Refer to the portal commissioning guide for adding a gateway ID to the portal.
  •  The gateway ID includes the (6-bytes) MAC address which comprises the nonzero hex numbers followed by “0” zeros towards the end of gateway ID i.e. last 6 bytes.
  •  New gateways have PoE capabilities refer to the datasheet for more details.

An example of ideal location can be visualized as below;

organic response 86296 IoT Gateway fig 1

2. Mounting Instructions

  • If mounted installation – Install the mounting kit as per the order displayed fix screw at the desired location, install plate 2 & 3 on top by fixing screws in place.
  •  Insert the power and ethernet cables as shown below by removing the detachable cover. Please note new versions of the gateway (white sleeve as shown below) are PoE compliant so can be powered by only inserting the ethernet.

organic response 86296 IoT Gateway fig 2

BOOTUP SEQUENCE (CASCADE SERIES)


Yellow/Amber

| Solid| Gateway is booting
---|---|---


Yellow/Amber

| Slow-blink (1 blink every 2 seconds)| Gateway is in provisioning sequence


Yellow/Amber

| Fast-blink (2 blinks per second)| Provisioning is complete, the gateway is authenticating
Green| Solid| Gateway is provisioned and authenticated with Rigado Edge Direct

  • Once powered correctly the led on the IoT gateway would light up. The indication for correct ethernet cable would be visible by standard led notification i.e. solid green & blinking orange next to ethernet cable jack.3

organic response 86296 IoT Gateway fig 3

NOTE: The sleeve on the gateway above can be white in color depending upon the version of the gateway. Regardless of the physical appearance each gateway is firmware upgradable and when delivered would be made good as part of the project delivery.

  • Place the detachable cover back in its place after appropriately inserting the cables to secure the connection.
  •  Choose an appropriate plug base as per your local standards
  •  Use the insertable spaces on the back of gateways as shown by 5 above on the mounting plates as shown in 4.

Network Requirements

If an IoT gateway is required to be installed on your site that has restricted access or firewall setup, you may need to contact network administrator before installation to allow gateways the appropriate access permissions.

Ports

IN VESTA SERIES: Consider allowing the following ports (Inbound and outbound) for IoT gateways

  • 443 for TCP/HTTPS protocols
  •  123 for UDP protocol
  •  8883 for TCP/MQTT

The connection to be allowed for the below URLs if required to specify otherwise if allowed for “ALL” you don’t need tospecify any URLs.

Port 22 can be used for doing ssh to a vesta gateway, however, it may only be needed while doing local troubleshooting through a laptop in the same network. The laptop might be accessed remotely via a TeamViewer for any such troubleshooting. It is not necessary for normal operations.

IN CASCADE SERIES: refer to the below ports to access the associated services.’

Remote Host Protocol Port
0.ubuntu.pool.ntp.org ntp.ubuntu.com UDP 123
geoip.ubuntu.com TCP/HTTPS 443

login.ubuntu.com api.snapcraft.io dashboard.snapcraft.io storage.snapcraftcontent.com

canonical-lgw01.cdn.snapcraftcontent.com canonical-lcy01.cdn.snapcraftcontent.com canonical-bos01.cdn.snapcraftcontent.com cloudfront.cdn.snapcraftcontent.com fastly.cdn.snapcraftcontent.com

fastly-global.cdn.snapcraftcontent.com

|

TCP/HTTP

|

443

provision.rigado.com serial-vault.rigado.io| TCP/HTTPS| 443
api.rigado.com| TCP/HTTP| 443
diagnostics.rigado.com| TCP/HTTPS| 443, 80
a2fyo1pewinh1f.iot.us-west-2.amazonaws.com| TCP/MQTT| 8883

https://portal.organicresponse.com

| TCP/HTTPS TCP/MQTT UDP| 443

8883

123

http://a2bghq9neujukx.iot.ap-northeast-1.amazonaws.com/ <http ://a2bghq9neujukx-ats.iot.ap-northeast-1.amazonaws.com/>| TCP/HTTP

TCP/MQTT UDP

| 443

8883

123

IP Configurations

The IoT gateways out of the box come as a DHCP device i.e. it can take any available IP address from the pool if available and installed correctly. If the network restricts DHCP connections, please contact ORT in assisting you to set static IP addresses for your site.

The two series of gateways are different in how they can be custom configured to suit network conditions

  • VESTA SERIES: require local ssh access to gateways to make such configuration changes. Which means a laptop connected to the same network as gateways which can allow TeamViewer connection remotely if this requires to be done remotely by ORT. Contact ORT for details on project delivery and details. A temporary 4G network or VPN setup is recommended if unable to use on-site network.
  •  CASCADE SERIES: would require internet access for initial setup in their DHCP settings. Consider setting up a VPN or a 4G router to segregate network for gateways such that the gateways would have internet access to enable initial set up remotely without the requirement of any TeamViewer access. Contact ORT and/or network admin for site to discuss in detail beforehand.

Please note the custom configuration can be implemented by ORT prior to dispatch of gateways. Contact ORT with details of any such custom changes prior to delivery commitments.

In order to implement static IP address, you should contact the network administrators to provide you;

  • An IP address or list of IP addresses
  •  Default Gateway address (this is the address for IP network gateway)
  • Subnet Mask
  •  DNS (Specify one even if it is default)

It is also important to note gateway IDs & serial numbers which are displayed on the box as well as at the back of all gateways to associate the IP addresses to correct gateways.

Gateway Reset (Cascade only)

Once configured to custom configuration the gateway would only have internet access once connected to the network that is suitable for those configurations in conjunction with above network requirements. If incorrect network configurations have been implemented a network reset option can be used, however, we highly recommend that it is performed in strict compliance to guidelines below;

Reset Action Time Behaviour
Quick Press < 2 seconds Soft Reboot
Short Press 2-4 seconds Network Reset
Long Press 10-15 seconds Hard Reboot
  • A Soft Reboot will restart the operating system on the gateway without interrupting power.
    • Network Reset clears all network configurations and requires the button to be pressed for 2 to 4 seconds. To aid timing for Network Reset, the LED quickly flashes yellow to indicate the window when the LED should be released. When the button is released during that window, the LED will quickly flash green to confirm the Network Reset operation has been triggered. If released after 4 seconds, the LED will return to the behaviour it displayed before quickly flashing yellow. If the button is released between 4 and 8 seconds, no actions (Reboot or Reset) are performed.
  • A Hard Reboot will reset the processor and restart the operating system.

Avoid doing any network reset without consulting ORT. It is recommended that you never hold the reset buttons longer than 15 seconds. If the reset button is held longer than that period, then you risk of doing a factory reset which means the gateway would need to be shipped back as everything installed would be removed.

Post Installation:
If you are unsure at any stage consult OR Technologies.
Refer to Portal Commissioning Guide to enable your SN3 / SN2.5 installation portal ready.

Documents / Resources

| organic response 86296 IoT Gateway [pdf] Instruction Manual
86296, IoT Gateway
---|---

Read User Manual Online (PDF format)

Loading......

Download This Manual (PDF format)

Download this manual  >>

Related Manuals