Fashionable Watches

mapp AlarmX 1 – How to set up an alarm management [sub: EN, DE, PL, PT-BR, RU]

mapp AlarmX 1 – How to set up an alarm management [sub: EN, DE, PL, PT-BR, RU]


Hello and welcome to Part 1 of the mapp tutorial “Alarm management”. In this video we’ll be learning how to set up an alarm management system quickly and easily using mapp. As you can see, I’ve already prepared a sample project. It’s a basic setup with an X20 controller. Before we can start using the alarm management component, we first have to add the configuration object “MpAlarmXCore”. Here, we add the mapp Link, which uniquely identifies the mapp component within the mapp environment. The mapp Link establishes the connection between the software and the configuration. We’ll create a new user alarm, called “TemperatureHigh”, which will be triggered later in the program. Under “Message”, we’ll enter the text that should be displayed with the alarm. This alarm will remain active for as long as the temperature is too high. As soon as it falls back into the tolerance range, the alarm will be reset. To achieve this, we need to create it as a “Persistent alarm”. Now we’re already at the last step: the programming. For this part I’ve already prepared a ladder program called “AlarmCtrl”. Of course, with mapp, you’re free to use any programming language you like. The first step is to add the “MpAlarmXCore” component. This forms the core of our alarm management system. Using the “MpLink” input, we’ll establish a connection to the configuration we created named “gLinkAlarmXCore”. We’ll enable the component by setting the “Enable” input. Once MpAlarmXCore is enabled, all alarms – mapp alarms and user alarms – are collected and managed. In order to set the alarm we created before in the configuration, we need to add the function “MpAlarmXSet”. The alarm is activated once by a rising edge on the “UserAlarm” command. For the mapp Link, we’ll use the same one that we connected to “MpAlarmXCore”. Under “Name” we specify the name of the user alarm: “TemperatureHigh”. “MpAlarmXReset” is responsible for resetting the alarm. The alarm is reset by a falling edge on the “UserAlarm” command. For the mapp Link, we’ll use the same one that we connected to “MpAlarmXCore”. Under “Name” we specify the name of the user alarm: “TemperatureHigh”. In order to acknowledge the alarm, we first have to add the function “MpAlarmXAcknowledge”. A rising edge on the “AckUserAlarm” command acknowledges the alarm. For the mapp Link, we’ll use the same one that we connected to “MpAlarmXCore”. The name of the user alarm is specified under “Name”. Now we can save the project and transfer it to the controller.

Then we’re ready to test our new alarm management system. First, we’ll switch to monitor mode. You can see I’ve added the “UserAlarm” variable in the Watch window.
Looking at MpAlarmXCore, we can see that no alarms are active. We’ll activate our alarm with the “UserAlarm” command. MpAlarmXCore now indicates that an alarm is active. To deactivate the alarm, we’ll reset the “UserAlarm” command. The “PendingAlarms” output indicates any alarms that have not yet been acknowledged, whether they are active or not. That’s why it is still set to 1. To acknowledge the alarm, we’ll use the “AckUserAlarm” command. Now there is no longer a “PendingAlarm”. A core feature of mapp is the ability to perform diagnostics and configuration via a web browser – using the mapp component “WebXs”. This is found in System Diagnostics Manager under “Application Status”. On the left you’ll see a list of all the mapp components that are currently enabled. Each component is now sending all of its live data to the web browser. This allows you to perform reliable diagnostics at the application level very quickly and without needing any special tools. We can check the current status of the function by expanding the “Info” structure. Check out Part 2 of the “Alarm management” tutorial to find out how to display your alarms via the HMI application. Thanks for watching!


Leave a Reply

Your email address will not be published. Required fields are marked *