Om compact control builder AC800M
Hej Stefan,
Hoppas du förstår svenska.. Annars så får jag översätta det till Engelska.
Först o främst ville jag tacka dig för att du lägger ner tid på min fråga.
Jag vill även nämna att jag har aldrig jobbat med ABB-system innan..
I Compact Control Builder AC800M
Finns det redan ett register som visar alla larmen som kommer..
Jag försöker hitta just de blocket..
Hoppas du förstår svenska.. Annars så får jag översätta det till Engelska.
Först o främst ville jag tacka dig för att du lägger ner tid på min fråga.
Jag vill även nämna att jag har aldrig jobbat med ABB-system innan..
I Compact Control Builder AC800M
Finns det redan ett register som visar alla larmen som kommer..
Jag försöker hitta just de blocket..
I Compact Control Builder AC800M.
Under Projectets namn så finns det 3 olika mappar
(Libraries-Applications-Controller)
Under Applications så är det ytterliggare (förutom själva PLC:programmet som vi har kallat det för (PLC_VEMAK.Fast))
4 Mappar som
-"Connected Libraries(där jag har conectat alla 3, AlarmEventLib/BasicLib/IconLib)"
-"Funktion Block Types" (Där finns 3 olika FB)
-"Control Module Types" (Där finns 3 olika FB)
-"Programs" (Där finns 3 olika program, Fast(Maskin)/Normal(Presentation)/Slow(Diagnostik)
Jag har höger klickat och gjort ytterligare ett "program" som jag har kallat för "Data_Logg".
(eller vart ska jag göra den specifika varialbeln för att den ska visas i HMI:et i maskinen)?
När jag öppnar "Data_Logg" programmet och i editorn har jag infört en ny FB ("SimpleEventDetector")
Hur kan jag ändra distinst class (1-10000)?
I Compact control
Hur hittar jag och en "colector service group" och kan jag säkerställa att det är sammankopplat med AC880M OPC Server?
Var hittar en jag Alarm Event Translator?
Jag uppskattar din tid!
Tack!
Asked 4 months ago
Answers
0
I do understand Swedish, my native tongue. However. for the benefit of AKS I will answer in English. I'm not at work right now and I have little means to provide a full detailed answer with images, etc. right now. Therefore this "short" answer until Monday when I might be able to provide something more rich:
Try digging for help about the SimpleEventDetector function block in the OnLine Help of Control Builder M, from my memory I recall the following parameters:
- Signal (boolean, event is generated on positive flank)
- SourceName (string, the name which must match with an object in the HMI, use letters & numbers only, no spaces nor special characters and less than 25 characters in total length)
- Message (string, the text you want to appear in the event list...)
- Severity (Integer, 1-1000, mainly used for sorting purpose)
- Class (Integer, 1-10000, mainly used for categorising purpose)
I might be wrong on a few bits here... anyway, if you are able to download to the controller, a simple event should turn up at the AC 800M OPC Server. A third party OPC AE client (if you have one) should see it as you toggle signal from FALSE > TRUE.
The HMI should already have an Event Collector service group setup in the Service Structure, or else no A&E will be subscribed from the application the controller runs. Likely this has already been taken care of by someone before you, this is not a new installation right? Or else the procedure should be documented in the "Getting Started" manuals, etc. belonging to Compact HMI.
For the HMI to accept the event, a name-to-object match must be made with the incoming event. SourceName in PLC code = Object Name in the system. The easiest is creating an object with the same name in some structure, e.g. Functional Structure. It does not need to have any specific type, a generic object will suffice for the matching to take place. Once accepted, the event can be viewed in many locations, filtered in some custom event list or non-filtered in e.g. the [Workplace Structure]Web System Workplace:Event List that usually has the "grand view" of all process events known to the system.
There is no absolute need to use any translator aspect (Create New Aspect...) if you are happy with what you can generate from the PLC code. However, formatting of a nice human readable text might be easier.in the HMI using a translator, then the PLC only need to send a cryptic string holding the event parameters, e.g. a value, code, etc.). Just start with trying to get a simple word as "Heureka" sent as message text. If the purpose is just to get something written to a file, any word will likely do...
I don't know if I can afford give you a Grand Tour of the system, I'm afraid that will take a tiny bit more time than what can be squeezed into a reasonable sized answer on an open Internet forum...
Try digging for help about the SimpleEventDetector function block in the OnLine Help of Control Builder M, from my memory I recall the following parameters:
- Signal (boolean, event is generated on positive flank)
- SourceName (string, the name which must match with an object in the HMI, use letters & numbers only, no spaces nor special characters and less than 25 characters in total length)
- Message (string, the text you want to appear in the event list...)
- Severity (Integer, 1-1000, mainly used for sorting purpose)
- Class (Integer, 1-10000, mainly used for categorising purpose)
I might be wrong on a few bits here... anyway, if you are able to download to the controller, a simple event should turn up at the AC 800M OPC Server. A third party OPC AE client (if you have one) should see it as you toggle signal from FALSE > TRUE.
The HMI should already have an Event Collector service group setup in the Service Structure, or else no A&E will be subscribed from the application the controller runs. Likely this has already been taken care of by someone before you, this is not a new installation right? Or else the procedure should be documented in the "Getting Started" manuals, etc. belonging to Compact HMI.
For the HMI to accept the event, a name-to-object match must be made with the incoming event. SourceName in PLC code = Object Name in the system. The easiest is creating an object with the same name in some structure, e.g. Functional Structure. It does not need to have any specific type, a generic object will suffice for the matching to take place. Once accepted, the event can be viewed in many locations, filtered in some custom event list or non-filtered in e.g. the [Workplace Structure]Web System Workplace:Event List that usually has the "grand view" of all process events known to the system.
There is no absolute need to use any translator aspect (Create New Aspect...) if you are happy with what you can generate from the PLC code. However, formatting of a nice human readable text might be easier.in the HMI using a translator, then the PLC only need to send a cryptic string holding the event parameters, e.g. a value, code, etc.). Just start with trying to get a simple word as "Heureka" sent as message text. If the purpose is just to get something written to a file, any word will likely do...
I don't know if I can afford give you a Grand Tour of the system, I'm afraid that will take a tiny bit more time than what can be squeezed into a reasonable sized answer on an open Internet forum...
0
See this as an exception to my normal behaviour (of not engaging myself too much in application programming and assisting with developing AC 800M code - I don't have the time, nor mission...)
Below an example of how you can use the SimpleEventDetector from the AlarmEventLib.
Usually Control Builder M will enforce all parameters lacking an initial value (e.g. Severity is 500 by default, can be omitted but SrcName is empty and must therefore be set by the application). Assigning the Error and Status parameters are, in my realm signs of good programming style (but will add weight to the application size and warm start time).
Parameters marked EDIT (red markup in the image below) are so called "edit" parameters and such cannot be changed online without performing a controller reset. SimpleEventDetect's "big brother" is AlarmCond (emitting alarms) and SrcName of big brother is marked EDIT, many are those who have in vain attempted to adjust SrcName and CondName for an alarm without having any effect (until the controller is warmstarted or the owning application is downloaded). Little brother does not have this limitation on SrcName. But watch out when you step up to create alarms... and always check the [Workplace Structure]Web System Workplace:System Event List after application download, an error in SrcName (e.g. uniqueness or use of invalid characters/settings will result in a system message "AlmDefErr", etc.).
I'm using 800xA, therefore the object will be created for me in the system - in your case, make sure SrcName is pointing to a valid object (carrying the same name, or having a Controller Name aspect with that string embedded)
After download I use the CBM Online Editor to push the signal to TRUE after which the event is seen in the HMI's event list
For the HMI to pickup A&E from the application, an Event Collector service group with at least one service provider in Service state is required (how you do this should be stated in the getting started / initial chapters of setting up Compact HMI). The AC 800M OPC Server has to be configured for OPC DA and AE (the latter is made on the right tab and is easily forgotten). Make sure to save panel settings. Below a redundant configuration (in 800xA, but CHMI should look very similar).
Below an example of how you can use the SimpleEventDetector from the AlarmEventLib.
Usually Control Builder M will enforce all parameters lacking an initial value (e.g. Severity is 500 by default, can be omitted but SrcName is empty and must therefore be set by the application). Assigning the Error and Status parameters are, in my realm signs of good programming style (but will add weight to the application size and warm start time).
Parameters marked EDIT (red markup in the image below) are so called "edit" parameters and such cannot be changed online without performing a controller reset. SimpleEventDetect's "big brother" is AlarmCond (emitting alarms) and SrcName of big brother is marked EDIT, many are those who have in vain attempted to adjust SrcName and CondName for an alarm without having any effect (until the controller is warmstarted or the owning application is downloaded). Little brother does not have this limitation on SrcName. But watch out when you step up to create alarms... and always check the [Workplace Structure]Web System Workplace:System Event List after application download, an error in SrcName (e.g. uniqueness or use of invalid characters/settings will result in a system message "AlmDefErr", etc.).
I'm using 800xA, therefore the object will be created for me in the system - in your case, make sure SrcName is pointing to a valid object (carrying the same name, or having a Controller Name aspect with that string embedded)
After download I use the CBM Online Editor to push the signal to TRUE after which the event is seen in the HMI's event list
For the HMI to pickup A&E from the application, an Event Collector service group with at least one service provider in Service state is required (how you do this should be stated in the getting started / initial chapters of setting up Compact HMI). The AC 800M OPC Server has to be configured for OPC DA and AE (the latter is made on the right tab and is easily forgotten). Make sure to save panel settings. Below a redundant configuration (in 800xA, but CHMI should look very similar).
Add new comment