HardwareReport: features to be implemented

[IamPete1]

Somewhere to note down all the features that we would like:

• GPS identification (HardwareReport: Added GPS #133)
  Currently there is no way to identify the connected GPS from parameters, if using a log we can look in the MSG log and find the detection message, such as GPS 1: specified as UAVCAN1-3
• Param changed in flight. HardwareReport: show parameter changes during log #97
• Add OSD to minimize param options.
  There are lots of OSD parameters, they should be excluded in the minimal param output and checkboxes added to allow them to be included. This would add a OSD section here:
  
  I'm not sure what the sub-options would be, maybe for each screen.

[SantamRC]

@IamPete1 Can you explain the other two features that needs to be added here. If I can contribute

[IamPete1]

@IamPete1 Can you explain the other two features that needs to be added here. If I can contribute

I added some more detail.

[SantamRC]

Hey @IamPete1 for the OSD parameters are we talking about such parameters?

PARM, 96586979, MSP_OSD_NCELLS, 0, 0
PARM, 96539561, OSD_TYPE, 0, 0

I found them in the flight logs, should we add these in checkboxes?

[IamPete1]

Hey @IamPete1 for the OSD parameters are we talking about such parameters?

PARM, 96586979, MSP_OSD_NCELLS, 0, 0
PARM, 96539561, OSD_TYPE, 0, 0

I found them in the flight logs, should we add these in checkboxes?

We have hundreds of parameters for each element in each screen. I think a top level one for type and then one for each screen. you can fund them all in the full list on the wiki: