Skip to main content
GW Instek MDO-2000E mixed-domain oscilloscope showing time and frequency domain displays

GW Instek MDO-2000E: Mixed-Domain Oscilloscope for Embedded and RF Debug

GSAS Engineering · · 7 min read

One Instrument, Two Domains

The GW Instek MDO-2000E is a mixed-domain oscilloscope (MDO) that combines a digital oscilloscope with a spectrum analyzer in a single instrument. Rather than using two separate instruments on the bench, an oscilloscope for time-domain signals and a spectrum analyzer for frequency-domain analysis, the MDO-2000E displays both simultaneously, correlated in time.

For engineers developing embedded systems with wireless connectivity (Wi-Fi, Bluetooth, Zigbee, LoRa, cellular), IoT devices, and RF-enabled products, this combined view solves a fundamental measurement problem: seeing what is happening in both domains at the same time.

Oscilloscope Specifications

The MDO-2000E’s oscilloscope section provides specifications suited to general-purpose embedded and mixed-signal debugging:

  • Bandwidth: 100 MHz and 200 MHz models
  • Channels: 2 analog + 1 dedicated RF input (some models), or 4 analog channels
  • Sample rate: Up to 1 GS/s
  • Memory depth: Up to 10 Mpoints per channel
  • Triggering: Edge, pulse, video, pattern, and serial bus triggers
  • Protocol decoding: I2C, SPI, UART, CAN, LIN (licence-based options)

Built-In Features

The MDO-2000E includes several capabilities that typically require separate licences on competing instruments:

  • Waveform generator: Built-in arbitrary waveform generator (25 MHz), useful for stimulus-response testing without a separate function generator
  • Logic analyzer: 16 digital channels (MSO models) for mixed-signal debugging
  • Protocol trigger and decode: Available for common serial buses
  • Power analysis: Automated power supply measurements (switching loss, harmonics, ripple)

Spectrum Analyzer Section

The spectrum analyzer input is a dedicated RF channel with its own front end, separate from the oscilloscope channels. This architectural choice matters, the RF input has appropriate impedance matching (50 ohm), sensitivity, and dynamic range for frequency-domain measurement.

  • Frequency range: 0 Hz to 2.5 GHz
  • Resolution bandwidth: Adjustable, suitable for narrowband signal analysis
  • Display modes: Normal spectrum, spectrogram (frequency vs time waterfall), persistence

Correlated Time-Frequency Display

The MDO-2000E’s defining feature is time correlation between the oscilloscope and spectrum analyzer views. When the engineer triggers the oscilloscope on a digital event, say, a microcontroller toggling a GPIO pin, the spectrum analyzer display shows the RF spectrum at that exact moment.

This correlation reveals:

  • RF emissions from digital switching: See which digital events cause spectral spurs
  • Wireless module behaviour: Correlate firmware actions (visible on digital channels) with RF transmission (visible on spectrum)
  • EMC debugging: Identify the time-domain source of spectral emissions
  • Interference diagnosis: Capture the time-domain signature of intermittent RF interference

Application: IoT Device Development

IoT devices combine a microcontroller, sensors, and a wireless module (Wi-Fi, BLE, LoRa, NB-IoT) on a single PCB. During development, engineers need to:

  1. Debug firmware using oscilloscope channels to monitor SPI/I2C communication with sensors
  2. Verify RF performance using the spectrum analyzer to confirm the wireless module transmits at the correct frequency with expected power
  3. Identify interference between the digital and RF sections of the board

The MDO-2000E handles all three on a single instrument, reducing bench clutter and measurement setup time.

Practical Example: BLE Module Commissioning

  • Oscilloscope channel 1: SPI clock between microcontroller and BLE module
  • Oscilloscope channel 2: SPI MOSI data line
  • Spectrum analyzer: 2.4 GHz band, monitoring BLE advertising packets
  • Digital channels (MSO): GPIO pins indicating firmware state (advertising, connected, sleeping)

When the firmware commands the BLE module to start advertising, the engineer sees the SPI transaction, the GPIO state change, and the 2.4 GHz advertising signal appear, all time-correlated. If the BLE module fails to transmit, the time correlation immediately reveals whether the SPI command was sent correctly, whether the firmware reached the expected state, and whether any RF energy appeared at all.

