LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

application freezes

Hi,

 

Hopefully someone can help and that I can explain so you can understand!!!

 

The hard drive on the one of a kind test station became corrupted and we had no back-up for the test environment but we managed to rebuild another disk from what we could see on the old one.

 

This test station was working fine with no changed made to it for a long period before the crash.

 

All the test scripts were backed up as these are downloaded each a product is run.

 

We are using Test Stand 3.1 and LabView 7.1.

 

The user kicks off with Test Stand which calls a  LabView script to display a combo box to select a product from.

 

There are a number of product so a scroll may be required to find the product in question.

 

This is where part of the problem lies in that the LabView application freezes not allowing you to scroll and there is no response from the OK button of the LabView application.

 

To over come this we can maximise or minimise  Windows explore window and then the list would have scrolled on or the OK would have taken effect.

 

We are using Windows 2000 and once we get passed the product selection all is OK with numerous LabView calls from Test Stand with no obvious ill effects.

 

Where might be the best place to look for difference is the setup of the test station?

 

Thanks for the help

 

Simon

0 Kudos
Message 1 of 11
(3,481 Views)
Hi Simon
 
Are you still having this problem? Does the Labview application work when you run it directly and not called through teststand? Also when you say "To over come this we can maximize or minimizeWindows explore window " where does windows explorer fit into this, do you mean you Minimize first then maximize again to view. In which case I would think this is a pure windows issue and you might like to do a bug search and then update the latest patches. Also try your system on an XP machine if you have one.
 
its sounds an interesting problem but a little more info would be useful on what debugging trials you have done so far so we dont reproduce things that you have already tried.
 
best regards
Graham Green
Software Product Marketing
NI | Emerson
0 Kudos
Message 2 of 11
(3,421 Views)
Graham,
 
Yes there is still a problem.
 
Does the Labview application work when you run it directly and not called through teststand?
        
 
0 Kudos
Message 3 of 11
(3,395 Views)

Graham,

 

Sorry about that it was an error to send, mixed up keys!!.

 

Yes there is still a problem.

 

The tester is in constant use so I will make time to get back on to it.

 

We are first given a list box (Lab View) with a number lines to select from.

 

If you try to scroll or move down 2 or 3 lines the Lab View list box freezes.

 

At this point by Max then min of an explorer window or text pad, which we have open, the highlight in the Lab View list box will move onto the next item in the list.

 

Once you have your choice made and select OK you once more need the max/min explorer or text pad to get Lab View accept the OK.

 

We have a number of other Lab View applications run from Test Stand but this, at the start is the only list box.

 

Thanks for the replay and help

 

Simon

 
 
 
0 Kudos
Message 4 of 11
(3,391 Views)
From what I understand you are calling this LabVIEW program as part of a test sequence within teststand. Is it possible to run the single step of the program without teststand. So call the VI directly from Labview?
 
Do you have LabVIEW as a development environment on your computer/test system or are you sunning the tester as a runtime only compiled executable.
 
Can you run other tests on this tester with no ill effects, is it only this one step that doesnt work?
 
sorry for so many questions but I'm trying to narrow down where your problem may lie.
 
 
Graham Green
Software Product Marketing
NI | Emerson
0 Kudos
Message 5 of 11
(3,367 Views)

Graham,

Questions are good.

I can only run from Test Stand, I am unable to find Lab View on the PC so I assume it is RunTime we have.

I just ran the single step in Test Stand with the same effect.

The step AFT_ProductSelection.vi is called from AFT_Utils.llb, would that sound correct?

Same frame work in TestStand for ALL test's all using the same vi at the start.

All other LabView parts work fine but there is only the one list box.

Thanks for the help

Simon

0 Kudos
Message 6 of 11
(3,360 Views)

Hi somon - I have been looking into this and cant seem to eith reproduce it or find much info on it. Could you please attach the code or the VI in question. if you can find AFT_ProductSelection.vi on your machine and post it up here I will take a look at it.

Best Regards

Graham Green
Software Product Marketing
NI | Emerson
0 Kudos
Message 7 of 11
(3,306 Views)
Graham,
 
Thanks for your time on this.
 
Not too sure if the code will help as this is the same code we used before we had to rebuild the hard drive.
 
Our problems only started after we try to rebuild the drive.
 
The people who originally put together this test system are no longer avable for comment.
 
I have attached the code.
 
Thanks
Simon
0 Kudos
Message 8 of 11
(3,286 Views)

That VI has no block diagram so it's impossible to determine what is being done. You would need to provide the original VI. It's likely that you have missed something when you had to rebuild the pc and having a look at the block diagram is going to be the best way to determine what it is. If you hired some developers to create this code, you should have stipulated that you owned the source code and would have access to it.

0 Kudos
Message 9 of 11
(3,273 Views)
Dennis,
 
Thanks for the replay .
 
I did not notice this fact, but I am VERY,VERY limited on LabView.
 
As I say I extracted this from a.dll file.
 
We have two .dll files only one has the source, which I have now found, sorry about that.
 
Is the attached better?
 
Thanks
Simon
0 Kudos
Message 10 of 11
(3,265 Views)