OWON HDS 200 Handheld Oscilloscope w/ builtin DMM/AWG

• #450 Reply
  Posted by konnor on 27 Sep, 2022 12:37
• The results of a small study.
  
  - The upp file consists of a header and several files.
    For the case with the HDS200 line, there are two files inside
    1)CPU firmware 
    2)FPGA firmware.
    No pack.
  
  - Firmware files with same FW version, but different device (242/272/242S/272S) - are identical.
    The only difference is in the model name in the header of the upp file.
    The CPU and FPGA files are the same in all variants.
  
  Known version/model names (in firmware header):
  Grouped by matching files in firmware
  
  Version     Device platform name
  V1.7.0    HDS272S
  V1.7.0zz  HDS242S
  ------------------
  V3.3.3    HDS272S_1
  V3.3.3    HDS272_1
  V3.3.3    HDS242S_1
  V3.3.3    HDS242_1
  ------------------
  V4.6.1    HDS272S_1
  V4.6.1    HDS272_1
  V4.6.1     HDS242S_1
  V4.6.1    HDS242_1
  ------------------
  V4.6.2    HDS272S_1
  ------------------
  V5.6.2zz  HDS272S_1
  ------------------
  V5.6.3    HDS272S_1
  ------------------
  V5.7.1    HDS272S_1
  V5.7.1    HDS272_1
  V5.7.1    HDS242S_1
  V5.7.1    HDS242_1
  ------------------
  V6.1.0    HDS272S_1
  V6.1.0     HDS272_1
  V6.1.0    HDS242S_1
  V6.1.0    HDS242_1
  ------------------
  V1.4.1    HDS2102S_1
  ------------------
  V1.5.1    HDS2102_1
  V1.5.1    HDS2102S_1
  ------------------
  V2.0.4    HDS2102_LS
  V2.0.4    HDS2102S_LS
  
  Different HW platform:
  
  low speed ADC (MXT208)
  1)HDS2*2*
  2)HDS2*2*_1
  
  High speed ADC:
  3)HDS2102*_1    - ADC HMCAD1511
  4)HDS2102*_LS    - ADC LS08D1500
  
  It is a pity that there is no firmware from my device on the site.
  Only old version (2.0.4)
  
  Used CPU resource:
  
  USART0 - debug console + alternative SCPI (3 pin socket) (115200)
  USART1 - DMM Interface (9600)
  SPI0 - internal disk nvram
  SPI1 - FPGA nvram
  ADC - batt monitoring + calibrate procedure
  
  gpio:
  PA0 - power key
  PA1 - power control (0 - off)
  PA4 - SPI0 CS
  PB0 - Charger (?)
  PB1 - USB detect(?)
  PB5-8 - DMM Control
  PB12 - SPI1 CS
  PC0-2 - Keyboard
  PC13-15 - Keyboard
  PD3 - DMM Control
  PD6 - DMM Control
  PE0-1 - Keyboard
  
• #451 Reply
  Posted by hobbeeist on 30 Sep, 2022 05:05
• konnor,
  
  I don't see the string "HDS" anywhere in the upp file I used to upgrade. Did you perform some sort of decryption first?
• #452 Reply
  Posted by konnor on 30 Sep, 2022 11:20
• Yes, some time ago I took care of writing a simple packer / unpacker for OWON firmware (not only for HDS200). If needed, I can post it. But I'm a little worried that this will increase the number of "bricked" devices. Not everyone has a jtag adapter, and the boot sector is not included in the update.
  
  
• #453 Reply
  Posted by rn777 on 30 Sep, 2022 18:59
• Need. Please, post it.
• #454 Reply
  Posted by konnor on 30 Sep, 2022 19:20
• There are two modes of operation - disassemble the firmware into components and assemble the firmware from the components. If everything works fine, then when you perform two operations in sequence, you should get a file that matches the initial file.
  

  ---

  owon_upp_maker.zip
• #455 Reply
  Posted by hobbeeist on 02 Oct, 2022 07:22
• Were there any undocumented features you came across in your investigation? Maybe some secret API commands, or functions that are present, but not called?
• #456 Reply
  Posted by konnor on 02 Oct, 2022 09:49
