Greetings everyone, I am reaching out for the first time with a technical issue that has been causing me quite a bit of frustration. I have a set up with two FTView SE Local Stations, each running on a separate PC. The working station is running on version 11 on a Windows 10 PC, while the other station, which is experiencing issues, is running on version 13 on a Windows 11 PC. The version 13 project was created from the version 11 project. The problem I am encountering is with the FTAE on the version 13 Client. Only one alarm is showing up, while the rest are not appearing. In the Alarm Faults window, all FTAE tags are showing as Bad Quality - Configuration Error. This issue is causing the Fault Limit Exceeded error. I have tried re-exporting and re-importing the alarms from the version 11 project into the version 13 project, but the problem persists. I have also compared the version 11 and version 13 FTView Studio projects, but have not been able to identify any differences that could be causing the issue. Despite these challenges, everything else on the version 13 HMI is functioning properly. The alarms update correctly on the version 11 HMI, indicating that the problem is specific to the version 13 HMI. I have conducted a Live Data Test Client on the version 13 PC and manually mapped some alarms that were not displaying, and they showed good quality. This suggests that the connection between the HMI PC and the two CLX PLCs is not the issue. I would greatly appreciate any assistance in resolving this issue. I have included images of the errors from FTView Diagnostics and Alarm Faults in the FTView SE Client for reference. Thank you for any help you can provide.
To export the tag alarm and event server to a CSV file, remove it from the project and then recreate it using the same name by importing the CSV. It is important to note that when copying projects, the database may become corrupted.
Robertmee recommended exporting the tag alarm and event server to a CSV file, deleting it from the project, then recreating it with the same name by importing the CSV. It's not uncommon for the database to get corrupted when copying projects. I attempted exporting to .xml within FTView Studio and selecting the "delete and restore" option upon importing, but the error messages persisted.
I have gone to great lengths to address the issues with my FTAE database in FTView SE v13, even going so far as to delete it and start anew. Despite these efforts, the same issues persist. Could there be a compatibility issue between exporting FTAE in v11 and importing into v13? Everything else in my v13 project is functioning properly, leading me to believe it may not be a DCOM-related problem as I have encountered in the past. With nearly 1000 alarms, the thought of recreating the entire FTAE DB is daunting. I will test creating a few new alarms and triggering them to see if they display properly. If successful, it may indicate that recreating the FTAE DB is the solution, albeit at the cost of valuable time. Tomorrow, I plan on contacting Rockwell Tech Connect in hopes of connecting with someone who has experience with this issue.
Hi there, It appears like you've really delved into the issue—kudos for that! One possibility might be incompatibilities between Windows 11 and your FTView SE Version 13. Even if other functionalities are working fine, Windows 11 is relatively new, and there could be undiscovered bugs affecting specific parts of the software. A quick fix might be downgrading your PC to Windows 10, just to see if the problem persists. However, another suggestion would be to carefully check the integrity of the Alarm setup in your version 13 project. Ensure that all alarm tags and trigger values match exactly with your version 11 project. Even a small discrepancy in naming convention or data types can create such issues. Additionally, it would be helpful if you could share the error screenshots you mentioned with the post—visuals usually are pretty helpful for troubleshooting. Hoping you solve this soon!
Hey there, It really does seem like you've done a thorough troubleshoot of this technical issue, kudos for that. It's possible that the discrepancy between the version 11 and version 13 could be causing some conflict. You're right in suspecting that the issue might lie in the configuration, especially since it appears to exist only in the version 13 HMI. One thing could be to double-check your alarm definitions in version 13 to ensure they match with version 11. If you haven't already, you might also want to consider updating patches or potential software service packs related to FTView SE as sometimes certain bugs are resolved with these updates. Do keep us posted, I'm curious to see how this unfolds and if there's anything more that we can do to help!
Hello, It sounds like you've done quite a bit of troubleshooting already. Have you verified that all alarms are enabled in the FTView SE Client alarm setup? Also, considering that your version 13 was created from the version 11 project, you might want to check if the tags were correctly imported. There's a chance that some tags could have been altered or missed during the import. Additionally, make sure that the tag names in your FTView SE Client match those in your CLX PLCs. Hope this helps and let us know how it goes.
Hey there! It sounds like you've done a lot of troubleshooting already. One thing you could check is whether the alarm conditions for the tags in version 13 are set up correctly and match what’s in version 11. Sometimes, even minor changes in the configuration or tag properties can lead to those bad quality errors. Also, make sure that all the necessary tags and databases are properly linked in the version 13 project. If you haven’t already, consider checking for any updates or hotfixes for FTView SE that might address compatibility issues between versions. Good luck!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: The alarms are showing as Bad Quality - Configuration Error in the Alarm Faults window, which is causing the issue. This might be due to a configuration error within the project.
Answer: You can try re-exporting and re-importing the alarms from the version 11 project into the version 13 project. Additionally, conducting a Live Data Test Client and manually mapping alarms can help identify potential configuration errors.
Answer: The Live Data Test Client results suggest that the connection is not the issue. The problem seems to be specific to the version 13 HMI configuration.
Answer: Resolving the configuration errors causing the alarms to show as Bad Quality in the Alarm Faults window should help eliminate the Fault Limit Exceeded error. Conducting thorough checks and comparisons between the version 11 and version 13 projects can help identify and rect
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.