LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

"bad argument was passed" message error

Hello,

I have a message "A bad argument was passed to a manager function. VI "VI name" was stop at node 0x1CA94 of subVI "SubVI name".
I work with LabVIEW 6.0.3.
I develop the application on my laptop and test it and there are not problem to execute the application.
But on the industrial PC, the application plant and post this message when the application compiled but not when I lauch the application with the source code.

If I delete the subVI and I recall it in my VI, that resolve my problem ?

Thanks.
0 Kudos
Message 1 of 7
(3,244 Views)
What is the subVI that is causing the error and what does the subVI do? Could you be calling a property node in the subVI? There are some properties that are not available in the run-time engine.
0 Kudos
Message 2 of 7
(3,229 Views)
There are no properies node in my subVI.
This subVI treats just a tab string.

But in entry there is a property node who gives the value of a listbox.
0 Kudos
Message 3 of 7
(3,226 Views)
Why don't you post the subVI and the main VI (or small example) that calls it.
0 Kudos
Message 4 of 7
(3,217 Views)

Could it be the file naming convention being different from the devlopment environment to how it is compiled in the .exe?

Maybe this thread will help.

0 Kudos
Message 5 of 7
(3,208 Views)
Herewith a part of my program. The main VI is "Configuration Cycle" and the subVI is "Contrôle conformité cycle mesure".

I think of it, that won't be a problem with the accents in the name of my subVI.

Thanks
0 Kudos
Message 6 of 7
(3,207 Views)

I think what I stated earlier is almost definitely your problem.  I see in configuration cycle .VI and the Initializer case a case where you use a global variable called VI path.  I'm not sure where the global variable gets written to.  But the path of a VI looks different in the development environment then it does in a compiled executable.

Development environment:   c:\myfiles\mysub.vi

Compiled environment:   c:\myfiles\myexecutable.exe\mysub.vi

By the way, when posting a large zip file like this with numerous sub-VI's.  It is helpful if you state which one is the main or toplevel VI.    It is even harder for someone who doesn't know your project to figure out which is the top VI when everything is written in a foreign language.Smiley Wink

 

 

Message Edited by Ravens Fan on 08-22-2007 11:24 AM

0 Kudos
Message 7 of 7
(3,199 Views)