Sorry, I should have said memory depth. Before I applied the latest patch I was following along with a YouTube video showing how the thickness of the trace can be seen to change going from 4k I to 8m, but I didn't see the same difference and put it down to filtering smoothing out the trace. Than Immediately after the latest patch the trace became noticeably thicker unless I used HR mode or a lower memory depth.
This made me wonder, as the reason they sent me the patch was I complained of laggy inputs and random lockups, if there was a change to the filtering to lighten the process load, with the added benefit of a more accurate display trace.
@OLderDan: I'm not sure. Maybe DavidAlfa understands your question (is it even a question? I'm not a native speaker).
As a general tip for the DSO2000, I would say: Don't look for a fly in the ointment, just enjoy what a great tool you got for $150 and explore everything you can do with it.
People often pay too much for this tool and are then rightly disappointed.
I agree with you entirely and I am happy to embrace all this bargain oscilloscope has to offer, including it's limitations. Through playing around, I have found great settings for trigger that have stabilized displays of unsynchronised waveforms, and through specifying the hex bit, triggering in useful parts of my uart streams etc.
Learning how to interpret the trace has taught me the real world differences of the acquisition settings and opened my circuit exploration far beyond what I was able to achieve before I bought this scope.
Hello, does anyone know how I can make the UART and I2C decoder show the letters instead of doing it by code? For example, I would like it to show an "A" instead of a "41" or at least show them together, my firmware is 3202 and Software 1.0.2.0.0 (221028.00), thanks
Hi, Thank You, it works for me
Please correct me if I'm wrong but the UART mod called "Patcher" makes i2C decoding stop working? That function no longer decodes me. The message "Please adjust the Triger" or "please adjust the base time" always appears, before it gave me the impression that it was half working.
Hello all you good folk.
Ok, I am slightly confused - so my doctor says ;-) ....
Question is basically this ?.
I have on order a jelly bean DSO2D10. I want - of course, to convert to the 2D15. I note the thread has taken many side channels, but could someone please advise the method to use for the change ?
Is it simply the firmware (currently) - dso3kb_20230327.upk - on a usb stick with the original first post - do_other_update - file and nothing else ?
My very best regards to all you great modders and hackers.
Joe
David, thank you for the reply and apologies if I am not up to date here. Normally, the first post is edited to keep up with the methods. I do not see a FAQ. I may well be being thick and if so I am sorry.
Regards, Joe. and thanks for the great work,
AH ! just saw FAQ in your suffix - doh - apologies.
Should be there, but as I'm not the OP I can't!
This thread is only for hacking, please keep it on topic.
For usage, doubts, updates, bugs... use the main thread:
New Hantek DSO2X1X models.
Spreading the information between different threads will only cause confusion, this update has already been
mentioned.
Thanks!