EAPro-GTWY Advance Network Troubleshooting

This is an in-depth guide for troubleshooting a network connection. It is advised to communicate with your network admin while going through these steps.

 

If you can ping the unit and the Ping Test passes, it typically implies an issue with NTP or a blocked port.

 

General Network Information:

This device uses Azure IoT Hub. IoT Hub IP addresses are not static and can change based upon device/region and version of communication and Azure itself. Winland currently does not have a static IP option for IoT communication.

 

Azure IoT Hub does not currently support IPv6. 

For more information dealing with IPv4 routing and IPv6 see: https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-understand-ip-address

 

Networking Rules/Ports Required

NTP RJ45: time.nist.gov (Default, can change though configuration file or through UI on certain firmware)

NTP WIFI: DNS query to time.gov for IP (default, can change through config file or through UI on certain firmware)

NTP Port: 123

 

DNS: EAProHub-Prod.azure-devices.net (hardcoded, not adjustable)

DNS Port: 53

 

SSL: Handled by IoT Hub

SSL: 443

 

MQTT: Communication to IoT Hub

MQTT Port: TCP 8883

This port should be allowed for: EAProHub-Prod.azure-devices.net, and not locked to a static IP.

 

Once installed and configured the EAPro-GTWY communicates to the Host System on a 2-minute interval for live readings, and for logs it sends based on the Cloud Sync setting. It does not accept any inbound connections.

 

TROUBLESHOOTING:

Note: Device should be unlocked for the following procedures.

 

Please verify you are on the correct firmware & bootloader, which can be checked by using the following:

 Firmware Guide

At this point, the bootloader and the firmware should be up to date. Typically the bootloader won't affect the network system.

 

Settings to Verify Network is enabled.

  • Located on the board (refer to image below) toggle to enable 1: Wi-Fi // 2: Ethernet (RJ45). Enable the switch corresponding with the method you plan to use. (It is recommended to only have one toggle on)

updatedeaproimage.jpg

  • Verify "Cloud" is enabled in: Unlock > Main Menu (Gear Icon) > Network > Cloud > Cloud = Enabled

 

 Check your current IP settings on the EAPro system

 Unlock Device > Main Menu (Gear Icon) > Network > View Ethernet OR View Wi-Fi

Hit "Next" in the bottom right of the screen to view more information including if DHCP is enabled or disabled.

1st Row, shows Wi-Fi, 2nd Row shows Ethernet.

ed730e7a-16fb-447d-890b-fb9bed5b77fb.jpg2e7fea11-3163-4d83-912b-aef19a1607a3.jpg3911a8ab-1b7e-45fe-8ab3-e8805d264b3c.jpg

23153234-c61a-4f7d-b94e-9b83a6329a4d.jpg5357216e-2282-41f9-aedd-3dc06d4c4cd4.jpga4117d4e-a846-4672-9012-f0d38efe13d4.jpg

 

Check your PING

Note:  The ping test utilizes an ICMP echo request which will ping 8.8.8.8 (hardcoded), a FAIL ping test indicates the device is unable to reach outside the local network.

Unlock Device > Main Menu (Gear Icon) > Network > Cloud > Test

Cloud.png

 

If Ping Passes but Unable to connect to INSIGHT and Ports are open

First attempt is to add or edit a sensor, then attempt to add on INSIGHT.

INSIGHT doesn't recognize a device has communicated unless it receives a sensor configuration. Editing a sensor or adding a sensor forces a device/sensor configuration change.

 

 

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.