• RE: TDS3054 comm problems w/Labview and Prologix controller

    <p>Afonso,</p> <p>Thanks for the information.  Off to plan B...</p> <p>John</p>
  • TDS3054 comm problems w/Labview and Prologix controller

    I'm having an issue with getting a full waveform out of a Tek TDS 3054. &#160;Initially, it seemed to be related to reading binary files from the scope. Now the problem seems to be more basic: writing commands to the scope with the VISA Write VI through the controller.<br> <br> Setup details:<br> Scope FW version: 3.15<br> Scope comm module: RSA3GV GPIB/RS-232/VGA<br> Laptop OS: Windows 10<br> LabView 2019<br> Prologix USB-GPIB Controller Version 6.107 (laptop USB to GPIB on equipment)<br> <br> I created the Set GPIB address VI (attached) to be able to assign GPIB addresses to each device (per the controller documentation).<br> <br> There are three devices on the GPIB bus: a Fluke DMM (GPIB 3), the 3054 (GPIB 5), and a Tek TDS 744A scope (GPIB 7). &#160;All three are powered. &#160;No problems controlling and reading measurements from the DMM. &#160;I haven't tackled the 744 yet.<br> <br> The example from NI/LabView (Tektronix TDS 3000 Series Transfer Current Waveform Example.vi) doesn't work as is, I believe due to the controller requiring a terminator at the end of all/some (?) VISA Writes. &#160;<br> <br> The Tek TDS 3054 Oscope Transfer Current Waveform Rev-.vi (attached) is the NI example VI, but with the Set GPIB address VI inserted at the beginning and a CR concatenated to each string feeding a VISA Write.<br> <br> The ID query (*IDN?) returns the correct information without generating an error. &#160;However, it appears that Writes that are not queries generate Error 420 (Query UNTERMINATED). &#160;<br> <br> When sending a reset (*RST;) the scope does reset, but I get an Error 420. &#160;This happens whether or not CR is added to the end of the reset command.<br> <br> The same goes for recalling a User Setup (*RCL 1); the scope recalls the stored setup correctly but I get an Error 420.<br> <br> What am I missing?<br> &#160;