Add Coupling Mode and Bus Selection to System Explorer, Scripting and Engine

[papowerNI]

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

• Adds Bus Selection and Coupling Mode to the Device Parameters.
• Also cleans up Initialize Bus Controller, although not related.

Why should this Pull Request be merged?

Bus Coupling is necessary for AIM 1553.

What testing has been done?

Test suite works (device parameters is already tested, so this gets lumped into those tests).
Also ran manual tests to read and write a word from Ballard -> AIM. When coupling mode is incompatible, the read/write does not go through, but when the coupling mode is compatible, it does.

Since a system test requires Ballard->AIM I did not add a system automated test for this. It could be added to a cross-compatible system test suite in the future.

With Correct Coupling:

With Incompatible coupling:

[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.

AIM MIL-STD-1553 Engine.lvlib--Custom Device.lvlib--Initialize Bus Controller.vi.png

AIM MIL-STD-1553 Engine.lvlib--Custom Device.lvlib--Initialize Hardware.vi.png

AIM MIL-STD-1553 Engine.lvlib--Implementation.lvlib--Shared Resources.lvclass--Construct.vi.png

AIM MIL-STD-1553 Hardware API.lvlib--Initialize 1553 Module.vi.png

AIM MIL-STD-1553 Hardware API.lvlib--Set Device Coupling.vi.png

AIM MIL-STD-1553 Scripting.lvlib--Constants.vi.png

AIM MIL-STD-1553 Scripting.lvlib--Get Device Parameters.vi.png

AIM MIL-STD-1553 Scripting.lvlib--Set Device Parameters.vi.png

AIM MIL-STD-1553 System Explorer.lvlib--Implementation.lvlib--Device Parameters to Configuration Elements.vi.png

AIM MIL-STD-1553 System Explorer.lvlib--Implementation.lvlib--Initialize.vi.png

AIM MIL-STD-1553 System Explorer.lvlib--Implementation.lvlib--Main Page.vi.png

Create Execution Unit.lvclass--test BC + RTs.vi.png

Create Execution Unit.lvclass--test BC Only.vi.png

Create Execution Unit.lvclass--test RTs Only.vi.png

Deployment.lvclass--globalSetUp.vi.png

Logging Loopback.lvclass--Script Custom Device.vi.png

Loopback.lvclass--globalSetUp.vi.png

Scripting.lvclass--test Get-Set-Get Device Parameters.vi.png

[buckd]

• Bus Selection.ctl and Coupling Mode.ctl need to be added to the project.

[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.

AIM MIL-STD-1553 Engine.lvlib--Custom Device.lvlib--Initialize Bus Controller.vi.png

AIM MIL-STD-1553 Engine.lvlib--Custom Device.lvlib--Initialize Hardware.vi.png

AIM MIL-STD-1553 Engine.lvlib--Implementation.lvlib--Shared Resources.lvclass--Construct.vi.png

AIM MIL-STD-1553 Hardware API.lvlib--Initialize 1553 Module.vi.png

AIM MIL-STD-1553 Hardware API.lvlib--Set Device Coupling.vi.png

AIM MIL-STD-1553 Scripting.lvlib--Constants.vi.png

AIM MIL-STD-1553 Scripting.lvlib--Get Device Parameters.vi.png

AIM MIL-STD-1553 Scripting.lvlib--Set Device Parameters.vi.png

AIM MIL-STD-1553 System Explorer.lvlib--Implementation.lvlib--Device Parameters to Configuration Elements.vi.png

AIM MIL-STD-1553 System Explorer.lvlib--Implementation.lvlib--Initialize.vi.png

AIM MIL-STD-1553 System Explorer.lvlib--Implementation.lvlib--Main Page.vi.png

Create Execution Unit.lvclass--test BC + RTs.vi.png

Create Execution Unit.lvclass--test BC Only.vi.png

Create Execution Unit.lvclass--test RTs Only.vi.png

Deployment.lvclass--globalSetUp.vi.png

Logging Loopback.lvclass--Script Custom Device.vi.png

Loopback.lvclass--globalSetUp.vi.png

Scripting.lvclass--test Get-Set-Get Device Parameters.vi.png