Test and Measurement Forum

Picoscope 5442B and labview 8.6/2013 keep hanging

Come here to introduce yourself, who you are, and what you do

Picoscope 5442B and labview 8.6/2013 keep hanging

Postby vtran@immersion » Fri Jun 06, 2014 7:48 pm

I am using Picoscope model 5442B with Labview version 8.6 or 2013, still have same issue when closing labview. Labview will no longer responding. It hung, no matter what I tried, such as closing the app's execution first then exit, or stop the loop, try different *.dlls. Is there any solution to this matter? Thanks
vtran@immersion
Newbie
 
Posts: 0
Joined: Fri Jun 06, 2014 7:33 pm

Re: Picoscope 5442B and labview 8.6/2013 keep hanging

Postby Karunen » Mon Jun 09, 2014 2:52 pm

Hi,

Have you made sure the close.VI is called before the application closes?

Please do not click abort execution as this will cause the device to stay on and and held by LabVIEW.
Just press the 'STOP' button on the front panel.

Are you running the SDK examples?

Thanks,
Karunen

Technical Specialist
Pico Technology
Karunen
Zen Master
Zen Master
 
Posts: 194
Joined: Thu Nov 21, 2013 9:22 am

Re: Picoscope 5442B and labview 8.6/2013 keep hanging

Postby vtran@immersion » Wed Jun 11, 2014 10:58 pm

Hello Karunen,

I tried all examples in the SDK, all gave me same problem.
I researched my problem before I posted this. Tried as all suggestion in this forum, such as: pressing the STOP button inside the VI loop before close the Labview App.
What I need to do is close the Labview completely each time I run a test. I don't have problem with other drivers, such as Agilent scope, etc...
Also:
I could not figure out how to generate signals below 1KHz in AWG yet. Please help. Is there a limit for the 5442B model which can not go below this range of frequency?
Thank you very much.
vtran@immersion
Newbie
 
Posts: 0
Joined: Fri Jun 06, 2014 7:33 pm

Re: Picoscope 5442B and labview 8.6/2013 keep hanging

Postby Karunen » Fri Jun 13, 2014 3:20 pm

Hi,

Would you mind copying and pasting the close.vi on the far left of the screen (so first block that is called) and input 16384(handle) into it?

When setting the frequency did you make sure the start and stop frequency where the same?

What value did try you use as the frequency?

When you try to set the frequency did you get an error message?
If you did what did the error message say?

Thanks,
Karunen

Technical Specialist
Pico Technology
Karunen
Zen Master
Zen Master
 
Posts: 194
Joined: Thu Nov 21, 2013 9:22 am


Return to Introductions

Who is online

Users browsing this forum: No registered users and 3 guests