570R

Socket Round

Catalogue Number: 570R
570R
Colour: White
Colour: Per UOM Std.
  • White 1 PCE

Specifications

hide show
Range of product
PDL
Product brand
Clipsal
Quantity per set
set of 1
Cover type
complete housing
Marking
without marking
Local signalling
without light indicator

Documents & downloads

hide show
Filter items
  • All

  • Product Brochures

  • Technical Data Catalogues

  • Installation Instruction

  • Specifications

  • Certificates (MSDS)

  • Corporate Marketing

Frequently Asked Questions

hide show

is there a mounting clip for the 570S?

No the 570S is supplied with a panel clamp for fitting through rectangular entry.
38mm wide x 31mm high.

Video: How to setup basic connection to SCADAPack 570/575

Video:

How to setup basic connection to SCADAPack 570/575

Product Line

SCADAPack 570, SCADAPack 575

Environment

Remote Connect

Description

This video will provide a brief demonstration of getting basic communications with SCADAPack 570/575 RTU.

What is the part code for a 15A version of 570S

There is no 15A version of 570S, only in the 193 range which are round not square ie 193/15/1

Is there a mounting block for the PDL570S?

No there is not. This is designed to panel mount directly onto surfaces.

For a wall mounted alternative you can use the round PDL570R with a PDL530 mounting block.

NetBotz | Do NetBotz support BACNET Integration?

Issue:
Do NetBotz appliances have BACNET Integration?

Product Line:
NetBotz (NB)

Environment:
NetBotz (all models and firmwares)

Resolution:

BACNET Integration is not currently supported by any Netbotz devices / appliances. NetBotz v3 (355, 450, 455, 550, & 570) appliances do offer a Modbus output option.

NetBotz Rack Access POD 170/171 | Manual and Installation Guides

Issue:
   Where can I find the manual for the APC Rack Access Pod 171 NBPD0171?

Product Line:
  Netbotz Appliance (455, 550, 570, & 750)

Environment:
   Netbotz Rack Access NBPD0171
   NetBotz Rack Access NBPD0172

Resolution:

NetBotz Rack Access Pod 170 (for APC SX rack)
https://www.apc.com/shop/us/en/products/NetBotz-Rack-Access-Pod-170-for-APC-SX-rack-/P-NBPD0171

NetBotz Rack Access Pod 170 (for Chatsworth GlobalFrame rack)
https://www.apc.com/shop/us/en/products/NetBotz-Rack-Access-Pod-170-for-Chatsworth-GlobalFrame-rack-/P-NBPD0172
 

NetBotz | What is compatible?

Issue:
What is compatible with a NetBotz Appliance?

Product Line:
NetBotz Appliance (250, 355, 450, 455, 570, & 750)

Environment:
NetBotz (all versions)

Cause:
This article explains in detail the entire NetBotz product line compatibility for Universal Sensors, Cameras, Rack Access, and Software.

Resolution:

NetBotz Appliance Compatibility Matrix
https://www.apc.com/salestools/JHIN-7PTK7P/JHIN-7PTK7P_R8_EN.pdf?sdirect=true

NetBotz Appliance Specifications Chart
https://www.apc.com/salestools/JHIN-7PTKDA/JHIN-7PTKDA_R4_EN.pdf?sdirect=true

NetBotz 250 Brochure
https://www.apc.com/salestools/MKEY-ADCS74/MKEY-ADCS74_R1_EN.pdf

NetBotz 750 Brochure
https://www.apc.com/salestools/SBRN-B7CKMD/SBRN-B7CKMD_R0_EN.pdf​

Password Reset on a V3 NetBotz appliance

Issue:

How do I reset the password on a version 3 NetBotz appliance.

Product Line:

NetBotz

Environment:

NetBotz version 3 appliances 3xx, 4xx, and 5xx devices.

Cause:

Recover from lost password.

Resolution:
 

