Page Comparison

The RS-485 Readers Expansion Board (RREB) is the component of Identiv’s end-to-end FICAM solution which provides eight independent RS-485 communication ports, for fast processing of PIV or PIV-I credentials at FICAM-compliant smart card readers (which are part of a physical access control system) using the bi-directional Open Supervised Device Protocol (OSDP). Each port is capable of supporting a door with both an entry reader and an exit reader.
The following figure shows an RREB, and identifies its connections.

Figure 2-1: Connections on the RS-485 Readers Expansion Board (RREB)

Government agencies transitioning from a traditional PACS to FICAM will need to replace their old readers and upgrade their version of the Velocity software, but the RREB (in conjunction with the SNIB3) enables them to reuse their existing wires and door controllers (including the M2, M8, and Mx series). The RREB:

• Provides the necessary connections to FICAM-compliant smart card readers (which are part of a physical access control system), for two-way communication with the SNIB3.

• Uses standard RS-485 wiring (two-pair stranded and twisted 18 AWG wires, with an overall shield) to the readers.

• Has the same form factor as other expansion boards, and draws power through the controller’s EBIC5 ribbon cable.

Wiring Diagram for an RREB

The following figure shows an example wiring diagram for an RREB and a pair of Identiv’s uTrust TS Government Readers, which are the entry reader and the optional exit reader for a door. Note that:

• The exit reader is wired through the entry reader for a door, so it shares an RS-485 port on the RREB.

• On the exit reader, a jumper wire is needed between P1.1 and P1.4 (or between the orange and the black wires on the pigtail model) to designate that it is the exit reader.

• All of these readers have a default OSDP Address of 0, which is the correct value when they are used as the entry reader for a door. If a door also requires an exit reader, then adding a jumper wire between P1.1 and P1.4 (or between the orange and the black wires on the pigtail model) changes the default OSDP Address to 1, which is the correct value for an exit reader. Be sure that you specify the correct OSDP
  Address when you configure each reader in a FICAM-capable version of the Velocity software.

• The diagram shows power being supplied to the readers from the RREB. But depending on the types and quantity of readers being used, you might need to power some of the remotely located readers from an external power supply. For more information, see “Power Provided at the RREB’s RS-485 Terminal Blocks”.

Figure 2-2: Example Wiring Diagram for an RS-485 Readers Expansion Board (RREB)

The following table lists Identiv’s FICAM-capable High Frequency TS readers (which appear in the Readers > uTrust TouchSecure > Government FICAM category of the Product Catalog for Hirsch by Identiv Physical Access Control Solutions).

For information about installing the RREB, see “RS-485 Readers Expansion Board (RREB) Installation”.

Power Provided at the RS-485 Terminal Blocks

An RS-485 Readers Expansion Board (RREB) draws its power from the EBIC5 cable connecting a controller to its expansion boards. The following table shows the power provided at the RS-485 terminal blocks of an RREB.

Table 2-1: Voltage and Maximum Current Draws for an RREB’s RS-485 Terminals

Because each RS-485 port is fuse-limited to a maximum of 0.5 Amps, you will need to use an external power supply when the combined requirements for the entry reader and the exit reader of a door exceed that limit.

RREB Power Rating

• The RREB is powered by the 28V rail from the EBIC5 cable from the controller.

• The quiescent current draw of the RREB is 10mA @ 28V.

• The RREB converts the 28V into two power rails 5V and 12V. The 5V rail can power the SNIB3 and the12V rail powers the readers.

• Max Rating of 5V rail on RREB is 3A.

• Max Rating of 12V rail on RREB is 4A.

• Each of the 8 reader ports on the RREB is fused at 500mA.

Touch Secure Reader Current Consumptions

** indicates supply voltage for the RREB is 28V

Load Calculation

(( RDR1 Current + RDR2 Current …. + RDRN Current) X RDR Voltage ) + (SNIB3 Current X 5V ) RREB Q Current

____________________________________________________________________________________ +

DCDC Efficiency X RREB Voltage

Where,

• RDR Voltage is 12V

• DCDC Efficiency is 80%

