To keep things up to date...

After initially removing PurpleAir-198e (labeled as #3) from the ISFS array because it isn't connecting to wifi, found that it connected ok to a spare dsm's wifi at base. So, back out to the array on the 30th to try to swap it back in (if both PurpleAirs can work with wifi, then better to have PurpleAir #3 set up, since PurpleAir-57ba (#2) doesn't have a working SD card slot). Ultimately unsuccessful, PurpleAir #3 having same problems as before with connecting to t44 dsm wifi. At the end of troubleshooting on 8/30, PurpleAir #2 still deployed at ISFS array. More details in this jira issue: https://jira.ucar.edu/browse/ISS-809

Noticed today that the new array PurpleAir hasn't been updating since around 8pm on the 30th (so, a few hours after we were at the array trying to swap the other one back in). Logging in that one is behaving in the same way as #3 which we removed from the array, namely: on, has a dns address, pingable, but no outgoing tcp packets showing up and browsing to its web interface from the dsm wifi doesn't work. Did some troubleshooting from the trailer and then out at the array, but long story short it seems to be having the same problem as PurpleAir #3 (more on jira: https://jira.ucar.edu/browse/ISS-810). If neither of the two can currently connect to dsm wifi at the array, we figured at least we could swap back to #3, which has a working SD card slot. So, current state is nothing showing up on the PurpleAir map, but we're hopefully recording data locally (though likely with the same bad timestamps problem as before).

  • No labels

1 Comment

  1. Isabel Suhr AUTHOR

    While out at the array today for other reasons, noticed that the PurpleAir-198e wifi network was still showing up. Once close enough, I could connect to its wifi and check that it's configured to connect to t44's dsm wifi, and re-entered and saved the password. At that point, same behavior as before (can ping the purpleair at its dhcp address, can't browse to it from t44 wifi). When I connect back to the purpleair wifi, it shows that it's connected to t44 and that the wifi is connected:

    except that it doesn't actually communicate over wifi.

    I'm guessing that whatever the purpleair checks to see whether it is connected to an external wifi network (and therefore can turn off its own wifi) is failing, presumably for the same reason that browsing to the purpleair over the dsm wifi doesn't work. I assume the purpleair wifi has been on since we plugged in this purpleair again yesterday, and I assume it'll stay on until/unless we can figure out how to properly connect to the t44 dsm wifi.