TekTronix TDS7404 help

Similar Questions

• OR VISA with Tektronix TDS7404

  Hello world

  I have problem connecting to the oscilloscope Tektronix TDS7404 via Ethernet of LabView. The driver is installed, but when I open the VI example came with the driver,

  I need the VISA name. If I leave the field blank, I get an error:

  1073807343 error occurred while opening VISA in Tektronix 7000
  Series.lvlib:initialize. VI-> Tektronix 7000 series gain Waveform.vi

  Possible reasons:

  VISA: (Hex 0xBFFF0011) insufficient location information or the device or
  resource is not present in the system.

  How can I configure the VISA for this scope?

  It is connected to the PC via a switch, ping for the works of scope, I can see the hard drive of it also.

  I use LabView 2010 SP1; I do not see the scope max.

  Thank you.

  Problem solved. Among device drivers has not been installed. Not the high level (VISA drivers), but the low level drivers. The TekVISA server on the scope did not work as well. Strange that LabView has not complained about these directly, just did not see the scope.

• Tektronix TDS2014C 2012 Labview driver

  Hello, I have to deal with the problem of communication with the PC with LabView 2012 new oscilloscope. I downloaded all the drivers site Web

  http://sine.NI.com/apps/UTF8/niid_web_display.download_page?p_id_guid=047216EC20B66FABE0440003BA7CCD...

  and it seems that none of them work. TDS2014C is connected via USB and I am running Windows 7. In the control panel - Device Manager I see this device but to run without a driver, so there is some sort of error. I tried to find any other device just for Windows, but there is no driver. So please help me with this problem of TDS2014C drivers running on my computer in LabView.

  Until I reinstalled LabView for 2012, it worked, but now, no, I don't know if it is possible because the new version of LabView it stopped working (a previous version of LabView was 2010 SP1).

  OK everything is solved, the guys at tektronix has helped me. I have their answer qote:

  With usb connections measuring instruments use USB - TMC to communicate, if you need a usb - tmc driver to get the highest level parts labview to work.

  You can find one when trying to install TekVisa, or by installing the appropriate components of NI-Visa.

  Then you can try to hit these urls to:
  http://digital.NI.com/public.nsf/allkb/044FA220F32774ED86256DB3005850CA
  or
  http://www.Tek.com/oscilloscope/tds7054-software/TekVISA-connectivity-software-V400

  (I do not use Labview myself, but looks like it is the piece that you miss).
  Byron

• Everyone used Tektronix TDS7704B Digital Phosphor Oscilloscope! URGENT help!

  Hi I use scope TDS7704B, communicate via GPIB.

  My only requirement is to set the trigger parameters in the scope & detect a trigger based on the amplitude of the signal available to track the scope 1.

  Now the problem is I did a code that works fine most of the time, but randomly problem giving appropriate results. I can download the VI is necessary.

  Hi guys,.

  Thanks for the help. Well I already use the same drivers you suggested.

  I enclose you attached my VI. Can you please take a look at the same [TDS7704B.vi] & suggest me if I am missing any stage of configuration or I do something wrong in this.

  All I have to do is check that when the input signal which is connected to my channel 1 go below a particular level. Normally, it must be above 1.5 Volts. In some special conditions that the input signal becomes less than 400 mV. Now, there are a lot of conditions of entry which are varied (automatically & sequentially) for whom this signal I need to capture changes its State from 1.5 Volts to< 400="" mv.="" i="" need="" to="" capture="" that="">

  Now to do this, I'll put a condition of Tigger timeout in the Oscilloscope (TDS7704B). Definition of the level like 450 mV & timer 1 dry, so that any time the input signal goes below this level of 450 mV to 1 dry, this should give a trigger.

  Problem starts here, sometimes the same works of logic very well. Sometimes it starts giving error IE even when the input signal level is 1.5 Volts it gives a trigger & a few such mistakes.

  Are there delays that must be used?   Infact I had already tried giving the delay (1 sec) after initialize and/or after setting the trigger conditions. But

  Are there any specific conditions that must be addressed, that I'm missing?

  Is there a any sequence error (sequencing of VI all in configutring the scope condition & trigger) I do?

• With the help of the command on paper by emission of GPIB Tektronix TDS540

  
  

  Search the fboard for "screenshot". There were many posts and include some of the code. A recent is present. Model different but similar orders.

