Avea WAC2 User manual

WAC2
USER MANUAL
IoT Wiegand Access Controller
29th June, 2018
AVEA International Company Limited
(http://avea.cc)

WAC2 IoT Access Controller
1
Table of Contents
Table of Contents .........................................................................................................................1
WAC2 IoT Access Controller.......................................................................................................3
1. SETUPTHE READER..................................................................................................................4
1.1 DEFAULT SETTINGS ...................................................................................................................4
1.2 RESET CONFIGURATIONS TO DEFAULT........................................................................................4
1.3 FORCE DHCPMODE..................................................................................................................4
2. INSTALLATION............................................................................................................................6
2.1 POWER INPUT AND ETHERNET CONNECTION.............................................................................7
2.2 WIEGAND INTERFACE................................................................................................................9
2.3 RELAY CONTROL.....................................................................................................................10
2.4 DIPSW OPTIONS.....................................................................................................................11
2.4.1 Reset to default...................................................................................................................... 11
2.4.2 Force DHCP enable.............................................................................................................. 11
2.4.3 Test mode...............................................................................................................................12
2.4.4 Reserved DIPSW...................................................................................................................12
2.5 BATTERY .................................................................................................................................12
2.6 RESERVED...............................................................................................................................13
2.7 MECHANICAL DIMENSIONS .....................................................................................................13
3. SOFTWARE .................................................................................................................................14
3.1 REQUESTS TO HTTPSERVER...................................................................................................14
3.1.1 \avea.php...............................................................................................................................14
3.1.2 $date and $time.....................................................................................................................14
3.1.3 $id..........................................................................................................................................14
3.1.4 $uid........................................................................................................................................15
3.1.5 $cmd......................................................................................................................................15
3.1.6 $channel................................................................................................................................15
3.1.7 $mode....................................................................................................................................16
3.1.8 $ver........................................................................................................................................16
3.1.9 $recno....................................................................................................................................16
3.1.10 $rdate and $rtime................................................................................................................16
3.1.11 $sid ......................................................................................................................................16
3.1.12 $deviceid .............................................................................................................................16
3.1.13 $md5....................................................................................................................................17
3.1.14 $event and $cn.....................................................................................................................17

WAC2 IoT Access Controller
2
3.2 RESPONSES FROM HTTPSERVER ............................................................................................18
3.2.1 HB=xxxx................................................................................................................................18
3.2.2 BEEP=x ................................................................................................................................18
3.2.3 CK=YYYY-MM-DD HH:MM:SS...........................................................................................18
3.2.4 GRNT=xx ..............................................................................................................................19
3.2.5 DENY ....................................................................................................................................19
3.2.6 ROOT=xxxxxxxx ...................................................................................................................19
3.2.7 EXT=x...................................................................................................................................19
3.2.8 DHCP=x ...............................................................................................................................20
3.2.9 IP=xxx.xxx.xxx.xxx................................................................................................................20
3.2.10 GW=xxx.xxx.xxx.xxx ...........................................................................................................20
3.2.11 NM=xxx.xxx.xxx.xxx............................................................................................................20
3.2.12 WS=xxx.xxx.xxx.xxx ............................................................................................................21
3.2.13 PT=xxxxx ............................................................................................................................21
3.2.14 RLY=x .................................................................................................................................21
3.2.15 REC_DEL=xxxx..................................................................................................................21
3.2.16 SID=xxxxxxxx......................................................................................................................21
3.2.17 AC=xxxxxxxxxx ...................................................................................................................22
3.2.18 DC=xxxxxxxxxx...................................................................................................................22
3.2.19 APC=xxxxxxxxxx.................................................................................................................22
3.2.20 CLEAR=ALL.......................................................................................................................23
3.2.21 ACPIN=xxxx .......................................................................................................................23
3.2.22 PPC=x.................................................................................................................................23
3.2.23 GRNT2=xx ..........................................................................................................................24
3.2.24 DEN2...................................................................................................................................24
3.2.25 RLY2=x ...............................................................................................................................24
4. PHP CODE EXAMPLE ..............................................................................................................25

WAC2 IoT Access Controller
3
WAC2 IoT Access Controller
WAC2 is an access controller which embedded with Ethernet connection and using HTTP
for communication control protocol. Hence, it can communicate directly with Apache Web
Server or Microsoft Internet Information Server. WAC2 provides 3,000 access cards and
50,000 access logs records.
It is implemented as a HTTP web client. Various page extension is selectable,
like .php, .asp, .cfm, .pl, .htm, .html and .aspx. So various HTTP server systems (e.g. IIS and
ASP from Microsoft; Apache with PHP enabled and mySQL database server from Unix/Linux),
a complete and powerful time attendance system can easily be implemented.
When cards are presented, the transaction information is stored inside the memory of the
reader with 50,000 records allowed. The record is looked up from the local access table with
3,000 records allowed. If access allowed, it will engaged the relay to allow door open. The
memory is retained even power is lost.
The controller provides two Wiegand RFID reader interface and two relays output for
controlling door access.
Whenever there is network connection and the server is running, those records will be
sent to the server. Upon confirmation by the server, the controller will be told to delete the
records accordingly.

WAC2 IoT Access Controller
4
1.Setup the reader
In order to work properly, WAC2 must be configured correctly before putting into actual
usage. For normal condition, the blue LED is blinking.
1.1 Default Settings
The default configurations of the WAC2 is listed as follows:
Parameter
Description
Default
IP
IP address of the reader itself
192.168.1.234
GW
Gateway IP address
192.168.1.1
NM
Netmask
255.255.255.0
WS
HTTP server IP address
192.168.1.1
PT
HTTP server port number
80
EXT
Page extension
php
1.2 Reset configurations to default
If for any reasons, the state of the WAC2 is not known. Before power up, set DIPSW 1 to
on position. When power on, the settings of WAC2 will be cleared and set to the default
settings. DIPSW 1 must be set to off for normal operation.
1.3 Force DHCP mode
When DIPSW 2 is set to on position. DHCP mode will be forced to enable for automatic
configuration of the WAC2.A DHCP server must be available in the network for this
operation. If the DHCP server configured with the options www-server, i.e. option 72, the
web server address of will also be set automatically.

WAC2 IoT Access Controller
5
Example of dhcpd.conf:
#example of dhcpd.conf for AVEA’s IoT devices
ddns-update-style ad-hoc;
subnet 192.168.1.0 netmask 255.255.255.0 {
# --- default gateway
option routers 192.168.1.1; # default gateway
option subnet-mask 255.255.255.0; # netmask
option www-server 192.168.1.123; # it must setup to the web server’s IP
range dynamic-bootp 192.168.1.10 192.168.1.99;
default-lease-time 300;
max-lease-time 3600;
}

WAC2 IoT Access Controller
6
2.Installation
In order to work properly, WAC2 must have stable power supply, a 10-baseT compatible
Ethernet connection. The WAC2 provides interface to connect two Wiegand 26 or
Wiegand 34 RFID reader and each associated with its own relay control.
Remember to remove power when doing any installation or connection.
The following diagram show the PCB of the WAC2 controller.
Remark:
1. Ethernet Connector
2. Channel 1 Relay Connector
3. Channel 2 Relay Connector
4. CR1220 Battery for Real-time Clock
5. Not used
6. DIP Switch Option Sector
7. Wiegand Reader Connector, Channel 1 and Channel 2
8. Reserved

WAC2 IoT Access Controller
7
All connections from the WAC2 is through the RJ45 connector. The following diagram
show the pinouts of the RJ45 plug.
2.1 Power Input and Ethernet Connection
Ethernet connector is a RJ45 terminal which is the connection to Ethernet network and
also the input power to the controller.
The pinouts of the terminals is as follows:
PINOUT
DESCRIPTIONS
1
ETHERNET, TX+
2
ETHERNET, TX-
3
ETHERNET, RX+
4
POWER
5
POWER
6
ETHERNET, Rx-
7
GROUND
8
GROUND

WAC2 IoT Access Controller
8
WAC2 requires 9 to 12V DC 500mAfor normal operation. Since the POWER/GROUND
will be connected to the Wiegand port as well, more current will be needed to drive them.
The power supply must be feed through the POE-02 power injector or equivalent.

WAC2 IoT Access Controller
9
2.2 Wiegand Interface
Wiegand reader connector is a RJ45 terminal for connecting Wiegand 26/34 RFID
reader.
The pinouts of the terminals is as follows:
PINOUT
DESCRIPTIONS
1
POWER
2
CHANNEL 1, DATA0
3
GROUND
4
CHANNEL 1, DATA1
5
POWER
6
CHANNEL 2, DATA0
7
GROUND
8
CHANNEL 2, DATA1
The POWER/GROUNG pair is the power supply to the controller which can be used to
power the Wiegand readers. Be careful of the correct voltage ratings.
DATA0/DATA1 corresponding to the Wiegand’s DATA0 and DATA1.