LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

xp embedded causing my on screen buttons to lock?

Solved!
Go to solution

Hi,

 

I am working ona Labview applications. basically I am controlling a device via RS232, also I have a Labjack U3 used for a series of input buttons which are duplicates of buttons I have on screen. The main interface is a Advantech touchscreen running XP Embedded. I am using Labview 8.6 for development the build of my executable.

 

I have no issues on my desktop or a laptop, however when I install the application on the touchscreen, occasionally my on screen buttons lock and I have to force quit the program. My program uses a tab structure to switch between screens and all buttons are connected to event structures. When I switch to a different screen in my program, all buttons on that screen will be frozen... I cannot click on them with a mouse or using the touch screen. Oddly enough, if I use my "manual" buttons tied to my labjack, these operate fine, even though they basically trigger the same code as clicking the buttons on screen (although these are onlu some control buttons on the main run screen).

 

Anyone else ever see anything like this? Does this sound like an XP Embedded issue or is it possible I have a code bug that only shows up under XP embedded as I am taxing the system more than on my normal computers?

 

Thanks for any insight!

 

Garrett 

0 Kudos
Message 1 of 4
(2,772 Views)

Hi Garrett,

 

Most likely its something to do with the event structures.  However, you said that it doesn't happen on the host environment; what if you run the exe on the host machine?  Does it happen in a particular tab only, or all tabs when you switch?  Is it reproducible or intermittent? If you could post the portion of the code that is causing problems, it would be helpful.  

 

I'd also like for you to go ahead and build a debuggable executable, and run this on highlight execution--do you see where it is hanging up?

 

Regards,

Marti C
Applications Engineer
National Instruments
NI Medical
0 Kudos
Message 2 of 4
(2,747 Views)
Solution
Accepted by topic author Herning

Hi Marti,

 

I believe you are right. I did some checking and I did not have my buttons that attach to the event structures all the same (mechanical action) and I had even forgotten to disable a few immediately after being pressed. The places where I seemed to lock up were all had the same mechanical action, so it must have been seeing the button pressed twice in rapid succession. Once I cleaned this up, things seem to be working fine. The application taxes the processor a lot more on the XP embedded than the desktop so it seems I need to be much more careful on the fine programming details.

 

Event structures are great, but you do have to be very careful!

 

I've never built a debuggable exectuable... I have to look at how to do this. I did a lot of programming on 7.1 and have been away from it for a couple years, so a lot has changed with 8.6.

 

Thanks for the help!

 

Garrett

 

 

0 Kudos
Message 3 of 4
(2,687 Views)

No problem, I'm glad I could help.  Here is some more information on Debugging Applications and Shared Libraries.  I believe this was a new feature in 8.0.

 

Cheers, 

Marti C
Applications Engineer
National Instruments
NI Medical
0 Kudos
Message 4 of 4
(2,658 Views)