Analog Alarms. Remote Automation Solutions OpenEnterprise NW3000
Add to My manuals32 Pages
Remote Automation Solutions OpenEnterprise NW3000 is a network gateway device that allows you to integrate your Bristol devices with other systems, such as a SCADA system or a historian. It supports a variety of communication protocols, including Modbus, DNP3, and OPC UA. This allows you to connect to a wide range of devices, regardless of their manufacturer.
The NW3000 also provides a number of features that make it easy to manage and monitor your devices. These features include:
- A web-based interface that allows you to configure and monitor the device from anywhere in the world
- Remote alarm support that allows you to receive alarms from your devices via email or text message
advertisement
![Analog Alarms. Remote Automation Solutions OpenEnterprise NW3000 | Manualzz Analog Alarms. Remote Automation Solutions OpenEnterprise NW3000 | Manualzz](http://s1.manualzz.com/store/data/008460384_1-128800b4516a0c04e7fe400b0c9c11ba-360x466.png)
Reference Guide
D301509X412
April 2012
3.6.10 Analog Alarms
NW3000 Setup
If checked, the following additional alarm states will be collected for analog signals that are not designated as RBE.
InHiHiAlarm
InHiAlarm
InLoAlarm
InLoLoAlarm
HighHighAcknowledged
HiAcknowleged
LoAcknowledged
LoLoAcknowledged
3.7 Signal Import Options
This dialog enables the user to fine tune their database build. The options apply to the NW3000
Database Builder, and affect how it builds Bristol signals into the database.
- 13 -
Reference Guide
D301509X412
April 2012
NW3000 Setup
If checked, this option will ensure that device system signals are included in the database build.
Enables RTU names with mixed upper and lower case characters to be defined (e.g. Memphis,
Area1) when adding devices and signals into the OpenEnterpriseObjectServer database. By default, all RTU names are converted to uppercase in the database (e.g. MEMPHIS, AREA1).
- 14 -
Reference Guide
D301509X412
April 2012
NW3000 Setup
If a build occurs for an RTU with mixed case characters without this option checked, the RTU name will be inserted into the database in upper case characters, and all its signals will be preceded and identified by the uppercase RTU name followed by a colon (e.g. MEMPHIS:PUMP1.RUNNING.001).
If a subsequent build for the same RTU occurs, but with this option checked, the NW3000 Database
Builder will ask for confirmation before inserting the device and its signals into the database.
This time, the mixed case name will be used. The previous entries for the same device and its signals with the capitalized name will NOT be deleted from the database. However, the NW3000 Database
Builder will only now recognize the capitalized name for the RTU.
- 15 -
Reference Guide
D301509X412
April 2012
NW3000 Setup
Checking this box will ensure that the DataBase Builder resolves the Control Wave device signal addresses, also known as MSD (Master Signal Directory) numbers. This must be checked in order for the Poll List Builder to create poll lists for Control Wave device's.
- 16 -
Reference Guide
D301509X412
April 2012
NW3000 Setup
When selected, ControlWave signal names will be converted to ACCOL signal name format (i.e.
<BASE>.<EXTENSION>.<ATTRIBUTE>).
When checked, the NW3000 Database Builder will use the 'Variable Extension Wizard' settings from the ControlWave load to determine alarm signals for ControlWave RTUs.
The default setting is for this and the 'Look for _ALM in name' option to be unchecked. This causes the NW3000 Database Builder to mark all signals as alarms.
When checked, the NW3000 Database Builder will look for signals with names that contain '_ALM' to determine alarm signals for ControlWave RTUs.
The default setting is for this and the 'Use variable extension wizard' option to be unchecked. This causes the NW3000 Database Builder to mark all signals as alarms.
3.8 System Set-up Summary
This is the final dialog displayed for the 'System Set-up' wizard. It enables the user to view the configuration parameters defined. Should anything require changing, the user is able to navigate back to the appropriate dialog to make the necessary changes prior to finalizing the system configuration.
Selecting the [Finish] button will update the server database with the requested configuration.
- 17 -
advertisement
Related manuals
advertisement
Table of contents
- 7 Automatically Start OpenBSI
- 7 Automatically Stop OpenBSI
- 7 Network Definition File
- 7 Number of seconds between subsequent start attempts
- 7 Number of times to retry OpenBSI start-up
- 7 Cancel Button
- 8 Help Button
- 8 Maximum total number of pending requests
- 9 Maximum number of pending requests per device
- 10 Number of seconds between device health checks
- 10 Number of devices per health check
- 10 Number of consecutive failures allowed
- 11 Enable Remote Alarm Support
- 11 Acknowledge Return to Normal Reports
- 11 Critical
- 12 Non-Critical
- 12 Operator Guide
- 12 Event
- 13 RBE Data Collection
- 14 Active Polling for NW3000 Analogs
- 14 Active Polling for NW3000 Digitals
- 14 Active Polling for NW3000 Strings
- 14 Active Polling Frequency
- 15 Include RBE Signals in Active Polling
- 15 Background Polling Frequency
- 15 One Shot Poll
- 15 Maximum Interval
- 15 Offset
- 16 Analog Alarms
- 21 System Setup Finish Button
- 22 All Devices
- 23 Single Device
- 23 Use Settings
- 24 Enable RBE Data Collection for Device
- 24 Scan Rate
- 24 Scan Slice
- 24 Timeout
- 25 StopXmit
- 26 Use Settings Here for Polling Support
- 26 Create a Unique Timeclass for each Device
- 26 Polling Frequency
- 28 Device Setup Finish Button