From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
06-06-2016 07:42 PM
Let us say I want to create a custom device with an inline HW inteface setup. In the initialization state. I have a static VI reference to a Main process. I use this static VI reference to pass the channel block data references to the main process VI for which the static reference is for.
Question: Is this data pass "by value" or "reference"? I am trying to understand how could such a VI continually receive the latest channel data values.
06-07-2016 06:19 AM
For inspiration look f.e. at following custom device:
https://github.com/NIVeriStandAdd-Ons/CANopen-Master-Custom-Device
It has inlined part and asynchronous part. Communication is handled by RT FIFO.
CLA, CTA, CLED
06-07-2016 08:02 AM
Github page not found...
06-07-2016 08:12 AM
Also, my understanding is that RT FIFOs are only available with asych custom devices and not inline HW devices.
06-07-2016 08:35 AM - edited 06-07-2016 08:43 AM
How would I get RT FIFOs into my inline HW interface RT Driver?
[nevermind] It appears I do not have the LabView Real-Time Module installed. The RT FIFO functions are a part of this...
06-08-2016 02:48 AM
just remove the space at the end of the link and you will see it at GitHub
You should have LV RT if you are using custom devices on RT target.
The RT FIFO are created by this custom device and owned by the custom device...
CLA, CTA, CLED