NetBotz

Device > NetBotz

Click the module name, NetBotz or NBPod150, to configure its settings, and view and configure settings for its connected sensors.

  • NetBotz: Name and Location
  • NBPod 150: Name, Location, and Blink Identifier LED on the selected Sensor Pod 150 module for the number of minutes you specify.

View the module factory information, including the model number, serial number, hardware revision, and software revision.

Wired Sensors

Name: Enter a name (up to 20 characters).

Location: Enter the location of the sensor (up to 20 characters).

Alarm Generation: Enable or disable. When Alarm Generation is disabled, the system continues to monitor the state of the sensor, but does not generate an alarm. Alarms are not recorded in the event log when Alarm Generation is disabled.

Threshold Settings: Click to enter the minimum, low, high, maximum, and hysteresis values for temperature and humidity.

Temperature above any of these thresholds causes an alarm:

Maximum: Must be greater than High Temperature Threshold.

High: Must be greater than the sum of Low Temperature Threshold and Temperature Threshold Hysteresis.

Temperature below any of these thresholds causes an alarm:

Low: Must be greater than Minimum Temperature Threshold.

Minimum: The lowest temperature threshold.

Humidity above any of these thresholds causes an alarm:

Maximum: Must be greater than High Humidity Threshold.

High: Must be greater than the sum of Low Humidity Threshold and Humidity Threshold Hysteresis.

Humidity below any of these thresholds causes an alarm:

Low: Must be greater than Minimum Humidity Threshold.

Minimum: The lowest humidity threshold.

Hysteresis

The difference between the threshold violation and the clearing point. This value specifies how far above or below a threshold the temperature or humidity must return to clear a threshold violation.

For Maximum and High threshold violations, the clearing point is the threshold minus the hysteresis.

For Minimum and Low threshold violations, the clearing point is the threshold plus the hysteresis.

Rate of Change Settings

Click to configure the acceptable short-term and long-term rate of change (increase and decrease in the time you specify). When the rate of change is exceeded, an alarm occurs.

Once an increase or decrease no longer exceeds the limits you specify, the rate of change alarm clears.

Wireless sensor network

Device > Wireless Sensor Network

Modify the settings for each wireless sensor, including name, extended address, location, alarm generation, and temperature, humidity, battery, and signal thresholds.

Name: Enter a name (up to 20 characters).

Extended Address: The extended address (MAC) of the wireless sensor.

Location: Enter the location of the sensor (up to 20 characters).

Alarm Generation: Enable or disable. When Alarm Generation is disabled, the system continues to monitor the state of the sensor, but does not generate an alarm. Alarms are not recorded in the event log when Alarm Generation is disabled.

Temperature Thresholds: Set the thresholds for the temperature:

Maximum: If the threshold for the maximum temperature for the sensor is exceeded, an alarm occurs.

High: If the threshold for the high temperature for the sensor is exceeded, an alarm occurs.

Low: If the temperature drops below its low threshold for the sensor, an alarm occurs.

Minimum: If the temperature drops below its minimum threshold for the sensor, an alarm occurs.

Humidity Thresholds: Set the thresholds for the humidity:

Maximum: If the threshold for the maximum humidity for the sensor is exceeded, an alarmoccurs.

High: If the threshold for the high humidity for the sensor is exceeded, an alarm occurs.

Low: If the humidity drops below its low threshold for the sensor, an alarm occurs.

Minimum: If the humidity drops below its minimum threshold for the sensor, an alarm occurs.

Battery Thresholds: Set the thresholds for the battery voltage:

Low: If the battery voltage drops below its low threshold for the sensor, an alarm occurs.

Minimum: If the battery voltage drops below its minimum threshold for the sensor, an alarm occurs.

Signal Thresholds: Set the thresholds for the signal strength:

Low: If the signal strength drops below its low threshold for the sensor, an alarm occurs.

Minimum: If the signal strength drops below its minimum threshold for the sensor, an alarm occurs.

See the NetBotz Installation and Quick Configuration manual for more information about setting up the wireless sensor network.

Outputs

Device > Outputs (Beacon, Output Relay, and Switched Outlet)

Note: The Output pages under the Status, Control, and Configuration menus are the same, and contain all the tasks for each menu option.

