Create Ballard ARINC 429 fork of template

[buckd]

• [x] This contribution adheres to CONTRIBUTING.md.

  What does this Pull Request accomplish?

  Modifies the custom device such that the Ballard ARINC 429 implementation can be used alongside the template implementation.

  • Update GUIDs such that VeriStand can distinguish between the custom devices.
  • Update installation paths such that the installs do not conflict.
  • Update the custom device menu and main page names.
  • Rename PPLs such that they can be loaded simultaneously. The underlying lvlibs are not renamed.
  • Rename the custom device lvlibs such that they can be loaded simultaneously. The LLBs are not renamed.
  • Update control files to generate Ballard ARINC 429-specific packages.

  Why should this Pull Request be merged?

  The changes here are being submitted to a ballard_arinc_429 branch, which will contain a Ballard ARINC 429 specific implementation of the template. The ballard_arinc_429 branch should never be merged into main.

  I am proposing that we do not squash merge this change, because the individual commit history here is potentially helpful.

  What testing has been done?

  Configured a system definition with both the Ballard ARINC 429 implementation and template implementation, and confirmed I could deploy them both concurrently and that I could alternate between their pages in System Explorer.

  Additional information

  Why are there still things with "Communication Bus Template" or "Communication Bus" in the name?

  1. I tried to keep this PR as small as possible to make it reviewable. Only things which needed to be renamed were renamed.
  2. I did not want to introduce unnecessary future merge conflicts. E.g. the PPLs have been renamed, but the top-level libraries in the PPLs have not been renamed, because renaming the lvlibs would force every VI to be re-saved.
  3. I would argue that most things with "Communication Bus [Template]" in the name should have the string omitted entirely, rather than replacing it. Just because the Custom Device Wizard inserted this string does not mean we need to perpetuate it -- especially if a user would be expected to manually update it.

The changes contained in the PR are based on the guide from #26. I have some updates to make to this document, but am putting this PR here for someone to test on a machine that is not mine to make sure there is nothing specific to my machine allowing this to work.

[rtzoeller]

It looks like you renamed build specs in the PPL project, but did not update their names in build.toml.

[niveristand-diff-bot]

Bleep bloop!

LabVIEW Diff Robot here with some diffs served up hot for your pull request.

Notice something funny? Help fix me on my GitHub repo.

Ballard ARINC 429 Engine.lvlib--RT Driver VI.vi.png


Ballard ARINC 429 Shared.lvlib--Constants.vi.png


Ballard ARINC 429 System Explorer.lvlib--ActionVIOnCompile.vi.png


Ballard ARINC 429 System Explorer.lvlib--Compile Asynchronous Execution Units.vi.png


Ballard ARINC 429 System Explorer.lvlib--Compile Inline Execution Units.vi.png


Ballard ARINC 429 System Explorer.lvlib--Export Configuration RTM.vi.png


Ballard ARINC 429 System Explorer.lvlib--Get Item GUID.vi.png


Ballard ARINC 429 System Explorer.lvlib--Import Configuration RTM.vi.png


Ballard ARINC 429 System Explorer.lvlib--Initialization VI.vi.png


Ballard ARINC 429 System Explorer.lvlib--Page Wrapper.vi.png


Ballard ARINC 429 System Explorer.lvlib--RunTimeMenu Custom Population.vi.png


Ballard ARINC 429 System Explorer.lvlib--RunTimeMenu Wrapper.vi.png


Communication Bus Template Scripting.lvlib--Constants.vi.png


Copy .LLB to NI VeriStand dir.vi.png


Copy PPLs to NI VeriStand dir.vi.png