Afonso Teles

Hi Francisco,

Yes, one probe per channel is included with the TBS1000C, as mentioned on page 11 of the datasheet.

Hi Howard,

SCPI commands are case insensitive, as mentioned on page 15 of the programmer's manual.

the write_binary_values method does indeed automatically do the binary formatting, as mentioned in the pyvisa docs

I have included a python example of loading a waveform into ememory of an AFG31000. I hope it's of use to you.

Hi Mathias,

A formula for the record length required when using BUJ is not publicly available.
I will mention that one can change the minimum number of UI require by going into Select -> Preferences -> Jitter Decomp .

Perhaps if you could give us more insight into why you need to calculate the required record length, we would be able to help you?

Hi Mathias,

For many of the more of the more complex jitter measurements, the record length required is a function of the minimum number of pattern repeats. That is to say, if the minimum pattern repeat for the measurement is 100, then your required record length will be whatever it takes your waveform to reach that number of pattern repeats.
The error or warning icon should tell you how many patterns are found and how many are needed.

Hi Eric,
 

The ports on the MSO70kC are TekConnect ports.
 

TekConnect to BNC or SMA (both 50 ohms) adapters are available here: https://www.tek.com/en/datasheet/tekconnect(tm)-adapters

Hi Ryan,

The 2232 has a digital storage mode which should allow you to view these slow sweep speeds much easier.
This mode is described on page 3-8 of the operator's manual available on the TekWiki: https://w140.com/tekwiki/wiki/2232
The slow speed storage mode is likely of most interest to you.

I will also mention that it does appear your signal is "clipping", as in, it's going over the vertical scale. This can result in inaccurate measurements.
I would suggest reading the XYZ of scopes: https://www.tek.com/en/documents/primer/xyzs-oscilloscopes-primer

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.