• Screenshot of Tektronix MSO4104B using LabVIEW

  I am trying to acquire a screenshot of an oscilloscope Tektronix MSO4104B using LabVIEW. I am currently able to collect data from the device and have a waveform displayed on my front of VI. However, for various reasons, our preference is to capture the actual screen shot of the scope.

  I have reviewed the reference for programmers for this camera and have done countless searches on Google for an answer, but have not been able to find a solution. It seems that a few people were able to reach on OTHER Tek scopes by sending a hard copy through the port of communication (GPIB, USB, Ethernet, etc.), but according to the reference of programmers for this particular device, it seems that he will send a paper copy of an installed printer, rather than simply as a stream of data to the port which can be read using VISA controls.

  The other solution I've seen is to record the screen turned to a flash drive, and then copy the file via the port to the PC. However, none of these solutions seems to be available on this device... it's one of the more advanced scopes makes Tek... I can't believe it's so hard! Help, please!

  
  

• Tektronix AFG 3253 USB question

  I'm having some problems with running a test of long duration (100 + hour) with a Tek AFG 3252.  I was using a converter USB / GPIB to communicate with him.  For some reason any USB port down and he refused to communicate after that and the settings are pasted on the AFG.  The issue seems to occur at random times and after a while.

  I checked the USB sleep on the port settings and it is not permissible to put he's asleep.  I also tried to use a hub USB powered and it does not solve the issue.

  I will try to convert the right USB communications today or tomorrow and see if that makes a difference.  If I can't make it work reliability with USB I'll try Ethernet.  We had a problem like this with a range of Tektronix finally had to convert the comms in Ethernet.

  Has anyone else had a problem like that?  If so what did you do to solve?

  Does anyone know if there is a sniffer software and/or hardware that can be used for USB ports?  I would like to know if there are any detectable reason this port is stalled.

  The problems get fixed if the USB cable is unplugged and plugged in the back.  I saw an article on the realization of a software new departure of a USB port.  Has anyone tried this before?  If it works, I'll have to make sure I can detect an error indicating that a reboot is necessary.  Is it possible a hardware switch that I can put in line with the USB port which will create the physical disconnect with digital or software control and does not interfere with the characteristics of the physical layer?

  Thanks for your help.

  You run Windows by chance? I had a similar problem a while crossing a field of Tektronix USB. After a few hours the connection would be deleted and I had to reconnect the USB and restart LabVIEW to resume the connection. In my case, the solution was to turn off the selective suspension of USB in Windows power settings. My understanding is that Windows, in an effort to save energy, turn off USB ports apparently at random. On Windows 7, go to the Power Saving settings > change Plan settings > change advanced power settings > USB settings > USB selective suspend framework. Of course, this might be different in other versions of Windows. If you do not use Windows, then your question is probably something different altogether so feel free to ignore this message.

• Unable to remote control Tektronix TBS1062 with USB Interface

  Hello

  I recently downloaded IVI Driver for Tektronix TBS1062 of national instruments.  I use the USB communication. I have configured the instrument NI Max and can identify the instrument successfully. However I'm unable to use other functions using the driver of the IVI. Stage of IVI to NI TestStand always runs without error and Trace of e/s OR watch VI_SUCCESS but I don't see any channels settings horizontal scaling and scale veritical configured by the IVI step. The horizontal and vertical scales are always the same.

  I'm not really sure, but would it be because of the USB interface? The driver supports USB?

  Anyone have the same mistake or could someone please help solve this problem.

  Thank you very much

  First thing I would do, is to ensure that the instrument is configured correctly to accept orders via the USB.

  After that, try to send commands through MAX to see if the range reacts.

  Make sure that you are not using a simulated IVI session.

