shared variable failed deployment

[Hillary_C_E]

Hi Bob,

So, I think its related to the path you are referencing. I have 2 ideas.

1. You've specified the path incorrectly. When you install your exe on your computer, does the file path location of the library change? This KnowledgeBase talks about VI location versus EXE location.

2. In previous posts, you reference the library but without the .lvlib. The invoke node might not be able to find the file because it is looking for the file without the .lvlib.

In either case, try creating the exe with the path of the library as a control on the front panel. Then when running the exe browse to the actual location on the machine where your exe is running. Do you still get the same error?

[EWTech]

Hillary,

The path to the SingleBool.lvlib seems to be an issue. I recieve the following error:

shared variable write in tiny.vi -> Timed Structure(es): L43127408<append> This warning occured while writing \\My COmputer\SingleBool\flash (\\localhost\SingleBool\Flash).

Both paths are wrong and I'm having trouble editing either the installer or the executable build entries in the project as if it never changes after editing the tiny.vi code.

Bob

[EWTech]

Hillary,

I tried using a control for the path to the library file. On the server (write only) side this worked ... sort of. I added the missing variables with the variable manager and the thing write to it. What des not work is for any of the variables to be read across the network. I tried sharing the path to the read version of the library and pointing to that and it failed. I tried adding variable using local versions of the variables tied to the one on the server and that failed.

Any suggestions? I do know that there is a tag engine running across the network using LabVIEW 7.1.1 but I shut it down long enough to try this. That was not the problem in this case as the LV application was down long enough for the effort above. Our NI rep has said he'll take a look later this week. I really don't want to write this in C++ and C# but I will if I have to just to send the data around through the network. The C# apps I've written have no trouble serving and saving data to SQL Server over the network as things are now.

Bob

[Hillary_C_E]

Hi Bob,

So, you're using LabVIEW 7.1.1?

Where is the library you're referencing, on your original computer or your end computer?

How are you referencing your host computer in the executable? Are you referencing it by IP or localhost?

Let me know if you can't get this worked out with your sales engineer.

[EWTech]

Hillary,

I am not using LV 7.1.1 on this project. It is running a program on the network using data sockets.

In either case I was able to deploy the variables. Alan Loprete, our local rep. here (Columbia office) showed me that the Invoke Node function was not required to deploy the variable. It worked fine without it and trying to open the included library separately caused the executable to gak. Once I removed the offending fuctions and reworked the panel as needed it worked fine. It deploys the variables as required. Since the display panel is just that and does no calculations at all it's just made up of indicators bound to the shared variables on the server machine - no code at all other than a reasonable update loop. Works like a champ. All *processing* is done on the server end with a C# DLL saving the values to SQL Server.

Many thanks for your help.

Bob

[jtc]

Hi Bob,

Sorry for chiming in to your old post. I am also using shared variable to pass data between two target PC. I am creating an executable file to a target PC but when I run it i will get a continuous Error 1950679035.

You said, "Invoke Node function was not required to deploy the variable". Is this true?

Is selecting "autodeploy" in the Project shared variable library.lvlib enough to deploy the variables?

I would appreciate for any advise as i am getting tired making exe for the target pc but found it getting the same kind of error.

 Thanks a lot.

bong

[EWTech]

The invoke nod function is used in the above case to deploy the DLL file and not the shared variable. The Invoke Node function opens an ADO.NET DLL file written using Visual Studio 2005 that saves the data programatically to the data collection database. It is simplistic in the extreme bit does the job just the way we want. We store acquired data into a SQL Server database across the network. The Invoke Node function  has nothing to do with the shared variable other than the fact that the server delivers the data to the display/client machines over shared variables sent as a large data string. On the receiving side there is a separate DLL that acts as a lookup mechanism that sorts through the list of strings and associates a value with a text string used a a lookup parameter. There is a "void Update(Input string)" function that updates the string to a new list of values and a "double GetValue(String paramName)" fuction to get individual values back out.