Technical Specifications

FAQ

1. What is the main function of the Bently Nevada 3500/33-A01-B00?
The Bently Nevada 3500/33-A01-B00 is a 16-channel relay module designed for integration into the 3500 Machinery Protection System. Its primary function is to convert alarm and machine-status information generated by monitoring modules into physical relay outputs for external systems. These outputs can be connected to alarm annunciators, PLC or DCS digital inputs, equipment interlocks, control circuits, and machinery shutdown systems. Each relay channel can be configured according to the required protection logic, allowing different machine conditions to control different external outputs. This makes the module useful in applications where several independent protection signals need to be transferred from the 3500 monitoring system to external control and safety equipment.

2. How many relay output channels does the 3500/33-A01-B00 provide?
The 3500/33-A01-B00 provides 16 independent relay output channels. Each channel uses an SPDT relay configuration and can be assigned to a specific alarm, machine status, or measured-variable condition. The 16 outputs are organized into four groups of four channels, providing flexibility when different relay operating modes are required. Because the channels can be programmed individually, one output can be used for an Alert condition, another for a Danger condition, and others for Not-OK status, machine interlocking, or external control functions. This allows a single relay module to handle a relatively large number of discrete protection signals without requiring separate external relay logic for every monitoring condition.

3. Can each relay channel be configured independently?
Yes. Each relay output can be independently configured using the 3500 Rack Configuration Software. The Alarm Drive Logic can be associated with Alert, Danger, Not-OK, and individual measured variables from the monitoring system. AND and OR logic can also be used when multiple conditions need to be combined. For example, a relay can be programmed to operate when a particular vibration channel reaches its Danger level, while another relay can be configured to respond only when two or more specified conditions are simultaneously active. This independent configuration capability provides considerable flexibility when designing machinery protection logic. It also makes troubleshooting easier because each relay channel can be reviewed against its specific alarm source and programmed logic rather than treating all 16 outputs as one common function.

4. What is the difference between Normally Energized and Normally De-energized relay operation?
The relay groups can be configured for Normally Energized (NE) or Normally De-energized (ND) operation depending on the required protection philosophy. In Normally Energized operation, the relay remains energized during normal operating conditions and changes state when the programmed alarm or protection condition occurs. This arrangement can be useful when the external circuit is designed to recognize loss of relay energy as an abnormal condition. In Normally De-energized operation, the relay normally remains de-energized and changes state when its programmed condition becomes active. The correct selection depends on the external control circuit, shutdown strategy, fail-safe requirements, and the expected response of the connected equipment. During commissioning, the actual relay state should always be verified by simulating the relevant alarm condition rather than relying only on the software configuration.

5. What should be checked if one of the relay outputs does not operate correctly?
Troubleshooting should begin with the module’s status indicators. The OK LED should be checked first to determine whether the module is operating normally, followed by the TX/RX indication to confirm communication activity with the 3500 rack. The corresponding channel alarm indication should then be reviewed to determine whether the configured alarm condition is actually active. Using the 3500 Rack Configuration Software, check the affected relay’s Alarm Drive Logic, including the alarm source, Alert or Danger status, Not-OK condition, measured variable, and AND/OR logic. It is also important to confirm that the monitored machine parameter has actually reached the programmed threshold. After the software configuration has been verified, inspect the relay terminals, external wiring, cables, and connected equipment for loose connections or incorrect wiring. If the alarm condition is active and the configuration and external circuit are correct but the relay still does not change state, the individual relay channel and associated hardware should be tested to determine whether the fault is internal to the module.

6. Can the 3500/33-A01-B00 be used for machinery shutdown and interlocking applications?
Yes. The relay outputs can be used for machinery alarm, interlocking, and shutdown functions when integrated into an appropriately designed external protection circuit. A relay can be configured to respond to a Danger condition, Alert condition, Not-OK status, or a selected measured variable. More complex protection logic can be created by combining multiple conditions using AND or OR logic. For example, a shutdown-related output could be configured to respond to a specific critical machine condition, while another output could provide a general alarm indication. When the module is connected to a critical shutdown circuit, the selected relay operating mode should match the overall fail-safe design of the system. The complete protection chain should be tested during commissioning, including the original monitoring signal, relay operation, external wiring, PLC or DCS input, interlock logic, and final equipment response.

7. How does the 3500/33-A01-B00 work with other modules in the 3500 Machinery Protection System?
The 3500/33-A01-B00 functions as the relay output stage of the larger machinery protection system. Other 3500 monitoring modules acquire and process signals from machinery sensors and determine whether configured alarm or status conditions exist. When an Alert, Danger, Not-OK, or selected measured-variable condition is generated, the relay module uses the configured Alarm Drive Logic to determine whether a particular relay should change state. This allows information from different monitoring channels to be used for external relay control. For example, an output can be configured to operate when any one of several monitoring points enters a specified alarm condition using OR logic, while another output can require several conditions to be active simultaneously using AND logic. This arrangement allows the relay module to act as an interface between the internal machinery protection system and external plant control or protection equipment.

8. How should the 3500/33-A01-B00 be installed and commissioned?
The 3500/33-A01-B00 should be installed in a compatible 3500 rack according to the system installation requirements, with the main module installed in the appropriate full-height front slot and its associated I/O module installed in the corresponding rear position. Before commissioning, the module model and configuration should be checked against the machinery protection design to ensure that the correct relay output function is being used. After installation, the 3500 Rack Configuration Software should be used to verify all 16 relay channels, including alarm sources, measured variables, AND/OR logic, and Normally Energized or Normally De-energized settings. Each relay output should then be functionally tested by applying or simulating its configured alarm condition and confirming that the relay changes state as expected. If the outputs are connected to PLC, DCS, interlock, or shutdown circuits, the external signal path should also be tested from the relay contacts through the receiving equipment to the final control action. Critical protection outputs should receive a complete functional test before the machinery is returned to normal operation, and the final configuration and wiring should be documented for future maintenance and troubleshooting.