Closed Karl-G1 closed 2 years ago
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.
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.
Asynchronous execution results are better. I have a question about theory of operation. When two MIL-STD-1553 custom devices are running, are they works parallel like image below? Execution time is approximetely 2500us at this operation. If it is like that what's the disadvantegas of this? There is one more thing I don't understand. How exactly does decimation work and what are it's advantages?
What does this Pull Request accomplish?
Why should this Pull Request be merged?
Enable users with lots of Rx 1553 message endpoints in a system to not block the PCL if it is permissible for this custom device to run at an effectively reduced loop rate.
With 3x custom devices and a PCL rate faster than the custom device can execute, there is noticeable contention in the Rx and Tx execution units visible due to jitter spikes in their execution duration. This points to potential improvements to reducing contention, but this is still a helpful addition for users whose system would fail timing for higher-speed tasks.
What testing has been done?
Hand testing plus ran automated tests against the ATS hardware.
VI Tester results
![image](https://user-images.githubusercontent.com/31290917/192001374-c379149a-ab91-478d-9ad2-7f773b86e0f8.png)HP Loop Duration with Inline custom device execution on 3x instances
![image](https://user-images.githubusercontent.com/31290917/192001537-9ad93a11-4ab7-408e-aeb0-5652cb429255.png)Execution duration of Rx and Tx with 3x instances and Rx async
![image](https://user-images.githubusercontent.com/31290917/192001805-fdea8b99-3f31-4e75-a100-ac220062c010.png)