MBLogic
for an open world in automation
3) Configure the Application User Data
This involves entering the application specific data into configuration files to be used by the web client.
3.1) Enter the Client ID String and Polling Interval
These are stored in the "clientconfigdata.js" file.
- MBT_ClientID - The client ID string. Replace this with your own client id.
- MBT_ScanRate - HMI scan in milliseconds. The web browser will poll the server at the interval defined here.
MBT_ClientID = "Default HMI Client ID"; MBT_ScanRate = 1500;
3.2) Enter the SVG Screen Layer List
This is also stored in the "clientconfigdata.js" file.
- MBT_SVGScreenTable - This is the list of SVG screen navigation "id" labels. This *must* match the list in the SVG drawing. It should only however include the "id" labels of the layers which you wish to hide and show under menu control. Layers which need to remain visible all the time (e.g. the menu, the background, etc.) should not be listed.
MBT_SVGScreenTable = ["ExampleSVGScreen1", "ExampleSVGScreen2", "ExampleSVGScreen3"];
3.3) Enter the Tag and Zone Lists
The tag and (alarm and event) zone lists determine what data is requested from the server by the client. This data is also stored in the "clientconfigdata.js" file.
- MBT_ReadList - Address tag read list. This is the list of address tags which will be read from the server. Replace the example tags with your own application tags. You can add or remove tags as necessary.
- MBT_AlarmZoneList - Alarm zone list. This is the list of alarm zones which will be read from the server. Replace the example zones with your own application zones. You can add or remove zones as necessary
- MBT_EventZoneList - Event zone list. This is the list of event zones which will be read from the server. Replace the example zones with your own application zones. You can add or remove zones as necessary.
MBT_ReadList = ["ExamplePL1", "ExamplePL2", "ExamplePL3", "ExampleTank1Level", "ExamplePumpSpeedCmd", "ExampleStripChart1"]; MBT_AlarmZoneList = ["ExampleZone1", "ExampleZone1", "ExampleZone1"]; MBT_EventZoneList = ["ExampleZone1", "ExampleZone1", "ExampleZone1"];
3.4) Enter the Alarm and Event Messages
The texts of the alarm and event messages are stored in a file called "messagetexts.js".
- MBT_AlarmText - Alarm message texts. This translates the alarm tags to the message texts which are displayed to the operator. Replace the tags and messages with your own actual data. You can add or remove records as necessary.
- MBT_EventText - Event message texts. This translates the event tags to the message texts which are displayed to the operator. Replace the tags and messages with your own actual data. You can add or remove records as necessary.
MBT_AlarmText = {
"PB1Alarm" : "PB1 was pressed.",
"PB2Alarm" : "PB2 was pressed.",
"PB3Alarm" : "PB3 was pressed.",
"PB4Alarm" : "PB4 was pressed."
}
MBT_EventText = {
"PumpRunning" : "Tank pump is running.",
"PumpStopped" : "Tank pump is stopped.",
"Tank1Empty" : "Tank 1 is empty.",
"Tank1Full" : "Tank 1 is full.",
"Tank2Empty" : "Tank 2 is empty.",
"Tank2Full" : "Tank 2 is full."
}
You can also store other message texts here as well. For example:
// This is an example of text indicators. Msg_HMIDemoColours = ["red", "orange", "yellow", "green", "blue", "indigo", "violet"];
If your HMI application requires several different HMI web pages with different alarm and event message texts (for example to support multiple languages), you can rename the "messagetexts.js" to something else (e.g. "messagetexts_en.js", "messagetexts_fr.js", etc.). However, you must then change the file name in the web page used to import the file.