/pps/qnx/device/<device>

Directory of status objects for devices attached to the head unit

Publishers: Device publishers (e.g., usblauncher)
Note: For more information about all the device publishers and how they interact with PPS, see the Device Publishers Developer's Guide.
Subscribers: Any app

Overview

When USB sticks are connected to the computer, PPS objects appear under the /pps/qnx/device/ directory to provide status information and control. For USB devices, object names are of the form:

usb-bus_number.device_number

Note: If usblauncher is called with the -S option, then the object name will also include the stackno attribute before the bus_number (e.g., usb-0.0.3).

For device control objects, see /pps/qnx/device/<device>_ctrl.

Sample USB object

[n]@usb-0.0.3
bus::USB
busno::0x00
configuration::1
configurations::1
device_class::0xff
device_protocol::0x00
device_subclass::0xff
devno::0x03
drivers_matched::1
drivers_running::1
manufacturer::D-Link Corporation
max_packet_size0::64
product::DUB-E100
product_id::0x3c05
serial_number::000001
stackno::0
topology::(1,3),(0,0)
upstream_device_address::1
upstream_host_controller::0
upstream_port::3
upstream_port_speed::High
vendor_id::0x2001

Attributes for USB objects

Attribute	Description
`bus`	Type of bus (`USB`).
`busno`	Bus number (in hex).
`configuration`	The device's USB configuration that is selected before launching suitable drivers.
`configurations`	Number of configurations.
`device_class`	Device class ID (in hex).
`device_protocol`	Device protocol (present only if `device_class` is not `0x00`).
`device_subclass`	Device subclass ID (present only if `device_class` is not `0x00`).
`devno`	Device number.
`drivers_matched`	Number of drivers that match the device, based on rules in the usblauncher configuration file (`0` means the device is unsupported). For details about these rules, see "Configuration files" in the Device Publishers Developer's Guide.
`drivers_running`	Number of drivers launched for the device, which can be less than `drivers_matched` if some drivers haven't been started yet or have terminated (possibly in error).
`manufacturer`	Device manufacturer.
`max_packet_size0`	Maximum packet size.
`product`	Product name (e.g., DUB-E100).
`product_id`	OEM product ID (in hex).
`serial_number`	Product serial number.
`stackno`	The USB stack number as specified with the -S command-line option for usblauncher (e.g., `usblauncher -S 0`).
`status`	Device status. Normally, this field is present only when the device is being reset; the field is deleted when the reset completes. For "bad" devices (i.e., devices that io-usb couldn't assign a device number), this field will contain: `48 (Not supported)`. When an overcurrent condition is detected, this field will contain: `-1 (Overcurrent)`.
`topology`	Duplicates the immediate upstream device and port numbers (`devno,upstream_port`) and also provides the upstream information for the hub chain. For example, `topology::(2,1),(0,2)` indicates the device is attached to hub device 2 port 1, which in turn is connected to root port 2.
`upstream_device_address`	USB address where the device is connected. When connected to a host controller, this is `0`; when connected to a USB hub, this is the hub's device address.
`upstream_host_controller`	Host controller number (usually `0`). If you have multiple USB controllers, this is the number of the controller that detected the device.
`upstream_port`	Port number (hub port number or `0` if connected to host controller).
`upstream_port_speed`	Port speed: `Full` `High` `Low`
`vendor_id`	Manufacturer ID (in hex).