error 10609 in executable file

[lmtis]

HI all,

I have a VI that runs the function generator VI in the background, and an analog trigger to collect data.  The function generator is launched with an invoke node.  It works well as a VI.  When I compile it and try to run the exe, I get error 10609 in clock config.  We used to run function generator as a seperately launched application, and that is the same error that we would get if we forgot to launch the function generator before starting the data collection VI.  I am running LV6.02 on Win2K.  Thanks in advance.

Jim

[andre.buurman@carya]

Hello,

Are you sure that the dynamic VI is started and intialised correctly before any data collection?

If not.

You could pass an occurence to the dynamically started VI.
Generate it in the dynamically started VI after all settings have been done.
Wait for the occurence before doing data collection.

Regards,

André

[lmtis]

Hi Andre,

Everything works well when I run the VIs with the developement system.  I am just now trying to compile and deploy it.  This is the first time that I have tried to run a VI in the background in a compiled application.  The function generator VI is in the same library as the main data collection VI.  The function generator just creates a sawtooth waveform continuously while data is being collected.  When building the application, do I need to select Add Dynamic VI, and add the function generator?  If so, do I also need to run VI Server?  I am beginning to suspect that the problem might be how I addressed the dynamically loaded VI.  For portability I am using the current VIs path property to build the path to the function generator.  There is a test running on that station right now, but after it finishes I'll try putting in an absolute path.  Any other suggestions?

Regards,

Jim

[Dennis_Knutson]

It sounds like you may have two problems. When you do a build, you have to select Add Dynamic VIs. Otherwise, they do not get included in the build. Also, when you use the Current VI's Path, the path it returns is different in a built VI than in the development mode. In the development mode, it would return something like c:\folder\example.vi. When you build it, it would return c:\folder\application.exe\example.vi. You need to test to see the mode you are in a do an extra strip path with a built app. One way to test is to use the Application.Kind property node.

[lmtis]

Hi Denis,

I'm a bit confused.  The function generator VI is in the same llb that the main application is in.  When I build the application, how do I address it?  Do I have to save the function generator as a seperate file when I deploy it, or is it bundled inside the exe?  If bundled, then Current VI's Path returning c:\folder\example.vi would work because I am stripping off example.vi and adding function generator.vi.  Also I am not sure that I understand your suggestion regarding the Application.Kind property.

Jim

[Dennis_Knutson]

I'm not sure what llb you are referring to. If it's in an llb you use for development (besides being a bad idea to use an llb), it does not automatically get included in the exe unless you select Add Dynamic VIs. If the dynamic VI call works in development mode with the function generator inside the same llb, then you don't have to do the additional strip path.

I just wanted to add that with LabVIEW 6, you can change the suffix of the exe to llb and open this just like any other llb. Do this and see if the dynamic VI is included in the built file.

Message Edited by Dennis Knutson on 08-23-2007 12:46 PM

[lmtis]

I'm afraid I only recently learned of the dangers of the llb files.  I will try the rebuilt application when the current test run finishes.  I didn't think about the fact that if the VI is not used as a sub-vi wired into the program, then LV won't add it into the exe.  Thanks.

[andre.buurman@carya]

Using the LLB manager in the Tools menu you can easily convert the llb to a directory, without having to rebuild teh apllication. It should only be a 15 minute exersize at the most.

Regards,

André

[lmtis]

Thanks for your help guys.  The exe works fine.  After years with my head down charging forward to "just get the job done" I am finally exploring the tools at my disposal.  By the way Andre, it only took two minutes to convert the llb.  I am ashamed to admit that I did the same exercise manually - copied the files into a directory and then re-linked all of the sub-vis.  I won't say how long that took!  Thanks again.

Regards

Jim