User Manual

Known issues in MP3.15

Building Technologies 008901_a_en MM8000 MP3.15 Release Notes

Fire Safety & Security Products 09.2005

New in 3.15

SiPass

– Multiple connections to SiPass server.

SiPass RPC interface supports only one connection. Configurations including multi-

ple MM8000 servers connected to the same SiPass server are not possible.

– Reader name, FLN name and structure.

This information cannot be acquired from SiPass; this prevents MM8000 from rep-

resenting the entire physical structure of the devices.

– Object states and events.

The following information is not transmitted to MM8000:

– Reader Tamper and Off-line

– REX Tamper

– Door Block and Door Open (frame contact)

– ACC Tamper, Power Fault, and Battery Operation

– Area and Elevator objects are not visible at all

– Duress Alarm

– Soft Anti-pass back

– Support of CerPass hardware (CC30) is currently not possible.

– Access Denied events are not transmitted to MM8000 in case of:

– Card not yet active

– Time schedule violation

– Expired card

– Void card

– Wrong PIN

– Access with Daily code

– The use of SiPass Alarm Classes with MM8000 is affected by a number of limita-

tions. MM8000 can receive and then present the SiPass events only if:

– Alarm Class Type is Input (no Outputs, Access or any other type)

– Alarm Handling is set to “Require Acknowledging”

– Alarm Options do not include the “Restorable Alarm”

– The definition includes all the possible input states of the object (e.g.: Door forced

and Door held, etc.)

 See also the SiPass chapter in the MM8000 ICC manual (Installation, Configu-

ration and Commissioning).

– Event categories defined by other types of Alarm Classes will not be handled by

MM8000 and should therefore be treated in SiPass (pop-up event).

– The SiPass functions which are also available in MM8000 - e.g. event notifica-

tion (message forwarding in SiPass), reactions and sequences (event tasks in Si-

Pass) - should be clearly assigned to either of the two systems, according to spe-

cific requirements, thus preventing any functional overlap.

– Access control transactions cannot be used in Reaction and Sequences yet.