Jump to content

pconrad

Members
  • Posts

    2
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2012
  • Since
    2008

pconrad's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hmm... I think I got a partial answer... If I make the shared variable reference "target relative", it appears to bind it to the PSP server on the localhost.
  2. I'm using a LabVIEW VI to control a 3rd party application (3PA, for short). This 3PA has a built-in scripting language that supports DLL calls. I needed a way to pause the 3PA script and have it wait for LabVIEW to do something. I wrote a LabVIEW DLL that uses a Shared Variable to pass a 'go-ahead' boolean between my master VI and the DLL, similar to an interrupt. The 3PA calls a DLL function that waits until the 'go-ahead' signal clears. My master VI sets the 'go-ahead' signal when it's ready for the 3PA to continue. Everything seems to be working, but this was the first time I ever had to work with "network published" shared variables. * How exactly does the DLL know which set of shared variables it should be using? * Does it have a fixed path somewhere to the lvlib that contains the variables? * Since these are network published variables, do I need to do anything to limit them to the localhost? Thanks! PC
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.