Issue
Why do you need to mask the events in both door editor and the point itself (08, 09)?
Environment
I/NET Seven
Cause
Door masking is required in both the door editor and the point itself.
Resolution
Think about door masking as layers.
When you create a door, you need to create a point/relay for the door. This relay changes state (0,1), this is the hardware layer, Layer one.
In order for AMT to get a event that the point have changed state it needs to ask the controller of the status. This is done by a quick poll command issued by the SLI.
In order to make this point to behave like a door we need to add some feature to it, a second layer. This layer is not hardware dependent but it speaks to the hardware. Here you can add some additional event or in this case alarm as "forced door". This alarm will be distributed to the event handler of the point so next quick pull will catch this information and it will be sent to AMT.
So in order to get alarms and transaction from the door specific attributes both the point/relay (So the quick pull can get its information) and the second layer door needs to be masked. So the information will become correct its also important that the points and door masking priority are the same.