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 Libraries
Sensor Developer's Guide
The Sensor library abstracts the complexity of interfacing with sensors and cameras connected to the target board.
Sensor Library Reference
The Sensor library provides applications with a consistent interface to interact with sensors connected to the system.
sensor_radar.h
The definitions of the data formats for radar sensors.
sensor_flag_radar_track_polar_t
Bit settings for the sensor_buffer_t flag field for data of type SENSOR_FORMAT_RADAR_POLAR

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
    - ADAS Library Developer's Guide
      The ADAS library facilitates the development of embedded systems that rely on sensor data.
    - Camera Developer's Guide
      The Camera library abstracts the complexity of interfacing with a camera connected to the target board.
    - Sensor Developer's Guide
      The Sensor library abstracts the complexity of interfacing with sensors and cameras connected to the target board.
      - Sensor Library Overview
        The Sensor library provides applications with a consistent interface to simultaneously access up to 64 sensors connected to the hardware platform.
      - Opening and closing a connection to a sensor unit
        Applications use a handle provided through the Sensor API to access each of the logical sensor units that are configured in the sensor configuration file.
      - Starting and stopping a sensor unit
      - Opening and closing a connection to an interim data unit
        Applications use a handle provided through the Sensor API to access each of the interim data units that are configured in the interim data configuration file.
      - Starting an interim data unit
      - Accessing sensor data and status
        Applications can access the sensor's data and status by binding callback functions or events that are of the structure sigevent to sensor events that are of particular interest.
      - Publishing interim data
        Publishers are applications that generate interim data information for other applications.
      - Subscribing to interim data
        Subscribers are applications that use interim data that publishers generate.
      - Recording data from a sensor
        Applications can record the data that's streaming from a sensor to a file.
      - Querying sensor information
      - Using external clocks
        Sensor timestamps can be based on a reference time provided by an external clock library.
      - Using external sensor drivers
        Sensors that aren't already supported by the Sensor Framework for QNX SDP can be provided by an external sensor driver library.
      - Sensor Library Reference
        The Sensor library provides applications with a consistent interface to interact with sensors connected to the system.
        sensor_api.h
        The definitions, data types, and functions to access sensors, receive and store data from them, and handle sensor events.
        sensor_gps_imu.h
        The definitions of the data formats for GPS and IMU sensors.
        sensor_interim_data.h
        The definitions and functions to work with interim data.
        sensor_lidar.h
        The definitions of the data formats for lidar sensors.
        sensor_radar.h
        The definitions of the data formats for radar sensors.
        sensor_flag_radar_track_polar_t
        Bit settings for the sensor_buffer_t flag field for data of type SENSOR_FORMAT_RADAR_POLAR
        sensor_flag_radar_track_spherical_t
        Bit settings for the sensor_buffer_t flag field for data of type SENSOR_FORMAT_RADAR_SPHERICAL
        sensor_radar_object_class_t
        Class of the object
        sensor_radar_track_flags_t
        Flags providing information about the tracked object
        sensor_radar_track_polar_t
        Data payload format for data of type SENSOR_FORMAT_RADAR_POLAR
        sensor_radar_track_spherical_t
        Data payload format for data of type SENSOR_FORMAT_RADAR_SPHERICAL
        external_sensor_api.h
        The definitions and functions to use the External Sensor library.
      - Glossary
        This is a list of terms commonly used in the context of the Sensor library.
  - Sensor Framework Services
- 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.

sensor_flag_radar_track_polar_t

Bit settings for the sensor_buffer_t flag field for data of type SENSOR_FORMAT_RADAR_POLAR

Synopsis:

#include <sensor/sensor_radar.h>

typedef enum {
    FLAG_RTP_DISTANCE = 1,
    FLAG_RTP_SPEED = 2,
    FLAG_RTP_TRACK_ID = 4,
    FLAG_RTP_AZIMUTH = 8,
    FLAG_RTP_FLAGS = 0x10,
    FLAG_RTP_ACCELERATION = 0x20,
    FLAG_RTP_WIDTH = 0x40,
    FLAG_RTP_LATERAL_SPEED = 0x80,
    FLAG_RTP_VALIDITY_LEVEL = 0x100
} sensor_flag_radar_track_polar_t;

Data:

FLAG_RTP_DISTANCE: The distance field is present.
FLAG_RTP_SPEED: The speed field is present.
FLAG_RTP_TRACK_ID: The track_id field is present.
FLAG_RTP_AZIMUTH: The azimuth field is present.
FLAG_RTP_FLAGS: The flags field is present.
FLAG_RTP_ACCELERATION: The acceleration field is present.
FLAG_RTP_WIDTH: The width field is present.
FLAG_RTP_LATERAL_SPEED: The lateral_speed field is present.
FLAG_RTP_VALIDITY_LEVEL: The validity_level field is present.

Library:

libsensor

Description:

This enumeration represents bits in the flag field that when set, indicate the data fields in the sensor_radar_track_polar_t structure that are defined for this buffer.

Page updated: March 12, 2026