To recover from a lost password:
1. Locate the reset switch on the appliance.
2. Using a thin wire such as a paperclip, press and hold down the reset switch for ten seconds. This
will cause the system to reboot.
3. Once the system reboots, you have two minutes to log in using the following default login values:
a. For Advanced View
• User ID: apc
• Password: apc
b. For the console
• User ID: root
• Password: apc
4. Once you have logged in to Advanced View, change the root password to ensure security.
Note: If you do not log in within two minutes after holding down the reset switch,
you must repeat the procedure.


 

Can StruxureWare Data Center Expert be configured to alert for NetBotz 3xx, 4xx, and 5xx devices?

Issue:

Can StruxureWare Data Center Expert be configured to alert for NetBotz 3xx, 4xx, and 5xx devices?

Product Line:

StruxureWare Data Center Expert
NetBotz

Environment:

StruxureWare Data Center Expert monitoring NetBotz using HTTP or HTTPS

Cause:

StruxureWare does not alert for NetBotz 3xx, 4xx, or 5xx devices that are being monitored using http or https (please note there is no DCE option to monitor these devices using SNMP.)

Resolution:

Ever since their integration with NetBotz Central, NetBotz devices were designed to alert for themselves. This was done to eliminate NetBotz Central as a single point of failure. This functionality is retained by DCE.

Although you can configure the NetBotz appliance through DCE, the alerting for sensors, their thresholds, and their communications status is handled by the NetBotz appliance directly. The only alert StruxureWare DCE will alert for is if DCE itself loses communications with the NetBotz device (and only if the DCE server has a user with an associated e-mail that also has access to that NetBots appliance.)  This does not necessarily mean that the NetBotz is off-line or even that it is not capable of alerting for itself, this simply means that DCE can not communicate and it could be because of anything from user/password changes to the device itself actually being off-line.

Please note that this is different than the NetBotz Rack Access AP9361, NetBotz 200, or NetBotz 250 which are monitored using SNMP. Devices monitored in this manner can be configured to alert for themselves but they are normally configured to alert through DCE for convenience.
 

NetBotz | End of Sale & End of Support Information

Issue:
   NetBotz - End of Sale & End of Support Information

Product Line:
   NetBotz (all models)
   NetBotz Central

Environment:
   NetBotz (all versions)

Resolution:

NetBotz End of Sale & End of Support
 
SKU Description End of Sale End of Support Recommended Replacement
AP9319 Environmental Monitoring Unit July 2006 July 2008 NBRK0250
AP9320 Environmental Management System September 2015 September 2017 NBRK0250
AP9340 Environmental Manager January 2017 January 2019 NBRK0250
NBRK0200 / NBRK0201 NetBotz Rack Monitor 200 October 2016 October 2018 NBRK0250
AP9360 Proximity Card Rack Lock Kit August 2007 August 2009 NBACS125
NBACS1356
AP9361 Rack Access PX - HID October 2016 October 2018 NBACS125
​NBACS1356
NetBotz 320 NetBotz 320 Rack Mount July 2009 July 2014 NBRK0750
NetBotz 320 Wall Mount July 2009 July 2014 NBWL0355A
NBWL0356A
NetBotz 320 Environmental July 2012 July 2017 NBRK0750
NetBotz 420 NetBotz 420 Rack Mount May 2009 May 2014 NBRK0750
NetBotz 420 Wall Mount May 2009 May 2014 NBWL0455A
NBWL0456A
NetBotz 420 Environmental May 2012 May 2017 NBRK0750
NetBotz 500 NetBotz 500 Wall Mount October 2013 October 2018 NBWL0455A
NBWL0456A
V2 Sensors* Sensors with PS/2 Connectors October 2017 October 2019 N/A*
NBPD0121 Camera Pod 120 November 2017 November 2019 N/A*
NBPD0122 Sensor Pod 120 October 2017 October 2019 N/A*
NBPD0180 Sensor Pod 180 April 2019 TBD N/A
NBCN1000 NetBotz Central September 2004 September 2006 StruxureWare Data Center Expert
*V2 Sensors (PS/2 connection) are only supported when they are integrated into a supported version 3 appliance (models: 355, 455, 450, & 570) utilizing a sensor POD 120.

Information on current appliances and compatibility/specifications can be found in knowledge base FA256261.

