Access Control Plugin breaking changes

MIP
, , , ,
1

I’ve just upgraded our demonstration system from the 2016 R3 release to the 2017 R3 release and am no longer able to add my input and output objects to a map.

The alarms for them show in the events and the state changes show in the developer tabs of the access control module in the manager application but the actual items are no longer shown in the tool window to drag and drop access control elements onto a map.

Is this a known issue, by design or something that has been inadvertently broken?

Regards,

Simon Davis

2

Does this fit - https://force.milestonesys.com/support/articles/en_US/How_To/deploy-a-newer-Access-solution-in-older-XProtect-software

?

3

I don’t believe so. we have an older access solution running against a newer XProtect one.

The problem appears to be at the Smart client - it no longer shows all the items that it did on the previous version

4

2016r2client
2016r2client422×480 52.7 KB
This is what it looked like on 2016 R3. on 2017 R3, I only see the Main entrance and stores beneath the top EntroStar unit and the access points beneath the doors

5

We suspect it might be an un-desired side-effect of a bug fix. (A fix that should hide diabled doors.)

We will be doing a closer investigation here at Milestone Systems.

6

Hi Simon,

I have few questions in order to understand your use case a bit

better.

  1. I can see that you have couple of inputs and outputs that are

related to some specific doors but are not underneath (children of) those. Why

is that the case?

  1. In case you need inputs/outputs that are not door related -

can you give us an example of that use case?

7

Hi Milos,

Our access control panel is a flexible unit that can have up to 2 doors/4 readers and then 9 inputs and 4 outputs.

By default, 3 inputs and 1 output are assigned to each door to cover the door contact, break glass and rte input functions plus the door strike and these are named according to the defaults. The remaining I/O is available for such functions as light control and intruder/perimeter detection equipment. Internally, within our EntroWatch product, we track the usage and condition of the inputs and update either the input itself or the door depending on its association.

In the case of the milestone plugin, for simplicity, we parent all the I/O against the controller, regardless of its usage.

I trust that this answers your questions, if you need any further information please ask.