Watchport Manager, a free software application for interfacing with Watchport USB sensors is no longer supported, primarily because it's older (last tested under Windows XP, so there could be issues with newer Windows OS's) and we no longer have any engineering resources to back it (so bugs and feature requests will not be pursued). This software is still offered on our website as a courtesy and should be treated "as is" without any support.
We have a walkthrough video on our website that's older (like the software) but goes through all the settings, so it's technically up-to-date.
SensorServ is essentially a newer version of Watchport Manager that was designed from the ground up to be run as a Service instead of an Application (Watchport Manager is an Application). SensorServ is also unsupported and provided as a courtesy, as-is.
If a customer is interested in trying out SensorServ, the following instructions may be passed along to them:
Thanks for your interest in beta testing SensorServ! SensorServ is intended to eventually replace Watchport Manager. The main feature of SensorServ is that it runs as a Windows Service, since Watchport Manager does not offer that feature. Unfortunately, there are currently no plans for future development of SensorServ, however that may change in the future.
*** Please note that SensorServ is BETA software and should thus be treated "as is". ***
1. Make sure you have the latest Microsoft .NET Framework and Service Pack installed before proceeding.
2. Make sure the Watchport Sensor(s) you plan to use with SensorServ is connected to the PC and installed. Watchport Sensors use the Edgeport driver, which can be downloaded from our support site.
To confirm the sensor is installed, launch the Edgeport Configuration Utility from the start menu, in the Digi USB program group. All Watchport Sensors that are attached and installed should be listed in the white area under the General tab.
3. Create a folder on your hard drive called "sensorserv". i.e. "c:\sensorserv"
4. Download the following file:
5. Extract the contents into the "c:\sensorserv" folder.
6. If you have our Watchport Manager software installed, be sure to close it and stop it from auto-starting, before proceeding. These two programs cannot be run at the same time.
7. Launch ServiceConfig.exe. It should detect all attached Watchport sensors. Click the blue-colored "Install Service" button at the top-left to install the SensorServ service. You must agree to the EULA in order to install the service.
8. Go through the tabs and configure as needed (see Notes just below for what isn't yet supported), then click the Save and Exit button. Choose Yes to start the service, when prompted.
Configuration instructions and other notes:
A. ServiceConfig.exe should only be used when the SensorServ service is stopped If you need to make configuration changes, be sure to first Stop the service (start, Run, "services.msc" and look for SensorServ). You would then click the Save and Exit button in ServiceConfig.exe and choose Yes to start the service, when prompted. We plan to make a change in the future so that the SensorServ service does not have to be stopped in order to make configuration changes.
B. Group Management (the "Manage Groups" tab) is not yet supported and will be in a future release.
C. To send alert e-mails to multiple recipients, use a comma (no space) to separate "to" e-mail addresses.
D. We don’t yet have a user manual. However, the options in the Configurator program should be mostly self explanatory. Still, if you have any questions, please let us know and we’ll be glad to help.
E. At this time, SensorServ supports the following Watchport Sensors: Watchport/D - Distance or Proximity combo sensor, Watchport/H - Humidity & Temperature combo sensor, and Watchport/T - Temperature sensor.
F. Currently, the only kinds of alerts that are available are e-mail alerts (compared to Watchport Manager, which offers phone alerts, etc.).
G. Most users will be mainly interested in getting e-mail alerts sent when a temperature threshold has been crossed, i.e. the temperature is too high. In order for this to happen, go to the "Alert Settings" tab in ServiceConfig.exe and CHECK "Out of range" in the "Send Alerts For:" section at the top-right. Of course, the SMTP server information also needs to be filled out.
H. To see the current status of a sensor, go to the "Sensor Discovery" tab of the Configurator program (ServiceConfig.exe), right-click on the sensor, then choose the menu option to show the status. You may need to click the “Show Advanced” button to do this. It's not possible to see the current status of a sensor once the service is running.
I. To see the history, go to the "Service Options" tab of the Configurator program and check “Comma Delimited (.CSV)” in the Output To section. The default "C:\WPS_Output.csv" folder/file name can be changed, if needed.
J. The 0.7.0.4 version above was tested fairly extensively by Digi and customers. Because of that, it's the version we recommend using. However, a newer 0.8.0.0 version was released afterwards, which did not get tested much since the SensorServ beta program was halted around that time. Still, you are welcome to try the newer 0.8.0.0 version by downloading the two files below and then copying and pasting them over the existing two files, overwriting them. Be sure to first stop the SensorServ Service.