Difference between revisions of "Troubleshooting"

From Nearwiki
Jump to: navigation, search
(Created page with "===Troubleshooting your NearBus Connection=== <br /> If your Arduino remains DOWN, make the following verifications: '''ETHERNET CHECK LIST''' '''1- Verify that the gre...")
 
(No difference)

Latest revision as of 20:46, 29 March 2018

Troubleshooting your NearBus Connection


If your Arduino remains DOWN, make the following verifications:


ETHERNET CHECK LIST

1- Verify that the green light in the Arduino's Ethernet connector is flashing.

2- Verify that your internet connection is Up (if you can surf the internet).

3- Verify that your Arduino "user" and "password" are configured Ok (the 8 character password, the Device_ID and the Arduino's MAC).

4- Verify that your Arduino's Ethernet MAC address is configured Ok (you can find it a label on the back side of your arduino Ethernet board).

5- Reset the Arduino, to ensure that it is properly initialized.


WiFi CHECK LIST

1- Verify that the green light (Link) in the Arduino's WiFi board is ON.

2- Verify that your internet connection is Up (if you can surf the internet).

3- Verify that your Arduino "user" and "password" are configured Ok (the 8 character password and the Device_ID).

4- Verify that your WiFi SSID is configured OK, and the "wifimode" parameter matches with your WiFi router configuration (Open = 0 | WAP2 = 1 | WEP = 2). If you find issues try to configure your wireless LAN in open mode (to test the Arduino connection).

5- Remember checking if your WiFi router has configured the MAC Filtering Feature (in this case you should enable the Arduino's WiFi MAC on it !!).

6- Reset the Arduino, to ensure that it is properly initialized.


NETWORK TOOL: With Advanced IP Scanner you be able to scan all your IP addresses including Wi-Fi network. Download App: [1]


IMPORTANT: The NearBus screens do not refresh in an automatic way, so you should reload it in order to get the device status.


REMEMBER: If you are experimenting random errors with your code (usually on memory exhaustion conditions), verify that the
#define parameters DEBUG_DATA, DEBUG_BETA and DEBUG_ERROR (in file NearBusxxx_xxx.h) are all set to 0 (in order to deactivate the 
output debug messages).

#define  DEBUG_DATA      0    // Set to 1 by default
#define  DEBUG_BETA      0
#define  DEBUG_ERROR     0