Can I extend the length of my Environmental Sensors and Probes?


Issue

Can I extend the length of my Environmental Sensors and Probes?

Product Line

  • Environmental Monitoring Products
    • NetBotz 250
    • NetBotz 355, 455, 450, 550, 570
    • Environmental Monitoring Unit/System


Environment
 
  • All serial numbers
  • All firmware versions


Cause

This document pertains to the Environmental Sensors and Probes that can be connected to APC's Environmental Monitoring and Management Units (AP9312, AP9319, AP9320, and AP9340) and version 3 NetBotz Appliances.


Resolution
 

  • AP9512T/THBLK - We do not officially support lengthening the temperature humidity probe with PS/2 extension cables. However, though not officially supported, we have extended the length using two 12 foot PS/2 extension cables for a total of 36 feet.
 
  • AP9335T - To increase the length, you must connect an additional Cat5 cable, connected via an RJ-45 coupler.
    • AP9312, AP9319, AP9320, AP9340 - 50 ft.
    • NetBotz 200 - 50 ft.
    • NetBotz 250 - 50 ft.
    • NetBotz 355, 455, 450, 550, 570 - 50 ft.
 
  • AP9335TH - To increase the length, you must connect an additional Cat5 cable, connected via an RJ-45 coupler.​
    • AP9312, AP9319, AP9320, AP9340 - 50 ft.
    • NetBotz 200 - 50 ft.
    • NetBotz 250 - 50 ft.
    • NetBotz 355, 455, 450, 550, 570 - 50 ft.
 
  • AP9520T/TH - This sensor connects via A-link communication. The Alink protocol has a maximum distance of 1000 meters (3,280 ft).  However, these sensors are connected via Cat5 cabling which has a functional limitation of 100m per length.  For lengths longer than 100m, a repeater device is required to amplify the signal.



Additional information on connecting Environmental Sensors and Probes can be obtained via the User's Manual for the AP9312, AP9319, AP9320, AP9340, and current NetBotz products.

 

Serial Terminal Connection Parameters for all NetBotz Appliances

Issue:

Serial Terminal Connection Parameters for all NetBotz Appliances

Product Line:

NetBotz

Environment:

Versions as described below
terminal emulation

Cause:

Terminal emulation (ie. Hyper-Terminal) configuration for communications with NetBotz appliances.

Resolution:

Terminal emulation is often used for initial IP configuration on NetBotz appliances. Hyper-terminal or Putty are often used for this configuration.
 

Serial Terminal Connection Parameters for all NetBotz Appliances

When connecting to a Netbotz appliance or a NetBotz Central via a serial cable, the terminal settings must be set to:

38400 and 8-N-1

When connecting to a models 300, 303, 310, or 400, you must use a standard serial cable, such as the kind used to connect a modem to a PC.

When connecting to models 320, 420 or 500, you must use a NULL modem cable.

When connecting to models 355, 455, 550, 570 or similar version 3 Netbotz, you must use a USB A-B cable.

The NetBotz 200 uses a Null Modem cable and a baud rate of 9600.

NOTE: When connecting to a NetBotz Central, you must use a NULL modem cable.
 

Wrong status if wrong sensor is plugged into sensor port on Netbotz Rack Monitor 550 or 570 with an Internal SP150

Issue:

Wrong status if wrong sensor is plugged into sensor port on Netbotz Rack Monitor 550 with an Internal SP150

Product Line:

NetBotz

Environment:

NetBotz version 3 appliances and sensors

Cause:

In some instances, sensors can be connected to only specific sensor ports.

Resolution:

"The attached XL sheet lists all the issues that may be seen if the wrong sensor is plugged into a port on the Netbotz 550 or 570.

This attachment references the following sensors:
Temp
Temp / humidity
Smoke
Vibration
0-5 volt cable
Spot leak
Rope Leak
Beacon
Dry contact
Ethernet
Door
A-Link


plugged into the following ports:
Universal Sensor port 1-6
Rope port
Beacon port
Ethernet port
A-Link port

NetBotz v3 | Serial connection issues

Issue:
Issues connecting serially to a v3 NetBotz appliance.

