Products > Test Equipment
Hantek HDG2002B AWG: 5Mhz or 100MHz? Let's see!
<< < (34/134) > >>
fremen67:

--- Quote from: tinhead on May 22, 2014, 06:55:51 pm ---- check first if the clock is really generated by FPGA (from pictures it looks like it is), if not, think wtf wrong here?

--- End quote ---
Yes it is. Pins 3&4 of the DAC are comming from C191&C187 just near the FPGA. If you prevent the fpga from being configured (ie moving htg1000.bit) than there is no signal anymore on c191&c187.


--- Quote from: tinhead on May 22, 2014, 06:55:51 pm ---What I would do is to:
- check first if the clock is really generated by FPGA (from pictures it looks like it is), if not, think wtf wrong here?
- measure (and at least check) how the DAC clock looks like
- is it variable?

--- End quote ---
250Mhz sine all the time. A variable frequency would have an impact on both output channels. Wouldn't it?
fremen67:

--- Quote from: tinhead on May 30, 2014, 11:38:00 am ---It can be as well that the FPGA firmware for HDG6xxx is different. But maybe there is way to check it. When you have
changed your AWG to HDG6xxx, and set 160MHz clock (probably it will be work in lower clocks as well, but let try the limit to ensure that no other option, from lower models, has been trigered), then you can measure the DAC clock. If the FPGA design is universal, you will see here 500MHz. This will be probably too much for the DAC and it will cloock on every second edge, so 250MHz.
But when you see 250MHz on DAC clockin, then the FPGA design is not universal and it is simply trying to set something based on control code from ARM fw.

--- End quote ---
When set to HDG6162B, the DAC clockin is still 250Mhz and the frequency output is divided by 2 for all the frequencies.
So the ARM part seems OK but the FPGA not. We would have to find the correct htg1000.bin or patch it.
I also saw jitter in the DAC clockin but I don't trust my MSO.
Something wired: Channel 1 is output 2 of the DAC and vice-versa  ;)

The limits when configured as HDG6162B are:
160Mhz sine
50Mhz square
4Mhz ramp
500khz pulse
This does not seem correct...
FrankenPC:

--- Quote from: tinhead on May 30, 2014, 07:27:08 pm ---
--- Quote from: FrankenPC on May 30, 2014, 04:05:10 pm ---FPGA 12

--- End quote ---

if you don't mind please make copy of what inside /lib/firmware/ directory, zip and post it here

--- End quote ---

See attached tar file.
fremen67:

--- Quote from: FrankenPC on May 31, 2014, 01:08:42 am ---See attached tar file.

--- End quote ---
Thank you. Your FPGA firmware (v12) was build on April 18th and mine (v11) on April 2nd.
Good thing that they are working on it so quickly (well, at least from bug correction point of view, not from stability point of view ;))
May be others with a newer HDG will have newer versions...
I did not see the difference at the moment.

The "ghost" waveforms that one can see on square waves are still there. I suspect a firmware bug rather than a hardware one as you dont see them when using the pulse function at the same rate. The pulse function also has a bug as it only create waves with frequencies that are sample rate divided(f.e. 19.230769Mhz wich is SR/13).
Compare a square wave @19.230769Mhz and a pulse wave at the same frequency: square has ghosts, pulse not.
idpromnut:
Same version info for me:

Software 1.00.1 (140402.0)
FPGA 12
PCB 1002
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod