Technical Specifications

FAQ

1. What is the main function of the Bently Nevada 60R/SIM01 System Interface Module?

The 60R/SIM01 is the primary system interface module for an Orbit 60 system. It provides the main access point for system configuration, protection configuration management, diagnostics, system controls, and maintenance activities. The SIM communicates with Orbit Studio and transfers configuration information to the other modules installed in the system. It also manages system-level information such as alarms, event records, diagnostics, firmware updates, and protection status. Because the SIM provides these central management functions, each Orbit 60 system requires one System Interface Module regardless of whether the system consists of a single chassis or multiple interconnected chassis.

2. How many 60R/SIM01 modules are required in an Orbit 60 system?

A single Orbit 60 system requires one 60R/SIM01 System Interface Module. This requirement remains the same even when multiple chassis are connected together as part of a larger distributed system. The SIM provides centralized access to system configuration and maintenance functions rather than requiring an individual interface module for every chassis. This architecture allows engineers to manage the overall protection and monitoring system from a common interface while the other modules perform their specific measurement, processing, monitoring, and output functions.

3. What software is used to configure the 60R/SIM01?

The 60R/SIM01 communicates with the Orbit Studio configuration software, which is used to configure and maintain the Orbit 60 system. Through the configuration environment, engineers can manage protection parameters, module settings, alarm logic, system functions, and other configuration information. The SIM transfers the configured information to the appropriate modules in the system. Before making configuration changes, engineers should verify that the proposed settings are consistent with the machinery protection design and operating requirements. Configuration changes should also be controlled carefully on running machinery because incorrect protection parameters can affect alarm or trip behavior.

4. What are the three Ethernet ports on the 60R/SIM01 used for?

The SIM provides three independently configurable Ethernet ports. Depending on the system configuration, these ports can be used for system configuration, system time synchronization, temporary troubleshooting, or connection to an external display. Separating these functions across configurable ports provides flexibility when integrating the Orbit 60 system into an industrial network. Network connections should be designed according to the site’s communication and cybersecurity requirements, particularly when the machinery protection system is connected to a plant control or monitoring network.

5. What should be checked if the 60R/SIM01 cannot communicate with Orbit Studio?

First, check that the SIM is correctly installed in the designated chassis position and that the module status indicators show normal operation. Then verify the Ethernet connection, cable condition, network configuration, and communication path between the engineering workstation and the SIM. If the physical connection is correct, check whether the selected Ethernet port has been configured for the intended function. The system’s diagnostic information should also be reviewed for communication or module-related faults. If the problem occurs after a configuration change, verify that the network settings and access permissions are still correct. Troubleshooting should proceed from the physical connection through network configuration and finally to the SIM and software configuration.

6. How does the 60R/SIM01 protect the Orbit 60 configuration from unauthorized changes?

The SIM provides a physical configuration security feature using a key-lock switch on the public side of the module and a corresponding contact on the utility side. These controls can be used to secure the system configuration and prevent unauthorized configuration changes. The Orbit 60 architecture also supports controlled user access, allowing configuration permissions to be managed according to the user’s role. When the system is placed in the appropriate protected operating mode, configuration changes that could affect machinery operation can be restricted while users can still access diagnostic information and current system values. This combination of physical and software-based controls helps reduce the risk of unintended changes to critical protection settings.

7. What system-level functions are available through the 60R/SIM01?

The SIM provides access to several important system-level functions, including the alarm list, system event list, system diagnostics, firmware updates, and system controls. The available controls include RUN/PROG mode management, Trip Multiply, System Alarm Inhibit, and System Reset. The SIM also manages the system protection fault relay and provides access to system status information through its indicators. These functions allow maintenance and engineering personnel to monitor the overall health of the Orbit 60 system and perform controlled configuration or maintenance activities without requiring direct access to every individual module.

8. What should be checked if the 60R/SIM01 shows a system fault or abnormal status?

Begin by checking the SIM status indicators and reviewing the system-level diagnostic information to identify the source of the abnormal condition. Verify that the SIM is installed correctly and that the adjacent Power Input Module is operating normally. The system power supply, module connections, communication network, and other installed Orbit 60 modules should also be checked because a system-level fault may originate outside the SIM itself. Review recent event records and configuration changes to determine whether the condition appeared after maintenance or parameter modification. If the fault affects protection functions, the machinery should be handled according to the site’s protection and operating procedures. Avoid unnecessary configuration changes during troubleshooting, as changing multiple parameters at the same time can make it more difficult to identify the original cause.