LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

CvtPanelToScreenCoords creating problems in executable

Dear Friends,

 

Need your assistance with an issue I'm facing. I'm using CvtPanelToScreenCoords function for aligning an executable's display onto a tab of my labview application. It works fine development environment. But when an executable is built and run this invoke node gives an error. What can I do about it? I'm attaching the VI that is using this invoke nose (this VI is used to convert  labview coordinates into users monitor screen coordinates. This data is then used to send command line arguments to the executable which aligngs it on the screen).

 

This VI was coded with LabVIEW version 8.6.

I'll be grateful for your assistance and help.

Message Edited by C .DOT on 02-10-2009 06:29 PM
Message Edited by C .DOT on 02-10-2009 06:30 PM
Download All
0 Kudos
Message 1 of 13
(3,519 Views)
What error are you getting? Can you attach a screen shot of the error?
Regards,
Claire Reid
National Instruments
0 Kudos
Message 2 of 13
(3,501 Views)

Thanks Claire R for the reply.

I am attaching a screnshot of the error. This error only surfaces while the executable version of the project is running, no errors while in development mode.

Your help is greatly appreciated!

 

Message Edited by C .DOT on 02-12-2009 05:02 PM
0 Kudos
Message 3 of 13
(3,488 Views)

Hey C.Dot. I tried to run your VI and it is not working. Getting error 1026, the VI reference used is not valid. Are you able to post the executable? I might have to file a Corrective Action Request.

 

Regards,
Claire Reid
National Instruments
0 Kudos
Message 4 of 13
(3,479 Views)

Dear Claire R! Thanks a lot for taking so much pain for solving the problem. Accept m grautude for it.

 The VI and the reference works fine during development mode, it is in the executable form that it gives this error. I traced the error to the last invoke node in theVI;

 

 

 

What do you mean by "posting an executable" and what is a "request for corrective action request"?


Claire R wrote:

Are you able to post the executable? I might have to file a Corrective Action Request.

 


Thanks a lot for your time and effort!

Have a very pleasant day!

 

Message Edited by C .DOT on 02-13-2009 02:41 PM
0 Kudos
Message 5 of 13
(3,467 Views)
In LV8.5.1, this works just fine!

Are you sure the vi reference *is* correct? The reference might be correct
in development mode, but wrong in the executable!

Regards,

Wiebe.


0 Kudos
Message 6 of 13
(3,462 Views)

Thanks a lot Wiebe.for the reply!


Wiebe@CARYA wrote:
In LV8.5.1, this works just fine!

Does this mean there is a bug in LabVIEW 8.6?


Wiebe@CARYA wrote:

Are you sure the vi reference *is* correct? The reference might be correct
in development mode, but wrong in the executable!

 

 I have no idea about this correct reference stuff. Could you provide more info about his issue. Is there an alternative reference that might keep the functionality same but still work in executables (compiled using version 8.6.

 

I'll be grateful for your assistance!

 

0 Kudos
Message 7 of 13
(3,457 Views)

"C .DOT" <x@no.email> wrote in message
news:1234527007954-852704@exchange.ni.com...
> &nbsp;&nbsp;I have no idea about this correct reference stuff. Could you
provide more info about his issue. Is there an alternative reference that
might keep the functionality same but still work in executables (compiled
using version 8.6.&nbsp;I'll be grateful for your assistance! &nbsp;

It all depends on how you get your reference. Once you get it, it works
exactly the same in an exe as in development environment.

I'm not sure how an exe won't succeed in getting a reference in your case.
It might have something to do with paths. It could also be that the vi you
pass a reference from, doesn't have a panel becuase it's removed.

Could you post a picture of the caller VI (of a simplyfied version that
demonstrates the problem)?

Regards,

Wiebe.


0 Kudos
Message 8 of 13
(3,454 Views)

Thanks Wiebe@CAR…! I am attaching both the pic and the VI.

 

Message Edited by C .DOT on 02-13-2009 06:31 PM
Download All
0 Kudos
Message 9 of 13
(3,452 Views)
But I really need the *diagram* of the calling VI. The piece of code where
the VI reference is obtained.

Regards,

Wiebe.


0 Kudos
Message 10 of 13
(3,445 Views)