• Some undocumented SCPI extension.
  
  !!!DON'T USE command "SECurity"!!!
  It removes the protection bits, but I'm not sure that this will not erase the
  entire firmware. In this case, the device will be irreversibly corrupted.
  Unfortunately, I don't have a 3.0.1 firmware image, and jtag appears to be blocked.
  Because of this, I can't do any experiments yet.
  I really do not want to roll back to 2.0.4 (which is _possibly_ compatible).
  
  By the way - owners of HDS2102 with firmware 2.0.4 can ask OWON about the possibility of updating to 3.0.1.
  
  
  main SCPI parser three:
    CH1 = SCPI_AddHook(0, "CH1", 0, 0);
    SCPI_AddHook(CH1, "DISPlay", (int (__fastcall *)(char *))SCPI_CH1_DISPlay_Set, SCPI_CH1_DISPlayGetText);
    SCPI_AddHook(CH1, "COUPling", (int (__fastcall *)(char *))SCPI_CH1_SetupCoupling, SCPI_CH1_GetCoupling);
    SCPI_AddHook(CH1, "BANDwidth", (int (__fastcall *)(char *))SCPI_CH1_SetupBandwidth, SCPI_CH1_GetBandwodthText);
    SCPI_AddHook(CH1, "PROBe", (int (__fastcall *)(char *))SCPI_SetupProbe, SCPI_CH1_GetProbeText);
    SCPI_AddHook(CH1, "SCALe", (int (__fastcall *)(char *))SCPI_CH1_SetupVScale, SCPI_CH1_GetScaleText);
    SCPI_AddHook(CH1, "OFFSet", (int (__fastcall *)(char *))SCPI_SetOffset_1, SCPI_CH1_GetOffset);
    CH2 = SCPI_AddHook(0, "CH2", 0, 0);
    SCPI_AddHook(CH2, "DISPlay", (int (__fastcall *)(char *))SCPI_CH2_DisplaySet, SCPI_CH2_DisplayGet);
    SCPI_AddHook(CH2, "COUPling", (int (__fastcall *)(char *))SCPI_CH2_CouplingSet, SCPI_CH2_CouplingGet);
    SCPI_AddHook(CH2, "BANDwidth", (int (__fastcall *)(char *))SCPI_CH2_BandWidthSet, SCPI_CH2_BandWidthGet);
    SCPI_AddHook(CH2, "PROBe", (int (__fastcall *)(char *))SCPI_CH2_ProbeDividerSet, SCPI_CH2_ProbeDividerGet);
    SCPI_AddHook(CH2, "SCALe", (int (__fastcall *)(char *))SCPI_CH2_SetupVScale, SCPI_SCPI_CH2_VScaleGet);
    SCPI_AddHook(CH2, "OFFSet", (int (__fastcall *)(char *))SCPI_CH2_OffsetSet, SCPI_CH2_OffsetGet);
    Hor = SCPI_AddHook(0, "HORizontal", 0, 0);
    SCPI_AddHook(Hor, "SCALe", (int (__fastcall *)(char *))SCPI_HorScaleSet, SCPI_HorScaleGet);
    SCPI_AddHook(Hor, "OFFSet", (int (__fastcall *)(char *))SCPI_HorOffsetSet, SCPI_GetHorOffset);
    ACQuire = SCPI_AddHook(0, "ACQuire", 0, 0);
    SCPI_AddHook(ACQuire, "MODe", (int (__fastcall *)(char *))SCPI_ChangePeakMode, SCPI_GetPeakModeStr);
    SCPI_AddHook(ACQuire, "DEPMem", (int (__fastcall *)(char *))SCPI_ChangeDepMem, SCPI_GetDepMemStr);
    Data = SCPI_AddHook(0, "DATa", 0, 0);
    Data_Wawe = SCPI_AddHook(Data, "WAVe", 0, 0);
    Data_Wawe_Screen = SCPI_AddHook(Data_Wawe, "SCReen", 0, SCPI_Data_Wawe_Screen_CH1);
    SCPI_AddHook(Data_Wawe_Screen, "CH1", 0, SCPI_Data_Wawe_Screen_CH1);
    SCPI_AddHook(Data_Wawe_Screen, "CH2", 0, SCPI_Data_Wawe_Screen_CH2);
    SCPI_AddHook(Data_Wawe_Screen, "HEAD", 0, SCPI_Data_Wave_Screen_Head);
    Trigger = SCPI_AddHook(0, "TRIGger", 0, 0);
    SCPI_AddHook(Trigger, "STATus", 0, SCPI_GetTriggerStatusText);
    Trigger_single = SCPI_AddHook(Trigger, "SINGle", 0, 0);
    Trigger_single_edge = SCPI_AddHook(
                            Trigger_single,
                            "EDGe",
                            (int (__fastcall *)(char *))SCPI_SetEdgeMode,
                            SCPI_GetEdgeText);
    SCPI_AddHook(Trigger_single_edge, "LEVel", (int (__fastcall *)(char *))SCPI_SetTriggLevel, SCPI_GetTriggLevel);
    SCPI_AddHook(Trigger_single_edge, "SOURce", (int (__fastcall *)(char *))SCPI_SetTriggSourcfe, SCPI_GetTriggSourceText);
    SCPI_AddHook(Trigger_single, "SOURce", (int (__fastcall *)(char *))SCPI_SetTriggSourcfe, SCPI_GetTriggSourceText);
    SCPI_AddHook(Trigger_single, "COUPling", (int (__fastcall *)(char *))SCPI_Setup_AC_DC, SCPI_GetCoupling);
    SCPI_AddHook(Trigger_single, "SWEep", (int (__fastcall *)(char *))SCPI_SetSWeepMode, SCPI_GetTriggerModeStr);
    MEASuremen = SCPI_AddHook(0, "MEASuremen", 0, 0);
    SCPI_AddHook(
      MEASuremen,
      "DISPlay",
      (int (__fastcall *)(char *))SCPI_MEASuremen_Display_Set,
      SCPI_MEASuremen_Display_Get);
    MEASuremen_CH1 = SCPI_AddHook(MEASuremen, "CH1", 0, 0);
    SCPI_AddHook(MEASuremen_CH1, "MAX", 0, SCPI_MEASuremen_CH1_MaxGet);
    SCPI_AddHook(MEASuremen_CH1, "MIN", 0, SCPI_MEASuremen_CH1_MinGet);
    SCPI_AddHook(MEASuremen_CH1, "PKPK", 0, SCPI_MEASuremen_CH1_PkPkGet);
    SCPI_AddHook(MEASuremen_CH1, "VAMP", 0, SCPI_MEASuremen_CH1_VampGet);
    SCPI_AddHook(MEASuremen_CH1, "AVERage", 0, SCPI_MEASuremen_CH1_AverageGet);
    SCPI_AddHook(MEASuremen_CH1, "PERiod", 0, SCPI_MEASuremen_CH1_PeriodeGet);
    SCPI_AddHook(MEASuremen_CH1, "FREQuency", 0, SCPI_MEASuremen_CH1_Freq);
    SCPI_AddHook(MEASuremen_CH1, "RTime", 0, SCPI_MEASuremen_CH1_RTime);
    SCPI_AddHook(MEASuremen_CH1, "FTime", 0, SCPI_MEASuremen_CH1_FTime);
    SCPI_AddHook(MEASuremen_CH1, "PWIDth", 0, SCPI_MEASuremen_CH1_PWidth);
    SCPI_AddHook(MEASuremen_CH1, "NWIDth", 0, SCPI_MEASuremen_CH1_NWidth);
    SCPI_AddHook(MEASuremen_CH1, "SQUAresum", 0, SCPI_MEASuremen_CH1_SquareSum);
    MEASuremen_CH2 = SCPI_AddHook(MEASuremen, "CH2", 0, 0);
    SCPI_AddHook(MEASuremen_CH2, "MAX", 0, SCPI_MEASuremen_CH2_MaxGet);
    SCPI_AddHook(MEASuremen_CH2, "MIN", 0, SCPI_MEASuremen_CH2_MinGet);
    SCPI_AddHook(MEASuremen_CH2, "PKPK", 0, SCPI_MEASuremen_CH2_PkPkGet);
    SCPI_AddHook(MEASuremen_CH2, "VAMP", 0, SCPI_MEASuremen_CH2_VampGet);
    SCPI_AddHook(MEASuremen_CH2, "AVERage", 0, SCPI_MEASuremen_CH2_AverageGet);
    SCPI_AddHook(MEASuremen_CH2, "PERiod", 0, SCPI_MEASuremen_CH2_PeriodeGet);
    SCPI_AddHook(MEASuremen_CH2, "FREQuency", 0, SCPI_MEASuremen_CH2_FreqGet);
    SCPI_AddHook(MEASuremen_CH2, "RTime", 0, SCPI_MEASuremen_CH2_RTimeGet);
    SCPI_AddHook(MEASuremen_CH2, "FTime", 0, SCPI_MEASuremen_CH2_FTimeGet);
    SCPI_AddHook(MEASuremen_CH2, "PWIDth", 0, SCPI_MEASuremen_CH2_pWidthGet);
    SCPI_AddHook(MEASuremen_CH2, "NWIDth", 0, SCPI_MEASuremen_CH2_NWidthGet);
    SCPI_AddHook(MEASuremen_CH2, "SQUAresum", 0, SCPI_MEASuremen_CH2_SquareSumGet);
    Function = SCPI_AddHook(0, "FUNCtion", (int (__fastcall *)(char *))SCPI_SetGeneratorMode, SCPI_GetGeneratorMode);
    SCPI_AddHook(Function, "FREQuency", (int (__fastcall *)(char *))SCPIFun_Freq_Set, SCPI_Fun_Freq_Get);
    SCPI_AddHook(Function, "PERiod", (int (__fastcall *)(char *))SCPI_Fun_Period_Set, SCPI_Fun_Period_Get);
    SCPI_AddHook(Function, "AMPLitude", (int (__fastcall *)(char *))SCPI_Fun_Ampl_Set, SCPI_Fun_Ampl_Get);
    SCPI_AddHook(Function, "OFFSet", (int (__fastcall *)(char *))SCPI_Fun_Offset_SEt, SCPI_Fun_Offset_Get);
    SCPI_AddHook(Function, "HIGHt", (int (__fastcall *)(char *))SCPI_Fun_Hightt_SEt, SCPI_Fun_Hightt_GEt);
    SCPI_AddHook(Function, "LOW", (int (__fastcall *)(char *))SCPI_Fun_Low_SEt, SCPI_Fun_Low_GEt);
    SCPI_AddHook(Function, "SYMMetry", (int (__fastcall *)(char *))SCPI_Fun_Symmetry_SEt, SCPI_Fun_Symmetry_GEt);
    SCPI_AddHook(Function, "WIDTh", (int (__fastcall *)(char *))SCPI_Fun_Width_SEt, SCPI_Fun_Width_GEt);
    SCPI_AddHook(Function, "DTYCycle", (int (__fastcall *)(char *))SCPI_Fun_Duty_SEt, SCPI_Fun_Duty_GEt);
    SCPI_AddHook(Function, "RISing", (int (__fastcall *)(char *))SCPI_Fun_Rising_SEt, SCPI_Func_Rising_Get);
    SCPI_AddHook(Function, "FALing", (int (__fastcall *)(char *))SCPI_Fun_Faling_SEt, SCPI_Fun_Faling_GEt);
    SCPI_AddHook(Function, "LOAD", (int (__fastcall *)(char *))SCPI_Fun_LoadOnOff_SEt, SCPI_Fun_LoadOnOff_GEt);
    SCPI_AddHook(0, "CHANnel", (int (__fastcall *)(char *))SCPI_ArbChannelSet, SCPI_ChannelGet);
    SCPI_AddHook(0, "MODel", 0, SCPI_Get_String_Model);
    SCPI_AddHook(0, "SERial", (int (__fastcall *)(char *))SCPI_Set_String_Serial, 0);
    SCPI_AddHook(0, "AUToset", (int (__fastcall *)(char *))SCPI_Autoset, 0);
    SCPI_AddHook(0, "Selfcorrec", (int (__fastcall *)(char *))SCPI_Selfcorrec_Set, 0);
    SCPI_AddHook(0, "SECurity", (int (__fastcall *)(char *))SPCI_SecuritySet, 0);
    DMM = SCPI_AddHook(0, "DMM", (int (__fastcall *)(char *))SCPI_DMM_Config_Set, SCPI_DMM_Get_String);
    DMM_Configure = SCPI_AddHook(DMM, "CONFigure", (int (__fastcall *)(char *))SCPI_DMM_Config_Set, SCPI_DMM_Get_String);
    SCPI_AddHook(DMM_Configure, "VOLTage", (int (__fastcall *)(char *))SCPI_DMMConfVoltSet, SCPI_DMM_Get_String_Voltage);
    SCPI_AddHook(DMM_Configure, "CURRent", (int (__fastcall *)(char *))SCPI_DMMConfCurrSet, SCPI_DMM_Get_String_Current);
    SCPI_AddHook(DMM, "REL", (int (__fastcall *)(char *))SCPI_DMM_Rel_Set, SCPI_DMM_Rel_Get);
    SCPI_AddHook(DMM, "RANGE", (int (__fastcall *)(char *))SCPI_DMM_Range_Set, SCPI_DMM_Range_Get);
    SCPI_AddHook(DMM, "AUTO", (int (__fastcall *)(char *))SCPI_DMM_AutoSet, SCPI_DMM_AutoGet);
    SCPI_AddHook(DMM, "MEAS", 0, SCPI_DMM_MeasGet);
    SCPI_AddHook(0, "VIDEO", SCPI_SetVideo, 0);
    SCPI_AddHook(0, "VOLFULL", SCPI_VOLFULL, 0);
  
  Separate command:
  STARTDEBUGTXT - HW model info
  COLOR - lcd palette setup
  SOFTWARERESET - reset
  
  Special key seq:
  Sys,sys,up,up,down,down,left,left,right,right - switch key "system" to enter specail menu
  
  in Measure menu:
  f3,f3,f4,f4,f3,f4,f3f4 - run some VERY long operations (7 step), with the output of not quite clear results. The operations are really long, and the device does not respond to the buttons at this time.
  
  I can't say what the consequences will be (probably nothing worse than having to reset to default and recalibrate), but BETTER DO NOT EXPERIMENT.
  
