|
|
|
|
|
|
|
|
 |
|
Frequently Asked Questions
|
|
|
|
| |
|
|
|
My Temperature Sensor or Temp/Humidity Sensor experiences periodic spikes in its values or readings. What can I do to stop these spikes?
When experiencing sensor spikes or exceptionally high/low ranges of values, the usual culprit is EMI (Electro-Magnetic Interference). EMI is usually generated by florescent lights, large motorized machinery, high powered cables, or any other device that may generate an Electro-Magnetic Field. To ensure that EMI is the cause of the issue, AVTECH recommends a series of basic test in an effort to minimize the effects. In general, increasing the distance of a sensor from the AVTECH monitor will also increase the chances of EMI causing sensor spikes. This is because the sensor's cable is typically effected by EMI from the surrounding equipment as opposed to the three inch probe itself. If possible, please take down any sensor deployed and coil it up right next to the monitor. If the sensor is connected to any extensions please remove them and connect the sensor directly to the monitor. By letting the monitor run with the sensor in this close coiled up state, the EMI effect should be minimized, and spikes in temperature or humidity are typically pacified. If this is the case, then it has been successfully determined that the cause of the spikes are in fact EMI. Unfortunately, there is not much to be done to prevent EMI, it can only be avoided in the monitoring environment. AVTECH suggests routing all sensor's cables away from any of the major causes of EMI as previously stated or changing the location of the monitor itself to be closer to the sensor's destinations. Minimizing the length and proximity of the sensor and its cable from EMI is the goal of this relocation.
If the above relocation and coiled up sensor cable tests are still yielding these spikes, the next recommendation is to relocate the monitor and its sensors to an isolated location such as an office to provide a trial atmosphere that is certain to be free of EMI. This should completely eliminate any EMI spikes from the interfering environment so the sensors should now provide accurate and consistent readings. For more information on discovering your unit after it has been relocated, please follow this link: http://avtech.com/Support/index.php?action=kb&article=73
There is a quick work around that generally avoids alerts from being triggered when encountering any EMI interference. (FIX REQUIRES AVTECH DEVICE MANAGER and its advanced alert settings). When EMI strikes, it usually occurs in short bursts, often less than a second of duration. To avoid this, there is a setting that can put alerts on a delay in the Device ManageR software. With this short delay, Device ManageR will have enough time to check the readings taken from your monitor 2 or 3 times to verify the values received for alert status. To do this, open Device ManageR and on the left hand side, click the 'Alerts / Tasks' button. Next, expand the green heading in the middle of the page that is labeled 'Action / Notification List'. In this category, click the list being used and press the 'Edit' button. This will call the 'Edit Action / Notification List' pop up window. Notice the field where each of your 'Alert Actions' are listed. Click on one of these Alert Actions and press 'Edit' below it. In this new pop up window there is a category called 'Start the Action after ____ seconds'. Here, we will need to change this value, (0 by default) to a number that is higher than the Device ManageR's Discovery refresh rate. By doing this, whenever the alert triggers, Device ManageR will wait to trigger the alarm until it reaches this set value. For example, if the refresh rate for Device ManageR is 15 seconds, you can set the 'Start this Action after' to 40 seconds. Your Device ManageR will be checking 3 times, once at 0, 15, and 30 seconds for a sensor value that is above the alert threshold. In this time, any spikes will come and go, and Device ManageR will not trigger an alert because the quick spike did not sustain the elevated threshold for longer than 40 seconds. Once modified, click the 'Save' button at the bottom of both pop up screens to properly save. This delay will have to be changed for each 'Action' listed in an 'Action/Notification List' if multiple actions are configured by following the previous method.
If the sensors are still experiencing spikes in their readings after being physically relocated, attempt to isolate the issue to a specific piece of hardware. Switch sensors around in different ports and see where the spikes follow and check if other sensors without spikes begin spiking when ports are changed. The goal is to determine if the issue lies with the environment the monitor is in, the monitor itself, or with the sensor. If any discoveries have been made here and none of the above steps seem to resolve the issue, please contact the Technical Support Team at Support@AVTECH.com and explain each attempt made and any discoveries about the hardware in detail. Please note that all AVTECH sensors and monitors respond to EMI in the same manor. Any AVTECH equipment in an environment with high EMI will unfortunately continue to get unfavorable results.
|
|
|
|
|
|
|
|
|
|
|
888.220.6700
Sales@AVTECH.com
AVTECH Software, Inc.