GCM Server User manual
Contents
1. See Note below RATIOSTN GENCON GENBIN GENUSD MOTCON VALVECON MMCX GRPALARM DRICONS DRICONE ObjectName The name of the object And the line format for nodes is NODES NODE_yyy man Each field is separated by where NODES NODE_yyy A text where yyy is the node number User Manual 8 2012 04 19 am For example if the node number is 7 then this text should look like this NODE 007 NOTE The following object types shall be set as AI AIPTS AIS AITCS PULSES AIXRS AIS610 AIS620 AIS625 AIS630 AIS635 AIS810 AIS820 AIS830 AIS835 AIC NOTE The following object types shall be set as AO AOS AOXS AOXRS AOS610 AOS650 AOS810 AOS820 AOC NOTE The following object types shall be set as DI DIS DIXS DIS610 DIS620 DIS621 DIS622 DIS635 DIS636 DIS650 DIS651 DIS652 DIS810 DIS811 DIS814 DIS820 DIS821 DIS830 DIS831 DIS885 DIS890 DIC NOTE The following object types shall be set as DO DOS DOXS DOS610 DOS620 DOS625 User Manual 2012 04 19 DOS630 DOS810 DOS814 DOS815 DOS820 DOS821 DOS890 DOC 3 1 Example Of a Area and Source File This example contains objects from process section 00 01 and 02 It also contain 4 nodes node no 2 5 6 and 19 PRO_SEC00 GRPALARM AKA93 111 20 PRO_SEC00 DI AKA93 DI101 PRO_SEC00 MMCX MMCX_001 PRO_SEC00 MOTCON MOTCON_001 PRO_SEC00 VALVECON VALVECON_001 PRO_SEC012. 5 375 6 250 7 125 YES Blocks alarm handling for 0 gt I transitions NO Invoke alarm handling for 0 gt I transitions Since most alarm signals flags are active high AL_TOBLK should be set NO to invoke alarm handling for 0 gt 1 transitions and YES to disable it If both AL_TOBLK and AL_FRBLK is set to YES then the alarm will be treated as a simple event instead of a condition event YES Blocks alarm handling for gt 0 transitions NO Invoke alarm handling for 1 gt 0 transitions Since most alarm signals flags are active high and since alarm handling on return to normal makes little sense AL_FRBLK should normally be set YES If both AL_TOBLK and AL_FRBLK is set to YES then the alarm will be treated as a simple event instead of a condition event YES Flag that blocks generation of text in lists and printouts when the event alarm changes from 0 gt 1 This will block a simple event to be shown in the MB3 A amp E OPC server YES Flag that blocks generation of text in lists and printouts when the event alarm changes from 1 gt 0 This will block a simple event to be shown in the MB3 A amp E OPC server Text Combination code Integer to select if Standard or User defined property text and event text shall be used Standard is text from either MB3 Standard Events txt file MB3 Standard Properties txt file and User defined is text from Event Treat block The combination codes are listed in t
3. AT AK A21 6 10 PRO_SECO01 DI AK A41 8 36 PRO_SEC01 GENUSD G4A32 117 5 PRO_SEC02 DI AKA93 DI338 NODES NODE_002 NODES NODE_005 NODES NODE_006 NODES NODE_019 User Manual 10 2012 04 19 4 Text files When the MB3 A amp E OPC server is installed 5 text files are copied to the installation directory These are MB3_System_Events txt MB3_System_Texts txt MB3 Standard Events txt MB3 Standard Properties txt and MB3 Event Treatments txt 4 1 MB3 System Events txt file This file contains all the texts that will be shown for System Events received from the nodes Below you see an extract from the file 280 PROC I O ST 3A2 board error Net 1A3 Node 2A3 281 PROC I O ST 3A2 board working Net 1A3 Node 2A3 282 REM I O ST Error in bus 111 node 212 Net 1A3 Node 2A3 283 REM I O ST Bus 111 node 212 working Net 1A3 Node 2A3 284 DEV ST Error Net 1A3 Node 2A3 285 DEV ST Device not ready Net 1A3 Node 2A3 You can translate the texts in this file to your choice of language The number that starts each row must be kept intact Also the sections that starts and stops with must be kept intact You must restart the MB3 A amp E OPC Server after you have modified the texts in the file 4 2 MB3_System_Texts txt file This file contains all the texts that will be shown for System Text events received from the nodes Below you see an extract from the file 55 Limit out of rang
4. OPC server connects to the MB3 DA OPC server then the DA OPC server will send the stored events to the A amp E OPC server 9 1 A amp E Statistics in MB3 Power Tool At the MB3 level in the tree browser you can watch statistics about the alarms amp events Event Queues statistics shows the number of events of each type that the MB3 DA OPC server has stored and not sent over to the MB3 A amp E OPC server A amp E OPC Server Stats shows some statistics from the MB3 A amp E OPC server s Num Event Server objects Indicates how many clients are connected to the MB3 A amp E OPC server e Num Subscriptions Indicates how many subscriptions have been created in the MB3 A amp E OPC server e Num Browser Objects Indicates how many browse sessions are underway in the MB3 A amp E OPC server e Alive Signal Toggles between 1 and 0 every third second in the MB3 A amp E OPC server User Manual 27 2012 04 19 User Manual 28 2012 04 19 10 MB3 A amp E OPC Server Window If you are running the MB3 A amp E OPC server as a service then the window is not visible The window contains some information about connected clients events generated and the connection to the MB3 DA OPC server MB3AEServer Simulator E 0 x Fie MB3 Connection Stats Trace View Help Statistic Sample Period ms Num Event Server Objects Num Subscriptions Num Browser Objects Num Events Generated Num Client Notifications Num Event
5. Sample Period ms 1000 Num Event Server Objects 0 Num Subscriptions 0 Num Browser Objects 0 Num Events Generated 354 Num Client Notifications Num Events Last Sample Period MB3 Server ConnectStatus MB3 Server Alive Connect MB3 Server Result Connect MB3 Callback Result Connect MB3 AlarmSink Result MB3 AlarmSink Cookie ooococoron MNT 4 Here you can set if you want to view the toolbar and or status bar 10 6 Help Menu GIMB3AEServer Simulator o File MB3 Connection Stats Trace View Help Help About MB34EServer Statistic Sample Period ms Num Event Server Objects Num Subscriptions Num Browser Objects Num Events Generated Num Client Notifications Num Events Last Sample Period MB3 Server ConnectStatus MB3 Server Alive Connect MB3 Server Result Connect MB3 Callback Result Connect MB3 AlarmSink Result MB3 AlarmSink Cookie G S O O O O 0 00 Menu Option User Manual 32 2012 04 19 Shows the online help Shows the About dialog box About MB3AEServer x ARE MB34E Server Version 7 20 OPC A amp E V1 10 Compliant Copyright C 2006 Novotek AB User Manual 33 2012 04 19 11 Simulation If you run the MB3 A amp E OPC server as a regular server process then you can start it in simulation mode with a command line parameter MB3AESrv exe Simulate The MB3 A amp E OPC server window will show the text Simulator in the title There
6. Text The System Text sent from an ABB Controller will be shown as simple events in the A amp E OPC client The Standard Attributes will contain Source NODE_yyy where yyy is the node number E g NODE 003 for node number 3 Time The timestamp when the server received the System Text This timestamp is created in the MB3 A amp E OPC server Type Simple EventCategory System Severity Always 625 for System Text Message A text based on a text index number sent from the controller The MB3 A amp E OPC server searches for the text in the MB3 System Texts txt file 6 3 Process Events The Process Events sent from the ABB controllers will either be shown as simple or condition events in the A amp E OPC client 6 3 1 Simple Process Events The Standard Attributes for simple events will contain Source The object name of the object that caused the event Time The timestamp when the event occurred in the controller This timestamp is sent from the controller Type Simple EventCategory ObjectEvents Severity The alarm priority 1 7 read from the Event Treat block is converted to an OPC severity 1 1000 Message Is created from the Description of the object sent with the event the combination of event text and property text told by the TEXTCOMB flag in the Event Treat block E g AI Description Alarm Blocked 6 3 2 Condition Process Events The Standard Attributes for conditi
7. also sent every time an OPC client writes lt gt 0 to the START_CM tag The nodes on the network must be set up to listen for time synchronization messages LOC_TIME in the controllers must be set to 3 Listen to Time Set Telegram and High Precision Time Synchronization Telegram 8 2 Another node on the masterbus network is clock master From an OPC DA client it is possible to read the latest received clock sync date and time and from those values then set the clock in the computer There are two possible clock sync telegrams that the MB3 DA OPC server might receive a broadcast clock sync telegram or a clock sync telegram sent from a specific node addressed to the MB3 DA OPC server In the MB3 DA OPC server it is possible to address both of these clock sync date and times as items Broadcast clock sync telegram Clock Master is set to CLK_SEND 3 ItemID st Type Description S O CS_DATE ChannelName Long Integer Latest Clock Sync Date received from a broadcast clock sync telegram The format is in number of days since 1 January 1980 1 January 1980 is day 1 CS_TIME ChannelName Long Integer Latest Clock Sync Time received from a broadcast clock sync telegram The format is in number of 0 1 milliseconds since midnight Clock sync from a node Clock Master is set to CLK_SEND 2 ItemID sd Type Description S O CS_DATE DeviceName Long Integer Latest Clock Sync Date received from this node s clock sync teleg
8. ea ae ded ae eden ee 4 VN I AA E A H ON CAERE EE EEE EEE EE EAEE unseeded endo EEEE ideas 4 INSTALLATION iii essensen odds sneen is essens ES ESEO EES S aE REOSE ESS 5 OPC PROGRAM ID TTT 5 RUNNING ASA SERVICE TTT 5 A amp E OPC AREA AND SOURCE CONFIGURATION u ccsssscscsssccesssccccsssccccsssscccssssccscsscsecssssccccssnee 8 EXAMPLE OF A AREA AND SOURCE FIE ieget n e a e ia ae E ei Si ieke 10 TEXT FILES visscssssiccecccicsvesccsadsccssscbietscvscdesunbencesstedivcsssesscoussedescedcstessosedudesssoveesducedesssbutdeesebecseveustesesesiiesessse 11 MB3_SYSTEM_EVENTS TXT FILE sese eee eee 11 MB3 SYSTEM TEXTS TXT FILE sss sese eee 11 MB3 STANDARD EVENTS TXT FILE ss sese ee eee 11 MB3 STANDARD PROPERTIES TXT FILE sese eee eee 12 MB3_EVENT_TREATMENTS TXT FILE sss sese ee eee 12 SUBSCRIPTION FILTERING IN THE MB3 A amp E OPC SERVER Mu s lt ss ss ss ss sss ss sss ss sss sss essea sss 15 SIMPLE EVENTS TTT 15 CONDON EVENTS T 15 EVENT CATEGORIES TTT 15 VENDOR SPECIFIC ATTRIBUTES visioenen inne esre ee ienei ei eia aeneae eiieeii iape 20 AREAS AND SOURGES orreee creet anae drer er aea eaae e e E a aea ae a eenen N ea e i Eei EEs 21 MB3 ALARM amp EVENTS IN THE A amp E OPC CLIENT sss ss sss ss sese soso osson 23 SYSTEM Sa To E EEE EEEE EEES E EEEE EEEIEE EEEE EE 23 SYSTEM TEX VTT 23 PROCESS EVENTS TTT 23 ACKNOWLEDGING PROCESS EVENT ccsssscscssssscssssscccssssccccssscccsssscccessseccccsssesesssecccessseccscssceseess 25 IN T
9. is no connection to the MB3 DA OPC server when it is started in simulation mode MB34EServer Simulator j lol x File MB3 Connection Stats Trace View Help Statistic Sample Period ms Num Event Server Objects Num Subscriptions Num Browser Objects Num Events Generated Num Client Notifications Num Events Last Sample Period MB3 Server ConnectStatus MB3 Server Alive Connect MB3 Server Result Connect MB3 Callback Result Connect MB3 AlarmSink Result MB3 AlarmSink Cookie The simulated events are generated from a file named MB3AESrv sim This is a text file where each row represents a new event When all events in the file has been read then it starts over from the beginning again but with a new timestamp There are three valid event types in this file They are System Text System Event and Process Event There are certain rules for the file These are Comment starts with Every field on a row must be separated with Each row starts with Simulation interval in ms gt time to generate the next event from the file The next field is Type of event 1 System Text 2 System Event 3 Process Event System Text fields Net Node MMI Text No System Event fields Time Quality Timestamp Net Node List Reason Source OutDesc Class Process Section List Store Priority AndRef TextStat LF TextNo RealPar IntPar1 IntPar2 HexPar AsciiParl AsciiPar2 AsciiPar3 AsciiPar4 AsciiPar5 DigPar TxtPtr1 Txt
10. C Server to run as a service you must register it as a service During installation the Setup wizard automatically registers the server as a regular server process To register it to run as a service you must run the server on the command line specifying that you wish to register it as a service Once the server is running as a service you may need to re register it in certain situations such as when you need to change the logon account Before you register the Server to run as a service follow these steps to ensure that it is not currently running s Ifthe server is currently running as a regular server you must stop the process by shutting down all A amp E OPC clients to the server s Ifthe driver is currently running as a service you must stop the process by shutting down all clients to the server and you must also perform these tasks on your operating system Windows XP and Windows 2000 from Control Panel select Administrative Tools and then select Services A list of all services configured on the machine displays Locate MB3 AE Server If the status is Started right click and Stop the server Windows NT from Control Panel select the Services icon A list of all services configured on the machine displays Locate MB3 AE Server If the status is Started click the Stop button Once you stop the server from running select the Process tab from the Task Manager and verify that the MB3AESrv exe process is no longer listed Use
11. EXTCOMB parameter in the Event Treat file in section 4 5 1 Event Treat Block Parameters used by the MB3 A amp E OPC Server for usage of user or standard property texts Below you see an extract from the file 2 Value 3 Sig Err 4 Lim H2 5 Lim H1 6 Lim L1 7 Lim L2 8 Value 9 Printout 10 Alarm 11 Update 12 Disturb 13 Opening 14 Closing 15 NotClose 16 Not Open You can translate the texts in this file to your choice of language The number that starts each row must be kept intact You must restart the MB3 A amp E OPC Server after you have modified the texts in the file 4 5 MB3_Event_Treatments txt file When the MB3 A amp E server is installed a default exported Operator Station Event Treat BAX file will be installed This file is named MB3_Event_Treatments txt This file contain all the ABB event treat blocks that will control how the Process Events sent from objects in ABB controllers will be displayed in the MB3 A amp E OPC server If you have an Operator Station that already contains the Event Treat configuration you want to use then you can export its Event Treat database to a BAX file After that you can copy the content from that BAX file and replace all content in the default MB3_Event_Treatments txt file You must restart the MB3 A amp E OPC Server after you have modified the file See the ABB documentation AdvaCommand Localization User s Guide 3BSE 009 666RO001 Rev A chapter 3 2 8 Alarm and Event Handling of
12. HE MB3 DA OPC SERVER 0 0 sscssssssssssssssssssssnsnsnsecesecusnsusecusnsususesssssnsusssusesssnsssssssssssssssssssssssssssssssees 25 IN THE MB3 A amp E OPC SERVER sese s eee eee 25 TIME SYNCHRONIZATION sandede sekserne 26 MBS3 OPC SERVER IS CLOCK MASTER e E eee Eaa 26 ANOTHER NODE ON THE MASTERBUS NETWORK IS CLOCK MASTER sese 26 CONFIGURATION IN MB3 POWER TOOL sss ss ss sss sss ss sss sees essen saos sees essens 27 A amp E STATISTICS IN MB3 POWER TOOL KM sss eee 2T MB3 A amp E OPC SERVER WINDOW eesseoesssecssosecssoceesseceecsecssccoeessoceesseoeesoeesscoeessoceesseceesseessooeessoceesse 29 PUB MENU ESEE RE E EES EEA E E error eee sanse reb 30 MB3 CONNECTION MEN Ursin eee renere o era EOE a ere e aT EOE ETES Es 30 STATS MENU enes eee eee ener entreen eee eres eee reen ener EEE ESE EEE eee reen rener reen er nere een eee SESE EESE S Eses Eseese ene 31 A ESSA A i INI EE A AE AE er E eN neden EE anes 31 Kk 1260 1 TANA OAEIAE EE A SA E ES E E E E E EVE E E EE 32 Ja KAE 501 IN EIEEE E AEE A N E E E E E AEE E E E A 32 SIMULA TION iissscscscocssoonssssesonsosssscassstuocessesscssssctudsodesvetsoscssesseestesssiecdesesdessesvssessesessossveenssodusoasosseseosestess 34 User Manual 3 2012 04 19 1 About the MB3 A amp E OPC Server The MB3 DA OPC server receives System Events System Text and Process Events from the ABB controllers These are then sent from the MB3 DA OPC server to the MB3 A amp E OPC server that makes the al
13. NOVOTEK lt USER MANUAL MB3 AXE OPC Server v7 20 3 A amp E OPC Server for ABB MasterBus 300 By Novotek Document version 7 20 3 This version printed Thursday 19 April 2012 Copyright 2007 Novotek Sverige AB MB3 A amp E OPC Server A amp E OPC Server for ABB MasterBus 300 Program version 7 20 3 Copyright 2007Novotek Sverige AB e No part of the contents of this document may be reproduced transmitted or translated to other languages without permission from Novotek Sverige AB e The information is subject to change without prior notice s All company names and other names data and addresses that are shown in screen dumps and other examples are fictive and have been worked out only to enhance understanding Novotek Sverige AB takes no responsibility for the function of the programs if e Non recommended hardware and software are used e Any of the required programs has been shut off by any other that staff from Novotek Sverige AB e Virus has destroyed any files Version information Revision Date 7 20 1 2006 07 04 7 20 2 2006 12 05 7 20 3 2007 10 24 Description Created New Version New Version User Manual 2012 04 19 CONTENTS 1 1 1 1 2 2 2 1 2 2 3 3 1 10 1 10 2 10 3 10 4 10 5 10 6 11 ABOUT THE MB3 A amp E OPC SERVER ssscsecssssucssesseeccseseckosessceusesosesscussccessusecesvetessssvdasesssusesssuundesesesvedeseses 4 TRA EA E RA SA EAN E SAE AEE EAE nn dee ee Sa ed eee aad
14. Ptr2 TxtPtr3 TxtPtr4 TxtPtr5 TxtPtr6 TxtPtr7 TxtPtr8 TxtPtr9 TxtPtr10 e Process Event Fields Time Quality Timestamp Net Node ObjectName ObjectDesc Value Unit Source TypOfReq Reason StatChkSrc Property PropTxt EvTxt AlrmBlk PrintBlk RepFailBlk RefType LF LR TreatRef GroupRef Process Section Class Net Masterbus 300 net number who senttheevent i O MMI The MMI number the text is intended for o O The system text no Valid numbers are those listed in MB3_System_Texts txt System Event Fields Time Quality Quality of the timestamp 0 Good User Manual 34 2012 04 19 1 No time 2 Uncertain Timestamp Timestamp in format YYYY MM DD HH MM SS ccc where ccc is milliseconds Masterbus 300 net number who sent the event Masterbus 300 node number who sent the event Always 0 Not used Reason Reason of the event 0 Normal 1 Blocked 2 Deblocked 3 Alarm 4 Normal 5 SysText 6 ValueChg 7 AckList 8 ClearPersist 9 On 10 Off 11 StatChkOn 12 UnackOn 13 UnackOff Always 3 alarm on for system events Always 0 Not used Always 1 Not used Class Class number 0 99 for the alarm Soo U ProcessSection Process Section 0 16 of the alarm ee o O Always 512 Not used Always 0 Not used TextNo The system event text no Valid numbers are those listed in MB3_System_Events txt Value of the Real parameter If no real parameter then add a space in th
15. SysText 6 ValueChg 7 AckList 8 ClearPersist 9 On 10 Off 11 StatChkOn 12 UnackOn 13 UnackOff StatChkSre Always 0 Not used Property The property of the object that caused the process event A value between 2 278 or 65502 65535 LF Logical record number for the object that caused the process event The number to the Event Treat block to use for this process event Valid block numbers are those listed in MB3_Event_Treatments txt User Manual 36 2012 04 19 When the MB3 A amp E OPC server is installed a default simulation file MB3AESrv sim will be installed This file contain Process Events for the following object names por OBYECT Of po CDOT DOOOBJECT T MMCX_ MMCX__ MMCXOBJCT 6 The file also contains 19 System Text events and 7 System Event events User Manual 2 37 2012 04 19
16. VECON PosErrO VALVECON_PosO VALVECON_IntPos 5 3 8 MOTCON_Events Conditions MOTCON_BimetalR MOTCON SafeMon MOTCON_MonLow 5 3 9 MMCX Events Conditions MMCX_IND1_01 IND status bit 1 Timeout step for GROUP IND1 status bit 8 MMCX_IND1_10 INDI status bit 10 MMCX_IND2_00 ND status bit 0 MMCX IND2 01 ND2 status bit 1 MMCX IND2 02 IND2 status bit 2 MMCX IND2 03 IND2 status bit 3 MMCX IND2 04 IND2 status bit 4 MMCX IND2 05 IND2 status bit 5 IND2 status bit 6 MMCX IND2 07 IND status bit 7 IND2 status bit 9 T T T T User Manual B e 2012 04 19 MMCX_IND2_14 IND2 status bit 14 MMCX IND2 15 IND2 status bit 15 5 3 10 GENUSD_Events Conditions GENUSD_AL_IND1 GENUSD_AL_IND6 Alarm ALF6 5 3 11 GENCON_Events Conditions 5 3 12 GENBIN_Events Conditions 5 3 13 SEQ_Events Conditions 5 3 14 GRPALARM_Events Conditions GRPALARM_Disturbance Abnormal position 5 3 15 DRICONS_Events Conditions DRICONS_IND1_00 IND status bit 0 DRICONS_IND1_01 INDI status bit 1 DRICONS_IND1_02 ND status bit 2 DRICONS_IND1_04 NDI status bit 4 DRICONS_IND1_05 NDI status bit 5 DRICONS_IND1_06 T DRICONS IND1 03 INDI status bit 3 T T IND status bit 6 DRICONS IND1 07 IND status bit 7 DRICONS_IND1_08 IND status bit 8 User Manual 18 2012 04 19 DRICONS_IND1_09 IND status bit 9 DRICONS_IND1_10 INDI
17. a 2012 04 19 3 A amp E OPC Area and Source Configuration At startup of the MB3 A amp E OPC server it will try to read a configuration file named MB3AESrv csv that should exist in the same directory as the exe file This file shall contain all ABB objects and ABB nodes that can generate System Events System Texts and Process Events This file is used to build up the A amp E Area and Source information in the MB3 A amp E OPC server A amp E clients can use the Area and Source information to filter from which sources and or areas it want to receive alarms and events Note If the MB3 A amp E OPC server receives an alarm or event from an object or node that not exists in its area and source configuration then it will be added to it automatically When the MB3 A amp E OPC server is shut down then it saves its current Area and Source configuration to the file The file is a text file with one line per object and node The line format for objects is PRO_SECxx ObjectType ObjectName my Each field is separated by where PRO_SECxx The ABB process section this object belongs to where xx is a number between 00 16 The process section for the object is configured in the ABB controller s database You can see it in the BAX files For example if the object belongs to process section 3 then this text should look like this PRO SEC03 ObjectType The type of the object Supported types are See Note below See Note below See Note below
18. arms reachable for A amp E OPC clients 1 1 References e MB3 Server User Manual e ABB GCOM Multidrop User s Guide 3BSE 000 165R0001 e ABB MasterNet User s Guide 3BSE 003 839R301 e AdvaCommand Basic Functions User s Guide 3BSE 001 976R0401 Rev A e AdvaCommand Localization User s Guide 3BSE 009 666RO0001 Rev A e OPC Foundation Alarms amp Events Custom Interface Standard Version 1 10 1 2 Abbreviations OPC A amp E OPC Alarms amp Events MB300 MasterBus 300 User Manual 4 2012 04 19 2 Installation The MB3 A amp E OPC Server is automatically installed together with the MB3 DA OPC installation The MB3 A amp E OPC server will also be registered The files installed that is used by the MB3 A amp E OPC Server are The MB3 A amp E OPC server will be uninstalled with the MB3 DA OPC Server uninstallation MB 3 Standard Events txt Alarm amp Event Texts 2 1 OPC Program ID The program ID of the MB3 A amp E OPC Server is Novotek MB3AEOPCSvr Browse for this program id or enter it manually when you want to connect your A amp E OPC client to the MB3 A amp E OPC server 2 2 Running as a Service When the MB3 A amp E OPC server is installed it is registered as a regular server process The MB3 A amp E OPC server can also run as a Windows Service Running your A amp E OPC server as a Windows service lets users log on and off the operating system without shutting down the A amp E OPC server To set up the MB3 A amp E OP
19. blocked in the Event Treat file are treated as condition events The priority 1 7 is taken from the Event Treat file and converted to the A amp E OPC severity 1 1000 as shown above 5 3 Event Categories The MB3 A amp E OPC server contains the following event categories ObjectEvents Simple The object Process Events not received as alarm on or alarm off events is treated as simple events Alarm on or alarm off events received but blocked with AL_TOBLK and AL_FRBLK in the Event Treat file are also treated as simple events oe 4 Simple All System Events and System Text sent from the ABB controllers are treated as simple events oe SERVER_ERROR Internalerros 0 User Manual 2 5 2012 04 19 5 3 1 Al Events Conditions AI_LevelHIHI Upper limit H2 AL LevelHI Upper limit H1 AI_LevelLO Lower limit L1 AI_LevelLOLO Lower limit L2 AL SigError 5 3 2 DI Events Conditions DI Value Abnormal position DI_SigError 5 3 3 PIDCON_Events Conditions PIDCON_DeviationLO 5 3 4 PIDCONA_Events Conditions PIDCONA_ATFai PIDCONA_AdFail 5 3 5 RATIOSTN_Events Conditions 5 3 6 MANSTN Events Conditions MANSTN LevelHIHI Upper limit H2 for measured value MANSTN LevelHI Upper limit H1 for measured value MANSTN_LevelLO Lower limit L1 for measured value MANSTN_LevelLOLO Lower limit L2 for measured value MANSTN_SigError Al error User Manual 16 2012 04 19 5 3 7 VALVECON Events Conditions VAL
20. e Input ignored 56 Value out of range Input ignored 57 Limit not used Input ignored 58 Manual orders blocked Command ignored 59 Blocking of Integration not allowed Command ignored 60 Blocking of Derivation not allowed Command ignored 61 Manual mode selection not allowed 62 Auto mode selection not allowed You can translate the texts in this file to your choice of language The number that starts each row must be kept intact You must restart the MB3 A amp E OPC Server after you have modified the texts in the file 4 3 MB3_Standard_Events txt file This file contains all the standard event texts that will be shown for Process Events See description of the TEXTCOMB parameter in the Event Treat file in section 4 5 1 Event Treat Block Parameters used by the MB3 A amp E OPC Server for usage of user or standard event texts Below you see the content of the file 0 Normal 1 Blocked 2 Deblocked 3 Alarm 4 Normal 5 SysText 6 ValueChg 7 AckList 8 ClearPersist 9 On 10 Off 11 StatChkOn 12 UnackOn 13 UnackOff User Manual 11 2012 04 19 You can translate the texts in this file to your choice of language The number that starts each row must be kept intact You must restart the MB3 A amp E OPC Server after you have modified the texts in the file 4 4 MB3_Standard_Properties txt file This file contains all the standard property texts that will be shown for Process Events See description of the T
21. e field IntPar1 Value of the Integer parameter 1 If no Integer parameter 1 then add a space in the field Value of the Integer parameter 2 If no Integer parameter 2 then add a space in the field Value of the Hex parameter If no Hex parameter then add a space in the field AsciiParl Value of the Ascii parameter 1 If no Ascii parameter 5 then add a space in the ST T AsciiPar2 Value of the Ascii parameter 2 If no Ascii parameter 5 then add a space in the ST T AsciiPar3 Value of the Ascii parameter 3 If no Ascii parameter 5 then add a space in the Pe ee A AsciiPar4 Value of the Ascii parameter 4 If no Ascii parameter 5 then add a space in the pe eee AsciiParS Value of the Ascii parameter 5 If no Ascii parameter 5 then add a space in the Pee ee field Enter a value 0 99 Not used Enter a value 0 99 Not used User Manual 35 2012 04 19 Enter a value 0 99 Not used Process Event Fields Time Quality Quality of the timestamp 0 Good 1 No time 2 Uncertain Timestamp Timestamp in format YYYY MM DD HH MM SS ccc where ccc is milliseconds Masterbus 300 net number who sent the event Masterbus 300 node number who sent the event ObjectName The name of the object that caused the process event Max 20 characters ObjectDesc The description of the object that caused the process event Max 28 characters Reason Reason of the event 0 Normal 1 Blocked 2 Deblocked 3 Alarm 4 Normal 5
22. he table below This text combination together with the object description is used as the alarm message text for object Process Events Text Combination Property Text Event Text Code O Standard Standard i OU oo serdefined 2 0 Standard Value Unit 30d Standard Userdefined 4 CCC Userdefined Standard 5 00 Userdefined Uar dened User Manual _ 13 2012 04 19 Standard Step no User defined Step no User defined Standard Step no User defined User Defined Step no User Manual 14 2012 04 19 5 Subscription Filtering in the MB3 A amp E OPC Server 5 1 Simple Events All System Events and System Text sent from the ABB controllers are treated as simple events in the MB3 A amp E OPC server The priority 1 7 received with the System Events is converted to A amp E OPC severity 1 1000 as shown below 1 875 2 750 3 625 4 500 5 375 6 250 7 125 System Text simple events always has A amp E OPC severity 625 The object Process Events not received as alarm on or alarm off events are treated as simple events Alarm on or alarm off events received but blocked with AL_TOBLK and AL_FRBLK in the Event Treat file are also treated as simple events The priority 1 7 is read from the Event Treat file and converted to the A amp E OPC severity 1 1000 as shown above 5 2 Condition Events Object Process Events received as alarm on or alarm off events and not
23. how to export your Event Treat database to file If you don t have any Operator Station Event Treat configuration you want to use then you can modify the default file with a text editor The Event Treat database functionality is described in the ABB documentation AdvaCommand Basic Functions User s Guide 3BSE 001 976R0401 Rev A in chapter 3 3 12 Alarm and Event Alarm Handling The text handling in the Event Treat database is described in the ABB documentation AdvaCommand Basic Functions User s Guide 3BSE 001 976R0401 Rev A in chapter Appendix A Event Texts The event texts for each object type are also described in the objects Functional Units documentation for example Functional Unit Part 6 MOTCON VALVECON 3BSE 003 854R0001 Rev A for MOTCON and VALVECON event texts 4 5 1 Event Treat Block Parameters used by the MB3 A amp E OPC Server The MB3 A amp E OPC server uses these parameters in an Event Treat block AUDIBLE The value of this flag is saved as a user attribute for the object Process Event in the MB3 A amp E OPC server User Manual 12 2012 04 19 AL PRIO AL TOBLK AL FRBLK TEXT TOBLK TEXT FRBLK TEXTCOMB ABB Description The connection between the Priority in the configured data of External Alarm is the property AUDIBLE in the Event Treat file Alarm priority 1 7 This priority is converted to OPC A amp E severity 1 1000 according to the values below 1 875 2 750 3 625 4 500
24. ics Sample Period milliseconds 1000 Cancel 10 4 Trace Menu MB3AEServer Simulator A oj x Fie MB3 Connection Stats Trace View Help v None Connect Statistic Server Sample Period ms Subscription Num Event Server Objects Event Num Subscriptions Al Num Browser Objects Num Events Generated Num Client Notifications Num Events Last Sample Perioc Enable COM Call Tracing MB3 Server ConnectStatus MB3 Server Alive Connect MB3 Server Result Connect MB3 Callback Result Connect MB3 AlarmSink Result MB3 AlarmSink Cookie Set Trace File SSO TED Menu Option No trace messages are output User Manual 31 2012 04 19 Connect Log trace messages associated with client connectivity and server activation Server Log trace messages from operations invoked on OPCEventServer object For example enabling and disabling conditions Subscription Log trace messages associated with subscription transactions For example client event notifications subscription state changes etc Event Log trace messages associated with the generation of events This is irrespective of whether or not any clients have subscribed All Log all message types Set Trace File Set filename where to store the trace Enable COM Call Tracing Is not supported in this version 10 5 View Menu ESMB3AEServer Simulator Lo Fie MB3 Connection Stats Trace View Help v Toolbar v Status Bar Statistic Yalu
25. ition into the condition which is associated with this event notification e Actor ID The identifier of the OPC client which acknowledged the condition User Manual 24 2012 04 19 7 Acknowledging Process Events Process Events Process Events System Events System Events System Texts System Texts Unacknowledge check in ABB EVENT TREAT MB3 DA MB3 A amp E Controller OPC Server OPC Server PROPERTY amp SYSTEM TEXTS 7 1 Inthe MB3 DA OPC server When the MB3 DA OPC server receives a Process Event from an ABB controller then it checks in the Event Treat file for the event if it shall send an Unacknowledge back to the ABB controller If it is an Alarm On event and the AL TOBLK flag in the Event treat block is set to NO then it will send an Unacknowledge If the AL_TOBLK flag is set to YES then it will not send a Unacknoweldge If you want to prevent the MB3 DA OPC server to send Unacknowledge to the ABB controllers then you have to set all the AL_TOBLK and AL_FRBLK parameters in the Event Treat file to YES 7 2 Inthe MB3 A amp E OPC server When the MB3 A amp E OPC server receives a Process Event then it checks in the Event Treat file block for the event if it shall set the AckRequired flag for the event to TRUE or FALSE If it is an Alarm On event and the AL_TOBLK flag in the Event treat block is set to NO then it will set the AckRequired flag to TRUE A condition event in the MB3 A amp E OPC server that require
26. on events will contain Source The object name of the object that caused the event Time The timestamp when the event occurred in the controller This timestamp is sent from the controller Type Condition EventCategory TYPE Events where type is the object type E g AI Events User Manual 23 2012 04 19 e Severity The alarm priority 1 7 read from the Event Treat block is converted to an OPC severity 1 1000 e Message Is created from the Description of the object sent with the event the combination of event text and property text told by the TEXTCOMB flag in the Event Treat block E g AI Description Lim H1 gt 75 e Condition Name Name of associated condition See tables in sections 5 3 1 5 3 16 for valid conditions for each object type e SubCondition Name The name of the currently active sub condition The name of the sub condition is the same as the condition e Change Mask Indicates which properties of the condition have changed to cause the server to send the event notification e New State Indicates the new values for the Enabled Active and Acked properties of the condition e Quality Always Good in MB3 A amp E OPC server e AckRequired Indicates whether or not an acknowledgement is required This is controlled with AL_TOBLK and ALFRBLEK in the Event Treat file when the server receives the event from the controller e ActiveTime The time of the trans
27. onnect Sends out a request to the connected clients that they should disconnect Save Source Cache To File Saves the actual Source Cache to the file MBAESrv csv This file is also updated when the server is shutdown Shuts down the MB3 A amp E Server if no clients are connected 10 2 MB3 Connection Menu io x File MB3 Connection Stats Trace View Help Connect To Server Disconnect Server Stat Sample Period ms 1000 Num Event Server Objects 0 Num Subscriptions 0 Num Browser Objects 0 Num Events Generated 201 Num Client Notifications 0 Num Events Last Sample Period MB3 Server ConnectStatus MB3 Server Alive Connect MB3 Server Result Connect MB3 Callback Result Connect MB3 AlarmSink Result MB3 AlarmSink Cookie 0 0 00 0 o m 2 Trigs a manual connection to the MB3 DA OPC server Trigs a manual disconnection from the MB3 DA OPC server User Manual 30 2012 04 19 10 3 Stats Menu MB3AEServer Simulator Fie MB3 Connection Stats Trace View Help 2 Set Sample Period Sample Period ms 1000 Num Event Server Objects 0 Num Subscriptions 0 Mum Browser Objects 0 Num Events Generated 229 Num Client Notifications 0 Num Events Last Sample Period O MB3 Server ConnectStatus 1 MB3 Server Alive 0 Connect MB3 Server Result 0 Connect MB3 Callback Result 0 Connect MB3 AlarmSink Result 0 MB3 AlarmSink Cookie 0 m 2 Set Statistics Sample Period l a Enter Statist
28. r Manual z5 2012 04 19 2 2 1 Registering the MB3 A amp E OPC Server as a Service To register the MB3 A amp E OPC Server as a service 1 Select Run from the Windows Start menu 2 Enter the following text and click OK Path MB3AESrv exe RegService The registration process now allows the user to specify a logon account This provides flexibility with the user s choice of security settings The Logon Account for Running As A Service dialog box appears after the user enters the command and clicks OK Logon Account for Running As A Service xl f Use FIXIOUser Account C Use System Account C Use This Account User Name This dialog box allows the user to select one of these accounts when registering the MB3 A amp E OPC server to run as a service FixIOUser Account uses the FixIOUser account to log on the MB3 A amp E OPC Server This conventional account uses a hard coded password and has the necessary privileges to log on as a service You should not modify this account if one or more 7 x drivers use this as the logon account when running the Server as a service If you do modify this account those drivers will not be able to start as a Windows service The FixIOUser account may not be created if it does not conform to your local IT department s security policies If this account does not exist you must select one of the other two options NOTE If you previously ran the MB3 A amp E OPC Server as a service withou
29. ram The format is in number of days since 1 January 1980 1 January 1980 is day 1 CS_TIME DeviceName Long Integer Latest Clock Sync Time received from this node s clock sync telegram The format is in number of 0 1 milliseconds since midnight There is installed an OPC DA client program for clock synchronization together with the MB3 OPC server The program is named MB3ClockSync exe and it has an own manual MB3 Clock Sync User Manual for further information User Manual 26 2012 04 19 9 Configuration in MB3 Power Tool In the MB3 Power Tool it is possible to set up how many events of each type the MB3 DA OPC server can store when no MB3 A amp E OPC server is connected to it x Display Setup Default Path Advanced opc Memory Signal Conditioning Maximum Size Path to signal conditioning dll Growth Increment 4095 D DYNAMICS MB3Sig dl Overrun Buffer 4095 Error Resource Dil ath to Error Resource dll DYNAMICS SMB 2E rn d Max Process Events 200 S Max System Events 1100 imulation Mode Of On Max System Texts 50 aes rent Of On Startup Alarm amp Event Queues Auto Start Of On The default values are e Process Events 200 e System Events 100 e System Texts 50 If you make changes to the values then you must restart the MB3 DA OPC server before it will take effect When a MB3 A amp E
30. rmal 1 Blocked 2 Deblocked 3 Alarm 4 Normal 5 SysText 6 ValueChg 7 AckList User Manual 20 2012 04 19 8 ClearPersist 9 On 10 Off 11 StatChkOn 12 UnackOn 13 UnackOff Property VT_I4 Which property in the object that caused the event A value between 2 278 or 65502 65535 RefType VT I4 The reference type of the object that caused the event LF T VT 14 Logical File number of the object that caused the event LR T VT 14 Logical Record number of the object that caused the event 5 5 Areas and Sources In the MB3 A amp E OPC server configuration there exist areas and sources 5 5 1 Areas For System Events and System Texts the area is hard coded to NODES For Process Events the area is built up from the process section the object belongs to and what type the object is of See example below xi Area NODES Server Namespace A PRO_SECOO A PRO SECO1 A Al A DI A GENUSD A GRPALARM PRO SECO2 RO SECO9 D E HA FA v In this example we have objects from four different process sections 0 1 2 and 9 We can also see that in process section 1 we have objects of type AI DI GENUSD and GRPALARM and in process section 9 we have objects of type AI and DI The NODES area contains all node sources that can send System Events and System Texts 5 5 2 Sources For System Events and System Texts the sources are the node numbers that can send the even
31. s Last Sample Period MB3 Server ConnectStatus MB3 Server Alive Connect MB3 Server Result Connect MB3 Callback Result Connect MB3 AlarmSink Result MB3 AlarmSink Cookie EJ oooccoro ounce Num Client Notifications Number of event notifications sent to the server s clients Note that a ae notification can contain data for multiple events MB3 Server ConnectStatus Connect status with the MB3 DA OPC server 1 Connected 0 MB3 Server Alive A toggle flag indicating a connection between the MB3 DA OPC server and BS Soner Ae hens ARE OPC server To tegeled every seeond o a Connect MB3 Callback Result HRESULT of last connection to the MB3 DA OPC server s callback connect interface 0 OK Connect MB3 AlarmSink Result HRESULT of last connection to the MB3 DA OPC servers AlarmSink 0 OK MB3 AlarmSink Cookie The returned Cookie to the MB3 DA OPC servers AlarmSink User Manual 29 2012 04 19 10 1 File Menu IMUSAEServer Simulator TT File MB3 Connection Stats Trace View Help Request Clients to Disconnect Save Source Cache To File Exit Num Event Server Objects Num Subscriptions Num Browser Objects Num Events Generated Num Client Notifications Num Events Last Sample Period MB3 Server ConnectStatus MB3 Server Alive Connect MB3 Server Result Connect MB3 Callback Result Connect MB3 AlarmSink Result MB3 AlarmSink Cookie on oO oooccor 0 0 0 0 0 Menu Option Request Clients to Disc
32. s acknowledge can be acknowledged in two ways 1 The condition event is acknowledged from the connected A amp E OPC client 2 The MB3 A amp E OPC server receives an acknowledge process event from the object that has caused the condition event This event is sent from the ABB controller When an operator acknowledges the alarm from the A amp E OPC client then it trigs the MB3 DA OPC server to send an Acknowledge order to the ABB controller The ABB controller will then send a process event to all event subscribers that the event has been acknowledged In this way the acknowledgement is synchronized in all MB3 A amp E OPC servers connected to the ABB controllers User Manual 25 2012 04 19 8 Time Synchronization There are two options 1 The MB3 OPC server is the clock master and sends broadcast clock synch telegrams every 10 minute 2 Another node on the network is clock master and the MB3 OPC server receives the clock synch telegram and sets the clock in the PC from it 8 1 MB3 OPC server is clock master There is a channel item that can be used to control the MB3 OPC server as a clock synch master on the Masterbus network ItemID sd Type Description S O START_CM ChannelName Long Whenever this tag is set lt gt 0 the MB3 OPC server sends clock Integer synch broadcast message every 10 minutes The state of the tag is saved in the registry at HKLM Software Novotek Drivers MB3 SendCM A clock synch broadcast is
33. status bit 10 DRICONS_IND1_11 IND status bit 11 DRICONS_IND1_12 NDI status bit 12 I DRICONS_IND1_13 INDI status bit 13 DRICONS_IND1_14 INDI status bit 14 T DRICONS_IND1_15 ND status bit 15 DRICONS_IND2_00 IND2 status bit 0 DRICONS IND2 01 IND2 status bit 1 DRICONS IND2 02 IND2 status bit 2 DRICONS IND2 03 IND2 status bit 3 DRICONS IND2 04 IND2 status bit 4 DRICONS IND2 05 IND2 status bit 5 DRICONS IND2 06 IND2 status bit 6 DRICONS IND2 07 IND2 status bit 7 DRICONS IND2 12 IND2 status bit 12 DRICONS_IND2_13 IND2 status bit 13 DRICONS_IND2_14 IND2 status bit 14 DRICONS_IND2_15 IND2 status bit 15 5 3 16 DRICONE_Events Conditions DRICONE_IND1_03 IND status bit 3 DRICONE IND1 04 INDI status bit 4 DRICONE_IND1_05 INDI status bit 5 DRICONE INDI 06 INDI status bit 6 DRICONE INDI 07 INDI status bit 7 DRICONE_IND1_08 IND status bit 8 DRICONE_IND1_09_ INDI status bit 9 DRICONE_IND1_10 INDI status bit 10 DRICONE_IND1_11 INDI status bit 11 DRICONE INDI 12 INDI status bit 12 DRICONE_IND1_13 INDI status bit 13 DRICONE_IND1_14 INDI status bit 14 DRICONE_IND1_15 INDI status bit 15 DRICONE IND2 00 IND2 status bit 0 DRICONE_IND2_01 IND2 status bit 1 DRICONE_IND2_06 IND2 status bit 6 DRICONE IND2 11 IND2 status bit 11 DRICONE IND2 12 IND2 status bit 12 DRICONE_IND2_13 IND2 status bi
34. t 13 User Manual 19 2012 04 19 DRICONE IND2 14 IND2 status bit 14 DRICONE IND2 15 IND2 status bit 15 5 4 Vendor Specific Attributes The MB3 A amp E OPC server can store some vendor specific attributes with each event generated An A amp E OPC client can view these attributes if the client has support of these attributes System Events and System Text events has one collection of attributes and Process Events has one collection of attributes 5 4 1 System Event and System Text Attributes TextNo VT 14 ProcSec VT_I4 Process section of the event System Event only ee ee MMI number the text is intended for System Text only VT 14 Class of the event System Event only TimeQuality VT I4 Quality of the time stamp Good 0 No time 1 Uncertain 2 System Event only 5 4 2 Process Event Attributes TimeQuality VT_I4 Quality of the time stamp Good 0 No time 1 Uncertain 2 System Event only Audible VT I4 The value of the flag AUDIBLE read from the Event Treat file for the event VT BSTR The actual value of the parameter in the object that caused the event VT 14 The index number of the Event Treat reference block that shall be used PropTxt VT 14 The index number of which property text in the Event Treat block that shall be used VT I4 The index number of which event text in the Event Treat block that shall be used Reason VT I4 Reason of the event A value between 0 13 0 No
35. t incident you should continue to run it using the FixIOUser account System Account uses the local system account to log on the MB3 A amp E OPC Server This pre defined account is useful when your local IT department s security policy requires password expiration This Account uses an account specified by the user to log on the MB3 A amp E OPC Server This account is useful if you need to specify a domain account The account used here must be an existing account with both Administrator and Logon as a Service privileges to run the server as a service To determine if the account has Administrator privileges refer to the manual provided with your operating system For example to determine Administrator privileges in Windows 2000 select Administrative Tools from Control panel and then select Users and Passwords Use the Local Security Policy Setting tool to grant the account Logon as a Service privilege You can reset the server to be a regular server process again by re registering it as Path MB3AESrv exe RegServer NOTE Before you register the Server to run as a regular server you must ensure that it is not currently running User Manual 6 2012 04 19 When registering the server this way it will run perform the necessary registration work and then exit You can then start the server by using more conventional methods such as starting any A amp E OPC client program capable of communicating with the server User Manual F
36. ts The sources will get the name NODE_yyy where yyy is the node number For Process Events the source is the object name that can send the events See example below User Manual z l 2012 04 19 Source Server E A NODES eS NODE 002 S NODE 005 S NODE 006 S NODE 019 A PRO_SECOO A PRO_SECO1 A PRO_SECO2 A PRO_SECOS E A D H Al G9A37 AU G9A72 VG AS S Cancel The NODES area contains four nodes node number 2 5 6 and 9 that can send System Events and System Texts The PROC_SEC09 AI area contains at least two AI object sources with name G9A37 AU and G9A72 VG AS User Manual 22 2012 04 19 6 MB3 Alarm amp Events in the A amp E OPC Client 6 1 System Events The System Events sent from an ABB controller will be shown as simple events in the AXE OPC client The Standard Attributes will contain Source NODE yyy where yyy is the node number E g NODE 003 for node number 3 Time The timestamp when the event occurred in the controller This timestamp is sent from the controller Type Simple EventCategory System Severity The alarm priority 1 7 sent with the event is converted to an OPC severity 1 1000 Message A text based on a text index number sent from the controller The MB3 A amp E OPC server searches for the text in the MB3_System_Events txt file The parameters in the text are filled in with the parameters received with the event 6 2 System
Download Pdf Manuals
Related Search