MikroTik RB924i-2nD-BT5&BG77 User manual

1.
2.
RB924i-2nD-BT5&BG77
KNOT RB924i-2nD-BT5&BG77
Connecting
Make sure your Internet service provider is allowing hardware change and will issue an automatic IP address;
Connect your ISP cable to the first Ethernet port;
Connect the device to the power source;
Open network connections on your computer and search for MikroTik wireless network - connect to it;
The configuration has to be done through the wireless network using a web browser or mobile app. Alternatively, you can use a WinBox
configuration tool ;https://mt.lv/winbox
Open in your web browser to start configuration, user name: admin and there is no password by default;https://192.168.88.1
Click the Check for updates button and update your RouterOS software to the latest version, must have an active Internet connection;
In the Quick Set, WISP AP menu choose your country and apply country regulation settings;
Set the antenna gain, depending on the antenna used;
Set up your wireless network password;
Set up your router password.
Mounting
The device can be mounted using provided DIN rail mount set. Designed to fit standard 35 mm x 7.5 mm DIN rails. Attach it with two provided
screws to the device and attach the device to the DIN rail. The DIN rail is not provided in the package.
Alternatively, it is possible to attach the device to a wall, using the provided screw holes on the back of the unit. The device should be mounted in
a way that the cable openings are pointing downward as shown in the picture.
Powering
Direct-input power jack (5.5 mm outside and 2 mm inside, female, pin positive plug) accepts 12-57 V DC.
microUSB port accepts 5 V powering.
Warning! This equipment should be installed and operated with a minimum distance of 20 cm between the device and your body. The operation
of this equipment in the residential environment could cause radio interference.
Mounting and configuration of this device should be done by a qualified person.

1.
2.
3.
Ethernet port accepts 802.3af/at Power over Ethernet 12-57 V DC.
The power consumption under maximum load with attachments can reach 18 W.
Connecting to a PoE Adapter:
Connect the Ethernet cable from the device to the PoE+DATA port of the PoE adapter.
Connect an Ethernet cable from your local network (LAN) to the PoE adapter.
Connect the power cord to the adapter, and then plug the power cord into a power outlet.
Extension slots and ports
2.4 GHz, 802.11b/g/n, antenna gain 1.5 dBi.
Built-in GPS module (GPS, GLONASS, BeiDou, Galileo).
Two 10/100 Ethernet ports, supporting automatic cross/straight cable correction (Auto MDI/X). Either straight or crossover cable can be used for
connecting to other network devices. The Ethernet port accepts 12-57 V DC power from an PoE injector.802.3af/at
One microUSB 2.0 port for powering only.
One nano SIM slot.
Bluetooth version 5.2, antenna gain 2 dBi.
GPS
NB/CAT-M
Attach your antennas to the SMA connectors:
BG77 supports NB and GNSS, cannot be used together. https://help.mikrotik.com/docs/display/ROS/IoT

Buttons and jumpers
Reset button
Hold this button during boot time until the LED light starts flashing, release the button to reset RouterOS configuration (total 5 seconds).
Keep holding for 5 more seconds, LED turns solid, release now to turn on CAP mode. The device will now look for a CAPsMAN server (total 10
seconds).
Or keep holding the button for 5 more seconds until LED turns off, then release it to make the RouterBOARD look for Netinstall servers (total 15
seconds).
Regardless of the above option used, the system will load the backup RouterBOOT loader if the button is pressed before power is applied to the device.
Useful for RouterBOOT debugging and recovery.
GPIO pinout
GPIO pins are located on the board under the case as shown in the picture:
ADC input/analog input (pin2 or pin3):
External antennas must be connected to use the Narrow Band modem and GPS. Not provided with the package.

:note Analog input voltage is 0-60 V. Theoretical resolution is 4 mV (14bit ADC). Analog input impedance is approximately 72K Ohm.
Connected relays (pin4 or pin6):
Tamper switch (pin5):

