Is your feature request related to a problem? Please describe.
Some custom devices based on the template in this repo may require use of shared resources across Execution Units (hardware sessions, common queue references, etc.). The template should provide an interface and calling code to access this interface so users don't have to re-implement a similar pattern in slightly different ways.
Describe the solution you'd like
The Ballard ARINC 429 custom device has implemented an interface, in PR 25, as described above and should be implemented in the template.
Describe alternatives you've considered
Nothing, although we could look at potential improvements to what the Ballard ARINC 429 custom device implemented.
Is your feature request related to a problem? Please describe. Some custom devices based on the template in this repo may require use of shared resources across Execution Units (hardware sessions, common queue references, etc.). The template should provide an interface and calling code to access this interface so users don't have to re-implement a similar pattern in slightly different ways.
Describe the solution you'd like The Ballard ARINC 429 custom device has implemented an interface, in PR 25, as described above and should be implemented in the template.
Describe alternatives you've considered Nothing, although we could look at potential improvements to what the Ballard ARINC 429 custom device implemented.
Additional context None.