Product Line:
NetBotz v3 Wall Appliance: 355/356 (NBWL0355/6) & 455/456 (NBWL0455/6)
NetBotz v3 Rack Appliance: 450/451 (NBRK0450/1), 550 (NBRK0550), & 570 (NBRK0570)

Environment:
NetBotz v3 (all versions)

Cause:
NetBotz version 3 appliances have integrated USB to serial adapters to allow connecting to the appliance using a USB-A to USB-B cable.  The USB connection to the appliance may not work properly without installing the required FTDI serial driver first.

Resolution:

Download and Install the driver from FTDI
Issues with USB 3.0 Ports from some manufacturers
 
Download and Install the driver from FTDI

1) Navigate to https://www.ftdichip.com/Drivers/VCP.htm
2) Download the driver as a setup executable.


3) Once downloaded run the setup executable to install the necessary drivers.
4) The USB cable may need to be unplugged and plugged back in to establish the proper serial connection.
5) There should now be an entry for a USB Serial communication port under Ports (COM & LPT).
 
Issues with Windows 7 USB 3.0 ports with FTDI driver

After installing the correct driver, the NetBotz Appliance may still show as an unknown device within the device manager when using a USB 3.0 port on a Windows 7 system.  To allow the driver to work properly, connect to the appliance using a USB 2.0 port. More information about the issue can be found on the FTDI site here:
https://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_152_USB_3.0_Compatibility_Issues_Explained.pdf
 

NetBotz 570/450: Beacon set to alarm for multiple threshold turns off after first alarm clears.

Issue:

NetBotz 570/450: Beacon set to alarm for multiple threshold turns off after 1 alarm clears.

Product Line:

NetBotz

Environment:

NetBotz 450, 550, 570 appliances.

Cause:

Any alarm that causes a state change is simply changing the relay or beacon logically from a 0 to a 1. Off to on. In the case of the beacon or a relay output, The alarm will cause the change to 1 and the clearing will cause the change back to 0. This happens regardless of how many alarms try to change the state to on or 1. It only needs a single state change to off or 0 to turn it off even if multiple other sensors are still in an alert state.

Resolution:

Probably the best workaround for this would be to edit the alert profile. Next, edit the alert sequence that calls the select beacon or relay alert action. Edit the sequence so that it repeats until the alarm returns to normal. In this way, even if another threshold changes to normal and turns off the beacon, the still alerting sensor will turn the beacon back on in at most 1 minute (or whatever time you have chosen for the interval. Do not leave the interval at 0.). 


An alternative option would be to set the alert action to not change the state after the alarm clears. This will leave the state on (or off) and would require the user to validate the current alarms and manually turn off the beacon.

 

NetBotz v3 | How do I enable/disable SNMP?

Issue:
Issues connecting serially to a v3 NetBotz appliance.

Product Line:
NetBotz v3 Wall Appliance: 355/356 (NBWL0355/6) & 455/456 (NBWL0455/6)
NetBotz v3 Rack Appliance: 450/451 (NBRK0450/1), 550 (NBRK0550), & 570 (NBRK0570)

Environment:
NetBotz v3 (all versions)
NetBotz v2 (all verisons)

Resolution:

Enable SNMP on a v3 NetBotz Appliance

1) Download and install the Advanced View Application.  Instructions for download can be found in knowledge base FA230223.
NOTE: If Advanced View is already installed, skip step 1.

2) Log into your NetBotz appliance as an administrator using the Advanced View application.

3) Select the Configuration tab and then under Appliance Settings navigate into SNMP.

4) Check the box for Enable SNMP agent.

5) Fill out the information within Version 1/Version 2c or Version 3 tabs.
NOTE: SNMPv3 settings are based on user profiles.  For user profile configuration see knowledge base FA323442.

6) Select OK to save the settings.


Disabling SNMP 

1) Download and install the Advanced View Application.  Instructions for download can be found in knowledge base FA230223.
NOTE: If Advanced View is already installed, skip step 1.

2) Log into your NetBotz appliance as an administrator using the Advanced View application.

3) Select the Configuration tab and then under Appliance Settings navigate into SNMP.

