You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pilot data all has a single SERIAL number on it (00000000d5bbc3d4) and a single location (according to Dan, I haven't decoded the locations). Which implies that the data from the PORTABLEPi aren't uploading to the SERVERPi.
Three possibilities:
PORTABLEPi aren't logging any data
PORTABLEPI aren't transferring data to the SERVERPI
SERVERPI is not uploading the PORTABLEPi data (but is uploading it's own data - problem with merging algorithm?
@cemac-ccs will send Jim instructions as to how to copy the SERVERPi SD card, so we can look and see if PORTABLEPi data is logged there.
Could Jim do the USB trick to download data from the PORTABLEPi and @KirstyPringle can check that the PORTBABLEPi are logging data?
The text was updated successfully, but these errors were encountered:
The data has now been downloaded manually from card images supplied by Jim, and csvs of the portable sensor data with no location data have been added to the Teams area, as have the logs from the run. db files have also been uploaded to aws.
Looking at the logs, it appears that possibility 2 is the culprit - the data is being collected but not uploaded to the serverpi. The error message that is generated when the upload fails refers to 'Nonetype is not callable', implying that a particular function is not being used correctly. I will update here once I have done some more testing, but currently the problem is either:
A problem in the software that was missed during testing
A problem in the hardware (for example casing or bumbags impeding the signal) that is interfering with the connection and generating a red-herring error message
Due to the use of the pysftp library, red herring error messages are unfortunately a distinct possibility however I strongly suspect that the issue is with software
I think it is software linked given the portable sensors were taken out of the bumbags to access the microSD cards and never returned, now sitting ontop of freezer next to serverpi. The portable units are built into a plastic box, I would be very surprised if there blocked the wifi signal between portable and server
The pilot data all has a single SERIAL number on it (00000000d5bbc3d4) and a single location (according to Dan, I haven't decoded the locations). Which implies that the data from the PORTABLEPi aren't uploading to the SERVERPi.
Three possibilities:
@cemac-ccs will send Jim instructions as to how to copy the SERVERPi SD card, so we can look and see if PORTABLEPi data is logged there.
Could Jim do the USB trick to download data from the PORTABLEPi and @KirstyPringle can check that the PORTBABLEPi are logging data?
The text was updated successfully, but these errors were encountered: