Compact control builder AC800M
Hi,
Can anyone help me with a specific task?
To make a log-file.
I need to log every stop of the mashine.
Is there any Function Block that i can use in Compact control builder AC800M?
The time of the stop, with a specific error-Code and also which diferent category-group it falls in to?
I know there is something similar in 800xA, sadly i don have the software.
Hopefully there is a kind soul that could guide me through this task?
Kind regards
Sebastian
Can anyone help me with a specific task?
To make a log-file.
I need to log every stop of the mashine.
Is there any Function Block that i can use in Compact control builder AC800M?
The time of the stop, with a specific error-Code and also which diferent category-group it falls in to?
I know there is something similar in 800xA, sadly i don have the software.
Hopefully there is a kind soul that could guide me through this task?
Kind regards
Sebastian
Asked 5 months ago
Voted best answer
3
In controller application
Create an AlarmEventLib:SimpleEventDetector emitting a suitable message.
Use a unique SourceName
The message string can be composed with letters, numbers, etc. as you like.
Alarm Event Translator aspects can be used to perform NLS conversion and save you from entering long strings into the controller code. E.g. the cryptic string "||AEMSG001 A 12.379999999 BF20" can be translated to "Unit A, too low temperature 12.4ºC, recipe variant BF20" which is stored in Event Storage (default 10.000 events, can be increased to 50.000, potentially a bit more).
Set a distinct Class (1,,10000).
In Compact System
Make sure there is an Event Collector service group connected to the AC 800M OPC Server
Make sure there is Alarm Event Translator created for "||AEMSG001"
Make sure there is an object created with the object name set to the SourceName you selected in the application. Or use a Controller Name aspect to map the PLC's SourceName to an arbitrary named object.
Create an Event List with filter for Category = Process Simple Event and the class number you selected. Potentially put the list aspect on the object having the SourceName and select "Object Alarms Only" in the Special Configuration. There are numerous of methods available to filter for severity, class, object, hierarchy, attributes, etc.
Create an Excel report using the DataDirect and ABBAERetrieval() function. Query the event list you created in the previous step. Find a way to know "start time", etc. so that you can filter out "previously fetched events" avoiding duplicate output (or look at last row of the output file). Hint: fetch data to one tab, use formula to copy data to second tab, format the data the way you like, use Excel Macro code to save (append) the results to a text file and update the "last received time", etc. so that repetitive executions does not duplicate the same message over and over again.
Use the Scheduler service to schedule the report as often you need (don't do it every minute, every hour, shift or day sounds more reasonable). Execution can also be triggered on OPC DA data changes.
The DataDirect and Scheduler functions are documented in the IM Data Access and Reports User's Guide, 3BUF001094-610
If you just want the messages to a file with no fuzz; skip using the system, get Visual Studio (or hire a developer/contractor) and implement an OPC AE client which you connect directly to the OPC AE server and then relays the desired events to a file.
Create an AlarmEventLib:SimpleEventDetector emitting a suitable message.
Use a unique SourceName
The message string can be composed with letters, numbers, etc. as you like.
Alarm Event Translator aspects can be used to perform NLS conversion and save you from entering long strings into the controller code. E.g. the cryptic string "||AEMSG001 A 12.379999999 BF20" can be translated to "Unit A, too low temperature 12.4ºC, recipe variant BF20" which is stored in Event Storage (default 10.000 events, can be increased to 50.000, potentially a bit more).
Set a distinct Class (1,,10000).
In Compact System
Make sure there is an Event Collector service group connected to the AC 800M OPC Server
Make sure there is Alarm Event Translator created for "||AEMSG001"
Make sure there is an object created with the object name set to the SourceName you selected in the application. Or use a Controller Name aspect to map the PLC's SourceName to an arbitrary named object.
Create an Event List with filter for Category = Process Simple Event and the class number you selected. Potentially put the list aspect on the object having the SourceName and select "Object Alarms Only" in the Special Configuration. There are numerous of methods available to filter for severity, class, object, hierarchy, attributes, etc.
Create an Excel report using the DataDirect and ABBAERetrieval() function. Query the event list you created in the previous step. Find a way to know "start time", etc. so that you can filter out "previously fetched events" avoiding duplicate output (or look at last row of the output file). Hint: fetch data to one tab, use formula to copy data to second tab, format the data the way you like, use Excel Macro code to save (append) the results to a text file and update the "last received time", etc. so that repetitive executions does not duplicate the same message over and over again.
Use the Scheduler service to schedule the report as often you need (don't do it every minute, every hour, shift or day sounds more reasonable). Execution can also be triggered on OPC DA data changes.
The DataDirect and Scheduler functions are documented in the IM Data Access and Reports User's Guide, 3BUF001094-610
If you just want the messages to a file with no fuzz; skip using the system, get Visual Studio (or hire a developer/contractor) and implement an OPC AE client which you connect directly to the OPC AE server and then relays the desired events to a file.
by sebbe_mena Rank: 1006 on 1/14/2021 7:10:42 AM | Like (0) | Report
CPU: PM861/ TP830
Add new comment