VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Inline HW Interface and block data refs

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.

0 Kudos
Message 1 of 6
(3,905 Views)

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

0 Kudos
Message 2 of 6
(3,894 Views)

Github page not found...

0 Kudos
Message 3 of 6
(3,888 Views)

Also, my understanding is that RT FIFOs are only available with asych custom devices and not inline HW devices.

0 Kudos
Message 4 of 6
(3,887 Views)

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...

0 Kudos
Message 5 of 6
(3,883 Views)

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

0 Kudos
Message 6 of 6
(3,861 Views)