Avigilon Access Control Core Installation Guide

Overview

The Avigilon Access Control Core (ACU) is an access control unit designed to manage up to 8, 12, or 16 entries through two expansion board connections. This guide covers the installation and configuration of the Access Control Core as part of the Alta access control system, including connections to Mercury™ hardware and third-party Wiegand and OSDP readers.

What's Included

• Access Control Core unit
• Power cable
• Bracket and push-in fasteners
• Tamper sensor wire (optional)

Site Survey and Requirements

Conducting Site Surveys

Before installing Avigilon hardware, conduct a site survey to determine:

• The number of entries (doors, gates, elevator floors) to be configured.
• The type of wiring required (legacy or new).
• The electronic entry mechanisms (e.g., Request to Exit - REX), door contact sensors, and their power requirements.
• If locking hardware requires 24V, determine if a Smart Hub with a 24V power supply or a separate 24V supply will be used.
• The need for backup batteries for a Smart Hub (refer to 'Selecting a backup battery' on page 32).
• Support for legacy access control panels for mobile gateway integration (refer to 'Wiring to legacy panels and mobile gateway' on page 19).

Network Requirements

An Ethernet connection with DHCP is required to connect the ACU to the Local Area Network (LAN). Firewall settings may need to be configured for communication with Alta Access, which uses the following outbound ports:

• TCP port 443
• UDP port 123

Note: If an external DNS server is used, outbound UDP port 53 must also be open.

Enclosure Requirements

• The Access Control Core and Avigilon expansion boards are typically installed in an Avigilon Smart Hub with a pre-installed power supply. The Avigilon 4-Door Smart Hub (SYS-4ENT-DVE1) is used as an example.
• For other Smart Hubs, refer to 'For more information' on page 33.
• The Access Control Core, Mercury controller, and subpanels can also be installed in a LifeSafety Power® enclosure.

Refer to vendor documentation for information on third-party enclosures.

Installation

Specifications

For detailed specifications and dimensions of the Access Control Core, consult the OP-CR-ACC datasheet. All national and local electrical codes must be followed during installation.

Avigilon Reader Wiring Requirements

Avigilon readers and ACUs communicate via RS-485. The following wire types are recommended, listed in order of preference for optimal distance:

• Shielded CAT6A (recommended; additional pairs can be used for sensors)
• Shielded Cat 6
• Shielded RS-485 (18-24 AWG; thicker wire is better)
• Shielded Cat 5
• Unshielded Cat 6
• Unshielded Cat 5
• Shielded 22/6
• Unshielded 22/6

Note: Use one twisted pair for GND and VIN (power) and another twisted pair for +B and -A (data).

ACU and Wiegand Reader Wiring Requirements

Table 1: Connections from Avigilon ACU to Avigilon Reader

Table 2: Connections to Third-Party Wiegand Reader (Optional)

Operating temperature range: -22°F to 140°F (-30°C to 60°C).

Recommended maximum cable length: 300 ft (91 m) with CAT6 or 500 ft (152 m) if two wire pairs are used for GND and VIN.

Shielded Wiring: Connect one side of the drain wire (shielding) to the GND terminal on the ACU. The shield and GND wire can share the same terminal. Do not connect the other side of the shield.

Note: For elevators, all relays and readers must connect to the same ACU. For more than four access-controlled floors or readers, use the 16 I/O Elevator Board.

Warning: Always disconnect power from the ACU and locking hardware before wiring Avigilon readers and other devices to prevent damage.

Legacy Wiring

Legacy wiring (unshielded, straight-through, often 22-6 AWG) can lead to slower connections and dropped packets. To improve this, swap GND and VIN with +B and -A connections on the ACU and readers, ensuring the data pair (+B and -A) uses the alternate wire pair.

Standard Configuration

Wiring the Access Control Core in a Smart Hub

Smart Hubs come with pre-installed power supplies; Avigilon boards must be installed separately. Example: 4-Door Smart Hub

1. Connect the Access Control Core to an Ethernet cable with internet access.
2. Connect the Access Control Core to an Avigilon expansion board using the USB cable.
3. Connect the Access Control Core to a power supply using the included power cable.

   Warning: Do not apply power during wiring. Ensure the power supply is unplugged until all wiring is complete.

4. Optional: To monitor tamper events, attach the included tamper wire to the tamper switch on the enclosure and plug it into the Access Control Core.

