Seamus Brokaw

From my coworker Xander Budd:

There are mainly two different options in terms of improving the spectral analysis capabilities of the 5/6 Series MSO. I try to clarify these below. 

 

One option is to utilize 6-SV-RFVT, which is an TekScope option that provides RF vs. Time Traces and RF vs. Time Triggers. If you have not already used this Spectrum View feature/option, you may find these triggers very beneficial in helping capture spectral events more effectively. I have linked an article and a few demo videos below: 

• https://www.tek.com/en/blog/new-rf-vs-time-waveforms-spectrum-view-what-are-they-and-what-can-they-do-you-part-3
• https://www.tek.com/en/video/capturing-a-clock-frequency-glitch-with-rf-vs-time-trigger
• https://www.tek.com/en/video/spread-spectrum-clock-analysis-with-rf-vs-time-triggering
• https://www.tek.com/en/video/time-correlated-multi-channel-analog-digital-rf-signal-analysis-workshop

 

However, if you are interested in performing more traditional Spectrum Analyzer measurements, then you may need to utilize our SignalVu-PC software combined with the MSO68B. SignalVu-PC is an RF and vector signal analysis software that allows engineers to easily validate RF designs. It is based on Teks’s signal analysis engine from our real-time signal analyzers, and the software runs on your computer. The Analysis software offers numerous analysis packages and options, but it also comes with plenty of base measurements as well. These base measurements can be found on page 11 of the datasheet. 

• SignalVu-PC Page/Datasheet: https://www.tek.com/en/products/software/signalvu-pc
  • SignalVu-PC Vector Signal Analysis Software - V4.5.0093: https://www.tek.com/en/support/software/application/signalvupc-vector-signal-analysis-software-v450093
  • SignalVu-PC Base Measurements: 

 

Our SignalVu-PC Analysis software can be installed on an MSO5/6B that is operating with Windows. TekScope and SignalVu-PC can then be linked, so that traces/data from the scope can be analyzed within SignalVu-PC all on one instrument. Below I have included an instructional video explaining how to sync TekScope and SignalVu-PC. I have also added SignalVu-PC introduction videos. 

• Demo - How to Get Up and Running with SignalVu-PC on the 5 and 6 Series MSO:https://www.tek.com/en/video/how-to/getting-signalvu-pc-running-on-5_6-series-msos
• SignalVu-PC Primer - Basics of Spectrum Analysis with SingalVu-PC: https://www.tek.com/en/video/how-to/signalvu-pc-primer---basics-of--spectrum-analysis
• SignalVu-PC Introduction and Basic Settings: https://www.youtube.com/watch?v=OpVf3rMHMQs

 

 

Moving on to the span dilemma.. You are correct that Spectrum View on the MSO58B has a maximum span of 500MHz (with option 5-SV-BW-1). If you are looking for a 0 to 2GHz span, then you may need use the MSO68B for increased span. Spectrum View’s span on the MSO68B can be set to a maximum span of 2GHz (with option 6-SV-BW-1). This can be found on page 49 of the MSO68B datasheet. This could be a viable option to reach the span you need. The 5/6 Series MSO’s Power and IMDA Harmonic measurements can both measure a maximum harmonic range of 0 to 200 harmonics.

• 6 Series B MSO Datasheet: https://www.tek.com/en/datasheet/6series-b-mso-mixed-signal-oscilloscope-datasheet

 

 

 

Let me know if you have any questions about the notes above, or if you would like a quote/pricing for any of the mentioned software/options. 

 

Best Regards,

 

Xander Budd

My mistake! Still, I think your best bet is to try different trigger settings. If it’s not CAN, then maybe the Serial trigger would work.

From the MSO70000C manual (p.72):

Trigger Selections

Serial                    Trigger on 64-bit NRZ serial pattern at data rates up to 1.25Gb/s and 4 8b/10b symbols at data rates up to 6.25Gb/s (MSO70000C/DX and DPO70000C/DX only). Requires option ST1G (DPO7000C) or ST6G (MSO70000C/DX and DPO70000C/DX). Includes clock recovery. Push the Push to Set 50% control to reinitialize clock recovery

