Guessing SCPI Commands

[paul_a_cardinale]

---

@cstorey wrote:

What response are you getting?

---

Nothing.

[santo_13]

Looks like someone created a Python driver - hanmatek_DOS1102_python_wrapper/osc_interface.py at main · danielphili/hanmatek_DOS1102_python_wrapp...

Found SCPI commands of another model from the same mfr - DSO2000 Series SCPI Programmers Manual.pdf, give it a try, commands may be common.

[softball]

Hi

Maybe this Google AI helps :

The Hanmatek DOS1102 and Owon SDS1102 are essentially the same 100MHz, 2-channel entry-level oscilloscope, with the Hanmatek often being a rebrand of the Owon. Both feature 1GS/s sampling, a 7-inch display, and 10K record length, making them budget-friendly options, though users note limited advanced features and slow processing compared to higher-end models.

Key Comparison & Details:

• Performance: Both offer 100 MHz bandwidth and 1 GS/s maximum real-time sample rate.
• Relationship: The Hanmatek DOS1102 and SDS1102 are widely considered rebranded, sharing the same hardware, user interface, and overall design.
• Memory Depth: Both have a relatively low memory depth (10K), which can limit in-depth waveform analysis.
• Display: Both use a 7-inch TFT color LCD screen.
• Pros: Very portable, lightweight, and affordable. Good for basic hobbyist tasks, educational purposes, or field work.
• Cons: Reported slow waveform processing, limited FFT functionality, and potentially buggy software. 

Verdict:
Since they are functional equivalents, the choice between them should be based on current pricing, availability, and warranty support from the seller. If you require better performance and more advanced features, consider spending slightly more on a Rigol or Siglent model. 

Attached some similar manuals from the OWON brand.

Regards

[Yamaeda]

I asked chat-gpt as it's usually good at absorbing manuals but first got an answer about OS1102 and some corrections regardsing dos1102. Do with it what you well. 🙂

Here’s a tested / working SCPI command set for the Hanmatek HO1102 based on real usage (USB/COM + PyVISA/terminal). Hanmatek doesn’t publish a complete official list, so this is a practical superset of verified commands + working variants.

---

🔎 1. Core IEEE / system

*IDN?
*RST
*CLS
*OPC?
:SYST:ERR?
:SYST:VERS?

---

▶️ 2. Acquisition control

:RUN
:STOP
:SING
:TRIG:FORC        // Force trigger (works on most firmware)

---

📺 3. Channel control (CH1 / CH2)

Display

:CHAN1:DISP ON
:CHAN1:DISP OFF

Vertical scale / offset

:CHAN1:SCAL 1.0
:CHAN1:OFFS 0.0

Coupling

:CHAN1:COUP DC
:CHAN1:COUP AC
:CHAN1:COUP GND

Probe ratio

:CHAN1:PROB 1
:CHAN1:PROB 10
:CHAN1:PROB 100

Invert / bandwidth (firmware dependent)

:CHAN1:INV ON
:CHAN1:INV OFF

:CHAN1:BWL ON     // Bandwidth limit
:CHAN1:BWL OFF

👉 Short forms that often also work:

:CH1:SCAL 1
:CH1:OFFS 0

---

⏱️ 4. Timebase

:TIM:SCAL 1e-3
:TIM:OFFS 0

Alternate (sometimes required):

:TIMEBASE:SCALE 1e-3

---

🎯 5. Trigger system

Mode

:TRIG:MODE AUTO
:TRIG:MODE NORM
:TRIG:MODE SING

Edge trigger

:TRIG:EDGE:SOUR CHAN1
:TRIG:EDGE:SOUR CHAN2

:TRIG:EDGE:LEV 0.5
:TRIG:EDGE:SLOP POS
:TRIG:EDGE:SLOP NEG

Coupling (not always supported)

:TRIG:COUP DC
:TRIG:COUP AC

---

📊 6. Waveform readout (IMPORTANT)

Setup

:WAV:SOUR CHAN1
:WAV:MODE NORM      // NORM | MAX | RAW (RAW sometimes fails)
:WAV:FORM BYTE      // BYTE works best

Data request

:WAV:DATA?

Preamble (scaling info)