Application: EMC Pre-Compliance

The MDO-2000E’s combined oscilloscope and spectrum analyzer capabilities support in-house EMC investigation:

  • Use the spectrum analyzer to identify problematic emission frequencies
  • Switch to the oscilloscope view and trigger on the digital signals that operate at or near those frequencies
  • Identify the specific circuit activity causing the emission
  • Modify the design and re-measure immediately

This iterative debug cycle, measure emission, identify source, modify, re-measure, is dramatically faster with a single-instrument MDO than with separate oscilloscope and spectrum analyzer setups.

Comparison with Separate Instruments

An engineer could achieve similar measurement capability with a standalone oscilloscope and a standalone spectrum analyzer. The MDO-2000E’s advantage is integration:

  • Single instrument instead of two, lower total cost, less bench space
  • Time correlation between domains, not possible with separate instruments unless they share an external trigger and careful synchronization
  • Simplified setup: one set of probes, one interface, one learning curve

The trade-off: a dedicated spectrum analyzer typically offers better sensitivity, dynamic range, and frequency resolution than the spectrum analyzer section of an MDO. For EMC compliance-grade measurements or sensitive RF receiver characterization, a dedicated spectrum analyzer remains the right tool.

Why Buy GW Instek from GSAS

GSAS Micro Systems is an authorized GW Instek partner, providing the full oscilloscope, power supply, and test instrument range with INR invoicing and local support.

  • Demo units available at offices in Bengaluru, Hyderabad, Chennai, Pune, Mumbai, and Delhi NCR
  • Application engineering for IoT, embedded, and EMC measurement setups
  • INR invoicing with GST-compliant documentation
  • Calibration coordination through NABL-traceable service

Request a quote → · Book a demo →

Interested in GW Instek tools?

Talk to our application engineers for personalized tool recommendations.

Stay in the Loop

Get monthly compliance updates, product insights, and engineering best practices delivered to your inbox.

Related Articles

Master and slave roles on a 100BASE-T1 link: the master PHY times its transmitter from a local clock, the slave recovers the clock from the received signal, with the both-master and both-slave misconfigurations that leave the link down, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

100BASE-T1 Link Won't Come Up: A Vendor-Neutral Checklist

A 100BASE-T1 link that will not come up is almost never a mystery, but the answers on the web are written per silicon vendor and do not transfer. This is the ordered bring-up checklist that holds regardless of which PHY, switch or SoC you have: physical layer first, then the PHY over MDIO, then the master and slave pairing, then the causes of a link that comes up and drops. The standards and tooling claims trace to IEEE 802.3 task force records, the Linux ethtool and kernel documentation or published test material. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 14 min read
Side by side comparison of a 10BASE-T1S multidrop mixing segment, one balanced pair with four nodes on short stubs and a termination at each end, against a point to point star of four separate links into switch ports, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

10BASE-T1S and PLCA: Multidrop Ethernet Explained

10BASE-T1S is the one member of the T1 single-pair Ethernet family that keeps a shared medium, and PLCA is the reconciliation sublayer that stops the nodes on it from colliding. This article covers what IEEE 802.3cg standardises, how the beacon and transmit opportunities schedule a cycle, the node count and segment length figures the OPEN Alliance interoperability test suite works to, and the failure modes that put a segment quietly back into contention while every link still looks up. Written by the GSAS Micro Systems engineering team in India for teams bringing up multidrop segments on the bench.

29 Aug 2026 · 12 min read
Horizontal stacked bar showing where an ADAS test vehicle's bandwidth budget is spent, split into cameras, lidar, radar and bus traffic, with the logger uplink limit drawn as a vertical rule crossing the bar, from GSAS Micro Systems India
Automotive Ethernet Automotive & Mobility

ADAS Sensor Data Logging: Bandwidth Budgets That Add Up

Every page that tells you an ADAS test vehicle produces terabytes a day states the headline and skips the arithmetic, so you cannot redo it for your own sensor set. This article publishes the arithmetic instead: one formula, every table row derived on the page, a worked eight-hour drive that chains those rows into a sustained write rate, a media count and an offload window, and the five places bandwidth budgets go wrong. Written by the GSAS Micro Systems engineering team in India.

29 Aug 2026 · 15 min read