:note Digital input voltage is 0-2.5 V max. To receive a logical "0" on the pin, the voltage should be between 0-0.3 V. To receive a logical "1" on the pin,
the voltage should be between 0.7-2.5 V.
Accessories
The package includes the following accessories that come with the device:
ADAPT1_ EU/US Switching Power Supply 24V, 1.2A, 28.8W, 86.8%, VI.
CAB1_ USB A Female to Micro B cable.
SET1_ K-47 wall mount set, two screws, and dowels.
SET2_ K-74 Din rail mount set.
Modbus connector, A+, B-.
Operating system support
The device supports RouterOS software version 6.48.1. The specific factory-installed version number is indicated in the RouterOS menu /system resource.
Other operating systems have not been tested.
Configuration
RouterOS includes many configuration options in addition to what is described in this document. We suggest starting here to get yourself accustomed to
the possibilities: . In case an IP connection is not available, the Winbox tool ( ) can be used to connect to the MAC https://mt.lv/help https://mt.lv/winbox
address of the device from the LAN side (all access is blocked from the internet port by default).
For recovery purposes, it is possible to boot the device from the network, see section .Buttons and jumpers
: note make sure that package is installed beforehand.iot
Overview
Protocols such as MQTT and HTTP are widely used to push data within networks. M2M topologies can use different technologies, such as Wi-Fi or M2M
Bluetooth to send data within networks.
KNOT is a new addition to one of our IoT solutions. KNOT acts as an IoT gateway ( ) and uses Bluetooth to that uses Narrow Band and CAT-M technology
scan broadcasted information. With the Bluetooth interface, you can use the KNOT for asset tracking and telemetry based on Bluetooth advertisement
packets. KNOT supports any BLE tag that sends advertisement data. iBeacon, Eddystone, or any other format. It has powerful filters for forwarding only
After the gateway processes the data that it receives, it can use an ISP connection to publish the data further to any relevant packets and ignoring others.
subscriber or server that is configured accordingly.
All you need to do is to configure a script. The script can filter broadcasted information and push it to the internet.
This article explains how to configure KNOT to publish data using MQTT or http protocols.

Reports
Navigate to IoT>Bluetooth.
You can find all broadcasting devices in the “Advertising reports” tab.
In this menu, you can set up a filter by pressing the “Filter” icon. For example, knowing the MAC address of the device, you can set up a filter to only show
specific reports.
You can add more filter options using “+” icon.
You can remove filter options using "-" icon.
MQTT Broker configuration
Navigate to IoT>MQTT.
You can add a new broker via “+” button.
External antennas must be connected to use the Narrow Band modem and GPS. Not provided with the package.

Properties Description
Name Identification. Brokers name.
Address IP address or FQDN name of the MQTT broker without ssl:// or tcp:// prefix.
Port Network port of the broker. Usually, 1883 or 8883 (for SSL).
SSL Enable/Disable Secure Socket Layer. If the server uses a self-signed certificate or certificate signed by a non-trusted CA, you have to
upload the server's certificates <crt> file to RouterOS. Upload .cer file to the "Files" menu and import the file to certificates in the
System>Certificates tab.
Username Username for MQTT broker.
Password Password for MQTT broker.
Client Id A unique ID used for the connection. The broker uses this ID to identify the client.
Certificate Chose a certificate if required for the two-way authentication.
:note You do not have to specify servers certificate (.cer file) in the MQTT broker settings. The "Certificate" field is used for the client's certificate.
:note "Name", "Address", and "Port" field configuration is required. Other parameters can be optional or required - depends on how the server/broker is set
up.
Publish
After you created a broker, click the "Publish" button. This box allows you to choose a broker and specify message information.
Select an already configured broker in the "Broker" field (scroll-down menu).

You can then specify the "Topic" (a string used by a broker to filter messages), "Message" (the message itself), "QoS" (indicates Quality of Service level for
the message), and "Retain" (whether to retain the message or discard it) parameters.
:note "Broker" and "Topic" field configuration is required. "Message", "QoS", and "Retain" can be optional or required - depends on how the server/broker is
set up.
MQTT with script scenario
MQTT broker can be configured with .scripts
Create a new script, use the template as a reference, change the parameters accordingly and run the script.
Every line that begins with a symbol " " is instructional and it describes the parameter that is going to be configured below the line. Change the parameters #
within quotation marks "" that would apply to your specific case.
Script example:
# Required packages: iot
################################ Configuration ################################
# Name of an existing MQTT broker that should be used for publishing
:local broker "Demo Device"
# MQTT topic where the message should be published
:local topic "v1/devices/me/telemetry"
# Interface whose MAC should be used as 'Locator ID'
:local locatorIface "ether1"
# POSIX regex for filtering advertisement Bluetooth addresses. E.g. "^BC:33:AC"
# would only include addresses which start with those 3 octets.
# To disable this filter, set it to ""
:local addressRegex ""
# POSIX regex for filtering Bluetooth advertisements based on their data. Same
# usage as with 'addressRegex'.
:local advertisingDataRegex ""
# Signal strength filter. E.g. -40 would only include Bluetooth advertisements
# whose signal strength is stronger than -40dBm.
# To disable this filter, set it to ""
:local rssiThreshold ""
#################################### System ###################################
:put ("[*] Gathering system info...")
:local ifaceMac [/interface get [/interface find name=$locatorIface] mac-address]
:local cpuLoad [/system resource get cpu-load]
:local freeMemory [/system resource get free-memory]
:local usedMemory ([/system resource get total-memory] - $freeMemory)
:local rosVersion [/system package get value-name=version \
  [/system package find where name ~ "^routeros"]]
:local model [/system routerboard get value-name=model]
:local serialNumber [/system routerboard get value-name=serial-number]
# Health is a bit iffy since '/system health' does not have 'find' in ROS6
:local health [/system health print as-value]
:local supplyVoltage 0
:local boardTemp 0
:foreach entry in=$health do={
  :if ($entry->"name" = "voltage") do={:set $supplyVoltage ($entry->"value")}
  :if ($entry->"name" = "board-temperature1") do={:set $boardTemp ($entry->"value")}
}

################################## Bluetooth ##################################
:put ("[*] Gathering Bluetooth info...")
:global btOldestAdvertisementTimestamp
:if ([:typeof $btOldestAdvertisementTimestamp] = "nothing") do={
  # First time this script has been run since booting, need to initialize
  # persistent variables
  :set $btOldestAdvertisementTimestamp 0
}
:local btProcessingStart [/system clock get time]
:local advertisements [/iot bluetooth scanners advertisements print detail \
  as-value where \
    epoch > $btOldestAdvertisementTimestamp and \
    address ~ $addressRegex and \
    data ~ $advertisingDataRegex and \
    rssi > $rssiThreshold
]
:local advJson ""
:local advCount 0
:local advSeparator ""
:local lastAdvTimestamp 0
# Remove semicolons from MAC/Bluetooth addresses
:local minimizeMac do={
  :local minimized
  :local lastIdx ([:len $address] - 1)
  :for idx from=0 to=$lastIdx step=1 do={
    :local char [:pick $address $idx]
    :if ($char != ":") do={
      :set $minimized "$minimized$char"
    }
  }
  :return $minimized
}
:foreach adv in=$advertisements do={
  :local address ($adv->"address")
  :local ts ($adv->"epoch")
  :local rssi ($adv->"rssi")
  :local ad ($adv->"data")
  :local obj "\
    {\
      \"id\":\"$[$minimizeMac address=$address]\",\
      \"ts\":$ts,\
      \"rssi\":$rssi,\
      \"ed\":{\
        \"ad\":\"$ad\"\
      }\
    }"
  :set $advCount ($advCount + 1)
  :set $lastAdvTimestamp $ts
  # Ensure that the last object is not terminated by a comma
  :set $advJson "$advJson$advSeparator$obj"
  :if ($advSeparator = "") do={
    :set $advSeparator ","
  }
}
:if ($advCount > 0) do={
  :set $btOldestAdvertisementTimestamp $lastAdvTimestamp
}
:put ("[*] Found $advCount new advertisements \
  (processing time: $[([/system clock get time] - $btProcessingStart)])")

