Has anybody else noticed that the their DS18B20 sometimes doesn't work properly if they "Exit" out of OAP and then launch OAP again from the Raspbian desktop? Following a failure like this, mine only works properly again if I shutdown completely and then boot up the system fresh. However, if I only reboot after a failure like this, the device doesn't show up in the file system and I end up getting readings such as 3865470597°F in OAP.
Is it possible that OAP is sometimes not releasing the device properly when OAP is closed and/or when a reboot occurs? Or is this likely a problem with the w1 kernel driver or the Raspberry Pi firmware? Again, this only happens sometimes. Perhaps only after OAP has been running for a while.
Usually the device shows up and works properly:
But sometimes (usually following an Exit of OAP after it has been running a while), the sensor no longer works or even shows up again until I shutdown and boot up again:
dmesg and vcdbg log msg output don't appear to show any related error messages. This may be difficult to reproduce since it doesn't always happen and it usually only happens after running OAP for a while. If a OAP log file would help in troubleshooting this issue, I'll try to get one following the next time this issue occurs.
Is it possible that OAP is sometimes not releasing the device properly when OAP is closed and/or when a reboot occurs? Or is this likely a problem with the w1 kernel driver or the Raspberry Pi firmware? Again, this only happens sometimes. Perhaps only after OAP has been running for a while.
Usually the device shows up and works properly:
pi@raspberrypi:~ $ ls -l /sys/bus/w1/devices
total 0
lrwxrwxrwx 1 root root 0 Mar 30 23:03 28-0306979450d6 -> ../../../devices/w1_bus_master1/28-0306979450d6
lrwxrwxrwx 1 root root 0 Feb 14 2019 w1_bus_master1 -> ../../../devices/w1_bus_master1
But sometimes (usually following an Exit of OAP after it has been running a while), the sensor no longer works or even shows up again until I shutdown and boot up again:
pi@raspberrypi:~ $ ls -l /sys/bus/w1/devices
total 0
lrwxrwxrwx 1 root root 0 Feb 14 2019 w1_bus_master1 -> ../../../devices/w1_bus_master1
dmesg and vcdbg log msg output don't appear to show any related error messages. This may be difficult to reproduce since it doesn't always happen and it usually only happens after running OAP for a while. If a OAP log file would help in troubleshooting this issue, I'll try to get one following the next time this issue occurs.