Each output type displays the following configuration information:

Name: Enter a name (up to 20 characters).

Location: Enter the location of the sensor (up to 20 characters).

Normal State: On/Off or Open/Closed (excluding the beacon)

Control: Turn On/Off or Open/Close

Alarm Mapping

The beacon, output relay and switched outlet can be activated by alarm states of sensors on the NetBotz module only.

  1. Select one or more alarm states that will change the state of the output.

  2. By default, each sensor connected to the NetBotz module is mapped to activate the output when the sensor is in an abnormal state. Click the name of the alarm state to view the sensors connected to the module.

  3. Select sensors to include in the alarm. Any selected sensor, in its abnormal state, activates the output.

Rack access

Device > Rack Access

The NetBotz Rack Monitor 250 supports the NetBotz Handle Kit only (NBHN125/NBHN1356). View the manual for the Handle Kit.

The Rack Monitor 250 can support up to 200 registered cardholders. You may be able to configure more than 200 cardholders by using a RADIUS server for authentication.

Registered users

Select a registered user's name to view the card ID number and to edit name, contact information, and access permissions.

Name: The name of the user (up to 20 characters)

Contact: The contact information for the user (up to 20 characters).

Door Access: The doors the access card is configured to unlock: Door 1 only, Door 2 only, or both doors.

Time Scheduled: Either Granted (the user's access schedule is configured) or Not Configured (the user's access schedule is not configured). Until the schedule is configured, this card cannot unlock enclosure doors.

Unregistered users

View the ID number of any unconfigured access card that has been held in front of the lock, and the date and time it was held in front of the lock.

To register a user, select the number of the card that will be assigned to the user, and specify:

Name: Enter a name for the user (up to 20 characters).

Contact: Enter the contact information for the user (up to 20 characters).

Card ID: The identification number of the card assigned to the user. This option is not configurable.

Account Access: Check the box to activate the card. To temporarily disable the access permission for the card without deleting the user, uncheck the box.

Door Access: Configure the card to open Door 1 only, the Door 2 only, or both doors.

Granted Access Schedule: Check the box for each day the card is permitted to unlock the doors, and configure the hours during each enabled day the user can access the rack. Valid values are 00:00 to 23:59.

Apply: Click to save your changes.

Cancel: Click to exit without saving.

Delete User: Click to erase the configured information and remove the card from the list of registered users. If the deleted card is held in front of the lock, the card number appears in the list of unregistered users.

RADIUS

Specify how users will be authenticated when they access the rack:

Lock user authentication

Local NetBotz appliance only: RADIUS is disabled. Rack access is controlled by the local authentication configured in the Registered Users option.

RADIUS, then Local NetBotz appliance: RADIUS is enabled, and local rack access authentication is enabled. Authentication is requested from the RADIUS server first; local rack access authentication is used only if the RADIUS server fails to respond.

RADIUS only: RADIUS is enabled. Local rack access authentication is disabled. If the RADIUS server fails to authenticate the user, access is denied.
Note: The message “No RADIUS servers have been configured” indicates you must add a properly configured RADIUS server so that RADIUS authentication can operate.

RADIUS server settings

RADIUS New password/Confirm password: The complex password for RADIUS (1 - 64 characters) is enabled by default. The default RADIUS password is the serial number of the NetBotz appliance, displayed in the About > Network option.

Lock properties

Both rack access handles must be the same model, either two 125 kHZ handles (NBHN125) or two 13.56 MHz handles (NBHN1356).

Use Door 1 and Door 2 ports for door switches used with handles; otherwise, use the universal sensor ports for door switches used without handles.

The proximity card type must be the same for both handles.

Card Reader: Enable or disable the card reader on the door lock. When disabled, you must use a key to access the enclosure.

Card Format: Rack access supports eight access card formats. Choose the format of the card you are configuring:

H10301 - Standard 26 bit: An access card with a 26-bit card ID number and a facility code.

H10302 - 37 bit w/o facility code: An access card with a 37-bit card ID number and no facility code.

H10304 - 37 bit w/ facility code: An access card with a 37-bit card ID number and a facility code.

CORP1000 - Corporate 1000: An access card with a 35-bit card ID number and a unique company ID code.

