-
RE: Save full-resolution image from MDO34 (3 Series) via network
Hi Jacob,
Yes, the option to change the default save location is under Tools -> Options -> General -> Default Save Locations. -
RE: Save full-resolution image from MDO34 (3 Series) via network
Hi Jacob,
There are several ways to connect your PC to your MDO34. eScope is meant as a quick and easy way to remote control the instrument.
If all you need to do is get a screenshot/hardcopy, I would recommend the free application, TekScope Utility.
It also features other data acquisition capabilities, like waveform data or measurement values.
For something more fully fledged, TekScope is the way to go. It allows you to connect to and control several scopes at the same time, controlling them all through the same interface as you will be used on the instrument itself. -
RE: Saving and exporting multiple waveforms in quick succession
Hi David,
The SAVE commands are generally used for saving to a mounted drive.
It appears what you want is to transfer the waveform over the connection.
To do this, you should use the following sequence:
"CURVE?" outputs the waveform data and the following line reads that into an array you can then process and/or save as you wish.scope.write('CURVE?') data = scope.read_raw()
-
RE: How to select type 'Time out' for MDO34 programmatically
Hi Jeremy,
Indeed the SCPI interface for the 4 and 3 series are slightly different.
The programmer's manual describes how to setup the timeout trigger on page 2-67 (picture attached). You will notice it is a different procedure from that you expected from the MSO4. -
RE: MSO54 different but synchronized time bases
Hi,
The MSO54 is not capable of doing two independent timebases, but it is capable of recording 80 ms of events at the full 6.25 GS/s, which would allow you to record both of your events at the same time and then zoom in on the event you would like, with no loss of signal fidelity. Higher recording lengths are possible with lower sample rates.
The image attached displays such a setup. Please note the Horizontal menu. -
RE: TDS3034B escope not connecting anymore, but ethernet print works
Hi Bruno,
I would suggest you try a few more things:
1) Make sure you are using http and not https (browsers often force https now a days);
2) Go into the "Save/Recall" menu and recall factory setup;
3) Go into "Utility", "I/O", "Ethernet Network Settings" and "Change Instrument Settings", make sure the instrument name and password are empty and that all the other fields are automatically populated as expected. Sharing a screenshot of this menu might be helpful;
4) Change networks and PC. -
RE: Saving and exporting multiple waveforms in quick succession
Hi David,
Indeed TekScope Utility is a great community made tool that can get and save waveform data from your instrument.
It appears you want to get the data in quick succession under some event/condition. For that you should go to the "Data Logger" tab in TekScope Utility.
There you can configure it to save analog waveform data on triggering or on a timer.
If TekScope Utility doesn't provide the functionality you need, then you can try the programmer's manual for the DPO2000, together with ready made remote control examples. -
RE: RSA306B What is the physical setup required to measure SINAD?
Hi John,
As you suspected, I would have to know your radio and signal generator to answer that concretely.
Generally, one would look at the power rating of the signal generator's output and the receiver's input to determine that. The characteristic impedance of each is also important.
If the power rating is too high, attenuators can be used. If there's an impedance mismatch, a matching network might be needed.
Those are the most typical specifications to look at for such considerations. -
RE: THS720 firmware upgrade
Hi Jerry,
Sadly we no longer provide new firmware for the THS720. -
RE: "Save Confirmation" message appears in screen captures since latest TekScope Update
It appears this is a small bug in 1.44 that will be fixed in the coming releases.
The cause seems to be the "Displayed Colors" and "Screen Capture Colors" options in the "User Preferences" menu being set differently. That is, if both options are set to "Normal" or "Inverted", this bug will not occur.
The current workaround is to set the options identically.