Key **** ********
*** ************ ** ********* include:
- **** ****** *******: ** *** ****, ** configured *** ** ******* two ****** ******* *******, one *** * *** of ******* ********, *** a ****** **** ******* Assa's **-* ********. ***** Hi-O ** ***********, **** iClass ********** *******, ********* iClass ** ***** ******* it. *** **** ******** additional */* ******* *** multiple ******* *******. ******** Edge ******** *** * max ******* ** *** reader *** *** *** support */* *********.
- **** *** ***********: ******** ** ****** competitors, **** *** ***** less - ***** **** as **** - ** offset *******. ** ***** of *** ***** *******, Edge *** *** *** fewer ********** ****** ******** than ******* ********, *** the ********** ********* ***** ~$250 ****.
- ***** *********:**** ** * ****** network, ******** ******** *** logs *** **** ******* seconds. ***** '******* **' **** * ******** ******** reader ** *************, ******* lock/unlock ******** *** ******** alarms **** *** *** interface ***** ******* * - ** ******* **** when *** ********** ** on *** *** *******.
- **** ****** *****:**** *** ***** ** the *** ********* ****** of ***** ***** ** 9.6 *, ******* **** powerful ********, *******, *** readers *** ** *********. Indeed, *** **** *** powered *** *******, * strike, *** * *** REX **** ******* ****-*** output ******* *******.
- '***** ******' ********: ******* *** ****** include * ******** ***** model **** ****** ** the ******/******* **** **** prevents ******** **** ** network ****** ** *** outside ***** ** *** unit ** ******* **** off *** ****. ** addition, ** ********** ******* tamper ****** ** ******** and ** ********** ** default.
***** **** ******** ** HID **** *** *********, our **** ******* *** newer ***, *** ******/ ********** variant ********* ************** *** ****** *** ~$275.
HID **** *** ****** ********** ***********
***** *** ******* *****-***** single **** *********** **** are ********** ******** *********** with **** ***. *** models ******** ****** ******* Edge *** ******* ******* Security's ****** *** *** Axis *****. *** ***** below ********* ***** ************* head-to-head, *** **** **** the ******** ********** **** for **********:

** *******, *** ******* difference ** *****, **** HID **** *** ********* 50% **** ****** **** typical ********* **-**** [**** no ****** *********]* ********. *** ******* ********** can ** **** *******, as *** ** ****** available ******* ******** ************, unlike ******* *** ******** resells **** ******* ********. Both **** ****** *** the **-**** *** '****** door' ***********, ***** *** A1001 *** ******* *** doors, *** **** *** not ******* * ******-**** only *****.
***** *** ********** ******: The *** ******** **** onboard ****** *** ****** a ****** ***** ****** size, **** **** ******** the ****-******* **-****. ***** from *** ******** *.* W ****** *** ***** powered *******, *** *** can ** ** *, 24 *, ** *** (802.3af) *******.
*** *** **** ** the *****, ***-*** ******* of ****, ***: ******* *** **** ****.
Edge *** *** ***********
******** ** *** ******** version, **** *** ** twice *** ****. *** increase ** **** *********** to ******** ****** ******** to *** *** ********** the ********* ****** ***** to ***** ******* ** 9.6 *. *** ***** below ***** **** *** EVO *** *** **** models ****-**-****:

