Greetings everyone! I am currently working on updating an older SE local station application. I have successfully transferred it to FactoryTalk View Studio ver. 8.0 on a 32bit virtual machine, then to my 64bit machine. I have also obtained the PLC file (SLC 5/05) and am simultaneously programming both the PLC and HMI. However, I am facing challenges with setting up alarms. The previous programmer had organized the Alarm tags pointing to file B12 in the HMI, but there is no corresponding data in the PLC program. Upon further investigation, I discovered that file B20 contains the same alarms set up in the HMI. Despite this, the HMI does not reference anything in file B20. I am puzzled as to why this discrepancy exists. I know the alarm system works as I have witnessed it, but I cannot figure out how to configure new alarms. I have included screenshots for reference. Any assistance would be greatly appreciated in resolving this issue.
Have you checked thoroughly for any overlooked elements in the PLC code related to the transfer of data between alarm files? In cases like this, it is recommended to search for ":[" in RSLogix to identify any instances of indirect referencing. It's important to note that indirection may not be visible in the usage view of a data table.
I am truly impressed by your prompt response, thank you! It was surprising to learn that searching for "B12" did not yield results when the format was "B12:[(FILE)]". The file is extensive, making it a daunting task to manually search for B12 within the program. I discovered that the alarm words are being transferred from file B20 to file B12 one word at a time, utilizing a pointer in file N26. This process involves scanning the logic using JMPs until all specified words have been processed in a single go. This is my first experience with SE applications. As I prepare to run the SE client to generate a client file, I am curious if the file will be compatible with the older machine. I will need to gather specs from the machine shortly. While the unit resembles a PanelView on the front, it operates on a Windows platform similar to a standard PC, with a comprehensive interface at the back of the unit (combining screen and hardware components).
My mistake: I just realized that typing "B12" in the search bar brings up the information! I probably should have tried that before posting. I was unaware that the "B12:[(FILE)]" format does not appear in the data table usage.
When using the "B12:[(FILE)]" format, I was unaware that it would not be displayed in the data table usage. The software is unable to accurately predict all potential outcomes of the indirect address, resulting in none of them being marked as used.
In my recent experience working with FactoryTalk SE Local Station, I have discovered that it is possible to downgrade an 8.0 application to a previous version, but not from a 64-bit system to a 32-bit version. Correct me if I am mistaken. To run the local station, a computer is required, often in the form of an industrial HMI. In cases where industrial computers have failed, we have temporarily used laptops as replacements.
Hey there! It certainly sounds like you're caught in an intriguing puzzle. This might seem like a simple suggestion, but you'll want to ensure that there's a clear communication path between HMI and the PLC. Sometimes, one-off tags like those found in B20 might be referenced through indirect addressing, which could explain why they're not immediately visible in the HMI. You might also want to look into transitioning the alarm system to an alarm and event system, which FactoryTalk handles natively. This might streamline the approach, so you're not so reliant on the old, potentially convoluted, setup. Good luck navigating this!
It sounds like you're facing quite the puzzle there! Since the alarms in your HMI are linked to file B12 but exist in B20, it might be worth checking if the previous programmer intended to duplicate or migrate those alarms for some reason. Sometimes older setups have legacy tags that don’t get updated, leading to that sort of disconnect. I’d recommend reviewing the HMI configuration to see if there’s a way to edit or map those alarm triggers directly to the data in B20. Alternatively, it might be helpful to create a new set of alarms in the HMI that point to B20 directly to avoid confusion and ensure you're working with the current data structure. Keep us posted on how it goes!
✅ 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 discrepancy could be due to a misalignment or misconfiguration during the transfer or setup process. It's important to ensure that the Alarm tags in both the HMI and PLC are correctly synchronized and referencing the correct data files.
Answer: - To configure new alarms, you may need to create new Alarm tags in the HMI application and make sure they are properly linked to the corresponding data in the PLC program. Double-check the tag references and ensure they are correctly set up to trigger alarms based on specified conditions.
Answer: - Start by verifying the Alarm tags setup in both the HMI and PLC programs. Check for any discrepancies in file references, data types, or alarm triggers. It may also be helpful to consult the FactoryTalk View Studio documentation or seek assistance from Rockwell Automation support for troubleshooting guidance.
Answer: - When updating an older application, ensure that all components, including the HMI screens, Alarm tags, and PLC programming, are properly migrated and configured in the
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.