• #457 Reply
  Posted by JogaBonito5 on 02 Oct, 2022 10:05
• Quote from: JogaBonito5 on 26 Sep, 2022 17:07

  Hello guys, I just bought the OWON HDS242!
  
  I attached some pictures regarding software information and PCB revision.
  
  I just have one minor problem: I have no batteries right now so the only way to turn it on is via USB cable. The problem is that when i plug it in, the power button starts flashing without stop. The oscilloscope works without any issues but this red flashing light is so annoying!
  Here's a video that shows the problem: https://gofile.io/d/FuRrn5.
  
  Is this a feature? Because i can't find any reference about it. Maybe it's because there are no batteries in?
  

  
  Small update to my problem:
  I wrote to OWON directly and they say that yes, if no batteries are installed, the power button will flash.
  That's kind of an annoying feature lol.

  ---

  
• #458 Reply
  Posted by NoMoreMagicSmoke on 02 Oct, 2022 14:41
• Quote from: JogaBonito5 on 02 Oct, 2022 10:05

  Quote from: JogaBonito5 on 26 Sep, 2022 17:07

  Hello guys, I just bought the OWON HDS242!
  
  I attached some pictures regarding software information and PCB revision.
  
  I just have one minor problem: I have no batteries right now so the only way to turn it on is via USB cable. The problem is that when i plug it in, the power button starts flashing without stop. The oscilloscope works without any issues but this red flashing light is so annoying!
  Here's a video that shows the problem: https://gofile.io/d/FuRrn5.
  
  Is this a feature? Because i can't find any reference about it. Maybe it's because there are no batteries in?
  

  
  Small update to my problem:
  I wrote to OWON directly and they say that yes, if no batteries are installed, the power button will flash.
  That's kind of an annoying feature lol.
  

  
  Why don't you have batteries?
• #459 Reply
  Posted by JogaBonito5 on 02 Oct, 2022 15:40
• Quote from: NoMoreMagicSmoke on 02 Oct, 2022 14:41

  Why don't you have batteries?
  

  
  Because I thought it would came with batteries lol
  I bought it from pollin.de but probably didn't pay too much attention to the description
• #460 Reply
  Posted by Mechatrommer on 02 Oct, 2022 17:59
• blinking button to warn missing batteries is a preferable feature imho. to warn us to get batteries asap. operating without batteries could overload charging circuit, or not recommended because of various reasons.
• #461 Reply
  Posted by NoMoreMagicSmoke on 02 Oct, 2022 18:24
• Quote from: JogaBonito5 on 02 Oct, 2022 15:40

  Quote from: NoMoreMagicSmoke on 02 Oct, 2022 14:41

  Why don't you have batteries?
  

  
  Because I thought it would came with batteries lol
  I bought it from pollin.de but probably didn't pay too much attention to the description
  

  
  Weird. Must be something with that vendor.
• #462 Reply
  Posted by JogaBonito5 on 02 Oct, 2022 19:41
• Quote from: Mechatrommer on 02 Oct, 2022 17:59

  blinking button to warn missing batteries is a preferable feature imho. to warn us to get batteries asap. operating without batteries could overload charging circuit, or not recommended because of various reasons.
  

  
  I see the point, yeah that's right. But I hoped for a direct supply via cable, like bypassing the overload circuit or something like that so I wouldn't have to rely always on batteries   