4) Uncheck the box for Enable SNMP agent.
NOTE: Specific SNMP portocol versions can not be individually enabled/disabled.  SNMP is either enabled/disabled as a whole protocol.

6) Select OK to save the settings.

NetBotz v3 | Camera POD 160A appears to not function properly

Issue:
Why does the Camera POD 160A appear to not work with the NetBotz appliance it is connected to?

Product Line:
NetBotz v3 Wall Appliance: 455/456 (NBWL0455/6)
NetBotz v3 Rack Appliance: 450/451 (NBRK0450/1), 550 (NBRK0550), & 570 (NBRK0570)
NetBotz v3 Accessories: Camera POD 160A (NBPD0160A)

Environment:
NetBotz v3 (firmware below 4.6.2)
NetBotz Camera POD 160A

Cause:
Newer NetBotz Camera Pods (NBPD0160A) are running a hardware revision that are not compatible with older NetBotz firmware. This causes the camera to appear failed and not register on the main NetBotz unit. 

Resolution:

Updating the NetBotz appliance to firmware version 4.6.2 or later will correct the problem.  If you have upgraded or are already running 4.6.2 or later and are still experiencing difficulties, contact technical support.
Please note that this could also happen on a NetBotz 355A or 455A with the on-board camera with firmware prior to 4.6.2..

Verifying NetBotz Appliance Firmware Revision

1) Log into the NetBotz appliance using the Advanced View application.
NOTE: For instructions on downloading Advanced View, see knowledge base FA230223.

2) Select the About tab.

3) The firmware revision will be listed in the Bootstrap Version field.


Upgrade NetBotz Appliance Firmware

Instructions on upgrading a NetBotz appliance firmware can be found within knowledge base FA158254.

 

IPMI Overview

Issue:

IPMI Overview

Product Line:

Netbotz

Environment:

NetBotz Version 2 and 3 appliances

Cause:

IPMI is a protocol supported by NetBotz appliance for monitoring 3rd party devices (mostly servers).

Resolution:


What is IPMI?
  • Intelligent Platform Management Interface (IPMI) is a relatively new technology designed to extend customers' IT capabilities and further improve remote management across their hardware platforms by providing an easy to use and scalable interface into their server’s hardware at a physical level.
  • Implemented on server’s baseboard management controller chip, independent of CPU and OS but uses existing Ethernet already on the system.

How does IPMI work?
  • A separate processor called a Baseboard Mgmt Controller (BMC) runs along side the core/main processor in a system to allow monitoring of the system’s status, environmental info, etc internally, regardless of the health of the core processor.
  • The BMC communicates with the system board both internally and externally, to provide for remote management and monitoring of the system.
  • IPMI is a self-describing environment, providing for easy integration into third party software applications (NetBotz).


NetBotz Support of IPMI
  • IPMI allows NetBotz to monitor physical characteristics of IPMI-enabled servers and network equipment:
    • Temperature, Voltage, Fan status
    • Midrange & enterprise servers will have multiple of each type of sensor
    • NetBotz appliances polls the IPMI device via the TCP/IP network using the IPMI protocol similar to how NetBotz polls SNMP devices.
  • NetBotz BotzWare 2.4 supports IPMI version 1.5 and 2.0 devices
  • BotzWare 2.4 (and later) supports monitoring only
  • Since IPMI is self-describing, manufacturers provide recommended threshold settings. This means that when an IPMI device is added to BotzWare 2.4, default thresholds are automatically created on the NetBotz appliance.
  • IPMI is supported on the NetBotz 500, 420, 320 with a valid Premium Software Module key installed
  • IPMI is supported on the NetBotz 450, 455, 550, and 570 units with a 5 node monitoring pack (NBWN0006) installed.
  • Default Port for IPMI is UDP 623.
  • IPMI must be supported and configured on the target device.

NetBotz | Hardware & Software Support Information and Limits

Issue:
   Description of NetBotz warranty extensions and limitations.

Product Line:
   NetBotz (all appliances)

Environment:
   NetBotz Hardware Warranty & Software Support

