User's Guide

LSP3A Clear User’s Guide

It is only for internal use and shall not be spread without permission

In this section, one can activate the useful Event Notification, a standalone feature which

duplicates the database entry by sending to any PC on the network a data frame. This allows

sending alarm data whenever an event occurs in any pedestal without having to regularly pool the

pedestal database over the network. It limits the traffic over the network.

To activate the Event Notification, just tick at least one Event out of the 3 available. All Events

can be selected if needed.

If IP address is left to the default “FF.FF.FF.FF” data is broadcasted to all equipments on the

network. Possible Events are:

 People Counter Change: Whenever one walks through the gate passageway, data is

sent over the network once. The Data field includes the new In Out and In + Out value.

 Alarms: Upon Tag(s) detection their UID & Memory Contents is sent over the network

according to the settings defined.

 GPIO State Changes: Whenever an Input or Output level changes it is notified over the

network. The data field reports the GPIO new status.

In this mode, when an event in the selected option occurs, a specific UDP message is sent to

the specified IP address and port.

Table 5.3:Head

Version Mac Addr IP Addr Date(M-D-Y) Time(H-M-S) Event ID

2bytes

(default:0x0100)

6 bytes 4 bytes 3 bytes 3 bytes

1 bytes (Alarm:0x00,

PeopleCount:0x01,

GPIO:0x02)

Table 5.4: when people counter is changed, sent an UDP message

Head InCount OutCount

Head frame 4 bytes 4 bytes

Table 5.5: when device is alarming, sent an UDP message

Head Alarminfo TagType RFU DataLen Data

Head frame 1 byte 1 byte 4 bytes 1 byte

Date_len’s

bytes

Table 5.6:when GPIO status is changed, sent an UDP message

Head GPIO Status Mask

Head frame

GPIO1 high: 000000x1b(bit 0 is 1)

GPIO1 low: 000000x0b(bit 0 is 0)

GPIO2 high: 0000001xb(bit 1 is 1)

GPIO2 low: 0000000xb(bit 1 is 0)