Device to Device Management

In order to maintain a well-aligned link, the two mounted FSO units communicate with one another through a secondary communication channel. This channel is decoupled from the main data transmission channel and is designed to work on a selection of RF technologies. Through this communication channel the following operations are conducted:
  • Initial unit configuration
  • Data monitoring
  • Remote unit management
  • Alignment and tracking

Primary and Secondary Unit

KORUZA v2 Pro units are declared upon configuration: one is primary unit, the other is secondary. Primary unit is the "brain" of the system, running the main processing and alignment algorithms and based on those, controls the secondary unit. Secondary unit performs the same baseline operations, but upon request from the primary unit. The diagram below shows operations done on each of the two units.
Diagram of primary and secondary operations
KORUZA v2 Pro demonstration units are all physically the same, running the same software hence maintenance and upgradability is unchanged. The primary/secondary role can be configured on every unit separately therefore this concept does not affect any production step. The primary/secondary declaration is part of system setup during installation.


A demonstration of device to device management in action can be seen in the Gif below. In this case the secondary unit is managed via the Graphical User Interface which is running on the Primary Unit.
You can see the RX Power on both units drop as the secondary unit is moved on the X axis.

Technology-agnostic Integration

KORUZA v2 Pro technology is designed as a novel implementation of FSO communication. The basic implementation is published open source and is aimed for advanced integration. Different technologies can be used, depending on the relevance to the use-case and the environment in which the particular FSO system is deployed.
So far, two of the following technologies have been implemented and tested, and two are under development :
  • WiFi
  • Local Network
  • Bluetooth
  • LoRa
All of the required information for this low-data communication channel to work is saved in the Config file.


  • Both units are using wireless USB dongles.
  • The primary unit is configured to act as a wireless access point.
  • The secondary unit has been configured to connect to primary unit's access point.
This has been implemented and tested.

Local Network

  • In this case, both units are connected to the local network using the WiFi of the RPi compute module inside.
This has been implemented and tested.


  • In this case, the two units pair with one another via Bluetooth.
  • A Bluetooth module is inserted inside the housing with suitable firmware to run this communication channel.
  • This technology (in comparison to WiFi) excludes other devices to connect to KORUZA v2 Pro unit.
This technology is currently under development.


  • In this case, each unit is a LoRa device,
  • LoRa module/chipset has to be added and configured, as well as RF antenna,
  • This technology is suitable for low power applications or RF-congested areas at 2.4GHz.
This is yet to be explored.


GitHub - IRNAS/koruza-v2-device-management
KORUZA v2 Pro Device Management Repository