Configure the ERT/Ethernet Gateway for Device Cloud¶
Connect and Power on the ERT/Ethernet Gateway¶
- Unpack the ERT/Ethernet Gateway.
- Connect the power supply to the ERT/Ethernet Gateway and connect the power supply to an electrical outlet. Check that the Power LED is lit.
- Connect an Ethernet cable from the ERT/Ethernet Gateway to your hub or switch that provides access to the Internet. Check that the Link LED (orange) on the Ethernet connector is lit to indicate a valid Ethernet connection.
Add Gateway to Device Cloud¶
To add a gateway to the device list, follow these steps:
Log into Device Cloud at devicecloud.digi.com using your user name and password.
In the Devices Manager, click the Add Devices button to bring up the Add Devices dialog.
Locate and select your device from the list of locally discovered devices and click the OK button. If your device was not found in the list, check that it is turned on and connected to the same local network as your PC and click the Discover button. Adding your device through automatic discovery informs Device Cloud about the device and configures that device to connect to Device Cloud.
Wait a few moments and click the Refresh button to ensure that your device is connected.
Note
If the device does not show up as connected or an error is displayed, Device Cloud may have been unable to configure the device connection. See Troubleshooting to update device connection manually and then repeat this procedure.
Select your device and double-click it, or right-click and select Properties.
Your device information will load into a separate tab.
Troubleshooting¶
By default, gateways point to the login.etherios.com production server (some older gateways may point to device.idigi.com or my.idigi.com). Accounts on the production servers are used for production devices and for testing. Adding a gateway to Device Cloud will normally configure the device appropriately but if necessary a gateway can also be manually configured.
To check your gateway’s Device Cloud server configuration¶
Use the Digi Device Discovery application (see Downloads) to determine your gateway’s IP address.
Telnet to this address and login with the following user name and password until you see the prompt as shown below.
login: root password: dbps #>
At the prompt enter the following command to check current Device Cloud server configuration.
login: root password: dbps #> set mgmtconnection MgmtConnection Configuration : conntype : client connenabled : on timedperiod : 5 timedoffset : immediate lkaupdateenabled : off clntreconntimeout : 60 pagedoverrideenabled : off svraddr1 : "en://login.etherios.com" secidx1 : 1
To configure your gateway to point to an alternate Device Cloud server¶
Use the Digi Device Discovery application (see Downloads) to determine your gateway’s IP address.
Telnet to this address and login with the following user name and password until you see the prompt as shown below.
login: root password: dbps #>
At the prompt, enter the following command to tell the gateway where to look for a Device Cloud server, specifically login.etherios.com.
login: root password: dbps #> set mgmtconnection svraddr1="en://login.etherios.com" conntype=client
Type the who command to get the number of the process currently controlling where the gateway points. In this case, it is process ID 1.
#> who ID From To Protocol -- ----------------- ------------------ -------- 1 10.8.16.83:45627 67.202.55.55:3197 idigi tcp 2 Python: main.py 3 10.8.16.85 local shell telnet 4 Python thread 5 Python thread 6 Python thread
Kill this process with the kill command, as shown below.
#> kill 1 Connection 1 : killing connection ...
Now that the process is killed, you can enter who again to see that the gateway is currently waiting to retry the server connection. By default the gateway will wait for up to one minute.
#> who ID From To Protocol -- ------------------- ------------------ -------- 1 waiting to connect wait 0:01:00 idigi wait 2 Python: main.py 3 10.8.16.85 local shell telnet 4 Python thread 5 Python thread 6 Python thread
After a couple of minutes enter the who command again to see that the gateway has reconnected to the correct Device Cloud server. The actual address under To will vary depending on the server selected.
#> who ID From To Protocol -- ----------------- ------------------- -------- 1 10.8.16.83:45627 75.101.143.63:3197 idigi tcp 2 Python: main.py 3 10.8.16.85 local shell telnet 4 Python thread 5 Python thread 6 Python thread
You are now ready to add the gateway to your Device Cloud account.