Card readers are typically used on exterior doors and allow entry to a
facility or area swiping a magnetic pass or small key fob over a
magnetic card reader, and an electric strike or magnetic lock opens.
The verification of the card ID takes place either locally at the door
(using an intelligent panel) or remotely via a database belonging to a
PC based access control system.
In the case of the COM1000, it is
possible to perform both of these functions, as well as additional
Here are some examples:
Using a locally
hosted access list inside the COM1000 (of up to 100 unique card IDs),
can read the card reader data, compare it to the local list, and then
activate an external door lock or relay.
The COM1000 can
transport the card data to a report server via any LAN or WAN IP network
using either UDP or TCP.
The COM1000 allows
for remote triggering of the relay via browser interface and/or command
The COM1000 can send
customized notifications based upon an unsuccessful match.
The COM1000 can date
and time stamp each card read regardless of authentication, and save
to a retrievable event log.
The COM1000 can send
the card reader event log to any user or remote server via either SMTP
- Easy Local or Remote Programming/Updates
Card access lists can
be created by simply swiping the card pass or key fob, and accepting
Card Reader Protocol
Access lists can be stored as part of a COM1000 configuration template,
and used to program other units.
Changes to the access list can be done remotely over any IP connection
using COM1000 Configuration Utility
or command line interface.
The COM1000 currently supports readers using the WIEGAND 26 protocol.
The WIEGAND 26 message is a 26-bit message, including a 10-bit Facility
ID and a 16-bit Card ID. We
currently do not support the facility ID portion of the message, only
the 16-bit Card ID. That means that each COM1000 Card
ID entry is entered as a 16-bit number, and therefore ranges from 0
The following are some examples of readers currently supported in this
If you have an interest in another reader, please consult with us at email@example.com