Since you live by the Beaverton factory, the Tektronix Recycling and Material Salvage (RAMS) store would be a good place to look. It is open every first and third Thursday of each month I believe 1pm is when they open to the public only for a few hours before closing.

Hello,

Specifically which MDO oscilloscope do you have?

I would speculate that error message means the Save Target is set to a USB drive that was removed and that is what the error message indicates. Change the save target to the local drive or insert a USB and target that flash drive.

Once you tell me the scope model I can investigate options for mounting network drives. On my 5 Series I mounted a network folder that was shared from my PC and use that to transfer Session files and logfiles back and forth.

Another option for transferring files is to use PI commands. You can investigate the FILESystem: PI commands  in the MDO Programmer manual to see options.

Hi Midhun,

One of the trigger types available on your instrument is CAN Bus. You can tell the MSO70kC to trigger on a specific address or message.

So if you find a message in the link training algorithm that correlates with the problem you are debugging then you can trigger on that message type.

I think by default the TekExpress package attempts to configure all the horizontal, vertical, and trigger settings itself when you are using it. In that case it may be better to capture the .wfm waveforms on their own and then use TekExpress on those captured .wfm files.

Your 6 Series will also need to be optioned at minimum with 2.5GHz bandwidth for the 6-SV-BW-1 option to open up the span. It makes sense that a 1 GHz scope could not do 2 GHz of span but I wanted to mention it.

Hi Mike,

The 6 Series has a couple of options that open up the full Spectrum View performance:

6-SV-BW-1	Increase Spectrum View Capture Bandwidth to 2 GHz
6-SV-RFVT	Spectrum View RF versus Time analysis and remote IQ data transferring

And further analysis can be done in an external application called Tek SignalVu-PC.

You are correct the 5 Series maxes out at 500MHz span and this is a hardware limitation of the platform. The 6 Series can go out to 2GHz span with the 6-SV-BW-1 option.

What do you mean by "understand the input L and input C readings"? I can ask my IMDA expert colleagues to clarify those measurements but I'm not sure what your question is.

Thank you,

Seamus Brokaw

I found this tutorial too:<br> <a href="https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x3gXCAQ&amp;l=en-US">https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x3gXCAQ&amp;l=en-US</a><br> <br> &nbsp;

Hello,

The MSO24 is IVI compliant which means you can automate it using PI commands found in our programmer manual. The first three pages of this document "Getting Started with Oscilloscope Automation and Python" gives some background on PI, SCPI, and VISA.

https://www.tek.com/en/documents/technical-brief/getting-started-with-oscilloscope-automation-and-python

https://www.tek.com/en/manual/oscilloscope/2-series-mso-programmer-manual-2-series-mso

For Labview, there are basic VISA functions built-in where you manually connect, write, read, and format data how you want it. National Instruments also maintains a library of "drivers" for various instruments that do a lot of massaging and formatting for you. I recommend starting with the basic VISA commands because there is no MSO24 specific driver in their library.
https://www.ni.com/en-us/search.html?pg=1&amp;ps=10&amp;sb=%2Brelevancy&amp;sn=catnav:sup.dwl.idr&amp;q=tektronix%20mso24

To summarize, a basic LabVIEW PI command tutorial will help you establish a connection to the instrument and do an IDN? query. From there you can use the programmer manual to automate to your heart’s content. I found this tutorial from a little bit of searching:
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x1qzCAA&amp;l=en-US

Faraday cage is a good experiment to check for external EMI issues. If you short the CH3 and CH4 center pin to the shell of the BNC connectors, that would also show if any EMI is coupling in through the front end. I'm afraid if its an internal EMI source it may be harder to pinpoint and resolve. I haven't seen EMI issues display as a DC offset but it's not impossible.