[Project Tracker] Sensor configuration display UI

junwoo091400 commented 2 years ago

Describe problem solved by the proposed feature

Currently it is hard to figure out which sensors are connected where, with which configuration and which priority (e.g. CAL_MAG0_PRIO) in a single view. For example during my boat project build, I wasn't sure if I needed to set the priority of magnetometer manually or not.

This is also quite related to the calibration pain addressed in the issue #19459. What can we do to improve user experience for setting up the sensors? If so, which part should be addressed and how?

What could be great (in my opinion) could be something like this in QGC (it won't be a literal text output like this, but just for giving some idea):

<mag-type> | <mag-orientation> | <mag-priority> | <mag-protocol?> # First mag sensor
<mag-type> | <mag-orientation> | <mag-priority> | <mag-protocol?> # One for the second mag
<baro-type> |              | <baro-priority> | <baro-protocol>
<gyro-type> | <gyro-orientation> | <gyro-priority> | <gyro-protocol>

But I am also not sure what others expectation / needs are, so any feedback would be appreciated!

Describe your preferred solution

@davids5 pointed out that transferring device tree information over to QGC could be a solution. Could you elaborate on that?
@dagar pointed out that having a unified view in general would be good. Could you let me know if a view I suggested above is similar to what you have imagined?

davids5 commented 2 years ago

@davids5 pointed out that transferring device tree information over to QGC could be a solution. Could you elaborate on that?

The topology of the system is described in Device Tree that is a hierarchy of buses device and pins.

this is far form DT but is gives and example of what bus a device is on, and in the case of these memories how they are partitioned.

junwoo091400 commented 2 years ago

@Igor-Misic I believe you were working with Device Trees, do they exist in NuttX yet?

Igor-Misic commented 2 years ago

@Igor-Misic I believe you were working with Device Trees, do they exist in NuttX yet?

As far as I know, there were just some ideas and no one worked at device tree yet.

algora-pbc[bot] commented 1 year ago

💎 $10 bounty • Junwoo Hwang

💎 $10 bounty • PX4 Autopilot

Steps to solve:

Start working: Comment /attempt #19970 with your implementation plan
Submit work: Create a pull request including /claim #19970 in the PR body to claim the bounty
Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to PX4/PX4-Autopilot!

Add a bounty • Share on socials

Attempt	Started (GMT+0)	Solution
🟢 @junwoo091400	Nov 5, 2023, 8:28:11 AM	#19568
🔴 @JugalIwPtl	Jun 22, 2024, 6:26:38 AM	WIP
🟢 @RS-labhub	Nov 10, 2024, 9:29:10 AM	WIP

RS-labhub commented 2 weeks ago

/attempt #19970

Why don't we make it simply like the below??

Sensor Type	Orientation	Priority	Protocol	Status
Magnetometer #1	XYZ (default)	Auto (Highest)	I2C	✅ Connected
Magnetometer #2	YZX (custom)	2nd Priority	SPI	⚠️ Adjust Priority
Barometer	N/A	Auto	I2C	✅ Calibrated
Gyroscope #1	XZY (custom)	Primary	CAN	✅ Connected
Gyroscope #2	ZYX (inverted)	Secondary	CAN	⚠️ Needs Calibration

(I built this table using chatGPT by proposing my solution)

Algora profile	Completed bounties	Tech	Active attempts	Options
@RS-labhub	4 bounties from 1 project	JavaScript, Python, Go & more		Cancel attempt

PX4 / PX4-Autopilot