OWON HDS 200 Handheld Oscilloscope w/ builtin DMM/AWG

[csuhi17]

One problem with Owon / Hantek is they seem to constantly modify their pcb design based on what inexpensive surplus parts are available at the time.  The result is many different hardware versions of the same product, which beyond possibly affecting operation or performance can also require different FW to run.  This leads to a lot of variations in performance from version to version and also reduces likelihood of FW updates, since they need to create FW for several hardware boards of the same product.  If you get a product from these companies and it works well, you cannot necessarily expect earlier or later versions to operate the same way - there is a LOT of variability in their products.  And if you discover software bugs, you cannot always assume they will address them with future updates.  Same applies for clone products from other companies that all share the same basic BOM - they all look the same, but can operate very differently.

I have old Owon HDS1021M and it still works ok for what it is but never a FW update for my version - instead they release new HDS1021M-N version which is the same product but different pcb.  Very frustrating.

Are you sure they are the same?
From what I found, the N got more memory, a higher sample rate, etc.

[TomKatt]

Yes - the N revision did include improved specs but nonetheless replaced the M version.  When the N version was released no new FW was available for the original version.  That is representative of Owon / Hantek support from my (albeit limited) experience.

Different hardware builds are not uncommon, but more upscale companies tend to continue supporting their earlier releases rather than simply replacing them and dropping all support.

[electr_peter]

I agree with the sentiment on too many HW revisions and limited supported for previous versions. On top of that, Owon has too many similar handheld models with minimal differences (consider HDS300 with almost the same specs as HDS200).
Still, Owon HDS200 range is pretty reasonable handheld scope with real specs. UI needs some improvements and there are some small bugs, but other than that scope is very usable.

[LiberaVeritas]

Got a 242S
HW version 3.3.2
FW version 8.6.4

Doesn't seem like there are any v8 FW downloads on the website

The ohmmeter auto ranging is quite slow

[alank2]

I tried to get the latest firmware from the OWON site, but it doesn't seem to work.  I select my model HDS242 and type in my firmware V8.1.0 and it doesn't find any.

[Othman]

Got a 242S
HW version 3.3.2
FW version 8.6.4

Doesn't seem like there are any v8 FW downloads on the website

The ohmmeter auto ranging is quite slow

this hds242 with this FW should has a RMS measurment
kindly confirm

[csuhi17]

If I remember correctly, those above V4 or V5 already contain it.
Unfortunately, mine is the V3, which does not include...

[Othman]

Got HDS242
HW version 3.3.2
FW version 8.4.0
it has a RMS measurement
is this feature "RMS measurement" related to HW ?

[firepower]

Built the Bungle Curve Tracer, Designed A 3d printed box in OpenScad. I included stl and openscad files. 3D printed box is 70x20x20mm, tight fit, great little project.
Use a smooth build plate if you want text visible, lol

[electr_peter]

How do you change Signal Generator Hi-Z ? is there 50 ohm mode?

Go to 2nd page of [System] to set impedance.

[alank2]

Has anyone had any luck with their firmware page?

https://www.owon.com.hk/download.asp?category=Digital%20Oscilloscope&series=HDS200%20Series&model=HDS242(S)&SortTag=Latest%20Firmware

I put in V8.1.0 and it shows nothing.  If I try V8.0.0, it still shows nothing.

I emailed them a couple weeks ago and no reply either.

[konnor]

I had a free minute and managed to resolve the issue of downloading the firmware from my device to a file.
In addition to the main firmware (version V3.0.1 for HDS2102S, not on the website), I also saved the bootloader.

Results of a little bootloader research:

1) Firmware can consist of three components: main cpu firmware, fpga frimware and configuration block. All firmware I know contain only the first two components. The configuration block is unique for each device, because contains the serial number and calibration parameters.
2) The firmware contains a text string indicating the base model of the device. This line encodes both real hardware features (ADC configuration, presence of a generator, etc.) and some purely software restrictions.
Sample:
HDS2<Freq>2<Generator>_<submodel>
"HDS2" - start signature
Freq - Max osc bandwith:
200MHz model: Model[4]=='2' && Model[5] == '0'
100MHz model: Model[4]=='1' && Model[5] == '0'
 70MHz model: Model[4]=='7'
 50MHz model: Model[4]=='5'
 40MHz model: Model[4]=='4'
Generator: 'S' after "HDS" and before any '_'

The submodel string has a random format (and may not be present at all).

The main firmware analyzes the following signatures:
'E' Model(maybe HDS300?): There is an "E" character anywhere on the line.
ADC LS08D1500: "_LS" after "HDS"
1/S   models: "_1" or "_LS" after "HDS"
1/S   models - some hardware diff on ADC work.


Update steps:
1) backup config block to ram
2) if set update flag (in config block), set bootloader update flag and reset flag in config block
3) check serial no and reset (if bad):
  if ( SerialNumberCode >= 2000000 && SerialNumberCode < 3500000
    || SerialNumberCode >= 20000000 && SerialNumberCode < 35000000
    || SerialNumberCode >= 200000000 && SerialNumberCode < 350000000 )
  {
    BackupFlashCfgArea();
    sprintf_0(BackupCfgArea.SerialNumberString, "%d", SerialNumberCode);
    SerialNumberCode = 0xFFFFFFFF;
    StartConfigArea.ResetToDefaultReq = 1;
    RestoreCfgArea();
  }
4) open file "Scope.upp"
5) check header and file CRC
6) compare hw model string (current flash and Scope.upp) if mismatch - stop update
7) check version string (V{aa}.{bb}.{cc}[zz]).
   If there are one or two "z's" at the end of the version string, no further version checking is performed.
   Main version code (aa) - hardware submodel id. It must match in the file and on the current device.
   bb.cc - firmware version. flash firmware version <= file firmware version, else error
check crc and update fpga firmware (if present)
9) check crc and update config block (if present)
10) check crc and update cpu firmware (if present)
11) store new version to config block
12) write config block to flash
13) one beep (100 ms)
14) delete file "Scope.upp"
15) reload

Thus, the first firmware version number is loosely related to the time of its release and only determines the subversion of the hardware platform. Relatively speaking, firmware V8.1.2 may be released earlier than V6.5.7 (all version numbers are random)