making executable files from vis

[SAL2005]

hi,

I found one very interesting things. I tried to make an exe out of the subvi that is lauched from one of the buttons that was giving error. Guess what?? it gave the same window error.So it seems the subvi has some problems.. The subvi works fine as itself but when created an exe gives the error? Whats going on? Any clue?

Thanks

SAL

[Dennis_Knutson]

What is inside this subVI. Exactly what DLL are you calling? Where is the DLL installed?

[SAL2005]

Hi,

Inside the subvi,I have some formulas. I read in one serial port, one anolog input, one output channel. If you need I cansend you the diagram.

Thanks

SAL

[JLS]

Hello,

Posting the VI may help, but also please post a screenshot of the error message you receive as this may also prove useful!  Also, placing some indicators are various places in the subVI, and showing it's front panel may help you determine/debug where in that subVI the error is originating - perhaps the error message indicates this or gives a clue as well.

Best Regards,

JLS

[SAL2005]

Hi,

Here is one of the subvi that didnt work including the error message.

[SAL2005]

Error displayed

[JLS]

Hello,

1. I don't know if you ever indicated whether or not you have upgraded your installation to 6.0.2 - if you haven't I think that is the first step in your debug process.

2. From those pictures alone I can't determine what the cause is at first pass.  Did you try putting some indicators in your code and then rebuilding the application, where those indicators should be placed strategically so that you can tell "how far" your application gets before crashing. 

3. You can try to debug using a debugger, but this may not be very useful.  You can enable a debugger on your machine so that you can debug what happens when the crash occurs.  If you have Visual Studio .NET installed you can enable JIT Debugging by going to Tools>Options then Debugging>>Just-In-Time. Place a checkmark in front of Native. Either you will see a debug button on the "Report to Microsoft" dialog, or Visual Studio will open by itself when the exception happens.  Otherwise, both Windows 2000 and XP come with Dr Watson which is a simple debugger. To configure Dr Watson run drwtsn32 from the Start>>Run dialog.  To install Dr Watson as the JIT Debugger run drwtsn32 -i from Start>>Run.  Of interest would be the log file; the log file is a text file with a log extension and the path is set at the top of of the Dr Watson window.  If you choose this option, this may also be helpful:

Microsoft KB: Interpreting the DrWtsn32.log File to Identify Program Crash Data

Ordinarily that would be something that I could take to R&D to discuss a future fix, but since you are using version 6.0, no further updates to that version are likely to be developed.  With that said, I would try putting some indicators at various places in order to get a good idea of where the crash occurs, AFTER performing the 6.0.2 upgrade IF it still crashes.

Best Regards,

JLS

Message Edited by JLS on 03-29-2006 10:39 AM

[SAL2005]

Hi there,

Once again I tried to create an executable from the VIs but failed. But I found some interesting thing which might be hepful.

I have a subvi for the instrument(flow meter) which configures it. I found that the reason i am having problem in creating an executable is due to that. When i remove the subvi for the instrument I can successfully make an executable and can run. But when the instrument subvi is present in the vis that I am trying to make an executable, the executable process is still successful. But when i run it , it gives me this error... ...exe has  problem ...and shuts down the program. The main page has four click buttons. Each of them pops up a different page. Two of the buttons which uses the instrumentsubvis is having this error. Other two works fine. So any conclusions???

The same instrument subvi works fine in other programs. I just copied it from the other program and tried to use it in the new one.

I am including one file which uses the instrument subvi.

By the way, I couldnt upload it to version 6.02. My service expired and I couldnt download from the site.

Thanks SAL

[JLS]

Hello,

It's been a while since we discussed this issue, so I reread the thread to get familiar again.  Could this be as simple as need to put a dll associated with the instrument calls in a location which the exe knows about?  If you're calling a dll underneath, and not carrying that dll to the same folder as the exe, perhaps that's causing the problem.  I tried to look at your VI but it is password protected, and missing some subVIs, so I was only able to see the front panel.  Maybe you can post just the instrument subVI in an unprotected form.

Best Regards,

JLS

[Tariah]

The password seems to be "sal",  but that doesn't help as the suspect VI is missing, as was mentioned.
Is it one of the serial port configuration VIs?
You don't use error flow in the portion of the VI where you start communications with your flowmeter.