Resolution:

NetBotz 750
The NetBotz Rack Appliances 750 has a software/hardware support limitation of 5 years (2 years factory with 3 years of purchasable extensions).  All attached downstream NetBotz Sensors and NetBotz Sensor Pods are covered under the extended warranty of the NetBotz Appliance, except for consumables, such as wireless sensor batteries (covered under Wireless Sensor factory warranty only).
  Year 1 Year 2 Year 3 Year 4 Year 5 Year 6
  Software Support &
Hardware Support  
  Factory Warranty     WBEXTWAR1YR-NB-07     WBEXTWAR1YR-NB-07     WBEXTWAR1YR-NB-07     Out of Support  
  WBEXTWAR3YR-NB-07     Out of Support  

NetBotz 250 / NBACS125 / NBACS1356
The NetBotz Rack Appliances 250 has a software/hardware support limitation of 5 years (2 years factory with 3 years of purchasable extensions).  All attached downstream NetBotz Sensors and NetBotz Sensor Pods are covered under the extended warranty of the NetBotz Appliance, except for consumables, such as wireless sensor batteries (covered under Wireless Sensor factory warranty only).
  Year 1 Year 2 Year 3 Year 4 Year 5 Year 6
  Software Support &
Hardware Support  
  Factory Warranty     WBEXTWAR1YR-NB-02     WBEXTWAR1YR-NB-02     WBEXTWAR1YR-NB-02     Out of Support  
  WBEXTWAR3YR-NB-02     Out of Support  

NetBotz 200
The NetBotz 200 is limited to the 2 year factory warranty only, which can not be extended.

NetBotz 355/355A & 455/455A
The NetBotz Rack Appliances 355 and 455 have a software/hardware support limitation of 5 years (2 years factory with 3 years of purchasable extensions).  A base 2 year software support contract must be purchased alongside the factory warranty.  All attached downstream NetBotz Sensors and NetBotz Sensor Pods are covered under the extended warranty of the NetBotz Appliance, except for consumables, such as wireless sensor batteries (covered under Wireless Sensor factory warranty only).
  Year 1 Year 2 Year 3 Year 4 Year 5 Year 6
  Software Support     WNBWN001     WNBWN003     WNBWN003     WNBWN003     Out of Support  
  Hardware Support     Factory Warranty     Out of Support  

NetBotz 450 & 570
The NetBotz Rack Appliances 450 and 570 have a software/hardware support limitation of 5 years (2 years factory with 3 years of purchasable extensions).  A base 2 year software support contract must be purchased alongside the factory warranty.  All attached downstream NetBotz Sensors and NetBotz Sensor Pods are covered under the extended warranty of the NetBotz Appliance, except for consumables, such as wireless sensor batteries (covered under Wireless Sensor factory warranty only).
  Year 1 Year 2 Year 3 Year 4 Year 5 Year 6
  Software Support     WNBWN002     WNBWN004     WNBWN004     WNBWN004     Out of Support  
  Hardware Support     Factory Warranty     Out of Support  
 
 

NetBotz v3 | How do I manage user credentials and login alerting?

Issue:
Process for configuring user credentials and login alerting on a version 3 NetBotz appliance.

Product Line:
NetBotz v3 Wall Appliance: 355/356 (NBWL0355/6) & 455/456 (NBWL0455/6)
NetBotz v3 Rack Appliance: 450/451 (NBRK0450/1), 550 (NBRK0550), & 570 (NBRK0570)

Environment:
NetBotz v3 (all versions)

Resolution:

TIP: 
To ensure security, change the default Administrator account User name and Password.
NOTE: The Guest and Administrator Accounts are permanent and cannot be removed. Their settings can be modified.
NOTE: If you give the Guest account any set of privileges other than "None", you are effectively giving unauthenticated users access to the features of the device. The security of the appliance's network should be considered before taking this step.

Accessing User Settings
Editing an Existing User
Creating a New User
Login Alerting Settings
 
Accessing User Settings

1) Log into the NetBotz appliance using the Advanced View application.
NOTE: For instructions on downloading Advanced View, see knowledge base FA230223.