#################################### MQTT #####################################
:local message \
  "{\
    \"clientId\":\"$[/iot mqtt brokers get value-name=client-id \
      [/iot mqtt brokers find name=$broker]]\",\
    \"t\":0,\
    \"v\":1,\
    \"OldestAdvertisementTimestamp\":$btOldestAdvertisementTimestamp,\
    \"locs\":[{\
      \"id\":\"$[$minimizeMac address=$ifaceMac]\",\
      \"tags\":[$advJson],\
      \"ed\":{\
        \"model\":\"$model\",\
        \"sn\":\"$serialNumber\",\
        \"ros\":\"$rosVersion\",\
        \"cpu\":$cpuLoad,\
        \"umem\":$usedMemory,\
        \"fmem\":$freeMemory,\
        \"psu\":$supplyVoltage,\
        \"temp\":$boardTemp\
      }\
    }]\
  }"
:log info "$message";
:put ("[*] Total message size: $[:len $message] bytes")
:put ("[*] Sending message to MQTT broker...")
/iot mqtt publish broker=$broker topic=$topic message=$message
:put ("[*] Done")
To run this script, the Broker should be pre-configured:
For example, only requires settings that are shown in the screenshot above. When you successfully configure the broker, the only thing that thingsboard
needs to be changed in the script is:
:local broker "Demo Device"
line, where you should specify the broker's name within the quotation marks "".
Another line that should be taken into account is:
:local topic "v1/devices/me/telemetry"
, where you should specify the topic.

The rest of the script configuration depends on the overall requirements. The script explains which exact parameters are configured to be published.
Navigate to System>Scripts and add a new script there (name it, for example, script1).
To run the script, you can use the command line:
/system script run script1
HTTP fetch with script scenario
Another way to publish data is to use HTTP (instead of MQTT). This can be achieved using .fetch tool
The same principles apply:
Create a new script, use the template as a reference, change the parameters accordingly and run the script.
Every line that begins with a symbol " " is instructional and it describes the parameter that is going to be configured below the line. Change the parameters #
within quotation marks "" that would apply to your specific case.
Script example:
# Required packages: iot
################################ Configuration ################################
# Interface whose MAC should be used as 'Locator ID'
:local locatorIface "ether1"
# POSIX regex for filtering advertisement Bluetooth addresses. E.g. "^BC:33:AC"
# would only include addresses which start with those 3 octets.
# To disable this filter, set it to ""
:local addressRegex ""
# POSIX regex for filtering Bluetooth advertisements based on their data. Same
# usage as with 'addressRegex'.
:local advertisingDataRegex ""
# Signal strength filter. E.g. -40 would only include Bluetooth advertisements
# whose signal strength is stronger than -40dBm.
# To disable this filter, set it to ""
:local rssiThreshold ""
#################################### System ###################################
:put ("[*] Gathering system info...")
:local ifaceMac [/interface get [/interface find name=$locatorIface] mac-address]
:local cpuLoad [/system resource get cpu-load]
:local freeMemory [/system resource get free-memory]
:local usedMemory ([/system resource get total-memory] - $freeMemory)
:local rosVersion [/system package get value-name=version \
  [/system package find where name ~ "^routeros"]]
:local model [/system routerboard get value-name=model]
:local serialNumber [/system routerboard get value-name=serial-number]
# Health is a bit iffy since '/system health' does not have 'find' in ROS6
:local health [/system health print as-value]
:local supplyVoltage 0
:local boardTemp 0
:foreach entry in=$health do={
  :if ($entry->"name" = "voltage") do={:set $supplyVoltage ($entry->"value")}
  :if ($entry->"name" = "board-temperature1") do={:set $boardTemp ($entry->"value")}
}

