4/29/2023 8:17 AM | |
Joined: 7/19/2018 Last visit: 7/23/2024 Posts: 2 Rating:
|
Hi, I have a machine that uses single-use filters/vessels as part of the build process for a batch. I have made a modification to add 2x additional user prompts to one existing step and 1x additional user prompt to another. My PLC stores the entered part number for each prompt, this is then linked to an Alarm Message which is written based on the change in state of an internal tag triggered by a C-Script. When the batch is complete, we generate a report which includes the time, date, message text and part number. For 2 out of the 3 new prompts, when the report is generated, I get the time, date and message text, but the setpoint value is blank or a 0/1. One of the new prompts works correctly. The same process was followed for all, replicating that of the existing prompts. The DB part number values (string) are definitely present and show the correct value in Tag Management and the Internal Tag used to trigger the message is definitely changing state because the alarm text etc. are present. I've tried to create a new PLC variable etc. but nothing seems to be working. The only thing I've noticed with anything conclusive is that in dbo.AlgViewENU there is a difference between the messages that work and the ones that don't whereby the PValue is being logged and the PText is empty, this is the opposite to the ones that are working. I don't know where or how this is configured but as far as I can see, the Tag and Alarm configuration in WinCC are the same and the PLC Tags are the same (strings). I have attached some screenshots but if there's anything anyone has come across similar or could suggest trying, it would be much appreciated. Many thanks, Jake AttachmentWinCC Alarm Issues.zip (221 Downloads) |
Follow us on