This morning, S15's EC150 stopped reporting. It appears to be associated with a ddn/dup at 1451 UTC. (There are several data files around this time. Data are in the file starting 1438 and not in the file starting 1451.) I've just tried eio 5 0/1 and failed to revive it. It also doesn't respond to <cr> to get a prompt. However, the station's Iload was constant during this period (and similar to the day before), which makes you think that the sensor is still trying to function.
FIXED: Somehow emode on 5 was back to 232 (even though it <should> have been set by the script pre_dsm.sh). I just manually entered: emode 5 422 and data started flowing.
2 Comments
Gary Granger
Yesterday morning we noticed one of the bluetooth mote connections went down (the previous night), and so I restarted dsm a few times attempting to diagnose the problem and restore the motes. Eventually I had to reboot the dsm, and then I didn't notice that the CSAT did not come back. Sorry. The details on the mote bluetooth problems are in JIRA ISFS-126. I assume the emode did not work on boot because of ISFS-125. That can be fixed with a package update on s15, but first I'll try to make sure there are no other custom changes that might be overwritten.
Gary Granger
Yesterday I checked that there weren't any local custom configuration changes on s15, and then I ran an update to get the emerald boot order dependency fix. At the time everything looked to be running same as before the update.