Autumn/Winter November and onwards 2017 deployment(s)
Re: Autumn/Winter November and onwards 2017 deployment(s)
Hmm, I guess we must still have leaks/overflowing on the lid then.
Hamish
Re: Autumn/Winter November and onwards 2017 deployment(s)
It will be interesting to see what the log says.
Re: Autumn/Winter November and onwards 2017 deployment(s)
Terry, can you bring your laptop to upload the software? My charger died today so I haven't had time to buy a replacement. Sorry for short notice - just got home from work
Hamish
Re: Autumn/Winter November and onwards 2017 deployment(s)
Hamish,
I had intended to anyway. It's charged and ready!
I had intended to anyway. It's charged and ready!
Terry
Re: Autumn/Winter November and onwards 2017 deployment(s)
Hello
I may be late, as per my email. Butt probe cable in box on bench in Hanham room.
Hwyl
I may be late, as per my email. Butt probe cable in box on bench in Hanham room.
Hwyl
Re: Autumn/Winter November and onwards 2017 deployment(s)
All,
Not a brilliant morning; apart from the problems with my wiring, we seem too have a return of the Ethernet connector issue that we experienced some time ago. Even when it was working, it was extremely slow and ping response varied from 70% packet loss to 23% packet loss.
Still we did manage to download the latest results; (see attached).
Not a brilliant morning; apart from the problems with my wiring, we seem too have a return of the Ethernet connector issue that we experienced some time ago. Even when it was working, it was extremely slow and ping response varied from 70% packet loss to 23% packet loss.
Still we did manage to download the latest results; (see attached).
- Attachments
-
- River_System_Results.zip
- (345.67 KiB) Downloaded 81 times
Terry
Re: Autumn/Winter November and onwards 2017 deployment(s)
More interesting this time:
Note: Perhaps buttspi's time is wrong?
universalmonitor.log:
Float_Switch.txt:
Hamish
Note: Perhaps buttspi's time is wrong?
universalmonitor.log:
- Couldn't connect to sumppi.
- Failed with a critical error on the 14th, then restarted.
- ^ Did we restart the software then? Was this an issue I fixed or a result of us messing with stuff?
- ^ May need further investigation/debugging.
- ^ May also not, because Sockets is more reliable and failure-proof now.
- Lots of null characters in the middle. Data corruption?
- Ends on the 14th?!
Float_Switch.txt:
- Null character here too - corruption?
- All seems fine.
- All seems fine, but note the sump level issues we were having the last few days.
- We need to fix some leaks.
Hamish
Hamish
Re: Autumn/Winter November and onwards 2017 deployment(s)
I thought the 14th was when we shut down the system and I took the hardware away for updating.
Terry
Re: Autumn/Winter November and onwards 2017 deployment(s)
Yeah, think so. Still though, any idea why we would have corruption/strange errors at that point in time?
Hamish