sib592

I have an application that has two nodes. One is a windows node and the other runs on a cRIO. There is alot of shared code but also code that will run base on the OS conditional disable. The customer now wants to create a training system so that they can train their employees on the system in the office. They do not want to have a a controller with every training system so we need to run both apps on a windows machine. The problem is we to build the rt code as a windows runnable executable with the OS==VxWorks condition. When I change the OS condition to VxWorks under the My Computer target it changes itself back to win. Does anyone have any suggestions on how to do this?

I am using client server tcp between two laptops. They connection is created properly and data is written and read properly at first. Eventually I get an error 56 and error 57 when trying to write to data to the client. This may start happening after 5 minutes or it may start happening after 5 hours. It is very unpredictable and hard to test. When there is no response for 4.6 seconds the connection is terminated and attempts to create a new connection. They are on a dedicated network with static ip addresses. Does anyone have any ides??

Thanks for the response.

To answer your questions. Yes it is the main vi within an llb that I'm trying to read. The code is being launched from an rtexe located on the 9012 crio. This same code is used in an exe and has never had a problem. The llb is located in the same directory as the rtexe. The path is passed into Open VI Reference as you show above and this is where the error 1124 shows up. Is there something different that needs to be done for the rt build? I couldn't find the VILinkerErr property you have shown.

SITUATION

Labview 7.1.1 Run Time Engine

OS : Linux Redhad WS4 or Mac OS X (we don't have time to really test it on WinXP, but it would be done soon)

Machines : Dell Bi-Xeon 3Ghz 1GB and Apple G5 Dual 2.5Ghz 1GB.

Application : ~2000 VIs, with lot of dynamic launches of parallel processes (VIT instanciation). Every 10 seconds, 4 processes are launched and destroy themselves after 7 secondes.

PROBLEM

Error 1124 appears randomly on Open VI Reference for instantiation of process VIs (it take between ~20 minutes and 24 hours~to happen). We try to handle this error by filtering and re-trying the launch but the application crash with a "memory.cpp in line 1038".

From LabVIEW General Error Codes page we have Here :

"VI is not loadable. In a built application, this error might occur because the VI being loaded was last compiled for a different OS, in which case you must save the VI on the current platform. This error also might occur if the VI is a polymorphic VI, which cannot be loaded in the LabVIEW Run-Time Engine. You must load an instance of the polymorphic VI instead of the polymorphic VI itself."

We have done a mass compile of all VI hierarchy before building application, and our process VIs are not polymorphic.

Some weird think seem to happen with intensive use of VI Server and multi-threading in LabVIEW. It remind me an another problem we have here (NI is aware of this bug but not resolved today), and I've seen something similar on this page.

Someone know what is really mean or ever seen this kind of problem?

I am currently having this problem on the 9012 crio and am running Vista. Does anyone know if this issue has been resolved or how to fix/work around it?