• Error time-out random - 1073807339 using pilots of series Oscilloscope Tektronix TDS 200 1000 2000

  I am trying to make measurements of waveform of an oscilloscope Tektronix 1052 B using LabVIEW. My program is intended to be run for hours at a time, and it works perfectly as expected for the first few hours. However, I noticed that after a few hours, there are apparently random of chances that a VISA to read or write the block function will produce the error - 1073807339. After that happens once, all read or write functions also produce this same error for a while. This happens even using subVIs new driver provided by OR (http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=047216EC20B66FABE0440003BA7CCD... Meanwhile if I stop the program, I can still bring up the oscilloscope in MAX and read and write commands him. The error seems to occur within a VI. I already read this page here: http://digital.ni.com/public.nsf/allkb/874B379E24C0A0D686256FCF007A6EA0?OpenDocument, but none of the solutions helped. I know that this is not a matter of actual timeout because I tried increasing the timeout of 30 seconds, but the error always occurs immediately as soon as the function of reading or writing block is called.

  I would like to know why this is happening and what can be done to remedy this. The Subvi in question is provided. This VI is called at various points in the program do acquire a waveform. The inititialize and narrow subVIs are called outside the Subvi.

  Then check your powersettings. Windows may unexpectedly turn off usb power

• Set ACQUISITION_START_TIME Tektronix DPO3034

  Hello

  I'm trying to set ACQUISITION_START_TIME to Tektronix DPO3034 through interface USB with CVI.
  I managed to install the driver and can communicate with the oscilloscope.
  When I write the time-out value (3.5334E - 005) that's what I get from the Spy:

  1 IviScope_SetAttributeViReal64 (DPOScope, NULL, ACQUISITION_START_TIME, 3.5334E - 005)
  PID: 0 x 00001534 ID of Thread: 0 x 00000874
  Departure time: 17:29:42.456 call duration 00:00:00.015
  Status: 0 (VI_SUCCESS)

  This means that the right control was adopted.
  But the delay in the scope comes with 0.4us resolution. This means I can get values of only 3, 56th-005 ACQUISITION_START_TIME, 3.6E - 005 etc..
  This is what I get in the spy with GetAttribute imeddiatley command after the SetAttribute above command:

  4 IviScope_GetAttributeViReal64 (DPOScope, NULL, ACQUISITION_START_TIME, 3, 56th-005)
  PID: 0 x 00001534 ID of Thread: 0 x 00000874
  Departure time: 17:34:11.995 call duration 00:00:00.016
  Status: 0 (VI_SUCCESS)
  (The actual time on the scope screen is also 3, 56th-005...)

  Thank you very much for your help!

  I've corrected the pilot...

• Unable to send arbitrary signals of CC. Help. Please, I beg you.

  Hello people,

  I am a student of Btech working with Labview 2013. I managed to generate an arbitrary Signal through Labview 2013 version for my project. Now, I need to send the signal to Agilent 6642 power supply dc to ampilfication and it will be used for my experience. I am facing problem here.

  I use GPIB USB HS to send the signal, and when I send commands * IDN, is successfully reading and writing, which means I have all my software and drivers installed perfectly. I have installed in my pc control expert and NI MAX.

  I did a program (which is attached) in labview and the GPIB seems to read (signal ACTIVE/Green shows when it is executed).
  But I do not see it in the oscilloscope (Tektronix TDS 2024 B) which means something's wrong here. I need to see the signal as shown in the attached picture.

  I am new to labview and don't know much. Please help me with the Labview program as I want to see the signal in the oscilloscope as well.

  If a command is needed, let me know the order.

  I'm stuck. Help, please.

  Thank you.

  
  

• Tektronix DPO2024 function average

  Dear Sir/Madam:

  I would like to use the average function in Tektronix DPO2024 to digitize the signal through Labview.

  The error appeared when I used the average function. Please see the attachment.

  Anyone got the same problem before?

  Willy0120 wrote:

  Hi, Ben:

  I have difficulty outside. Thanks for your information.

  You then mark the post helped you in the accepted solution. You should also put the updated the vi that works, it might help others with a similar problem to find a solution.

  Ben64

• Urgent: oscilliscope Tektronix TDS 2014 B USB communication interface

  Changed the code from a GPIB interface to the oscilliscope to a USB (Tektronix TDS2014B) and now the code will not work. The VI is not the scope triggering. I checked the USB interactive control of VISA address and it matches the block diagram. I get this error:

  VISA write to Tektronix TDS 200 1000 2000 Series.lvlib:Error Query.vi-> Tektronix TDS 200 1000 2000
  Series.lvlib:Close.VI-> 200 1000 2000 Tektronix TDS Series.lvlib:Initialize.vi

  Help, please!

  Do not take account of this post, I left my signed account and a graduate, decided to ask a question on my behalf. The oscilloscope just need a reboot.

• V6.1 LV driver for Tektronix 2440 &amp; Keithley 485 Picoammeter necessary

  Does anyone have the driver 6.0 or 6.1 for the oscilloscope Tektronix 2440 and the 485 Keithley Picoammeter? Only drivers that appear currently available are for V7 or V8.

  Thank you

  I posted this request with lttle hope so I'm glad to not only get a response, but the drivers, all within 12 hours.

  Nathan Merci for your help and by publishing the drivers.

  Concerning

  Shane

• programming Tektronix mixed signal oscilloscope

  Hello

  I'm using Labview programming to control tektronix oscilloscope to mixed signal 2014

  Initially, I tried to control the vertical position and vertical scale of waveform.

  It works but it takes a few seconds(5-8sec) disables it.

  I tried to understand. However, I am unable to do, could you please help me what I need to do to reduce the delay time

  Here is the block diagram of my vi

  Hello

  Email ID: [email protected]

  Try to put two entries in the same loop, to run in the order of wiring.

  In addition, you must add a waiting inside the loop (maybe 100 ms) to reduce the rate of update of the VISA application.

  A stop button would be nice, too.

  The way you wired things upwards, the two loops are trying to write their orders as quickly as possible on the instrument at the same time.

  This most likely disrupts the scope.

  You're also hogging your processor by not having is not a wait in there.

  In addition, you close the VISA reference in two places, not that you would never get there because your curls are endless...

  Klaus