Mercury Releases New Series 3 Redboard Access Panels

By Brian Rhodes, Published Feb 15, 2018, 12:40pm EST

Mercury Security has their first major product release post-HID buyout, and things literally look different. The Series 3 SIO boards now are red instead of green. However, the new series also incorporates hardware changes that deepen OSDP integration, plus improvements in on-board LED notifications.

But with new product shipments already started, will the new products work as before, and do they cost more?

We examine the new releases inside based on feedback from Mercury.

Hardware ********

******* *********** ***** ******** ********** 'Serial *****/******' ******* ******, which *** ******* ** calling '****** * ***'. ***** *** ********* level ****** *** *******, the ******* ****, *****, and ********* ****** *** the **** ******* ****** * ******.

***** *** ******* ** post-HID ********, *** ******* tell ** '****** * products **** **** ** design *** *********** *** 18 ****** *** ******* well ****** *** *** acquisition.' 

****** *** *************** **** ******* *****:

  • **** - ****** ****** I/O
  • **** - **** ******, 8 *********** */* *****
  • ******- ********** ***** *****, supporting ** ** ** devices
  • ******* - ********** ****** board, ********** ** ** 16 *******

******* *** **** **********, but ******** ******** **********, is *** *** (******* circuit ******) *** ** longer***** *** ***:

******* ** ********* ** this ********** ** ******** as '********', *** ********** the **** ** *******'* portfolio **** ** ******* to *****.

******** ******** *** ******* Series * *** ****** 3 ***************, *** *** new ******** ******** *** backward ********** **** ****** 2 *******.

Deepens **** *******

*************, *** '****** *' update ******** ******* ********** that ******* **** ********** security *********, **** ** FICAM *** ****'* '****** Channel' ********* ****.*.* *** *****. **** *********** ********** ********** over ****, ************ ********* **********:

****** ******* **** ******* * method ** ************ **********, key **********, *** ************** on ** **** **********. Using ***-*** ********** *** CMAC ******** (*** **** ***), **** ****** ****** relatively **** ************** ** control ****** *** ********** devices, **** ** ******* in Assembler.

** ******** ******* *** versions, **** ******** ******* support *** '*********', *** the ******** *********** ***** up **-***** ******** ********* across *** ******* ***** to **** ******* ****** and ** ******* *********** when ***********. ******* **** **** that *** ****** * design ** ***** *** supporting ******, **** ********* security *********:

"*** [****** *] ***** needed * ******* ** avoid ********* **** ************ and *********** **** ********** power *** ******."

******* **** ********* *** deepened **** ******* ******** in ****** *:

"*** ****** * ****** support **** ********* ******** features **** ** **** Secure *******, **** ********, and ******** ************ *** biometrics *** ******* ********** specific ******** ** ******* of ***** *************.  ************, we **** ***** ** embedded ****** ****** **** for ******** **** ******** that ******** * ****** layer ** ********** *** sensitive **** ** *** device. "

*** ******* **** ********* that **** ** ******** for ****** ********/******** ** be ******** ** ** upgraded ** *** ********* systems ** ****:

"****** **** ****** ******* and ***** *******, *** of *** ********* *** features **** **** ** the ******* ** *********** specific ********.  **** ******* Mercury ** ****** *** personality ** ********* *******.  For *******, ** *** case ** ***, ****** end ********* ** **** off **** ******** ** through *** *** ** config *****.  ******, **** transfer **** ****** *** reader ******** ******** ** be ********* ****** *** the ******* ********** ** potentially *** *** *** software ********* ******* ***********."

Including ****** *** ********

*** ** *** **** visible ******* ** *** update ** **** ****** 3 ****** *** ******* the ******* ** *********** information ** ***** *** onboard *** ********, **** the **** ********* **-***-*********:

****** ******* ********* ******* that **** *********** **** to *** **********, **** accommodates ************* *************, ********* user prompt ************* ** ******** options *** *******.

** *** ****-**** ************ at ******* ** ********, as ****** ** ***** messages *** *** ** descriptive. ** ********, ***-**** systems ********* **** ****** reader *** ***** ** sound * ****** - signals **** ***** *** *** easily ***********.

