Temp sensor reading jumps to 0 degrees F spontaneously

Running USB Watchport Temperature sensor with driver ver 3. Watchport Manager Build 1.19.07.

The temp sensor reads out correctly for a few days and then sends out a 0 degrees F reading once in the middle of the night. The readings then return to normal for a couple days after which it happens again. It happens at a different time in the middle of the night and its just one reading that comes out to 0 F.

Tried running virus scanner to see if it keeps a log file open but can’t determine the issue.

We send all out of range alerts to an on-call pager so the tech is getting annoyed… :slight_smile:

Any ideas?

J

Has this issue always happened since you setup this scenario (this PC + sensor + Watchport Manager)? Or did this issue “suddenly” start happening?

We just setup the sensor last week so it’s been happening from the beginning.

Sounds to me like a hardware issue but let’s first rule out the driver version you’re running as well as Watchport Manager.

  1. To update the driver, the easiest way to do this is to download the latest driver from this link:

http://ftp1.digi.com/support/driver/40002537_F.exe

Then extract the contents to the default c: emp folder, open “edgeport.cab” and extract “edgeser.sys” to “c:\windows\system32\drivers” overwriting the existing one.

Reboot the PC afterwards and confirm that the driver was update, by opening the Edgeport Configuration Utility (start menu shortcut), clicking the Version tab and noting the version of “edgeser.sys”. It should be 5.xx.xx.

  1. To update Watchport Manager, first make a note of any custom configuration settings you’ve done because we will be uninstalling it instead of installing the newer version over the top.

Then uninstall the existing version of Watchport Manager via Add or Remove Programs in Control Panel.

Reboot the PC afterwards and then install the latest version of Watchport Manager which you can download from this link:

http://ftp1.digi.com/support/utilities/40002560_B.exe

Finally, have Watchport Manager auto-detect the sensor, re-configure it the way it was, and then monitor the behavior. Let me know if this seems to help or not.