Hantek HDG2002B AWG: 5Mhz or 100MHz? Let's see!

[TurboTom]

Hey Marco -

sorry I didn't noticed your inquiry the last time I checked this thread. Maybe it's a little late to answer, but better late than never.

I checked the modulation schemes you requested and found all of them working exactly as they should. I attached a few screen shots of the waveforms on the scope. For the 20MHz carrier FM test I had to increase the modulation frequency to 50kHz and the deviation to 5kHz, otherwise I wouldn't have had a chance to visualize the modulation with my DS1054Z's FFT function. My spectrum analyzer is at home and I'm on work... 

Actually, after playing around with a Rigol DS4102 generator which isn't without its flaws either, the Hantek (at least in the H/W - S/W configuration that I've got) doesn't seem such a bad choice, at least for "standard" waveforms.

Cheers,
Thomas

[SteveRosenlund]

Can anyone point me to the calibration procedure on this?  When I select calibrate from the menu and then start, it asks me to input the voltage value from channel one into the hantek. I cannot get past this point. Even after entering the voltage (-560mV dc) I hit next but nothing happens.

[markone]

I checked the modulation schemes you requested and found all of them working exactly as they should. I attached a few screen shots of the waveforms on the scope.

Unfortunately this is not valid for my device, you own a more recent HW board's issue where the new FW does a "decent" job.

My HDG2002B sits in its cardboard box on my basement, i think forever thanks to Hantek's ridiculous / nonexistent aftermarket support.

My suggestion for potential buyer is : stay away from this pile of crap.

[TurboTom]

It's quite funny Hantek still seems to support this "pile of crap"  - there's a new firmware available for download on their web site http://www.hantek.com/en/ProductDetail_12_149.html

I did the update on my toy, it now reports Software 1.00.3.03.07 (2016/04/11), Linux 3.2.35, FPGA 60 and keyboard 3. The software seems to be pretty stable now and most interestingly, the arbitrary functions (via the windows-based editor) work on channel 2, yet they don't on channel 1 (but no crashes so far). So maybe the generator is turning into something half-way usable after all  . Unfortunately, the new firmware didn't address the shortcomings that annoy me most, namley the adjusted digit in incremental mode stays fixed relative to the decimal point which means when the units change (Hz to KHz for example), the increments that you control the value with suddenly change by a factor of 1000 -- CRAP! Maybe this won't have been the last update though...

Cheers,
Thomas

[Freedom]

I want to get my counter working. There are some missing parts on my pcb. I circled them in red.
If you know their model, value, please, share it.
Thanks!

[TurboTom]

Component values are:

C233, C234, C238 are 100nF/25V
C236, C237 are 1nF / 50V
R183 51Ohms
R134 120kOhms
D14 1SS226 (equiv. BAV99)
L27 RF-Choke 805

D4, R194 and U29 are not related to frequency counter and aren't populated on my HDG2002 either. Was the LMX5080 already populated on your board or did you assemble it? It would be funny if it was and all the cheap "chicken food" left off. So far, I've only seen it the other way round as it was on mine, everyting except the RF divider populated...

Cheers,
Thomas

Edit: Correction of values for C236 and C237

[Freedom]

Thanks, TurboTom!
 I populated LMX5080 and BNC connector.
Thanks a lot !

[Dwaine]

Wow this this is garbage.   I'm so glad I did not buy one off ebay.   Thanks everyone for these discussions.  It really saves a lot of people money and time.

Off to buy the Rigol....

[TurboTom]

Wow this this is garbage.   I'm so glad I did not buy one off ebay.   Thanks everyone for these discussions.  It really saves a lot of people money and time.

Off to buy the Rigol....

