program no longer works when compiled

[PRCalDude]

I'm not really quite sure why, but when I compile this basic RS232 program, it no longer works.  It runs fine in the actual LabView block diagram/front panel.  Does anyone have any suggestions?

Thanks

[Dennis_Knutson]

Could you be a little more specific? Just saying 'it does not work' is pretty vague.

At the minimum, you need to have included the LabVIEW and VISA runtimes in your installer. Did you do that?

[PRCalDude]

Well, I haven't even created an installer for it yet.  I've just tried to build an application.  The application builds fine and the VISA dependencies are included in the build (along with many others), but the commands I'm trying to send don't appear to be going through the serial port.  I've attached output from NI Spy, and it looks like it tries to establish communications with "Com 6" (the port I'm using), and then hangs up.  There should be commands going back and forth.

[elset191]

Do you use relative file paths?

[PRCalDude]

I'm not sure.  I don't know what those are. 

[Dennis_Knutson]

I have no idea what relative file paths have to do with the problem either.

Did you look up the error? It indicates that something else is already using the port. Make sure LabVIEW/Hyperterminal/etc. is closed.

I'm also assuming that the error happens on the development pc.

Message Edited by Dennis Knutson on 04-30-2009 02:08 PM

[GerdW]

Hi,

there are no relative paths in the vi.

But there are several hidden buttons (some of them using the same label). Maybe they aren't set correctly when compiling the vi to an executable?

How do you want to control the executable when the buttons are hidden?

[elset191]

I brought up relative paths, because elative paths don't point to the same things in dev mode and in builds.  And accessing a file that does not exist causes an error.

At the time I posted my message I had no other info to go on.  Mostly because I didn't notice he posted the VI...

Message Edited by elset191 on 04-30-2009 03:26 PM

[PRCalDude]

Yeah, that was part of the problem.  Now it will actually communicate with the board, but it's not sending the "Stop" commands inside the "while" loop.  Do you think the 'read' after the "stop" command is affecting whether or not "Stop" is received?  Should I send the "stop" command more than once? 

[PRCalDude]

I want the hidden buttons hidden so that the customer using the compiled program can't fool with them.