there was just one animated cartoon video as a sample and nothing else when it worked.
Sure i will check on your tips.
I just received a Hantek DSO5072P, and I was quite surprised to see that it came "hacked" from the factory.
I can go down to 2ns/div, the firmware says it's a DSO5072P, sw is 3.40.0(150521.0), hw is 1000xffff8108, serial number is >3000.
And I am absolutely certain it came right from the factory, since it was still sealed by the original branded scotch tape, plus the seller told me that they never touched it.
To say the least I'm pleasantly surprised, but I'm also quite confused as to why this happened.
I have the same DSO1122S scope you have. I have probably used the meter function on this scope only two or three times, as it isn't well protected (or nearly as accurate) compared to my Fluke meters. I did give it a go this morning and all of the functions performed normally. I do hear quite a lot of relay switching when changing meter functions, so I would suspect faulty relay contacts as the first thing. Have you repeatedly changed functions to exercise the relays to see if that changes anything? The next steps are probably going to be investigating cold/broken solder connections. Also, what firmware version are you using? Whatever you do, do NOT use the firmware posted on the Hantek web site. It will brick your scope. As far as I know they have not fixed this yet (someone feel free to update me on that).
Good luck!
Thanks. It seems to be a common behavior of the DMM unit. At least the DSO part works as I expect it.
Is the number in brackets of the SW version the build date (YY-DD-MM)?
after nearly a year of absence i'm back. I have still to check/reset my emails and other data to be able to login here again as "tinhead", so for now just with temp account. I bet there are lot of PMs in "tinhead"s inbox, to make a clean cut i will simply purge them all, if you have still something important please re-send PM (in a week or so, i need to "reboot" myself first).
tinhead
after nearly a year of absence i'm back. I have still to check/reset my emails and other data to be able to login here again as "tinhead", so for now just with temp account. I bet there are lot of PMs in "tinhead"s inbox, to make a clean cut i will simply purge them all, if you have still something important please re-send PM (in a week or so, i need to "reboot" myself first).
tinhead
Hi.
I see that you have 4 wires connected. 3 wires should be enough.
-Don't connect that+3.3V to the USBtoserial adapter.
-Check that RXD line is connected to the right pin.
-Try to use your adapter alone and see that the characters are echoed. This can be done by connecting txd and rxd lines together on the usbtoserial adapter. The character should ehco when you type a letter.
-Check that flow control and parity is set to None.
-Check in device manager that the comport has 115200 speedsetting. This is normaly 9600.
For the backup I used files from "Tools_P_models.zip" to my P type osciloscope. Check that the backup is for your D model. I don't know if there is some difference.
In the "Backup_P_models" folder there is a text file describing the commands. Possibly you could run the backup commands from commandpromt if you get it to work.