SystemLink Idea Exchange

Idea

Host the full Python SDK package on PyPI to support pip install operation. There is  a PyPI package for Systemlink, but it currently only provides the Tags API. 

Motivation

There is a helpful set of tools that can leverage the Test Monitor API, Files API, etc. for interacting with Systemlink data, but as of now, the only way to access those files is by installing the Systemlink Client via NI Package Manager, and then referencing the python modules via absolute path.

It would be nice if we could pip install these packages into a virtual environment as we develop utilities that leverage them.

See also: https://forums.ni.com/t5/SystemLink/pip-install-systemlink-sdk/m-p/4200716

Currently a great deal of functionality is available via the SystemLink API. This is a very valuable tool. However, it is quite difficult to utilize these features via LabVIEW and build out integrations within the NI ecosystem. Tight integration between hardware and software has been a staple of NI and it would greatly benefit us as LabVIEW developers if we could more readily access the full feature set available in SystemLink. Further, when putting together programmatic implementations it often leads to partial solutions that are fragile and limited in scope. 

Allow to copy a package in one feed (say a dev feed) to another (say a release feed) so that you don't need to publish to two different feeds from a LV Project, but can still have devices only able to see one feed (release) and not the other feed (dev).

We noticed that when there is an ATML report included in Systemink, one needs to double-click the report log to check for the parameters additional results pulled from a TestStand as parameters with the log box checked. 

It seems like this information should be accessible without double click the test. It might be a good idea to use some additional blocks like the following:

Or to explicitly include the parameters and values. 

Currently, you can only read one message from session your queue at a time through the SystemLink message service (nimessage/v1/). It would be nice if it was possible to read multiple messages with a single HTTP call.