Advanced Configuration

Mercury Device Installation

Mercury devices can manage entries with third-party Wiegand and OSDP readers:

• MP Series MP1501 and LP Series LP1501 controllers support up to 8 entries.
• MP Series MP1502 and MP2500, and LP Series LP1502 and LP2500 controllers support up to 32 entries.

Prerequisites

Before proceeding, refer to:

• Enclosure requirements on page 8.
• Mercury device installation in Third-party documentation on page 33.

Note: Avigilon Alta Access supports only the specified Mercury devices. Other models may not function as described.

Supported Devices

Mercury devices are added to Alta Access as follows:

• Mercury MP Series or LP Series Controllers: Added as expansion boards, connecting to the Access Control Core. Supported models include MP1501, MP1502, MP2500, LP1501, LP1502, LP2500.
• Mercury Series 3 Subpanels: Added as expansion boards, connecting to the MP Series or LP Series controller. Supported models include MR50-S3, MR52-S3B, MR16IN-S3, MR16OUT-S3.
• Third-Party Wiegand and OSDP Readers: Added as inputs. One expansion board port supports one Wiegand reader, or two OSDP readers.
• Door Contact Sensors: Added as contact sensors, reporting open/close status.
• REX Inputs: Added as REX inputs, reporting events.

Note: Alta mobile credentials can be issued to users in Alta Access and used to unlock entries via the Avigilon Alta Open mobile app.

System Requirements

• Ensure the SIO baud rate is set to 38400 or higher on the board and matches the baud rate in Alta Access for TLS support (required for Mercury Series 3 subpanels).
• Set the bit raw read on Wiegand or OSDP readers to 64-bit for accurate DESFire® card reads.
• Custom reader wiring is needed for BZR and LED support. Wiegand reader LED control requires wiring the Green LED output to the LED input and the Red LED output to the BZR input on a Mercury reader port. If LED wires are not wired correctly, a single beep and a Green LED blink will occur for card scans.

Installing and Configuring Controllers and Subpanels

Tip: A subpanel can be pre-configured before controller installation. Refer to Mercury device installation in Third-party documentation (page 33) for details on subpanel installation and RS-485 wiring.

1. Connect the controller to a power supply using a power cable (not included). Refer to vendor documentation for power selector details.
2. Connect the controller to the LAN using an Ethernet cable (not included).
3. Move the S1 (or SW1) DIP switch on the controller to the ON position (e.g., LP1502). This enables the web interface login.

Note: This step can be skipped for a previously provisioned controller.

4. Log in to a computer on the same network as the Alta Access network. The default IP address for controllers and panels is 192.168.0.251. Consult vendor documentation for specific device settings.

Important: Assigning unique IP addresses to controllers is recommended during initial setup.

5. Open a web browser and navigate to 192.168.0.251 to access the Configuration Manager. Alternatively, enter the unique IP address of a previously provisioned controller.
6. In the Username field, enter 'admin'. In the Password field, enter 'password'. Click the Login button.

Important: Creating user accounts in the Users menu is recommended during initial setup.

7. When logged in, select 'Network' from the left menu.
• Select 'Use Static IP configuration' to ensure the IP address remains constant. Configure the IP Address, Subnet Mask, and Default Gateway.
• Select 'DNS Settings' to configure LAN communication settings.

Note: The controller or subpanel must be on the same subnet and LAN segment as the ACU it connects to. Document the IP address for Alta Access setup.

8. Select 'Host Comm' from the left menu.
• Change the Communication Address to 2.
• Leave the Port Number at the default of 3001.
• Set Data Security to 'TLS Required'.

Note: The Network port and the 'TLS Enabled (Recommended)' checkbox in Alta Access must be configured when creating the ACU.

9. Ensure the 'Allow All' button is selected.
10. Select 'Apply Settings' to save changes.
11. Select 'Log Out' to exit the web interface.
12. Return the S1 (or SW1) DIP switch to the OFF position on the controller.

Assign Wiegand or OSDP Readers to Entries