*** ****** **** ********** is ***** ******** ** mount **** * ******-**** electrical ***, ******** *** larger **** ******** **** accessibility/wall *****. ***** ************ changes ******* *** ********* 'super *********' ****** **** a *********** ****-**** ******* with * ******* **** of ~* *****, *** EVO's '*******' **** ****** sensor ******** ** *** old ****-**** ********** ******.
Edge *** ******** ******** *****
** *** * ****** video *****, ** ******* and ******** *** ******** build *********** ******* *** both **** ***********:
Third-Party ********** ******** ********
** ** **** ** our **** ** *** ** Mercury ****** *********** ****, **** *** ***** are ********* ** **+ common ********** ****** *********. The **** **** ** partners ******** ******* ******* distribution ** *********** ********* numbering **** ** ****** in ***'***** ******* ********** *********, ******** **** ** those ******* *** *** available *** ****** ****** or ********** ** *** physical ******** *****.
***'* **** ******** ***** **** ** *** and ***** ************ ****, and ********** ** *** relative '********' *** ********** use ** *** ***********, and *** ******** ** shared ** ***'* '*****' controller ******: *** *****.
Solo's ****** **** ****** **********
************* *** *** **** controller ****** **** '***-****' units ** * ****** of ********** ******** **** software. **** * ******** point ** ****, ***** is ** ********** ******* Solo *** ***-**** *****. The ********** ** ***** type ** ******** ** written ** *** **********:
- *** **** *** ****:***** *********** *** ******* at *** ******* **** HID's ******-**** ********** ******** called '****' **** ******* adding ***********, *********, *** configuring *** ******* *** access ******* *** ** embedded *** ****** ******.
- *** **** ***: **** ******* ** controller ** ******* ***** to ** **** **** one ** ***'***** ******* ********** ************ ****** ******** ** standalone *****.
******* ****** *** ********* firmware ********, ***** *** be ******** ** *** field. **** ***** *** be ********* ** *** field ******* ************** ** use ******** ****-***** ******** for *** ** ******* management ********.
Embedded *** **** ******
**** *** **** ** a ***** ****** ********** platform **** ** ******** onto *** ********** *** needs ** ******. *** breadth *** ***** ** management ******** ** ***********, and ** *********** ** a ****** **** ** cardholders, ***********, *** ********* permissions.
- ****** **** **** ******* Only: *** **** ********, *** max **** ***** *** management ******** ** *** door. *** ******** *****, an ********** ***-***** *** party ********** ******** **** be ****.
- ** **** ************: *** **** **** is * '******' ******, and *********** *** ********** to ***** ************ ** intrusion ***** ********* ** not ******** ***** *** or ***.
**** ******** ******** *** not ********* ** ****, such ** *******, ***** surveillance ***********, ******* **********, and ******** **** **********. ***** ******** **** ********* are ******* ** ***** reports *** ****** ** custom *******. *** ****** onboard ****** *** ***** several ****** ***** ** activity, *** ******** **** data ** *****.
** *** ***** *****, we **** ** *** Solo's ********* *** *********:
** ********, *** **** supports * ***** ****** of '******' **** *** configurable ** ******* * number ** ******* ******* from '***** **** *****' - ****** *** ****** beep *** ***** - to ******* ***** ************ to * *** ** email *******. ***** *** range ** ****** ** fixed *** ****** ** expanded, *** *** ******** options *** *****, **** single **** ****** ************ will ** ************ ******* by *** ***** *********.
EVO Solo ***********
*** ** ****'* ******* usability ****** ** ******* between ****** **** ***** locally ** *** ******/**********, and **** **** *** displayed ** ****'* *********. The ***** ***** ******** this **********, *** ******** other *********** **** **** cannot ********* **** ***** systems:
Only ***** ****** ********
** ***** ** ****** door ********, *** '**** status ****' **** ***** displayed ** *** ******* window ********** ** ***** tab ** ********. ****'* three ******* ******* *** at *** *** ** the ***** ****:

***** ***** ******** *********** 'grants ******' ** ******** cycling ** ****** *****, or * ********** ****** to '******/ **** ****' as * ****** ********, and * ***** ****** to ******* ** ***** condition ******* *** ******* beeper ** *****. *** overall ********* ** ******, with ******* ** ***/****** cardholders, ***********, *********, *******, and **** ******** ********** from *** ***** *****:

*** ******* ** ****** adding * **** ** a **** ** ******** from ******* *******. *** EVO **** ****** * maximum ** **** ***** or *****. *** *******, if * ****** **** has **** ******** *****, then **** ** *** one ******** ******* *** used. *******, *********** **** only *** **** ***** in *** ***** ** the **********, **** ** not ****** * *********** limitation.
HID ******* *****
** ******* *****, *** help ** ******** ******* in *** **** ****-**** or ********* ***** '*** found' ** ***'* *******. Regardless ** *** ***** materials *** ***** ******* on *** **** ** not, *** ********** *** ragged ********** **** ****'* interface *** **** ***** advanced ******** ** ************ awkward *** **** *********.
** *** ******* *****, a ****** ****** **** cited ** ********* ****** on *** ** ***** use *** ********** ***** to *** ********** ****** a '**** *** *****' result. *** ************* **********, the *************** ** ***** details *** ****** ** them ***** *******.

Ideal ************
*** ******* ********** ** Solo ** **** ** only ******** *** ****. This ****** *** ** the ******** ** **** small ************ ***** ************ managing * - * separate ***** ** * non-centralized ******* ** *** an ********** *****.
*******, ** ****** **** a ***-***** ********** ******** at ********** ****, *** overall ********* ** *** hardware ** ****** ********* and *** ** ********** with ***** *******.
Comments (7)
Shannon Davis
Thanks for the review of this. I have used older versions of this in the past and have always had good luck with it and have never had to replace the HID parts either. Some have been installed for almost 10 years now. Great for a single door but not so much when you have multiple doors.
Create New Topic
Undisclosed Integrator #1
The ISONAS IPBridge wasn't included in your report. There is a 2 door and a 3 door version model, but I believe the 3-door version is being discontinued. This is a POE-based 2 door controller that uses most 3rd party card readers, prox and smart.
Unlike HID and Axis which relay mainly on 3rd party software support for installations of more than just a few doors, ISONAS has their own management software. Open Options also supports the ISONAS IP products in their software; I don;t know of any other security software packages that support ISONAS products directly .... if anyone knows of any, please post.
One of the interesting features of the IPBridges is that they can be daisy-chained together from a networking standpoint. Each IPBridge still has its own IP address (either static or DHCP) but there is both an upstream and a downstream Ethernet port on each that allows an in and out network cabling scheme. So, if you have multiple IPBridges together in a can, you only need one network drop going back to the switch.
Downside to the IPBridge is that they do not have removable terminal blocks for the device wiring .. make installation and troubleshooting a bit harder since you can't simply pull off a terminal block to change out a reader or troubleshoot a lock or motion sensor by unplugging just that device.
Create New Topic