LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

timeout of shared variable (write)

I am using a shared variable (boolean) between two independent applications, A and B.
Application A writes to the variable, while application B reads from it, and we can configure a timeout for the read operation in B.


The timeout flag only becomes True after B initiates the read and the specified timeout period elapses.
If B reads the value for the first time a long time after A has written it, B retrieves the stale value that still remains on the network.
However, there is no timeout setting available on the write side in application A.


Question: How can we configure the system so that B discards data written by A a long time ago?

 

Using a full flush operation might work, but we are concerned that it could affect other shared variables in the system.


Thank you for your guidance.

0 Kudos
Message 1 of 3
(100 Views)

I don't really understand what you are talking about. 

  • How are you representing (show some LabVIEW code) the "shared Boolean variable"?  Show us how this is represented in LabVIEW, show us the code you use to Write this variable, and to Read it.
  • What are "application A" and "application B"?  Are these parallel Loops (or sub-VIs) in a single LabVIEW program?  Are you communicating (and if so, how) between two LabVIEW programs running independently on the same PC?  Are the two programs on different PCs?
  • What is "the timeout flag"?  Is it in A, in B, or somewhere else?  Show the LabVIEW code.
  • What version of LabVIEW are you using?  Note that longtime users of LabVIEW might not have LabVIEW 2025 on their machines ...
  • What do you mean by a "full flush operation" (again, show the LabVIEW code for a "full flush operation").

Bob Schor

0 Kudos
Message 2 of 3
(82 Views)

Thank you for your interest. Upon reflection, I realize it was a rather foolish question.

Please disregard it.

 

labmaster.

0 Kudos
Message 3 of 3
(20 Views)