1. Navigate to control.openpath.com/login and sign in. For EU access, use control.eu.openpath.com/login.
2. Go to 'Sites' > 'Entries', then create or edit an existing entry. Refer to the Avigilon Alta Access Administrator Guide for details on creating entries.
3. In the 'Controller' field, select the Access Control Core.
4. Assign the contact sensor, REX device, or reader to the entry:
   • For 'CONTACT SENSOR', select the Mercury controller or subpanel expansion board in 'Port' and other relevant settings.
   • For 'ENTRY/EXIT DEVICES', select the Mercury controller or subpanel expansion board in 'Port' and other relevant settings.
   • For 'REQUEST TO EXIT', select the Mercury controller or subpanel expansion board in 'Port' and other relevant settings.
   • For 'THIRD PARTY READER - WIEGAND', select the Wiegand reader in 'Port' and enter the OSDP address and Baud rate.
   • For 'THIRD PARTY READER - OSDP', select the OSDP reader in 'Port' and enter the OSDP address and Baud rate.
5. Click 'Save'.

Change Input and Output Types

Inputs and outputs (I/O) on the 4-Port and 8-Port Boards are labeled REX and CONTACT by default but can be used interchangeably or as generic inputs by configuring their type in Alta Access. They can also be configured as Wiegand inputs, which requires additional steps. For more information, see 'Wiring to Wiegand devices on Smart Hubs' on page 18.

Reader and input ports on Mercury boards can be configured in Alta Access to support third-party Wiegand or OSDP readers.

Change Input Types in Alta Access

1. Navigate to control.openpath.com/login and sign in. For EU access, use control.eu.openpath.com/login.
2. Go to 'Devices' > 'ACUs' and click the ACU to edit it.
3. Click the 'Ports' tab.
4. Scroll to the right and click the [Port] icon next to the input to be configured.

5. Select a different type from 'Input type'.
   • For an Avigilon board, click 'Input type' to change to a Contact sensor, Openpath reader, Request to exit device, Wiegand device, or Generic input.
   • For a Mercury board, click 'Input type' to select Contact sensor, Generic input, or Request to exit device.

Note: Inputs cannot be changed if they are already assigned to an entry.

6. For a Mercury board, in the reader expansion board section, scroll to the right and click the [Port] icon.
7. In 'Input type', select 'Third party reader - OSDP' or 'Third party reader - Wiegand'.

Note: After setting the reader port to OSDP, ensure the reader is also configured for OSDP communication. Refer to vendor documentation for reader configuration details.

7. Click 'Save'.

For the next step, see 'Provision the ACU using Alta Access on a laptop' on page 27.

Wiring to Wiegand Devices on Smart Hubs

Third-party Wiegand readers and panels can be wired to the ACU for integrations or Mobile Gateway mode. Auxiliary I/Os on the 4-Port and 8-Port Boards can be used for Wiegand devices, or any I/O pair including Contact and REX inputs.

Configure Wiegand Devices in Alta Access

1. Navigate to control.openpath.com/login and sign in. For EU access, use control.eu.openpath.com/login.
2. Go to 'Devices' > 'ACUs' and click the ACU to edit it.
   • Click the 'Ports' tab.
   • Click the [Port] icon next to the first input of the I/O pair configured with a Wiegand device (e.g., Contact2, AUX1).
   • Select from 'Input type' and click 'Save'. This labels the subsequent input as 'Wiegand device (extended)' and disables it from editing.

Note: Inputs cannot be changed if they are already assigned to an entry.

Once the Wiegand device is configured on the ACU, it can be assigned to an entry.

3. Go to 'Sites' > 'Entries', and create or edit an existing entry. In the Wiegand device settings, configure the following:
   • Port: The port for the Wiegand device to which this entry is wired.
   • Mode: The direction card credential data is sent.
     • Input: Receives data from the Wiegand reader.
     • Output (gateway): Sends credential data to a third-party control panel. Enable 'Gateway credential pass-through' if Alta Access should not authenticate credentials but instead send all data to the legacy panel.
   • Enter a 'Default gateway card number' so all credentials (including mobile) are sent to the legacy panel as a Wiegand ID.

Refer to the Avigilon Alta Access Administrator Guide for more information on creating entries.

Wiring to Legacy Panels and Mobile Gateway

Example: Avigilon boards

In this configuration, the legacy panel manages all locking hardware and entry mechanisms, while the Alta access control system enables the use of the Alta Open mobile app, Smart Reader, and Wave to Unlock functionality.

To add mobile credential features to a legacy access control system:

1. Install the Avigilon ACU between the Avigilon Smart Readers and the legacy panel connected to legacy software. Refer to 'Change input and output types' on page 1 for configuring the ACU as output to the legacy panel and 'Configure Wiegand devices in Alta Access' on the previous page.
2. If existing Wiegand readers use a proprietary card format, they can be wired to new Smart Readers. Otherwise, replace existing readers with Smart Readers.

Provisioning

Provisioning the ACU involves registering it in Alta Access and running the latest firmware. Re-provisioning is necessary after a hard reset (see 'Resetting ACUs' on page 31).

Note: If provisioning ACUs for a customer account, the customer organization must be created first.

Prerequisites

• Connect the ACU to a power supply using the included power cable.
• Meet all Network requirements on page 7.
• Connect the ACU to the internet using the Ethernet cable.

Note: Expansion boards must be on the same subnet and LAN as the ACU they connect to.

• Install the Alta Access mobile app.

• If using a laptop instead of the app, the laptop must be on the same network as the ACU. If using a VLAN, ensure the laptop is on the same VLAN.
• For laptops running Microsoft™ Windows or Linux®, download the iTunes app, which includes Bonjour software for the provisioning process. Alternatively, download iTunes and extract Bonjour MSI separately.

App Store® and the Apple logo® are trademarks of Apple Inc. Google Play and the Google Play logo are trademarks of Google LLC. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

Add ACUs using Alta Access

Tip: ACUs can be added using the Alta Access mobile app.

Refer to the Alta Access article for more information.

Add Multiple ACUs using Quick Start Option

Note: Bulk ACU creation is not supported for Access Control Cores connected to Mercury expansion boards. These ACUs must be created individually.

1. Navigate to control.openpath.com/login and sign in. For EU access, use control.eu.openpath.com/login.
2. Go to 'Administration' > 'Quick start'.
3. Enter a Site name and other relevant site information. Select the preferred language for site-wide emails in 'Site language'. Click 'Next'.
4. Enter the number of controllers at your site:
   • Enter names for the controllers.
   • In 'Controller type', select the type used:
     • 'First generation - Red Board (OP-AS-01)' for first-generation Smart Hubs.
     • 'Core series ACU' for Core Series Smart Hubs.
   • If your ACU connects to an expansion board, add the appropriate types under 'EXPANSION BOARDS':
     • Openpath 4-Port Expansion
     • Openpath 8-Port Expansion
     • Openpath 16-Port Elevator

Tip: Avigilon (formerly Openpath) boards are most common with the Core Series Smart Hub.

5. Enter the number of readers connected to the controllers, their names, and click 'Next'.
6. Review your site details and click 'Confirm & submit'. Setup may take a few minutes.

Add One ACU

1. Go to 'Devices' > 'ACUs'.
2. To add a new ACU, click the [+] button in the upper-right corner.
3. Enter a unique name for the ACU.
4. In 'Controller type', select the type used:
   • 'First generation - Red Board (OP-AS-01)' for first-generation Smart Hubs.
   • 'Core series ACU' for Core Series Smart Hubs.
5. If your ACU also connects to an expansion board, add the appropriate types under 'EXPANSION BOARDS':
   • Openpath 4-Port Expansion
   • Openpath 8-Port Expansion
   • Openpath 16-Port Elevator
   • Mercury LP1501
   • Mercury LP1501 (With Downstream)
   • Mercury LP1502
   • Mercury LP2500
   • Mercury MP1501
   • Mercury MP1501 (With Downstream)
   • Mercury MP1502
   • Mercury MP2500

Note: For Mercury controller boards, enter their unique IP address and Network port (default 3001). 'TLS Enabled (Recommended)' is enabled by default. If using Mercury MP1501 (With Downstream) or LP1501 (With Downstream), ensure the baud rate matches the physical board's baud rate (default 38400).

6. Click 'Add board'. The Mercury board is disabled by default.
   • When ready to communicate with the Mercury board, ensure it is disconnected from any previous access control system.
   • In the 'ENABLE' column, select 'Enabled' for the board.

Caution: The previous configuration on the legacy access control system will be overwritten.

7. If you have additional subpanels, click 'Add board' again and add the appropriate types:
   • Mercury MR16IN-S3
   • Mercury MR16OUT-S3
   • Mercury MR50-S3
   • Mercury MR52-S3

Note: For Mercury readers and panels, enter the Port and RS-485 address (supported range 0-31).

8. Optional: To connect your network to the Cloud using a static IP address and port on an allowlist, enable the 'Enable Static Cloud IP' toggle. Default port is 443.