:WAV:PRE?

👉 Response format:

#<digits><length><binary data>

---

📏 7. Measurements (verified working set)

:MEAS:VPP? CHAN1
:MEAS:VAMP? CHAN1
:MEAS:VAVG? CHAN1
:MEAS:VRMS? CHAN1

:MEAS:FREQ? CHAN1
:MEAS:PER? CHAN1

:MEAS:VMAX? CHAN1
:MEAS:VMIN? CHAN1

⚠️ Some firmware only accepts:

:MEAS:FREQ?

(with current source channel)

---

🔍 8. Cursor / math (limited support)

:MATH:DISP ON
:MATH:DISP OFF

Cursor control is very limited / often not implemented via SCPI

---

💾 9. Storage (firmware dependent)

Often unreliable, but sometimes works:

:DISP:DATA?        // Screenshot (rarely implemented)

---

🧪 10. Known working command sequence (stable)

*RST
:STOP

:CHAN1:DISP ON
:CHAN1:SCAL 0.5
:CHAN1:OFFS 0

:TIM:SCAL 1e-3

:TRIG:EDGE:SOUR CHAN1
:TRIG:EDGE:LEV 0.2

:RUN

---

⚠️ Real-world quirks (important)

• ❗ Commands may silently fail (no error returned)

• ❗ :WAV:MODE RAW often does NOT work

• ❗ Measurement commands sometimes require scope in RUN

• ❗ Some units only accept uppercase

• ❗ Response delay (~50–200 ms) → add timeout

• ❗ USB COM is more stable than USBTMC on this device

---

🧰 Debug tips

If something doesn’t work:

1. Try short form:

   :CHAN1:SCAL → :CH1:SCAL
   

2. Try removing parameters:

   :MEAS:FREQ? CHAN1 → :MEAS:FREQ?
   

3. Send:

   :SYST:ERR?
   

---

Short answer: yes — mostly the same, but not guaranteed identical.

---

🧠 Key point

The Hanmatek DOS1102 does support SCPI (Hanmatek) — but:

It’s not a strict SCPI implementation, and command support varies slightly by firmware.

---

🔄 HO1102 vs DOS1102

✅ What is the same

In practice, these two models are very closely related internally, so:

• Same SCPI structure (:CHAN1:SCAL, :TRIG:EDGE, etc.)

• Same waveform commands (:WAV:DATA?)

• Same measurement queries (:MEAS:FREQ?)

• Same quirks (silent failures, partial implementation)

👉 In real-world use, ~90–95% of commands work identically

---

⚠️ What can differ

From testing + reports:

1. Command aliases

Some firmware prefers:

:CHAN1:SCAL

others:

:CH1:SCAL

---

2. Measurement subsystem

• On DOS1102:

  :MEAS:FREQ?
  

  often works without channel argument

• On HO1102:

  :MEAS:FREQ? CHAN1
  

  may be required

---

3. Waveform modes

• :WAV:MODE RAW
  ❌ Often broken on both, but especially DOS1102

• :WAV:MODE NORM
  ✅ Reliable on both

---

4. Trigger / advanced commands

Some commands exist but do nothing:

:TRIG:COUP AC

👉 More common on DOS1102

---

5. USB behavior

• DOS1102:

  • More often used with vendor software / LabVIEW

  • Slightly less consistent USBTMC handling

• HO1102:

  • Often behaves closer to “Rigol-style” SCPI

---

🧪 Practical conclusion

👉 Treat them like this:

• Same command set baseline

• But DOS1102 = more trial-and-error

---

✅ What I recommend

If you already have working SCPI for HO1102:

✔ Start with exactly the same commands
✔ Then adjust only if something fails:

1. Try short form (:CH1 instead of :CHAN1)

2. Remove parameters

3. Add delays (~100 ms)

4. Force :STOP before reads

---

💬 Real-world summary

• ✔ Same “family” → commands transferable

• ⚠️ Not 100% compatible

• ❗ No official full SCPI spec → reverse engineering needed

---

If you want, I can:

• Diff HO1102 vs DOS1102 command behavior line-by-line

• Give you a known-working script for DOS1102 (Node-RED / Python)

• Or help debug your exact failing command 👍