• #463 Reply
  Posted by konnor on 20 Oct, 2022 18:22
• ADC area HDS2102S vs HDS2202S:
  

  ---

  

  
• #464 Reply
  Posted by eti on 23 Oct, 2022 02:11
• To save a thread trawl, would someone tell me what the latest HDS272S firmware is (V3 H/W if I recall) and what it has that deems an upgrade worthwhile? Charrrrz!
• #465 Reply
  Posted by gtube on 28 Oct, 2022 21:30
• The new V3 version use Chinese made 1Ghz 8bit ADC. Here is the link:
  http://linsimicro.com/Products/info.aspx?itemid=5
• #466 Reply
  Posted by eti on 28 Oct, 2022 22:26
• Quote from: gtube on 28 Oct, 2022 21:30

  The new V3 version use Chinese made 1Ghz 8bit ADC. Here is the link:
  http://linsimicro.com/Products/info.aspx?itemid=5
  

  
  Ah, no, what I meant was, what is the latest firmware, and what is in it to make it worth me upgrading? Thanks!
• #467 Reply
  Posted by topconchen on 02 Nov, 2022 09:35
•  The latest firmware is V8.0.1，it can't be downloaded.

  ---

  
• #468 Reply
  Posted by tunk on 02 Nov, 2022 12:23
