Nifty, you would think the other vendors have learned a thing or two after the rigol incident.
I have a sneaking suspicion letting the hack info continue and not be suppressed is actually good for business.
Consider:
If sales of the Rigol 1052E double, it would compensate for each single lost sale of the 1102E
But If the 1102E is really just a factory hacked 1052E, then the manufacturing cost to make either scopes is equal, so they are not losing any sales at all, just making more. The excess inventory of 1102E can always have their case stickers changed and firmware reburned to downgrade them into 1052E. So the only cost to make an 1102E over a 1052E is labor to do the firmware and casing decal changes.
If the owner bricks his scope and asks for factory repair, the unit is not under warranty, and now not only did they make a sale on a scope, they can charge for repair
Rigol now has a bigger reputation, free publicity, more people own it, know its electronics intimately and thus have a better appreciation of its capabilities, and will consider buying their other products now too
So, its a win win.
If you look at the trends in electronics, there is a market of makers and hackers so manufacturers are addressing their wants. Hakko's new iron, the FX888, Agilent's DMM skins, Hakko 936 skins etc., certainly isn't directed towards professional electronics.Nifty, you would think the other vendors have learned a thing or two after the rigol incident.
cant find it in ebay, just the 200MHz version. maybe they are pulling all 100MHz back to upgrade to 2.04.SP1 FW? ??? just speculation, not related to anyone who is still live or dead.
Nifty, you would think the other vendors have learned a thing or two after the rigol incident.
maybe they are pulling all 100MHz back to upgrade to 2.04.SP1 FW? ???
Hi tinman,
Can you post some more pictures please?
Looks like I'll be picking one of these up in China next month ;o)
Thanks.
Any idea if Tekway makes Hantek's handheld oscilloscopes too?
Do you know if the Hantek DSO-1060 could be modified to be
a DSO-1200? This would change a 60Mhz scope into a 200Mhz scope.
Great information, I bet there's going to be tons of discussion
about this topic!
Scott
whats with the blank capacitor? top left near the samsung? 4th picture
I wonder if you can redirect the terminal session to the 7" LCD and use a USB keyboard (that would make an awesome hackable scope)
I did find this one for sale, but it is already at 200Mhz.
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=270568563296&ssPageName=STRK:MEWAX:IT (http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=270568563296&ssPageName=STRK:MEWAX:IT)
Tinman, have you tried this hack on the DST1062B?
Do you know if the DST1062B has the same components as the DST1102B?
Thanks.
that's the self-calibration unit, it runs with 125Mhz.Do you mean that it has a 125Meg oscillator on board which is used for the sole purpose of selfcalibration???
Yes tinhead, there is now a 200Mhz DSO5102B! I will let the scope warm up for an hour or so, and then re-adjust the scope probes. Should I do a recallibration as well?
Many thanks again for the massive effort yesterday, I got quite a surprise when I switched on the PC...to find a working firmware update! ;D
Are the Tekway/Hantek firmwares directly interchangeable, what I mean is, if say Tekway brought out an update, could it be applied to a Hantek without having to be modified?
another one screenshot ...
My previous bw measure was done with 1ns rise time generator, which is normally not sufficient (due cable, terminator loss).
So here we are, i did build the 250ps generator (well, at least on my 500MHz scope it shows 550ps rise time)
and made some measurments on the Tekway/Hantek DSO. The result is 1.3ns which is equal to 270MHz -3db bw.
So here we are, i did build the 250ps generator (well, at least on my 500MHz scope it shows 550ps rise time)Did you verify the amplitude with your 500MHz scope? Rise time is measured from 10% to 90% of the signal amplitude, so if the scope shows a lower amplitude due to the attenuation of the high-frequency component, the apparent rise time will be higher. A step is much easier to use than a pulse for this reason.
and made some measurments on the Tekway/Hantek DSO. The result is 1.3ns which is equal to 270MHz -3db bw.
NICE, tinman, what did you use generate 250ps?
NICE, tinman, what did you use generate 250ps?
the Linear Technology, App Note 47.
I didn't had LT1073 but 1073-5 so changed some Rs values in 90V power supply part, but the rest is the same.
Did you verify the amplitude with your 500MHz scope? Rise time is measured from 10% to 90% of the signal amplitude, so if the scope shows a lower amplitude due to the attenuation of the high-frequency component, the apparent rise time will be higher. A step is much easier to use than a pulse for this reason.
well actually this is like apple and birnes, a scope with higher BW will show evt. higher amplitude. On the other side 10%/90% areJust to elaborate why I think amplitude matters:
from measured signal amplitude and not the real amplitude.
It should be fine for relative tests, but I wouldn't rely on the actual numbers.
The SDK kit (for both Hantek and Tekway) is scheduled to be released end of Jauary 2011,
the firmware source code (which is under GPL and have to be published) will be not published,
this seems to be GPL licensing misunderstanding so i will try to explain again both companies what's about.
The SDK kit (for both Hantek and Tekway) is scheduled to be released end of Jauary 2011,
the firmware source code (which is under GPL and have to be published) will be not published,
this seems to be GPL licensing misunderstanding so i will try to explain again both companies what's about.
Send an email off to this group (http://gpl-violations.org/about.html). They'll do the chasing up about GPL compliance.
Do they link their proprietary executables statically and/or with GPL (not LGPL) libraries? If yes, they have to publish sources or at least linkable object files of these executables as well.
and again.. sorry if i miss something... where can get this hackable DSO model? still didnt show up in my ebay :( ...can the hack update... be updated in the 1st post for ease of referencing? (just a suggestion) as i said.. i may have missed something due to lack of supply. :-\I bought mine from GoodLuckBuy.com (Hantek DSO5102B)
Is the Tekway Chinese?
.o:0|O|0:o.
This thread caught my eye. Do you care to do a review on the Hantek scope? In particular, can this scope be controlled via the USB port?
One thing that I like about the Instek is that it has a documented programming interface, and you can interface
it to your own software (such as NI Labview, or Python/VISA). Does the Tekway have a similar interface?
How does the triggering, display, etc. compare? How is the brightness/crispness/viewing angle?
Also, anyone had experience ordering from Goodluckbuy.com to the US? How long did it take?
Also, anyone had experience ordering from Goodluckbuy.com to the US? How long did it take?
Many thanks!
Dave
Hi everyone!
Also, anyone had experience ordering from Goodluckbuy.com to the US? How long did it take?
Many thanks!
Dave
Same question - different destination ;)
Anyone had experience ordering from Goodluckbuy.com to Germany? How long did it take?
Tinhead, can you shed some light on how you managed to extract the gpg key ? Might be of interest to other projects as well.
Great! Have you by any chance tried out the USB port on the back? With the drivers installed, does it look like a serial port? Does it implement an SCPI command subset?
Also, a question about the responsiveness.
Currently there is funny firmware bug (fw 2.06.2), with some specific combination of run&stop/single/time base change/memory length
the DSO is showing wrong data. This means don't use single shot with long memory (everything over 40k) in higher time base than 200µs.
Run/Stop is displaying proper data, single shot too as long you don't change time base. I did send a error log/description to Hantek/Tekway today.
Well, I needed a scope this week, so although I had been leaning toward the instek before finding this thread, I decided to go with the Hantek unit, in part due to the higher bandwidth, and bigger screen at a cheaper price. I'll post my thoughts in the review section once I've had time to play with it.
I ordered mine from Emtesco/Morton Controls in Colorado. They appear to be the US official distributor for these Hantek scopes, and also stock some other interesting cheap scopes: https://www.mortoncontrols.com/index.php?main_page=index (https://www.mortoncontrols.com/index.php?main_page=index). BTW, it sounds as if they will be offering some Black Friday deals on these units.
Pray tell, what is your final price like, after S&H, and taxes?
what type of scope would you choose/recommend for someone like me, who is just about to buy a new scope ith limited budget
My understanding aber reading the entire thread is that the tekway offers the better screen and resolution, but the innards seem to be all the same?
To: tinhead.
What can you say about Oscilloscopes OWON PDS8102T/PDS8202T?
Can I change the first model in the second (100 MHz to 200 MHz)?
I choose the oscilloscope, and looking at your messages.
Thank you!
Igor, Russia.
Just received my 100 MHz Hantek. I'm thinking about replacing dso.exe with something that would be more extensible, i.e. with wavelet support in addition to FFT etc. Are there such projects already?
Upd: I made another firmware extract utility. It does exactly the same but does not modify any files on oscilloscope at all. Everyting is done inside the update script on tmpfs. See attached file.
To start with, I'll have a go at backing up the firmware (in NAND flash) once I get the unit.
One question, does the USB firmware dump utility backup the vivi bootloader as well?
I am not sure if Nanddump utility could access that partition at all.
Also any idea where in NAND flash the factory settings are stored or what these settings are for?
@ Tinhead
Thanks for the extra .bin files. I received my Hantek today, and did a firmware dump.
It is reassuring that the total of the .bin file sizes (including the ones you posted) works out to be the same as the Nand Flash memory size.
Is there a schematic of Hantek input stage, maybe reverse engineered?
Is there a schematic of Hantek input stage, maybe reverse engineered?
It's 2.06.2 (101028.0)
I think this is the last one.
I didn't made any update, so this is the pre-loaded (original) version.
Before I make any changes I will find out if this scope could make me happy at last :)
Santa was here :)
What do you think the odds are we can get LA software running on these things?
Do you know how the input from the probes is passed to dso.exe? (fancy memory access, "Everything is a File" /dev instance, ...?)
Santa was here :)all those santas... do you intend to sell it here? interesting.
Santa was here :)all those santas... do you intend to sell it here? interesting.
- ARM I/O port (which have 16bit data, 4 address, nOE, nWE, nWAIT, GPIO select 3, nBE1, ext int9, reset signals and 3.3V/GND)
- ARM I/O port (which have 16bit data, 4 address, nOE, nWE, nWAIT, GPIO select 3, nBE1, ext int9, reset signals and 3.3V/GND)
Hello tinman,
have you been able to find out the exact io port assignment?
I've already tried to find out myself and I found similar signals. But there are still ambiguities with some pins.
I'm afraid it's nearly impossible to clarify them without unsoldering the cpu.
Thanks a lot
I'm afraid it's nearly impossible to clarify them without unsoldering the cpu.
I'm afraid it's nearly impossible to clarify them without unsoldering the cpu.
btw, i did it, so now we know all used/unused pins.
Unfortunately i have still to work from time to time, so reversing is going slow...
A bit offtopic, but regarding the ARM processor:
Where do You buy them? There is a project with S3C2440 uC and farnell/digikey/etc has no such processors on stock.
Hello Guys,
We are Hantek 'a agent in France and we can deliver many DSO5102B as our stock is large enough.
Please visit our website: http://elec3i.com (http://elec3i.com)
Hope to deal with you soon. ;)
Best regards,
Pascal
Hello Guys,
We are Hantek 'a agent in France and we can deliver many DSO5102B as our stock is large enough.
Please visit our website: http://elec3i.com (http://elec3i.com)
Hope to deal with you soon. ;)
Best regards,
Pascal
Are there possible discounts for students? I've managed to get a discount @ German Pinsonne electronics to the same price(shipping included) as Yours for DSO5062B. If it is possible to have a discount @ Your company, I will cancel my order there and buy Yours :)
cuo le mei you ? dui bu qi.... :oyou can translate some of chinese ee sites for us.
Hao ba ! :-\
I think we can argue and we don try to cheat people anyway. ;D
Well, if VAT is not mentioned in the invoice or it is marked as added already, then who cares in Europe? :)
Well, if VAT is not mentioned in the invoice or it is marked as added already, then who cares in Europe? :)DSO5102B price on elec3i.com is 589EUR, -30EUR for eevblog users is a good total price.
I would say cancel your pins**** order and buy the 100MHz from elec3i.com.
...
Or buy the DSO5062B and extra 200MHz probes ...
1. Using cursors with 2 channels with different volts/div. Triggering is off channel 2. Voltage cursors are on channel 1 - but the scope displays cursor readings using volts/div for channel 1. I am definitely selecting cursors to be sourced by channel 1.i think you mean "but the scope is displaying cursor reading using volt/div from ch2 (and not ch1)
2. Observe a signal on channel 1 and setup triggering using a suitable level and timebase. While observing the waveform press "SINGLE SEQ". The waveform is captured. Change the timebase to another setting. Press "SINGLE SEQ" again. The waveform is captured but at the OLD timebase setting, even though the scope is displaying the NEW timebase on the screen. The workaround is to change the timebase only while the scope is in the RUN mode i.e. the "RUN STOP" button is green.
Apologies if this has been answered already. Can the Hantek DSO5102B standard software be upgraded with Tekway DSO1102B files. Also can either Hantek or Tekway TTscope software be used with my scope?
This is just my experience and it could be different for other people:
I bought my DSO5102B from the chinese website Goodluckbuy for ~492 EUR and they shipped via DHL express for free. It arrived here in the UK within 7 days and it was in prefectly new condition (the box had seen better days though).
I let people think about risks carefully...
Hmm, I have run into a stumbling block. I have tried to update my 'scope (a Hantek DS5102B) with the files provided in do_Hantek_DSO5202B.zip, and I get:
Software upgrade failed, error 0xf7
Illegal upgrade files detected!
Haven't got a JTAG programmer handy, so I'm hoping the USB upgrade method will work.
Dear Scrts,
Of course not, no service for people who buy outside our shop, because warranty is relative to a device serial number. Another thing too, we cannot garantee devices which were illegaly upgraded (hacked) and I don't know any which will accept this... ;)
Oh by the way, I paid 2000 Yuan for it, that's about 235 euro ;D
Unfortunately, many Chinese websites do not have the English version.
It is very difficult to make an order on such site. Often they do not accept international payments because work with the Yuan only.
Chinese vendor's limited access to international payment systems (credit card, Paypal *spit*) is.This is what I meant.
But they of course take a fee, and I would be very careful when selecting one, so not to end up with a conman. In the end it might not be worth using an agent.This problem actually exists.
Since mine DSO5102B has a new firmware, I have to use UART or JTAG. Is it really UART there is 5V levels? I have my own board with FT232 and 3.3V levels.
Also maybe it is possible to get step-by-step manual how to flash firmware using JTAG? I have Segger J-Link :)
I see that the scope top surface above LCD gets warm, since there is no cooler. Is it normal?
2. Observe a signal on channel 1 and setup triggering using a suitable level and timebase. While observing the waveform press "SINGLE SEQ". The waveform is captured. Change the timebase to another setting. Press "SINGLE SEQ" again. The waveform is captured but at the OLD timebase setting, even though the scope is displaying the NEW timebase on the screen. The workaround is to change the timebase only while the scope is in the RUN mode i.e. the "RUN STOP" button is green.
yes, this is known bug (new since 2.6.x), i did notified Hantek/Tekway about it already.
As a work around you have to select always first "run", change time base, and then use single seq.
Especially if long memory is specified this bug really sucks, but the work around works (so let's hipe next fw will fix it).
The i/o port is LVCMOS of course (3.3V). I know that the ports are 5V tolerant, but i would still
recommend to use "proper" 3.3V levels.
so as you can see they hot but still within specs. You can install a cooler, there is everything prepared on power supply PCB (7805 + some caps).
It is enough to drive a 12V cooler with 8V or even 5V to make the enclosure temperature much lower (with 5V almost no cooler noise)
so as you can see they hot but still within specs. You can install a cooler, there is everything prepared on power supply PCB (7805 + some caps).
It is enough to drive a 12V cooler with 8V or even 5V to make the enclosure temperature much lower (with 5V almost no cooler noise)
BTW, no news about SDK? I've managed to dump all the firmware, so I am safe to start :)
Hi,
on this side I have written down my experience with the Tekway DST1102B. Maybe someone find it useful.
Here is the Side in German (http://www.martin-lauff.de/tekway-dst1102b.html (http://www.martin-lauff.de/tekway-dst1102b.html))
and here in English (http://translate.google.com/translate?hl=en&sl=de&tl=en&u=http%3A%2F%2Fwww.martin-lauff.de%2Ftekway-dst1102b.html (http://translate.google.com/translate?hl=en&sl=de&tl=en&u=http%3A%2F%2Fwww.martin-lauff.de%2Ftekway-dst1102b.html)) by Google translator.
I have the Firmware version 2.06.1 (101008.0). I wonder if there is an update for my DSO. In the Internet I haven’t found any.
So if the updates are pretty frequent, what about hacked devices updates? Once hacked to the better BW scope, the official firmware will detect the hack or not? I wonder if the firmware update tool check the current version of the software or it checks the hardware. There is possibility, that one day, the hacked scope could be updated (or actually downgraded) only using JTAG.
The ch2 position knob protrudes about 2mm more than the ch1 knob, it was glued (or is stuck) to far out on its shaft.
On my unit the measure and cursor buttons have to be pressed about twice as hard as all the other ones.
The ch2 position knob protrudes about 2mm more than the ch1 knob, it was glued (or is stuck) to far out on its shaft.
The TTScope software shows the not very informative message "5" upon clicking the connect button in Vista (in VMWare Fusion, will try on native windows).
Btw, That TTScope software is slow as hell... Pointless except of using for steady signal screenshots... Like on every scope :) I wonder if the scope has LAN expand module, what software does it support?
The TTScope software shows the not very informative message "5" upon clicking the connect button in Vista (in VMWare Fusion, will try on native windows).
On my unit the measure and cursor buttons have to be pressed about twice as hard as all the other ones.
disassemble the unit, maybe there is a piece of whatever inbetween.
The ch2 position knob protrudes about 2mm more than the ch1 knob, it was glued (or is stuck) to far out on its shaft.
they normally not glued, you can remove them easily.
I discoverd your TTscope hang with the DSO.
I read it in the Eevblog. I wanted to post the answer but i cannot access the
blog most of the time because of DNS propagation again, I suppose.
So here is the issue: Hantek used to deliver bad TTscope and I found that the
TTscope from DSO5202B CDRom works well with DSO5102B. I reported the issue to
Hantek who will correct it with new shipments.
You will receive a link from NextSend server to download new TTscope version.
Follow the instructions and read our bugs report.
Thank you.
Kind regards,
Pascal Geyre
Elec3i
I have chosen to void the warranty... Whatever :) I could reupload the previous firmware and send it back to hantek if something happens, but seems like all of the parts inside (FPGA/uC/ADC/etc) are orderable and still in production, so it is possible to change them myself.
hehe, just joking guys. I did ordered some PCBs and was about to announce the production,
but if Elec3i will sell them too (as manufacturer supported version) i will throw my PCBs into trash.
@Zinahe
if you ever heard about "chinese piece of crap", then it was one of such famous things like the UNI-T CEL.
This is one of these management decision devices, not a new design, just a new display, cheap interpolation (actually not interpolation, 4 pixels will be displayed as one) on a cheap 480x234 display. So what is the resolution ? Exact 240 x 120 ...
So no, don't compare it and no there is nothing "similar" (just think about 7' BMW and VW Golf .. both are cars - you can drive both but you should not compare). For sure some ppl will buy UNI-T, but to be very honest Rigol is cheaper (and with some luck you hack it)
is having 320x240 resolution and light years better than the UNI-T.
About a hcak possibility : UNI-T is like Rigol FPGA + DSP based - the most critical thing is to hack the DSP firmware. Just check the Rigol thread and you will see it can be possible but only if the manufacturer was too lazy ... If you have a chance to get both 100 and i don't know 60MHz? you can try to compare firmwares .. but that's a lot of work, time and it costs some money.
... since I sell and support all the Mini2440/Mini6410 products.Maybe You have Your eshop? I am interested in mini2440/6410 boards
before i change my mine, how many of you guys would buy such LAN-addon board right now?Hm, what about WLAN modules? :) I would be interested in those :)
before i change my mine, how many of you guys would buy such LAN-addon board right now?Hm, what about WLAN modules? :) I would be interested in those :)
... since I sell and support all the Mini2440/Mini6410 products.Maybe You have Your eshop? I am interested in mini2440/6410 boardsbefore i change my mine, how many of you guys would buy such LAN-addon board right now?Hm, what about WLAN modules? :) I would be interested in those :)
before i change my mine, how many of you guys would buy such LAN-addon board right now?Hm, what about WLAN modules? :) I would be interested in those :)
all china DSO have one common thing - the enclosure mechanical construction. Just remove top screws (behind the hangripp so you have to remove it forst), remove bottom screws.
Regards Linux 2.6.13 and DM9000, no there are no issues with drivers.
Can you generate a lissajou pattern with frequencies >= 100kHz? If you can, what's the limit before the scope starts to choke?
Can you generate a lissajou pattern with frequencies >= 100kHz? If you can, what's the limit before the scope starts to choke?
no issue up to end of bandwidth, even 190/380MHz has been displayed properly. Starting from 1MHz down to 150Hz there are some small gaps (like on analog scope), but they can be easily "disabled" by the wave persistency setting (e.g. 0.2 sec persistency is fast enough for human eye to produce complette waveform but still fast enough to not produce visual latency). Then from 150 to 20Hz the signal is dropping producing more noice than "waveform".
The persistence function in the Rigol 1052E works so long as the phase is matched and doesn't drift, otherwise it slowly paints the entire view area a nice solid color!
The persistence function in the Rigol 1052E works so long as the phase is matched and doesn't drift, otherwise it slowly paints the entire view area a nice solid color!
luckily the HanTekway DSO have 0.2sec, i believe the lowest persistance on Rigol is 1sec, that's just too much.
Additionally you can change screen refresh rate on HanTekway between auto, 30, 40 and 50 frames.
I did my tests with 50frames/sec (i just love when the screen is updating very fast), but recognized later that
for phase unsync slow XY signals is better to set auto or 30frames/sec to get even better picture than with persistency on 0.2sec.
So you can see there are some features helping a bit out. Someone mentioned already that the noice level in XY mode is very high
on HanTekway DSOs. But to be very honest it seems to be the same "issue" on Rigol (or at least from what i saw on screenshots).
Can I add another Russian? I'm willing to translate all menus and built-in help.
How do I upgrade to DST1202B?
Looks to me that Tekway DST1102B and Hantek DSO5102B is the same scope
... but the Hantek is bit cheaper. Should I expect better quality with Tekway?
Looks to me that Tekway DST1102B and Hantek DSO5102B is the same scope, but the Hantek is bit cheaper. Should I expect better quality with Tekway?
Hantek/Tekway buyers, do not forget Elec3i for your purchase ;D
i got nice answer from Hantek/Tekway, they will not release the SDK yet (company policy - the firmware have too many bugs
and they wish first to fix them before SDK will be released, this is good idea).
The only bad thing is - they will not release the source code.
For above someone asked could not find USB driver for windows 7. You can just install TTscope on CD come with your machine first, and plug DSO in and manual install driver from TTscope installation directory under x:\program file\TTscope\drivers or similar, accept install driver anyway, it'll work. But when u trying to connect it with TTscope, it'll report sort of error and won't work anyhow.
Before I open it up, I had a feeling that this one is 200Mhz ready, as the SN lable on the back of machine is T 1G/200M 00xxxx, but firmware show T 1G/100M 00xxxx. Yep after I open it up it is 200Mhz ready--44A(280) and 330 risistors on board.
Btw I think the front shell and knobs color should be gray instead irovy, as time and heat will let irovy turns to yellowish.
just don't use the TTScope from CD, the one on Hantek website is bit better, especially drivers.
So after spending a lot of time debating buying Atten, then finding and reading this entire thread (thank you to all of you who have contributed) I no longer am interested in Atten and want to get one of these instead. The questions I have are is there a preference (quality, potential future support, ect) between Hantek and Tekway? Also is the 100MHz version worth $140USD more than the 60 or has anyone here successfully upgraded a 60 to say a 100 or even 200 (money is tight so if its not necessary I don't want to spend it)?
Sorry for all the questions and I appreciate any responses.
Thanks,
-Ian
This was the question that I had before I got my. Believe Tinhead. Hantek and tekway are identical, all their boards made by tekway, diff maybe just on firmware/logo and frontpanel cosmatic look.
Yes, you can mod 60 to 100 or to 200,or 100 to 200. someone already confirm it.the whole thread is about the mod, and yes this works.
All you need is change some risistors and hack the software. but Three things remind you.
1.Those are SMD resistors, you'll need proper tool and skill to change them (hot gun or smd tweezer iron), and resistors cost money. Mine's lucky, come with 200 ready.
2. For hantek5102B 2.6.2(101108.0), you'll need JTAG way to hack it, or modify USB files to cheat DSO. I don't know tekway.
3. I heard probes come 60Mhz is 80Mhz. You may ask these to confirm. My 100Mhz come with 150Mhz. Good probes cost quite a bit in NA, 1/10 price in China.
tinhead, do you have the input schematic for this scope? I am trying to learn a bit more about oscilloscope inputs and filters. I lost the original PDF, then you took it down. Would appreciate it, thanks!
yeah i do have, currently a bit busy with other things but soon i will publish it, together with Ethernet-addon schematic.
why do you give the option of 100MHz, 150, and 200? why not just 200? why should any one want to be at 100/150 when they can have 200Mhz??
so i just got mine DSO5062B and i tried to updated it to the 200Mhz.. So i went here:
https://www.eevblog.com/forum/index.php?topic=1571.msg24564#msg24564 (https://www.eevblog.com/forum/index.php?topic=1571.msg24564#msg24564)
downloaded do_hantek_DSO5202B.zip extracted it to a flash drive and when i hit update firmware i get an error saying:
Software upgrade failed, error 0xf7 Ilegal upgrade files detected!
System status shows:
model: DSO5062B
soft version: 2.06.2 (101108.0)
hard version: 0x555583e8
so i just got mine DSO5062B and i tried to updated it to the 200Mhz.. Software upgrade failed, error 0xf7 Ilegal upgrade files detected!
System status shows:
model: DSO5062B
soft version: 2.06.2 (101108.0)
hard version: 0x555583e8
Guess more people ask, Tinhead may release new version USB files.
New Firmware dump utility
Hantek/Tekway did added some protection into firmware update procedure, therefore the fw dump
utility need to be changed too.
Tinhead, you write: "must be same as your DSO model!"
I have a DST1102B but the DSO installed DST1202B. Which model do I specify, and do I need to update your software?
I installed your program without saving the original.
I think they're watching this thread ;)New Firmware dump utility
Hantek/Tekway did added some protection into firmware update procedure, therefore the fw dump
utility need to be changed too.
I think they're watching this thread ;)
- i promised Han/Tekway to not create any new USB hacks
- i wish Han/Tekway will spend time on fixing firmware bigs and the SDK - and not on new protections only because i created another one USB hack for "lazy" ppl
Q. Does that mean the rest of us can't/shouldn't talk about the USB hacks?
But I just wanted to know what your policy was on others posting what could be considered...let's say "sensitive"...information regarding these DSOs. And when I saw your post saying that you promised not to post any more USB hacks, I thought it would be a good idea for me to ask first.
So tinhead, would it be okay with you if I were to start a new thread discussing in detail these DSO's internal workings (with some info regarding USB modding) and modding in general?
if you download the fw_backupV3.zip you will see what is always needed to allow an update, in principle it is only the logotype.dis which need to be present in firmware file and the content must match the content of logotype.dis in DSO root directory.
The CR+LF issue is just because the firmware update procedure does string compare.
If you decompile dso.exe you will see the "magic" arround ubdb.swi, logotype.dis, ucUpdateType, ucSysType, ucSysBrand and ucUpdateBrand - just look for UpdateSysFiles procedure.
Q. What's the file format for the .ico files? (e.g. hantek_DSO5202B_mid.ico) Anyone know? It looks like a .png or RGB format to me.
Does anyone know where a Hantek or Tekway DST1202 or DST1102 can be purchased for a reasonable price.What do you consider a "reasonable price"?
Hi all,
I was about to purchase a Tekway DST1202 from a trader in China. But when the trader asked the manufacturer about supplying a Australian 240V power plug, he was told that they now don't supply Chinese traders with English menu oscilloscopes, they would only supply him oscilloscopes with Chinese menu. He was told this was to protect their overseas agents. He indicated that Hantek also wouldn't supply oscilloscopes with English menu.
I wonder if China have a Trade Practice Act (law), isn't that restricting free trade.
A search on Ebay didn't find any Tekways.
Does anyone know where a Hantek or Tekway DST1202 or DST1102 can be purchased for a reasonable price.
Thanks for your help.
I check the power board, The reserve fan connector has a dedicated 12v power supply(7812). But I would like the fan run less speed, I connect the fun to 5v on board, not even can hear fan noise.
replace the 7812 by 7805, it is oly dedicated for fan, so no big deal - and of course less stress for the 5V on main PCB.
Question, will the hack also fix the language problem if there is a command to change the language?See my questions on Tekway DST1102 in the Chinese version of Tinhead, and answers, starting with # 212 in this forum thread.
Thanks rf-loop and all for your help.
Mr Pioneer Huang was one of the Chinese traders who said that he only had Telway oscilloscopes with Chinese Menu (display). Another Chinese trader said that both Tekway and Hantek would now only supply him with Chinese Menu oscilloscopes. And that the reason was to protect their overseas agents. It was only when he talked to the manufacturers that he found this out.
[cmd] cp -f /usr/up/tekwayup_client/l /logotype.dis
[cmd] chmod 766 /logotype.dis
And you're good to go.Okay, well, back to modding my DSO5102B via the USB Update Firmare...
Finally got it to work! Turns out the only hitch was that if you include a file named logotype.dis in the .up file, it will be checked for the correct "hantek_DSOxxxxx" label inside. But if you simply rename it to something else (I just renamed it l), it won't be checked. And like I've mentioned before, you only need the update file listed in the upend file. You can include other files without listing them in the upend file since it's all untarred en-masse. Then in the update file, you just need to do something like this:
it is stored in eeprom connected to s3c2440, it is easy to change it.
But another thing bug me know, while checking my boot log, looks my NAND has a bad block. Can you please confirm with me?
...
Even looks doesn't make any trouble with the DSO, I think I need make a JTAG for full backup really soon.
Backup is always good idea, as long you have no ARM JTAG just use the fwdump v3, it will save
bootloader, root and kernel - that's all you evt. need later.
Update: yes it'll works, H-jatag has driver too.
you will need OOB H-JTAG driver to save/restore OOB blocks too!
you can find NAND-OOB drivers for H-JTAG here
http://www.mikrocontroller.net/topic/163836 (http://www.mikrocontroller.net/topic/163836)
The s3c2440 ARM need to be initialized, the right one init is already included in H-JTAG software, just
load in H-Flasher the ..\HFC Examples\S3C2440+K9F1208.hfc
You can disable flash id check too if H-Flasher don't like Hynix with NAND OOB drivers (or change the driver, whcih is simple)
Tekway
USD 580 and free shipping in this store in mainland China: Store http://www.aliexpress.com/fm-store/312788 (http://www.aliexpress.com/fm-store/312788)
(I have also talk in phone with this store man "Mr Pioneer Huang" But I did not buy becouse I find more economy solution (not only one scope))
Scope in this store http://www.aliexpress.com/product-fm/414433064-DHL-Free-Shipping-Tekway-DST1102B-Oscilloscope-2channels-100MHz-1GSa-s-7-TFT-16-digit-color-800-wholesalers.html (http://www.aliexpress.com/product-fm/414433064-DHL-Free-Shipping-Tekway-DST1102B-Oscilloscope-2channels-100MHz-1GSa-s-7-TFT-16-digit-color-800-wholesalers.html)
Is there any advantage in using a Hantek DSO5102B over a DSO5062B or a DSO5062C (60MHz) when hacking to a DSO5202B (200MHz). Other than the price.
Tekway
USD 580 and free shipping in this store in mainland China: Store http://www.aliexpress.com/fm-store/312788 (http://www.aliexpress.com/fm-store/312788)
(I have also talk in phone with this store man "Mr Pioneer Huang" But I did not buy becouse I find more economy solution (not only one scope))
Scope in this store http://www.aliexpress.com/product-fm/414433064-DHL-Free-Shipping-Tekway-DST1102B-Oscilloscope-2channels-100MHz-1GSa-s-7-TFT-16-digit-color-800-wholesalers.html (http://www.aliexpress.com/product-fm/414433064-DHL-Free-Shipping-Tekway-DST1102B-Oscilloscope-2channels-100MHz-1GSa-s-7-TFT-16-digit-color-800-wholesalers.html)
In Ali you can also chat with seller and this seller also answer phone if you want check for security. (you ask his phone if you need)
Also you can buy with safe system (seller get money after you get scope - but you send money first...)
This seller write quite good english.
And also you can select with same price Hantek or Tekway (100MHz)
MOQ = 1pcs
price USD580
Shipping = Free by DHL (and I think also to Australia)
Power cord... normal power plug in scope end ... just as nearly all equipment you can buy compatible power cable in your country.
China normal electric is 50Hz 220 - 230Vac. (only what chance is this cable wall end, scope end is always same)
With same price my own opinion is "buy Tekway" mut this is only my opinion.
Also you can use PayPal
There is also Escrow (littlebit more safety) system between you and seller.
Mr Huang had to keep the package as small as possible so he could make some money from the sale. I don't mind as long as it arrive in working condition,yeah, normally there is another one a bit bigger paper box arround the small one, but you ruight as long i did arrived healthy who cares.
See what I mean? English buttons plus Chinese panel. Maybe someone here with an English panel could scan and upload so that we could print it out? Or even better, learn Chinese, I don't think it's that hard you only need to memorize the top 9 or so buttons the rest are in common positions.
Hantek DSO5062C
Okay now I need to go figure out how to change the chinese menu/firmware to English. Or take up Chinese electronics class :P
Okay now I need to go figure out how to change the chinese menu/firmware to English. Or take up Chinese electronics class :P
tell me the firmware version, click on red marked button and then F1
I think the firmware version is the second line ??? 2.05.0(100305.0)
but I am not ready to alter the Mhz of my scope yet because I am still 'evaluating' the unit.
to add parallel resistors instead of replacing resistors to get the 200MHz resistor values. Problem is where can you purchase these resistor values in 0.1% and 1%?
Do you know what physical size the SMD resistors are.mouser is haveing alle of them,
what equipment do you need to calibrate the oscilloscope when the above resistors have been changed. What is the procedure. Would the normal oscilloscope push button calibration do the job? I don't know much about what the calibration is other than you only have the power cable connected to calibrate.
Just arrived:
but all this need now lot of work for tests.
Attached the official 2.6.3 for Tekway DST1102B, so you can update your scope to latest vfw version and add english language.
true, you always very sceptic so you will definitely test 5x :)
Q1. Can I load v2.06.3 onto my Hantek 5102B?no, you can't.
Q2. What's the improvements in v2.06.3 from v2.06.2? (i.e. Is it worth upgrading?)
5x is not enough.
If test full specs temp range, humidity range, pressure range it need more... and also repeating so that can make some opinion about random variations... haha. (yes I do not...)
hi ,tinhead'
would you make a firmware for tekway1062B(version 2.06) to hack it to 200MHz?
hi Mirgo,
Ni shi zhong guo ren ba ? ;D ( ::) Are you chinese ? ;))
I scanned the Chinese panel and replaced the characters with English.
I haven't tried it on for size yet, but it looks close!
-P
Trigger stage
100MHz - 466.5R !!!
Sorry, I measured again it's 100R. All good!
Btw, Tekway is as always clean soldered, i wish Hantek will learn to soldr too ... almost every Hantek was not that clean.
I scanned the Chinese panel and replaced the characters with English.
I scanned the Chinese panel and replaced the characters with English.
Tekway/Hantek doing YouScope demo ...Are you a magician?
Tekway/Hantek doing YouScope demo ...Are you a magician?
I want this demo too! ;D
what equipment do you need to calibrate the oscilloscope when the above resistors have been changed. What is the procedure. Would the normal oscilloscope push button calibration do the job? I don't know much about what the calibration is other than you only have the power cable connected to calibrate.
Question: For compensation you refer to 3 components. Do you have to change all 3 components or you only have to adjust the trim capacitor?
I have finally ordered a Tekway DST1102B 100MHz oscilloscope from Pioneer.
http://www.aliexpress.com/product-fm/414433064-DHL-Free-Shipping-Tekway-DST1102B-Oscilloscope-2channels-100MHz-1GSa-s-7-TFT-16-digit-color-800-wholesalers.html#tabbed-pane (http://www.aliexpress.com/product-fm/414433064-DHL-Free-Shipping-Tekway-DST1102B-Oscilloscope-2channels-100MHz-1GSa-s-7-TFT-16-digit-color-800-wholesalers.html#tabbed-pane)
I will let you all know how this purchase go, I don't anticipate any problems as Pioneer has at this time a 100% positive feedback, refer to the above link :).
My God, I had visited this Aliexpress website :o . You can see how no care is made for packaging and handle electronics accessories like probes.
If people only concentrate the price, well why not proposing everything like a kit with components, case, bill of materials and serigraphy masks for each country!
Then people arrange by themselves (soldering, cleaning, testing) and everything is ok. Ok, men, we will give you a 300.00 EUR oscilloscope kit, and wish you good luck ! ;D Just this policy is not ours: we change bad boxes, change power cord with 2.50m (Hantek/tekway is 1.50m, a bit short for convenience), change CD small pocket when this one is damaged. Electronics should be handled with care, not like trash...
If people only concentrate the price, well why not proposing everything like a kit with components, case,
bill of materials and serigraphy masks for each country!
My God, I had visited this Aliexpress website :o . You can see how no care is made for packaging and handle electronics accessories like probes.
If people only concentrate the price, well why not proposing everything like a kit with components, case, bill of materials and serigraphy masks for each country!
Then people arrange by themselves (soldering, cleaning, testing) and everything is ok. Ok, men, we will give you a 300.00 EUR oscilloscope kit, and wish you good luck ! ;D Just this policy is not ours: we change bad boxes, change power cord with 2.50m (Hantek/tekway is 1.50m, a bit short for convenience), change CD small pocket when this one is damaged. Electronics should be handled with care, not like trash...
Hi Pascal,
Question: do you give a three year warranty if we change the resistors and firmware in the oscilloscope?
Hi Pascal,
Question: do you give a three year warranty if we change the resistors and firmware in the oscilloscope?
hehe, RFman, knowing that a custom might play with the DSO internals is one thing, allowing up front is a different thing.
I would never allow it up front, therefore all my customers got a simple question "shall i do it for you?",
if yes i did it and i'm responsible for potential warranty issues, if no then i placed "tags" in NAND, PCB and input channels cover.
But well, the question is not what i think and allow, the question is what Pascal does.
I scanned the Chinese panel and replaced the characters with English.
I haven't tried it on for size yet, but it looks close!
-P
Hi guys,
I heard that recently all the new DST 1062B from the traders have been with upgraded firmware version 2.06.3. The new version has hack-prevention which prevents illegal firmware update as we did for ver 2.06.2.
Although firmware upgrading with hacked fimware image by USB is not allowed anymore, , I guess by JTAG we still can backup the image and then change to hacked version, if CPLD and FPGA design are not changed from v2.06.2 to v2.06.3. Has anyone tried and confirmed this? Also kindly correct me if I'm wrong.
Thanks!
The Photoshop file is about 50MB if you want to play with it PM me your email address and I'll send it to you.I want to. ;D
Hi guys,
I heard that recently all the new DST 1062B from the traders have been with upgraded firmware version 2.06.3. The new version has hack-prevention which prevents illegal firmware update as we did for ver 2.06.2.
Although firmware upgrading with hacked fimware image by USB is not allowed anymore, , I guess by JTAG we still can backup the image and then change to hacked version, if CPLD and FPGA design are not changed from v2.06.2 to v2.06.3. Has anyone tried and confirmed this? Also kindly correct me if I'm wrong.
Thanks!
if you would spend 10mins to read this thread you will see that:
- yes we know it
- yes it works still over UART
- yes it can work over USB if you read carefully what i wrote
I dont think so, there are 24 pages with 350 answers,
it took me one afternoon to read everything,
result was: I know less than before!
Hi Tinhead,Tinman, have you tried this hack on the DST1062B?
Do you know if the DST1062B has the same components as the DST1102B?
Thanks.
Afaik yes, all Tekway's are equal inside within model series:
DST1062B=DST1102B=DST1202B
DST4062B=DST4102B
DST3022B=DST3042B
The DST3xxxB are probably like DST4000B, but without SRAM soldered and with different FPGA config applied.
The DST4xxxB are a bit different then DST1xxxB (layout and XO), and of course FPGA config didn't match.
So as already said, hacks within model series are possible, but not accross.
Regards the DST1062B hack, it has been tested and confirmed as working by someone else.
On my DST1102B i can switch firmwares between 60-100-200MHz, there are of course measurable differences,
see attached picture (db vs MHz on screen)
Tekway seems to be broad-minded, the -3db bandwidth is always higher
than the model bandwidth (R&S SMY -> DSO ->T 50Ohm terminated)
>>> I should have read the thread more carefully!
I dont think so, there are 24 pages with 350 answers,
it took me one afternoon to read everything,
result was: I know less than before!
(because 95% of the thread is bla-bla-bla...)
Hi Tinhead,
In the plot Frequency/dB that you did with DST1202B fw in your DST1102B Hardware. Did you change the channel amp resistors etc for this plot/trace? I note that with DST1102B fw it is 0dB at 100MHz. If components were not changed, what is the plot/trace like with these changed.
Thanks for your help.
Please zip it and replace the attached, it is slowing down this page ...Edit: Sorry … Corrected.
>>> I should have read the thread more carefully!
I dont think so, there are 24 pages with 350 answers,
it took me one afternoon to read everything,
result was: I know less than before!
(because 95% of the thread is bla-bla-bla...)
I found this page for Hantek Scopes:
http://www.socratesblog.eu/?p=174 (http://www.socratesblog.eu/?p=174)
maybe it helps a little bit.
Hi Tinhead,
In the plot Frequency/dB that you did with DST1202B fw in your DST1102B Hardware. Did you change the channel amp resistors etc for this plot/trace? I note that with DST1102B fw it is 0dB at 100MHz. If components were not changed, what is the plot/trace like with these changed.
Thanks for your help.
this plot was created on very early 100MHz Tekway hw revision, where some parts are like in currenty 200MHz model
and some ~ like in 100MHz model. I should probably create a "proper" one from each model (current hw revision) hacked/not hacked.
In principle as already mentioned it will be a bit worse if you hack 60MHz to 200MHz bw, and almost equal (to my old plot)
if you hack 100MHz model.
For sure, if you change the few resistors it will looks like on original 200MHz model (current hw revision) - see attached
- sweep from HP8594E , 0-400 MHz in 50 ms. Channel 1 is connected with a known good LMR-195 N-to-BNC cable
with a 50-ohm terminator on the scope end. The knee occurs at about 2 ms = 400MHz*27ms/50ms=216 MHz, -3db point is about 266 MHz.
Hi Tinhead,
In the plot Frequency/dB that you did with DST1202B fw in your DST1102B Hardware. Did you change the channel amp resistors etc for this plot/trace? I note that with DST1102B fw it is 0dB at 100MHz. If components were not changed, what is the plot/trace like with these changed.
Thanks for your help.
this plot was created on very early 100MHz Tekway hw revision, where some parts are like in currenty 200MHz model
and some ~ like in 100MHz model. I should probably create a "proper" one from each model (current hw revision) hacked/not hacked.
In principle as already mentioned it will be a bit worse if you hack 60MHz to 200MHz bw, and almost equal (to my old plot)
if you hack 100MHz model.
For sure, if you change the few resistors it will looks like on original 200MHz model (current hw revision) - see attached
- sweep from HP8594E , 0-400 MHz in 50 ms. Channel 1 is connected with a known good LMR-195 N-to-BNC cable
with a 50-ohm terminator on the scope end. The knee occurs at about 2 ms = 400MHz*27ms/50ms=216 MHz, -3db point is about 266 MHz.
Am I correct in saying you meant "The knee occurs at 27ms" and not 2ms? 400MHz x (27ms/50ms) = 216MHz. The step at the right of the screen (13.5 divisions from the left) looks to be the point where the sweep ends (400MHz) and starts (0MHz) again. Do you know what the spike is that is at around 4 divisions from the left, looks to me as if something is wrong like a BNC connector problem? There is also a step at around 3.5 divisions from the left, should there be a step?
But all is ok if the -3dB point is 266MHz. I've never measured it but I wonder what it would be when a 200MHz probe is connected and used. That would make it worse. I take it that your test was without a probe, with the 50ohm terminator at the oscilloscope BNC connector.
Later I may change the resistors after I have my Tekway DST1102B running a English UI. Am I correct in saying that if you don't change the resistors (and adjust the compensation etc). And run it at 200MHz. Then you are better to get the Tekway 100MHz and not a 60MHz oscilloscope to convert/hack?
Yes, traces for not hacked and hacked for each model would be interesting and would show a lot on what performance to expect.
Thanks for your help.
no idea where the spike was coming from, not really important.
Do you know what the spike is that is at around 4 divisions from the left, looks to me as if something is wrong like a BNC connector problem? There is also a step at around 3.5 divisions from the left, should there be a step?It's from normal tracking generator function, switching of RF circuits inside the tracking generator prior to the sweep. It's in the "dead period" during sweep setup, so it's irrelevant.
Do you know what the spike is that is at around 4 divisions from the left, looks to me as if something is wrong like a BNC connector problem? There is also a step at around 3.5 divisions from the left, should there be a step?It's from normal tracking generator function, switching of RF circuits inside the tracking generator prior to the sweep. It's in the "dead period" during sweep setup, so it's irrelevant.
no idea where the spike was coming from, not really important.
looks like a singal bounce to me, no big deal for the test.
0MHz is at the left of the screen. 400MHz is at around 13.5 divisions from the left. That makes the step and spike at around 3.5 and 4 divisions from the left, somewhere between 0MHz and 400MHz. Maybe around 3.75 divisions x(400MHz/13.5) = 111MHz. That's not during sweep setup but is during a sweep at around 111MHz.
0MHz is at the left of the screen. 400MHz is at around 13.5 divisions from the left. That makes the step and spike at around 3.5 and 4 divisions from the left, somewhere between 0MHz and 400MHz. Maybe around 3.75 divisions x(400MHz/13.5) = 111MHz. That's not during sweep setup but is during a sweep at around 111MHz.
no, check the picture, the spike was on 0MHz
Same but now connection is HP8567B, same cable, terminator (tektronix), 10dB suhner attenuator, scope BNC.Probably reflections causing trouble. A high-impedance input is not a nice resistive circuit like a low-impedance transmission line, which is why all high bandwidth scopes have 50 ohm inputs. It's actually standard practice for scope bandwidth testing to use as much attenuation as possible (limited by the generator's output power), to eliminate exactly this problem.
(I think attenuator reduce scope input reactance bad effects littlebit?? (less "ringing")
Same but now connection is HP8567B, same cable, terminator (tektronix), 10dB suhner attenuator, scope BNC.Probably reflections causing trouble. A high-impedance input is not a nice resistive circuit like a low-impedance transmission line, which is why all high bandwidth scopes have 50 ohm inputs. It's actually standard practice for scope bandwidth testing to use as much attenuation as possible (limited by the generator's output power), to eliminate exactly this problem.
(I think attenuator reduce scope input reactance bad effects littlebit?? (less "ringing")
I draw my front panel to fit the real oscilloscope.
For this had to completely disassemble the device.
Slightly changed design. Design Tekway I don't like.
In the tekway.zip - two good quality file (*.PDF).
I have just received my Tekway oscilloscope. It is:
Model: dst1102b
Soft version: 2.05.0 (100305.0)
Hardware version: 0x555583e8
I've purchased a USB UART RS232 3.3V TTL board to enable me to change the Menu Display to English.
On reading the instructions again, it said that there was a prehacked version for firmware versions before 2.6.xx.
Are the prehacked versions upgrades still available. Would like to make it a 100MHz or 200MHz oscilloscope with English Menu Display.
I also can't find a USB driver to run TTScop program via USB from my Laptop computer. Any idea where I can download this driver? I have Windows 7 64 bit.
BTW if someone have Tektronix "input normalizer" (small box with BNC connectors) it is useful tool (it need be just made for this capacitance value what is scope input)... but today can not find very easy.
BTW if someone have Tektronix "input normalizer" (small box with BNC connectors) it is useful tool (it need be just made for this capacitance value what is scope input)... but today can not find very easy.
It's just an adjustable capacitor in a box. A 10:1 probe accomplishes exactly the same: making sure the capacitance of all channels is the same so you can swap probes without checking compensation each time. Just compensate the probe to one channel, and adjust the other channels so the signal looks the same. The actual capacitance value doesn't really matter as long as it's within the compensation range of your probes. On scopes were you can adjust the input capacitance (which does not include the Tekway/Hantek scopes, as far as I know)
Really? But why they sell these calibration fixtures for every different scope input capacitances seoarately.To be more accurate, it's a fixed cap with a smaller trimmer cap in parallel (18pF // 2-8pF for the 20pF model according to Håkan). There is also a 1Mohm resistor in parallel (so it forms a 1:1 compensated voltage divider if the scope's input capacitance matches the normalizer). They need different ones because you would need a huge adjustment range (=bad resolution) to cover 12pF-47pF or so.
If it is adjusted capacitance how you can calibrate with it becouse you never know if capacitance is right.Just like every other calibration, by comparing it to a more accurate source (at some point they probably use a capacitance meter). Not sure what the factory calibration procedure was. But I don't see the point about caring about input capacitance, as long as the channels match, everything should be fine. And you can't adjust it on (most) modern scopes anyway.
Also in tektronix service/calibration manuals ask put this "normalizer" to scope input (and also extremely fast rising pulse generator) but never it tell that adjust this box capacitance.That would be the service manual for the normalizer, if such a thing exists (it was designed for internal use, so I'm not sure how well it was documented).
This box can use in calibration routines for adjusting device under calibration! If you adjust tools for calibration what you then calibrate?That's the whole traceability chain of calibration, all the way to the national standards lab. A 3.5/4.5 digit DMM is calibrated by a DMM calibration system, which may be calibrated by a reference DMM, which is calibrated by a voltage and resistor transfer standard, which is calibrated to a Josephson standard, which is a fundamental physical standard which defines the volt. Same for time/frequency, which is traced to a cesium clock. You can derive capacitance from those.
After searching through some data this is the best info you will find. Straight from the horses mouth........so to speak. Both the author of this procedure and the gentleman who inserted it into the microfiche files worked at Tek during the 60's and I am just the means by which it made its way to the digital realm.
If readjustment should be necessary, the internal resistor should first be measured to be sure it is in tolerance. Then the internal variable capacitor may be adjusted to produce a square—cornered, flat-topped response to a square-wave signal on an oscilloscope it is designed to be used with, in the same way as described in the instructions for adjusting scope input capacitance. The response of the scope to square waves should first be known to be normal, and the input capacitance to the scope should be known to be within about five per cent of its nominal value at the attenuator setting used. It is normal for input capacitance to vary slightly from one setting to the next to correspond with slight variations of input resistance. A Tektronix type 130L-C Meter may be used to measure the scope input capacitance. Measurement should be made while the scope is operating. When using the Type 130, to avoid a small possibility of a measurement error due to over driving the input, it is a good idea to use an attenuator setting that corresponds to a deflection factor of about 1 volt per division.
Written by: Leon Orchard
PE/Elec Evaluation
Inserted by: John Mulvey
Tektronix 3-1-67
btw, i did said "manafacturer is installing by defualt 2.6.3 (110225.0) now",
this is not yet bug-free firmware, it is still in principle the same as 2.06.3 (110118.0).
Hanek did changed the PCB revision, so small firmware update was necessary, therefore revision 2.6.3 (110225.0).
It can be downloaded from Hantek website.
No idea if Tekway changed the hardware too, so therefore there is not new firmware on Tekway website.
There are no details on hw modification, we have to wait until someone bought a Hantek with new hw version.
They just started the production, so probably few old hardware revision models still available.
Even if Hantek said "minor modifications only" i can tell you already that
display init is different (same display but connected a bit different),
buzzer driver has been changed (connected to different port - probably pin swap with display),
some FPGA design changes (only for new hw revisions).
The firmware update is of course checking the hw revision, so it will not "destroy" old models
(and will not update buzzer, display and FPGA).
Most interessting thing during hw revision check is the information
which will be read by the "readHWVersion" from EEPROM:
- PCB revision
- LCD revision
- TOUCH revision
- FRONT PANEL revision
- USB revision
- NET revision
PCB and DISPLAY are clear, probably some routing changes to support new functions, NET is know, that's the LAN addon,
USB revision (probably) for the planned SCPI support, TOUCH - yeah, we know there will be touch in the future,
and FRONT PANEL - right, Hantek have on the front panel preparation for DB25 plug - probably LA functionality in the future.
I think i will order a new hw revision and check what inside, however not now - i will wait until the Hantek's LAN addon is ready.
from china
Yes... right. And for me it did not with with the ..(1).up in the end of the filename. Checking this on the console (UART) showed the error "... unexpected character '(' "
;) You need to remove the '(1)' from filename so that ist looks like all update files. And - of course you need to copy back the language files...
One of these ching chong language files contained in the hantek version must be corrupt. The system crashed when I tried to switch language thru one of these funny character settings (don't know which one) ....yep,indeed (that's why deleted my posting few sec. ago ...)
So here is an update file that contains Chinese, English, French and German and works fine for me.
And there is on additional (empty) file in the update file set called 'special'. This one is unique to Tekway update set. Anybody any idea what this means?
from china
dst1kb_2.06.3_1062ridoflim(110315.1).up - this is somehow broken or template for upcoming firmware 2.6.3_110315.1
wjb444 , any idea for what this file is ? (i see what inside, seems to be like fw template only).
Is the clue in the filename ?
dst1kb_2.06.3_1062ridoflim(110315.1).up
rid of limits ?
New design of my Chinese Tekway DST1102B.
(http://img97.imageshack.us/img97/2131/newtekway.jpg) (http://img97.imageshack.us/i/newtekway.jpg/)
(http://img14.imageshack.us/img14/4323/newtekway2.jpg) (http://img14.imageshack.us/i/newtekway2.jpg/)
(http://img821.imageshack.us/img821/4270/newtekway1.jpg) (http://img821.imageshack.us/i/newtekway1.jpg/)
Your front panels look great.Thank you!
Is it possible for you to produce a PDF of the correct size for your origional design. How did you do the cut outs?I have long picked up material for printing. Watched the film and paper. Stopped on paper density 125.
I have not been able to get Windows 7 to install/update the driver that comes with TTScope in the Driver folder. I've downloaded TTScope from both Tekway and Hentek but the driver will not install in Windows 7. Looks to me as if a different driver is required for windows 7. A search has not found a suitable driver. Has anyone a solution for this problem,
Thanks all.
Both channel get same signal but becouse signal split is not as good as it can be (only things what affect timing is ok).
(same cable lenght and same type of cable so trawel time is enough same.)
Both channel get same signal but becouse signal split is not as good as it can be (only things what affect timing is ok).
(same cable lenght and same type of cable so trawel time is enough same.)
If you swap the signal cables between channels does it change?
If you swap the signal cables between channels does it change?
it didn't matter, ch2 is always 1ns behind ch1.
This is actually software error, my DSO (cold) is having 200ps skew time between channels, after warm-up 1ns.
Of course ALT trigger works without skew time, but is not having avg. and long mem mode, so not really a work around.
Even with ext trigger no difference, ext/5 even worse because of bug which has been still not fixed (ext/5 is increasing the 1ns to 3ns or so).
Of course you can create a small loop with RG316 cable for ch1 data and setup trigger on ch2 - hehe, then of course skew time is 0ns.
Skew time is common for many DSOs, but of course every company is reducing it to few ps during manufacturer calibration,
this seems to be not the case anylonger for HanTekway (if i'm not wrong, it wasn't there with very old firmware - but hacked).
If you use scope in high temperature. Room temperature high or if air do not flow very free around scope.
Maybe it is good in this case install small fan inside scope. (no need full speed, you can reduce nominal speed example x0.7 - 0.9 (depends fan type and quality) and you get low noise and it still helps airflow inside scope. It need only small extra amount of air. (example double speed if compare natural free air flow and exance rate) In this case I recommend fan take outside air and flow is to inside. In this case you can put small filter before fan so all dirty do not free travel to inside. In normal 22Celsius room temp some components work quite high temp. Clearly over 70C case temperature. It is not good to go any more high. They may last but maybe fail rate start grow.
... are choking to death.
actually all components are still within specs, but a slow running fan will of course reduce the potential stress.
If you have good quality fan you can use temp / speed control, if you use a cheap one it is enough to replace the 7812
on power board by 7805 (and run a 12V fan with 5V).
Does anybody have the details of the fan (size ?) and are there any pictures of the mod ?
What about using a filter and running the fan to suck the air in ?
The only thing that I've noticed that I don't like so far is the max 5V/div. Why not 10/dev...at least that way I could work on a 240V system without needing to buy a 100x probe...
Thank you for the response, I certainly appreciate and I should have been more specific that I meant AC systems.
240VAC with 50v/div doesn't fit with the default setup (unlike the Rigol which will display 10V/div, this was a big issue for us when we bought a LeCroy WaveAce as a second scope in my office and it only supported 5V/div max)
680Vpk-pk/50V = 14 divisions minimum meaning that you would need 10V/div and use 7 of the eight available on the screen to display the waveform.
Finally got my DST1062B from taobao. Easily upgraded it to DST1202. Dont run any benchmark tests on the edge of the bandwidth. There are only 60MHz probes out of the box, so I need to buy another to take appropriate tests. Everything is great! 8) , but I cant connect my oscilloscope to PC via usb. I'm using TTScope 2.0.0.4 software that i've downloaded from Tekway official site but it doesn't work :'( . And I cant get svg data to my USB flash greater than 40k points >:(, I want to get 512k and 1M points!
Thanks a lot to all forum members in this topic, especially tinhead.
use the software from Hantek website or chinese Tekway website .. there is 2.0.5 too, http://www.tekwayins.com/pic/TTScope.rar (http://www.tekwayins.com/pic/TTScope.rar)
Software is works but I still can't get svg data greater than 40k points. In this case PC software is useless for me. Can you get 512k or 1M points out of your oscilloscope?
Software is works but I still can't get svg data greater than 40k points. In this case PC software is useless for me. Can you get 512k or 1M points out of your oscilloscope?
with firmware version 2.6.1 the 1M data export is working, with other versions not. It has been confirmed as bug and it will be fixed soon.
mine works to 512k, but not 1M.
with firmware version 2.6.1 the 1M data export is working, with other versions not. It has been confirmed as bug and it will be fixed soon.
just to find a PCB I can't remember having seen in this thread so far (see attachment)
There is a footprint for a Ethernet jack, for speaker and microphone jack and finally for a micro-SD!
I have not yet tried to "unlock" 200 MHz operation, just wanted to get a quick response on the PCB shot.
I must be out of my mind for doing this, but
I plugged in a USB Flash Drive in the retrofitted USB Host connector:
"usbctl: zombie --> [reset] --> default. Device in default state."
So, no luck - but the good news: Everything else still works! ;-)
Next, instead of measuring some test-signals:
The 28-pin footprint shown in P1170503 is connected to the "PHONE1" jack footprint. After some investigation in the Mini2440 schematics (http://www.friendlyarm.net/dl.php?file=mini2440_schematic.zip (http://www.friendlyarm.net/dl.php?file=mini2440_schematic.zip)) it is for 100% sure that this can be used to retrofit a UDA1340: http://www.datasheetcatalog.org/datasheet/philips/UDA1340.pdf (http://www.datasheetcatalog.org/datasheet/philips/UDA1340.pdf)
Looking at the SDIO Pinout I am sure we just have to find the right SD-slot. Unfortunately, the buzzer right in front blocks changing the SD-card, so I guess I will go for some flat ribbon cable... Only thing missing could be the missing pullups.
I still can't find a way to see how a Davicom DM9000 or another Ethernet-PHY could be attached to the board to make use of the ethernet-jack. So to make a sophisticated guess I say the ethernet-part is implemented in the FPGA I can't identify due to its heatsink...
Hi!
No luck with the micro-SD... Soldered a flat ribbon cable to the footprints and to a micro-SD slot. No matter if I insert the start before power up or after powering up - nothing happens. The resistors on the bottom side of the pcb are fine - so I guess software is not capable?
BR
Robert
it works very simple - these 3 input selectors (4053 pin 9,10,11) are connected via 10k resistor (near usb client jack) to VUSB, cap to GND (giving some delay) and missing resistor to unknown GPIO port.Yes, this is exactly what I've said and showed in the picture.
This missing resistor (that's where you soldered the 2.2k) is used (i gues) only if the firmware is forced switching the USB client off and USB Host2 on (no matter if there is VUSB on USB client).
Without this resistor (there is currently no support in firmware for this anyway - btw, what fw version is istalled on your DSO?) this circuit still works, but only via VUSB detection.
By default 4052 is selecting X inputs, so the second host is enabled if no VUSB. If VUSB exists, 4052 is switching USB signals to USB client and the USB_Enable (actually another one GPIO port)
to the 1.5k resistor (which is soldered near USB client jack and routed to 3Y1). This signal (actually the 1.5 resistor between D- and the GPIO port) is necessary to allow proper USB client functionality.
The 3rd resistor between 3Y1 and 3Z is probably for hysteresis.
To monitor GPIO port status there are 3 ways
- boundary scan over JTAG (which is always the best way)
BSDL files are available on Samsung website, but if you have no hardware and knowledge how to use it, then you lost.
- via test app loaded instead of linux.
There are many such test applications for S3C2440 to show the GPIO port status (some over USB which didn't make sense here, others via shell/uart),
but you have to compile them and load to NAND or even better to memory over JTAG.
- via what already on the DSO
Normally you can read GPIO under linux, you will need an GPIO driver and application calling such driver.
Luckily there is such driver availble on HanTekway DSOs - /dso/driver/dso-iobank.ko and there is application calling this driver /dso/app/setio
The "setio" is being used by default like that /dso/app/setio g12 o 1 (where G12 is GPG12 port/pin, "o" is output and "1" the actual data which will be written to that port/pin).
However this app can be user like /dso/app/setio g12 i to display the port value.
So all you need is to connect via UART to the Linux shell, kill the dso.exe by ctrl+c, to connect 3.3V via 2k to the unknown GPIO pin (i mean the one where you soldered 2.2k resistor)
and monitor what changed ... lot of ports/pins to monitor, but you can write a script to loop until change and display what changed.
I don't agree on this. The missing resistor connects to an INPUT, this is where the USB-driver should look at to reconfigure the USB core on the S3C2440. Working against the 4.7k/10k voltage divider of VBUS of USB A jack would work somehow, but would be a design flaw. This is supported by measurements I did when the DSO was running: you get ~0V when no USB-A is in (10k to GND) on BOTH sides (so not even a pullup) and ~3.3V when connected (voltage divider to VBUS) on BOTH sides (so again no pulldown). The pin is not driven at all - this will be the pin to consider for reconfiguring the S3C2440. By the way, I was looking at the Mini2440 - I saw somebody asking about the SEL_USBPAD bit (http://www.armkits.com/download/s3c2440.pdf (http://www.armkits.com/download/s3c2440.pdf)) but I doubt this is enough for reconfiguration. Never saw somebody telling it actually works. To be honest, it is of course more tempting to stick in a small 4-port-hub and avoid the hassle.
I don't think so. To do this, it would have to have a connection to Sx. This is not the case. I guess 3Z is connected to the pin controlling the 1.5k pullup in the original design. By soldering a zero-ohm resistor to this location you ALWAYS have the pullup-control connected to the USB A jack. Using the actual configuration, its only connected if VBUS is applied. I guess 3Y0 (default) is open (so the 1.5k is flowing on one side in default state).
I will do this when I have time. Have a Segger J-Link, so this is not a problem at all. More of a problem is that we don't have 2.00mm headers on stock in the lab. I don't like to solder plain cable to this socket. I think I will tackle this when upgrading the analog parts, because I don't want to srew/unscrew the frontpanel frequently (the threads in the plastic get stale way to fast even if you're cautious).j-link works, but don't forget to save NAND dump with OOB blocks in case you wish to restore it some day.
Quite probable I will try to get some WiFi-stick running with the DSO to allow ssh (dropbear?) access to avoid the hassle of designing an addon-card we don't have to connections for. I think it takes a broken unit to unsolder the BGAs and "beep" all connections. - And I prefer it won't be mine... ;-)
So, does anybody has some kind of toolchain ready? Some kind of BSP available? What about triggering Hantek/Tekway or - if they are not nice, which I don't think - let FSF making them releasing the relevant sources?
just buy H-JTAG and USB UART converter , but the USB UART converter not workI broke into the brains oscilloscope through such devays:
oscilloscope through such devays:how?
My DSO firmware version is 2.6.3,
by measurement,the last pin of UART is 3.3v on the picture,not 0v. if USB UART converter 's "gnd "to the last pin of UART in DSO , can't this instrument be damaged ? now rx0 : 0.1v rx1: 0v
just buy H-JTAG and USB UART converter , but the USB UART converter not work,
I felt very strange: fw2dump.zip can dump 3 files(boot.bin kernel.bin root.bin ),but fw_backupV3.zip can't.
If only use H-JTAG, What should I do? How do you define the offset of the 3 file .with H-JTAG, or actually H-Flasher software you can backup the whole NAND or restore it. If you backup via h-jtag/h-flasher you have to ensure that OOB blocks are also saved,
How do I downgrade to 2.6.2 or lower?
How did the "bin" file compile or decompile?
What's changed, Where's changed, Every version firmware?ohh, this is very bad question, actually for 2.6.3 there is description of changes on chinese Tekway website, as you from china it will be easy for you to read it.
And finally analyze this, What will I need to access and read for this course?
I'm not concerned about Linux version. It is embedded linux and for user it is Oscilloscope (not linux entertainment machine). User do not need even know about system behind display and knobs. It works and linux version do not make any problem afaik. Of course if people want make some modifications and if he want make it as game box or tv or music box he need use 2.6.13 compaible things.
But then I remember - if I think this quality... it is <1k$ scope and in this class it is really unexpected good.
Building guality (main board) seems littlebit better now in these new HW. (I have look only some old and new units so I can tell only these units what I have checked)
I wasn't lucky to get a "new" hardware, but I was lucky enough to get Tekway's 1.00.3 mainboard with 200 MHz ready out of the box. I can see all input stages resistors are 200 MHz version, so, seems that no soldering needed at all.aha, so check the i2c.log, maybe it is rebranded 200MHz model.
The thing I definitely don't lake at all, is how it all soldered. I thinks kids in kindergarten do better! Resistors and capacitors sometimes are more than a half case out of there place, flux is everywhere and I wasn't able to wash it out with isopropyl alcohol and even with FluxOff!take a picture of that ...
One of 4 ADC radiators is missing.that's ugly
For now, I like to know is at a good idea to apply Cramolin FluxOff to wash PCBs and... avoid using PVC and polysterene. ... hmm, i would use pure Isopropanol (99.7%).
where SN is stored?in the EEPROM, located between display connector and front USB.
I think this caused by product line wasn't adjust properly, and QA not good too.
^^ maybe that's why this one was suposed to be for chinese market.Nop. Pioneer told me it's original English, besides there were some 5062 from Pioneer with English face for another guy from Russia (not Igor).
BTW, I know there is a shift between waveforms on first and second channel when connected to same source on old hardware version. But I was unable to reproduce that, what I'm doing wrong and how can I see that to handle such a thing in feature?
Mine is 2.06.3 (110118.0) which isn't latest. I'm asking because if I'm using both channels, basically I'm doing that to monitor two signal synchronously to see what's going on when one changes with the other one. So, if there is a shift, that might be a little bit tricky. So, if this is a hardware bug, it's not a 2 channel oscilloscope, it's a couple of scopes in one case. Having two channels became useless if they are not showing _exactly_same_time_ signal. You will not be able to see a hysteresis, for example. IMHO.BTW, I know there is a shift between waveforms on first and second channel when connected to same source on old hardware version. But I was unable to reproduce that, what I'm doing wrong and how can I see that to handle such a thing in feature?
depends, it can be that your unit have different firmware, or due some flying components is doing the job better (haha, not a good joke),
or just cable length caused.
Mine is 2.06.3 (110118.0) which isn't latest. I'm asking because if I'm using both channels, basically I'm doing that to monitor two signal synchronously to see what's going on when one changes with the other one. So, if there is a shift, that might be a little bit tricky. So, if this is a hardware bug, it's not a 2 channel oscilloscope, it's a couple of scopes in one case. Having two channels became useless if they are not showing _exactly_same_time_ signal. You will not be able to see a hysteresis, for example. IMHO.
Source 60M 4nsWhat's your fw version?
Not the same as the sampling depth, the waveform will be inconsistent it? :(
I thought why not to replace electrolytic capacitors as they seem to me to be low quality.
To start with PSU: there are:
1. 100 uF x 400 V (150C)
2. 47 uF x 35 V
3. 22 uF x 16 V
4. 1000 uF x 16 V (4 pc)
5. 47 uF x 25 V
6. 1000 uF x 25 V
7. 100 uF x 35 V
I would like to know is there is a way to improve PSU by increasing capacitance or voltages of this caps? Should I use low impedance/ESR caps?
Besides, there are 6 1000 uF x 10 V and 8 220 uF x 16 V and one 470 uF x 25 on mainboard, any suggestions what to with them?
Huh, this device looks like a DIY kit :) But we can squeeze more out of it, I think. Unfortunately, I'm not a PSU designer at all. and when it comes to switching PSUs - hands up.
cu -l /dev/ttyUSB0 -s 115200
and to get "almost all" backup typetar -cvpf /mnt/root_backup_originall.tar / --exclude "mnt/*" --exclude "proc/*"
and don't forget to umount /mnt before you rip out thumbdrive.(http://www.e-priest.ru/projects/electronics/Hantek_DSO_5xx2/p1020441_pw.jpg) (http://www.e-priest.ru/projects/electronics/Hantek_DSO_5xx2/p1020444_pw.jpg) |
(http://www.e-priest.ru/projects/electronics/Hantek_DSO_5xx2/p1020446_pw.jpg) (http://www.e-priest.ru/projects/electronics/Hantek_DSO_5xx2/p1020447_pw.jpg) |
(http://www.e-priest.ru/projects/electronics/Hantek_DSO_5xx2/p1020449_pw.jpg) (http://www.e-priest.ru/projects/electronics/Hantek_DSO_5xx2/p1020450_pw.jpg) |
(http://www.e-priest.ru/projects/electronics/Hantek_DSO_5xx2/p1020452_pw.jpg) (http://www.e-priest.ru/projects/electronics/Hantek_DSO_5xx2/p1020455_pw.jpg) |
(http://www.e-priest.ru/projects/electronics/Hantek_DSO_5xx2/p1020457_pw.jpg) (http://www.e-priest.ru/projects/electronics/Hantek_DSO_5xx2/p1020458_pw.jpg) |
(http://www.e-priest.ru/projects/electronics/Hantek_DSO_5xx2/p1020461_pw.jpg) (http://www.e-priest.ru/projects/electronics/Hantek_DSO_5xx2/p1020463_pw.jpg) |
(http://www.e-priest.ru/projects/electronics/Hantek_DSO_5xx2/p1020464_pw.jpg) (http://www.e-priest.ru/projects/electronics/Hantek_DSO_5xx2/p1020466_pw.jpg) |
2 tinhead: do you have any sujestions about "10USD total" PSU fixup?
So, what part quality may be different? Solid devices should be same, any idea?
I'm I right thinking that 3.3V PSU ripple is what we see on idle/connected to ground probe?
Modification of own DSO not suppose to be a crime, I think.
But tinhead made recipe public available. Is that a crime?
For now, my questions are:
1. what fs is used for .bin files?
2. what database language files stored in?
There are two versions of YAFFS: yaffs and yaffs2, so what is the used one?
Hi everybody,
Thanks for you for helping me choose Hantek DSO1502B which has arrived yesterday. I'm very satisfied with it. Today I had a look inside and found that it has new hardware revision PCB. Is it possible to "upgrade" it to 200Mhz? What about resistors? Thank you in advance for advise.
Regards,
Paul
Thanks tinhead for the prompt answer. I'll try to do it over uart. Is it possible to determine what version do I have? The resistors values are different compare to what you published for Tekway PCB. I'm not going to replace them, just curious.
e-priest:I've bought it from AliExpress.com, search for "Hantek DSO-5102B".
Can you send me contact info on your Hantek DSO5102B supplier please...?
Thanks tinhead for the prompt answer. I'll try to do it over uart. Is it possible to determine what version do I have? The resistors values are different compare to what you published for Tekway PCB. I'm not going to replace them, just curious.And it will be nice if you post a photo of power supply to.
How are your progressing on your mod(s) ?Well, my device OK and works fine, but I'm not going to mod it until I at least I will be able to measure the difference. I'm going to build 350 ps rise edge generator. I crack opened it, you can find some photos on pages above, but nothing special, same 1.00.3 Tekway board inside. Dirty soldering, tons of flux.. but still not bad and much better than expected from 6 hundred backs Chinese toy. It's definitely can be hacked, but I have some unanswered questions. Seems that prices go down.
Please advise...
Thanks!
Doug
What Volts/Div:Coarse/Fine does in channel menu? A can't figure you what changes between Coarse and Fine.
Normal steps are example 1 - 2 - 5V / divGot it, thank you.
Select Fine.
Now turn channel voltage adjust knob. (Vertical: Volts/div)
It changes example 1.02V - 1.04V - 1.06V - 1.08V - 1.10V / div
(steps are different in different voltage "band") example if go under 1V next is 990mV/div etc.)
If Tekway disable the UART port,What can I do?My dso 's UART not transmit any message.Before this,I let after-sales department to handle this so-called update .I don't know is or isn't this(http://www.xici.net/#b1293165/door.asp (http://www.xici.net/#b1293165/door.asp))
How am I to open the UART port? what to writer the vivi.bin or the original bootloader ,I want knoe the specific address or offset ?
Hello tinhead, first of all I want to thank you for your time and dedication to this subject, this thread definitively made me decide which DSO to get, my DST1102B is on its way bought from Mr. Pioneer Huang at Aliexpress.
I'll sure take it apart after a quick DOA check, will post 8MPX pics of the boards. The scope will arrive in chinese and I will change it to engish, does this will require a complete firmware change or just some setup? AFAIK the latest FW is 2.6.3 right? But at the Tekway homepage theres only 2.5 version. Where can I find the latest english version? Sorry I have not finished reading all the thread since Im currently in a extensive work project that takes almost all of my time.
I cant wait to have my own scope, currently using a Fluke 199 Scopemeter from the company I work for which does not have all the complete DSO functionality (also, the horizontal black line disease, common for this series fluke scopmeters, is stating to appear)
Can it be possible that I get that new redesigned PCB with SD, Ethernet footprints? Or currently its only possible with Hantek DSOs like RobertB's?
Thanks !
tinhead,thank you!
Yes,I do it in accordance with your same step before ask you, press the CTRL+C and Enter many times (in SecureCRT and HyperTerminal ).But am I wrong,is it possible in DNW.exe.
but whatever l tried, wouldn't get any message in windows .
My USB FT232 converter is normal when connection rx to tx itself.
What time to Post your matching supervivi and own compiled vivi ,and the interrelated files of other ways?
In addition, I do not have the qualifications to DIY LAN.
You know (Attempt to disassemble the product can damage it and void your warranty),I don't want to miss the boat 3 years easily.Because JTAG 20 pins not solder.Although I bought the H-JTAG .
If you are interested,I can post my backup files ( boot.bin kernel.bin root.bin )
I often work with short single pulses, so I need to know what the scope is doing if I am to trust what I see on the screen. If I want to look at a repeating waveforms I have several analogue scopes I can use that are much faster to drive. The thing that DSOs do, that beats analogue scopes, is single shot storage of a waveform. There's not a lot of point talking about DSOs for repeating waveforms, that has already been solved. So for this discussion, I always refer to single shot operation.
On my LeCroy there is an info screen, one button, anytime and you see all the channel settings, timebase settings, sample rate and memory acquired at a single glance. It is very clear to me what it is doing, and I know what pulses I can sensibly measure and what is likely to be aliased. By comparison, the Hantek/Tekway design seems to be hiding that information, so I wonder why. Also, they hide the change from Real Time operation to Equivalent Time operation, that is deeply annoying. LeCroy automatically switch to Equivalent Time (they call it RIS, or Repetitive Interleaved Sampling) but it is clearly visible at all times. The operator really <needs> to know when this is happening, otherwise the data on the screen might be totally undersampled and quite untrustworthy.
"actually it is very hard to say what is the real sample rate on these scopes." and "Probably we should ask the original developer"
I agree completely with these comments, but are we never likely to find who it was and ask them...
You said:
"The DSO is using Altera Cyclone II, if you check the specs you will see the amount of internal SRAM is "big" enough for
only one channel 4k sampling"
OK, thanks for that information, I'm not experienced with FPGA so their specs are confusing to me. That would explain the default back to 4k with Autoset. It does change the way the scope must work, there are many compromises compared to my old LeCroy. Even though my 9310 is only 100MS/s, I can trust that what I have on the screen, since I know always what sample rate it being used.
I don't know what SoC/UI means.
In the LeCroy, the sample rate changes are completely logical and in keeping with the published limitations and specs. The Info screen always tells you precisely what is happening. In my LeCroy, the scope acquisition memory defaults to 10k, but you can select 50k. Using 50k increases the processing required to display the waveforms, so drops the update rate, but the choice is yours. As you increase the timebase setting, the scope it will automatically change to RIS (Repetitive Interleaved Sampling) or Equivalent Time automatically, but it clearly tells you this is the case, so you can't be easily fooled alias.
You said:Me too, there is no difference between single and repetitive run in the logic, except the fact that the memory will be purged and filled again and again and again.
"I said "finally" because in 8ns/4ns/2ns/div the diff is very small and hard to count exactly, but it seems to be
200ps, 100ps and 50ps."
Of course, this is what it would do for repeating waveforms. I was testing it for single shot only. Single shot waveform storage is the banner capability that separates DSOs from analogue scopes, so my focus is on single shot.
You said:
"This is of course with real time mode sampling selected. With equ mode selected and 20ns/div the diff between dots
is 100ps instead of 500ps like in real time mode."
Agreed, but I did all my tests on single shot acquisitions. I have analogue scopes and didn't buy a a digital scope to show easy repetitive waveforms.
This is just result of how they using sin/x interpolation and the way how the DSO is designed."
Clearly the maker must work within the limits of physics and with difficult cost restraints. So, I am not being critical of the makers. But, there is no reason for not letting the user know what the scope is doing. There is still something weird happening with the sample rate getting stuck at 400MS/s for so long. I cannot understand why this should happen. At higher time base settings, the scope appears to use 500MS/s and 1000MS/s sample rate, so it's not like the digitiser can't do it. It's not because of a 4k fast RAM limitation, since at 200nS/div, it samples 1.28k at 400MS/s. It just makes no sense to me. I can't understand why they break the 1-2-5 sequence of sample rate at lower timbase settings and go to 1-2-4. I'm looking to explain why it is like this. I can accept quirks of design, but I like to know <why> it is like that.
You said:
"This is just result of how they using sin/x interpolation and the way how the DSO is designed. "
What? Surely this must be a mistake. I saw nothing in the manual about the scope using sinx/x interpolation between actual data points. I detest sinx/x interpolation. I used to sell LeCroy DSOs many years ago, and I have seen many many comparisons of different digital scopes. I finished that work 8 years ago, so I have not seen the latest HP DSOs. Apparently, they have improved dramatically, but in my past experience, by far the worst alias problems my customers encountered were cases where sinx/x was operating. Linear interpolation is the safest method. As soon as you see the very characteristic alpine looking sharp peaks, you know you have undersampling and need to take care to ensure you aren't looking at alias. Since Hantek/Tekway under the Display menu allows selection of Dots or Vectors, I assumed Vectors meant linear interpolation. We must find some way to be sure about this, it really matters to me.
You said:Physically these dots have to be interpolated dots and not actual sampled points.
"Therefore don't count the dots, they not one per sample and don't compare to other DSOs"
If the dots are not actual sample points, what else could they be? Don't forget, I have always used single shot mode and ensured Real Time mode was operating.
Please don't think I am full of criticism, I'm just trying to understand how this thing works, and whether I can trust its single shot screens. I deal with photomultiplier and gas radiation detectors and fast one-ff pulses matter to me.
As general DSO philosophy, the vital thing is to understand the limitations of the technology so you are not fooled by alias. Aliasing happens all the time, we just don't often realise it. Trusting a DSO screen without questioning is a good way to fool yourself.
Another interesting factor is screen alias. The screen only has a limited number of dots across it, if you squeeze memory down to show the pixels, then data is not being shown and alias can occur. To my best knowledge, Hantek/Tekway at least make an effort to capture spikes that are present in memory and display something on the screen that grabs your attention and makes you zoom for more info. LeCroy have always done this. I believe GW Instek take the trouble also. Many little modern scopes simply ignore the spike in memory and if luck has it fall into the data that is decimated for screen display, then bad luck, you never see it. If you ask a Tek salesman about this, they get excited and say the data isn't lost, it's still in memory. But so what, why would you scroll through anything up to 1 meg of waveform data <every single time> to find something that you don't know is there!!
I have no trouble with instrument and technology limitations. I have no trouble with compromise made for better cost. But if you can't find out what those imitations are, how can you ever know when to be alert for alias? Even a car manual tells you what speeds to use for each gear...
Please keep up the good work, I have very much appreciated your work in informing us all about these scopes. I'm enjoying tinkering with the HAntek/Tekway scope, the screen readability for my older eyes is very nice, I just don't trust it yet and may never fully, unless I get some answers. I have emailed this issue to Hantek, who have sent a polite "gone to engineering evaluation" reply, so I wait with interest. In the mean time, I thought it would be interesting to ask your thoughts on the matter. *smile*
they located in the (shielding) input channel part of the PCB, which you already opened - i can see tme on your pics :)
I tried to find the resistors which determine the lowpass filter value, but I did not find them, I guess they are on the other side and I was lazy to do that.
Something that I noticed is that it gets really hot inside. After 30 minutes of playing with it, when I opened it, all the metal plates were REALLY hot (I dont want to know the ICs). In fact before opening it I noticed a very intense heatwave coming from the top. I installed a 5cmx5cm fan in the place designed for that, and soldered a header in the power supply where it says "fan". Now it runs cool after hours of use. Sure its noisy but if it's a guarantee of a better lifespan i think it's not a big sacrifice, anyway I always have earphones listening some good music ;)right, the most heating comes from PSU, then the input circuit then FPGA and ADC.
UPDATE: NOW HACKED !!!
At first I was afraid but the procedure seemed to be very easy, so i did it. Now I'm happy and grateful for tinhead :)
I also wanted to do something about the PSU's 3.3v but didnt have much caps or regs lying around so I installed 2 extra 220uF Tantalumyou can measure the ripple by yourself :)
caps in the 3.3v output:
Tinhead, do you think the tantalums are helping? Im looking towards fully hack the device including Ethernet, PSU mods, etc.
Something curious is that my DSO had a permanent +20mV offset on CH1, I did not took pictures of the shorted probe showing the offset. After the hack and tantalum caps the problem has dissappeared, I dont know why.
you can measure the ripple by yourself :)
The Ethernet mod, yeah, maybe i should produce some PCBs. Few ppl asked already, it seems that the 6mil is to small for home made PCBs.
Can the scope measure its own ripple by placing the probe in the +3.3v net?
wow 6mil sounds difficult but could be possible, I've done 8mil with a lot of problems, but got good results at last.
Tinhead,You saw that my upload files?Because i didn't have enough power to do that now. Only if i need to enough to know to do it .Can you tell me what the difference is between the received files and your previously files,and reciprocal measures ?(if you can post the better nandflash backup file of dst1602, so much the better.)I only know a little Linux.used all your upgrade applications, always reported error code . I don't know what Tekway did?
BTW ... Loaded TTScope Software from Scope CD ... plugged in USB ... and a bad bong ! Usb Driver failed to load ..... won't attach ... eMail off to Hantek Support just to see what happens ... :( ??? .. :'(
Anyone w/similar USB problem ?
Thanks!
Doug
Tinhead,You saw that my upload files?Because i didn't have enough power to do that now. Only if i need to enough to know to do it .Can you tell me what the difference is between the received files and your previously files,and reciprocal measures ?(if you can post the better nandflash backup file of dst1602, so much the better.)I only know a little Linux.used all your upgrade applications, always reported error code . I don't know what Tekway did?
yes i saw and got it, i will check on weekend (quite busy right now)
Tinhead ...DSO5102B doen support 1M only in one chan mode, so if even this did'nt work then you have an issue with your DSO (if so, tell me fw version)
Removed my new Hantek DSO5102B from shipping container here .... applied power .... the display is quite nice at quick look.
... looking around etc ... I notice Acquire Menu - 1M LongMem is not supported by the model. Is this a SW, HW issue or both ?
Very Interesying Features ;D ... I think I am going to like this
Probably will do Power Supply mods this week ... got the TI PTH04070WAH Chip as sample.
Comments Please ...
Thanks!
Doug
Hi Tinhead.
I've been waiting for the Windows 7 64 bit driver for TTScope. Do you know if this has been released.
Thanks for all the work that you do for us. I also wouldn't have a Tekway 200MHz oscilloscope if it wasn't for you.
RFman.
1: I think this is not a good way of understanding what is happening. Any DSO can under-sample. I don't care who argues, any DSO can alias and show nonsense - I've done it myself and seen it on 1GS/s scopes with 500MHz bandwidth and huge memory that cost $70,000!! I don't wish to sound horrible, but there can no argument about this.
It is a fact of the universe, like the speed of light.
If you sample in anyway, you can get alias.
There are some compromises with the Hantek/Tekway for long memory, but they don't make it clear when and how those compromises happen, an information screen is absolutely necessary!
Basically, I believe that a DSO should work for the user, not against the user. Most Chinese models I have seen don't seem to do this. It is a shame, I have no trouble with cost based limitations to a design. Honest disclosure shows respect for the customer. Would you get into an aeroplane that had "aerobatic" written on it without knowing the exact limits for vertical and inverted acceleration??? *laughs*
Hello, I've been using my DST1102B (my first scope :D) to design a microcontrolled buck converter and everything has been pure sweetness. The only things ths bugs me is when you save to USB, why does it save a .bmp and .gif of the picture? I can do just fine with .gif, Is there any way to make it only save .gif file? Or better ! is there any way to get fast oscillograph screenshots in the PC without using the slow TTScope?
I've found a way to use Tekway's TTScope in windows 7, Just copy and rename:
<Hantek's TTScope Installation Dir>\config\DSO5202B_eng.ini
to
<Tekway's TTScope Installation Dir>\config\DST1202B_eng.ini
This way I can use Tekway's TTScope, but it's still slow :( I suspect the scope sends *.bmp screenshots instead of some type of compressed image. Is there any third party software ?
Hope HanTekWay will eventually go open-source.Why would they do that? What would be the incentive? Most Chinese companies are even more restrictive about documentation and details than companies like Tek and Agilent, and even they have never released the source as far as I know, even when they published full schematics.
I guess that's why they haven't releases the SDK yet - they just don't have all the sources anymore. I saw such a situation once, I was the one who had to develop new software after the previous main developer ... (to be polite) retired and left only binary compiled version to us.
I have no sympathy for companies losing their source code. It is simply gross mismanagement when this happens. Firing people is no excuse for losing assets like source code. In fact, there is no excuse. It is not rocket science keeping track of source code, and the principles aren't new. More like known since 30 or 40 years.
It sounds like they don't do version control either else they would have the archives. The implications are that they can't backtrack and fix bugs properly, hence flaky f/w
Sure version control exists, but nobody really cares about clean programming - time to fix is important as this costs money!
So why chinese company should be different? No reason at all.
Probably another good reason that HanTekway should release the API, they can concentrate on the hardware and let the developer community decide the functionality of the equipment. Both sides win.
full ack, and afaik they got during last days some proposals, up to them to decide. In my opinion is not a shame to let ppl help you,
it is a shame to ignore it.
From 200nS.div up to 8nS/div, the sample rate stays stuck at 800MS/S.
Finally, at the top timebase setting of 4uS per div, (100MHz model limit) the sample rate jumps to 1GS/S.
if you count like that, you should count what behind the menu, the scope is always using this area, menu is only overlay displayed (click F0 to hide it).
Number of sample points = time/div x number of divisions (16 in Hantek/Tekway) / time between sample points (or 1/sample rate)...
What I have found with my Hantek, in single channel 4k memory mode, is this rule is followed at various timebase settings until it reaches 2 uS,
when the sample rate is 100MS/S, and the total memory acquired in each 'sweep' is 3200 points.
See what I mean, (2 uS x 16)/10 nS = 3200 (at 100MS/S, the time between points is 10nS) It doesn't always work out to give 4000.
This is quite normal in all DSOs and just their basic internal mechanics at work.
I'm sure all these modern cheaper DSOs have limitations with memory at fast digitising speed. 4K shows up because it is likely the maximum of fast RAM available in the FPGA chip. We are talking about very fast data, 1GS/S means an 8 bit data word every 1 nanosecond. Light travels 30cm in that time, no RAM in the world can cope with 1 nanosecond write times! All sorts of engineering cleverness is needed to get this to work. But this means memory size limits, you can't use big cheap DRAM, it's not fast enough at all.
What i found is nice feature allowing to extend the analog bw. As already said before these DSOs are using variable gain amplifier inlet me repeat this post. this is interesting stuff and have been in my dream. so tinhead, is that means if the x setting is default to x10, then 400++MHz signal will not be able to be detected? ie low amplifier gain? badly attenuated by firm/software?
the input stage in combination with digital filter to cut the bw...
where x is the digital filter max corner frequency (it will be normally read from model, where for example DST1102B
is setting the x to 10 (x10) = 100MHz. This "tst" file is overwritting (temporairy in the memory, so no change to firmware)
the model based settings, so you can use higher values. Of course the VAG opamp will not allow to have flat frequency
response but you will be able to do e.g. FFT or avg. sampling up to 450MHz.
Everything above 450MHz didn't really matter, the overclocked ADCs can not handle much more.
With such setting ( [filter] 45 ) in the tst file my DSO is allowing to capture 400MHz singnals (with -15db attenuation )
and 300MHz signals (with -9db attenuation).
The best rise time with such mod is about 1.05ns (pulse generator), giving 333MHz bw which seems to be
good but in principle we have still -3db on 220MHz, -6db on 250MHz, -9db 300MHz, -15db 400MHz and falling (instead of digital
filter and vag based brick wall on 300MHz). I did used it for example to control 433MHz carrier signal,
which worked beautiful....
let me repeat this post. this is interesting stuff and have been in my dream. so tinhead, is that means if the x setting is default to x10, then 400++MHz signal will not be able to be detected? ie low amplifier gain? badly attenuated by firm/software?
100Mhz DSO don't have to detect 400Mhz signals :)you are right. but 1Gs/s should be able to detect 400MHz according to Nyquist.
For a full "300 or 400MHz hack" the VAG opamp part of the firmware should to be changed, therefore i will not call it "hack",for me , it is a hack... that not everybody can do. last question pls. by enabling 400MHz "feature" (ie disabling brick wall filter), will the lower frequency <=200MHz distorted, affected, contaminated? (or whatever you want to call it). edit: ok i just read about the why "dso bw limit", is to avoid noise, but how about flatness, is it affected?
it is just a feature.
100Mhz DSO don't have to detect 400Mhz signals :)you are right. but 1Gs/s should be able to detect 400MHz according to Nyquist.
for me , it is a hack... that not everybody can do. last question pls. by enabling 400MHz "feature" (ie disabling brick wall filter), will the lower frequency <=200MHz distorted, affected, contaminated? (or whatever you want to call it). edit: ok i just read about the why "dso bw limit", is to avoid noise, but how about flatness, is it affected?
if the answer is no, then i think this is the most stupidiest effort that the manufacturer did. even if the answer is yes, then they still the same by not giving access to user to enable/disable it. my 2cnts.
If you don't have necessary equipment to measure for example 400MHz signal this solution will help you,yes sure, very sure! it will help alot! -15db is better than nothing. and as you have indicated in earlier post, it did help you.
it is maybe not a every day situation anyway.yes sure it will not be everyday. but could be a saviour on one particular project in a month.
if the answer is no, then i think this is the most stupidiest effort that the manufacturer did. even if the answer is yes, then they still the same by not giving access to user to enable/disable it. my 2cnts.i'm sorry. there was a misunderstanding. i was in emotional state that i thought my dso is the same as the discussed hantek. it turned out they are different. but my previous points still stand.
if the answer is no, then i think this is the most stupidiest effort that the manufacturer did. even if the answer is yes, then they still the same by not giving access to user to enable/disable it. my 2cnts.i'm sorry. there was a misunderstanding. i was in emotional state that i thought my dso is the same as the discussed hantek. it turned out they are different. but my previous points still stand.
edit: tried to find hantek dso user manual in google but unsuccessful. instead i found this thread is mentioned in hackaday (i did search if its mentioned here, but no) http://hackaday.com/2010/11/24/double-the-hertz-double-the-pleasure/ (http://hackaday.com/2010/11/24/double-the-hertz-double-the-pleasure/) i havent read all the lengthty replies there.
different ? now i'm lost :)coz mine is rigol :P i thought they come from the same root. i should have check the feature earlier. thanx i got the manual already. i was searching dst1102b keyword earlier.
different ? now i'm lost :)coz mine is rigol :P i thought they come from the same root.
look at the avatar.
Everything above 450MHz didn't really matter, the overclocked ADCs can not handle much more.
With such setting ( [filter] 45 ) in the tst file my DSO is allowing to capture 400MHz singnals (with -15db attenuation )
and 300MHz signals (with -9db attenuation).
The best rise time with such mod is about 1.05ns (pulse generator), giving 333MHz bw which seems to be
good but in principle we have still -3db on 220MHz, -6db on 250MHz, -9db 300MHz, -15db 400MHz and falling (instead of digital
filter and vag based brick wall on 300MHz).
"Take it apart!" ;)
Tekway DST1062B, PCB Ver1.00.5 2010/11/30...
if you count like that, you should count what behind the menu, the scope is always using this area, menu is only overlay displayed (click F0 to hide it).
Generally spoken this didn't matter because of ADC hold function, the waveform per seconds time (up to 2500 wfrm/s) is describing how fast the data will get collected and processed, the dead time between can be used for whatever (haven't analyzed how this actuall design works) - the DSO can continuously sample until 4k are full or it can sample/hold every 1ns The FPGA can handle both, that's only 8 x 8bit data, refreshed every 125MHz on each ADC where the FPGA can sample i/o with 250MHz.
It reminds me of the old engineer's saying, you can have good, fast, and cheap, pick any two!dso maker (hardware and software) can struggle to maximize and perfect the performance. but later they will charge exponential. or they (engineers and management) can ignore it, and let it flow/blend/balance with the market (profit vs cost). its called business, a "contaminated engineering", imho.
Not sure what you are trying to say here? The waveform update rate isn't very important to digital scopes, despite the fact that some mainstream DSO makers try to get you to think it is the only number that matters - it is in their interest to promote their banner spec and get you to ignore so many important things that affect the usefulness of a DSO. .....
I think they should be called something else, because they do not work like an analogue scope, but I also realise that this is hoping for too much, the name DSO - we are stuck with it now. ......
As another thought about update rate... what is the response time of the LCD display, and how fast are its pixels updated? I don't have a model number or spec on the display LCD used int he Hantek/Tekway DSOs. If it is typically around 5mS pixel response time, the fastest update rate that can be seen is limited by the LCD response rate. 1/5mS =2000 changes black to white per second = 1000 hertz of a waveform. So, the fastest that any pixel can turn on and off, is 1000 times per second. It makes the very high waveform update rates that Tek and HP have been quoting pretty pointless I think.
Additionally, the majority of debugging does not involve hunting for gitches; you're more often looking at highly reproducible, deterministic behavior. In this case as well as the intermittent events, great triggering and deep memory are a boon. That's why those old Lecroy scopes are such a great deal. They've got fantastic triggering capability and (even by today's standards) incredibly deep memory with segmentation ability, and are typically much cheaper than similar bandwidth/sample rate HP and Tek scopes with 1/100 the memory, no segments, and less powerful math and triggering. (According to TeraPeak, last 90 days Ebay final sale prices of 2 working LeCroy 9354 scopes was $300 and $500; and a tek TDS754A was $2600).
good one, go home and sleep a bit :)Done 8)
Today, even a "open" source prostitute is getting more "customers", even if she already wide open.LOL!
@new hardware revision owners
can someone test the /tst hack on new hardware revision ?
is there in v2.06.3 (110420.0) a bugfix with 1M samples saving? Can I upgrade my DST1062 with this Hantek fw?
This is probably the reason, why the fast pulse amplitude fluctuates on DST1062B while on Rigol DS1052E you can see nice stable pulse. Frankly speaking, I don't understand why Tekway/Hantek chose this way and I don't really understand how this can work when you need to capture fast single-shot signals. What is the single-shot bandwidth then? Based on what data is the gain calculated??
It might work for sinus, but how can this work for square with fast rissing/falling eges?
I've also found out, that the varicap bias in low-pass filter is still the same for DST1062B and DS1202B unit. They must do all BW control in VGA. The low-pass filter is used only for 20MHz BW limit on/off...
Hi tinhead,no, it's not. On chinese webpage for 60Mhz model is available, on english webpage for 100Mhz model ... crazy what? , but there is
There seems to only be one version of firmware. Is this the same for all 3 models? Does it change the bandwidth or read some config file and leave bandwidth correct for each model?
Colin
no, it's not. On chinese webpage for 60Mhz model is available, on english webpage for 100Mhz model ... crazy what?
What you always can do is to decrypt/unpack firmware content
Sounds like a good idea. What sort of encryption is used to package the operating software? <colin at lasielle dot net> if you want to email direct.
Frankly, I am beginning to suspect Hantek/Tekway software development is not run by engineers, maybe talented amateurs - talent, but no discipline. Lack of changelog, early release of only some versions, upgrades that don't work. This is not building my confidence in them at all. ???
Hi tinhead,Quoteno, it's not. On chinese webpage for 60Mhz model is available, on english webpage for 100Mhz model ... crazy what?
Defintiely a bit crazy. I found the 100MHz version [dst1kb_2.06.3_15102b_fact(110225.0).up] on the Chinese page. I tried to upgrade my DSO5102B DSO and it appeared to do everything correctly, saying successful upgrade, power off and then on to run it. When I turn it on again, the DSO still shows version 110225, and upgrade count is still 0!! The upgrade simply doesn't work at all.QuoteWhat you always can do is to decrypt/unpack firmware content
Sounds like a good idea. What sort of encryption is used to package the operating software? <colin at lasielle dot net> if you want to email direct.
Frankly, I am beginning to suspect Hantek/Tekway software development is not run by engineers, maybe talented amateurs - talent, but no discipline. Lack of changelog, early release of only some versions, upgrades that don't work. This is not building my confidence in them at all. ???
it was fw from the official webpage. To stop the confusion, Hantek updated shortly the file on the webserver.
Those who downloaded the older file found only update for one model, the file what is right now on server does have
updates files for all models.
The version number, well, look in hex editor and you will see, the dso.exe DOES NOT have the number updated,
it is still 2.06.3(110225.0) and not (110420.0)
Even the update script is talking about old number:
[DST type]dst1000b
[soft version]2.06.3(110225.0)
So yes, we assume it is 110420.0 just because it was compiled in April, but after update the DSO will still show you 110225.0
And btw, Tekway is sending exact the same firmware with exact the same version number "bug"
Phew, I have finally read all 41 pages of this thread...
I bought my Hantek DSO5102B last Christmas and did not even fully unpack it until couple of days ago.
I wonder now, is it worth upgrading to 2.06.3 (110420.0) using the original file vias the USB? Will that cause any problems with the hack,
or should I manually copy the files?
yeah, i created some shortcuts in my first posting to save some reading time )I saw those, but you made many more posts in-between that I found having valuable information. I actually pasted it all into a text file so I can refer to it later and contemplate what's said. :)
how come ?I was building a new workbench and my equipment was all stacked aside waiting for the build to finish. It just took sooooo long but here's the product of that labour:
hacked device is working exact as original device, so as you hacked you can use manufacturer firmware updatesAppears it worked via USB, although it says 2.06.3 (110225.0) even though I used the 110420.0 file from their website, weird.
(for the target model, which i assume is now 200MHz model).
Manuall copy work of course too, but it's not that handy is you don't have LAN addon board or at least uart port outside DSO.
I was building a new workbench and my equipment was all stacked aside waiting for the build to finish. It just took sooooo long but here's the product of that labour:
(http://img838.imageshack.us/img838/7144/dsc01907p.th.jpg) (http://img838.imageshack.us/img838/7144/dsc01907p.jpg)
Appears it worked via USB, although it says 2.06.3 (110225.0) even though I used the 110420.0 file from their website, weird.
I looked at the latest firmware update and it seems the only difference is in the scripts in the main tekwayup_client/ folder. Binaries are the same according to my diff here for allactually as there is new and old hw revision each update is checking first for hw model and then calling the child update script.
three versions (5062B, 5102B, 5202B). I wonder why they are separating them now by model if all the binaries are the same.
You mentioned that another member here did some "looking" into the circuits and the code, so I suppose I should not invest time into it if that's going to be presented soon?
What we really need is Hex Rays ARM as that would give us pseudo code, rather than trying to guess through disassembly. Sadly, I do not have it and do not know anyone with it. Kinda pricey at that, too. :\
heh, that's perfect excuse. Btw, on the pic, 4 x Xantrex/Sorensen power supply ? I like them, good value for money, especialy if you use gpib/uart.Yup Sorensen - I got them for $200 on eBay, I think the best deal I ever got judging that you can hook these up parallel, serial, stand-alone. :)
...I agree with you all the way when you said they should focus on fixing bugs and not spending resources on protection as that's just going to make people even more interested to go around it. Just look at what's happening with the commercial software and "fancy" ways of protection that all failed miserably. But I guess Hantekway is trying to keep their shareholders happy, too bad the shareholders don't have much insight into it or they would probably long abandoned protections as they are futile.
so they implemented a secret way to skip model check (by the "special" file). However this only works if the fw version on the DSO know it (so must be at least 2.06.3 (110225.0)).
Anyway, as i heard they will soon have only single fw for all models, probably with better protection, which actually didn't really matter.
i draw schematic (i still have to update some sheets from paper to sch) of the old hw revision (which is what you have), the member i mentionedHe wrote a plugin to convert to pseudo code, that's impressive?!
focused on firmware itself. He disassembled the firmware and analyzed deeper. However as asm analysis cost time he stopped and wrote
own arm decompiler (i think plugin for ida). For sure it might not work that good as Hex Rays, but defnitelly better than nothing (or pure asm).
To buy Hex Rays is not an option (not for single person).
He haven't published yet anything due private work load (so you can still spend some time analyzing too), no idea when he will be "ready",
but i'm bothering him all the time :)
Yup Sorensen - I got them for $200 on eBay, I think the best deal I ever got judging that you can hook these up parallel, serial, stand-alone. :)
He wrote a plugin to convert to pseudo code, that's impressive?!
I thought you wouldn't need a plugin to just disassemble with IDA because ARM is already supported, but can't generate pseudo code without Hex Rays ARM...
When can we see those schematics? :)
Say, I'm struggling here with the dumped image of the firmware. I thought we could mount the root.bin as a yaffs(2) but I'm getting nowhere with it? I managed to compile yaffs2 and got mtd-utils and yaffs2utils as well, but it keeps telling me it's not the right image or not a multiple of 2048+64?
I suppose you aren't using vanilla Linux for your debugging but instead the Mini2440 board?
So now I'm worried that I wont be able to upgrade with future updates?? So how serious is it ? will a new upgrade work? Thanks.you did something wrong, but don't worry, you can't brick HanTekway DSO that easy.
(http://img838.imageshack.us/img838/7144/dsc01907p.th.jpg) (http://img838.imageshack.us/img838/7144/dsc01907p.jpg)
Just for the record, that's really a beautiful setup.Thanks Dave, here's a bit wider view of that side of the room.
Dave
tinhead,
slightly off topic, but do you ever sleep? :)
I envy your passion and ability to stay up non-stop if you never sleep! :D
i did the "worst" thing human being can do - turned hobby into my job.
Hello, could somebody share the latest firmware (for a 100 to 200 Mhz hacked DSO), I sent an Email to Tekway but they did not replied and would like to test the new firmware. Thanks !
simple, there is a array with possible bandwidth values,
[0..6] '02 04 06 08 10 15 20'
so we have 20, 40, 60, 80, 100, 150 and 200MHz.
If the model is set to DST1062B we have 60MHz bw, so the value 06 is selected
which is second value in the array and with DST1202 we have 200MHz, so value 20 which
is the last, also 6th value from the array.
This array will be used to specify the bw filter corner frequency.
Regards the fw version, well hard to say, i remember there are some ugly bugs in 2.6.2,
so it might make sense to update to latest (which have already some bug fixed, but still crashing in measurment-> help menu and
after few minutes when trigger selected to alt. )
About Factory Calibration
I wonder why they didn't just break up the transactions, into smaller
chunks (16-32K), so the watchdog can get "scratched" regularly?
It sounds like the speed of the USB flash stick will also factor into
how big an export can be performed, without triggering the watchdog?
Short of releasing a complete source package, or a development kit,
I wonder if Hantek/Tekway would be open to the idea of releasing
key source files, where known bugs are likely to reside? After all, I
doubt there is too much proprietary technology in their file manager
app, or the CSV export routines. They could publish the file, let the
user community submit changes, and then reintegrate on their end.
They could save a lot of time, and expense, and we could get critical
bugs fixed. Everybody wins.
BTW, thanks for getting pissed off ;)
another DSO hacked, this time in Poland, thanks (:
nice, 110531.1 ... i hope it will be available public (soon)
Btw, HW 10070 seems to be a new hardware revision, do you see any difference?
for those who looking for 64bit driver, Hantek relesed them today, they works of course for Tekway too.
Can someone PLEASE point me in the correct direction with the URL address for the 64 bit Windows 7 Driver for TTscope software
QuoteCan someone PLEASE point me in the correct direction with the URL address for the 64 bit Windows 7 Driver for TTscope software
Sure, try here:
http://www.hantek.com.cn/Product/64Driver/DSO5000.rar
ECL -K
ready compiled update file for Tekway DSOs only (with patched 512k/1M CSV export and updated help file)
ready compiled update files for Hantek DSOs only (with patched 512k/1M CSV export and updated help file)
Thank you very much tinhead about nice work!
I hope that the company Hantek also like to thank and appreciate the work you've done.
Mmmmh - first bug found where the scope always crashes??
· Press button "Display"
· Choosing XY instead of YT immediately chrashes my scope.
Can somebody verify that this crash happens everywhere?
One more questions:yes, don't care about that. That's historical thing, both companies belongs to sahe share holders and dev team is also shared,
I noticed, that in my terminal program the scope says:
root@Tekway-dso /]#
I assume that is OK ??
Mmmmh - first bug found where the scope always crashes??
· Press button "Display"
· Choosing XY instead of YT immediately chrashes my scope.
Hardware: Hantek5102B, pimped to 5202B
HW 10005 (blue PCB), latest FW (110531.1. from Tinheads files dst1kb_2.06.3_15202b_fact)
Can somebody verify that this crash happens everywhere?
One more questions:
I noticed, that in my terminal program the scope says:
root@Tekway-dso /]#
I assume that is OK ??
Update: Logfile (RS232 output) is attached
NOTE!
Do not use this new here shared 110531.1 FW (tinhead shared .up) for new HW version 10070 scopes.
this time it is not compatible without some adjustment/repair.
Only for HW 10050 and below afaik.
(original factory installed 110531.1 works of course with new 10070 HW)
Thank you very much tinhead about nice work!
I hope that the company Hantek also like to thank and appreciate the work you've done.
you welcome.
You mean is it time to ask for free Hantek Handheld DSO ? Or maybe one of the new DSO5000BMV series?
Probably i should, support costs always money. However, they know my address and my real name, so up to them.
tinhead
Do you know what toolchain they used in hantek? I'm still trying to run chroot on scope.
tinhead
Do you know what toolchain they used in hantek? I'm still trying to run chroot on scope.
i tell you something, with different linux you will probably get some issues with lcd , definitely with usb,
we don't know the i/o nor memory mapping of cpld and fpga ... so we running blind.
If you need to compile kernel modules for this board, a good starting point is QQ2440 2.6.13 toolchain, gcc 2.95.3 OABI
(however i complied mtd utils with 3.4.1 EABI). A good idea is to look for firendlyarm2440, mini2440, qq2440, tq2440 boards
and 2.6.13 sources/cross toolchains, many things are already really ancient but you will still find them
(someone posted in this thread link for Q2440 sources).
This will work for all things except new hardware like wifi-sticks (ok, there are some working exceptions).
There is no problem with usb or lcd, framebuffer test works, I can display anything on screen. I can't make busybox or other binutils working. Then I whant to put X11 on screen and run some soft with GUI
Now I know that they use crosstool-0.27 gcc 2.3.2 and glibc 3.4.1 to Fedora Core 4 system (: oh source code could save lot of time, How did you know about "rgj" developer?
i tell you something, with different linux you will probably get some issues with lcd , definitely with usb,Haven't you tried to determine this?
we don't know the i/o nor memory mapping of cpld and fpga ... so we running blind.
Haven't you tried to determine this?
Most likely the peripherals are occupying whole memory banks (nGCS#x) for simplicity. One memory bank of S4C2440 is 128M, and it is quite probbale that the DSO's memory is just mapped to S3C2440's address space. Another memory bank may be used for control registers ant it may be that only 2-3 least significant bits are used while MSBs are completely ignored, resulting in 4-8 io ports occupying the whole 128M bank.
Did you make any other hires photos of the board with components unsoldered?
May be we can run the kernel debugger?
I launch TTScope and it connects to the scope but it says: "No exsit [sic] configuration files to this machine!", whatever that means. The only thing that seems to work is the "Auto Set" function from the Setup list.
PS: I rather shoot myself in the foot than trying to replace a PB-free BGA. Thanks for the warning.
Hantek sent me a list of timebase setting versus digitiser speed, and it's a bit strange, but obviously trying to get around some sort of hardware limitations.
Thanks again for the improved language file, that really does help to make using the machine nicer. It's a shame that Hantek/Tekway couldn't do that in the first place... It doesn't look like they will ever admit they need some help.
I am trying to see what a modern DSO input stage looks like: the most modern schematic I have found so far is from the Tek 2232 (June 1992 !).Well, I think that you can consider yourself lucky, since I have just posted(!) the Rigol DS1052E HW58 (2011 March PCB revision) Channel 1 analog front-end schematics (https://www.eevblog.com/forum/index.php?topic=4048.msg53676#msg53676), while trying to troubleshoot my device (https://www.eevblog.com/forum/index.php?topic=3738.0)!
You are welcome!
But the credit goes to Tinhead, since his work has been an inspiration for many of us.
-George
When I see so many talented people struggling to make such proprietary DSOs work as expected, despite language, culture and manufacturer's short term-only vision, and put so many efforts in it, I am now sure it is worth trying to develop a decent open source/hardware DSO!
Tinhead, if in the window “Display” press F4 (Format XY) oscilloscope hangs and stops responding to all buttons. You can only revive the Power button (re-enable).
Do You encountered this error?
Mmmmh - first bug found where the scope always crashes??
· Press button "Display"
· Choosing XY instead of YT immediately chrashes my scope.
Can somebody verify that this crash happens everywhere?
yes, i noticed it too. It does have something to do with an overflow during channel activation.
However it works perfect if you enable (just turn on, it does not matter if then on AC/DC/GND) both channels
or actually disable (turn off) both channels before you enable XY mode.
A small bug only, normally you will anyway enable both channels, setup coupling etc. before you go to XY.
I noticed in this picture these 3 strange new unpopulated footprints between the AD8370/LMH6552 and the AD8510... Really looks like a crystal with foot capacitors layout, but I am sure this can't be the case.hehe, no not for cristal, probably temp sensor, however we should track back these pins.
Still, I don't understand the lack of current limiting resistor for the OptoMos: this device is a Cosmo KAQY214S solid-state relay with MOSFet output, with a max forward voltage of 1.5 V, and max forward current of 5 mA.oh there is one,
Also, although I may understand the reason why the input capacitor before the JFET and the dual BAV99 diodes is angled at 45 degrees to shorten the trace in this particularly sensitive area, however I don't understand why Tekway also angled all the AD8370/LMH6552 stuff this way? Is this to stress their pick-and-place machine? ;D
Do not keep any signal connected to scope when you on or off oscilloscope power.
...In a good design, I would recommend:
Ok, go to do some (imagined) industrial service work with this. So, that you example try find some problems in situation where all systems are running with full speed... then you keep your scope connected and watching... and there come lunch time... you shut off your scope... (or come back and shut on) one PID loop swings from one end to one end... after ten seconds whole system is short time heavy disturbed, alarm rings and paper breaks... oh...thank you Hantek... it was only some tens of kilo euro. (imagined worst case scenario ;) )
(this is one reason why Agilent (oh maybe I'm wrong and need say, old Hewlett-Packard) or Tektronix professional series instrumets (not hobby series) are very cheap in use.)[/size]
- to put a 2kV spark gap at the input, with very good path to ground for ESD protection, see Dave's videos if you are not sure what I am talking about :o
- to provide a normally-open GND coupling relay at the input, which would physically disconnect the device under test when the scope is turned off and during start-up transients, to avoid any harm to it, or don't go out for lunch during tests ;D
right, the input is never ever really off.
replace all these cheap relays/optoMOS by more adequate models
replace BAV99 diodes
replace the 2 BC846 transistor for current mirror by at least a matched pair (BC846B)that's already matched pair of BC846B (actually you don't have to much them today anymore)
replace the AD8310/LMH6552/VariCap by the LMH6518 abovefor what? Actually you mean AD8370 and not 8310 (or you mean the AD8510 in LF path?)
straighten the signal trace as much as possiblehmm, it is stight, then 45° to first opamp then again stright ... the only think i don't like
keep the signal trace as short as possible and away from other tracesthat would be complettly new PCB, much bigger anyway. Hantek/Tekway did it anyway better
I am trying to see what a modern DSO input stage looks like: the most modern schematic I have found so far is from the Tek 2232 (June 1992 !).There's a more modern service manual for the Tek TDS520 available, I think on tek.com. Not exactly modern, but fairly detailed.
Really? Do you have more details on this? Maybe pictures, schematic of it? I am really interested!well both, but i can't publish as they has been created by someone else who don't wish to publish them,
This can't be, you have to do anti-aliasing filtering before sampling, not after. Maybe you mean that filtering is controlled by firmware?no you don't, or not in form of what you interpreted from the schematics. It is hard to say what exactly Rigol/Atten/Instek/UNI-T/Tonghui are doing within the firmware because nobody (yet) reversed it. However it is simple to reverse Hantek/Tekway
Unfortunately, Tek schematics are only block level after the Tek 2232, so is the TDS520 :-\Really? Have you checked? The document is called 'TDS 520B Mod CM Digitizing Oscilloscope Component Service Manual', and those schematics don't look like block level to me.
that would be complettly new PCB, much bigger anyway. Hantek/Tekway did it anyway better
(they have at least better shielding) than Rigol/ATTEN where the PSU is so close to ADCs/Trigger
stage/1MSs-500MSs relays that you have already influence.
EDIT: Actually, I found the "Component Level Service Manual"on an exotic websitetek.com is exotic?
but not really useful: Tek was already using hybrid modules for the analog front-end, thanks anyway :-\That's a modern DSO for you ;). Lots of custom silicon, even more today than back then. This helps decreasing footprint and costs, and increasing performance. Some SMT passives on FR-4 just doesn't cut it for good HF performance.
I could only find the "Module Level Service Manual" there, I had to search for TDS520 "component level" service manual in order to find it somewhere else.A search for tds520b on tek.com finds this (http://www2.tek.com/cmswpt/madetails.lotr?ct=MA&cs=msv&ci=9971&lc=EN).
The Tek 2232 was probably one of the latestAgreed, you learn more from studying the older technology, but it's not how a modern DSO is build. Just like a modern consumer widget often consists of a blob of epoxy on a phenolic PCB.
As hobbyists, we have no access to either Hybrids or analog ASICs, so both the "old" Tek 2232 and these cheap low-end DSOs are interesting to look at.
Well, that's confusing: for a single ADC, you need to meet was is known as the "Nyquist criterion", see Wikipedia ...
But what I am saying is only good when you have a single ADC...
As there are up to 10 of them, they can be clocked so that each one is sampling with a calibrated period that is 1/10 of the sampling period, thus achieving an effective sampling frequency of 1 GHz. Then, by digital reconstruction, you are able to get a 1 GSPS resolution digital signal, that you can THEN filter digitally to whatever you want below that.
And in this case, I really don't know if what I said for a single ADC is still valid, or if aliasing "magically" cancels itself by using several of them working with such a clock scheme, only requiring a max signal frequency of 1 GHz/2=500 MHz...
I think, Hnatek need immediately solve this design bug. If there need boot time cal connection it need solve different way.
500 ohm directly from CH1 to CH2 center whole boot up time!
Maybe 2/3 of the boot time is the OS coming up. After that, the DSO app is run.
I have not observed any scope related state changes, prior to DSO running. This
leads me to believe that the problem is caused by the initial state of the shift register,
controlling the relay. Hantek should have added a tristate control, and pullup/down resistors
to all of the outputs, so the controls could be set to a knows state, prior to software initialization.
Looking at tinhead's (very handy) schematic, it appears that we may be able to force the
shift register to clear, by adding a RCD circuit to the SRCLR pin.
Just curious if anyone else is experiencing this behavior? If I power-on my
Hantek, with a USB stick installed (front port), the stick is not recognized by the
DSO application. The OS, however, does see the stick, and auto-mounts it.
I need to unplug the stick, and re-insert, before the scope will flag it's presence.
500 ohm directly from CH1 to CH2 center whole boot up time!
are you sure ? When off, the self-calibration relay is not connected, the attenuator not active, so in principle 1.2M input
(the state of relays on my schematic is off mode)
Yes, all what I can now look is HW5 and HW7 with FW, ..225, 420, 427patch, 531.1... all have this problem and afaik problem was also before. Not nice but can live with it. If need lot of USB things all times, it is good to buy short cable.... no need wear scope USB connector. (specially becouse these quality is just as entertainment quality (all USB connectors not only hantek but who care... today electronic need only 1-3year lifetime and tomorrow we go more short "designed" lifetimes.)..
yep, i know it. The funny part is, firmware update menu is even trying to access to stick, but
it fails because stick didn't exists (but the stick led is blinking ...) So it seems the firmware
just don't see a specific flag. Not sure if this is really firmware bug or linux hotplug delay bug,
it takes anyway a bit long to recognize usb devices. Maybe a delay before dso.exe will be loaded can help out.
Well, channel 2 has stopped working and also the vertical position control (it jumps back down to 0). The oscilloscopes self calibration stops at step 13.
Channel 1 seems fine.
Anyone know whats the cause or how to fix.
I bought it from www.youroscilloscope.com (http://www.youroscilloscope.com). I think they dropship from Hantek china.?first of all try to contact them, for sure Hantek does have warranty, but it might be that the seller will not
I'm in europe/cyprus.
So do you think i have to ship the oscilloscope back or is there an easier solution, maybe in europe?
I'll play around with it, and see if I can figure out
what they're doing.
This is also not good to measure real BW becouse input reactance. 50 ohm termination is not good method becouse it is not matced to 1M 20+-3pF input. It do not see scope input as pure resistive load. SWR is not 1.
Now Hantek input is 20 +-3pF
How to make better external 50ohm temination if scope have not internal 50ohm impedance matched inputs?
... if scope have not internal 50ohm impedance matched inputs?
@rf-loop: I checked the Tek 2465 schematics, 50 ohm coupling only consists in switching in a 50 ohm resistor in parallel to the 1 M resistor. The only additional trick is to put a thermal sensor on the 50 ohm resistor to check for channel overload.
Anyway, 50 ohm // 1 Mohm = 49.9975 ohm ::)
@tinhead:
From which model is this picture from? From all the front-end pictures I have seen so far,
I never observed the ability to get a 50 ohm input termination!
Even worse: in most of these scopes, there is no real GND coupling and the Rigol does not even have AC coupling for trigger...
@tinhead: GND coupling should actually isolate completely the DUT from the front-end! At least, this is what I observed in ALL other scopes before. But of course, this costs one additional relay ;)
I wouldn't leave this unpowered DSO connected to my DUT, if I were you ;)
I completely agree with you rf-loop, of course, a schematic doesn't tell you the whole story :)
EEs at Tek, HP and LeCroy really knew their job: even 20 years later, these scopes are still nice pieces of jewelry!
To give you an idea of what these scopes are made of, please look at this very interesting April 1986 issue of the HP Journal (http://www.hpl.hp.com/hpjournal/pdfs/IssuePDFs/1986-04.pdf), almost dedicated to "Digitizing Oscilloscopes", and to the HP5411OD in particular.
But we should compare what is comparable: these were x$10,000 scopes, vs. $300 ones! These old scopes were built around hybrid circuits with coupled microstrip lines and delay lines, our cheap DSOs are made up of 6-layer FR4 with stock components...
So for sure, you can't expect the same performance from both. Even if progress has made things cheaper, RF rules have not changed :-[
To give you an idea of what these scopes are made of, please look at this very interesting April 1986 issue of the HP Journal (http://www.hpl.hp.com/hpjournal/pdfs/IssuePDFs/1986-04.pdf), almost dedicated to "Digitizing Oscilloscopes", and to the HP5411OD in particular.
When I use only CH1 and cross 200ns time base boundary it switches probably to interlaced mode (my guess, I hear relay click) and I get a little bit different readings. See attached images. The change is subtle but noticable. Is this a normal behavior?
Hello everyone,
Just joined up.
I came across this thread looking for info on the Hantek DSO5202B which I subsequently purchased from an ebay seller.
The CRO works really well but I have struck a few issues with this CRO which I wonder if other people have found. I have sent this info off to Hantek but have not heard back from them. The firmware installed is later than what is on the website.
For instance, AC coupling of the input channels inserts a high pass filter that peaks at 100 Hz and rolls off below that. So when you display a 100 Hz sinewave and switch from DC to AC coupling the signal amplitude actually increases !! Ideally the AC coupling should be flat down to 10Hz and roll off below that without any peaking otherwise this is causing an error in the readings.
Also frequency measurement on the bottom of the screen does not correlate with the menu because the bottom screen measurement decimal places are always zero. ie frequency shown in measurement menu is 105.3Hz and frequency shown at the bottom of the screen is 105.00 Hz.
regards
Hello everyone,
Just joined up.
I came across this thread looking for info on the Hantek DSO5202B which I subsequently purchased from an ebay seller.
The CRO works really well but I have struck a few issues with this CRO which I wonder if other people have found. I have sent this info off to Hantek but have not heard back from them. The firmware installed is later than what is on the website.
For instance, AC coupling of the input channels inserts a high pass filter that peaks at 100 Hz and rolls off below that. So when you display a 100 Hz sinewave and switch from DC to AC coupling the signal amplitude actually increases !! Ideally the AC coupling should be flat down to 10Hz and roll off below that without any peaking otherwise this is causing an error in the readings.
Also frequency measurement on the bottom of the screen does not correlate with the menu because the bottom screen measurement decimal places are always zero. ie frequency shown in measurement menu is 105.3Hz and frequency shown at the bottom of the screen is 105.00 Hz.
regards
I test with HW7 DSO5102B (in this case very same as 5202B)
AC mode (Why?)
If compare to 1kHz sine signal level (set in calculations as 0dB reference)
Measured directly without probe.
Including old Wavetek flatness errors (yes but this my Wavetek is carefully adjusted so that it is surprising flat level - error is significantly below +-0.1dB in this area)
CH1, AC, 500mV/div
signal level 6div p-p @ 0dB
-6dB 10Hz
-3dB 17Hz
0dB 41Hz
+1dB 80Hz
0dB 350Hz - 1kHz
----------
About frequency counter.
Measure menu freq are _calculated_ from ADC captured data.
With low freq it may sometimes be better and more accurate than HW counter. Specially if use averaging.
HW counter work totally different. It counts events in trig line. It is event counter. It counts how many events in time window.
Becouse it is not as modern real timeintervall counters it resolution is highly dsependent about time window setting for counting. How long is gate open window what time it use for counting these pulses. (yes it is just pulse counter. Totally different as modern frequency calculating time interval counters as something like cheap HP53131 or similars. They can solve 9-10 or more decimals in one second.)
And why use AC coupling ? Simply because you may have a small AC signal superimposed on a large DC offset so you want to be able to get rid of the DC component otherwise it is not possible to view the small AC signal with maximum sensitivity.
regards
And why use AC coupling ? Simply because you may have a small AC signal superimposed on a large DC offset so you want to be able to get rid of the DC component otherwise it is not possible to view the small AC signal with maximum sensitivity.
regards
Yes, this is mostly nearly only reason.
This is not FW related thing. It is HW.
Analog front end is simple and cheap. It is just like compromise.
If we look example old expensive HP or Tektronix front ends they have lot of adjustments for corrections and corrections for corrections.. more accurate want, there is more small errors what need compensate with some adjustable or not adjustable circuit.
Specially I do not like this way they do AC/DC in front end. From designer I can ask why? Some reason? Any reason?
Or reason is becouse copymachine did not change it. It is problem with copy, you copy also mistakes or bad's. ;)
Also there are all component tolerances. Tolerances may be sometimes in worst case compination and randomly sometimes best case. (example this peaking freq difference - but in this case you have real 5202B what have some different componet values in front end so it may also affect this difference.)
I do not like this front end. I can not understand this solution for AC/DC. (or maybe if really think every cent)
I have recommend to some my customer (who want more low cut off frequency) to use external DC block.
I make one short experience.
Scope input DC
Probe 1x
Measured
From 50ohm output terminated with 50ohm feed trough terminator.
For DC block: 100nF capacitor from terminator center to probe tip.
Response "flat" to around 20Hz
very slowly it satrt drop. 10Hz 3V-pp have drop to 2,9V
1,5Hz it have drop to 2,14V
Lack of time I did not test with 1uF
Probe 10x
as before, 100nF
in practice, nearly flat down to 1Hz.
This can give also idea how to measure extremely low frequencies over high DC. (1uF, 10uF and even more but be careful if voltage is high... becouse..if there is transient... well: after smoke come out from component, equipment do not work...smoke need put back agen)
In lab it is many times needed. DC block. (for common use it may be total block or sometimes only ground connecting "center" block.) For probe tip DC block, well, everyone can imagine how to do if need.
In some rare case I have use 100uF polypropylene capacitor with some Tektronix. (some reason need measure extremely low freq's over high DC)
I think this front-end design is not bad, especially for its price and using only stock components.
Regarding the LF loopback, the "corner" point at which it occurs is given by the capacitor in the loop and I don't remember which resistors around. But it occurs at some 100s Hz, and if position is well compensated, should be smooth to HF without too much hiccups. This shouldn't affect the frequency response above that.
In order to understand what's going on, we should put a probe on the AD8370 input (TP2_1), first, then a differential probe between the 2 test points at the LMH6552 output, and see what we get. I suspect that the varicap introduces non-linearities, but I am not sure.
Then what is displayed on the LCD, that's another story... The ADC clock seems to have a lot of jitter, so this is not good for ADC interlacing and may thus produce a lot of distortion, and running without any anti-aliasing filter too is a bad idea, as you may get additional distortion by spectrum folding at the sampling frequency...
You can find it as an attachment to this tinhead's post (https://www.eevblog.com/forum/index.php?topic=1571.msg53703#msg53703).I think this front-end design is not bad, especially for its price and using only stock components.
Regarding the LF loopback, the "corner" point at which it occurs is given by the capacitor in the loop and I don't remember which resistors around. But it occurs at some 100s Hz, and if position is well compensated, should be smooth to HF without too much hiccups. This shouldn't affect the frequency response above that.
In order to understand what's going on, we should put a probe on the AD8370 input (TP2_1), first, then a differential probe between the 2 test points at the LMH6552 output, and see what we get. I suspect that the varicap introduces non-linearities, but I am not sure.
Then what is displayed on the LCD, that's another story... The ADC clock seems to have a lot of jitter, so this is not good for ADC interlacing and may thus produce a lot of distortion, and running without any anti-aliasing filter too is a bad idea, as you may get additional distortion by spectrum folding at the sampling frequency...
do you have the schematic of the front end so I can see what you are talking about ?
regards
david
I can see the AC/DC relay and DC blocking cap but where is the peaking coming from at 100 Hz ??Please read again my reply above (https://www.eevblog.com/forum/index.php?topic=1571.msg55917#msg55917), when a speak about the corner frequency at some 100s of Hz. It looks like the transition from LF to HF is not well calibrated.Possibly need to simulate it in spice to see what is going on.Possible, but not easy... You must make provisions for stray capacitance due to component pins and also to the FR4 PCB (with permeability tolerance of around 50%), and circuit loop inductance and also mutual inductance between circuit loops :P
When you get a model that is close enough to reality, let me know, I will be very interested, and probably others too!
placeholder ?check next page to see why ..
A complette schematic of Hantek / Tekway hw revision 1.02 and 1.0.3
Hm. Why CPLD? Why not FPGA only? Did they save some pins? They seem to have XBUS which is quite wide.
Tinhead - I am speechless... all I could say is, thank you for your work and support to make this wide screen DSO so valuable.
The important thing is to know what's inside CPLD.Xbus seems to be 16 bit + 3 bit control, all these CPLD pins are on input (when i disable FPGA).Maybe XBUS is a 16-bit muxed address/data bus, with r/w, strobe, and mode (or r/w, address strobe, data strobe), also in charge of access to the logic analyzer stuff?
Address counter probably triggered by FPGA, i have to check that in detail.
Just my guess, though... You might have to put a logic sniffer to see what's going on between the FPGA and the CPLD.
There is a possibility to write alternative software from scratch. Worst case scenario is developing FPGA firmware from scratch too. It is not possible for CPLD and it is unwise to reflash CPLD.as we speek about software, do you got my PM about SDK?
The good thing is that there's no need to use CPLD to talk to the ADC. But there will be no memory buffer.
BTW, do these low-memory scopes have CPLD too? I noticed that Atten doesn't have a SRAM chip on the board, just empty place. Is it possible that CPLD is turned off in short-memory mode?
as we speek about software, do you got my PM about SDK?Now I did, thank you! Please see my reply.
The good thing is that there's no need to use CPLD to talk to the ADC. But there will be no memory buffer.
in current design no because the data will be shifted over CPLD, there is no physical data bus connection
between SoC and FPGA.
There was even some cheaper than "CAL" model (CL? don't recall). I saw a photo of it's board (really poor soldering job!) and noticed that there is an unpopulated place instead of SRAM. Of course, there's a little possibility that the chip was just removed by the owner.BTW, do these low-memory scopes have CPLD too? I noticed that Atten doesn't have a SRAM chip on the board, just empty place. Is it possible that CPLD is turned off in short-memory mode?
no idea, i know that Atten CML does have one, but never saw the bottom side of CAL model.
Turned off for sure not, you will not find even single resistor which don't need to be populated.
tinhead
Can it be fixed booting bug in the CPLD with
self-calibration relay ?
I would really appreciate a tutorial!
Nice thanks!
What about de/re-soldering the BGA, then?
What?!? :oWith patience! :P
I am curious to know how do you do that?
I think is is time for a short tutorial on the BGA and Flat Pachage rework process, using home equipment:
Equipment used: A hot-air rework station, a soldering iron, soldering wick (ERSA 2mm/3mm/4mm wide), flux paste (I prefer the RMA flavor but I've only found a no-clean syringe container at the local stores -that is fine for this job), SMD rework solder-wire (sub-millimeter Alpha-Fry 62/36/2) and flux soldering paste (EDSYN 62/36/2 no-clean).
Remember that the activated flux (RA/RMA) based products have only a few months self-life, even if stored in the refrigerator.
This is the rework strategy:
1. Preheat the PCB using 130 degrees hot air for 2-3 minutes, to avoid any thermal expansion artifacts,
2. Use conventional (kitchen) aluminium foil to protect the surrounding components, by cutting off a small window to expose ONLY the target chip to the hot air flow,
3. Desolder the BGA using 300..320 degrees hot air, remove the chip and wait for everything to cool down,
4. Clean the old solder, holding the BGA package in a small plastic vice using solder wick and lots of flux; always clean the used flux (I use medical alcohol of 95 degrees or better),
5. Clean the PCB, as above,
6. Reball the BGA with the soldering iron, Ag-containing solder-wire (I use 62/36/2) and lots of fresh flux; always clean the used flux,
7. [Optional step] Reverse the PCB (that takes tiiiiiiime...),
8. Reball the PCB pads as well, as in step (6), since chip re-balling has not provided the pads with enough solder,
9a. Carefully apply flux soldering paste on the PCB pads only and flux at the chip pads, or
9b. Apply flux in lack of flux soldering paste,
10. Carefully place the BGA package on the PCB (in a single move, if possible) and
11. Preheat the whole PCB area around the chip using 130 degrees hot air for 2-3 minutes,
12. Raise the hot air temperature at 280..300 degrees and apply it to the chip in a slow circular motion,
13. Wait for the molten solder surface tension to move the chip in place when the solder melts,
14. Tap the chip gently towards the PCB, to make sure that all its pads are in contact with the solder underneath,
15. Remove the hot air and wait for everything to cool down naturally (by themselves); always clean the used flux, and
16. Done! Power the device up.
Right now I am at the seventh step...
NOTE: It is not as difficult as it sounds to be; but you need to practice enough before daring to touch your actual device without destroying it!
A second note is about the chip size: As a rule of thumb, use a hot air nozzle of half the diameter of the chip size. For chips smaller than 20mm x 20mm you may skip the PCB preheating step, only if the PCB is very thin. Unfortunately, this is not the case with Rigol's mainboard.
A third and very important note: Always know what you are doing. Always use your common sense! Miracles happen only in fairy tales...
Finally, remember that a good tool is NEVER expensive enough to have it. Just consider the possible extra cost of a damage done by using cheap ("affordable" in the marketing jargon) tools...
All the complaints about my English- to google-translator.
In English I translate all the same it is better :)
About Hantek noise.right, and actually when you look on PCB these caps are really missing. I have no idea who started first
On page 6 "samples | hold offset control" published schemes, it is clear that there is a DAC, switch on 74HC4051, and repeaters on operational amplifiers.
Some circuit have a ripple capacitances, some nothing.
It seems to me that the reason for the strong noise in this part of the scheme. The rest of the analog special crime unnoticed.on hw1007 Hantek optimized it a bit
My point of view, confirms that the on high-frequency scan, noise is greatly reduced. I.e. with increasing frequency voltage is kept more accurately.
Or the easiest and cheapest way - much to raise the switching frequency of the reference DAC and switch in firmware.there is nothing we can do as the DAC is controlled by FPGA design
Btw, i'm testing right now two new firmware versions - they not public yet, but i can already tell you the changes:
- FFT is more accurate than before, compared some measurment with my SA and i like it
- Timebase have now fine adjustment (up to 200ps)
- XY bug of course fixed
- CSV export and import works for memeory depth settings
- the actual Sample rate and few other system informations will be displayed in separate infobox
Btw, i'm testing right now two new firmware versions - they not public yet, but i can already tell you the changes:
- FFT is more accurate than before, compared some measurment with my SA and i like it
- Timebase have now fine adjustment (up to 200ps)
- XY bug of course fixed
- CSV export and import works for memeory depth settings
- the actual Sample rate and few other system informations will be displayed in separate infobox
Do you know when can we expect it to be released? I assume that this will be official firmware, right?
No matter how many divs is display. It have not so much to do with this.
is only more or less processed "window"
What I wanted to explain, is that having a large wvfrm/s figure is only useful not to miss an event, if you don't have a "digital phosphor" display.
(049)mem valid cnt=545..time 10s wave frames = 1150...
(050)mem valid cnt=546..time 10s wave frames = 1177...
(051)mem valid cnt=543..time 10s wave frames = 1163...
(052)mem valid cnt=541..time 10s wave frames = 1178...
(053)mem valid cnt=546..time 10s wave frames = 839...
(054)mem valid cnt=546..time 10s wave frames = 232...
(055)mem valid cnt=545..time 10s wave frames = 231...
(056)mem valid cnt=545..time 10s wave frames = 232...
4) Given all of this information, I find that the figure quoted by tinhead in the first post of this thread of the Rigol DS1052E achieving 2000 wfrms/s as highly unlikely. Does anyone know where this figure has originated? Obviously the tiny screen of the Rigol allows faster updating (and less acquisition time), but I still think the figure seems high.Based on the findings of the owner of an Agilent 1000 series scope, it appears that the 1000 series is equivalent to the Rigol 1000B series, which looks to be much higher in their range than the DS1052E.
4) Given all of this information, I find that the figure quoted by tinhead in the first post of this thread of the Rigol DS1052E achieving 2000 wfrms/s as highly unlikely. Does anyone know where this figure has originated? Obviously the tiny screen of the Rigol allows faster updating (and less acquisition time), but I still think the figure seems high.
@tinhead
Note that UART out do not show wfrm/s
Look agen what UART exactly send out!
I can not find any wfrm/s.
"time 10s wave frames = nnnn"
Btw, what is meaning of waveforms what can not see or settled. How you set 10div capture.
Only captured waveforms what are really usable and/or also they can relly see or can use for some useful things are meaningfull. If there are behind processing (before processing) some captured waveforms what can not see or what do not affect anything... they are just to garbage collection. Also poersonally I'm not interest any kind of calculated unreal speeds. Only what moves me is what can really use in practice and they are meaningfull.
Stop capture, also there is ONLY one capture. Where are these others what need be in "digital phosphor" memory. Why they disappear every time I stop capturing. ;) So this DPO "effect" is done only for human eyes as scope is running.
Hi,tinhead!
Can see the raw data from the ADC via the console?
Something I have some suspicions that the noise is the result of dithering or mathematical artifact.
Because at the ADC input, with shorted at the input on BNC, voltage noise is less than 0.25 bits(<1mV). Reducing supply ripple ADC twice does not lead to any result.
today we know Rigol E have 800 wfrm/s (you remember maybe Dave's video, 50000events, after ~60second first event was shown on Rigol).
today we know Rigol E have 800 wfrm/s (you remember maybe Dave's video, 50000events, after ~60second first event was shown on Rigol).
No, no, no!! Dave's conclusions were wrong. I don't think it's likely that the Rigol DS1052E (or E series in general) does 800 wfrms/s - if it did, they would advertise it in their specs because that is a VERY good figure (look at the figures in the Agilent literature for much more expensive scopes). Please, let's put an end to this unverified information right now and not spread it any further.
Anyway, i build yesterday glitch generator (similar to what Agilent doing) , 500kHz square,
glitch every 500, 1k, 2.5k, 5k, 10k and 50k clocks. I just don't liked the code which i posted before,
it does the work too but every 1.3 second and one single event ever 65535 - for a scopes with
low wfrm/s the event takes forever and the chance to not catch them i very high.
....or i can have no luck and start perfectly in blind time - after 30minutes no single frame captured.
Sorry, tinhead [to be again poking at your figures with a stick ]don't sorry if you poke, i don't mind :)
If you don't capture a single frame in 30 minutes, it means that your scope CAN'T be a xxxxx wfrms/s scope - because probability theory says there is a 99.9999....% chance that it would have captured the frame otherwise. As I said in my previous post, it's easy to prove how fast your scope ISN'T with glitches - not how fast it IS.
Anyway, i build yesterday glitch generator (similar to what Agilent doing) , 500kHz square, glitch every 500, 1k, 2.5k, 5k, 10k and 50k clocks....after 30minutes no single frame captured.
Which specific test were you running when you had the 30 minute gap?
P.S. Both the Hantek and the Owon appear to use 20 divisions for a full-screen capture - which is double the 10 division scopes - so you can basically double their rates in comparison (or halve the competition with 10 division screens).yes, in 19.5 div mode HanTekway is in real using 20divs, but the 16divs mode is not just a cut,
Yes, surprising as these DSO are not full ready ;D,right, Hantek confirmed this once again last night.
BMV series will come first with chinese video help, better is to wait all languages video help.
We wonder how will be the spoken translation... :-\
Whatever, Tinhead, what kind of gift you can propose? ;)
Mind you, ever the pedophiles have rights in this world...
It is hardware version 10070x55553e8, still hope I would be able to upgrade to 200 mhz even though the package came with 150Mhz probes set.
I ordered this (http://www.ebay.com/itm/370532286388?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649) USB TTL. Do you think it will work?
The bad thing... For the whole this thread I have read I didn't found some one to complain about the fan. I saw that most people are saying there is no fan. Yeah - but this has one. And it is loud, very very noisy one. Like most of you I disssembled the scope and after reviewing it - choose the most easy thing to fix the noise. I had added 150 Ohm /1W resitor. The current without the resistor was 40 mAmps and with it ~ 17mAmps. I did tried 0.5W resistors but they gets warm so 1W is better. Using the resistor, the fan is spinning at reasonable speed but at much lower speed than the original. I guess that would be enough but I don't really understand the purpose of that fan. There are holes over the PSU and at the same time the fan is far way from it and it is blowing to outside of the box. What do you think about this ?
Also did self calibration several times and tuned the probes but there is noise you will see on the attached pictures. They use the scope's oscillator (peak 5.2V). It looks like the noise is taking 1/15 the voltage, and so the noise would be ~0.3V. Is only me finding this disturbing? I see some of you had discussed it, but there is no solutions, right ?first of all before you run self calibration do once "default setup".
See the pics attached. Some of them are a bit blurred. Its due to my camera and photo skills quality. Don't judge me too much.i can see your serial ... not that i really care about, but is maybe not wise to talk about haking the device
Whatever, for people like us surrounded with other noisy machines in our laboratory, the DSO fan is a piece of cake... ;D
In lab there is always noise but it is not very nice. It was -80's when nobody think noise. Todays peoples play heavy rock with earphiones but then they are extremely critical if some equipment give small noise. But yes - I hope manufacturers keep this noise levels down as possible without super high price.
Is only me finding this disturbing? I see some of you had discussed it, but there is no solutions, right ?
@tinhead. Thanks for the responses man. You really rule and should be getting sallary from Hantek :P
I have updated the post with the usb short of the noise. Could please take a look and compare ?
Also could you give more info about the 3.3 V LDO to DC/DC converting. I have read your post about the capacitors changing but didn't understand the part of the DC/DC (i'm ee novice).
Hi walt,
Have you tried actually that? Is there any more pictures?
Could you give us more information about the element - like picture of the main board?
Btw have you measured the temperature before and after?enclore temp right over PSU - before "hot", i remember someone measured it, but just disable fan and leave DSO
Btw you say the noise level would be lower... why ? How the PSU is related to the ADC measurement paths?google "ADC PSRR" and "Power Supply Effects on Noise Performance".
Just curiosity - how much you had been able to lower the noise ?... a littlebit only. You will always have some small differences between produced units,
Guess the engeneer(s) at Tekway was too much in hury (or not at your level - lol) to calc properly the things out. Few dollars above the price with your set of components for PSU might be saved from the old one + the fan.
Have you tried actually that?
Without probe attached, pushed Auto Set button and then the measure menu ...
How did you achieve it ?
Can you make a ordered list of what exactly you have done
Do you think it would be too illegible if you start open source hardware project. Actually
... before ppl spend now time desoldering parts
maybe someone of you here have a bit of spare time and can try to identify these still unknown components:
SOT23-3, part marking SCJG, pinout 1-VCC, 2-Vout, 3-GND
- this is voltage ref. used in hw1007 instead of LT1790-4.096V
Hi again
Just wanted to inform you that the CMOS UART port had been removed from the latest hw version.
PS. Put 2.2 uF (WIMA MKS2) capacitors in addition to the standard capacitors,
had you though about wifi usb dongle plugin in ?
I think the drivers could be uploaded through the console, we only need to know the kernel vers and architecture. I bet there would be toolchans available.
Drivers could be mod'ed to work with this kern.
Or kernel could be upgraded ?
Or a suitable wifi dongle could be found.
Although I wonder what could be the benefits of all that, It wouldn't make big difference to use the dongle instead of the UART port.
Would Hantek ever release the dso.exe source, so we can mod it and make useful things from the network ?
Well I tried 3 x DSO5102B and 1 x DSO5062B, all with 2.06.3 - 110808.0 from Hantek this morning, and they all work without this bug ! ;)
yes, maybe, mine are new from yesterday :Pyeah, perfectly possible, there wa a lot of beta versions in between, at some time
Whatever, updating with last version cannot be wrong... 8)
Known bugs in this firmware:
Please, tell Hantek don't reset color of screen, when pressed "default configuration button".
It is no sense!
Pascal, as you there, did you plan to order some of these DSO1000B/S handhelds?
This is only one and small example:
Set display dots
400us/div
1M memory
capture.
push Utility
look SysRunParam it show 100MS/s, 800000 sample dots, 800000display dots
Stop
Cursors
Turn sec/div 20ns/div ok you see dots but not 10ns distance, they are 8ns,
ok turn 8ns/div oh well now dots are 6.4ns and only left half of screen
try horizontal position: can not move
turn 4ns/div all disappears
Ok same agen but 200us/div
oh, can not select 1M, only 512k
push Utility
look SysRunParam it show 100MS/s, 400000 sample dots, 400000display dots
cursors
Stop
Sec/div to 20ns
measure 10 dot interval = 107ns
turn 8ns/div measure dot interval 12.8ns
turn 4ns/div now dots only left half of display
measure dits interval = 6.4ns
Mode dots, 200us/div 1Mpoints, 10MHz signal from Rubidium standard to scope. Capture.. Stop, change to 8ns/div
measure freq on the screen. 11.7MHz so use 0.855 but specs do not tell that need use this constant for multiply.
Btw, display vectors have not this problem. So how they make vectors if they do not use these sampled dots, or is it so that display dots are not sampled true dots at all? What is meaning if displayed dots are not sampled datapoints?
If they can scale vector display why not these dots?
200us/div, zoom to 20ns/div, measure 10 dot interval = 107ns
and here as mentioned above my version of the 2.06.3 110909 (110908) firmware
wtf .. only 10 download?
Mode dots, 200us/div 1Mpoints, 10MHz signal from Rubidium standard to scope. Capture.. Stop, change to 8ns/div
measure freq on the screen. 11.7MHz so use 0.855 but specs do not tell that need use this constant for multiply.
This data is exactly in memory, every single sample point. Only what need do is pick up them to screen so that displayed time is right enough.
10:11.7 ... this can not accept. I understand well that always can not show exactly becouse screen have only limited resolution. It can not be very difficult higher level math if want know what is every sampled point time becouse this sampler is really simple becouse interval is fixed.
Also what about jitter. This need not take account. In calculus there is some sampling speed and then some time interval between samples. Multiply 2 and if you multiply it ten or ten million it is just as it is... zooming factor do not mean anything in this case. 100MS/s means 10ns sampling interval. If there is 2, 4, 8 20 or what ever time/div just plot these pxels right place.
I can't but agree with rf-loop on many things. It seems to me too that they have no system of fixing bugs. I mean I'm happy too that they added tracking cursors, but there are still many bugs that should have been already fixed long time ago. Slowly I'm becoming tired reporting again and again same bugs, filming videos (because they almost always ask for it) and asking for the answers after many days of silence (now I'm talking especially about Hantek). I have no time for that and I have to agree with rf-loop again, I'm also not a tester, I'm a customer (not takling now about testing new features like tracking cursors, which I'm always happy to do).
1. Filters - the implementation of digital filters is horrible
2. Scrolling 1M and 512k sampled signal at 4ns and 2ns timebase doesn't work. The signal disappears and the time scale is "jumping".
3. Display Dots doesn't work in 2ns and 4ns timebasehmm, you mean when you enable dots, go to 4ns/div and stop you can't see any dots when
Thanks for the FW patch, tinhead, you're an untiring fighter! :)
offtop..and in the next lesson we'll learn the difference between "gay" and "guy" ;D
Gays, with you, i learn English :)
tinhead , in new firmware, and/or you patched save to usb flash work properly?
I am not sure, may by my flash drive is not good (apacer ah323), but update firmware was from it.
Save picture- not work, oscilloscope report "save complite", but usb drive is empty. :(
offtop..and in the next lesson we'll learn the difference between "gay" and "guy" ;D
Gays, with you, i learn English :)
Or did I miss something? Tinhead, you? :-*
..and in the next lesson we'll learn the difference between "gay" and "guy" ;D
and here as mentioned above my version of the 2.06.3 110909 (110908) firmware
wtf .. only 10 download?
Don't worry, this will not break your scope (and if, you will get new one from me), it will make it faster!
Yes, that's is. Maybe I don't get the point of diplay Dots feature in Hantek/Tekway, but when I select Dots, I want to see real samples, not the "dotted line". So this doesn't work. If I sample at 20ns timebase (it says 800MSa/s), stop the acquisition and "zoom" timebase to 2ns, I see interval between points of 500ps which would corespond to 2GSa/s of sampling rate ;) If initial timebase is 8, 4, or 2ns, interval is even smaller. So if the display Dots doesn't mean it will show you real samples, what is it good for?3. Display Dots doesn't work in 2ns and 4ns timebasehmm, you mean when you enable dots, go to 4ns/div and stop you can't see any dots when
you go to 2ns/div ? Well, they are there, believe me. Even in 2ns/div when you stop they are there,
the point is, you always see interpolated dots between, when you would be able to zoom more
(like now from 200us/div to 20ns/div) you wil see them, but let me show you that on attached picture .
What on the picture is firmware with 200ps/div timebase, i did stopped acq. while in 4ns/div
and switched over to 200ps - and bingo, you can see all these points there.
When the interpolation would be really swichable on/off you would see only the real sampled dots
and not the interpolated between, but it is always on. How this looks like ?
Well, check another one picture, this is fw with interpolation off (2ns/div and stopped acq.)
So if the display Dots doesn't mean it will show you real samples, what is it good for?
In one Tektronix (old) digiscope have very nice feature.
If use Sin(x)/x then can select "highlighted" real sample dots.
(of course always can select display dots. In this mode it do not make any calculated "joke" dots. In this mode every displayed dot is just real sampled dots as is. .... Yes I know.. it have been expensive scope. So I do not compare but today these kind of things maybe more easy to implement.
Also one note. Old times these leaders did not afraid publice full documents. Schematics, all details with thousend of sides expalanations in theory and practice. All test and calibration details... everything. They did not afraid as chinese or japanese.Everyone can copy...yes. Is it problem. NO. Becouse one secret thing. Quality is difficult to copy! This is key point!
Also after the recent fw upgrade - the official Hantek + tinhead's one I noticed that the update speed drops significantly when tune the scope to ranged > 20 milisecs. Any idea?
Hello
Today i got my Hantek DSO5102B ;D
Is the Hack to update to 200Mhz still working?
Hello
Today i got my Hantek DSO5102B ;D
Is the Hack to update to 200Mhz still working?
Can the Tekway DST1062B (Hantek DSO5062B) be hack to become Tekway DST1202B (Hantek DSO5202B) from 60MHz to 180MHz (200MHZ)? I would like to order this model if it is hackable.
-Which Operating System to use (prefer to work with Windows, not familiar with Linux)?: Windows or Linux
-Do I have to modify any hardware?
-Do I have to roll-back the firmware to peform the hack? if so, which firmware version?
-Which utility softwares are used to dump/update the firmware? What is the latest working hacking tool version to use? What is the best hacking method to use for the Tekway DST1062B (Hantek DSO5062B)?
-Which I/O output (Jtag, USB, UART) is recommended for dump/update/backup the firmware? I can solder the missing I/O
connector if needed, so long as it make the hacking process easy.
-Do I also need other special equipment/cable to do the hack?
you mean probe check? I cant find it ! What buttons do I need to push to view this bar?
Im also having a LCD contrast problem I didnt had with 110531.1, contrast resets to minimum on every power-up, is there any workaround? (I have original HW 0x555583e8)
The contrast is a bug, 110909 firmware is fixing it (partialy, because you have to set value <>8 to get saved),
the actual firmware 110923.1 is fixing it complettly.
Probe check is another button, after nearly 2yrs i still don't know what the real purpose of that button :)
Force trigger is useful when you've set the triggering to normal, which makes the scope wait for a trigger before acquiring the signal. By pressing force trigger, you can see the signal (eg. why is it not triggering) without changing triggering settings.
the yellow bar ist standard in the firmware, it pops-up when you push AutoSet button AND when the signal has been identified as square/sinus.
There voltage AC ground
Try this. Hantekway uses common use HighVoltage capacitor (2kV), but its not rial Y-capacitor, which with certification behavior (low leakage and with overvoltage failure mode is break, not shorted, like common use ).https://www.eevblog.com/forum/index.php?action=dlattach;topic=1571.0;attach=16386;image (https://www.eevblog.com/forum/index.php?action=dlattach;topic=1571.0;attach=16386;image)
Try this. Hantekway uses common use HighVoltage capacitor (2kV), but its not rial Y-capacitor, which with certification behavior (low leakage and with overvoltage failure mode is break, not shorted, like common use ).
Good y-cap should be covered with icons, certificates for which it was tested
I am so glad that my photo to someone needed! :)
In DSOs produced for international market you will find proper Y caps, see attached picture.Nice macro ! :)
as some ppl asked for, here the latest firmware (110923.1)...
i have the DSO5102B
I am surprised is that I use 220V isolation transformer, isolation of the grid, but the phenomenon remains
As the frequency or voltage is not normal, to line voltage of about 30V.
which is the reason why the update fail,
which is the reason why the update fail,
step 8, error 0xfb. Failed to decompress upgrade file. >:(
Checking on 2 different USB storage. :'(
oh maybe file got broken, which one you tested?
oh maybe file got broken, which one you tested?
for Hantek 5102.
tinhead, I download file 6 time, and its definitely different files.
files have different lengths. Upload files in "raw-format" is not good idea, More better in common archive, to test the integrity of the file in standard Windows/Linux PC.
file was broken, uploaded it again, check list on previous page
I mean file for DSO 5202B
length 2 549 266 byte,
MD5 generated by Total commander 7.55
fe93c083c614353257871b7559c68a83 *dst1kb_2.06.3_15202b_fact(110923.1).up
and it work.
as some ppl asked for, here the latest firmware (110923.1) for
Tekway DST1xxxB
http://hotfile.com/dl/133482275/8da8e64/dst1kb_2.06.3_01202b_fe(110923.1).up.html (http://hotfile.com/dl/133482275/8da8e64/dst1kb_2.06.3_01202b_fe(110923.1).up.html)
as some ppl asked for, here the latest firmware (110923.1) for
Tekway DST1xxxB
http://hotfile.com/dl/133482275/8da8e64/dst1kb_2.06.3_01202b_fe(110923.1).up.html (http://hotfile.com/dl/133482275/8da8e64/dst1kb_2.06.3_01202b_fe(110923.1).up.html)
Hi Tinhead,
I received the following error message when I used the above file to update via the USB memory stick: "Software upgrade failed, error 0xf7 illegal upgrade files detected".
My Tekway is:
Model: DST1202B (Has been upgraded from 100MHz).
Soft/Version: 2.06.03 (110118.0)
Hard Version: 0x555583e8.
Thanks for your help,
RFman.
this happens when the company name (tekway) or model name (dst1202b) are with cap letters in logotype.dis
or when there is no CR at the end of the line. You should fix that because every org. update will fail,
however for now see attached special version which is not checking these things
http://hotfile.com/dl/134086905/54cd538/dst1kb_2.06.3_01202b_fe(110923.1)_special.up.html (http://hotfile.com/dl/134086905/54cd538/dst1kb_2.06.3_01202b_fe(110923.1)_special.up.html)
(MD5 check sum is c0d05af7c91f2cd2c552e7a908f10aff *dst1kb_2.06.3_01202b_fe(110923.1)_special.up )
I wonder if it would be better if I correct the necessary files and that would then allow me to use the normal upgrades which I guess would also include Teckway updates. Am I correct in saying this.
I have already purchases a USB serial interface to allow me to get into the Linux operating system. This should allow me to correct the required files.
But I need to know what to fix in each file and some extra instructions as to what program I need to use to modify the files. Or maybe I can just copy the correct files? I'm no expert in Linux :(.
I wonder if it would be better if I correct the necessary files and that would then allow me to use the normal upgrades which I guess would also include Teckway updates. Am I correct in saying this.
yeah, it is better.
I have already purchases a USB serial interface to allow me to get into the Linux operating system. This should allow me to correct the required files.
But I need to know what to fix in each file and some extra instructions as to what program I need to use to modify the files. Or maybe I can just copy the correct files? I'm no expert in Linux :(.
you don't have to be an expert, all you need is to connect over uart to the linux shell, once you in only few files need to be
probably edited (with vi editor), that's simple steps.
So, now back to the "update" script
[cmd] rm /dst* -rf
[cmd] touch /dst1202b
<- here the model file will be deleted and created again. This file is the magis one for the bandwidth hack
[cmd] rm /logotype.dis
[cmd] mv /usr/up/tekwayup_client/logotype.dis /logotype.dis
<- and here the logotype.dis will be deleted and new one will be copied to root fs of the DSO.
Now what you have to know is, exactly here the firmware is checking the Brand (which might be hantek or tekway)
and the model - for Hantek DSO5062B, DSO5102B, DSO5202B and for Tekway dst1062b, dst1102b, dst1152b, dst1202b.
There are of course Tekway dst4xxxb and dst3xxxb models (as well Hantek N/C series), but i don't care abotu them
as we speek here about 1GSs models.
The firmware is checking then following
ucUpdateBrand = ucSysBrand ?
ucUpdateType = ucSysType ?
if not you will get an error 0x7f
ucSysxxx are read from the logotype.dis of your DSO, usUpdatexxx are from the firmware update file itself
This has been implemented to prevent people from running a wrong update (model, manufacturer - so not only hack protection)
However, in case you update file contains an empty file named "special" (/usr/up/tekwayup_client/special)
exact this update step will be not execute - so you can update from Hantek to Tekway or from whatever model to another one.
Hi again,
Forgive my stupid question but does the Hantek has the option to save the data from the screen or the memory to a CSV file ?
If does not isn't possible to handle this some how from the shell, I know the hardware calibration puts down the the volts of the captured sourse to a text file. Is there any hole we can use for capturing to CSV file.
CSV file is very useful for creating excel sheets and diagrams but mostly for calculatng the power of impulse and so on.
Uhm ::) ... Thanks!
I was searching the Hantek manual for CSV keyword and haven't luck. Thanks for helping the fool.
maybe someone of you here have a bit of spare time and can try to identify these still unknown components:
SOT23-3, part marking SCJG, pinout 1-VCC, 2-Vout, 3-GND
- this is voltage ref. used in hw1007 instead of LT1790-4.096V
Diodes Inc AP7313-15SR seems to match, in terms of package marking,
but the SR is a reversed pinout (to the more common 1=ground organization).
Output is 1.5V.
Maxim MAX6145EUR-T matches pinout and voltage, no sign of SC marking code
Could match some of the precision shunt lines, like LM4040 etc
These folks suggest SCxx is a Microchip marking prefix (handy site BTW, good job to the team that runs it!):
http://chip.tomsk.ru/chip/chipdoc.nsf/vc1 (http://chip.tomsk.ru/chip/chipdoc.nsf/vc1)!readform&view=smd&cat=S&start=501&count=500
If so, it might be the MCP1541, which matches voltage output and pinout.
TI REF3040 series may also be a match
ECL -K
Tinhead, you write that you have seen several makes of DSO5000. My board is green. Unfortunately, my model is different from the one for which you published complete schematic. The board I have (hardware 10070x55553e8) has the routes and holes for the Ethernet (RJ45) socket. I have a suspition the main board has all the routes for the Ethernet CS8900A-based
controller. It only needs soldering the RJ-45 and CS8900A chip. Is this true?
Hi, folks, I'm been away for some time, but now I'm back :)
So, I have two questions/requests for now:
1) tinhead could you upload your improved English.lan as a plane file, so ppl, having UART can update without using fw updating procedure?
Hi benkev
the issue 1, 2, 3 belongs together, they actually not an issue / bug / error.
As soon "something" is connected to the Samsung SoC (S3C2440) UART, the bootloader might stop with the Tekway > prompt, this is because
the bootloader picked up "any character". The best solution is probably pull up / pul down (i don't remember exactly, what i remember someone tested it here) ...
...I'm working (in spare time) on the hw1007 schematics (this is the latest hw revision and exactly what you have), it will be ready before christmas :)
The Ethernet chip on hw1007 is DM9000EP, the unpopulated parts on main pcb are for an combination of rs232/LAN, however some are placed (well supposed to be)
on a separate small pcb connected to the i/o port. You will see the details as soon i published the schematics.
In principle you can use the CS8900A too, but of course then you will have "only 10mbit" instead of 100 with DM9000EP and of course you will have to re-design the PCB which i posted some time ago (as the i/o port pinout has been changed since hw1005)
(3) Since I do not have the 2mm pitch female headers or connectors, I had to simply solder three wires to the onboard UART pins: GND, TXD, and RXD. The three wires with 2.54 (or 100 mil) connector now stick out from the back panel. They are always available for connecting to the CP2102 adapter. Can the wires cause such misbehaviour?
tinhead,
sorry for my silly question (2.), I was tired :)
Could I test it on my Tekway DST1102b ( converted to 200Mhz of course :) ) ?
which is the reason why the update fail,
step 8, error 0xfb. Failed to decompress upgrade file. >:(
Checking on 2 different USB storage. :'(
1- there is really no space on NAND (which i doubt, but who knows, maybe too many broken sectors)
Check that, do df -h on the shell
2- the firmware update file you downloaded is corrupt - check the MD5 checksumI unarchive file on USB storage manualy on PC, end after look #1
A corrupt file can't be unpacked and it's causing memory overflow error, which might result as "no space"
I have a Hantek 5102 with hw1005, sw 110229. I have made no modifications to it.
I just started using it and have a few questions.
1. The SINGLE SEQ button is translucent just like the RUN button, is it suppose to light up as well?
2. Setting the Verticle resolution knobs (either channel) without probes connected, I see 200 mv of ripple at 50v, rotating the knobs to 50mv, I would expect the noise peaks to increase in size, like on my analog scope, however the ripple drops to 1.8 mv, this seems strange to me, is this normal for this type of scope?
3. I was going into various menus and the screen froze, it would not respond to any other button presses, stuck on displaying channel 1 setup. I powered down and back up attempting to duplicate the problem, pushing various buttons, but not rapidly. Pressing Channel 2 caused it to freeze again, I rebooted again to unfreeze it. So now I determined that pushing Channel 1 then Channel 2 and back to Channel 1 then Channel 2 with about 5 seconds in between presses would freeze the screen. The 4th time I rebooted, I pressed Default Setup before it froze, since then I have not been able to duplicate the freeze problem. Unfortunately, I didnt think of recording any of the settings prior to pressing Default Setup. :-\ Has anyone else experienced this problem?
I'm not sure if I have a newer formware (111122) than anyone else has?
There still seems to be a couple of bugs when changing horizontal timebase in some modes.
Minor display bug;
press; Acquire->Equ-time
then MemDepth is greyed out like it is disabled, but still allows memdepth selection.
Function bug;
press; Utility->page3->Filter
the filter does NOTHING at all! No change in waveform or amplitude for any filter type setting or any filter Hz setting. This is disappointing, it almost looks like they disabled the filter completely but left the filter menu working!
The filter can be turned on, and then some other options stop working, like it is not possible with filter on to set Memdepth in Acquire!
It is disappointing that the filter does not work, it would have been very nice to be able to add some low-pass filtering to reduce HF noise on the waveform.
TTScope problem;
I use Win98, and have not been able to successfully set up the drivers for TTScope.exe. I put the drivers in c;\windows\system32 but no good. Also windows cannot auto detect the drivers it keeps looking for a driver file but not able to find it, even when I tell the exact location of the file.
Hope my Hantek (near 6 Months old) will not get away.
...yes, i have 111124.0 and 111202.0. If you don't mind make a backup of the 111122.0 and send me PM
with download link (I'm collecting versions to track changes)...
Minor display bug;
press; Acquire->Equ-time
then MemDepth is greyed out like it is disabled, but still allows memdepth selection.
this is not a bug, these scopes have in Equ time mode only 4k samples, see user manual
Thank you very much Tinhead for responding to my post. :)...yes, i have 111124.0 and 111202.0. If you don't mind make a backup of the 111122.0 and send me PM
with download link (I'm collecting versions to track changes)...
Sorry I don't know how to do that. Is there an easy way to do it without opening the case or needing to solder to the PCB and get a USB/uart?
My workshop PC runs Win98 and needs the older support for parallel ports etc that only Win98 can provide. I also have some high speed Dos software which needs Win98. :)
Now my question? Which software upgrade would you recommend?
Thanks a lot for your help.
Hi all,Me too!
This is my first post here. I skimmed this tread with 68 (!) pages and I can find it very interesting.
My intention is to buy a Hantek DSO5062B (60Mhz), I've seeing the mod for Hantek at 100 Mhz, but not for this one. It can be done, can I use the same way?Based one of the posts in the middle, Hardware in the 60mhz = 100mhz = 200mhz (almost). All can be updated through TTL level UART connection in the same manner. (Instructions in first post). The input stage has a few resistor and compensation differences for the various units, so the 60mhz model only gets up to around 185mhz bandwidth.
Owon 25Mhz can be modded? Can somebody share his experience?
Note: 'latest' firmware links on the first post could be updated, whenever is convenient.
I just ordered the 100Mhz version recently over the comparative (and slightly cheaper) Rigol DS1102E based on it running linux and being able to update / improve the hardware to do more than advertised. However, I don't think I'llmolestopen it right away to get to the UART until it's a ways into the warranty (or the SDK is released and labview connectivity is closer to reality), whichever comes first...
Dim HackBytes As [Byte]() = {&H43, &H18, &H0, &H11, &H6D, &H76, &H20, &H2F, &H64, &H73, &H74, &H31,
&H31, &H30, &H32, &H62, &H20, &H2F, &H64, &H73, &H74, &H31, &H32, &H30, &H32, &H62, &HD0}
DSOIP = IPAddress.Parse("1.2.3.4")
DSOPORT = "9966"
udpClient.Connect(DSOIP , DSOPORT )
udpClient.Send(HackBytes , HackBytes.Length)
It should be ready by tomorrow evening if the windows USB api is working as expected.
usb_set_configuration(handle,1)
usb_claim_interface(handle,0)
before you do usb_bulk_write.The (messy, ugly) source code is attached. (VC2010)
Maybe you can post your updated source code.
Or, if the hack is working for everyone, link your/my binary in the first post so people do not have to open their scope's cases.
Hello
I have a DSO5102B HW 10070 SW 111124.0. Can I also use the USB Updater?
Greets Christoph
For a custom PC software, I would stick with libusb ...
Okay. Can't this be derived from the TTScope decompilation?
signed __int64 __cdecl CalcVoltBase(signed int a1, int a2)
{
signed int v2; // ecx@1
signed __int64 result; // qax@2
float v4; // [sp+Ch] [bp+4h]@3
v2 = a1;
if ( a1 == 1 )
{
result = 2 * a2;
}
else
{
v4 = 2.5;
if ( v2 % 3 != 2 )
v4 = 2.0;
result = (signed __int64)((double)CalcVoltBase(v2 - 1, a2) * v4);
}
return result;
}
double __cdecl CalcVoltBaseEx(signed int a1, int a2, int a3, int a4)
{
signed int v4; // ecx@1
double result; // st7@3
int v6; // edi@7
int v7; // eax@8
float v8; // [sp+8h] [bp+4h]@5
float v9; // [sp+10h] [bp+Ch]@8
v4 = a1;
if ( a1 == 1 )
{
if ( a4 == 1000 )
{
*(_DWORD *)a2 = 1;
CString::Format(a3, "%s", dword_10012174);
result = 2.0;
}
else
{
*(_DWORD *)a2 = 2;
CString::Format(a3, "%s", dword_10012178);
result = (double)(2 * a4);
}
}
else
{
v8 = 2.5;
if ( v4 % 3 != 2 )
v8 = 2.0;
v6 = a3;
result = CalcVoltBaseEx(v4 - 1, a2, a3, a4) * v8;
if ( result >= 1000.0 )
{
v7 = *(_DWORD *)a2 - 1;
*(_DWORD *)a2 = v7;
v9 = result * 0.001;
CString::Format(v6, "%s", dword_10012170[v7]);
result = v9;
}
}
return result;
}
@patz:
Is it possible to add an option to your software which allows me to change back to the 1062b and not only one way to 1202b?
best regards
Johannes
I'll be posting instructions and some .ko's in the next few days.yeah, you asked a day or two ago about kernel version of these DSOs, it is 2.6.13, these new models (which will support LAN)
Now just need to figure out how to make this setup sustain reboot.
/bin/hostname -F /etc/sysconfig/HOSTNAME
/nethack.sh start ; sleep 1
/dso.exe
@tinhead: Hello, what were the problems you encountered using the hantek DSO5***?
Right now the only problem is the seller of the hantek, it does not look very confident. I worried about the warranty if anything should happen to the scope.
Hi,tinhead !
What the option in new firmware "Bode asistant" (open|close, default- close, not changeable ) and "Video" (gray, not active) ? :o
Hi all,
maybe it's not the right place to post, but I do not where else:
my Tekway dst1062b hangs (latest firmware). After restarting it still hangs and the screen come up, but the device is not reacting on any key or so, the UI is there, both channels activated, RUN/STOP is green but not reacting at all. and idea how to resovle this (before connection to UART again...)
Thanks
D
Sorry to missuse the thread.
anyone else with the same problem?
Maybe one thing, when ou reboot your scope, everything works again ?no, it does not work unless I remove the params. then it boots correctly. the DSOreboot tool does not work for me, tried a few times...
QuoteMaybe one thing, when ou reboot your scope, everything works again ?no, it does not work unless I remove the params. then it boots correctly. the DSOreboot tool does not work for me, tried a few times...
but all other stuff seems to work well like video signal messureing. that's really odd...
since I own the DSO few days I am thinking about to ship back. but then I need to revert all the changes (-> 200mhz).
I've been following the thread, I've got a really early DSO1102B handheld scope with firmware 2.01.1
None of the hacked firmware I can find will work with it! It all saysx for 2.5-2.6 etc.
I got it from China when they were first released. Can anybody run me through how to hack my device to 200mhz or point me to a link?
Even Hantek doesn't have firmware on their page so I can't update the device.
Hello,
I have a problem with my Tekway DST1062B - the scope hangs with white screen after running for about 30 seconds to 30 minutes. I have tried upgrading the factory firmware to version 2.06.3 (111202.0) - no change. I have not tried to hack the scope yet.
Hardware version shown is 10050x555583e8, serial number T 1G/005 003613.
Do you have any advice? Thank you!
Ivo
Hello,
I have a problem with my Tekway DST1062B - the scope hangs with white screen after running for about 30 seconds to 30 minutes. I have tried upgrading the factory firmware to version 2.06.3 (111202.0) - no change. I have not tried to hack the scope yet.
Hardware version shown is 10050x555583e8, serial number T 1G/005 003613.
Do you have any advice? Thank you!
Ivo
For now in Elec3i, we are promoting hand-held DSO1102B/DSO1062B
I recently bought a DST1102B for my hackerspace and few ppl have used recently. After their use (sampling/recording/etc) the oscilloscope is freezing, randomly. Really randomly.
On my own opinion, I think there is some broken samples still remaining on the file system, cause when I do a "df" on the debug console, I got :
Filesystem 1K-blocks Used Available Use Mount
/dev/root 63152 63152 0 100% /
I would like to know :
- Where are recorded the samples before recording them on an usb key ?
- Is it normal to have the root filesystem used at 100% ?
- Have you ever met this problem before ?
Unfortunately I had the same problem as djeans, my scope locked up at the weekend.
I tried the reset tool over USB but that did not work.
From a earlier post
remove the /param/sav/run* and /param/sav/run*
arent these two the same ? Or am I missing something.
it seems to be issue with the latest models (what is your version in system info->hw? 555583e8 or 83e9 ?)No, this behaviour can also be found on oldest versions (0x10050 555583e8) !
Quoteit seems to be issue with the latest models (what is your version in system info->hw? 555583e8 or 83e9 ?)No, this behaviour can also be found on oldest versions (0x10050 555583e8) !
However I upgraded it to 111226 two weeks ago and it started locking up again !
BTW I didnt notice that the header is a 2mm pitch until I tried to plug in my 0.1” lead, and am I right in assuming that the uart is 3.3V ?
it would be helpful if all the firmware Updates are for example on the first page.
Hi
I just receive my DSO5102B
First I change it into DSO5202B and everything works great. Thanks for great job with reverese engineering.
Now I have a HW 10070 of PCB and there is a space on it for RJ45 for LAN and I wonder if it is possible to just add this connector and enable this option in firmware???
sobomax :
I think I have looked everywhere but I can't seem to find your network adapter supported list. :(
Also, any code updates ?
@patz:
Is it possible to add an option to your software which allows me to change back to the 1062b and not only one way to 1202b?
best regards
Johannes
Hi,
should be possible, I'll have a look at it ASAP.
Hi,
it works! Communication is done through the official USB driver.
I attached the first version as EXE file. Use at your own risk!
(https://www.eevblog.com/forum/index.php?action=dlattach;topic=1571.0;attach=18664)
Some feedback if it is working would be nice. Tested with Hantek DSO5102B.
I just took patz' sources to turn my Tekway DST1062 into a DST1202.
as mentioned at the beginning of this thread for manual hack you need to change not only the
- After I changed the bandwidth, TTScope identifies the scope with the new bandwidth, and I may switch to 2ns timebase, but the scopes system information still reads dst1062b.
Is this the suspected behaviour?
- Unfortunately I don't have a adequate source to check the actual bandwidth, thus I just "listened" to some USB communication to get an idea of it (poor thing, I know).
The rise-time improvement was from 5,7ns to 4ns (3.7 at best, 61MHz -> 95Mhz)
Now I'm considering my probes.
Pinsonne offers three different accessories probes. One for each bandwidth, but they all seem to be identical.
Of courxe I have only the 60MHz version.
http://www.pinsonne-elektronik.de/pi10/pd111.html (http://www.pinsonne-elektronik.de/pi10/pd111.html)
http://www.pinsonne-elektronik.de/pi10/pd108.html (http://www.pinsonne-elektronik.de/pi10/pd108.html)
http://www.pinsonne-elektronik.de/pi10/pd107.html (http://www.pinsonne-elektronik.de/pi10/pd107.html)
Do you have any experience, which bandwidth you could reach with the original probes?
- How did you test your improvements?
Did you take the original probes or something different?
@Tinhead, how did you manage to reverse engineer the schematics? Looks like a very difficult task,well it is dificult, but everything is just question of time and/or knowledge.
did you have to depopulate the board first?
Or did you use a buzzbox method?sure, when possible or no other way available
What tools are used?Continuity checker - it must be always a good one (low voltage!!!). Everything below 0.7V is ok,
Is it possible to leave the board populated and achieve good results?
So, I finally have a question of my own. Hope this is the right place for it.
Would it be possible to put a custom boot screen in place of the default?
You know when you turn it on it has "the Screen" that shows brand and model.
sure, just build your own logos and replace the corresponding files in /logo directory on DSO
Format of these files (they not icon files, only named like that) is something raw 16 or 8 bit RGB,
i did played a time ago with that, don't remember exactly the values now.
Hello again,
Thank you for all your help thus far.
Ok I'd say I have a pretty good/basic grasp on the linux commands required to navi/edit in PuTTY via usb-TTL adapter (Been late night Cramming Like the days of Ole')
So I'm still playing with the custom logo's, right.
Reading everything I can find but I'm having problems in one area particularly.
I feel down right "DUMB" for having to ask such a noob question and it is probably stupid easy and I'm just over looking it but,
How do I transfer the logo files from the oscilloscope to my Pc or the other way around, my newly created logos from the pc to the oscilloscope.
One thing I realized on the Conrad page:it is physicaly 1GSs device, it does have the same PCB, same amount of ADCs, actually everything is the same as for
As they say it is a 500MS/s scope, wouldn't that mean this stupid equivalent sample rate would be halved, too? But it still says 25GS/s.
Just one question:
"Is" it the 1GS/s version, or do I need to hack it to be 1GS/s? How do I proof or measure this? Were do I have to hook up my LA for timing measurment? ;)
Any way to identify it's the right model/hardware?
well, create bmp and convert it with tool like Img2Lcd.exe to bin. There are many tools like that,"
good starting point is to search for "FriendlyARM S3C2440 boot logo tools
A quick look into a .ico file tells me it is rather primitive. It starts with two 32 bit numbers, giving width and heigh (or hight and width) of the image in pixels. Then follows what looks like 1 byte per pixel data, indexing into a colour pallet. The colour pallet, however, is not part of the file. It is likely hardcoded in the software that reads the file.
Nice detail in Conrad:
1062C 60MHz in text but in picture front panel read 100MHz (and this 500MSa/s and oh yes also it is exactly true. It is 500MSa/s maximum! If it is used with 2 channel so, there is not anything exactly wrong, also becouse 60MHz model real -3dB point is around or just over 100MHz.(without any mod ) ;) :
Nice detail in Conrad:
1062C 60MHz in text but in picture front panel read 100MHz (and this 500MSa/s and oh yes also it is exactly true. It is 500MSa/s maximum! If it is used with 2 channel so, there is not anything exactly wrong, also becouse 60MHz model real -3dB point is around or just over 100MHz.(without any mod ) ;) :
but you know that this is bullshit - typical what you will see on enclosure is the max max max value :)
I got firmware back from such Conrad DSO - 100% 1GSs Hantek model, even better - it was originaly DSO5202B ...
You mean that also HW is with 5202B components related to BW.
If this all, meybe Conrad have busy days for ship all purchased 3062C's
I do not know what is shipping price for other countries.
(maybe they close this offer soon..... )
How are you looking at it!Converted to a hex-dump, then just scrolling through it.
if I open it in notepadExcuse me while I vomit.
Can you pick one and possibly give an example.The first two 32 bit numbers are obvious, because there are many zeros in the first eight bytes. Multiplying the values from the first two 32 bit numbers happens to give the file size minus eight.
So if it's pretty primitive what do i have to do to edit/make one?
hi,
what can i do if i have this problem ? whithout installing this patch before ?
i have last firmware.
thanks.
marc
few people have mentioned that the especialy last 2 firmwares 2.06.3 (111226.1) and 2.06.3(120112.1)
when crashing they damaging the setup file (/param/sav/run1kb*).
walt,
I quickly compiled (based on the already here posted USB hack tool )
a DSOExec tool. It will in principle execute every command you type in edit box on the DSO.
so let say to cleanup /mnt just type rm -r /mnt/* and you ready.
[root@Tekway-dso /]# ls -lh /mnt/
total 13507
drwxr-xr-x 1 root root 512 Dec 28 22:04 tekway0_1
drwxr-xr-x 1 root root 512 Dec 28 22:07 tekway0_2
drwxr-xr-x 1 root root 512 Dec 28 22:09 tekway0_3
drwxr-xr-x 1 root root 512 Dec 28 22:27 tekway10_11
drwxr-xr-x 1 root root 512 Dec 28 22:28 tekway10_12
drwxr-xr-x 1 root root 512 Jan 4 21:27 tekway13_1
drwxr-xr-x 1 root root 512 Dec 28 21:41 tekway7_1
drwxr-xr-x 1 root root 512 Dec 28 21:41 tekway7_2
drwxr-xr-x 1 root root 512 Dec 28 21:42 tekway7_3
drwxr-xr-x 1 root root 512 Dec 28 21:42 tekway7_4
drwxr-xr-x 1 root root 512 Dec 28 21:43 tekway7_5
drwxr-xr-x 1 root root 512 Dec 28 21:43 tekway7_6
drwxr-xr-x 1 root root 512 Dec 28 21:45 tekway7_7
drwxr-xr-x 1 root root 512 Dec 28 21:53 tekway8_1
drwxr-xr-x 1 root root 512 Dec 28 21:54 tekway8_2
drwxr-xr-x 1 root root 512 Dec 28 21:56 tekway8_3
drwxr-xr-x 1 root root 512 Dec 28 21:57 tekway8_4
drwxr-xr-x 1 root root 512 Dec 28 21:59 tekway8_5
drwxr-xr-x 1 root root 512 Dec 28 21:59 tekway8_6
drwxr-xr-x 1 root root 512 Dec 28 22:00 tekway8_7
drwxr-xr-x 1 root root 512 Dec 28 22:00 tekway8_8
-rw-r--r-- 1 root root 5.0M Dec 28 22:11 tekwayRecord00.rec
-rw-r--r-- 1 root root 4.2K Dec 28 22:03 tekwaySetUp01.set
-rw-r--r-- 1 root root 4.2K Jan 4 21:28 tekwaySetUp130.set
-rw-r--r-- 1 root root 4.0K Jan 4 21:58 tekwaySetUp150.set
-rw-r--r-- 1 root root 4.2K Dec 28 21:59 tekwaySetUp80.set
-rw-r--r-- 1 root root 4.2K Dec 28 21:59 tekwaySetUp81.set
-rw-r--r-- 1 root root 4.2K Dec 28 21:59 tekwaySetUp82.set
-rw-r--r-- 1 root root 4.2K Dec 28 21:59 tekwaySetUp83.set
-rw-r--r-- 1 root root 4.2K Dec 28 22:02 tekwaySetUp90.set
-rw-r--r-- 1 root root 36.6K Dec 28 22:08 tekwayWaveData00.csv
-rw-r--r-- 1 root root 36.6K Dec 28 22:08 tekwayWaveData01.csv
-rw-r--r-- 1 root root 36.6K Dec 28 22:08 tekwayWaveData02.csv
-rw-r--r-- 1 root root 36.6K Dec 28 22:08 tekwayWaveData03.csv
-rw-r--r-- 1 root root 36.6K Dec 28 22:08 tekwayWaveData04.csv
-rw-r--r-- 1 root root 36.1K Dec 28 22:08 tekwayWaveData05.csv
-rw-r--r-- 1 root root 36.1K Dec 28 22:08 tekwayWaveData06.csv
-rw-r--r-- 1 root root 36.1K Dec 28 22:08 tekwayWaveData07.csv
-rw-r--r-- 1 root root 36.0K Dec 28 22:43 tekwayWaveData101.csv
-rw-r--r-- 1 root root 3.4M Jan 4 21:28 tekwayWaveData130.csv
-rw-r--r-- 1 root root 35.2K Jan 4 21:33 tekwayWaveData131.csv
-rw-r--r-- 1 root root 4.3M Jan 4 21:50 tekwayWaveData135.csv
-rw-r--r-- 1 root root 6.0K Jan 4 21:56 tekwayWaveData141.csv
[root@Tekway-dso /]#
So I followed your advice, and in /mnt/ I found :
As it seems to be a little weird for me, I would like to know what's the "normal" output of ls -lh /mnt/
why not make reset with pressed key at startup instead of putting USB key with good file ?
So I followed your advice, and in /mnt/ I found
Now you might ask why, well very simple. Look on the schematics, none of the keys are connected to
SoC directly (which would be great and piece of cake from coding point of view), they connected to FPGA.
I have not seen this problem mentioned on the forum, is it only my scope doing this ?
Just curious, has anyone tried hacking the 5102BM model? Supposedly, it is the same scope as DS5102B but with larger memory depth (2M one channel, 1M for 2 channes). Would the same hack work for this model? Thanks!
Thanks! tinhead. Yeah, I am interested in the BM model (for the larger memory) but they are a little hard to find.
The price quote that I got from a Chinese web-store (where else) was quite reasonable and the price was only about
10% higher than the regular B version.
@tinhead this is checked from sw 111026.1 that I sent You?
Regards,
Your vertical scale is 2V so the reading is correct
Are you looking at the 2.48V ? that is the trigger voltage
Read up or google, RMS, peak to peak and average
Your meter is probably reading average
Read up or google, RMS, peak to peak and averageThe meter is probably indicating RMS. Whether this is an actual RMS value or an approximation by multiplying the average absolute value by sqrt(2) depends on the quality of the meter.
Read up or google, RMS, peak to peak and averageThe meter is probably indicating RMS. Whether this is an actual RMS value or an approximation by multiplying the average absolute value by sqrt(2) depends on the quality of the meter.
http://www.mikrocontroller.net/attachment/136103/all_logos.zip (http://www.mikrocontroller.net/attachment/136103/all_logos.zip)
/fpga.exe w 40 2E8E
/fpga.exe w 41 0050
/fpga.exe w 41 0600
/fpga.exe w 41 0614 #VGA 1
/fpga.exe w 16 6af0
/fpga.exe w 17 30
/fpga.exe w 18 6af0
/fpga.exe w 19 30
/fpga.exe w 1a b010
/fpga.exe w 1b 30
/fpga.exe w 1c b010
/fpga.exe w 1d 30
/fpga.exe w 1e 6c10
/fpga.exe w 1f 30
/fpga.exe w 20 0000
/fpga.exe w 21 30
/fpga.exe w 22 D000
/fpga.exe w 23 30
/fpga.exe w 24 6c10
/fpga.exe w 25 30
/fpga.exe w 00 9900
/fpga.exe w 01 0000
/fpga.exe w 0d 1000
/fpga.exe w 13 1000
/fpga.exe w 2d 0
/fpga.exe w 2d 2
/fpga.exe w 42 1
/fpga.exe w 42 0
/fpga.exe w 2d 0
I got the voltcraft dso3062c yesterday from Conrad in the Netherlands. The unit was now only 269 euros. How low can you go?
QuoteI got the voltcraft dso3062c yesterday from Conrad in the Netherlands. The unit was now only 269 euros. How low can you go?
Do you mean exclusive VAT - or from a shop? Because when I look online at Conrad, the price is still € 299:
I found a file called test in the root of the voltcraft that intrigued me.Code: [Select]/fpga.exe w 40 2E8E
/fpga.exe w 41 0050
/fpga.exe w 41 0600
/fpga.exe w 41 0614 #VGA 1
/fpga.exe w 16 6af0
/fpga.exe w 17 30
/fpga.exe w 18 6af0
/fpga.exe w 19 30
/fpga.exe w 1a b010
/fpga.exe w 1b 30
/fpga.exe w 1c b010
/fpga.exe w 1d 30
/fpga.exe w 1e 6c10
/fpga.exe w 1f 30
/fpga.exe w 20 0000
/fpga.exe w 21 30
/fpga.exe w 22 D000
/fpga.exe w 23 30
/fpga.exe w 24 6c10
/fpga.exe w 25 30
/fpga.exe w 00 9900
/fpga.exe w 01 0000
/fpga.exe w 0d 1000
/fpga.exe w 13 1000
/fpga.exe w 2d 0
/fpga.exe w 2d 2
/fpga.exe w 42 1
/fpga.exe w 42 0
/fpga.exe w 2d 0
Does it mean something to you?
Including VAT and shipping. Every once in a while conrad sends out coupon codes for a 10% discount. At least they do in the Netherlands.
Ahh.... I see. I rarely ever buy anything from Conrad - they are normally much more expensive for electronics
Same here. If I need it quicky, I use farnell for their free shipping and next day delivery. Bargains come from china. But once in a while conrad suprises me, like now.
On 1M bench model two IS42S16160C-7TL(I) (http://www.issi.com/pdf/42-45S83200D-16160D.pdf (http://www.issi.com/pdf/42-45S83200D-16160D.pdf))
memory's are used. I assume two of IS42S16320b-7TLI (http://www.issi.com/pdf/42S16320B-86400B.pdf (http://www.issi.com/pdf/42S16320B-86400B.pdf)) are suitable replacement for 2M upgrade?
@mightyzen - Your report of the 10% off action at Conrad (NL/BE) has gotten me excited to pull the trigger on a Voltcraft (HanTekway) scope. I assume the scope came with 60MHz probes - did you buy another set?
The best buy I can currently find on a higher-bandwidth set is: http://www.reichelt.de/Tastkoepfe-und-Zubehoer/TESTEC-MF-312-2/index.html?;ACTION=3;LA=5;GROUP=D169;GROUPID=4043;ARTICLE=48467;START=0;SORT=user;OFFSET=16;SID=13T1D-mH8AAAIAAG3fMaI898a7da000ecbd08212a4af587f46bf2 (http://www.reichelt.de/Tastkoepfe-und-Zubehoer/TESTEC-MF-312-2/index.html?;ACTION=3;LA=5;GROUP=D169;GROUPID=4043;ARTICLE=48467;START=0;SORT=user;OFFSET=16;SID=13T1D-mH8AAAIAAG3fMaI898a7da000ecbd08212a4af587f46bf2)
Does anyone know of a better deal?
Search eBay for "PP-200", they're about 12-15 Euros plus shipping/customs from China.
Thanks for the great tips everyone! ;)
@Spawn - one question about your cheap probes - how soft is the 1x/10x switch? When I had the Rigol DS1052E, I found that I was constantly accidentally changing the probe switch without realizing it (until later).
Place a rubber band on the shaft, it will keep it from moving unless you do so purposefully. If you have orthodontic rubber bands, they are the right size [like you know someone who has braces], you can also add them to any probe to help improve its grip while being electrically inert. If colored you can also use extras to color code your cables, unlike the color bands many probes ship with that easily fall off; I use colored zip ties to color mark cables as latex bands eventually degrade.
Mightyzen, you got me thinking too, I didn’t know the Voltcraft rebadged these and Conrad extended 10% till 3 april yesterday (I am subscribed to their daily news)
I am not in need in a DSO but the price is so low for 200Mhz scope and I can’t resist to get one...
Really big kudos to Tinhead
out of stock till 20 april
which worries me I am not sure which version FW we get if we buy one,
I don’t think Voltcraft will make a custom FW just for this scope but you never know.
For those using Linux, I did a quick Python script (using PyUSB >= 1.0) which lets you upgrade the scope from 60MHz to 200MHz (or other variants if you edit the script, see comments).
Migtyhzen, I got 2 scopes one 20 MHz dual channel and a 100 MHz dual channel with 4kb memory, but I can’t resist the price on this one right now, I think I just need a new toy and a nice digital scope with all modern capabilities. Well I got one more day to think about it and it looks like I am going to order one.
.... Care to share some details?
Tinhead! Kudos!
Now, there's a bug in the handheld I have fo
here: http://www.biasedlogic.com/index.php/hantek-dso1062b-dso1102b-dso1202b-vs-5gss-lecroy-waverunner/ (http://www.biasedlogic.com/index.php/hantek-dso1062b-dso1102b-dso1202b-vs-5gss-lecroy-waverunner/) I have put a few observations about triggering on tricky signals from LeCroy's "demo generator". There's also a comparison of 33MHz "square" wave image from the Hantek and from a 600MHz 5GS/s LeCroy Xi-series (Xi 660 I think).
here: http://www.biasedlogic.com/index.php/hantek-dso1062b-dso1102b-dso1202b-vs-5gss-lecroy-waverunner/ (http://www.biasedlogic.com/index.php/hantek-dso1062b-dso1102b-dso1202b-vs-5gss-lecroy-waverunner/) I have put a few observations about triggering on tricky signals from LeCroy's "demo generator". There's also a comparison of 33MHz "square" wave image from the Hantek and from a 600MHz 5GS/s LeCroy Xi-series (Xi 660 I think).
prosze bardzo :)
indeed, i can confirm the first bug (actually only the first part, i ddin't saw any trash on my display)
on 111212 firmware version. Btw, what is loaded on your handheld?
Not sure about second bug, sometimes it looks like what you said but sometimes it seems to be
just a bit delayed post-processing.
I did compared both handheld and bench versions, from what i can saw handheld
is having bit less jitter (pcb routing and new fpga design) and bit higher bw.
With active probes (and the /tst file hack to set bw filter higher) i got 250MHz -3db bw,
more than sufficient for 1GSs DSO.
"PP008 price", yeah, this is "the dark side of cheap scopes", a good set of probes costs
more than such DSO itself.
prosze bardzo :)
What's your mother tongue?
I have populated the DM9000EP along with a LF8505 magnetics (picked one from an old network card) and in the bootlog I see the driver picking it up. So far so good. I'm still missing a suitable jack, but I have ordered one that might fit, it just didn't arrive yet.send me PM and i will explain you how to make it working.
The scope menu shows network not supported, I believe this is configuration issue, do you have any details on this?
Is there any useful functionality available over the network interface BESIDES a console (which was reason enough for me to try the thing with a DM9000EP)?there is indeed full support in the firmware, you can use LAN to communicate like you do over USB - the full protocol is implemented,
Hello ,
I am new here and have an Voltcraft DSO upgraded to 200MHZ . All worked fine so far .
Now by looking at the Hantek home-page , I found an new Firmware 120224.0
Has anybody already experience with this version -repectivly what known bugs are fixed ?
Thanks for feedback in advance
Liebref
Few hours ago , I checked the online store from Conrad ; SURPRISE ! It does show the Voltcraft DSO 3062C "Sold out "
As the original delivery dates were already changed in the past from 20 April to 20 May , I guess somebody has stopped this offer .
Hello ,
Few hours ago , I checked the online store from Conrad ; SURPRISE ! It does show the Voltcraft DSO 3062C "Sold out "
As the original delivery dates were already changed in the past from 20 April to 20 May , I guess somebody has stopped this offer .
Guess they have figured out the real value of the offer :(
There are some other reasons why the Voltcraft DSO-3062C is no longer available
I started documenting my JTAG setup for the S3C2440 (basically I abused an old IDE cable and soldered directly to the PCB), and I also wrote a small OpenOCD config (which has been included upstream already).
http://randomprojects.org/wiki/Voltcraft_DSO-3062C#JTAG_.28for_Samsung_S3C2440.29 (http://randomprojects.org/wiki/Voltcraft_DSO-3062C#JTAG_.28for_Samsung_S3C2440.29)
JTAG seems to work fine, I'm currently dumping the NAND flash chip contents via JTAG (takes quite a while though).
I've also started playing with Barebox (will also test U-Boot later) and buildroot (for rootfs and cross-toolchain). Building a Linux kernel and flashing my own rootfs will be the next step.
My UART setup is also documented here:
http://randomprojects.org/wiki/Voltcraft_DSO-3062C#UART_2 (http://randomprojects.org/wiki/Voltcraft_DSO-3062C#UART_2)
For this, I used a standard FTDI FT232R-3V3 cable and some custom-soldered mini-addons to allow for the cable being removed later (if I need it for another project).
Also, if anyone is interested in more PCB photos, UART bootlogs, lsmod/cpuinfo/mtdinfo/etc., waveform comparison before/after the 200MHz hack, and such stuff: I've put some more photos and info on the randomprojects.org wiki, and more detailed photos of individual PCB parts / chips will follow.
Uwe.
QuoteThere are some other reasons why the Voltcraft DSO-3062C is no longer available
Huh? Would you please care to explain? This forum is a place of open exchange and dispersal of information.
i am not able to explain in detail at the moment other than to say Conrad as well as several other Hantek product distributors in the US have been made aware of GPL violations in the hantek products.
Quotei am not able to explain in detail at the moment other than to say Conrad as well as several other Hantek product distributors in the US have been made aware of GPL violations in the hantek products.
Hmmm... I don't really see how this could be related to specifically selling out the Voltcraft (rebadged Hantek) DSO-3062C - since the Conrad online site is still listing for sale ALL of the other Voltcraft oscilloscopes which are rebadged Hanteks.
Edit: I don't know how many Voltcraft scopes are rebadged Hanteks - but at quick glance, I recognize at the very least the 4 USB scopes as Hanteks.
i am not able to explain in detail at the moment other than to say Conrad as well as several other Hantek product distributors in the US have been made aware of GPL violations in the hantek products.
right, Hantek was refusing any GPL related discussion since 2years, on the other side they made a (let's call) mistake.
Their using WEEE number which is asociated with Conrad (WEEE DE28001718), not only on these "Voltcraft"
DSOs, even on Hantek handhelds (confirmed, have screenshots of that) or even recent Tekway bench DSOs
(not yet confirmed).
This means Conrad will be not able to explain it as "one time action, OEM products with no deep business relationship therefore
no chance to fulfil GPL", they know what Hantek is doing, and they selling re-branded Hantek devices (e.g. USB DSOs) since
years.
the conrad.de has removed all references, i suspect that the english site just hasn't caught up......
Quotethe conrad.de has removed all references, i suspect that the english site just hasn't caught up......
I'm looking at conrad.nl
Edit: Actually, I just looked at conrad.de - and they ARE still selling the Voltcraft rebadged Hantek USB scopes.
Quotethe conrad.de has removed all references, i suspect that the english site just hasn't caught up......
I'm looking at conrad.nl
Edit: Actually, I just looked at conrad.de - and they ARE still selling the Voltcraft rebadged Hantek USB scopes.
Edit2: Not only that, but they still list the following (but as sold out):
Jubiläumsangebot: VOLTCRAFT DSO-3062C 2-Kanal Oszilloskop, Digitales Speicheroszilloskop, Bandbreite 60 MHz , inkl. Tast »
Best.-Nr.: 122464 - 62
60 MHz Bandbreite
500 MS/s Realtime-Samplingrate, 25 GS/s equivalent
Tastköpfe inklusive
€ 299,00
Mengenrabatt
inkl. gesetzl. MwSt., zzgl. Versand »
ausverkauft
Quotethe conrad.de has removed all references, i suspect that the english site just hasn't caught up......
I'm looking at conrad.nl
Edit: Actually, I just looked at conrad.de - and they ARE still selling the Voltcraft rebadged Hantek USB scopes.
Edit2: Not only that, but they still list the following (but as sold out):
well, when you search for VOLTCRAFT DSO-3062C you will find "item deleted", however you might see
still this model on some subcategories. This is because their website is caching internaly items even
if they already removed from database -> when you click on such link you will get "item not found or removed".
Btw, these USB DSOs are not issue at all, they not using Linux. Only bench (and Hantek handhelds B series) are
covered by this GPL violation action.
Quotewell, when you search for VOLTCRAFT DSO-3062C you will find "item deleted", however you might see
still this model on some subcategories. This is because their website is caching internaly items even
if they already removed from database -> when you click on such link you will get "item not found or removed".
If you search VOLTCRAFT OSCILLOSCOPE, you see it in the list - but yes, the item page itself is deleted. Same as on the Dutch site.QuoteBtw, these USB DSOs are not issue at all, they not using Linux. Only bench (and Hantek handhelds B series) are
covered by this GPL violation action.
The whole issue seems stupid to me; but then again, I'm not a big believer in licenses, copyrights, patents, and other ancient forms of copy protection. They seem to mainly protect and benefit those with deep pockets.
I am curious as to how it's going to affect outstanding orders. I've had one of the Voltcraft scopes on order at Conrad for about 3 weeks now - I think I'll contact them tomorrow to find out what's going on.
I am curious as to how it's going to affect outstanding orders.
i am not a big fan of many types of copyrights and patents, however, i do expect that my contributions to open source projects such as the linux kernel be honored for the license i have provided the work under. if they can't play by the rules then they don't deserve to play......
Quotei am not a big fan of many types of copyrights and patents, however, i do expect that my contributions to open source projects such as the linux kernel be honored for the license i have provided the work under. if they can't play by the rules then they don't deserve to play......
Well, the problem is picking and choosing... it seems you have to have the whole mess - or none of it. As a visual artist and software programmer for over 30 years, I've created tons of copyright-able material - but I've pretty much lost faith in the system. The world market is a much different place today than when these protection systems were invented and developed - it's dominated by huge corporations that use these systems to create and maintain monopolies. It was corporations that had the ridiculous Copyright Term Extension Act passed in the US to further protect their 'products' - and at the same time, if you're an entrepreneur and you've created something that they really want - they will just steal it - whether it's patented / copyrighted or not.
Quote from: Spawn on April 02, 2012, 02:08:50 AM
out of stock till 20 april
don't worry about the date, anther container is already on the way from China to EU.
well i am 9 and 0 on wins against people violating the GPL with the linux kernel, and the folks at gpl-violations.org have much higher numbers than i do......
QuoteQuote from: Spawn on April 02, 2012, 02:08:50 AM
out of stock till 20 april
don't worry about the date, anther container is already on the way from China to EU.
tinhead - you mentioned in the above-quoted message of 2 April that another container of Hanteks was on it's way to EU - did that actually arrive since you posted?Quotewell i am 9 and 0 on wins against people violating the GPL with the linux kernel, and the folks at gpl-violations.org have much higher numbers than i do......
Well I'm curious what those 9 wins amount to. Money? Recognition? Removal of the violation? How much of your own time was invested? Sorry, but this doesn't prove very much.
Of course, there are examples of individuals/smaller companies taking on bigger companies or corporations that violate patents and copyrights - and winning a sizable settlement, etc. - but they are undoubtedly the EXCEPTION - not the rule. In most cases, the infringed party will end up spending as much or more money than is ever awarded. Gosh, just go look up the story of Tesla and Marconi to see the history of patent/copyright infringement by bigger entities in a nutshell.
you have to stand up for your rights or else people/companies will take advantage of them....
QuoteQuote from: Spawn on April 02, 2012, 02:08:50 AM
out of stock till 20 april
don't worry about the date, anther container is already on the way from China to EU.
tinhead - you mentioned in the above-quoted message of 2 April that another container of Hanteks was on it's way to EU - did that actually arrive since you posted?
i would not use the 120224.0, sure it does fix the "roll mode" bug, but it does have few new bugs.
Even Conrad removed this fw from their website. Soon there will be new version available, so just be patient.
Thanks to the hard work of the folks at gpl-violations.org and a coordinated effort against Hantek's distributors, all open source license code for the Hantek/Tekway DSO has been released:
http://ftp.gpl-devices.org/pub/vendors/Voltcraft/VOLTCRAFT_dso3000series.zip (http://ftp.gpl-devices.org/pub/vendors/Voltcraft/VOLTCRAFT_dso3000series.zip)
we will be dissecting and making it available from a github repo within the next few days.
thanks gpl-violtations.org!!
Thanks, just downloaded it. Either I have a bad download or some of the tar.gz files are corrupt !!
we will be dissecting and making it available from a github repo within the next few days.
thanks gpl-violtations.org!!
This are kernel and driver sources as well some tools (e.g. the fpga tool missing on Voltcraft DSOs).
For sure it is really nice to have these sources (regardless of GPL whatsoever thing), however don't forget
that the DSO code itself (FPGA , CPLD and ARM code) is not and will not be published as they
are Hantek / Tekway Intellectual Property.
Therefore the amount of "new DIY features" is reduced to only few things (like e.g. custom LAN)
You should also not forget that the firmware (ARM code) itself is checking the kernel version,
it need to be 2.6.13 or 2.6.30.4 - if not some features/the firmware will not work.
This are kernel and driver sources as well some tools (e.g. the fpga tool missing on Voltcraft DSOs).
For sure it is really nice to have these sources (regardless of GPL whatsoever thing), however don't forget
that the DSO code itself (FPGA , CPLD and ARM code) is not and will not be published as they
are Hantek / Tekway Intellectual Property.
Therefore the amount of "new DIY features" is reduced to only few things (like e.g. custom LAN)
You should also not forget that the firmware (ARM code) itself is checking the kernel version,
it need to be 2.6.13 or 2.6.30.4 - if not some features/the firmware will not work.
major performance issues
major performance issues
explain that point
i've counted seven spinlock issues that have already been fixed in newer kernels, as well as two atomic operations that are suspect. the root file system also has two processes that are zombies on startup and multiple issues with the init scripts. the usb host and usb slave devices drivers have _major_ improvements in new kernels that deal with errata about double buffering. the dma driver is missing work arounds for about a number of errata.
the whole kernel and root file system is a disaster. hantek should fire everyone involved in the development linux development of this device. in fact i plan to make to make it a case study on what _not_ to do for a commercial product.......
i've counted seven spinlock issues that have already been fixed in newer kernels, as well as two atomic operations that are suspect. the root file system also has two processes that are zombies on startup and multiple issues with the init scripts. the usb host and usb slave devices drivers have _major_ improvements in new kernels that deal with errata about double buffering. the dma driver is missing work arounds for about a number of errata.
hmm, so nothing really (maybe except dma driver) important for an DSO.
Usb is anyway 1.1 - even with quad buffering and kernel 25.765 will be still exact that slow
(or even slower due blowed up kernel), zombies or init script are not an performance issues - nobody really
care if DSO need a half second longer to boot (as it have anyway to warm up).
I really doubt that newer overblown kernel on a box with reduced resources with what so ever file
system used only to boot will make an DSO faster ^^the whole kernel and root file system is a disaster. hantek should fire everyone involved in the development linux development of this device. in fact i plan to make to make it a case study on what _not_ to do for a commercial product.......
maybe, but on the other side this firmware has been developed in 2008, released begin 2009 for testing and
end 2009 for production. At that time 2.6.13 was not that old (actually prefered version on many systems).
I do have here almost all firmware versions from the last years, and when i look inside it was already a chalange
to maintain and support all these versions.
The good things about new models (BM/BMV) - Hantek took the chance for a cut, they now based
on 2.6.30.4 and newer drivers (and usb slave is making me crazy on PC side ... double buffered=doubled issue)
Thanks to the hard work of the folks at gpl-violations.org and a coordinated effort against Hantek's distributors, all open source license code for the Hantek/Tekway DSO has been released:
http://ftp.gpl-devices.org/pub/vendors/Voltcraft/VOLTCRAFT_dso3000series.zip (http://ftp.gpl-devices.org/pub/vendors/Voltcraft/VOLTCRAFT_dso3000series.zip)
we will be dissecting and making it available from a github repo within the next few days.
thanks gpl-violtations.org!!
There is no force of law in any real case, and certainly not in China. China have the Chinese laws and regulations of China and China's laws are in force - and only them. The only way is not to buy them outside of China. And, it is unlikely anyone would want to practice.Agreed. Unless that Chinese company wants to have international sales, which Owon apparently does, since they struck a deal with Conrad. At that point the distributors will require them to comply with local laws, which apparently happened in this case. Few western companies will be willing to take the risk of being found responsible, so they'll request compliance or drop the product. Not exactly a good deal for said Chinese company, is it?
I want to see that these GNU dream ideologists go and try with some western company, example with Agilent etc..Plenty of cases against western companies, did you care to take even ten seconds to do research before starting off on a rant?
In reality, there is no legal way to force the manufacturer to comply with any of the paper which has no legal force, over the manufacturer.This comment is based on the large number of lawsuits being dismissed, and the fact that Conrad/Owon ignored this request and refused to release any source code? It's extremely rare for these cases to even make it to the courtroom, presumably because defendant's council does not consider the piece of paper worthless.
Conrad/Owon ignored this request and refused to release any source code? It's extremely rare for these cases to even make it to the courtroom, presumably because defendant's council does not consider the piece of paper worthless.
@rf-loop: WTF!? :oActually he does.
IMHO you seem to have little to no idea, what you're talking about... it's just ridiculous, not worth to go in any detail. ::)
Indeed, I confused Hantek and Owon. I saw your name and assumed it was about Owon.Conrad/Owon ignored this request and refused to release any source code? It's extremely rare for these cases to even make it to the courtroom, presumably because defendant's council does not consider the piece of paper worthless.
Why Owon need release any source code. How Owon is related to this case?
Hantek, no need release any source codes.
@rf-loop: WTF!? :oActually he does.
IMHO you seem to have little to no idea, what you're talking about... it's just ridiculous, not worth to go in any detail. ::)
But because product management will probably be lead by MBA style thinking, this will not happen and they will miss a great opportunity to make them a name in the industry and the market by making their devices unique. An opportunity to lower their r&d costs, making bigger chunks of money by driving demand and a respectable name for themselves, that is. And who wouldn't want that actually... but I'm afraid it is their MBA ideology (there you have it!) that hinders them from even realizing opportunities like this, one that is open to them to take on right now in this somewhat difficult situation they brought themselves into.Well said, I would like to add that Hantekway el al should concentrate their efforts on hardware design and manufacture, which they seem to be reasonably good at. They can easily keep that proprietary and let the hackers loose on their product to fix and enhance the firmware which is where their skills are seriously lacking
Now, if Hantek were smart,
Now, if Hantek were smart, they'd gone open-source with their scopes from day one.
Maybe we should start a voting - to see how many ppl would buy such small kit ?
Who knows, maybe HanTekway wish to make ppl happy and tie them ?
What is the best firmware for the DSO-1202B handheld?
I have firmware version 2.01.1 (111212.0)
How do I get measurements for channel 2 to display?
Hello, Im running HW 0x555583e8 SW 120224.0 and have been using my scope a lot recently, being no master I found an annoying bug,tthere is major bug inside this firmware, or actually last (already 3) firmwares. The reason is that Hantek/Tekway
When having just captured a single seq and pressed any menu button, the graph gets compressed in order to get space for the menu bar, this seems Ok, but if you want to measure time with the cursor, you end up measing an horizontally (time) compressed graph, aka, you measure more time than the actual real time.
Thanks for the reply tinhead.
Mark
shit, i have to answer your PM ... :)
There is newer firmware since day or two available on Hantek website, it does not change that much (if any)
but it is GPL compliant^^
Regards the measurments, sure click Meas button, chose with blue cursor keys the item you wish to change, click F5
to modify and select with F1 the source of measurments.
There are 4 measruments visible in same time, however you can scroll with these blue cursor keys between 4 pages - so you can setup on page 1 and two channel1 and pages 3 and 4 channel 2 - then in principle just scrol up and down between
pages.
tthere is major bug inside this firmware, or actually last (already 3) firmwares. The reason is that Hantek/Tekway
is working on the timebase procedure - the whole part has been re-written and does have bugs.
They has been notified about and actually they knew it. The good news it - they working on several bugs now,
so soon new firmware with fiex timebase will be available (and probably already the version 1:2:5 instead of 2:4:8 timebase ratio)
Installed 120423.0 and it has fixed the above issue, thanks. I now have measurements on channel 2. :DThanks for the reply tinhead.
Mark
shit, i have to answer your PM ... :)
There is newer firmware since day or two available on Hantek website, it does not change that much (if any)
but it is GPL compliant^^
Regards the measurments, sure click Meas button, chose with blue cursor keys the item you wish to change, click F5
to modify and select with F1 the source of measurments.
There are 4 measruments visible in same time, however you can scroll with these blue cursor keys between 4 pages - so you can setup on page 1 and two channel1 and pages 3 and 4 channel 2 - then in principle just scrol up and down between
pages.
The problem is, I have done what you said, but it does not change to ch2 when I press F1 (yes, ch2 is on).
Even when channel 1 is off and channel 2 is th eonly one displayed, it won't display amy ch2 measurements or allow ch2 to be selected by pressing F1.
I will upgrade the firmware and see if this is fixed.
(PS, I didn't send you a PM, so it must have been someone else).
Thanks again,
@Mark
My DSO5102 desktop scope behaves the same. I think this is a long standing bug, I posted about it here :-
https://www.eevblog.com/forum/general-chat/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg94907/#msg94907 (https://www.eevblog.com/forum/general-chat/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg94907/#msg94907)
But I think you described it better than I did.
Paul.
Installed 120423.0 and it has fixed the above issue, thanks. I now have measurements on channel 2. :DThe DSO1202B crashed at the weekend while I was playing around with it, and when it rebooted I had lost measurements on channel 2 again! Firmware still showed the upgraded number.
Quote from: MarkInstalled 120423.0 and it has fixed the above issue, thanks. I now have measurements on channel 2. :DThe DSO1202B crashed at the weekend while I was playing around with it, and when it rebooted I had lost measurements on channel 2 again! Firmware still showed the upgraded number.
Flashed firmware again and it's showing channel 2 measurements again. Maybe there is a way of resetting the scope which will fix this if it happens again instead of reflash.
(and when you so far they you can ask me how to enable licenses in eeprom).
(and when you so far they you can ask me how to enable licenses in eeprom).
Sorry can you rephrase that? Im not sure what you mean.
(and when you so far they you can ask me how to enable licenses in eeprom).
Sorry can you rephrase that? Im not sure what you mean.
and when you so far then you can ask me how to enable licenses in eeprom
(and when you so far they you can ask me how to enable licenses in eeprom).
Sorry can you rephrase that? Im not sure what you mean.
and when you so far then you can ask me how to enable licenses in eeprom
Ok I think I got you. Thanks
I was just curious about the possibility. However isn't it possible with the current kernel to create a mounting point in the filesystem that points to the SD card as an extension of the root filesystem? Because if it is, than we could use that to record waveforms on the scope I believe. But maybe it is just wishful thinking on my part.
Use the attached usb tool (special version of www.dreisiebner.at/dso-usb-tool (http://www.dreisiebner.at/dso-usb-tool) ), to delete delete the file /param/sav/run* (which is the setting profile)
In principle even the "default" button (save button and then F4 or F5?) should do the same,
if not try to delete the file above. You can also delete the sys.inf and then reboot:
rm /param/sav/r*
rm /sys.inf
EDIT: The attached usb tool is actually special version for handhelds, not
everything works but shell/settings/screenshot are already ok.
You will need to remove the "zip" in file names and use winrar to unpack it.
Hi guys.
This month my Hantek DSO5102B decided enough is enough, and froze up (knobs not working) so i had to open it up, hack it with my Seeeduino via UART, but when I did I found something unexpected. On the right side (top view) of the scope main PCB I saw a MicroSD card slot facing the buzzer. This got me curious whether it is something usable or not because i saw the pads on other images but in my case it was populated. Should I desolder the buzzer and try it out?
I am teetering between the Hantek and the Owon. I like the Hantek because of it's features and because it runs Linux. The Owon doesn't have the split zoom and update speed but it offers battery operation which would be handy for some things that I do. Kinda like a cordless drill.
How about a snapshot of the current situation?
if you plan on hacking around with your Hantek on regular bases, you might want to look at the procedure a number of people have used to add an easy to access uart connection to their das_oszi:
http://elinux.org/Das_Oszi_3.5MM_Uart (http://elinux.org/Das_Oszi_3.5MM_Uart)
Dave
Nice!
Considering the amount of time all this has taken - is there Tinhead Beer Fund somewhere to receive small tokens of appreciations :)?
Nice!
Considering the amount of time all this has taken - is there Tinhead Beer Fund somewhere to receive small tokens of appreciations :)?
well, when you like my work scroll up and give me 5 stars!
A 1Mpoint DSO will not mutate to 2Mpoint model only if you change license informations
in EEPROM - a physical chip will be necessary .. and few other things like e.g. kernel 2.6.30.4 (yeah, the firmware will
check this and if you don't on 2.6.30.4 the 2Mpoint will be not enabled even if you have license).
The kernel check (for 2.6.30.4) seems to be only cosmetic in nature for the 2Mpoint depth (appears to work with checks removed, with 120224.0). Also it seems unnecessary at first glance, that capture depth 1M/2M check is executed with changing timebase...
Can the debugmode be entered, something interesting there?
Sure, it can be removed. You need to check in few places as the firmware is checking also while accessing
device drivers (still in dso.exe), just look for "26304" string in disassembly.
Btw, did i mentioned already that exports are removed from current firmware? It make sense to leave copy of
2.06.3_120224.0 somewhere to have a chance to compare code from older (with exports) and current (w/o exports) versions.
Not that this is really necessary, but it makes quick checks easier.
regards debug mode, haven't tried anymore since a long time as it was nothing special there.
So this means that original "B" model users could save up to 2Mpoint?
What do you call exports? I've just saved a CSV to USB stick using 120430 firmware, so I guess exports are another thing.
Looks complex? No, it's not. Kernel and device drivers are since the published GPL code not an issue anymore
(so no need to wait for physical dump from someones BMV model). FPGA and CPLD designs are still what we
eventually looking for. I do have working FPGA and CPLD designs to support 2Mpoint, but they from
handhelds - in principle they runs on bench models too, but two SRAM traces need to be selfmade (even of hw1007 where
even 4Mpoint is already routed between CPLD, FPGA and SRAM). I do have all i need to run a test,
but no time for that (as i would need to solder all components from that board which i'm using to double check the
hw1007 schematics ...) so you see just too many tasks i'm working on.
Maybe someone can try to solder bigger SRAM - IS61LPS51236A-200TQLI(digikey 706-1100-ND ),
to patch fw (or install 2.6.30.4 kernel or patch uname) and to report back if the hw1007 boards and
their CPLD design are already good enought for 2Mpoint.
Now, I was thinking in adding extra features and it would be nice if we can organize ourselves to boost it up.
* Logic analyzer capability: let's start with I2C, SPI...
I would prefer connecting via LAN instead of serial connection.
right, you need to special crafted firmware to be able to downgrade.
However, it does not fix it. I suspect because the upgrade process is only incremental, reverting to an earlier upgrade can't fix it.
Anyone got suggestions how I have revert to the earlier software, or how to do a full install and upgrade to a less horrible version that the current one?
Frankly, I'm fed up with Hantek. I've had this scope one year now. I've made 'new product' excuses for Hantek a number of times, hoping they would improve their software and support. After one year, their new software upgrade wrecks the scope. They seem to have learned nothing.
Is there an easy way to fix this?
All i did was to patch out 3 bugs (this part works already with no issues), however i will try to patch 3 other
bugs (20, 22 and 24) before i post it here. In case i fail, i will of course post the latest working version.
Just give me a day or two
hi,
what can i do if i have this problem ? whithout installing this patch before ?
i have last firmware.
thanks.
marc
unfortunately you will have to connect via UART to the DSO (3.3V TTL UART converter is what you need)
and delete manualy the affected file, just execute on the shell rm -f /param/sav/run1kb*
or send the unit back to the shop where you bought it originaly.
Another reason why I would not believe in the rewritten software. The current codebase has a few years of QC, done by the customers. The fresh one, hacked together in two month, will not have any OC worth to mention.
EDIT: i've just got nice email from Hantek, the firmware will be revised not re-developed.This of course change the whole situation and make sense,
two months to re-develop
would be a typical chinese killer, but two months to revise the firmware is perfectly acceptable
hi,
what can i do if i have this problem ? whithout installing this patch before ?
i have last firmware.
thanks.
marc
unfortunately you will have to connect via UART to the DSO (3.3V TTL UART converter is what you need)
and delete manualy the affected file, just execute on the shell rm -f /param/sav/run1kb*
or send the unit back to the shop where you bought it originaly.
I assume this is what I have to do. I've got an iTeaduino v1.1 (http://www.komputer.de/wordpress/wp-content/uploads/2012/02/iteaduino_sch.pdf) (Ardunio clone) which has a FT232RL chip on it, I asume I could talk to this chip over Putty / Hyperterminal. Will have to test it out later ...
Hi,
I am really impressed about the work of tinhead and others about Hantek "upgrades".
Recently I purchased a handheld DSO1102B.
After checking the PCB I have some questions:
It seems that the RJ45 socket connects not only to LAN but also to some kind of RS232 interface.
Do you have information how to populate/activate the RS232 option?
---> Edit/Add:
Hoppla, just saw some information about RJ45 UART in #1029.
Did you try this option in the meantime?
---
For SD card option: Is it sufficient just to populate the card holder or are some additional resistors etc. necessary?you only card holder (and the SD card licensing in EEPROM, search this thread for details)
Then I saw near to the UART connector an empty connector named "WLAN" Do you have information about this option?
anyone who knows if this is still the 1GSs 100MHz version?
Gentoo Linux kernel: 3.5.0
Xorg
LXDE - Desktop environment
XChat - IRC client
terminal windows behind
(http://i.imgur.com/MuAMnl.jpg) (http://imgur.com/MuAMn)
Now we got almost everything, working on fpga configuration...
open source DSO soft will be directly for fbdev(lcd) not for xorg due to memory usage, this is quite far future but everything is going good
more fun (:
Hello,
I have a problem with my Tekway DST1062B - the scope hangs with white screen after running for about 30 seconds to 30 minutes. I have tried upgrading the factory firmware to version 2.06.3 (111202.0) - no change. I have not tried to hack the scope yet.
Hardware version shown is 10050x555583e8, serial number T 1G/005 003613.
Do you have any advice? Thank you!
Ivo
SeanB:
How did you accomplish thi ??? Do you have directions written?
Please advise..
Thanks!
Doug
nothing is gone, just kill watchdog after you loged-on to console by typing:
killall dsod
Also, I noticed something I dont think it was before, while navigating between pages of the utility menu, the navigation is now 1, 2, 3, 2, 1, 2, 3, 2, ... instead of 1, 2, 3, 1, 2, 3... Is this new of I just didn't noticed before?
I did some HW upgrades according to tinhead's infos on my handheld DSO1102B:
Service interface:
I used an ELV USB-TTL interface module.
The module is fixed with two screws M2.5 and two thin square nuts which are inserted in the ventilation openings in the back cover.
The plug can be reached after removing the battery cover.
SD-Card:
Just the card holder. By the way, I tried a 16GB SDHC and it was working fine.
I just received my DSO3062C from Conrad.
Hi,
can you tell me in which Conrad you bought the scope? German Conrad now claims it's sold out:/
After successfully flashing with the latest firmware, Thanks Tinhead. I'm getting an error while doing a calibration, it gets to 33 and fails with "self calibration failed,error:0x502" I've tried several times with the same error, any ideas as to what's gone wrong? Thanks, jellytot
Conrad.com, but it seems that indeed it is sold out. Also http://www.voelkner.de (http://www.voelkner.de) doesn't list it anymore.
Hi Chrisme, thanks for your post. Can you just try running the calibration a second time and see if it still works..? Thanks!
After successfully flashing with the latest firmware, Thanks Tinhead. I'm getting an error while doing a calibration, it gets to 33 and fails with "self calibration failed,error:0x502" I've tried several times with the same error, any ideas as to what's gone wrong? Thanks, jellytot
After reading this topic I have bigger doubt than I had before. I'm about to buy cheap DSO. Which one will you recommend me: Tekway DST1102B, Owon SDS7102 (I have read whole topic about it also) or Rigol DS1052E? Every one of them have some disadvantages.At this cheaper end of the market, all you can do is weight up WHAT you can't live without and WHAT you can make do.
[...] Every one of them have some disadvantages.
[...]
Rigol:
-100MHz only with hacked fw
[...]
I think that I'm going to buy Owon.Also have averaging (VERY handy) and record length settings. Get the battery if you can afford it ($60), VERY handy !!It's a pity that there is no persistence option but well... I can deal with it...Oh there is a persistence option so I'm buying it right now ;D
At 1Meg memory length the owon is WAYYY faster than a hantek
and this actually does not matter, you talk about 30 vs 4 waveframes per second. Both values are suchThis all is about human perception. I personally feel more comfortable if the waveform on the display reacts smoothly to my commands. I hope it will be possible to emulate analog scope look and feel in the Hantek custom firmware.
low that you can't use these scopes (in this particular memory depth setting) to catch any kind of glitches.
and this actually does not matter, you talk about 30 vs 4 waveframes per second. Both values are suchThis all is about human perception. I personally feel more comfortable if the waveform on the display reacts smoothly to my commands. I hope it will be possible to emulate analog scope look and feel in the Hantek custom firmware.
low that you can't use these scopes (in this particular memory depth setting) to catch any kind of glitches.
On the other side they working on the firmware, the progress (of bug fixing and improvements) was already very goodThis firmware is appropriate for hantek dso1202b (hw: 83e8)?
(see fw 2.06.3_120625.0), let's hope they still on track. I think i will ask for updates on that.
I am new to this forum and I am going to buy an oscilloscope. I need about 200Mhz one.I'm curious. If I may ask, what do you want to do with a 200 MHz oscilloscope? Do you want an analog or digital oscilloscope? What does "moderate budget" mean to you exactly?
Which brand can you recommend? ( having in mind moderate budget).
I was thinking about Hantek DSO 5202B.
Or do you know a better choice at a similar price and function?
Thanks
Need it for the satellite repairs and other things.
By moderate budget I mean that I want to spend on oscilloscope about USD 500.
Reading a thread COMPLETELY is good etiquette before asking a question that has probably been asked somewhere in that thread already....
You will probably get a better response if you put forth a little effort yourself.....
I read all the pages.....Reading a thread COMPLETELY is good etiquette before asking a question that has probably been asked somewhere in that thread already....
You will probably get a better response if you put forth a little effort yourself.....
Reading 90 pages of thread is.. a little much.
Can anyone tell me please how to dismantle the DSO5062? Are there only 2 bottom srews or any others I must removed first?Thanks
But there is also a possibility to use JTAG.
Does anyone know the pin assignments for the CPU Samsung S3C2440 . The SoC used in the oscilloscope?
... CPU Samsung S3C2440 . The SoC used in the oscilloscope?
tinhead
Hi. I have hantek DSO1052b with hw 1007. I have read you posts, but did not understand if will buy DM9000EP, can it work with hw 1007. At first look i didn't see place on PCB where i could solder it. May be I must develop additional board with DM9000EP. How can I enable Ethernet on hw 1007?
Recently I bought Tekway 1062 model at Pioneer Huang, after a few minutes of work DSO started to hang with the white screen.
...
If you want to check this trick quickly you can pull off cooler plug and let DSO to work some time without it, there should be no white screens anymore, but the radiators will be hotter than usual, so enhancing of radiators must be did for continuous work.
Reading a thread COMPLETELY is good etiquette before asking a question that has probably been asked somewhere in that thread already....
You will probably get a better response if you put forth a little effort yourself.....
Reading 90 pages of thread is.. a little much.
@tinhead:thanks for the reply.
So it seems I upgraded my scope. But when I try to self calibration, it fails with the error 0x2
and I can do nothing but restart scope
Does any one know the reason?
Thanks
Thanks for the reply. That error( 0x2) I received also before upgrade.It does not have probably anything in common with the upgrade. But do you happen to know how I can repair that error and make the self calibration?
Thanks
By ugrading sw, the problem is solved
Can anyone explain why I receive different values when measuring frequency?
Why is the difference of the frequency on the bottom line( which is correct) and the frequency on the measuring menu( which is incorrect) ?
I compared that hacked DSO5262 with the unhacked DSO5262.
And trigger counter( on bottom status) shows about 199 Mhz measuring frequency with both DSO5262.
Is that normal?
How can I test then the hacking was successful?
@tinhead: I was sent dst1kb_2.06.3_15062b_fact(120808.2).up file. If anyone needs it I can upload somewhere. After updating, self calibration is OK.
The file is too big.
Uploaded
https://hotfile.com/dl/171886296/83de0a9/dst1kb_2.06.3_15062b_fact(120808.2).up.html (https://hotfile.com/dl/171886296/83de0a9/dst1k
b_2.06.3_15062b_fact(120808.2).up.html)
(one line)
I'm also interested in the MSO/LA but I checked my DSO and it's a HW1007 board but the PCB header socket (2mm) to connect the LA board is not installed.
Can I solder one myself ? Did I have to add something else to my DSO ?
I'm also interested in the MSO/LA but I checked my DSO and it's a HW1007 board but the PCB header socket (2mm) to connect the LA board is not installed.
Can I solder one myself ? Did I have to add something else to my DSO ?
I will deliver all the necessary small parts. This means also that you will get :
- 1.27mm pin header
- 2 screews
- distance holder
- 5cm flat cable with 20pin IDC plug (to connect DB25 socket to LA/MSO PCB)
- DB25 socket
- DB25 header
You will not get any test cables, but they are really cheap on ebay 251150864536
All you will have to do is to:
- backup firmware (over USB flash drive with backup tool)
- remove sticker (front panel near USB) to expose the hole for DB25 socket. Every hw1007 have such hole.
- solder cable to DB25 socket (the IDT20 cable which will be pluged into LA PCB)
- mount this DB25 socket to front panel. I think there are already holes in the shielding, when you remove the sticker
you will see immediately if there is any drill work necessary.
- solder the 1.27mm pitch header to DSO PCB
- mount the LA PCB to DSO PCB
- connect the IDT20 cable (from DB25) to LA
- reconnect all other DSO cables, so you can boot DSO.
Boot DSO and install new firmware. You will need for this UART<->PC connection and deatiled description how to
do this. I will get special crafted firmware (actually complette dump), this must be complettly restored to DSO
overwriting the old version. The biggest advantage : you will have newer Linux version, which is anyway necessary to
get network working. In Germany i'm offering "instalaltion service", so everybody who don't wish to play with
UART/USB to install firmware or solder cables/header can get this step done by me (for a small fee).
So as long you have :
- screwdriver
- solder station
- UART<->USB adapter cable
- max 2GB USB flash drive
it's not so much to do.
iwconfig, iwlist, iwXXXX | Wireless tools (http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html (http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html)) |
wpa_supplicant | Handles wireless network encryption WPA/WPA2 |
ifplugd | Checks for the adapter and runs a script when plugged in/out |
8192cu.ko | Driver for realtek 8192 / 8188 chipset + different versions (syslog off, powersaving off) |
How will the MSO/LA modification affect the future firmware upgrade path for the DSO5000?
Did anyone try to hack DSO5102BM?
I bought DSO5102BM few days ago only and wanted to hack it.
But I noticed it uses a different software.
E.g. I need not use
killall dsod command
to enter console and also booting is different.
I were not able to change logo and not sure if the hack was really successful.
It shows DSO5202B( as I wanted) but not sure if it also works as DSO5202B.
Besides when it starts booting it shows
*** Warning - bad CRC or NAND, using default environment
##### EmbedSky BIOS for SKY2440/TQ2440 #####
Press Space key to Download Mode !
Booting Linux ...
Copy linux kernel from 0x00200000 to 0x30008000, size = 0x00200000 ... Copy Kernel to SDRAM done,NOW, Booting Linux......
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.30.4 (root@rain-fc4) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #9 Mon Dec 12 11:50:21 CST 2011
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
CPU: VIVT data cache, VIVT instruction cache
Machine: TQ2440
...
....
...
...
Thanks for help.
- root fs is newer, contains newer drivers, media player, etc.
- root fs is newer, contains newer drivers, media player, etc.
Wat?
Does it mean BM/BMV models has also different hardware or only software?
I noticed there is P1 connector for buzzer but nothing more different
And is there a way how I can change the logo also?
A few people mentioned WiFi dongles, and I really liked that idea, so I got a 10€ one from amazon.
It has a realtek chipset, and they provide linux sources for the driver.
...
If you have a different dongle than the EDIMAX EW-7811UN
@tinhead
Is there any chance of getting network support for the DSO-app on the bench models?
I tried to activate it by writing the [net]1 to the EEPROM, but I couldn't connect with ttscope or dreisiebners' dso-tool.
Taking a screenshot wirelessly seems like a very neat feature to me, so already tried to grab it directly from the framebuffer, but /dev/fb0 seems to be unused.
In principle a UDP server and patched usb-char i think? (from usbdevice driver) could work as well.
@tinhead:You say I can change logo by editing disp file.
Do you mean
/logotype.dis
file ?
I changed
/logotype.dis
It consists only
hantek_DSO5202B
But still no good
Thanks for reply
In principle a UDP server and patched usb-char i think? (from usbdevice driver) could work as well.
Thanks for the good idea, i got it working! Hantek released the source code for the usb-char module, so it was relatively easy to redirect all communication to a udp server. For this, I wrote a new kernel module using the nice ksocket library/module.
I will clean up the code a bit and post the sources tomorrow.
Okay, so here are the sources for the usb-char module with integrated udp-server.
All you will have to do is to:
- backup firmware (over USB flash drive with backup tool)
- remove sticker (front panel near USB) to expose the hole for DB25 socket. Every hw1007 have such hole.
- solder cable to DB25 socket (the IDT20 cable which will be pluged into LA PCB)
- mount this DB25 socket to front panel. I think there are already holes in the shielding, when you remove the sticker
you will see immediately if there is any drill work necessary.
- solder the 1.27mm pitch header to DSO PCB
- mount the LA PCB to DSO PCB
- connect the IDT20 cable (from DB25) to LA
- reconnect all other DSO cables, so you can boot DSO.
Boot DSO and install new firmware. You will need for this UART<->PC connection and deatiled description how to
do this. I will get special crafted firmware (actually complette dump), this must be complettly restored to DSO
overwriting the old version. The biggest advantage : you will have newer Linux version, which is anyway necessary to
get network working. In Germany i'm offering "instalaltion service", so everybody who don't wish to play with
UART/USB to install firmware or solder cables/header can get this step done by me (for a small fee).
So as long you have :
- screwdriver
- solder station
- UART<->USB adapter cable
- max 2GB USB flash drive
it's not so much to do.
Quote from: Jane on September 18, 2012, 07:58:35 PMTinhead, but how can I change the logo of DSO5102BM, if the /dso/app/disp file is already compiled?How can I edit a compiled file?
@tinhead:You say I can change logo by editing disp file.
Do you mean
/logotype.dis
file ?
I changed
/logotype.dis
It consists only
hantek_DSO5202B
But still no good
Thanks for reply
no, the disp file. Just check the file system, there is /disp or /dso/app/disp file, and inside this file a
raw image is included (in principle like the logo files before but this time compiled into executable file)
You can replace/edit this file to create own disp file - for our model the logotype.dis is not changing anything.
just saw this, so had a look at the Voltcraft DSO-3062C hw1007 version
there is a hole in the plastic of the case for the DB25 socket in the front panel, but there is a metal shield behind it, is the clearing between those enough to install the DB25 socket ?
edit: ha, having second look at http://www.tekwayins.com/pic/201202080007.jpg (http://www.tekwayins.com/pic/201202080007.jpg) it measn you need to cut you're own hole in the metal to mount the db25... hum..
and what's up with those unpopulated phone/mic things next to the rear USB port? where are they used for in other models? :)a few ppl here (e.g. Jane two postings above) bought these BM/BMV models, so they can answer you if there is
I also don't see any models with a second front usb port, anyway, info about that must be buried most likely somewhere here in the thread :)
I would say, before you buy from Extech but 2+pcs from Hante, hehe.
Do you know if both of the latter models are hackable to 200mhz with your method?
I wouldn't mind the extra memory but do you know what the video does for BMV model?
But, but, but, Extech is soooo ISO9000 certified. That is for sure worth the higher price ... *ducks and runs*
luckily we know that ISO9001 certificated does not means anything about quality of products.
Gentoo Linux kernel: 3.5.0
Xorg
LXDE - Desktop environment
XChat - IRC client
terminal windows behind
(http://i.imgur.com/MuAMnl.jpg) (http://imgur.com/MuAMn)
Now we got almost everything, working on fpga configuration...
open source DSO soft will be directly for fbdev(lcd) not for xorg due to memory usage, this is quite far future but everything is going good
Hello Tinhead, sorry if you've said it but I couldn't find it in the last 5 pages. Does the older HW version 0x555583E8 could be hackable to a MSO ?
Thanks !
Hello Tinhead, sorry if you've said it but I couldn't find it in the last 5 pages. Does the older HW version 0x555583E8 could be hackable to a MSO ?
Thanks !
I'm also interested in that hack as well.
[DST type]dst1202b
[soft version]2.06.3(120808.0)
[fpga version]0x555583eb
[start time]15
[update time]1
- /sys.inf 1/5 20%
/dst1202b
- /tmpdst 1/1 100%
dst1202b
- /logotype 0/0 100%
pce_DSO5202B
- /logotype.dis 1/1 100%
The question is, why is the watchdog resetting the device?
Hello Tinhead, sorry if you've said it but I couldn't find it in the last 5 pages. Does the older HW version 0x555583E8 could be hackable to a MSO ?
Thanks !
I'm also interested in that hack as well.
The question is, why is the watchdog resetting the device?
this is exactly what a watchdog have to do: if the main process, in the case of this DSO the dso.exe exectable,
terminates the watchdog have to re-initialize the device, which is on a these DSO reboot (to ensure that memory has been cleaned-up and all necessary sub-processes restarted properly).
Hi,
is http://www.pce-instruments.com/deutsch/messtechnik-im-online-handel/messgeraete-fuer-alle-parameter/oszilloskop-pce-holding-gmbh-speicheroszilloskop-pce-dso5062b-det_257116.htm?_list=kat&_listpos=4 (http://www.pce-instruments.com/deutsch/messtechnik-im-online-handel/messgeraete-fuer-alle-parameter/oszilloskop-pce-holding-gmbh-speicheroszilloskop-pce-dso5062b-det_257116.htm?_list=kat&_listpos=4) same as Hantek DSO5102B?
I have been reading this thread for a while and finally purchased my DSO1062b and decided to hack it.
It has firmware version 2.01.1 (120909.0) and hardware version 0x555583e8
...
P.S. If anyone needs the original firmware from my scope - I have backed it up and can share.
The funny (or maybe not so funny) thing is that when I connect to it through the UART interface using minicom, I get a constant stream of messages:
power_ioctl:IOCTL_SCAN_POWER_BI_TOUT:1
power_ioctl:IOCTL_SCAN_POWER_BI_TOUT:0
which come with ~1 second interval
..
I have been able to apply the hack successfully and all the functions seem to work fine, but those messages bother me - does anyone have any idea what these "power_ioctl" messages may mean?
The question is, why is the watchdog resetting the device?
The question is, why is the watchdog resetting the device?
1- you got DOA device
2- you screwed something up (typo?), which is causing somewhere an error in the dso.exe
3- something is different in the pce-instruments firmware version (whcih i doubt, but who knows, maybe Hantek screwed something up)
I've flashed the original firmware that I've backed up with the fw3dump tool and did the hack one more time.
Unfortunately the behaviour is the same. So I don't think it's caused by doing something wrong in the software changes from dst1062b to dst1202b.
Is it possible that this is a hardware problem? I mean that the components of this particular device can't handle this high bandwidths?
The silly thing is that I needed to solder cables in the appropriate pinheader holes of the UART, thus the warranty should be gone...
I have a PCE DSO5062B, I've hacked it a while ago and it's running fine for about 15 minutes.
But I'm very disappointed by the number of bugs in the firmware (120808). :(
I've flashed the original firmware that I've backed up with the fw3dump tool and did the hack one more time.
Unfortunately the behaviour is the same. So I don't think it's caused by doing something wrong in the software changes from dst1062b to dst1202b.
Is it possible that this is a hardware problem?
I mean that the components of this particular device can't handle this high bandwidths?
The silly thing is that I needed to solder cables in the appropriate pinheader holes of the UART, thus the warranty should be gone...
that does not very inviting.
I got the 60MHz DSO from PCE-Instruments and wonder if I can just flash the firmware from Hantek, or Tekway? Which one is newer, or more bug free?
For the next days I test the device without hack, just to make sure it works fine.
Other question is, how to easily generate a test signal with 50, 100 or 200MHz to test the dso? Because my generator only offers 2MHz max. Any tips for cheap solutions?
Hi beard, would you mind sending me the link too? Or posting it here ! I want to see if they've fixed a bug that's pretty annoying to me :)
I will try to figure out what those messages mean, but are they normal, have you seen those before?
I haven't checked deeper what changed
"...so they quickly ordered new stickers and here we go...", yeah... new stickers but again not correct :-DD On sticker is 100 MHz and 500MS/s :) But in Highlights & Details is: 60 MHz Bandbreite
1 GS/s Realtime-Samplingrate, 25 GS/s equivalent.
MasterFX... in product page of DSO3062C (http://www.conrad.at/ce/de/product/122464 (http://www.conrad.at/ce/de/product/122464)), resolution is 800 x 400 pixels too.
Can anyone confirm that this is the same device as 3062C (Hantek DSO5062B) ???
what is your point? It is described as 1GS/s DSO, with 1Mpoint memory, so it is what it should be.On sticker is 100 MHz... instead of 60 MHz.
I would say they edit the old picture with Photoshop without having the real picture of the scope... so the small mistakes did also survive in the new picture. I'll buy the 1062C next week or so. I will post some "real" images. I'm pretty sure thats an Hantek inside. If not I'll give it back to Conrad.Quotewhat is your point? It is described as 1GS/s DSO, with 1Mpoint memory, so it is what it should be.On sticker is 100 MHz... instead of 60 MHz.
i bough a DSO1060
...
Is there much hardware diference between this and DSO1062b bv bvb?
Hi,
My first post here - I want to buy an oscilloscope in the next week or so and that conrad.de thing got me very curious. Any confirmation that the VOLTCRAFT DSO-3062C and D models are actually the same thing as Tekway DST1062B hardware- and software-wise? Even the D one would be a decent deal for a beginner like me.
Thanks!
Unfortunately it's already sold out: http://www.conrad.de/ce/de/product/122464/VOLTCRAFT-DSO-3062C-DIGITAL-OSZILLOSKOP (http://www.conrad.de/ce/de/product/122464/VOLTCRAFT-DSO-3062C-DIGITAL-OSZILLOSKOP)Hi,
My first post here - I want to buy an oscilloscope in the next week or so and that conrad.de thing got me very curious. Any confirmation that the VOLTCRAFT DSO-3062C and D models are actually the same thing as Tekway DST1062B hardware- and software-wise? Even the D one would be a decent deal for a beginner like me.
Thanks!
Could you send me the link for VOLTCRAFT DSO-3062C on conrad.de???
Yes I know. Therefore, I was not clear why the interest for VOLTCRAFT DSO-3062C. MasterFX will buy 1062C so I'm waiting hes review.Not a review but a Systeminfo Screen. Looks it is almost the same but it has e8 instead of the e9 at the end. Seems like it has something to do with the FPGA.
Does anyone else have experience with 1062C, and witch firmware they use?
Being out of ideas I just removed and plugged back the two power connectors coming to the main board,
it seemed to work fine afterwards.
the horizontal and vertical positions knobs cannot be rotated with one finger
Vertical LCD viewing angles are pretty poor.
Sure, in the real world you might have DSO on your desk, but then you will still don't want to look from top on it,
but stright to display (which is why there are plastic foldout feets under each lab gear to align the angle).
I just wondered if it is possible to hack the DSO to 200 MHz by using DSO-USB-Tool (http://www.dreisiebner.at/dso-usb-tool/ (http://www.dreisiebner.at/dso-usb-tool/))
Because with this tool you're able to read and write the system files /sys.inf,/tmpdst, /logotype (see attached image) and execute system commands via shell.
And what about the 83e8 and 83e9 FPGA?? What are the differences?
Very interesting tinhead, any way to know which 83E8 version I got? Maybe I have the best design ever 83E8 and will just ruin it upgrading it to the latest 83E9
copy from DSO to flash drive and binary compare on PC with attached versions :)
copy from DSO to flash drive and binary compare on PC with attached versions :)
hehe I suspected something like that knowing that linux sees it as a file. Thanks !
What these 83E8, 83E9 means ?Hi, tinhead
The dn_hw1007_83E9_date111122.rbf is less than half the filesize, seems they throw much garbage away.
What about the factory calibration on the benchtop DSOs?
... it does seem like this little DSO have a raw but amazing refresh rate. does any 1 know approx what is it? 1k refresh? 2 k?
it does seem like this little DSO have a raw but amazing refresh rate. does any 1 know approx what is it? 1k refresh? 2 k?Keep in mind that any DSO manufacturer that specifies a wfrm/s rate (and many don't) uses the fastest possible rate - and there is only one single timebase setting + sample depth (with a single channel) that will achieve that rate. You can see in this table I made (https://www.eevblog.com/forum/reviews/first-impressions-and-review-of-the-rigol-ds2072-ds2000-series-dso/msg160064/#msg160064) of the Rigol DS2072s waveform capture rates at all scale and memory depths that it peaks at the 20ns setting - but other DSOs have different 'sweet spots'. If you know what it is for your DSO, then you can specifically use that setting when glitch-hunting,
The amplitude of a 130MHz sine wave signal from a lashed up Colpitts oscillator has increased by 60%, so bandwidth has also been improved, although at this stage I cannot confirm full 200MHz capability.
I'm guessing from the schematics that you have posted in this thread that to get proper HF performance from this 60MHz model, I would need to change some values in the front end.
Is that correct?
Just got a Voltcraft DSO-1062D. It appears to be another rebadged Tekway DST-1062B with 10070x555583eb hardware and 2.06.3(121012.0) software.
Just got a Voltcraft DSO-1062D. It appears to be another rebadged Tekway DST-1062B with 10070x555583eb hardware and 2.06.3(121012.0) software.
Does the 555583eb indicate a new FPGA release for the DSO-1062D, namely 83EB? If so, does anyone know how it compares to the 83E8 and 83E9 FPGA configs?
And: would it be possible to use the 83EB on the Voltcraft 3062C and/or the regular Hanteks?
So, reading from your chart, I conclude the 83E9 is the best choice at the moment and there is no need to update the 3062C to the 83EB firmware.
Anyhow, is there a download link for the 83EB firmware if one would like to experiment? It is not in the fpga archive is it?
Hello Tinhead,
Do you have some news for the MSO extention ? Did you received the firmware ?
What's the status ?
Bernard
I'm happy that i got official answer, but somehow it does not make sense - ok, maybe DSOs with EA and EB designs have again different DACs than my E9 (with already different DA as in previous E9 hardware versions).
My 3062C has its DAC on the bottom of the board. I did not make that many photos of the bottom, as it did not seem that interesting at the time. This is the best I have of the DAC. Can you make something of it?
If you look further there is also one for USD389 :)
hmmm didnt see any of that, what should i search under?If you look further there is also one for USD389 :)
One issue that I did not find in the bug list, is the resolution of the trigger frequency display. I have a signal of 21.58Hz, it displays 21.0000Hz in the bottom. If it is not possible to measure it better than with 1Hz resolution, display at least 21Hz instead of 21.0000Hz. :-BROKE
hmmm didnt see any of that, what should i search under?If you look further there is also one for USD389 :)
ebay item 140872766162
So i don't know how much space is there in FPGA, i can ask to implement better counter, but i can't promise anything.
if( freq < 1000 )
printf("%dHz", freq);
else if( freq < 1000000 )
printf("%d.%03dkHz", freq / 1000, freq % 1000);
else
printf("%d.%03dMHz", freq / 1000000, (freq / 1000) % 1000);
A Rigol? 8)
1500 replies and (nearly) 250000 views ... Dave, where is my DMM ? :-//
1500 replies and (nearly) 250000 views ... Dave, where is my DMM ? :-//
Perhaps there should be a prize for threads that crack numbers like that.
Email me your snail mail address!
Dave.
Damn you tinhead! I can never catch up!! :scared:
1500 replies and (nearly) 250000 views ... Dave, where is my DMM ? :-//
Damn you tinhead! I can never catch up!! :scared:
..really? :) you had no idea? (https://www.eevblog.com/forum/blog/changing-the-rigol-ds1052e-to-ds1102e-using-usb-the-dummy-guide/) (and all other threads about this?) 8)
Sure, third of all the replies are coming from me, but still, i was really surprised how many poeple discussed these DSOs.
..really? :) you had no idea? (https://www.eevblog.com/forum/blog/changing-the-rigol-ds1052e-to-ds1102e-using-usb-the-dummy-guide/) (and all other threads about this?) 8)
Sure, third of all the replies are coming from me, but still, i was really surprised how many poeple discussed these DSOs.
EDIT: i forgot to mention, there are few new measurments:FOVShoot: Fall overshoot voltage
FOVShoot
RPREShoot
BWidth
FRF
FFR
LRR
LRF
LFR
LFF
but don't ask me what they doing, i haven't found any info in the (updated) help file, maybe i'm simply blind.
I assume this are First (waveform?) Rising Falling etc? Check it and let me knwo what you think :scared:
FOVShoot: Fall overshoot voltage
RPREShoot: Rise preshoot voltage
There is new firmware available for Hantek DSO5xxxB/Tekway DST1000B/Voltcraft DSO3062/1062/PCE DSOs,Does this firmware run on the original Tekway 1202B Hardware ?
http://www.hantek.com.cn/english/down_list.asp?unid=30 (http://www.hantek.com.cn/english/down_list.asp?unid=30)
There is new firmware available for Hantek DSO5xxxB/Tekway DST1000B/Voltcraft DSO3062/1062/PCE DSOs,Does this firmware run on the original Tekway 1202B Hardware ?
http://www.hantek.com.cn/english/down_list.asp?unid=30 (http://www.hantek.com.cn/english/down_list.asp?unid=30)
Thanks ever so much for the 1202B files. I extracted the zip and found .exe file. I run Linux. I expected to see a .up file. Will the exe extract on Windows ?
I have an updated DSO5062B
My system crashed while I was on the FFT screen and moving the cursor. I rebooted it a few times but it always goes back to display the crashed screen after booting up. No button or knob responds. :-BROKE
I'm guessing maybe the configuration from the last operating mode is saved somewhere on a file so when it reboots, it redirects to that code. What I am curious about is what the exact bootup sequence is up to the initialization file so I can reset it to the factory default configuration. What is the name of the initialization file, the factory default configuration file, and the directory?
In addition, the scope displayed the factory default screen for a few months whilst rebooting. Sometime recently however, it has been going back to the last used configuration.
OK guys,
Let this be a warning to all of you upgraders. Be very carefull when fitting the MSO add-on card to the mainboard.
My glasses are not strong enough, it was off by one row when I did a first test after loading the new software.
A flash, some smoke and the S3C2440 SOC is looking very dead now with its newly formed bubble. :palm:
Maurits
Thank you very much tinhead.
After file "run1kb_100302" was deleted, it's working.
Did you ever made backup of your DSO? If not (and if 'we' manage to let is boot properly) then i would like to
get backup of your DSO, simply to double check if there is something in the file system killing your device.
How to backup -> https://www.eevblog.com/forum/chat/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg35683/#msg35683 (https://www.eevblog.com/forum/chat/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg35683/#msg35683)
OK guys,
Let this be a warning to all of you upgraders. Be very carefull when fitting the MSO add-on card to the mainboard.
My glasses are not strong enough, it was off by one row when I did a first test after loading the new software.
A flash, some smoke and the S3C2440 SOC is looking very dead now with its newly formed bubble. :palm:
Maurits
W
What is the correct commad:
mv dso1062d dso5202b
or
mv dso1062d DSP5202B
I can not see any files in / ??????
ls clears screen on terminal and nothing appears.
This is a Voltcraft DSO-1062D and I want a DSO5202B as target.
I'm logged as root, I can go to /bin or /logo but can not list any file.
If type ls screen blanks and promt dissapears. When press ENTER, promt appears again.
I have been testing the new firmware and checking if the delayed sweep bug has been fixed, I started to record the result (attached below) against the 1KHz probe calibrator with the trigger point offset to 500uS and then 1.000mS to see if any errors were cumulative.
for 1Mpoint benchtop Tekway/Hantek/Voltcraft models
Just to be sure, that's the classic "B" model? because I have that, and I remember being able to do 1Mpoint, but now I've checked and now I can't select 1Mpoint, currently running FW 2.06.3(130114.0) maybe It's disabled in this version.
The 1Mpoint option is only available when a single channel is active.
Just re-checked and nope, in this version (130114.0) it's disabled, can anyone double check that?
I'm running tinheads latest (test) version 130131.0 and 1M is enabled when only single channel active.
First of all the 200us/div and 1M was not working from the beginning. Right after i recognized it on a very
first firmware i send it as bug report - i don't know when exactly but one on next firmwares was able
to enable 1M in 200us/div but zoom was not working. So i asked again and got answer
that the way how the DSO is designed they can't enable 200us/DIV and 1M - the next fw version then was
not capable again of doing 200us/div and 1M. I thought, what a bummer, but anyway,
it works below and above 200us/div, or just with 512k while in 200us/div.
I updated the firmware and repeated the tests, no change.
first of all thanks for the effort. If you don't mind, could you repeat your measurments with the firmware 130131.0 from link above?
I updated the firmware and repeated the tests, no change.ahh, not that good
I can report that the error is the same with a 10 Second delayed sweep time as it is with 1 mS :)
Total length of the shaft?
right, i should say "total high" or "shaft length". My hw0 was using, when i remember it right,I see.. do you have this BCB in access, as I already assembled mine DSO (I need it for playing with my new Rubidium frequency reference)? Can you measure encoder dimensions and shaft length for me?
ALPS encoders. I've checked right now the current model, but i don't see any marks on it.
I see.. do you have this BCB in access, as I already assembled mine DSO (I need it for playing with my new Rubidium frequency reference)? Can you measure encoder dimensions and shaft length for me?
It looks very similar to Bourns PEC-12 type.Right! Seems to be that one. I will crack that thing open to check according datasheet for pad positions and total dimensions.
I exported a wave and it came in a .hws file, but I can't figure out what format it is.
Second I exported a cvs file, but the Hantek and the Siglent has different format/information in the file.
The only thing I can see is to make a cvs converter from Hantek to Siglent format, but can this be true?
Back again..
On the 23rd of January, during a test after the MSO modification, I blew the s3c2440 of my scope. A few days ago I managed to get the broken chip off the board. Today I had a go at soldering a new chip in place. Miracle.. It is working!!
Further testing now to find out if the LA board was damaged at the disaster of a month ago.
Do you think that there are other people that can use a converter like this. I am thinking about
how much work I shall put into it or in other words, make it easy to use it with other Wave generators.
let's hope the best. In principle when you appy 3.3V to the LA pcb the fpga should start working, when you see
the proper ID ovr JTAG then at least this is working. The next step is lan ic, when current consumption is not more
than 100mA everything will be fine, then you can plug the LA PCB to DSO and run other tests.
Another thing: since I removed the lithium cell during the repair, the clock needs resetting. The VO knob is not working as expected, is this a bug in the MSO Firmware?
Back again..
On the 23rd of January, during a test after the MSO modification, I blew the s3c2440 of my scope. A few days ago I managed to get the broken chip off the board. Today I had a go at soldering a new chip in place. Miracle.. It is working!!
awsome!Further testing now to find out if the LA board was damaged at the disaster of a month ago.
let's hope the best. In principle when you appy 3.3V to the LA pcb the fpga should start working, when you see
the proper ID ovr JTAG then at least this is working. The next step is lan ic, when current consumption is not more
than 100mA everything will be fine, then you can plug the LA PCB to DSO and run other tests.
In wort case the io communication between both FPGAs will not work (due the applied reversed voltage to io21 and 22),
then you will have to check which one of the FPGAs is broken (let's hope none, they much harder to solder than the SoC),
the best way is over jtag to test with boundary scan the status of FPGA pins/ports.
In best case nothing else broken, hope the best for you.
I managed to boundary scan this FPGA, the IO21 and IO22 pins are working, input and output. The FPGA of the main board I did scan as well but I am in the blind here. I don't know what to look for: the hw version 1007 is totally different from the published 1003.
There must be something wrong since the LA FPGA is not loading its program.
Just got my Hantek DSO5102B. Bought from goodluckbuy on eBay for $388.88 shipped.hmm
Sw. version 2.06.3 (111025.0), hw.version 10070x555583e8.this is old stock, Hantek stopped 83E8 production somewhere in Nov 2011.
The scope came with the fan installed; first impression - fan is less noisy than Tek7104 but more noisy than Tek475a. Overall - nice liitle scope.well, replace the 7812 by 7808, turn fan in oposite direction - or replace the KA378R33 by dc/dc converter or Micrel HELDO.
According to what I've read so far this is 200MHz input stage, is this correct?
if someone wish to test - here another one firmware for
- Tekway DST1062B, DST1102B, DST1202B
- Hantek DSO5062B, DSO5102B, DSO5202B
- Voltcraft DSO3062C, DSO1062D
- PCE DSOs: PCE-DSO5062B, PCE-DSO5102B, PCE-DSO5202B
http://www.mikrocontroller.net/attachment/170890/dst1kb_2.06.3_15202b_fact_130221.0_.zip (http://www.mikrocontroller.net/attachment/170890/dst1kb_2.06.3_15202b_fact_130221.0_.zip)
There must be something wrong since the LA FPGA is not loading its program.
there is as well JTAG port on LA PCB, use it (the best would be to test while the LA PCB is NOT mounted in DSO).
I've attached small design, load it over jtag, it should produce 25MHz clock on FPGA pin1 (the clock for LAN IC)
I learned here that while pin to pin boundary scan is working the chip core is not guaranteed to be allright. The LA-FPGA was not loading the configuration file over JTAG. The shorted nCONFIG pin I found earlier made me decide to change the LA-FPGA.
Another soldering miracle was performed. With the new FPGA the start up log file shows the config file is loaded.
However I had to overcome the pinnumber issue with the cable connector for the frontpanel connection of the LA. In the schematic the odd numbered pins are GND. The connector on the board is wired even pins to GND. Looks like the pin connector was on the bottom side during the board design stage. The silkscreen marking "1" is at the position of pin 2 now.
When I sorted this out I made another adapter and now the Logic Analyzer is working, Finally!and that's really good news!
The DM9000 chip most probably also not survived the accident because I can trace no network activity. The LnOE net is also routed to pin 1 of the DM9000 and this net was relatively negative 1.7 V. during the accident. Another soldering job; but I'll have to find a new DM9000 chip first.i will send you new chip
i will send you new chip
Somebody have Hantek DSO1202B ?
Please read "disp" file from the root directory and place it here...
The DM9000 chip most probably also not survived the accident because I can trace no network activity. The LnOE net is also routed to pin 1 of the DM9000 and this net was relatively negative 1.7 V. during the accident. Another soldering job; but I'll have to find a new DM9000 chip first.i will send you new chip
It seems that Hantek tries to prevent people from getting console access. With the latest fw (reply #1589), when I press Ctrl-C, Enter in the serial console, I have only 5 seconds before system sends SIGTERM and reboots the scope.
Received DM9000 yesterday, replaced broken one. Today, doublechecking, fitted LA board in place. Now Ethernet is working too.
Finally the hardware of my MSO is complete. :-+
Thanks again Tinhead. A small token of gratitude is underway by 'snailmail'.
While checking my soldering I found some minor differences with the LA board schematic, I made the following handcorrections in my printout:
DM9000 pin 60 SPEED# routes to pin 51 of J20 P2, E-ACT
DM9000 pin 62 LINK_ACT# routes to pin 52 of J20 P2, E-LINK
DM9000 pin 90 DvDD routes to +3.3D
DM9000 pin 91 IO16 is unconnected
A 0 Ohm R marked R27 (topside) in route LA_CLK25, can be used as testpoint for clock signal to DM9000.
If you have your USB terminal connection open during self calibration you will notice a message when it is ready:i know, there are many other hidden things like :
"mv: can't rename '/autochk.tmp' : No such file or directory". An artefact of some form of factory calibration?
This unit has the 83EB revision FPGA, and I'm not sure if I should bother trying to switch to the 83E9. Thoughts?
The only question I have is regarding the 24 hour clock. It seems to be only a 23 hour clock - unless I'm failing to understand something fundamental.
Thanks again Tinhead. A small token of gratitude is underway by 'snailmail'.
you welcome ... "gratitude " ? huh, whatever it is, thank you!
Can this just be installed via the update menu without needing to do any UART stuff?
Still, it make sense to change to 83E9 design if someone have 83E8,1 UNRAR files
1 UNRAR files
2 Copy from folder <save_from_DSO> file dst1kb_2.06.3_15102b_fact(130114.0).up to FLASH storage
3 Plug flash disk in DSO, run firmware upgrade
..
..
Regards the factory calibration, in case you don't have stable source then don't do anything on that.
Simply run the self calibration and your fine.
Hi again tinhead, about the calibration, as I remember in some post, it is better to do it in Equ-Time setting right? Along with about 1 hour warm up, or it was valid only for the factory calibration?
it was better, but since some time EQU-time mode is not working at all, so no matter what you select you always in real time mode.
For the warm up, 15-30 mins are good enough.
I had to rename the file to dst1kb_2.06.3_15102b_fact(999999.9).up as it was telling me that no update files were found.
rename *.rbf file to dn.rbf
For example, dn_hw1007_83E9_date111122.rbf to dn.rbf
..
..
Oh, and is it normal that when a crash happens all settings revert back to the defaults?
Are there any known problems with the pass/fail testing using the latest firmware?
My scope crashes after the test is running anywhere between a few seconds and a few minutes.
SW 2.06.3 (130131.0) HW 10070x555583eb
Does anyone have 2.06.3 (120927.1) they can supply me? I'd like to do some comparisons. (I assume I'll be able to load an earlier version if I rename it to look like it's a later one)
Are there any known problems with the pass/fail testing using the latest firmware?
My scope crashes after the test is running anywhere between a few seconds and a few minutes.
not on my test DSO, i will try another one and let you know.
the last 4+ hours, two DSOs - a Tekway DST1202B and Voltcraft DSO-162B, both with 130306.0 firmware loaded,
both with 1kHz test signal applied - exact same setup as your and no crash (actually funny to see the event
counter starting after some poi nt again from 0 - without any problem).
the last 4+ hours, two DSOs - a Tekway DST1202B and Voltcraft DSO-162B, both with 130306.0 firmware loaded,
both with 1kHz test signal applied - exact same setup as your and no crash (actually funny to see the event
counter starting after some poi nt again from 0 - without any problem).
Strange. I've also had a PM form someone else who was able to duplicate my test, so that's at least 3. I thought I was going mad last night when I couldn't get it to play up for so long after it failing so regularly during the day.
Strange. I've also had a PM form someone else who was able to duplicate my test, so that's at least 3. I thought I was going mad last night when I couldn't get it to play up for so long after it failing so regularly during the day.
Now your DSO, what is the first number of the serial? (asking because Tekway is not producing DSOs with this particular enclosure since some time), the FPGA
design i assume you loaded 83E9, right?
it would be nice if you would update to the latest fw version (which is 130306.0)with pleasure, but the Hantek site has only dst1kb_2.06.3_15102b_fact(130114.0) version :(
it would be nice if you would update to the latest fw version (which is 130306.0)with pleasure, but the Hantek site has only dst1kb_2.06.3_15102b_fact(130114.0) version :(
and here the latest DSO firmware (for following DSOs only):
- Tekway DST1062B, DST1102B, DST1202B
- Hantek DSO5062B, DSO5102B, DSO5202B
- Voltcraft DSO3062C, DSO1062D
- PCE DSOs: PCE-DSO5062B, PCE-DSO5102B, PCE-DSO5202B
http://www.mikrocontroller.net/topic/205820?goto=3094416#3094416 (http://www.mikrocontroller.net/topic/205820?goto=3094416#3094416)
Feedback as always welcome!
3 days ago, tinhead shared that version:
I was poking around looking for nothing in particular and came across http://www.goodluckbuy.com/hantek-lan-pcb-module-board-ht312-for-oscilliscopoe-.html (http://www.goodluckbuy.com/hantek-lan-pcb-module-board-ht312-for-oscilliscopoe-.html)
Does anyone know anything about this module? and is it compatible with the CROs under discussion in this thread
Cheers
Robik
Hi guys,
I need to buy an oscilloscope and the models I am considering are Hantek DSO5102B and Hantek DSO5202B. I am sorry if my question is stupid but I didn't understand if these two are identical( I mean the hardware) ? I am sure that somewhere in these 100+ pages is mentioned but I really don't have the time to read them right now ( I have to study for my exams) and I need to get an oscilloscope quickly so please could someone tell me if it is worth giving 100 pounds more to get the 200mhz scope or the 100mhz version would be the same after hacking ? I know that is very annoying when someone asks something which is already written somewhere but I am really short of time and I have to buy a scope as soon as possible.
Thank you!
Thank you very much for your quick reply! I guess I will save 100 pounds :) By the way is there any advantage of buying the 200mhz version apart of keeping your warranty (which anyway I guess is useless since I am buying the scope from China) ?I don't think so - but I'm no expert about it. Tinhead (the OP) or one of the other current owners would be better suited to answer that question. And as far as voiding the warranty - try not to. There are videos (like this one from fellow member Mike of mikeselectricstuff) that suggest how to deal with warranty stickers:
I was poking around looking for nothing in particular and came across http://www.goodluckbuy.com/hantek-lan-pcb-module-board-ht312-for-oscilliscopoe-.html (http://www.goodluckbuy.com/hantek-lan-pcb-module-board-ht312-for-oscilliscopoe-.html)
Does anyone know anything about this module? and is it compatible with the CROs under discussion in this thread
Cheers
Rob
Thank you very much for your quick reply! I guess I will save 100 pounds :) By the way is there any advantage of buying the 200mhz version apart of keeping your warranty (which anyway I guess is useless since I am buying the scope from China) ?
I was poking around looking for nothing in particular and came across http://www.goodluckbuy.com/hantek-lan-pcb-module-board-ht312-for-oscilliscopoe-.html (http://www.goodluckbuy.com/hantek-lan-pcb-module-board-ht312-for-oscilliscopoe-.html)
Does anyone know anything about this module? and is it compatible with the CROs under discussion in this thread
Cheers
Rob
Just try this one : http://www.ebay.com/itm/HANTEK-LAN-PCB-HT312-For-Hantek-Oscilloscope-Scopemeter-/121088280120?ssPageName=STRK:MESE:IT (http://www.ebay.com/itm/HANTEK-LAN-PCB-HT312-For-Hantek-Oscilloscope-Scopemeter-/121088280120?ssPageName=STRK:MESE:IT)
Thank you very much for your quick reply! I guess I will save 100 pounds :)
Thank you very much for your quick reply! I guess I will save 100 pounds :) By the way is there any advantage of buying the 200mhz version apart of keeping your warranty (which anyway I guess is useless since I am buying the scope from China) ?
The 60MHz and 100MHz models come with 150MHz probes. I expect the 200MHz models will come with 200MHz probes.
Apart from that ...
Ie: did you try, one day, to implement a trigger output signal through an un used differential pair of pins of the Cyclone III (if you got access to the VHDL code of course ...).
I just checked conrad-uk and this voltcraft (DSO-1062D) is 293 pounds exl. delivery.. The Chinese version - Hantek 100mhz - is 220-230 pounds including free shipping from China. The price of the 60mhz version on ebay is 290 pounds ;D
Like tinhead said, don't forget to add customs (15-30%?) and VAT (20%).But according to the European Taxation and Customs Union, there is 0% duty on an electronic oscilloscope shipped from China (as shown here (http://ec.europa.eu/taxation_customs/dds2/taric/measures.jsp?Lang=en&SimDate=20130403&Area=CN&Taric=9030209190&LangDescr=en)). The problem is sometimes getting the customs people to be aware of this. If you go this route, it's best to have the shipper put the TARIC code (9030 20 91 90) into the documentation. But you do have to pay VAT of course.
I did not know that. Is that also applicable to normal multimeters?
Interesting...So far I have always paid only the price stated on ebay (no duty, vat etc).... I have never bought anything more expensive than 30-40 pounds but still....I didn't have to pay VAT etc...as a matter of fact I pay the VAT when I buy the product from ebay so why should I pay VAT again ?!
as a matter of fact I pay the VAT when I buy the product from ebay so why should I pay VAT again ?!
I don't know what the rules in the UK are, but in NL it's the following:
Up to € 22 value = No duty, no VAT.
From € 22 to € 150 = No duty, yes VAT.
€ 150 or more = Yes duty, yes VAT.
Hantek 100mhz - is 220-230 pounds including free shipping from China. The price of the 60mhz version on ebay is 290 pounds ;D
Do you mean DSO5102P?
(Example there is one who picture DSO5202B but then you read he sell DSO5102P where is total 24k capture memory)
this is not point in my post.
Many times I use example my one Tektronix I set it for 500 point or 1k and not 50k.
If I look what is going on just on the screen area and not at all interest about what is out of screen... . It is good to realize that with 1Gsa/s and with 2ns/div there is just 20 real sample point visible on the screen if screen area is 10div horizontally. So, sometimes I hope I can adjust memory to 20 sample but capture this "waveform" as fast as possible.
Hantek 100mhz - is 220-230 pounds including free shipping from China. The price of the 60mhz version on ebay is 290 pounds ;D
Do you mean DSO5102P?
(Example there is one who picture DSO5202B but then you read he sell DSO5102P where is total 24k capture memory)
http://www.hantek.com/english/news_list.asp?unid=44 (http://www.hantek.com/english/news_list.asp?unid=44)
Do you think Conrad 1062D model is this P serie. Not AFAIK.
:)
...can the DSO5062 be hacked into the 200mhz model, or just the DSO5102? Or are they ALL the same hardware?
here we go ... i did it again:
A complette schematic of hw1005 and hw1007 DSOs(with S/N < 15000)
Hello, do you guys think the hack works also for the DSO5000 P models? I've a DSO5102P so i would like to ....
Thanks
I was planning to use this to make it possible to start an 'upgraded' DSO/MSO in either the DSO or in the MSO mode.
HOWEVER....
The 'upgraded' DSO/MSO is running a later Linux version and fpga.exe is not running here. It is depending on some older library files not present. To solve it properly fpga.exe should be recompiled with the proper libraries. I tried a few tricks found on several forums, like symlinking an older library, but no succes.
So far for my attempt to create a DSO - MSO menu.
so you picked up my idea, cool.
I've tested the script, so far it does works great on 2.6.14. To make this idea "complete" i recompiled
the fpga.exe for Linux 2.6.30.4 (it must be simply linked against ld-linux.so.3, not ld-linux.so.2)
Btw, where you found the proper register? Or did you simply tried them all?
QuoteI've tested the script, so far it does works great on 2.6.14. To make this idea "complete" i recompiled
the fpga.exe for Linux 2.6.30.4 (it must be simply linked against ld-linux.so.3, not ld-linux.so.2)
Thanks again, great: "simply recompile". I did find that problem with: 'readelf -l fpga.exe | grep "program interpreter" ' but I had no idea how to proceed further. Lots of learning to do.
Hi all...
Today I received the QFP100 SRAM = IS61LPS51236A-200TQLI.
What HW mods need to do to use a 2M capability in DSO1202B(exDSO1062B) ?
Somebody tested SRAM replacement? Any results?
I did not get 2Mb IS61LPS51236A-200TQLI to actually work in bench HW1007 correctly. I do see 2MB option enabled in scope menus but actual capture repeats itself when 2MB is allowed, so I assume addressing problem with highest used address pin. Have to check if CPLD pin 47 (used in handheld for SRA18 signal) gives anything out during 2MB capture. Also the SDRAM ZZ pin is not grounded, have to test the effect of that too.
I did not get 2Mb IS61LPS51236A-200TQLI to actually work in bench HW1007 correctly. I do see 2MB option enabled in scope menus but actual capture repeats itself when 2MB is allowed, so I assume addressing problem with highest used address pin. Have to check if CPLD pin 47 (used in handheld for SRA18 signal) gives anything out during 2MB capture. Also the SDRAM ZZ pin is not grounded, have to test the effect of that too.
hw1007 is benchtop, so when running firmware for B models you will not get 2M working. This is because there is a check for
linux version in the firmare, BM/BMV models have 2.6.30.4 instead of 2.6.13 on B models.
On Handheld there is no 2.6.13, there was from the beginning 2.6.30.4 and 2M works.
btw NCG, you can switch to higher linux version by doing following stept:
1- run http://embdev.net/articles/Tekway_MSO#Firmware_upgrade (http://embdev.net/articles/Tekway_MSO#Firmware_upgrade) to get Linux and MSO firmware
(with all these steps -> backup of your factory files, installation of MSO fw, resotre of your factory files)
2- install special BMV model firmware on your temp MSO model, http://www.mikrocontroller.net/topic/289260#3094394 (http://www.mikrocontroller.net/topic/289260#3094394)
You need to run the *dodso* file, http://www.mikrocontroller.net/attachment/173447/dst1kb_2.06.3_dodso.up (http://www.mikrocontroller.net/attachment/173447/dst1kb_2.06.3_dodso.up)
3- use the regular BM/BMV firmware once. You might consider changing logo as well, as described in this thread here somewhere.
I am testing my new MSO5102D (updated to latest Hantec SW but not hacked) and notice that the logic analyser results seems to lag the analogue channels by one trig.
ie. I get the data sampled on the previous trigger for the analyser part and fresh result for the two analogue channels.
Is this a know issue? I do not seem to find anything about it elsewhere.
from system status screen:
model: MSO5102D
SW: 2.07.1 (130321.0)
HW: 10070x555583e9
I am already at step 2 (tested dso.exe check removal for kernel version too) - just curious what does regular BM/BMW update does (the relevant files are)?Quotebtw NCG, you can switch to higher linux version by doing following stept:
1- run http://embdev.net/articles/Tekway_MSO#Firmware_upgrade (http://embdev.net/articles/Tekway_MSO#Firmware_upgrade) to get Linux and MSO firmware
(with all these steps -> backup of your factory files, installation of MSO fw, resotre of your factory files)
2- install special BMV model firmware on your temp MSO model, http://www.mikrocontroller.net/topic/289260#3094394 (http://www.mikrocontroller.net/topic/289260#3094394)
You need to run the *dodso* file, http://www.mikrocontroller.net/attachment/173447/dst1kb_2.06.3_dodso.up (http://www.mikrocontroller.net/attachment/173447/dst1kb_2.06.3_dodso.up)
3- use the regular BM/BMV firmware once. You might consider changing logo as well, as described in this thread here somewhere.
I am testing my new MSO5102D (updated to latest Hantec SW but not hacked) and notice that the logic analyser results seems to lag the analogue channels by one trig.
ie. I get the data sampled on the previous trigger for the analyser part and fresh result for the two analogue channels.
Is this a know issue? I do not seem to find anything about it elsewhere.
I am testing my new MSO5102D (updated to latest Hantec SW but not hacked) and notice that the logic analyser results seems to lag the analogue channels by one trig.
ie. I get the data sampled on the previous trigger for the analyser part and fresh result for the two analogue channels.
Is this a know issue? I do not seem to find anything about it elsewhere.
Can you please give some more details and maybe illustrate with an example? I would like to try reproducing this issue.
The only 'place' I have seen a thing like this is during S condition, repeatedly pressing 'single seq'. You probably will need several pushes anyway before the analog signals in the display refreshes ( bug #40 ) and then you'll see the digital traces lag behind the analog for one refresh event( #41 in my personal buglist ).
A proper buglist for the MSO(MST) models has not been published yet, allthough Tinhead might be working on one, as far as I know.
Just an update on the Pass/Fail crash.
I received an update from Tekway that appears from the file name to be the same version (130306) we have all been using, but I have not had a crash in the last 3 days. And I was running Pass/Fail tests for about 9 hours yesterday.
Pass/Fail was unusable for me before this.
The only thing that suggests it is not the same version is that the file size s quite different.
dst1kb_2.06.3_15202b_fact_130306.0_.up - 2888019 bytes
dst1kb_2.06.3_01102b_fe(130306.0).up - 2,800,232 bytes
Can you please attach this new update? I, and maybe others, would certainly like to have a look at it.
only help.db is different, Tekway's firmware have as well two extra languages "Spanish.lan" and "Portugal.lan"
but it lacks "Chinese.lan" and "Tridchn.lan".
This might be already reason why something work or didn't work properly.
btw NCG, you can switch to higher linux version by doing following stept:
1- run http://embdev.net/articles/Tekway_MSO#Firmware_upgrade (http://embdev.net/articles/Tekway_MSO#Firmware_upgrade) to get Linux and MSO firmware
(with all these steps -> backup of your factory files, installation of MSO fw, resotre of your factory files)
2- install special BMV model firmware on your temp MSO model, http://www.mikrocontroller.net/topic/289260#3094394 (http://www.mikrocontroller.net/topic/289260#3094394)
You need to run the *dodso* file, http://www.mikrocontroller.net/attachment/173447/dst1kb_2.06.3_dodso.up (http://www.mikrocontroller.net/attachment/173447/dst1kb_2.06.3_dodso.up)
3- use the regular BM/BMV firmware once. You might consider changing logo as well, as described in this thread here somewhere.
yeah, here we go ... on your DSO(MSO) it is bad idea to use regular BM/BMV updates, they will of course replace the rcS,
for a regular B model user this does not matter, but for you it does as you have MSO.
For you make sense to use this solution
http://www.mikrocontroller.net/topic/289260#3126759 (http://www.mikrocontroller.net/topic/289260#3126759)
and then to copy (as you haev anyway network on your MSO) the unpacked firmware files instead of install them.
For sure this "sucks", on one side you have 2M on board, on the other side you have MSO.
in the gpl code (e.g. for MSO) there is in "third_part" directory the 4.3.3 gcc toolchain, with all the libs whcih need to
be set in ldconfig flag. I made it very simple, created new directory in third_part, copied fpga code there, re-used make file
from "bmptogif", added section in make file in dir above nad in top dir - that's all. Now, when i compile kernel and drivers
and what so ever tools the fpga code will be compiled as well (with proper gcc, libs, etc. - no need to spend any unnecessary
second on that).
EDIT:
attached my sources and make files. All you need is to download the MSO GPL sources, install them into /opt/build/mso_env,
untar attached file to / and build it (make from /opt/build/mso_env or /opt/build/mso_env/third_part)
it does make sense to compare if the version you got from CD is the same as on website.
I'm using this one
http://www.eedownload.com:8888/mso.zip (http://www.eedownload.com:8888/mso.zip)
but there is also older version available
http://www.eedownload.com:7635/MSO_env.tar.zip (http://www.eedownload.com:7635/MSO_env.tar.zip)
You don't need to configure anything, simply make clean and make.
I had to, for some reason, to make first bootloader and then make all, probably because i missed first time to clean first.
Another lesson learned.
Hi
I am about to purchase a Hantek DSO1102B Oscilloscope,
and I would like to ask a small question..
Is it true that the Hantek Handhelds do not have a Wave Generator?
yes, only DSO8060 have wave generator
That review says that the DSO1060 has a "connector output of square-wave generators".
Does the DSO1102B have those?
Can the Frequency an Voltage of that square wave be set?
From Hantek product palette (as of today) only the DSO8060 have waveform generator (in this case AWG) functionality,
this is actually an "integrated DDS-3x25". The disadvantage of DSO8060 is of course the 250MS/s sample rate.
failing with the error 0x702 and then rebooting, when i try to use the scope its measurements are all over the place any ideas as to what is happening? has it happened to anyone else, or have i just been unlucky, is it curable? anyone got a spare board for sale? Regards jellytot
Working! ;D turns out to be a faulty relay. Now all I've got to do is restore my backup :-\ anyone know if a dds generator is sufficiently accurate to use for calibrating, don't have anything decent at hand. :(
- I actually made a couple of GPL request myself. One at Agilent for the 3000-X and another to vodafone. And in both cases I got the sources I asked for. Took time each time ( > 1 month ) but it worked out fine.Which sources did you get? The Agilent DSO-X 3012A uses WindowsCE and a big custom written program and some custom libraries (I've disassembled it a bit, thanks the the firmware update image is not crypted). And once you have shell access, which you get e.g. if you connect the internal UART and then use u-boot to boot the image (with telnetd patched) over network, you can do interesting things on it. The main program has some nice command line parameters 8)
Tinhead I was thinking of restoring a backup as I deleted the factory calibration files but because I have changed relays is it pointless restoring a backup ? I don't have good precise signal source to calibrate with.
also my restore file is 69206016 while yours is 69206026 should it still work?
also my restore file is 69206016 while yours is 69206026 should it still work?
where i wrote 69206026 ?
From a screenshot on the restore instructions it mentions the file size transfered this is why I was worried :)
(https://www.eevblog.com/forum/index.php?action=dlattach;topic=1571.0;attach=17592)
just a tip for anyone that's doing the restore, Don't forget to use the usb port at the rear and not the front as I was doing for over an hour |O trying different drivers for dnw until I realised :-DD
But happy to say it worked great in the end. Thanks again Tinhead for your great work on these scopes. :-+
just a tip for anyone that's doing the restore, Don't forget to use the usb port at the rear and not the front as I was doing for over an hour |O trying different drivers for dnw until I realised :-DD
I did not make a backup before I flashed it.
So, I have access to the shell through the UART and I have been able to stop the watchdog reset and I have copied a few DSO.exe files from this tread to the scope, but still no go. I get a segmentation fault every time.
What firmware I should download of the site Hantek? DSO1062B or DSO1202B.
Hi,
How to read / write the "DISP" file using DSO-USB-Tool. I proceed as follows:
I select the Read / write File (F4) tab and in the Filename field I entered "/ DISP" then I clik on the "Read from DSO" button. This method does not work.
Thank you.
I'm looking for a oscilloscope which is going to be my first and the Tekway DSO1062B looks like a really nice device.The answer seems to be yes, as nobody has said the contrary in the last posts.
If I were to order a new one today, would I still be able to perform the UART hack? Or did Tekway block it off in a new hard/firmware revision?
If it still is possible I'll be ordering a new one from pinsonne elektronik asap :)
Hi
As the DSO-USB-Tool has a shell option to send comands to busybox. Is it possible to follow the procedure with that tool, without opening the case and soldering the UART?
check circuit specialistsThanks jebcom! Nice to have at least one option besides ebay, and their 30-day return option is nice to know about.
http://www.circuitspecialists.com/digital-storage-oscilloscopes (http://www.circuitspecialists.com/digital-storage-oscilloscopes)
Well I just changed my Voltcraft DSO-1062D to a DSO-1202D, and I think it went ok. I can select 4ns/div, so I guess it's ok now :)
I renamed the dst1062b file to dst1202b, adjusted sys.inf accordingly, and also adjusted tmpdst, logotype and logotype.dis.
Just in case it matters, here is the system information:
Model: DSO1202D
SW version: 2.06.3 (130306.0)
HW version: 10070x555583eb
EDIT: I do get an error that a logo file cannot be found for the 1202 version, but it boots up just fine.sure, but here somewhere in thread (haha) are all the logos you need (i think),
I renamed the dst1062b file to dst1202b, adjusted sys.inf accordingly, and also adjusted tmpdst, logotype and logotype.dis.
actually it is only necessary to rename the /dst1062b to /dst1202b
and (if you need boot logo) edit the /logotype.dis file
Everything else will be automatically changed after two reboots after you remaned the /dstxxxx file
Just in case it matters, here is the system information:
Model: DSO1202D
SW version: 2.06.3 (130306.0)
HW version: 10070x555583eb
is your serial number higher than 15000? (the last numbers)
Btw, there is no such model DSO1202D, so copy paste error or you really typed wrong name?
For the logotype.dis file, it is better to use something generic, like "hantek_DSO5202B", which
will give you then DSO5202B as model.
EDIT: I do get an error that a logo file cannot be found for the 1202 version, but it boots up just fine.sure, but here somewhere in thread (haha) are all the logos you need (i think),
for the functionality it does not have any influence.
I might have seen the post you'd be looking for just earlier today or yesterday. Wasn't able to find it quickly, but maybe this one will help:188 pages... :-DD I'll see if I can find them :)EDIT: I do get an error that a logo file cannot be found for the 1202 version, but it boots up just fine.sure, but here somewhere in thread (haha) are all the logos you need (i think), for the functionality it does not have any influence.
as few people asked for it, attached BSDL files for:
- Tekway DST1000(A) - SoC S3C2410
- Tekway/Hantek/Voltcraft/Extech B/BM/BMV/S series DSO/MSO/Handhelds, S/N < 15000 - SoC S3C2440
- Tekway/Hantek/Voltcraft/Extech B/BM/BMV/S/P series DSO/MSO/Handhelds, S/N > 15000 - SoC S3C2416
The S3C2416_bsdl file is as well good for Owon SDS users.
as few people asked for it, attached BSDL files for:
- Tekway DST1000(A) - SoC S3C2410
- Tekway/Hantek/Voltcraft/Extech B/BM/BMV/S series DSO/MSO/Handhelds, S/N < 15000 - SoC S3C2440
- Tekway/Hantek/Voltcraft/Extech B/BM/BMV/S/P series DSO/MSO/Handhelds, S/N > 15000 - SoC S3C2416
The S3C2416_bsdl file is as well good for Owon SDS users.
yes, Owon SDS series is using as well the same Samsung S3C2416 SoC as Hantek in their latest hardware revision
(all "P" models, all others with S/N > 15000)
Hi tinhead!
For Owon SDS?
Sorry, but:
What is the purpose? What I can modify with this BSDL file?
Do you have any updated information about DSO5072P
You say: "there is complettly different SoC/new PCB"
Can this model be updated (hacked) with RAM memory?
I can now select 2ns/div and 2ns is 500MHz. Does it have something to do with the sampling rate?
Hi,
i have a cheap Fluke 124 Scopemeter.
Would a Rigol 1052 perform better than this old Fluke Scopemeter?
I don't need all the multimeter option of the fluke?
and recommendation?
[8mv]167
[20mv]359
[400mv]403
[2000mv]1999
*** Warning - bad CRC or NAND, using default environment
##### EmbedSky BIOS for SKY2440/TQ2440 #####
Press Space key to Download Mode !
Booting Linux ...
Copy linux kernel from 0x00200000 to 0x30008000, size = 0x00200000 ... Copy Kernel to SDRAM done,NOW, Booting Linux......
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.30.4 (root@rain-fc4) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #9 Mon Dec 12 11:50:21 CST 2011
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
CPU: VIVT data cache, VIVT instruction cache
Machine: TQ2440
ATAG_INITRD is deprecated; please update your bootloader.
Memory policy: ECC disabled, Data cache writeback
CPU S3C2440A (id 0x32440001)
S3C24XX Clocks, (c) 2004 Simtec Electronics
S3C244X: core 400.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz
CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0
NR_IRQS:85
irq: clearing subpending status 00000002
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
console [ttySAC0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61316KB available (3116K code, 333K data, 100K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Calibrating delay loop... 199.47 BogoMIPS (lpj=498688)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 296 bytes
NET: Registered protocol family 16
S3C2440: Initialising architecture
S3C2440: IRQ Support
S3C24XX DMA Driver, (c) 2003-2004,2006 Simtec Electronics
DMA channel 0 at c4808000, irq 33
DMA channel 1 at c4808040, irq 34
DMA channel 2 at c4808080, irq 35
DMA channel 3 at c48080c0, irq 36
S3C244X: Clock Support, DVS off
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Calling CRDA to update world regulatory domain
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
yaffs Sep 21 2011 16:15:16 Installing.
msgmni has been set to 119
alg: No test for stdrng (krng)
io scheduler noop registered (default)
s3c2440-uart.0: tq2440_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2440
s3c2440-uart.1: tq2440_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: tq2440_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2440
loop: module loaded
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
s3c2440-nand s3c2440-nand: Tacls=2, 20ns Twrph0=3 30ns, Twrph1=2 20ns
NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit)
Scanning device for bad blocks
Creating 4 MTD partitions on "NAND 64MiB 3,3V 8-bit":
0x000000000000-0x000000040000 : "EmbedSky_Board_uboot"
0x000000200000-0x000000400000 : "EmbedSky_Board_kernel"
0x000000400000-0x000003ff8000 : "EmbedSky_Board_yaffs2"
0x000000100000-0x000000200000 : "EmbedSky_Board_logo"
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
mice: PS/2 mouse device common for all mice
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c2410-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
Linux video capture interface: v2.00
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: starting watchdog timer
s3c2410-wdt s3c2410-wdt: watchdog active, reset abled, irq enabled
mapped channel 0 to 0
s3c2440-sdi s3c2440-sdi: powered down.
s3c2440-sdi s3c2440-sdi: initialisation done.
Advanced Linux Sound Architecture Driver Version 1.0.18a.
No device for DAI UDA134X
No device for DAI s3c24xx-i2s
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: UDA134X <-> s3c24xx-i2s mapping ok
s3c2440-sdi s3c2440-sdi: powered down.
ALSA device list:
#0: S3C24XX_UDA134X (UDA134X)
TCP cubic registered
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
lib80211: common routines for IEEE802.11 drivers
s3c2410-rtc s3c2410-rtc: setting system clock to 2013-06-05 11:33:53 UTC (1370432033)
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:2.
Freeing init memory: 100K
__init s3c24xxfb_probe
setting vert: up=29, low=13, sync=3
setting horz: lft=40, rt=40, sync=48
s3c2410fb_activate_var
S3C2410_LCDCON1_CLKVAL(default_display->setclkval)=1
Console: switching to mono frame buffer device 100x30
fb0: s3c2410fb frame buffer device
var.xres=800
var.yres=480
var.bits_per_pixel=8
var.xres_virtual=800
var.yres_virtual=480
fix.id=s3c2410fb
fix.smem_start=866123776
fix.smem_len=768000
fix.type=0
fix.type_aux=0
fix.xpanstep=0
fix.ypanstep=0
fsetting vert: up=29, low=13, sync=3
setting horz: lft=40, rt=40, sync=48
s3c2410fb_activate_var
S3C2410_LCDCON1_CLKVAL(default_display->setclkval)=1
ix.ywrapstep=0
fix.line_length=800
argv[1]=16
var.xres=800 var.yres=480 var.bits_per_pixel=16
show logo,video_buf_size = 768000
bwscon:0x2201d110
fpga bank 221422
dso-fpga: install ok
dso-spi initialized
Init spi success!
New Log Write OK Length:21
open spi error
dm9000 Ethernet Driver, V1.31
dm9000 dm9000.0: read wrong id 0x002a0028
dm9000 dm9000.0: read wrong id 0xffffffff
dm9000 dm9000.0: read wrong id 0xffffffff
dm9000 dm9000.0: read wrong id 0xffffffff
dm9000 dm9000.0: read wrong id 0x2b2a2928
dm9000 dm9000.0: read wrong id 0xff2a2928
dm9000 dm9000.0: read wrong id 0x2b2a2928
dm9000 dm9000.0: read wrong id 0xffffffff
dm9000 dm9000.0: wrong id: 0xffffffff
dm9000 dm9000.0: not found (-19).
Try to bring eth0 interface up ...
Hantek GPIO(buzzer/speaker),(c)20110309
gpioG11 initialized
speaker on
Beep
ifconfig: SIOCGIFFLAGS: No such device
dso-buzzer initialized
ifconfig: SIOCSIFHWADDR: No such device
ifconfig eth0 hw ether 10:23:45:67:89:ab
ifconfig: SIOCSIFADDR: No such device
ifconfig eth0 192.168.1.55 netmask 255.255.255.0 up
/sbin/net_set: line 5: route: not found
add default gw 192.168.1.2
Done
i2c /dev entries driver
s3c2440-i2c s3c2440-i2c: slave address 0x10
pdata->frequency=6000
s3c2440-i2c s3c2440-i2c: bus frequency set to 9 KHz
s3c2440-i2c s3c2440-i2c: i2c-0: S3C I2C adapter
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
s3c2410_udc: debugfs dir creation failed -19
s3c2440-usbgadget s3c2440-usbgadget: S3C2440: increasing FIFO to 128 bytes
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$4s3c2410_udc_disable()
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
s3c2440_clkcon=00FF7FF0
fpga download file_name :/dn.rbf
status: 0x1
fpga_down_load file name : /dn.rbf.
data DOWN finish.
dso-spi:FPGA_DOWNLOAD ok.
release
no update file to foud
now run app .....
var.xres=800
var.yres=480
var.bits_per_pixel=16
var.xres_virtual=800
var.yres_virtual=480
fix.id=s3c2410fb
fix.smem_stasetting vert: up=29, low=13, sync=3
setting horz: lft=40, rt=40, sync=48
s3c2410fb_activate_var
S3C2410_LCDCON1_CLKVAL(default_display->setclkval)=1
rt=866123776
fix.smem_len=768000
fix.type=0
fix.type_aux=0
fix.xpanstep=0
fix.ypanstep=0
fix.ywrapstep=0
fix.line_length=1600
argv[1]=8
var.xres=800 var.yres=480 var.bits_per_pixel=8
Please press Enter to activate this console. s3c2440_clkcon=00FF7FF0
cannot open lcd
: No such file or directory
cannot open lcd
: No such file or directory
[root@Hantek /]#
Thanks Tin for all the work and information you have put forward here.
Very much appreciated.
Just modded a Hantek DSO5062BM
Tin,
Are you still needing copies of BM models backups? If so let me know. I can supply
The first post is a bit confusing with so much informationstrikethrough'ed
I appreciate its better to not delete the information though, maybe we can move it
The BM model backup firmware script is very difficult to find for new users (as you link to the B version in the instructions)
I have changed the BW to 200Mhz and upgraded to 1202 latest firmware (130xxxx). Everything is fine now. Thanks again.
And one more question - when I turn on the unit and it is still cool, the fan starts blowing for some time, and then stops despite that the unit heats up. The BNC connectors becomes hot enough that it is hard to keep my finger on them for more than 3-4 seconds, and the fan is still off.
Is this a normal behaviour?
Fan test works (the fan blows when "open" and does not blow when "close).
Any one experienced this before and could it be the hardware or possibly NAND flash corruption.
Where do I get the "gpg.exe" and "guzip.exe" from. Can it done on a Windows platform
Better still does anyone have all the components already extracted from the latest released software.
This does not quite fit into the firmware thread but I have regular problems with the supply connector: every three months or so I have to open the scope and refit the connectors. I've bent the odd and even pins a little in the opposite ways and tightened the female plugs a bit but I'm not sure how well this will hold up. Is there any other way to avoid the regular 'white screen' problem?
AFAIK not, but?
Was there ever any serious issue with this scope like the well-known Owon noise problem?
Not a single wrong unit, but many of them?
oh yes, there was between Feb 2011 and Jun 2011 hardware revision hw1005.I (unfortunately) got a hw1005 on april 2011 (I was happy to have a new - better - hardware at that time :palm:)
That was first revision made by Hantek, and it was not working as expected.
There was a difference between production and test unit, the FPGA design was
just a bit over the limit, so while sampling with 1GS/s there was a lot of distortion
making these DSO useless at 1GS/s.
I can't tell you how many units was affected exact, but it was something like 90%
The remaining 10% got special FPGA deisgn, making them bit more noisy but stable.
I (unfortunately) got a hw1005 on april 2011 (I was happy to have a new - better - hardware at that time :palm:)
Is there a way to know if I'm 10% happy or 90%...?
I have read through most of the 121 pages here and I am confused whether this scope can be hacked
to 200MHz or not. As the 60MHz model is about $100 more expensive.
Looking at buy this one
http://www.ebay.com.au/itm/Hantek-DSO5102P-Digital-Oscilloscope-100MHz-1Gs-2CH-7-TFT-Compared-TEK-TDS2012-/121080518250?pt=BI_Oscilloscopes&hash=item1c30f6166a (http://www.ebay.com.au/itm/Hantek-DSO5102P-Digital-Oscilloscope-100MHz-1Gs-2CH-7-TFT-Compared-TEK-TDS2012-/121080518250?pt=BI_Oscilloscopes&hash=item1c30f6166a)
I have read through most of the 121 pages here and I am confused whether this scope can be hacked to 200MHz or not. As the 60MHz model is about $100 more expensive.
Sorry if it has been asked already.
Nick
Just watched dave's review and as an owner of this scope I'd like to know if anyone has any clue about why is the analog frontend makes the captured signal "jump all over the place", could it be his hardware revision? How can I test without that fancy evaluation board he got?
2. What is the difference, if any, between a Hantek DSO5102B and a DSO5102P?B has 1M memory (http://www.hantek.com/english/produce_list.asp?unid=78), P has only 24K (http://www.hantek.com/english/produce_list.asp?unid=160). Other than that, the specs look identical.
2. What is the difference, if any, between a Hantek DSO5102B and a DSO5102P?B has 1M memory (http://www.hantek.com/english/produce_list.asp?unid=78), P has only 24K (http://www.hantek.com/english/produce_list.asp?unid=160). Other than that, the specs look identical.
and "P" model have brand new mainboard (which contains different SoC and DDR memory), newer Linux (3.x).Thanks for that info. Found the web page for the "P" version and it looks like it's just an attempt to lower the cost of the scope which makes sense with the lower memory count.
Thanks, couldn't find any specs on the Hantek site, they just listed their "DSO5000C Series" with no real info on it in English.2. What is the difference, if any, between a Hantek DSO5102B and a DSO5102P?B has 1M memory (http://www.hantek.com/english/produce_list.asp?unid=78), P has only 24K (http://www.hantek.com/english/produce_list.asp?unid=160). Other than that, the specs look identical.
and "P" model have brand new mainboard (which contains different SoC and DDR memory), newer Linux (3.x).Thanks for that info.
Other than the smaller amount of memory, is that new mainboard better than the old mainboard or did they simply redesign it to lower production costs?
Was the Hantek DSO5102B with the older mainboard just the Tekway DST1102B hardware and firmware sold under a different brand name?
and "P" model have brand new mainboard (which contains different SoC and DDR memory), newer Linux (3.x).Thanks for that info.
Other than the smaller amount of memory, is that new mainboard better than the old mainboard or did they simply redesign it to lower production costs?
they redesigned the PCB because the main SoC is EOL. Now they using Samsung S3C2416 instead of S3C2440.Was the Hantek DSO5102B with the older mainboard just the Tekway DST1102B hardware and firmware sold under a different brand name?
afaik Hantek nd Tekway belongs to same shareholders, they did a merger to optimize production costs. On the other side they selling still under own names (even if firmware is actually owned by Tekway and mainbaord produced by Hantek) and Tekway costs more (on the other side i know they running burn-out tests). What else behind, no idea, this is all they told me.
Hello!
Is this model compatible with the hack?
Hantek DSO5072P Digital Oscilloscope 70MHz 1Gs 2CH 7" TFT WVGA(800x480)
http://www.ebay.com/itm/121089632989 (http://www.ebay.com/itm/121089632989)
Hello!
Is this model compatible with the hack?
Hantek DSO5072P Digital Oscilloscope 70MHz 1Gs 2CH 7" TFT WVGA(800x480)
http://www.ebay.com/itm/121089632989 (http://www.ebay.com/itm/121089632989)
everything you need ti know is posted here
https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg21170/#msg21170 (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg21170/#msg21170)
Just watched dave's review and as an owner of this scope I'd like to know if anyone has any clue about why is the analog frontend makes the captured signal "jump all over the place", could it be his hardware revision? How can I test without that fancy evaluation board he got?
I'd really like to know more as well. Any thoughts on this guys? Tinhead?
That ringing Dave discovered really is horrible. How can I trust the scope is displaying an accurate waveform without having to compare it to another scope?
Rigol has excellent signal and trigger integrity.
But it seems nobody is reading what i wrote...this don't is true
Not sure if it's a bug or a 'feature' but software measurements while in Peak mode are wrong.
Is there any way to let the scope save only .gif files and ignore .bmp files? Not sure, but probably the few seconds spent saving are actually spent writing the bmp file.
Is there any way to simulate segmented memory? I might be able to do some stuff with the recorder function if I know exactly the timing between RS232 messages, but is there a way to do this trigger-based instead of time-based?
You've said something about time-grading with 4/16 levels, is there any way to control this? Is it dependent on the wave intensity or contrast? Is it dependent on persistency duration? For me this is really not transparent how it works, I have more luck catching glitches with persistence set to off (50 fps, 4k buffer).
How fast is the rise time of the probe cal output? I seem to get a consistent 2us, but not sure how much of that is the actual probe (not much) and I don't have fancy equipment to measure it.
Another issue/feature: boot count and upgrade count get reset to zero after upgrade. I went from 130131.0 to 130425.0this is not bug, it is like that since first fw version. I have no idea why, i guess to remove any evidence of cross model/version updates. Both information are in /sys.inf and that file ie being replaced during update.
Not sure if it's a bug or a 'feature' but software measurements while in Peak mode are wrong.
haven't tested but i would say the selected memory depth is too smallHow fast is the rise time of the probe cal output? I seem to get a consistent 2us, but not sure how much of that is the actual probe (not much) and I don't have fancy equipment to measure it.
the CPLD itself goes down to ps range, the driver however includes low pass. You can simulate that circuit to get exact values, see attached schematics (i need to update the pdf, few values were wrong)
1500 replies and (nearly) 250000 views ... Dave, where is my DMM ? :-//
Damn you tinhead! I can never catch up!! :scared:
1500 replies and (nearly) 250000 views ... Dave, where is my DMM ? :-//
Damn you tinhead! I can never catch up!! :scared:
Well - I spoke too soon. ;D 6 months later and we've cracked 100 pages (https://www.eevblog.com/forum/testgear/first-impressions-and-review-of-the-rigol-ds2072-ds2000-series-dso/msg260019/#msg260019) - just 14 shy of 1500 replies. Although I know we'll never catch you in views, see you at the top (of replies) soon. ;)
and here is my answer
https://www.eevblog.com/forum/testgear/first-impressions-and-review-of-the-rigol-ds2072-ds2000-series-dso/msg260445/#msg260445 (https://www.eevblog.com/forum/testgear/first-impressions-and-review-of-the-rigol-ds2072-ds2000-series-dso/msg260445/#msg260445)
Btw, i got DMM from Dave, i will make a separate thread about that (well, because i hacked it already ...)
My first post here, so I'd like to start by thanking tinhead for some pretty heroic effort in maintaining information about these scopes - it's incredibly useful.
I have one question though. I recently asked a seller offering the MSO5102D for the hardware version number, as I'm under the impression these are basically the same as the DSO5102B but with the extra LA board, and so hardware/FPGA versions should be comparable. He replied with "1010X55558340", which doesn't look quite like any I've seen mentioned. Was my assumption wrong, or could this be some really old (or really new) version?
I recently asked a seller offering the MSO5102D for the hardware version numberIt would also be interesting to know what software version (and software date) they're currently shipping on these. My MSO5202D is hard version ...83e9, soft 2.07.1(date=130321.0) This software version was withdrawn, and now a much older version is available. Also whether the logic analyzer actually works properly, save to usb works, and system date can be set.
These 1010X55558340 you reported, that make sense for me, hardware revision 1010 and FPGA revision 8340. That means Hantek/Tekway released already MSO with latest hardware (i wish i could see inside such DSO/MSO).
It would also be interesting to know what software version (and software date) they're currently shipping on these. My MSO5202D is hard version ...83e9, soft 2.07.1(date=130321.0) This software version was withdrawn, and now a much older version is available. Also whether the logic analyzer actually works properly, save to usb works, and system date can be set.
I'm tempted to take a punt and see what it's like.
It would also be interesting to know what software version (and software date) they're currently shipping on these. My MSO5202D is hard version ...83e9, soft 2.07.1(date=130321.0) This software version was withdrawn, and now a much older version is available. Also whether the logic analyzer actually works properly, save to usb works, and system date can be set.
Hello
Thank you again for your work!
Do you know if the "P" model can be "hacked" to add extra RAM?
Would it be possible to change the operating system distro on the Hantek scopes? Maybe install Ubuntu on it?
Backup tool for DSO5000P models
How to use it (backup):
Unzip the attached file, go to Backup_P_models and copy the dso5kp_backuptool.up to empty usb flash drive.
Insert it into your DSO and run "firmware update" from DSOs "Utility Menu".
This will create a folder on your USB Flash drive containing all MTD partition dumps.
I get error 0xFE... I can save waveforms so usb drive seems ok.
I recently got one of those DSOs (5072P) and noticed the software download is down on the english side of the Hantek website.
btw tinhead, what do you know about the 5072p, what does the p mean?
oh well.. I'm hoping its still hackable :)btw tinhead, what do you know about the 5072p, what does the p mean?
It's the model without long memory I believe. Only 40k.
yes, it is. Updated mine to 40k by new fw and 200 mhz bw just renaming a file (see first post) ... thanks to tinhead for his great work ;D
this is crap, someone just bought latest MSO5202D model from Hantek and installed latest firmware from Hantek website. ... and of course the MSO is now bricked !!!I just did this to an MSO5102D. It's on it's way back to China. Not happy >:(
this is crap, someone just bought latest MSO5202D model from Hantek and installed latest firmware from Hantek website. ... and of course the MSO is now bricked !!!I just did this to an MSO5102D. It's on it's way back to China. Not happy >:(
cp /mnt/udisk/dso/app/dsod /dso/app/dsod
cp /mnt/udisk/dso/drivers/tq2416_backlight.ko /dso/drivers/tq2416_backlight.ko
cp /mnt/udisk/etc/init.d/rcS /etc/init.d/rcS
cp /mnt/udisk/OurLanguages/English.lan /OurLanguages/English.lan
cp /mnt/udisk/dso_bin /dso_bin
chmod 777 /dso/app/dsod
chmod 777 /dso_bin
chmod 777 /etc/init.d/rcS
sync
sync
rm /dso.exe
so is $280 including dhl express shipping a good price for this?it is probably the best you can get Sure, 40k are not 1M, but honestly most things can be done with 2.5k^^
and has anyone ever gotten the LA addon for a 5072 scope?
any photos of the insides of a 5072p?
... and i got solution from Hantek. In principle all you needed is set of files which were repalced as you installed the wrong firmware.Thanks for the info. I really wish that Hantek would've provided this to me when I emailed their support staff.
my hantek arrived today, far sooner than I expected for $10 express shipping :) I'm very happy :)
any thing you want me to do tinhead?
my hantek arrived today, far sooner than I expected for $10 express shipping :) I'm very happy :)
so make a backup, just in case.any thing you want me to do tinhead?
my post above, on the frontend.jpg, there are two transistors together - first is marked 6K, second 3EM. Tell me if your DSO is still having this combination.
is this normal or is there something wrong? I dont want to turn it off unless you say its okay.
is this normal or is there something wrong? I dont want to turn it off unless you say its okay.
no, for some reason this didn't work properly on your DSO. There is problem with nanddump, even with proper params it does read on some DSO forever, looks for me as cloned bad partition. When i do the backup on virgin NAND, it works.
All you can do now is to backup your device specific files, use that tool http://peter.dreisiebner.at/dso-usb-tool/ (http://peter.dreisiebner.at/dso-usb-tool/)
go to virtual shell, insert flash drive and copy files from / to /mnt/udisk/
my question on the serial number of mine. is it a newer model or older model? 035000xxx
but I'm getting the dreaded fe error on the3.40 firmwares you posted. not sure whats going on there..
but I'm getting the dreaded fe error on the3.40 firmwares you posted. not sure whats going on there..
don't worry, the DSO you ("P" model) have is complettly new design. There is no other firmware version than 3.x for your DSO.
Other models (like "B" and "MSO", "BM/BMV" not yet confirmed but probably the same problem) have multiple hardware
revisions:
- hw0, hw1005, hw1007 with Samsung S3C2440 SoC - with firmware 2.x
- hw??? with Samsung S3C2416 SoC - with firmware 3.x
For both, ppl with 2.x or/and 3.x firmware installed, when then install different firmware the DSO/MSO will get bricked.
So they have to watch out what they installing. For you as already said, didn't matter, your DSO is new, based on
S3C2416 and there only existing firmware is already 3.x. You can't install 2.x because there was never 2.x for your DSO,
you can't install firmware from other models because they using different naming cnvention for update files and different
firmware encryption pwd.
alright, anything else you want me to do?
anyway, I tried to run all the commands that your tool runs from the serial console.. and it seems to get stuck on this line.
nanddump -o -b -l 0x7900000 -f /mnt/udisk/dump/root.bin /dev/mtd3
so what kind of command do I need to run to backup the scope then? or just some files?
Hello,
I wonder if it is possible to reset the "bout count" and "upgrade count" counters?!
THX
Now i must solder the pins in order to connect the uart adaptor... :)
it still displays the 5072p logo on booting..
I edited the logotype (I think that displays the proper model # in the system info) and logotype.dis and the boot logo still reports 5072p
oh well, it is not really complex. You have to compile kernel and the frame buffer driver - where the boot logo is located.
You need of course the GPL source for these DSOs, check here (there are two version, to get all you need, you need to download both)
https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg266507/#msg266507 (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg266507/#msg266507)
time to install getright and try and see if that can download it.. we shall see
okay one is done, took nearly 10 hours to download with getright, the other file is still downloading. they have such a bad connection apparently.
Do you know what is the max sample rate/second than can be transfered to pc through lan on DSO5000P Series (for real time data login).
Feedback is welcome.
Sorry, does anyone have a copy of new DSO5202P firmware? I'm trying to upgrade my 5072p, have no problems with 5102 version, but link to 5202P from the http://www.hantek.com.cn/en/PagesFW_Vzxgj.html (http://www.hantek.com.cn/en/PagesFW_Vzxgj.html) doesn't work...
so far ok, maybe except this :Thanks, the section is revised now.
"After a bandwidth upgrade it is recommended to also upgrade the hardware input stage of your DSO as described below".
I do not recommend to change anything in the hardware without real need. There are multiple variation of the hardware, currently even two complette different frontends. So for sure, for these with bad response it make sense to apply modifications. But not based on what the enduser think or measure, but based on components values! I know lot of professionals not capable of doing simple measurment^^.If I get you right you think it is wrong to recommend a hardware mod for everyone just measuring an overshooting square wave (as you think there is too much risk of measuring bullshit)? Makes sense somehow.
how to distinguish between a good and a poor input stage then? You say based on component values, but as you say there seem to be a lot (or at least several) different component values out there... Which are worth upgrading and which are not?
Feedback is welcome.
How do i fix this?
Under windows the DSO is shown as USB\VID_0000&PID_00005&FEC3355&0&1.
Windows suggests that the driver from Hantek's website isn't for this device.
--- reproduceable crashes on specific settings---
With both channels displayed, "Acquire" settings set to "Type: Real Time; Mode: Average; Averages: 128; Mem Depth: 20k" the scope always crashes after a few seconds (with fast time scale).
With slow timescale (like 40.0ms) I can count the changes of the "a"/"T"-icon which always stops after about 120 acquisitions.
These crashes don't happen with any other setting (single channel / 40k mem depth or 64 averages). Is this a general bug, can anyone reproduce this behaviour? or is this some hardware/software issue with my device?
Another question: The latest software shows a menu entry which I didn't notice with old version: "Utility / page 3 / Option ... / Video" .this is the video player option known from DSO5xxxBMV
This entry is always disabled, what is it supposed to do ?nothing, i don't think all the necessary libs/apps (mplayer) are available on P models, on the dump i'm working with they not there.
the /dn.rbf seems to be missing as well, that looks generally bad when already two files are broken.
that looks like wrong dso.exe or missing one or more libs, probably libc
I can for sure attach more files, but that looks here as broken NAND/file system.
So it would be more usefull if someone else could test it as well and let us know the results (together with the HW/FPGA design version, your is hw ver: 10000xffff8103)
i'm not able to reproduce this (can run DSO for minutes) however i don't have FPGA attached so no data acquired (on the other side no data is data as wel, but maybe the pure fact that my SoC can't get anything from FPGA is not stopping the firmware from working).Thanks for checking this, however I am a little confused... what do you mean by "don't have FPGA attached" ? Did you unsolder it from mainboard? ???
Another question: The latest software shows a menu entry which I didn't notice with old version: "Utility / page 3 / Option ... / Video" .this is the video player option known from DSO5xxxBMV
[...]
Sure, you could enable that menu, but for what when the player is not working.
So it would be more usefull if someone else could test it as well and let us know the results (together with the HW/FPGA design version, your is hw ver: 10000xffff8103)
I can confirm this bug. dso.exe crashes with:
dso.exe: opt/average_opt.c:469: Avg_AvgArrayAddAndAvg: Assertion `((void *)0) != pt_average' failed.
ver 8101
Thanks for checking this, however I am a little confused... what do you mean by "don't have FPGA attached" ? Did you unsolder it from mainboard? ???
So it might be a issue within FPGA?
I thought I might have been some functionality to record video of the DSO-screen for educational purposes or something like that.
I am glad it's no hardware issue with my mainboard and might likely be fixed somewhen. With knowing this bug it can be easily be avoided and honestly I don't really need these settings very often.
I've installed 2.06.3(130814.0) and I have the DSO back up and running.
There's obviously something weird going on with the files i have here. Tinhead can you post the correct links to the files i need to update my DSO to your latest software and firmware please? Just to be sure i'm using the correct files?
How do i flash the firmware via uart? I'd like to revert to an older version to test.
the 2.06.3(130814.0) is the latest for your DSO (and so far i haven't done any patching to it). So when it runs, then everything fine.
The DSO itself seems to read reasonably accurately up to 200Mhz and then tails off after that.
you should check as well if your DSO is using the less good combination of resistors in frontend.
... is it really worth the hassle of changing them? And by that i mean am i going to see much more than 200mhz usable?
I don't have anything that will put out a square wave at any reasonable frequency. |O
I'll test it when i can borrow a decent function generator.
in my opinion
:-DD. Seriously though. Trust the many people who have fast function generators and have tried this before.in my opinion
i don't give a shit about your opinion ... when you too dumb to read specs, compare results, check all the measurments made by me and lot of other ppl posted here and on the mikrocontroller.net forum (there are two looong threads about these DSOs, longer as this one here) then really, nobody cares about hat you think.
to be sure one has to connect a signal generator say a sinus wave 180-200MHz on a pre hacked osci , then repeat the same after hacking.
which i never saw here on this forum and elsewhere.
Perhaps he's just trying
Perhaps he's just trying
he posted as well (as new user) on mikrocontroller.net, in mutiple threads. So he must be
- fanboy of what so ever
- desperate Hameg employee (haha, no, that's joke guys)
- dumb troll
To ignore one - two ppl who think they "improved or hacked something" is generally said ok, the internet is full of such stories. But to ignore thousands of people (and all their experience) is another story.
...
But to ignore some doubtfull people (and all their questions) is another story.
Cheers !
SEC S3C2410DX Test B/D (which is not on the install CD)
Best course is to ignore ignorant people who are deliberately trying to anger you with their unsupported opinions. To respond only makes them feel wanted - like the unloved child provoking a parent to punish them.
I recently saw a discussion about handheld Hantek scopes being up-gradable as well, so I searched this thread but found nothing about my model.
Can a Hantek DSO8060 be upgraded from 60MHz bandwidth?
It looks like Hantek upped the sampling rate at some point for this model, so I think it has 250MS/s. That's still 4 times lower than the 1060, maybe it has to do with the extra function generator that's taking some FPGA real-estate?[/font][/size]
I guess 60MHz will do for my use. :-/O
I've got a little problem with my Hantek scope. I bought the DSO5102B back in early 2010, before this thread started. Judging by the condition of packaging when it arrived it had been around for a while before I got it so its now probably getting on for four years old.
recently when I started using it again I noticed that it was losing trigger settings and getting strange offsets and calibration changes when powered off. It would work ok. after self-calibration then lose it all again next shut down.the selfcalibration is creating files and saving its own results into memory. So that can be file system error, the data can't be saved were the already loaded into memor is giving you working DSO until next reboot.
Anyway this gave me the excuse to buy another scope ;)it is always good to have an excuse :)
When I pulled it apart I found that the backup battery was low and decided to change it. Intended to do this with power on but got called away and forgot to boot up when I came back before changing battery.afaik the battery is only used to save the date/time, and afaik the firmware don't care about what set there.
Scope now powers up with the standard noises (relay clicking etc) and the usual buttons light up but the screen is dead. Functions like autoset appear to work, or at least make the right noises and vertical gain relay clicks at about the right point etc.
Before I make any more stupid mistakes can anyone give some advice on what to do next?
Many Thanks Tinhead - you are amazing.
Some further information: the hardware is hw0 and I hacked the scope using your original patch on a usb stick. The faults occurred with all firmwares and 130425.0 is currently installed.
I'll have a look at the schematics and the items you suggest, here's hoping it's not just a box of spare parts.
looks like bad contact on the large FPC, so the display is not getting the +5V for backlight. It can be as well the power supply cable on right side. This plug supply +5V for USB and display and +3.3V for the whole digital part of the DSO. So when this is plug issue, you should not measure any voltage on the USB port on the frontpanel. If there is 5V then it is the FPC bad contacting.
Regards your DSO, solder a wire and you fine. Who cares about when the display goes on :P
thought perhaps there was some reason why they put the switching circuit there in the first place. Is there?
Sorry, does anyone have a copy of new DSO5202P firmware? I'm trying to upgrade my 5072p, have no problems with 5102 version, but link to 5202P from the http://www.hantek.com.cn/en/PagesFW_Vzxgj.html (http://www.hantek.com.cn/en/PagesFW_Vzxgj.html) doesn't work...
ask Hantek! I told them already 4 weeks ago that this link didn't work, but still not fixed.
Update on problems:
Any suggestions?
Unfortunately, no. Same for Russian dealer, no answer. Maybe that's because I wrote 5072 serial during registration.
Update on problems:
Any suggestions?
it would be nice if you could first update to latest firmware, there are sometimes hugh differences between versions
ehm, i thought you bought real 5202P and not 5072? I saw some on ebay, but honestly no idea if they really exists or simply stupid dealers. Sure, Hantek is listing that model, but who knows.
Problem Solved! :)
Took a closer look at the PCB and found discolouration of some pins on both top adc's. Looked like flux residue and cleaned up easily with alcohol and q-tip
I think it really exists, it can be pre-ordered from local dealer: http://www.hantek.ru/products/dso5202P.html (http://www.hantek.ru/products/dso5202P.html)
But this dealer warns that questions are forwarded to China and it can take a long time to get any solution...
Problem Solved! :)
Spoke too soon - when I reassembled after cleaning bottom adc's the problem was back again in all its glory. |O
Now I find that it comes and goes as I apply pressure to the PCB around the area of the input circuitry so it looks like a dry joint or cracked trace - somewhere.....
... cracked trace - somewhere.....
Got my replacement unit. Just a quick question: the Single Seq button is translucent, like the Run/Stop and auto buttons, but it doesn't light up. Is it supposed to?this is crap, someone just bought latest MSO5202D model from Hantek and installed latest firmware from Hantek website. ... and of course the MSO is now bricked !!!I just did this to an MSO5102D. It's on it's way back to China. Not happy >:(
Got my replacement unit.
Just a quick question: the Single Seq button is translucent, like the Run/Stop and auto buttons, but it doesn't light up. Is it supposed to?
Got my replacement unit.this is crap, someone just bought latest MSO5202D model from Hantek and installed latest firmware from Hantek website. ... and of course the MSO is now bricked !!!I just did this to an MSO5102D. It's on it's way back to China. Not happy >:(
Got my replacement unit.
happy youJust a quick question: the Single Seq button is translucent, like the Run/Stop and auto buttons, but it doesn't light up. Is it supposed to?I'm thinking of a jury rigged hack to make it light up...
no, there is no LED for that button.
I'm thinking of a jury rigged hack to make it light up...
just wondering if there is any benefit to fitting the micro SD card or RJ45 port and transformer
(looks like a HTX1260NL?).
Watching the OS boot it seems to attempt to boot from SD before NAND so could this be an
easy way for trying newly compiled bits?
The LAN port driver seems to be installed in the OS, could this make life a little easier
for transferring files onto the scope or even act as an SSH connection?
(looks like a HTX1260NL?).
no idea, you will have to check pinout, i think it is H1102NL
Just got a Hantek DSO5072P... I've changed the bandwidth
Just got a Hantek DSO5072P... I've changed the bandwidth
You installed firmware from 5202P, right? Could You please give me a link for it?
there is no need to install 5202P firmware to get 5072P changed to 5202P (unless you need bootlogo)
there is no need to install 5202P firmware to get 5072P changed to 5202P (unless you need bootlogo)
Oh, thanks for allusion, I started reading this thread again from the beginning and at last got 2ns. :-)
BTW, after flashing 5102P firmware bootlogo still shows 5072, but doesn't matter.
Ich danke Ihnen tausendmal!
1500 replies and (nearlyhuhu, made it) 250000 views ... Dave, where is my DMM ? :-//
Perhaps there should be a prize for threads that crack numbers like that.
Email me your snail mail address!
Dave.
Well, I just tried it. Everything works fine, for me
its not for my dso5072p/dso5202p or I would have tried :)
That firmare is compatible with following models:
- Hantek DSO5072P, DSO5102P, DSO5202P
its not for my dso5072p/dso5202p or I would have tried :)
i don't know how is your DSO5xxxP but i think it will work, check what i wrote:That firmare is compatible with following models:
- Hantek DSO5072P, DSO5102P, DSO5202P
Lol how did I miss that the update went smoothly. currently running self calibration. we shall see how it works/its not for my dso5072p/dso5202p or I would have tried :)
i don't know how is your DSO5xxxP but i think it will work, check what i wrote:That firmare is compatible with following models:
- Hantek DSO5072P, DSO5102P, DSO5202P
how about running a custom script on clicking the "sys status" button, the user could edit it to do what they want.
Did you update anything to the logic analyser part except for the HELP button?
I only tried the DSO part so far, except I noticed while trying the HELP button that I still have spurious flashes of random data on all LA channels.
LA is the most broken part as far as I am concerned.
not all samples captured in LA memory can be zoomed to
LA memory seems to be only 4k deep (should be 512k?)
triggering in mixed mode leaves the LA data trailing the DSO data by one event (seems like it is only a misplaced refresh operation since if you force a display refresh by operating controls it shows the newest samples)
The support from Hantek has been horrible and unresponsive to the point that I have given up any hope they will fix the LA in the foreseeable future. Also beware of their support web site, they log your IP (that is OK i guess) and publish it in full for all posters (NOT OK). Pointed it out 5 months ago and they would look at blanking out parts of it to shield their customers... not a thing happens >:(
As a result I have moved on to a DS4014. First priority on my home lab todo list at the moment is checking out the BW settings on the I2C bus of the DS4014 (looking for confirmation that BW limits are set as in DS2000).
I wrote a story on entry-level oscilloscopes, technology and some comparison of a few popular models (including the Hantek) for my blog, and included a shout-out to the thread here for more Hantek details. Check it out if you're inclined: http://www.bigmessowires.com/2013/09/23/entry-level-oscilloscopes/ (http://www.bigmessowires.com/2013/09/23/entry-level-oscilloscopes/)
I've been lurking in this thread for a couple of days now - thanks for all the great information! I don't actually own a Hantek scope, but I'm considering getting one soon. Actually I was first looking at the Hantek MSO with the logic analyzer functions, before I read about the issues with it here. So I will probably stick with one of the DSO models.
I'm back with an irritating problem on my DSO-8060: I want to make screenshots (BMP, JPG or whatever) via USB, with the push of a button (in the PC app). If I want to document my work, it's annoying to keep plugging in a USB stick, going through the menus and options, wait, unplug USB stick, transfer to PC, save. And do it all over again for every screenshot, because if I screen capture 5-10 images one after another, and then transfer to PC, I don't remember what is what.
The Hantek software(v1.04) is crap.
I tried the USB tool from here: http://www.dreisiebner.at/dso-usb-tool/ (http://www.dreisiebner.at/dso-usb-tool/)
...
I also tried the modified dso-usb-tool that tinhead posted in this thread
...
Am I doing something wrong?
- for repetitive signals the "4x bandwidth vs. sampling rule" apply only to DSOs
with gaussian frequency response, but not with flat response; see Agilent 5988-8008EN
In case of these DSOs from this thread, they does have flat response, which is unique for that price class.
This is good from point of measurment accuracy from zero to near bandwidth limit
this is question of trust - do you trust manufacturer to be able to fix problems in acceptable time x? If so, buy MSO, if not buy DSO. The MSO itself is nothing else than DSO + additional PCB, so it can be still perfectly used as DSO until bugs fixed.
I don't like more things like these artifacts on LA, sometimes middle of measurment, sometimes when changi ng timebase, sometimes even when you stop acq, zoom in, move waveform and then boom - they appears on screen. That can ruin your work and be very frustrating:
I think I decided that even if the MSO features worked correctly, I'd rather have a real logic analyzer with complex triggering, a state listing, channel grouping and naming, etc. I have an old HP1631d now, which has pretty good logic analyzer functions, and I'd hate to lose some of the features it has. So I'm probably going to upgrade to a separate DSO and logic analyzer, instead of a single combo instrument.
I'm thinking about getting one of the newer Hantek -P models without the long memory, and I'm hoping to confirm a few things:Having read most of this thread recently I can probably help a bit here.
- Is there any known difference between the DSO5072P and DSO5102P, or will they be exactly the same once they are bandwidth hacked? Maybe the front-end is different, or the probes that are sold with them?No hardware differences, but the 70/100MHz ones come with 150?MHz probes. the 200 comes with 200MHz probes. Spend $50 on some Texas 250MHz probes and all is well though (or $20 on some cheap chinese 200MHz ones) - I wouldn't trust the frequency rating of the stock probes anyway.
- It seems like some -P models advertise 24K sample memory, but others say 40K. Will they all be 40K after the firmware hacking, or is it an actual hardware difference?Early firmware versions only offered 24Ksamples, later firmwares give you 40Ksamples. The update to give 24K models 40K samples can be found here: https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg271366/?topicseen#msg271366 (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg271366/?topicseen#msg271366)
- Do the new -P models require replacing any resistors in the front end after hacking? Or is that only for the -B and -BM models?Not as far as tinhead seems to know, I recall it being mentioned in an earlier post - and the first page thread specifically mentions that it's for SN under 15000, which excludes the P models.
Thanks Neggles! According to eBay listings, it looks like the 70 MHz DSO5072P actually comes with only 80 Mhz probes (the PP-90), although the official Hantek website doesn't specify either way. The PP-150 probes are also 100 MHz rated by Hantek, not 150, despite their name: http://www.hantek.com/en/ProductDetail_15_73.html (http://www.hantek.com/en/ProductDetail_15_73.html)
Not a big deal if you're planning on replacing the probes anyway, or already have some.
'Thanks Neggles! According to eBay listings, it looks like the 70 MHz DSO5072P actually comes with only 80 Mhz probes (the PP-90), although the official Hantek website doesn't specify either way. The PP-150 probes are also 100 MHz rated by Hantek, not 150, despite their name: http://www.hantek.com/en/ProductDetail_15_73.html (http://www.hantek.com/en/ProductDetail_15_73.html)
Not a big deal if you're planning on replacing the probes anyway, or already have some.
You're welcome :) Huh, I didn't manage to find a listing showing the probe bandwidth, but, like you said, given the cheapness of reasonably-good probes it's not a huge issue.
I've actually got a DSO5072P on its way from an AliExpress seller (here, if you're interested: http://bit.ly/1fDdk5c (http://bit.ly/1fDdk5c) ) and I've ordered a couple of Uni-T 200MHz-rated probes to go along with it from a local seller down here in 'straya. It should be here within a couple of days, if i'm lucky, so I'll gladly check out anything you'd like me to once I get it :)
oh, a thing I found out that you might like to know: if you're viewing a thread in the forum, and you search for something with the search box while on that thread page, it'll search just the thread. Trés useful.
Quick Q: does anyone happen to know the output voltage and current specifications of the 5000P series' internal PSU, & is there any spare space inside the case? (5000B info would be appreciated too as it's probably the same/similar)
for P models not, but for B/BMV/MSO models, see the first page, there are links to schematics. I would say best reference is hw1007 schematic (is the newest i've made).
also the B version may still have the spot for the logic analyzer inside. The P does not.. I might have tried to find a B version if I would have known that and had the extra money.
Is it possible to buy the LA board separately?
or build your own maybe?
Thanks for all that work.
Also you send a bug report to Hantek about duration trigger. This makes me wonder if there exists an 'official' bug list
Did you notice the 'Black Hole' of about 2.5 us near the center of the LA traces when at 800ns /div?
I just got my DSO5072P in the mail so if there's anything you'd like me to check out, BMOW, feel free to ask.
I just got my DSO5072P in the mail so if there's anything you'd like me to check out, BMOW, feel free to ask.
Lucky you! I don't think there's anything specific I need tested, but general impressions would be good. I just can't seem to decide between the DS5072P or the DS5062B (or something fancier like the Rigol DS1074z). The -72P has the advantage of being cheaper and not needing any kind of front end resistor tweaking, but the -62B has the advantage of long memory. I'm thinking that for debugging microcontroller stuff I might really benefit from the long memory, but not sure if it's really worth it.
I should probably just shut up and buy something already. :-)
Lucky you! I don't think there's anything specific I need tested, but general impressions would be good. I just can't seem to decide between the DS5072P or the DS5062B (or something fancier like the Rigol DS1074z). The -72P has the advantage of being cheaper and not needing any kind of front end resistor tweaking, but the -62B has the advantage of long memory. I'm thinking that for debugging microcontroller stuff I might really benefit from the long memory, but not sure if it's really worth it.
I should probably just shut up and buy something already. :-)
well not only that, but the B possibly has the LA spot as well, so you could turn it into a MSO as well
Did you notice the 'Black Hole' of about 2.5 us near the center of the LA traces when at 800ns /div?
hmm, no, i don't see it. Try to make a screenshot of that, not that your display is broken :\
Pic_45_1.gif at 2us/div shows a set of equally spaced pulses on traces D0-D7, D0 is also present on analog CH1.
Pic_45_2.gif at 800ns/div shows the same, but now a 'hole' appears near the center of the LA traces of about 2.5us, pulses on D7 and D0 are missing.
Pic_45_3.gif after a little Horizontal Shifting the pulse on D0 becomes visible 'out of the hole'. The 'hole' is at about 0.2 div right of center.
Pic_45_1.gif at 2us/div shows a set of equally spaced pulses on traces D0-D7, D0 is also present on analog CH1.
Pic_45_2.gif at 800ns/div shows the same, but now a 'hole' appears near the center of the LA traces of about 2.5us, pulses on D7 and D0 are missing.
Pic_45_3.gif after a little Horizontal Shifting the pulse on D0 becomes visible 'out of the hole'. The 'hole' is at about 0.2 div right of center.
:wtf: I wasn't even considering the MSO, but that's the kind of data-altering firmware bug that should make anyone think twice about buying Hantek. It's definitely got me worried. I can live with occasional lockups or other little firmware glitches, but not something like this.
It's not only that the pulse on D0 disappears, but the timing of all the following pulses is completely wrong! :o
On the other hand, the logic analyzer is definitely an afterthought (and we DO only have one example of this occurring) so I don't think we're likely to have such issues with the in-much-wider-use DSO section, but still...
On an unrelated note I used my Hantek to debug some bits of my oneTesla ( http://onetesla.com/ (http://onetesla.com/) ) musical DRSSTC earlier today and it worked swimmingly.
With the tool from Peter http://peter.dreisiebner.at/dso-usb-tool/ (http://peter.dreisiebner.at/dso-usb-tool/) to get virtual shell ?
What is the current firmware release for the DSO5102B? Mine is 2.06.3(130814.0). Hardware version is: 10070x555583e8.
Has Hantek now leaped to firmware version 3.0 or is that just for new models?
Paul
What is the current firmware release for the DSO5102B? Mine is 2.06.3(130814.0). Hardware version is: 10070x555583e8.
Has Hantek now leaped to firmware version 3.0 or is that just for new models?
Paul
you are on the latest FW for your model. Regards the 3.0 FW, afaik for now it is only for new models.
Even if a version 3.0 firmware is released for older DSO5102s like mine, my fear is that it would include some form of protection against the BW upgrade many have been using, and equally as bad...no way to flash firmware back to Level 2.0.
for the new B/BM/BMV models wit SN > 15000 there is no backup tool yet available.
However, the "nanddump" is now integrated, so you can do it manually, something like this could work:nanddump -o -b -f /mnt/udisk/dump/boot.bin /dev/mtd0
nanddump -o -b -f /mnt/udisk/dump/logo.bin /dev/mtd1
nanddump -o -b -f /mnt/udisk/dump/kernel.bin /dev/mtd2
nanddump -o -b -f /mnt/udisk/dump/root.bin /dev/mtd3
Of course you need first to insert falsh drive into usb port and run these command from the shell
With mine DSO, power switch should be pressed firmly, otherwise screen will just blink once and doesn't power on. May be it's common bug with this model, not sure.Thanks for help. Maybe you are right and most of power switch of these Hantek oscilloscopes are with poor quality. Anyway I decide to return the oscilloscope to seller and maybe I will spend more money for new Rigol 1074Z. This Voltcraft was bargain in the price but I think Rigol is better investment.
With mine DSO, power switch should be pressed firmly, otherwise screen will just blink once and doesn't power on. May be it's common bug with this model, not sure.
When I tried to power on the oscilloscope doesn't starts up at all.
because there is Guarantee sticker in the bottom of case.
After switching I can hear some type of switching relays inside of oscilloscope, It is possible some of they do not work properly.
And finally one stupid question. It is possible to be that firmware bug?
Both the front panel and system info say that model is: DSO5062B (Notice lack of M). Sounds like I was sent the wrong model.
HW version is: 10070x555583e8 - Which if I understand is an old HW revision based on this thread. What is not quite clear to me is if there were actually improvements/fixes with later HW revisions, or it does not matter in practice.
SW version: 2.06.3 (130306.0)
In general, but should I be expecting a unit with SN > 15000 at this point in time. Does new SoC fix any performance issues, or it is just EOL replacement part?
After switching I can hear some type of switching relays inside of oscilloscope, It is possible some of they do not work properly.
And finally one stupid question. It is possible to be that firmware bug?
ok,is any firmware update for my dso?
I'm new here reading through this tread since hours... completely confused meanwhile :scared:
Can anyone verify that this will work and if so what do I need (as far as I understand meanwhile the typical FPGAs for the e8/e9 hardwares won't work).
My problem is I bought a Voltcraft 1062D DSO with hw 1010x5555830f and still don't know if it is possible to hack this thing or not?
Today I unboxed my HanTek MSO5102D mixed oscilloscope, every thing looks and works fine except I hear an annoying high pitch whistle noise as soon as the screen shows probe reading.
This noise never stops and I think is due to capacitance discharging and charging or something similar.
@tihead
Sorry I can not open the Video link, is it possible to upload it on other website.
Thanks
If anybody want to sell mso pcb i will listen you deals or somebody knows where to buy it. If you interesting write me to PM
as mentioned above, check the first page of this thread, very first posting, you will find out that:
- backup with a backtup tool is not (yet) possible (which is not a big deal, you can save files manually)
- bandwidth hack is possible
- logo hack is not (yet) possible (but who cares about boot logo), unless you compile new frame buffer driver with new logo
as mentioned above, check the first page of this thread, very first posting, you will find out that:
- backup with a backtup tool is not (yet) possible (which is not a big deal, you can save files manually)
- bandwidth hack is possible
- logo hack is not (yet) possible (but who cares about boot logo), unless you compile new frame buffer driver with new logo
Thanks for this tip, i didn't start read on the first page because this would have been taken days to read the thread up to the end ;)
I read the very first postings as you suggested and found "For all others (not listed above) ... please PM me." what I've done but didn't get an answer but this isn't a problem I simply try it here again:
I have a DSO1062D from Voltcraft with hw 1010x5555830f, serial is > 15000 and sw 3.30.0. I learned that 1062D doesn't mean 1062D... so at least the hw confuses me a little bit because most solutions that I found seems to be for 1005 and 1007.
Backup manually means I need a console on the device... you meant "which is not a big deal"... what would be the easiest way for this? Where the uart has to be connected to is only described for hw1005 and hw1007 but not for hw1010 or is there an even easier way for doing this?
By the way any idea where I can get a logic analyzer board to make a DSO5xx out of the scope, will this work and what will it cost?
Thanks,
Michael
SN > 15000
soft version: 3.30.0(130709.0)
fpga version:0x5555830f
Creating 4 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "Bootloader"
0x000000100000-0x000000300000 : "LOGO"
0x000000300000-0x000000700000 : "Kernel"
0x000000700000-0x000008000000 : "ROOTFS"
BusyBox v1.20.2 (2013-03-15 09:24:06 CST) multi-call binary.The logic for nanddump is implemented in the miscutils/nandwrite.c file. I used corresponding git tag (https://github.com/vmpn/busybox/tree/1_20_2 (https://github.com/vmpn/busybox/tree/1_20_2)) as baseline when analyzing the code. The following commits in the busybox repo fixes some of the issues:
updating...here's attached log console.the mtd size of "rootfs"is 121Mb,then why the nunddump is dumping 124Mb? :-[
{Path}/busybox nanddump ....
Please, can someone to feedback us about this test?
Set a waveform to screen (triangle, sinusoidal).
Move the waveform to up or down so to cut the edge of the screen.
Now invert the waveform.
What is appearing? Is it normal or the bottom of waveform is also cutting?
i've noticed that with busybox from vmpn the dump files are like this
boot.bin-1.03mb
logo.bin-2.06mb
kernel.bin-4.12mb
root.bin-124mb
and the dumped files with original busybox
boot.bin-1mb
logo.bin-2mb
kernel.bin-4mb
root.bin-dumping forever
yes,i'm using -o
Still reading through this thread. Huge amount of great info here.
I was wondering what the current hardware revision is for a Hantek DSO5102BM model? Is it 10070x555583e9? Couldn't find the info on the Hantek site and still waiting for a their response to my email.
Is it possible to use the DSO-BW-Changer for the DSO 5102P to change the bandwith to 200 MHz?
@lemon
i think this is the wrong section for your problem, in the video is a owon brand device that has nothing to do with hantek/teckway/voltraft and so on ...
Please, can someone to feedback us about this test?
Set a waveform to screen (triangle, sinusoidal).
Move the waveform to up or down so to cut the edge of the screen.
Now invert the waveform.
What is appearing? Is it normal or the bottom of waveform is also cutting?
there are not such issues on Tekway/Hantek, nor these others nown from Owon (with inverted and moved to top signal).
This must be firmware bug in Owon firmware, you should tell that Owon (or rf-loop, he is collecting bugs as well).
You are right, the threat is too long.
I tried out the BW Changer. The timebase can set to 2ns but the input signal will be filtered. I measured the -3 dB point with a signal generator at 80 MHz.
So I must check if a SW downgrade to 3.3 is possible. And the how to do and the necesary files.
Can you explain this for me?
part of the timebase.
I have used my Spectrum Analyzer with Tracking Generator. Now I tried it with an "real" signal generator. The same result.
I cannot belive the limited BW comes from dirty PCB.
Both channels shows the exact same damping and the filter curve is "to linear".
Both channels shows the exact same damping and the filter curve is "to linear".
Thanks for your support!
I cleaned the PCB with Flux Off, no changes.
So I try out the software solution. For this I must study which tools I need, and do the modifications.
This thread is way too long ! Is anybody running a forum with the topics a bit more searchable ?!
I'm looking at buying one of the hantek scopes but having trouble working out the tradeoffs. I don't think there's any saving in buying the DSO1062, and I'm not convinced 1GS/s is enough for 200Mhz mode, so I'll probably stick with 100MHz bandwidth. I've got faster analog scopes anyway.
But there's the choice of B, BM, P and MSO5120D. :-\
B is a bit cheaper
BM has 2M memory (but does that make it really slow update ?)
MSO is useful but only 1M memory.
P is really cheap but only 40K memory (or maybe 24k?)
Of course, I'd really like the best of everything ! It seems the MSO option isn't that great and can be added fairly easily. So maybe the 2M is the best choice ?
Are there any options now with ethernet already fitted ? There seem to be some add-in boards, or I can put a wifi adapter in the USB.
The RMS calculations seem to be wrong. 880mV peak to peak should give 311mV RMS but my hacked voltcraft doesn't seem to agree.
...
I've also noticed that at 10MHz the levels are measured slightly lower than under 10Mhz.
Is this the front end problem that you mentioned a while ago Tinhead?
I would also like to know what is the best to buy.it depends what you need. Due the fact that some distirbutors stil might have hw1007 models, i would be careful buying. It does make more sense to buy the latest hardware and not the hw1007. So watch the SN.
From this site the BM is cheaper that the B model... http://www.rigoloszilloskop.de/search/?DirID=&q=dso5062 (http://www.rigoloszilloskop.de/search/?DirID=&q=dso5062) I'm trying to stay close to the 300€ mark...
I would also like to know what is the best to buy.it depends what you need. Due the fact that some distirbutors stil might have hw1007 models, i would be careful buying. It does make more sense to buy the latest hardware and not the hw1007. So watch the SN.
Lol. I'm from Portugal with zero knowledge of German, i've used google translator and the translations seams normal (for google...). I'm avoiding the store now...From this site the BM is cheaper that the B model... http://www.rigoloszilloskop.de/search/?DirID=&q=dso5062 (http://www.rigoloszilloskop.de/search/?DirID=&q=dso5062) I'm trying to stay close to the 300€ mark...
yeah, look on that crap webite, "Wir sprechen Deutsch", yeah my dog as well.
When you in Germany, buy from Conrad/Voelkner or Pinsonne.Thanks for the tips! I'm trying to buy inside the EU to avoid the border/custom taxes...
Hi;
I recently got my brand new MSO5202D V3.2.35. I download latest firmware from www.hantek.com (http://www.hantek.com) website and put in to usb stick. Then I upgrade the scope. Menu appears please restart the scope. When I restart the oscilloscope Hantek logo comes then blue screen comes and restarts forewer. I thing that it was wrong version (SW: V2).
Now I have dst1kb_3.2.35_15202d_fact130826.0.up file but i hope it is not too late. Please help me.....
Hi all,
I got my 1st scope, a DSO5062BM, 15000 version, because I liked what I read here and because of the great work of Tinhead. Anyway, its menus are all in Chinese and I cant read it. Does anyone know how to switch the language? Thanks.
The "Self Calibration" function does fail at "self calibration step (13/34)" with message "Self calibration failed, error x502".
Can somebody tell me the meaning of "error x502" (what function of the MSO does not work)?
- I'm a bit puzzled by the Wave and Save Wave submenus under SAVE/RECALL: setting Media to USB or Flash, Save and Recall work as expected, but Recall fails when Media is set to SD even though Save succeeds according to the message. The SD card status is "built in"; is the "EEPROM licensing hack" still needed if I want to use the SD card for saving waveforms?i don't have handheld anymore, so can't check that ...
- The Save Wave button always saves to USB, regardless of the Media settings; is this a bug or normal?is there a way to select SD as destination? if not, then it is not a bug, if yes - well, then it is bug.
- The UART header is marked differently on two pictures (RX and TX are swapped,one of them :)
- Beside the UART header, there is a four hole connector marked @WLAN. What module can be used there?yeah, i remember that header. On the bottom side you can see missing IC near that header, which is in principle USB mux like on BM/BMV model (check the hw1007 benchtop scheematic). I assume the intention was to enable second USB Host (and a usb wlan card connected to that header), but there is not option in firmware yet to use that from the menu (sure, you can add a script doing this or oatch firmware to enable it instead of beeper ...)
The "Self Calibration" function does fail at "self calibration step (13/34)" with message "Self calibration failed, error x502".
- The Save Wave button always saves to USB, regardless of the Media settings; is this a bug or normal?is there a way to select SD as destination? if not, then it is not a bug, if yes - well, then it is bug.
I am interested in MSO5074F oscilloscopes. Does it with the USB interface?
So I picked up a DSO5072P over the last summer, put it through it's paces for a few days, and then did the 200MHz upgrade... Now the probe test output is reading as a 0.188V@1kHz square wave, and the self-calibration fails at step 2 with the error code 0xa00... Anything I can do to fix this, or is it hosed?
Hello!yes
I did revice my Hantek DSO5102P yesterday, it's a 100mhz oscilloscope
It's running fw: 3.40
Is there any 200mhz hack for it?
I did read first post in this thread and did make backup of mtd blocks.
Now im connect to uart pins directly beside usb port on the backside.
i got console now, and could see file dst 1102b i did raname it to dst1202b
is that all? =/
Hi again, did try to make own disp file with image2lcd with info from readme file included, but after reboot it's still same as original
Did place disp file in /dso/app/
Hi,
I'm new here and have a Hantek DSO1102BV (hw version: 0x555583e8, SN: DSO0501xxx, PCB marking: DSO1000H v.1.00.1).
I haven't changed anything yet, except for a fw upgrade from 2.01.1 (120701) to 2.01.1 (130129).
After having read through the forum, I have several questions:
- I'm a bit puzzled by the Wave and Save Wave submenus under SAVE/RECALL: setting Media to USB or Flash, Save and Recall work as expected, but Recall fails when Media is set to SD even though Save succeeds according to the message. The SD card status is "built in"; is the "EEPROM licensing hack" still needed if I want to use the SD card for saving waveforms?
- The Save Wave button always saves to USB, regardless of the Media settings; is this a bug or normal?
- The UART header is marked differently on two pictures (RX and TX are swapped,
https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/?action=dlattach;attach=50483 (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/?action=dlattach;attach=50483) vs.
https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/?action=dlattach;attach=19887 (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/?action=dlattach;attach=19887) ). Ok, one is the pinout of the DSO itself, and the other of the module to be connected, but which is which?
- Beside the UART header, there is a four hole connector marked @WLAN. What module can be used there?
Thanks for all the useful info already here, and any answers to come, cheers :)
Hello! I found Hantek has a update firmware can Recall when Media is set to SD.
anyone know, 5072P can be cracked?
hello, anyone have a 2Gsa/s sample rate, 60Mhz DSO7000 series?this series looks just launch.
help, replace the file on your DST1102B dso.exe (I do not remember how) now boot up logo on UART is not available (nor any greeting Putty)normally even if you delete every file, the DSO will still load bootloader and later kernel, so you should see messages from both of them. I guess you attached UART adapter, booted DSO then (but DSO stopped in bootloader) and then you deleted something in bootloader (probably purged it). Now what you can do is to restore the bootloader - and before i tell you how i need to know what hw/fw revision was installed (or at least what is your SN, < or > than 15000) and maybe how old is your DSO.
What should I do!
I would like to send him anywhere and not solve the problem by hand, using your valuable suggestions.
It's new, it is about 1 week. I have a week to NAND programmer available.
...model ADS1102CAL +.
Although the menu interface completely ATTEN.
Well, I do what you need pictures, and you help me make a repair program today.
tinhead
www.hantek.com/Product/DSO5000Series/DSO5102B_Firmware.zip (http://www.hantek.com/Product/DSO5000Series/DSO5102B_Firmware.zip)
Newly firmware 5000B series, contain dso5kb_func_dso5102b20140111.up (3 325 038 byte) 01.14.2014
"error 0xf7 illegal update file detected"
gpg.exe with "0571tekway" - decryption failed:bad key :o
What could it mean?
upd.
password: dso5000b :palm:
tinhead
www.hantek.com/Product/DSO5000Series/DSO5102B_Firmware.zip (http://www.hantek.com/Product/DSO5000Series/DSO5102B_Firmware.zip)
Newly firmware 5000B series, contain dso5kb_func_dso5102b20140111.up (3 325 038 byte) 01.14.2014
"error 0xf7 illegal update file detected"
gpg.exe with "0571tekway" - decryption failed:bad key :o
What could it mean?
upd.
password: dso5000b :palm:
maybe is for the latest hardware
the dso5000bm and p series is updated too
maybe tinhead can tell us what is all about...
means so worked initially everything, then on the second day at work with scanned picture crumbled. I decided to flash it, no firmware is not approached, I found that on an embedded operating system in the device linux. In the search for the desired firmware, I replaced the file dso.exe found in this thread, after replacing the oscilloscope to load the logo and all the buttons are lit by UART access is no more, using JTAG not figured out how to flash it!
Some questions:
1) what is backup method for these > 15000 units? (Not listed for MSO and ser no > 15000)
2) can I upgrade bandwidth as usual (rename dst file in root, or use DSO_BW_Changer, etc?)
3) I guess this doesn't change the LA part (always 500mS/s?)
4) How to enable LAN? There is a transformer position on both the LA sub-board and the main board - which to use? Any software changes?
There is now a 4 pin header next to the LAN jack for UART access (documented on your page 125). Also a 10 pin now on other side of LAN jack - I havent seen a picture of that in the blog so far...
UART converter - I use an (very!) old mobile phone Serial cable, one with a "box" halfway down containing an RS232 chip - cut off the phone end and connect to the scope (look up chip used in the box to discover connections...).
I'll see if I can take some decent pictures - anything else you want to know about this newer version?
...thanks tinhead - lots to do there - I'll try to keep you updated...
I have an Altera Blaster, so may be able to get FPGA image? Is it main board, LA or both you want? Also will attempt some NAND dumps - command via terminal, output to USB I guess...
It seems that the Hantek website has been down. I just got a DSO5102B. Where can I get the latest firmware update?
right, they do have holidays until i think Feb 10th or something, so no IT admin there to reboot IIS :-BROKEIt is 2.06.3 (130329.0)
what version do you have currently installed?
Quoteright, they do have holidays until i think Feb 10th or something, so no IT admin there to reboot IIS :-BROKEIt is 2.06.3 (130329.0)
what version do you have currently installed?
Dear tinhead, could you throw me a NAND dump from DSO5102B. I'll try to pour through the programmer. May start! ARM S3C2416 Processor
EDIT: in case oyu really have 2.06.3, here download link. There are two fw version, one from April 2013 and one from September. Try first the one from April, then if this was working the one from September. Both are original files, for DSO5102B, so they must work.
QuoteEDIT: in case oyu really have 2.06.3, here download link. There are two fw version, one from April 2013 and one from September. Try first the one from April, then if this was working the one from September. Both are original files, for DSO5102B, so they must work.
Thank you VERY much!
It now shows 2.06.3(130814.0) The September one worked!
ok, then try to update to the patched version (the one above which gives you 0x7F error). But rename the update file to
dst1kb_2.06.3_15102b_fact(130814.1).up first ^^
If there is any information you want from this 'scope, let me know.
Thanks again
On the Hantek web site, there are firmware files e.g. dso5kb_func_dso5062b20140111, which I expect are newer than what is in my DSO considering they are dated January 11th 2014.
and that firmware on the website is ONLY for models with newer hardware, this is why you getting update error. For your DSO, the latest is the one published here in thread.
and that firmware on the website is ONLY for models with newer hardware, this is why you getting update error. For your DSO, the latest is the one published here in thread.
VGA has a board, do you have this board for MSO5202D?
VGA has a board, do you have this board for MSO5202D?
Anyone tried to recompile or migrate from open source Welec W2000A
What ever happened to TinHead?
I used to enjoy all the information that he would post here.
and that firmware on the website is ONLY for models with newer hardware, this is why you getting update error. For your DSO, the latest is the one published here in thread.
Hello Tinhead/Experts
Can the experts on this forum clarify weather Hantek model DSO1062BV can be hacked to 200Mhz.Is there anything else like memory that can be hacked in this model.
I have this model on hand but wanted all you experts advice on how to go about it.I do not want a new scope bricked, as this is my sole scope.
Please help by reverting back
Vinay
Hi friends.
In my new DSO5072P for 200MHz bandwidth had to remove 2 capacitors 47pF (see photo). Hope this helps someone.
What ever happened to TinHead?
I used to enjoy all the information that he would post here.
Anyone tried to recompile or migrate from open source Welec W2000A
From what I have read, the Welec scope firmware was terrible in design and execution, it went open source after the company went bankrupt, and the community tried to fix the many bugs. It probably has no value.
Hi friends.
In my new DSO5072P for 200MHz bandwidth had to remove 2 capacitors 47pF (see photo). Hope this helps someone.
(https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/?action=dlattach;attach=86225;image)
btw, something completty offtopic - did anyone recognized that Hantek have now new AWGs?
Just a note that Hantek issued a firmware update for at least the DSO1000S series handheld scopes (what I have. Maybe for other series, too). Version 2.01.1(140212.0)
Does the Tekway do DPO/intensity gradning?
Despite being rather old 2009's design
this scope is now manufactured by MCP Shanghai.
I tried backing up the firmware to USB stick first but it doesn't work, says there are no new firmware files on the stick.
Please don't shoot me if any of this has been discussed somewhere earlier in these 150 pages...
Can I hack this Voltcraft ? I found some hints saying there were problems with it (new hardware ?).
I have ordered an MSO5074FG oscilloscope (with integrated logic analyzer and function generator)
the major difference between Welec and Tekway designs is:Welec implement softcore CPU with UI writted in pure C. So, it possible to move Welec UI to ARM with new HAL layer. At the first step original Tekway FPGA image used. At linux src drivers s3c2440-spi.c contain FPGA load routines.
- Welec - all in FPGA
vs.
- Tekway DPO in FPGA, UI in ARM, with mapped (via CPLD) memory
At the first step original Tekway FPGA image used. At linux src drivers s3c2440-spi.c contain FPGA load routines.
Also s3c2440-fpga_noirq_1000b.c contain full info about interaction from FPGA to linux. But comments in Chinese and algo is not clear for me.
I tried backing up the firmware to USB stick first but it doesn't work, says there are no new firmware files on the stick.
Please don't shoot me if any of this has been discussed somewhere earlier in these 150 pages...
Can I hack this Voltcraft ? I found some hints saying there were problems with it (new hardware ?).
well, i will shoot you (actually i should shoot or fuck everybody who start reading book from page 150 and not the VERY FIRST !!!).
Really, just check the first page:
bold "- before you hack made a backup", aha, you have version with SN > 15000, so what there? "S/N > 15000 ... PM me", where i can already tell you, i will not answer any PMs anymore. Why? well, use search, and you will find that backup can be done with (already integrated in models with SN > 15000) nanddump tool and was ALWAYS possible with e.g. tar.
now let's continue, first page, bold "- the bandwidth hack" - then, read this shit " As far i fucking know, all DSO/MSO/Handhelds since 2009 can be hacked". So no idea what you mean with "I found some hints saying there were problems with it", i don't know any. I can even tell you that even not yet released models can be hacked.
So, that was not exactly very clear.
"Nanddump tool" and "tar" doesn't ring a bell with newbies....sorry, I have no clue what you mean.
I have ordered an MSO5074FG oscilloscope (with integrated logic analyzer and function generator)
thats crazy, one can clearly see here 2GSa/s,
(https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/?action=dlattach;attach=87948;image)
where here another actual unit shows clearly 1GSa/s :\
http://www.hantek.org/asken/iaskdetail.aspx?id=2014030822583972 (http://www.hantek.org/asken/iaskdetail.aspx?id=2014030822583972)
Yes, already briefly discussed on the forum. No one has one. Maybe they aren't on the market, just announced.
I checked all MSO5074F data on Hantek website, it is 1GSa/s. I think the 2GSa/s is an printing error.
However i am undecided which model to get. I will get one of the lower bandwidth models and hack it to 200MHz, but which one?up to now all can be hacked, however some need hardware modifications.
The P model is the cheapest but has the least memory.right, there are even cheaper i think, DSO4102B which is 500MS/s but int he new enclosure. Now the question is,
The BMV andwell yeah, 2M are alays better than 1M
MSO seem to be around the same price on aliexpress. I am undecided between these.which one, MSO5074F(G) or MSO5062D? The MSO5xxxD they do have LA on separate PCB,
From what i have read the MSO's LA seems to have problems. Is this any closer to being fixed?as said above
I like the idea of having a LA built into the scope, but i do have cheap ebay USB logic analyser.the question is what analyzer you have, when one of these salease/uesbee then of course is
The BMV has bigger memory and a video help (although im not sure about how useful this is).memory as said above, it is always good to have "more". Video, hmm, for sure one can use
With a price difference of about £6 between the BM, BMV and the MSO in that order, i'm a little confused as to which one to get. :-// :-//
The P model is the cheapest but has the least memory.
Is anyone interested in a new open source Hantek DSO/MSO made for Mac OS X?
Is anyone interested in a new open source Hantek DSO/MSO made for Mac OS X?
Although the existing DSO USB tool fulfills my basic needs I sure would love to see a nicer
OS X version!
I recently bought a used Hantek DSO5102B from ebay.
I'm not sure what hardware version this model is.
On System Information it says hw version 0x555583e8.
I was getting 0xfe and 0xf7 errors. The only firmware that worked was tinhead's (thanks man) dst1kb_2.06.3__130814.1_.up when I renamed it to dst1kb_2.06.3_15102b_fact(130814.1).up.
Any idea on what hardware version I got? It's probably an old one, I opened up the scope and wanted to see the version number on the pcb but I couldn't find any (or I missed it).
The pcb of the power supply had a 1.02 version number.
By the way, I saw a picture of the pcb somewhere and it had heatsinks on the ADCs and on the Altera Cyclone 3 FPGA chip.
In my case, there are heatsinks on the ADCs, but not on the FPGA chip.
Should I put a heatsink there, or it doesn't get hot enough?
Also, no fan is installed.
I've got a Hantek DSO5102B here, firmware is the old 2.06.3 120112.1 and ...
/e: Issue probably resolved. I found a 6 pin J801 between the two FPC connectors J900 and J702.
you have hw0 !!!, from a SN i would say produced in Oct 2010 or so. This is the very first version, wondering who sold you that :rant:I see, I was suspecting a hw0 version too. It was a used unit, I wasn't expecting the latest version, but I wasn't expecting the oldest version either.
right, there is no firmware support for that hardware anymore. For sure firmwares 2.6.x will run on it (be happy you didn't got hw1005 which is actually younger as yours but with hardware bugs), but on the other side you bought it 8 months after Hantek/Tekway stopped production of any S3C2440 based DSOs (and your is using that SoC).If I ever need a different firmware version, (I doubt it, your firmware 130814.1 works great, but I wanted to ask anyway) should I assume that Tekway firmwares (for the DST1102B) should work on my Hantek DSO5102B? Tekway's firmware filename is "dst1kb_2.06.3_01102b_fe(120423.0).up".
I received a few days ago my new scope: a hantek dso1122s.
Yesterday decided to try the bandwidth hack, with my surprise, I found that hantek had 'already hacked my scope' ( the scope already had the file /dst1202b in it and the 2ns timebase is already available ).
Sadly the only thing I can do is change the 'name' of the scope ( i think I should have to change logotype anf logotype.dis )... but I'm too lazy for that.
In conclusion I'm not happy for what hantek did to my scope... ;-)
P.P.S. my unit was advertised as having 2M memory, but it has only 1Mthat sucks, it should be 2M. It might be an licensing thing (not a problem to "fix" it, heh), but picture of the PCB would tell us more (if there is 2M memory then maybe they forgot to enable it)
It was a used unit, I wasn't expecting the latest version,
I got it for about half the price compared to how much a new unit costs (at least for my area), so I thought to give it a try.
Do you believe the version I got (hw0) is vastly inferior (regarding signal accuracy / performance etc.) to the latest version (hw1007) Hantek DSO5102B?
However this looks to me like an older firmware version (so probably not worth it). I assume the number "120423" is a date code and means April 23rd 2012, is that correct?yes
If I ever need a different firmware version, (I doubt it, your firmware 130814.1 works great, but I wanted to ask anyway) should I assume that Tekway firmwares (for the DST1102B) should work on my Hantek DSO5102B? Tekway's firmware filename is "dst1kb_2.06.3_01102b_fe(120423.0).up".you can use any "B" model 2.06.3 firmware, you can NOT use any B model 3.x or any other version/revision (MSO, BM, BMV, P, etc).
Here a few, not so good, photos of one side of the hantek dso1122s board:
P.S. by the way I'm looking for the sd socket, have you got a suitable part number ( or farnel/mouser code )
Here a few, not so good, photos of one side of the hantek dso1122s board:
btw, something completty offtopic - did anyone recognized that Hantek have now new AWGs? e.g. HDG2002B, this is the cheapest model, but for me it looks like the DAC is running anyway same speed on all models, so maybe time to hack it ?:P
I don't have spare money to give a try, so hope someone will soon buy one and play a bit with them >:D
btw, something completty offtopic - did anyone recognized that Hantek have now new AWGs? e.g. HDG2002B, this is the cheapest model, but for me it looks like the DAC is running anyway same speed on all models, so maybe time to hack it ?:P
I don't have spare money to give a try, so hope someone will soon buy one and play a bit with them >:D
I received mine last week. If someone is intereded I could post some photos of the board.
The software hack for unlocking frequencies is very simple. You just have to change the model name in the system.inf (now in /etc) and reboot...
So I just replaced HDG2002B with HDG2102B to get 100Mhz instead of 5Mhz.
At the moment I don't know if there is also some hardware mod to do (a 100Mhz sine of 2V amp is shown with 300mV amp on my MSO5062D with PP-200 Hantek probe, but I didn't mod the frontend yet)
Still have some some work in progress on my MSO ;-)
holy shit! please make a new topic on that, this is really awesome!size]
Sounds sad but it would even match the scope i just ordered.. >:D
I would love to see a pic of them together on the bench. That new case looks good. Hantek seem to have the best looking GUI's of 'low cost' test equipment by far.... and they are hackable. Love it.Sounds sad but it would even match the scope i just ordered.. >:D
I know what you are talking about...I bought it to match my MSO5062D ;)
I'm interested in the MSO5074FG ... mainly for budget reasons. ($700 max )Unfortunately, I have the MSO5074FG and the bandwidth hack is not as simple. Yes, the software hack works as is for other Hantek DSO's but there are hardware limitations...
I have read page 1, and now page 151 ( hence the edit ).
So, I can change a file name in root and get the 200MHz bandwidth ( after doing a backup which IS available in the software on SN 15000 upwards ) ???
Near ADCs (that two ICs on top and two on bottom, each of them with small heatsink) on top and bottom there are on each side two ICs, on one of the pictures i think i can read NXP and HEF4053. If that's the case, one have to replace them by e.g TI CD74HC4053 to get more bandwidth, these NXP ICs they only good to 70MHz.Most likely, the bandwidth hack for this model may require a faster multiplexer with matching pin configuration and possibly removal of input capacitors on the frontend (I haven't looked at that yet).
From your pictures i can tell you alrady that the acually used the new "B" model platform, added two extra channels, added necessary logic for triggering, repalced the two channel-mux relais with 4pcs of i think HEF4053 (which is for 70MHz bw ok), added an small DDS PCB and that's all. Where the LA is connected, no idea (as said above, can't see from the pictures).
So for sure it will not do 2GS/s but 1x1GS/s, 2x500MS/s and 3/4 x 250MS/s, so like Rigol DS1000Z. Why they not used the same ADC as Rigol is using, no idea, from price point of view should be same. The good think is, it looks like they changed the way the FPGA is clocking, they added two mif files for the PLL, they can be externally loaded, so it looks for me that they trid to improve the ADC clocking, which is good think. Anyway, we wil see (well, you) how that baby performs.
I downloaded the manual prior to finalizing a purchase decision and there is no obvious mention of a trigger output that I could use to trigger my USB logic analyzer. Does anyone have info on that please ????The scope does not have the ability to output a trigger signal AFAIK.
I know that this may be off topic, but I'm looking for a hackable MSO/DSO with Logic Analyzer that has good memory depth and that can trigger on SPI, I2C etc, and either, have a trigger output to trigger my USB logic analyzer ( which does have protocol analysis), or, output signals to a PC so that software protocol decoding can be done there. I know the RIGOL DSO will trigger on I2C and SPI, but won't decode. Given the level of activity and knowledge on the Hantek scopes I assumed that someone must have the same desires as me.The MSO5074FG does not have logic decoding functionality or protocol based triggering. The logic analyzer is very basic, but I am looking into outputing recorded data to a PC based decoding tool. The ability to do logic decoding is possible in the future , but right now, the logic analyzer is bare-bones.
Also, this scope is now $464 plus $80 shipping to USA... approx $80 cheaper than amazon, or USA dealers.Got mine 15% off, $505.95 USD shipped.
The latest firmware on the Hantek site contains dso5kb_func_dso5102b20140111.up. Can you more knowledgeable people tell me if this is the same as what i have, or is it an update from what I have installed?? (see picture in my last post). From the numbers it looks like an update but will it be suitable for my revision 1010 machine??. I Think I read somewhere further back, that someone bricked there scope with a update that was unsuitable. Last thing i want to do is screw up my scope!! :-// :-//Based on the screenshot you uploaded in your previous message, your firmware version is 3.30.0(130928.0)
btw, something completty offtopic - did anyone recognized that Hantek have now new AWGs? e.g. HDG2002B, this is the cheapest model, but for me it looks like the DAC is running anyway same speed on all models, so maybe time to hack it ?:P
I don't have spare money to give a try, so hope someone will soon buy one and play a bit with them >:D
I received mine last week. If someone is intereded I could post some photos of the board.
The software hack for unlocking frequencies is very simple. You just have to change the model name in the system.inf (now in /etc) and reboot...
So I just replaced HDG2002B with HDG2102B to get 100Mhz instead of 5Mhz.
At the moment I don't know if there is also some hardware mod to do (a 100Mhz sine of 2V amp is shown with 300mV amp on my MSO5062D with PP-200 Hantek probe, but I didn't mod the frontend yet)
Still have some some work in progress on my MSO ;-)
holy shit! please make a new topic on that, this is really awesome!size]
The latest firmware on the Hantek site contains dso5kb_func_dso5102b20140111.up. Can you more knowledgeable people tell me if this is the same as what i have, or is it an update from what I have installed?? (see picture in my last post). From the numbers it looks like an update but will it be suitable for my revision 1010 machine??. I Think I read somewhere further back, that someone bricked there scope with a update that was unsuitable. Last thing i want to do is screw up my scope!! :-// :-//
Hi Tinhead,
at first thank you very very much for all your effort and time you invest in this project.
Have the voltcraft 1062D 1010hw and renaming the bandwidth file with Peters DSO Tool was no problem :-+. Easy to understand and on the first page :).
But I have 2 questions and it would be nice if you could answer it.
At page 133 the is a picture of the firmware you made with sample rate indicator. But i couldn't find a version for the 1062D hw1010 (fw 3.30.0 140111.0 ).
I didn't take the "P" version (of course) since it'S not a "P" ;). Did you make a version for my model? If not, it'S ok too ;).
Second question is about the digital filter for the corner frequency. I tried to make a "tst" file and upload it with the DSO Tool, but the scope hangs and the file is not uploaded.
(But can simple restart the scope.)
Is there a way to create the file and the "[filter] ... " content with the DSO Tool shell (commands)?
I don't need to see 400 MHz ;), but 250-300 would be nice (the amplitude dosn't matter).
I would prefer doing this mod with the DSO Tool and not hacking into the UART chip.
Quick Edit: Just got the file to the scope :). Found your post in the mikrocontroller.net tread with the cp command to copy from USB Stick.
But there is -after reboot of course- no message which says that the tst file is used? This would be the question left.
Thank you very much and nice greetings, Thomas :D :D
Kevin Liu
:-+ :D
bootloader -
https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg75015/#msg75015 (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg75015/#msg75015)
i.e.
www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/?action=dlattach;attach=4153 (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/?action=dlattach;attach=4153)
supervivi.bin
I still have a problem that is I also need a works firmware.I don't have the fullflash for programmator, but if you successfully recovered bootloader, I will upload full factory backup firmware today evening.
Kevin Liu
http://rghost.ru/55157657 (http://rghost.ru/55157657)
Password for archive: 0571tekway
Archive made 7zip open archiver
http://sourceforge.net/projects/sevenzip/files/7-Zip/9.22/ (http://sourceforge.net/projects/sevenzip/files/7-Zip/9.22/)
Actually, My DSO only response at one supervivi-128M that download from FriendARM but it still can not restore fw_backup.bin back.What yours DSO output to terminal?
I try several version supervivi just this one is USB:OK but still can not work.
Does any one know why?
MSO5074F:
Soft Version 3.2.35 (140219.0)
Hard Version 10020x54028205
Serial No T1G/654 000 173.
* Horizontal offset only goes up to 2.3mS, regardless of your timebase, so on long timebases it's effectively zero.
MSO5074F:
Soft Version 3.2.35 (140219.0)
Hard Version 10020x54028205
* Horizontal offset only goes up to 2.3mS, regardless of your timebase, so on long timebases it's effectively zero.
Can this offset be solved by self calibration?
Send them every day an email, with bug report and question if and if not when they will be ready :) that might help, really.
The menu in the device reports the following:
MSO5074F:
Soft Version 3.2.35 (140219.0)
Hard Version 10020x54028205
Serial No T1G/654 000 173.
* Included PC software - unbelievably bad, looks like Tektronix Wavestar (which was also hideous) but seems unable to reload any waveform files you may have saved. I've tried DSO-USB Tool and it works fine, with the exception of only showing 2 channels instead of 4.
what about this one
http://www.aliexpress.com/item/H100-Hantek-MSO7084BLG-4-Channel-Oscilloscope-8-Channel-Logic-Analyzer-25MHz-Arb-Waveform-Generator-2Gsa-s/1857305228.html (http://www.aliexpress.com/item/H100-Hantek-MSO7084BLG-4-Channel-Oscilloscope-8-Channel-Logic-Analyzer-25MHz-Arb-Waveform-Generator-2Gsa-s/1857305228.html)
the MSO7084BLG
what is that? how is it that much different than the MSO5074FG other than the small mhz difference and the older style LA headers
Hello, I just bought a Voltcraft DSO-1062D and I seem to be having some issues with it.
I adjusted the probe compensation according to the manual.
When I connect a probe to the scope's reference 5V@1KHz it looks alright,
unless I set the probe to 1X and set the V/Div to 200mV/Div or lower.
there is nothing wrong with DSO but with your understanding of what DSO can measure. There is volt/DIV setting, DSO have 10DIV max (8.4 DIV visible). In 500mV/DIV that means you have full scale 5Vpp, and when that signal is set in the middle like on you pictures (which is typical for DC coupled signal here), then you already over the scale. With 200mV/DIV you already 500% of the scale, and i even think that you simply switched x10 to x10, without changing then scale on DSO, so you in principle measuring 5Vpp signal with setting 20mV/DIV (x5 Div from screen middle to max scale that 100mV but you applied 5V .. so the signal have to bee complettly crap).In both the pictures the probe as well as the DSO are set to X1 - so it is really 200mV/DIV (therefore 100mV offset).
I inadvertently flashed the wrong BIOS to my DSO5062. I loaded the MSO BIOS by error (dst1kb_2.7.1_15202d_fact130826.0.up).
...
I am honestly confused by all the information I found here about doing a restore, so I am asking (politely) for help in restoring the unit - using the best method - so I do not make things worse.
Sorry i was not clear.
nothing to the scope since since then.
I need some help!
This is a big mess and I am sad.
Hantek seems to be more and more weird ... the MSO5074F(G) is gone from product page, there is MSO5054F(G) instead. There are no 2M point in the specs anymore but 1M (ok, at leat this has been fixed). The bandwidth is now specified as 40MHz (where one could think xx5x means 50MHz, hmm) instead of 70MHz. On chinese website there are still 5074F(G) listed, and of couse one can still buy them (but no sign of MSO5054F(G)). On OneDrive there is as well only MSO5054F(G) stuff, no sign of MSO5074F(G). This is all already weird, but check that : in the user manual, from MSO5054FG, there is picture showing MSO5054FG but with "70MHz / 1GSs" sticker on it. And now? What bw/numbering is real and what PS-made?
Another thing - they specified 4k <-> 1M as Logoc Anayzer Depth. So exact the same as on MSO5000D. However, due firmware bug there is always only 4k available on MSO5000D. Since 1.5yrs ... My question is - how is that working on MSO50x4F(G) ?
Is root filesystem space a likely cause of my 0xfb errors?Did you read/try this?: https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg206840/#msg206840 (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg206840/#msg206840)
Or, given I have version hw0 hardware should I just cut my losses and trade up for something newer/better and stop wasting time on this one?Actually according tinhead:
the hw0 was actually the best hw, the cost reduction was applied later. However i/o port on hw0 was not giving so many possibilities (like LA or DDS or even 100Mbit ethernet - only 10Mbit was available). So as long you using it as is, it's everything ok. Sure, you can add 10Mbit ethernet, but that's all then.
Did it again just to be sure....0xfb error.
i do like the logic plug system it uses, the 5074FG just has a pin socket array with kinda short logic leads. the 7084BLG uses the same as the old model MSO.... im looking at what i might want to get in a few months time when i feel like ive learned enough to deserve a real scope. i just want to see what it is i would be looking for at that time.
I just wanted to post my experience with the new Hantek MSO5074FG.
Contrary to info I have read, which said the trigger was available on only channels 1 and 2 and EXT, the scope could trigger on all four channels.
Now here's the bad. Once I installed the software and plugged the scope into my PC, the scope froze.
Also, in the PC trigger menu, you can set only channel 1 or 2 or EXT as trigger. But as I said earlier, I was able to trigger off of channel 3 and 4 when the scope controls worked!
FYI, I never found a way to use the "arbitrary" part of the waveform generator. The only thing the manual has to say about the subject is that you can "use the mouse to change the waveform."
*Update:
Hantek customer service sent me a rescue tool. It effectively reset the scope. So it's back up and running. I have found a multitude of ways to make the scope crash, but a total lock up is fairly rare, at least. I have only managed to do it once, or twice more, but at least there's a way to recover it, if you are next to a computer.
another Curios Problem on my hantek Handheld 1062b
i already bought 300mhz 100x Probe
So messuring AC 230V Inverter
Scale 50V PKPK 588V
Scale >=51V PKPK 750V
using 10X probe @ max Range 50V.. messuring is fine .. buw using 100x 51V- max Scale 500V messuring is completly wrong
So .. this would really be a little bit stupid for using 100X Probe with scale 100-200V
See Pictures.. any ideas?
Hello, I have a new version software, hardware and rescue tool may help solve your MSO5074FG problem.
www.hantek.com/Hantek/down/MSO5074FG.zip (http://www.hantek.com/Hantek/down/MSO5074FG.zip)
The reason with I settled to such compromise is that in my country the only trustworthy local seller was the well-know (in Europe) TME distributor.
"DSO5102P", hardware version "10000xffff8103" (so it well may be a DS5000C
1. I haven't made any modification ... 2ns ...
2.
... so that every time I restore a SetUp, the RTC is reset back to the time settings at the moment that I saved the respective setup, which is annoying in that I have to re-set it every time. Is it possible to modify some files or the firmware update file itself so that it doesn't save the date and time too?
3. Also, I saw a few tens/ hundreds of replies ago that Mr. "TinHead" managed to modify the firmware so that the sampling rate is displayed instead of time (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg294794/#msg294794 (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg294794/#msg294794)). Is it possible to patch the latest firmware too (20140111)? That would be useful for my second question too, because the date and time will not appear on my screenshot, so I wouldn't have to re-set them every time.
4. Regarding firmware, is there any more development for the "P" series, or any newer (than 20140111) one available? Please don't consider it as a request, it's more like a "more to come" view, than a "final, mature" software, with no more improvements and/or bug-fixes and/or unlocks to come.
5. More than two years ago a user named "flodins" posted a few photos depicting a desktop environment displayed on a Hantek DSO5062B unit (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg124677/#msg124677 (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg124677/#msg124677)), but besides those few posts no other updates were posted (and his home website's domain, http://flodins.info/, (http://flodins.info/,) is for sale). It seemed like a very interesting project, but I can't find any more info on the internet. Does anybody know the current status, or a way to replicate his result?
trustworthy is better than cheap. The germanelectronics.ro, which is Conrad/Voelkner could be an option as well, but they does not have P models (but the DSO-1062D which where same as Hantek DSO5062D).Yes, that's a good alternative, but as I read throughout this thread, there is a risk for the "D" series to be an older hardware version, whereas the "P" is newer and improved(?).
easy to check, download that tool from Peter http://peter.dreisiebner.at/dso-usb-tool/ (http://peter.dreisiebner.at/dso-usb-tool/) connect DSO to PC/MAC, run that software, go to shell tab and paste/execute "ls". When you see /dst1202b in the listing, then it was already hacked, when not, then it does have something to do with firmware (kind of "bug").Ok, I followed your suggestion, but before that I tried using your "Tools_P_models" backup tool, but after an hour or so it yielded a 1024KB "boot.bin", 4096KB "kernel.bin", 2048KB "logo.bin" and over 3GB of "root.bin" (it would have been even bigger where I not have cancelled the upgrade - by pressing the "cancel" button, and not by unplugging the USB stick or powering off). After that I re-checked your first post and saw that the tool applies to SN >15000, whilst mine is noticeably smaller. Is there another way to backup (should I use the nanddump commands via DSO USB Tool)? Regardless of any backup, I checked with "ls", and there is no /dst1202b, only the following:
OurLanguages
bin
chk_base_volt
cur_acq.type
dev
disk_sta.info
dso
dso.exe
dsod
dst1102b
etc
fpgabank.conf
help.db
i2c.log
icon
keyprotocol.inf
language.img
lib
linuxrc
logo
logotype
logotype.dis
mnt
msg
mult_adc.log
param
proc
protocol.inf
root
sbin
sys
sys.inf
tdc.log
tdc_edge125M
tdc_overtime125M
tdc_pulse125M
tmp
usr
var
So it's a software bug or some other form of hack (modification)? As I said, I was able to see multiple cycles of my 135MHz sine-wave (I just forgot to make a screenshot, I can make another one tomorrow, if necessary). Also, is there any way to read (not write, that operation is possible, as I saw in some posts) the value of the digital knee filter stored on the EEPROM? I'm curios if that was altered as well.this is of course crap. What you can try is to rename the /bin/date , it looks like the firmware is using it to set date/timeAnd what effect will the rename operation have?
well, all you need is the original 3.40.0_130717.0_P firmware, the patched 3.40.0_130717.0_P and the 3.40.0_140111.0_P. Then Ida Pro, hex editor, arm assembler book and some time - then you can made your own patch. It is really not that hard.Ummm.... can you please share some hints or instruction regarding the patching? It's a bit over my head, as I have very few experiences with such a task. Just some some first time short how-to?
that link is not working, but this does:
http://www.hantek.com/down/MSO5074FG.zip (http://www.hantek.com/down/MSO5074FG.zip)
I'm wondering a bit, only Hantek employees are using links with Hantek to point to their web server, are you one of them? >:D
Yes, that's a good alternative, but as I read throughout this thread, there is a risk for the "D" series to be an older hardware version, whereas the "P" is newer and improved(?).
Ok, I followed your suggestion, but before that I tried using your "Tools_P_models" backup tool, but after an hour or so it yielded a 1024KB "boot.bin", 4096KB "kernel.bin", 2048KB "logo.bin" and over 3GB of "root.bin" (it would have been even bigger where I not have cancelled the upgrade - by pressing the "cancel" button, and not by unplugging the USB stick or powering off).
So it's a software bug or some other form of hack (modification)? As I said, I was able to see multiple cycles of my 135MHz sine-wave
the value of the digital knee filter stored on the EEPROM? I'm curios if that was altered as well.
Ummm.... can you please share some hints or instruction regarding the patching? It's a bit over my head, as I have very few experiences with such a task. Just some some first time short how-to?
I have one more question: there is an option in the utility menu, as it looks, to save waveforms, i.e. to print them. I'm not sure how this is accomplished, I tried connecting three different printers (Laser, Inkjet and multi-functional), but I'm greeted by the same error "printer not detected, operation failed". So I assume it was designed to print via a printer connected to the front USB? It was just out of curiosity, it's real-life usefulness is kinda limited, but interesting (if one doesn't have a PC at hand).
2. Now some firmware "bugs": I'm using multiple settings for multiple types of signals to be analysed, so the settings save/recall feature is very useful (in order to spare the sensitive rotary encoders). The only issue is that the date and time is also saved and restored, so that every time I restore a SetUp, the RTC is reset back to the time settings at the moment that I saved the respective setup, which is annoying in that I have to re-set it every time. Is it possible to modify some files or the firmware update file itself so that it doesn't save the date and time too?
I'm currently using Tinhead's modified dst1kb_2.06.3_15102b_fact(130814.1).up firmware.I got this link from Hantek Tina.
I'm just curious, Is there any newer version than that?
Here's the latest version I got from Hantek.Unfortunately this firmware is not compatible with hw0 hardware version of this scope, but thanks anyway.
http://www.hantek.com/Product/DSO5000Series/DSO5102B_Firmware.zip (http://www.hantek.com/Product/DSO5000Series/DSO5102B_Firmware.zip)
Here's the latest version I got from Hantek.Unfortunately this firmware is not compatible with hw0 hardware version of this scope, but thanks anyway.
http://www.hantek.com/Product/DSO5000Series/DSO5102B_Firmware.zip (http://www.hantek.com/Product/DSO5000Series/DSO5102B_Firmware.zip)
I have one more question: there is an option in the utility menu, as it looks, to save waveforms, i.e. to print them. I'm not sure how this is accomplished, I tried connecting three different printers (Laser, Inkjet and multi-functional), but I'm greeted by the same error "printer not detected, operation failed". So I assume it was designed to print via a printer connected to the front USB? It was just out of curiosity, it's real-life usefulness is kinda limited, but interesting (if one doesn't have a PC at hand).
Could DSO5072P add a VGA output as optional?
How is this option enabled, as I would like connect the DSO to a flat panel monitor for display.
right, there is no other version compatible with hw0->hw1007 and kernel 2.6.13.I wonder if Hantek is going to put it on the download section, when it's available, but I guess they probably won't.
However, soon Hantek will made one (maybe the last one, depends on bug list status) for these models.
no, so that shit is not working, this is due errors in partiton table or the nanddump tool. Some models are unfortunately affected.So I should try the direct nanddump method (by inputting the commands via the DSO Tool), or there is simply no usable method of backing up for my model and s/n?
use google :) really. You will for sure find some tutorials (x86 for sure, some arm as well).Ok, will try, but after I have a working backup (just to be 100% sure I can recover from my "experiments") and enough knowledge.
Hello! My firmware dso5kp_func_dso5102p20140208 hasn't such RTC problem, you may update it to test.Thank you for the link!
www.hantek.com/Product/5000P/DSO5102P_Firmware.zip (http://www.hantek.com/Product/5000P/DSO5102P_Firmware.zip)
Yes, Hantek DSO5000 series support printer, but only HP laseijet1010/1020/1022.I see, I only tried with HP Deskjet and Lexmark laser. In the future I'll do as TinHead did, and implement my own printer(s)' drivers as well.
The Hantek ... hardware looks like it should be ok. The software is amateurish, and their support is laughable
You know, if you connect the 1kHz calibration output to a 50 ohm coax cable, then to a BNC T on one input and hang a half metre piece of coax cable on the spare end of the T. Set the input to 50 ohms, and look at the pulse reflection on the cable, and you can measure how many centimetres of cable you have attached to the input. Light travels about 20cm in a nanosecond (in a cable) and it's easy to measure 50cm of unterminated cable with the LeCroy.
Try that with the Hantek...
connect the 1kHz calibration output to a 50 ohm coax cable ... Try that with the Hantek...
connect the 1kHz calibration output to a 50 ohm coax cable ... Try that with the Hantek...
proprietary secrets
Hi. I have Hantek DSO5102B hw version 1010 and serial 19XXX. Tried to backup via nanddump in DSO-USB-Tool, but this command doesn't work. There is another way to make a backup?
what exactly is not working? Can you dump mtd1 ?There is no attempt to access USB flash drive (LED is not blinking), and does not appear any files on it.
There is no attempt to access USB flash drive (LED is not blinking), and does not appear any files on it.
Can I do something wrong?
then copy somthing to /mnt/udisk/ , e.g.Yes, this is works, appears busybox on flash drive.
cp /bin/busybox /mnt/udisk/
and then
sync
to check if the flash drive got recognized
then copy somthing to /mnt/udisk/ , e.g.Yes, this is works, appears busybox on flash drive.
cp /bin/busybox /mnt/udisk/
and then
sync
to check if the flash drive got recognized
ok, so give me that file. The "nanddump" itself is an link to busybox, which is multical binary. So maybe that version you have does NOT include nanddump command anymore.
ok, that busybox does include nanddump, so must be something else.found nanddump in a directory /usr/sbin/
Go to the shell tab and check (with ls) if there is nanddump in /usr/sbin/ or /usr/bin/
then try againThanks, it works. The problem, it turns out, was that I set the path to a flash drive "/mnt/udisk/dump/", but the "dump" folder on the flash drive does not exist. I thought it should automatically create. :-DD I should have simply specify "/mnt/udisk/", as you suggested.
/usr/sbin/nanddump -o -b -f /mnt/udisk/dump.bin /dev/mtd1
sync
that must work. You can of course connect via physical UART and check if nanddump is giving any error.
you welcome :)Here it is https://www.dropbox.com/s/z8tbe1jhhnn72ps/dump.zip (https://www.dropbox.com/s/z8tbe1jhhnn72ps/dump.zip)
Btw, could you zip your backup (of mtd0,1,2,3) and upload somewhere? Your S/N seems to be one of the latests,
so i could make more recent restore image (my current is with S/N just above 15000).
Here it is ...
I have another question. In my oscilloscope 2ns horizontal sweep available without any hack (file dst1102b in root directory). Does this mean that I do not make sense to do a software hack?
it seems that all current (with firmware 3.x from 2014) Hantek/Tekway "B", "BM", "BMV" and "P" models does have 2ns/DIV always enabled. That means, the presence of 2ns/DIV can NOT be used anymore as indication for a successful hack.So that explains my unit too. But is there a functional method of backup for my model (DSO5102P, s/n <15000)? Thanks!
Since 2 months i own a HANTEK DSO5102P. I also tried the DSO hack to go up to 200MHz, but i see no difference compared without it. I also had the 2ns timebase before.Hi, I also own the same model for some time and didn't have any of the issue you mentioned. Those limitations can be reproduced on my unit through some specific settings:
A 125MHz clock signal will be detected as 125.000 but i will not trigger at all.
Then i tried HANTEKs new Firmware dso5202p20140208 and dso5102p20140208.
Unfortunately i didnt make a backup,because previous tries always resulted in an endless loop until the USB-stick got full.
So what do you guess. This new firmware is worse than my previous one (see attachment).
So i requested Hantek to send me a copy of my previous firmware.
i did it once on my Tekway,with 800x600 reslution the picture looks ok
Who knows HDG2000B series has 10MHz external reference input(BNC) or not.
with no issue - i'm using MSO with 2M SRAM, so can during boot chose between MSO and BMV DSO), and between B and MSO models it is only the additional PCB mounted to i/o port on the B model mainbaord (and some few passive parts necessary to enable int , etc on the extra PCB).
How ... ?
How ... ?
If can find curve tracer on Tekway scope?
Wow, what kind of 'small external circuit' should be with?
I didn'n read all the topic but you can answer my question quicker. (I hope it :P)depends, some ppl know how to search, some know how to ask (dedicated) question, others spend weeks to read 160 pages to find nothing.
If I buy a Hantek DSO5102P and hack it into 200Mhz, shall I flash the DSO5202P's official firmware to DSO5102P or I have to use the DSO5102P type?after hack always firmware for the new model, so in your case DSO5202P
There is any different between the firmwares?currently no differences, but that might change.
I apologize in advance for posting what probably is a dumb question, but I really like my new scope and would hate to brick it by doing something that I am not sure of.
google "curve tracer circuit oscilloscope" there are lot of them. Some very simple (and working very good), some complex (and not giving any big difference, wondering why ppl always trying to "make better" simple things ...), enought to play with for years:
I got the latest firmware from the Hantek site (dso5kp_func_dso5102p20140208.up), and completed the update without a hitch. My problem is that the MATH MENU does not have the FFT option that is mentioned in the scope's data sheet and manual, before or after the update.
I would like to install Tinhead's improved firmware for the DSO5102P that was introduced on page 133 post 1994 of this thread, but while the post says the firmware is for the "P" series it does not mention any possible hardware versions?
I have read about differences occuring with serial numbers above 15000, but my serial number of (T 1G/036 001705) seems to be from a completely different series?
My question is does anyone have experience with Tinhead's improved firmware on a "P" series device with hardware version (1000xffff8103)?
so i assume you have 8103? In principle exact that version should have FFT and 40k memory maximum.
There are other ppl having same model, e.g. page 160, and no problems with FFT, as long of course memory
depth not set to higher than 20k and trigger not in Alter mode.
What when you do default setup, then go to math and scroll trough MATH options with arrows ?
(use F1 and/or F2 buttons to scroll, one can see only CH1+CH2, CH1-CH2, CH2-CH1, CH1xCH2, CH1/CH2,
the CH2/CH1 and FFT are not directly visible ...)
I did not notice the scroll arrows to the right of the math menu. Of course I have FFT available and my trace memory goes up to 40K, and my sweep speed down to 2ns per division. Everything just as it should be.
...
At 70+ years the old brain just is not what it used to be.
Thank you very much for your help and I will add a beer to your Paypal donation account, right now :-+
Before trying the BW hack, I tried to backup my DSO5102B ( bought some 3 weeks ago) using dso usb tool and nanddump. I entered those commands :Have a look there :https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let's-see!/msg476550/#msg476550 (https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let's-see!/msg476550/#msg476550)
nanddump -o -b -f /mnt/udisk/dump/boot.bin /dev/mtd0
nanddump -o -b -f /mnt/udisk/dump/logo.bin /dev/mtd1
nanddump -o -b -f /mnt/udisk/dump/kernel.bin /dev/mtd2
nanddump -o -b -f /mnt/udisk/dump/root.bin /dev/mtd3
The first 3 worked somehow but nanddump remained blocked at root.bin. It was continuously writing in the USB device so I unplugged it without waiting the end ( after something like 45 min) and root.bin was over 1.9 Go. This seems to be a known bug but I don't know if it is related to some models or completely random. Anyway, here are the system info :
model : Hantek DSO5102B
sw version : 3.30.0 (140610.0)
hw version : 1010x5555830f
serial number : T 1G/012 016***
The DSO was updated once with the latest firmware from Hantek before attempting the backup.
I didn't find any solution to the issue in this ( quite long) thread so if there is another way to make a full backup, I'm opened to suggestions.
I upgraded the scope to the latest file on the hantek site (not onedrive) and it updated successfully, but after a reboot the screen was black.
I connected to the UART and manually copied the correct dso.exe and afterwards, it worked again. After that, I tried the latest update from the hantek onedrive. This is my current situation.
Charging problems: It seems the battery does not charge anymore. Or more accurately: the software seems to think so. Symptoms: The battery symbol is always red, except when I plug in the power - then it switches to the "charging" animations for a few seconds (and then back to a red battery symbol). Also, when I remove the power, the device starts beeping like it had a low battery. This beeping stops when I plug the power back in. The scope still works when unplugged, it is only very annoying.
This was not the case before the update. Is there a way to fix this?
Fan: Before the update, the fan ran very rarely (maybe after 30mins on time). Now, it is always on. Is there a way to revert this?
Delay: When I measure the same signal on CH1 and CH2, there is a delay of 32ns (CH2 after CH1). Is this normal?
LAN: I would like to upgrade my handheld to LAN. I tried to understand as much as possible from this thread and mikrocontroller.net, but I am not sure. Is it enough to just solder in the DM9000 + magnetics + ethernet port + 25MHz crystal?
I could set the time base to 2ns/div without any hacking, but I made the hack.right, i posted here that all latest (from 2014) firmares does enable 2ns by default.
At the first seem nothing changed but I checked the sys.inf file and the [DST type]dst1202b so I think it's fine.that's ok, all what one can see after hack is if the filename has been really changed from /dst1062b or /dst1102b to /dst1202b.
At the first seem nothing changed but I checked the sys.inf file and the [DST type]dst1202b so I think it's fine.that's ok, all what one can see after hack is if the filename has been really changed from /dst1062b or /dst1102b to /dst1202b.
Well, and of course faster risetime/beter frequency response when measured.
I tried to switch dual-window mode after capturing a signal but the signal disappeared...if I use the dual-window mode from the beginning it's working. Is it a bug or I make something wrong?
Can someone validate this on actual "P" model? If so, you guys should send Hantek an email,
you have "P" model so you can check if new fw will work better.
If so, you guys should send Hantek an email, you have "P" model so you can check if new fw will work better.I have the latest fw. from the Hantek website so I sent a mail to the support team I hope they will correct it...
Finally, is there a substitute (i.e. drop-in replacement) for the DM9000AEP chip? I can't seem to find it anywhere near (in online store from my country). The other components (RJ45 socket, magnetics, and 25MHz osscilator are not that critical) Thanks!I can't find it too but if I read well the "B" model is compatible with the "A" (not necessary other driver) so I think you can use the newer one but I can't guarantee.. and the "B" is available from the farnell:
for DM9000AEP use ebay, e.g. item 171272339299 or 301232128882.
Is it worth to make the LAN access? Does it give extra function?
Before trying the BW hack, I tried to backup my DSO5102B ( bought some 3 weeks ago) using dso usb tool and nanddump. I entered those commands :Have a look there :https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let's-see!/msg476550/#msg476550 (https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let's-see!/msg476550/#msg476550)
nanddump -o -b -f /mnt/udisk/dump/boot.bin /dev/mtd0
nanddump -o -b -f /mnt/udisk/dump/logo.bin /dev/mtd1
nanddump -o -b -f /mnt/udisk/dump/kernel.bin /dev/mtd2
nanddump -o -b -f /mnt/udisk/dump/root.bin /dev/mtd3
The first 3 worked somehow but nanddump remained blocked at root.bin. It was continuously writing in the USB device so I unplugged it without waiting the end ( after something like 45 min) and root.bin was over 1.9 Go. This seems to be a known bug but I don't know if it is related to some models or completely random. Anyway, here are the system info :
model : Hantek DSO5102B
sw version : 3.30.0 (140610.0)
hw version : 1010x5555830f
serial number : T 1G/012 016***
The DSO was updated once with the latest firmware from Hantek before attempting the backup.
I didn't find any solution to the issue in this ( quite long) thread so if there is another way to make a full backup, I'm opened to suggestions.
you should be able to run the three commands needed via the DSO-USB-Tool.
It just uses another version of nanddump that should work. The 4 files will be zipped in the dump.tar.gz file and you should be able to extract them on a PC with 7zip for example or on a linux machine with the tar command.
(root.log)
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 2
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x07900000...
OK thanks.
Is there a way to update the .up backup file to work on the 5000p's? How are they created?
I have the same type of DSO and it's possible to change the bootup logo just need to recompile the whole display driver....not so easy than the other models so I left it.
After hacking the scope to 200Mhz, I flashed the 5202P firmware - even though it was the same version, it seemed to flash OK. But the bootup screen still shows the old model - is there a way to change that?
Do you mean 3.40.0(140208.0)?
re. 'digital filter', do you mean the optional 20Mhz bandwidth limit?
I have an extra yellow bar below the waveform when using Autoset (with Pk-Pk, Mean, Freq and Period readouts).
I also sometimes get a massive yellow box with tons of readouts that take up most of the screen. I haven't figured out yet what triggers that, or how to toggle it ...
First, System Info still lists the 5072p model - is that normal?
On all others, meaning even "B" models with 2.x firmware, or latest "P" models
in your case one can only use remote access to the Linux itself. This is for my needs sufficient. -tinhead
Knowing now that the latest "S" models (hw1.00.4) are S3C2416 SoC and Cyclone IV based no wonder that there was issues with latest firmware updates on older "S" models (hw 1.00.1 and hw 1.00.2).And would it be any real benefits from this except lower energy consumption?
i think lot of people are curious how they made the channel isolation.Judging by the photos is it good made? The black boxes with erased part numbers seem to be transformers.
Judging by the photos is it good made? The black boxes with erased part numbers seem to be transformers.
tinhead, do you know how the built-in DMM is calibrating in handhelds? Is there any file with calibration data, or there is no software ability to influence on dmm readings?
i accidently removed the dso.exe while playing around in the shell for the very first time (i am indeed a total noob)
when i try to start my Hantek DSO5102B it just freezes on the boot screen :S
Maybe someone out tthere has got the correct dso.exe? and maybe willing to share?
Using the BP:s "transparent UART bridge" macro with 115200 bps, I got a terminal and changed /dst1102b to /dst1202b.right, that work as well. The best hack ever was i think an atmega something sending only rm /param/save/r* to reset DSO with broken UI setup. But it worked, so what :)
I assume I will also have to remove the capacitors that PL00 talked aboutyes, on top and bottom side.
Also, thank you tinhead for all your work! Did "The Doc" send you those backup files? If not, I can do it if needed.
no, he probably missed my post. So yes, if you can made that backup for me.Alright, I sent a link in a PM.
no, he probably missed my post. So yes, if you can made that backup for me.Alright, I sent a link in a PM.
Hello!I broke my Hantek DSO5102P replaced file Russian.lan from DSO5062BM |O |O |O
Good!Say what I need to do I'll do.
what on your display is the latest version of "watchdog" on these DSOs, very powerful one. No more need for fight what so ever, simply insert flash drive with proper update files (system.up, hantek.up, emerg.do, etc). Unfortunately there is no documentation about and i have not (yet) reversed what/when happens.
In principle one have to download proper firmware (so for your model), decrypt it with proper password (in your case dso5000p) and encrypt it again with dsoduse (when trying system.up or hantek.up as recovery file name on flash) or 949307 (when using emerg.do as recovery file name on flash drive). And then of course rename that new encrypted firmwre file to one of these names above, copy to flash drive and then watch your DSO restroing itself.
DSO5062B patched to DSO5202B, hw1007.
Downloaded the newest firmware from Hantek, dso5kb_func_dso5202b20140805.up dated 8/8/14. Put the .up file on the root of a 2GB USB stick formatted FAT32. The DSO upgrade doesn't progress at all, fails with code 0xff.
Is the Hantek firmware on their web site compatible with hardware 1007? If not, what is the latest and where do I get it? Why else would the upgrade fail?
Hello all, new to forum. I have a Hantek DSO5072P and have done the 200mhz hack, and removed the two 47pf caps that PL00 identified. However, I am unable to find those caps on the bottom side of the board that tinhead said should also be removed. Can anyone identify where these capacitors are located?
no it's not, the last available firmware for hw1007 and DSO5000B is the one i patched, DSO-B-custom_2.06.3_130814.1.zip on my OneDrive (in fw, hw1007, custom).
got them, thanks for support!no, he probably missed my post. So yes, if you can made that backup for me.Alright, I sent a link in a PM.
I can't find any informations about the changings.
An must i install the Firmware for the DSO5202p after hacking it?
Can someone let me know what is the exact procedure to restore my scope in case something goes wrong?
I won't touch mtd0 and mtd1 so the bootloader will be intact. I also have plenty of JTAG tools, memory programmer etc. What's the restore procedure if I accidently botch the kernel (of course I have a full backup)?
The logo is stored as 16bit RGB565 values and one can binary patch the kernel without the need to recompile everything.
##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; LCD display size is: 800 X 480
Press Space key to Download Mode.!
SD:File System init failed!
##### Boot for SKY2416/TQ2416 Main Menu #####
##### EmbedSky USB download mode #####
[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash
[2] Download Eboot (eboot.nb0) to Nand Flash
[3] Download Linux Kernel (zImage.bin) to Nand Flash
[4] Download LOGO Picture (logo.bin) to Nand Flash
[5] Download UBIFS image (root.ubi) to Nand Flash
[6] Download YAFFS image (root.bin) to Nand Flash
[7] Download Program to SDRAM and Run it
[8] Boot the system
[9] Format the Nand Flash
[0] Set the boot parameters
[a] Download User Program
[n] Enter TFTP download mode menu
[r] Reboot u-boot
[t] Test Linux Image (zImage)
Enter your selection: 0
##### Parameter Menu #####
[1] Set NFS boot parameter
[2] Set Yaffs boot parameter for Standard Linux
[3] Set UBIfs boot parameter for Standard Linux
[4] Set parameter
[5] View the parameters
[d] Delete parameter
[s] Save the parameters to Nand Flash
[q] Return main Menu
Enter your selection: 5
Name(enter to view all paramters):
bootargs=noinitrd ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 mem=64M
bootcmd=nand read.jffs2 c0008000 kernel;bootm c0008000
bootdelay=1
baudrate=115200
ethaddr=10:23:45:67:89:ab
ipaddr=192.168.1.6
serverip=192.168.1.8
gatewayip=192.168.1.2
netmask=255.255.255.0
stdin=serial
stdout=serial
stderr=serial
ethact=dm9000
mtdids=nand0=nandflash0
mtdparts=mtdparts=nandflash0:512k@0(bios),512k(params),2048K(logo),4m(kernel),-(root)
partition=nand0,0
mtddevnum=0
mtddevname=bios
##### Boot for SKY2416/TQ2416 Main Menu #####
##### EmbedSky USB download mode #####
[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash
[2] Download Eboot (eboot.nb0) to Nand Flash
[3] Download Linux Kernel (zImage.bin) to Nand Flash
[4] Download LOGO Picture (logo.bin) to Nand Flash
[5] Download UBIFS image (root.ubi) to Nand Flash
[6] Download YAFFS image (root.bin) to Nand Flash
[7] Download Program to SDRAM and Run it
[8] Boot the system
[9] Format the Nand Flash
[0] Set the boot parameters
[a] Download User Program
[n] Enter TFTP download mode menu
[r] Reboot u-boot
[t] Test Linux Image (zImage)
Enter your selection: t
Now, Please connect to USB cable and USB interface!
Once the kernel is tested you may also flash it via the same method.git clone https://github.com/changbindu/dnw-linux.git
Enter bootloader by pressing space in console and then use dnw and a USB cable to transfer the new kernel.Where can I find the pinout of the JTAG connector for this scope (a very recent model DO5000B)? I've searched this thread and I haven't been able to find this info.
openocd -f target/samsung_s3c2440.cfg
telnet localhost 4444
Beware the ARM JTAG and Serial use 2mm spaced headers.
I decided to purchase a DSO mainly for analyzing Serial data transmission (Serial, USB, I2C, SPI, VGA, Video), various noise, spikes and other signals (cursor measurements, FFT analysis etc.).
...
Also, does this model know to decode serial data automatically?
...
I have chosen Hantek DSO5072P
I saw in the pictures that there is a possibility to add an Ethernet jack. Did anyone tried adding it? What is it useful for?currently, on "P" models, only for data transmitions
I've discovered that my bootloader allows kernel testing over USB. I've attached the serial capture and you can see the new menu. Once the kernel is tested you may also flash it via the same method.
There is a dnw utility for linux too:Code: [Select]git clone https://github.com/changbindu/dnw-linux.git
Enter bootloader by pressing space in console and then use dnw and a USB cable to transfer the new kernel.
I don't understand why nobody bothers to reply me. Common guys, you've been playing with this scope for years,
I've only had mine for 2 weeks.
What do you recommend for me to buy between hantek dso5072p and dso5062b? I understand that B model has more sample memory, but P model has newer hardware and software. Is the software on P model better?
Thank you for reply. Do they both run the same Linux kernel? (3.2) On the website it is stated that the B model runs 2.6.
I just looked at the power supply in the pictures. What voltages does it provide? I wonde if I could make the scope portable with some internal Li-Ion batteries.
do I still have to do the bw-hack (renaming the folder ?)no
or does the scope simply thinks that it's an real DSO5202P with full bandwidth ?yes
And: will the DSO5202P firmware provide more features than the model 5072P one ?
At least I expect another boot logo, but will there be more ?no, bootlogo is different thing:
no, bootlogo is different thing:
Hello, i install all the things for LAN comunication, but scope don't work. Someone have any idea?
.Hello, i install all the things for LAN comunication, but scope don't work. Someone have any idea?
even two :)
add two 22pf caps t the crystal (i assume you soldered 25MHz crystal?) and remove that 0R resistor.
(https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/?action=dlattach;attach=112581;image)
With this resistor one don't need crystal, in the theory, when FPGA is producing clock (which must not be the case in the current hardware / firmware). Easier, and always working, is when one use crystal, but then that resistor need to be removed and of course two caps need to be added to crystal as well.
mmm not, still doesn't work =( and microSD the same XD
you might as well check this
https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg467313/#msg467313 (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg467313/#msg467313)
before you change anything, make a back of the /i2c.log file. Inside that file you will find options you your models, you will have to creat a new EEPROM licensing (write HDVersion.set button) , use all values from your current i2c.log but change the "lan version" from 0 to 1.
yes, when you plug a cable.They dont do, then i think its something else like CHIP
Nothing to do, i chek again the components and all has good soldering. I think its a defective chip or i burned them
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: read wrong id 0xffffffff
dm9000 dm9000: wrong id: 0xffffffff
dm9000 dm9000: not found (-19).
root@hantek:~# rmmod dm9000
root@hantek:~# modprobe dm9000
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: eth%d: Invalid ethernet MAC address. Please set using ifconfig
eth0: dm9000a at c49e4300,c49e6308 IRQ 48 MAC: c6:fe:7c:c9:e1:c4 (random)
Nothing to do, i chek again the components and all has good soldering. I think its a defective chip or i burned them
on my 5072p I need to unload/reload the LAN driver for it to work:Code: [Select]dm9000 Ethernet Driver, V1.31
dm9000 dm9000: read wrong id 0xffffffff
dm9000 dm9000: wrong id: 0xffffffff
dm9000 dm9000: not found (-19).
root@hantek:~# rmmod dm9000
root@hantek:~# modprobe dm9000
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: eth%d: Invalid ethernet MAC address. Please set using ifconfig
eth0: dm9000a at c49e4300,c49e6308 IRQ 48 MAC: c6:fe:7c:c9:e1:c4 (random)
The driver doesn't seem to be getting loaded at all. Try running insmod /dso/drivers/dm9000.ko and see if anything shows up in the logHello, do it, this is the output:
[root@Hantek ~]#
[root@Hantek ~]# insmod /dso/drivers/dm9000.ko
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: eth%d: Invalid ethernet MAC address. Please set using ifconfig
eth0: dm9000a at c4976300,c4978308 IRQ 48 MAC: ba:97:89:4e:f1:22 (random)
[root@Hantek ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr BA:97:89:4E:F1:22
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:48 Base address:0x6300
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Looks good!First richard thx fpe your help.
You need to bring up the interface (using ifconfig + IP/subnet etc.) before you see any activity LEDs. I think you have to do all this manually, as far as I know the standard Hantek software doesn't support any kind of network stuff so it's only useful for custom work
OK Guys, I think I've solved it.Judging by the screenshots, it looks like you switched the probe attenuation to X1, from the default X10. Try moving the switch on the handle of the "bad" probe to X10 and it should work normally.
I was reading through page 158 when a came across a reply from Rosaharn to Pezibaer about 'Probe problems', and I thought 'I haven't tried the other probe'.
I'm one happy bunny, all is now back to normal (See attached screen shot).
So it was just a 'bad' probe.
Well it may help someone with a similar problem, so I will leave the post in place.
Thanks guys and especially tinhead for a fantastic thread, if it were up to me I'd nominate him for the 'Nobel Prize'.
oneeye
OK Guys, I think I've solved it.
I was reading through page 158 when a came across a reply from Rosaharn to Pezibaer about 'Probe problems', and I thought 'I haven't tried the other probe'.
I'm one happy bunny, all is now back to normal (See attached screen shot).
So it was just a 'bad' probe.
Well it may help someone with a similar problem, so I will leave the post in place.
Thanks guys and especially tinhead for a fantastic thread, if it were up to me I'd nominate him for the 'Nobel Prize'.
oneeye
Judging by the screenshots, it looks like you switched the probe attenuation to X1, from the default X10. Try moving the switch on the handle of the "bad" probe to X10 and it should work normally.
Help please, ostsillograf , my son wanted to install Russian language using DSO-USB-Tool, tab Read / Write File (F4) in the window 'Filename' bottom put 'Russian.lan' and hit Write. Now all the time breaks USB connection with the program 'DigitalScope', 'default setup' does not reset the color. Can someone give bekup? Help please!
sorry, but i can't communicate like that, to be able to repair something we first have to be able to talk to each other somehow. Post error message in your native language, maybe here is someone who can help you.Great forum :-+, if you read the first page, you learn a lot. tinhead, thank you!
Thanks for sharing. I tested your program and successfully change the logo in my Voltcraft DSO-1602D (sn > 15000)The logo is stored as 16bit RGB565 values and one can binary patch the kernel without the need to recompile everything.
I've discovered that my bootloader allows kernel testing over USB. You can see the new menu in this serial capture.Code: [Select]##### EmbedSky BIOS for SKY2416/TQ2416 #####
Once the kernel is tested you may also flash it via the same method.
This Board: SDRAM is 64MB; LCD display size is: 800 X 480
Press Space key to Download Mode.!
SD:File System init failed!
##### Boot for SKY2416/TQ2416 Main Menu #####
##### EmbedSky USB download mode #####
[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash
[2] Download Eboot (eboot.nb0) to Nand Flash
[3] Download Linux Kernel (zImage.bin) to Nand Flash
[4] Download LOGO Picture (logo.bin) to Nand Flash
[5] Download UBIFS image (root.ubi) to Nand Flash
[6] Download YAFFS image (root.bin) to Nand Flash
[7] Download Program to SDRAM and Run it
[8] Boot the system
[9] Format the Nand Flash
[0] Set the boot parameters
[a] Download User Program
[n] Enter TFTP download mode menu
[r] Reboot u-boot
[t] Test Linux Image (zImage)
Enter your selection: 0
##### Parameter Menu #####
[1] Set NFS boot parameter
[2] Set Yaffs boot parameter for Standard Linux
[3] Set UBIfs boot parameter for Standard Linux
[4] Set parameter
[5] View the parameters
[d] Delete parameter
[s] Save the parameters to Nand Flash
[q] Return main Menu
Enter your selection: 5
Name(enter to view all paramters):
bootargs=noinitrd ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 mem=64M
bootcmd=nand read.jffs2 c0008000 kernel;bootm c0008000
bootdelay=1
baudrate=115200
ethaddr=10:23:45:67:89:ab
ipaddr=192.168.1.6
serverip=192.168.1.8
gatewayip=192.168.1.2
netmask=255.255.255.0
stdin=serial
stdout=serial
stderr=serial
ethact=dm9000
mtdids=nand0=nandflash0
mtdparts=mtdparts=nandflash0:512k@0(bios),512k(params),2048K(logo),4m(kernel),-(root)
partition=nand0,0
mtddevnum=0
mtddevname=bios
##### Boot for SKY2416/TQ2416 Main Menu #####
##### EmbedSky USB download mode #####
[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash
[2] Download Eboot (eboot.nb0) to Nand Flash
[3] Download Linux Kernel (zImage.bin) to Nand Flash
[4] Download LOGO Picture (logo.bin) to Nand Flash
[5] Download UBIFS image (root.ubi) to Nand Flash
[6] Download YAFFS image (root.bin) to Nand Flash
[7] Download Program to SDRAM and Run it
[8] Boot the system
[9] Format the Nand Flash
[0] Set the boot parameters
[a] Download User Program
[n] Enter TFTP download mode menu
[r] Reboot u-boot
[t] Test Linux Image (zImage)
Enter your selection: t
Now, Please connect to USB cable and USB interface!
There is a dnw utility for linux too:Code: [Select]git clone https://github.com/changbindu/dnw-linux.git
Enter bootloader by pressing space in console and then use dnw and a USB cable to transfer the new kernel.
So my little C program works and this is my new logo screen of my scope.
Hantek just released GPL sources for Kernel/drivers and some test tools for Hantek HDG AWG,Oh wow! I'm downloading now - I want to make my MSO5102D actually do something useful with its logic analyzer. Having the source I'm sure I could implement protocol decoding, even if it's only over the USB link to the PC. Also making it USB SCPI compliant won't hurt either.
but they contain as well sources for Handhelds and benchtop Hantek DSOs, so go and grab it
if you wish to hack something ! This are the best Hantek GPL sources ever, and yes, they only
for gears based on Samsung S3C2416 SoC.
http://www.hantek.com/download/HDG.zip (http://www.hantek.com/download/HDG.zip)
Oh wow! I'm downloading now - I want to make my MSO5102D actually do something useful with its logic analyzer. Having the source I'm sure I could implement protocol decoding, even if it's only over the USB link to the PC. Also making it USB SCPI compliant won't hurt either.
Hi everybody, this is my first post I have been reading this very long thread and found it very interesting, I got myself a Hantek MSO5202D and I am generally very happy with it. I am not sure if this is the right place to ask this question, if not could someone direct me to the right place. I would like to write a program to access the oscilloscope under Windows but can seems to find a way to access the driver. I have littler experience with accessing drivers (only did it on a parallel port) but when it comes to USB I have no clues. I read the Das Oszi web pages with the protocol which seems simple enough but I tried using the windows CreateFile to open the device \\?\usb#vid_049f&pid_505a#5&b877f8b&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed} which is the Hantek oscillocope and it returns a valid file HANDLE however any WriteFile or ReadFile return an invalid operation (error code 1 from GetLastError()) Any clues on how to do this?
Again thank you very much.
Can the MSO5062D be hacked to add 2M memory?
...
It seems your knowledge about DSOs is googled togehther from here and thereis based on what exactly, what was wrong with any of my statements?
***S3C2440 CPU 400MHz BUS 100MHz 64M SDRAM (DST1000B bootloader)****(091201)
Tekway Bootloader (modify from mizi vivi)0.1.4 (root@rain-fc4) (gcc version 2.95
.3 20010315 (release)) #0.1.4 三 5??? 9 11:25:23 CST 2012
UPLLCON : 0x56022
MMU table base address = 0x33DFC000
NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung K9D1208V0M)
Found default parameters
GPfcon :0x5555
Press Return to start the LINUX now, any other key for Bootloader
from : 0x50000, size :0x200000, media_type:0x3
done
zImage magic = 0x016f2818
Setup linux parameters at 0x30000100
linux command line is: "noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySA
C0"
MACH_TYPE = 782
NOW, Booting Linux......
Uncompressing Linux.............................................................
........................................ done, booting the kernel.
Linux version 2.6.13 (root@rain-fc4) (gcc version 3.4.1) #2 Sat May 5 13:40:08 C
ST 2012
CPU: ARM920Tid(wb) [41129200] revision 0 (ARMv4T)
Machine: QQ2440
ATAG_INITRD is deprecated; please update your bootloader.
Memory policy: ECC disabled, Data cache writeback
CPU S3C2440A (id 0x32440001)
BUG: mapping for 0x19000000 at 0xd0000000 overlaps vmalloc space
S3C2440: core 405.000 MHz, memory 101.250 MHz, peripheral 50.625 MHz
S3C2410 Clocks, (c) 2004 Simtec Electronics
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists
Kernel command line: noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0
irq: clearing pending ext status 0000e000
irq: clearing subpending status 00000002
PID hash table entries: 512 (order: 9, 8192 bytes)
timer tcon=00000000, tcnt a4ca, tcfg 00000200,00000000, usec 00001e57
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 64MB = 64MB total
Memory: 61184KB available (2467K code, 995K data, 100K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
USB Power Control, (c) 2004 Simtec Electronics
S3C2440: Initialising architecture
S3C2440: IRQ Support
S3C2440: Clock Support, UPLL 48.000 MHz
SCSI subsystem initialized
usbcore: registered new driver hub
S3C2410 DMA Driver, (c) 2003-2004 Simtec Electronics
DMA channel 0 at c4800000, irq 33
DMA channel 1 at c4800040, irq 34
DMA channel 2 at c4800080, irq 35
DMA channel 3 at c48000c0, irq 36
NetWinder Floating Point Emulator V0.97 (double precision)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
yaffs Apr 24 2012 11:31:15 Installing.
Initializing Cryptographic API
Console: switching to colour frame buffer device 100x30
S3C24X0 fb0: s3c2410fb frame buffer device initialize done
GPIO L3 bus interface for S3C2440, installed
S3C2410 RTC, (c) 2004 Simtec Electronics
s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c2410_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2440
s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2410_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2440
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
nbd: registered device at major 43
Linux video capture interface: v1.00
ovcamchip: v2.27 for Linux 2.6 : OV camera chip I2C driver
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
s3c2410-nand: mapped registers at c4880000
30 ns is too big for current clock rate 101250
s3c2410-nand: timing: Tacls 0ns, Twrph0 4294ns, Twrph1 0ns
NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit
)
NAND_ECC_NONE selected by board driver. This is not recommended !!
Scanning device for bad blocks
Creating 3 MTD partitions on "NAND 64MiB 3,3V 8-bit":
0x00000000-0x00030000 : "bootloader"
0x00050000-0x00250000 : "kernel"
0x00250000-0x03ffc000 : "root"
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
usbcore: registered new driver ov511
drivers/usb/media/ov511.c: v1.64 for Linux 2.5 : ov511 USB Camera Driver
usbcore: registered new driver gspca
drivers/usb/media/gspca/gspca_core.c: gspca driver 00.60.00 registered
mice: PS/2 mouse device common for all mice
ts: Compaq touchscreen protocol output
s3c2410 TouchScreen successfully loaded
i2c /dev entries driver
SBC2440 SOUND driver register
SBC2440 SOUND driver probe!
SBC2440 UDA1341 audio driver initialized
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
VFS: Mounted root (yaffs filesystem).
Mounted devfs on /dev
Freeing init memory: 100K
rm: can't remove '/usr/udisk-flag': No such file or directory
CPU 400MHZ BUS 100MHZ
dso-iobank: install ok
<k>hantek_DSO5062B
dso-lcd installed lcd module ok
0x404
gpio_major_n = 4, io_minor_n = 4, output 0
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
S3C2410 USB Controller Core Initialized
USB Function Character Driver Interface - 0.5, (C) 2001, Extenex Corp.
usbctl: Opened for usb-char
usbctl: Started for usb-char
usbcore: registered new driver usblp
drivers/dso_drivers/usblp.c: v0.13: USB Printer Device Class driver
bwscon:0x22111110
fpga bank 11811
dso-fpga: install ok
S3C2410_GPECON : 0Xa00001aa , S3C2410_GPEUP: 0X0
rIICCON :0Xaf
dso-i2c: xx install ok
x gpio e: 0xaa0001a6, gpio g :0xfd62f19a , gdata:0x7f8f
dso-spi: install ok
dso-uart: install ok
dso-buzzer: install ok
0x60c
gpio_major_n = 6, io_minor_n = 12, output 1
fpga download file_name :/dn.rbf
data DOWN finish.
dso-spi:FPGA_DOWNLOAD ok.
hub 1-0:1.0: over-current change on port 1
hub 1-0:1.0: over-current change on port 2
no update file to foud
now run app .....
Please press Enter to activate this console.
[root@Tekway-dso /]# ls
OurLanguages fpgabank.conf logotype.dis sys.inf
bin help.db lost+found tdc.log
chk_base_volt home mnt tdc_edge125M
cur_acq.type i2c.log msg tdc_overtime125M
dev icon mult_adc.log tdc_pulse125M
disk_sta.info keyprotocol.inf opt tmp
dn.rbf language.img param tmpdst
dso lib proc ubdb.swi
dso.exe linuxrc root usr
dst1202b logo sbin var
etc logotype sys
[root@Tekway-dso /]# run
-/bin/sh: run: not found
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Restarting system.
.
arch_reset: attempting watchdog reset
***S3C2440 CPU 400MHz BUS 100MHz 64M SDRAM (DST1000B bootloader)****(091201)
Tekway Bootloader (modify from mizi vivi)0.1.4 (root@rain-fc4) (gcc version 2.95
.3 20010315 (release)) #0.1.4 三 5??? 9 11:25:23 CST 2012
UPLLCON : 0x56022
MMU table base address = 0x33DFC000
NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung K9D1208V0M)
Found default parameters
Dummy_isr error, interrupt number: 2
GPfcon :0x5555
Press Return to start the LINUX now, any other key for Bootloader
from : 0x50000, size :0x200000, media_type:0x3
done
zImage magic = 0x016f2818
Setup linux parameters at 0x30000100
linux command line is: "noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySA
C0"
MACH_TYPE = 782
NOW, Booting Linux......
Uncompressing Linux.............................................................
........................................ done, booting the kernel.
Linux version 2.6.13 (root@rain-fc4) (gcc version 3.4.1) #2 Sat May 5 13:40:08 C
ST 2012
CPU: ARM920Tid(wb) [41129200] revision 0 (ARMv4T)
Machine: QQ2440
ATAG_INITRD is deprecated; please update your bootloader.
Memory policy: ECC disabled, Data cache writeback
CPU S3C2440A (id 0x32440001)
BUG: mapping for 0x19000000 at 0xd0000000 overlaps vmalloc space
S3C2440: core 405.000 MHz, memory 101.250 MHz, peripheral 50.625 MHz
S3C2410 Clocks, (c) 2004 Simtec Electronics
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists
Kernel command line: noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0
irq: clearing pending ext status 0000c000
irq: clearing subpending status 00000002
PID hash table entries: 512 (order: 9, 8192 bytes)
timer tcon=00000000, tcnt a4ca, tcfg 00000200,00000000, usec 00001e57
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 64MB = 64MB total
Memory: 61184KB available (2467K code, 995K data, 100K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
USB Power Control, (c) 2004 Simtec Electronics
S3C2440: Initialising architecture
S3C2440: IRQ Support
S3C2440: Clock Support, UPLL 48.000 MHz
SCSI subsystem initialized
usbcore: registered new driver hub
S3C2410 DMA Driver, (c) 2003-2004 Simtec Electronics
DMA channel 0 at c4800000, irq 33
DMA channel 1 at c4800040, irq 34
DMA channel 2 at c4800080, irq 35
DMA channel 3 at c48000c0, irq 36
NetWinder Floating Point Emulator V0.97 (double precision)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
yaffs Apr 24 2012 11:31:15 Installing.
Initializing Cryptographic API
Console: switching to colour frame buffer device 100x30
S3C24X0 fb0: s3c2410fb frame buffer device initialize done
GPIO L3 bus interface for S3C2440, installed
S3C2410 RTC, (c) 2004 Simtec Electronics
s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c2410_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2440
s3c2410_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2410_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2440
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
nbd: registered device at major 43
Linux video capture interface: v1.00
ovcamchip: v2.27 for Linux 2.6 : OV camera chip I2C driver
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
s3c2410-nand: mapped registers at c4880000
30 ns is too big for current clock rate 101250
s3c2410-nand: timing: Tacls 0ns, Twrph0 4294ns, Twrph1 0ns
NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit
)
NAND_ECC_NONE selected by board driver. This is not recommended !!
Scanning device for bad blocks
Creating 3 MTD partitions on "NAND 64MiB 3,3V 8-bit":
0x00000000-0x00030000 : "bootloader"
0x00050000-0x00250000 : "kernel"
0x00250000-0x03ffc000 : "root"
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
usbcore: registered new driver ov511
drivers/usb/media/ov511.c: v1.64 for Linux 2.5 : ov511 USB Camera Driver
usbcore: registered new driver gspca
drivers/usb/media/gspca/gspca_core.c: gspca driver 00.60.00 registered
mice: PS/2 mouse device common for all mice
ts: Compaq touchscreen protocol output
s3c2410 TouchScreen successfully loaded
i2c /dev entries driver
SBC2440 SOUND driver register
SBC2440 SOUND driver probe!
SBC2440 UDA1341 audio driver initialized
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
VFS: Mounted root (yaffs filesystem).
Mounted devfs on /dev
Freeing init memory: 100K
rm: can't remove '/usr/udisk-flag': No such file or directory
CPU 400MHZ BUS 100MHZ
dso-iobank: install ok
<k>hantek_DSO5062B
dso-lcd installed lcd module ok
0x404
gpio_major_n = 4, io_minor_n = 4, output 0
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
S3C2410 USB Controller Core Initialized
USB Function Character Driver Interface - 0.5, (C) 2001, Extenex Corp.
usbctl: Opened for usb-char
usbctl: Started for usb-char
usbcore: registered new driver usblp
drivers/dso_drivers/usblp.c: v0.13: USB Printer Device Class driver
bwscon:0x22111110
fpga bank 11811
dso-fpga: install ok
S3C2410_GPECON : 0Xa00001aa , S3C2410_GPEUP: 0X0
rIICCON :0Xaf
dso-i2c: xx install ok
x gpio e: 0xaa0001a6, gpio g :0xfd62f19a , gdata:0x7faf
dso-spi: install ok
dso-uart: install ok
dso-buzzer: install ok
0x60c
gpio_major_n = 6, io_minor_n = 12, output 1
fpga download file_name :/dn.rbf
data DOWN finish.
dso-spi:FPGA_DOWNLOAD ok.
hub 1-0:1.0: over-current change on port 1
hub 1-0:1.0: over-current change on port 2
no update file to foud
now run app ..... <<<<<<<<<<<<<<<<<<<<<<<<<<here it's stops bootingup
Killed
The system is going down NOW!e this console.
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system reboot
Restarting system.
.
arch_reset: attempting watchdog reset
It's more than 250% of the $200 being asked for the Hantek. Then there's shipping on top of that.
Where can you get the DSO5072P for that price?
I'm sorry that I have to ask this question here, but with the massive size of this thread I find it incredibly hard to find the information I am looking for.
I got the following type of scope (see attached picture), and I am looking for the most recent firmware.
Can anyone point me in the right direction? Where do I find the most recent FW for this model?
Cheers,
LEECH666
It's more than 250% of the $200 being asked for the Hantek. Then there's shipping on top of that.
Where can you get the DSO5072P for that price?
http://www.aliexpress.com/item/Hantek-DSO5072P-Mixed-Signal-Oscilloscope-70MHz-1GSa-s-Real-Time-Sample-Rate/2030485138.html (http://www.aliexpress.com/item/Hantek-DSO5072P-Mixed-Signal-Oscilloscope-70MHz-1GSa-s-Real-Time-Sample-Rate/2030485138.html)
OK, the Hantek is showing as $264 delivered from that vendor.
The Rigol DS1054Z with shipping to Brunei would cost $464 from Tequipment.
So that's only 175% of the Hantek price :)
This is cheap for anyone in the UK, possibly EU?
£234 Delivered!!!
http://www.rapidonline.com/Test-Measurement/Voltcraft-DSO-1062D-Digital-Storage-Oscilloscope-60Mhz-51-5195/?source=googleps&utm_source=googleps&IncVat=1&gclid=Cj0KEQiAypGjBRCPme6jmqu3gZsBEiQA8NAiIKEPsXuYz_jq_NNbmlAVQVAzrSp39PaNllGlfwAQoJUaArY18P8HAQ (http://www.rapidonline.com/Test-Measurement/Voltcraft-DSO-1062D-Digital-Storage-Oscilloscope-60Mhz-51-5195/?source=googleps&utm_source=googleps&IncVat=1&gclid=Cj0KEQiAypGjBRCPme6jmqu3gZsBEiQA8NAiIKEPsXuYz_jq_NNbmlAVQVAzrSp39PaNllGlfwAQoJUaArY18P8HAQ)
No getting stung by taxes etc from China and easy to ship back if it has any faults.
Is there a official hantek or rebranded dealer for Australia?
seems on available from china/HK via ebay.
8)
Just changed my new handheld IP51 rated DSO8000E series model http://www.hantek.com/en/ProductDetail_1_159.html DSO8072E (http://www.hantek.com/en/ProductDetail_1_159.html DSO8072E) to 200MHz using Peter's DSO-USB-tool http://peter.dreisiebner.at/dso-usb-tool/ (http://peter.dreisiebner.at/dso-usb-tool/) via the shell. Hantek made a small change to the location of the files they are now stored in /dso/apps/ the command is:
mv /dso/apps/dst1072b /dso/apps/dst1202b
then reboot the scope using the power switch and keep your fingers crossed good luck. >:D
Thank you to Tinhead and all the other contributors. :-+
i got DSO8000E and will write an review and some hack infos withing few next daysGreat! tinhead
I think I have the latest software ( version 3.2.35 (130312.0) and hardware version 1010x55778340).Hi Claude,
The scope is really rugged, it has large clear fonts that hantek is well known for, the firmware could be improved on the FFT function.Hi donP! Any idea how to improve the FFT function?
The signal generator has an arbitrary waveform mode but no built in arbitrary waveforms like ECG which is found on most good arbitray signal generators, however this is a small thing since one can easily build their own waveforms on the PC and download onto the scope.Hope there will be improved waveforms soon.
Well, that certainly reminds me of the conspiracy theory that Microsoft was loose on copy protection in the early years to ensure that they get the market share in first.
2- Conrad got good prices from Hantek, so DSO-1062D from Voltcraft cost less than Hantek DSO5062B from China
directly (and DSO1062D=DSO5062B),
I don't know if it is a typo but the file you suggest as update for my MSO5202D is dst1kb3.2.25_????????? which is version 3.2.25 the one I have in my scope is 3.2.35 is it really the correct file or file name?I think it's a typo in the file name. I updated my MSO 5202D (same hardware version as yours) with this file without any problem.
Where do these firmware come from I checked Hantek site and the download page for firware never works..I think, you may try to email Hantek support mail box directly to ask for the old version firmware you need. :-/O
I should backup my firmware first, anybody knows which backup tools works with MSO5202D HW 1010x55778340?
I also have an RTC issue, where the clock (and date) hangs after a power-off, and is the same when I power it on (it doesn't reset to 2009, it is exactly the same time and date as just before I powered down), and continues to "tic" (i.e. it keeps going second-to-second) after the unit is turned on. I don't believe to be a problem with the backup battery, as it would have reset to 2009. Can anyone confirm my bug?Hi, this is a (late) follow-up on my RTC problem. I've finally gathered the nerves to troubleshoot it. After some analysis, and datasheet reading, I was convinced that the only culprit is the 32.768KHz quartz crystal resonator. My hypothesis was also backed-up by running "hwclock" via UART console. It's return value (date, time) was the same as the last manual setting (via the DSO's Utility menu), even if the unit was powered-cycled, meaning that the RTC's external source clock wasn't working (or the SoC was defective, but I didn't even dare to consider that :) ). After a quartz replace, it's finally working! Hope it helps others with similar issue.
As said above i took a look on the "Rescue Tool", when started it look like this:
(https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/?action=dlattach;attach=98822;image)
"connect and send", which is so far ok, but when one check the about dialog there is "Time and Language set". That look like the "tool" is or was doing more than only connect and send soemthing. And actually there is more, but all in chinese language and disabled. So i did translated it into english and re-aranged/enabled again all hidden things. Now the tool likes like this:
(https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/?action=dlattach;attach=98824;image)
Hi,UART connection is only for console mode connection. The Rescue Tool will connect through the rear usb connector but you will need dirvers installed on your system for that. Did you install them and were you able to connect to your scope with
could you tell me, please, if you've already tested this tool on the last devices? I bought Voltcraf DSO1062D from Conrad, sw v3.30.0 (140924.0) and hw v1010x55778344.
It was very easy to changed bw to 200MHz (by changer, but it is possible to change it in the os by rewriting some files, as it is noted above in this forum). I'd like to have an Ethernet interface, so I soldered Ethernet connector with two LEDs and trafo PULSE H1102NL. And wanted to use your software to change my license to net version. But I can't connect to scope. I trying it by rear USB connector, it's correct, please? Or should I use serial interface with UART on the connector J801? (No one LEDs on the Ethernet connector lights up and on the switch I haven't any connection - UTP cable is "dead".) My OS is Windows 8.1 64b. :(
Could you help me, please?
Hi, thank you for your kind offer of help. :clap:Hi, could you tell me, please, if you've already tested this tool on the last devices? I bought Voltcraf DSO1062D from Conrad, sw v3.30.0 (140924.0) and hw v1010x55778344.UART connection is only for console mode connection. The Rescue Tool will connect through the rear usb connector but you will need dirvers installed on your system for that. Did you install them and were you able to connect to your scope with TTsource?
Did you also add the 2 x22pF caps plus the 25Mhz Crystal? Eventually you could also have to remove a 0R resistor near the DM9000AEP...
If you could post a photo of the DM9000AEP area and a photo of the H1102NL than we might have more détails to help you...
But I don't know what do you mean "TTsource", what is it - it is software source?Sorry I made a typo , that is TTscope, the software that is on the miniCD you get with your scope. It allows control of the scope from your PC.
THX. You've helped me -> my software (from Conrad) has the name "Digital Scope" (=TTscope), it's in the version 2.0.0.7. And it was broken. When I repaired driver, I got "DSO USB Tool" broken, but "Digital Scope" is functional. And together with the "DSO Tool". Now I can connect to the scope and maybe to write some informations into it. But I'm afraid, first I'll do some backups ...But I don't know what do you mean "TTsource", what is it - it is software source?Sorry I made a typo , that is TTscope, the software that is on the miniCD you get with your scope. It allows control of the scope from your PC.
tinhead, do you know where calibration data is stored? If it is a file, I need to chek if it is readonly - the self calibration on my DSO1072E does not work - it exits on stage 11 and nothing changes. There is offset on the channels and the vertical voltage is not correct. (something like 360mV on 400mV square wave input).
Complete newbie ... considering a Hantek DSO5072P - the summary page mentions software upgrades but not removing capacitors(page last edited Nov 8 2014), is it still necessary to remove the capacitors pl00 mentioned here (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg411573/#msg411573)?
Im thinking about 70mhz version and upgrading it to 200mhz, I dont mind the rework as long as it can be done with an iron. Would you say paying for the b model is a waste of money? Is the scope to slow when using the deeper memory past the P models?
Secondly and this is my biggest fear, does the scopes front end have any issues or have the been fixed? How about the constant lock ups? After watching Daves video it somewhat scared me away. Although I know there has been plenty of firmware releases since then.
Lastly is there a way to hack some type of pass fail trigger even if its through USB? I would like to write scripts to integrate with my saeleae logic analyzer?
Sorry, it has took me so long ... Here is my photos. (http://host.csb.cz/osciloskop/)Hi, could you tell me, please, if you've already tested this tool on the last devices? I bought Voltcraf DSO1062D from Conrad, sw v3.30.0 (140924.0) and hw v1010x55778344. I'd like to have an Ethernet interface, so I soldered Ethernet connector with two LEDs and trafo PULSE H1102NL. And wanted to use your software to change my license to net version. But I can't connect to scope. I trying it by rear USB connector, it's correct, please? Or should I use serial interface with UART on the connector J801? (No one LEDs on the Ethernet connector lights up and on the switch I haven't any connection - UTP cable is "dead".) My OS is Windows 8.1 64b. :( Could you help me, please?Did you also add the 2 x22pF caps plus the 25Mhz Crystal? Eventually you could also have to remove a 0R resistor near the DM9000AEP...
If you could post a photo of the DM9000AEP area and a photo of the H1102NL than we might have more détails to help you...
ZdH,Thank you, I've thought I haven't any components ... But -> DM9000 has 100 pins - is't possible to put on the PCB? I'll study it againg. Thank you one more.
Try this... [see attachment jpg]
Make sure you put Y2 (25MHz Xtal) on the TOP side. :-)
-Decker
Thank you, I've thought I haven't any components ... But -> DM9000 has 100 pins - is't possible to put on the PCB? I'll study it againg. Thank you one more.You need the DM9000AEP in QFP48 package, here's an eBay example:
ZdH
MSO5202D is it possible to install the Russian language?
ZdH,I' want to install DM9000AEP, H1102NL and optos in RJ45 line. In theard #1105 is Tinhead's sch. and picture. Intresting me the types & values of missing components, (if it's possible).
Try this... [see attachment jpg]
Make sure you put Y2 (25MHz Xtal) on the TOP side. :-)
-Decker
I' want to install DM9000AEP, H1102NL and optos in RJ45 line. In theard #1105 is Tinhead's sch. and picture. Intresting me the types & values of missing components, (if it's possible).
(I' have same scope as ZdH, and juse their picture.)
I' want to install DM9000AEP, H1102NL and optos in RJ45 line. In theard #1105 is Tinhead's sch. and picture. Intresting me the types & values of missing components, (if it's possible).
(I' have same scope as ZdH, and juse their picture.)
vferencz,
The opto-isolator components are for UART-over-RJ.
You should not be installing LAN transformer with additional opto devices.
Just install the LAN components and be done. :-)
Use the UART over J801 with TTL 3.3v -> COM interface.
LAN components for latest HW version:
RJ LAN Jack (j2)
DM9000AEP (u17)
25MHz Xtal (y2)
LAN Xformer (jc1)
2x 22pF caps (remove 0 ohm resistor - if present)
And manual config of network module via UART console...
All of the necessary info is available in the recent posts to this thread.
-Decker
Hello !
This is my 1st post on EEV blog, and english is not my 1st langage. I hope you'll be indulgent !
I just got a brand new Hantek DSO5102P yesterday, after my old CRT oscope died on me last week. This is my first DSO.
System information :
Model : DSO5102P
SW version : 3.40.0(140925.0)
HW version : 1000xffff8108
Serial : T 1G/036 xxxxxx
I have one question : is it possible to make it wireless with a bluetooth module, for use with DigitalScope, and for data logging ? (HC-05 for example).
I have no idea of the required baudrate. I also imagine that the UART is not suitable (???). I've read almost all this huge thread, but did'nt find the needed information. It seems to me that the UART port is intended for remote access to the embeded system, nothing else (???)
Reply #2459 on: August 27, 2014, 12:46:25 PM
I'd just like to thank tinhead for his hard work and dedication to hacking this 'scope... Cheers!
My DSO5072P arrived today and I finally plucked up the courage to hack it. I tried it first with the DSO-USB tool but it locked up and the 'scope froze. I thought I'd killed it, but it rebooted and I decided not to risk it that way again.
I didn't have a USB-Serial adapter but I did find a Serial over Bluetooth adapter, so I wired it in and connected using Putty, then changed the file name and the name of the scope in logotype.dis, and I'm up and running.
I'll probably leave the Bluetooth module in for now. It might come in handy one day, and it saves taking it apart again.
Now I just need to figure out (I need someone else to figure out) how to change the boot logo... ;D
Hi,
I have received a Volcraft DSO-1062D scope that crashes at the very begining after start, shoving only Volcraft logo. After connecting via UART to my laptop with Putty software I have noticed that linux faild to start with "Kernel panic - not syncing: Attempted to kill init!" error.
Full log below.
Can I ask anyone that has simmilar scope (Hantek DSO5062D or Takwey) to make a backup file for me that I could flash mine?
I guess the flash chip broken. :palm:This may rather come from a corrupted partition. If this is the case, this could be fixed by flashing again this partition... but we need a flash dump from a working device for that...
:-[
Hi All, I have Hantek 1062BV with SW Version : 2.01.1(131115.0) HW Version : 10020x55558312
I had used the 200 hack earlier ( did not do the logo hack as it did not work),today i had updated to the latest firmware from Hantek site the 200 firmware dso1kb_2.01.1_DSO1202BV(140730.0).up instead of the 60 mhz one.
Now the Oscilloscope blanks up after showing the Hantek Boot screen and the Firmware Number.It just blanks up,i tried removing the battery etc but of no help.Have also send across a mail to Dave ( Tim ) as iam struck and it wont progress ahead
Vinay
Hi all,
After 4 years of service - but <10 hours total runtime - my Tekway DST1102B expressed its disapproval for being ignored by popping a capacitor. Sorry, I don't have the cap number in the board but it's the -5V rail cap next to the regulator. The blown cap was completely dried out and opened (thankfully). Replacing it with a known good one brought the scope back to service with no other apparent damage.
Regards,
JR
Hello !
This is my 1st post on EEV blog, and english is not my 1st langage. I hope you'll be indulgent !
I just got a brand new Hantek DSO5102P yesterday, after my old CRT oscope died on me last week. This is my first DSO.
System information :
Model : DSO5102P
SW version : 3.40.0(140925.0)
HW version : 1000xffff8108
Serial : T 1G/036 xxxxxx
I have one question : is it possible to make it wireless with a bluetooth module, for use with DigitalScope, and for data logging ? (HC-05 for example).
I have no idea of the required baudrate. I also imagine that the UART is not suitable (???). I've read almost all this huge thread, but did'nt find the needed information. It seems to me that the UART port is intended for remote access to the embeded system, nothing else (???)
Hello !
This is my 1st post on EEV blog, and english is not my 1st langage. I hope you'll be indulgent !
I just got a brand new Hantek DSO5102P yesterday, after my old CRT oscope died on me last week. This is my first DSO.
System information :
Model : DSO5102P
SW version : 3.40.0(140925.0)
HW version : 1000xffff8108
Serial : T 1G/036 xxxxxx
I have one question : is it possible to make it wireless with a bluetooth module, for use with DigitalScope, and for data logging ? (HC-05 for example).
I have no idea of the required baudrate. I also imagine that the UART is not suitable (???). I've read almost all this huge thread, but did'nt find the needed information. It seems to me that the UART port is intended for remote access to the embeded system, nothing else (???)
THis website gives you all the info you need: http://www.circuitsathome.com/measurements/hantek-dso5000-series-oscilloscope-modifications-part-1-doubling-the-bandwidth-of-dso5102b (http://www.circuitsathome.com/measurements/hantek-dso5000-series-oscilloscope-modifications-part-1-doubling-the-bandwidth-of-dso5102b)
Pin layout, speed, etc.
Are you OK with changing the HC-05 settings, or do you need some help with that?
Hi guys i wanna to ask any1 , is there some has got experince with HANTEK MSO7084BLG ? Is it hackable to better rate?hello!
Can I ask a very noobish question: How do you connect the PC with the scope? I have a hantek dso5102p, my first scope, and naturally would like to up its sampling rate to 200, but I'm not sure how to connect the two together.
Hi, I got lost in this extremly long thread. Did anyone have the chance to tear down all the 3 models: DSO-5062B,5102B,5202B? What are the hardware differences between these 3 models? Someone said there is a little difference at the frontend? Is it true? What is the real bandwidth when DSO-5062B is hacked into "200MHz"? Or DSO-5102B hacked into "200MHz"? The amplitude should not be lower than the -3dB value.... :-// :-// :-//
After an firmware upgrade It did not work. (did not start)
Via serial port I repaired the NAND FLASH, it was full with pictures.
Now the oscilloskop working properly, but only on the half srceen.
Badest that i did not get jtag firmware dump before uploading new firmware. Is there any chance to get Jtag dump from someone of you guys ?Hi Nikolas, I have the same 'scope and haven't got around to tearing it apart and messing with it just yet, so the firmware is factory.
How old is this DSO4072c model? Is it hackable? I search everywhere but can't find any reviews or mention of this DSO4000c series - not even here - the only thread discussing Hantek.
Would like to hear if anyone has comments on it. Is DSO 4072c a better model to get at the same price?
[root@Hantek ~]# cat sys.inf
[DST type]dst1202b
[soft version]3.30.0(150116.0)
[fpga version]0x55778344
[start time]33
[update time]0
I'm interested in :Yes, me too! I currently use it piggy backed with a cheap ass Salae so I can do stuff on the PC. I can't see why the Hantek, despite having a USB interface, doesn't have standard fucking drivers like USBTMC with SCPI to use with NI-VISA, etc.
tweaking the OS with the intention of running custom code such as protocol analysers
adding the lan portThis has been done, but there is nothing of substance to use it for, at least with the existing crappy firmware.
removing the smell of tobacco smoke (it's not grubby but it sure stinks)
I decided on a Hanko DSO5102P for my first scope.Great choice for a first scope. Never heard of it, can't find it on google either. What made you decide on this enigma? :palm:
I went for the Rigol.
Macbeth: got link to the 100Mhz hack.
Here a few, not so good, photos of one side of the hantek dso1122s board:
http://www.davidefabbri.net/files/foto/SANY0114.JPG (http://www.davidefabbri.net/files/foto/SANY0114.JPG)
http://www.davidefabbri.net/files/foto/SANY0115.JPG (http://www.davidefabbri.net/files/foto/SANY0115.JPG)
http://www.davidefabbri.net/files/foto/SANY0116.JPG (http://www.davidefabbri.net/files/foto/SANY0116.JPG)
http://www.davidefabbri.net/files/foto/SANY0117.JPG (http://www.davidefabbri.net/files/foto/SANY0117.JPG)
http://www.davidefabbri.net/files/foto/SANY0118.JPG (http://www.davidefabbri.net/files/foto/SANY0118.JPG)
http://www.davidefabbri.net/files/foto/SANY0119.JPG (http://www.davidefabbri.net/files/foto/SANY0119.JPG)
P.S. by the way I'm looking for the sd socket, have you got a suitable part number ( or farnel/mouser code )
Hello,
I bought a new Hantek DSO1122S and I would like to add LAN support. The board looks like that one from post #2282:Here a few, not so good, photos of one side of the hantek dso1122s board:
http://www.davidefabbri.net/files/foto/SANY0114.JPG (http://www.davidefabbri.net/files/foto/SANY0114.JPG)
http://www.davidefabbri.net/files/foto/SANY0115.JPG (http://www.davidefabbri.net/files/foto/SANY0115.JPG)
http://www.davidefabbri.net/files/foto/SANY0116.JPG (http://www.davidefabbri.net/files/foto/SANY0116.JPG)
http://www.davidefabbri.net/files/foto/SANY0117.JPG (http://www.davidefabbri.net/files/foto/SANY0117.JPG)
http://www.davidefabbri.net/files/foto/SANY0118.JPG (http://www.davidefabbri.net/files/foto/SANY0118.JPG)
http://www.davidefabbri.net/files/foto/SANY0119.JPG (http://www.davidefabbri.net/files/foto/SANY0119.JPG)
P.S. by the way I'm looking for the sd socket, have you got a suitable part number ( or farnel/mouser code )
I am running SW 2.01.1 (150108.0)
HW version is 10040x57029100
(I guess that means HW1.00.4)
I have a DM9000AEP, an HL1102NL and a RJHSE-5381 Jack (RJ45).
Is it enough to solder these in place? Do I need anything else? What about that 25M crystal that is missing on board? Is it required or can the DM9k run from the FPGA clock? I have read soemething about a 0R SMD that should be removed, but I do not understand why. Are all the other parts (resistors, caps) already on board or do I need to add something? If the crystal is required, is it possible that the caps are already on board?
Thanks in advance for any assistance.
Yes you will need a 25MHz crystal. The load caps are already on the board, C467, C468. Given how close C467 looks to the crystal you may want to check the size of the crystal part to make sure they do not touch. I did a similar mod to my sig gen and the only parts needed where the RJ45 socket, magnetics, chip, crystal and in my case the load caps. Don't know about any 0R resistor. Hope this helps.
Yes you will need a 25MHz crystal. The load caps are already on the board, C467, C468. Given how close C467 looks to the crystal you may want to check the size of the crystal part to make sure they do not touch. I did a similar mod to my sig gen and the only parts needed where the RJ45 socket, magnetics, chip, crystal and in my case the load caps. Don't know about any 0R resistor. Hope this helps.
We have a 14 months old DSO1062BV that wont start, when we connect it to battery or Power adapter. All it does is make a "TRRRRK" chatter under the cans.
This Unit was earlier repaired under warrenty for the same issue and checked after repair to be running OK, now it has not been used in last 4 months and has developed the same issue.
Any idea where to start since the dealer is absolutely useless and will not honor his own repair warrenty and is pretty useless.
Thanks for any pointer towards repairing the same
Posting iton this forum as this issue happend when i updated the firmware and it didnt reboot.It later developed the same "TRRK" chatter issue in the cans after i did the 200 hack and tried rebooting it.
Thanks for any pointer to resolving this issue, the oscilloscope has hardly been used earlier before the repair and now just a few moths after repair it is again dead, without being used even once.Is this dso so unreliable or did the dealer who fixed it did a shoddy job.
Vinay
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).Yeah! Welcome back tinhead!
tinhead
Hi.it's not connected (sorry I forgot to write that)
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.yes, rdx to tdx and vice versa. otherwise the terminal window stays empty
-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.hmm... then I just see the character I type (once, as in a 'normal' terminal
-Check that flow control and parity is set to None.was not, changed it, no difference
-Check in device manager that the comport has 115200 speedsetting. This is normaly 9600.set in putty - do I need to set it somewhere else?
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.Thanks, I'll try that.
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.
Hi,
I've got an Hantek MSO5062D
Software Version 3.2.35 (141129.1)
Hardware Version 1020x55778344
Serial Number T 1G/012 023xxx (so higher than 15000)
In this version the PINs for the serial interface are completely missing, but I just plugged some in.
I can connect with my USBtoSerial adapter and see the starting of Linux. But after booting the console cannot be reached by pressing "Space and Ctrl-C" (and enter)
I've googled and read a lot of pages of this topic but I did not find any solution to this problem (nor anybody else who has this issue).
Any hints? what did I miss?
Hi all,
I just got a Hantek 5202P, and noticed something odd. Above 20ns/div in equivalent time, the waveform reconstruction becomes very erratic, like it is piecing together the wrong slices of waveform. The triggering was fine at 20ns and faster in real-time just in equivelent time the sampling seems to fail. And, at slower than 20ns/div equivalent time works okay (although it isn't really all that useful at the low sleep rates). Is this need a f/w update to latest or does it sound like a hardware bug? A self-cal didn't help. F/W version 3.40.00
More info :
It appears that there's no uart login because /etc/init.d/rcS gets stuck. It's executing dsod in the foreground and doesn't return. If dsod is killed, the script runs to completion, starting telnetd and allowing inittab to run getty.
There's still a problem : the tty flags are wrong and it needs a line feed to terminate a line. But, ^Jroot^Jstty sane^J fixes things. Note that you actually have to login - the initial console dies.
I've tried backgrounding the dsod in rcS but it then seems to run twice (and it's already got two instances running so that's three. )
More info :
It appears that there's no uart login because /etc/init.d/rcS gets stuck. It's executing dsod in the foreground and doesn't return. If dsod is killed, the script runs to completion, starting telnetd and allowing inittab to run getty.
There's still a problem : the tty flags are wrong and it needs a line feed to terminate a line. But, ^Jroot^Jstty sane^J fixes things. Note that you actually have to login - the initial console dies.
I've tried backgrounding the dsod in rcS but it then seems to run twice (and it's already got two instances running so that's three. )
I'm in the same boat. Brand new MSO5062D. How did you manage to kill dsod? CTRL-C doesn't seem to be doing anything.
Are the DSO5xxx's still hackable? Ebay has them going for 200 USD shipped (looks like vendors are trying to push out old stock to prep for a new model?). I had no intention of buying one but 2 chans at 200 mhz for 200 USD, eh, impulse purchase territory right there.
Yeah, sorry, 260, my mistake. What's you get isntead? Can anyone report if the new firmware is any better? The acquisition hardware + screen size all seem appealing, the reboots seem like firmware issues, that perhaps was resolved over the course of the year between now and when you bought it..Are the DSO5xxx's still hackable? Ebay has them going for 200 USD shipped (looks like vendors are trying to push out old stock to prep for a new model?). I had no intention of buying one but 2 chans at 200 mhz for 200 USD, eh, impulse purchase territory right there.
I'm not seeing where you get that idea from. I see the one you linked with a starting bid of $199.99 ($34.99 shipping), but the buy it now prices is still $259.99, which is right around what I'm seeing all the others being offered for. But to answer your question, yes, they are still hackable, but honestly, even if they were going for $100 its still a waste of money. I made the mistake of buying one over a year ago and had nothing but trouble with it. Constant complete lockups that required a reboot. Ended up sending it back and getting something else.
The BMV model seems to be the most advanced model. 2 MPoints of sample memory and Video Help.
Does anybody here on the forum have example videos of the Video Help feature?
Seems like a nice feature! :)
drwxr-xr-x 2 root root 880 Jul 2 20:32 OurLanguages
drwxr-xr-x 2 root root 24016 Jun 8 2015 bin
-rwxrwxrwx 1 root root 43 Jan 1 2009 chk_base_volt
-rw-r--r-- 1 root root 4 Jan 1 2000 cur_acq.type
drwxr-xr-x 4 root root 0 Jul 4 00:11 dev
-rw-r--r-- 1 root root 125 Jul 2 19:50 disk_sta.info
drwxr-xr-x 5 root root 488 Mar 7 09:00 dso
-rwxr-xr-x 1 root root 4529432 Jul 2 20:32 dso_bin
-rwxr-xr-x 1 root root 0 Mar 7 09:00 dst1072b
-rwxr-xr-x 1 root root 0 Jun 8 2015 dst1102b
drwxr-xr-x 5 root root 808 Jul 2 20:30 etc
-rwxr-xr-x 1 root root 924672 Jun 8 2015 help.db
-rw-r--r-- 1 root root 8192 Jun 12 2015 i2c.log
drwxr-xr-x 2 root root 11096 Jun 8 2015 icon
-rwxr-xr-x 1 root root 1131 Jun 8 2015 keyprotocol.inf
-rw-r--r-- 1 root root 0 Jun 12 2015 language.img
drwxr-xr-x 6 root root 15120 Jul 2 20:32 lib
lrwxrwxrwx 1 root root 11 Jun 8 2015 linuxrc -> bin/busybox
-rw-r--r-- 1 root root 8 Jul 4 00:11 logotype
-rwxr-xr-x 1 root root 15 Mar 7 09:00 logotype.dis
-rw-r--r-- 1 root root 524288 Jul 4 00:11 misc.bin
drwxr-xr-x 5 root root 352 Jun 8 2015 mnt
-rw-r--r-- 1 root root 0 Jul 4 00:27 msg
-rw-r--r-- 1 root root 317477 Jul 2 20:55 mult_adc.log
drwxr-xr-x 3 root root 224 Jan 1 2000 param
dr-xr-xr-x 52 root root 0 Jan 1 1970 proc
-rwxr-xr-x 1 root root 4448 Jun 8 2015 protocol.inf
drwxr-xr-x 2 root root 160 Jun 8 2015 root
drwxr-xr-x 2 root root 5264 Jul 2 20:32 sbin
drwxr-xr-x 11 root root 0 Jul 4 00:11 sys
-rw-r--r-- 1 root root 105 Jul 4 00:11 sys.inf
-rw-r--r-- 1 root root 2400 Jan 1 2009 tdc.log
-rw-r--r-- 1 root root 1113 Jan 1 2009 tdc_edge125M
-rw-r--r-- 1 root root 1126 Jan 1 2009 tdc_overtime125M
-rw-r--r-- 1 root root 1114 Jan 1 2009 tdc_pulse125M
drwxr-xr-x 2 root root 0 Jul 4 00:11 tmp
drwxr-xr-x 8 root root 552 Jun 8 2015 usr
drwxr-xr-x 2 root root 0 Jul 4 00:11 var
One thing I've noticed with my particular unit is that the mainboard was definitely not washed; the board is a little sticky to the touch and I was wondering whether it's worth the risk to take some flux remover and give it a good scrub, followed with some isoprop to get the surface of the board squeaky clean. The digital stuff won't care so much but the input circuitry seems like it might appreciate this kind of treatment. Do you have any comment on that?
Is it in the same range as the Siglent or Rigol what? They both make more than 1 model. Also, instead firing off questions for every little thing, is there some reason you can't look up most of this information yourself?
You still aren't being exact enough for CustomEngineerer who clearly can't offer anything either way.Is it in the same range as the Siglent or Rigol what? They both make more than 1 model. Also, instead firing off questions for every little thing, is there some reason you can't look up most of this information yourself?
Of course I can look at the specs, but specs don't say a lot.
There is overall noise floor of the oscilloscope, and then there is also noise on the offset level.
Moreover some people might have both Hantek and Rigol or Siglent, and can contribute with their comparison and experience on both scopes.
Sorry tinhead, but... :(
THE KING IS DEAD, LONG LIVE THE KING!...
Welcome, tatus1969! :-+
Reached my goal: Gaussian response, as much bandwidth as possible.
Sorry tinhead, but... :(
THE KING IS DEAD, LONG LIVE THE KING!...
Welcome, tatus1969! :-+
hrhr, no big dealReached my goal: Gaussian response, as much bandwidth as possible.
my goal was to get as much as possible "affordable" DSO with flat (and not gaussian) response, to replace my broken TDS754D, which i managed to get with my hardware hacks. Happy to see, that you reached your goal.
Btw, it seems they have some new engineers, they changed a lot of things in latest fw versions, equ sampling is implemented (that was funny to see), 9 digits frequency counter (at least on my old hw version MSO), some bugs (where is was begging for) has been finally fixed. Bit late, yeah, but at least my new DSO8202E have all the new things as well (except the 9 digit frequency counter) implemented.
How is that on other (latest hw) models?
with flat (and not gaussian) responseThat is pobably a bit philosophical subject. Maximally flat response reproduces the slope best but adds significant overshoot. Gaussian response is slower but has no overshoot. Depends on what properties of your signal you are interested in. By the way, I think that your solution should actually be close to Gaussian, and the overshoot is probably mostly software related (sinc filter). Would be interesting for me if you could post a screenshot with equ sampling time.
Btw, it seems they have some new engineers, they changed a lot of things in latest fw versions, equ sampling is implemented (that was funny to see), 9 digits frequency counter (at least on my old hw version MSO), some bugs (where is was begging for) has been finally fixed. Bit late, yeah, but at least my new DSO8202E have all the new things as well (except the 9 digit frequency counter) implemented.It is still crashing now and then, but not annoyingly often. And it seems to be related to specific (exotic?) settings.
How is that on other (latest hw) models?
By the way, I think that your solution should actually be close to Gaussian, and the overshoot is probably mostly software related (sinc filter). Would be interesting for me if you could post a screenshot with equ sampling time.
I got a new firmware package from Hantek support, and can share it if you are interested. It is not on their website. And important to mention: they seem to have changed their crypto keys.
are you sure that you got firmware for proper model?They have firmware update packages for the 5000B on their website. But after I applied that I had a smaller revision number than before. The scope was still working though. The package that I sent you is from Hantek support.
I just bought a MSO7000BLG series used Oscilloscope for $400.Would be interesting if you could post pictures from the input stages. How have you terminated the transmission line at oscilloscope side, was that inline termination or does the scope have it integrated? It it was the first, then the frequency response does not surprise me. The DSO5000B's input stage had quite long traces adding inductance, and they had not compensated them. This caused excessive ringing, also when feeding 50R terminated signals.
They Changed the format of the front side bus trying to make it smaller. The scope uses the Samsung S3C2416XH-40. The Internal File Structure Appears to be the same, and the bandwidth hack apparently still works on this version. LAN is availible to be added. Can't seem to Identify the memory chip. It may be the 1GB NAND (K9F1G08U0E) that I'm assuming for the software.
Most of the internal boards except the main are marked with DSO5000E.
I'm planning on doing the Lan hack, 2GB memory hack, and seeing if I can add a Bluetooth UART to the debug connection.
With the 300MHz (aka dst1302b) hack turned on I measured the following data points from channel 1.
With 1V set @ 1KHz
800mv @ 80MHz
740-760mv @ 150MHz - 400MHz
1.1V @ 480Mhz
@ 490MHz Hardware Side Failed to read Properly
@ 500MHz Software Side Jumps by 12MHz and has long since been inaccurate (around 300MHz).
@545.9MHz it finally started reading 700-680mv jumping from accuracy and knee.
Take all measurements with a grain of salt since the 250KHz - 40GHz generator has been damaged before by other students. I do have pictures of the higher end frequencies to prove it. Unfortunately, they are too big.
I did direct line from waveform generator to scope, non terminated. Would expect reflections.From the pictures, the analog stage pretty much looks identical to the DSO5000 series. They probably have tweaked here and there, but they also made the trace from BNC to the range relay muuuch longer. I would be surprised if that amplifier is anywhere flat.
The BNCs are most likely non terminated. Have identified the DM9000EP location and the on board DDR2 SRAM is 64mb from the serial.
Images are here: https://1drv.ms/f/s!AnmmyurkkYaJilHJ6x7BgxpD3wSC
Looked at i2c.log for hardware version number and it showed "102"
Thanks for the hack! I had it done in just a few minutes and also updated it the most recent stock firmware then with tinhead's modified firmware. Unfortunately, this scope had issues before that. Most of the time it would read a flat DC signal(or square wave) up to 800mV too high depending on the time base and vertical settings.Had you disconnected your probes during calibration?
It will self calibrate, but doesn't seem to help. There's actually a new issue now. Seems to be reading the peaks a bit better(5.00v-5.20v), but look at the minimum, maximum and mean. Any idea on this?
I can hear a relay click at step 24/36 then it resets without an error message.If problem continues, please check the 595 in the Frontends. Had a similar problem after both 595 gone bad, solder new ones in and one was not soldered right at one or two pin and than the calibrations resets at point 24/36 too. Maybe it can help
I can hear a relay click at step 24/36 then it resets without an error message.If problem continues, please check the 595 in the Frontends. Had a similar problem after both 595 gone bad, solder new ones in and one was not soldered right at one or two pin and than the calibrations resets at point 24/36 too. Maybe it can help
Just to make sure, you're referring to the 74HC595Ns, correct?:-+
QuoteJust to make sure, you're referring to the 74HC595Ns, correct?:-+
In my scope both (74HC)595 TSSOP16 in the Frontends for Ch1 and 2 was completly faulty. Maybe one of yours also... Got a bunch of them as bargain on eBay, so the replace was very cheap.
QuoteJust to make sure, you're referring to the 74HC595Ns, correct?:-+
In my scope both (74HC)595 TSSOP16 in the Frontends for Ch1 and 2 was completly faulty. Maybe one of yours also... Got a bunch of them as bargain on eBay, so the replace was very cheap.
Thanks, I appreciate it! I just ordered some. I'll report back soon.
You could try and follow the signal path from the BNC to the ADCs, with no signal. Also check the reference voltage of the differential path. I would also check soldering, maybe push on some chips to find cold joints. Check for thevreverse engineered schematic that is around.QuoteJust to make sure, you're referring to the 74HC595Ns, correct?:-+
In my scope both (74HC)595 TSSOP16 in the Frontends for Ch1 and 2 was completly faulty. Maybe one of yours also... Got a bunch of them as bargain on eBay, so the replace was very cheap.
Thanks, I appreciate it! I just ordered some. I'll report back soon.
Replaced both and same issue. Triple checked the soldering. Ordering the Rigol 1054z, as I need a working scope within the next two weeks. I appreciate the help, though. I'll mess with it later.
Hi,
I just bought an Hantek DSO5102P and I want to unlock the bandwidth to 200Mhz.
My question is after I unlock the oscilloscope how can I do the fw update?what update I could use DSO5202P or DSO5102P.
The second question is after unlock I can use official updates or only modified?
Thanks
oh man the bugs and oddities on the MSO5074FG... that could be an entire thread of its own!
Too bad they can't open up the UI software and document how to talk to the FPGA and hardware. Let us take a crack at the UI...
Prompt pinout JTAG connector J901 (10 pin connector) on the board hw version 1.01 from DSO5072P. 1 and 2 - 3.3V, 3 - nTRST, 4 - nRESET, 8 and 10 - GND. The rest are not known.
they actually hired someone who can at least read my buglist, and even fix some of them .. but it takes still forever ;(
This is mine with different HW, I want to add LAN (22pf capacitor, 25Mhz crystal oscillator, DM9000), UART and J-tag Pins.
The micro SD card slot have the same role like the front USB?
Which of the pin group are for UART and J-tag?
I've check different hardware configuration and on all the J801 is for UART
J2 -> RJ LAN Jack
U17 -> DM9000AEP (it can be found below the main board)
Y2 -> 25MHz Xtal
JC1 -> H1102nl Sop-16
Thanks
Hi, I bought a hantek DSO5062BMV a while back and it looks like there haven't been firmware updates since 2014, I attached my system info window.
I tried installing the latest firmware from the hantek website but i get this error: "No upgrade files detected on USB device". From what I could skim in this thread, the BMV is just a BM with a sd card with video tutorials, the BM model had updates this year. Is there a way to install that firmware on my scope? Did anything really improve since 2012? I am getting increasingly frustrated on how crappy this scope's firmware is :(
Hi, I bought a hantek DSO5062BMV a while back and it looks like there haven't been firmware updates since 2014, I attached my system info window.
I tried installing the latest firmware from the hantek website but i get this error: "No upgrade files detected on USB device". From what I could skim in this thread, the BMV is just a BM with a sd card with video tutorials, the BM model had updates this year. Is there a way to install that firmware on my scope? Did anything really improve since 2012? I am getting increasingly frustrated on how crappy this scope's firmware is :(
As I can see from the firmware file in the Hantek page, the last firmware is from 2014-08-23! When you choose Hantek you should restrain your selection on the more basic and popular models. Firmware support isn't the best thing in Hantek, they simple don't care, mainly with the less popular models like yours.
By the way, in your model, BMV looks like V stands for Video Help... Really?! Do you think it makes sense a video help on the scope to the point of paying twice the original P model? Again, Hantek is all about the basics, anything more is just to rip some extra money from you. That's why I think that a scope like GW Instek GDS-1072AU is definitely a better option, I would chose that instead if I knew what I know today.
GW Instek GDS-1072AU 70MHz Dual Channel TFT Oscilloscope (Maplin N53NA) (https://youtu.be/xyoHgwmylnM)
Hi, I bought a hantek DSO5062BMV a while back and it looks like there haven't been firmware updates since 2014, I attached my system info window.
I tried installing the latest firmware from the hantek website but i get this error: "No upgrade files detected on USB device". From what I could skim in this thread, the BMV is just a BM with a sd card with video tutorials, the BM model had updates this year. Is there a way to install that firmware on my scope? Did anything really improve since 2012? I am getting increasingly frustrated on how crappy this scope's firmware is :(
Hi, I bought a hantek DSO5062BMV a while back and it looks like there haven't been firmware updates since 2014, I attached my system info window.
I tried installing the latest firmware from the hantek website but i get this error: "No upgrade files detected on USB device". From what I could skim in this thread, the BMV is just a BM with a sd card with video tutorials, the BM model had updates this year. Is there a way to install that firmware on my scope? Did anything really improve since 2012? I am getting increasingly frustrated on how crappy this scope's firmware is :(
send email to Amy Cai caiyijun@hantek.com
in principle they can always compile latest firmware for your hardware version
Got the update from Hantek, they said my kernel is no longer supported for updates (so they just gave me the 2014 one), to the question of how I could update my kernel they said "Buy a new one", lol.
Firmware file i got from Hantek (https://drive.google.com/file/d/0B4B_JmDvI-0eRlFjU2tNYXFjTDQ/view?usp=sharing)
ha ha ha ha-ntek
i have kernel 2.6.30.4 running, with month old firmware 3.30.0 running on my old Tekway (with exact same hw version than yours).
Yes, i do all updates over the network, manually, but it is possible.
for older hardware, there is still hidden direkt link
http://www.hantek.com/Product/DSO5000/DSO5202B_Firmware.zip (http://www.hantek.com/Product/DSO5000/DSO5202B_Firmware.zip)
where for new hardware, and that link is on Hantek's webpage, is
http://www.hantek.com/Product/DSO5000/DSO5202B_Firmware2.zip (http://www.hantek.com/Product/DSO5000/DSO5202B_Firmware2.zip)
Hi,I also had issues with failing calibration when I developed my improved 250MHz analog hack (www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg979548/#msg979548 (https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg979548/#msg979548)). It seems that the they check if offset and gain of the input stage are within reasonable ranges. I would look there first.
I have 2x scopes of the of revision hw1005, hacked to 200MHz bandwidth and updated to firmware 130814.
Both worked fine, until a year ago, when the first one started to hang at step 8/36 of self calibration - error code 0x400.
Now the second Hantek fails self calibration too, only at step 2/36 with error code 0xa00
Any idea, how to fix it ? Is it caused by a HW defect and what components are most likely concerned ?
Hello,
I have an Hantek DSO5102P oscilloscope with stock firmware dso5kp_func_dso5102p20140208 on it, that has not been used for the last 6 months.
Yesterday I tried to turn it on and remains frozen on screen logo. I connected a serial interface to internal port and I got the following result (text file).
How can I solve this problem? I did dump restore before installing the firmware. If I try to rewrite root.bin with DNW freezes, as shown in picture.
I can access the boot menu but I can not get into console. Please help.
Please add fw_backup.bin fileHello,
I have an Hantek DSO5102P oscilloscope with stock firmware dso5kp_func_dso5102p20140208 on it, that has not been used for the last 6 months.
Yesterday I tried to turn it on and remains frozen on screen logo. I connected a serial interface to internal port and I got the following result (text file).
How can I solve this problem? I did dump restore before installing the firmware. If I try to rewrite root.bin with DNW freezes, as shown in picture.
I can access the boot menu but I can not get into console. Please help.
Problem solved via JTAG port. The programming interface is simple. Cost insignificant. Programming requires 270 minutes with this interface.
Very slow speed, only 10K per second with this LPT interface. But you can correct firmware problems. My problem consisted in bad NandFlash.
I changed NandFlash. I programmed NandFlash with fw_beackup.bin
1. Install H-Jtag software ( download from http://www.hjtag.com/en/index.asp (http://www.hjtag.com/en/index.asp) )
2. Set the parallel port (JTAG Interface pins)
3. Open the file "config processor HJTAG.hfc" in H-Flasher with Load
4. Write fw_beackup.bin in NandFlash
5. Restart the power
Hi, I have a DSO5102P hw version 1010, sw version 3.40.0. I renamed dst1102b to dst1202b and have rebooted several times but the model number hasn't changed. Have I missed something, or does this recent firmware (19/6/16) disable the hack?edit logotype file (with vi /logotype ) and change dst1102b to dst1202b
Tinheads 200MHz Input Hardware ModificationDid you see this? https://www.eevblog.com/forum/testgear/hantek-ds5000-series-300mhz-input-stage-mod/msg1201675/#msg1201675 (https://www.eevblog.com/forum/testgear/hantek-ds5000-series-300mhz-input-stage-mod/msg1201675/#msg1201675)
Yes, I saw this and did go through your PDF. Great contribition!thanks! And yes, truly right... But my mod does not only increase the bandwidth, but also removes ringing artifacts. That was my primary goal, the bandwidth came along with it.
I have all the parts for the Tinhead mod already since 4 years and got my courage together to perform this mod.
Your mod is more complex and my rational was to leave out the benefit of the increased bandwidt above 200Mhz in respect to the 1G samplingfrequency.
Hello all, I have read (well scanned) all 117 pages and was all ready to do the 200mhz hack to my new DSO5072P like I had previously done to my old 5072P some years ago. Then I turned the sec/div knob, and it went down to 2ns. So, is it already at 200mhz but without the hardware mods? Anyone know what the latest HW mods should be? And, do I still need to the name change thing? sw ver: 3.40.0, hw version: 1010; S/N T1G/135xxxxxx Best regards...Did you catch this link while scanning? https://www.eevblog.com/forum/testgear/hantek-ds5000-series-300mhz-input-stage-mod/ (https://www.eevblog.com/forum/testgear/hantek-ds5000-series-300mhz-input-stage-mod/)
I managed to repair the oscilloscope. Replaced NAND and RAM, then flash via jtag. Everything works fine.
Any chance we can modify the useable RAM by hardware modification? I realize this probably means the firmware has to be recompiled, just wondering...NAND flash can be replaced by a larger one without recompiling.
I recently purchased a hantek dso5072p 70mhz scope. Picked up the required items to gain access to uart and a usb drive. Followed the directions exactly and no matter what I do or how many times I do it, or reboot it after doing it, or chmod ing the files so the scope can not change them it appears as a dso5072p in the menu every single time. I decided to update to latest firmware from hantek and rinse and repeat to same results. If it matters I've been able to turn the knob to 2ns even the day I pulled it out of the box.
**********************
Another thing worth mentioning. I've never had a bootscreen with my model number. I get a square qr code with hantek typed out, and then the second screen hantek your testing solution then im in the scope running
sw version 3.40.0 (170714.0)
serial ended in 8069
lcd.front.ts 3.3.0
If anyone could help me out that would be great.
>Quote
Quote from: hasjon on Yesterday at 08:05:34 AM (https://www.eevblog.com/forum/index.php?topic=1571.msg1402592#msg1402592)Hi All
I have successfully made serial connection with my Hantek DSO5102P, via USB to serial and the direct USB connection. Attempted to reflash. However after the reflash, the oscilloscope hangs after the reboot. Upon power up, the Hantek logo displays and after that nothing happens.
Please see the attached screens shots from 'EmbedSkyDownLoadTool_V1.0'' and the terminal Running Information after transferring the file 'wh5 root_dso5102p3.ubi'.
I believe I may have the wrong .ubi file. I may have a partition error and thus would also require a working backup from another DSO5102P. Please can someone provide a backup and help to convert to the correct .ubi file so that I can attempt a successful firmware reflash.
Thank you
No more opening and soldering connections to hack would be an incredible feat imo!
>QuoteQuote from: Terry01 on Yesterday at 06:26:43 PM (https://www.eevblog.com/forum/index.php?topic=1571.msg1403885#msg1403885)If your machine is showing the 2ns out the box the 200MHz upgrade is already done. I got my 5102p from Amazon around a month ago and it was already done from the factory. I have seen quite a few others the same.
Enjoy! :)
Very interesting.
I don't know if this matters or not, but after checking the FW, it would appear that it is using the 5072P according to the Hantek website.
Questions:
1: Does DSO4072C have all functionalities DSO5072P have, plus a function generator?
2: Can DSO4072C be hacked to get 200Mhz bandwidth?
3: Are there any reverse engineering data for DSO4072C/DSO4102C/DSO4202C?
Thank you very much for your quick reply! I guess I will save 100 pounds :) By the way is there any advantage of buying the 200mhz version apart of keeping your warranty (which anyway I guess is useless since I am buying the scope from China) ?
The 60MHz and 100MHz models come with 150MHz probes. I expect the 200MHz models will come with 200MHz probes.
Apart from that ...
all current 60 and 100MHz models are using not that great (for hacking over 100MHz bw) combination of resistors in input stage.
When hacked to 200MHz, there is up to +5dB overshoot at 150MHz (depends on probe type and termination kind)
I've made tons of measurments on current models (and where to modify):
http://www.mikrocontroller.net/attachment/173049/mod_input_circuit.pdf (http://www.mikrocontroller.net/attachment/173049/mod_input_circuit.pdf)
of my old Tekway DST1202B
http://www.mikrocontroller.net/topic/249628?page=8#3092292 (http://www.mikrocontroller.net/topic/249628?page=8#3092292)
of how bad the frequency response is on current60/100MHz DSO hacked to 200MHz
http://www.mikrocontroller.net/topic/249628?page=8#3098757 (http://www.mikrocontroller.net/topic/249628?page=8#3098757)
and how it can be improved to near perfect (don't forget, this is flat-response DSO, this overshoot need to be there)
http://www.mikrocontroller.net/topic/249628?page=8#3093970 (http://www.mikrocontroller.net/topic/249628?page=8#3093970)
Short said, by replacing the 4x22R resistor arrays in inputt stage the frequency response is already better (or on what it was on original 200MHZ DSO).
This can be however even more improved :
RX1_1 = RX1_2 = RX1_3 = RX1_4 = change all to 270R 0.1% (digikey 4 x P270DBCT-ND)
RX2_1 = RX2_2 = RX2_3 = RX2_4 = change all to 270R 0.1% (digikey 4 x P270DBCT-ND)
RA01_1 = RA01_2 = change all to 4 x 33R 1% (digikey 2 x CRA6E833.0ACT-ND)
RA02_1 = RA02_2 = change all to 4 x 33R 1% (digikey 2 x CRA6E833.0ACT-ND)
R01_25, R02_25 = change to 49R9 0.1% (digikey 2 x P49.9DBCT-ND)
R01_27, R02_27 = change to 120R 0.1% (digikey 2 x A103149CT-ND)
R01_29, R02_29 = change to 1R (what so ever 1206 resistors)
As the original probes are anyway not so good (oh well, they good up to 100MHz, for sure) it might change them to different models as well,
in my measurments you can see the original probe results (PP-150), some better chinese probes from Texas (TX250 -simply ebay "texas probes")
and more expensive 500MHz passive probes from Testec (HF-512).
for older hardware, there is still hidden direkt link
http://www.hantek.com/Product/DSO5000/DSO5202B_Firmware.zip (http://www.hantek.com/Product/DSO5000/DSO5202B_Firmware.zip)
where for new hardware, and that link is on Hantek's webpage, is
http://www.hantek.com/Product/DSO5000/DSO5202B_Firmware2.zip (http://www.hantek.com/Product/DSO5000/DSO5202B_Firmware2.zip)
Have an OLIMEX ARM-USB-OCD-H JTAG Flasher and OpenOCD as
JTAG software.
Can anyone give me a guide to flashing the K9F1G08U0D-SCB0 and the
to to give necessary firmware?
set CHIPNAME s3c2416
set CPUTAPID 0x07926f0f
source [find target/samsung_s3c2416.cfg]
adapter_khz 1000
adapter_nsrst_delay 100
jtag_ntrst_delay 100
reset_config trst_and_srst
scan_chain
nand device $_CHIPNAME.nand s3c2412 $_TARGETNAME
openocd -f interface/jlink.cfg -f smdk.cfg -c init -c halt
nand probe 0
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html (http://openocd.org/doc/doxygen/bugs.html)
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
adapter speed: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
TapName Enabled IdCode Expected IrLen IrCap IrMask
-- ------------------- -------- ---------- ---------- ----- ----- ------
0 s3c2416.cpu Y 0x00000000 0x07926f0f 4 0x01 0x0f
Info : No device selected, using first device.
Info : J-Link ARM V8 compiled May 27 2009 17:31:22
Info : Hardware version: 8.00
Info : VTarget = 2.154 V
Info : clock speed 1000 kHz
Info : JTAG tap: s3c2416.cpu tap/device found: 0x07926f0f (mfg: 0x787 (<unknown>), part: 0x7926, ver: 0x0)
Info : Embedded ICE version 6
Info : s3c2416.cpu: hardware has 2 breakpoint/watchpoint units
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x800000d3 pc: 0xc3e06ba4
MMU: enabled, D-Cache: disabled, I-Cache: enabled
Info : accepting 'telnet' connection on tcp/4444
NAND flash device 'NAND 128MiB 3.3V 8-bit (Samsung)' found
nand erase 0
nand raw_access 0 enable
finally, write the actual file:nand write 0 uboot.bin 0
Pleas upload, link to DSO-USB-TOOL..
Thx..
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: read wrong id 0x2b2a2928
dm9000 dm9000: wrong id: 0x2b2a2928
dm9000 dm9000: not found (-19).
bkl tq2416-backlight initialized done...
close beep now
dso-buzzer s3c2416-beep initialized done...
hub 1-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
ifconfig: SIOCSIFADDR: No such device
mkdir: can't create directory '/param': File exists
mkdir: can't create directory '/param/sav': File exists
open_serial_device:open serial success
Langu_Init() <opt/language.c,220>: read img languID=87
Langu_Init() <opt/language.c,226>: set locale1=1
Langu_Init() <opt/language.c,235>: set domain1=1
Langu_Init:Dso_GetLanguageID = 0
hub 1-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
hub 1-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
hub 1-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
hub 1-0:1.0: unable to enumerate USB device on port 2
I did the hack to convert my DSO5102B to a DSO5202B some years ago which went well. The last firmware update was back in 2013. I recently tried to update the firmware but it I get Error: 0xfe No upgrade files detected on USB device.
What do I do to be able to update the firmware on the scope?
Thanks for any help!!
Model: DSO5202B
SW Vers: 2.06.3(130814.1)
HW Vers: 10070x555583ED
SN: T 1G/012007832
Hey lads,
There's a new firmware release on the hantek site dated yesterday or the day before 3.40.0(190125.0), that makes it one year and five days since the latest update 3.40.0(180120.0)
The changed files are show_pic and dso.exe.
A plain dumb strings diff suggests at least some bugfixes .. so it might worth testing this against your favourite bugs.
Happy upgrade.
Cheers,
A plain dumb strings diff suggests at least some bugfixes .. so it might worth testing this against your favourite bugs.
>QuoteQuote from: Terry01 on Yesterday at 06:26:43 PM (https://www.eevblog.com/forum/index.php?topic=1571.msg1403885#msg1403885)If your machine is showing the 2ns out the box the 200MHz upgrade is already done. I got my 5102p from Amazon around a month ago and it was already done from the factory. I have seen quite a few others the same.
Enjoy! :)
Very interesting.
I don't know if this matters or not, but after checking the FW, it would appear that it is using the 5072P according to the Hantek website.
Just bought mine and got it since last saturday.
It's a 5102P 100 MHz
Upgraded firmware to 3.40.0 dated 25-JANUARY-2019
hardware revision 1010xffff8108
Goes down to 2 ns
Please tell me where I can find detail information of this equipment, I didn't find it on website.
I thought it was mentioned some time ago that the 2ns feature is no longer an indication that the hack worked, or that its 200Mhz.
It comes as default now, but doesnt mean you have 200Mhz enabled.
May be wrong, but I am sure I read that on here from Tinhead
When giving one signal on 2 channels (through cables of identical length) oscillograms are shifted rather each other on 2ns.
How can a noobie like me build a 200 MHz generator to test it ?
I have no idea how to
For me it's mostly crashing when in split-screen/zoom mode, I haven't been able to identify the exact settings.good to know about the screen cable... if it becomes white my face will do the same :phew:
I also had issues with the loose screen connector but that usually just results in a white screen, rarely a reboot.
I don't know if it's the case to use this thread but this seems to be the most famous one about these scopes, the fact is that I think to have found a bad firmware bug and spotted how to replicate it
the bug is the entire scope that freezes after startup, i can tell it's doing that because the Led near the V0 knob is on while powerup (sometimes ALL the Leds are on but it's ok apparently), when it comes to actual wave screen it seems going but there's an "adjust V0 to set brightness" message on the bottom and the moment i touch ANYTHING it freezes immediately for a pair of seconds and reboots with all the memorized setups at default, this happens like once per 10\20 times i turn it on and i always have the fear it bricks totally, i remember it rebooted also once, while messing too fast with a lot of settings, apart this startup problem
recently I press "default setup" before turning it off and apparently it never did that again... honestly the only setting I usually had on was the silly buzzer for button presses (apart regular settings like 20MHz bw filter, 5V per unit vertical, and maybe a faster timebase), probably it fails some settings checksum
my unit is a DSO5102P with fw dso5kp_func_dso5102p20170714... the previous 3.40.0 161227.0 had the same exact issue (sorry the format of the infos i give) i waited some time before posting this considering it may do this trick again but apparently it did not
some apparently say that it may be a bad CMOS memory but at this point i also think it can be a battery-to-line power transition issue... i don't know :-//
any idea? solutions? similar cases?
I don't know if it's the case to use this thread but this seems to be the most famous one about these scopes, the fact is that I think to have found a bad firmware bug and spotted how to replicate it
the bug is the entire scope that freezes after startup, i can tell it's doing that because the Led near the V0 knob is on while powerup (sometimes ALL the Leds are on but it's ok apparently), when it comes to actual wave screen it seems going but there's an "adjust V0 to set brightness" message on the bottom and the moment i touch ANYTHING it freezes immediately for a pair of seconds and reboots with all the memorized setups at default, this happens like once per 10\20 times i turn it on and i always have the fear it bricks totally, i remember it rebooted also once, while messing too fast with a lot of settings, apart this startup problem
recently I press "default setup" before turning it off and apparently it never did that again... honestly the only setting I usually had on was the silly buzzer for button presses (apart regular settings like 20MHz bw filter, 5V per unit vertical, and maybe a faster timebase), probably it fails some settings checksum
my unit is a DSO5102P with fw dso5kp_func_dso5102p20170714... the previous 3.40.0 161227.0 had the same exact issue (sorry the format of the infos i give) i waited some time before posting this considering it may do this trick again but apparently it did not
some apparently say that it may be a bad CMOS memory but at this point i also think it can be a battery-to-line power transition issue... i don't know :-//
any idea? solutions? similar cases?
It happened with me once with the firmware version 180120.0.
Updated to the last firmware (dso5kp_func_dso5102p20190125.up) a couple of days ago. Now only the time will tell if the problem returns.
anyways... it's not doing that anymore apparently, i press "default setup" every time i turn it off (also a good thing for me)
there is general "thing" with these DSO series, when you change settings (any, so default as well), they write it into memory and save 2-5 seconds later. When you turn off while DSO is saving, you might get fancy issues.
Hello, to All Members! I am Sergiy from Ukraine. Would you be so kind to help me? My Hantek DSO 4102C after the 1st year of working "unexpectedly died". Once, after starting, LCD became black. All buttons are working and LEDs are working too. I checked power supply. All are good: +14,5V; +12V; -8V; +6,4V; +5V; +3,3V. I found control points on the main board (DSO4000C V1.02 2015-03) & checked them. They are: +14,4V; +12V; -7V; +5V; -5V; +3,3V; +2,5V; +1,8V; +1,3V; +1,25V. Only +2,5V was absent at all. One SMD SOT23 part was damaged (burned). It marked as (SANE) & seems like precision voltage reference . I did not find the electrical circuit of Hantek DSO 4102C. I have the picture of a board. Can someone help me?
Received from Hantek for:
MSO5202D
sw 3.2.35 (131029.0)
hw 1010x55558340
sn t1g/012016xxx
new firmware
https://yadi.sk/d/Tm1Esxa9iyWm4w (https://yadi.sk/d/Tm1Esxa9iyWm4w)
@tinhead I think it was you who mentioned you had a pinout file for the FPGA and maybe a memory map of which buttons/controls were where... If this is true and you could share it perhaps we could take a crack at a first third-party UI for this thing. It's not bad hardware but the software is awful.
I've got a Hantek DSO4102C, all is OK, but I can't figure out how to make screenshots. It seems that DSO5102 series have a button named "Save to USB", but 4102C doesn't. Is there a way to capture screen to USB sticks?
Is there a way to capture screen to USB sticks?Not the most intuitive but it is possible: Press "Utility" button then, on page 1/3 of the menu use F3 do select the option "Save Waveform". Now use F1 to choose between "position" and "Screenshot" options. That will set the function of the position knob of CH1. With "Screenshot" selected, just press the knob to capture the screen to the USB stick.
i made complete schematics of DSTxxxxA, DSTXXXXB hw0, hw1007 DSO's (one can use hw1007 as well for hw1005 and partialy for other models). I should have somewhere as well some Memory map etc. description, i have to check in my archive files, have not touched Tekway/Hantek reversing since years anymore. More important is, for which model/series would you like to know more?
download from my 1drv, from firmware, version, model folder the proper/latest file.
There is even a way to run firmware from Feb 2018 on hw1007 platform (like i do on my old hw1007),
but it's bit tricky (one have to copy over ssh some libs first, updates can be done only over lan/uart by copying latest only executable file).
...
Creating 4 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "Bootloader"
0x000000100000-0x000000300000 : "LOGO"
0x000000300000-0x000000700000 : "Kernel"
0x000000700000-0x000008000000 : "ROOTFS"
UBI: attaching mtd3 to ubi0
...
...
Creating 8 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "uboot"
0x000000100000-0x000000180000 : "params"
0x000000180000-0x000000380000 : "logo"
0x000000380000-0x000000400000 : "misc"
0x000000400000-0x000000800000 : "kernel"
0x000000800000-0x000004e00000 : "rootfs"
0x000004e00000-0x000005200000 : "kernel_bk"
0x000005200000-0x000008000000 : "recover"
UBI: attaching mtd5 to ubi0
...
/dev/mtd8: Device or resource busy
Nevertheles mtd0-mtd7 are dumped (in my case, in 4 partitions it should be mtd0-mtd3) as:mtd0-uboot.bin
mtd1-params.bin
mtd2-logo.bin
mtd3-misc.bin
mtd4-kernel.bin
mtd5-rootfs.bin
mtd6-kernel_bk.bin
mtd7-recover.bin
...
OOB will be not dumped, if need it you can edit this tool and remove the -o options from the command line inside.
How to use it (restore):
...
then burn with JTAG the fw_backup.bin file (no OOB blocks inside!) to NAND
...
...it is several times here (yes/no/yes/no/yes/no/...)
the (dumped) data with OOB blocks (which is necessary for restore over JTAG or the method i've published)
...
- Create file 'oob.txt' when you want dumps with OOB or 'omitoob.txt' when don't. Required.
- Create file 'dumpbad.txt' when you want dump including bad PEBs or 'omitbad.txt' when don't. Required.
- Optionally create file 'mtd.txt' with list of MTD partitions which should be dumped (each on separate line).
Available MTDs are listed in 'MTDs-available.txt' ("dev:" column).
Option files can be empty (it is its names what matters).int __fastcall sub_C3E1015C(int a1)
{
int v1; // r4@1
const char *v2; // r0@2
const char *v3; // r0@9
v1 = a1;
printf("\r\n#####\t Boot for SKY2416/TQ2416 Main Menu\t#####\r\n");
if ( v1 == 1 )
{
printf("##### EmbedSky USB download mode #####\r\n\n");
v2 = "[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash\r\n";
LABEL_7:
printf(v2);
goto LABEL_8;
}
if ( v1 == 2 )
printf("##### EmbedSky TFTP download mode #####\r\n\n");
if ( (unsigned int)(v1 - 2) <= 1 )
{
v2 = "[1] Download u-boot.bin to Nand Flash\r\n";
goto LABEL_7;
}
LABEL_8:
printf("[2] Download LOGO (logo.bin) to Nand Flash\r\n");
printf("[3] Erase the MISC partion\r\n");
printf("[4] Download Kernel (kernel.bin) to Nand Flash\r\n");
printf("[5] Download UBIFS image (rootfs.ubi) to Nand Flash\r\n");
printf("[6] Download Kernel_bk (kernel_bk.bin) to Nand Flash\r\n");
printf("[7] Download UBIFS image (recover.ubi) to Nand Flash\r\n");
printf("[8] normal start!\r\n");
printf("[9] recover start!\r\n");
printf("[0] Set the boot parameters\r\n");
printf("[f] Format the Nand Flash\r\n");
printf("[a] Download User Program\r\n");
printf("[c] Choice lcd type.\r\n");
if ( v1 == 1 )
{
v3 = "[n] Enter TFTP download mode menu\r\n";
LABEL_12:
printf(v3);
goto LABEL_13;
}
if ( v1 == 2 )
{
printf("[n] Set TFTP parameters(PC IP,SKY2416/TQ2416 IP,Mask IP...)\r\n");
v3 = "[p] Test network (TQ2416 Ping PC's IP)\r\n";
goto LABEL_12;
}
LABEL_13:
printf("[r] Reboot u-boot\r\n");
if ( v1 != 1 && (unsigned int)(v1 - 2) <= 1 )
printf("[s] Download STEPLDR.nb1 to Nand Flash\r\n");
printf("[t] Test Linux Image (zImage)\r\n");
if ( (unsigned int)(v1 - 2) <= 1 )
printf("[q] Return main Menu \r\n");
return printf("Enter your selection: ");
}
int parameter_menu()
{
printf("\r\n##### Parameter Menu #####\r\n");
printf("[1] Set NFS boot parameter \r\n");
printf("[2] Set Yaffs boot parameter for Standard Linux \r\n");
printf("[3] Set UBIfs boot parameter for Standard Linux \r\n");
printf("[4] Set parameter \r\n");
printf("[5] View the parameters \r\n");
printf("[d] Delete parameter \r\n");
printf("[s] Save the parameters to Nand Flash \r\n");
printf("[q] Return main Menu \r\n");
return printf("Enter your selection: ");
}
int LCD_menu()
{
printf("\r\n##### LCD select Menu #####\r\n");
printf("[1] T43\" screen.\r\n");
printf("[2] A70TN92\" screen.\r\n");
printf("[3] A104\" screen.\r\n");
printf("[4] VGA1024768\" screen.\r\n");
printf("[5] W35\" screen.\r\n");
printf("[6] VGA640480\" screen.\r\n");
printf("[r] Reboot u-boot\r\n");
printf("[q] Return Parameter Menu \r\n");
return printf("Enter your selection: ");
}
I am no expert about that, but my guess is mtd0 to mtd8.
Double check with NAND partitions output in dmesg (shortly after boot).
fw_backup.batHow bring this backup back ?
copy /b rootfs.00.bin+rootfs.01.bin+rootfs.02.bin+rootfs.03.bin+rootfs.04.bin+rootfs.05.bin+rootfs.06.bin+rootfs.07.bin+rootfs.08.bin+rootfs.09.bin+rootfs.10.bin+rootfs.11.bin+rootfs.12.bin+rootfs.13.bin+rootfs.14.bin+rootfs.15.bin+rootfs.16.bin+rootfs.17.bin rootfs.bin
copy /b recover.00.bin+recover.01.bin+recover.02.bin+recover.03.bin+recover.04.bin+recover.05.bin+recover.06.bin+recover.07.bin+recover.08.bin+recover.09.bin+recover.10.bin+recover.11.bin recover.bin
copy /b uboot.bin+params.bin+logo.bin+misc.bin+kernel.bin+rootfs.bin+kernel_bk.bin+recover.bin fwbackup.bin
del rootfs.*.bin
del recover.*.bin
fwbackup.bin
Late to party but picked up a Hantek 5202P cause it was the last one and it was only $269 delivered.Hi everyone. First post but i've been following EEVblog on Youtube and reading this forum for a long time.
The only issue I have with this is the low memory... is it possible to change the flash memory chip on these so it's more like the "B" models?
I'm also going to do a portable battery mod to run off 5V cause these are so light, I can take them in the field... they are so low priced I don't mind them being out there.
I have found UART (it is next to the USB port on the back) and thanks to this descrption:
https://www.eevblog.com/forum/repair/voltcraft-dso-1102d/msg2036896/#msg2036896 (https://www.eevblog.com/forum/repair/voltcraft-dso-1102d/msg2036896/#msg2036896)
i have managed to fix mine oscilloscope.
Hello group:
I recently bought a Hantek oscilloscope model Dso4104b.
My question is, do you know if there is a hack for these model?
Thank you, best regards!
DSO still doesn't work and I have no idea how fix it. Please help!
Hi,
I have just updated my Hantek DSO1062B handheld with the newest firmware from hantek's site 2.01.1 (130129.0) and discovered several bugs (when beep is on and you move cursor, it beeps even if you push and hold the direction buttons, trigger level is erratic - it sets lower trigger level than indicated), and I want to go back to the older firmware.
Does anyone have a firmware older than 2.01.1 (130129.0)? My older was 2.01.1 (12xxxxx.x), and it was OK, more or less, but I don't have it anymore and I cannot revert back to it.
Thanks.
Hey guys, nice to see, that this thread is still active!Nice try, just contact caiyijun@hantek.com he/she will give you factory file to reflash.
After several years, now I'm experiencing some problems with my Hantek DSO-5062B...
The buttons on the front are not working any more.
During boot, shortly an error message box appears:
"Hardware Init Error Code 0x01"
I didn't make any changes onto the software. This problem occured suddenly.
My first try was to open the device and reinsert all cables. Didn't help.
Second try was to reflash my firmware backup using UART/USB, but that didn't help either.
Now I would like to update the firmware, but I'm stuck.
The normal firmware update process works using the onscreen utility, but - as already stated - my buttons are not working.
Any idea how I can flash this firmware (http://www.hantek.com/Product/DSO5000/DSO5062B_Firmware.zip) using UART/USB?
This file seems to be only a part of the whole firmware, since the original firmware has 66MB.
So I'm not sure which files I need to combine to have a complete firmware which I can flash using supervivi.
/e: Update...
I was able to decrypt the firmware using password "dst5000b".
Afterwards I unzipped and copied all files to USB flash drive.
Inserted the drive and manually updated the device by processing all steps listed in do_update.sh manually.
"dso.exe" and "dsod" cannot be started now, though both files are 777 and +x.
Seems the firmware is not compatible O,o
I noticed: Old dso.exe has 4MB and new one has only 1.5MB... strange.
But.. I don't think this is a software problem. This is just my last resort xD
Maybe I try to remove the whole keyboard unit to see if there are obvious problems.
Hm.. just noticing. Maybe it's no problem with the keyboard but a general problem with dso.exe or the scope itself. Because I can't see any waveforms (even with the test signal). The screen seems to be frozen.
No idea what may be the root cause...
I fear I will switch to Rigol DS1054Z...
https://geizhals.de/rigol-ds1054z-digital-oszilloskop-a1218892.html (https://geizhals.de/rigol-ds1054z-digital-oszilloskop-a1218892.html)
/e: I've created a thread on eediscuss.com:
https://www.eediscuss.com/forum.php?mod=viewthread&tid=15326&extra=page%3D1 (https://www.eediscuss.com/forum.php?mod=viewthread&tid=15326&extra=page%3D1)
Nice try, just contact caiyijun@hantek.com he/she will give you factory file to reflash.Thanks for the answer!
Rigol DS1054z is good, I have had one, can make it from 50mhz to 100mhz with some easy command.
good luck!
My DSO1062B after brick >:D >:D >:D
(Attachment Link)
Hello, I have been able to modify the speed of my Hantek DSO5102P to 200Mhz.
Everything works correctly. :-+
Thanks to the information and work that you share.
Thank you very much. :)
Hi Perepandel. I'm also waiting for DSO2С10, bought at a discount, and would like to know what has changed in the new firmware, languages have been added, or is it still only English and Chinese? It is hardly possible to flash my oscilloscope with your firmware with a generator without additional modification. Where did you get the firmware? I asked the seller, but so far there is no specific answer.
Modified the square wave output waveform problem of the signal source and the display problem of the measurement font.
*** Warning - bad CRC or NAND, using default environment
##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; LCD display size is: 800 X 480
Press Space key to Download Mode.!
SD:File System init failed!
Start Linux ...
NAND read: device 0 offset 0x300000, size 0x400000
4194304 bytes read: OK
Boot with zImage
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
(... nothing more at this point)
Hi! I need help. Updated oscilloscope DSO5102B with firmware dso5kb_func_dso5102b20190830.up - only the splash screen is loaded. Before that, dso5kb_func_dso5202b20180226.up was updated normally
Previous system information:
sw 3.33.0 (140902.0)
hw 1010 / 5555830F
Give a link for recovery via the console. If there is, you can throw a dump to the mail.
When these oscilloscopes are turned off during boot the file system can get corrupted and it will hang during initialization. Have you already tried to restore the system?
See this msg in Hantek's forum for reference: https://www.eediscuss.com/forum.php?mod=redirect&goto=findpost&ptid=15009&pid=19633&fromuid=26055 (https://www.eediscuss.com/forum.php?mod=redirect&goto=findpost&ptid=15009&pid=19633&fromuid=26055)
If the restoration process fail, simply send an e-mail to Hantek's support that they will send you the files to recover the partition.
Im missing the right commands to start the machine to copy/extract/update a firmware through a USB stick without using the standard procedure (on screen of scope)...
I finally did it! I got the original Firmware from Hantek. This doesnt contain any code changes (older version) which demands unfindable libraries.
Hello, I'm new on this forum and went through this long thread (days of reading) since I've a problem with my DSO-1062D from Voltcraft. As many others on this forum, I did a firmware update (downloaded the files on http://voltcraftdownload.info/Default.aspx?modelno=DSO-1062D (http://voltcraftdownload.info/Default.aspx?modelno=DSO-1062D)), after that my scope was stuck. Unlikely I haven't done the backup before the firmware update :palm:.
After so much reading and following some suggested recovery procedure on this thread, that's the situation: on teraterm (ttl to usb adapter connected and working well) I have this message:
System Volume Information tekwayup_client
dso5kb_func_dso5062b20180226.up
ls: /mnt/udisk/system*.up: No such file or directory
and the display says "Please insert the USB device with update files which can be obtained from the supplier"
Please, can anyone help me?
Hello, I'm new on this forum and went through this long thread (days of reading) since I've a problem with my DSO-1062D from Voltcraft. As many others on this forum, I did a firmware update (downloaded the files on http://voltcraftdownload.info/Default.aspx?modelno=DSO-1062D (http://voltcraftdownload.info/Default.aspx?modelno=DSO-1062D)), after that my scope was stuck. Unlikely I haven't done the backup before the firmware update :palm:.
After so much reading and following some suggested recovery procedure on this thread, that's the situation: on teraterm (ttl to usb adapter connected and working well) I have this message:
System Volume Information tekwayup_client
dso5kb_func_dso5062b20180226.up
ls: /mnt/udisk/system*.up: No such file or directory
and the display says "Please insert the USB device with update files which can be obtained from the supplier"
Please, can anyone help me?
Hello, I'm continously cehcking for a replay since a month :'( .
Is there anyone who can kindly help me ? My oscilloscope is completely stuck and need it in my own lab.
It might be very appreciated if anyone could share the original firmware files for the DSO-1062D or give me some advice.
Thanks
Anybody has old firmwares for Hantek DSO5202B (or any DSO5000B series)?
I've updated to the latest firmware from hantek.com and it bricked my scope. Seems like the latest update package has some files missing which were introduced in an in-between version. (My error is /dso.exe: error while loading shared libraries: libgstreamer-1.0.so.0: cannot open shared object file: No such file or directory)
Unfortunately Hantek does not keep old versions on their website. If anybody has an older update which happens to have the libgstreamer files I may be able to unbrick my scope with them.
the FPGA logic analyzer board connector pinout, etc.?
ls: /mnt/udisk/system*.up: No such file or directory
My little request/bitte is if someone has a compatible firmware for this old model and how can be that firmware installed, either from the u-Boot menu or from Linux console.
My little request/bitte is if someone has a compatible firmware for this old model and how can be that firmware installed, either from the u-Boot menu or from Linux console.
Your best bet is for someone to do a dump from UBoot and handed it over to you to do a flash.
USB host is connected. Waiting a download.[/tt]
##### Boot for Nand Flash Main Menu #####
[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash
[2] Download Eboot to Nand Flash
[3] Download Linux Kernel to Nand Flash
[5] Download CRAMFS image to Nand Flash
[6] Download YAFFS image to Nand Flash
[7] Download Program (uCOS-II or TQ2440_Test) to SDRAM and Run it
[8] Boot the system
[9] Format the Nand Flash
[0] Set the boot parameters
[a] Download User Program (eg: uCOS-II or TQ2440_Test)
[b] Download LOGO Picture (.bin) to Nand Flash
[l] Set LCD Parameters
[r] Reboot u-boot
[t] Test Linux Image (zImage)
[q] quit from menu
Enter your selection:
EmbedSky> help
? - alias for 'help'
autoscr - run script from memory
base - print or set address offset
bdinfo - print Board Info structure
boot - boot default, i.e., run 'bootcmd'
boot_noos - boot User Program
boot_zImage - boot Linux 's zImage
bootd - boot default, i.e., run 'bootcmd'
bootelf - Boot from an ELF image in memory
bootm - boot application image from memory
bootp - boot image via network using BootP/TFTP protocol
bootvx - Boot vxWorks from an ELF image
chpart - change active partition
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
date - get/set/reset date & time
dcache - enable or disable data cache
eboot - Run Wince Ethernet Bootloader(eboot)
echo - echo args to console
erase - erase FLASH memory
flinfo - print FLASH memory information
fsinfo - print information about filesystems
fsload - load binary file from a filesystem image
go - start application at address 'addr'
help - print online help
icache - enable or disable instruction cache
iminfo - print header information for application image
itest - return true/false on integer compare
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loadx - load binary file over serial line (xmodem mode)
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
ls - list files in a directory (default /)
md - memory display
menu - display a menu, to select the items to do something
mm - memory modify (auto-incrementing)
mtdparts- define flash/nand partitions
mtest - simple RAM test
mw - memory write (fill)
nand - NAND sub-system
nboot - boot from NAND device
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
rarpboot- boot image via network using RARP/TFTP protocol
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
sleep - delay execution for some time
test_zImage - test Linux 's zImage
tftpboot- boot image via network using TFTP protocol
usbslave - get file from host(PC)
version - print monitor version
wince [ram] - Run Wince from flash or ram
##### EmbedSky BIOS for SKY2440/TQ2440 #####
Press Space key to Download Mode !
Booting Linux ...
Copy linux kernel from 0x00200000 to 0x30008000, size = 0x00200000 ... Copy Kernel to SDRAM done,NOW, Booting Linux......
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.30.4 (root@localhost.localdomain) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #17 Sun Oct 9 14:24:29 CST 2011
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
CPU: VIVT data cache, VIVT instruction cache
Machine: TQ2440
ATAG_INITRD is deprecated; please update your bootloader.
Memory policy: ECC disabled, Data cache writeback
CPU S3C2440A (id 0x32440001)
S3C24XX Clocks, (c) 2004 Simtec Electronics
S3C244X: core 400.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz
CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: noinitrd root=/dev/mtdblock2 init=/linuxrc console=ttySAC0
NR_IRQS:85
irq: clearing pending ext status 00000200
irq: clearing subpending status 00000002
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
console [ttySAC0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61316KB available (3116K code, 333K data, 100K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Calibrating delay loop... 199.47 BogoMIPS (lpj=498688)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 296 bytes
NET: Registered protocol family 16
S3C2440: Initialising architecture
S3C2440: IRQ Support
S3C24XX DMA Driver, (c) 2003-2004,2006 Simtec Electronics
DMA channel 0 at c4808000, irq 33
DMA channel 1 at c4808040, irq 34
DMA channel 2 at c4808080, irq 35
DMA channel 3 at c48080c0, irq 36
S3C244X: Clock Support, DVS off
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
cfg80211: Calling CRDA to update world regulatory domain
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
yaffs Sep 30 2011 10:36:32 Installing.
msgmni has been set to 119
alg: No test for stdrng (krng)
io scheduler noop registered (default)
s3c2440-uart.0: tq2440_serial0 at MMIO 0x50000000 (irq = 70) is a S3C2440
s3c2440-uart.1: tq2440_serial1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: tq2440_serial2 at MMIO 0x50008000 (irq = 76) is a S3C2440
loop: module loaded
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
s3c2440-nand s3c2440-nand: Tacls=2, 20ns Twrph0=3 30ns, Twrph1=2 20ns
NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit)
Scanning device for bad blocks
Creating 3 MTD partitions on "NAND 64MiB 3,3V 8-bit":
0x000000000000-0x000000040000 : "EmbedSky_Board_uboot"
0x000000200000-0x000000400000 : "EmbedSky_Board_kernel"
0x000000400000-0x000003ff8000 : "EmbedSky_Board_yaffs2"
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
mice: PS/2 mouse device common for all mice
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c2410-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
Linux video capture interface: v2.00
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: starting watchdog timer
s3c2410-wdt s3c2410-wdt: watchdog active, reset abled, irq enabled
mapped channel 0 to 0
s3c2440-sdi s3c2440-sdi: powered down.
s3c2440-sdi s3c2440-sdi: initialisation done.
Advanced Linux Sound Architecture Driver Version 1.0.18a.
No device for DAI UDA134X
No device for DAI s3c24xx-i2s
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: UDA134X <-> s3c24xx-i2s mapping ok
s3c2440-sdi s3c2440-sdi: powered down.
ALSA device list:
#0: S3C24XX_UDA134X (UDA134X)
TCP cubic registered
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
lib80211: common routines for IEEE802.11 drivers
s3c2410-rtc s3c2410-rtc: hctosys: invalid date/time
yaffs: dev is 32505858 name is "mtdblock2"
yaffs: passed flags ""
yaffs: Attempting MTD mount on 31.2, "mtdblock2"
yaffs_read_super: isCheckpointed 0
VFS: Mounted root (yaffs filesystem) on device 31:2.
Freeing init memory: 100K
/etc/init.d/rcS: line 8: /usr/local/bin/wdg: not found
/etc/init.d/rcS: line 9: /dso/app/show_pic: not found
hwclock: settimeofday: Invalid argument
insmod: can't insert '/dso/drivers/s3c2416-io_bank.ko': No such file or directory
insmod: can't insert '/dso/drivers/s3c2416_adc.ko': No such file or directory
/etc/init.d/rcS: line 20: /dso/app/io_bank: not found
/etc/init.d/rcS: line 21: /dso/app/io_bank: not found
/etc/init.d/rcS: line 22: /dso/app/io_bank: not found
/etc/init.d/rcS: line 23: /dso/app/io_bank: not found
insmod: can't insert '/dso/drivers/fpga_cfg.ko': No such file or directory
insmod: can't insert '/dso/drivers/fpga_ctl.ko': No such file or directory
insmod: can't insert '/dso/drivers/fpga_ctl_la.ko': No such file or directory
insmod: can't insert '/dso/drivers/dm9000.ko': No such file or directory
insmod: can't insert '/dso/drivers/tq2416_backlight.ko': No such file or directory
insmod: can't insert '/dso/drivers/tq2416_beep.ko': No such file or directory
ifconfig: SIOCSIFADDR: No such device
/etc/init.d/rcS: line 35: /dso/app/dsod: not found
/etc/init.d/rcS: line 36: /etc/init.d/nfs.sh: not found
--------------------------------------------------------------------------------
start
--------------------------------------------------------------------------------
/etc/init.d/rcS: line 43: /dso/run.sh: not found
Please press Enter to activate this console.
EmbedSky> mtdparts
device nand0 <nandflash0>, # parts = 7
#: name size offset mask_flags
0: bios 0x00040000 0x00000000 0
1: params 0x00020000 0x00040000 0
2: toc 0x00020000 0x00060000 0
3: eboot 0x00080000 0x00080000 0
4: logo 0x00100000 0x00100000 0
5: kernel 0x00200000 0x00200000 0
6: root 0x03c00000 0x00400000 0
active partition: nand0,0 - (bios) 0x00040000 @ 0x00000000
defaults:
mtdids : nand0=nandflash0
mtdparts: mtdparts=nandflash0:256k@0(bios),128k(params),128k(toc),512k(eboot),1024k(logo),2m(kernel),-(root)
It seems that there are more partitions that it meets the eye or so so says the U-Boot:
It seems that there are more partitions that it meets the eye or so so says the U-Boot:
Nice. It's all compatible with what I had displayed and fills the gaps that we had.
I would suggest you dump all the NAND up to 0x00400000. (4 MBytes)
Use "nand dump" or "nand read" and log all the displayed values in the terminal.
That way you have a reference base to verify if all is correct with those parts. Then the only thing missing will be the root FS.
BTW, a long shot would also be: if you are replacing the full root partition, maybe you can use one from a S/N greater than 15000. I mean the limitation for 15000 is for FW updates using only part of the files. Maybe you can get away with a full partition replacement.
Hello DC1MC,
Ii looks like I found a dump, made with Tinheads special dump software, of an original, not converted, Voltcraft MSO 5062 in my old confuserbox. Is that what you're looking for? It contains three files: boot.bin, kernel.bin and root.bin. Too big to attach it here, about 16MB zipped. Can I upload it somewhere?
regards, Maurits
Hello DC1MC,
Ii looks like I found a dump, made with Tinheads special dump software, of an original, not converted, Voltcraft MSO 5062 in my old confuserbox. Is that what you're looking for? It contains three files: boot.bin, kernel.bin and root.bin. Too big to attach it here, about 16MB zipped. Can I upload it somewhere?
regards, Maurits
Hello again DC1MC,
I really hope you can use these files. I am quit certain that they come from an original Voltcraft MSO-5062B. After all the trouble I had with my modified / converted DSO / MSO this thing was ordered from Conrad. That was a bit of a disappointment. The thing had the same problems as my modified one; so Conrad took it back and refunded me. But I did make a backup of it, you know, for just in case..!.
The MSO firmware has a strange bug, the digital and analog traces on the screen are not always from the same trigger event, that was my main issue to send it back.
Also it doesn't do any protocol decoding so.. my remaining modified Voltcraft ended in a box in storage when a better MSO came on my bench (HAMEG HMO3054).
About restoring the firmware from the dump files:
I found in my old computer a pdf that describes "how to" proceed with a restore. It looks you are aware of this info as well since you mentioned the special dnw.exe program that is needed earlier in this thread. But just for fun I will attach it here.
:palm: If there is no uboot output, you can forget all the rest.
How did you do that?
Relatively simple :'(, the u-boot there seem to not have been the original or at least the one that the documents were referring, now I can either forget all the rest and either see if one of my J-Link clones see the NAND
Better check that again.. there are several empty footprints. The H1007 hardware has a 20 pin, 2x 10 pin, 2mm pitch connector for the processor's JTAG. Attached a picture here.
From the schematic: the 2x10 pin headers are programming ports for the FPGA and the CPLD.
Attached here a detail of the schematic containing the JTAG header and the reset circuit.
Well, from what I see in my notes the NAND isn't talked to directly by the JTAG. I used the H-TAG program with LPT-port JTAG as mentioned earlier. After connecting to the processor a short program was uploaded in RAM and that made it possible to read and write the Flash memory. Also a script file needed to be filled with some parameters about addresses and clock setup. For now I didn't find any more info on my old W7 disk, the script was probably with the program on an even older XP system.
I suggest that you get your connection to the CPU working first and thereafter see what is needed in your setup to connect to the flash memory.
Easiest is to flash the NAND with an assembled file that contains boot, empty area, kernel and root files with OOB info. That will contain in hex 0x0420.0000 bytes, 131072 pages, 4096 blocks.
For reference, the complete schematics attached here. They were published earlier in this thread and on Mikrocontroller.net. And be aware, this is all the great work of Tinhead who reverse engineered the whole thing.
GND- Black
nTRST - Brown
VTRef - Republicans
TDI - Trump
TMS - Yellow
TCK - Greta
TDO - Democrats
nRST - Purple rain
git clone https://git.code.sf.net/p/openocd/code openocd-code
cd openocd-code
sudo apt install libftdi-dev libftdi1-dev libhidapi-dev
#(these were the development libraries that I was missing, if you have others not installed, configure will stop and indicate what is missing)
./boostrap
./configure --enable-jlink --enable-usb-blaster --enable-stlink --enable-doxygen-pdf --enable-usbprog --enable-openjtag --enable-cmsis-dap --enable-cmsis-dap-v2 --enable-usb-blaster-2 --enable-ulink --enable-ftdi
# (these are all the JTAG adapters that I already have or plan to get in the future).
# At the end of the configure script, if you used the same parameters, you should get:
OpenOCD configuration summary
--------------------------------------------------
MPSSE mode of FTDI based devices yes
ST-Link Programmer yes
TI ICDI JTAG Programmer yes (auto)
Keil ULINK JTAG Programmer yes
Altera USB-Blaster II Compatible yes
Bitbang mode of FT232R based devices yes (auto)
Versaloon-Link JTAG Programmer yes (auto)
TI XDS110 Debug Probe yes (auto)
CMSIS-DAP v2 Compliant Debugger yes
OSBDM (JTAG only) Programmer yes (auto)
eStick/opendous JTAG Programmer yes (auto)
Olimex ARM-JTAG-EW Programmer yes (auto)
Raisonance RLink JTAG Programmer yes (auto)
USBProg JTAG Programmer yes
Andes JTAG Programmer yes (auto)
CMSIS-DAP Compliant Debugger yes
Nu-Link Programmer yes (auto)
Cypress KitProg Programmer yes (auto)
Altera USB-Blaster Compatible yes
ASIX Presto Adapter yes (auto)
OpenJTAG Adapter yes
Linux GPIO bitbang through libgpiod no
SEGGER J-Link Programmer yes
Bus Pirate yes (auto)
Use Capstone disassembly framework no
#(The last command will install the new openocd in the /usr/local/bin)
make && sudo make install
openocd -f interface/jlink.cfg -f target/voltcraft_dso-3062c.cfg
Open On-Chip Debugger 0.11.0+dev-00463-ga498a3dea (2021-11-14-12:31)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
Info : J-Link V9 compiled May 7 2021 16:26:12
Info : Hardware version: 9.70
Info : VTarget = 3.279 V
Info : Reduced speed from 16000 kHz to 15000 kHz (maximum)
Info : Reduced speed from 16000 kHz to 15000 kHz (maximum)
Info : clock speed 16000 kHz
Info : JTAG tap: s3c2440.cpu tap/device found: 0x0032409d (mfg: 0x04e (Samsung), part: 0x0324, ver: 0x0)
Info : Embedded ICE version 2
Info : s3c2440.cpu: hardware has 2 breakpoint/watchpoint units
Info : starting gdb server for s3c2440.cpu on 3333
Info : Listening on port 3333 for gdb connections
[b]Info : JTAG tap: s3c2440.cpu tap/device found: 0x0032409d (mfg: 0x04e (Samsung), part: 0x0324, ver: 0x0)[/b]
Warn : NOTE! DCC downloads have not been enabled, defaulting to slow memory writes. Type 'help dcc'.
Warn : NOTE! Severe performance degradation without fast memory access enabled. Type 'help fast'.
target halted in ARM state due to debug-request, current mode: Undefined instruction
cpsr: 0x800000db pc: 0x33d801c4
MMU: disabled, D-Cache: disabled, I-Cache: enabled
[b]#0: NAND 64MiB 3.3V 8-bit (Samsung) pagesize: 512, buswidth: 8,
blocksize: 16384, blocks: 4096
[/b]
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : accepting 'telnet' connection on tcp/4444
(it will stay here waiting to be killed, but I keep it in the foreground to see what is printed and do the telnet in another terminal window)
telnet localhost 4444
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
> nand probe 0
NAND flash device 'NAND 64MiB 3.3V 8-bit (Samsung)' found
s3c2440.cpu arm7_9 fast_memory_access enable
> nand erase 0
s3c2440_read_block_data: reading data: 0x5569077b5730, 0x7fff3c3a61e2, 6
s3c2440_read_block_data: reading data: 0x5569077b5730, 0x7fff3c3a61e2, 6
... a MILLION of these lines will scroll, and scroll, and scroll, for ca. 5 min :palm:
... and then, suddeny:
erased blocks 0 to 4095 on NAND flash device #0 'NAND 64MiB 3.3V 8-bit'
> nand write 0 fw_backup.bin 0 oob_raw
Hello. There is a dso5102p Hunter. When measuring, it hovered. After the reboot, the inscription appears on the screen (Error: the Fpga version does not match the application!!!). It does not respond to pressing the buttons. When exiting to recovery, the buttons don't work either. Please tell me what can be done ? I'm sorry if I don't understand using a translator .
And here we stop for the moment, because after two hours, the operation didn't completed yet |O, when/if will complete I'll update the post, but I have high hopes that will be done, as opposed with the erase operation the write is completely mute :( and doesn't produce any message on the console, but the good thing is that there are also no error messages ^-^.
EDIT: IT WORKS !!!
And here we stop for the moment, because after two hours, the operation didn't completed yet |O, when/if will complete I'll update the post, but I have high hopes that will be done, as opposed with the erase operation the write is completely mute :( and doesn't produce any message on the console, but the good thing is that there are also no error messages ^-^.
EDIT: IT WORKS !!!
It took some time, I must say I waited with fingers crossed during this cliffhanger...!
Well, at least the backup I made in April 2013 served a purpose after all.
Have fun,
Morris6
@DC1MC: Maybe have a look at the schematic. The last page has the option LAN info. Transformer is a H1102NL, looks not too difficult to score one. But once again, the network functionality is restricted as far as I remember. The Linux driver and adaptation was done by Tinhead cs. I'm not sure the adaptation is in the mainstream firmware. It has never been a factory supported option, as far as I know. So no integration in the software further, no webpage or SCPI. Only Telnet on a fixed IP??
The user manual for the thing is still available it seems, from Hantek: http://www.hantek.com/Product/MSO5000D/MSO5000D_Manual.pdf (http://www.hantek.com/Product/MSO5000D/MSO5000D_Manual.pdf)
Have fun with all the bugs this thing has, in my view it was never a completed product.
Morris6
Well, the hack is supposed to work, also for the MSO5062B. It is indeed working for the thing I have here. So maybe start again at page 1 of this thread?
Yes, without any problem, I did so, check my messages in this thread, it is very easy.Thank you for the answer, in which page you wrote this ? I do not see my model (Hantek DSO 8072E) in neither messages
is that hack working also for DSO5102B?
Tried to find the full nand backup for dso5072p everywhere in the forum but no luck.. would be much appreciate if anyone willing to share their full backup of dso5072p.. my dso5072p firmware is corrupted.. and stuck in the boot logo screen. And would try to fix the firmware with all the guideline available in this forum..
*** Warning - bad CRC or NAND, using default environment
##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; LCD display size is: 800 X 480
Press Space key to Download Mode.!
SD:File System init failed!
Start Linux ...
NAND read: device 0 offset 0x300000, size 0x400000
4194304 bytes read: OK
Boot with zImage
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version 3.2.35 (root@zgt) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #10 PREEMPT Thu Feb 9 10:40:49 CST 2017
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: SMDK2416
Memory policy: ECC disabled, Data cache writeback
CPU S3C2416/S3C2450 (id 0x32450003)
S3C24XX Clocks, Copyright 2004 Simtec Electronics
CPU: MPLL on 800.000 MHz, cpu 400.000 MHz, mem 133.333 MHz, pclk 66.666 MHz
CPU: EPLL on 96.000 MHz, usb-bus 48.000 MHz
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: noinitrd ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 mem=64M
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 58996k/58996k available, 6540k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
vmalloc : 0xc4800000 - 0xf6000000 ( 792 MB)
lowmem : 0xc0000000 - 0xc4000000 ( 64 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.text : 0xc0008000 - 0xc03f0000 (4000 kB)
.init : 0xc03f0000 - 0xc0410000 ( 128 kB)
.data : 0xc0410000 - 0xc05a9140 (1637 kB)
.bss : 0xc05a9164 - 0xc05c6e9c ( 120 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:107
irq: clearing subpending status 00000002
Calibrating delay loop... 198.45 BogoMIPS (lpj=496128)
pid_max: default: 4096 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
S3C2416: Initializing architecture
S3C2416: IRQ Support
S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
DMA channel 0 at c4804000, irq 88
DMA channel 1 at c4804100, irq 89
DMA channel 2 at c4804200, irq 90
DMA channel 3 at c4804300, irq 91
DMA channel 4 at c4804400, irq 92
DMA channel 5 at c4804500, irq 93
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
s3c-i2c s3c2410-i2c: slave address 0x10
s3c-i2c s3c2410-i2c: bus frequency set to 9 KHz
s3c-i2c s3c2410-i2c: i2c-0: S3C I2C adapter
Advanced Linux Sound Architecture Driver Version 1.0.24.
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
s3c-adc s3c24xx-adc: attached adc driver
msgmni has been set to 115
io scheduler noop registered (default)
io scheduler cfq registered
s3c-fb s3c-fb: window 0: fb
s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5
s3c-fb s3c-fb: window 1: fb
s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5
s3c2440-uart.0: ttySAC0 at MMIO 0x50000000 (irq = 70) is a S3C2440
console [ttySAC0] enabled
s3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76) is a S3C2440
s3c2440-uart.3: ttySAC3 at MMIO 0x5000c000 (irq = 94) is a S3C2440
loop: module loaded
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
info->cpu_type=3, tacls_max=8
s3c24xx-nand s3c2416-nand: Tacls=3, 22ns Twrph0=7 52ns, Twrph1=3 22ns
s3c24xx-nand s3c2416-nand: System booted from NAND
s3c24xx-nand s3c2416-nand: NAND ECC disabled
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended!
Scanning device for bad blocks
Bad eraseblock 103 at 0x000000ce0000
Bad eraseblock 242 at 0x000001e40000
Creating 8 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "uboot"
0x000000100000-0x000000180000 : "params"
0x000000180000-0x000000380000 : "logo"
0x000000380000-0x000000400000 : "misc"
0x000000400000-0x000000800000 : "kernel"
0x000000800000-0x000004e00000 : "rootfs"
0x000004e00000-0x000005200000 : "kernel_bk"
0x000005200000-0x000008000000 : "recover"
UBI: attaching mtd3 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: max. sequence number: 0
UBI error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd3
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usblp
usbcore: registered new interface driver uas
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
s3c-hsudc s3c-hsudc: bound driver g_serial
samsung-ts s3c2416-ts: driver attached, registering input device
input: S3C24XX TouchScreen as /devices/virtual/input/input0
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
i2c /dev entries driver
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq disabled
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 2: hsmmc-if (24000000 Hz)
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: uda134x-hifi <-> s3c24xx-iis mapping ok
ALSA device list:
#0: S3C24XX_UDA134X
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
s3c-rtc s3c2410-rtc: setting system clock to 2000-01-01 00:00:01 UTC (946684801)
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00 1024 mtdblock0 (driver?)
1f01 512 mtdblock1 (driver?)
1f02 2048 mtdblock2 (driver?)
1f03 512 mtdblock3 (driver?)
1f04 4096 mtdblock4 (driver?)
1f05 71680 mtdblock5 (driver?)
1f06 4096 mtdblock6 (driver?)
1f07 47104 mtdblock7 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Enter your selection: 5
Name(enter to view all paramters):
bootargs=noinitrd ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 mem=64M
bootcmd=nand read.jffs2 c0008000 kernel;bootm c0008000
bootdelay=1
baudrate=115200
ethaddr=10:23:45:67:89:ab
ipaddr=192.168.1.6
serverip=192.168.1.8
gatewayip=192.168.1.2
netmask=255.255.255.0
stdin=serial
stdout=serial
stderr=serial
ethact=dm9000
mtdids=nand0=nandflash0
mtdparts=mtdparts=nandflash0:512k@0(bios),512k(params),2048K(logo),4m(kernel),-(root)
partition=nand0,0
mtddevnum=0
mtddevname=bios
Environment size: 504/16380 bytes
as far as I can see, root=ubi0:rootfs , that is correct or wrong ?For the backup of the 8 elements, you need a key that contains in the root :Thanks a lot!
- dso5kp_backuptool2.up
- dumpbad.txt (empty file)
- oob.txt (empty file)
The saved files will be in the "dump" directory.
The operation takes a few minutes.
And now 132 MB are saved!Here are the files. Take whoever needs it.
Thank you for answer.
I did exactly as you said.
After your post, I tried with other USB sticks, the result is the same.
Firmware failed.
Thank you both for your replies. @ DC1MC I'm going to try this afternoon to rename the file to be updated, but I think it won't help because when it starts running, the update bar appears with the green line and in a very short time it gives the error.