ni / niveristand-data-sharing-framework-custom-device-plugins

Protocol plugins for the Data Sharing Framework VeriStand custom device.

Data Sharing Framework Plugins

The Data Sharing Framework Plugins provides built components to the Data Sharing Framework and its VeriStand Custom Device for reflecting data between applications.

Validated Plugin and Target Support

This repository contains three Data Sharing Framework plugins:

1. UDP
2. GE Reflective Memory
3. RDMA

Each plugin supports a different set of targets. The following table displays the plugin support status for each target type.

Plugin	Windows	PXI Linux x64	cRIO Linux x64
UDP	✔️	✔️	✔️
GE Reflective Memory	✔️	❌	➖
RDMA	➖	✔️	➖

• ✔️ - Supported, validated, and building.
• ❌ - Potentially supported, not currently validated or building.
• ➖ - Not supported.

LabVIEW Source Code Version

LabVIEW 2020

Dependencies

Running the plugins with the custom device

• VeriStand 2020 or later
• NI-VISA 20.0 or later
• Optional (if using RDMA): NI-RDMA 21.5 or later
• Data Sharing Framework Custom Device

Developing or building from source

• DSF Core.lvlibp from Data Sharing Framework (See note below)
• LabVIEW 2020 or later
• LabVIEW Real-Time Module
• VeriStand Custom Device Development Tools
  • Install the latest package from the release page
• VeriStand Custom Device Testing Tools
  • Install the latest package from the release page

Note: You must build and copy all Data Sharing Framework core packed project libraries into the source location before attempting to modify or build the plugins. For more information on building components manually, refer to Manual Build Instructions for the Data Sharing Framework.

Git History & Rebasing Policy

Branch rebasing and other history modifications will be listed here, with several notable exceptions:

• Branches prefixed with dev/ may be rebased, overwritten, or deleted at any time.
• Pull requests may be squashed on merge.

License

The Data Sharing Framework is licensed under an MIT-style license (see LICENSE) unless otherwise specified. Other incorporated projects may be licensed under different licenses. All licenses allow for non-commercial and commercial use.

niveristand-data-sharing-framework-custom-device-plugins's Issues

consider change to build process utilizing pseudopaths

I saw Stephen posted this on the community and lavag:
https://forums.ni.com/t5/Community-Documents/Resolution-of-Pseudopaths-in-LabVIEW-Per-Target-Invocation-of/ta-p/4087124?profile.language=en
As I understand it this would make component builds a lot simpler, as the code would load up the appropriate ppl based on super secret internal labview search paths.

Describe the solution you'd like
Right click -> build :)

Describe alternatives you've considered

Additional context