New Hantek DSO2X1X models?

[crysti]

I was able to attach an external battery

I like your mod.
It is practical for mobility and also protects the scope when you want to poke around freely in ground-referenced circuits.
Have you noticed any change in the noise floor and/or sensitivity?
How much impact does the additional SMPS have on them?

Without measuring probes, the noise level is the same, with probes 10x noise level is higher, because I think the grounding is missing. I use 200Mhz probes, because have lower attenuation over 100Mhz.

[DavidAlfa]

That's just the fpga firmware. The zoom bug seems caused by the dso software.

[DavidAlfa]

Please make it simple and tidy. I've seen less dense concrete bricks than your message
Neither I can test anything as mine is FW 3102.

» Nobody said FW3203 is compatible with existing  FW3200/3202. It might be some small design change causing the spikes...

» 2022.02.10 and 2022.02.18 have exactly the same scope software.

» 2022.02.10 doesn't modify the fpga, 2022.02.18 updates it to FW3203.
   So please stop using those endless filenames. FW3202 and FW3203 is more than enough.

» Any Hantek update will make a factory reset, you always should calibrate it afterwards.

» Given this, the simplest method would be to stay in 2022.02.10, switching between FW3202 and FW3203 with FW changer, always calibrating before doing any tests.

Hmm...
- Step up the battery to 250V to power the mains converter (loses)
- Step down to +-8V , +5V (more loses)

The heavy load goes into the 5V line.
I have to measure it, but +-8V is for the analog frontend and probaly have low consumption, I suspect 200mA at most.

My idea is to replace the power supply with another of 9V 5A, connecting a 4P2S battery (With charging circuitry and protection) to the output, so it'll simply charge from the power supply.
Battery output goes directly to +8V, the other voltages will be sourced by adding a buck converter for +5V and a negative converter for -8V.
Removing the noise from these small 1MHz buck modules should be much easier that 20-40KHz.

I might do nothing in the end!

[crysti]

Please make it simple and tidy. I've seen less dense concrete bricks than your message
Neither I can test anything as mine is FW 3102.

» Nobody said FW3203 is compatible with existing  FW3200/3202. It might be some small design change causing the spikes...

» 2022.02.10 and 2022.02.18 have exactly the same scope software.

» 2022.02.10 doesn't modify the fpga, 2022.02.18 updates it to FW3203.
   So please stop using those endless filenames. FW3202 and FW3203 is more than enough.




» Any Hantek update will make a factory reset, you always should calibrate it afterwards.

» Given this, the simplest method would be to stay in 2022.02.10, switching between FW3202 and FW3203 with FW changer, always calibrating before doing any tests.

Hmm...
- Step up the battery to 250V to power the mains converter (loses)
- Step down to +-8V , +5V (more loses)

The heavy load goes into the 5V line.
I have to measure it, but +-8V is for the analog frontend and probaly have low consumption, I suspect 200mA at most.

My idea is to replace the power supply with another of 9V 5A, connecting a 4P2S battery (With charging circuitry and protection) to the output, so it'll simply charge from the power supply.
Battery output goes directly to +8V, the other voltages will be sourced by adding a buck converter for +5V and a negative converter for -8V.
Removing the noise from these small 1MHz buck modules should be much easier that 20-40KHz.

I might do nothing in the end!

Internal power source have on output +8V, -8V, +5V and TR (Line trigger). How to correctly emulate TR output pin?
First attempt is to use 9V/1,5A from any QC2.0 USB phone  charger, with QC2.0 trigger https://lygte-info.dk/review/USBmeter%20QC2-QC3%20trigger%20UK.html, and I would have used 2 converters at +7.5V and +5V.
I use 7,5V because I measure 7,5V to +8V line, and DC-DC PWM converter needs a minimum voltage drop.
For the -8V voltage I would have used existing onboard converter, but I got stuck at the TR pin.
Anyway, the consumption is 11W from the 12Vdc source and 9W from the 230Vac power network.

[DavidAlfa]

You don't care about TR unless you want to sync with mains, which is impossible when you're no longer connected to it, and rarely used anyways.

A 2S batery will output 7.4-8.4V, which is perfect for this application.
The power supply controller is rated for ~24W, so if there's another 10W available, using that power to charge batteries makes it even easier.
Perhabs these diodes will need to be replaced with beefier ones.
Once I wanted to check the car speaker signal, mains power dependence was a little annoying, but battery power isn't something I really need.

[crysti]

You don't care about TR unless you want to sync with mains, which is impossible when you're no longer connected to it, and rarely used anyways.

A 2S batery will output 7.4-8.4V, which is perfect for this application.
The power supply controller is rated for ~24W, so if there's another 10W available, using that power to charge batteries makes it even easier.
Perhabs these diodes will need to be replaced with beefier ones.
Once I wanted to check the car speaker signal, mains power dependence was a little annoying, but battery power isn't something I really need.

Without TR pin (I use 1,7V delayed signal) my DSO not booting every time.

[DavidAlfa]

Might it be a power-ok signal to start the system?
Or a delay to hold the system in reset while the power supply starts?

[crysti]

Someone has a fix for high memory bug?

[DavidAlfa]

Didn't FW3203 work for you?

[crysti]

Didn't FW3203 work for you?

I have FW3200

[DavidAlfa]

You should have updated to 3202 already. So try 3203.

[crysti]

You should have updated to 3202 already. So try 3203.

I update to latest official firmware from Hantek and hack to DSO2D10 to DSO2D15.
Now have Software 1.0.2.0.0 and unchanged firmware version.
Bugs firmware problems remain, only manifesting differently
Which is the safest way to update firmware?
If I update to the 3203 firmware fix this issue?

[DavidAlfa]

Don't take it bad, but it seems someone is not reading...
Everything about this issue has been said in the last page, also the FAQ was updated to mention this issue...
All you need is to run FW Changer 3203, can be reversed by installing any other FW Changer version (3200, 3202...).
I won't extend further repeating the same again and again: Read the FAQ, then ask if and doubt remains.

[Tekjive]

Bug Report: LowLevel Voltage Adjust

So I converted to 2D15 from 2C10, then updated to latest software 20220210 from 20210726, kept FW @3202, and Scope seems to be probing great/accurate, although when trying to adjust the voltage on the Low Level setting using the AWG the parameters only go down, regardless of which way I turn the knob, is that normal? I can record a video if needed. Everything else is working spot on so far, and no crazy rapid relay clicks anymore with auto set either lol 😅

Side Note/Question: AWG a grounded signal?

I use my AWG to send signals to class D & A/B amps on my bench that I’m troubleshooting/repairing. I use a BNC>RCA converter lug (currently looking for a single bnc to dual rca lug so I can test both channels at once on monoblock amps) and need to know if it’s a grounded signal like a typical headunit in a car environment has, I’m assuming it is being a precise grounded instrument but I wanted to ask and not just assume because it is important to my troubleshooting/repair procedures.

Update/Hack&AWG working great so far though, nice to have AWG to use a 40Hz Sine wave @ 2.5 amplitude, 1v offset (need to read what that offset really is and if I really need it above 000v while running signal through amp) on 1 device instead of hooking up 3-5 additional things to get that signal to amp. 🤓

Thx! 🖖🏼

[JOSM]

I have updated the FW on my DSO to 3203 and am running SW 1.0.2.0 (20220210.00).
I think the "spikes on the signal" problem has moved from higher resolutions to the 4Kpt and 40 Kpt region now. It occurs on lower time bases (200 ns/Div. and lower).

Then I found another issue (less anoying):
When displaying a stored reference wave as overlay and shutting down and restarting the DSO then the reference info section on top left is still shown. The reference signal is not.

[DavidAlfa]

I guess you were lucky and your amp was ac-coupled, otherwise you would have blown the speakers.
Offset is the DC compound of the wave.
Normally it should be 0, otherwise the wave would be assymetrical.
In the worst case, you'll make a DC signal with AC ripple, which would push the speakers all the way out damaging the suspension, and if the amplitude is too high or the exposur time too long, burn the coil or even the amplifier.

I have updated the FW on my DSO to 3203 and running SW 1.0.2.0 (20220210.00).

Have you compared 3200, 3202 and 3203?

[JOSM]

Have you compared 3200, 3202 and 3203?

I have reapplied 3202 and the spikes are gone.

[DavidAlfa]

I think it's pretty clear that FW3203 is (theorically) only for those having the spikes in FW3202.
Maybe they made a new hardware revision, who knows.
Otherwise, as they say, don't touch if ain't broken

[crysti]

After update to FW3203 spikes disappear.  So far, I haven't had any problems. Thank you for help!

I think it's pretty clear that FW3203 is (theorically) only for those having the spikes in FW3202.
Maybe they made a new hardware revision, who knows.
Otherwise, as they say, don't touch if ain't broken

[PiperFlyer]

This is my first post, however, I have reviewed almost all of the over 900 posts on this thread.  I purchased my DSO2D15 based on reviews on YouTube (before I found this forum) and thought it was a great unit for my needs (replacing a Heathkit IO-4205, 5mHz scope).  However within one hour of opening my new scope (March 6, 2022), the unit bricked.  Cycled the power on and off, pressed buttons, nothing.  It just would go through the hardware initialization and then stop, looking at me goofily.  Thanks to DavidAlfa and all the others on this thread, I determined that this unit was still worth fighting for; so I wrote to Hantek and within 10 hours, they sent me the link to 烧录 3202.zip including the platform tools.  It worked like a champ and I'm back in business.  I'll have to update my serial number and other system info because the unit bricked before I knew I should backup the system info with DavidAlfa's backup builder.  I uploaded the full file I downloaded from Hantek to the DavidAlfa's Google Drive just in case you can use it; downloading the file was the hardest part of the fix.  Thanks again!

[Maxie]

Thanks PiperFlyer.
I was just going to ask if there is a Platform Tools for the 3200 FW series scopes.
All I found was older versions made for the 3000 series and I was not sure if I could use them in case of a problem.
I guess those could also be used to restore to factory state and then update the FW to 3200. Am I right?

[DavidAlfa]

Thanks for contributing PiperFlyer, will have a look at the files later 

Maxie, yes, you can use any platform tools, as long as you later install FW changer 320x . That's all it needs.

[Tekjive]

Ahhh, so thats why my 10" test sub almost jumped out of its soul ...lol. ty 😅

[DavidAlfa]

I wanted to test the plataform-tools, but I found my FEL button had failed, so I replaced it.

After that I thought ”why not?” and also clamped two long heatskinks over the ADC/FPGA with some cpu thermal paste, making a clampling thingy with a thin metal plate.

Didn't like the idea of glueing them with hardening paste, I've seen terrible things when removing the heatsink later...

[vistorik]

they sent me the link to 烧录 3202.zip including the platform tools.

After using this platform-tools, if you short press the DEFAULT SETUP button you'll get the known default menu1, but if you keep this button pressed a little longer you'll get a new default menu2. If you'll choose in this menu 'Wave Gen', you'll get the next screen (default menu3).