devices Devices

This menu displays the possible payloads/devices that can be configured with BCS. Each section will allow the user to configure different parameters from the available variety of payloads.


Devices menu

By default, only the Transponder/ADS-B device is added to this menu (as shown in the figure above). However, users can added other supported devices by simply by clicking Add device:


Add devices


A transponder is a device that generates or parses ADS-B messages. This menu allows the user to use/configure a transponder through Custom Messages.

The interface includes different transponder models, depending on the one selected, some configurable parameters are enabled or disabled.


The parameters that appear in this menu and that must be configured by the user depending on the transponder model are explained below:

  • Model: The options available in Veronte BCS are as follows:

    • Internal Transponder

    • uAvionix Ping 20s

    • uAvionix Ping 1090

    • Sagetech MX Series

    • Sagetech XPS-TR

    • Sagetech XPG-TR

    • Sagetech XPS-TRB

    • Daedalean

  • Custom message: Select the Custom message 1-3 to be used for the information exchange, as it will be automatically filled with the information required by the transponder/ADS-B.


    This option is not available for the Internal Transponder model, as it is already integrated in the BCS.

  • Control Mode: The user must configure the transponder type:

    • Standby: Transponder will not respond to interrogation.

    • ADS-B In: When the transponder sends the detected UAVs.


      This option is not admitted for the uAvionix Ping 20s model.

    • ADS-B Out: When the transponder wants to send the position of the UAV.


      This option is not admitted for the Deadelean model.

    • ADS-B In/Out: This option is not admitted for uAvionix Ping 20s and Daedalean models.

  • Icao: Unique ICAO 24-bit address permanent for the aircraft, which becomes a part of the aircraft’s Certificate of Registration.

    It is represented by six hexadecimal characters.


    • This option is not available for Sagetech and Daedalean models.

    • If the ADS-B In control mode has been selected, this option will be disabled.

  • Emitter type: The user should specify the type/category of the vehicle in which the transponder is located. The available options are:


    • This option is not available for Sagetech and Daedalean models.

    • If the ADS-B In control mode has been selected, this option will be disabled.

  • Call sign: Communication call sign assigned as unique identifier to the aircraft.


    • This option is not available for Sagetech and Daedalean models.

    • If the ADS-B In control mode has been selected, this option will be disabled.


Adding a camera will create a default Camera configuration menu.


Cameras section

  1. Name: Give a name to the customized camera.

  2. Search: Users can also choose a camera from the predefined list of cameras, which will automatically establish the values of the Sensor, Resolution and Lens parameters.

  3. Sensor: Defines the camera sensor width and height in mm.

  4. Resolution: Defines the camera resolution width and height.

  5. Lens: Defines the focal length from the camera in mm.

  6. Camera cache: Defines the cache time used to play the selected camera on the gimbal widget.

    • A higher cache might increase the video delay.

    • A lower cache might cause video artifacts or disconnections.


    333 miliseconds should be enough for a 1080p video.

  7. Cam associated with gimbal: If the camera is from a Gimbal device, it is important to configure this field and select the the Gimbal block number that is related to this camera.

  8. Photogrammetry: This allows the creation of Photogrammetry actions.

    The actions performed in a Photogrammetry mission can be defined here, following the same possibilities as in Actions - Automations.

    • Add Action: Will add a new action.


      A maximum of 4 Actions can be defined (Actions 0-3).

    • Generate: Clicking on ‘Generate’ will create the automation ‘Photogrammetry’ with a Button as event and with the actions defined here.

An example is given below:


Cameras - Example

The automation created for Photogrammetry is shown below:


Cameras - Automation example


This board menu allows the user to configure communicate via CAN, in BCS PDI Builder, with another device such as CEX, MEX, MC01, etc., in only 1 step, so in only 1 interface window. Instead of doing it in several steps, as is explained in CEX - Integration examples or MC01 - Integration examples.


Board section

  • Click on the add icon to add a new field. The following parameters must be defined:

    • Commgr port: Select the desired COM Manager port: Commgr port 1-6.

    • Can Over Serie: Select the desired Serial to CAN / CAN to serial: Serial to CAN 1-2/CAN to Serial 1-2.

    • Can Input Filter: Select the desired input filter to use: Input Filter 1-2.

    • Can Output Filter: Select the output filter the user wishes to use: Output Filter 1-2.

    • Can Port: CAN A, CAN B or BOTH can be selected.

    • ID Can Tx: Enter the ID of the CAN message to be sent.

    • ID Can Rx: Enter the ID of the CAN message to be received.


    Be careful not to select a producer/consumer that is being used for another purpose, as the configuration defined here has “priority” and will be changed to this.

    For more information on these parameters, see Input/Output section of this manual.

  • Clicking the remove icon will remove the field and display a confirmation warning message.

  • By clicking on ‘Apply changes’, all these CAN communication settings are applied to the BCS configuration.

Below is an example of before/after when changes are applied:


Board - I/O Setup configuration


Board - CAN Setup configuration


Board - Mailboxes configuration