7/6/2021 7:29 AM | |
Joined: 5/3/2017 Last visit: 5/21/2024 Posts: 673 Rating: (217) |
Hi LostinFog, to add an Alarm_8P to your block, you only have to add a special input and and a call the function Alarm_8P. The input needs the attributes S7_server:='alarm_archiv'; S7_a_type:='alarm_8p'; and is from type DWORD. You can find a example for use a Alarm_8P in the FAQ What should you watch out for if you want to call two ALARM_8P blocks in a function block?. With regards |
This contribution was helpful to1 thankful Users |
7/6/2021 1:37 PM | |
Joined: 3/14/2008 Last visit: 9/20/2024 Posts: 2095 Rating: (936)
|
Hi, If you want to do it the PCS7 way (APL), you have to do the following:
1. Set the block with alarm attribute (System attributes for blocks)
2. Configure the MsgEvId1 in the VAR_INPUT section
3. Configure an ALARM_8P instance in the VAR section
4. Configure the ALARM_8P instance in the code, under FALSE, you can write your own variables to create the alarm. The SD_x items are auxiliary values that can be sent with the alarm. Normally, the batchname, step number and batchID are being sent, along with external values. You do not need to use the SD_x values, just out comment them.
However, there is more to it. In APL a runup cycle (RunUpCyc) is used to prevent alarms being sent during startup of the block. Also, calling alarms is prevented when OoS is active (Out of Service). |
If I could help you, you can use the RATE button. Thank you. |
|
Follow us on