Open AndersonRayner opened 3 years ago
Could be done with a custom (bsp) tab next to data viewer with a table view.
On 27. May 2021, at 02:48, AndersonRayner @.***> wrote:
Both the ArduPilot and PX4 import scripts import the parameter values stored in the logs. Maybe we could come up with a good way of displaying those? Currently they are imported into the fds struct as a PARAM field
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/flyingk/kVIS3/issues/123, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAQS4ZVZFFTL6TD2EQGWRTLTPWJGXANCNFSM45TE7WQQ.
Good idea. I think prototyping internally within the APM or PX4 bsp could be a good proof of concept, but might be worth thinking about introducing it into the fds file structure formally so all BSPs could use the functionality.
Not sure if not too bsp specific… maybe give the ads field a bsp_ prefix for now.
Examples how to register a tab in bsp_id and the required ui definition are in uavmainframe bsp.
On 28. May 2021, at 20:32, AndersonRayner @.***> wrote:
Good idea. I think prototyping internally within the APM or PX4 bsp could be a good proof of concept, but might be worth thinking about introducing it into the fds file structure formally so all BSPs could use the functionality.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/flyingk/kVIS3/issues/123#issuecomment-850595447, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAQS4ZWR2EYSXPORCI2CX5LTP7OS5ANCNFSM45TE7WQQ.
Both the ArduPilot and PX4 import scripts import the parameter values stored in the logs. Maybe we could come up with a good way of displaying those? Currently they are imported into the fds struct as a PARAM field