################################## Bluetooth ##################################
:put ("[*] Gathering Bluetooth info...")
:global btOldestAdvertisementTimestamp
:if ([:typeof $btOldestAdvertisementTimestamp] = "nothing") do={
  # First time this script has been run since booting, need to initialize
  # persistent variables
  :set $btOldestAdvertisementTimestamp 0
}
:local btProcessingStart [/system clock get time]
:local advertisements [/iot bluetooth scanners advertisements print detail \
  as-value where \
    epoch > $btOldestAdvertisementTimestamp and \
    address ~ $addressRegex and \
    data ~ $advertisingDataRegex and \
    rssi > $rssiThreshold
]
:local advJson ""
:local advCount 0
:local advSeparator ""
:local lastAdvTimestamp 0
# Remove semicolons from MAC/Bluetooth addresses
:local minimizeMac do={
  :local minimized
  :local lastIdx ([:len $address] - 1)
  :for idx from=0 to=$lastIdx step=1 do={
    :local char [:pick $address $idx]
    :if ($char != ":") do={
      :set $minimized "$minimized$char"
    }
  }
  :return $minimized
}
:foreach adv in=$advertisements do={
  :local address ($adv->"address")
  :local ts ($adv->"epoch")
  :local rssi ($adv->"rssi")
  :local ad ($adv->"data")
  :local obj "\
    {\
      \"id\":\"$[$minimizeMac address=$address]\",\
      \"ts\":$ts,\
      \"rssi\":$rssi,\
      \"ed\":{\
        \"ad\":\"$ad\"\
      }\
    }"
  :set $advCount ($advCount + 1)
  :set $lastAdvTimestamp $ts
  # Ensure that the last object is not terminated by a comma
  :set $advJson "$advJson$advSeparator$obj"
  :if ($advSeparator = "") do={
    :set $advSeparator ","
  }
}
:if ($advCount > 0) do={
  :set $btOldestAdvertisementTimestamp $lastAdvTimestamp
}
:put ("[*] Found $advCount new advertisements \
  (processing time: $[([/system clock get time] - $btProcessingStart)])")

1.
2.
3.
4.
5.
6.
#################################### MQTT #####################################
:local message \
  "{\
    \"t\":0,\
    \"v\":1,\
    \"OldestAdvertisementTimestamp\":$btOldestAdvertisementTimestamp,\
    \"locs\":[{\
      \"id\":\"$[$minimizeMac address=$ifaceMac]\",\
      \"tags\":[$advJson],\
      \"ed\":{\
        \"model\":\"$model\",\
        \"sn\":\"$serialNumber\",\
        \"ros\":\"$rosVersion\",\
        \"cpu\":$cpuLoad,\
        \"umem\":$usedMemory,\
        \"fmem\":$freeMemory,\
        \"psu\":$supplyVoltage,\
        \"temp\":$boardTemp\
      }\
    }]\
  }"