2) Select the Configuration tab.

3) Under Appliance Settings, double-click into Users.
 
Editing an Existing User

1) Select a user from the list and click Edit.
NOTE: The default Guest and Administrator Accounts are permanent and cannot be removed. Their settings can be modified, with the exception of the Administrator account's privilege set.

2) The following information can be edited:
- Name: Descriptive name that displays in the Users list.
- User Name: Username used for authentication.
- Password (Verify Password): Password used in combination with the User Name for authentication.

3) Click OK to save the changes.
 
Creating a New User

1) Select Add below the Users list.

2) Provide the following information:
Name:  Descriptive name that displays in the Users list.
- User Name: Username used for authentication.
- Password (Verify Password): Password used in combination with the User Name for authentication.

3) Chose a Privilege Set (Listed below) from the drop down list and then click OK.
Privilege Set Description
Administrator Gives user access to all information and configuration icons.
Application Gives user access to only the Navigation, Sensor Data, and selected portions of the Information/Action panes. User accounts configured with the Application privilege set can view the Cameras, Graphs, Alerts, and About panes.
Application (with Alert Update) Gives user access to only the Navigation, Sensor Data, and selected portions of the Information/Action panes.
The user can also resolve alert conditions for thresholds that are configured with the Return-To-Normal Requires User Input setting in their Advanced Settings. This privilege set does not permit access to the configuration pane.
Sensor Gives user access to only the Navigation, Sensor Data, and selected portions of the Information/Action panes. User accounts configured with the Sensor privilege set can view the Cameras, Graphs, and About panes.
This privilege set does not permit access to the Alerts pane, or to the Appliance Log, Change Root Password, and Reboot Appliance Tool menu selections.
Sensor (No Camera) Gives user access to only the Navigation, Sensor Data, and selected portions of the Information/Action panes. User accounts configured with the Sensor (No Camera) privilege set can view Graphs and About panes.
This privilege set does not permit access to the Cameras pane, Alerts pane, Configuration pane, or to the Appliance Log, Change Root Password, and Reboot Appliance Tool menu selections.
None Does not permit access to any of the appliance features.
 
Login Alerting Settings

Login failure alert severity can be set to any of the following: None, Informational, Warning, Error, Critical, or Failure (default).

Login failure alert profile to can set to any of the defined alert profiles to provide a login failure security email.

How to I monitor NetBotz alarms using Modbus?

Issue:
Monitoring alarms on NetBotz using Modbus.
 
Product Line:
NetBotz
 
Environment:
NetBotz 550
NetBotz 570
NetBotz 450 (with Advanced Software Pack)
NetBotz 455 (with Advanced Software Pack)
 
 
Cause:
This is just a guide showing how to monitor NetBotz events using Modbus. Modbus output is not available on the 4xx units by default.
 
Resolution:
 
In this example, I have configured a NetBots 570 with a rack access pod NBPD0171. I want to see when there is a forced entry into a rack door being monitored by this NetBotz configuration. Any supported firmware should work but in this case, I have used version 4.5.2.
There is no way using Modbus to know the exact error message. Based on the return values and the register maps, you can tell what sensor is in an error state and you can tell what level of event is occurring. Let me first state that this mimics the DCE modbus output and you can use the following document (at least the beginning of it) to figure out the level of alarm:
https://www.apcmedia.com/salestools/JRUK-7R4L9N/JRUK-7R4L9N_R3_EN.pdf?sdirect=true
This is app note 156 and the link may change over time.
 
First, Enable the Modbus output on the “Modbus Slave Communications” applet in NetBotz Advanced View (AV). On a 4xx unit, you must first install the advanced software pack. On a 5xx unit, this is enabled by default. 3xx units and older version 2 units does not support this feature.

This example is using Modbus over TCP but there is a serial option. Please see the user manual for your unit as to how to use the serial connections.
 
Next, using the ”Modbus Slave System” applet in AV, find the appropriate pod. In this case, I am using Rack Access Pod 170 (03)

 
Click “Modify Pod Settings” and you will be able to give the pod a slave address and create a register map for all it’s sensors:


