Afonso Teles

Hi Howard,

You might have better luck posting your code as an attached file or using the example code block (go into Source mode and you can see and edit the HTML).

Additionally, the following link has several AFG programming examples: https://forum.tek.com/viewtopic.php?f=580&t=133570

I will note that it doesn't appear to have any AFG31000 examples and the programming interface between it and the AFG3000 do differ.

You can register your MSO4 here and unlock a free DVM and frequency counter option: https://www.tek.com/en/register4mso

If that fits your measurement needs, it might be simpler than using the immediate measurement command mentioned above.

Hi,

You can use MEASUREMENT:IMMED:VALUE? and its associated commands to setup and read a measurement without displaying it or adding it to the list of measurements.
You might also consider using the free DVM, if that fits your needs.

Hi Mike,

I apologize, I was not very clear with my explanation of the workaround.

The AB trigger works by first waiting for the A trigger, then waiting the configured trigger delay period and then acquiring when B trigger conditions are met.

I suggest configuring A trigger to Edge trigger type and Line as source (this generates a trigger event to start the 8 second countdown). Then B trigger should be configured to trigger on your waveform of interest.

This means that, with trigger delay set to 8 s, you will have at least an 8 second delay between hitting Run/Stop and your acquisition. You will also have another 8 seconds before the next acquisition, giving you time to press Run/Stop again to stop acquisition.

This is not the most elegant workaround, if you have more information about your expected waveform then it might be possible to configure the trigger system to not need so much manual input.

Hi Jeremy,

We were able to replicate your issue with the channel power measurement where the result calculated by the scope is mismatched from what we calculated with Excel by about 0.2 dBm. We are currently working with our product line to understand this issue.

I don't have an authoritative answer to your question about N, it might be the source of the measurement discrepancy discussed above.

 

_{CBW should be channel width instead of bandwidth limit?}

Yes, channel width is the relevant number to channel power calculation. The SCPI command is MEASUrement:MEASx:CPWIDTh


The measurement type is CPOWER, as defined on page 2-886.

Hi Michael,

I do not believe the 5000/7000 have an equivalent option to "Enable Acquisition History". You can change the acquisition mode to Envelope, Average or WfmDB, but then you won't have measurement statistics.

Instead, I would suggest a workaround: set trigger mode as Normal, when ready to take a measurement press Run/Stop to enable acquisition and press it again after your event was acquired. Repeat as many times as desired.
If you have several possible trigger events within a few seconds but only wish to trigger on the first one, then you can setup A->B sequence triggering to have a delay of up to 8 seconds, giving you enough time to press Run/Stop before the next event.

If this workaround doesn't do what you need to do then probably the next solution to try would be to use remote control programming (SCPI commands) to automate the process of gathering measurement data and generating the statistics on a PC.
TekScope Utility can log this data automatically after a single shot trigger event and save it as a .csv.

Hi Howard,

I don't have a specific resource that describes this process, but I will try to give a short summary of it:

1.  Send the waveform data into edit memory using trace:data
2.  Save that data into mass memory using mmemory:store:trace
3.  Piece the waveform back together in the sequencer using wlist:waveform:import and sequence:elem[n]:waveform[m]

You will also need a couple other miscellaneous commands to configure the amplitude, sample rate, sequence, etc.

Additionally, please note there will be a delay between waveforms in the sequencer. I have empirically found this delay to be around several hundred nanoseconds under certain conditions. This may make this whole idea of little use to you.

Please do let me know if you need any help in this matter!

Hi Tercio!

I do not believe the 1740/50/60 non letter series had calibration software, this was done manually through on board adjustments.
The 1740A/50A/60A did have calibration software and it used completely different hardware from the non letters.

If you are indeed in need of the calibration software for the 17xxA's, we sadly no longer have it as we sold our video division to Telestream.
You can reach them at the following email: videosupport@telestream.net

1) A compensation circuit might be required, but to design one we would need to know what load the probe expects, which is not defined anywhere by the manufacturer.
The probe is still usable with a mismatched load, it just won't be viable for accurate measurements.

2) Yes, the MSO3034 is able to invert input signals, the procedure is described on page 90 of the manual: https://www.tek.com/en/bench-oscilloscopes/mso3000-dpo3000-manual/mso3000-and-dpo3000-series

3) You posted three scopes, a TDS3000 which has a max input in 1M of 150 Vrms CAT I, an MSO3034 which has a max input of 300 Vrms CATII in 1M mode.
The DSO3064 manual you posted does not appear to be for one of our products and I could not find its input voltage rating listed.

Additionally, from the measurements you took of the probe, it appears to me that the input and output of the probe are shorted, which I do not believe would lead to the 1000:1 attenuation claimed by the manufacturer. This might be because it is damaged and needs repair before use.
I would suggest contacting the probe manufacturer about this and other questions about the probe.

Hi Randy,

To make a compensation circuit I would need to know what termination the probe expects, which isn't specified by the manufacturer.

From the images you sent me, this probe seems to be little more than a coax cable with connection points at both ends. The capacitance you measured is a normal characteristic of coax lines, it does not represent a capacitance that needs to be compensated for.
It is essentially working like a 1x passive probe. These do not require compensation, although they may require matching if their characteristic impedance is different from that of other parts of the system (usually 50 or 75 ohms). This characteristic impedance is also not specified by the manufacturer, as far as I can tell, but it is probably 50 ohms.

I will also note that this probe, if used in a spark plug circuit, could supersede the maximum rated voltage of the oscilloscope.

I would suggest contacting Hantek about the above mentioned points.