Home
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running QNX Neutrino 7.1.
Sensor Framework
Sensor Framework Services
Sensor (sensor)
Start the Sensor service
Sensor configuration file
The configuration file is used to identify the sensors and cameras to use on your system. You can have multiple sensors and cameras physically connected to the board, but your system uses only the ones identified in this file.
Example: Sensor configuration file for file data
This sample configuration file is for using data sensor data.

QNX Momentics IDE User's Guide
This User's Guide describes version 7.1 of the Integrated Development Environment (IDE) that's part of the QNX Momentics tool suite.
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running QNX Neutrino 7.1.
- Quickstart Guide
- OS Components & Operations
- Audio & Graphics API
- Multimedia
- Networking Middleware
- Programming
- Sensor Framework
  - Architecture
  - Getting Started
    This guide gets you started with the Sensor Framework for QNX SDP.
  - Sensor Framework Libraries
  - Sensor Framework Services
    - Synchronizing Sensor Timestamps
      The Sensor (sensor) service supports the use of Precision Time Protocol to synchronize the timestamps for sensors across multiple target boards.
    - Sensor (sensor)
      Start the Sensor service
      - Sensor configuration file
        The configuration file is used to identify the sensors and cameras to use on your system. You can have multiple sensors and cameras physically connected to the board, but your system uses only the ones identified in this file.
        Example: Sensor configuration file for USB camera
        The following configuration file is for one USB camera connected the target.
        Example: Sensor configuration file for two USB cameras
        This is a configuration file for two USB cameras connected to the board.
        Example: Sensor configuration file for GigE network camera
        The following configuration file is for one network (e.g., Gigabit Ethernet (GigE)) camera connected to the target.
        Example: Sensor configuration file for file camera
        This is a configuration file for file cameras. File cameras aren't real cameras, but a configuration that plays a video.
        Example: Sensor configuration file for file data
        This sample configuration file is for using data sensor data.
        Example: Sensor configuration file for radar
        In this example, radar is connected directly to the target. The packet_size parameter for radar specifies the number of tracks (or tracked objects). The number you specify must be a multiple of 64.
        Example: Sensor configuration file for lidar
        In the following examples, Velodyne's lidar sensors are connected directly to the target.
        Example: Sensor configuration file for lidar (Leddartech)
        In this example, Leddartech lidar is connected directly to the target.
        Example: Sensor configuration file for GPS (XSens)
        In this example, an XSens global positioning system (GPS) is connected directly to the target. The vendorID and deviceID identifies the Kvaser CAN cable that's supported for this release.
        Example: Sensor configuration file for ONVIF camera
        In this example, an ONVIF camera is connected to the board.
        Example: Sensor configuration file for OV5640 camera
        In this example, an OV5640 camera is connected to the board.
        Example: Sensor configuration file for OV10635 camera
        In this example, one OV10635 camera is connected to the board.
        Example: Sensor configuration file for four OV10635 cameras
        In this example, four OV10635 cameras are connected to the board.
        Example: Sensor configuration file for four AMI MINICube RDACM24 cameras
        In this example, four AMI MINICube RDACM24 cameras are connected to the board.
        Example: Sensor configuration file for NovAtel GPS and IMU sensors
        In this example, a NovAtel GPS and IMU sensor are connected to the board.
      - Interim data configuration file
        The interim data configuration file is used to identify the units that correspond to interim data. All interim data units that publishers and subscribers can use to publish and receive interim data are identified in this configuration file.
      - Debugging
        You can retrieve sensor information on your target from /dev/sensor.
      - Security considerations
        When you use the Sensor service, there are many relevant recommendations and system interactions to consider.
    - System Launch and Monitor (slm)
      Use slm in the Sensor Framework for QNX SDP to modify the launch order of applications and services without rebuilding the target image.
- System Security Guide
  The QNX System Security Guide is intended for both system integrators who are responsible for the security of a QNX Neutrino RTOS system and developers who want to create a QNX Neutrino resource manager free from vulnerabilities.
- Utilities & Libraries
QNX Hypervisor
The QNX Hypervisor allows you to run multiple OSs on a target system so you can separate critical and non-critical functions, support a wide variety of applications, and reduce hardware costs.
QNX Software in the Cloud
QNX Software in the Cloud enables developers to use the QNX software in Amazon Web Services (AWS) and Microsoft Azure (Azure).
QNX Advanced Virtualization Frameworks User's Guide
This User's Guide is aimed at all systems integrators and developers who want to design and build embedded systems using the QNX Advanced Virtualization Frameworks.
Typographical Conventions, Support, and Licensing
This section describes the typographical conventions used throughout the documentation and explains how to obtain technical support.

Example: Sensor configuration file for file data

This sample configuration file is for using data sensor data.

The address parameter specifies the GZIP-compressed (TGZ) or raw (.raw) file. Here's what the configuration file looks like for lidar data and uncompressed video:

begin SENSOR_UNIT_1
    type = file_data
    name = vlp-16
    address = /accounts/1000/shared/capturelidar.tgz
    playback_group = 1
    direction = 0,0,0
    position = 1000,0,1100
end SENSOR_UNIT_1
begin SENSOR_UNIT_2
    type = file_data
    name = frontcam
    address = /accounts/1000/shared/capturevideo.raw
    playback_group = 1
    direction = 0,0,0
    position = 1000,0,1100
end SENSOR_UNIT_2

Page updated: March 12, 2026