-
Notifications
You must be signed in to change notification settings - Fork 1
Troubleshooting
Good luck
- Working on motor pi ->
ssh pi@192.168.1.4 - Working on camera pi ->
ssh pi@192.168.1.3 - Working on surface pi ->
ssh pi@192.168.1.2
Likely there is still code running on the pi. Try finding the process id with ps aux | grep "server2020" or ps aux | grep "webSocketServer". If there is a process, use the left most number or the result of pgrep -f "server2020" or pgrep -f "webSocketServer" to get the process id. Kill the process with kill -9 [process id].
If that doesn't work, then find the line PORT = 8008 at the top of server2020.py and webSocketClient.py and change the port number to something else like 8009, 8010, or 8011 in both files on both motor pi and server pi. The port number MUST be the same across all the software.
the output contains a line of the like 58 Connection was refused by other side: 111: Connection refused., where the number in front (58 here) is going up every couple of seconds, then the code is automatically trying to reconnect.
The code might not be able to connect to the server. Press ^C (Control-C) and start the program again to try to reconnect.
Make sure server2020.py is up and running without errors on surface pi. Else check the ip address on motor2020.py on motor pi. The last line should read webSocketClient.start('motor', process, ip="192.168.1.2"), where 192.168.1.2 is the ip address of surface pi.
For who knows why, surface2020.py must be run in a terminal window of the raspberry pi, and CANNOT be run in an ssh session.
The standard code used is for python3. Ensure that python3 someFile.py is used instead of python someFile.py, as that will run python 2.7.
You have issues
-
Don't use Chromium
-
Wait 5-10 seconds
-
Reload the page
-
Check
status.html. It should sayStatus: Running. If not, try:- ssh into camera pi ->
ssh pi@192.168.1.3 - run
/var/www/scripts/dataCollection.sh start - check
status.htmlanddataSheet.htmlagain - Try step 4
- ssh into camera pi ->
-
If on chrome -> right click -> inspect -> console
- If it says some error other than the likes of
Error in connection establishment: net::ERR_CONNECTION_REFUSED, then the code has an error, RIP. - If there are no errors except for the likes of
ERR_CONNECTION_REFUSED, then try step 5.
- If it says some error other than the likes of
-
Check Logs
- run
less /var/www/scripts/nohub.out - visit page
cgi-bin/getLog.py - If either show an error, then your on your own.
- run
Every once a while an error will show up in the data normally, but if they are continuous, the wiring is probably broken.
