Prox Reader Compatibility

We had a bit of a fuss recently over some reader incompatibilities. A client was previously using CDVI Centaur access controls on their sites, then the last few years started moving to Kantech with HID readers on new sites (and retrofitted one older site). Naturally, the Centaur and HID fobs don't work with each other's readers, and while the plan is to eventually replace all the Centaur stuff with Kantech and HID, that's happening more on an if-it-ain't-broke-don't-fix-it basis.

Somewhere along the way, on the last two sites (both with Kantech panels), a miscommunication meant one new site got a mix of HID and ioProx readers, and another was outfitted with all ioProx readers, which of course, don't work with everyone's existing HID fobs. The one site also got a bunch of ioProx fobs that naturally didn't work with the half of the readers that were HID. (Fortunately, NONE of this was my fault!)

Now I've made an interesting discovery: I was given a decommissioned CDVI Atrium panel, and playing with it at home, I discovered the CDVI reader with it works with both the Centaur AND HID fobs, as well as a Viscount fob. Now I'm thinking... if these readers will work with both the Centaur (should, it's made by CDVI as well) and Kantech panels, we could start using them in new builds to allow use of both types of fobs they already have, and gradually swapping out existing readers for these would put us ahead of the game when other sites are upgraded to the Kantech.

So... has anyone tried this - specifically, CDVI DigiProx readers with a Kantech panel? How about with a Centaur?

Login to read this IPVM discussion.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

*** ***** ** ****** *****'* ******, **** ******* ** *** bit ******/********* **** ** ****** ** *** ******. ** *** case ** *** **** ********, *** ******** ****** ****** ** 26-bit ******* *** **** ** ********* (* ***** *****) ** every ****** ****** ******* ******** *** *****. ** *** **** have ** ******** ** *** ********** *** **** ******* ** the ******* ******. ** **** ** **** ***** *** ** the ****** (*** ********* **** ** **-*** ** **-***) *** frequency (*** ***) **** ** **** ** **** ****** *** understood ** *** **********, **** *** ******* ********** **** ********** it ******* *** ******.

**** *** ***** **** ******* *** ********, ** ***'** ***** Weigand ** ******* ******* ** *****, ** **** ****.

*******, *** *** **** ******* **** **** *** ******* (**:** ** ** ****** **** **** ***), ** *** ***** ************* *** ****.

** ****,

* *** *** ******** ** **** **** ******* *** ***** and ******** * ******* ****** **** * **** ****** *****. I ******** *** *** ****** ******* *** *** ***** ****** without *** ******.

* **** * *** * ***** ** **** ****** ** try *** **** *** *** *******, *** * ** ******* you *** *** **** ** ** **** ** *** ****** the ******* ****** ****** ** *** ** *** *******.

**** **** *** ***** ** ** *-**** **** ******* (******* at ****.**) *** **** ****** ** **** ** ****** *********. The ***** ******* *** ***** *** ** *******, *** * don't **** ** ****** **** **** **** ***** ****** *** the *** ** ** ****.

******, ***!

*** *** *** ******* **** * **** *** *** **** ones **** ** *** ******, ** * **** ** * suggest ***** **** ******* **** **** **** ****, ****'** **** with ******. *** ** * **** ***** ******* *** **-*** Wiegand, ** ***** ****** ** ** *******. ****** **** ******** if ****** *** ******** **** **. * **** * *** old ******* *** *** ******* ** **** * *** **** up ** ** ****** ** ****, **** *******. **'* ** AV-22, *** ******* *** *** *****, ** *'** **** ** just *** * ****** ** * **** :)

** ****, * **** **** * **** ******* ***** **** the **** ** ******** ** *******/***... * ***** **'* *** main ***** *** * ****** ******** *******. **** ******* ** a *** *** *** **** **** ** **, *** **** I'm ******** ** *** ****** * *** **** ** *** it ** ** ** ***** ****** *** **** **** ** too!