Products > Test Equipment
New Hantek DSO2X1X models?
artmau:
Yes, the scope is still locked up (boots up, but at the end of sequence there the relays do not switch, no waveforms, the keybord is unresponsive, and the all keys are lit). But I used only unified version the Platform Tools (are there some tools missing?) for restoring and failed. I emailed Hantec for version working with GD5F1GQ5UEYIG, still waiting. Btw. are the previous versions of PT still somewhere available?
It may not be apparent, but the serial number is on the bar code sticker on the back of the scope.
It seems, that the command "DDS:CAL:RESUlt" from SCPI codes list extracted by David gives back calibration data, in my case: 0.833235, 5.294509 (offset, amplitude). Is this correct?
Tomorrow morning I'll try to restore with dsoflash v.36 once more.
edit: the command should be "DDS:CAL:RESUlt?"
vistorik:
--- Quote from: artmau on March 20, 2024, 08:45:33 pm ---Yes, the scope is still locked up (boots up, but at the end of sequence there the relays do not switch, no waveforms, the keybord is unresponsive, and the all keys are lit). But I used only unified version the Platform Tools (are there some tools missing?) for restoring and failed. I emailed Hantec for version working with GD5F1GQ5UEYIG, still waiting. Btw. are the previous versions of PT still somewhere available?
It may not be apparent, but the serial number is on the bar code sticker on the back of the scope.
It seems, that the command "DDS:CAL:RESUlt" from SCPI codes list extracted by David gives back calibration data, in my case: 0.833235, 5.294509 (offset, amplitude). Is this correct?
Tomorrow morning I'll try to restore with dsoflash v.36 once more.
--- End quote ---
If your scope is locked up with the same memory contents as mine while my scope is working normally, this can only mean a problem with the hardware, provided that you sent me the dump exactly corresponding to the contents of your scope's memory at the current moment when your scop is locked up.
Calibration data are correct.
You could aloso try to flash the dump from another scope with the GD5F1GQ5UEYIG memory chip (link: https://filetransfer.io/data-package/vemVQ7dA#link) using dsoflash v0.36. If your scope is still locked up with this dump then it looks like a hardware problem.
artmau:
Ok, after using the dsoflash v.36 second time with my own dump the oscilloscope is alive! The only change that I can think of is that the first time I reflashed the dump was in state before using "PRIVate:FACTORY:RESET" command.
Using the "PRIVate:FACTORY:RESET" itself did not unlock the scope for me.
edit: At first all looked good, but after the third power cycle the scope got locked again. This time noumerous flashing with dsoflash v.36 with any available dump does not unlock the scope. Some hardware issue after all...
edit2: looks like the unlocking was just a fluke. There is no apparent hardware cause and for now i do not have any more ideas.
to go deeper i would need to know the end of startup sequence. I'll disconnect power for 12 hours like yesterday and try tomorrow morning. Should I update firmware to 3208 if the scope somehow unlocks?
edit3: still no luck. clearly a hardware problem :(
supphol:
Hello all,
first post here so be gentle. I just got the DSO2D15 and i have read the topic from the start.
The following question / idea came to my mind about the slagish UI.
I have seen development boards for the GW2AR-18-144 (that manages all LVDS connectivity) and the F1C200S and what hit me was that the GW2AR-18-144 boards used 50Mhz crystals while F1C200S all used 24Mhz.
Likewise in the datasheets the only option for the F1C200S is 24/25Mhz crystals, which i consider a limitation to the GW2AR-18-144 that seems to be able to work with at least double the reference frequency.
So my idea is, if it is possible to utilize a frequency doubler(phase-locked loop if im correct) to feed the GW2AR-18-144 with 48Mhz from the same 24Mhz crystal (to keep phase between ICs) that feeds them both on the factory hantek implementation? Fun part is that R820 is perfect to interfere with the GW2AR-18-144 Clock path.
Do you think this will solve the slagish UI?
BitMaP:
Hi,
I was in the market for a hobby level scope and came across this thread. After a lot of reading (especially this thread) I decided on the DSO2C10 and ordered it off Amazon. Two days later and I received the scope today. I'm very pleased, it was fully populated and because of everyone's hard work and documentation I was able to navigate through the upgrade process without any issues. A special thanks to DavidAlfa, you have spent a lot of time and shown more patience than most with this effort and it certainly shows.
Thanks, and have a happy Easter!
BitMaP
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version