MIFAREC4: Mifare Classic 4 byte card.

MIFAREC7: Mifare Classic 7 byte.

MIFAREDF: Mifare DESfire.

MIFAREPL: Mifare Plus.

iCLASS

To register a new proximity card:

  1. Check the box to enable the card reader. Specify the card type for the installed handle(s), the auto-relock time (10 - 60 seconds), and the time to wait before the door open alarm is activated for Door 1, Door 2, or both (1 - 120 minutes). Click Apply.

  2. Hold the card in front of the proximity reader on the handle until you hear a beep.

  3. Go to Configuration > Device > User Access > Unregistered Users.

  4. Click the card ID number to specify the user name, door access (Door 1, Door 2, or both), the access schedule (24 x 7 by default), and enable account access.

  5. Click Apply.

To view, modify, or delete registered users, go to Configuration > Device > User Access > Registered Users.

Auto-Relock: Enter the number of seconds that elapse before the door re-locks, if the door is not opened within this period of time.

Door Open Alarm: Check the box to enable the alarm for Door 1, Door 2, or both, and enter the number of minutes the door can remain open before an alarm occurs.

Schedule

Schedule a date and time to automatically unlock the enclosure doors.

One-time Schedule: Enable or disable the scheduled unlock.

Date: Specify the date the doors will unlock.

Time: Specify the time the doors will unlock, in hours and minutes. Valid values are 00:00 to 23:59.

Unlock Doors: Unlock Door 1, Door 2, or both doors.

Remain Unlocked: Choose the units (minutes or hours) and enter the number of minutes or hours the doors will remain unlocked before causing an alarm.

Disable relock for the duration: Check the box to prevent the door from locking if it is closed during the scheduled unlock.

 


 

Title: INTERNAL: How to disable the NetBotz Modem Reset Daemon

 

Issue

 

For installations of NetBotz with a GSM modem, it may be helpful for troubleshooting to disable the Modem Reset Daemon if the NetBotz appliance is rebooting sporadically.

 

 

Product Line

 

  • NetBotz 450, 455, 550, 570

 

Environment

 

  • BotzWare v4.3.0 and higher
  • Appliances with USB GSM modem connected
  • All serial numbers

 

Cause

 

When a GSM modem is connected to a supported NetBotz appliance mentioned above, it is possible that the NetBotz unit may reboot seemingly randomly if the response from GSM carrier is too slow or absent. (This may be due to low signal, carrier issue, or both.) The NetBotz’s aforementioned reboot behavior is a function of the onboard Modem Reset Daemon which periodically checks the carrier status and signal quality.

 

 

Resolution

 

It is highly recommended to verify the NetBotz appliance is truly rebooting. Check the uptime from the console OR check the appliance event log for frequent “Init Event log” messages. Once you verify the appliance is rebooting only when a GSM modem is attached, you can configure and run modem debug output (configure Modem Reset Daemon to Information level in AV’s Log configuration) to a syslog server and verify that the last message printed before every reboot is the modem AT command being sent but no response.

 

Assuming the information you review and gather above points to reboots due to Modem Reset Daemon, you can try manually disabling the Modem Reset Daemon. Note: You can only perform the below commands with BotzWare v4.6.2 and higher. BotzWare v4.3.0 and higher contains the daemon but it can only be disabled using BotzWare v4.6.2 or higher.

 

To disable the daemon, enter the following URL into your web browser (change to https if needed): http://<Bot IP or hostname>/disablemodemreset . Upon doing this, a message in the Appliance Log will be recorded: Modem Reset daemon has been disabled by user action.

 

Note: If the modem reset daemon is disabled, then after each and every appliance reboot, a message will be recorded in the Appliance Log: Modem Reset daemon has been disabled by configuration.

 

In order to re-enable the Modem Reset Daemon, enter the following URL into your web browser (change to https if needed): http://<Bot IP or hostname>/enablemodemreset . Upon doing this, a message in the Appliance Log will be recorded: Modem Reset daemon has been enabled by user action.

Skip to end of metadata
Go to start of metadata
  • No labels
RELATED COMMUNITY QUESTIONS
WAS THIS ARTICLE HELPFUL?