After this configuration, you can view and subsequently export the register map back on the “Modbus Slave System” page.
You will see the alarms configured this way (and more):
all   30992(0x7910)  Alarm #03                                                         002     UINT16       RO      Alarm - Alarm Code + Corresponding Sensor
 all   30994(0x7912)  Alarm #02                                                         002     UINT16       RO      Alarm - Alarm Code + Corresponding Sensor
 all   30996(0x7914)  Alarm #01                                                         002     UINT16       RO      Alarm - Alarm Code + Corresponding Sensor

You will also see each pod as it’s own slave. Here you can see the main unit as slave 1 and the NetBotz 170 pod as slave 2:
 
001   31000(0x7918)  NetBotz Rack Monitor 570:Ethernet Link Status                     002     INT16        RO      Value - 0(Down), 1(Up)
 001   31002(0x791a)  NetBotz Rack Monitor 570:A-Link Bus Power                         002     INT16        RO      Value - 0(OK), 1(Overloaded)
 
 002   31000(0x7918)  Rack Access Pod 170 (03):Handle  (2)                              002     INT16        RO      Value - 0(Up), 1(Down)
 002   31002(0x791a)  Rack Access Pod 170 (03):Handle  (1)                              002     INT16        RO      Value - 0(Up), 1(Down)
 002   31004(0x791c)  Rack Access Pod 170 (03):Lock  (1)                                002     INT16        RO      Value - 0(Unlocked), 1(Locked)
 002   31006(0x791e)  Rack Access Pod 170 (03):Reader  (2)                              002     INT16        RO      Value - 0(Disabled), 1(Enabled)
 002   31008(0x7920)  Rack Access Pod 170 (03):Reader  (1)                              002     INT16        RO      Value - 0(Disabled), 1(Enabled)
 002   31010(0x7922)  Rack Access Pod 170 (03):Door  (1)                                002     INT16        RO      Value - 0(Open), 1(Closed)
 002   31012(0x7924)  Rack Access Pod 170 (03):Lock  (2)                                002     INT16        RO      Value - 0(Unlocked), 1(Locked)
 
Please note that each register is actually listed as 2 numbers higher than the last. This is because each sensor is configured as 2 registers. If you're looking for data on a specific register say 31000, you actually have to pull 31000 and 31001. Note the register in bold is 31010. To get the data for this sensor, you need to pull 31010 and 31011. It also shows this is the door sensor and the value should be 0 for open and 1 for closed. Knowledge base FA214410 can assist if you’re unsure how to use dual registers but it should not be necessary in this specific instance.
 
Next, when you poll for alarms, you poll register 30999. This  shows how many alarms there are. Register 30998 shows the highest severity of the alarms if there are multiple. For each alarm, you should read 2 registers back. In this case there is 1 alarm so reading 2 registers before the 30998 is 30997 and 30996.
 
In this image from AV, you can see the door is open and in an error state:

 
Upon polling the device’s IP and slave address 2, you can see that 31010 and 31011 (31011 is the important one) is reading 0. This means from the register map that the door is open. Value - 0(Open), 1(Closed)
 

Here is what that same register looks like if I close the door:

 
 
Putting the door back in alarm, you can see that 30999 is 1 meaning there is 1 error and 30998 is 2 which means it is level 2 (error)....the latter is defined in the DCE app note 156 linked above.

 
The register 30997 above reports the sensor. The return is 31010. This matches the register on that door sensor as shown in the register map. The register 30996 reports the actual error. This is also defined in the DCE app note. It's in HEX in the app note so you have to show the return in hex as I am doing here:

 
Note that 30996  is reporting 000E. If you check the device alarm codes here (again from app note 156), you'll see that 000E relates to "General Device Alarm":

 
So with this information, I opened a door with a locked handle and the information I pulled via Modbus shows that sensor (register) 31010  is in an alarm state of general device alarm and it is an error level. Looking at the register map I can tell that 31010 (remember, it's 2 registers on a sensor) is a door sensor and since it's return is 0, the door is open. You can also check the other sensors such as handle to see if it is down or check the lock to ensure it is locked etc.