LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Reentrant data space could not be

I have developed an order track vi in LBV5.1 here in Belgium for vibration
monitoring of rotating machinery and tried to exchange it to a colleague in
California after converting it to LBV6i.
It contains lots of diagramless reentrant vi's for these reentrant vi's in
the llb.
My colleague tried to load the llb both in LBV5.1 and LBV6i this past night
(in Belgium, that is).
To no avail since he sent me this mail:


Gerard
The 2 vi's that will not open are synch_provider8.vi,
and streamfreq8.vi. They will not open in either LV6
or LV5.1. The "Reentrant data space could not be
cloned!!" appears in both LV versions. All other vi's
seem to open without these. There may an issue with
some of the subvi's for these 2, but I ca
nnot tellwithout them loading
first.
Thanks
Jim

I guess that without the diagram it cannot generate all occurrences of the
reentrant vi's to run the package. Am I supposed to sent him the llb with
diagrams protected by a password? Is this password enough to prevent access
to the diagram?
Can you tell me what went wrong and what I could do about it?
Gérard at gdans@ulb.ac.be
http://www.ulb.ac.be/polytech/laborulb/index.htm
0 Kudos
Message 1 of 2
(2,378 Views)
You have sent him probably a slightly different labview version, so it need to be compiled on his machine and that is not possible without a diagram.
Password protection is failsafe enough.
It takes much longer to crack a password than to develop a new vi that has the same functionality. Especially when the pasword contains a mix of letters, numbers and other idiot signs. Using a belgium keyboard makes it even better possible to generate a crazy password. In the Netehrlands we need to press shift for the @#$%^&* ect keys.
greetings from the Netherlands
Message 2 of 2
(2,378 Views)