Related Manuals for Avea WAC2
Summary of Contents for Avea WAC2
- Page 1 WAC2 USER MANUAL IoT Wiegand Access Controller June, 2018 AVEA International Company Limited (http://avea.cc)
-
Page 2: Table Of Contents
Table of Contents Table of Contents ......................... 1 WAC2 IoT Access Controller ....................... 3 SETUP THE READER ........................4 ........................4 EFAULT ETTINGS ..................4 ESET CONFIGURATIONS TO DEFAULT DHCP ........................4 ORCE MODE INSTALLATION ..........................6 ................7 OWER... - Page 3 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 PHP CODE EXAMPLE ......................25 WAC2 IoT Access Controller...
-
Page 4: Wac2 Iot Access Controller
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. -
Page 5: Setup The Reader
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. - Page 6 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;...
-
Page 7: Installation
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. -
Page 8: Power Input And Ethernet Connection
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. - Page 9 WAC2 requires 9 to 12V DC 500mA for 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.
-
Page 10: Wiegand Interface
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. WAC2 IoT Access Controller... -
Page 11: Relay Control
The pinouts of the terminals is as follows: PINOUT DESCRIPTIONS NC - normal close, it is connected to CO normally. CO - common, it will connects to either NO or NC, but not both. NO - normal open, it is open circuit normally. WAC2 IoT Access Controller... -
Page 12: Dipsw Options
2.4 DIPSW Options DIP switch option sector is the DIPSW for selecting varies options for the WAC2. 2.4.1 Reset to default By setting DIPSW position 1 to on, the controller configuration will be reset to the default state. -
Page 13: Test Mode
By setting DIPSW position 3 to on, the controller configuration will be set to the access the AVEA’s server for testing purpose. It must be set to off position for normal operation. It assumes a DHCP server is available in the local network. -
Page 14: Reserved
2.6 Reserved 2.7 Mechanical Dimensions Height: 25mm Width: 78mm Depth: 112mm WAC2 IoT Access Controller... -
Page 15: Software
3. Software WAC2 is a HTTP client with PHP enabled. It will send PHP URL requests to the HTTP server with the various parameters. And it accepts responses from the HTTP server to perform various actions on the reader. 3.1 Requests to HTTP server The followings are the variables presented to the PHP. -
Page 16: Uid
So the server can decided to take further actions. 3.1.6 $channel It signify the action is coming from which channel of the WAC2. $channel=1, the action is coming from channel 1 $channel=2, the action is coming from channel 2. -
Page 17: Mode
3.1.7 $mode For WAC2, $mode=AC1. So it can be used to identify the reader. 3.1.8 $ver It is the firmware revision. Currently it is 1.39. 3.1.9 $recno Hold the reference number of the record in decimal format. The server must response this parameter in order to acknowledge the record and confirm the deletion of that record. -
Page 18: Md5
$cmd=ET to the web server with those parameters. $event valid values are { ‘add’ , ’app’ , ’del’ , ’clr’ , ’err’ } $cnd is the RFID card number WAC2 IoT Access Controller... -
Page 19: Responses From Http Server
3.2 Responses from HTTP server After sending request, WAC2 will wait for a response from the HTTP server. It looks for the starting flag <AVEA> and the ending flag </AVEA>. Then it interprets the strings in between. There must be no space between the keywords and parameters. The maximum size of the response packet should be less than 600 bytes. -
Page 20: Grnt=Xx
This will change the root page to be access by the reader. It is a fixed length format in decimal value. For example: ROOT=00024689, this will make the reader to access the page /24689.php rather than the default /avea.php. By setting ROOT=00000000 will reset to access the default page. -
Page 21: Dhcp=X
This is a fixed length command and values are in decimal. It will change the default router of the reader. Example: GW=192.168.001.002 3.2.11 NM=xxx.xxx.xxx.xxx This is a fixed length command and values are in decimal. It will change the netmask of the reader. Example: NM=255.255.255.000 WAC2 IoT Access Controller... -
Page 22: Ws=Xxx.xxx.xxx.xxx
Once the reader get this response, it will delete that record accordingly and cannot be recovered. 3.2.16 SID=xxxxxxxx This is a fixed length command and values are in hexadecimal value. It is a non-volatile value and will not be changed after power removed. WAC2 IoT Access Controller... -
Page 23: Ac=Xxxxxxxxxx
10 decimal digit of the access card number. It is a non-volatile value and will not changed after power removed. The controller will not search for the duplication of the card, hence, it will take short time for the appending. WAC2 IoT Access Controller... -
Page 24: Clear=All
If PPC=0, card only access is enabled. Presenting the granted card will allow access. If PPC=1, PIN and CARD mode is enabled. User need to enter the PIN number then presenting the granted card to get access. WAC2 IoT Access Controller... -
Page 25: Grnt2=Xx
This is a fixed length command and values are in decimal. If RLY=1, the channel 1 relay will be turned on. If RLY=0, the relay will be turned off. The state of relay will be affected by the subsequence commands. WAC2 IoT Access Controller... -
Page 26: Php Code Example
$mycard=359452; // replaced by your card number $rtime=$date . $time; // access the date and time of the reader $remote_open=1; echo "<AVEA>"; // starting flag switch ($cmd) { case "PU": // power up echo "CK=$st"; // set clock if ($mode==ID2) { // for web08s only echo “DHCP=1”;... - Page 27 "HB": // heartbeat echo "CK=$st"; // set clock break; case "PG": // being pinged echo "CK=$st"; // set clock break; echo "</AVEA>"; // ending flag ?> </body> </html> WAC2 IoT Access Controller...
Need help?
Do you have a question about the WAC2 and is the answer not in the manual?
Questions and answers