One

Top Level Category

Table of Contents

  1. Contents of Top Level Category
    1. Support (Post-sales related questions, literature...)
      1. Device ManageR
      2. Room Alert 26W
        1. Initial Discovery & Setup
        2. Status Screen
        3. Settings Screen
        4. Sensors
        5. Wireless
      3. Room Alert 24E
        1. Initial Discovery & Setup
        2. Status Screen
        3. Settings Screen
        4. Sensors
      4. Room Alert 32
        1. Initial Discovery & Setup
        2. Status Screen
        3. Settings Screen
        4. Sensors
      5. Room Alert 11E
        1. Initial Discovery & Setup
        2. Status Screen
        3. Settings Screen
        4. Sensors
      6. Room Alert 7E
        1. Initial Discovery & Setup
        2. Status Screen
        3. Settings Screen
        4. Sensors
      7. Room Alert 4E & Signal Tower
        1. Initial Discovery & Setup
        2. Status Screen
        3. Settings Screen
        4. Sensors
      8. TemPageR
        1. Initial Discovery & Setup
        2. Status Screen
        3. Settings Screen
        4. Sensors
      9. Device Discovery Utility
        1. Discovery
        2. Firmware Update
        3. Other Features

Top Level Category

Parent category to all other categories

Configuring AXIS Camera Name

Configuring a name for your AXIS camera is done through the Bonjour Settings in the AXIS Camera's web interface. To change the name of your AXIS camera, please follow the instructions below.

1. Select your AXIS Camera in the list of Discovered Devices in Device ManageR. Once it's selected, click on the 'Open Settings' option.



2. Select 'System Options' in the navigation list.



3. Select the 'Network' option, followed by the 'Bonjour' option.



4. Enter in the desired name for your AXIS Camera in the text field labeled 'Friendly Name', and then click the 'Save' button.



Once Device ManageR scans the network for changes, your AXIS camera should appear in the Discovered Devices list with the name you just configured.

How Do I Enable A Security Password On Room Alert Or TemPageR Monitors?

A password can be configured for each individual Room Alert or TemPageR to prevent unauthorized users from modifying the 'Settings' section.  Passwords should be alphanumeric and cannot include special characters or symbols.

To Configure A Password For Room Alert or TemPageR
  1. Type the IP Address of the monitor into a web browser to access the 'Status' page. (For Device ManageR, click the monitor in the 'Device Status' list, then select 'Open Web')
  2. Once the 'Status' page is displayed in the web browser, click the 'Settings' tab.
  3. Unless you have previously configured a password for the device, leave the user name and password fields blank and click 'OK'.  If you have previously created a password for the monitor, leave the user name field blank and enter the current password, then click 'OK'.
  4. When the 'Settings' screen displays, click the 'Security' button on the left side list.
  5. In this screen, enter the old password, new password, and confirm the new password. (If an old password is not set, leave this field completely blank)
  6. Click the 'Accept Changes' button at the bottom of the screen, then click the 'Save Settings' button in the left side list to reboot the monitor. The monitor will  reboot, and now require a password only to access the 'Settings' section.
To Reset An Unknown Password That Was Previously Set

All current Room Alert and TemPageR monitors feature a hard reset button on the back of the case. While the monitor is powered on and connected to an active network or crossover cable connection, please locate and hold down this reset button while watching the top left green light on the monitor's network port. This network light will go out for two seconds, then reappear to signify a complete reset. The monitor will now have factory default settings, which includes a blank password set for the 'Settings' section. Note that the unit will be configured for DHCP and any static IP set previously will need to be reconfigured.

If the monitor does not have a physical reset button, please contact AVTECH Technical Support and speak with one of our Technical Specialists.  

To contact AVTECH support, click here.

How To Use The Trace Feature On A Room Alert Or TemPageR Device

The tracing feature is a very useful tool that can be used to assist in troubleshooting issues with your Room Alert or TemPageR device.

To enable tracing on your unit, follow these steps:

       1.   Access the 'Advanced' tab of the 'Settings' page.


  

       2.   In the 'Trace Configuration' section, ensure that the 'Enable Tracing' check box is checked. The tracing port is 143 by default. You do not need to change this unless you know port 143 will be blocked by your network for some reason. After making changes in this section, click the 'Accept Changes' button at the bottom of the screen, then the 'Save Settings' button on the left hand side of the screen.




To generate a trace from your device you will want to enter the following command into a Windows command prompt: 'telnet -f c:\tracefile.txt <IP of unit> <trace port #>' then press the <Enter> key. Where 'IP of unit' is the IP address of your Room Alert or TemPageR device and 'trace port #' is the configured trace port (143 by default). So the command might look something like this: 'telnet -f c:\tracefile.txt 192.168.33.100 143'. This command will capture your trace data directly to a text file named 'tracefile.txt' in the C: directory.

Please note that Windows 7 and Vista have disabled the Telnet client by default. If you get an error saying 'telnet is not recognized as an internal or external command, operable program or batch file' you will need to enable it by going to 'Start', 'Control Panel', 'Programs And Features', 'Turn Windows Features On Or Off' then checking the 'Telnet Client' row and clicking 'OK'.


At times, it may be useful or necessary for our engineers to review a trace from a Room Alert or TemPageR device and we may request you send us the results of a trace. If you are requested to send a trace in by one of our technical support specialists, or if you feel it will be helpful before being asked, simply attach the file created by the command given above to an email and send it to us at 'Support@AVTECH.com'.

One example of how to use the tracing feature is for troubleshooting email issues with your device. To troubleshoot email issues using the trace feature, launch the trace window using the process described above. Once you have successfully connected to the trace, browse to the 'SMTP Email' tab on the 'Settings' page. Try sending an email by clicking the 'Send Test Email' button at the bottom of the SMTP Email tab. You should see the attempts by the Room Alert or TemPageR device to connect to the configured mail server in the trace output window. If there are any issues occurring with the email process, you should see corresponding errors displayed in the output window which should point you in the right direction as to what might be causing any issue.

I am unable to get my Room Alert or TemPageR monitor to send email alerts properly. How do I send email alerts directly from the monitor's web page?

Email alerts from the Room Alert or TemPageR monitors are sent using anonymous, unauthenticated SMTP email on TCP port 25. If email notifications are not received, first verify the email settings in the 'SMTP Email' section of the 'Settings' page.
  1. Mail Server Port: This port is typically port 25 but can be different based on personal mail server settings and network preferences. Please check with the mail server administrator for the exact port number.
  2. Mail Server: If the monitor is configured to obtain an IP address using DHCP, enter the specific IP address of the mail server in the ‘Mail Server Address’ field. If the monitor is configured with a static IP address, the DNS name for the mail server can be entered in this field. For initial testing purposes, enter an email address from the same domain as the mail server in the ‘Email Recipients’ field. For example, if the domain name is 'Example.com', be sure the email used to test is from the same domain (i.e. YourEmail@Example.com).
  3. Return Address: To finish the configuration, enter the same email address in the ‘Return Address (From)’ field. Using the same domain name minimizes the risk that security settings on the email server would prevent the message from being delivered.
  4. Display URL: The display URL is a URL that will be at the bottom of your received email alert. This URL is here to allow quick link/access to any URL after an alert is triggered. This URL can be a link to any web page you would like, but typically we assume that quick access to your Room Alert's web page is necessary here. Type in the IP address of the monitor or any other web page that is desired in this field.
  5. Authentication: This field is optional because not all mail servers require authentication. Please check with the mail server administrator if there are any questions about this field. The Username and Password would typically be the same credentials used to log on to a mail server directly.
  6. Email Recipients: List the email addresses that the alert will be sent to and separate multiple addresses by a comma. For example, John@Example.com,James@Example.com,Steve@Example.com Please note that due to limited flash memory on the Room Alert and TemPageR monitors, the Email Recipients field is only 79 characters long. For more space, AVTECH recommends creating a distribution list in the email server itself or for unlimited email entries and advanced/custom alerting, please follow this link for AVTECH Device ManageR: http://avtech.com/Products/Device_ManageR/


     Once the email settings are configured, click the ‘Test Email’ button and check the email account(s) for the test email. If the message is not received, first check any spam filter that may be in place. If the test email cannot be found, it could be blocked by the mail server. Be sure the mail server is configured to allow 'SMTP Relaying' from the IP address of the monitor. Also, be sure the Room Alert or TemPageR is on the email server's 'whitelist' to prevent messages from being filtered or blocked as spam. If messages from the monitor continue to be blocked by the mail server, contact the mail server administrator to see if the mail server logs can be reviewed to determine why the messages are being blocked.

If you have followed the steps above but are still unable to receive email alerts, please contact our Technical Support Team by
submitting a support ticket.

Temperature Conversion Formulas

[F = Fahrenheit, C = Celsius]


To Convert Celsius To Fahrenheit

F = 1.8C + 32


To Convert Fahrenheit To Celsius

C = F – 32
          1.8

What is the Default 'Settings' Screen Password on Room Alert or TemPageR?

The 'Settings' screen of Room Alert and TemPageR is password protected to prevent unauthorized users from modifying the settings. By default, there is no user name and password configured to access the 'Settings' screen of a Room Alert or TemPageR. With the User Name and Password fields left blank, select 'OK' to access the 'Settings' screen.

If you have previously configured a password for the device, leave the User Name field blank and enter your password in the 'Password' field, then select 'OK' to access the 'Settings' screen.

Support

Post-sales related questions, literature materials and/or other items involving AVTECH Software products and/or services.

How Do I Update The Firmware On My Room Alert Or TemPageR Monitor?

- Verify that you have either the AVTECH Device Discovery Utility or Device ManageR software installed on a host machine that has network visibility to the Room Alert or TemPageR monitor that is to be updated.
 - Verify that the software being used is the most current version of AVTECH Device Discovery or Device ManageR. The most current versions can be obtained via the 'Downloads' section of AVTECH.com for current MSUS subscribers.


Note which firmware version the Room Alert or TemPageR is currently running by checking the monitor's 'Status' page. The monitor's version will be in the top right hand corner.

Click here: http://avtech.com/Downloads/ and check the left side box for a list of AVTECH's released versions. If your current firmware version is older than the version listed here, please continue by logging in to the 'Downloads' section. (If you do not know your login password or if you are unsure if you  have an account, click the 'Forgot/Reset Password' link and enter your email address. If your email address is not recognized, click the 'Email Request/Inquiry' button and fill in your information. If your email address is recognized but you do not receive an email with your password, check any SPAM filter in place before contacting AVTECH Technical Support.)

Once in the downloads section, navigate to the monitor's section. Save the firmware update file but DO NOT unzip/decompress the file if it arrives as a .zip or .upd file.


DEVICE DISCOVERY UTILITY: Open Device Discovery and click the 'Search' button. 



Select the monitor that is to be updated and click the 'Update' button.

 


Follow the prompts to specify the location of the Firmware Update file for the monitor and click the 'Upload' button.

 



DEVICE MANAGER: Open Device ManageR and select the monitor from the Device Status list or click on the unit's information in the middle of the page.



Click the 'Update Firmware' button.



Click 'Browse'.



Select the appropriate file and click 'Open'.



Click the 'Update' button to begin the firmware update process.



When the firmware update process completes, the unit will automatically reboot to apply the update.
If you experience an issue during this process, please feel free to contact the Technical Support Team by submitting a support ticket.

How do I extend my Digital Sensor Cable longer than the supplied 25 feet?

By design, external digital sensor cables are 25 feet in length and can be extended up to a supported100 feet in total length.

To extend the sensor cable, you will need a RJ-11 cable with coupler which is available from AVTECH Software.

To order these cables, contact your Product Specialist or click here to purchase on-line.

To extend an external digital sensor cable:

  1. Remove the external digital sensor to be extended by unplugging its RJ-11 cable from the front of the unit.
  2. Using a 25 foot RJ-11 cable with coupler, insert the RJ-11 connector into the AVTECH unit’s external sensor port.
  3. Plug the RJ-11 connector on the sensor cable to the extension cable.

If you wish to extend the sensor up to the supported 100 feet in length, multiple RJ-11 extension cables can be connected using the methods above.

It is important to note that AVTECH does not recommend extending a cable to a greater distance than 100 feet and does not support splicing or cutting into existing wires to shorten or lengthen the provided cable.



Internal Temperature Sensor Can Be Higher on Powered WiSH Sensors

The Powered Wireless Sensor Hub (P-WiSH) is a wireless sensor that transmits sensor data from internal and connected sensors back to the Room Alert 26W. The P-WiSH has one internal Digital Temperature Sensor and two external digital sensor ports. The P-WiSH is powered by an AVTECH 5V Power Adapter and has internal circuitry to regulate this power. The heat generated by the internal power regulator can cause the internal temperature sensor to report a slightly higher temperature when compared to one of its external sensors or a third party thermometer. This is normal, and the internal temperature reading can be adjusted using the 'Adjust' field in the Room Alert 26W or Room Alert 32W Settings. For more information on the adjust field and how to change it, click here.

Trouble/Issues Accessing the 'Downloads' Section of AVTECH.com

The 'Downloads' section on AVTECH.com is AVTECH's only source of Device ManageR, Room Alert/TemPageR firmware updates, Software updates, MIB files, Device ManageR plugins, and the Device Discovery utility. To gain access to this section, AVTECH will issue a username and password to all contacts that are employed by organizations that have purchased a Room Alert or TemPageR environmental monitor.

If you have been previously issued a username and password from AVTECH: When attempting to log on to the AVTECH Downloads section, make sure that the password being used is entered correctly as the password is case sensitive. Please note the email address that was initially given to AVTECH at the time of registration is the only email that can be used to log on to this section.

If the initial password for the 'Downloads' section of AVTECH.com has been lost or forgotten, go to AVTECH.com/Downloads/ and select the 'Forgot/Reset Password' link below the login section. Enter the registered email address in the new screen and select 'Submit'. If the email address matches a record that was previously created in AVTECH's registry, an email will be sent with the required password.

If you are able to access AVTECH's downloads, but your downloads are expired: The specific downloads provided to your organization are regulated by AVTECH's Maintenance, Support, and Update Service (MSUS). MSUS is an annually renewed service for each of the Room Alert and TemPageR units owned by the organization. If MSUS needs to be renewed, please send an email to RenewMSUS@AVTECH.com including the organization's name and your personal contact information. For more information on MSUS, please refer to this page link:  http://www.AVTECH.com/PDFs/AVTECH_MSUS_Explained.pdf 

If you are a new contractor or temporary hire and require access to AVTECH Downloads: Please provide the following information in an email to 'Support@AVTECH.com' along with a short message explaining the need for access. Once approved, you will be registered as a contractor or temporary hire directly under the organization that owns the Room Alert or TempageR product. Please include the following information in this email:

Organization Name
Organization Address
Organization Phone Number
Your Full Name
Direct Phone Number
Email Address
Job Title
Summary Of Work To Be Completed

For all other issues accessing the 'Downloads' section of AVTECH.com, send an email to 'Support@AVTECH.com' and we will be able to provide further assistance.

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.


My Room Alert Or TemPageR Monitor Is Not Discoverable Or Accessible On My Network. How Do I Discover My Room Alert Or TemPageR?

Device ManageR and the Device Discovery Utility use a broadcast scan on UDP port 30718 to automatically locate AVTECH monitors on a network.
AVTECH recommends the following for initial product discovery:
 - DHCP Enabled on network.
 - UDP Broadcasts allowed at a computer and network level.
Please Note Before Beginning:
 - The network cable must be plugged in to the Room Alert or TemPageR monitor and the switch or computer before power is connected. This ensures that the initial DHCP request will be sent successfully when power is connected.

 - If the monitor has been assigned a static IP address that is invalid for the current IP address range of the network, please proceed to step 3 of this guide.
 - When the Room Alert or TemPageR monitor is powered on and plugged into a network, please check the current status of the Network Jack's lights as these lights are used to determine the current state of the monitor. The left link light should be a solid green color while the right light should be a flashing green or orange. If these lights display any other patterns than this, please skip to step 5 of this guide.

To begin discovering the monitor's IP address, please follow the instructions below starting at step 1.

1. Both Device ManageR and the Device Discovery Utility have a manual discovery feature that uses a TCP scan on TCP port 30718. This feature is helpful if the network range or specific IP address of the monitor is known. 

 - To access this feature using Device ManageR, click the 'Advanced Discovery Options...' button under 'Device Status' in the left menu. Click the 'Manually Add Device/s Via IP Address' button and select either 'Single IP Address' or 'Range Of IP Addresses'. Insert the desired IP address or range and click the 'Begin Scan...' button.

 

 - To access this feature using the Device Discovery Utility, click the 'Advanced Discovery' button located under the 'Search' button. Then, select either 'Single IP Address' or 'Range IP Addresses' and enter the single IP address or IP address range. Start the scan using the 'Begin Scan' button.


2. DHCP Enabled On Network – All AVTECH monitors are initially set to obtain an IP address automatically using DHCP. DHCP must be enabled on the network for the monitor to receive a valid IP address. If DHCP is not enabled, the monitor will default to an auto IP address in the 169.254.xxx.xxx range. At this IP address, the router or system firewalls may not allow discovery because the IP address is outside of the valid network IP range. Valid assignment could potentially be hindered by a managed switch even if DHCP is enabled. If DHCP assignment is delayed in the managed switch, the DHCP request sent from the monitor can timeout and default to a 169.254.xxx.xxx Auto IP address.

 - If DHCP is enabled on the network, there is a chance the DHCP server has already assigned a valid IP address even though the monitor is not discoverable. If the manual discovery option from step 1 does not discover the monitor, the IP address can sometimes be obtained by checking the DHCP server for the MAC address of the monitor.

 - If the IP address can be verified by checking the DHCP server and the IP address is in range of the network, it can be added to Device ManageR and the Device Discovery Utility using the manual scan feature from step 1. This IP address can additionally be accessed by directly by typing the IP address in a web browser. 

 - It is also possible to create a DHCP reserved IP address on a server. Doing this and recycling the power on the monitor should allow the IP address to be assigned by the DHCP server. If this process is unknown or unable to be completed personally, please consult the local Network Administrator. Otherwise, continue to the next step.

3. If the IP address of the monitor is still not discoverable, AVTECH recommends connecting the unit directly to a computer or laptop using a cross-over Ethernet cable or spare network hub.

 - Before disconnecting a computer or laptop to be used from the current network, be sure that the Device Discovery utility is installed along with a protocol analyzer (packet sniffer) application. If a preferred protocol analyzer application is unknown or not installed, a free utility called 'Wireshark' can be installed from http://www.wireshark.org/.

 - Begin by assigning a static IP address to the computer's network card, then connect the monitor via cross-over Ethernet cable or spare network hub to the computer. Lastly, plug in the power to the Room Alert or TemPageR monitor to begin the connection process. 

 - Attempt discovery using the Device Discovery utility by clicking the 'Set IP' button. The 'Set IP' button can set an IP via the MAC address which can be found at the bottom of any Room Alert or TemPageR monitor's case. Follow the procedure as prompted by Device Discovery and remember to set the IP to a valid IP address that is within the same subnet as the IP set for the computer's network card. After doing this, the monitor should be accessible via the Device Discovery list or by directly entering the newly set IP address in a web browser.

4. DHCP alternative to the static IP settings above: While still on the cross-over cable direct connection between the computer and monitor, the Room Alert or TemPageR may also be reset back to initial DHCP factory defaults via the reset button on the back panel of the monitor (if applicable). 

- For TemPageR3E, Room Alert 4E, 11E: Hold the reset button in for 10-15 seconds until the top left LED on the Ethernet jack blinks. A reset has occurred when this light on the ethernet jack goes out, then reappears 1 second later. Please release the reset button after this occurs.

 - For Room Alert 24E, 26W, 32E/W: Hold the reset button in for 10-15 seconds and watch the 3 main status lights on the front of the monitor. A reset has occurred as the front 3 status lights cycle through red and then finish cycling. Please release the reset button after this occurs.

 - With the unit now set back to DHCP factory defaults, change the laptop's network card settings to automatically obtain an IP address as opposed to specifying a static IP. Start up the Device Discovery utility and click 'Search' to locate the monitor.

 - If the Device Discovery utility methods are not working and the above steps have not located the monitor, start the protocol analyzer application, Begin packet capture and recycle the power on the monitor. Look for incoming packets coming from the MAC address of the monitor (located on a sticker on the bottom of the monitor's case or on the back of a rack mount kit if applicable). One of these packets should contain the source IP address of the monitor. Once this IP address has been obtained, configure a static IP address on the laptop or computer that is within a valid network range in relation to the IP address assigned to the unit as in step 3 (i.e. IP of unit: 192.168.2.3 - IP for computer or laptop: 192.168.2.4). The monitor can now be directly accessed by entering the IP address in a web browser.

5. If the above trials have been unsuccessful in discovering the IP address of the unit, please email Support@AVTECH.com with the packet capture obtained in step 4 attached to the email.

Room Alert/TemPageR Sensor Data Not Loading

The Room Alert and TemPageR devices load the sensor data for display on the Status page using a background xml http request to a file called "getData.htm".

If sensor data is not loading, first verify that the 'getData.htm' web page is accessible by entering "http://<ip_address_of_device>/getData.htm" in the web browser location bar. 

Example 192.168.2.95/getData.htm   

You should see the following output.......





If the data fails to load, the cause can usually be traced to a proxy server or Microsoft ISA server. If your network has a proxy server or Microsoft ISA server, be sure that it is configured to ignore requests to and from Room Alert. Also verify that you do not have any local Internet security, anti-virus, or firewall applications that may be blocking, filtering or caching the background requests to this page.

A shorter test can also be used by entering in  http://ip_address_of_device/mobile.txt    Example 192.168.2.95/mobile.txt    you should see the following output....




If you see an image loading like the one above, your issue is related to either a web browser, security device/application or anti-virus program blocking requests and traffic made to the unit.  You will want to further examine  your  current security settings on your security applications and devices running on your pc and on your network.  


Please feel free to contact our Support Team at Support@AVTECH.com with any further questions.

How To Enable Telnet in Windows Vista and Windows 7

In certain cases, it may be necessary to Telnet into an AVTECH device to modify its settings or view the trace output when directed by Technical Support to do so.  By default, the Telnet client is disabled in both Windows Vista and Windows 7.  It is a simple process to get them enabled, and those steps are detailed herein. 

1.) Click on the 'Start Menu' button and click on the 'Control Panel' button. 

NOTE: If you cannot locate the 'Control Panel' button follow these instructions, otherwise skip to step 2.):

     

2.) Double click on the 'Programs and Features' option

3.) Click the 'Turn Windows Features On or Off' option



4.) A new window will appear.  Place a check mark in the 'Telnet Client' option and click 'OK'



5.) A window will appear with a status bar.  Once this windows disappears, the Telnet client has been activated

How To Enable TFTP In Windows Vista And Windows 7

In certain cases, it may be necessary to upload specific files to an AVTECH device when directed to do so by Technical Support.  By default, the TFTP client is disabled in both Windows Vista and Windows 7.  It is a simple process to get them enabled, and those steps are detailed below. 

1.) Click the 'Start Menu' and then the 'Control Panel' button. 

NOTE: If you cannot locate the 'Control Panel' button follow these instructions, otherwise skip to step 2.):

   

2.) Double click on the 'Programs and Features' option

3.) Click on the 'Turn Windows Features On or Off' option



4.) A new window will appear.  Place a check mark in the 'TFTP Client' option and click 'OK'



5.) A window will appear with a status bar.  Once this windows disappears, the TFTP client has been activated

How Do I Configure A "Dial Out Via GSM Modem" Action?

In order to 'Send an Alert Via GSM'. It is recommended that you first configure and successfully test your Modem in the 'External Modem' section located in the main 'Settings' screen.

For more details see the FAQ article  "How To Configure External Modem Settingshttp://Avtech.com/Support/index.php?action=kb&article=111

Once the test has completed successfully, you can then create the 'Action' that will send the 'Alert via GSM' and will be triggered after a previously configured alert threshold is exceeded. 


Listed below are the steps required to configure Device ManageR to 'Send an Alert via GSM'.


1.Click on the 'Alerting' tab on the left navigation menu of Device ManageR to expand the available options. 


2.Select 'Actions' to expand the list of currently configured 'Actions'.


3.Click the 'Add' button to create a new 'Action', and select the 'Send Alert Via GSM' for the 'Action Type'.

 


 


4. Enter text in the 'Name' field that will make it easy to identify this Action. This is what will be shown in the lists where the Actions are displayed.

In the 'Description' field it can be helpful to provide a more detailed description of this Action. Since the option allows for specific contacts to send the Alert to, you may wish to describe the action with some further explanation as to who will be receiving the message.

In the example below we have described the alert   'GSM Alert to Administrator'.


 

5. The next step is to configure a 'Contact', or to select a previously configured 'Contact' from the drop down. Click the 'Add' button to configure a new 'Contact' or click the 'Edit' button to edit an existing 'Contact'




Depending on the plug-in installed different Contact configuration options might be available. These could include 'Email', 'Modem', and 'GSM' contact notification methods.







6. -The 'Message field is the actual text message that will be sent to the selected 'Contact'. This message can be customized with desired text or can also be configured to accept additional keywords. To modify the message by inserting text, or to insert a special keyword, simply click within the 'Message' field.

Note that the 'Insert An Alert Keyword' button will become available when the cursor is in the 'Message' field. 










7.Click 'Save' to save the new Action.


Now that the 'Send Alert Via GSM' Action has been created, it can be used in an 'Action/Notification List' .


For additional information regarding configuring an 'Action/Notification List', please see the following FAQ Article....   

"How To Configure Action / Notification Lists In Device ManageR"

http://avtech.com/Support/index.php?action=kb&article=91


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.

Experiencing High/Low Temperature Spikes

When experiencing sensor spikes or exceptionally high/low ranges of values, we have found that the usual culprit is Electro-Magnetic Interference (EMI.) EMI is typically generated by florescent lights, air conditioning units, large motorized machinery, high powered cables, or any other device that may generate an Electro-Magnetic Field. To confirm whether EMI is the cause of your issue, we typically recommend a basic test to try to minimize the effects of it. If possible, you should take down any sensor you have deployed, and coil it up right next to the monitor. If your sensor is connected to any extensions, please remove them and connect the sensor directly to your device.

With the sensor in this close coiled up state, you should not receive any more unexpected spikes in temperature. If this is the case, then we have successfully determined that the cause of the spikes is EMI. The best way to mitigate spikes caused by EMI is to avoid likely sources of it. We suggest routing your sensor's cable away from any of the major causes of EMI, such as florescent lights, air conditioning units, large motorized machinery, and high powered cables, or changing the location of your AVTECH device to be closer to your sensor's destinations. Minimizing the length and proximity of your sensor and its cable from EMI is the goal of this relocation.

If you are still receiving these spikes while your sensors are in this coiled up test state, we recommend relocating the entire monitor and its sensors to an isolated location to run the device for an adequate trial. This should completely eliminate any EMI spikes from the interfering environment so your sensors should provide accurate and consistent readings. Setting up a remote location for testing is very easy to do with a laptop or desktop computer. Simply connect your AVTECH device directly to your computer's network card with a crossover cable. You can monitor the sensors connected to the device with the Room Alert web interface, or better yet, you can download another copy of AVTECH Device ManageR from our website to access a graph of the monitor's activity on your test computer.

If your sensors are still experiencing spikes in their readings, you should attempt to try to isolate the problem. Connect sensors to ports and see if the spikes follow the sensor. We will need to determine if the problem lies with the environment the monitor is in, the monitor itself, or with the sensor attached to the monitor. If you have reached this point and feel that you have given the above tests a fair trial, please contact our Technical Support team at Support@AVTECH.com and we can explore further options for you.

Device ManageR

Manually Testing A GSM Modem

Manually Testing A GSM Modem

To test a GSM modem first connect the modem to the host system of Device ManageR using the documentation provided with the corresponding GSM modem. Once it is connected properly be sure to install the latest drivers compatible with the operating system that the host system of Device ManageR is running on. The driver should be available from the manufacturer of the modem and will ensure that the host system is able to connect properly to the modem.

Once the modem is properly connected to the system with the latest compatible driver installed, the modem should be mapped to a COM port on the system. To determine which COM port the modem is mapped to you will need to navigate to the system's 'Device Manager' by using the below steps (note this is from a Windows 7 system)

'Start Menu' => 'Control Panel'
=> 'System and Security' => 'System' => 'Device Manager'




Next if the modem is recognized properly it should be found in the 'Modems' section of the available hardware components shown in the Device Manager screen. Click on the 'Modems' section to expand the available modems. If for some reason your modem is not recognized it may still be mapped to a COM port within the 'Ports (COM & LPT)' section so try expanding that option and see if a COM port is available. Please note that if the GSM modem is a serial modem then it is most likely in COM1 or whichever port the serial port you connected the modem to is on. Once you find the option you believe to be the modem, right-click on it and select 'properties'. Within the properties screen select the 'Modem' tab and there you should see what port the modem is mapped to as well as the 'Maximum Port Speed' (baud rate). Generally the baud rate is 115200.




Now that you have confirmed the COM port the modem is mapped to you can attempt to manually send a SMS message using Putty or another serial connection tool. For the example we are using Putty as it is a free and very easy tool to use for this purpose.

Once you have downloaded Putty you can just run the EXE file to start the application. We will first want to change the 'Connection type' selection to be 'serial' as the modem is connected to a COM port.



After selecting the 'Serial' option you will see fields for 'Serial line' and 'Speed'. You will need to change the 'Serial line' field to be the COM port that you found the modem mapped to and the 'Speed' field to be the 'Maximum Port Speed' (baud rate) of the modem.



After changing the settings select the 'Open' button at the bottom-right of the screen to open the connection to the modem. If the connection is successful you should see a window similar to the one below.



This is a direct connection to the modem and you can now type in commands to the modem. The Device ManageR software uses standard commands to set the modem into SMS Text Mode and to send a SMS message. Please try using the below commands in order, one line at a time to see if you are able to send a test message to a target phone.

Please note that in the below commands '~C' should be replaced with pressing the 'Enter' key, '^Z' replaced with pressing 'CTRL+Z', replace the keyword [SERVICE] with the GSM service center number, [PHONE] with the phone you want to send a SMS text to and [ALARM_TEXT] with the text you want to send.

AT+CMGF=1~C
AT+CSCA="+[SERVICE]"~C
AT+CMGS="[PHONE]"~C
[ALARM_TEXT]^Z~C

NOTE: If you are outside the U.S. you may have need to place a '+' sign before the target phone number you are attempting to send a message to.

Below is a screen shot of a successful attempt to send a message.


 

Further Troubleshooting With A GSM Modem

First verify that the modem you are using supports SMS Text mode. Currently this is the only mode supported by Device ManageR. To verify that your modem supports this mode you can use the commands noted below and it should return a 1 if it is available. (ex. Good response: +CMGF: (0,1) )

AT+CMGF=?




Next check to ensure that you have inserted a SIM card into the modem that has been unlocked and is tied to an activated data plan with a phone service provider. You should also try using the below command to verify that the SIM card is unlocked as it should respond with '+CPIN: READY' to the below command.

AT+CPIN?



Once the SIM card is verified, we will want to ensure the proper band setting is being used to connect to the SMS Service Center. The command noted below can be used to verify what the modem is currently set to.

AT+WMBS=?

+WMBS: 4,0

The below commands will cause the modem to respond with the available band settings for this modem.

AT+WMBS?




Below are the available band settings for a Sierra Wireless GL6110 modem.

+WMBS: 0,x Mono band mode 850MHz is selected

+WMBS: 1,x Mono band mode extended 900MHz is selected

+WMBS: 2,x Mono band mode 1800MHz is selected

+WMBS: 3,x Mono band mode 1900MHz is selected

+WMBS: 4,x Dual band mode 850/1900MHz are selected

+WMBS: 5,x Dual band mode extended 900MHz/1800MHz are selected

+WMBS: 6,x Dual band mode extended 900MHz/1900MHz are selected

If you do not have a Sierra Wireless GL6110 modem, you will need to review the documentation provided with the modem to verify which setting indicates which band setting for your modem as they may be different.

To change the current band setting used by the modem you can use the below commands through putty.

Below are the commands for setting the modem to the dual band 850/1900MHz. (North America & U.S.)

AT+WMBS=4
AT+CFUN=1

Below are the commands for setting the modem to the dual band 900/1800MHz (UK and most countries outside of North America).

AT+WMBS=5
AT+CFUN=1

Configuring Device ManageR To Send Email Notifications (VIDEO)


Click Here To View A Larger Video.

Device ManageR can send alert notifications to unlimited contacts via SMTP Email when Alerts occur. In order to send SMTP Email, the 'SMTP Email' section of the settings must be configured with valid mail server information that Device ManageR can use to send email notifications. Email notifications will be enabled and available to use as an Alert Action as long as valid settings are configured.

Click the 'Settings' button in the left navigation menu and select the 'SMTP Email' option to display the configuration options for SMTP Email.
 
Device ManageR allows both a primary mail server and a secondary mail server to be configured. The primary mail server is always used first, however if an email attempt fails then the email notification is attempted again using the settings for the secondary mail server. This is a highly valuable feature as it allows email notifications to still be sent using a backup mail server in the event that the primary mail server is temporarily unavailable or experiencing unexpected downtime.



Enter the mail server IP address or DNS name in the 'Mail Server IP or DNS Name' field. If you do not know the IP address of your mail server or have multiple mail servers, you can simply enter the domain name for your mail server.

The 'Port' number field must be the SMTP port used by the mail server noted in the 'Mail Server IP or DNS Name' field. Port 25 is a commonly used SMTP port, although you should confirm with your mail server administrator to ensure the proper SMTP port is used.

The 'From (Return) Email Address' field defines the email address Device ManageR will send the emails from and is seen by the recipients as the 'sender' of the email.

If your mail server requires authentication, enter the username and password credentials required for the email account specified in the 'From (Return) Email Address' field.

If authentication is not required, the username and password fields can be left blank, however you should confirm with your mail server administrator that the mail server is configured to allow SMTP relaying to internal and external accounts from the IP address of the host system where Device ManageR is running. If the mail server is not configured to allow SMTP relaying to external accounts, then Device ManageR will only be able to send SMTP email to accounts that are local to the mail server.



Once the desired email settings are configured, click the 'Save Settings' button, then click the 'Send Test Email' button to attempt to send a test email using the configured mail servers. The results of the test will be displayed in a dialog that is opened automatically. If the test email was successful, the email address defined in the 'Test Email Recipient' field should receive one test email from each configured mail server. If there are any errors in the test, a message will be displayed.




The 'View Email Log'  link can be clicked to view the contents of the 'Email.log' file, which can be useful in determining proper configuration or for troubleshooting errors with the email process.





Once SMTP Email is configured properly, Device ManageR can be configured to send email notifications to an unlimited number of contacts in response to alert conditions. Simply create a new 'Send Email Notification' Action for each contact you wish to notify. Once these Actions are defined, they can be added as desired to 'Action / Notification Lists' so email notifications will be sent in response to Alert conditions. For details regarding configuring Actions or Action / Notification Lists, please see the additional resources available at AVTECH.com/Support, or feel free to contact us at Support@AVTECH.com

Trouble/Issues Accessing the 'Downloads' Section of AVTECH.com

The 'Downloads' section on AVTECH.com is AVTECH's only source of Device ManageR, Room Alert/TemPageR firmware updates, Software updates, MIB files, Device ManageR plugins, and the Device Discovery utility. To gain access to this section, AVTECH will issue a username and password to all contacts that are employed by organizations that have purchased a Room Alert or TemPageR environmental monitor.

If you have been previously issued a username and password from AVTECH: When attempting to log on to the AVTECH Downloads section, make sure that the password being used is entered correctly as the password is case sensitive. Please note the email address that was initially given to AVTECH at the time of registration is the only email that can be used to log on to this section.

If the initial password for the 'Downloads' section of AVTECH.com has been lost or forgotten, go to AVTECH.com/Downloads/ and select the 'Forgot/Reset Password' link below the login section. Enter the registered email address in the new screen and select 'Submit'. If the email address matches a record that was previously created in AVTECH's registry, an email will be sent with the required password.

If you are able to access AVTECH's downloads, but your downloads are expired: The specific downloads provided to your organization are regulated by AVTECH's Maintenance, Support, and Update Service (MSUS). MSUS is an annually renewed service for each of the Room Alert and TemPageR units owned by the organization. If MSUS needs to be renewed, please send an email to RenewMSUS@AVTECH.com including the organization's name and your personal contact information. For more information on MSUS, please refer to this page link:  http://www.AVTECH.com/PDFs/AVTECH_MSUS_Explained.pdf 

If you are a new contractor or temporary hire and require access to AVTECH Downloads: Please provide the following information in an email to 'Support@AVTECH.com' along with a short message explaining the need for access. Once approved, you will be registered as a contractor or temporary hire directly under the organization that owns the Room Alert or TempageR product. Please include the following information in this email:

Organization Name
Organization Address
Organization Phone Number
Your Full Name
Direct Phone Number
Email Address
Job Title
Summary Of Work To Be Completed

For all other issues accessing the 'Downloads' section of AVTECH.com, send an email to 'Support@AVTECH.com' and we will be able to provide further assistance.

Configuring External Modems in Device ManageR

To Send 'GSM Modem' and 'Dial Out Modem' notifications,  AVTECH Device ManageR requires that an external modem be connected to the same PC or Server that is running Device ManageR.

For 'Dial-Out Modem' notifications, a "Hayes-compatible" analog modem should be connected and installed on an available COM Port on the Device ManageR host system.

For 'GSM Modem' notifications, a "GSM/GPRS Modem" compatible with industry standard GSM AT commands should be connected and installed on an available COM Port on the Device ManageR host system.



This FAQ article will outline configuration options for both the 'Dial Out' and the 'GSM' modem configurations.


For more information regarding sending alerts via 'Dial Out' and 'GSM' see these FAQ's:

How Do I Configure a "Dial Out Via GSM Modem" Action?   http://avtech.com/Support/index.php?action=kb&article=109

How Do I Configure A "Dial Out Modem" Action?   http://avtech.com/Support/index.php?action=kb&article=110





Configuring 'Dial Out Modem' Settings

Fields that start with 'Test' are used only for testing and 'Alerts' will not be sent to these numbers. Once the modem is tested and working , 'Contacts' should be configured that will be notified when 'Alerts' occur.


The 'Phone System Prefix' is the number to dial that is required to access an outside line. For example, if your phone system requires you to dial a ' 9 ' to make an outside call, enter a ' 9 ' in this field.
 



In order to at least send a test message through a TAP service, you will need to configure the 'Test Service# ' and 'Test Phone/ID#' fields.   
If the TAP service requires a password you will also need to enter it in the 'Test Password' field.

Note** If you want to call a phone directly and play dial tones, or to simply dial a phone directly, only the 'Test Phone/ID #' is required.




The 'Test Initialization String' is used to configure the modem so that it can be used by the Device ManageR software. The default initialization string provided should work for most modems.



'Com Port', 'Baud Rate', 'Data Stop Bits' and 'Parity' will need to be configured as well.  The 'COM Port' entered should match the 'COM Port' that the modem is connected to. The remaining modem settings that are entered should be compatible with the settings required by the TAP service provider.





The 'Test Dial Out Modem' feature is available to test your configuration to ensure that a test message is sent. This is an important step and should be completed to ensure proper notification occurs in the event of an actual alert. If you need to trace or further troubleshoot the sending of the test you can click 'View Modem Log'. 





Configuring GSM Modem Settings

In order to receive 'Alerts via GSM Modem', you must first confirm the 'SMS Center' or 'Service Number' that you want to send messages through. The 'SMS Service Center Number' can be obtained from your mobile service provider and can sometimes be found in the settings of a phone that uses the same network.   





'Com Port', 'Baud Rate', 'Data Stop Bits' and 'Parity' will need to be configured as well. The 'COM Port' entered should match the 'COM Port' that the modem is connected to. The remaining modem settings that are entered should be compatible with the settings required by the TAP service provider.



The 'GSM Advanced Settings' can be clicked on to expand the 'GSM Modem Script' used by Device ManageR to send GSM Notification Actions.

This script can be modified so that it will work with the particular GSM Modem connected to the system. The default 'GSM Modem Script' should work with most GSM Modems without any modifications required.




The 'Test GSM Modem' feature is available to test your configuration to ensure that a test message is sent. This is an important step and should be completed to ensure proper notification occurs in the event of an actual alert. If you need to trace or further troubleshoot the sending of the test you can click 'View Modem Log'
 












How do I set a Static IP address on my Room Alert or TemPageR?

A Static IP address can be set for your Room Alert or TemPageR unit by using the AVTECH Device Discovery Utility, AVTECH Device ManageR, or via the 'Network' section in the 'Settings' tab of the Room Alert or TemPageR web browser interface.

To set a Static IP address using the AVTECH Device Discovery Utility, open the AVTECH Device Discovery Utility and click the 'Search' button. Select the monitor you wish to assign a static IP address to and click the 'Set IP' button. Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit being updated.

To set a Static IP address using the AVTECH Device ManageR Software, open the Device ManageR software and click the monitor in the left hand 'Device Status' list. You will notice a small drop down below the currently selected monitor. Click the '-Set IP Address' button.
Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit you are updating.

To set a Static IP address using the monitor's web browser interface, enter the current IP address of your Room Alert or TemPageR monitor into the location bar of a web browser. The 'Status' page will load by default and display the current sensor values. Click the 'Settings' tab at the top of the page and the 'Network' section will load. Uncheck the 'Use DHCP' checkbox and enter the desired static IP information in the available fields. Be sure that all static IP address information is correct for the location of the monitor you are updating. To complete the changes, please click the 'Accept Changes' button at the bottom of your page and then the 'Save Settings' button on the left hand side. The monitor will now reboot and apply the new changes.

If the Room Alert or TemPageR monitor cannot be discovered or you do not know the existing IP address, a Static IP address can be set using the MAC address of the unit, which can be found on a label on the bottom of the monitors. Please open Device Discovery and click the 'Set IP' button without selecting a device from the list and follow the prompts from the AVTECH Device Discovery Utility. Alternatively, you can set a Static IP address via the MAC address of your monitor in Device ManageR.
Open Device ManageR and click the 'Advanced Discovery' button in the top left hand corner on the 'Device Status' list. This button will display a pop up that will have a 'Set IP Via MAC Address' button. From here, enter the MAC address of the monitor and the desired Static IP address.When finished, press the 'Update IP Settings' button to make the changes.

Access Errors Occur When Shutting Down Windows Systems

If you are experiencing Access Denied or other access exceptions when attempting to shutdown a Windows target system using the Windows Shutdown Plugin, please verify the settings below to be sure the system is configured properly to accept remote shutdown requests. Also with v1.1.0 and later of the Windows Shutdown Plugin, an alternative method of shutdown will be performed if the standard procedure fails. It will attempt the alternative shutdown script which will attempt to shutdown the remote system using the credentials that Device ManageR has been set to use within the 'Log On' tab of the AVTECH Device ManageR service. So if you have issues with the initial process working you will want to make sure that the Device ManageR service is configured to use an administrative account that has administrative privileges with remote shutdown privileges for the target system you want to shut down.


Shutdown Of A Windows Vista Or Later Windows System


If the target system is a Windows Vista, Windows 7, Windows Server 2008 or later Windows system the most likely cause for issues with remote shutdown requests is the new User Access Control (UAC) feature.

If the target system is part of a domain, it is recommended to connect to the target system using a domain account that is in the local Administrators group of the target system. This will prevent UAC access token filtering from blocking the WMI connection attempts. Do not use a local, non-domain account on the target system. Even if the account is in the Administrators group, it will experience issues with the WMI connections since Windows will not allow the necessary privileges.

When a user account that is part of a workgroup connects remotely to a system, it connects as a local user on the system. This is done even if the account is in the Administrators group as UAC filtering means that a script runs as a standard user. It would be recommended to create a dedicated local user group or user account on the target system specifically for remote connections.

If you connect to a remote system using a non-domain user account included in the local Administrators group of the remote computer, then you must explicitly grant remote DCOM access, activation, and launch rights to the account. You should be able to use the below steps to explicitly grant those privileges for remote WMI access using the following steps. Please note that depending on the operating system the location may be different or there may be other setting changes required.


For more details please review the 'Handling Remote Connections Under UAC' section of the 'User Account Control and WMI (Windows)' MSDN article found at the link below.
http://msdn.microsoft.com/en-us/library/aa826699%28v=VS.85%29.aspx


Other related and useful MSDN articles can be found below.

Connecting to WMI Remotely Starting with Windows Vista
http://msdn.microsoft.com/en-us/library/aa822854%28VS.85%29.aspx

Connecting to WMI on a Remote Computer
http://msdn.microsoft.com/en-us/library/aa389290%28v=VS.85%29.aspx

Thank you and please feel free to contact our Support Team at Support@AVTECH.com with any further questions.

How To Configure A Windows Shutdown Action (VIDEO)

The Windows Shutdown Plugin Action is used to force a power down of a target Windows system. This Action is extremely beneficial for powering down a system or group of systems when environment conditions exist that could potentially lead to catastrophic system damage, such as high temperatures, power loss, flooding, etc.


Click To View A Larger Video

To create a Windows Shutdown action, first download and install the Windows Shutdown Plugin from AVTECH.com. Click here for additional information about the Windows Shutdown Plugin, including purchasing options. After installing the Windows Shutdown Plugin, open Device ManageR and navigate to the 'Alerting' screen by clicking on the 'Alerting' button in the left navigation bar. Note that if the Device ManageR interface was open while installing the Windows Shutdown Plugin, the browser will have to be refreshed before the new plugin can be used.


Next expand the 'Actions' option in the right main frame and click the 'Add' button.


In the 'Add New Action' window, enter the desired 'Name' and 'Description' fields to give details regarding the Action being created. Next, select the 'Shutdown A Windows System' option from the 'Action Type' drop down as shown in the screenshot below.


Once the 'Shutdown A Windows System' option is selected for the 'Action Type' three new configuration fields will be displayed that are unique to this action.


The 'IP or System Name' field is the IP address or computer name of the system that the Action will send the force power down command to when this Action is performed. The 'Username' and 'Password' fields are the account information that should be used when the Action attempts to access the target system. An administrator level account is recommended so that remote shutdown privileges are allowed.


Once the Action is created, it can then be selected from the 'Alert Action' or 'Clear Action' drop down box from within the 'Add Action / Notification List Item' or 'Edit Action / Notification List Item' screen when configuring an Action / Notification List as shown below.

The Windows Shutdown Plugin allows an unlimited number of Windows Shutdown Actions to be created. These Windows Shutdown Actions can then be added to an 'Action / Notifications List' which will allow these systems to be shutdown simultaneously, sequentially, or according to a defined schedule. For additional information about the Windows Shutdown Plugin, or for assistance configuring it, please feel free to contact us at Support@AVTECH.com.

How To Configure Action / Notification Lists In Device ManageR (VIDEO)


Click Here To View A Larger Video.

This is a step-by-step guide that explains the simple process of creating an 'Action / Notification List' in Device ManageR. Action / Notification Lists define what sequence of events occur is response to Alert conditions. The most common Action is to send an email notification to a defined contact. Other available Actions include Windows Shutdown, Linux Shutdown, Email An Axis Camera Snapshot, Toggle Signal Tower or Relay, and many more. Each Action can be defined to start after a certain period of time and can optionally repeat at regular intervals.

Select the 'Alerts/Tasks' tab.  Click on 'Action / Notification List', then 'Add'.



Enter a name for the Action / Notification List in the 'Name' field.



Click the 'Add' button to add an Action / Notification List Item to your Action / Notification List.



Note that most configuration screens in Device ManageR have associated 'Help' files that you can access for additional useful reference information. Access the Help file by clicking on the green '?' .



Click the 'Alert Action:' drop-down menu to select an Action to take when an Alert is triggered (If you do not have any Actions configured, click the 'Add' button to the right of the drop-down menu to create one).



Enter a value, in seconds, for the 'Start the Action after' field to delay the start of the selected Action.  The default is 0.



Enter a value, in seconds, for the 'Repeat the Action every' field to configure the Action to repeat at the defined interval.  Once selected, the number of times the Action is repeated can be modified.  Choose the 'Continuously' radio button to perform the Action until the Alert is cleared, or the 'A maximum of' radio button to limit how many times the Action will be repeated.  A number of repetitions is required, in the field to the right of the radio button.  The default is 1.



Click the 'Clear Action:' drop-down menu to select an Action to take when the Alert clears or returns to normal (If you do not have any Actions configured, click the 'Add' button to the right of the combo box to create one).



Click the 'Save' button to save your 'Action / Notification List Item' to your 'Action / Notification List'.



Click the 'Save' button again to save the 'Action / Notification List'.



For more details on creating Alerts, please refer to Creating An Alert In AVTECH Device ManageR

If further assistance is required with this procedure, please initiate a support case by sending an email to our Technical Support staff at Support@AVTECH.com.

How Do I Configure A "Dial Out Via GSM Modem" Action?

In order to 'Send an Alert Via GSM'. It is recommended that you first configure and successfully test your Modem in the 'External Modem' section located in the main 'Settings' screen.

For more details see the FAQ article  "How To Configure External Modem Settingshttp://Avtech.com/Support/index.php?action=kb&article=111

Once the test has completed successfully, you can then create the 'Action' that will send the 'Alert via GSM' and will be triggered after a previously configured alert threshold is exceeded. 


Listed below are the steps required to configure Device ManageR to 'Send an Alert via GSM'.


1.Click on the 'Alerting' tab on the left navigation menu of Device ManageR to expand the available options. 


2.Select 'Actions' to expand the list of currently configured 'Actions'.


3.Click the 'Add' button to create a new 'Action', and select the 'Send Alert Via GSM' for the 'Action Type'.

 


 


4. Enter text in the 'Name' field that will make it easy to identify this Action. This is what will be shown in the lists where the Actions are displayed.

In the 'Description' field it can be helpful to provide a more detailed description of this Action. Since the option allows for specific contacts to send the Alert to, you may wish to describe the action with some further explanation as to who will be receiving the message.

In the example below we have described the alert   'GSM Alert to Administrator'.


 

5. The next step is to configure a 'Contact', or to select a previously configured 'Contact' from the drop down. Click the 'Add' button to configure a new 'Contact' or click the 'Edit' button to edit an existing 'Contact'




Depending on the plug-in installed different Contact configuration options might be available. These could include 'Email', 'Modem', and 'GSM' contact notification methods.







6. -The 'Message field is the actual text message that will be sent to the selected 'Contact'. This message can be customized with desired text or can also be configured to accept additional keywords. To modify the message by inserting text, or to insert a special keyword, simply click within the 'Message' field.

Note that the 'Insert An Alert Keyword' button will become available when the cursor is in the 'Message' field. 










7.Click 'Save' to save the new Action.


Now that the 'Send Alert Via GSM' Action has been created, it can be used in an 'Action/Notification List' .


For additional information regarding configuring an 'Action/Notification List', please see the following FAQ Article....   

"How To Configure Action / Notification Lists In Device ManageR"

http://avtech.com/Support/index.php?action=kb&article=91


How To View A Real-time Graph Of Sensor Values

Device ManageR will automatically discover any Room Alert or TemPageR devices on the network and regularly log the current sensor values to a database. Using the logged sensor values, Device ManageR allows users to view real-time graphs of sensor data over multiple date and time ranges. This is especially useful for identifying historical trends in power or cooling as well as for identifying potential trouble spots in the data center environment.

To view the real-time sensor data graph, open Device ManageR and select the device you wish to view either from the left menu, or the 'Discovered Devices Summary' section on the right hand side of the screen.




Near the top of the 'Sensor Display' view you will see four tabs for your device, select the 'Graph Display' tab. When you first open the 'Graph Display' tab, it will begin loading the default graph. The default graph will display all of the sensor data from the current day. On the y-axis of the graph (left vertical side) you will see the range of values that are being graphed. On the x-axis of the graph (bottom horizontal side) you will see the time range of the current graph.




Below the graphed data, a date and time range can optionally be selected to determine the period of time that should be displayed in the graph. To change the start date and time for the graphed data, click on the calendar icon next to the 'Start' label. To change the end date and time for the graphed data, click on the calendar icon next to the 'End' label. After selecting the date and time range to display, click on the 'Reload Graph Data' button and Device ManageR will update the graph display to show the sensor data over the new date and time range.




At the bottom of the Graph Display is a 'Graphed Sensors' section that functions as the legend for the graphed data. By default, the temperature values will be selected and displayed on all Digital Temperature and Digital Temp/Humidity Sensors connected to the selected device. The currently displayed sensors are highlighted in blue. To add or remove a value from the graph display, simply click the desired sensor type below the sensor label. The new sensors will automatically be displayed on the graph and the range of values on the y-axis will automatically be updated if necessary to display the new values..



How To Configure A 'Dial-Out Modem Action'

In order to 'Send an Alert via Dial Out Modem' it is recommended that you first configure and successfully test your Modem in the 'External Modem' section that is located in the main 'Settings' screen of  Device ManageR.

For more details see the FAQ Article  "How To Configure External Modem Settingshttp://AVTECH.com/Support/index.php?action=kb&article=111

Once the test has completed successfully, you can then create the 'Action' that will send the 'Alert Via Modem' and will be triggered after a previously configured alert threshold is exceeded.


Listed below  are the steps required to Configure Device ManageR to 'Send an Alert via Dial Out Modem'.


1.Click the 'Alerting' tab on the left navigation menu of Device ManageR to expand the available options.


2.Select 'Actions'  to expand the list of currently configured 'Actions'.



3.Click the 'Add' button to create a new Action, and select the 'Send Alert via Modem' for the 'Action Type'.


 


4.Enter text in the 'Name' field that will make it easy to identify this Action. This is what will be shown in the lists where the Actions are displayed.

In the 'Description' field it can be helpful to provide a more detailed description of this Action. Since the option allows for specific contacts to send the Alert to, you may wish to describe the action with some further explanation as to who will be receiving the message.


In the example below we have described the alert as 'Dial AVTECH's IT Administrator's Phone Number'.




5.The next step is to configure a 'Contact', or a previously configured 'Contact' can be selected from the drop down. Click the 'Add' button to configure a new 'Contact' or click the 'Edit' Button to edit an existing 'Contact'.





Depending on the plug-ins that are installed in Device ManageR, different Contact configuration options might be available. These could include 'Email', 'Modem' and 'GSM' Contact notification methods.

 

6.After choosing a 'Contact' , select the appropriate 'Dial Out Option'. This will depend on whether you want to directly dial a number and play dial tones or send an actual text message.



Direct Dial Out
 
-Use the 'Direct Dial Out'  option to call a contact's phone directly and play dial tones.

-Select a previously configured 'Contact' that has 'Dial Out Settings' configured from the drop down list.


-The 'Initialization String' is used to prepare the modem being used with Device ManageR. The default 'Intialization String' provided should work for most modems.

-The 'Message Pause' is the time in seconds that the modem will pause between each character.

-The 'Message'  Field (when used in conjunction with the 'Direct Dial Out' option) will be a string of numbers. The comma can be used between characters for pausing between tones.
The example above would be similar to a 'SOS' message played over dial tones. 



TAP Dial Out

Use the 'Tap Dial Out' option to use the TAP protocol to send a text message to a mobile device.


Select a previously configured 'Contact' that has 'Dial Out Settings' configured from the drop down list.


-The 'Initialization String' is used to prepare the modem being used with Device ManageR. The default 'Intialization String' provided should work for most modems. 

-The 'Message' field is the actual text message that will be sent to the selected Contact.  This message can be customized with desired text or can also be configured to accept additional keywords. To modify the message by inserting text, or to insert a special keyword, simply click within the 'Message' field. Note that the 'Insert An Alert Keyword' button will become available when the cursor is in the 'Message' field.

 



 




8.Click 'Save' to save the new Action.


Now that the 'Dial-Out Modem Action' has been created, it can be used in an 'Action/ Notification List'.


For additional information regarding an 'Action Notification List' please see the following FAQ article.....

"How To Configure Action / Notification Lists In Device ManageR"

http://AVTECH.com/Support/index.php?action=kb&article=91



Creating An Alert In AVTECH Device ManageR (VIDEO)

To create an Alert, click on the 'Device Status' button in the Navigation Panel on the left side of the Device ManageR interface. To display the list of available devices. Notice that a list populates on the left side within the Navigation Panel, and a sorted list of devices that includes device details appears in the Main Viewing Pane on the right. 



Click Here To View A Larger Video.

Selecting the desired device from either location will display the device's sensors and other details in the right main section. 



Click on the 'Configured Alerts' button to see the list of available Alerts for this device, and to add new Alerts.



Click 'Add' to create a new Alert.



The 'Add New 'Alert'' screen will appear. Enter the desired name for the Alert in the 'Name' field. Next, optionally enter a description of the purpose of this Alert in the 'Description' field. Lastly, ensure that the device that this Alert is being configured for is correctly selected in the 'Device' field.



Next the actual details of the Alert must be configured. When a device is selected, the available sensors to monitor will automatically load in the 'Choose An Item To Monitor' drop-down box. Ensure that the appropriate sensor is selected from the 'Choose An Item To Monitor' drop-down box.



In this example, we are creating an Alert that is triggered when the temperature on a specific sensor is too high. After selecting the desired temperature sensor, select 'greater than (>)' from the 'Choose Comparison Value' drop-down box


Next, enter the temperature value that will be used to trigger an Alert if the current temperature is greater than it. In this example, we want to trigger an Alert if the current temperature is greater than 80 degrees Fahrenheit. 



Finally, decide if this Alert will be triggered if its corresponding sensor or device becomes unavailable. If this option is selected, the desired number of scans (i.e. Alert Intervals which are every 15 seconds) must be provided, to determine how soon an Alert is triggered if the sensor or device becomes unavailable. 



After providing the necessary parameters for the Alert, and when it is triggered, a corresponding Action or set of Actions must be configured. The most common Action to take when an Alert is triggered is to send an email to one or more defined contacts. Choose a configured option from 'Action/Notification List' drop-down box, or click 'Add' to configure an Action/Notification List. More can be learned about configuring an Action/Notification List and its Actions is by browsing to: How To Configure Action / Notification Lists In Device ManageR

A schedule can be configured for the corresponding Alert. This will cause the Alert to be checked only on certain days or between certain times. To use an Optional Schedule, simply put a check in the 'Option Schedule' check box, and then select a configured Optional Schedule from the 'If desired, choose an 'Optional Schedule'' drop-down box. Or, if none is configured, click the 'Add' button. 



The actual Alert text that users receive when an Alert and its corresponding Action(s) are triggered is fully customizable and can also be configured with the use of keywords. The 'Alert Notification Text' options can be accessed by clicking on the 'Edit Alert Notification Text' button.



The 'Edit Alert Notification Text' button will open the 'Edit Email Alert Text' dialog which shows the 'Alert Subject', 'Alert Body', 'Clear Subject' and 'Clear Body' fields that are used when an alert occurs or clears. These fields can be modified completely and are also able to use keywords that are listed in the right side of the of the dialog. These keywords are replaced at the time the action is being processed and will update accordingly.



Once you have made the changes to the alert or clear text fields click the 'Save Alert Text' button to return you back to the 'Add New Alert' screen and click the 'Save' button to create your Alert object. It will take you back to the 'Configured Alerts' display for your device with the new Alert object now showing in the list as shown in the image below.
 

How To Create And Edit Contacts In Device ManageR

AVTECH Device ManageR has the capability to send alerts via email to an intended recipient's email address or via Email-to-SMS to a mobile phone or smart phone device. 

After entering and testing the SMTP Server information in the 'SMTP Email' option under the 'Settings' section, 'Contacts'  can be configured to send the alert notifications to.  

Adding Both Email and Email-to-SMS Recipients is quite easy and can be done in just a few steps.

'Adding Email Contacts'

1. In the AVTECH Device ManageR Console, click on the 'Alerting' menu option on the left column of the main console view.

2. Select 'Contacts' and click the 'Add' button.





3. Next, enter the details for the 'Contact' that the 'Alerts' will be sent to.



The 'Name' field is required and defines the name of the 'Contact'  being configured. In addition to the person's name, it is recommended to add something that describes the contact method, such as 'John Smith-Email'.

The 'Description' field is optional and can be used to provide a more detailed description for the intended use of the Contact.

The 'Email Address' field is required and defines the Email address that alert notifications will be sent to.





AVTECH Device ManageR also has the capability to send Email-to-SMS messages to a mobile phone or smart phone device. 


A list of known Email-to-SMS addresses for many mobile carriers is available on our website at  http://avtech.com/Support/Email/index.htm

Once the desired 'Contacts' have been configured, they can be added to an unlimited number of 'Send Email to Configured Contact' Actions. These Actions can be configured in the 'Actions'  Option under the 'Alerting' Section of AVTECH Device ManageR. 

Configuring Optional Schedules in Device ManageR

Optional Schedules allow for the specific scheduling of  'Alerts', 'Actions' or 'AXIS Camera Motion Capture Events'. This ensures that the criteria is only enabled or run at the specified days and  times. The 'Optional Schedules' can also be enabled/disabled.

The 'Optional Schedule'  box will first appear as a greyed out option near the bottom of any 'Alert' or 'Action' configuration screen. 



  


To configure click on the configuration box next to the 'Optional Schedule' box, the greyed out line will now appear as regular text. 


 



Next, click on the 'Add' button to configure an 'Optional Schedule'.


Enter a 'Name' and 'Description' (if desired) for this 'Optional Schedule'.





 



To Modify, Delete or Add to this 'Optional Schedule'  move the pointer over a time range to edit it. Click the 'Save' button to store this 'Action'.

**Note**  A 'Copy To' feature drop down is available added for ease of configuration. This allows for the applying of the same settings to single/multiple days.
Next click on the plus and minus signs to create an entry for the specific day.



Configuring User Accounts In Device ManageR: 'Viewer' Accounts (VIDEO)

By default, Device ManageR does not require user accounts with user names and passwords. However, they are an option if you would like to add security in terms of who can reconfigure the program and who can see what data.

There are three types of user accounts available in Device ManageR:  ‘Administrator’, ‘Viewer’ and ‘Guest’. Each has its own level of access to the application.

A Viewer account has read-only access to Device ManageR:

- A Viewer can see and get reports on all discovered devices.

- However, it cannot reconfigure ‘Alerts / Tasks’ or ‘Settings’ in the program.

This FAQ will show you how to set up a Viewer account and what a Viewer can see and do in Device ManageR.

Note that you must be logged in as an Administrator in order to create a Viewer account. For more information about ‘Administrator’ accounts, please refer to the Configuring User Accounts In Device ManageR: 'Administrator' Accounts FAQ, or watch the 'Device ManageR Configuring User Accounts' video below.

Click Here To View A Larger Video.


How To Configure A 'Viewer' Account

1. Log in to Device ManageR as an Administrator.

- A Viewer account can only be created after the first Administrator account is created.

- A Viewer account cannot  be created by another Viewer or a Guest.

2. Click on ‘Settings’ --> ‘Security’ in the navigation bar to the left of your screen to bring up the ‘Configure User Account’ box. Notice that the Administrator account appears here.


3. In ‘Configure User Accounts,’ click ‘Add’.

Configure User Accounts - Add (Viewer)

4. When the 'Add New User Account' dialog box appears, click 'Viewer' under ‘Account Privilege Settings’.

Account Privilege Settings - Viewer

5. Then enter a username and password for the Viewer.

Username & Password - Viewer

6. Finally, click ‘Add User’.

Add New User Account - Viewer - Add User Button

7. This will bring you back to the security screen with the Viewer account added.

- Viewer accounts are marked ‘(Viewer)’.

Security Screen - Viewer Account Added

- An Administrator can create an unlimited number of Viewer accounts.

ViewerUser, ViewerUser2, ViewerUser 3

8. At this point, you are still logged in as an Administrator. To log in as a Viewer, restart Device ManageR and enter the Viewer’s username and password when prompted for your credentials. (If you are not prompted for credentials, clear your browser's cache and start Device ManageR again.)

What A Viewer Can See And Do

1. Like an Administrator, a Viewer can see all of the discovered devices on the network. In the example below, there are 14 devices connected to the network; all of them are discovered and appear under ‘Device Status’.


2. Like an Administrator, a Viewer can add (or reconfigure) widgets in its personalized ‘Dashboard View’ for all discovered devices.


3. However, since a Viewer has read-only access, it cannot reconfigure the items in ‘Alerts / Tasks’. Notice that the ‘Add’, ‘Edit’, ‘Copy’ and ‘Delete’ buttons do not appear under the items in the Viewer’s ‘Alerts / Tasks’ screen, preventing a Viewer from changing any settings.

4. A Viewer also cannot reconfigure ‘Settings,’ which is completely inaccessible to this type of account. Notice that the ‘Settings’ button is absent from the Viewer’s navigation bar, as shown below.



For More Information

For more information about the other two types of user accounts, ‘Administrator’ and ‘Guest’, please refer to the Configuring User Accounts In Device ManageR: 'Administrator' Accounts and Configuring User Accounts In Device ManageR: 'Guest' Accounts FAQs, or watch the Device ManageR Configuring User Accounts video.

How To Configure A Linux Shutdown Action

The Linux Shutdown action is used to shut down a target Linux system. To date, the plugin has been tested extensively with Ubuntu, Fedora and OpenSuse, although it uses the standard 'shutdown' command, so all Linux distributions should be supported. This plugin uses telnet to connect to the target Linux system, so the target Linux systems that you want to shut down will need to have the telnet daemon installed and running. This Action is extremely beneficial for powering down a system or group of systems when environment conditions exist that could potentially lead to catastrophic system damage, such as high temperatures, power loss, flooding, etc.

To create a Linux Shutdown action, first download and install the Linux Shutdown Plugin from AVTECH.com. Click here for additional information about the Linux Shutdown Plugin, including purchasing options. After installing the Linux Shutdown Plugin, open Device ManageR and navigate to the 'Alerting' screen by clicking on the 'Alerting' button in the left navigation bar. Note that if the Device ManageR interface was open while installing the Linux Shutdown Plugin, the browser will have to be refreshed before the new plugin can be used.


Next expand the 'Actions' option in the right main frame and click the 'Add' button.

In the 'Add New Action window, enter the desired 'Name' and 'Description' fields to give details regarding the Action being created. Next, select the 'Shutdown A Linux System' option from the 'Action Type' drop down as shown in the screenshot below.


Once the 'Shutdown A Linux System' option is selected for the 'Action Type' several new fields will be displayed that are unique to this action.

A description of all of the fields for the Linux Shutdown Plugin can be found below.



Once the action is created you can then select the action from the 'Alert Action' or 'Clear Action' drop down box from within the 'Add Action / Notification List Item' or 'Edit Action / Notification List Item' screen when configuring an Action / Notification List as shown below.

The Linux Shutdown Plugin allows an unlimited number of Linux Shutdown Actions to be created. These Linux Shutdown Actions can then be added to an 'Action / Notifications List' which will allow these systems to be shutdown simultaneously, sequentially, or according to a defined schedule. For additional information about the Linux Shutdown Plugin, or for assistance configuring it, please feel free to contact us at Support@AVTECH.com.

How To Configure Ping Devices In Device ManageR

This is a step-by-step guide of how to create a Ping Device in Device ManageR. Ping Devices can attempt to connect to a device on the network and check if a service is running on a specific port. If the service is running, the connection will be established and the Ping Device will return as successful and register in a normal state. If the service is not running or Device ManageR cannot reach the configured system or device, the connection will not be established and the Ping Device will return as failed and register an alarm state.

To configure a Ping Device, click on the 'Device Status' tab on the left hand menu of Device ManageR.
Click the 'Modify Ping Devices' button to bring up the 'Configure Ping Devices:' popup menu.



Click the 'Add' button to create a new Ping Device.



Select the type of Ping Device you wish to create by clicking in the 'Type' combo box. The options are TCP, UDP and HTTP.



Enter the desired name of the Ping Device in the 'Name' field.
Enter the IP Address or Domain Name in the 'IP / Domain Name:' field for the device or system you wish to test.
In the 'Port:' field, enter the TCP, UDP or HTTP port number (corresponding to the Ping Device 'Type') that you wish to test with your Ping Device.
In the 'Timeout' field enter a value (in seconds) for how long to wait for a reply to the connection attempt.
The 'Max Retries' field allows you to configure how many connection attempts will be made before an alarm condition is generated.
The 'Message' field (TCP/UDP only) allows you to configure any message (if required) that should be sent after the connection has been established.
The 'Response' field allows you to configure any response (if required) that should be expected after the connection has been established.



The 'Page' field (HTTP only) allows you to configure a specific web page that Device ManageR should attempt to load.
The 'Method' field (HTTP only) allows you to configure what method to use when accessing the specified page. HEAD requests only the HTTP headers be returned while GET will return the entire web page.



Once you have configured your Ping Device as desired, click the 'Save' button to save the Ping Device. It should now be displayed on the 'Device Status' tab.

How To Use The Database Delete Plugin

The Delete Database Plugin is useful to allow database operations within Device ManageR to continue running close to their optimal performance over time. As time goes on the database used by Device ManageR will grow in size due to continually logging sensor and alert data. If you only need to keep data from a certain period (the last month for example) you can use the Delete Database Plugin to automatically clear data that is older than you need. By clearing this unneeded data from the database, the queries that are used to generate graphs and export data to CSV files will be able to execute much more quickly.

The Delete Database Plugin can take a fair amount of time to execute, especially the first time it is executed on an installation. Due to this we recommend configuring an instance of the Delete Database Action to run on a weekly schedule that runs overnight during the weekend. If you're starting out with a large database it is a good idea to manually delete unnecessary data from your database using the 'Reset Logfile Data' button under the 'Sensor Logging' section of the 'Settings' tab.

To start configuring the Delete Database Plugin you will first want to browse to the 'Alerts / Tasks' tab in Device ManageR. From here, click on the 'Add' button under the 'Scheduled Tasks' section.



Give your Scheduled Task a name, for this example we'll use 'Clear Old Data Weekly'. You can also give the Scheduled Task an optional description if you'd like to leave an extended explanation of what this task does. You will need to create a Schedule for this task to run off of, to do so click the 'Add' button next the the 'Schedule' drop down.



You will need to give your Schedule a name, we'll use 'Deletion Schedule' for this example. To start a fresh Schedule click the '-' (minus) button next to the timeset on the 'Sun' row, then select 'All' from the 'Copy To' dropdown in the same row.



You can now add a time set where you want your Delete Database Action to run. I'm going to choose to have mine run at 12:00 AM Sunday morning as this should be a low use time for the application. Click on the '+' button in the 'Sun' row and enter '12:00 AM to 12:01 AM' as your timeset. This will cause the Scheduled Action to begin executing its items at 12:00 AM. Since we don't have any Actions that need to repeat we can simply tell the Schedule to end a minute later.



Once your Schedule is complete click the 'Save' button to get back to the Scheduled Task configuration window. You will now want to click on the 'Add' button in the middle of the window to add a new execution row to your Scheduled Task



This will bring you to the 'Add Scheduled Task Item' screen.



You will now be prompted to select the Action you want this execution row to run. Click on the 'Add' button next to the 'Task Action' drop down to configure a new Delete Database Action. Give your Action a name, we'll use 'Delete Data Older Than A Month' for this example, then select 'Delete Database Data' from the 'Action Type' drop down.



Enter the number of days of data you want to keep in the 'Number Of Days To Retain' field. We'll use '30' for this example to keep 30 days of data. Every time this Action is executed it will delete any data that is older than however many days you enter. By using 30 days we'll be keeping about a month's worth of data at all times.

There are two options for data that the plugin can delete. It can either delete logged sensor data, logged alert data, or both. Logged sensor data is almost always going to be a lot more than the logged alert data and will have a much bigger impact on your database performance. For this reason we always suggest resetting the logged sensor data if you're trying to keep your database performance high. The Alert data typically isn't too much data, so if you'd like to keep track of all instances of Alerts going into their alarm state you can keep this row unchecked. For our example we'll be selecting both options to wipe the most data possible from the database.



Once you have finished creating your Database Delete Action click the 'Save' button to get back to the previous screen. Next you'll want to set this Action to only execute once by selecting 'A maximum of 1 time'.



You can now click the 'Save' button to get back to your base Scheduled Task which should be fully completed.



Click the 'Save' button to save your complete Scheduled Task.

Your Device ManageR installation should now be configured to reset data from it's database on a weekly basis. This should keep your sensor graphs and dashboard data loading quickly, and improve overall performance with the application.

To download the Delete Database Plugin please visit the Downloads section on AVTECH.com at http://AVTECH.com/Downloads.

Configuring User Accounts In Device ManageR: 'Administrator' Accounts (VIDEO)

By default, Device ManageR does not require user accounts with user names and passwords. However, they are an option if you would like to add security in terms of who can reconfigure the program and who can see what data.

There are three types of user accounts available in Device ManageR:  ‘Administrator’, ‘Viewer’ and ‘Guest’. Each has its own level of access to the application.

An Administrator account has full access:

- An Administrator can see and get reports on all discovered devices.

- It can reconfigure all items in ‘Alerts / Tasks’ and ‘Settings.’

This FAQ will show you how to set up an Administrator account and what an Administrator can see and do in Device ManageR.

For more information about the other two types of user accounts, ‘Viewer’ and ‘Guest’, which have more restricted access, please refer to the Configuring User Accounts In Device ManageR: 'Viewer' Accounts and Configuring User Accounts In Device ManageR: 'Guest' Accounts FAQs, or watch the 'Device ManageR Configuring User Accounts' video below.

Click Here To View A Larger Video.


How To Configure An Administrator Account

1. Click ‘Settings’ --> ‘Security’ in the navigation bar to the left of your screen to bring up the ‘Configure User Accounts’ dialog box. Note that there are no users currently configured.


2. In ‘Configure User Accounts,’ click ‘Add’.

Configure User Accounts - Add Button

3. When the ‘Add New User’ dialog box appears, leave 'Administrator' clicked under 'Account Privilege Settings'.

- ‘Viewer’ and ‘Guest’ remain grayed out and unavailable until the first Administrator account is created.

- The Administrator account is always the first to be created and the last to be deleted.


4. Then enter a username and password for the Administrator.


5. Finally, click ‘Add User’.


6. This brings you back to the ‘Security’ screen, where a dialog box will pop up to prompt you for your user credentials:

- Enter the username & password you just created.

- Then click ‘OK’.


7. Now you are logged in as an Administrator.

- Administrator accounts are marked with '(Admin)', as shown below.


- An Administrator can create an unlimited number of Administrator accounts for other users.


What An Administrator Can See And Do

1. An Administrator can see all devices discovered on the network. In the example below, there are 14 devices connected to the network; all of them are discovered and appear under ‘Device Status’.


2. An Administrator can add (or reconfigure) widgets in the ‘Dashboard View’ for all discovered devices.


3. An Administrator can also reconfigure all items in the ‘Alerts / Tasks’ screen. Notice that the ‘Add’, ‘Edit’, ‘Copy’ and ‘Delete’ buttons are available for each item in 'Alerts / Tasks'.


4. An Administrator has full access to the ‘Settings’ screen and is able to reconfigure all items, including creating Viewer, Guest and other Administrator accounts for other users under ‘Security’.



For More Information

For more information about the other two types of user accounts, ‘Viewer’ and ‘Guest’, please refer to the Configuring User Accounts In Device ManageR: 'Viewer' Accounts and Configuring User Accounts In Device ManageR: 'Guest' Accounts FAQs, or watch the Device ManageR Configuring User Accounts video.

Access Errors Occur When Logging Users Off A Windows System

If you are experiencing Access Denied or other access exceptions when attempting to logoff users from a target system using the Windows Logoff Plugin, please verify the settings below to be sure the system is configured properly to accept remote logoff requests:


Logoff A Windows Vista Or Later Windows System


If the target system is a Windows Vista, Windows 7, Windows Server 2008 or later Windows system the most likely cause for the issues with remote logoff requests is the new User Access Control (UAC) feature.

If the target system is part of a domain, it is recommended to connect to the target system using a domain account that is in the local Administrators group of the target system. This will prevent UAC access token filtering from blocking the WMI connection attempts. Do not use a local, non-domain account on the target system. Even if the account is in the Administrators group, it will experience issues with the WMI connections since Windows will not allow the necessary privileges.

When a user account that is part of a workgroup connects remotely to a system, it connects as a local user on the system. This is done even if the account is in the Administrators group as UAC filtering means that a script runs as a standard user. It would be recommended to create a dedicated local user group or user account on the target system specifically for remote connections.

If you connect to a remote system using a non-domain user account included in the local Administrators group of the remote computer, then you must explicitly grant remote DCOM access, activation, and launch rights to the account. You should be able to use the below steps to explicitly grant those privileges for remote WMI access using the following steps. Please note that depending on the operating system the location may be different or there may be other setting changes required.


For more details please review the 'Handling Remote Connections Under UAC' section of the 'User Account Control and WMI (Windows)' MSDN article found at the below link.
http://msdn.microsoft.com/en-us/library/aa826699%28v=VS.85%29.aspx

Other related and useful MSDN articles can be found below.

Connecting to WMI Remotely Starting with Windows Vista
http://msdn.microsoft.com/en-us/library/aa822854%28VS.85%29.aspx

Connecting to WMI on a Remote Computer
http://msdn.microsoft.com/en-us/library/aa389290%28v=VS.85%29.aspx

If you have additional questions regarding the Windows Logoff Plugin for AVTECH Device ManageR, please feel free to contact us at Support@AVTECH.com.

Access Errors Occur When Attempting To Reboot A Windows System

If you are experiencing Access Denied or other access exceptions when attempting to reboot a Windows target system using the Windows Reboot Plugin, please verify the settings below to be sure the system is configured properly to accept remote reboot requests.


Reboot Of A Windows Vista Or Later Windows System


If the target system is a Windows Vista, Windows 7, Windows Server 2008 or later Windows system the cause for the issues with remote reboot requests is the new User Access Control (UAC) feature.

If the target system is part of a domain, it is recommended to connect to the target system using a domain account that is in the local Administrators group of the target system. This will prevent UAC access token filtering from blocking the WMI connection attempts. Do not use a local, non-domain account on the target system. Even if the account is in the Administrators group as it will experience issues with the WMI connections since Windows will not allow the necessary privileges.

When a user account that is part of a workgroup connects remotely to a system, it connects as a local user on the system. This is done even if the account is in the Administrators group as UAC filtering means that a script runs as a standard user. It would be recommended to create a dedicated local user group or user account on the target system specifically for remote connections.

If you connect to a remote system using a non-domain user account included in the local Administrators group of the remote computer, then you must explicitly grant remote DCOM access, activation, and launch rights to the account. You should be able to use the below steps to explicitly grant those privileges for remote WMI access  using the following steps. Please note that depending on the operating system the location may be different or there may be other setting changes required.


For more details please review the 'Handling Remote Connections Under UAC' section of the 'User Account Control and WMI (Windows)' MSDN article found at the below link.
http://msdn.microsoft.com/en-us/library/aa826699%28v=VS.85%29.aspx

Other related and useful MSDN articles can be found below.

Connecting to WMI Remotely Starting with Windows Vista
http://msdn.microsoft.com/en-us/library/aa822854%28VS.85%29.aspx

Connecting to WMI on a Remote Computer
http://msdn.microsoft.com/en-us/library/aa389290%28v=VS.85%29.aspx

If you have further questions regarding the use of the Windows Reboot Plugin for AVTECH Device ManageR, please feel free to contact us at Support@AVTECH.com.

Configuring User Accounts In Device ManageR: 'Guest' Accounts (VIDEO)

By default, Device ManageR does not require user accounts with user names and passwords. However, they are an option if you would like to add security in terms of who can reconfigure the program and who can see what data.

There are three types of user accounts available in Device ManageR: ‘Administrator’, ‘Viewer’ and ‘Guest'. Each account type has its own level of access to the application.

A Guest account has read-only access to certain assigned devices, which is the most restricted level of access to Device ManageR:

- A Guest can see and get reports on only those devices that the Administrator allows.

- It cannot reconfigure ‘Alerts / Tasks’ or ‘Settings’ in the program.

This FAQ will show you how to set up a Guest account and what a Guest can see and do in Device ManageR.

Note that you must be logged in as an Administrator in order to create a Guest account. For more information about ‘Administrator’ accounts, please refer to the Configuring User Accounts In Device ManageR: 'Administrator' Accounts FAQ or watch the 'Device ManageR Configuring User Accounts' video below.

Click Here To View A Larger Video.


How To Configure A Guest Account

1. Log in to Device ManageR as an Administrator.

- A Guest account can only be created after the first Administrator account is created.

- A Guest account cannot be created by a Viewer or another Guest.

2. Click on ‘Settings’ --> 'Security' in the navigation bar to the left of your screen to bring up the ‘Configure User Accounts’ box. Notice that the Administrator account appears here.


3. In ‘Configure User Accounts,’ click ‘Add’.


4. When the ‘Add New User’ dialog box appears, click 'Guest' under ‘Account Privilege Settings’.


5. Once you click ‘Guest,’ the ‘Add Allowed Devices For This Guest’ menu expands. Click on one or more of the devices to move them to the ‘Allowed Devices’ field.

Guest's Allowed Devices - R32-Data Center

6. Then enter a username and password for the Guest.


7. Finally, click ‘Add User’.


8. This will bring you back to the security screen with the Guest account added.

- Guest accounts are marked with ‘(Guest)’, as shown below.


 - An Administrator can create an unlimited number of Guest accounts.


9. At this point, you are still logged in as an Administrator. To log in as a Guest, restart Device ManageR and enter the Guest’s username and password when prompted for your credentials. (If you are not prompted for credentials, clear your browser's cache and start Device ManageR again.)

What A Guest Can See and Do

1. A Guest can only see those devices assigned to it. In the example below, although there are actually 14 devices on the network, this Guest account can discover and display only 1, the Room Alert 32E from its 'Allowed Devices' list.


2. While a Guest can add (or reconfigure) widgets in its own personalized ‘Dashboard View’, it has access only to the device(s) assigned to it. In this Guest's view, only the allowed Room Alert 32E appears in the widget’s dropdown list.

Guest's Dashboard Widget Dropdown List

 3. Under ‘Alerts / Tasks’, a Guest cannot reconfigure any items and can see only allowed devices.

- Notice that the ‘Add,’ ‘Edit’, ‘Copy’ and ‘Delete’ are absent from the Guest ‘Alerts / Tasks’ screen, preventing a Guest from changing any settings.

- Also, although there are actually 4 Alerts set up, this Guest can only see the Alert for the assigned Room Alert 32E, as shown below.


 4. A Guest cannot reconfigure ‘Settings,’ which is completely inaccessible to this type of account. Notice that the ‘Settings’ button is absent from the Guest’s navigation bar, as shown below.



For More Information

For more information about the other two types of user accounts, ‘Administrator’ and ‘Viewer’, please refer to the Configuring User Accounts In Device Manager: 'Administrator' Accounts, and Configuring User Accounts In Device ManageR: 'Viewer' Accounts FAQs, or watch the Device ManageR Configuring User Accounts video.

How Do I View The Alert History of a Discovered Device in Device ManageR?

The 'Alert History' Option allows you to view a quick snapshot of both the 'Current' and 'Historical' alerts of a discovered device. If desired, the history can also be exported to a CSV file.

The article below outlines the steps to view both the 'Current' and 'Historical' alert history, as well as how to export this data to a CSV file.

1. In the web interface of AVTECH Device ManageR click the 'Device Status' Tab in the left hand menu of the main interface.
2. Select the discovered device you wish to obtain the history data for.
3. Toward the center of the screen you will see four tabs for your device. Click on the 'Alert History' Tab to the far right. 


4. The window that displays will now show separate sections for any 'Current' and  'Historical' Alerts.


**Note** There is a drop down option for selecting the number of alerts that can be viewed.  (10,20,50,100)  This will depend on the amount of data that Device ManageR has polled/collected for the unit. If a device has recently been added it will take several polling cycles to collect any information.

-The information can be updated via the 'Refresh History' button.

-Toward the center of the screen the user is present with options to 'View' or 'Hide' the 'Current' or 'Historical' Alert information for the selected device. This can be done simply by clicking on the appropriate word  'View' or 'Hide' in the border area surrounding the displayed data.  By clicking on the word 'Drag' you can re-size/adjust the amount of screen real estate this window occupies.

 8.  The 'Alert History/Notification' Data can be also exported by clicking on the the 'Export To CSV' button function on this screen.



NOTE:  Clicking on this function is similar to performing the same operation under the 'Settings'>'Alert Logging'>'Export Alerts/Notifications' feature.  The only difference is that the screen will be automatically configured for the actual device currently being viewed.

 

 

 

 


For more details please see the article:   “How Do I Export the Alert History of a Discovered Device in AVTECH Device ManageR? ”
http://AVTECH.com/Support/index.php?action=kb&article=90

How To Configure A URL Web Request Action (VIDEO)

The URL Web Request action can be used to access a target URL when an Alert is triggered or clears. This is useful for sending commands to other devices on the network such as power distribution units (PDUs) when alerts occur. By sending a URL Web Request to a device such as a PDU, Device ManageR can automatically turn power outlets on or off when environment extremes occur, preventing costly damage to the systems or devices connected to the PDU.


Click To View A Larger Video

Open Device ManageR and click the 'Alerting' button in the left navigation bar to open the 'Alerting' options.



Next, click to expand the 'Actions' option and click the 'Add' button.



In the 'Add New Action' window, enter values in the 'Name' and 'Description' fields as desired to give details regarding the action being created. Next, select the 'Send URL Web Request' option from the 'Action Type' drop down as shown in the screenshot below.



Once the 'Send URL Web Request' option is selected for the 'Action Type', two new fields will be displayed that are unique to this action.



The 'Web Request URL' field is the fully qualified URL that will be accessed when this action is performed. The 'Response' field is optional and is the expected HTTP response when the URL specified is accessed. This is useful for verifying that the target URL was accessed properly and the remote device executed the desired command.


Once the new Action is created, it can be used by selecting the Action from the 'Alert Action' or 'Clear Action' drop down box from within the 'Add Action / Notification List Item' or 'Edit Action / Notification List Item' screen when configuring an Action / Notification List as shown below.

Configuring An AXIS Camera Motion Alert

Device ManageR can be configured to alert when motion is detected by an AXIS Camera on the network.  Before this can be done, the AXIS Camera must be discovered either automatically via Bonjour protocol, or by using the manual discovery feature accessible via the 'Advanced Discovery...' button under 'Device Status'. In addition to being discovered, valid authentication credentials must be supplied to the camera by selecting it in the 'Device Status' list and entering the credentials in the fields provided.

Once this has been completed, open the 'Alerting' tab and click the 'Add' button under the 'Alerts' section.



Enter a 'Name' for this 'Alert' and choose an authenticated AXIS Camera from the 'Device' drop-down. From the 'Choose An Item To Monitor' drop-down directly below it, select the item that ends with '-Motion'. Add and/or choose an 'Action/Notification List' for this 'Alert' and click the 'Save' button.



Alerting for motion events from an AXIS Camera requires that a Motion window, Motion event type and TCP Server pointing to the Device ManageR computer has been added to the selected AXIS Camera. When Device ManageR saves an alert for motion events from an AXIS Camera, the application will detect whether or not a Motion Event has been configured previously on the selected AXIS Camera via the automatic add feature. If a Motion Event has not been created for this AXIS Camera, a dialog will load asking if you would like to do so now. This is the recommended method for adding an AXIS Motion Event. Click the 'Add Motion Event' button to start the automatic Motion Event addition process.



The automatic Motion Event addition process will now try adding a Motion detection window, Motion event type and TCP Server to the AXIS Camera you selected.



If more than one Network Interface Card (NIC) exists on the computer that Device ManageR is installed on, the dialog will show the detected NICs and request a selection. In order for the Motion Event configuration on the AXIS Camera to have access to the Device ManageR installation, the NIC from which requests are sent to the AXIS Camera from Device ManageR must be selected.



The result of the Motion Event addition attempt will be displayed shortly. If the attempt was successful, the configuration can be tested and adjusted if necessary. Adjustments like sensitivity, motion threshold and object size can all be made by logging into the AXIS Camera web interface, navigating to 'Setup->Event Config->Motion Detection' and selecting the motion window for the current Device ManageR installation.



If the Motion Event addition attempt is not successful first make sure that the correct NIC was chosen. If you are still unable to configure a Motion Event, please submit a support ticket.

Configuring Device ManageR To Toggle Lights & Audio On A Room Alert Signal Tower Module

Before starting, please ensure that the correct Signal Tower module is selected on the Room Alert 4E's 'Alarm Options' page of the 'Settings' tab. It is recommend that an external digital sensor be connected to the unit if an alarm condition is to be simulated. This will allow configured Alerts to be tested to ensure that they are working as expected.

Click on the ' Alerts/Tasks ' tab in the Navigation Pane of the Device ManageR interface and expand 'Actions' from the displayed options.  Two Actions need to be created - one to turn the red light on, and one to turn the red light off.  Click the 'Add' button to create a new Action. 



On the 'Add New Action' window, give the Action an appropriate name.  The 'Description' field is optional.



Note that most configuration screens in Device ManageR have associated 'Help' files that you can access for additional useful reference information. Access the Help file by clicking on the green '?' .



Select the 'Toggle Room Alert 4E With Signal Tower Or Relay' option from the 'Action Type' drop-down menu.



Select a discovered Room Alert 4E unit with an attached Signal Tower Module from the 'Device' drop-down menu.



Select the 'Red Light' option from  the 'Toggle the' drop-down menu.  In the next drop-down menu, select 'On'.

Click the 'Save' button at the bottom of the window.



A second Action will need to be created to turn the red light off when the Alert clears.  Click the 'Add' button to create the second new Action.



On the 'Add New Action' window, name this Action 'Turn Red Light Off'.



In the 'Action Type' drop-down menu, select the 'Toggle Room Alert 4E With Signal Tower Or Relay' option.



Select the same discovered Room Alert 4E unit with an attached Signal Tower Module as in the previous Action from the 'Device' drop-down menu



Select the 'Red Light' option from  the 'Toggle the' drop-down menu.  In the next drop-down menu, select 'Off'.



Click 'Save' at the bottom of the window to save the new Action.

Now that these Actions are created for the Signal Tower, an Action/Notification List can be created to turn the Signal Tower on and off.  Please refer to How To Configure Action/Notification Lists In Device ManageR for more details.

Once the Action/Notification List has been created, an Alert must be configured to use the Signal Tower Actions.  Please refer to Creating An Alert In AVTECH Device ManageR for more details.  Remember that the 'Turn Red Light On' 'Action' should be used when the Alert is triggered, and the 'Turn Red Light Off' Action should be used as the Alert's 'Clear Action'.

If further assistance is required with this procedure, please initiate a support case by sending an email to our Technical Support staff at Support@AVTECH.com.

How To Configure An Axis Snapshot Action

Open Device ManageR and navigate to the 'Alerting' screen by clicking on the 'Alerting' button in the left navigation bar within the bottom-left side of the screen.



Next expand the 'Actions' option in the right frame and click the 'Add' button




In the 'Add New Action' window, you can fill in the 'Name' and 'Description' fields as desired to give details regarding the Action you are creating. Next, select the 'Email Snapshot From AXIS Camera' option from the 'Action Type' drop down as shown in the screen shot below.




Once you have selected the 'Email Snapshot From AXIS Camera' option, you will see two fields below the 'Action Type' drop down titled 'Contact' and 'Device'.




The 'Contact' drop down will allow you to select a pre-configured Contact to send the snapshot to. If you have no configured Contacts, you can click the 'Add' button to add a new one. The 'Device' drop down will list all of the compatible AXIS cameras discovered on your network. Select the AXIS camera you wish to get a snapshot from in this drop down.




You can select an Optional Schedule for this Action by clicking on the 'Optional Schedule' check box and selecting a configured Optional Schedule from the drop down.

For more information on Optional Schedules in Device Manager, please follow this link: Configuring Optional Schedules In Device ManageR


 

For more information on email settings in Device ManageR, please follow this link (PDF): Configuring Device ManageR To Send Email Notifications

Configure Device ManageR To Control The Relay Sensor

This is a step-by-step guide to configuring Device ManageR to toggle relay outputs on and off on a Relay Sensor attached to a Room Alert 4E unit. Before starting, please ensure that the 'Relay' option is selected on the 'Alarm Options' tab of the 'Settings' page of your Room Alert 4E. What follows is an explanation of all the steps needed to create an Alert to toggle the outputs on a Relay Sensor when the unit is in an alarm state.

In Device ManageR, click on the 'Alerting' tab on the left had menu of the interface and expand 'Actions' from the displayed options. 



First you will need to create one Action to turn a relay on and a second Action to turn the relay off on your Relay Sensor.
Click the 'Add' button to create a new Action.
On the 'Add New Action' window, give the Action an appropriate name. For this example, name it 'Relay 1 On'. You can give the Action a description to add further details if you wish, although the 'Description' field is optional.



Note that most configuration screens in Device ManageR have associated 'Help' files that you can access for additional useful reference information. Access the Help file by clicking on the green '?' to expand the Help file.



Click the 'Action Type' combo box in the pop-up window and select the 'Toggle Room Alert 4E With Signal Tower Or Relay' option.



When the 'Device' combo box is displayed, click in this combo box to select a discovered Room Alert 4E unit with an attached Relay Sensor.
Next, click the 'Toggle the' combo box and select 'Relay 1'. In the next combo box, select 'On' to turn the selected relay on when this Action is executed.



Click 'Save' at the bottom of the window to save the new Action.
Now a second Action will need to be created to turn the relay off when the Alert clears.

Click the 'Add' button to create the second new Action.
On the 'Add New Action' window, name this Action 'Relay 1 Off'.



In the 'Action Type' combo box, select the 'Toggle Room Alert 4E With Signal Tower Or Relay' option.



When the 'Device' combo box is displayed, click in this combo box and again select the same discovered Room Alert 4E unit with an attached Relay Sensor as in the previous Action.
Click the 'Toggle the' combo box and select 'Relay 1'. In the next combo box, select 'Off' to turn the relay off when the Action is executed.



Click 'Save' at the bottom of the window to save the new Action.

There are now two Actions with which can be used to turn Relay 1 on the configured Relay Sensor On and Off.

Now that these Actions are created for the Relay Sensor, you can create an Action / Notification List that will utilize the new Actions. Click on the 'Action / Notification Lists' option and click the 'Add' button.



For this example, call the Action / Notification List 'Toggle Relay 1 On/Off'. Again, the 'Description' field is optional but it may be useful to add additional notes pertinent to this item. As an example for a 'Description', you could reference that this list will turn relay 1 on when the specific reading is in an alarm state and that relay 1 will be turned off when the reading returns to a normal or cleared state.
Click the 'Add' button to add specific Actions for 'On Alert' and 'On Clear' conditions. For this example, relay 1 will be turned on when an alert occurs and turned off when that alert clears.



Click the 'Alert Action' combo box and select the 'Relay 1 On' Action you created earlier.



Now click the 'Clear Action' combo box and select the 'Relay 1 Off' Action created previously.



Click the 'Save' button to save the list item to the Action / Notification List, then click 'Save' again to save the configured Action / Notification List. Note that additional list items can be added to the Action / Notification List, such as another list item to toggle Relay 2 On/Off, or another to send out an email notification on Alert/Clear.

Next we can configure an Alert for a Room Alert 4E that will make use of the Action / Notification List that was just created. Please note that the following step assumes that an External Digital Sensor is connected to the Room Alert 4E. If not using an External Digital Sensor, adjust this step as needed to fit your specific configuration.
Expand the 'Alerts' section and click on the 'Add' button to create a new Alert.



Name your Alert 'High Temp Ext Sensor 3'
In the 'Device' combo box, select the Room Alert 4E with the Relay Sensor and External Digital Sensor connected to it.



In the 'Alarm when the sensor reading for' combo box, select the External Digital Sensor that is connected to the unit with a Fahrenheit reading (F).



In the combo box below select 'greater than or equal to (>=)' and in the field to the right, enter the value of '85'. (NOTE: You may wish to configure a different threshold. Please use whatever threshold is appropriate for your situation and that can be easily tested.)



In the 'Action / Notification List' combo box below, select the Action / Notification List you previously configured named 'Toggle Relay 1 On/Off'.



Click the 'Save' button at the bottom to save this Alert.

Now you know the basic steps needed to toggle the outputs on your Relay Sensor using Device ManageR. You can replicate these same steps for any relay option/combination for your Relay Sensor and select 'On' or 'Off' as appropriate for the specific Action. Additional Actions can be added to your Action/Notification List if desired for extra responses such as toggling the lights on a Signal Tower module, sending out email notifications on alert and clear status, taking corrective action such as shutting down Windows systems with the optional Windows Shutdown Plugin for Device ManageR  and much more.

Feel free to explore the powerful features of Device ManageR, the possibilities are limitless!

If you require assistance with this procedure or you have any questions about Device ManageR please initiate a support case by sending an email to our Technical Support staff at Support@AVTECH.com.

How To View Multiple Devices Simultaneously In Device ManageR

Device ManageR makes it possible to view multiple Room Alert or TemPageR devices simultaneously on the same screen. This makes it extremely easy to review current sensor data from multiple devices without needing to view a separate web interface for each device. To view multiple devices, open the main Device ManageR web interface. On the left side of the screen is a list of all the discovered devices on your network.



A single device can be selected by simply clicking the name of the device in the list. To select multiple devices hold the Control (CTRL) key and click on each device that you want to view. You can also hold the Control (CTRL) key and click on a device that is already selected to remove it from your multiple device view.


After you have selected the devices you want to view, you will see their current sensor status displayed. On the bottom of the left menu where you selected the devices you will also see a group of actions you can perform on all of the selected devices.


To view graphed sensor data for the selected devices, click on the 'Graph Display' tab in each device's section. This will show you the graph data for each device separately. To learn more about the graphing display, read our help article located here: How To View A Real-time Graph Of Sensor Values.

 

Device ManageR makes it extremely easy to work with multiple devices installed world-wide on the network. Sensor data from multiple devices can be displayed and graphed on a single web interface, making it easy to stay informed regarding the current status of your data center or IT environment. If you have any questions regarding configuring Device ManageR, please feel free to contact us at Support@AVTECH.com.

Unable to discover Devices with the Advanced Discovery Manual Scan Feature.

          If automatic discovery is unable to locate devices on the network, the 'Manually Add Device/s Via IP Address' feature, accessible by clicking the 'Advanced Discovery' button under 'Device Status', can be used to perform a TCP Scan on the network. This can often find devices that are overlooked by the automatic scan as it uses TCP rather than a UDP broadcast.
           If the manual scan feature is unable to find the devices, verify that TCP ports 30718 and 80 are not blocked by a firewall or other security application that may exist on the computer Device ManageR is installed on. Other possible causes for a failed scan include a local proxy or Microsoft ISA server, an intranet security device or an improperly configured managed switch. The Network Administrator at your Organization should be able to assist you in determining if any of these items are blocking your scan request. If you continue to have difficulty, please submit a support ticket.

     

  

How Do I Export the Sensor Data of a Discovered Device in Device ManageR?

A valuable feature of Device ManageR is the ability to export the 'Sensor History' data of your AVTECH Devices.  

The 'Export Log File' function allows 'Sensor History' data for either 'All' or 'Selected Devices' to be outputted to a .CSV Comma Delimited File.  This file can later be viewed in 'Excel' or 'Open Office Calc' applications for further data trending and reporting purposes.

Outlined below are the steps needed to export the 'Sensor Data History' of any AVTECH 'Room Alert' or 'TemPageR' Appliance.

1. In the AVTECH Device Manager Web Interface click on 'Settings' then 'Sensor Logging


2.Click on the 'Export Logfile' Radio Button. By default, this function is configured to export all logged sensor data for a single selected appliance. 

 

 


3. If you would like to choose from a range of dates select the 'Date Range' option instead and choose a start and end date. 


4.After making your selections, click the 'Export Alerts/Notification' button when your selections are complete to begin the export process otherwise click 'Cancel'.



5. You will be given the option to 'Open with' the file in Microsoft Office- Excel (Default), another program of choice by selecting the program in the drop down , or to 'Save' the file .


For additional questions about this or other features in Device ManageR, please contact our Technical Support team.

How To Edit Email Alert Messages in Device ManageR

One of the features of AVTECH's Device ManageR Software is to send specifically worded  'Alert' and 'Clear' Messages to the intended recipients based on the user defined temperature/humidity threshold violations, switch sensor change of state, as well as their return to normal status. 

These messages contain all the necessary information to notify users of what devices are alerting and what the current value is.

As an added option, the software offers the ability to 'customize' these alert messages.
(For Example 'Alert Subject' , 'Alert Body', 'Clear Subject' and 'Clear Body' can all be customized).  

To modify the actual text:
1. Navigate to the bottom of the alert screen.
2. Click on the black arrow that appears next to the 'Alert Notification Text ( Used For Send Email Actions - Click to Expand and Edit )' heading.





3. Once the screen expands, to add or remove text, simply click in the field of the area you wish to make the changes in, and either type in the desired text, or remove any unwanted text.

\

4. **Option** To insert 'Keywords'.

**Note** that the keywords the software is already using in the messages will be displayed by two brackets. [KEYWORD]

These can be removed or added to by clicking on the 'Insert Keyword' Radio Button.

For a complete list of keywords or to choose one, simply click on the insert keyword radio button and you will be presented with a list of them as well as a brief description of what each 'Keyword' is for.





Once the configuration has been entered, click on the 'Save' button.

How To Use The Report Generator Plugin (VIDEO)



Click Here To View A Larger Video

The Report Generator Plugin will allow you to send details about your Device ManageR installation to a Contact via email. This plugin is best used in conjunction with the Scheduled Tasks functionality of Device ManageR, however you can also send a report email when an Alert occurs. Using the Report Generator Plugin along with the Scheduled Task functionality will allow you to periodically receive automatic updates about the current status of your Room Alert, and TemPageR monitors.

To get started with the Report Generator Plugin you will first need to configure Device ManageR to use your SMTP mail server. For instructions on doing this please see the following FAQ article: Configuring Device ManageR To Send Email Notifications

Once your SMTP settings are configured you will need to configure a Contact with a valid email address. For full details on creating a Contact please see the following FAQ article: How To Create And Edit Contacts In Device ManageR

Once you have done the above steps you will be ready to configure your Action which will send a Report to a configured Contact. To do so navigate to the 'Alerts / Tasks' tab which is found in Device ManageR's left menu. Expand the 'Actions' section then click the 'Add' button. You will want to give your Action a descriptive name so you know what it's used for at with a quick glance. For example I'll name my Action 'Send Report To Network Admin'. You can also give an optional description of the Action using the 'Description' text entry field. Once you have given the Action a name and description select 'Send Email Report To Configured Contact' from the 'Action Type' drop down menu.



Once you select the Action Type you will see the extra options for the Report Generator Plugin appear. You will now want to select the Contact who will receive the report from the 'Contact' drop down menu. The other two fields which appear when you select the Reporting Action type control the actual email which is sent to the Contact. Both of these fields can be updated using the special keywords provided by the Report Generator Plugin. In order to insert a keyword into either the 'Email Subject' or 'Email Body' field you will want to place your cursor in the field at the spot you want to insert the keyword. You should then see the 'Click To Insert A Keyword' button appear.



Once you click on the insert keyword button a new screen will pop up with all of the available keywords. There are two tabs of keywords here, one set is keywords which can be used only with Alert, the other set of keywords are supplied by the Report Generator Plugin but can also be used with either Reports or Alerts. If you're creating a Report Generator Action that will be used with the Scheduled Tasks functionality none of the keywords on the 'Alerting' tab will work properly and they will not be replaced in the final email.



Once you have your email text configured  save your Action. Now that your Action is finished you can link it to a Scheduled Task which will determine when the Action is automatically executed. From the main 'Alerts / Tasks' tab click the 'Add' button under the 'Scheduled Tasks' section. You will want to give your Scheduled Task a name and optional description so you know exactly what it is configured to do.



In order for the Scheduled Task to know when to execute your Actions you will need to give it a Schedule to run off of. To create a new Schedule for this Scheduled Task click the 'Add button next to the 'Schedule' drop down.



The Optional Schedule is broken down into individual days and time ranges. When a time range is entered the Scheduled Task will begin executing the configured Actions until that time range ends. If your Actions are set up to execute repeatedly in your Scheduled Task they will continue to be executed at the defined interval until the end of the current time set.

For this example we will set the Scheduled Task to run every day at noon. First, remove all of the initial time sets except for the one under 'Sunday' by clicking the red '-' button next to them. Now set your 'Sunday' time set for '12:00PM to 12:01PM'. Once you have done this click on the 'Copy To' drop down to the right of the 'Sunday' time set and select 'All'.



This will copy the time sets that are configured for 'Sunday' to every other day of the week.



Your Optional Schedule is now configured to send your report out every day at Noon, click the 'Save' button to continue. Now that your Scheduled Task has the Optional Schedule it will use you can add the Actions that will actually be executed. Click on the 'Add' button to add a new Scheduled Task Item. On this screen you can select one Action that will be executed by the Scheduled Task. For our example all you will need to do is select your Report Generator Action from the 'Task Action' drop down menu then set the 'Perform the Action' setting to 'A maximum of 1 time'. This will cause the Action to be executed once every time a time set is entered in the configured Optional Schedule. Click the 'Save' button to save this Scheduled Task Item.

For further information regarding Optional Schedule configuration please see the following FAQ article: Configuring Optional Schedules in Device ManageR



You should now see your Scheduled Task Item appear in the table in your Scheduled Task screen. If you have any other Actions you want to execute at the same time as your Report Generator Action you can click the 'Add' button below this table to add another execution row to the Scheduled Task.

Setting Up The Dashboard View In AVTECH's Device ManageR Software.


Click Here To View A Larger Video.

Device ManageR v5.0 introduces a new 'Dashboard' feature to the main display.



The Dashboard makes it easy for users to display the information that is most important to them on a single screen, without having to check multiple pages for a variety of information.

When users open a web browser to the Device ManageR interface, a default dashboard is displayed instead of the previous device summary display. The default dashboard initially viewed is intended to demonstrate some of the possible widget types that can be configured here. 

The dashboard consists of multiple 'Widgets' that contribute to this custom setup.

Multiple types of widgets are displayed by default including:
 - A graph widget displaying the last 24 hours of sensor data for a sensor,
 - A Statistics widget that shows information about the devices and alerts being monitored by Device ManageR,
 - A Table widget that can show items such as the Top 5 Sensors ranked by:
                - The number of alerts occurred.
                - The Top 5 Devices ranked by number of alerts,
                - The Top 5 Actions taken in response to alerts,
                - The Display showing the Average, Maximum and Minimum values for sensors connected to a device
                - Much more.

Users can use this as a starting point and edit the dashboard to display the details and information specific to their application.

To edit the Dashboard, simply click the 'Edit' button next to Device ManageR Dashboard at the top of the screen.



Each of the currently displayed widgets will display along with fields to configure them.

Users can easily change the title of the widget, change the type of widget, or change the device or sensor a widget refers to.



To add a new widget, simply click the 'Add New Widget' button. Type a name the new widget and select the desired type of widget from the drop down menu.
After selecting the type of widget, additional options are available depending on the type of widget selected. For example, a Table widget can display many different types of data, all available from the appropriate drop down menu. You can display the Average, Maximum and Minimum temperature values for one of our Room Alert devices.
     
After editing the Dashboard, click the 'Save' button to save the changes. Device ManageR will then take a minute to update all of the widget data prior to displaying it.

Device ManageR will automatically update these widgets at regular intervals, so users can create widgets showing the most important information for their application
and leave it open on screen to see constant trends and information.

In addition, if multiple users have been configured in Device ManageR, each user can create their own Dashboard that is unique from other users' Dashboards. This allows each Device ManageR user to create a Dashboard that is specific to their interests and responsibilities.

Configure Device ManageR To Use Gmail As Mail Server

Device ManageR allows the use of Mail Servers that require an SSL or TLS connection. A common use for this is to configure Gmail as a Mail Server in Device ManageR. The following settings typically work with Gmail:

Mail Server IP or DNS Name: smtp.gmail.com
Port Number: 465
From (Return) Email Address: Your full Gmail address (including '@gmail.com')
Username: Your full Gmail address (including '@gmail.com')
Password: Your Gmail password

AVTECH Device ManageR Gmail Server Settings

Changing Device ManageR's Default HTTP Port

By default, Device ManageR will run on HTTP port 8080, making it accessible via web browser at 'http://<IP of Host>:8080'. If you have another service running on that port, you can change Device ManageR's default HTTP port by either using, or by editing a configuration file in Device ManageR's installation directory. Instructions for each of those methods are below.

Using DataBase Update Utility

1. Open the Windows Services dialog ('Start,' 'Control Panel,' 'Administrative Tools,' 'Services) Find the service titled 'AVTECH Device ManageR', right-click on it and select 'Stop'.

Stop AVTECH Device ManageR Service

2. Browse to your Device ManageR installation directory ('C:|Program Files|AVTECH Device ManageR' by default).

Device ManageR Default Installation Directory

3. Click on the application labeled 'DBUpdate.exe'.

4. Click on the tab labeled 'Web Server', enter the desired port into the text box labeled 'Web Port', and then click on the 'Save' button.



5. Open the Windows Services dialog again. Right-click on the 'AVTECH Device ManageR' service and select 'Start'.



You should now be able to access Device ManageR on the port you configured.For example, if you changed the port to '8585', Device ManageR will be accessible at 'http://<IP of Host>:8585'. If you have trouble accessing Device ManageR after changing the HTTP port, check to be sure no other applications are running on that port and check the logs in the 'log' folder for errors.


Manually Editing Device ManageR Configuration File


1. Open the Windows Services dialog ('Start,' 'Control Panel,' 'Administrative Tools,' 'Services) Find the service titled 'AVTECH Device ManageR', right-click on it and select 'Stop'.

2. Browse to your Device ManageR installation directory ('C:|Program Files|AVTECH Device ManageR' by default).

3. Open the folder labeled 'conf' Open the file labeled 'settings.xml' into a text editor program (i.e. Notepad).

4. The option called '<http_port>' determines which port Device ManageR will use. Change '8080' to whichever port you would like to use, and then save the file.



5. Open the Windows Services dialog again. Right-click on the 'AVTECH Device ManageR' service and select 'Start'.

Reset Device ManageR Authentication Settings

If you have misplaced or forgotten your authentication credentials to access the web interface of Device ManageR, but have access to the host system where Device ManageR is installed, you can follow the instructions below to reset them.

1. Open the Windows Services dialog ('Start', 'Control Panel', 'Administrative Tools', 'Services'), find the service named 'AVTECH Device ManageR', right-click on it and select 'Stop'.



2. Browse to your Device ManageR installation directory ('C:|Program Files|AVTECH Device ManageR' by default).



3. Open the 'conf' folder and delete the 'realm.properties' file.



4. Open the Windows Services Dialog again and right-click on the AVTECH Device ManageR service and select 'Start'.

 

Once the Device ManageR service is started, it will rebuild the 'realm.properties' file, and you should now be able to access Device ManageR without providing any user credentials. You will then want to configure credentials again on the 'Settings' page of the Device ManageR interface. For more information on configuring user accounts in Device ManageR, please see the following links:

Configuring User Accounts In Device ManageR: 'Administrator' Accounts (VIDEO): http://avtech.com/Support/index.php?action=kb&article=123

Configuring User Accounts In Device ManageR: 'Viewer' Accounts (VIDEO): http://avtech.com/Support/index.php?action=kb&article=124

Configuring User Accounts In Device ManageR: 'Guest' Accounts' (VIDEO): http://avtech.com/Support/index.php?action=kb&article=125

Room Alert 26W

Can I log sensor data on my Room Alert or TemPageR?

     AVTECH's Device ManageR software can log all sensor data for each and every Room Alert and TemPageR monitor connected to a network. Device ManageR runs as a Windows Service and uses the host system's hard drive to store logs in an SQL database. Device ManageR is available for free to all customers who have purchased a Room Alert or TemPageR monitor and have current Maintenance, Support, and Update Service (MSUS) with AVTECH. Device ManageR's logging is a standard feature along with graphing, unlimited/custom alerts, and much more. Device ManageR can be downloaded from the Downloads section at http://AVTECH.com/Downloads/ For more information on Device ManageR, please follow this link: http://AVTECH.com/Products/Device_ManageR/

How Do I Update The Firmware On My Room Alert Or TemPageR Monitor?

- Verify that you have either the AVTECH Device Discovery Utility or Device ManageR software installed on a host machine that has network visibility to the Room Alert or TemPageR monitor that is to be updated.
 - Verify that the software being used is the most current version of AVTECH Device Discovery or Device ManageR. The most current versions can be obtained via the 'Downloads' section of AVTECH.com for current MSUS subscribers.


Note which firmware version the Room Alert or TemPageR is currently running by checking the monitor's 'Status' page. The monitor's version will be in the top right hand corner.

Click here: http://avtech.com/Downloads/ and check the left side box for a list of AVTECH's released versions. If your current firmware version is older than the version listed here, please continue by logging in to the 'Downloads' section. (If you do not know your login password or if you are unsure if you  have an account, click the 'Forgot/Reset Password' link and enter your email address. If your email address is not recognized, click the 'Email Request/Inquiry' button and fill in your information. If your email address is recognized but you do not receive an email with your password, check any SPAM filter in place before contacting AVTECH Technical Support.)

Once in the downloads section, navigate to the monitor's section. Save the firmware update file but DO NOT unzip/decompress the file if it arrives as a .zip or .upd file.


DEVICE DISCOVERY UTILITY: Open Device Discovery and click the 'Search' button. 



Select the monitor that is to be updated and click the 'Update' button.

 


Follow the prompts to specify the location of the Firmware Update file for the monitor and click the 'Upload' button.

 



DEVICE MANAGER: Open Device ManageR and select the monitor from the Device Status list or click on the unit's information in the middle of the page.



Click the 'Update Firmware' button.



Click 'Browse'.



Select the appropriate file and click 'Open'.



Click the 'Update' button to begin the firmware update process.



When the firmware update process completes, the unit will automatically reboot to apply the update.
If you experience an issue during this process, please feel free to contact the Technical Support Team by submitting a support ticket.

Room Alert/TemPageR Sensor Data Not Loading

The Room Alert and TemPageR devices load the sensor data for display on the Status page using a background xml http request to a file called "getData.htm".

If sensor data is not loading, first verify that the 'getData.htm' web page is accessible by entering "http://<ip_address_of_device>/getData.htm" in the web browser location bar. 

Example 192.168.2.95/getData.htm   

You should see the following output.......





If the data fails to load, the cause can usually be traced to a proxy server or Microsoft ISA server. If your network has a proxy server or Microsoft ISA server, be sure that it is configured to ignore requests to and from Room Alert. Also verify that you do not have any local Internet security, anti-virus, or firewall applications that may be blocking, filtering or caching the background requests to this page.

A shorter test can also be used by entering in  http://ip_address_of_device/mobile.txt    Example 192.168.2.95/mobile.txt    you should see the following output....




If you see an image loading like the one above, your issue is related to either a web browser, security device/application or anti-virus program blocking requests and traffic made to the unit.  You will want to further examine  your  current security settings on your security applications and devices running on your pc and on your network.  


Please feel free to contact our Support Team at Support@AVTECH.com with any further questions.

What is Room Alert 26W?

Room Alert 26W is AVTECH Software's more advanced hardware solution for "Computer Room Environment Monitoring, Alerting & Automatic Corrective Action". It is designed specifically to assist with monitoring computer room temperature, humidity, power, flood and much more in multiple locations while utilizing wireless technology to avoid running cables in hard to reach areas or through unmodifiable walls such as walk in refrigerators. Room Alert 26W's Wireless Sensor Hubs (WiSH) communicate via a secure, private protocol that is ZigBee compatible, allowing users the ability to monitor large numbers of sensors both indoors and out up to 250´ away. Room Alert 26W allows users to log environment sensor status for immediate alert notification, historical review and graphing. Room Alert 26W allows alert notifications via email, email-to-SMS, SNMP and more to devices like computers, mobile phones, pagers and PDAs. Room Alert 26W comes standard in a 1U 19" configuration and offers an easy to use web browser interface for settings changes and viewing real-time temperature, humidity, power, flood and other environment sensor status.


Initial Discovery & Setup

A Device That Is Connected To A Managed Switch Is Not Accessible

Managed switches are a more powerful version of the basic network switch. They can be configured to screen traffic on certain ports or protocols and have been found to sometimes interfere with TemPageR or Room Alert communications. Because of this, a device can initially work as expected, but become inaccessible over time. Any switch that allows extra control over the traffic it sees is considered a managed switch for the purposes of this discussion. Symptoms usually observed are that a unit will initially work as expected but after a period of time will become inaccessible. In some cases, the IP address of the unit will still respond to pings. Cycling power on the unit temporarily resolves the issue.

A quick test to verify if the switch is the issue is to attach the device to a different network switch or hub. Be sure that the other switch is on the same network segment or the unit might be inaccessible. You can also connect the unit off the network with a crossover cable to see if the issue persists.

If the managed switch is found to be the cause of the issue, be sure to remove any configurations that might interfere with the traffic sent by the unit. Along with normal TCP 80 traffic, the device will send NTP requests on UDP port 123, email on TCP port 25, SNMP Traps on UDP port 161 and can be accessed via UDP port 30718.

In conjunction with this, there are a few other recommendations.

1.If your switch has a setting that will allow the port to act as an un-managed switch port, we highly recommend you enable this setting.

2.You should hard code the port speed on the switch the AVTECH device is connected to to a 100/Full Duplex setting. 

3.In addition, hard code the port speed on the AVTECH unit to 100/Full Duplex. The MTU size defines the size of data packets sent from the Room Alert or TemPageR device and might need to be modified to match settings on the managed switch.


4.Also, we recommend starting with a MTU of 1024. If your issues persist after hardcoding the port speed and setting the MTU, then adjust the MTU downward in increments of 64. Please note that the lowest allowable MTU size is 512. These settings are available on the 'Network' tab of the 'Settings' page of the Room Alert or TemPageR device. Uncheck the 'Auto Negotiate' checkbox and select the '100 MB' and 'Full Duplex' radio buttons. In the 'MTU Size' field, ensure that a value of 1024 or lower is entered. Remember, if your issues persist after applying these settings, gradually lower the MTU until you find the right size.

5. Finally, another option is to place a hub in between the Room Alert or TemPageR device and the switch, so that the unit connects to the hub and the hub connects to the switch. This way, the unit is negotiating with the hub rather than the switch and this should mitigate the issue.

How Do I Enable A Security Password On Room Alert Or TemPageR Monitors?

A password can be configured for each individual Room Alert or TemPageR to prevent unauthorized users from modifying the 'Settings' section.  Passwords should be alphanumeric and cannot include special characters or symbols.

To Configure A Password For Room Alert or TemPageR
  1. Type the IP Address of the monitor into a web browser to access the 'Status' page. (For Device ManageR, click the monitor in the 'Device Status' list, then select 'Open Web')
  2. Once the 'Status' page is displayed in the web browser, click the 'Settings' tab.
  3. Unless you have previously configured a password for the device, leave the user name and password fields blank and click 'OK'.  If you have previously created a password for the monitor, leave the user name field blank and enter the current password, then click 'OK'.
  4. When the 'Settings' screen displays, click the 'Security' button on the left side list.
  5. In this screen, enter the old password, new password, and confirm the new password. (If an old password is not set, leave this field completely blank)
  6. Click the 'Accept Changes' button at the bottom of the screen, then click the 'Save Settings' button in the left side list to reboot the monitor. The monitor will  reboot, and now require a password only to access the 'Settings' section.
To Reset An Unknown Password That Was Previously Set

All current Room Alert and TemPageR monitors feature a hard reset button on the back of the case. While the monitor is powered on and connected to an active network or crossover cable connection, please locate and hold down this reset button while watching the top left green light on the monitor's network port. This network light will go out for two seconds, then reappear to signify a complete reset. The monitor will now have factory default settings, which includes a blank password set for the 'Settings' section. Note that the unit will be configured for DHCP and any static IP set previously will need to be reconfigured.

If the monitor does not have a physical reset button, please contact AVTECH Technical Support and speak with one of our Technical Specialists.  

To contact AVTECH support, click here.

How do I set a Static IP address on my Room Alert or TemPageR?

A Static IP address can be set for your Room Alert or TemPageR unit by using the AVTECH Device Discovery Utility, AVTECH Device ManageR, or via the 'Network' section in the 'Settings' tab of the Room Alert or TemPageR web browser interface.

To set a Static IP address using the AVTECH Device Discovery Utility, open the AVTECH Device Discovery Utility and click the 'Search' button. Select the monitor you wish to assign a static IP address to and click the 'Set IP' button. Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit being updated.

To set a Static IP address using the AVTECH Device ManageR Software, open the Device ManageR software and click the monitor in the left hand 'Device Status' list. You will notice a small drop down below the currently selected monitor. Click the '-Set IP Address' button.
Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit you are updating.

To set a Static IP address using the monitor's web browser interface, enter the current IP address of your Room Alert or TemPageR monitor into the location bar of a web browser. The 'Status' page will load by default and display the current sensor values. Click the 'Settings' tab at the top of the page and the 'Network' section will load. Uncheck the 'Use DHCP' checkbox and enter the desired static IP information in the available fields. Be sure that all static IP address information is correct for the location of the monitor you are updating. To complete the changes, please click the 'Accept Changes' button at the bottom of your page and then the 'Save Settings' button on the left hand side. The monitor will now reboot and apply the new changes.

If the Room Alert or TemPageR monitor cannot be discovered or you do not know the existing IP address, a Static IP address can be set using the MAC address of the unit, which can be found on a label on the bottom of the monitors. Please open Device Discovery and click the 'Set IP' button without selecting a device from the list and follow the prompts from the AVTECH Device Discovery Utility. Alternatively, you can set a Static IP address via the MAC address of your monitor in Device ManageR.
Open Device ManageR and click the 'Advanced Discovery' button in the top left hand corner on the 'Device Status' list. This button will display a pop up that will have a 'Set IP Via MAC Address' button. From here, enter the MAC address of the monitor and the desired Static IP address.When finished, press the 'Update IP Settings' button to make the changes.

How Do I Update The Firmware On My Room Alert Or TemPageR Monitor?

- Verify that you have either the AVTECH Device Discovery Utility or Device ManageR software installed on a host machine that has network visibility to the Room Alert or TemPageR monitor that is to be updated.
 - Verify that the software being used is the most current version of AVTECH Device Discovery or Device ManageR. The most current versions can be obtained via the 'Downloads' section of AVTECH.com for current MSUS subscribers.


Note which firmware version the Room Alert or TemPageR is currently running by checking the monitor's 'Status' page. The monitor's version will be in the top right hand corner.

Click here: http://avtech.com/Downloads/ and check the left side box for a list of AVTECH's released versions. If your current firmware version is older than the version listed here, please continue by logging in to the 'Downloads' section. (If you do not know your login password or if you are unsure if you  have an account, click the 'Forgot/Reset Password' link and enter your email address. If your email address is not recognized, click the 'Email Request/Inquiry' button and fill in your information. If your email address is recognized but you do not receive an email with your password, check any SPAM filter in place before contacting AVTECH Technical Support.)

Once in the downloads section, navigate to the monitor's section. Save the firmware update file but DO NOT unzip/decompress the file if it arrives as a .zip or .upd file.


DEVICE DISCOVERY UTILITY: Open Device Discovery and click the 'Search' button. 



Select the monitor that is to be updated and click the 'Update' button.

 


Follow the prompts to specify the location of the Firmware Update file for the monitor and click the 'Upload' button.

 



DEVICE MANAGER: Open Device ManageR and select the monitor from the Device Status list or click on the unit's information in the middle of the page.



Click the 'Update Firmware' button.



Click 'Browse'.



Select the appropriate file and click 'Open'.



Click the 'Update' button to begin the firmware update process.



When the firmware update process completes, the unit will automatically reboot to apply the update.
If you experience an issue during this process, please feel free to contact the Technical Support Team by submitting a support ticket.

How To Use The Trace Feature On A Room Alert Or TemPageR Device

The tracing feature is a very useful tool that can be used to assist in troubleshooting issues with your Room Alert or TemPageR device.

To enable tracing on your unit, follow these steps:

       1.   Access the 'Advanced' tab of the 'Settings' page.


  

       2.   In the 'Trace Configuration' section, ensure that the 'Enable Tracing' check box is checked. The tracing port is 143 by default. You do not need to change this unless you know port 143 will be blocked by your network for some reason. After making changes in this section, click the 'Accept Changes' button at the bottom of the screen, then the 'Save Settings' button on the left hand side of the screen.




To generate a trace from your device you will want to enter the following command into a Windows command prompt: 'telnet -f c:\tracefile.txt <IP of unit> <trace port #>' then press the <Enter> key. Where 'IP of unit' is the IP address of your Room Alert or TemPageR device and 'trace port #' is the configured trace port (143 by default). So the command might look something like this: 'telnet -f c:\tracefile.txt 192.168.33.100 143'. This command will capture your trace data directly to a text file named 'tracefile.txt' in the C: directory.

Please note that Windows 7 and Vista have disabled the Telnet client by default. If you get an error saying 'telnet is not recognized as an internal or external command, operable program or batch file' you will need to enable it by going to 'Start', 'Control Panel', 'Programs And Features', 'Turn Windows Features On Or Off' then checking the 'Telnet Client' row and clicking 'OK'.


At times, it may be useful or necessary for our engineers to review a trace from a Room Alert or TemPageR device and we may request you send us the results of a trace. If you are requested to send a trace in by one of our technical support specialists, or if you feel it will be helpful before being asked, simply attach the file created by the command given above to an email and send it to us at 'Support@AVTECH.com'.

One example of how to use the tracing feature is for troubleshooting email issues with your device. To troubleshoot email issues using the trace feature, launch the trace window using the process described above. Once you have successfully connected to the trace, browse to the 'SMTP Email' tab on the 'Settings' page. Try sending an email by clicking the 'Send Test Email' button at the bottom of the SMTP Email tab. You should see the attempts by the Room Alert or TemPageR device to connect to the configured mail server in the trace output window. If there are any issues occurring with the email process, you should see corresponding errors displayed in the output window which should point you in the right direction as to what might be causing any issue.

My Room Alert Or TemPageR Monitor Is Not Discoverable Or Accessible On My Network. How Do I Discover My Room Alert Or TemPageR?

Device ManageR and the Device Discovery Utility use a broadcast scan on UDP port 30718 to automatically locate AVTECH monitors on a network.
AVTECH recommends the following for initial product discovery:
 - DHCP Enabled on network.
 - UDP Broadcasts allowed at a computer and network level.
Please Note Before Beginning:
 - The network cable must be plugged in to the Room Alert or TemPageR monitor and the switch or computer before power is connected. This ensures that the initial DHCP request will be sent successfully when power is connected.

 - If the monitor has been assigned a static IP address that is invalid for the current IP address range of the network, please proceed to step 3 of this guide.
 - When the Room Alert or TemPageR monitor is powered on and plugged into a network, please check the current status of the Network Jack's lights as these lights are used to determine the current state of the monitor. The left link light should be a solid green color while the right light should be a flashing green or orange. If these lights display any other patterns than this, please skip to step 5 of this guide.

To begin discovering the monitor's IP address, please follow the instructions below starting at step 1.

1. Both Device ManageR and the Device Discovery Utility have a manual discovery feature that uses a TCP scan on TCP port 30718. This feature is helpful if the network range or specific IP address of the monitor is known. 

 - To access this feature using Device ManageR, click the 'Advanced Discovery Options...' button under 'Device Status' in the left menu. Click the 'Manually Add Device/s Via IP Address' button and select either 'Single IP Address' or 'Range Of IP Addresses'. Insert the desired IP address or range and click the 'Begin Scan...' button.

 

 - To access this feature using the Device Discovery Utility, click the 'Advanced Discovery' button located under the 'Search' button. Then, select either 'Single IP Address' or 'Range IP Addresses' and enter the single IP address or IP address range. Start the scan using the 'Begin Scan' button.


2. DHCP Enabled On Network – All AVTECH monitors are initially set to obtain an IP address automatically using DHCP. DHCP must be enabled on the network for the monitor to receive a valid IP address. If DHCP is not enabled, the monitor will default to an auto IP address in the 169.254.xxx.xxx range. At this IP address, the router or system firewalls may not allow discovery because the IP address is outside of the valid network IP range. Valid assignment could potentially be hindered by a managed switch even if DHCP is enabled. If DHCP assignment is delayed in the managed switch, the DHCP request sent from the monitor can timeout and default to a 169.254.xxx.xxx Auto IP address.

 - If DHCP is enabled on the network, there is a chance the DHCP server has already assigned a valid IP address even though the monitor is not discoverable. If the manual discovery option from step 1 does not discover the monitor, the IP address can sometimes be obtained by checking the DHCP server for the MAC address of the monitor.

 - If the IP address can be verified by checking the DHCP server and the IP address is in range of the network, it can be added to Device ManageR and the Device Discovery Utility using the manual scan feature from step 1. This IP address can additionally be accessed by directly by typing the IP address in a web browser. 

 - It is also possible to create a DHCP reserved IP address on a server. Doing this and recycling the power on the monitor should allow the IP address to be assigned by the DHCP server. If this process is unknown or unable to be completed personally, please consult the local Network Administrator. Otherwise, continue to the next step.

3. If the IP address of the monitor is still not discoverable, AVTECH recommends connecting the unit directly to a computer or laptop using a cross-over Ethernet cable or spare network hub.

 - Before disconnecting a computer or laptop to be used from the current network, be sure that the Device Discovery utility is installed along with a protocol analyzer (packet sniffer) application. If a preferred protocol analyzer application is unknown or not installed, a free utility called 'Wireshark' can be installed from http://www.wireshark.org/.

 - Begin by assigning a static IP address to the computer's network card, then connect the monitor via cross-over Ethernet cable or spare network hub to the computer. Lastly, plug in the power to the Room Alert or TemPageR monitor to begin the connection process. 

 - Attempt discovery using the Device Discovery utility by clicking the 'Set IP' button. The 'Set IP' button can set an IP via the MAC address which can be found at the bottom of any Room Alert or TemPageR monitor's case. Follow the procedure as prompted by Device Discovery and remember to set the IP to a valid IP address that is within the same subnet as the IP set for the computer's network card. After doing this, the monitor should be accessible via the Device Discovery list or by directly entering the newly set IP address in a web browser.

4. DHCP alternative to the static IP settings above: While still on the cross-over cable direct connection between the computer and monitor, the Room Alert or TemPageR may also be reset back to initial DHCP factory defaults via the reset button on the back panel of the monitor (if applicable). 

- For TemPageR3E, Room Alert 4E, 11E: Hold the reset button in for 10-15 seconds until the top left LED on the Ethernet jack blinks. A reset has occurred when this light on the ethernet jack goes out, then reappears 1 second later. Please release the reset button after this occurs.

 - For Room Alert 24E, 26W, 32E/W: Hold the reset button in for 10-15 seconds and watch the 3 main status lights on the front of the monitor. A reset has occurred as the front 3 status lights cycle through red and then finish cycling. Please release the reset button after this occurs.

 - With the unit now set back to DHCP factory defaults, change the laptop's network card settings to automatically obtain an IP address as opposed to specifying a static IP. Start up the Device Discovery utility and click 'Search' to locate the monitor.

 - If the Device Discovery utility methods are not working and the above steps have not located the monitor, start the protocol analyzer application, Begin packet capture and recycle the power on the monitor. Look for incoming packets coming from the MAC address of the monitor (located on a sticker on the bottom of the monitor's case or on the back of a rack mount kit if applicable). One of these packets should contain the source IP address of the monitor. Once this IP address has been obtained, configure a static IP address on the laptop or computer that is within a valid network range in relation to the IP address assigned to the unit as in step 3 (i.e. IP of unit: 192.168.2.3 - IP for computer or laptop: 192.168.2.4). The monitor can now be directly accessed by entering the IP address in a web browser.

5. If the above trials have been unsuccessful in discovering the IP address of the unit, please email Support@AVTECH.com with the packet capture obtained in step 4 attached to the email.

The Activity LED is flashing orange on my Room Alert unit and it does not appear on the network. How can I resolve this?

In the event that your Room Alert unit is inaccessible on your network, the Link LED (LED on left side of Ethernet port) on your unit is unlit and the Activity LED (LED on right side of Ethernet port) on your unit is flashing orange, please follow the instructions below to recover your unit.

  1. Verify that you have version 3.1.1 or later of the AVTECH Device Discovery Utility installed on a system with only 1 Ethernet Adapter.

  2. Obtain your unit's Firmware Update file from the download section for that specific model. Save it to your desktop and DO NOT unzip the Firmware Update file if it arrives as a .zip file.

  3. Disconnect the Ethernet cable from the system you are currently working on and use a crossover Ethernet cable to connect the system to the hardware unit.

  4. If your system does not have a static IP address set, temporarily configure it with a static IP address for the recovery process.

  5. Temporarily disable any firewalls or anti-virus programs that might block the firmware recovery packets.

  6. Reconnect the power to the hardware unit and start the AVTECH Device Discovery Utility.

  7. Click the 'OK' button on the dialog that appears and replace the 'XX-XX-XX' in the next dialog with the last three segments of the MAC address of your hardware unit. The MAC address of your hardware unit will be listed on a label located on the bottom of the hardware unit.

  8. Follow the instructions on the next dialog and recycle the power on your hardware unit.

  9. When the 'Open File' dialog opens, navigate to the location where you saved the Firmware Update file, select it and click the 'Upload' button.

  10. When the 'Set IP' dialog appears, enter a valid static IP address, gateway IP address, subnet mask and DNS server IP address in relation to the static IP settings you configured the system you are working on with.

  11. The IP address information you entered will be uploaded to your hardware unit and your hardware unit will be rebooted. Upon reboot, the full Firmware Update file will be uploaded to your hardware unit. If you initially had your unit set to DHCP before performing these steps, select your hardware unit in the AVTECH Device Discovery Utility, click the 'Set IP' button and enter '0.0.0.0' in the 'Set IP' dialog. Click 'OK' and wait for your unit to reboot. If a static IP address, gateway IP address, subnet mask and DNS server IP address were originally assigned to your hardware unit, select your unit in the AVTECH Device Discovery Utility and click the 'Set IP' button. Enter the original static IP address, gateway IP address, subnet mask and DNS server IP address assigned to the hardware unit. Click 'OK' and wait for your unit to reboot.

  12. Unplug your hardware unit and disconnect the crossover Ethernet cable.

  13. Install your unit in it's previous location by plugging in the Ethernet cable first and then powering on the hardware unit.

If you experience an issue during this process, please feel free to contact our technical support department by submitting a support ticket.

Trouble/Issues Accessing the 'Downloads' Section of AVTECH.com

The 'Downloads' section on AVTECH.com is AVTECH's only source of Device ManageR, Room Alert/TemPageR firmware updates, Software updates, MIB files, Device ManageR plugins, and the Device Discovery utility. To gain access to this section, AVTECH will issue a username and password to all contacts that are employed by organizations that have purchased a Room Alert or TemPageR environmental monitor.

If you have been previously issued a username and password from AVTECH: When attempting to log on to the AVTECH Downloads section, make sure that the password being used is entered correctly as the password is case sensitive. Please note the email address that was initially given to AVTECH at the time of registration is the only email that can be used to log on to this section.

If the initial password for the 'Downloads' section of AVTECH.com has been lost or forgotten, go to AVTECH.com/Downloads/ and select the 'Forgot/Reset Password' link below the login section. Enter the registered email address in the new screen and select 'Submit'. If the email address matches a record that was previously created in AVTECH's registry, an email will be sent with the required password.

If you are able to access AVTECH's downloads, but your downloads are expired: The specific downloads provided to your organization are regulated by AVTECH's Maintenance, Support, and Update Service (MSUS). MSUS is an annually renewed service for each of the Room Alert and TemPageR units owned by the organization. If MSUS needs to be renewed, please send an email to RenewMSUS@AVTECH.com including the organization's name and your personal contact information. For more information on MSUS, please refer to this page link:  http://www.AVTECH.com/PDFs/AVTECH_MSUS_Explained.pdf 

If you are a new contractor or temporary hire and require access to AVTECH Downloads: Please provide the following information in an email to 'Support@AVTECH.com' along with a short message explaining the need for access. Once approved, you will be registered as a contractor or temporary hire directly under the organization that owns the Room Alert or TempageR product. Please include the following information in this email:

Organization Name
Organization Address
Organization Phone Number
Your Full Name
Direct Phone Number
Email Address
Job Title
Summary Of Work To Be Completed

For all other issues accessing the 'Downloads' section of AVTECH.com, send an email to 'Support@AVTECH.com' and we will be able to provide further assistance.


Status Screen

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.



Settings Screen

I am unable to get my Room Alert or TemPageR monitor to send email alerts properly. How do I send email alerts directly from the monitor's web page?

Email alerts from the Room Alert or TemPageR monitors are sent using anonymous, unauthenticated SMTP email on TCP port 25. If email notifications are not received, first verify the email settings in the 'SMTP Email' section of the 'Settings' page.
  1. Mail Server Port: This port is typically port 25 but can be different based on personal mail server settings and network preferences. Please check with the mail server administrator for the exact port number.
  2. Mail Server: If the monitor is configured to obtain an IP address using DHCP, enter the specific IP address of the mail server in the ‘Mail Server Address’ field. If the monitor is configured with a static IP address, the DNS name for the mail server can be entered in this field. For initial testing purposes, enter an email address from the same domain as the mail server in the ‘Email Recipients’ field. For example, if the domain name is 'Example.com', be sure the email used to test is from the same domain (i.e. YourEmail@Example.com).
  3. Return Address: To finish the configuration, enter the same email address in the ‘Return Address (From)’ field. Using the same domain name minimizes the risk that security settings on the email server would prevent the message from being delivered.
  4. Display URL: The display URL is a URL that will be at the bottom of your received email alert. This URL is here to allow quick link/access to any URL after an alert is triggered. This URL can be a link to any web page you would like, but typically we assume that quick access to your Room Alert's web page is necessary here. Type in the IP address of the monitor or any other web page that is desired in this field.
  5. Authentication: This field is optional because not all mail servers require authentication. Please check with the mail server administrator if there are any questions about this field. The Username and Password would typically be the same credentials used to log on to a mail server directly.
  6. Email Recipients: List the email addresses that the alert will be sent to and separate multiple addresses by a comma. For example, John@Example.com,James@Example.com,Steve@Example.com Please note that due to limited flash memory on the Room Alert and TemPageR monitors, the Email Recipients field is only 79 characters long. For more space, AVTECH recommends creating a distribution list in the email server itself or for unlimited email entries and advanced/custom alerting, please follow this link for AVTECH Device ManageR: http://avtech.com/Products/Device_ManageR/


     Once the email settings are configured, click the ‘Test Email’ button and check the email account(s) for the test email. If the message is not received, first check any spam filter that may be in place. If the test email cannot be found, it could be blocked by the mail server. Be sure the mail server is configured to allow 'SMTP Relaying' from the IP address of the monitor. Also, be sure the Room Alert or TemPageR is on the email server's 'whitelist' to prevent messages from being filtered or blocked as spam. If messages from the monitor continue to be blocked by the mail server, contact the mail server administrator to see if the mail server logs can be reviewed to determine why the messages are being blocked.

If you have followed the steps above but are still unable to receive email alerts, please contact our Technical Support Team by
submitting a support ticket.

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.


What is the Default 'Settings' Screen Password on Room Alert or TemPageR?

The 'Settings' screen of Room Alert and TemPageR is password protected to prevent unauthorized users from modifying the settings. By default, there is no user name and password configured to access the 'Settings' screen of a Room Alert or TemPageR. With the User Name and Password fields left blank, select 'OK' to access the 'Settings' screen.

If you have previously configured a password for the device, leave the User Name field blank and enter your password in the 'Password' field, then select 'OK' to access the 'Settings' screen.

When I try to access the 'Settings' screen on my Room Alert or TemPageR, my web page flashes or does not load properly. How do I access the 'Settings' screen?

The 'Settings' screen on the Room Alert and TemPageR units consist of a Java applet that accesses the device on UDP port 30718 and 30719. To view the 'Settings' applet, Java software must be installed in the browser being used to access the web interface. Java software can be installed at Java.com. Next, verify that you do not have UDP port 30718 and 30719 blocked on any device located between the system or server you are currently using and your unit. If this is the case, unblock the port and try accessing the 'Settings' screen again.

The 'Settings' screen consists of an HTML form that submits and retrieves data using Java script and normal http 'get' and 'post' requests. When the 'Settings' screen flashes or doesn't load properly, we have noticed that a typical cause would be certain security devices such as Microsoft's ISA proxy server or antivirus programs that are implemented on your network. If you can, please check your network and see if any of these items are in fact implemented and are interfering with communications. In order for the 'Settings' tab to open, our program runs certain commands and pages in the background which conflict with some antivirus program's or Internet Security Server's configured settings.

You can attempt to check these pages by trying the following two addresses   http://<IP of unit>/secure/setuprec.xml  and  http://<IP of unit>/secure/unitinfo.xml  Once you have called upon them, please right click and 'view source' on them. If you notice anything strange here or are receiving an error message we would appreciate seeing them for reference. You can  take screen shots or make a text copy of the contents and send them to us here at Support@AVTECH.com

To resolve this issue, typically we see that a proxy server or antivirus is blocking background XML HTTP requests. A typical fix is to allow or add exceptions to the Room Alert Or TemPageR IP address in all security implementations.

If you are still having difficulty, please follow the steps below and attempt to access the 'Settings' screen after completing each one.

  1. Completely close the web browser you are using and reload. If you have any alternate web browsers, please attempt to access the settings page with these browsers as well.

  2. Recycle the power on your unit.

  3. Reupload/update the firmware on your Room Alert or TemPageR unit. For complete instructions on doing so, please follow this link:  http://avtech.com/Support/index.php?action=kb&article=40

If steps 1-3 do not resolve the issue, we suggest disconnecting your device from your network and attempt to connect to it via a laptop and Device Discovery through a crossover cable. When using a cross over cable, you should plug the crossover cable in to the device and the PC first, then plug in the power to the unit. Remember to set up your laptop's network card to be within the same subnet range as your Room Alert and TemPageR unit, then attempt to discover your unit with the Device Discovery Unit. For more information on discovering your unit, please follow this link. http://AVTECH.com/Support/index.php?action=kb&article=73 If you have discovered your unit and are able to access your unit's 'Settings' page, this means that one of the previous topics discussed is most likely still an issue on your network. If you have successfully connected via a crossover cable and are still unable to properly access the settings page, please feel free to contact our technical support staff by submitting a support ticket.


Sensors

Can I add additional sensors to my Room Alert or TemPageR after my initial order?

Yes. Many environmental sensors are available for purchase at any time from AVTECH such as temperature, humidity, power, flood, smoke, motion, room entry and many more. A list of these sensors can be found here: http://avtech.com/Products/Monitor_-_Sensors/ For additional information and purchasing of our environmental sensors, please contact an AVTECH Senior Product Specialist at 888.220.6700.

External Digital Temperature and Humidity Sensor Placement Suggestions

Placing Digital Temperature Sensors in the right locations is essential for reliable monitoring of the environment. Without proper placement, the most relevant temperature data may not be obtained.

 - It is recommended that the Room Alert or TemPageR unit itself is placed near the equipment that you wish to monitor as the standard cable length for Digital Temperature Sensors is 25 feet. External digital sensors may be extended up to 100 feet in length with the use of cable extensions found here: http://avtech.com/Products/Monitor_-_Accessories/Extended_Cable_Coupler.htm.

 - Measuring the temperature of the aisles in the data center at multiple height levels can give an early indication of a potential temperature problem. For consistent and reliable temperature monitoring, place a temperature sensor at least every 25 feet in each aisle with sensors placed closer together if high temperature equipment like blade servers are in use. It is important to know that data center temperatures can drastically vary in nearby locations depending on height from the floor, the specific equipment that is present, and how much equipment is present.

 - AVTECH recommends installing TemPageR and Room Alert rack units at the top of each rack in the data center as the heat generated by the components in the rack rises up to the unit which will give the most accurate readings, TemPageR and Room Alert units will be able to provide an early warning and notify staff for temperature issues before critical systems, servers or network equipment is damaged. You may wish to consider purchasing additional AVTECH devices and sensors to maximize the area that can be monitored.

 - In addition, avoid locating your sensor cables near large electromagnetic devices and florescent lights.

 - Place your sensor cables so that they are located in a safe place away from frequent foot traffic or constant disruption from moving parts.

Click here to review an article entitled Recommended Computer Room Temperature and Humidity. For additional information, please visit ASHRAE (the American Society of Heating, Refrigerating, and Air-Conditioning Engineers) to view a document called "Thermal Guidelines for Data Processing Environments" to assist you in planning how to best place your Digital Temperature Sensors in your organization's environment.

How do I extend my Digital Sensor Cable longer than the supplied 25 feet?

By design, external digital sensor cables are 25 feet in length and can be extended up to a supported100 feet in total length.

To extend the sensor cable, you will need a RJ-11 cable with coupler which is available from AVTECH Software.

To order these cables, contact your Product Specialist or click here to purchase on-line.

To extend an external digital sensor cable:

  1. Remove the external digital sensor to be extended by unplugging its RJ-11 cable from the front of the unit.
  2. Using a 25 foot RJ-11 cable with coupler, insert the RJ-11 connector into the AVTECH unit’s external sensor port.
  3. Plug the RJ-11 connector on the sensor cable to the extension cable.

If you wish to extend the sensor up to the supported 100 feet in length, multiple RJ-11 extension cables can be connected using the methods above.

It is important to note that AVTECH does not recommend extending a cable to a greater distance than 100 feet and does not support splicing or cutting into existing wires to shorten or lengthen the provided cable.



Internal Temperature Sensor Can Be Higher on Powered WiSH Sensors

The Powered Wireless Sensor Hub (P-WiSH) is a wireless sensor that transmits sensor data from internal and connected sensors back to the Room Alert 26W. The P-WiSH has one internal Digital Temperature Sensor and two external digital sensor ports. The P-WiSH is powered by an AVTECH 5V Power Adapter and has internal circuitry to regulate this power. The heat generated by the internal power regulator can cause the internal temperature sensor to report a slightly higher temperature when compared to one of its external sensors or a third party thermometer. This is normal, and the internal temperature reading can be adjusted using the 'Adjust' field in the Room Alert 26W or Room Alert 32W Settings. For more information on the adjust field and how to change it, click here.

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.

Temperature Conversion Formulas

[F = Fahrenheit, C = Celsius]


To Convert Celsius To Fahrenheit

F = 1.8C + 32


To Convert Fahrenheit To Celsius

C = F – 32
          1.8

Why is the internal temperature reading on my Room Alert or TemPageR monitor higher than the external sensors?

The internal temperature sensor measures the ambient air temperature inside the Room Alert or TemPageR device. Under normal operating conditions, the device can generate some heat internally that can cause the internal sensor to register a temperature that is a few degrees higher than the external sensors. This is normal and especially holds true for any rack mounted monitors, as the temperature inside of a rack is typically warmer than the surrounding environment where the external temperature sensors are located. All sensor readings, including internal sensors, can be calibrated using the 'Settings' page of the monitor's firmware.

Click the 'Settings' link and go to the 'Sensors' tab. If desired, enter a integer value in the 'Adjust' field to calibrate the internal sensor reading to match the readings from the external sensors. For example, if the internal temperature is two (2) degrees higher than the external sensor, put a '-2' in the 'Adjust' field for Sensor 1.

If your Adjust field value seems to be different than what you initially saved it as, it is most likely due to the conversion from Celsius to Fahrenheit. For more information, please follow this link: http://AVTECH.com/Support/index.php?action=kb&article=119

If you have any further questions, please feel free to contact our Technical Support Team by submitting a support ticket.

Wireless

Internal Temperature Sensor Can Be Higher on Powered WiSH Sensors

The Powered Wireless Sensor Hub (P-WiSH) is a wireless sensor that transmits sensor data from internal and connected sensors back to the Room Alert 26W. The P-WiSH has one internal Digital Temperature Sensor and two external digital sensor ports. The P-WiSH is powered by an AVTECH 5V Power Adapter and has internal circuitry to regulate this power. The heat generated by the internal power regulator can cause the internal temperature sensor to report a slightly higher temperature when compared to one of its external sensors or a third party thermometer. This is normal, and the internal temperature reading can be adjusted using the 'Adjust' field in the Room Alert 26W or Room Alert 32W Settings. For more information on the adjust field and how to change it, click here.

Room Alert 24E

Can I log sensor data on my Room Alert or TemPageR?

     AVTECH's Device ManageR software can log all sensor data for each and every Room Alert and TemPageR monitor connected to a network. Device ManageR runs as a Windows Service and uses the host system's hard drive to store logs in an SQL database. Device ManageR is available for free to all customers who have purchased a Room Alert or TemPageR monitor and have current Maintenance, Support, and Update Service (MSUS) with AVTECH. Device ManageR's logging is a standard feature along with graphing, unlimited/custom alerts, and much more. Device ManageR can be downloaded from the Downloads section at http://AVTECH.com/Downloads/ For more information on Device ManageR, please follow this link: http://AVTECH.com/Products/Device_ManageR/

How Do I Update The Firmware On My Room Alert Or TemPageR Monitor?

- Verify that you have either the AVTECH Device Discovery Utility or Device ManageR software installed on a host machine that has network visibility to the Room Alert or TemPageR monitor that is to be updated.
 - Verify that the software being used is the most current version of AVTECH Device Discovery or Device ManageR. The most current versions can be obtained via the 'Downloads' section of AVTECH.com for current MSUS subscribers.


Note which firmware version the Room Alert or TemPageR is currently running by checking the monitor's 'Status' page. The monitor's version will be in the top right hand corner.

Click here: http://avtech.com/Downloads/ and check the left side box for a list of AVTECH's released versions. If your current firmware version is older than the version listed here, please continue by logging in to the 'Downloads' section. (If you do not know your login password or if you are unsure if you  have an account, click the 'Forgot/Reset Password' link and enter your email address. If your email address is not recognized, click the 'Email Request/Inquiry' button and fill in your information. If your email address is recognized but you do not receive an email with your password, check any SPAM filter in place before contacting AVTECH Technical Support.)

Once in the downloads section, navigate to the monitor's section. Save the firmware update file but DO NOT unzip/decompress the file if it arrives as a .zip or .upd file.


DEVICE DISCOVERY UTILITY: Open Device Discovery and click the 'Search' button. 



Select the monitor that is to be updated and click the 'Update' button.

 


Follow the prompts to specify the location of the Firmware Update file for the monitor and click the 'Upload' button.

 



DEVICE MANAGER: Open Device ManageR and select the monitor from the Device Status list or click on the unit's information in the middle of the page.



Click the 'Update Firmware' button.



Click 'Browse'.



Select the appropriate file and click 'Open'.



Click the 'Update' button to begin the firmware update process.



When the firmware update process completes, the unit will automatically reboot to apply the update.
If you experience an issue during this process, please feel free to contact the Technical Support Team by submitting a support ticket.

Room Alert/TemPageR Sensor Data Not Loading

The Room Alert and TemPageR devices load the sensor data for display on the Status page using a background xml http request to a file called "getData.htm".

If sensor data is not loading, first verify that the 'getData.htm' web page is accessible by entering "http://<ip_address_of_device>/getData.htm" in the web browser location bar. 

Example 192.168.2.95/getData.htm   

You should see the following output.......





If the data fails to load, the cause can usually be traced to a proxy server or Microsoft ISA server. If your network has a proxy server or Microsoft ISA server, be sure that it is configured to ignore requests to and from Room Alert. Also verify that you do not have any local Internet security, anti-virus, or firewall applications that may be blocking, filtering or caching the background requests to this page.

A shorter test can also be used by entering in  http://ip_address_of_device/mobile.txt    Example 192.168.2.95/mobile.txt    you should see the following output....




If you see an image loading like the one above, your issue is related to either a web browser, security device/application or anti-virus program blocking requests and traffic made to the unit.  You will want to further examine  your  current security settings on your security applications and devices running on your pc and on your network.  


Please feel free to contact our Support Team at Support@AVTECH.com with any further questions.

What is Room Alert 24E?

Room Alert 24E is an advanced hardware solution for "Computer Room Environment Monitoring, Alerting & Automatic Corrective Action". It is designed specifically to assist with monitoring computer room temperature, humidity, power and much more in multiple locations up to 900' away from the ID box. Room Alert 24E offers users the ability to monitor large numbers of sensors both indoors and out. Room Alert 24E allows users to log environment sensor status for immediate alert notification, historical review and graphing. Room Alert 24E allows alert notifications via email, email-to-SMS, SNMP and more to devices like computers, mobile phones, pagers and PDAs. Room Alert 24E comes standard in a 1U 19" configuration and offers an easy to use web browser interface for settings changes and viewing real-time temperature, humidity, power and other environment sensor status. For complete information on the Room Alert 24E, please visit the unit's web page: http://avtech.com/Products/Environment_Monitors/Room_Alert_24E.htm


Initial Discovery & Setup

A Device That Is Connected To A Managed Switch Is Not Accessible

Managed switches are a more powerful version of the basic network switch. They can be configured to screen traffic on certain ports or protocols and have been found to sometimes interfere with TemPageR or Room Alert communications. Because of this, a device can initially work as expected, but become inaccessible over time. Any switch that allows extra control over the traffic it sees is considered a managed switch for the purposes of this discussion. Symptoms usually observed are that a unit will initially work as expected but after a period of time will become inaccessible. In some cases, the IP address of the unit will still respond to pings. Cycling power on the unit temporarily resolves the issue.

A quick test to verify if the switch is the issue is to attach the device to a different network switch or hub. Be sure that the other switch is on the same network segment or the unit might be inaccessible. You can also connect the unit off the network with a crossover cable to see if the issue persists.

If the managed switch is found to be the cause of the issue, be sure to remove any configurations that might interfere with the traffic sent by the unit. Along with normal TCP 80 traffic, the device will send NTP requests on UDP port 123, email on TCP port 25, SNMP Traps on UDP port 161 and can be accessed via UDP port 30718.

In conjunction with this, there are a few other recommendations.

1.If your switch has a setting that will allow the port to act as an un-managed switch port, we highly recommend you enable this setting.

2.You should hard code the port speed on the switch the AVTECH device is connected to to a 100/Full Duplex setting. 

3.In addition, hard code the port speed on the AVTECH unit to 100/Full Duplex. The MTU size defines the size of data packets sent from the Room Alert or TemPageR device and might need to be modified to match settings on the managed switch.


4.Also, we recommend starting with a MTU of 1024. If your issues persist after hardcoding the port speed and setting the MTU, then adjust the MTU downward in increments of 64. Please note that the lowest allowable MTU size is 512. These settings are available on the 'Network' tab of the 'Settings' page of the Room Alert or TemPageR device. Uncheck the 'Auto Negotiate' checkbox and select the '100 MB' and 'Full Duplex' radio buttons. In the 'MTU Size' field, ensure that a value of 1024 or lower is entered. Remember, if your issues persist after applying these settings, gradually lower the MTU until you find the right size.

5. Finally, another option is to place a hub in between the Room Alert or TemPageR device and the switch, so that the unit connects to the hub and the hub connects to the switch. This way, the unit is negotiating with the hub rather than the switch and this should mitigate the issue.

How Do I Enable A Security Password On Room Alert Or TemPageR Monitors?

A password can be configured for each individual Room Alert or TemPageR to prevent unauthorized users from modifying the 'Settings' section.  Passwords should be alphanumeric and cannot include special characters or symbols.

To Configure A Password For Room Alert or TemPageR
  1. Type the IP Address of the monitor into a web browser to access the 'Status' page. (For Device ManageR, click the monitor in the 'Device Status' list, then select 'Open Web')
  2. Once the 'Status' page is displayed in the web browser, click the 'Settings' tab.
  3. Unless you have previously configured a password for the device, leave the user name and password fields blank and click 'OK'.  If you have previously created a password for the monitor, leave the user name field blank and enter the current password, then click 'OK'.
  4. When the 'Settings' screen displays, click the 'Security' button on the left side list.
  5. In this screen, enter the old password, new password, and confirm the new password. (If an old password is not set, leave this field completely blank)
  6. Click the 'Accept Changes' button at the bottom of the screen, then click the 'Save Settings' button in the left side list to reboot the monitor. The monitor will  reboot, and now require a password only to access the 'Settings' section.
To Reset An Unknown Password That Was Previously Set

All current Room Alert and TemPageR monitors feature a hard reset button on the back of the case. While the monitor is powered on and connected to an active network or crossover cable connection, please locate and hold down this reset button while watching the top left green light on the monitor's network port. This network light will go out for two seconds, then reappear to signify a complete reset. The monitor will now have factory default settings, which includes a blank password set for the 'Settings' section. Note that the unit will be configured for DHCP and any static IP set previously will need to be reconfigured.

If the monitor does not have a physical reset button, please contact AVTECH Technical Support and speak with one of our Technical Specialists.  

To contact AVTECH support, click here.

How do I set a Static IP address on my Room Alert or TemPageR?

A Static IP address can be set for your Room Alert or TemPageR unit by using the AVTECH Device Discovery Utility, AVTECH Device ManageR, or via the 'Network' section in the 'Settings' tab of the Room Alert or TemPageR web browser interface.

To set a Static IP address using the AVTECH Device Discovery Utility, open the AVTECH Device Discovery Utility and click the 'Search' button. Select the monitor you wish to assign a static IP address to and click the 'Set IP' button. Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit being updated.

To set a Static IP address using the AVTECH Device ManageR Software, open the Device ManageR software and click the monitor in the left hand 'Device Status' list. You will notice a small drop down below the currently selected monitor. Click the '-Set IP Address' button.
Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit you are updating.

To set a Static IP address using the monitor's web browser interface, enter the current IP address of your Room Alert or TemPageR monitor into the location bar of a web browser. The 'Status' page will load by default and display the current sensor values. Click the 'Settings' tab at the top of the page and the 'Network' section will load. Uncheck the 'Use DHCP' checkbox and enter the desired static IP information in the available fields. Be sure that all static IP address information is correct for the location of the monitor you are updating. To complete the changes, please click the 'Accept Changes' button at the bottom of your page and then the 'Save Settings' button on the left hand side. The monitor will now reboot and apply the new changes.

If the Room Alert or TemPageR monitor cannot be discovered or you do not know the existing IP address, a Static IP address can be set using the MAC address of the unit, which can be found on a label on the bottom of the monitors. Please open Device Discovery and click the 'Set IP' button without selecting a device from the list and follow the prompts from the AVTECH Device Discovery Utility. Alternatively, you can set a Static IP address via the MAC address of your monitor in Device ManageR.
Open Device ManageR and click the 'Advanced Discovery' button in the top left hand corner on the 'Device Status' list. This button will display a pop up that will have a 'Set IP Via MAC Address' button. From here, enter the MAC address of the monitor and the desired Static IP address.When finished, press the 'Update IP Settings' button to make the changes.

How Do I Update The Firmware On My Room Alert Or TemPageR Monitor?

- Verify that you have either the AVTECH Device Discovery Utility or Device ManageR software installed on a host machine that has network visibility to the Room Alert or TemPageR monitor that is to be updated.
 - Verify that the software being used is the most current version of AVTECH Device Discovery or Device ManageR. The most current versions can be obtained via the 'Downloads' section of AVTECH.com for current MSUS subscribers.


Note which firmware version the Room Alert or TemPageR is currently running by checking the monitor's 'Status' page. The monitor's version will be in the top right hand corner.

Click here: http://avtech.com/Downloads/ and check the left side box for a list of AVTECH's released versions. If your current firmware version is older than the version listed here, please continue by logging in to the 'Downloads' section. (If you do not know your login password or if you are unsure if you  have an account, click the 'Forgot/Reset Password' link and enter your email address. If your email address is not recognized, click the 'Email Request/Inquiry' button and fill in your information. If your email address is recognized but you do not receive an email with your password, check any SPAM filter in place before contacting AVTECH Technical Support.)

Once in the downloads section, navigate to the monitor's section. Save the firmware update file but DO NOT unzip/decompress the file if it arrives as a .zip or .upd file.


DEVICE DISCOVERY UTILITY: Open Device Discovery and click the 'Search' button. 



Select the monitor that is to be updated and click the 'Update' button.

 


Follow the prompts to specify the location of the Firmware Update file for the monitor and click the 'Upload' button.

 



DEVICE MANAGER: Open Device ManageR and select the monitor from the Device Status list or click on the unit's information in the middle of the page.



Click the 'Update Firmware' button.



Click 'Browse'.



Select the appropriate file and click 'Open'.



Click the 'Update' button to begin the firmware update process.



When the firmware update process completes, the unit will automatically reboot to apply the update.
If you experience an issue during this process, please feel free to contact the Technical Support Team by submitting a support ticket.

How To Use The Trace Feature On A Room Alert Or TemPageR Device

The tracing feature is a very useful tool that can be used to assist in troubleshooting issues with your Room Alert or TemPageR device.

To enable tracing on your unit, follow these steps:

       1.   Access the 'Advanced' tab of the 'Settings' page.


  

       2.   In the 'Trace Configuration' section, ensure that the 'Enable Tracing' check box is checked. The tracing port is 143 by default. You do not need to change this unless you know port 143 will be blocked by your network for some reason. After making changes in this section, click the 'Accept Changes' button at the bottom of the screen, then the 'Save Settings' button on the left hand side of the screen.




To generate a trace from your device you will want to enter the following command into a Windows command prompt: 'telnet -f c:\tracefile.txt <IP of unit> <trace port #>' then press the <Enter> key. Where 'IP of unit' is the IP address of your Room Alert or TemPageR device and 'trace port #' is the configured trace port (143 by default). So the command might look something like this: 'telnet -f c:\tracefile.txt 192.168.33.100 143'. This command will capture your trace data directly to a text file named 'tracefile.txt' in the C: directory.

Please note that Windows 7 and Vista have disabled the Telnet client by default. If you get an error saying 'telnet is not recognized as an internal or external command, operable program or batch file' you will need to enable it by going to 'Start', 'Control Panel', 'Programs And Features', 'Turn Windows Features On Or Off' then checking the 'Telnet Client' row and clicking 'OK'.


At times, it may be useful or necessary for our engineers to review a trace from a Room Alert or TemPageR device and we may request you send us the results of a trace. If you are requested to send a trace in by one of our technical support specialists, or if you feel it will be helpful before being asked, simply attach the file created by the command given above to an email and send it to us at 'Support@AVTECH.com'.

One example of how to use the tracing feature is for troubleshooting email issues with your device. To troubleshoot email issues using the trace feature, launch the trace window using the process described above. Once you have successfully connected to the trace, browse to the 'SMTP Email' tab on the 'Settings' page. Try sending an email by clicking the 'Send Test Email' button at the bottom of the SMTP Email tab. You should see the attempts by the Room Alert or TemPageR device to connect to the configured mail server in the trace output window. If there are any issues occurring with the email process, you should see corresponding errors displayed in the output window which should point you in the right direction as to what might be causing any issue.

My Room Alert Or TemPageR Monitor Is Not Discoverable Or Accessible On My Network. How Do I Discover My Room Alert Or TemPageR?

Device ManageR and the Device Discovery Utility use a broadcast scan on UDP port 30718 to automatically locate AVTECH monitors on a network.
AVTECH recommends the following for initial product discovery:
 - DHCP Enabled on network.
 - UDP Broadcasts allowed at a computer and network level.
Please Note Before Beginning:
 - The network cable must be plugged in to the Room Alert or TemPageR monitor and the switch or computer before power is connected. This ensures that the initial DHCP request will be sent successfully when power is connected.

 - If the monitor has been assigned a static IP address that is invalid for the current IP address range of the network, please proceed to step 3 of this guide.
 - When the Room Alert or TemPageR monitor is powered on and plugged into a network, please check the current status of the Network Jack's lights as these lights are used to determine the current state of the monitor. The left link light should be a solid green color while the right light should be a flashing green or orange. If these lights display any other patterns than this, please skip to step 5 of this guide.

To begin discovering the monitor's IP address, please follow the instructions below starting at step 1.

1. Both Device ManageR and the Device Discovery Utility have a manual discovery feature that uses a TCP scan on TCP port 30718. This feature is helpful if the network range or specific IP address of the monitor is known. 

 - To access this feature using Device ManageR, click the 'Advanced Discovery Options...' button under 'Device Status' in the left menu. Click the 'Manually Add Device/s Via IP Address' button and select either 'Single IP Address' or 'Range Of IP Addresses'. Insert the desired IP address or range and click the 'Begin Scan...' button.

 

 - To access this feature using the Device Discovery Utility, click the 'Advanced Discovery' button located under the 'Search' button. Then, select either 'Single IP Address' or 'Range IP Addresses' and enter the single IP address or IP address range. Start the scan using the 'Begin Scan' button.


2. DHCP Enabled On Network – All AVTECH monitors are initially set to obtain an IP address automatically using DHCP. DHCP must be enabled on the network for the monitor to receive a valid IP address. If DHCP is not enabled, the monitor will default to an auto IP address in the 169.254.xxx.xxx range. At this IP address, the router or system firewalls may not allow discovery because the IP address is outside of the valid network IP range. Valid assignment could potentially be hindered by a managed switch even if DHCP is enabled. If DHCP assignment is delayed in the managed switch, the DHCP request sent from the monitor can timeout and default to a 169.254.xxx.xxx Auto IP address.

 - If DHCP is enabled on the network, there is a chance the DHCP server has already assigned a valid IP address even though the monitor is not discoverable. If the manual discovery option from step 1 does not discover the monitor, the IP address can sometimes be obtained by checking the DHCP server for the MAC address of the monitor.

 - If the IP address can be verified by checking the DHCP server and the IP address is in range of the network, it can be added to Device ManageR and the Device Discovery Utility using the manual scan feature from step 1. This IP address can additionally be accessed by directly by typing the IP address in a web browser. 

 - It is also possible to create a DHCP reserved IP address on a server. Doing this and recycling the power on the monitor should allow the IP address to be assigned by the DHCP server. If this process is unknown or unable to be completed personally, please consult the local Network Administrator. Otherwise, continue to the next step.

3. If the IP address of the monitor is still not discoverable, AVTECH recommends connecting the unit directly to a computer or laptop using a cross-over Ethernet cable or spare network hub.

 - Before disconnecting a computer or laptop to be used from the current network, be sure that the Device Discovery utility is installed along with a protocol analyzer (packet sniffer) application. If a preferred protocol analyzer application is unknown or not installed, a free utility called 'Wireshark' can be installed from http://www.wireshark.org/.

 - Begin by assigning a static IP address to the computer's network card, then connect the monitor via cross-over Ethernet cable or spare network hub to the computer. Lastly, plug in the power to the Room Alert or TemPageR monitor to begin the connection process. 

 - Attempt discovery using the Device Discovery utility by clicking the 'Set IP' button. The 'Set IP' button can set an IP via the MAC address which can be found at the bottom of any Room Alert or TemPageR monitor's case. Follow the procedure as prompted by Device Discovery and remember to set the IP to a valid IP address that is within the same subnet as the IP set for the computer's network card. After doing this, the monitor should be accessible via the Device Discovery list or by directly entering the newly set IP address in a web browser.

4. DHCP alternative to the static IP settings above: While still on the cross-over cable direct connection between the computer and monitor, the Room Alert or TemPageR may also be reset back to initial DHCP factory defaults via the reset button on the back panel of the monitor (if applicable). 

- For TemPageR3E, Room Alert 4E, 11E: Hold the reset button in for 10-15 seconds until the top left LED on the Ethernet jack blinks. A reset has occurred when this light on the ethernet jack goes out, then reappears 1 second later. Please release the reset button after this occurs.

 - For Room Alert 24E, 26W, 32E/W: Hold the reset button in for 10-15 seconds and watch the 3 main status lights on the front of the monitor. A reset has occurred as the front 3 status lights cycle through red and then finish cycling. Please release the reset button after this occurs.

 - With the unit now set back to DHCP factory defaults, change the laptop's network card settings to automatically obtain an IP address as opposed to specifying a static IP. Start up the Device Discovery utility and click 'Search' to locate the monitor.

 - If the Device Discovery utility methods are not working and the above steps have not located the monitor, start the protocol analyzer application, Begin packet capture and recycle the power on the monitor. Look for incoming packets coming from the MAC address of the monitor (located on a sticker on the bottom of the monitor's case or on the back of a rack mount kit if applicable). One of these packets should contain the source IP address of the monitor. Once this IP address has been obtained, configure a static IP address on the laptop or computer that is within a valid network range in relation to the IP address assigned to the unit as in step 3 (i.e. IP of unit: 192.168.2.3 - IP for computer or laptop: 192.168.2.4). The monitor can now be directly accessed by entering the IP address in a web browser.

5. If the above trials have been unsuccessful in discovering the IP address of the unit, please email Support@AVTECH.com with the packet capture obtained in step 4 attached to the email.

The Activity LED is flashing orange on my Room Alert unit and it does not appear on the network. How can I resolve this?

In the event that your Room Alert unit is inaccessible on your network, the Link LED (LED on left side of Ethernet port) on your unit is unlit and the Activity LED (LED on right side of Ethernet port) on your unit is flashing orange, please follow the instructions below to recover your unit.

  1. Verify that you have version 3.1.1 or later of the AVTECH Device Discovery Utility installed on a system with only 1 Ethernet Adapter.

  2. Obtain your unit's Firmware Update file from the download section for that specific model. Save it to your desktop and DO NOT unzip the Firmware Update file if it arrives as a .zip file.

  3. Disconnect the Ethernet cable from the system you are currently working on and use a crossover Ethernet cable to connect the system to the hardware unit.

  4. If your system does not have a static IP address set, temporarily configure it with a static IP address for the recovery process.

  5. Temporarily disable any firewalls or anti-virus programs that might block the firmware recovery packets.

  6. Reconnect the power to the hardware unit and start the AVTECH Device Discovery Utility.

  7. Click the 'OK' button on the dialog that appears and replace the 'XX-XX-XX' in the next dialog with the last three segments of the MAC address of your hardware unit. The MAC address of your hardware unit will be listed on a label located on the bottom of the hardware unit.

  8. Follow the instructions on the next dialog and recycle the power on your hardware unit.

  9. When the 'Open File' dialog opens, navigate to the location where you saved the Firmware Update file, select it and click the 'Upload' button.

  10. When the 'Set IP' dialog appears, enter a valid static IP address, gateway IP address, subnet mask and DNS server IP address in relation to the static IP settings you configured the system you are working on with.

  11. The IP address information you entered will be uploaded to your hardware unit and your hardware unit will be rebooted. Upon reboot, the full Firmware Update file will be uploaded to your hardware unit. If you initially had your unit set to DHCP before performing these steps, select your hardware unit in the AVTECH Device Discovery Utility, click the 'Set IP' button and enter '0.0.0.0' in the 'Set IP' dialog. Click 'OK' and wait for your unit to reboot. If a static IP address, gateway IP address, subnet mask and DNS server IP address were originally assigned to your hardware unit, select your unit in the AVTECH Device Discovery Utility and click the 'Set IP' button. Enter the original static IP address, gateway IP address, subnet mask and DNS server IP address assigned to the hardware unit. Click 'OK' and wait for your unit to reboot.

  12. Unplug your hardware unit and disconnect the crossover Ethernet cable.

  13. Install your unit in it's previous location by plugging in the Ethernet cable first and then powering on the hardware unit.

If you experience an issue during this process, please feel free to contact our technical support department by submitting a support ticket.

Trouble/Issues Accessing the 'Downloads' Section of AVTECH.com

The 'Downloads' section on AVTECH.com is AVTECH's only source of Device ManageR, Room Alert/TemPageR firmware updates, Software updates, MIB files, Device ManageR plugins, and the Device Discovery utility. To gain access to this section, AVTECH will issue a username and password to all contacts that are employed by organizations that have purchased a Room Alert or TemPageR environmental monitor.

If you have been previously issued a username and password from AVTECH: When attempting to log on to the AVTECH Downloads section, make sure that the password being used is entered correctly as the password is case sensitive. Please note the email address that was initially given to AVTECH at the time of registration is the only email that can be used to log on to this section.

If the initial password for the 'Downloads' section of AVTECH.com has been lost or forgotten, go to AVTECH.com/Downloads/ and select the 'Forgot/Reset Password' link below the login section. Enter the registered email address in the new screen and select 'Submit'. If the email address matches a record that was previously created in AVTECH's registry, an email will be sent with the required password.

If you are able to access AVTECH's downloads, but your downloads are expired: The specific downloads provided to your organization are regulated by AVTECH's Maintenance, Support, and Update Service (MSUS). MSUS is an annually renewed service for each of the Room Alert and TemPageR units owned by the organization. If MSUS needs to be renewed, please send an email to RenewMSUS@AVTECH.com including the organization's name and your personal contact information. For more information on MSUS, please refer to this page link:  http://www.AVTECH.com/PDFs/AVTECH_MSUS_Explained.pdf 

If you are a new contractor or temporary hire and require access to AVTECH Downloads: Please provide the following information in an email to 'Support@AVTECH.com' along with a short message explaining the need for access. Once approved, you will be registered as a contractor or temporary hire directly under the organization that owns the Room Alert or TempageR product. Please include the following information in this email:

Organization Name
Organization Address
Organization Phone Number
Your Full Name
Direct Phone Number
Email Address
Job Title
Summary Of Work To Be Completed

For all other issues accessing the 'Downloads' section of AVTECH.com, send an email to 'Support@AVTECH.com' and we will be able to provide further assistance.


Status Screen

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.



Settings Screen

I am unable to get my Room Alert or TemPageR monitor to send email alerts properly. How do I send email alerts directly from the monitor's web page?

Email alerts from the Room Alert or TemPageR monitors are sent using anonymous, unauthenticated SMTP email on TCP port 25. If email notifications are not received, first verify the email settings in the 'SMTP Email' section of the 'Settings' page.
  1. Mail Server Port: This port is typically port 25 but can be different based on personal mail server settings and network preferences. Please check with the mail server administrator for the exact port number.
  2. Mail Server: If the monitor is configured to obtain an IP address using DHCP, enter the specific IP address of the mail server in the ‘Mail Server Address’ field. If the monitor is configured with a static IP address, the DNS name for the mail server can be entered in this field. For initial testing purposes, enter an email address from the same domain as the mail server in the ‘Email Recipients’ field. For example, if the domain name is 'Example.com', be sure the email used to test is from the same domain (i.e. YourEmail@Example.com).
  3. Return Address: To finish the configuration, enter the same email address in the ‘Return Address (From)’ field. Using the same domain name minimizes the risk that security settings on the email server would prevent the message from being delivered.
  4. Display URL: The display URL is a URL that will be at the bottom of your received email alert. This URL is here to allow quick link/access to any URL after an alert is triggered. This URL can be a link to any web page you would like, but typically we assume that quick access to your Room Alert's web page is necessary here. Type in the IP address of the monitor or any other web page that is desired in this field.
  5. Authentication: This field is optional because not all mail servers require authentication. Please check with the mail server administrator if there are any questions about this field. The Username and Password would typically be the same credentials used to log on to a mail server directly.
  6. Email Recipients: List the email addresses that the alert will be sent to and separate multiple addresses by a comma. For example, John@Example.com,James@Example.com,Steve@Example.com Please note that due to limited flash memory on the Room Alert and TemPageR monitors, the Email Recipients field is only 79 characters long. For more space, AVTECH recommends creating a distribution list in the email server itself or for unlimited email entries and advanced/custom alerting, please follow this link for AVTECH Device ManageR: http://avtech.com/Products/Device_ManageR/


     Once the email settings are configured, click the ‘Test Email’ button and check the email account(s) for the test email. If the message is not received, first check any spam filter that may be in place. If the test email cannot be found, it could be blocked by the mail server. Be sure the mail server is configured to allow 'SMTP Relaying' from the IP address of the monitor. Also, be sure the Room Alert or TemPageR is on the email server's 'whitelist' to prevent messages from being filtered or blocked as spam. If messages from the monitor continue to be blocked by the mail server, contact the mail server administrator to see if the mail server logs can be reviewed to determine why the messages are being blocked.

If you have followed the steps above but are still unable to receive email alerts, please contact our Technical Support Team by
submitting a support ticket.

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.


What is the Default 'Settings' Screen Password on Room Alert or TemPageR?

The 'Settings' screen of Room Alert and TemPageR is password protected to prevent unauthorized users from modifying the settings. By default, there is no user name and password configured to access the 'Settings' screen of a Room Alert or TemPageR. With the User Name and Password fields left blank, select 'OK' to access the 'Settings' screen.

If you have previously configured a password for the device, leave the User Name field blank and enter your password in the 'Password' field, then select 'OK' to access the 'Settings' screen.

When I try to access the 'Settings' screen on my Room Alert or TemPageR, my web page flashes or does not load properly. How do I access the 'Settings' screen?

The 'Settings' screen on the Room Alert and TemPageR units consist of a Java applet that accesses the device on UDP port 30718 and 30719. To view the 'Settings' applet, Java software must be installed in the browser being used to access the web interface. Java software can be installed at Java.com. Next, verify that you do not have UDP port 30718 and 30719 blocked on any device located between the system or server you are currently using and your unit. If this is the case, unblock the port and try accessing the 'Settings' screen again.

The 'Settings' screen consists of an HTML form that submits and retrieves data using Java script and normal http 'get' and 'post' requests. When the 'Settings' screen flashes or doesn't load properly, we have noticed that a typical cause would be certain security devices such as Microsoft's ISA proxy server or antivirus programs that are implemented on your network. If you can, please check your network and see if any of these items are in fact implemented and are interfering with communications. In order for the 'Settings' tab to open, our program runs certain commands and pages in the background which conflict with some antivirus program's or Internet Security Server's configured settings.

You can attempt to check these pages by trying the following two addresses   http://<IP of unit>/secure/setuprec.xml  and  http://<IP of unit>/secure/unitinfo.xml  Once you have called upon them, please right click and 'view source' on them. If you notice anything strange here or are receiving an error message we would appreciate seeing them for reference. You can  take screen shots or make a text copy of the contents and send them to us here at Support@AVTECH.com

To resolve this issue, typically we see that a proxy server or antivirus is blocking background XML HTTP requests. A typical fix is to allow or add exceptions to the Room Alert Or TemPageR IP address in all security implementations.

If you are still having difficulty, please follow the steps below and attempt to access the 'Settings' screen after completing each one.

  1. Completely close the web browser you are using and reload. If you have any alternate web browsers, please attempt to access the settings page with these browsers as well.

  2. Recycle the power on your unit.

  3. Reupload/update the firmware on your Room Alert or TemPageR unit. For complete instructions on doing so, please follow this link:  http://avtech.com/Support/index.php?action=kb&article=40

If steps 1-3 do not resolve the issue, we suggest disconnecting your device from your network and attempt to connect to it via a laptop and Device Discovery through a crossover cable. When using a cross over cable, you should plug the crossover cable in to the device and the PC first, then plug in the power to the unit. Remember to set up your laptop's network card to be within the same subnet range as your Room Alert and TemPageR unit, then attempt to discover your unit with the Device Discovery Unit. For more information on discovering your unit, please follow this link. http://AVTECH.com/Support/index.php?action=kb&article=73 If you have discovered your unit and are able to access your unit's 'Settings' page, this means that one of the previous topics discussed is most likely still an issue on your network. If you have successfully connected via a crossover cable and are still unable to properly access the settings page, please feel free to contact our technical support staff by submitting a support ticket.


Sensors

Can I add additional sensors to my Room Alert or TemPageR after my initial order?

Yes. Many environmental sensors are available for purchase at any time from AVTECH such as temperature, humidity, power, flood, smoke, motion, room entry and many more. A list of these sensors can be found here: http://avtech.com/Products/Monitor_-_Sensors/ For additional information and purchasing of our environmental sensors, please contact an AVTECH Senior Product Specialist at 888.220.6700.

External Digital Temperature and Humidity Sensor Placement Suggestions

Placing Digital Temperature Sensors in the right locations is essential for reliable monitoring of the environment. Without proper placement, the most relevant temperature data may not be obtained.

 - It is recommended that the Room Alert or TemPageR unit itself is placed near the equipment that you wish to monitor as the standard cable length for Digital Temperature Sensors is 25 feet. External digital sensors may be extended up to 100 feet in length with the use of cable extensions found here: http://avtech.com/Products/Monitor_-_Accessories/Extended_Cable_Coupler.htm.

 - Measuring the temperature of the aisles in the data center at multiple height levels can give an early indication of a potential temperature problem. For consistent and reliable temperature monitoring, place a temperature sensor at least every 25 feet in each aisle with sensors placed closer together if high temperature equipment like blade servers are in use. It is important to know that data center temperatures can drastically vary in nearby locations depending on height from the floor, the specific equipment that is present, and how much equipment is present.

 - AVTECH recommends installing TemPageR and Room Alert rack units at the top of each rack in the data center as the heat generated by the components in the rack rises up to the unit which will give the most accurate readings, TemPageR and Room Alert units will be able to provide an early warning and notify staff for temperature issues before critical systems, servers or network equipment is damaged. You may wish to consider purchasing additional AVTECH devices and sensors to maximize the area that can be monitored.

 - In addition, avoid locating your sensor cables near large electromagnetic devices and florescent lights.

 - Place your sensor cables so that they are located in a safe place away from frequent foot traffic or constant disruption from moving parts.

Click here to review an article entitled Recommended Computer Room Temperature and Humidity. For additional information, please visit ASHRAE (the American Society of Heating, Refrigerating, and Air-Conditioning Engineers) to view a document called "Thermal Guidelines for Data Processing Environments" to assist you in planning how to best place your Digital Temperature Sensors in your organization's environment.

How do I extend my Digital Sensor Cable longer than the supplied 25 feet?

By design, external digital sensor cables are 25 feet in length and can be extended up to a supported100 feet in total length.

To extend the sensor cable, you will need a RJ-11 cable with coupler which is available from AVTECH Software.

To order these cables, contact your Product Specialist or click here to purchase on-line.

To extend an external digital sensor cable:

  1. Remove the external digital sensor to be extended by unplugging its RJ-11 cable from the front of the unit.
  2. Using a 25 foot RJ-11 cable with coupler, insert the RJ-11 connector into the AVTECH unit’s external sensor port.
  3. Plug the RJ-11 connector on the sensor cable to the extension cable.

If you wish to extend the sensor up to the supported 100 feet in length, multiple RJ-11 extension cables can be connected using the methods above.

It is important to note that AVTECH does not recommend extending a cable to a greater distance than 100 feet and does not support splicing or cutting into existing wires to shorten or lengthen the provided cable.



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.

Temperature Conversion Formulas

[F = Fahrenheit, C = Celsius]


To Convert Celsius To Fahrenheit

F = 1.8C + 32


To Convert Fahrenheit To Celsius

C = F – 32
          1.8

Why is the internal temperature reading on my Room Alert or TemPageR monitor higher than the external sensors?

The internal temperature sensor measures the ambient air temperature inside the Room Alert or TemPageR device. Under normal operating conditions, the device can generate some heat internally that can cause the internal sensor to register a temperature that is a few degrees higher than the external sensors. This is normal and especially holds true for any rack mounted monitors, as the temperature inside of a rack is typically warmer than the surrounding environment where the external temperature sensors are located. All sensor readings, including internal sensors, can be calibrated using the 'Settings' page of the monitor's firmware.

Click the 'Settings' link and go to the 'Sensors' tab. If desired, enter a integer value in the 'Adjust' field to calibrate the internal sensor reading to match the readings from the external sensors. For example, if the internal temperature is two (2) degrees higher than the external sensor, put a '-2' in the 'Adjust' field for Sensor 1.

If your Adjust field value seems to be different than what you initially saved it as, it is most likely due to the conversion from Celsius to Fahrenheit. For more information, please follow this link: http://AVTECH.com/Support/index.php?action=kb&article=119

If you have any further questions, please feel free to contact our Technical Support Team by submitting a support ticket.

Room Alert 32

Can I log sensor data on my Room Alert or TemPageR?

     AVTECH's Device ManageR software can log all sensor data for each and every Room Alert and TemPageR monitor connected to a network. Device ManageR runs as a Windows Service and uses the host system's hard drive to store logs in an SQL database. Device ManageR is available for free to all customers who have purchased a Room Alert or TemPageR monitor and have current Maintenance, Support, and Update Service (MSUS) with AVTECH. Device ManageR's logging is a standard feature along with graphing, unlimited/custom alerts, and much more. Device ManageR can be downloaded from the Downloads section at http://AVTECH.com/Downloads/ For more information on Device ManageR, please follow this link: http://AVTECH.com/Products/Device_ManageR/

How Do I Update The Firmware On My Room Alert Or TemPageR Monitor?

- Verify that you have either the AVTECH Device Discovery Utility or Device ManageR software installed on a host machine that has network visibility to the Room Alert or TemPageR monitor that is to be updated.
 - Verify that the software being used is the most current version of AVTECH Device Discovery or Device ManageR. The most current versions can be obtained via the 'Downloads' section of AVTECH.com for current MSUS subscribers.


Note which firmware version the Room Alert or TemPageR is currently running by checking the monitor's 'Status' page. The monitor's version will be in the top right hand corner.

Click here: http://avtech.com/Downloads/ and check the left side box for a list of AVTECH's released versions. If your current firmware version is older than the version listed here, please continue by logging in to the 'Downloads' section. (If you do not know your login password or if you are unsure if you  have an account, click the 'Forgot/Reset Password' link and enter your email address. If your email address is not recognized, click the 'Email Request/Inquiry' button and fill in your information. If your email address is recognized but you do not receive an email with your password, check any SPAM filter in place before contacting AVTECH Technical Support.)

Once in the downloads section, navigate to the monitor's section. Save the firmware update file but DO NOT unzip/decompress the file if it arrives as a .zip or .upd file.


DEVICE DISCOVERY UTILITY: Open Device Discovery and click the 'Search' button. 



Select the monitor that is to be updated and click the 'Update' button.

 


Follow the prompts to specify the location of the Firmware Update file for the monitor and click the 'Upload' button.

 



DEVICE MANAGER: Open Device ManageR and select the monitor from the Device Status list or click on the unit's information in the middle of the page.



Click the 'Update Firmware' button.



Click 'Browse'.



Select the appropriate file and click 'Open'.



Click the 'Update' button to begin the firmware update process.



When the firmware update process completes, the unit will automatically reboot to apply the update.
If you experience an issue during this process, please feel free to contact the Technical Support Team by submitting a support ticket.

Initial Discovery & Setup

How Do I Enable A Security Password On Room Alert Or TemPageR Monitors?

A password can be configured for each individual Room Alert or TemPageR to prevent unauthorized users from modifying the 'Settings' section.  Passwords should be alphanumeric and cannot include special characters or symbols.

To Configure A Password For Room Alert or TemPageR
  1. Type the IP Address of the monitor into a web browser to access the 'Status' page. (For Device ManageR, click the monitor in the 'Device Status' list, then select 'Open Web')
  2. Once the 'Status' page is displayed in the web browser, click the 'Settings' tab.
  3. Unless you have previously configured a password for the device, leave the user name and password fields blank and click 'OK'.  If you have previously created a password for the monitor, leave the user name field blank and enter the current password, then click 'OK'.
  4. When the 'Settings' screen displays, click the 'Security' button on the left side list.
  5. In this screen, enter the old password, new password, and confirm the new password. (If an old password is not set, leave this field completely blank)
  6. Click the 'Accept Changes' button at the bottom of the screen, then click the 'Save Settings' button in the left side list to reboot the monitor. The monitor will  reboot, and now require a password only to access the 'Settings' section.
To Reset An Unknown Password That Was Previously Set

All current Room Alert and TemPageR monitors feature a hard reset button on the back of the case. While the monitor is powered on and connected to an active network or crossover cable connection, please locate and hold down this reset button while watching the top left green light on the monitor's network port. This network light will go out for two seconds, then reappear to signify a complete reset. The monitor will now have factory default settings, which includes a blank password set for the 'Settings' section. Note that the unit will be configured for DHCP and any static IP set previously will need to be reconfigured.

If the monitor does not have a physical reset button, please contact AVTECH Technical Support and speak with one of our Technical Specialists.  

To contact AVTECH support, click here.

How do I set a Static IP address on my Room Alert or TemPageR?

A Static IP address can be set for your Room Alert or TemPageR unit by using the AVTECH Device Discovery Utility, AVTECH Device ManageR, or via the 'Network' section in the 'Settings' tab of the Room Alert or TemPageR web browser interface.

To set a Static IP address using the AVTECH Device Discovery Utility, open the AVTECH Device Discovery Utility and click the 'Search' button. Select the monitor you wish to assign a static IP address to and click the 'Set IP' button. Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit being updated.

To set a Static IP address using the AVTECH Device ManageR Software, open the Device ManageR software and click the monitor in the left hand 'Device Status' list. You will notice a small drop down below the currently selected monitor. Click the '-Set IP Address' button.
Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit you are updating.

To set a Static IP address using the monitor's web browser interface, enter the current IP address of your Room Alert or TemPageR monitor into the location bar of a web browser. The 'Status' page will load by default and display the current sensor values. Click the 'Settings' tab at the top of the page and the 'Network' section will load. Uncheck the 'Use DHCP' checkbox and enter the desired static IP information in the available fields. Be sure that all static IP address information is correct for the location of the monitor you are updating. To complete the changes, please click the 'Accept Changes' button at the bottom of your page and then the 'Save Settings' button on the left hand side. The monitor will now reboot and apply the new changes.

If the Room Alert or TemPageR monitor cannot be discovered or you do not know the existing IP address, a Static IP address can be set using the MAC address of the unit, which can be found on a label on the bottom of the monitors. Please open Device Discovery and click the 'Set IP' button without selecting a device from the list and follow the prompts from the AVTECH Device Discovery Utility. Alternatively, you can set a Static IP address via the MAC address of your monitor in Device ManageR.
Open Device ManageR and click the 'Advanced Discovery' button in the top left hand corner on the 'Device Status' list. This button will display a pop up that will have a 'Set IP Via MAC Address' button. From here, enter the MAC address of the monitor and the desired Static IP address.When finished, press the 'Update IP Settings' button to make the changes.

How Do I Update The Firmware On My Room Alert Or TemPageR Monitor?

- Verify that you have either the AVTECH Device Discovery Utility or Device ManageR software installed on a host machine that has network visibility to the Room Alert or TemPageR monitor that is to be updated.
 - Verify that the software being used is the most current version of AVTECH Device Discovery or Device ManageR. The most current versions can be obtained via the 'Downloads' section of AVTECH.com for current MSUS subscribers.


Note which firmware version the Room Alert or TemPageR is currently running by checking the monitor's 'Status' page. The monitor's version will be in the top right hand corner.

Click here: http://avtech.com/Downloads/ and check the left side box for a list of AVTECH's released versions. If your current firmware version is older than the version listed here, please continue by logging in to the 'Downloads' section. (If you do not know your login password or if you are unsure if you  have an account, click the 'Forgot/Reset Password' link and enter your email address. If your email address is not recognized, click the 'Email Request/Inquiry' button and fill in your information. If your email address is recognized but you do not receive an email with your password, check any SPAM filter in place before contacting AVTECH Technical Support.)

Once in the downloads section, navigate to the monitor's section. Save the firmware update file but DO NOT unzip/decompress the file if it arrives as a .zip or .upd file.


DEVICE DISCOVERY UTILITY: Open Device Discovery and click the 'Search' button. 



Select the monitor that is to be updated and click the 'Update' button.

 


Follow the prompts to specify the location of the Firmware Update file for the monitor and click the 'Upload' button.

 



DEVICE MANAGER: Open Device ManageR and select the monitor from the Device Status list or click on the unit's information in the middle of the page.



Click the 'Update Firmware' button.



Click 'Browse'.



Select the appropriate file and click 'Open'.



Click the 'Update' button to begin the firmware update process.



When the firmware update process completes, the unit will automatically reboot to apply the update.
If you experience an issue during this process, please feel free to contact the Technical Support Team by submitting a support ticket.

My Room Alert Or TemPageR Monitor Is Not Discoverable Or Accessible On My Network. How Do I Discover My Room Alert Or TemPageR?

Device ManageR and the Device Discovery Utility use a broadcast scan on UDP port 30718 to automatically locate AVTECH monitors on a network.
AVTECH recommends the following for initial product discovery:
 - DHCP Enabled on network.
 - UDP Broadcasts allowed at a computer and network level.
Please Note Before Beginning:
 - The network cable must be plugged in to the Room Alert or TemPageR monitor and the switch or computer before power is connected. This ensures that the initial DHCP request will be sent successfully when power is connected.

 - If the monitor has been assigned a static IP address that is invalid for the current IP address range of the network, please proceed to step 3 of this guide.
 - When the Room Alert or TemPageR monitor is powered on and plugged into a network, please check the current status of the Network Jack's lights as these lights are used to determine the current state of the monitor. The left link light should be a solid green color while the right light should be a flashing green or orange. If these lights display any other patterns than this, please skip to step 5 of this guide.

To begin discovering the monitor's IP address, please follow the instructions below starting at step 1.

1. Both Device ManageR and the Device Discovery Utility have a manual discovery feature that uses a TCP scan on TCP port 30718. This feature is helpful if the network range or specific IP address of the monitor is known. 

 - To access this feature using Device ManageR, click the 'Advanced Discovery Options...' button under 'Device Status' in the left menu. Click the 'Manually Add Device/s Via IP Address' button and select either 'Single IP Address' or 'Range Of IP Addresses'. Insert the desired IP address or range and click the 'Begin Scan...' button.

 

 - To access this feature using the Device Discovery Utility, click the 'Advanced Discovery' button located under the 'Search' button. Then, select either 'Single IP Address' or 'Range IP Addresses' and enter the single IP address or IP address range. Start the scan using the 'Begin Scan' button.


2. DHCP Enabled On Network – All AVTECH monitors are initially set to obtain an IP address automatically using DHCP. DHCP must be enabled on the network for the monitor to receive a valid IP address. If DHCP is not enabled, the monitor will default to an auto IP address in the 169.254.xxx.xxx range. At this IP address, the router or system firewalls may not allow discovery because the IP address is outside of the valid network IP range. Valid assignment could potentially be hindered by a managed switch even if DHCP is enabled. If DHCP assignment is delayed in the managed switch, the DHCP request sent from the monitor can timeout and default to a 169.254.xxx.xxx Auto IP address.

 - If DHCP is enabled on the network, there is a chance the DHCP server has already assigned a valid IP address even though the monitor is not discoverable. If the manual discovery option from step 1 does not discover the monitor, the IP address can sometimes be obtained by checking the DHCP server for the MAC address of the monitor.

 - If the IP address can be verified by checking the DHCP server and the IP address is in range of the network, it can be added to Device ManageR and the Device Discovery Utility using the manual scan feature from step 1. This IP address can additionally be accessed by directly by typing the IP address in a web browser. 

 - It is also possible to create a DHCP reserved IP address on a server. Doing this and recycling the power on the monitor should allow the IP address to be assigned by the DHCP server. If this process is unknown or unable to be completed personally, please consult the local Network Administrator. Otherwise, continue to the next step.

3. If the IP address of the monitor is still not discoverable, AVTECH recommends connecting the unit directly to a computer or laptop using a cross-over Ethernet cable or spare network hub.

 - Before disconnecting a computer or laptop to be used from the current network, be sure that the Device Discovery utility is installed along with a protocol analyzer (packet sniffer) application. If a preferred protocol analyzer application is unknown or not installed, a free utility called 'Wireshark' can be installed from http://www.wireshark.org/.

 - Begin by assigning a static IP address to the computer's network card, then connect the monitor via cross-over Ethernet cable or spare network hub to the computer. Lastly, plug in the power to the Room Alert or TemPageR monitor to begin the connection process. 

 - Attempt discovery using the Device Discovery utility by clicking the 'Set IP' button. The 'Set IP' button can set an IP via the MAC address which can be found at the bottom of any Room Alert or TemPageR monitor's case. Follow the procedure as prompted by Device Discovery and remember to set the IP to a valid IP address that is within the same subnet as the IP set for the computer's network card. After doing this, the monitor should be accessible via the Device Discovery list or by directly entering the newly set IP address in a web browser.

4. DHCP alternative to the static IP settings above: While still on the cross-over cable direct connection between the computer and monitor, the Room Alert or TemPageR may also be reset back to initial DHCP factory defaults via the reset button on the back panel of the monitor (if applicable). 

- For TemPageR3E, Room Alert 4E, 11E: Hold the reset button in for 10-15 seconds until the top left LED on the Ethernet jack blinks. A reset has occurred when this light on the ethernet jack goes out, then reappears 1 second later. Please release the reset button after this occurs.

 - For Room Alert 24E, 26W, 32E/W: Hold the reset button in for 10-15 seconds and watch the 3 main status lights on the front of the monitor. A reset has occurred as the front 3 status lights cycle through red and then finish cycling. Please release the reset button after this occurs.

 - With the unit now set back to DHCP factory defaults, change the laptop's network card settings to automatically obtain an IP address as opposed to specifying a static IP. Start up the Device Discovery utility and click 'Search' to locate the monitor.

 - If the Device Discovery utility methods are not working and the above steps have not located the monitor, start the protocol analyzer application, Begin packet capture and recycle the power on the monitor. Look for incoming packets coming from the MAC address of the monitor (located on a sticker on the bottom of the monitor's case or on the back of a rack mount kit if applicable). One of these packets should contain the source IP address of the monitor. Once this IP address has been obtained, configure a static IP address on the laptop or computer that is within a valid network range in relation to the IP address assigned to the unit as in step 3 (i.e. IP of unit: 192.168.2.3 - IP for computer or laptop: 192.168.2.4). The monitor can now be directly accessed by entering the IP address in a web browser.

5. If the above trials have been unsuccessful in discovering the IP address of the unit, please email Support@AVTECH.com with the packet capture obtained in step 4 attached to the email.

Trouble/Issues Accessing the 'Downloads' Section of AVTECH.com

The 'Downloads' section on AVTECH.com is AVTECH's only source of Device ManageR, Room Alert/TemPageR firmware updates, Software updates, MIB files, Device ManageR plugins, and the Device Discovery utility. To gain access to this section, AVTECH will issue a username and password to all contacts that are employed by organizations that have purchased a Room Alert or TemPageR environmental monitor.

If you have been previously issued a username and password from AVTECH: When attempting to log on to the AVTECH Downloads section, make sure that the password being used is entered correctly as the password is case sensitive. Please note the email address that was initially given to AVTECH at the time of registration is the only email that can be used to log on to this section.

If the initial password for the 'Downloads' section of AVTECH.com has been lost or forgotten, go to AVTECH.com/Downloads/ and select the 'Forgot/Reset Password' link below the login section. Enter the registered email address in the new screen and select 'Submit'. If the email address matches a record that was previously created in AVTECH's registry, an email will be sent with the required password.

If you are able to access AVTECH's downloads, but your downloads are expired: The specific downloads provided to your organization are regulated by AVTECH's Maintenance, Support, and Update Service (MSUS). MSUS is an annually renewed service for each of the Room Alert and TemPageR units owned by the organization. If MSUS needs to be renewed, please send an email to RenewMSUS@AVTECH.com including the organization's name and your personal contact information. For more information on MSUS, please refer to this page link:  http://www.AVTECH.com/PDFs/AVTECH_MSUS_Explained.pdf 

If you are a new contractor or temporary hire and require access to AVTECH Downloads: Please provide the following information in an email to 'Support@AVTECH.com' along with a short message explaining the need for access. Once approved, you will be registered as a contractor or temporary hire directly under the organization that owns the Room Alert or TempageR product. Please include the following information in this email:

Organization Name
Organization Address
Organization Phone Number
Your Full Name
Direct Phone Number
Email Address
Job Title
Summary Of Work To Be Completed

For all other issues accessing the 'Downloads' section of AVTECH.com, send an email to 'Support@AVTECH.com' and we will be able to provide further assistance.


Status Screen

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.



Settings Screen

I am unable to get my Room Alert or TemPageR monitor to send email alerts properly. How do I send email alerts directly from the monitor's web page?

Email alerts from the Room Alert or TemPageR monitors are sent using anonymous, unauthenticated SMTP email on TCP port 25. If email notifications are not received, first verify the email settings in the 'SMTP Email' section of the 'Settings' page.
  1. Mail Server Port: This port is typically port 25 but can be different based on personal mail server settings and network preferences. Please check with the mail server administrator for the exact port number.
  2. Mail Server: If the monitor is configured to obtain an IP address using DHCP, enter the specific IP address of the mail server in the ‘Mail Server Address’ field. If the monitor is configured with a static IP address, the DNS name for the mail server can be entered in this field. For initial testing purposes, enter an email address from the same domain as the mail server in the ‘Email Recipients’ field. For example, if the domain name is 'Example.com', be sure the email used to test is from the same domain (i.e. YourEmail@Example.com).
  3. Return Address: To finish the configuration, enter the same email address in the ‘Return Address (From)’ field. Using the same domain name minimizes the risk that security settings on the email server would prevent the message from being delivered.
  4. Display URL: The display URL is a URL that will be at the bottom of your received email alert. This URL is here to allow quick link/access to any URL after an alert is triggered. This URL can be a link to any web page you would like, but typically we assume that quick access to your Room Alert's web page is necessary here. Type in the IP address of the monitor or any other web page that is desired in this field.
  5. Authentication: This field is optional because not all mail servers require authentication. Please check with the mail server administrator if there are any questions about this field. The Username and Password would typically be the same credentials used to log on to a mail server directly.
  6. Email Recipients: List the email addresses that the alert will be sent to and separate multiple addresses by a comma. For example, John@Example.com,James@Example.com,Steve@Example.com Please note that due to limited flash memory on the Room Alert and TemPageR monitors, the Email Recipients field is only 79 characters long. For more space, AVTECH recommends creating a distribution list in the email server itself or for unlimited email entries and advanced/custom alerting, please follow this link for AVTECH Device ManageR: http://avtech.com/Products/Device_ManageR/


     Once the email settings are configured, click the ‘Test Email’ button and check the email account(s) for the test email. If the message is not received, first check any spam filter that may be in place. If the test email cannot be found, it could be blocked by the mail server. Be sure the mail server is configured to allow 'SMTP Relaying' from the IP address of the monitor. Also, be sure the Room Alert or TemPageR is on the email server's 'whitelist' to prevent messages from being filtered or blocked as spam. If messages from the monitor continue to be blocked by the mail server, contact the mail server administrator to see if the mail server logs can be reviewed to determine why the messages are being blocked.

If you have followed the steps above but are still unable to receive email alerts, please contact our Technical Support Team by
submitting a support ticket.

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.


What is the Default 'Settings' Screen Password on Room Alert or TemPageR?

The 'Settings' screen of Room Alert and TemPageR is password protected to prevent unauthorized users from modifying the settings. By default, there is no user name and password configured to access the 'Settings' screen of a Room Alert or TemPageR. With the User Name and Password fields left blank, select 'OK' to access the 'Settings' screen.

If you have previously configured a password for the device, leave the User Name field blank and enter your password in the 'Password' field, then select 'OK' to access the 'Settings' screen.

When I try to access the 'Settings' screen on my Room Alert or TemPageR, my web page flashes or does not load properly. How do I access the 'Settings' screen?

The 'Settings' screen on the Room Alert and TemPageR units consist of a Java applet that accesses the device on UDP port 30718 and 30719. To view the 'Settings' applet, Java software must be installed in the browser being used to access the web interface. Java software can be installed at Java.com. Next, verify that you do not have UDP port 30718 and 30719 blocked on any device located between the system or server you are currently using and your unit. If this is the case, unblock the port and try accessing the 'Settings' screen again.

The 'Settings' screen consists of an HTML form that submits and retrieves data using Java script and normal http 'get' and 'post' requests. When the 'Settings' screen flashes or doesn't load properly, we have noticed that a typical cause would be certain security devices such as Microsoft's ISA proxy server or antivirus programs that are implemented on your network. If you can, please check your network and see if any of these items are in fact implemented and are interfering with communications. In order for the 'Settings' tab to open, our program runs certain commands and pages in the background which conflict with some antivirus program's or Internet Security Server's configured settings.

You can attempt to check these pages by trying the following two addresses   http://<IP of unit>/secure/setuprec.xml  and  http://<IP of unit>/secure/unitinfo.xml  Once you have called upon them, please right click and 'view source' on them. If you notice anything strange here or are receiving an error message we would appreciate seeing them for reference. You can  take screen shots or make a text copy of the contents and send them to us here at Support@AVTECH.com

To resolve this issue, typically we see that a proxy server or antivirus is blocking background XML HTTP requests. A typical fix is to allow or add exceptions to the Room Alert Or TemPageR IP address in all security implementations.

If you are still having difficulty, please follow the steps below and attempt to access the 'Settings' screen after completing each one.

  1. Completely close the web browser you are using and reload. If you have any alternate web browsers, please attempt to access the settings page with these browsers as well.

  2. Recycle the power on your unit.

  3. Reupload/update the firmware on your Room Alert or TemPageR unit. For complete instructions on doing so, please follow this link:  http://avtech.com/Support/index.php?action=kb&article=40

If steps 1-3 do not resolve the issue, we suggest disconnecting your device from your network and attempt to connect to it via a laptop and Device Discovery through a crossover cable. When using a cross over cable, you should plug the crossover cable in to the device and the PC first, then plug in the power to the unit. Remember to set up your laptop's network card to be within the same subnet range as your Room Alert and TemPageR unit, then attempt to discover your unit with the Device Discovery Unit. For more information on discovering your unit, please follow this link. http://AVTECH.com/Support/index.php?action=kb&article=73 If you have discovered your unit and are able to access your unit's 'Settings' page, this means that one of the previous topics discussed is most likely still an issue on your network. If you have successfully connected via a crossover cable and are still unable to properly access the settings page, please feel free to contact our technical support staff by submitting a support ticket.


Sensors

External Digital Temperature and Humidity Sensor Placement Suggestions

Placing Digital Temperature Sensors in the right locations is essential for reliable monitoring of the environment. Without proper placement, the most relevant temperature data may not be obtained.

 - It is recommended that the Room Alert or TemPageR unit itself is placed near the equipment that you wish to monitor as the standard cable length for Digital Temperature Sensors is 25 feet. External digital sensors may be extended up to 100 feet in length with the use of cable extensions found here: http://avtech.com/Products/Monitor_-_Accessories/Extended_Cable_Coupler.htm.

 - Measuring the temperature of the aisles in the data center at multiple height levels can give an early indication of a potential temperature problem. For consistent and reliable temperature monitoring, place a temperature sensor at least every 25 feet in each aisle with sensors placed closer together if high temperature equipment like blade servers are in use. It is important to know that data center temperatures can drastically vary in nearby locations depending on height from the floor, the specific equipment that is present, and how much equipment is present.

 - AVTECH recommends installing TemPageR and Room Alert rack units at the top of each rack in the data center as the heat generated by the components in the rack rises up to the unit which will give the most accurate readings, TemPageR and Room Alert units will be able to provide an early warning and notify staff for temperature issues before critical systems, servers or network equipment is damaged. You may wish to consider purchasing additional AVTECH devices and sensors to maximize the area that can be monitored.

 - In addition, avoid locating your sensor cables near large electromagnetic devices and florescent lights.

 - Place your sensor cables so that they are located in a safe place away from frequent foot traffic or constant disruption from moving parts.

Click here to review an article entitled Recommended Computer Room Temperature and Humidity. For additional information, please visit ASHRAE (the American Society of Heating, Refrigerating, and Air-Conditioning Engineers) to view a document called "Thermal Guidelines for Data Processing Environments" to assist you in planning how to best place your Digital Temperature Sensors in your organization's environment.

How do I extend my Digital Sensor Cable longer than the supplied 25 feet?

By design, external digital sensor cables are 25 feet in length and can be extended up to a supported100 feet in total length.

To extend the sensor cable, you will need a RJ-11 cable with coupler which is available from AVTECH Software.

To order these cables, contact your Product Specialist or click here to purchase on-line.

To extend an external digital sensor cable:

  1. Remove the external digital sensor to be extended by unplugging its RJ-11 cable from the front of the unit.
  2. Using a 25 foot RJ-11 cable with coupler, insert the RJ-11 connector into the AVTECH unit’s external sensor port.
  3. Plug the RJ-11 connector on the sensor cable to the extension cable.

If you wish to extend the sensor up to the supported 100 feet in length, multiple RJ-11 extension cables can be connected using the methods above.

It is important to note that AVTECH does not recommend extending a cable to a greater distance than 100 feet and does not support splicing or cutting into existing wires to shorten or lengthen the provided cable.



Internal Temperature Sensor Can Be Higher on Powered WiSH Sensors

The Powered Wireless Sensor Hub (P-WiSH) is a wireless sensor that transmits sensor data from internal and connected sensors back to the Room Alert 26W. The P-WiSH has one internal Digital Temperature Sensor and two external digital sensor ports. The P-WiSH is powered by an AVTECH 5V Power Adapter and has internal circuitry to regulate this power. The heat generated by the internal power regulator can cause the internal temperature sensor to report a slightly higher temperature when compared to one of its external sensors or a third party thermometer. This is normal, and the internal temperature reading can be adjusted using the 'Adjust' field in the Room Alert 26W or Room Alert 32W Settings. For more information on the adjust field and how to change it, click here.

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.

Why is the internal temperature reading on my Room Alert or TemPageR monitor higher than the external sensors?

The internal temperature sensor measures the ambient air temperature inside the Room Alert or TemPageR device. Under normal operating conditions, the device can generate some heat internally that can cause the internal sensor to register a temperature that is a few degrees higher than the external sensors. This is normal and especially holds true for any rack mounted monitors, as the temperature inside of a rack is typically warmer than the surrounding environment where the external temperature sensors are located. All sensor readings, including internal sensors, can be calibrated using the 'Settings' page of the monitor's firmware.

Click the 'Settings' link and go to the 'Sensors' tab. If desired, enter a integer value in the 'Adjust' field to calibrate the internal sensor reading to match the readings from the external sensors. For example, if the internal temperature is two (2) degrees higher than the external sensor, put a '-2' in the 'Adjust' field for Sensor 1.

If your Adjust field value seems to be different than what you initially saved it as, it is most likely due to the conversion from Celsius to Fahrenheit. For more information, please follow this link: http://AVTECH.com/Support/index.php?action=kb&article=119

If you have any further questions, please feel free to contact our Technical Support Team by submitting a support ticket.

Room Alert 11E

Can I log sensor data on my Room Alert or TemPageR?

     AVTECH's Device ManageR software can log all sensor data for each and every Room Alert and TemPageR monitor connected to a network. Device ManageR runs as a Windows Service and uses the host system's hard drive to store logs in an SQL database. Device ManageR is available for free to all customers who have purchased a Room Alert or TemPageR monitor and have current Maintenance, Support, and Update Service (MSUS) with AVTECH. Device ManageR's logging is a standard feature along with graphing, unlimited/custom alerts, and much more. Device ManageR can be downloaded from the Downloads section at http://AVTECH.com/Downloads/ For more information on Device ManageR, please follow this link: http://AVTECH.com/Products/Device_ManageR/

How Do I Update The Firmware On My Room Alert Or TemPageR Monitor?

- Verify that you have either the AVTECH Device Discovery Utility or Device ManageR software installed on a host machine that has network visibility to the Room Alert or TemPageR monitor that is to be updated.
 - Verify that the software being used is the most current version of AVTECH Device Discovery or Device ManageR. The most current versions can be obtained via the 'Downloads' section of AVTECH.com for current MSUS subscribers.


Note which firmware version the Room Alert or TemPageR is currently running by checking the monitor's 'Status' page. The monitor's version will be in the top right hand corner.

Click here: http://avtech.com/Downloads/ and check the left side box for a list of AVTECH's released versions. If your current firmware version is older than the version listed here, please continue by logging in to the 'Downloads' section. (If you do not know your login password or if you are unsure if you  have an account, click the 'Forgot/Reset Password' link and enter your email address. If your email address is not recognized, click the 'Email Request/Inquiry' button and fill in your information. If your email address is recognized but you do not receive an email with your password, check any SPAM filter in place before contacting AVTECH Technical Support.)

Once in the downloads section, navigate to the monitor's section. Save the firmware update file but DO NOT unzip/decompress the file if it arrives as a .zip or .upd file.


DEVICE DISCOVERY UTILITY: Open Device Discovery and click the 'Search' button. 



Select the monitor that is to be updated and click the 'Update' button.

 


Follow the prompts to specify the location of the Firmware Update file for the monitor and click the 'Upload' button.

 



DEVICE MANAGER: Open Device ManageR and select the monitor from the Device Status list or click on the unit's information in the middle of the page.



Click the 'Update Firmware' button.



Click 'Browse'.



Select the appropriate file and click 'Open'.



Click the 'Update' button to begin the firmware update process.



When the firmware update process completes, the unit will automatically reboot to apply the update.
If you experience an issue during this process, please feel free to contact the Technical Support Team by submitting a support ticket.

Room Alert/TemPageR Sensor Data Not Loading

The Room Alert and TemPageR devices load the sensor data for display on the Status page using a background xml http request to a file called "getData.htm".

If sensor data is not loading, first verify that the 'getData.htm' web page is accessible by entering "http://<ip_address_of_device>/getData.htm" in the web browser location bar. 

Example 192.168.2.95/getData.htm   

You should see the following output.......





If the data fails to load, the cause can usually be traced to a proxy server or Microsoft ISA server. If your network has a proxy server or Microsoft ISA server, be sure that it is configured to ignore requests to and from Room Alert. Also verify that you do not have any local Internet security, anti-virus, or firewall applications that may be blocking, filtering or caching the background requests to this page.

A shorter test can also be used by entering in  http://ip_address_of_device/mobile.txt    Example 192.168.2.95/mobile.txt    you should see the following output....




If you see an image loading like the one above, your issue is related to either a web browser, security device/application or anti-virus program blocking requests and traffic made to the unit.  You will want to further examine  your  current security settings on your security applications and devices running on your pc and on your network.  


Please feel free to contact our Support Team at Support@AVTECH.com with any further questions.

What is Room Alert 11E?

Room Alert 11E is "Advanced Computer Room Environment Monitoring, Alerting & Automatic Corrective Action". Room Alert 11E has a built-in web server that allows alert notifications via email, email-to-SMS, SNMP and more. Room Alert 11E offers an easy to use web browser interface for settings changes and viewing real-time temperature, humidity and environment sensor status from anywhere. Device ManageR software (included free) expands alerting and allows automatic corrective actions. It also includes advanced graphing and many extended features such as report generating and modem support. For complete information on the Room Alert 11E, please visit the unit's web page: http://avtech.com/Products/Environment_Monitors/Room_Alert_11E.htm


Initial Discovery & Setup

A Device That Is Connected To A Managed Switch Is Not Accessible

Managed switches are a more powerful version of the basic network switch. They can be configured to screen traffic on certain ports or protocols and have been found to sometimes interfere with TemPageR or Room Alert communications. Because of this, a device can initially work as expected, but become inaccessible over time. Any switch that allows extra control over the traffic it sees is considered a managed switch for the purposes of this discussion. Symptoms usually observed are that a unit will initially work as expected but after a period of time will become inaccessible. In some cases, the IP address of the unit will still respond to pings. Cycling power on the unit temporarily resolves the issue.

A quick test to verify if the switch is the issue is to attach the device to a different network switch or hub. Be sure that the other switch is on the same network segment or the unit might be inaccessible. You can also connect the unit off the network with a crossover cable to see if the issue persists.

If the managed switch is found to be the cause of the issue, be sure to remove any configurations that might interfere with the traffic sent by the unit. Along with normal TCP 80 traffic, the device will send NTP requests on UDP port 123, email on TCP port 25, SNMP Traps on UDP port 161 and can be accessed via UDP port 30718.

In conjunction with this, there are a few other recommendations.

1.If your switch has a setting that will allow the port to act as an un-managed switch port, we highly recommend you enable this setting.

2.You should hard code the port speed on the switch the AVTECH device is connected to to a 100/Full Duplex setting. 

3.In addition, hard code the port speed on the AVTECH unit to 100/Full Duplex. The MTU size defines the size of data packets sent from the Room Alert or TemPageR device and might need to be modified to match settings on the managed switch.


4.Also, we recommend starting with a MTU of 1024. If your issues persist after hardcoding the port speed and setting the MTU, then adjust the MTU downward in increments of 64. Please note that the lowest allowable MTU size is 512. These settings are available on the 'Network' tab of the 'Settings' page of the Room Alert or TemPageR device. Uncheck the 'Auto Negotiate' checkbox and select the '100 MB' and 'Full Duplex' radio buttons. In the 'MTU Size' field, ensure that a value of 1024 or lower is entered. Remember, if your issues persist after applying these settings, gradually lower the MTU until you find the right size.

5. Finally, another option is to place a hub in between the Room Alert or TemPageR device and the switch, so that the unit connects to the hub and the hub connects to the switch. This way, the unit is negotiating with the hub rather than the switch and this should mitigate the issue.

How Do I Enable A Security Password On Room Alert Or TemPageR Monitors?

A password can be configured for each individual Room Alert or TemPageR to prevent unauthorized users from modifying the 'Settings' section.  Passwords should be alphanumeric and cannot include special characters or symbols.

To Configure A Password For Room Alert or TemPageR
  1. Type the IP Address of the monitor into a web browser to access the 'Status' page. (For Device ManageR, click the monitor in the 'Device Status' list, then select 'Open Web')
  2. Once the 'Status' page is displayed in the web browser, click the 'Settings' tab.
  3. Unless you have previously configured a password for the device, leave the user name and password fields blank and click 'OK'.  If you have previously created a password for the monitor, leave the user name field blank and enter the current password, then click 'OK'.
  4. When the 'Settings' screen displays, click the 'Security' button on the left side list.
  5. In this screen, enter the old password, new password, and confirm the new password. (If an old password is not set, leave this field completely blank)
  6. Click the 'Accept Changes' button at the bottom of the screen, then click the 'Save Settings' button in the left side list to reboot the monitor. The monitor will  reboot, and now require a password only to access the 'Settings' section.
To Reset An Unknown Password That Was Previously Set

All current Room Alert and TemPageR monitors feature a hard reset button on the back of the case. While the monitor is powered on and connected to an active network or crossover cable connection, please locate and hold down this reset button while watching the top left green light on the monitor's network port. This network light will go out for two seconds, then reappear to signify a complete reset. The monitor will now have factory default settings, which includes a blank password set for the 'Settings' section. Note that the unit will be configured for DHCP and any static IP set previously will need to be reconfigured.

If the monitor does not have a physical reset button, please contact AVTECH Technical Support and speak with one of our Technical Specialists.  

To contact AVTECH support, click here.

How do I set a Static IP address on my Room Alert or TemPageR?

A Static IP address can be set for your Room Alert or TemPageR unit by using the AVTECH Device Discovery Utility, AVTECH Device ManageR, or via the 'Network' section in the 'Settings' tab of the Room Alert or TemPageR web browser interface.

To set a Static IP address using the AVTECH Device Discovery Utility, open the AVTECH Device Discovery Utility and click the 'Search' button. Select the monitor you wish to assign a static IP address to and click the 'Set IP' button. Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit being updated.

To set a Static IP address using the AVTECH Device ManageR Software, open the Device ManageR software and click the monitor in the left hand 'Device Status' list. You will notice a small drop down below the currently selected monitor. Click the '-Set IP Address' button.
Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit you are updating.

To set a Static IP address using the monitor's web browser interface, enter the current IP address of your Room Alert or TemPageR monitor into the location bar of a web browser. The 'Status' page will load by default and display the current sensor values. Click the 'Settings' tab at the top of the page and the 'Network' section will load. Uncheck the 'Use DHCP' checkbox and enter the desired static IP information in the available fields. Be sure that all static IP address information is correct for the location of the monitor you are updating. To complete the changes, please click the 'Accept Changes' button at the bottom of your page and then the 'Save Settings' button on the left hand side. The monitor will now reboot and apply the new changes.

If the Room Alert or TemPageR monitor cannot be discovered or you do not know the existing IP address, a Static IP address can be set using the MAC address of the unit, which can be found on a label on the bottom of the monitors. Please open Device Discovery and click the 'Set IP' button without selecting a device from the list and follow the prompts from the AVTECH Device Discovery Utility. Alternatively, you can set a Static IP address via the MAC address of your monitor in Device ManageR.
Open Device ManageR and click the 'Advanced Discovery' button in the top left hand corner on the 'Device Status' list. This button will display a pop up that will have a 'Set IP Via MAC Address' button. From here, enter the MAC address of the monitor and the desired Static IP address.When finished, press the 'Update IP Settings' button to make the changes.

How To Use The Trace Feature On A Room Alert Or TemPageR Device

The tracing feature is a very useful tool that can be used to assist in troubleshooting issues with your Room Alert or TemPageR device.

To enable tracing on your unit, follow these steps:

       1.   Access the 'Advanced' tab of the 'Settings' page.


  

       2.   In the 'Trace Configuration' section, ensure that the 'Enable Tracing' check box is checked. The tracing port is 143 by default. You do not need to change this unless you know port 143 will be blocked by your network for some reason. After making changes in this section, click the 'Accept Changes' button at the bottom of the screen, then the 'Save Settings' button on the left hand side of the screen.




To generate a trace from your device you will want to enter the following command into a Windows command prompt: 'telnet -f c:\tracefile.txt <IP of unit> <trace port #>' then press the <Enter> key. Where 'IP of unit' is the IP address of your Room Alert or TemPageR device and 'trace port #' is the configured trace port (143 by default). So the command might look something like this: 'telnet -f c:\tracefile.txt 192.168.33.100 143'. This command will capture your trace data directly to a text file named 'tracefile.txt' in the C: directory.

Please note that Windows 7 and Vista have disabled the Telnet client by default. If you get an error saying 'telnet is not recognized as an internal or external command, operable program or batch file' you will need to enable it by going to 'Start', 'Control Panel', 'Programs And Features', 'Turn Windows Features On Or Off' then checking the 'Telnet Client' row and clicking 'OK'.


At times, it may be useful or necessary for our engineers to review a trace from a Room Alert or TemPageR device and we may request you send us the results of a trace. If you are requested to send a trace in by one of our technical support specialists, or if you feel it will be helpful before being asked, simply attach the file created by the command given above to an email and send it to us at 'Support@AVTECH.com'.

One example of how to use the tracing feature is for troubleshooting email issues with your device. To troubleshoot email issues using the trace feature, launch the trace window using the process described above. Once you have successfully connected to the trace, browse to the 'SMTP Email' tab on the 'Settings' page. Try sending an email by clicking the 'Send Test Email' button at the bottom of the SMTP Email tab. You should see the attempts by the Room Alert or TemPageR device to connect to the configured mail server in the trace output window. If there are any issues occurring with the email process, you should see corresponding errors displayed in the output window which should point you in the right direction as to what might be causing any issue.

My Room Alert Or TemPageR Monitor Is Not Discoverable Or Accessible On My Network. How Do I Discover My Room Alert Or TemPageR?

Device ManageR and the Device Discovery Utility use a broadcast scan on UDP port 30718 to automatically locate AVTECH monitors on a network.
AVTECH recommends the following for initial product discovery:
 - DHCP Enabled on network.
 - UDP Broadcasts allowed at a computer and network level.
Please Note Before Beginning:
 - The network cable must be plugged in to the Room Alert or TemPageR monitor and the switch or computer before power is connected. This ensures that the initial DHCP request will be sent successfully when power is connected.

 - If the monitor has been assigned a static IP address that is invalid for the current IP address range of the network, please proceed to step 3 of this guide.
 - When the Room Alert or TemPageR monitor is powered on and plugged into a network, please check the current status of the Network Jack's lights as these lights are used to determine the current state of the monitor. The left link light should be a solid green color while the right light should be a flashing green or orange. If these lights display any other patterns than this, please skip to step 5 of this guide.

To begin discovering the monitor's IP address, please follow the instructions below starting at step 1.

1. Both Device ManageR and the Device Discovery Utility have a manual discovery feature that uses a TCP scan on TCP port 30718. This feature is helpful if the network range or specific IP address of the monitor is known. 

 - To access this feature using Device ManageR, click the 'Advanced Discovery Options...' button under 'Device Status' in the left menu. Click the 'Manually Add Device/s Via IP Address' button and select either 'Single IP Address' or 'Range Of IP Addresses'. Insert the desired IP address or range and click the 'Begin Scan...' button.

 

 - To access this feature using the Device Discovery Utility, click the 'Advanced Discovery' button located under the 'Search' button. Then, select either 'Single IP Address' or 'Range IP Addresses' and enter the single IP address or IP address range. Start the scan using the 'Begin Scan' button.


2. DHCP Enabled On Network – All AVTECH monitors are initially set to obtain an IP address automatically using DHCP. DHCP must be enabled on the network for the monitor to receive a valid IP address. If DHCP is not enabled, the monitor will default to an auto IP address in the 169.254.xxx.xxx range. At this IP address, the router or system firewalls may not allow discovery because the IP address is outside of the valid network IP range. Valid assignment could potentially be hindered by a managed switch even if DHCP is enabled. If DHCP assignment is delayed in the managed switch, the DHCP request sent from the monitor can timeout and default to a 169.254.xxx.xxx Auto IP address.

 - If DHCP is enabled on the network, there is a chance the DHCP server has already assigned a valid IP address even though the monitor is not discoverable. If the manual discovery option from step 1 does not discover the monitor, the IP address can sometimes be obtained by checking the DHCP server for the MAC address of the monitor.

 - If the IP address can be verified by checking the DHCP server and the IP address is in range of the network, it can be added to Device ManageR and the Device Discovery Utility using the manual scan feature from step 1. This IP address can additionally be accessed by directly by typing the IP address in a web browser. 

 - It is also possible to create a DHCP reserved IP address on a server. Doing this and recycling the power on the monitor should allow the IP address to be assigned by the DHCP server. If this process is unknown or unable to be completed personally, please consult the local Network Administrator. Otherwise, continue to the next step.

3. If the IP address of the monitor is still not discoverable, AVTECH recommends connecting the unit directly to a computer or laptop using a cross-over Ethernet cable or spare network hub.

 - Before disconnecting a computer or laptop to be used from the current network, be sure that the Device Discovery utility is installed along with a protocol analyzer (packet sniffer) application. If a preferred protocol analyzer application is unknown or not installed, a free utility called 'Wireshark' can be installed from http://www.wireshark.org/.

 - Begin by assigning a static IP address to the computer's network card, then connect the monitor via cross-over Ethernet cable or spare network hub to the computer. Lastly, plug in the power to the Room Alert or TemPageR monitor to begin the connection process. 

 - Attempt discovery using the Device Discovery utility by clicking the 'Set IP' button. The 'Set IP' button can set an IP via the MAC address which can be found at the bottom of any Room Alert or TemPageR monitor's case. Follow the procedure as prompted by Device Discovery and remember to set the IP to a valid IP address that is within the same subnet as the IP set for the computer's network card. After doing this, the monitor should be accessible via the Device Discovery list or by directly entering the newly set IP address in a web browser.

4. DHCP alternative to the static IP settings above: While still on the cross-over cable direct connection between the computer and monitor, the Room Alert or TemPageR may also be reset back to initial DHCP factory defaults via the reset button on the back panel of the monitor (if applicable). 

- For TemPageR3E, Room Alert 4E, 11E: Hold the reset button in for 10-15 seconds until the top left LED on the Ethernet jack blinks. A reset has occurred when this light on the ethernet jack goes out, then reappears 1 second later. Please release the reset button after this occurs.

 - For Room Alert 24E, 26W, 32E/W: Hold the reset button in for 10-15 seconds and watch the 3 main status lights on the front of the monitor. A reset has occurred as the front 3 status lights cycle through red and then finish cycling. Please release the reset button after this occurs.

 - With the unit now set back to DHCP factory defaults, change the laptop's network card settings to automatically obtain an IP address as opposed to specifying a static IP. Start up the Device Discovery utility and click 'Search' to locate the monitor.

 - If the Device Discovery utility methods are not working and the above steps have not located the monitor, start the protocol analyzer application, Begin packet capture and recycle the power on the monitor. Look for incoming packets coming from the MAC address of the monitor (located on a sticker on the bottom of the monitor's case or on the back of a rack mount kit if applicable). One of these packets should contain the source IP address of the monitor. Once this IP address has been obtained, configure a static IP address on the laptop or computer that is within a valid network range in relation to the IP address assigned to the unit as in step 3 (i.e. IP of unit: 192.168.2.3 - IP for computer or laptop: 192.168.2.4). The monitor can now be directly accessed by entering the IP address in a web browser.

5. If the above trials have been unsuccessful in discovering the IP address of the unit, please email Support@AVTECH.com with the packet capture obtained in step 4 attached to the email.

Trouble/Issues Accessing the 'Downloads' Section of AVTECH.com

The 'Downloads' section on AVTECH.com is AVTECH's only source of Device ManageR, Room Alert/TemPageR firmware updates, Software updates, MIB files, Device ManageR plugins, and the Device Discovery utility. To gain access to this section, AVTECH will issue a username and password to all contacts that are employed by organizations that have purchased a Room Alert or TemPageR environmental monitor.

If you have been previously issued a username and password from AVTECH: When attempting to log on to the AVTECH Downloads section, make sure that the password being used is entered correctly as the password is case sensitive. Please note the email address that was initially given to AVTECH at the time of registration is the only email that can be used to log on to this section.

If the initial password for the 'Downloads' section of AVTECH.com has been lost or forgotten, go to AVTECH.com/Downloads/ and select the 'Forgot/Reset Password' link below the login section. Enter the registered email address in the new screen and select 'Submit'. If the email address matches a record that was previously created in AVTECH's registry, an email will be sent with the required password.

If you are able to access AVTECH's downloads, but your downloads are expired: The specific downloads provided to your organization are regulated by AVTECH's Maintenance, Support, and Update Service (MSUS). MSUS is an annually renewed service for each of the Room Alert and TemPageR units owned by the organization. If MSUS needs to be renewed, please send an email to RenewMSUS@AVTECH.com including the organization's name and your personal contact information. For more information on MSUS, please refer to this page link:  http://www.AVTECH.com/PDFs/AVTECH_MSUS_Explained.pdf 

If you are a new contractor or temporary hire and require access to AVTECH Downloads: Please provide the following information in an email to 'Support@AVTECH.com' along with a short message explaining the need for access. Once approved, you will be registered as a contractor or temporary hire directly under the organization that owns the Room Alert or TempageR product. Please include the following information in this email:

Organization Name
Organization Address
Organization Phone Number
Your Full Name
Direct Phone Number
Email Address
Job Title
Summary Of Work To Be Completed

For all other issues accessing the 'Downloads' section of AVTECH.com, send an email to 'Support@AVTECH.com' and we will be able to provide further assistance.


Status Screen

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.



Settings Screen

I am unable to get my Room Alert or TemPageR monitor to send email alerts properly. How do I send email alerts directly from the monitor's web page?

Email alerts from the Room Alert or TemPageR monitors are sent using anonymous, unauthenticated SMTP email on TCP port 25. If email notifications are not received, first verify the email settings in the 'SMTP Email' section of the 'Settings' page.
  1. Mail Server Port: This port is typically port 25 but can be different based on personal mail server settings and network preferences. Please check with the mail server administrator for the exact port number.
  2. Mail Server: If the monitor is configured to obtain an IP address using DHCP, enter the specific IP address of the mail server in the ‘Mail Server Address’ field. If the monitor is configured with a static IP address, the DNS name for the mail server can be entered in this field. For initial testing purposes, enter an email address from the same domain as the mail server in the ‘Email Recipients’ field. For example, if the domain name is 'Example.com', be sure the email used to test is from the same domain (i.e. YourEmail@Example.com).
  3. Return Address: To finish the configuration, enter the same email address in the ‘Return Address (From)’ field. Using the same domain name minimizes the risk that security settings on the email server would prevent the message from being delivered.
  4. Display URL: The display URL is a URL that will be at the bottom of your received email alert. This URL is here to allow quick link/access to any URL after an alert is triggered. This URL can be a link to any web page you would like, but typically we assume that quick access to your Room Alert's web page is necessary here. Type in the IP address of the monitor or any other web page that is desired in this field.
  5. Authentication: This field is optional because not all mail servers require authentication. Please check with the mail server administrator if there are any questions about this field. The Username and Password would typically be the same credentials used to log on to a mail server directly.
  6. Email Recipients: List the email addresses that the alert will be sent to and separate multiple addresses by a comma. For example, John@Example.com,James@Example.com,Steve@Example.com Please note that due to limited flash memory on the Room Alert and TemPageR monitors, the Email Recipients field is only 79 characters long. For more space, AVTECH recommends creating a distribution list in the email server itself or for unlimited email entries and advanced/custom alerting, please follow this link for AVTECH Device ManageR: http://avtech.com/Products/Device_ManageR/


     Once the email settings are configured, click the ‘Test Email’ button and check the email account(s) for the test email. If the message is not received, first check any spam filter that may be in place. If the test email cannot be found, it could be blocked by the mail server. Be sure the mail server is configured to allow 'SMTP Relaying' from the IP address of the monitor. Also, be sure the Room Alert or TemPageR is on the email server's 'whitelist' to prevent messages from being filtered or blocked as spam. If messages from the monitor continue to be blocked by the mail server, contact the mail server administrator to see if the mail server logs can be reviewed to determine why the messages are being blocked.

If you have followed the steps above but are still unable to receive email alerts, please contact our Technical Support Team by
submitting a support ticket.

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.


What is the Default 'Settings' Screen Password on Room Alert or TemPageR?

The 'Settings' screen of Room Alert and TemPageR is password protected to prevent unauthorized users from modifying the settings. By default, there is no user name and password configured to access the 'Settings' screen of a Room Alert or TemPageR. With the User Name and Password fields left blank, select 'OK' to access the 'Settings' screen.

If you have previously configured a password for the device, leave the User Name field blank and enter your password in the 'Password' field, then select 'OK' to access the 'Settings' screen.

When I try to access the 'Settings' screen on my Room Alert or TemPageR, my web page flashes or does not load properly. How do I access the 'Settings' screen?

The 'Settings' screen on the Room Alert and TemPageR units consist of a Java applet that accesses the device on UDP port 30718 and 30719. To view the 'Settings' applet, Java software must be installed in the browser being used to access the web interface. Java software can be installed at Java.com. Next, verify that you do not have UDP port 30718 and 30719 blocked on any device located between the system or server you are currently using and your unit. If this is the case, unblock the port and try accessing the 'Settings' screen again.

The 'Settings' screen consists of an HTML form that submits and retrieves data using Java script and normal http 'get' and 'post' requests. When the 'Settings' screen flashes or doesn't load properly, we have noticed that a typical cause would be certain security devices such as Microsoft's ISA proxy server or antivirus programs that are implemented on your network. If you can, please check your network and see if any of these items are in fact implemented and are interfering with communications. In order for the 'Settings' tab to open, our program runs certain commands and pages in the background which conflict with some antivirus program's or Internet Security Server's configured settings.

You can attempt to check these pages by trying the following two addresses   http://<IP of unit>/secure/setuprec.xml  and  http://<IP of unit>/secure/unitinfo.xml  Once you have called upon them, please right click and 'view source' on them. If you notice anything strange here or are receiving an error message we would appreciate seeing them for reference. You can  take screen shots or make a text copy of the contents and send them to us here at Support@AVTECH.com

To resolve this issue, typically we see that a proxy server or antivirus is blocking background XML HTTP requests. A typical fix is to allow or add exceptions to the Room Alert Or TemPageR IP address in all security implementations.

If you are still having difficulty, please follow the steps below and attempt to access the 'Settings' screen after completing each one.

  1. Completely close the web browser you are using and reload. If you have any alternate web browsers, please attempt to access the settings page with these browsers as well.

  2. Recycle the power on your unit.

  3. Reupload/update the firmware on your Room Alert or TemPageR unit. For complete instructions on doing so, please follow this link:  http://avtech.com/Support/index.php?action=kb&article=40

If steps 1-3 do not resolve the issue, we suggest disconnecting your device from your network and attempt to connect to it via a laptop and Device Discovery through a crossover cable. When using a cross over cable, you should plug the crossover cable in to the device and the PC first, then plug in the power to the unit. Remember to set up your laptop's network card to be within the same subnet range as your Room Alert and TemPageR unit, then attempt to discover your unit with the Device Discovery Unit. For more information on discovering your unit, please follow this link. http://AVTECH.com/Support/index.php?action=kb&article=73 If you have discovered your unit and are able to access your unit's 'Settings' page, this means that one of the previous topics discussed is most likely still an issue on your network. If you have successfully connected via a crossover cable and are still unable to properly access the settings page, please feel free to contact our technical support staff by submitting a support ticket.


Sensors

Can I add additional sensors to my Room Alert or TemPageR after my initial order?

Yes. Many environmental sensors are available for purchase at any time from AVTECH such as temperature, humidity, power, flood, smoke, motion, room entry and many more. A list of these sensors can be found here: http://avtech.com/Products/Monitor_-_Sensors/ For additional information and purchasing of our environmental sensors, please contact an AVTECH Senior Product Specialist at 888.220.6700.

External Digital Temperature and Humidity Sensor Placement Suggestions

Placing Digital Temperature Sensors in the right locations is essential for reliable monitoring of the environment. Without proper placement, the most relevant temperature data may not be obtained.

 - It is recommended that the Room Alert or TemPageR unit itself is placed near the equipment that you wish to monitor as the standard cable length for Digital Temperature Sensors is 25 feet. External digital sensors may be extended up to 100 feet in length with the use of cable extensions found here: http://avtech.com/Products/Monitor_-_Accessories/Extended_Cable_Coupler.htm.

 - Measuring the temperature of the aisles in the data center at multiple height levels can give an early indication of a potential temperature problem. For consistent and reliable temperature monitoring, place a temperature sensor at least every 25 feet in each aisle with sensors placed closer together if high temperature equipment like blade servers are in use. It is important to know that data center temperatures can drastically vary in nearby locations depending on height from the floor, the specific equipment that is present, and how much equipment is present.

 - AVTECH recommends installing TemPageR and Room Alert rack units at the top of each rack in the data center as the heat generated by the components in the rack rises up to the unit which will give the most accurate readings, TemPageR and Room Alert units will be able to provide an early warning and notify staff for temperature issues before critical systems, servers or network equipment is damaged. You may wish to consider purchasing additional AVTECH devices and sensors to maximize the area that can be monitored.

 - In addition, avoid locating your sensor cables near large electromagnetic devices and florescent lights.

 - Place your sensor cables so that they are located in a safe place away from frequent foot traffic or constant disruption from moving parts.

Click here to review an article entitled Recommended Computer Room Temperature and Humidity. For additional information, please visit ASHRAE (the American Society of Heating, Refrigerating, and Air-Conditioning Engineers) to view a document called "Thermal Guidelines for Data Processing Environments" to assist you in planning how to best place your Digital Temperature Sensors in your organization's environment.

How do I extend my Digital Sensor Cable longer than the supplied 25 feet?

By design, external digital sensor cables are 25 feet in length and can be extended up to a supported100 feet in total length.

To extend the sensor cable, you will need a RJ-11 cable with coupler which is available from AVTECH Software.

To order these cables, contact your Product Specialist or click here to purchase on-line.

To extend an external digital sensor cable:

  1. Remove the external digital sensor to be extended by unplugging its RJ-11 cable from the front of the unit.
  2. Using a 25 foot RJ-11 cable with coupler, insert the RJ-11 connector into the AVTECH unit’s external sensor port.
  3. Plug the RJ-11 connector on the sensor cable to the extension cable.

If you wish to extend the sensor up to the supported 100 feet in length, multiple RJ-11 extension cables can be connected using the methods above.

It is important to note that AVTECH does not recommend extending a cable to a greater distance than 100 feet and does not support splicing or cutting into existing wires to shorten or lengthen the provided cable.



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.

Temperature Conversion Formulas

[F = Fahrenheit, C = Celsius]


To Convert Celsius To Fahrenheit

F = 1.8C + 32


To Convert Fahrenheit To Celsius

C = F – 32
          1.8

Why is the internal temperature reading on my Room Alert or TemPageR monitor higher than the external sensors?

The internal temperature sensor measures the ambient air temperature inside the Room Alert or TemPageR device. Under normal operating conditions, the device can generate some heat internally that can cause the internal sensor to register a temperature that is a few degrees higher than the external sensors. This is normal and especially holds true for any rack mounted monitors, as the temperature inside of a rack is typically warmer than the surrounding environment where the external temperature sensors are located. All sensor readings, including internal sensors, can be calibrated using the 'Settings' page of the monitor's firmware.

Click the 'Settings' link and go to the 'Sensors' tab. If desired, enter a integer value in the 'Adjust' field to calibrate the internal sensor reading to match the readings from the external sensors. For example, if the internal temperature is two (2) degrees higher than the external sensor, put a '-2' in the 'Adjust' field for Sensor 1.

If your Adjust field value seems to be different than what you initially saved it as, it is most likely due to the conversion from Celsius to Fahrenheit. For more information, please follow this link: http://AVTECH.com/Support/index.php?action=kb&article=119

If you have any further questions, please feel free to contact our Technical Support Team by submitting a support ticket.

Room Alert 7E

Can I log sensor data on my Room Alert or TemPageR?

     AVTECH's Device ManageR software can log all sensor data for each and every Room Alert and TemPageR monitor connected to a network. Device ManageR runs as a Windows Service and uses the host system's hard drive to store logs in an SQL database. Device ManageR is available for free to all customers who have purchased a Room Alert or TemPageR monitor and have current Maintenance, Support, and Update Service (MSUS) with AVTECH. Device ManageR's logging is a standard feature along with graphing, unlimited/custom alerts, and much more. Device ManageR can be downloaded from the Downloads section at http://AVTECH.com/Downloads/ For more information on Device ManageR, please follow this link: http://AVTECH.com/Products/Device_ManageR/

How Do I Update The Firmware On My Room Alert Or TemPageR Monitor?

- Verify that you have either the AVTECH Device Discovery Utility or Device ManageR software installed on a host machine that has network visibility to the Room Alert or TemPageR monitor that is to be updated.
 - Verify that the software being used is the most current version of AVTECH Device Discovery or Device ManageR. The most current versions can be obtained via the 'Downloads' section of AVTECH.com for current MSUS subscribers.


Note which firmware version the Room Alert or TemPageR is currently running by checking the monitor's 'Status' page. The monitor's version will be in the top right hand corner.

Click here: http://avtech.com/Downloads/ and check the left side box for a list of AVTECH's released versions. If your current firmware version is older than the version listed here, please continue by logging in to the 'Downloads' section. (If you do not know your login password or if you are unsure if you  have an account, click the 'Forgot/Reset Password' link and enter your email address. If your email address is not recognized, click the 'Email Request/Inquiry' button and fill in your information. If your email address is recognized but you do not receive an email with your password, check any SPAM filter in place before contacting AVTECH Technical Support.)

Once in the downloads section, navigate to the monitor's section. Save the firmware update file but DO NOT unzip/decompress the file if it arrives as a .zip or .upd file.


DEVICE DISCOVERY UTILITY: Open Device Discovery and click the 'Search' button. 



Select the monitor that is to be updated and click the 'Update' button.

 


Follow the prompts to specify the location of the Firmware Update file for the monitor and click the 'Upload' button.

 



DEVICE MANAGER: Open Device ManageR and select the monitor from the Device Status list or click on the unit's information in the middle of the page.



Click the 'Update Firmware' button.



Click 'Browse'.



Select the appropriate file and click 'Open'.



Click the 'Update' button to begin the firmware update process.



When the firmware update process completes, the unit will automatically reboot to apply the update.
If you experience an issue during this process, please feel free to contact the Technical Support Team by submitting a support ticket.

Room Alert/TemPageR Sensor Data Not Loading

The Room Alert and TemPageR devices load the sensor data for display on the Status page using a background xml http request to a file called "getData.htm".

If sensor data is not loading, first verify that the 'getData.htm' web page is accessible by entering "http://<ip_address_of_device>/getData.htm" in the web browser location bar. 

Example 192.168.2.95/getData.htm   

You should see the following output.......





If the data fails to load, the cause can usually be traced to a proxy server or Microsoft ISA server. If your network has a proxy server or Microsoft ISA server, be sure that it is configured to ignore requests to and from Room Alert. Also verify that you do not have any local Internet security, anti-virus, or firewall applications that may be blocking, filtering or caching the background requests to this page.

A shorter test can also be used by entering in  http://ip_address_of_device/mobile.txt    Example 192.168.2.95/mobile.txt    you should see the following output....




If you see an image loading like the one above, your issue is related to either a web browser, security device/application or anti-virus program blocking requests and traffic made to the unit.  You will want to further examine  your  current security settings on your security applications and devices running on your pc and on your network.  


Please feel free to contact our Support Team at Support@AVTECH.com with any further questions.

Initial Discovery & Setup

A Device That Is Connected To A Managed Switch Is Not Accessible

Managed switches are a more powerful version of the basic network switch. They can be configured to screen traffic on certain ports or protocols and have been found to sometimes interfere with TemPageR or Room Alert communications. Because of this, a device can initially work as expected, but become inaccessible over time. Any switch that allows extra control over the traffic it sees is considered a managed switch for the purposes of this discussion. Symptoms usually observed are that a unit will initially work as expected but after a period of time will become inaccessible. In some cases, the IP address of the unit will still respond to pings. Cycling power on the unit temporarily resolves the issue.

A quick test to verify if the switch is the issue is to attach the device to a different network switch or hub. Be sure that the other switch is on the same network segment or the unit might be inaccessible. You can also connect the unit off the network with a crossover cable to see if the issue persists.

If the managed switch is found to be the cause of the issue, be sure to remove any configurations that might interfere with the traffic sent by the unit. Along with normal TCP 80 traffic, the device will send NTP requests on UDP port 123, email on TCP port 25, SNMP Traps on UDP port 161 and can be accessed via UDP port 30718.

In conjunction with this, there are a few other recommendations.

1.If your switch has a setting that will allow the port to act as an un-managed switch port, we highly recommend you enable this setting.

2.You should hard code the port speed on the switch the AVTECH device is connected to to a 100/Full Duplex setting. 

3.In addition, hard code the port speed on the AVTECH unit to 100/Full Duplex. The MTU size defines the size of data packets sent from the Room Alert or TemPageR device and might need to be modified to match settings on the managed switch.


4.Also, we recommend starting with a MTU of 1024. If your issues persist after hardcoding the port speed and setting the MTU, then adjust the MTU downward in increments of 64. Please note that the lowest allowable MTU size is 512. These settings are available on the 'Network' tab of the 'Settings' page of the Room Alert or TemPageR device. Uncheck the 'Auto Negotiate' checkbox and select the '100 MB' and 'Full Duplex' radio buttons. In the 'MTU Size' field, ensure that a value of 1024 or lower is entered. Remember, if your issues persist after applying these settings, gradually lower the MTU until you find the right size.

5. Finally, another option is to place a hub in between the Room Alert or TemPageR device and the switch, so that the unit connects to the hub and the hub connects to the switch. This way, the unit is negotiating with the hub rather than the switch and this should mitigate the issue.

How Do I Enable A Security Password On Room Alert Or TemPageR Monitors?

A password can be configured for each individual Room Alert or TemPageR to prevent unauthorized users from modifying the 'Settings' section.  Passwords should be alphanumeric and cannot include special characters or symbols.

To Configure A Password For Room Alert or TemPageR
  1. Type the IP Address of the monitor into a web browser to access the 'Status' page. (For Device ManageR, click the monitor in the 'Device Status' list, then select 'Open Web')
  2. Once the 'Status' page is displayed in the web browser, click the 'Settings' tab.
  3. Unless you have previously configured a password for the device, leave the user name and password fields blank and click 'OK'.  If you have previously created a password for the monitor, leave the user name field blank and enter the current password, then click 'OK'.
  4. When the 'Settings' screen displays, click the 'Security' button on the left side list.
  5. In this screen, enter the old password, new password, and confirm the new password. (If an old password is not set, leave this field completely blank)
  6. Click the 'Accept Changes' button at the bottom of the screen, then click the 'Save Settings' button in the left side list to reboot the monitor. The monitor will  reboot, and now require a password only to access the 'Settings' section.
To Reset An Unknown Password That Was Previously Set

All current Room Alert and TemPageR monitors feature a hard reset button on the back of the case. While the monitor is powered on and connected to an active network or crossover cable connection, please locate and hold down this reset button while watching the top left green light on the monitor's network port. This network light will go out for two seconds, then reappear to signify a complete reset. The monitor will now have factory default settings, which includes a blank password set for the 'Settings' section. Note that the unit will be configured for DHCP and any static IP set previously will need to be reconfigured.

If the monitor does not have a physical reset button, please contact AVTECH Technical Support and speak with one of our Technical Specialists.  

To contact AVTECH support, click here.

How do I set a Static IP address on my Room Alert or TemPageR?

A Static IP address can be set for your Room Alert or TemPageR unit by using the AVTECH Device Discovery Utility, AVTECH Device ManageR, or via the 'Network' section in the 'Settings' tab of the Room Alert or TemPageR web browser interface.

To set a Static IP address using the AVTECH Device Discovery Utility, open the AVTECH Device Discovery Utility and click the 'Search' button. Select the monitor you wish to assign a static IP address to and click the 'Set IP' button. Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit being updated.

To set a Static IP address using the AVTECH Device ManageR Software, open the Device ManageR software and click the monitor in the left hand 'Device Status' list. You will notice a small drop down below the currently selected monitor. Click the '-Set IP Address' button.
Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit you are updating.

To set a Static IP address using the monitor's web browser interface, enter the current IP address of your Room Alert or TemPageR monitor into the location bar of a web browser. The 'Status' page will load by default and display the current sensor values. Click the 'Settings' tab at the top of the page and the 'Network' section will load. Uncheck the 'Use DHCP' checkbox and enter the desired static IP information in the available fields. Be sure that all static IP address information is correct for the location of the monitor you are updating. To complete the changes, please click the 'Accept Changes' button at the bottom of your page and then the 'Save Settings' button on the left hand side. The monitor will now reboot and apply the new changes.

If the Room Alert or TemPageR monitor cannot be discovered or you do not know the existing IP address, a Static IP address can be set using the MAC address of the unit, which can be found on a label on the bottom of the monitors. Please open Device Discovery and click the 'Set IP' button without selecting a device from the list and follow the prompts from the AVTECH Device Discovery Utility. Alternatively, you can set a Static IP address via the MAC address of your monitor in Device ManageR.
Open Device ManageR and click the 'Advanced Discovery' button in the top left hand corner on the 'Device Status' list. This button will display a pop up that will have a 'Set IP Via MAC Address' button. From here, enter the MAC address of the monitor and the desired Static IP address.When finished, press the 'Update IP Settings' button to make the changes.

How Do I Update The Firmware On My Room Alert Or TemPageR Monitor?

- Verify that you have either the AVTECH Device Discovery Utility or Device ManageR software installed on a host machine that has network visibility to the Room Alert or TemPageR monitor that is to be updated.
 - Verify that the software being used is the most current version of AVTECH Device Discovery or Device ManageR. The most current versions can be obtained via the 'Downloads' section of AVTECH.com for current MSUS subscribers.


Note which firmware version the Room Alert or TemPageR is currently running by checking the monitor's 'Status' page. The monitor's version will be in the top right hand corner.

Click here: http://avtech.com/Downloads/ and check the left side box for a list of AVTECH's released versions. If your current firmware version is older than the version listed here, please continue by logging in to the 'Downloads' section. (If you do not know your login password or if you are unsure if you  have an account, click the 'Forgot/Reset Password' link and enter your email address. If your email address is not recognized, click the 'Email Request/Inquiry' button and fill in your information. If your email address is recognized but you do not receive an email with your password, check any SPAM filter in place before contacting AVTECH Technical Support.)

Once in the downloads section, navigate to the monitor's section. Save the firmware update file but DO NOT unzip/decompress the file if it arrives as a .zip or .upd file.


DEVICE DISCOVERY UTILITY: Open Device Discovery and click the 'Search' button. 



Select the monitor that is to be updated and click the 'Update' button.

 


Follow the prompts to specify the location of the Firmware Update file for the monitor and click the 'Upload' button.

 



DEVICE MANAGER: Open Device ManageR and select the monitor from the Device Status list or click on the unit's information in the middle of the page.



Click the 'Update Firmware' button.



Click 'Browse'.



Select the appropriate file and click 'Open'.



Click the 'Update' button to begin the firmware update process.



When the firmware update process completes, the unit will automatically reboot to apply the update.
If you experience an issue during this process, please feel free to contact the Technical Support Team by submitting a support ticket.

How To Use The Trace Feature On A Room Alert Or TemPageR Device

The tracing feature is a very useful tool that can be used to assist in troubleshooting issues with your Room Alert or TemPageR device.

To enable tracing on your unit, follow these steps:

       1.   Access the 'Advanced' tab of the 'Settings' page.


  

       2.   In the 'Trace Configuration' section, ensure that the 'Enable Tracing' check box is checked. The tracing port is 143 by default. You do not need to change this unless you know port 143 will be blocked by your network for some reason. After making changes in this section, click the 'Accept Changes' button at the bottom of the screen, then the 'Save Settings' button on the left hand side of the screen.




To generate a trace from your device you will want to enter the following command into a Windows command prompt: 'telnet -f c:\tracefile.txt <IP of unit> <trace port #>' then press the <Enter> key. Where 'IP of unit' is the IP address of your Room Alert or TemPageR device and 'trace port #' is the configured trace port (143 by default). So the command might look something like this: 'telnet -f c:\tracefile.txt 192.168.33.100 143'. This command will capture your trace data directly to a text file named 'tracefile.txt' in the C: directory.

Please note that Windows 7 and Vista have disabled the Telnet client by default. If you get an error saying 'telnet is not recognized as an internal or external command, operable program or batch file' you will need to enable it by going to 'Start', 'Control Panel', 'Programs And Features', 'Turn Windows Features On Or Off' then checking the 'Telnet Client' row and clicking 'OK'.


At times, it may be useful or necessary for our engineers to review a trace from a Room Alert or TemPageR device and we may request you send us the results of a trace. If you are requested to send a trace in by one of our technical support specialists, or if you feel it will be helpful before being asked, simply attach the file created by the command given above to an email and send it to us at 'Support@AVTECH.com'.

One example of how to use the tracing feature is for troubleshooting email issues with your device. To troubleshoot email issues using the trace feature, launch the trace window using the process described above. Once you have successfully connected to the trace, browse to the 'SMTP Email' tab on the 'Settings' page. Try sending an email by clicking the 'Send Test Email' button at the bottom of the SMTP Email tab. You should see the attempts by the Room Alert or TemPageR device to connect to the configured mail server in the trace output window. If there are any issues occurring with the email process, you should see corresponding errors displayed in the output window which should point you in the right direction as to what might be causing any issue.

My Room Alert Or TemPageR Monitor Is Not Discoverable Or Accessible On My Network. How Do I Discover My Room Alert Or TemPageR?

Device ManageR and the Device Discovery Utility use a broadcast scan on UDP port 30718 to automatically locate AVTECH monitors on a network.
AVTECH recommends the following for initial product discovery:
 - DHCP Enabled on network.
 - UDP Broadcasts allowed at a computer and network level.
Please Note Before Beginning:
 - The network cable must be plugged in to the Room Alert or TemPageR monitor and the switch or computer before power is connected. This ensures that the initial DHCP request will be sent successfully when power is connected.

 - If the monitor has been assigned a static IP address that is invalid for the current IP address range of the network, please proceed to step 3 of this guide.
 - When the Room Alert or TemPageR monitor is powered on and plugged into a network, please check the current status of the Network Jack's lights as these lights are used to determine the current state of the monitor. The left link light should be a solid green color while the right light should be a flashing green or orange. If these lights display any other patterns than this, please skip to step 5 of this guide.

To begin discovering the monitor's IP address, please follow the instructions below starting at step 1.

1. Both Device ManageR and the Device Discovery Utility have a manual discovery feature that uses a TCP scan on TCP port 30718. This feature is helpful if the network range or specific IP address of the monitor is known. 

 - To access this feature using Device ManageR, click the 'Advanced Discovery Options...' button under 'Device Status' in the left menu. Click the 'Manually Add Device/s Via IP Address' button and select either 'Single IP Address' or 'Range Of IP Addresses'. Insert the desired IP address or range and click the 'Begin Scan...' button.

 

 - To access this feature using the Device Discovery Utility, click the 'Advanced Discovery' button located under the 'Search' button. Then, select either 'Single IP Address' or 'Range IP Addresses' and enter the single IP address or IP address range. Start the scan using the 'Begin Scan' button.


2. DHCP Enabled On Network – All AVTECH monitors are initially set to obtain an IP address automatically using DHCP. DHCP must be enabled on the network for the monitor to receive a valid IP address. If DHCP is not enabled, the monitor will default to an auto IP address in the 169.254.xxx.xxx range. At this IP address, the router or system firewalls may not allow discovery because the IP address is outside of the valid network IP range. Valid assignment could potentially be hindered by a managed switch even if DHCP is enabled. If DHCP assignment is delayed in the managed switch, the DHCP request sent from the monitor can timeout and default to a 169.254.xxx.xxx Auto IP address.

 - If DHCP is enabled on the network, there is a chance the DHCP server has already assigned a valid IP address even though the monitor is not discoverable. If the manual discovery option from step 1 does not discover the monitor, the IP address can sometimes be obtained by checking the DHCP server for the MAC address of the monitor.

 - If the IP address can be verified by checking the DHCP server and the IP address is in range of the network, it can be added to Device ManageR and the Device Discovery Utility using the manual scan feature from step 1. This IP address can additionally be accessed by directly by typing the IP address in a web browser. 

 - It is also possible to create a DHCP reserved IP address on a server. Doing this and recycling the power on the monitor should allow the IP address to be assigned by the DHCP server. If this process is unknown or unable to be completed personally, please consult the local Network Administrator. Otherwise, continue to the next step.

3. If the IP address of the monitor is still not discoverable, AVTECH recommends connecting the unit directly to a computer or laptop using a cross-over Ethernet cable or spare network hub.

 - Before disconnecting a computer or laptop to be used from the current network, be sure that the Device Discovery utility is installed along with a protocol analyzer (packet sniffer) application. If a preferred protocol analyzer application is unknown or not installed, a free utility called 'Wireshark' can be installed from http://www.wireshark.org/.

 - Begin by assigning a static IP address to the computer's network card, then connect the monitor via cross-over Ethernet cable or spare network hub to the computer. Lastly, plug in the power to the Room Alert or TemPageR monitor to begin the connection process. 

 - Attempt discovery using the Device Discovery utility by clicking the 'Set IP' button. The 'Set IP' button can set an IP via the MAC address which can be found at the bottom of any Room Alert or TemPageR monitor's case. Follow the procedure as prompted by Device Discovery and remember to set the IP to a valid IP address that is within the same subnet as the IP set for the computer's network card. After doing this, the monitor should be accessible via the Device Discovery list or by directly entering the newly set IP address in a web browser.

4. DHCP alternative to the static IP settings above: While still on the cross-over cable direct connection between the computer and monitor, the Room Alert or TemPageR may also be reset back to initial DHCP factory defaults via the reset button on the back panel of the monitor (if applicable). 

- For TemPageR3E, Room Alert 4E, 11E: Hold the reset button in for 10-15 seconds until the top left LED on the Ethernet jack blinks. A reset has occurred when this light on the ethernet jack goes out, then reappears 1 second later. Please release the reset button after this occurs.

 - For Room Alert 24E, 26W, 32E/W: Hold the reset button in for 10-15 seconds and watch the 3 main status lights on the front of the monitor. A reset has occurred as the front 3 status lights cycle through red and then finish cycling. Please release the reset button after this occurs.

 - With the unit now set back to DHCP factory defaults, change the laptop's network card settings to automatically obtain an IP address as opposed to specifying a static IP. Start up the Device Discovery utility and click 'Search' to locate the monitor.

 - If the Device Discovery utility methods are not working and the above steps have not located the monitor, start the protocol analyzer application, Begin packet capture and recycle the power on the monitor. Look for incoming packets coming from the MAC address of the monitor (located on a sticker on the bottom of the monitor's case or on the back of a rack mount kit if applicable). One of these packets should contain the source IP address of the monitor. Once this IP address has been obtained, configure a static IP address on the laptop or computer that is within a valid network range in relation to the IP address assigned to the unit as in step 3 (i.e. IP of unit: 192.168.2.3 - IP for computer or laptop: 192.168.2.4). The monitor can now be directly accessed by entering the IP address in a web browser.

5. If the above trials have been unsuccessful in discovering the IP address of the unit, please email Support@AVTECH.com with the packet capture obtained in step 4 attached to the email.

The Activity LED is flashing orange on my Room Alert unit and it does not appear on the network. How can I resolve this?

In the event that your Room Alert unit is inaccessible on your network, the Link LED (LED on left side of Ethernet port) on your unit is unlit and the Activity LED (LED on right side of Ethernet port) on your unit is flashing orange, please follow the instructions below to recover your unit.

  1. Verify that you have version 3.1.1 or later of the AVTECH Device Discovery Utility installed on a system with only 1 Ethernet Adapter.

  2. Obtain your unit's Firmware Update file from the download section for that specific model. Save it to your desktop and DO NOT unzip the Firmware Update file if it arrives as a .zip file.

  3. Disconnect the Ethernet cable from the system you are currently working on and use a crossover Ethernet cable to connect the system to the hardware unit.

  4. If your system does not have a static IP address set, temporarily configure it with a static IP address for the recovery process.

  5. Temporarily disable any firewalls or anti-virus programs that might block the firmware recovery packets.

  6. Reconnect the power to the hardware unit and start the AVTECH Device Discovery Utility.

  7. Click the 'OK' button on the dialog that appears and replace the 'XX-XX-XX' in the next dialog with the last three segments of the MAC address of your hardware unit. The MAC address of your hardware unit will be listed on a label located on the bottom of the hardware unit.

  8. Follow the instructions on the next dialog and recycle the power on your hardware unit.

  9. When the 'Open File' dialog opens, navigate to the location where you saved the Firmware Update file, select it and click the 'Upload' button.

  10. When the 'Set IP' dialog appears, enter a valid static IP address, gateway IP address, subnet mask and DNS server IP address in relation to the static IP settings you configured the system you are working on with.

  11. The IP address information you entered will be uploaded to your hardware unit and your hardware unit will be rebooted. Upon reboot, the full Firmware Update file will be uploaded to your hardware unit. If you initially had your unit set to DHCP before performing these steps, select your hardware unit in the AVTECH Device Discovery Utility, click the 'Set IP' button and enter '0.0.0.0' in the 'Set IP' dialog. Click 'OK' and wait for your unit to reboot. If a static IP address, gateway IP address, subnet mask and DNS server IP address were originally assigned to your hardware unit, select your unit in the AVTECH Device Discovery Utility and click the 'Set IP' button. Enter the original static IP address, gateway IP address, subnet mask and DNS server IP address assigned to the hardware unit. Click 'OK' and wait for your unit to reboot.

  12. Unplug your hardware unit and disconnect the crossover Ethernet cable.

  13. Install your unit in it's previous location by plugging in the Ethernet cable first and then powering on the hardware unit.

If you experience an issue during this process, please feel free to contact our technical support department by submitting a support ticket.

Trouble/Issues Accessing the 'Downloads' Section of AVTECH.com

The 'Downloads' section on AVTECH.com is AVTECH's only source of Device ManageR, Room Alert/TemPageR firmware updates, Software updates, MIB files, Device ManageR plugins, and the Device Discovery utility. To gain access to this section, AVTECH will issue a username and password to all contacts that are employed by organizations that have purchased a Room Alert or TemPageR environmental monitor.

If you have been previously issued a username and password from AVTECH: When attempting to log on to the AVTECH Downloads section, make sure that the password being used is entered correctly as the password is case sensitive. Please note the email address that was initially given to AVTECH at the time of registration is the only email that can be used to log on to this section.

If the initial password for the 'Downloads' section of AVTECH.com has been lost or forgotten, go to AVTECH.com/Downloads/ and select the 'Forgot/Reset Password' link below the login section. Enter the registered email address in the new screen and select 'Submit'. If the email address matches a record that was previously created in AVTECH's registry, an email will be sent with the required password.

If you are able to access AVTECH's downloads, but your downloads are expired: The specific downloads provided to your organization are regulated by AVTECH's Maintenance, Support, and Update Service (MSUS). MSUS is an annually renewed service for each of the Room Alert and TemPageR units owned by the organization. If MSUS needs to be renewed, please send an email to RenewMSUS@AVTECH.com including the organization's name and your personal contact information. For more information on MSUS, please refer to this page link:  http://www.AVTECH.com/PDFs/AVTECH_MSUS_Explained.pdf 

If you are a new contractor or temporary hire and require access to AVTECH Downloads: Please provide the following information in an email to 'Support@AVTECH.com' along with a short message explaining the need for access. Once approved, you will be registered as a contractor or temporary hire directly under the organization that owns the Room Alert or TempageR product. Please include the following information in this email:

Organization Name
Organization Address
Organization Phone Number
Your Full Name
Direct Phone Number
Email Address
Job Title
Summary Of Work To Be Completed

For all other issues accessing the 'Downloads' section of AVTECH.com, send an email to 'Support@AVTECH.com' and we will be able to provide further assistance.


Status Screen

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.



Settings Screen

I am unable to get my Room Alert or TemPageR monitor to send email alerts properly. How do I send email alerts directly from the monitor's web page?

Email alerts from the Room Alert or TemPageR monitors are sent using anonymous, unauthenticated SMTP email on TCP port 25. If email notifications are not received, first verify the email settings in the 'SMTP Email' section of the 'Settings' page.
  1. Mail Server Port: This port is typically port 25 but can be different based on personal mail server settings and network preferences. Please check with the mail server administrator for the exact port number.
  2. Mail Server: If the monitor is configured to obtain an IP address using DHCP, enter the specific IP address of the mail server in the ‘Mail Server Address’ field. If the monitor is configured with a static IP address, the DNS name for the mail server can be entered in this field. For initial testing purposes, enter an email address from the same domain as the mail server in the ‘Email Recipients’ field. For example, if the domain name is 'Example.com', be sure the email used to test is from the same domain (i.e. YourEmail@Example.com).
  3. Return Address: To finish the configuration, enter the same email address in the ‘Return Address (From)’ field. Using the same domain name minimizes the risk that security settings on the email server would prevent the message from being delivered.
  4. Display URL: The display URL is a URL that will be at the bottom of your received email alert. This URL is here to allow quick link/access to any URL after an alert is triggered. This URL can be a link to any web page you would like, but typically we assume that quick access to your Room Alert's web page is necessary here. Type in the IP address of the monitor or any other web page that is desired in this field.
  5. Authentication: This field is optional because not all mail servers require authentication. Please check with the mail server administrator if there are any questions about this field. The Username and Password would typically be the same credentials used to log on to a mail server directly.
  6. Email Recipients: List the email addresses that the alert will be sent to and separate multiple addresses by a comma. For example, John@Example.com,James@Example.com,Steve@Example.com Please note that due to limited flash memory on the Room Alert and TemPageR monitors, the Email Recipients field is only 79 characters long. For more space, AVTECH recommends creating a distribution list in the email server itself or for unlimited email entries and advanced/custom alerting, please follow this link for AVTECH Device ManageR: http://avtech.com/Products/Device_ManageR/


     Once the email settings are configured, click the ‘Test Email’ button and check the email account(s) for the test email. If the message is not received, first check any spam filter that may be in place. If the test email cannot be found, it could be blocked by the mail server. Be sure the mail server is configured to allow 'SMTP Relaying' from the IP address of the monitor. Also, be sure the Room Alert or TemPageR is on the email server's 'whitelist' to prevent messages from being filtered or blocked as spam. If messages from the monitor continue to be blocked by the mail server, contact the mail server administrator to see if the mail server logs can be reviewed to determine why the messages are being blocked.

If you have followed the steps above but are still unable to receive email alerts, please contact our Technical Support Team by
submitting a support ticket.

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.


What is the Default 'Settings' Screen Password on Room Alert or TemPageR?

The 'Settings' screen of Room Alert and TemPageR is password protected to prevent unauthorized users from modifying the settings. By default, there is no user name and password configured to access the 'Settings' screen of a Room Alert or TemPageR. With the User Name and Password fields left blank, select 'OK' to access the 'Settings' screen.

If you have previously configured a password for the device, leave the User Name field blank and enter your password in the 'Password' field, then select 'OK' to access the 'Settings' screen.

When I try to access the 'Settings' screen on my Room Alert or TemPageR, my web page flashes or does not load properly. How do I access the 'Settings' screen?

The 'Settings' screen on the Room Alert and TemPageR units consist of a Java applet that accesses the device on UDP port 30718 and 30719. To view the 'Settings' applet, Java software must be installed in the browser being used to access the web interface. Java software can be installed at Java.com. Next, verify that you do not have UDP port 30718 and 30719 blocked on any device located between the system or server you are currently using and your unit. If this is the case, unblock the port and try accessing the 'Settings' screen again.

The 'Settings' screen consists of an HTML form that submits and retrieves data using Java script and normal http 'get' and 'post' requests. When the 'Settings' screen flashes or doesn't load properly, we have noticed that a typical cause would be certain security devices such as Microsoft's ISA proxy server or antivirus programs that are implemented on your network. If you can, please check your network and see if any of these items are in fact implemented and are interfering with communications. In order for the 'Settings' tab to open, our program runs certain commands and pages in the background which conflict with some antivirus program's or Internet Security Server's configured settings.

You can attempt to check these pages by trying the following two addresses   http://<IP of unit>/secure/setuprec.xml  and  http://<IP of unit>/secure/unitinfo.xml  Once you have called upon them, please right click and 'view source' on them. If you notice anything strange here or are receiving an error message we would appreciate seeing them for reference. You can  take screen shots or make a text copy of the contents and send them to us here at Support@AVTECH.com

To resolve this issue, typically we see that a proxy server or antivirus is blocking background XML HTTP requests. A typical fix is to allow or add exceptions to the Room Alert Or TemPageR IP address in all security implementations.

If you are still having difficulty, please follow the steps below and attempt to access the 'Settings' screen after completing each one.

  1. Completely close the web browser you are using and reload. If you have any alternate web browsers, please attempt to access the settings page with these browsers as well.

  2. Recycle the power on your unit.

  3. Reupload/update the firmware on your Room Alert or TemPageR unit. For complete instructions on doing so, please follow this link:  http://avtech.com/Support/index.php?action=kb&article=40

If steps 1-3 do not resolve the issue, we suggest disconnecting your device from your network and attempt to connect to it via a laptop and Device Discovery through a crossover cable. When using a cross over cable, you should plug the crossover cable in to the device and the PC first, then plug in the power to the unit. Remember to set up your laptop's network card to be within the same subnet range as your Room Alert and TemPageR unit, then attempt to discover your unit with the Device Discovery Unit. For more information on discovering your unit, please follow this link. http://AVTECH.com/Support/index.php?action=kb&article=73 If you have discovered your unit and are able to access your unit's 'Settings' page, this means that one of the previous topics discussed is most likely still an issue on your network. If you have successfully connected via a crossover cable and are still unable to properly access the settings page, please feel free to contact our technical support staff by submitting a support ticket.


Sensors

Can I add additional sensors to my Room Alert or TemPageR after my initial order?

Yes. Many environmental sensors are available for purchase at any time from AVTECH such as temperature, humidity, power, flood, smoke, motion, room entry and many more. A list of these sensors can be found here: http://avtech.com/Products/Monitor_-_Sensors/ For additional information and purchasing of our environmental sensors, please contact an AVTECH Senior Product Specialist at 888.220.6700.

External Digital Temperature and Humidity Sensor Placement Suggestions

Placing Digital Temperature Sensors in the right locations is essential for reliable monitoring of the environment. Without proper placement, the most relevant temperature data may not be obtained.

 - It is recommended that the Room Alert or TemPageR unit itself is placed near the equipment that you wish to monitor as the standard cable length for Digital Temperature Sensors is 25 feet. External digital sensors may be extended up to 100 feet in length with the use of cable extensions found here: http://avtech.com/Products/Monitor_-_Accessories/Extended_Cable_Coupler.htm.

 - Measuring the temperature of the aisles in the data center at multiple height levels can give an early indication of a potential temperature problem. For consistent and reliable temperature monitoring, place a temperature sensor at least every 25 feet in each aisle with sensors placed closer together if high temperature equipment like blade servers are in use. It is important to know that data center temperatures can drastically vary in nearby locations depending on height from the floor, the specific equipment that is present, and how much equipment is present.

 - AVTECH recommends installing TemPageR and Room Alert rack units at the top of each rack in the data center as the heat generated by the components in the rack rises up to the unit which will give the most accurate readings, TemPageR and Room Alert units will be able to provide an early warning and notify staff for temperature issues before critical systems, servers or network equipment is damaged. You may wish to consider purchasing additional AVTECH devices and sensors to maximize the area that can be monitored.

 - In addition, avoid locating your sensor cables near large electromagnetic devices and florescent lights.

 - Place your sensor cables so that they are located in a safe place away from frequent foot traffic or constant disruption from moving parts.

Click here to review an article entitled Recommended Computer Room Temperature and Humidity. For additional information, please visit ASHRAE (the American Society of Heating, Refrigerating, and Air-Conditioning Engineers) to view a document called "Thermal Guidelines for Data Processing Environments" to assist you in planning how to best place your Digital Temperature Sensors in your organization's environment.

How do I extend my Digital Sensor Cable longer than the supplied 25 feet?

By design, external digital sensor cables are 25 feet in length and can be extended up to a supported100 feet in total length.

To extend the sensor cable, you will need a RJ-11 cable with coupler which is available from AVTECH Software.

To order these cables, contact your Product Specialist or click here to purchase on-line.

To extend an external digital sensor cable:

  1. Remove the external digital sensor to be extended by unplugging its RJ-11 cable from the front of the unit.
  2. Using a 25 foot RJ-11 cable with coupler, insert the RJ-11 connector into the AVTECH unit’s external sensor port.
  3. Plug the RJ-11 connector on the sensor cable to the extension cable.

If you wish to extend the sensor up to the supported 100 feet in length, multiple RJ-11 extension cables can be connected using the methods above.

It is important to note that AVTECH does not recommend extending a cable to a greater distance than 100 feet and does not support splicing or cutting into existing wires to shorten or lengthen the provided cable.



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.

Temperature Conversion Formulas

[F = Fahrenheit, C = Celsius]


To Convert Celsius To Fahrenheit

F = 1.8C + 32


To Convert Fahrenheit To Celsius

C = F – 32
          1.8

Why is the internal temperature reading on my Room Alert or TemPageR monitor higher than the external sensors?

The internal temperature sensor measures the ambient air temperature inside the Room Alert or TemPageR device. Under normal operating conditions, the device can generate some heat internally that can cause the internal sensor to register a temperature that is a few degrees higher than the external sensors. This is normal and especially holds true for any rack mounted monitors, as the temperature inside of a rack is typically warmer than the surrounding environment where the external temperature sensors are located. All sensor readings, including internal sensors, can be calibrated using the 'Settings' page of the monitor's firmware.

Click the 'Settings' link and go to the 'Sensors' tab. If desired, enter a integer value in the 'Adjust' field to calibrate the internal sensor reading to match the readings from the external sensors. For example, if the internal temperature is two (2) degrees higher than the external sensor, put a '-2' in the 'Adjust' field for Sensor 1.

If your Adjust field value seems to be different than what you initially saved it as, it is most likely due to the conversion from Celsius to Fahrenheit. For more information, please follow this link: http://AVTECH.com/Support/index.php?action=kb&article=119

If you have any further questions, please feel free to contact our Technical Support Team by submitting a support ticket.

Room Alert 4E & Signal Tower

Can I log sensor data on my Room Alert or TemPageR?

     AVTECH's Device ManageR software can log all sensor data for each and every Room Alert and TemPageR monitor connected to a network. Device ManageR runs as a Windows Service and uses the host system's hard drive to store logs in an SQL database. Device ManageR is available for free to all customers who have purchased a Room Alert or TemPageR monitor and have current Maintenance, Support, and Update Service (MSUS) with AVTECH. Device ManageR's logging is a standard feature along with graphing, unlimited/custom alerts, and much more. Device ManageR can be downloaded from the Downloads section at http://AVTECH.com/Downloads/ For more information on Device ManageR, please follow this link: http://AVTECH.com/Products/Device_ManageR/

Configuring Device ManageR To Toggle Lights & Audio On A Room Alert Signal Tower Module

Before starting, please ensure that the correct Signal Tower module is selected on the Room Alert 4E's 'Alarm Options' page of the 'Settings' tab. It is recommend that an external digital sensor be connected to the unit if an alarm condition is to be simulated. This will allow configured Alerts to be tested to ensure that they are working as expected.

Click on the ' Alerts/Tasks ' tab in the Navigation Pane of the Device ManageR interface and expand 'Actions' from the displayed options.  Two Actions need to be created - one to turn the red light on, and one to turn the red light off.  Click the 'Add' button to create a new Action. 



On the 'Add New Action' window, give the Action an appropriate name.  The 'Description' field is optional.



Note that most configuration screens in Device ManageR have associated 'Help' files that you can access for additional useful reference information. Access the Help file by clicking on the green '?' .



Select the 'Toggle Room Alert 4E With Signal Tower Or Relay' option from the 'Action Type' drop-down menu.



Select a discovered Room Alert 4E unit with an attached Signal Tower Module from the 'Device' drop-down menu.



Select the 'Red Light' option from  the 'Toggle the' drop-down menu.  In the next drop-down menu, select 'On'.

Click the 'Save' button at the bottom of the window.



A second Action will need to be created to turn the red light off when the Alert clears.  Click the 'Add' button to create the second new Action.



On the 'Add New Action' window, name this Action 'Turn Red Light Off'.



In the 'Action Type' drop-down menu, select the 'Toggle Room Alert 4E With Signal Tower Or Relay' option.



Select the same discovered Room Alert 4E unit with an attached Signal Tower Module as in the previous Action from the 'Device' drop-down menu



Select the 'Red Light' option from  the 'Toggle the' drop-down menu.  In the next drop-down menu, select 'Off'.



Click 'Save' at the bottom of the window to save the new Action.

Now that these Actions are created for the Signal Tower, an Action/Notification List can be created to turn the Signal Tower on and off.  Please refer to How To Configure Action/Notification Lists In Device ManageR for more details.

Once the Action/Notification List has been created, an Alert must be configured to use the Signal Tower Actions.  Please refer to Creating An Alert In AVTECH Device ManageR for more details.  Remember that the 'Turn Red Light On' 'Action' should be used when the Alert is triggered, and the 'Turn Red Light Off' Action should be used as the Alert's 'Clear Action'.

If further assistance is required with this procedure, please initiate a support case by sending an email to our Technical Support staff at Support@AVTECH.com.

Disable Receiving SNMP Traps On Room Alert 4E

The Room Alert 4E is the only device in our product line that can receive SNMP traps from other network devices (i.e. printers, fax machines, etc.) If this is not a feature you wish to have enabled, you can follow the instructions to disable receiving traps on the Room Alert 4E.

1. Browse to your device's 'Settings' screen



2. Click on the option labeled 'SNMP'



3. Under the heading, 'SNMP Trap Receiving Configuration,' change 'Trap Receive IP 1' to '1.1.1.1' from '0.0.0.0'



4. Click the 'Accept Changes' button



5. Click the 'Save Settings' option



This will cause the Room Alert 4E to only receive SNMP traps from devices in the IP range of 1.1.1.1.

How Do I Update The Firmware On My Room Alert Or TemPageR Monitor?

- Verify that you have either the AVTECH Device Discovery Utility or Device ManageR software installed on a host machine that has network visibility to the Room Alert or TemPageR monitor that is to be updated.
 - Verify that the software being used is the most current version of AVTECH Device Discovery or Device ManageR. The most current versions can be obtained via the 'Downloads' section of AVTECH.com for current MSUS subscribers.


Note which firmware version the Room Alert or TemPageR is currently running by checking the monitor's 'Status' page. The monitor's version will be in the top right hand corner.

Click here: http://avtech.com/Downloads/ and check the left side box for a list of AVTECH's released versions. If your current firmware version is older than the version listed here, please continue by logging in to the 'Downloads' section. (If you do not know your login password or if you are unsure if you  have an account, click the 'Forgot/Reset Password' link and enter your email address. If your email address is not recognized, click the 'Email Request/Inquiry' button and fill in your information. If your email address is recognized but you do not receive an email with your password, check any SPAM filter in place before contacting AVTECH Technical Support.)

Once in the downloads section, navigate to the monitor's section. Save the firmware update file but DO NOT unzip/decompress the file if it arrives as a .zip or .upd file.


DEVICE DISCOVERY UTILITY: Open Device Discovery and click the 'Search' button. 



Select the monitor that is to be updated and click the 'Update' button.

 


Follow the prompts to specify the location of the Firmware Update file for the monitor and click the 'Upload' button.

 



DEVICE MANAGER: Open Device ManageR and select the monitor from the Device Status list or click on the unit's information in the middle of the page.



Click the 'Update Firmware' button.



Click 'Browse'.



Select the appropriate file and click 'Open'.



Click the 'Update' button to begin the firmware update process.



When the firmware update process completes, the unit will automatically reboot to apply the update.
If you experience an issue during this process, please feel free to contact the Technical Support Team by submitting a support ticket.

Room Alert/TemPageR Sensor Data Not Loading

The Room Alert and TemPageR devices load the sensor data for display on the Status page using a background xml http request to a file called "getData.htm".

If sensor data is not loading, first verify that the 'getData.htm' web page is accessible by entering "http://<ip_address_of_device>/getData.htm" in the web browser location bar. 

Example 192.168.2.95/getData.htm   

You should see the following output.......





If the data fails to load, the cause can usually be traced to a proxy server or Microsoft ISA server. If your network has a proxy server or Microsoft ISA server, be sure that it is configured to ignore requests to and from Room Alert. Also verify that you do not have any local Internet security, anti-virus, or firewall applications that may be blocking, filtering or caching the background requests to this page.

A shorter test can also be used by entering in  http://ip_address_of_device/mobile.txt    Example 192.168.2.95/mobile.txt    you should see the following output....




If you see an image loading like the one above, your issue is related to either a web browser, security device/application or anti-virus program blocking requests and traffic made to the unit.  You will want to further examine  your  current security settings on your security applications and devices running on your pc and on your network.  


Please feel free to contact our Support Team at Support@AVTECH.com with any further questions.

Initial Discovery & Setup

A Device That Is Connected To A Managed Switch Is Not Accessible

Managed switches are a more powerful version of the basic network switch. They can be configured to screen traffic on certain ports or protocols and have been found to sometimes interfere with TemPageR or Room Alert communications. Because of this, a device can initially work as expected, but become inaccessible over time. Any switch that allows extra control over the traffic it sees is considered a managed switch for the purposes of this discussion. Symptoms usually observed are that a unit will initially work as expected but after a period of time will become inaccessible. In some cases, the IP address of the unit will still respond to pings. Cycling power on the unit temporarily resolves the issue.

A quick test to verify if the switch is the issue is to attach the device to a different network switch or hub. Be sure that the other switch is on the same network segment or the unit might be inaccessible. You can also connect the unit off the network with a crossover cable to see if the issue persists.

If the managed switch is found to be the cause of the issue, be sure to remove any configurations that might interfere with the traffic sent by the unit. Along with normal TCP 80 traffic, the device will send NTP requests on UDP port 123, email on TCP port 25, SNMP Traps on UDP port 161 and can be accessed via UDP port 30718.

In conjunction with this, there are a few other recommendations.

1.If your switch has a setting that will allow the port to act as an un-managed switch port, we highly recommend you enable this setting.

2.You should hard code the port speed on the switch the AVTECH device is connected to to a 100/Full Duplex setting. 

3.In addition, hard code the port speed on the AVTECH unit to 100/Full Duplex. The MTU size defines the size of data packets sent from the Room Alert or TemPageR device and might need to be modified to match settings on the managed switch.


4.Also, we recommend starting with a MTU of 1024. If your issues persist after hardcoding the port speed and setting the MTU, then adjust the MTU downward in increments of 64. Please note that the lowest allowable MTU size is 512. These settings are available on the 'Network' tab of the 'Settings' page of the Room Alert or TemPageR device. Uncheck the 'Auto Negotiate' checkbox and select the '100 MB' and 'Full Duplex' radio buttons. In the 'MTU Size' field, ensure that a value of 1024 or lower is entered. Remember, if your issues persist after applying these settings, gradually lower the MTU until you find the right size.

5. Finally, another option is to place a hub in between the Room Alert or TemPageR device and the switch, so that the unit connects to the hub and the hub connects to the switch. This way, the unit is negotiating with the hub rather than the switch and this should mitigate the issue.

How Do I Enable A Security Password On Room Alert Or TemPageR Monitors?

A password can be configured for each individual Room Alert or TemPageR to prevent unauthorized users from modifying the 'Settings' section.  Passwords should be alphanumeric and cannot include special characters or symbols.

To Configure A Password For Room Alert or TemPageR
  1. Type the IP Address of the monitor into a web browser to access the 'Status' page. (For Device ManageR, click the monitor in the 'Device Status' list, then select 'Open Web')
  2. Once the 'Status' page is displayed in the web browser, click the 'Settings' tab.
  3. Unless you have previously configured a password for the device, leave the user name and password fields blank and click 'OK'.  If you have previously created a password for the monitor, leave the user name field blank and enter the current password, then click 'OK'.
  4. When the 'Settings' screen displays, click the 'Security' button on the left side list.
  5. In this screen, enter the old password, new password, and confirm the new password. (If an old password is not set, leave this field completely blank)
  6. Click the 'Accept Changes' button at the bottom of the screen, then click the 'Save Settings' button in the left side list to reboot the monitor. The monitor will  reboot, and now require a password only to access the 'Settings' section.
To Reset An Unknown Password That Was Previously Set

All current Room Alert and TemPageR monitors feature a hard reset button on the back of the case. While the monitor is powered on and connected to an active network or crossover cable connection, please locate and hold down this reset button while watching the top left green light on the monitor's network port. This network light will go out for two seconds, then reappear to signify a complete reset. The monitor will now have factory default settings, which includes a blank password set for the 'Settings' section. Note that the unit will be configured for DHCP and any static IP set previously will need to be reconfigured.

If the monitor does not have a physical reset button, please contact AVTECH Technical Support and speak with one of our Technical Specialists.  

To contact AVTECH support, click here.

How do I set a Static IP address on my Room Alert or TemPageR?

A Static IP address can be set for your Room Alert or TemPageR unit by using the AVTECH Device Discovery Utility, AVTECH Device ManageR, or via the 'Network' section in the 'Settings' tab of the Room Alert or TemPageR web browser interface.

To set a Static IP address using the AVTECH Device Discovery Utility, open the AVTECH Device Discovery Utility and click the 'Search' button. Select the monitor you wish to assign a static IP address to and click the 'Set IP' button. Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit being updated.

To set a Static IP address using the AVTECH Device ManageR Software, open the Device ManageR software and click the monitor in the left hand 'Device Status' list. You will notice a small drop down below the currently selected monitor. Click the '-Set IP Address' button.
Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit you are updating.

To set a Static IP address using the monitor's web browser interface, enter the current IP address of your Room Alert or TemPageR monitor into the location bar of a web browser. The 'Status' page will load by default and display the current sensor values. Click the 'Settings' tab at the top of the page and the 'Network' section will load. Uncheck the 'Use DHCP' checkbox and enter the desired static IP information in the available fields. Be sure that all static IP address information is correct for the location of the monitor you are updating. To complete the changes, please click the 'Accept Changes' button at the bottom of your page and then the 'Save Settings' button on the left hand side. The monitor will now reboot and apply the new changes.

If the Room Alert or TemPageR monitor cannot be discovered or you do not know the existing IP address, a Static IP address can be set using the MAC address of the unit, which can be found on a label on the bottom of the monitors. Please open Device Discovery and click the 'Set IP' button without selecting a device from the list and follow the prompts from the AVTECH Device Discovery Utility. Alternatively, you can set a Static IP address via the MAC address of your monitor in Device ManageR.
Open Device ManageR and click the 'Advanced Discovery' button in the top left hand corner on the 'Device Status' list. This button will display a pop up that will have a 'Set IP Via MAC Address' button. From here, enter the MAC address of the monitor and the desired Static IP address.When finished, press the 'Update IP Settings' button to make the changes.

How Do I Update The Firmware On My Room Alert Or TemPageR Monitor?

- Verify that you have either the AVTECH Device Discovery Utility or Device ManageR software installed on a host machine that has network visibility to the Room Alert or TemPageR monitor that is to be updated.
 - Verify that the software being used is the most current version of AVTECH Device Discovery or Device ManageR. The most current versions can be obtained via the 'Downloads' section of AVTECH.com for current MSUS subscribers.


Note which firmware version the Room Alert or TemPageR is currently running by checking the monitor's 'Status' page. The monitor's version will be in the top right hand corner.

Click here: http://avtech.com/Downloads/ and check the left side box for a list of AVTECH's released versions. If your current firmware version is older than the version listed here, please continue by logging in to the 'Downloads' section. (If you do not know your login password or if you are unsure if you  have an account, click the 'Forgot/Reset Password' link and enter your email address. If your email address is not recognized, click the 'Email Request/Inquiry' button and fill in your information. If your email address is recognized but you do not receive an email with your password, check any SPAM filter in place before contacting AVTECH Technical Support.)

Once in the downloads section, navigate to the monitor's section. Save the firmware update file but DO NOT unzip/decompress the file if it arrives as a .zip or .upd file.


DEVICE DISCOVERY UTILITY: Open Device Discovery and click the 'Search' button. 



Select the monitor that is to be updated and click the 'Update' button.

 


Follow the prompts to specify the location of the Firmware Update file for the monitor and click the 'Upload' button.

 



DEVICE MANAGER: Open Device ManageR and select the monitor from the Device Status list or click on the unit's information in the middle of the page.



Click the 'Update Firmware' button.



Click 'Browse'.



Select the appropriate file and click 'Open'.



Click the 'Update' button to begin the firmware update process.



When the firmware update process completes, the unit will automatically reboot to apply the update.
If you experience an issue during this process, please feel free to contact the Technical Support Team by submitting a support ticket.

How To Use The Trace Feature On A Room Alert Or TemPageR Device

The tracing feature is a very useful tool that can be used to assist in troubleshooting issues with your Room Alert or TemPageR device.

To enable tracing on your unit, follow these steps:

       1.   Access the 'Advanced' tab of the 'Settings' page.


  

       2.   In the 'Trace Configuration' section, ensure that the 'Enable Tracing' check box is checked. The tracing port is 143 by default. You do not need to change this unless you know port 143 will be blocked by your network for some reason. After making changes in this section, click the 'Accept Changes' button at the bottom of the screen, then the 'Save Settings' button on the left hand side of the screen.




To generate a trace from your device you will want to enter the following command into a Windows command prompt: 'telnet -f c:\tracefile.txt <IP of unit> <trace port #>' then press the <Enter> key. Where 'IP of unit' is the IP address of your Room Alert or TemPageR device and 'trace port #' is the configured trace port (143 by default). So the command might look something like this: 'telnet -f c:\tracefile.txt 192.168.33.100 143'. This command will capture your trace data directly to a text file named 'tracefile.txt' in the C: directory.

Please note that Windows 7 and Vista have disabled the Telnet client by default. If you get an error saying 'telnet is not recognized as an internal or external command, operable program or batch file' you will need to enable it by going to 'Start', 'Control Panel', 'Programs And Features', 'Turn Windows Features On Or Off' then checking the 'Telnet Client' row and clicking 'OK'.


At times, it may be useful or necessary for our engineers to review a trace from a Room Alert or TemPageR device and we may request you send us the results of a trace. If you are requested to send a trace in by one of our technical support specialists, or if you feel it will be helpful before being asked, simply attach the file created by the command given above to an email and send it to us at 'Support@AVTECH.com'.

One example of how to use the tracing feature is for troubleshooting email issues with your device. To troubleshoot email issues using the trace feature, launch the trace window using the process described above. Once you have successfully connected to the trace, browse to the 'SMTP Email' tab on the 'Settings' page. Try sending an email by clicking the 'Send Test Email' button at the bottom of the SMTP Email tab. You should see the attempts by the Room Alert or TemPageR device to connect to the configured mail server in the trace output window. If there are any issues occurring with the email process, you should see corresponding errors displayed in the output window which should point you in the right direction as to what might be causing any issue.

My Room Alert Or TemPageR Monitor Is Not Discoverable Or Accessible On My Network. How Do I Discover My Room Alert Or TemPageR?

Device ManageR and the Device Discovery Utility use a broadcast scan on UDP port 30718 to automatically locate AVTECH monitors on a network.
AVTECH recommends the following for initial product discovery:
 - DHCP Enabled on network.
 - UDP Broadcasts allowed at a computer and network level.
Please Note Before Beginning:
 - The network cable must be plugged in to the Room Alert or TemPageR monitor and the switch or computer before power is connected. This ensures that the initial DHCP request will be sent successfully when power is connected.

 - If the monitor has been assigned a static IP address that is invalid for the current IP address range of the network, please proceed to step 3 of this guide.
 - When the Room Alert or TemPageR monitor is powered on and plugged into a network, please check the current status of the Network Jack's lights as these lights are used to determine the current state of the monitor. The left link light should be a solid green color while the right light should be a flashing green or orange. If these lights display any other patterns than this, please skip to step 5 of this guide.

To begin discovering the monitor's IP address, please follow the instructions below starting at step 1.

1. Both Device ManageR and the Device Discovery Utility have a manual discovery feature that uses a TCP scan on TCP port 30718. This feature is helpful if the network range or specific IP address of the monitor is known. 

 - To access this feature using Device ManageR, click the 'Advanced Discovery Options...' button under 'Device Status' in the left menu. Click the 'Manually Add Device/s Via IP Address' button and select either 'Single IP Address' or 'Range Of IP Addresses'. Insert the desired IP address or range and click the 'Begin Scan...' button.

 

 - To access this feature using the Device Discovery Utility, click the 'Advanced Discovery' button located under the 'Search' button. Then, select either 'Single IP Address' or 'Range IP Addresses' and enter the single IP address or IP address range. Start the scan using the 'Begin Scan' button.


2. DHCP Enabled On Network – All AVTECH monitors are initially set to obtain an IP address automatically using DHCP. DHCP must be enabled on the network for the monitor to receive a valid IP address. If DHCP is not enabled, the monitor will default to an auto IP address in the 169.254.xxx.xxx range. At this IP address, the router or system firewalls may not allow discovery because the IP address is outside of the valid network IP range. Valid assignment could potentially be hindered by a managed switch even if DHCP is enabled. If DHCP assignment is delayed in the managed switch, the DHCP request sent from the monitor can timeout and default to a 169.254.xxx.xxx Auto IP address.

 - If DHCP is enabled on the network, there is a chance the DHCP server has already assigned a valid IP address even though the monitor is not discoverable. If the manual discovery option from step 1 does not discover the monitor, the IP address can sometimes be obtained by checking the DHCP server for the MAC address of the monitor.

 - If the IP address can be verified by checking the DHCP server and the IP address is in range of the network, it can be added to Device ManageR and the Device Discovery Utility using the manual scan feature from step 1. This IP address can additionally be accessed by directly by typing the IP address in a web browser. 

 - It is also possible to create a DHCP reserved IP address on a server. Doing this and recycling the power on the monitor should allow the IP address to be assigned by the DHCP server. If this process is unknown or unable to be completed personally, please consult the local Network Administrator. Otherwise, continue to the next step.

3. If the IP address of the monitor is still not discoverable, AVTECH recommends connecting the unit directly to a computer or laptop using a cross-over Ethernet cable or spare network hub.

 - Before disconnecting a computer or laptop to be used from the current network, be sure that the Device Discovery utility is installed along with a protocol analyzer (packet sniffer) application. If a preferred protocol analyzer application is unknown or not installed, a free utility called 'Wireshark' can be installed from http://www.wireshark.org/.

 - Begin by assigning a static IP address to the computer's network card, then connect the monitor via cross-over Ethernet cable or spare network hub to the computer. Lastly, plug in the power to the Room Alert or TemPageR monitor to begin the connection process. 

 - Attempt discovery using the Device Discovery utility by clicking the 'Set IP' button. The 'Set IP' button can set an IP via the MAC address which can be found at the bottom of any Room Alert or TemPageR monitor's case. Follow the procedure as prompted by Device Discovery and remember to set the IP to a valid IP address that is within the same subnet as the IP set for the computer's network card. After doing this, the monitor should be accessible via the Device Discovery list or by directly entering the newly set IP address in a web browser.

4. DHCP alternative to the static IP settings above: While still on the cross-over cable direct connection between the computer and monitor, the Room Alert or TemPageR may also be reset back to initial DHCP factory defaults via the reset button on the back panel of the monitor (if applicable). 

- For TemPageR3E, Room Alert 4E, 11E: Hold the reset button in for 10-15 seconds until the top left LED on the Ethernet jack blinks. A reset has occurred when this light on the ethernet jack goes out, then reappears 1 second later. Please release the reset button after this occurs.

 - For Room Alert 24E, 26W, 32E/W: Hold the reset button in for 10-15 seconds and watch the 3 main status lights on the front of the monitor. A reset has occurred as the front 3 status lights cycle through red and then finish cycling. Please release the reset button after this occurs.

 - With the unit now set back to DHCP factory defaults, change the laptop's network card settings to automatically obtain an IP address as opposed to specifying a static IP. Start up the Device Discovery utility and click 'Search' to locate the monitor.

 - If the Device Discovery utility methods are not working and the above steps have not located the monitor, start the protocol analyzer application, Begin packet capture and recycle the power on the monitor. Look for incoming packets coming from the MAC address of the monitor (located on a sticker on the bottom of the monitor's case or on the back of a rack mount kit if applicable). One of these packets should contain the source IP address of the monitor. Once this IP address has been obtained, configure a static IP address on the laptop or computer that is within a valid network range in relation to the IP address assigned to the unit as in step 3 (i.e. IP of unit: 192.168.2.3 - IP for computer or laptop: 192.168.2.4). The monitor can now be directly accessed by entering the IP address in a web browser.

5. If the above trials have been unsuccessful in discovering the IP address of the unit, please email Support@AVTECH.com with the packet capture obtained in step 4 attached to the email.

Trouble/Issues Accessing the 'Downloads' Section of AVTECH.com

The 'Downloads' section on AVTECH.com is AVTECH's only source of Device ManageR, Room Alert/TemPageR firmware updates, Software updates, MIB files, Device ManageR plugins, and the Device Discovery utility. To gain access to this section, AVTECH will issue a username and password to all contacts that are employed by organizations that have purchased a Room Alert or TemPageR environmental monitor.

If you have been previously issued a username and password from AVTECH: When attempting to log on to the AVTECH Downloads section, make sure that the password being used is entered correctly as the password is case sensitive. Please note the email address that was initially given to AVTECH at the time of registration is the only email that can be used to log on to this section.

If the initial password for the 'Downloads' section of AVTECH.com has been lost or forgotten, go to AVTECH.com/Downloads/ and select the 'Forgot/Reset Password' link below the login section. Enter the registered email address in the new screen and select 'Submit'. If the email address matches a record that was previously created in AVTECH's registry, an email will be sent with the required password.

If you are able to access AVTECH's downloads, but your downloads are expired: The specific downloads provided to your organization are regulated by AVTECH's Maintenance, Support, and Update Service (MSUS). MSUS is an annually renewed service for each of the Room Alert and TemPageR units owned by the organization. If MSUS needs to be renewed, please send an email to RenewMSUS@AVTECH.com including the organization's name and your personal contact information. For more information on MSUS, please refer to this page link:  http://www.AVTECH.com/PDFs/AVTECH_MSUS_Explained.pdf 

If you are a new contractor or temporary hire and require access to AVTECH Downloads: Please provide the following information in an email to 'Support@AVTECH.com' along with a short message explaining the need for access. Once approved, you will be registered as a contractor or temporary hire directly under the organization that owns the Room Alert or TempageR product. Please include the following information in this email:

Organization Name
Organization Address
Organization Phone Number
Your Full Name
Direct Phone Number
Email Address
Job Title
Summary Of Work To Be Completed

For all other issues accessing the 'Downloads' section of AVTECH.com, send an email to 'Support@AVTECH.com' and we will be able to provide further assistance.


Status Screen

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.



Settings Screen

I am unable to get my Room Alert or TemPageR monitor to send email alerts properly. How do I send email alerts directly from the monitor's web page?

Email alerts from the Room Alert or TemPageR monitors are sent using anonymous, unauthenticated SMTP email on TCP port 25. If email notifications are not received, first verify the email settings in the 'SMTP Email' section of the 'Settings' page.
  1. Mail Server Port: This port is typically port 25 but can be different based on personal mail server settings and network preferences. Please check with the mail server administrator for the exact port number.
  2. Mail Server: If the monitor is configured to obtain an IP address using DHCP, enter the specific IP address of the mail server in the ‘Mail Server Address’ field. If the monitor is configured with a static IP address, the DNS name for the mail server can be entered in this field. For initial testing purposes, enter an email address from the same domain as the mail server in the ‘Email Recipients’ field. For example, if the domain name is 'Example.com', be sure the email used to test is from the same domain (i.e. YourEmail@Example.com).
  3. Return Address: To finish the configuration, enter the same email address in the ‘Return Address (From)’ field. Using the same domain name minimizes the risk that security settings on the email server would prevent the message from being delivered.
  4. Display URL: The display URL is a URL that will be at the bottom of your received email alert. This URL is here to allow quick link/access to any URL after an alert is triggered. This URL can be a link to any web page you would like, but typically we assume that quick access to your Room Alert's web page is necessary here. Type in the IP address of the monitor or any other web page that is desired in this field.
  5. Authentication: This field is optional because not all mail servers require authentication. Please check with the mail server administrator if there are any questions about this field. The Username and Password would typically be the same credentials used to log on to a mail server directly.
  6. Email Recipients: List the email addresses that the alert will be sent to and separate multiple addresses by a comma. For example, John@Example.com,James@Example.com,Steve@Example.com Please note that due to limited flash memory on the Room Alert and TemPageR monitors, the Email Recipients field is only 79 characters long. For more space, AVTECH recommends creating a distribution list in the email server itself or for unlimited email entries and advanced/custom alerting, please follow this link for AVTECH Device ManageR: http://avtech.com/Products/Device_ManageR/


     Once the email settings are configured, click the ‘Test Email’ button and check the email account(s) for the test email. If the message is not received, first check any spam filter that may be in place. If the test email cannot be found, it could be blocked by the mail server. Be sure the mail server is configured to allow 'SMTP Relaying' from the IP address of the monitor. Also, be sure the Room Alert or TemPageR is on the email server's 'whitelist' to prevent messages from being filtered or blocked as spam. If messages from the monitor continue to be blocked by the mail server, contact the mail server administrator to see if the mail server logs can be reviewed to determine why the messages are being blocked.

If you have followed the steps above but are still unable to receive email alerts, please contact our Technical Support Team by
submitting a support ticket.

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.


What is the Default 'Settings' Screen Password on Room Alert or TemPageR?

The 'Settings' screen of Room Alert and TemPageR is password protected to prevent unauthorized users from modifying the settings. By default, there is no user name and password configured to access the 'Settings' screen of a Room Alert or TemPageR. With the User Name and Password fields left blank, select 'OK' to access the 'Settings' screen.

If you have previously configured a password for the device, leave the User Name field blank and enter your password in the 'Password' field, then select 'OK' to access the 'Settings' screen.

When I try to access the 'Settings' screen on my Room Alert or TemPageR, my web page flashes or does not load properly. How do I access the 'Settings' screen?

The 'Settings' screen on the Room Alert and TemPageR units consist of a Java applet that accesses the device on UDP port 30718 and 30719. To view the 'Settings' applet, Java software must be installed in the browser being used to access the web interface. Java software can be installed at Java.com. Next, verify that you do not have UDP port 30718 and 30719 blocked on any device located between the system or server you are currently using and your unit. If this is the case, unblock the port and try accessing the 'Settings' screen again.

The 'Settings' screen consists of an HTML form that submits and retrieves data using Java script and normal http 'get' and 'post' requests. When the 'Settings' screen flashes or doesn't load properly, we have noticed that a typical cause would be certain security devices such as Microsoft's ISA proxy server or antivirus programs that are implemented on your network. If you can, please check your network and see if any of these items are in fact implemented and are interfering with communications. In order for the 'Settings' tab to open, our program runs certain commands and pages in the background which conflict with some antivirus program's or Internet Security Server's configured settings.

You can attempt to check these pages by trying the following two addresses   http://<IP of unit>/secure/setuprec.xml  and  http://<IP of unit>/secure/unitinfo.xml  Once you have called upon them, please right click and 'view source' on them. If you notice anything strange here or are receiving an error message we would appreciate seeing them for reference. You can  take screen shots or make a text copy of the contents and send them to us here at Support@AVTECH.com

To resolve this issue, typically we see that a proxy server or antivirus is blocking background XML HTTP requests. A typical fix is to allow or add exceptions to the Room Alert Or TemPageR IP address in all security implementations.

If you are still having difficulty, please follow the steps below and attempt to access the 'Settings' screen after completing each one.

  1. Completely close the web browser you are using and reload. If you have any alternate web browsers, please attempt to access the settings page with these browsers as well.

  2. Recycle the power on your unit.

  3. Reupload/update the firmware on your Room Alert or TemPageR unit. For complete instructions on doing so, please follow this link:  http://avtech.com/Support/index.php?action=kb&article=40

If steps 1-3 do not resolve the issue, we suggest disconnecting your device from your network and attempt to connect to it via a laptop and Device Discovery through a crossover cable. When using a cross over cable, you should plug the crossover cable in to the device and the PC first, then plug in the power to the unit. Remember to set up your laptop's network card to be within the same subnet range as your Room Alert and TemPageR unit, then attempt to discover your unit with the Device Discovery Unit. For more information on discovering your unit, please follow this link. http://AVTECH.com/Support/index.php?action=kb&article=73 If you have discovered your unit and are able to access your unit's 'Settings' page, this means that one of the previous topics discussed is most likely still an issue on your network. If you have successfully connected via a crossover cable and are still unable to properly access the settings page, please feel free to contact our technical support staff by submitting a support ticket.


Sensors

Can I add additional sensors to my Room Alert or TemPageR after my initial order?

Yes. Many environmental sensors are available for purchase at any time from AVTECH such as temperature, humidity, power, flood, smoke, motion, room entry and many more. A list of these sensors can be found here: http://avtech.com/Products/Monitor_-_Sensors/ For additional information and purchasing of our environmental sensors, please contact an AVTECH Senior Product Specialist at 888.220.6700.

External Digital Temperature and Humidity Sensor Placement Suggestions

Placing Digital Temperature Sensors in the right locations is essential for reliable monitoring of the environment. Without proper placement, the most relevant temperature data may not be obtained.

 - It is recommended that the Room Alert or TemPageR unit itself is placed near the equipment that you wish to monitor as the standard cable length for Digital Temperature Sensors is 25 feet. External digital sensors may be extended up to 100 feet in length with the use of cable extensions found here: http://avtech.com/Products/Monitor_-_Accessories/Extended_Cable_Coupler.htm.

 - Measuring the temperature of the aisles in the data center at multiple height levels can give an early indication of a potential temperature problem. For consistent and reliable temperature monitoring, place a temperature sensor at least every 25 feet in each aisle with sensors placed closer together if high temperature equipment like blade servers are in use. It is important to know that data center temperatures can drastically vary in nearby locations depending on height from the floor, the specific equipment that is present, and how much equipment is present.

 - AVTECH recommends installing TemPageR and Room Alert rack units at the top of each rack in the data center as the heat generated by the components in the rack rises up to the unit which will give the most accurate readings, TemPageR and Room Alert units will be able to provide an early warning and notify staff for temperature issues before critical systems, servers or network equipment is damaged. You may wish to consider purchasing additional AVTECH devices and sensors to maximize the area that can be monitored.

 - In addition, avoid locating your sensor cables near large electromagnetic devices and florescent lights.

 - Place your sensor cables so that they are located in a safe place away from frequent foot traffic or constant disruption from moving parts.

Click here to review an article entitled Recommended Computer Room Temperature and Humidity. For additional information, please visit ASHRAE (the American Society of Heating, Refrigerating, and Air-Conditioning Engineers) to view a document called "Thermal Guidelines for Data Processing Environments" to assist you in planning how to best place your Digital Temperature Sensors in your organization's environment.

How do I extend my Digital Sensor Cable longer than the supplied 25 feet?

By design, external digital sensor cables are 25 feet in length and can be extended up to a supported100 feet in total length.

To extend the sensor cable, you will need a RJ-11 cable with coupler which is available from AVTECH Software.

To order these cables, contact your Product Specialist or click here to purchase on-line.

To extend an external digital sensor cable:

  1. Remove the external digital sensor to be extended by unplugging its RJ-11 cable from the front of the unit.
  2. Using a 25 foot RJ-11 cable with coupler, insert the RJ-11 connector into the AVTECH unit’s external sensor port.
  3. Plug the RJ-11 connector on the sensor cable to the extension cable.

If you wish to extend the sensor up to the supported 100 feet in length, multiple RJ-11 extension cables can be connected using the methods above.

It is important to note that AVTECH does not recommend extending a cable to a greater distance than 100 feet and does not support splicing or cutting into existing wires to shorten or lengthen the provided cable.



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.

Temperature Conversion Formulas

[F = Fahrenheit, C = Celsius]


To Convert Celsius To Fahrenheit

F = 1.8C + 32


To Convert Fahrenheit To Celsius

C = F – 32
          1.8

Why is the internal temperature reading on my Room Alert or TemPageR monitor higher than the external sensors?

The internal temperature sensor measures the ambient air temperature inside the Room Alert or TemPageR device. Under normal operating conditions, the device can generate some heat internally that can cause the internal sensor to register a temperature that is a few degrees higher than the external sensors. This is normal and especially holds true for any rack mounted monitors, as the temperature inside of a rack is typically warmer than the surrounding environment where the external temperature sensors are located. All sensor readings, including internal sensors, can be calibrated using the 'Settings' page of the monitor's firmware.

Click the 'Settings' link and go to the 'Sensors' tab. If desired, enter a integer value in the 'Adjust' field to calibrate the internal sensor reading to match the readings from the external sensors. For example, if the internal temperature is two (2) degrees higher than the external sensor, put a '-2' in the 'Adjust' field for Sensor 1.

If your Adjust field value seems to be different than what you initially saved it as, it is most likely due to the conversion from Celsius to Fahrenheit. For more information, please follow this link: http://AVTECH.com/Support/index.php?action=kb&article=119

If you have any further questions, please feel free to contact our Technical Support Team by submitting a support ticket.

TemPageR

Can I log sensor data on my Room Alert or TemPageR?

     AVTECH's Device ManageR software can log all sensor data for each and every Room Alert and TemPageR monitor connected to a network. Device ManageR runs as a Windows Service and uses the host system's hard drive to store logs in an SQL database. Device ManageR is available for free to all customers who have purchased a Room Alert or TemPageR monitor and have current Maintenance, Support, and Update Service (MSUS) with AVTECH. Device ManageR's logging is a standard feature along with graphing, unlimited/custom alerts, and much more. Device ManageR can be downloaded from the Downloads section at http://AVTECH.com/Downloads/ For more information on Device ManageR, please follow this link: http://AVTECH.com/Products/Device_ManageR/

How Do I Update The Firmware On My Room Alert Or TemPageR Monitor?

- Verify that you have either the AVTECH Device Discovery Utility or Device ManageR software installed on a host machine that has network visibility to the Room Alert or TemPageR monitor that is to be updated.
 - Verify that the software being used is the most current version of AVTECH Device Discovery or Device ManageR. The most current versions can be obtained via the 'Downloads' section of AVTECH.com for current MSUS subscribers.


Note which firmware version the Room Alert or TemPageR is currently running by checking the monitor's 'Status' page. The monitor's version will be in the top right hand corner.

Click here: http://avtech.com/Downloads/ and check the left side box for a list of AVTECH's released versions. If your current firmware version is older than the version listed here, please continue by logging in to the 'Downloads' section. (If you do not know your login password or if you are unsure if you  have an account, click the 'Forgot/Reset Password' link and enter your email address. If your email address is not recognized, click the 'Email Request/Inquiry' button and fill in your information. If your email address is recognized but you do not receive an email with your password, check any SPAM filter in place before contacting AVTECH Technical Support.)

Once in the downloads section, navigate to the monitor's section. Save the firmware update file but DO NOT unzip/decompress the file if it arrives as a .zip or .upd file.


DEVICE DISCOVERY UTILITY: Open Device Discovery and click the 'Search' button. 



Select the monitor that is to be updated and click the 'Update' button.

 


Follow the prompts to specify the location of the Firmware Update file for the monitor and click the 'Upload' button.

 



DEVICE MANAGER: Open Device ManageR and select the monitor from the Device Status list or click on the unit's information in the middle of the page.



Click the 'Update Firmware' button.



Click 'Browse'.



Select the appropriate file and click 'Open'.



Click the 'Update' button to begin the firmware update process.



When the firmware update process completes, the unit will automatically reboot to apply the update.
If you experience an issue during this process, please feel free to contact the Technical Support Team by submitting a support ticket.

Room Alert/TemPageR Sensor Data Not Loading

The Room Alert and TemPageR devices load the sensor data for display on the Status page using a background xml http request to a file called "getData.htm".

If sensor data is not loading, first verify that the 'getData.htm' web page is accessible by entering "http://<ip_address_of_device>/getData.htm" in the web browser location bar. 

Example 192.168.2.95/getData.htm   

You should see the following output.......





If the data fails to load, the cause can usually be traced to a proxy server or Microsoft ISA server. If your network has a proxy server or Microsoft ISA server, be sure that it is configured to ignore requests to and from Room Alert. Also verify that you do not have any local Internet security, anti-virus, or firewall applications that may be blocking, filtering or caching the background requests to this page.

A shorter test can also be used by entering in  http://ip_address_of_device/mobile.txt    Example 192.168.2.95/mobile.txt    you should see the following output....




If you see an image loading like the one above, your issue is related to either a web browser, security device/application or anti-virus program blocking requests and traffic made to the unit.  You will want to further examine  your  current security settings on your security applications and devices running on your pc and on your network.  


Please feel free to contact our Support Team at Support@AVTECH.com with any further questions.

Initial Discovery & Setup

A Device That Is Connected To A Managed Switch Is Not Accessible

Managed switches are a more powerful version of the basic network switch. They can be configured to screen traffic on certain ports or protocols and have been found to sometimes interfere with TemPageR or Room Alert communications. Because of this, a device can initially work as expected, but become inaccessible over time. Any switch that allows extra control over the traffic it sees is considered a managed switch for the purposes of this discussion. Symptoms usually observed are that a unit will initially work as expected but after a period of time will become inaccessible. In some cases, the IP address of the unit will still respond to pings. Cycling power on the unit temporarily resolves the issue.

A quick test to verify if the switch is the issue is to attach the device to a different network switch or hub. Be sure that the other switch is on the same network segment or the unit might be inaccessible. You can also connect the unit off the network with a crossover cable to see if the issue persists.

If the managed switch is found to be the cause of the issue, be sure to remove any configurations that might interfere with the traffic sent by the unit. Along with normal TCP 80 traffic, the device will send NTP requests on UDP port 123, email on TCP port 25, SNMP Traps on UDP port 161 and can be accessed via UDP port 30718.

In conjunction with this, there are a few other recommendations.

1.If your switch has a setting that will allow the port to act as an un-managed switch port, we highly recommend you enable this setting.

2.You should hard code the port speed on the switch the AVTECH device is connected to to a 100/Full Duplex setting. 

3.In addition, hard code the port speed on the AVTECH unit to 100/Full Duplex. The MTU size defines the size of data packets sent from the Room Alert or TemPageR device and might need to be modified to match settings on the managed switch.


4.Also, we recommend starting with a MTU of 1024. If your issues persist after hardcoding the port speed and setting the MTU, then adjust the MTU downward in increments of 64. Please note that the lowest allowable MTU size is 512. These settings are available on the 'Network' tab of the 'Settings' page of the Room Alert or TemPageR device. Uncheck the 'Auto Negotiate' checkbox and select the '100 MB' and 'Full Duplex' radio buttons. In the 'MTU Size' field, ensure that a value of 1024 or lower is entered. Remember, if your issues persist after applying these settings, gradually lower the MTU until you find the right size.

5. Finally, another option is to place a hub in between the Room Alert or TemPageR device and the switch, so that the unit connects to the hub and the hub connects to the switch. This way, the unit is negotiating with the hub rather than the switch and this should mitigate the issue.

How Do I Enable A Security Password On Room Alert Or TemPageR Monitors?

A password can be configured for each individual Room Alert or TemPageR to prevent unauthorized users from modifying the 'Settings' section.  Passwords should be alphanumeric and cannot include special characters or symbols.

To Configure A Password For Room Alert or TemPageR
  1. Type the IP Address of the monitor into a web browser to access the 'Status' page. (For Device ManageR, click the monitor in the 'Device Status' list, then select 'Open Web')
  2. Once the 'Status' page is displayed in the web browser, click the 'Settings' tab.
  3. Unless you have previously configured a password for the device, leave the user name and password fields blank and click 'OK'.  If you have previously created a password for the monitor, leave the user name field blank and enter the current password, then click 'OK'.
  4. When the 'Settings' screen displays, click the 'Security' button on the left side list.
  5. In this screen, enter the old password, new password, and confirm the new password. (If an old password is not set, leave this field completely blank)
  6. Click the 'Accept Changes' button at the bottom of the screen, then click the 'Save Settings' button in the left side list to reboot the monitor. The monitor will  reboot, and now require a password only to access the 'Settings' section.
To Reset An Unknown Password That Was Previously Set

All current Room Alert and TemPageR monitors feature a hard reset button on the back of the case. While the monitor is powered on and connected to an active network or crossover cable connection, please locate and hold down this reset button while watching the top left green light on the monitor's network port. This network light will go out for two seconds, then reappear to signify a complete reset. The monitor will now have factory default settings, which includes a blank password set for the 'Settings' section. Note that the unit will be configured for DHCP and any static IP set previously will need to be reconfigured.

If the monitor does not have a physical reset button, please contact AVTECH Technical Support and speak with one of our Technical Specialists.  

To contact AVTECH support, click here.

How do I set a Static IP address on my Room Alert or TemPageR?

A Static IP address can be set for your Room Alert or TemPageR unit by using the AVTECH Device Discovery Utility, AVTECH Device ManageR, or via the 'Network' section in the 'Settings' tab of the Room Alert or TemPageR web browser interface.

To set a Static IP address using the AVTECH Device Discovery Utility, open the AVTECH Device Discovery Utility and click the 'Search' button. Select the monitor you wish to assign a static IP address to and click the 'Set IP' button. Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit being updated.

To set a Static IP address using the AVTECH Device ManageR Software, open the Device ManageR software and click the monitor in the left hand 'Device Status' list. You will notice a small drop down below the currently selected monitor. Click the '-Set IP Address' button.
Follow the prompts to set a static IP address. Be sure that all static IP address information is correct for the location of the unit you are updating.

To set a Static IP address using the monitor's web browser interface, enter the current IP address of your Room Alert or TemPageR monitor into the location bar of a web browser. The 'Status' page will load by default and display the current sensor values. Click the 'Settings' tab at the top of the page and the 'Network' section will load. Uncheck the 'Use DHCP' checkbox and enter the desired static IP information in the available fields. Be sure that all static IP address information is correct for the location of the monitor you are updating. To complete the changes, please click the 'Accept Changes' button at the bottom of your page and then the 'Save Settings' button on the left hand side. The monitor will now reboot and apply the new changes.

If the Room Alert or TemPageR monitor cannot be discovered or you do not know the existing IP address, a Static IP address can be set using the MAC address of the unit, which can be found on a label on the bottom of the monitors. Please open Device Discovery and click the 'Set IP' button without selecting a device from the list and follow the prompts from the AVTECH Device Discovery Utility. Alternatively, you can set a Static IP address via the MAC address of your monitor in Device ManageR.
Open Device ManageR and click the 'Advanced Discovery' button in the top left hand corner on the 'Device Status' list. This button will display a pop up that will have a 'Set IP Via MAC Address' button. From here, enter the MAC address of the monitor and the desired Static IP address.When finished, press the 'Update IP Settings' button to make the changes.

How Do I Update The Firmware On My Room Alert Or TemPageR Monitor?

- Verify that you have either the AVTECH Device Discovery Utility or Device ManageR software installed on a host machine that has network visibility to the Room Alert or TemPageR monitor that is to be updated.
 - Verify that the software being used is the most current version of AVTECH Device Discovery or Device ManageR. The most current versions can be obtained via the 'Downloads' section of AVTECH.com for current MSUS subscribers.


Note which firmware version the Room Alert or TemPageR is currently running by checking the monitor's 'Status' page. The monitor's version will be in the top right hand corner.

Click here: http://avtech.com/Downloads/ and check the left side box for a list of AVTECH's released versions. If your current firmware version is older than the version listed here, please continue by logging in to the 'Downloads' section. (If you do not know your login password or if you are unsure if you  have an account, click the 'Forgot/Reset Password' link and enter your email address. If your email address is not recognized, click the 'Email Request/Inquiry' button and fill in your information. If your email address is recognized but you do not receive an email with your password, check any SPAM filter in place before contacting AVTECH Technical Support.)

Once in the downloads section, navigate to the monitor's section. Save the firmware update file but DO NOT unzip/decompress the file if it arrives as a .zip or .upd file.


DEVICE DISCOVERY UTILITY: Open Device Discovery and click the 'Search' button. 



Select the monitor that is to be updated and click the 'Update' button.

 


Follow the prompts to specify the location of the Firmware Update file for the monitor and click the 'Upload' button.

 



DEVICE MANAGER: Open Device ManageR and select the monitor from the Device Status list or click on the unit's information in the middle of the page.



Click the 'Update Firmware' button.



Click 'Browse'.



Select the appropriate file and click 'Open'.



Click the 'Update' button to begin the firmware update process.



When the firmware update process completes, the unit will automatically reboot to apply the update.
If you experience an issue during this process, please feel free to contact the Technical Support Team by submitting a support ticket.

How To Use The Trace Feature On A Room Alert Or TemPageR Device

The tracing feature is a very useful tool that can be used to assist in troubleshooting issues with your Room Alert or TemPageR device.

To enable tracing on your unit, follow these steps:

       1.   Access the 'Advanced' tab of the 'Settings' page.


  

       2.   In the 'Trace Configuration' section, ensure that the 'Enable Tracing' check box is checked. The tracing port is 143 by default. You do not need to change this unless you know port 143 will be blocked by your network for some reason. After making changes in this section, click the 'Accept Changes' button at the bottom of the screen, then the 'Save Settings' button on the left hand side of the screen.




To generate a trace from your device you will want to enter the following command into a Windows command prompt: 'telnet -f c:\tracefile.txt <IP of unit> <trace port #>' then press the <Enter> key. Where 'IP of unit' is the IP address of your Room Alert or TemPageR device and 'trace port #' is the configured trace port (143 by default). So the command might look something like this: 'telnet -f c:\tracefile.txt 192.168.33.100 143'. This command will capture your trace data directly to a text file named 'tracefile.txt' in the C: directory.

Please note that Windows 7 and Vista have disabled the Telnet client by default. If you get an error saying 'telnet is not recognized as an internal or external command, operable program or batch file' you will need to enable it by going to 'Start', 'Control Panel', 'Programs And Features', 'Turn Windows Features On Or Off' then checking the 'Telnet Client' row and clicking 'OK'.


At times, it may be useful or necessary for our engineers to review a trace from a Room Alert or TemPageR device and we may request you send us the results of a trace. If you are requested to send a trace in by one of our technical support specialists, or if you feel it will be helpful before being asked, simply attach the file created by the command given above to an email and send it to us at 'Support@AVTECH.com'.

One example of how to use the tracing feature is for troubleshooting email issues with your device. To troubleshoot email issues using the trace feature, launch the trace window using the process described above. Once you have successfully connected to the trace, browse to the 'SMTP Email' tab on the 'Settings' page. Try sending an email by clicking the 'Send Test Email' button at the bottom of the SMTP Email tab. You should see the attempts by the Room Alert or TemPageR device to connect to the configured mail server in the trace output window. If there are any issues occurring with the email process, you should see corresponding errors displayed in the output window which should point you in the right direction as to what might be causing any issue.

My Room Alert Or TemPageR Monitor Is Not Discoverable Or Accessible On My Network. How Do I Discover My Room Alert Or TemPageR?

Device ManageR and the Device Discovery Utility use a broadcast scan on UDP port 30718 to automatically locate AVTECH monitors on a network.
AVTECH recommends the following for initial product discovery:
 - DHCP Enabled on network.
 - UDP Broadcasts allowed at a computer and network level.
Please Note Before Beginning:
 - The network cable must be plugged in to the Room Alert or TemPageR monitor and the switch or computer before power is connected. This ensures that the initial DHCP request will be sent successfully when power is connected.

 - If the monitor has been assigned a static IP address that is invalid for the current IP address range of the network, please proceed to step 3 of this guide.
 - When the Room Alert or TemPageR monitor is powered on and plugged into a network, please check the current status of the Network Jack's lights as these lights are used to determine the current state of the monitor. The left link light should be a solid green color while the right light should be a flashing green or orange. If these lights display any other patterns than this, please skip to step 5 of this guide.

To begin discovering the monitor's IP address, please follow the instructions below starting at step 1.

1. Both Device ManageR and the Device Discovery Utility have a manual discovery feature that uses a TCP scan on TCP port 30718. This feature is helpful if the network range or specific IP address of the monitor is known. 

 - To access this feature using Device ManageR, click the 'Advanced Discovery Options...' button under 'Device Status' in the left menu. Click the 'Manually Add Device/s Via IP Address' button and select either 'Single IP Address' or 'Range Of IP Addresses'. Insert the desired IP address or range and click the 'Begin Scan...' button.

 

 - To access this feature using the Device Discovery Utility, click the 'Advanced Discovery' button located under the 'Search' button. Then, select either 'Single IP Address' or 'Range IP Addresses' and enter the single IP address or IP address range. Start the scan using the 'Begin Scan' button.


2. DHCP Enabled On Network – All AVTECH monitors are initially set to obtain an IP address automatically using DHCP. DHCP must be enabled on the network for the monitor to receive a valid IP address. If DHCP is not enabled, the monitor will default to an auto IP address in the 169.254.xxx.xxx range. At this IP address, the router or system firewalls may not allow discovery because the IP address is outside of the valid network IP range. Valid assignment could potentially be hindered by a managed switch even if DHCP is enabled. If DHCP assignment is delayed in the managed switch, the DHCP request sent from the monitor can timeout and default to a 169.254.xxx.xxx Auto IP address.

 - If DHCP is enabled on the network, there is a chance the DHCP server has already assigned a valid IP address even though the monitor is not discoverable. If the manual discovery option from step 1 does not discover the monitor, the IP address can sometimes be obtained by checking the DHCP server for the MAC address of the monitor.

 - If the IP address can be verified by checking the DHCP server and the IP address is in range of the network, it can be added to Device ManageR and the Device Discovery Utility using the manual scan feature from step 1. This IP address can additionally be accessed by directly by typing the IP address in a web browser. 

 - It is also possible to create a DHCP reserved IP address on a server. Doing this and recycling the power on the monitor should allow the IP address to be assigned by the DHCP server. If this process is unknown or unable to be completed personally, please consult the local Network Administrator. Otherwise, continue to the next step.

3. If the IP address of the monitor is still not discoverable, AVTECH recommends connecting the unit directly to a computer or laptop using a cross-over Ethernet cable or spare network hub.

 - Before disconnecting a computer or laptop to be used from the current network, be sure that the Device Discovery utility is installed along with a protocol analyzer (packet sniffer) application. If a preferred protocol analyzer application is unknown or not installed, a free utility called 'Wireshark' can be installed from http://www.wireshark.org/.

 - Begin by assigning a static IP address to the computer's network card, then connect the monitor via cross-over Ethernet cable or spare network hub to the computer. Lastly, plug in the power to the Room Alert or TemPageR monitor to begin the connection process. 

 - Attempt discovery using the Device Discovery utility by clicking the 'Set IP' button. The 'Set IP' button can set an IP via the MAC address which can be found at the bottom of any Room Alert or TemPageR monitor's case. Follow the procedure as prompted by Device Discovery and remember to set the IP to a valid IP address that is within the same subnet as the IP set for the computer's network card. After doing this, the monitor should be accessible via the Device Discovery list or by directly entering the newly set IP address in a web browser.

4. DHCP alternative to the static IP settings above: While still on the cross-over cable direct connection between the computer and monitor, the Room Alert or TemPageR may also be reset back to initial DHCP factory defaults via the reset button on the back panel of the monitor (if applicable). 

- For TemPageR3E, Room Alert 4E, 11E: Hold the reset button in for 10-15 seconds until the top left LED on the Ethernet jack blinks. A reset has occurred when this light on the ethernet jack goes out, then reappears 1 second later. Please release the reset button after this occurs.

 - For Room Alert 24E, 26W, 32E/W: Hold the reset button in for 10-15 seconds and watch the 3 main status lights on the front of the monitor. A reset has occurred as the front 3 status lights cycle through red and then finish cycling. Please release the reset button after this occurs.

 - With the unit now set back to DHCP factory defaults, change the laptop's network card settings to automatically obtain an IP address as opposed to specifying a static IP. Start up the Device Discovery utility and click 'Search' to locate the monitor.

 - If the Device Discovery utility methods are not working and the above steps have not located the monitor, start the protocol analyzer application, Begin packet capture and recycle the power on the monitor. Look for incoming packets coming from the MAC address of the monitor (located on a sticker on the bottom of the monitor's case or on the back of a rack mount kit if applicable). One of these packets should contain the source IP address of the monitor. Once this IP address has been obtained, configure a static IP address on the laptop or computer that is within a valid network range in relation to the IP address assigned to the unit as in step 3 (i.e. IP of unit: 192.168.2.3 - IP for computer or laptop: 192.168.2.4). The monitor can now be directly accessed by entering the IP address in a web browser.

5. If the above trials have been unsuccessful in discovering the IP address of the unit, please email Support@AVTECH.com with the packet capture obtained in step 4 attached to the email.

Trouble/Issues Accessing the 'Downloads' Section of AVTECH.com

The 'Downloads' section on AVTECH.com is AVTECH's only source of Device ManageR, Room Alert/TemPageR firmware updates, Software updates, MIB files, Device ManageR plugins, and the Device Discovery utility. To gain access to this section, AVTECH will issue a username and password to all contacts that are employed by organizations that have purchased a Room Alert or TemPageR environmental monitor.

If you have been previously issued a username and password from AVTECH: When attempting to log on to the AVTECH Downloads section, make sure that the password being used is entered correctly as the password is case sensitive. Please note the email address that was initially given to AVTECH at the time of registration is the only email that can be used to log on to this section.

If the initial password for the 'Downloads' section of AVTECH.com has been lost or forgotten, go to AVTECH.com/Downloads/ and select the 'Forgot/Reset Password' link below the login section. Enter the registered email address in the new screen and select 'Submit'. If the email address matches a record that was previously created in AVTECH's registry, an email will be sent with the required password.

If you are able to access AVTECH's downloads, but your downloads are expired: The specific downloads provided to your organization are regulated by AVTECH's Maintenance, Support, and Update Service (MSUS). MSUS is an annually renewed service for each of the Room Alert and TemPageR units owned by the organization. If MSUS needs to be renewed, please send an email to RenewMSUS@AVTECH.com including the organization's name and your personal contact information. For more information on MSUS, please refer to this page link:  http://www.AVTECH.com/PDFs/AVTECH_MSUS_Explained.pdf 

If you are a new contractor or temporary hire and require access to AVTECH Downloads: Please provide the following information in an email to 'Support@AVTECH.com' along with a short message explaining the need for access. Once approved, you will be registered as a contractor or temporary hire directly under the organization that owns the Room Alert or TempageR product. Please include the following information in this email:

Organization Name
Organization Address
Organization Phone Number
Your Full Name
Direct Phone Number
Email Address
Job Title
Summary Of Work To Be Completed

For all other issues accessing the 'Downloads' section of AVTECH.com, send an email to 'Support@AVTECH.com' and we will be able to provide further assistance.


Status Screen

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.



Settings Screen

I am unable to get my Room Alert or TemPageR monitor to send email alerts properly. How do I send email alerts directly from the monitor's web page?

Email alerts from the Room Alert or TemPageR monitors are sent using anonymous, unauthenticated SMTP email on TCP port 25. If email notifications are not received, first verify the email settings in the 'SMTP Email' section of the 'Settings' page.
  1. Mail Server Port: This port is typically port 25 but can be different based on personal mail server settings and network preferences. Please check with the mail server administrator for the exact port number.
  2. Mail Server: If the monitor is configured to obtain an IP address using DHCP, enter the specific IP address of the mail server in the ‘Mail Server Address’ field. If the monitor is configured with a static IP address, the DNS name for the mail server can be entered in this field. For initial testing purposes, enter an email address from the same domain as the mail server in the ‘Email Recipients’ field. For example, if the domain name is 'Example.com', be sure the email used to test is from the same domain (i.e. YourEmail@Example.com).
  3. Return Address: To finish the configuration, enter the same email address in the ‘Return Address (From)’ field. Using the same domain name minimizes the risk that security settings on the email server would prevent the message from being delivered.
  4. Display URL: The display URL is a URL that will be at the bottom of your received email alert. This URL is here to allow quick link/access to any URL after an alert is triggered. This URL can be a link to any web page you would like, but typically we assume that quick access to your Room Alert's web page is necessary here. Type in the IP address of the monitor or any other web page that is desired in this field.
  5. Authentication: This field is optional because not all mail servers require authentication. Please check with the mail server administrator if there are any questions about this field. The Username and Password would typically be the same credentials used to log on to a mail server directly.
  6. Email Recipients: List the email addresses that the alert will be sent to and separate multiple addresses by a comma. For example, John@Example.com,James@Example.com,Steve@Example.com Please note that due to limited flash memory on the Room Alert and TemPageR monitors, the Email Recipients field is only 79 characters long. For more space, AVTECH recommends creating a distribution list in the email server itself or for unlimited email entries and advanced/custom alerting, please follow this link for AVTECH Device ManageR: http://avtech.com/Products/Device_ManageR/


     Once the email settings are configured, click the ‘Test Email’ button and check the email account(s) for the test email. If the message is not received, first check any spam filter that may be in place. If the test email cannot be found, it could be blocked by the mail server. Be sure the mail server is configured to allow 'SMTP Relaying' from the IP address of the monitor. Also, be sure the Room Alert or TemPageR is on the email server's 'whitelist' to prevent messages from being filtered or blocked as spam. If messages from the monitor continue to be blocked by the mail server, contact the mail server administrator to see if the mail server logs can be reviewed to determine why the messages are being blocked.

If you have followed the steps above but are still unable to receive email alerts, please contact our Technical Support Team by
submitting a support ticket.

Room Alert Or TemPageR Device Displays An Incorrect Date & Time

Room Alert and TemPageR units obtain the date and time from a NTP time server located on the Internet by default. The IP address of the default time server is 198.82.1.201 and timeserver requests are sent on UDP port 123. Please be sure that UDP requests on port 123 are not blocked on your network, which would prevent the Room Alert or TemPageR unit from syncing to the timeserver properly.

Room Alert or TemPageR units can also be configured to obtain the date and time from a NTP time server on the local network. Navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. Enter the IP address of a time server located on the network in the 'Time Server IP' field. Please remember to press the 'Accept Changes' button below, then the 'Save Settings' button on the left menu to reboot the unit. When the unit reboots, it will attempt to obtain the time and date from the new IP address.

For information regarding how to configure a Windows XP Professional or Server 2003 system to be a Network Time Server, see the following article: http://www.AVTECH.com/Support/Articles/RAST/TA/All/-/AA-NA-TN/Windows_Time_Server.htm.

You can synchronize the time manually by entering:
http://<IP of your unit >/cmd.cgi?action=SyncTime in a browser address bar. 

To customize the current timezone settings, navigate to the Room Alert or TempageR's 'Settings' tab, then select the 'Advanced' button on the left menu. The 'Time & Date Configuration' options can be customized to suit the particular environment of the device here. After changing the below settings, please press the 'Accept Changes' button below, then press the 'Save Settings' button on the left menu to reboot the unit.


What is the Default 'Settings' Screen Password on Room Alert or TemPageR?

The 'Settings' screen of Room Alert and TemPageR is password protected to prevent unauthorized users from modifying the settings. By default, there is no user name and password configured to access the 'Settings' screen of a Room Alert or TemPageR. With the User Name and Password fields left blank, select 'OK' to access the 'Settings' screen.

If you have previously configured a password for the device, leave the User Name field blank and enter your password in the 'Password' field, then select 'OK' to access the 'Settings' screen.

When I try to access the 'Settings' screen on my Room Alert or TemPageR, my web page flashes or does not load properly. How do I access the 'Settings' screen?

The 'Settings' screen on the Room Alert and TemPageR units consist of a Java applet that accesses the device on UDP port 30718 and 30719. To view the 'Settings' applet, Java software must be installed in the browser being used to access the web interface. Java software can be installed at Java.com. Next, verify that you do not have UDP port 30718 and 30719 blocked on any device located between the system or server you are currently using and your unit. If this is the case, unblock the port and try accessing the 'Settings' screen again.

The 'Settings' screen consists of an HTML form that submits and retrieves data using Java script and normal http 'get' and 'post' requests. When the 'Settings' screen flashes or doesn't load properly, we have noticed that a typical cause would be certain security devices such as Microsoft's ISA proxy server or antivirus programs that are implemented on your network. If you can, please check your network and see if any of these items are in fact implemented and are interfering with communications. In order for the 'Settings' tab to open, our program runs certain commands and pages in the background which conflict with some antivirus program's or Internet Security Server's configured settings.

You can attempt to check these pages by trying the following two addresses   http://<IP of unit>/secure/setuprec.xml  and  http://<IP of unit>/secure/unitinfo.xml  Once you have called upon them, please right click and 'view source' on them. If you notice anything strange here or are receiving an error message we would appreciate seeing them for reference. You can  take screen shots or make a text copy of the contents and send them to us here at Support@AVTECH.com

To resolve this issue, typically we see that a proxy server or antivirus is blocking background XML HTTP requests. A typical fix is to allow or add exceptions to the Room Alert Or TemPageR IP address in all security implementations.

If you are still having difficulty, please follow the steps below and attempt to access the 'Settings' screen after completing each one.

  1. Completely close the web browser you are using and reload. If you have any alternate web browsers, please attempt to access the settings page with these browsers as well.

  2. Recycle the power on your unit.

  3. Reupload/update the firmware on your Room Alert or TemPageR unit. For complete instructions on doing so, please follow this link:  http://avtech.com/Support/index.php?action=kb&article=40

If steps 1-3 do not resolve the issue, we suggest disconnecting your device from your network and attempt to connect to it via a laptop and Device Discovery through a crossover cable. When using a cross over cable, you should plug the crossover cable in to the device and the PC first, then plug in the power to the unit. Remember to set up your laptop's network card to be within the same subnet range as your Room Alert and TemPageR unit, then attempt to discover your unit with the Device Discovery Unit. For more information on discovering your unit, please follow this link. http://AVTECH.com/Support/index.php?action=kb&article=73 If you have discovered your unit and are able to access your unit's 'Settings' page, this means that one of the previous topics discussed is most likely still an issue on your network. If you have successfully connected via a crossover cable and are still unable to properly access the settings page, please feel free to contact our technical support staff by submitting a support ticket.


Sensors

Can I add additional sensors to my Room Alert or TemPageR after my initial order?

Yes. Many environmental sensors are available for purchase at any time from AVTECH such as temperature, humidity, power, flood, smoke, motion, room entry and many more. A list of these sensors can be found here: http://avtech.com/Products/Monitor_-_Sensors/ For additional information and purchasing of our environmental sensors, please contact an AVTECH Senior Product Specialist at 888.220.6700.

External Digital Temperature and Humidity Sensor Placement Suggestions

Placing Digital Temperature Sensors in the right locations is essential for reliable monitoring of the environment. Without proper placement, the most relevant temperature data may not be obtained.

 - It is recommended that the Room Alert or TemPageR unit itself is placed near the equipment that you wish to monitor as the standard cable length for Digital Temperature Sensors is 25 feet. External digital sensors may be extended up to 100 feet in length with the use of cable extensions found here: http://avtech.com/Products/Monitor_-_Accessories/Extended_Cable_Coupler.htm.

 - Measuring the temperature of the aisles in the data center at multiple height levels can give an early indication of a potential temperature problem. For consistent and reliable temperature monitoring, place a temperature sensor at least every 25 feet in each aisle with sensors placed closer together if high temperature equipment like blade servers are in use. It is important to know that data center temperatures can drastically vary in nearby locations depending on height from the floor, the specific equipment that is present, and how much equipment is present.

 - AVTECH recommends installing TemPageR and Room Alert rack units at the top of each rack in the data center as the heat generated by the components in the rack rises up to the unit which will give the most accurate readings, TemPageR and Room Alert units will be able to provide an early warning and notify staff for temperature issues before critical systems, servers or network equipment is damaged. You may wish to consider purchasing additional AVTECH devices and sensors to maximize the area that can be monitored.

 - In addition, avoid locating your sensor cables near large electromagnetic devices and florescent lights.

 - Place your sensor cables so that they are located in a safe place away from frequent foot traffic or constant disruption from moving parts.

Click here to review an article entitled Recommended Computer Room Temperature and Humidity. For additional information, please visit ASHRAE (the American Society of Heating, Refrigerating, and Air-Conditioning Engineers) to view a document called "Thermal Guidelines for Data Processing Environments" to assist you in planning how to best place your Digital Temperature Sensors in your organization's environment.

How do I extend my Digital Sensor Cable longer than the supplied 25 feet?

By design, external digital sensor cables are 25 feet in length and can be extended up to a supported100 feet in total length.

To extend the sensor cable, you will need a RJ-11 cable with coupler which is available from AVTECH Software.

To order these cables, contact your Product Specialist or click here to purchase on-line.

To extend an external digital sensor cable:

  1. Remove the external digital sensor to be extended by unplugging its RJ-11 cable from the front of the unit.
  2. Using a 25 foot RJ-11 cable with coupler, insert the RJ-11 connector into the AVTECH unit’s external sensor port.
  3. Plug the RJ-11 connector on the sensor cable to the extension cable.

If you wish to extend the sensor up to the supported 100 feet in length, multiple RJ-11 extension cables can be connected using the methods above.

It is important to note that AVTECH does not recommend extending a cable to a greater distance than 100 feet and does not support splicing or cutting into existing wires to shorten or lengthen the provided cable.



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.

Temperature Conversion Formulas

[F = Fahrenheit, C = Celsius]


To Convert Celsius To Fahrenheit

F = 1.8C + 32


To Convert Fahrenheit To Celsius

C = F – 32
          1.8

Why is the internal temperature reading on my Room Alert or TemPageR monitor higher than the external sensors?

The internal temperature sensor measures the ambient air temperature inside the Room Alert or TemPageR device. Under normal operating conditions, the device can generate some heat internally that can cause the internal sensor to register a temperature that is a few degrees higher than the external sensors. This is normal and especially holds true for any rack mounted monitors, as the temperature inside of a rack is typically warmer than the surrounding environment where the external temperature sensors are located. All sensor readings, including internal sensors, can be calibrated using the 'Settings' page of the monitor's firmware.

Click the 'Settings' link and go to the 'Sensors' tab. If desired, enter a integer value in the 'Adjust' field to calibrate the internal sensor reading to match the readings from the external sensors. For example, if the internal temperature is two (2) degrees higher than the external sensor, put a '-2' in the 'Adjust' field for Sensor 1.

If your Adjust field value seems to be different than what you initially saved it as, it is most likely due to the conversion from Celsius to Fahrenheit. For more information, please follow this link: http://AVTECH.com/Support/index.php?action=kb&article=119

If you have any further questions, please feel free to contact our Technical Support Team by submitting a support ticket.

Device Discovery Utility

Trouble/Issues Accessing the 'Downloads' Section of AVTECH.com

The 'Downloads' section on AVTECH.com is AVTECH's only source of Device ManageR, Room Alert/TemPageR firmware updates, Software updates, MIB files, Device ManageR plugins, and the Device Discovery utility. To gain access to this section, AVTECH will issue a username and password to all contacts that are employed by organizations that have purchased a Room Alert or TemPageR environmental monitor.

If you have been previously issued a username and password from AVTECH: When attempting to log on to the AVTECH Downloads section, make sure that the password being used is entered correctly as the password is case sensitive. Please note the email address that was initially given to AVTECH at the time of registration is the only email that can be used to log on to this section.

If the initial password for the 'Downloads' section of AVTECH.com has been lost or forgotten, go to AVTECH.com/Downloads/ and select the 'Forgot/Reset Password' link below the login section. Enter the registered email address in the new screen and select 'Submit'. If the email address matches a record that was previously created in AVTECH's registry, an email will be sent with the required password.

If you are able to access AVTECH's downloads, but your downloads are expired: The specific downloads provided to your organization are regulated by AVTECH's Maintenance, Support, and Update Service (MSUS). MSUS is an annually renewed service for each of the Room Alert and TemPageR units owned by the organization. If MSUS needs to be renewed, please send an email to RenewMSUS@AVTECH.com including the organization's name and your personal contact information. For more information on MSUS, please refer to this page link:  http://www.AVTECH.com/PDFs/AVTECH_MSUS_Explained.pdf 

If you are a new contractor or temporary hire and require access to AVTECH Downloads: Please provide the following information in an email to 'Support@AVTECH.com' along with a short message explaining the need for access. Once approved, you will be registered as a contractor or temporary hire directly under the organization that owns the Room Alert or TempageR product. Please include the following information in this email:

Organization Name
Organization Address
Organization Phone Number
Your Full Name
Direct Phone Number
Email Address
Job Title
Summary Of Work To Be Completed

For all other issues accessing the 'Downloads' section of AVTECH.com, send an email to 'Support@AVTECH.com' and we will be able to provide further assistance.


Discovery

Discovery Methods with the Device Discovery Utility

This article's purpose is to guide users through the process of discovering AVTECH devices through the Device Discovery Utility via the Discovery and Advanced Discovery methods.  Please refer to LINK [this] LINK article to manually set a device's IP address.

Basic Discovery with the Device Discovery Utility

To discover devices connected to the network using the Device Discovery Utility, start the Device Discovery Utility application.  The application can be found on most Windows-based systems by referring to the following path <C:\Program Files\AVTECH Device Discovery Utility>.

Once the application is open, click the 'Search' button.  This will start the discovery process, which will continue at regular 60 second intervals until the stop button, at the bottom left of the screen is clicked.  The discovered devices will populate in the middle of the application interface.





Advanced Discovery with the Device Discovery Utility

While Basic Discovery will search an entire network for AVTECH devices, the Advanced Discovery feature of the Device Discovery Utility provides a more precise and specific way to locate AVTECH devices on a network.  Click on the 'Advanced Discovery' button to see more options.



The next screen allows a user to search for either a single IP address, or within a range of IP addresses.  To locate a device with its IP address, select the 'Single IP Address' radio button.  Then, enter the device's IP address into the 'Start IP' input field, and click 'Begin Scan'.  If the device's IP address is discoverable, it will be displayed in the Device Discovery Utility's main interface.



 
To scan a range of IP addresses for a device, select the 'Range IP Addresses' radio button.  Once selected, enter an initial IP address and a final IP address in the 'Start IP' and 'End IP' fields, respectively.  Then, click the 'Begin Scan' button  If any AVTECH device's IP address within the specified range is discoverable, it will be displayed in the Device Discovery Utility's main interface.


Trouble/Issues Accessing the 'Downloads' Section of AVTECH.com

The 'Downloads' section on AVTECH.com is AVTECH's only source of Device ManageR, Room Alert/TemPageR firmware updates, Software updates, MIB files, Device ManageR plugins, and the Device Discovery utility. To gain access to this section, AVTECH will issue a username and password to all contacts that are employed by organizations that have purchased a Room Alert or TemPageR environmental monitor.

If you have been previously issued a username and password from AVTECH: When attempting to log on to the AVTECH Downloads section, make sure that the password being used is entered correctly as the password is case sensitive. Please note the email address that was initially given to AVTECH at the time of registration is the only email that can be used to log on to this section.

If the initial password for the 'Downloads' section of AVTECH.com has been lost or forgotten, go to AVTECH.com/Downloads/ and select the 'Forgot/Reset Password' link below the login section. Enter the registered email address in the new screen and select 'Submit'. If the email address matches a record that was previously created in AVTECH's registry, an email will be sent with the required password.

If you are able to access AVTECH's downloads, but your downloads are expired: The specific downloads provided to your organization are regulated by AVTECH's Maintenance, Support, and Update Service (MSUS). MSUS is an annually renewed service for each of the Room Alert and TemPageR units owned by the organization. If MSUS needs to be renewed, please send an email to RenewMSUS@AVTECH.com including the organization's name and your personal contact information. For more information on MSUS, please refer to this page link:  http://www.AVTECH.com/PDFs/AVTECH_MSUS_Explained.pdf 

If you are a new contractor or temporary hire and require access to AVTECH Downloads: Please provide the following information in an email to 'Support@AVTECH.com' along with a short message explaining the need for access. Once approved, you will be registered as a contractor or temporary hire directly under the organization that owns the Room Alert or TempageR product. Please include the following information in this email:

Organization Name
Organization Address
Organization Phone Number
Your Full Name
Direct Phone Number
Email Address
Job Title
Summary Of Work To Be Completed

For all other issues accessing the 'Downloads' section of AVTECH.com, send an email to 'Support@AVTECH.com' and we will be able to provide further assistance.


Firmware Update

Trouble/Issues Accessing the 'Downloads' Section of AVTECH.com

The 'Downloads' section on AVTECH.com is AVTECH's only source of Device ManageR, Room Alert/TemPageR firmware updates, Software updates, MIB files, Device ManageR plugins, and the Device Discovery utility. To gain access to this section, AVTECH will issue a username and password to all contacts that are employed by organizations that have purchased a Room Alert or TemPageR environmental monitor.

If you have been previously issued a username and password from AVTECH: When attempting to log on to the AVTECH Downloads section, make sure that the password being used is entered correctly as the password is case sensitive. Please note the email address that was initially given to AVTECH at the time of registration is the only email that can be used to log on to this section.

If the initial password for the 'Downloads' section of AVTECH.com has been lost or forgotten, go to AVTECH.com/Downloads/ and select the 'Forgot/Reset Password' link below the login section. Enter the registered email address in the new screen and select 'Submit'. If the email address matches a record that was previously created in AVTECH's registry, an email will be sent with the required password.

If you are able to access AVTECH's downloads, but your downloads are expired: The specific downloads provided to your organization are regulated by AVTECH's Maintenance, Support, and Update Service (MSUS). MSUS is an annually renewed service for each of the Room Alert and TemPageR units owned by the organization. If MSUS needs to be renewed, please send an email to RenewMSUS@AVTECH.com including the organization's name and your personal contact information. For more information on MSUS, please refer to this page link:  http://www.AVTECH.com/PDFs/AVTECH_MSUS_Explained.pdf 

If you are a new contractor or temporary hire and require access to AVTECH Downloads: Please provide the following information in an email to 'Support@AVTECH.com' along with a short message explaining the need for access. Once approved, you will be registered as a contractor or temporary hire directly under the organization that owns the Room Alert or TempageR product. Please include the following information in this email:

Organization Name
Organization Address
Organization Phone Number
Your Full Name
Direct Phone Number
Email Address
Job Title
Summary Of Work To Be Completed

For all other issues accessing the 'Downloads' section of AVTECH.com, send an email to 'Support@AVTECH.com' and we will be able to provide further assistance.

Updating Firmware with the Device Discovery Utility

The Device Discovery Utility is capable of updating the firmware on an unlimited number of Room Alert or TemPageR devices across the network.  Keep in mind that the appropriate firmware file must be downloaded before the update process can be initiated.  The firmware can be downloaded at http://AVTECH.com/Downloads.  The process of updating device firmware via the Device Discovery Utility is detailed below.

Firmware Update for a Discovered Device:

Open the Device Discovery Utility application.  The file path on most Windows-based computers is C:\Program Files\AVTECH Device Discovery Utility.  Once the application is open, click 'Search'.



The list of available devices will populate below.  Locate and select the device that will have its firmware updated.  Multiple devices can be selected by holding the 'CTRL' key and clicked each desired device. Keep in mind that only one type of device can be updated at a time. For example, if you select a Room Alert 11E, only other Room Alert 11E devices can be selected and updated simultaneously. Once the desired devices are selected, click the 'Update' button.



A new window will appear.  Click 'OK'.



A file browser will open to locate the desired firmware file to use for the update.  Browse to the appropriate file location, select the firmware file, and click 'Upload'.



The README window will appear next, and a website detailing changes on this revision will open in the default browser.  Click 'OK'.



The firmware upload progress bar will appear.  Allow the firmware process to complete.



Once the update process is complete, the option to view the Update.log file will be presented.  Click 'Yes' to view the file, 'No' to close the window without viewing the file.


Firmware Update for an Undiscovered Device:

If the device to be updated is not discoverable, click the 'Update' button without selecting any devices from the list of discovered devices.



The 'Enter Device IP' window will appear.  Enter the IP address of the desired device, and click 'OK'.

A new window will appear.  Click 'OK'.



A Windows browser will open.  Browse to the appropriate file location, select the firmware file, and click 'Upload'.



The Readme window will appear next, and a website detailing changes on this revision will open in the default browser.  Click 'OK'.



The firmware upload progress bar will appear.  Allow the firmware process to complete.



Once the update process is complete, the option to view the Update.log file will be presented.  Click 'Yes' to view the file, 'No' to close the window without viewing the file.




 

 

Other Features

Trouble/Issues Accessing the 'Downloads' Section of AVTECH.com

The 'Downloads' section on AVTECH.com is AVTECH's only source of Device ManageR, Room Alert/TemPageR firmware updates, Software updates, MIB files, Device ManageR plugins, and the Device Discovery utility. To gain access to this section, AVTECH will issue a username and password to all contacts that are employed by organizations that have purchased a Room Alert or TemPageR environmental monitor.

If you have been previously issued a username and password from AVTECH: When attempting to log on to the AVTECH Downloads section, make sure that the password being used is entered correctly as the password is case sensitive. Please note the email address that was initially given to AVTECH at the time of registration is the only email that can be used to log on to this section.

If the initial password for the 'Downloads' section of AVTECH.com has been lost or forgotten, go to AVTECH.com/Downloads/ and select the 'Forgot/Reset Password' link below the login section. Enter the registered email address in the new screen and select 'Submit'. If the email address matches a record that was previously created in AVTECH's registry, an email will be sent with the required password.

If you are able to access AVTECH's downloads, but your downloads are expired: The specific downloads provided to your organization are regulated by AVTECH's Maintenance, Support, and Update Service (MSUS). MSUS is an annually renewed service for each of the Room Alert and TemPageR units owned by the organization. If MSUS needs to be renewed, please send an email to RenewMSUS@AVTECH.com including the organization's name and your personal contact information. For more information on MSUS, please refer to this page link:  http://www.AVTECH.com/PDFs/AVTECH_MSUS_Explained.pdf 

If you are a new contractor or temporary hire and require access to AVTECH Downloads: Please provide the following information in an email to 'Support@AVTECH.com' along with a short message explaining the need for access. Once approved, you will be registered as a contractor or temporary hire directly under the organization that owns the Room Alert or TempageR product. Please include the following information in this email:

Organization Name
Organization Address
Organization Phone Number
Your Full Name
Direct Phone Number
Email Address
Job Title
Summary Of Work To Be Completed

For all other issues accessing the 'Downloads' section of AVTECH.com, send an email to 'Support@AVTECH.com' and we will be able to provide further assistance.

Using The Device Discovery Utility To Assign A Static Or DHCP IP Address To A Device

This article provides instructions on setting a device's IP address through the Device Discovery Utility.  It deals with both static and DHCP assignments, as well as how to set the IP address of an undiscovered device.  The Device Discovery Utility can assign a static IP address, or set the device to request a DHCP address from an available DHCP server.  There are several ways that this can be done, and each will be addressed individually.

Setting an IP Address for an Undiscovered Device

For DHCP:

Open the Device Discovery Utility.  In most Windows computers, the file path will be C\Program Files\AVTECH Device Discovery Utility.  Once it's open, click the 'Set IP' button.



Click 'OK' on the 'Device Not Selected' window.



Enter the last 3 sets of hexadecimal digits of the device's MAC address.  The last 3 sets of hexadecimals digits are the device's NIC's MAC address.  The device's MAC address can most often be located on a sticker on the underside of the device.  Click 'OK'



Another window will appear.  This window explains that the IP address entered must be within the same subnet as the PC used to configure the device.  Otherwise, the device may become undiscoverable.  Click 'OK'.



In the next screen, enter 0.0.0.0.  Click 'OK'.




For Static:

Open the Device Discovery Utility.  In most Windows computers, the file path will be C\Program Files\AVTECH Device Discovery Utility.  Once it's open, click the 'Set IP' button.



Click 'OK' on the 'Device Not Selected' window.



Another window will appear.  This window explains that the IP address entered must be within the same subnet as the PC used to configure the device.  Otherwise, the device may become undiscoverable.  Click 'OK'.


Enter the desired static IP address.  Click 'OK'.



Enter the IP address of the Gateway the device will use.  Click 'OK'


The 'Enter DNS IP' window will appear.  Enter the IP address of the DNS server the device will refer to.  Click 'OK'.



The next window to appear is the 'Enter Subnet Mask' window.  Enter the device's subnet mask.  Click 'OK'.



Setting an IP Address for a Discovered Device

For DHCP:

Open the Device Discovery Utility.  In most Windows computers, the file path will be C\Program Files\AVTECH Device Discovery Utility.  Once it's open, click the 'Search' button to find all discoverable devices on the network.  Once the desired device has been discovered, select it and  click the 'Set IP' button.



Another window will appear.  This window explains that the IP address entered must be within the same subnet as the PC used to configure the device.  Otherwise, the device may become undiscoverable.  Click 'OK'.



In the next window, 'Enter IP Address', enter 0.0.0.0 as the IP address.  Click 'OK'




For Static:

Open the Device Discovery Utility.  In most Windows computers, the file path will be C\Program Files\AVTECH Device Discovery Utility.  Once it's open, click the 'Search' button to find all discoverable devices on the network.  Once the desired device has been discovered, select it and  click the 'Set IP' button.


Another window will appear.  This window explains that the IP address entered must be within the same subnet as the PC used to configure the device.  Otherwise, the device may become undiscoverable.  Click 'OK'.



In the next window, 'Enter IP Address', enter the desired static IP address.  Click 'OK'



Enter the IP address of the Gateway the device will use.  Click 'OK'



The 'Enter DNS IP' window will appear.  Enter the IP address of the DNS server the device will refer to.  Click 'OK'.



The next window to appear is the 'Enter Subnet Mask' window.  Enter the device's subnet mask.  Click 'OK'.


 

 

 

 

Powered by KnowledgeBuilder