It may be crappy but actually, having "inherited" also Rigol DG4102, and comparing prices and performance between the two, I'm not so sure which money is better spent. Currently, I hardly use any real arbitrary functionality on any of the two and after hacking and calibrating the Hantek, it performs quite reasonably as a "standard" generator. As a clock for a stepper-driven pump or to evaluate a (lower) RF signal transformer, it performs pretty reasonably, especially with the latest firmware which sped up the incremental encoder considerably. The Rigol generator isn't without its flaws either and more than twice the price tag (see my post here https://www.eevblog.com/forum/testgear/any-update-on-rigol-dg4000-series-hacking/msg857122/#msg857122 ) .

I don't know how the "smaller" Rigol models compare or the Siglent AWGs but I guess you've always got to be prepared for some shortcomings. Maybe not if you spend the money for a Keysight but at least for me these would be too expensive for an instrument basically used for my hobby.

Cheers,
Thomas

[markone]

Wow this this is garbage.   I'm so glad I did not buy one off ebay.   Thanks everyone for these discussions.  It really saves a lot of people money and time.

Off to buy the Rigol....

It may be crappy but actually, having "inherited" also Rigol DG4102, and comparing ....

Cheers,
Thomas

Just to revive this old 3ad ....

TurboTom, you  forgot to mention that was necessary to apply a huge HW mode to turn the Hantek in a safe instrument, at least Rigol is OK out of the box under this aspect.

The value of the workmanship involved in this process is well over the cost of the "toy" and you still have a subpar device functionally wise.

To those are looking for a fair ARB signal generator i would suggest a Siglent 2042x, i'm working with it  (expanded to 100Mhz) from several months without any important glitch.

Maybe still Rust inside (maybe, actually i never opened it), but very good performance for the price, for sure it rounds circles around several similar priced instruments.

[FrankenPC]

Need some help.  I moved and after unpacking, the FG would not boot.  So, I hooked up the serial connection and got this...any ideas?

----------------------------------------------------

*** Warning - bad CRC or NAND, using default environment

##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; LCD display size is: 800 X 480
Press Space key to Download Mode.!
SD:File System init failed!
Start Linux ...

NAND read: device 0 offset 0x300000, size 0x400000
 4194304 bytes read: OK
Boot with zImage

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.2.35 (root@zgt) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #42 PREEMPT Wed Mar 26 12:49:52 CST 2014
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: SMDK2416
Memory policy: ECC disabled, Data cache writeback
CPU S3C2416/S3C2450 (id 0x32450003)
S3C24XX Clocks, Copyright 2004 Simtec Electronics
CPU: MPLL on 800.000 MHz, cpu 400.000 MHz, mem 133.333 MHz, pclk 66.666 MHz
CPU: EPLL on 96.000 MHz, usb-bus 48.000 MHz
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: noinitrd ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 mem=64M
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 59028k/59028k available, 6508k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xc4800000 - 0xf6000000   ( 792 MB)
    lowmem  : 0xc0000000 - 0xc4000000   (  64 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc03e9000   (3972 kB)
      .init : 0xc03e9000 - 0xc0408000   ( 124 kB)
      .data : 0xc0408000 - 0xc05a0e00   (1636 kB)
       .bss : 0xc05a0e24 - 0xc05bea7c   ( 120 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:107
irq: clearing subpending status 00000002
Calibrating delay loop... 198.45 BogoMIPS (lpj=496128)
pid_max: default: 4096 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
S3C2416: Initializing architecture
S3C2416: IRQ Support
S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
DMA channel 0 at c4804000, irq 88
DMA channel 1 at c4804100, irq 89
DMA channel 2 at c4804200, irq 90
DMA channel 3 at c4804300, irq 91
DMA channel 4 at c4804400, irq 92
DMA channel 5 at c4804500, irq 93
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
s3c-i2c s3c2410-i2c: slave address 0x10
s3c-i2c s3c2410-i2c: bus frequency set to 9 KHz
s3c-i2c s3c2410-i2c: i2c-0: S3C I2C adapter
Advanced Linux Sound Architecture Driver Version 1.0.24.
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
s3c-adc s3c24xx-adc: attached adc driver
msgmni has been set to 115
io scheduler noop registered (default)
io scheduler cfq registered
s3c-fb s3c-fb: window 0: fb
s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5
s3c2440-uart.0: ttySAC0 at MMIO 0x50000000 (irq = 70) is a S3C2440
console [ttySAC0] enabled
s3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76) is a S3C2440
s3c2440-uart.3: ttySAC3 at MMIO 0x5000c000 (irq = 94) is a S3C2440
loop: module loaded
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
info->cpu_type=3, tacls_max=8
s3c24xx-nand s3c2416-nand: Tacls=3, 22ns Twrph0=7 52ns, Twrph1=3 22ns
s3c24xx-nand s3c2416-nand: System booted from NAND
s3c24xx-nand s3c2416-nand: NAND ECC disabled
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended!
Scanning device for bad blocks
Bad eraseblock 291 at 0x000002460000
Bad eraseblock 923 at 0x000007360000
Creating 4 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "Bootloader"
0x000000100000-0x000000300000 : "LOGO"
0x000000300000-0x000000700000 : "Kernel"
0x000000700000-0x000008000000 : "ROOTFS"
UBI: attaching mtd3 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    126976 bytes
UBI: smallest flash I/O unit:    2048
UBI: VID header offset:          2048 (aligned 2048)
UBI: data offset:                4096
UBI: max. sequence number:       2348
UBI: attached mtd3 to ubi0
UBI: MTD device name:            "ROOTFS"
UBI: MTD device size:            121 MiB
UBI: number of good PEBs:        966
UBI: number of bad PEBs:         2
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             0
UBI: total number of reserved PEBs: 966
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 6/2
UBI: image sequence number:  0
UBI: background thread "ubi_bgt0d" started, PID 310
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usblp
usbcore: registered new interface driver uas
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
samsung-ts s3c2416-ts: driver attached, registering input device
input: S3C24XX TouchScreen as /devices/virtual/input/input0
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
i2c /dev entries driver
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq disabled
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 2: hsmmc-if (24000000 Hz)
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: uda134x-hifi <-> s3c24xx-iis mapping ok
ALSA device list:
  #0: S3C24XX_UDA134X
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
s3c-rtc s3c2410-rtc: setting system clock to 2016-10-30 17:40:07 UTC (1477849207)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size:   119611392 bytes (116808 KiB, 114 MiB, 942 LEBs)
UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:10.
Freeing init memory: 124K
UBIFS error (pid 1): ubifs_check_node: bad node length 525337
UBIFS error (pid 1): ubifs_check_node: bad node at LEB 117:14632
UBIFS error (pid 1): ubifs_read_node: expected node type 1
UBIFS error (pid 1): do_readpage: cannot read page 219 of inode 467, error -22
UBIFS error (pid 1): ubifs_check_node: bad node length 525337
UBIFS error (pid 1): ubifs_check_node: bad node at LEB 117:14632
UBIFS error (pid 1): ubifs_read_node: expected node type 1
UBIFS error (pid 1): do_readpage: cannot read page 219 of inode 467, error -22
Failed to execute /linuxrc.  Attempting defaults...
Kernel panic - not syncing: No init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.

[fremen67]

Hi FrankenPC,

I would suggest that you try reflashing your File System partition which seems very sick...

From your logs, it appears that you have a nand layout without recovery partition so you will have to manually reflash the partition. You will need to connect your HDG to your PC via the USB port and use the DNW utility.
You will find the rootfs.ubi file that you need on my Onedrive: https://1drv.ms/f/s!AuLJ8Arc4GbGcstRrjm2d33uI8Q
Have a look in "04-Nand Recover" / "Firmware 1.00.1 (without Recovery Partition)".

You may not have to reflash the whole nand, just rootfs.ubi should do the trick.
In any case, you will want afterward to upgrade your firmware with the latest firmware (another directory of the Onedrive).
You may also update your serial number in the /etc/system.inf file (S/N=230000000 otherwise)

Good luck!

[FrankenPC]

Hi FrankenPC,

I would suggest that you try reflashing your File System partition which seems very sick...

From your logs, it appears that you have a nand layout without recovery partition so you will have to manually reflash the partition. You will need to connect your HDG to your PC via the USB port and use the DNW utility.
You will find the rootfs.ubi file that you need on my Onedrive: https://1drv.ms/f/s!AuLJ8Arc4GbGcstRrjm2d33uI8Q
Have a look in "04-Nand Recover" / "Firmware 1.00.1 (without Recovery Partition)".

You may not have to reflash the whole nand, just rootfs.ubi should do the trick.
In any case, you will want afterward to upgrade your firmware with the latest firmware (another directory of the Onedrive).
You may also update your serial number in the /etc/system.inf file (S/N=230000000 otherwise)

Good luck!

Thanks again.  I take it the DNW.EXE USB download program is part of the ARM toolchain support files?  Or some kind of dev tools download?   

[fremen67]

I take it the DNW.EXE USB download program is part of the ARM toolchain support files?  Or some kind of dev tools download?

Yes. Have a look back in the thread, here: https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let's-see!/msg451021/#msg451021
and here:https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let's-see!/msg451081/#msg451081

You don't need configs.zip as it is for OpenOCD. Just dnw and the drivers corresponding to your system.
 

[FrankenPC]

I take it the DNW.EXE USB download program is part of the ARM toolchain support files?  Or some kind of dev tools download?

Yes. Have a look back in the thread, here: https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let's-see!/msg451021/#msg451021
and here:https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let's-see!/msg451081/#msg451081

You don't need configs.zip as it is for OpenOCD. Just dnw and the drivers corresponding to your system.

You are very helpful.  Thanks a bunch!

[FrankenPC]

I take it the DNW.EXE USB download program is part of the ARM toolchain support files?  Or some kind of dev tools download?

Yes. Have a look back in the thread, here: https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let's-see!/msg451021/#msg451021
and here:https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let's-see!/msg451081/#msg451081

You don't need configs.zip as it is for OpenOCD. Just dnw and the drivers corresponding to your system.

HOKAY!  So...Windows 7 x64 can now see the device when I plug/unplug the usb cable.  "FriendlyARM MINI2416"...yadda yadda...  It has a yellow exclamation mark but that may or may not mean anything.  I select option 5 in UBOOT to download the rootfs.ubi file and run DNW.  DNW says it can't open the USB port. 

In the config section of DNW do I need to put in a magic number for the USB connection?  In device manager address property is "00000006".  I've tried that in 0x00000006 hex notation.  I've tried it without.  I ran DNW as admin.  Nadda.

Any other pointers before I "Titanic" this thing?  Thanks again for your assist.  I still don't even know why the effin nand went bad in the first place.  Gives me all kinds of warm fuzzies.

[fremen67]

HOKAY!  So...Windows 7 x64 can now see the device when I plug/unplug the usb cable.  "FriendlyARM MINI2416"...yadda yadda...  It has a yellow exclamation mark but that may or may not mean anything.  I select option 5 in UBOOT to download the rootfs.ubi file and run DNW.  DNW says it can't open the USB port. 

With Windows 7 x64, I guess you have a "code 52" meaning that it does not want an unsigned driver. If it is the case (and it should be ), use dseo13b to activate the test mode on Windows and then reboot. It should than work. Just run it again when you are finished, desactivate test mode and reboot.

In the config section of DNW do I need to put in a magic number for the USB connection?  In device manager address property is "00000006".  I've tried that in 0x00000006 hex notation.  I've tried it without.  I ran DNW as admin.  Nadda.

Any other pointers before I "Titanic" this thing?  Thanks again for your assist.  I still don't even know why the effin nand went bad in the first place.  Gives me all kinds of warm fuzzies.

Nothing to change on dnw. Just select "USB Port", "Transmit", "Transmit" again, select your file and this will launch the tranfer.

Update: I changed the driver name to "EmbedSky TQ2416 Board" in the attached files as it is the name which appears initially when there is not driver installed ...

[FrankenPC]

HOKAY!  So...Windows 7 x64 can now see the device when I plug/unplug the usb cable.  "FriendlyARM MINI2416"...yadda yadda...  It has a yellow exclamation mark but that may or may not mean anything.  I select option 5 in UBOOT to download the rootfs.ubi file and run DNW.  DNW says it can't open the USB port. 

So, after a 7 day vacation....I came back to this.  You were right about the digital signature.  But also, the intel USB 3.0 driver was killing the entire bus.  So, it was a double whammy. 

Anyhow, it's running!  Thanks again for your help!  And yeah, I only uploaded the rootfs.ubi image.  Nothing else.  I need to calibrate I assume.  No big deal.  Cheers!

[TurboTom]

F/W 1.00.3.03.10, FPGA 81 is out!

[wojt]

Luckily they fixed the issue with phase jumping when 2 channels have very close frequencies. Nice.

[zelea2]

F/W 1.00.3.03.10, FPGA 81 is out!

Can someone let me know which is the best firmware version for an old PCB 1004 version?
I've read through this thread that either the AM modulation or the HF counters stopped working
with more recent firmwares.

My current software is:

PCB: 1004
Software: 1.00.2(140819.0)
Kernel: Linux 3.2.35
FPGA: 12
Keyboard: 3

I don't care about arbitrary waveforms and for my use the current firmware was stable enough.
Is it worth to upgrade to a newer firmware considering that I'll have to go through the calibration again?

[Daruosha]

New firmware with FPGA version 82 is released.

[copperline]

Zoom failures seem to be heat related.

Unmodified HDG2022B. When first starting up, everything passes. If I leave it on for 10 mins I get both zoom failures. If i shut it off for a bit then try again, both zoom tests pass.

Not sure if this helps anyone. Latest firmware did not fix it.

[TurboTom]

Maybe an issue with a bad solder joint? Mine isn´t showing any problems (like these that is...) even if left running for hours. Seems like the waveform editor has been removed from the latest firmware. Yet, control via the PC software appears to be working fairly well.

Cheers,
Tom

[aquaaddict]

Hi,

I had a corruption (similar to FrankenPC's issue above) and used a recovery image from fremen67 to recover it, so massive thanks for that! However I need to edit system.inf to include the my board version, but how do I know what board version I have as I cant see it printed anywhere on the board (and system info just reports whatever version is written in the config.inf file)?

It had stopped booting so I couldn't check before recovery, but I did run a nandbackup, is there anywhere I can get it from those backup files (can I get the old calibration from that backup to?)?

Thanks

Anthony