Products > Test Equipment

Hantek 6254BD 250MHz 1GSa/s PC/USB DSO

<< < (7/11) > >>

Neekeetos:
Slight update on HW initialization details. The PLL is initialized every time scope software starts and never changes. There is a lock output from ADF4360 (muxout) connected to fpga pin , but it is not used. Init sequence is as follows:
Full init sequence

Word 1

Word 2

Word 3


There is also a chain of hc595 registers sharing SPI CLK/SRCLK and DATA/SER pins with ADF4360, however RCLK is independent( so as LE on PLL). Each register connects to own oscilloscope channel sharing the same functions which are :
QHLPF_ENABLEQF/QGATT2_RELAYQD/QEATT1_RELAYQCAC_DC_RELAYQBADC_DRIVER_ENABLE
Some example bus data:


Word 1

Word 2

eevblogfan1:
I managed to score a 6254BD for $80 on ebay and while I await it to arrive, and cross my fingers I didn't get bamboozled, I decided to research everything I could find about the device, and I found your forum and the hantek support forum in the process. In particular I noticed the below:


--- Quote from: rgon on April 01, 2019, 01:30:14 pm ---Previously, when bricking my scope, I had to ask Hantek for a file (DSO6106BD20160601.iic), but I'm unable to redistribute it since I haven't got permission.

--- End quote ---


And I also noticed a person on Hantek support forum had an issue with the usb device having the wrong id


--- Quote ---I have a problem with the Hantek6254BD oscilloscope. The DRIVER does not install -- but the actual scope software does install.
Can you supply the correct driver? I downloaded the latest software from the Product page for Hantel 6004 page.
Description:
The PID and Device ID appear to be wrong...
So the Scope software installs -- but the driver does not install. If I change the strings to match -- of course the driver is rejected by windows since it does not match the security string in the CAT file.
My device has:
04B5 and 8613 for the two codes -- not the o4B5 and PI_6CDE
My string in the USB identifier -- read from the SCOPE shows as
USB\VID_04B4&PID_8613
Your software is looking for this code.
[Device]
%VID_04B5&PID_6CDE.DeviceDesc% = Section, USB\VID_04B5&PID_6CDE
;for windows 2000 non intel platforms

--- End quote ---

Which is quite common, so it seems they finally got tired of emailing out that iic firmware to fix usb device issues and their employee Amy just attached it to a to their post in reply.  You have to register to see attachments, but it can be done in less than a minute, I have also attached it to the end of this post.  Perhaps it will help some people out here.  The iic itself seems to be the same for 0x13FD bytes as the cy_eeprom_dso6074bc.zip firmware posted by neeketos, but neeketos seems to have additional data beyond that.

Screenshot of forum post and partial file listing


If anybody would like to decode the iic file, one way would be to go to section 3.4.3 Serial EEPROM Present, First Byte is 0xC2 of the manual here.  Although there might be better ways, perhaps sigrok has some utilities that automate the process, I don't really know to much about the project other than it seems they are fx2 gurus.



--- Quote from: rgon on April 01, 2019, 01:30:14 pm ---When I get some more free time, I'll continue investigating and will keep you up to date (even if I spend another 2h organizing my findings and writing this post lol). With some luck, I'll clean up the mess of code I've written and will publish it.

--- End quote ---

While I am on the topic of rgon's post, did you ever publish anything or do any more investigation work?

Appocalypse_br:
Hi every one, mine 6104bc bricked it self in normal day to day use, so i desolder the 24lc64 and writed the 6074bc firmware dump provided in this forum. YAY! device is working now!

BUT when i set in milivolts and the relay activates the signals of the channel gets mixed with the others, any clue why that is happening? i will try to program the original firmware back.

Thanks to the users that are helping me.

Appocalypse_br:
Problem 1
Before writting the original dump back in i tried the program posted above seems to write via EZ-USB.
But when i click the EZ-USB shows the next screen, in that screen i can't click in any button, you guys have any clue why is that?
Maybe because i have the eproom with data in it, the program do not works?
Should i erase the data and try trought the EZ-USB to fix the milivolts problem?

Problem 2
Attached the pictures of the problem.
1x Probe, 100mv div, DC, measure the 2vpp test point (AC no problem)(10x PROBE no problem)

Microcheap:
I'm not sure if I understood your 2nd problem, but there was a bug in the software version 2.2.4 (the one you are using) that I helped Hantek to identify and that introduced an offset error in the oscilloscope's channels. You need to update the software to Ver2.2.5 or downgrade to version 2.1.36 and run the self-calibration again.

https://www.eediscuss.com/forum.php?mod=redirect&goto=findpost&ptid=14725&pid=18097&fromuid=26055

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod