Overview

NetworkLockServlet demonstrates how a 1-Wire® device can be deployed in an access control system. In this example, a DS2409 is connected to a Blue Dot receptor and a DS2406. The Blue Dot receptor detects authorized users while DS2406 controls the opening and closing of the door. Since only one channel of the DS2409 can be active at any time, opening the door by tampering with the Blue Dot receptor can be prevented and hence increase security.

Controlled Door Access Flow Chart


Also, with the ability of a web server, all administrative monitoring can be performed via the Internet. For the purpose of demonstration, some Network Commands are included to show the possibilities.

Schematic

The reference design can be found at TINIDoor.pdf

Setup

The following information assumes that the reader is familiar with building and running applications on the TINI platform. For information on TINI, please see http://www.ibutton.com/TINI/index.html.

The NetworkLockServlet has been tested with TINI 1.02 and TiniHttpServer0.14.
  1. Download tini1.02 from ftp://ftp.dalsemi.com/pub/tini/tini1_02.tgz.
  2. In order to run the NetworkLockServlet, TiniHttpServer needs to be installed as well. TiniHttpServer can be downloaded from http://www.smartsc.com/tini/TiniHttpServer/docs/index.html. Follow the instructions given there.
  3. For information on using NetworkLockServlet with TiniHttpServer0.12, please see THS0.12setup.html. For TiniHttpServer0.14, please see THS0.14setup.html.
  4. Make sure that the door lock circuit is connected to TINI. The LED should start flashing. Open a telnet session and run TiniHttpServer.tini by typing at the TINI prompt:
    source /bin/TiniHttpServer
  5. You should see the following message:
    NetworkLockServlet: init
    which indicates that the NetworkLockServlet is up and running.
  6. Open your favorite browser and type in a URL similar to the following:
    http://www.your_tini_url/NetworkLock.html
    The log in page now appears.
  7. Log in with:
    Username = admin
    Password = tini
    
    Note that both the username and password are case sensitive.
  8. Click on the "Start Circuit" link to activate the lock. Status in the initialization process will appear in the right frame. Once initialization has completed, place a valid iButton on the Blue Dot receptor, the door LED will light up indicating that access has been granted. If you touch an invalid iButton on the receptor, the LED should stop flashing. It will remain off for a couple of seconds, indicating access is denied.

Operation

Door LED blinking Door lock is operational and is waiting for valid iButton.
Door LED ON If a valid iButton is detected, access is granted and the door LED will stay ON for DOOR_OPEN_MILLIS millisecond.
Door LED OFF Either the lock is disabled or invalid iButton is detected. In the case where an invalid iButton is detected, access is denied and the LED will stay OFF. The door will resume operation after DOOR_DISABLE_MILLIS millisecond.

Sample Network Commands

Log In Administrator log in page. ALL administrative functions require log in to verify authorized access.
Log Out Log out page. Terminate administrative rights for this log in session.
Start Circuit Start lock circuits. Log in required.
Stop Circuit Stop all active lock circuits. Log in required.
Open Door Open door from a remote host. A list of available door circuits are displayed and the user can select from the list. Log in required.
Add User Add in authorized user. Administrator needs to supply user name and a valid iButton serial number. Log in required.
Remove User Remove user access. Administrator needs to supply a valid iButton serial number. Log in required.
Display All Users Display all authorized users. Log in required.
Change Password Change administrator password. Administrator needs to supply "User Name", "Old Password", "New Password" and "Confirm New Password". Log in required.
Commit Changes Commit changes to memory. Any changes not committed will be lost on next TiniHttpServer launches. Log in required.

Performance

Emperical results indicate that less than 100 mS are required to detect iButton and open the lock. Response time is directly proportional to the number of locks monitored by TINI and the amount of process active on TINI.