Note: An Enterprise plan is required to use Static Cloud IP.

• Go to the App marketplace and ensure the 'Static Cloud IP' app is installed.
• After enabling the toggle in Alta Access, open the Alta Access mobile app and select 'Provision with Static Cloud IP' to provision the devices.
9. Click 'Save'.

Note: If saving a new Mercury expansion board, Access Control Core firmware will download and install automatically, taking up to 30 minutes depending on network speed.

Provisioning the ACU

Provision the ACU using Alta Access Mobile App (Recommended)

Note: Mobile app provisioning is not applicable to the Access Control Core when connected to Mercury boards and subpanels.

1. Log in to the Alta Access mobile app using your mobile credentials.
2. Locate your organization by list or search, then tap the organization name.
3. Press the Admin button on the Access Control Core.
4. In the Alta Access mobile app, tap the last four digits of the ACU's serial number.
5. Tap 'Test Internet Connection' and wait for a green 'YES' before proceeding.

Note: This verifies the ACU can ping https://api.openpath.com/health.

6. Tap 'Provision Device'.
7. Tap the ACU Name you want to provision (created in Alta Access) and tap 'Yes' to proceed.
8. The app will send notifications for provisioning status changes: 'Unprovisioned' to 'Provisioning in progress', then to 'Provisioning complete'.

Note: The ACU will disconnect from the Alta Access mobile app 5 minutes after the Admin button is first pressed.

Provision the ACU using Alta Access on a Laptop

1. Navigate to control.openpath.com/login and sign in. For EU access, use control.eu.openpath.com/login.

Note: The laptop must be connected to the same network as the ACU.

2. Go to 'Devices' > 'ACUs'.
3. Locate your ACU on the list.
4. If your ACU is not listed, create a new one:
   • Click the [+] button in the upper-right corner.
   • Enter a unique name for the ACU.
   • In 'Controller type', select the controller and any appropriate expansion boards.
   • Click 'Save'.

Note: If saving a new Mercury expansion board, Access Control Core firmware will download and install automatically, taking up to 30 minutes depending on network speed.

5. On the ACU, press the Admin button.
6. In Alta Access, click the 'Register' button next to your ACU's name.
   • Click 'Yes' to proceed. A new window will open.
   • Click 'Provision'.
   • If a 'This Site Cannot be Reached' error occurs, ping the ACU using the command line:
     • On Windows: Run ping oppi.local
     • On Mac or Linux: Run ping -c4 oppi.local
     • If no response, check your network requirements (page 7).
   • You should see the ACU's IP address (IPv4 or IPv6). Copy it and return to the error page. In the URL, delete everything before ':8080'. Paste the IP address before ':8080'. For IPv6 addresses, remove the last two digits and the percentage sign, and enclose the address in square brackets. Example: 192.0.2.0:8080 (IPv4) or [a123::b456:5a18:eb8f:7fd6]:8080 (Correct IPv6).
   • Press 'Enter' and then click the 'Provision' button.
   • If the 'Provision' button does not appear, contact Avigilon Alta Support at (844) 673-6728 Ext 2 or support@openpath.com.

Test Internet Connection using Alta Access Mobile App

In the Alta Access mobile app, tap 'Test Internet Connection' to verify the ACU can ping api.openpath.com/health.

Configure Network Settings using Alta Access Mobile App

Network settings for the ACU can be configured via the Alta Access mobile app. Ethernet connections can use DHCP (default) or a static IP address.

Note: DHCP reservation and static IP addresses are recommended for allowlisting or safelisting the same address during ACU reboots.

Change Network Settings

1. Connect to the Access Control Core device by pressing the Admin button again if needed.
2. Tap 'Network Settings'.
3. Select 'Configure network manually'.
4. Configure network settings as needed, such as setting a static IP address or a preferred DNS server.
5. Tap 'Save' in the top-right corner.

Status LED Indicator

The Status LED on the Access Control Core indicates the following:

Maintenance and Troubleshooting

Warning:

• Disconnect power before servicing.
• Do not plug into an outlet controlled by an on/off switch.
• Powering the supply with 230V requires jumper modification. Consult the power supply datasheet.

Resetting ACUs

Soft Reset

To soft reset the ACU, disconnect power, wait 10 seconds, and then reconnect power.

Hard Reset

Warning: Only perform a hard reset if absolutely necessary and instructed by Avigilon Alta Support. This action clears all data from the ACU and requires reprovisioning.

1. Disconnect power from the ACU.
2. Press the Admin button (labeled 'b' in the diagram).
3. While holding the Admin button, reconnect power. Continue holding for another 15 seconds until the status LED (labeled 'a') turns yellow. Release the button.
4. Wait 15 minutes or until the status LED turns blue before provisioning. See 'Provisioning' on page 21.

Selecting a Backup Battery

A backup battery is recommended for power outages. 12V supplies need one 12V battery; 24V supplies need two 12V batteries in series. Battery size depends on your setup and desired runtime.

Table 1: Example Power Requirements for Core Series Smart Hubs (24V)

A Core Series Smart Hub with four Avigilon readers and locking hardware using a 24V supply draws approximately 2 Amps. For 3 hours of runtime with all entries engaged, you need 6AH (2A x 3 hours), requiring two 12V 6AH sealed lead acid (SLA) or gel cell batteries wired in series.

Mercury Device Installation

Note: For Mercury subpanels and third-party Wiegand/OSDP readers, calculate the power draw to determine the appropriate battery size.

For More Information

Technical Support

For additional support documentation, visit support.avigilon.com.

Product Documentation

For additional product documentation, see the Alta Access (Cloud Solutions) product suite on avigilon.com.

Third-Party Documentation

Mercury Hardware:

• MP1501 Installation Manual, MP1502 Installation Manual, MP2500 Installation Manual
• LP1501 Installation Manual, LP1502 Installation Manual, LP2500 Installation Manual
• MR50-S3 Installation Manual, MR52-S3B Installation Manual, MR16IN-S3 Installation Manual, MR16-OUT-S3 Installation Manual

Avigilon Warranty

Warranty terms for Avigilon products are available at avigilon.com/support/warranty.

Regulatory Notice

All national and local electrical codes apply.

FCC Compliance

This device complies with part 15 of the FCC Rules. Operation is subject to two conditions: (1) it must not cause harmful interference, and (2) it must accept any interference received, including interference that may cause undesired operation. To comply with FCC RF exposure requirements, maintain a separation distance of at least 20 cm between the antenna of Openpath Smart Reader(s) and persons during operation.

NOTE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and may cause harmful interference to radio communications if not installed and used per the manual. Operation in a residential area may cause harmful interference, requiring the user to correct it at their own expense.

IEC 62368-1

• This equipment is intended only for use in a restricted access area.
• Securely fasten the equipment according to LifeSafety Power mounting instructions.
• PROTECTIVE EARTHING: For safety, the Smart Hub must be plugged into a grounded 3-prong outlet, wired with a minimum of 16 gauge wire to ground.

RF Radiation Hazard Warning

To ensure compliance with FCC and Industry Canada RF exposure requirements, Smart Hubs must be installed at least 20 cm from all persons. Using uncertified higher gain antennas is not allowed. The device shall not be co-located with another transmitter.

French translation: Installez l'appareil en veillant à conserver une distance d'au moins 20 cm entre les éléments rayonnants et les personnes. Cet avertissement de sécurité est conforme aux limites d'exposition définies par la norme CNR-102 at relative aux fréquences radio.

Industry Canada Notice and Marking

Under Industry Canada regulations, this radio transmitter may only operate using an antenna of a type and maximum (or lesser) gain approved by Industry Canada. To reduce potential radio interference, the antenna type and gain should be chosen such that the equivalent isotropically radiated power (e.i.r.p.) is not more than necessary for successful communication.

French translation: Conformément à la réglementation d'Industrie Canada, le présent émetteur radio peut fonctionner avec une antenne d'un type et d'un gain maximal (ou inférieur) approuvé pour l'émetteur par Industrie Canada. Dans le but de réduire les risques de brouillage radioélectrique à l'intention des autres utilisateurs, il faut choisir le type d'antenne et son gain de sorte que la puissance isotrope rayonnée équivalente (p.i.r.e.) ne dépasse pas l'intensité nécessaire à l'établissement d'une communication satisfaisante.

This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation.

French translation: Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes : (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en compromettre le fonctionnement.

OP-CR-ACC: Contains FCC ID: 2ABCB-RPI4B. Contains IC ID: 20953-RPI4B.

Electrical Specification

Electrical