:log info "$message";
:put ("[*] Total message size: $[:len $message] bytes")
/tool fetch http-method=post http-header-field="Content-Type:application/json" http-data=$message url="https://demo.thingsboard.io
"/api/v1/Q99YlBqv59NdzOel6tyP/telemetry
:put ("[*] Done")
Change the URL accordingly (depends on the server configuration).
/tool fetch http-method=post http-header-field="Content-Type:application/json" http-data=$message url="https://demo.thingsboard.io
"/api/v1/Q99YlBqv59NdzOel6tyP/telemetry
Navigate to System>Scripts and add a new script there (name it, for example, script1).
To run the script, you can use the command line:
/system script run script1
MikroTik mobile app
Use the MikroTik smartphone app to configure your router in the field, or to apply the most basic initial settings for your MikroTik home access point.
Scan QR code and choose your preferred OS.
Install and open the application.
By default, the IP address and user name will be already entered.
Click Connect to establish a connection to your device through a wireless network.
Choose Quick setup and the application will guide you through all basic configuration settings in a couple of easy steps.
An advanced menu is available to fully configure all necessary settings.
Federal Communication Commission Interference Statement
Model FCC ID Contains FCC ID
RB924i-2nD-BT5&BG77 TV7924BT5BG77 XMR201912BG77

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are
designed to provide reasonable protection against harmful interference in a residential installation.
This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause
harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment
does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to
try to correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna.
Increase the separation between the equipment and receiver.
Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
FCC Caution: Any changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate this
equipment.
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful
interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
Note: This unit was tested with shielded cables on the peripheral devices. Shielded cables must be used with the unit to ensure compliance.
Innovation, Science and Economic Development Canada
Model IC Contains
IC
RB924i-2nD-BT5&BG77 7442A-924BT5BG77 10224A-
201912BG
77
This device contains license-exempt transmitter(s)/receiver(s) that comply with Innovation, Science, and Economic Development Canada’s license-exempt
RSS(s). Operation is subject to the following two conditions: (1) This device may not cause interference. (2) This device must accept any interference,
including interference that may cause undesired operation of the device.
L’émetteur/récepteur exempt de licence contenu dans le présent appareil est conforme aux CNR d’Innovation, Sciences et Développement économique
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; 2) L’appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d’en compromettre le fonctionnement.
This Class B digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe [B] est conforme à la norme NMB-003 du Canada.
CAN ICES-003 (B) / NMB-003 (B)
CE Declaration of Conformity
BG С настоящото Mikrotīkls SIA декларира, че този тип радиосъоръжение RB924i-2nD-BT5&BG77 е в съответствие с Директива 2014/53/ЕС.
Цялостният текст на ЕС декларацията за съответствие може да се намери на следния интернет адрес: https://mikrotik.com/products
CS Tímto Mikrotīkls SIA prohlašuje, že typ rádiového zařízení RB924i-2nD-BT5&BG77 je v souladu se směrnicí 2014/53/EU. Úplné znění EU
prohlášení o shodě je k dispozici na této internetové adrese: https://mikrotik.com/products
DA Hermed erklærer Mikrotīkls SIA, at radioudstyrstypen RB924i-2nD-BT5&BG77 er i overensstemmelse med direktiv 2014/53/EU. EU-
overensstemmelseserklæringens fulde tekst kan findes på følgende internetadresse: https://mikrotik.com/products
DE Hiermit erklärt Mikrotīkls SIA, dass der Funkanlagentyp RB924i-2nD-BT5&BG77 der Richtlinie 2014/53/EU entspricht. Der vollständige Text der EU-
Konformitätserklärung ist unter der folgenden Internetadresse verfügbar: https://mikrotik.com/products
EL Με την παρούσα ο/η Mikrotīkls SIA, δηλώνει ότι ο ραδιοεξοπλισμός RB924i-2nD-BT5&BG77 πληροί την οδηγία 2014/53/ΕΕ. Το πλήρες κείμενο της
δήλωσης συμμόρφωσης ΕΕ διατίθεται στην ακόλουθη ιστοσελίδα στο διαδίκτυο: https://mikrotik.com/products
EN Hereby, Mikrotīkls SIA declares that the radio equipment type RB924i-2nD-BT5&BG77 is in compliance with Directive 2014/53/EU. The full text of
the EU declaration of conformity is available at the following internet address: https://mikrotik.com/products

ES Por la presente, Mikrotīkls SIA declara que el tipo de equipo radioeléctrico RB924i-2nD-BT5&BG77 es conforme con la Directiva 2014/53/UE. El
texto completo de la declaración UE de conformidad está disponible en la dirección Internet siguiente: https://mikrotik.com/products
ET Käesolevaga deklareerib Mikrotīkls SIA, et käesolev raadioseadme tüüp RB924i-2nD-BT5&BG77 vastab direktiivi 2014/53/EL nõuetele. ELi
vastavusdeklaratsiooni täielik tekst on kättesaadav järgmisel internetiaadressil: https://mikrotik.com/products
FI Mikrotīkls SIA vakuuttaa, että radiolaitetyyppi RB924i-2nD-BT5&BG77 on direktiivin 2014/53/EU mukainen. EU-vaatimustenmukaisuusvakuutuksen
täysimittainen teksti on saatavilla seuraavassa internetosoitteessa: https://mikrotik.com/products
FR Le soussigné, Mikrotīkls SIA, déclare que l'équipement radioélectrique du type RB924i-2nD-BT5&BG77 est conforme à la directive 2014/53/UE. Le
texte complet de la déclaration UE de conformité est disponible à l'adresse internet suivante: https://mikrotik.com/products
HR Mikrotīkls SIA ovime izjavljuje da je radijska oprema tipa RB924i-2nD-BT5&BG77 u skladu s Direktivom 2014/53/EU. Cjeloviti tekst EU izjave o
sukladnosti dostupan je na sljedećoj internetskoj adresi: https://mikrotik.com/products
HU Mikrotīkls SIA igazolja, hogy a RB924i-2nD-BT5&BG77 típusú rádióberendezés megfelel a 2014/53/EU irányelvnek. Az EU-megfelelőségi
nyilatkozat teljes szövege elérhető a következő internetes címen: https://mikrotik.com/products
IT Il fabbricante, Mikrotīkls SIA, dichiara che il tipo di apparecchiatura radio RB924i-2nD-BT5&BG77 è conforme alla direttiva 2014/53/UE. Il testo
completo della dichiarazione di conformità UE è disponibile al seguente indirizzo Internet: https://mikrotik.com/products
IS Hér með lýsir Mikrotīkls SIA því yfir að RB924i-2nD-BT5&BG77 er í samræmi við grunnkröfur og aðrar kröfur, sem gerðar eru í tilskipun 2014/53/EU.
Fullur texti ESB samræmisyfirlýsingar er að finna á eftirfarandi veffangi: https://mikrotik.com/products
LT Aš, Mikrotīkls SIA, patvirtinu, kad radijo įrenginių tipas RB924i-2nD-BT5&BG77 atitinka Direktyvą 2014/53/ES. Visas ES atitikties deklaracijos
tekstas prieinamas šiuo interneto adresu: https://mikrotik.com/products
LV Ar šo Mikrotīkls SIA deklarē, ka radioiekārta RB924i-2nD-BT5&BG77 atbilst Direktīvai 2014/53/ES. Pilns ES atbilstības deklarācijas teksts ir
pieejams šādā interneta vietnē: https://mikrotik.com/products
MT B'dan, Mikrotīkls SIA, niddikjara li dan it-tip ta' tagħmir tar-radju RB924i-2nD-BT5&BG77 huwa konformi mad-Direttiva 2014/53/UE. It-test kollu tad-
dikjarazzjoni ta' konformità tal-UE huwa disponibbli f'dan l-indirizz tal-Internet li ġej: https://mikrotik.com/products
NL Hierbij verklaar ik, Mikrotīkls SIA, dat het type radioapparatuur RB924i-2nD-BT5&BG77 conform is met Richtlijn 2014/53/EU. De volledige tekst van
de EU-conformiteitsverklaring kan worden geraadpleegd op het volgende internetadres: https://mikrotik.com/products
NO Mikrotīkls SIA erklærer herved at utstyret RB924i-2nD-BT5&BG77 er i samsvar med de grunnleggende krav og øvrige relevante krav i direktiv 2014
/53/EU. Den fulle teksten til EU-samsvarserklæringen er tilgjengelig på følgende internettadresse: https://mikrotik.com/products
PL Mikrotīkls SIA niniejszym oświadcza, że typ urządzenia radiowego RB924i-2nD-BT5&BG77 jest zgodny z dyrektywą 2014/53/UE. Pełny tekst
deklaracji zgodności UE jest dostępny pod następującym adresem internetowym: https://mikrotik.com/products
PT O(a) abaixo assinado(a) Mikrotīkls SIA declara que o presente tipo de equipamento de rádio RB924i-2nD-BT5&BG77 está em conformidade com a
Diretiva 2014/53/UE. O texto integral da declaração de conformidade está disponível no seguinte endereço de Internet: https://mikrotik.com/products
RO Prin prezenta, Mikrotīkls SIA declară că tipul de echipamente radio RB924i-2nD-BT5&BG77 este în conformitate cu Directiva 2014/53/UE. Textul
integral al declaraiei UE de conformitate este disponibil la următoarea adresă internet: https://mikrotik.com/products
SK Mikrotīkls SIA týmto vyhlasuje, že rádiové zariadenie typu RB924i-2nD-BT5&BG77 je v súlade so smernicou 2014/53/EÚ. Úplné EÚ vyhlásenie o
zhode je k dispozícii na tejto internetovej adrese: https://mikrotik.com/products
SL Mikrotīkls SIA potrjuje, da je tip radijske opreme RB924i-2nD-BT5&BG77 skladen z Direktivo 2014/53/EU. Celotno besedilo izjave EU o skladnosti
je na voljo na naslednjem spletnem naslovu: https://mikrotik.com/products
SV Härmed försäkrar Mikrotīkls SIA att denna typ av radioutrustning RB924i-2nD-BT5&BG77 överensstämmer med direktiv 2014/53/EU. Den
fullständiga texten till EU-försäkran om överensstämmelse finns på följande webbadress: https://mikrotik.com/products
WLAN / Bluetooth / LTE
(EN) Operating Frequency / Maximum output power
(DE) Betriebsfrequenz / maximale Ausgangsleistung
(FR) Fréquence de fonctionnement / puissance de sortie maximale
(IT) Frequenza operativa / massima potenza di uscita
WLAN 2400-2483.5 MHz / 20 dBm
Bluetooth 2400-2483.5 MHz/ 20 dBm
LTE FDD Band 1 2100 MHz / 21 dBm
LTE FDD Band 3 1800 MHz / 21 dBm
LTE FDD Band 8 900 MHz / 21 dBm

(ES) Frecuencia de funcionamiento / potencia de salida máxima
(RU) Рабочая частота / максимальная выходная мощность
LTE FDD Band 20 800 MHz / 21 dBm
LTE FDD Band 28 700 MHz / 21 dBm
(EN) Technical Specifications / (DE) Technische Spezifikationen / (FR) Spécifications
techniques /
(IT) Specifiche tecniche / (ES) Especificaciones técnicas / (RU) Технические характеристики:
Product Power Input Options Power Adapter Output Specification Degrees of protection provided by enclosure (IP Code) Operating Temperature
Voltage Current
DC Jack
PoE In Ethernet Port
MIcroUSB 5V Port
24 V 1.2 A IP20 0°..+40°C±
(EN) This MikroTik device meets Maximum WLAN and LTE transmit power limits per ETSI regulations. For more detailed information see
Declaration of Conformity above / (DE) Dieses MikroTik-Gerät erfüllt die maximalen WLAN- und LTE-Sendeleistung Grenzwerte gemäß ETSI-
Bestimmungen. Weitere Informationen finden Sie oben unter Konformitätserklärung / (FR) Cet appareil MikroTik respecte les limites maximales
de puissance de transmission WLAN et LTE conformément aux réglementations ETSI. Pour plus d'informations, voir la déclaration de
conformité ci-dessus / (IT) Questo dispositivo MikroTik è conforme ai limiti massimi di potenza di trasmissione WLAN e LTE in conformità con le
normative ETSI. Per ulteriori informazioni, consultare la dichiarazione di conformità sopra / (ES) Este dispositivo MikroTik cumple con los límites
máximos de potencia de transmisión WLAN y LTE de acuerdo con las regulaciones ETSI. Para obtener más información, consulte la
declaración de conformidad anterior / (RU) Это устройство MikroTik соответствует максимальным пределам мощности передачи WLAN и
LTE в соответствии с правилами ETSI. Для получения дополнительной информации см. Декларацию соответствия выше.