Describe the bug
As a template user, it is really frustrating when there are debugging elements in the template that wind up being the focus of a debugging/diagnostics effort. In this case, @Karl-G1 noted performance issues (max rate limited to 100 Hz) when testing the Ballard MIL-STD-1553 custom device.
To Reproduce
Steps to reproduce the behavior in an instantiated custom device:
Increase the loop rate to 1 kHz.
Deploy the system definition.
Take note of the actual loop rate.
Actual loop rate topped out at 100 Hz for the 1553 custom device before tracing was conditionally disabled. Furthermore, the actual loop rate showed regular drops to 50 Hz.
Expected behavior
I expect the custom devices generated from this template to be able to achieve some healthy percentage of the theoretical maximum for the supported protocol.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: Linux RT
Version: VeriStand 2020 R6 running on host and target.
Describe the bug As a template user, it is really frustrating when there are debugging elements in the template that wind up being the focus of a debugging/diagnostics effort. In this case, @Karl-G1 noted performance issues (max rate limited to 100 Hz) when testing the Ballard MIL-STD-1553 custom device.
To Reproduce Steps to reproduce the behavior in an instantiated custom device:
Expected behavior I expect the custom devices generated from this template to be able to achieve some healthy percentage of the theoretical maximum for the supported protocol.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context https://github.com/ni/niveristand-ballard-milStd1553-custom-device/pull/157