• Quote from: topconchen on 02 Nov, 2022 09:35

  The latest firmware is V8.0.1，it can't be downloaded.
  

  Any chance of opening it, i.e. to see if the hardware is the same?
• #469 Reply
  Posted by eti on 03 Nov, 2022 05:13
• Quote from: Mechatrommer on 29 Oct, 2022 00:46

  You can credit $5 to my paypal i'll do the homework for you...
  

  
  It’s useful to quote people to whom you’re responding, otherwise we have an ambiguous reply floating in space with no recipient known.
• #470 Reply
  Posted by eti on 03 Nov, 2022 05:39
• Quote from: Mechatrommer on 03 Nov, 2022 05:29

  Yes it is meant as general purpose statement. If quoting name, there is risk of backfire so better not mention it whoever in need will know who the statement is for. Cheers.
  

  Ah, righty Ho 😃
• #471 Reply
  Posted by jomaroliv on 14 Nov, 2022 19:07
• Just got mine with FW 8.01 (HDS242). Did not (yet) open to check board version.
• #472 Reply
  Posted by jomaroliv on 15 Nov, 2022 17:16
• Ok, só MB revision is 3.02 from end of July 22 FW 8.01

  ---

  
• #473 Reply
  Posted by tly on 16 Nov, 2022 13:54
• Quote from: jomaroliv on 15 Nov, 2022 17:16

  Ok, só MB revision is 3.02 from end of July 22 FW 8.01
  

  
  (just for info:) The batteries can be changed or are glued ?
• #474 Reply
  Posted by wb0gaz on 16 Nov, 2022 14:04
• Followed the url (from gtube a few postings back) for linsimicro.com's ADC - didn't see anything that looked like a datasheet link, but the few specs (lower on the page) indicate 7-bit ADC (the headline on the page appears to be 8-bit.)