Troubleshooting iFIX 5.8 Alarm Horn Activation Issues

Question:

Hello, I am experiencing difficulty with activating the alarm horn during alarm events. I have ensured that the horn is enabled in the SCU and have also verified its functionality using a pushbutton. Despite it seeming like a minor issue, I would be grateful for any assistance. Additionally, I have redundant database servers and am utilizing a terminal server for client access. Your help is much appreciated. Thank you in advance.

Top Replies

If my memory serves me right, there is a method to activate or deactivate the horn from within the program. This means that even if the horn is configured in the SCU, it can still be controlled through the application. It might be wise to verify if someone has deactivated it in the code.

Thanks Parky for your input. I double-checked and confirmed that the horn is indeed enabled, as indicated by the horn status pushbutton I tested. During my research, I came across an article on troubleshooting sound issues in Windows Terminal Server sessions. I have a hunch that the problem lies on the Windows end. If anyone could verify my suspicion, it would be greatly appreciated. Recently, we upgraded the terminal server to Windows 2016, and although I am not an expert in server management, I am going to attempt some solutions.

It sounds like you've done some thorough troubleshooting already! Have you checked the configuration settings for alarm priority levels? Sometimes, alarms may not activate the horn if there's a higher priority event or if the alarm handling is set incorrectly. Also, you might want to confirm that there aren't any overrides or filters applied that could be suppressing the horn activation. If all else fails, I’d recommend reaching out to your system’s support team, as they might have more insight into any quirks specific to your setup. Good luck!

It sounds frustrating to deal with that, especially when you've checked the basic settings. Have you tried looking into the alarm event configuration to ensure that the conditions for triggering the horn are correctly set? Sometimes, the issue can be tied to event priority settings or even conflicting configurations on the terminal server. It might also be helpful to check the logs for any error messages that could give you a clue about what's going wrong. Good luck, and I hope you get it sorted out soon!

It sounds like you've done a thorough job of troubleshooting already! One thing to double-check is whether there are any specific alarm event configurations that might be affecting the horn activation. Also, consider looking into the permissions set on your terminal server, as they might be influencing how the alarm horn behaves during those events. Sometimes, it can be a simple oversight in settings. If all else fails, reaching out to your system's support can yield quick answers too. Good luck!

More Replies →

Streamline Your Asset Management
See How Oxmaint Works!!

✅   Work Order Management

✅   Asset Tracking

✅   Preventive Maintenance

✅   Inspection Report

We have received your information. We will share Schedule Demo details on your Mail Id.

You must be a registered user to add a comment. If you've already registered,
sign in. Otherwise, register and sign in.

Frequently Asked Questions (FAQ)

FAQ: FAQs:

Answer: 1. How can I troubleshoot alarm horn activation issues in iFIX 5.8? - To troubleshoot alarm horn activation issues in iFIX 5.8, ensure that the horn is enabled in the SCU and verify its functionality using a pushbutton. Check for any potential configuration errors or conflicts that may be preventing the alarm horn from activating during alarm events.

FAQ: 2. What steps should I take if the alarm horn is not activating despite being enabled in the SCU?

Answer: - If the alarm horn is not activating despite being enabled in the SCU, consider checking the wiring connections to ensure proper functionality. Additionally, review the alarm configuration settings to confirm that the correct triggers and conditions are set for the alarm events.

FAQ: 3. How can redundant database servers and a terminal server impact alarm horn activation in iFIX 5.8?

Answer: - Redundant database servers and a terminal server for client access can introduce additional complexity to the system architecture. Ensure that the communication paths between servers and clients are configured correctly to avoid any disruptions that may affect alarm horn activation. Consider reviewing network configurations and server settings to address any potential issues related to redundancy and client access.

Ready to Simplify Maintenance?

Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.

Request Demo  →