NSV w/ RT-FIFO has strange behavior

[viScience]

After enabling RT-FIFO (single element) on a cRIO hosted NSV my previously working application is failing to read the correct value of this NSV.

I can see and verify the NSV value using the DSM but within my labview exe it does not read it correctly (it is a boolean value and always returns False even when it is True)

Another strange aspect to this is that the same LabVIEW exe runs fine when executed as a vi within the development environment.  I have a conflicting mix of  information regarding whether or not

NSV w/RT-FIFO create separate client side buffers for multiple readers.  This is stated to be the case in the famous SV white paper from NI but elsewhere in the discussion forums I have heard that

it actually does not work that way.  In any event, I still do not understand why this would cause the problem I am seeing.  Once again, shot in the foot with NSV's due to inconsistant behavior and/or incorrect documentation.

[Christian_L]

Is the EXE that is causing this bad behavior running on Windows or on the cRIO target?

I tried reproducing this behavior in a simple example and could not see the same effect. Can you put together a simplified example that shows the behavior that you can share with us?

[viScience]

Hi Christian,

Thanks for looking into this.  The exe I was refering to was running on Windows with the NSV's hosted on the cRIO.

Perhaps I am expecting too much from the PSP to keep all my various readers updated with the latest NSV value.

My cRIO readers are using the SV API and I verified that they are working but on the windows side I am using tags

which do not update correctly.  I will see if I can find some time to revisit this and put together an example...for the moment I have disabled the RT-FIFO

option.