DroneScout - Receiver Manual 230/240-series (https://download.bluemark.io/dronescout_sensor_manual_230.pdf)
citeturn14view0 [wordlim: 200] Crawled: today; Content type: application/pdf; Number of pages: 61; Source: open({"ref_id":"https://download.bluemark.io/dronescout_sensor_manual_230.pdf","lineno":690}); Total lines: 1814
L569@P25: mount -o remount,ro /media/root-ro;
L570@P25: reboot -f # or power cycle and the sensor will be a DHCP client
L571@P25: 1.9 Open Drone ID
L572@P25: DroneScout uses the Open Drone ID framework to encode Remote ID signals. The framework can
L573@P25: be found on this page:
L574@P25: https://www.opendroneid.org/
L575@P25: 1.10 Global architecture
L576@P25: The receiver has a binary, dronescout.arm64, in the root-folder (/root) to sense for Remote ID
L577@P25: signals. There is also a configuration file dronescout.conf to configure MQTT and other settings. The
L578@P25: file wlan_channels.conf is used to specify the WiFi channels that will be scanned. Finally, there are
L579@P25: some auxiliary files that are discussed in the next chapter.
L580@P25: 1.11 Maximum detection range
L581@P25: The maximum detection range of the ds230/ds240 receiver depends on several factors:
L582@P25:  Effective radiated power (ERP) of the transponder (transmit power, antenna design)
L583@P25:  Antenna height of the receiver and transponder. Detection range increases with higher
L584@P25: height as it converges to free-space propagation.
L585@P25:  Antenna gain and directivity of the receiver. The maximum ERP power of the transponder is
L586@P25: limited by the WiFi/Bluetooth technology standard.
L587@P25-26: 26/61DroneScout Receiver Manual - version 2.7 July 2026 - © BlueMark Innovations BV 2022 - 2026
L588@P26:  Line of sight versus non-line of sight to the transponder due to buildings, trees, hills etc.
L589@P26:  Weather: rain, fog or other “wet” weather will limit the range.
L590@P26:  Moving drone: if the drones moves, it will impact negatively on the range. The average RSSI
L591@P26: will vary more (signals may be lost more easy). Also if the drones move fast, typically the drone
L592@P26: will tilt. In such a case, the drone may block partly the signals towards the receiver.
L593@P26:  Probability threshold of detection.
L594@P26:  Urban vs Rural areas, see “Urban versus Rural detection range” in section 1.4 and also section
L595@P26: 1.5. In dense urban areas the detection range can be reduced to 1.5 km!
L596@P26: No guarantees can be made about the detection range, due to the complex nature
L597@P26: of wireless propagation, as shortly described above. Typically, the detection range is at
L598@P26: least multiple kilometers.
L599@P26: The ds240 receiver has 3x larger detection range compared to the ds230 receiver due to the use of
L600@P26: high gain antennas that result in a 10 dB extra increase in the sensitivity.
L601@P26: The detection range below is calculated based on internal measurements, that have been
L602@P26: extrapolated using the “best-case” Free space propagation model1.
L603@P26: In general, free-space is considered the most ideal situation. In real-life situation there is more
L604@P26: attenuation between the receiver and beacon. Typically, how higher the receiver is installed, how
L605@P26: more the propagation mimics free-space. Hence, the detection range increases. This is supported
L606@P26: for instance by publications like: “Characterization of Radio Path Loss in Seaport Environment for
L607@P26: WiMAX Applications” - Ming-Tuo Zhou , Joe Jurianto , Jaya Shankar , M. Fujise
L608@P26: 2
L609@P26: The free-space path loss model is:
L610@P26: PL = 20 log10 (d /d0) + c
L611@P26: Where d is the distance, d0 , a reference distance and c a constant value that among other depends
L612@P26: on the frequency. If the distance d doubles i.e. d = 2d , the path loss will increase by 6 dB and if d
L613@P26: would be 10 times larger, the path loss increases by 20 dB.
L614@P26: Measurement setup (ds230 receiver):
L615@P26:  receiver antenna height 2.5 m
L616@P26:  drone/transponder height 10 m
L617@P26:  transponder ERP power 20 dBm.
L618@P26:  RSSI measurements based on a slow moving drone equipped with the DroneBeacon
L619@P26: transponder.
L620@P26:  flat agricultural land
L621@P26:  nearby trees > 15 meter (behind antenna), nearby building > 25 meter (behind antenna)
L622@P26:  nearby building can act as reflector, so results could be (slightly) too optimistic.
L623@P26:  sunny weather
L624@P26: BLE legacy
L625@P26:  Average RSSI at 500 m: -78 dBm
L626@P26:  Sensitivity radio -97 dBm
L627@P26: So 19 dB (-78 - -97) above sensitivity level. Assuming free space propagation (6 dB loss per doubling
L628@P26: of the distance), the maximum detection range is: 500*10^(19/20) = 4.4 km (ds230 receiver). This
L629@P26: results in an detection area of 61 km2.
L630@P26: .
L631@P26: The ds240 receiver has 10 dB more sensitivity, the maximum detection range is 13.2 km (ds240
L632@P26: receiver). This results in an detection area of 547 km2.
L633@P26: .
L634@P26: 1
L635@P26: https://en.wikipedia.org/wiki/Free-space_path_loss
L636@P26: 2 http://ap-s.ei.tuat.ac.jp/isapx/2006/pdf/3B1b-4.pdf (Table 1).
L637@P26-27: 27/61DroneScout Receiver Manual - version 2.7 July 2026 - © BlueMark Innovations BV 2022 - 2026
L638@P27: BLE Long Range
L639@P27:  Average RSSI at 500 m: -78 dBm
L640@P27:  Sensitivity radio -105 dBm
L641@P27: So 27 dB (-78 - -105) above sensitivity level. Assuming free space propagation (6 dB loss per
L642@P27: doubling of the distance), the maximum detection range is: 500*10^(27/20) = 11.2 km (ds230
L643@P27: receiver). This results in an detection area of 394 km2.
L644@P27: .
L645@P27: The ds240 receiver has 10 dB more sensitivity, the maximum detection range is 33.6 km (ds240
L646@P27: receiver). This results in an detection area of 3545 km2.
L647@P27: .
L648@P27: WiFi NaN 2.4 GHz
L649@P27:  Average RSSI at 500 m: -61 dBm
L650@P27:  Sensitivity radio -85 dBm
L651@P27: So 19 dB (-61 - -85) above sensitivity level. Assuming free space propagation (6 dB loss per doubling
L652@P27: of the distance), the maximum detection range is: 500*10^(19/20) = 7.9 km (ds230 receiver). This
L653@P27: results in an detection area of 196 km2.
L654@P27: .
L655@P27: The ds240 receiver has 10 dB more sensitivity, the maximum detection range is 23.7 km (ds240
L656@P27: receiver). This results in an detection area of 1764 km2.
L657@P27: .
L658@P27: WiFi Beacon 2.4 GHz
L659@P27:  Average RSSI at 500 m: -60 dBm
L660@P27:  Sensitivity radio -85 dBm
L661@P27: So 25 dB (-60 - -85) above sensitivity level. Assuming free space propagation (6 dB loss per doubling
L662@P27: of the distance.) So maximum detection range is: 500*10^(25/20) = 8.9 km (ds230 receiver). This
L663@P27: results in an detection area of 249 km2.
L664@P27: The ds240 receiver has 10 dB more sensitivity, the maximum detection range is 26.7 km (ds240
L665@P27: receiver). This results in an detection area of 2238 km2.
L666@P27: WiFi Beacon 5.2 GHz
L667@P27:  Average RSSI at 500 m: -68 dBm
L668@P27:  Sensitivity radio -85 dBm
L669@P27: Typically, the 5.2 and 5.8 GHz frequency band have lower detection range due to the higher
L670@P27: frequency.
L671@P27: So 17 dB (-68 - -85) above sensitivity level. Assuming free space propagation (6 dB loss per doubling
L672@P27: of the distance), the maximum detection range is: 500*10^(17/20) = 3.5 km (ds230 receiver). This
L673@P27: results in an detection area of 39 km2.
L674@P27: The ds240 receiver has 10 dB more sensitivity, the maximum detection range is 10.5 km (ds240
L675@P27: receiver). This results in an detection area of 346 km2.
L676@P27-28: 28/61DroneScout Receiver Manual - version 2.7 July 2026 - © BlueMark Innovations BV 2022 - 2026
L677@P28: Extending the detection range
L678@P28: The detection range can be extended in the following ways:
L679@P28:  Install the receiver at a higher place. In this case the received signal will be stronger as
L680@P28: propagation is more similar to free-space propagation.
L681@P28:  Replace the antennas with a higher antenna gain. Rule of thumb is that every 6 dB increase,
L682@P28: will result in doubling of the detection range. Hence, a 15 dBi antenna would triple (3x) the
L683@P28: maximum detection distance. High-gain antennas and/or high receiver location may prevent
L684@P28: detection of nearby drones. Experiments with the 5 dBi antennas and flying 50 m above the
L685@P28: receiver, did not give any problem detecting the transponder. (The signal was strong received.)
L686@P28: The same holds for a 50 m distance experiment, where the drone was moved from 3m to 50
L687@P28: meter height. In all cases the drones was received with a strong signal.
L688@P28:  The range can not be extended in all situations. For instance, if the sensor is used in urban
L689@P28: areas, see “Urban versus Rural detection range” in section 1.4.
L690@P28: 1.12 RSSI values at 1 meter distance
L691@P28: The following RSSI values were measured at 1 meter distance using a db120 transponder in an
L692@P28: office environment and a ds230 receiver. If you measure much weaker RSSI signals as the ones
L693@P28: stated below with the db120 transponder (larger as 10 dB), typically the ds230 receiver is broken or
L694@P28: the antennas are not mounted properly.
L695@P28: Using a transponder of a different brand can result in different (lower RSSI values), for instance if the
L696@P28: transmit power of that transponder is lower or a different antenna is used. In general the RSSI values
L697@P28: also depend on the environment and position of the transponder. This can result in RSSI values that
L698@P28: are 3 dB higher or lower.
L699@P28: WLAN transmission protocols: on average -20 dBm +/- 3 dB.
L700@P28: Bluetooth transmission protocols: ~ -37 dBm +/- 3 dB.
L701@P28: 1.13 System time
L702@P28: The DroneScout ds230/ds240 receiver don’t have an onboard RTC clock. It means that when the
L703@P28: system is powered off, the current time is not saved. If the DroneScout receiver is booted, it will use
L704@P28: chrony, a Network Time Protocol (NTP) client (https://chrony-project.org/) to set the correct system
L705@P28: time.
L706@P28: Do you need the correct system time?
L707@P28: DroneScout receivers will detect RemoteID signals regardless of the system time. If the time is
L708@P28: incorrect all (local) timestamps in the MQTT messages are wrong. If your own processing of the
L709@P28: RemoteID data does not care about the correct timestamp, there is no need to have the correct
L710@P28: time.
L711@P28: In case of DroneScout Dashboard you need to have the correct system time. In this solution we
L712@P28: compare the reported UTC time by the client browser, with the time of detection. If it is too old, it is
L713@P28: not shown/displayed. Also, we use this to determine if a sensor is still up and running.
L714@P28: In firmware 20250228-1115 there is also an extra option set_system_time. You only need to set this
L715@P28: option, if you are in an offline environment (and don’t have other options for setting the system
L716@P28: time). If enabled, the receiver will set the system time based on the reported time by the GNSS
L717@P28: receiver of the LTE add-on. Note that this method of setting the system time is less accurate, but the
L718@P28: time accuracy should still be less than second.
L719@P28-29: 29/61DroneScout Receiver Manual - version 2.7 July 2026 - © BlueMark Innovations BV 2022 - 2026
L720@P29: In file /var/log/syslog you will see messages like this to confirm that the system time has been set:
L721@P29: 2025-02-28T11:23:56.136865+00:00 ds221000000230 root: BlueMark application:
L722@P29: set system time 1740741836.13
L723@P29: The GNSS receiver of the LTE add-on can take up to 15 minutes to get a GPS fix. The application will
L724@P29: set the system time when there is a GPS fix and will update every few hours this system time.
L725@P29: 1.14 RemoteID manufacturer and model identification
L726@P29: In firmware 20250228-1115 or higher DroneScout receivers contain an embedded database that
L727@P29: will use the detected serial number to identify:
L728@P29:  present, set to 1 if the detected RemoteID signal contains a Serial Number
L729@P29:  basic checks if the serial number is valid (does it follow the ANSI/CTA-2063-A requirements)
L730@P29:  brand like DJI
L731@P29:  model like Mavic 3
L732@P29:  type like multirotor
L733@P29:  application, free text like consumer or industrial
L734@P29:  weight, the Maximum Take-off Weight (mtow) in kg
L735@P29:  dimensions, free text, the size is reported in mm.
L736@P29: The database is based Open Source Intelligence (OSINT) sources. The database contains more than
L737@P29: 200 brands and more than 400 popular drone models with RemoteID. Additional fields like type,
L738@P29: application, weight, dimensions are free text fields that can be incomplete, or contain errors.
L739@P29-30: 30/61DroneScout Receiver Manual - version 2.7 July 2026 - © BlueMark Innovations BV 2022 - 2026
L740@P30: 2 CONFIGURATION
L741@P30: The firmware is protected by a license/device key. In case the receiver does not work
L742@P30: anymore due to license errors, please contact support.
L743@P30: The ds230/ds240 needs a MQTT broker for uploading data. In the default
L744@P30: configuration none is configured. For test purposes you can also install a MQTT broker
L745@P30: on the sensor it self. This is described in section 2.5.
L746@P30: root password
L747@P30: For production environments it is strongly advised to change the default password.
L748@P30: overlayroot-chroot
L749@P30: passwd #interactive tool to change the password
L750@P30: exit
L751@P30: reboot # new password will work after a reboot
L752@P30: dronescout.conf
L753@P30: The file /root/dronescout.conf is the main configuration file.
L754@P30: The default contents are shown below.
L755@P30: #
L756@P30: # Configuration file
L757@P30: # (c) Bluemark Innovations BV 2022 - 2026
L758@P30: [global]
L759@P30: sensorID = ds220500000100 ; receiver ID up to 256 characters
L760@P30: status_interval_s = 60 ; how often status messages are generated in [s].
L761@P30: temp_dummy_load_enabled = 1 ; if 1 it will generate a dummy load
L762@P30: [mqtt]
L763@P30: host = localhost ; MQTT host
L764@P30: port = 1883 ; MQTT port
L765@P30: topic = ; leave empty to use default topic based on receiverID
L766@P30: QoSlevel = 1 ; QoS level 0, 1 or 2
L767@P30: username = ; leave empty if not used
L768@P30: password = ; leave empty if not used
L769@P30: keepalive = 60 ; keep alive period in seconds.
L770@P30: clientID = ; set clientID, leave empty for default setting
L771@P30: ssl = 0 ; 0 disable SSL in MQTT connection 1, enable SSL (recommended)
L772@P30: ssl_verify = 0 ; disable/enable SSL verification
L773@P30: CAfile = /root/certs/ca.crt ; location to CA file for SSL connection
L774@P30: CRTfile = /root/certs/client.crt ; location to CRT file for SSL connection
L775@P30: KEYfile = /root/certs/client.key ; locaton to KEY file for SSL connection
L776@P30: compression = lzma ; none or lzma. In case of lzma, payload is compressed.
L777@P30: retain = 0 ; set to 1 in order to retain messages on mqtt broker
L778@P30-31: 31/61DroneScout Receiver Manual - version 2.7 July 2026 - © BlueMark Innovations BV 2022 - 2026
L779@P31: transmit_mode = 2; 0 send MQTT message for each new message, 1 every second
L780@P31: # (truncate), 2 combine all and send at transmit mode 2
L781@P31: # interval ms period
L782@P31: transmit_mode_2_interval_ms = 250; set the transmission interval (ms) in
L783@P31: # transmit mode 2 (valid range: 50 to 60000)
L784@P31: raw_data = 0 ; 0 do not include raw data (of the air interface),
L785@P31: # 1 include raw data
L786@P31: aggregate_data = 1; 0 send MQTT message with latest received message only, 1
L787@P31: # send all information about this RemoteID device
L788@P31: [mqtt2]
L789@P31: enabled = 0 ; set to 1 to enable publishing to a second broker
L790@P31: host = second_broker ; MQTT host
L791@P31: port = 1883 ; MQTT port
L792@P31: topic = ; leave empty to use default topic based on receiverID
L793@P31: QoSlevel = 1 ; QoS level 0, 1 or 2
L794@P31: username = ; leave empty if not used
L795@P31: password = ; leave empty if not used
L796@P31: keepalive = 60 ; keep alive period in seconds.
L797@P31: clientID = ; set clientID, leave empty for default setting
L798@P31: ssl = 0 ; 0 disable SSL in MQTT connection 1, enable SSL (recommended)
L799@P31: ssl_verify = 0 ; disable/enable SSL verification
L800@P31: CAfile = /root/certs/ca.crt ; location to CA file for SSL connection
L801@P31: CRTfile = /root/certs/client.crt ; location to CRT file for SSL connection
L802@P31: KEYfile = /root/certs/client.key ; locaton to KEY file for SSL connection
L803@P31: compression = lzma ; none or lzma. In case of lzma, payload is compressed.
L804@P31: retain = 0 ; set to 1 in order to retain messages on mqtt broker
L805@P31: [interface]
L806@P31: WLAN_USB_1 = wlan1 ; interface for WLAN 1 adapter
L807@P31: WLAN_USB_2 = wlan2 ; interface for WLAN 2 adapter
L808@P31: # WLAN_USB_3 = wlan3 ; [ds240 only] interface for WLAN 3 adapter,
L809@P31: BT_UART_1 = /dev/ttyACM0 ; interface for USB UART adapter
L810@P31: [threshold]
L811@P31: WLAN_USB = -200 ; signals weaker as the threshold won't be processed.
L812@P31: BT_UART = -200 ; signals weakers as the threshold won't be processed.
L813@P31: # new configuration parameters/keys for 20240927-1205 firmware upwards
L814@P31: [rid]
L815@P31: enabled = 1 ; enable RemoteID detections, default 1 (enabled)
L816@P31: wlan = 1 ; enable RemoteID WLAN detections, default 1 (enabled)
L817@P31: wlan_france = 0 ; Enable French INFODRONE detection, default 0 (disabled)
L818@P31: ble = 1 ; enable RemoteID BLE (Bluetooth) detections, default 1 (enabled)
L819@P31: extra = 1; enable extra RemoteID info like make, model default 1 (enabled)
L820@P31: discard_bridge = 1; discard DroneScout Bridge packets
L821@P31: # GPS section only relevant if LTE add-on is installed
L822@P31: [gps]
L823@P31: enabled = 0 ; enable GPS function of LTE modem (if add-on is installed)
L824@P31: port = /dev/ttyUSB2 ; port for sending AT commands
L825@P31: location = 1 ; enable locations messages
L826@P31: network = 1 ; enable mobile network messages
L827@P31: set_system_time = 0 ; if set to 1, the sensor will set the system time
L828@P31: # using the GNSS receiver of the LTE-add on
L829@P31: # ADS-B section only relevant if ADS-B receiver add-on is installed
L830@P31: [ads-b]
L831@P31-32: 32/61DroneScout Receiver Manual - version 2.7 July 2026 - © BlueMark Innovations BV 2022 - 2026
L832@P32: enabled = 0 ; enable ADS-B receiver
L833@P32: gain = 48 ; gain of SDR radio. 0 - 50 dB. Set to -1 for auto gain
L834@P32: aggregate_data = 1 ; if 1, use older data from aircraft to fill missing
L835@P32: # data fields
L836@P32: valid_location = 0 ; process signals with valid location only, default 0
L837@P32: data_reduction = 0 ; one message per aircraft per
L838@P32: # transmit_mode_2_interval_ms, default 0 (disabled)
L839@P32: # UAT section only relevant if UAT receiver add-on is installed
L840@P32: [uat]
L841@P32: enabled = 0 ; enable UAT receiver
L842@P32: gain = 48 ; gain of SDR radio. 0 - 50 dB. Set to -1 for auto gain
L843@P32: aggregate_data = 1 ; if 1, use older data from aircraft to fill missing
L844@P32: # data fields
L845@P32: valid_location = 0 ; process signals with valid location only, default 0
L846@P32: data_reduction = 0 ; one message per aircraft per
L847@P32: # transmit_mode_2_interval_ms, default 0 (disabled)
L848@P32: # LTE settings, only relevant if LTE option has been installed.
L849@P32: [lte]
L850@P32: enabled = 0 ; #if set to 0, no connection is created
L851@P32: mode = backup ; # modes: primary, backup, ondemand
L852@P32: port = /dev/ttyUSB3 ; port for data
L853@P32: apn = internet
L854@P32: user =
L855@P32: password =
L856@P32: pincode=
L857@P32: upgrade = 1 ; upgrade LTE scripts when there is a new update
L858@P32: lteplus = 1 ; if 1, force lte or higher networks (and do not allow 2G or 3G
L859@P32: networks)
L860@P32: # Settings for reverse SSH connections
L861@P32: [remote]
L862@P32: enabled = 0 ; if enabled setup a reverse SSH connection
L863@P32: server = myserver ; host
L864@P32: sshkey = /root/.ssh/id_rsa ; location of the SSH key
L865@P32: user = user
L866@P32: port_server = 22 ; ssh port of server
L867@P32: port_remote = 2222 ; the sensor can be reached (ssh) at this port
L868@P32: Use the following commands to edit file /root/dronescout.conf:
L869@P32: overlayroot-chroot
L870@P32: nano /root/dronescout.conf # use nano (or vi) as editor
L871@P32: exit
L872@P32: reboot # to apply changes
L873@P32: sensorID
L874@P32: The sensorID is a string up to 256 characters. It is used to identify the DroneScout receiver and is
L875@P32: also used in the MQTT payload.
L876@P32-33: 33/61DroneScout Receiver Manual - version 2.7 July 2026 - © BlueMark Innovations BV 2022 - 2026
L877@P33: status_interval_s
L878@P33: In firmware 20240528-1739 and higher: how often should a status message be generated in
L879@P33: seconds. Default is 60 seconds. See Chapter 3 for more information about status messages.
L880@P33: temp_dummy_load_enabled
L881@P33: Introduced in firmware 20240108-1539 and later. It will create a dummy CPU load to increase the
L882@P33: temperature in cold environments. This should benefit the reliability if the outside temperature is
L883@P33: -20 degree Celsius. This dummy load is only triggered/generated if the outside temperature is
L884@P33: around 0 degree Celsius or lower.
L885@P33: MQTT
L886@P33: The receiver uses internally the MQTT mosquitto library (https://mosquitto.org/). Settings in this
L887@P33: MQTT section relate to this library.
L888@P33: For non-encrypted MQTT brokers, only set the host and port. Make sure that ssl is set to 0. If no topic
L889@P33: is specified, the receiver will use the topic: /sensor/<sensorID>/upload
L890@P33: If compression is set to none, the receiver will publish JSON payload in plain text. If compression is
L891@P33: set to lzma the entire JSON payload will be compressed with LZMA. Typically, LZMA achieves over
L892@P33: 80% compression ratio. In plain text mode, the payload is typically around 1400 bytes, with LZMA
L893@P33: compression, it is around 260 bytes.
L894@P33: For production deployments, it is strongly advised to enable SSL encrypted communication! In this
L895@P33: case set ssl to 1. Also, set the related file locations: CAfile, CRTfile and KEYfile to the files needed for
L896@P33: SSL-encrypted communication to the MQTT broker. If case of self-generated SSL keys, set ssl_verify
L897@P33: to 0.
L898@P33: For more security also a username, password can be configured, if the MQTT broker requires this.
L899@P33: In firmware 20221208-1250 and higher, two new options are available: transmit_mode and
L900@P33: aggregate_data. The default value for both variables is 1. If transmit_mode is 1, roughly 2 times per
L901@P33: second (2 Hz) the sensor will generate a MQTT message for each detected Remote ID device (if new
L902@P33: signals are detected for that device). If transmit_mode is 0, a MQTT message is generated every time
L903@P33: a Remote ID signal is detected. (No throttling.) In case transmit_mode is 0, the MQTT broker may be
L904@P33: overloaded, if a lot of signals are detected and a lot of sensors are uploading data to the broker. In
L905@P33: such cases new MQTT messages will get stalled at the sensor. In most smaller setups, it is safe to use
L906@P33: transmit_mode is 0.
L907@P33: In firmware 20230329-1042 and higher transmit mode 2 has been introduced. In this mode all
L908@P33: received MQTT messages are combined into one payload. At the interval
L909@P33: transmit_mode_2_interval_ms the combined payload (in milliseconds) is transmitted via MQTT. The
L910@P33: valid range is between 250 ms and 60000 (1 minute). Use this transmit mode if you want to publish
L911@P33: all received Remote ID signals, but at the same time want to limit the message rate to prevent
L912@P33: overloading of the MQTT broker/publishing capacity. Note for transmit mode 2 you also need the
L913@P33: latest MQTT subscriber application (Chapter 4).
L914@P33: Potential risks of transmit mode 1 Although transmit mode 1 prevents overloading of a MQTT
L915@P33: broker, there is a small probability that an attacker could use this throttling, to broadcast a similar
L916@P33: malicious Remote ID signal where some values have been changed (like location data). If the
L917@P33: attacker uses the correct timing, it can prevent the ds230 to receive the original Remote ID signal.
L918@P33: For that reason newer ds230 receiver will use transmit mode 2 by default. Also for existing
L919@P33: deployments we recommend to switch from transmit mode 1 to 2.
L920@P33-34: 34/61DroneScout Receiver Manual - version 2.7 July 2026 - © BlueMark Innovations BV 2022 - 2026
L921@P34: The other option is aggregate_data. In transmission mode BT4 legacy, only one part of the Remote
L922@P34: ID signal is broadcast per time. E.g. one message for the Basic ID, another one for the Location data
L923@P34: etc. For other transmission modes, the messages will typically contain all Remote ID information. If
L924@P34: aggregate_data = 1, the sensor will save in memory the latest contents of the Remote ID device. So
L925@P34: if a BT4 Basic ID message is received, that information element is updated. Other elements are
L926@P34: unchanged. The sensor will output an MQTT signal with all available information elements. In case
L927@P34: of aggregate_data = 0, all information elements are set to zero and only the latest received
L928@P34: information will be saved to memory and the sensor will output an MQTT signal accordingly. In
L929@P34: firmware 20240717-1353 and higher, the option raw_data was introduced. If set to 1, the MQTT
L930@P34: message will have a message field raw, which contains the base64 encoded raw data of the air
L931@P34: interface (payload).
L932@P34: Seccond MQTT broker.
L933@P34: In version 20260623-1549 and higher, there is a section mqtt2. If enabled, the receiver will both
L934@P34: publish data to the MQTT broker defined in the mqtt section, but also to the one in the mqtt2
L935@P34: section.
L936@P34: interfaces
L937@P34: This section configures the location of the Bluetooth and WiFi radios. Leave to default settings.
L938@P34: threshold
L939@P34: Advanced setting that you typically don’t need to change. All radios sense with maximum
L940@P34: sensitivity. In case you want to reduce the detection range, you can specify here a threshold. Signals
