:: Manuals Home   :: Contact us   :: SG1 Website   :: Site Map  
Key Machine Configurations
| AttendanceNET | DeveloperNET | KeyNET | ProjectNET | WorkNET

Sections

   
Table of Contents    
Access & Restrictions    
Your Desktop    
     
PEOPLE Module    

 

   

KEY ISSUE Module

 
   

LOCKSHOP Module

   
   Key Operations    
   Display Inventory    
   Modify Key Definition    
   Add/Remove Hooks    
   Add/Remove Location    
   Add/Remove Masters    
   Add/Cut NEW Key    
   Billing & Cost Centers    
   Bulk Transfer    

   Recall a KeyID

   

Masterkey Systems

   
   2 Step Progression    
   1 Step Progression    
   SFIC A2    
   SFIC A3    
   SFIC A4    
   Assa    

   Medeco

   

   Custom Developed

   
     
System Manager    
   People Configuration    
   Lockshop Config    
   Key Machine Config    
     

Features

   
Authorizations    
eKeyRequest    
   Request Methods    
   WEB Forms    
eKeyOrder    
ePhotoID    
eSignature    
iKeyID    
Keyrings    
Multiple Key Issue Sites    
     

F.A.Q.

   
     

       

Each Module has a CONFIGURATION section which is ONLY seen by the system administrators

 

The Requirements for using a computerized key machine with KeyNET are listed below.

The CONFIGURATION for the Computerized Key Machines is accomplished like this:

NETWORKED: Each device must be assigned a STATIC IP ADDRESS.  When the KeyCut module is licensed.  Setup may be accomplished.  KeyNET technicians must configure your communications device (Cyclades TS-100 or Lantronix UDS-10, although the UDS-10 is field configurable).

 

SERIAL CONNECTION:  When connecting a device directly to a computer, two things are necessary.  First, your Browser must be set to read JAVA Script APPLETS.  Second, the KeyCut module must be licensed.

The KeyCut module is a separately-licensed product which allows keys to be cut under program control on automated key machines.  Infrastructure is in place to support a virtually unlimited number of key machines, and to support various interfaces and models of key machines, as we add support for them.

Currently, cutting on an ITL-9000 box connected through a Cyclades TS-100 or Lantronix UDS-10 interface is supported.  However, other devices are being tested all the time, and when approved may be used to communicate to Computerized Key Machines and Computerized Stamp Machines.

When the product is licensed, new checkboxes appear in the Lockshop, Configuration, Module Permissions configuration allowing specific users permission to cut keys.  In addition, System Administrators see a new choice in Keynet Configuration, "CONFIGURE KEY MACHINES."  Clicking on this link allows users to define one or more key machines to the system.

When defining a key machine, you choose a name for the machine, then you provide the IP address of that machine.  You also specify the interface type and key machine model via pull-down menus.  If your product is not shown, contact support@sg1.us for help.

Once key machines are defined, users with authorization are given the option to cut keys in the "Add/Cut New Keys" screen.  The user selects the desired key machine, and clicks the CUT button, and the cut is immediately initiated.  This section is displayed with red shading and a warning message to emphasize the need for caution.  Users can choose their "preferred" key machine in MY
PREFERENCES.

As in Connie, a three-digit CUT CODE is recognized by the ITL-9000 driver as being an ITL manufacturer ID.  Anything else in the CUT CODE field will result in the ESP custom depth table being downloaded prior to the cut.

Unlike Connie, KeyNET remembers the "0=10" status as a part of the key's definition.  Keys will be cut with the "A" code when the 0=10 box is set in the key definition, regardless of vendor and/or modifier keys.

WHEN DEFINING KEY MACHINES FOR TESTING, PLEASE USE ONLY THE FOLLOWING IP ADDRESS:
 

127.0.0.1

This will tell the server you're testing, and prevent it from sending data to un-expecting recipients.

The TS-100 and UDS-10 communicate with the ITL-9000 at 9600 baud, so reducing the speed to other baud rates is no longer needed, to insure non-corruption of data.

KeyNET supports automatic interfacing with all ITL Computerized Key Machines.  The communications is over a TCP/IP connection between the KeyNET server and a Cyclades, or Lantronix converter box. 

REQUIREMENTS FOR SUPPORTING A REMOTE KEY MACHINE:

Cyclades TS-100 - Support of a remote key machine requires that we deploy a Cyclades TS-100 micro-server or similar device, which is physically attached to the key machine. This device has two ports - a serial port which drives the key machine, and an Ethernet port, which plugs into the nearest LAN jack.  Spectrum Group should pre-configure your Cyclades TS-100 for your system.  The requirements to operate this device are:

  1. Device must have its own dedicated IP address.  Customer must provide IP address, Submask and Default Gateway information for programming purposes.

  2. If in a NAT/private LAN block, device must also have a public internet IP address assigned to it, which routes traffic on ports 22, 7000 and 7001 from said public IP address to the internal IP address of the Cyclades box.

  3. If behind a firewall, device must also be permitted to receive traffic on ports 22, 7000 and 7001 from our central server network (we will provide a range of 10 static IP addresses which should be permitted to send to the Cyclades box.)

  4. If neither NAT/PLAN/firewalled, Cyclades box will be configured to use its own internal firewall protection scheme.

Lantronix UDS-10 - Support of a remote key machine requires that we deploy a Lantronix UDS-10 device server or similar device, which is physically attached to the key machine. This device has two ports - a serial port which drives the key machine, and an Ethernet port, which plugs into the nearest LAN jack. Spectrum Group will pre-configure your Lantronix UDS-10, or it is field configurable.  The requirements to operate this device are:

  1. Device must have its own dedicated IP address.  Customer must provide IP address, Submask and Default Gateway information for programming purposes.

  2. If in a NAT/private LAN block, device must also have a public internet IP address assigned to it, which routes traffic on ports 10001 from said public IP address to the internal IP address of the Lantronix box.

  3. If behind a firewall, device must also be permitted to receive traffic on ports 9999 from our central server network (we will provide a range of 10 static IP addresses which should be permitted to send to the Lantronix box.)

 
Copyright ⓒ 1996-2006 The Spectrum Group. All rights reserved