You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
DEV_ID parameters are currently the main way in ardupilot to identify sensors from a GCS
Describe the solution you'd like
I''d like that the AP_TemperatureSensor library had its own DEV_ID parameters, so users can easily tell if a temperature sensor is attached and how/which one.
This would allow us to list temperature sensors alongside the sensors we already detect and display in BlueOS, in a standardized way.
Currently we need to do something like this
The text was updated successfully, but these errors were encountered:
Feature request
Is your feature request related to a problem? Please describe.
DEV_ID parameters are currently the main way in ardupilot to identify sensors from a GCS
Describe the solution you'd like
I''d like that the AP_TemperatureSensor library had its own DEV_ID parameters, so users can easily tell if a temperature sensor is attached and how/which one.
This would allow us to list temperature sensors alongside the sensors we already detect and display in BlueOS, in a standardized way.
Currently we need to do something like this
The text was updated successfully, but these errors were encountered: