We're entertaining using a Raspberry Pi based-device for some aspects of the Otolith work on the elephants for various reasons that are better captured in another issue or elsewhere. We do want to, however, have a quick and dirty way to check WiFi connectivity on the run tomorrow. Part of our plan is to run this command on another machine on the network while the pi is deployed:
ping -i 60 IP_ADDRESS | ts "%Y %m %d %H:%M:%S" | tee ping_record.log
We won't have a GPS track on the Pi but we will have a video recording so it is plausible that we could compare this with the ping record to get a sense of where there was connectivity.
It would be useful to have some scripts that process the ping record into something more useful in visualizing where there was connectivity so this issue is for tracking that effort.
We're entertaining using a Raspberry Pi based-device for some aspects of the Otolith work on the elephants for various reasons that are better captured in another issue or elsewhere. We do want to, however, have a quick and dirty way to check WiFi connectivity on the run tomorrow. Part of our plan is to run this command on another machine on the network while the pi is deployed:
ping -i 60 IP_ADDRESS | ts "%Y %m %d %H:%M:%S" | tee ping_record.logWe won't have a GPS track on the Pi but we will have a video recording so it is plausible that we could compare this with the ping record to get a sense of where there was connectivity.
It would be useful to have some scripts that process the ping record into something more useful in visualizing where there was connectivity so this issue is for tracking that effort.