shared variable with RT FIFO initial value

[viScience]

The Good News:  It is possible to set the initial value of a NSV on an RT target.

The Bad News:  There does not seem to be anyway to determine when this initial value is available from the SV server.

For some reason there an initializing period of time that the PSP client (your RT application) needs to connect to the SV server to obtain the

current value of a NSV.  You can try looping until the warning message  (Warning -1950679027 occurred at an unidentified location

Possible reason(s):

LabVIEW:  (Hex 0x8BBB000D) NI-PSP has not connected to the server yet)

goes away but this does not alway guaranteee that the next transaction will be good.

I think NI should provide a utility that can be called that forces this initialization process to occur.  Putting the burdon on the LV developer

in this case is bound to be creating many frustrated engineers.

[DiscoBall]

Hi Sachsm,
 
While I do not have another work around for you at the moment I do want to note that the confusing behavior of Network Shared Variables has been previously noted in Corrective Action Request (CAR) #123473 and #123474. To add more weight to the CAR I suggest filing a Product Suggestion and mentioning the above CAR numbers when stating your application

For others that might not know, Shared Variable do have many quality codes that can understood from KnowledgeBase 42UIDM8J Shared Variable Quality Codes.

[LabBEAN]

This sure would be handy.  Any update on the CARs or clever work arounds?

[viScience]

This behavior seems to have improved in LV2010, in my application I no longer have this issue.  But as LabBEAN points out, it would be nice to see a published CAR to verify what

changes, if any, were actually made.

[DiscoBall]

Hello all,

CARs 123473 is closed as fixed for LabVIEW 2009. CAR 123474 is still being worked on....