***** *** ******** *** still ******** ** **** access *******, ******* ****** support ***** ** ******** level *********** *** *** feature ** ******** ******** who ********* * *********** percentage ** *** ****** market.

Pricing *********

****** **** ****** *******, Mercury ***** ** ******** but **** *** ****** under *** *** *****. As ****, ******* ******* is ********* *** ************ negotiated, *** ******* ******* companies **** ********* ***** reseller ****** * ******* is *** **** ** Series *.

More '*********' ******

***** ******* ********, ********* the ********-********* ********** '**' series, **** ** ******* to '********' ** ****. However, *** ****** *** not ** ******* *********** across ********. ******* ********* to **** ** *** update ** **, ***** will ** ****** '**' as ***** ******** *** moved ** * ***** based **:

** **** ** ********* an ****** ** *** current ** ********** ****** as ****.  ** ******** to *** ******** ******* like **** *** ****** 3 *******, *** *** feature *** *** **** generation *********** **** ** the ********* ** *** underlying ********* ****** ** the ***** ***********.  *** that ******, ** ***** to *** *** **** of *********** ** *** “LP” ****** *** “***** Platform”.  

** ***** ** *******, Mercury ****** ** ***** are '***** ** *** development *** ******* *****' with ** ******** ******* in **** ****.

*******, **** ** *** advanced **** ******* ****** by ****** * *** boards ** * ****** of *** ****** ******* are ********* ** *** 'smarter' *** **** ********* EP ******, *** *** future ** ****** *** slated ** ** ****.

Competitive *********

************, *** ******* ********** to ****** * *** interestingly ** ********** ********, *** ***** series**** ****, ****, *** V300 ********* ******. *******, given ***** ******* *** dated, **** ** *** support *** **** ********* versions ** **** **** Series * ****.  ***** like **** ******** ** reader ****** *** *** supported.

******* ***** ********* **** **** ****** ************ ****** *******, *** ********* ****** ******* ** *** ******* *****/****** boards, *** **** ********* be ******** ** ***** enterprise *********** ********* **, they ** *** ******* offsets ** ****** * product.

Comments (8)

Thanks, Brian! Great article with very timely info for me!

Agree
Disagree
Informative: 2
Unhelpful
Funny

This is good except we are still waiting for Encryption at rest on the ISC (LNL-4420) and only then we can have true end to end Encryption.  Right now its bits and pieces, glad to see they are making headway.

Agree
Disagree
Informative: 2
Unhelpful
Funny: 1

"Existing partners can support Series 2 and Series 3 interchangeably, and the new redboard products are backward compatible with Series 2 systems."

I was under the impression that Series 3 boards were not backwards compatible for use with Wiegand readers. Sounds like this is not the case?

Agree
Disagree
Informative
Unhelpful
Funny

Yes, Series 3 still support Wiegand as well.

Agree
Disagree
Informative: 2
Unhelpful
Funny

How about a comparison to S2?

Agree
Disagree
Informative
Unhelpful
Funny

Welcome!  Thanks for the question.

Mercury only makes hardware.  In fact, S2 is one of the platforms that uses Mercury hardware, in addition to NetBox controllers.  (For more platforms compatible with Mercury, see: Axis vs HID vs Mercury Access Controllers)

Because of this, the comparison is either incomplete (ie: hardware only vs. access system), or a comparison of S2 to itself!  :)

Does that help?

Agree: 1
Disagree
Informative: 1
Unhelpful
Funny

Maybe the question was a comparison between the capabilities of series 2 versus series 3 Mercury Hardware?

Agree
Disagree
Informative
Unhelpful
Funny

For me the most important development is the addition of the hardware crypto element. At long last manufacturers, and hopefully, end users are starting to realise that security should only be implemented on hardware designed for that purpose. The greatest weakness in OSDP2 (a very good protocol) is the storage and dissemination of secrets, and hopefully this should address this.

Agree
Disagree
Informative
Unhelpful
Funny
Read this IPVM report for free.

This article is part of IPVM's 6,910 reports, 923 tests and is only available to members. To get a one-time preview of our work, enter your work email to access the full article.

Already a member? Login here | Join now
Loading Related Reports