Setting up ww.dll:
The .dll must be version 4.2 and have Validation and Axess sections to the ww.INI file.
[Validation]
SalesEZ=127.0.0.1:4203
Location=1
[Axess]
GoodScan=<BTURNSTILEACTIVE>1</BTURNSTILEACTIVE><NTURNSTILEACTION>0</NTURNSTILEACTION><NGREENLIGHT>1</NGREENLIGHT><NREDLIGHT>0</NREDLIGHT><NYELLOWLIGHT>0</NYELLOWLIGHT><NRETNICKTIME>30</NRETNICKTIME><NSOUNDTYPE>1</NSOUNDTYPE><NDISPTIME>30</NDISPTIME>
BadScan= <BTURNSTILEACTIVE>0</BTURNSTILEACTIVE><NTURNSTILEACTION>0</NTURNSTILEACTION><NGREENLIGHT>0</NGREENLIGHT><NREDLIGHT>0</NREDLIGHT><NYELLOWLIGHT>1</NYELLOWLIGHT><NRETNICKTIME>30</NRETNICKTIME><NSOUNDTYPE>2</NSOUNDTYPE><NDISPTIME>30</NDISPTIME>
It’s important that all possible fields be filled in for the GoodScan and BadScan settings. These settings are described in Axess’ documentation, but indicate the manner in which the turnstile is to respond to scans.
Note:
• NRETNICKTIME and NDISPTIME is in tenths of seconds.
• BTURNSTILEACTIVE indicates whether or not to open the turnstile (and, as of POE #100 (192.168.0.104) it indicates the number of entries). So, this is often overridden.
• NRETNICKTIME may need to be adjusted with multiple entries. It is the amount of time the person has to go through. Axess recommends setting this to 0, but actually a long time-out (i.e., 300 / 30 seconds or 600 / 60 seconds) makes sense for a group.