Tektronix 3054B Screenshot

[Davidson_D]

I tried the same and getting timeout error.

I couldn't find any help for now in TEK site also.

Is there any update or solution for this issue.Please find the attached image of NI SPY.

I tried with some delay of 10 seconds after starting the hard-copy.

The problem is that i don't get the image from the GPIB using the "Read to File" function except for the timeout.

TEKTRONIX,TDS 3054B,0,CF:91.1CT FV:v3.26 TDS3GV:v1.00 TDS3FFT:v1.00 TDS3TRG:v1.00

Any suggestion or help is greatly appreciated. Thanks in Advance.

Thanks,

Davidson

[Joe D.]

Hi Davidson D,

What version of LabVIEW are you using and what version of the Tek 3054B are you using? 

[Davidson_D]

Dear Joe,

I use LabVIEW 8.6.1f version.

And TEKTRONIX,TDS 3054B,0,CF:91.1CT FV:v3.26 TDS3GV:v1.00 TDS3FFT:v1.00 TDS3TRG:v1.00

Thanks,

Davidson

[Joe D.]

Hi Davidson,

Were did you get the instrument driver?

[Davidson_D]

I hope the driver was downloaded from NI site. Its "tkds30xx.llb".

Actually this driver didn't have the screenshot options. So i was using the commands in manual "TDS30xx User Manual.pdf" and created a VI for the hardcopy function by sending the commands i highlighted in the SPY.

Thanks,

Davidson

[Dennis_Knutson]

Instead of doing a Read To File, try doing a normal VISA Read and set the VISA Timeout to a higher value.

You could also just save the LabVIEW image of your acquisition. That way, you do not transfer the same data twice.

[Davidson_D]

Dear Joe,

Also i installed the latest driver "Tektronix TDS 3000 Series" - Project style from IDNET. It do not have Hardcopy functionality in it 😞

Thanks,

Davidson

[Davidson_D]

@Dennis,

I will try this with the instrument and update what happens with the normal VISA read.

We are using the "save LabVIEW image" method temporarily. 

Thanks,

Davidson

[Davidson_D]

@Dennis,

VISA Read is also getting timedout.

Does anyone have the working version of this VI for screenshot?

Regards,

Davidson

[Davidson_D]

I got it working.

It was my mistake of sending the HardCopy start command incorrect.

I was sending HARDCopy:STARt instead of HARDCopy START

I should have a lens to verify the commands that are sent to the scope.

Thanks,

Davidson