WIEGAND access control

This example shows how to setup an access control using wiegand interface of Avior. Connect a WIEGAND reader to digital inputs:

• Terminal 07 (Input 1): Data 0.
• Terminal 08 (Input2): Data 1.
• Terminal 01: Negative.

EXTERNAL POWER SUPPLY FOR WIEGAND READER MUST MEET SELV CIRCUITS REQUIREMENTS ACCORDING TO EN/IEC 62368

Configuration

WIEGAND channel enabled.

Users

In user list, some wiegand users are added:

NAME:       MagneticCard
TYPE:       WIEGAND
IDENTIFIER: 12345678
GROUP:      
START:      01/01/2000 00:00
STOP:       31/12/2099 23:59
WEEKDAYS:   YYYYYYY
TICKETS:    UNLIMITED
NAME:       PlateNumber
TYPE:       WIEGAND
IDENTIFIER: 1C2345F6
GROUP:
START:      01/01/2000 00:00
STOP:       31/12/2099 23:59
WEEKDAYS:   YYYYYYY
TICKETS:    UNLIMITED
NAME:       RFdongle
TYPE:       WIEGAND
IDENTIFIER: 12345678
GROUP:
START:      01/01/2000 00:00
STOP:       31/12/2099 23:59
WEEKDAYS:   YYYYYYY
TICKETS:    UNLIMITED
For the PlateNumber an APNR camera is required.
In general any equipment which transmits a wiegand code can be connected to Avior.

If you don't know the WIEGAND identifier associated with your tag, keyboard or license plate open the Terminal and ask for the status. Here you can see the last WIEGAND code detected by Avior.

Rules

Rule 001 is triggered on reception of a Wiegand code stored within the users list.
No conditions are set.
A pulse of 3 seconds is made on output 1 and a local beep is played.

WiegandUsers
↯ WIEGAND from user
✛
✛
✛
✛
✛
> out1=ON,3
> at#spk=5
>
>
>

Rule 002 is triggered on reception of unknown wiegand code.
No conditions are set.
An email with detected code (K01) is sent to "admin@email.com" address.

WiegandUnknown
↯ WIEGAND from unknown
✛
✛
✛
✛
✛
> at#email=admin@email.com,"unknown wiegand","$K01"
>
>
>
>