• RREB Voltage is 28V

• RREB Q Current is 10mA

Illustration 1: SNIB3 with 2 TS Wall Mount STD Reader and 2 TS Keypad STD Reader

• Current draw of TS WM STD RDR at 12Vis 114mA

• Current draw of TS KP STD RDR at 12Vis 166mA

• Current draw of SNIB3 at 5Vis 1.35A
  

= ( 0.114 + 0.114 + 0.166 + 0.166) X 12 ) + ( 1.35 X 5 ) + 10 = 611mA

________________________________________________

0.8 X 28

Illustration 2: TS Wall Mount STD Reader and 2 TS Keypad CTY Reader (SNIB3 is not powered from RREB)

• Current draw of TS WM STD RDR at 12V is 114mA

• Current draw of TS KP CTY RDR at 12V is 166mA

• SNIB3 is not Powered from RREB
  

= ( 0.114 + 0.114 + 0.266 + 0.266) X 12 ) + 10 = 417mA

___________________________________

0.8 X 28

Wiring Distance Limits for an RREB

The following table shows the wiring distance limits between an RS-485 Readers Expansion Board (RREB) and a FICAM-compliant smart card reader (which is part of a physical access control system). Note that the wires must be stranded and pair twisted, with an overall shield.

Table 2-2: Wiring Distance Limits Between an RREB and a FICAM-compliant Smart Card Reader

RS-485 Readers Expansion Board (RREB) Installation

When installing an RREB, you will typically also be installing a SNIB3 (unless one was previously installed in your controller) as part of upgrading your traditional Velocity system to a FICAM-capable solution. Here is the general procedure for installing an RREB and a SNIB3.

1. Power down the controller.
   a. Disconnect the battery backup power from the controller.
   b. Disconnect the AC power from the controller.

2. If this is an existing controller which still has a SNIB or SNIB2 board installed, remove it.

3. If this is an existing controller which is wired to traditional readers that are being upgraded, disconnect the wires from the MATCH and/or Wiegand terminals (on the controller's main board).

4. If you are upgrading an existing system, there might be enough slack in the wire runs that you can reuse the existing wires. Otherwise, run the necessary wires from the new readers to the controller.

5. Connect the appropriate wires to the male end of the RS-485 connectors, as shown in “Example Wiring Diagram for an RREB”. Here is a close-up diagram of an RS-485 connector:
   

Image Removed

1. Image Added

2. Install the RREB on the supplied standoffs, and attach it to the next-to-last connector on the EBIC5 ribbon cable. If you need more details, see “Connecting Expansion Boards”.

3. Plug the wired male end of each RS-485 connector that is used into the female end of the correct door port on the RREB.

4. Check whether your SNIB3 is a current version which includes surge protection, or whether it is the initial version which did not include surge protection.
   
   When using the initial version of the SNIB3 board (which has a serial number of the form SNIB3-S-nnnnn), surge protection must be provided for the master SNIB3 in each chain of connected controllers, using the Sankosha Guardian Net LAN-CAT5e-P+ surge protection device. For details, see “Providing Surge Protection for a Master SNIB3”.

5. Connect the 8-wire data cable between the RREB and the SNIB3, as shown in the following diagram.
   

Image Removed

1. Image Added

2. Install the SNIB3 on the supplied standoffs, and attach it to the last connector on the EBIC5 ribbon cable, so it is the topmost board on this controller’s stack of expansion boards.

3. Route the incoming Cat5e (or higher) Ethernet cable through a knockout hole in the controller’s cabinet and connect it to the Ethernet connector 1 RJ-45 jack on the SNIB3 board (which is colored blue on the previous diagram).

4. Restore power to the controller.

   1. Reconnect the AC power to the controller.

   2. Reconnect the battery backup power to the controller.

5. At the Velocity host, use Velocity to configure the SNIB3, as explained in “Using Velocity to Configure a SNIB3 on the Same Subnet”.

If this is an Mx controller which provides SNIB2 functionality using a daughterboard attached to the main board, see “Preparing an Mx Controller with a SNIB2 to Use a SNIB3” for detailed instructions.