-
#775 Reply
Posted by
DavidAlfa
on 09 Oct, 2021 22:26
-
Yes, 320x versions are only for models coming with that version from factory.
Read the FAQ.
-
#776 Reply
Posted by
xuraax
on 10 Oct, 2021 04:30
-
I am confused. So what is the difference between 3000, 3101 and 3102?
-
#777 Reply
Posted by
DavidAlfa
on 10 Oct, 2021 08:54
-
I think they're updates, like 3200 and 3202
-
#778 Reply
Posted by
xuraax
on 11 Oct, 2021 04:58
-
OK. Are the 31xx upgrades to the 3000 or does it not matter?
For sure changing the 3000 to 3200 causes calibration to fail at the very least.
-
#779 Reply
Posted by
LZ4TU
on 12 Oct, 2021 20:06
-
-
#780 Reply
Posted by
ars_ha3hz
on 15 Oct, 2021 10:22
-
LZ4TU,
Interestingly, they also link to this blog, so read on.
Gyula HA3HZ
-
#781 Reply
Posted by
Algoma
on 15 Oct, 2021 16:13
-
in Follow-up to the SoC (AllWinner F1C200s) in these scopes.. Looks like a few potential alternate dev boards to test things with, and perhaps find better Documentation:
Another F1C200s Development board, (Other than the Lichee Pi Nano from Seeed Studio that I've found stocked at Digikey,)
MongoPi-R3 Development Board
https://www.dfrobot.com/product-2274.htmlIncludes an well documented Wiki of related tools and procedures that may be useful for poking deeper into these F1C200s.
https://wiki.dfrobot.com/MangoPi_R3_SKU_DFR0780
-
-
-
#783 Reply
Posted by
ptluis
on 03 Nov, 2021 12:26
-
hello, can anyone tell me what's the "waveform refresh rate" (wfms/s) of these oscilloscopes?
Thank you
-
#784 Reply
Posted by
Algoma
on 03 Nov, 2021 14:57
-
In the Manual, Page 62:
"Acquisition Rate, typical: Up to 2000 waveform per second per channel (Normal acquisition mode, no measurement)"
Its limited by the CPU's interface with the FPGA, pretty typical of an entry level scope. Only issue it might miss triggering on short duration, intermittent, transient signals if you're troubleshooting for some rare, specific event. Certainly if you're troubleshooting for such issues, you'll want a higher end scope with more wfms/s.. I feel 2K has been plenty for my basic use needs, certainly well faster than what it can display on screen.
-
#785 Reply
Posted by
ptluis
on 03 Nov, 2021 19:15
-
In the Manual, Page 62:
"Acquisition Rate, typical: Up to 2000 waveform per second per channel (Normal acquisition mode, no measurement)"
The manual I downloaded doesn't have page 62, that's why I couldn't find it. Downloaded the complete manual now from hantek. Thank you for the info
... it might miss triggering on short duration, intermittent, transient signals if you're troubleshooting for some rare, specific event. Certainly if you're troubleshooting for such issues, you'll want a higher end scope with more wfms/s..
That's exactly what I need it for to capture short duration, intermittent, transient signals, some rare, specific event and three-phase signals. Maybe a Siglent, Rigol or Micsig, need to decide.
-
#786 Reply
Posted by
jemarro12
on 09 Nov, 2021 13:57
-
New update uploaded today. Any changelog??
-
#787 Reply
Posted by
Algoma
on 09 Nov, 2021 16:25
-
Hantek has been poked a few times about that offset some are encountering where the trace is always sitting a few random mV above Zero, even after running calibration. Hopefully they've addressed that in this software update... hopefully.
-
#788 Reply
Posted by
DavidAlfa
on 09 Nov, 2021 20:17
-
Interesting...Will test it. It includes the USB fix, but also updates the DSO software.
FW version is unchanged.
-
#789 Reply
Posted by
Algoma
on 10 Nov, 2021 01:22
-
Seems my DC coupled offset has improved / resolved with the update. The traces now visually settle towards zero during initial warmup, after a good calibration. Though GND couple a channel and it now displays a significant negative offset (-712mV). Not that I really needed an accurate GND coupling anyway.
-
#790 Reply
Posted by
blackbile
on 15 Nov, 2021 09:43
-
What does it mean: "Though GND couple a channel and it now displays a significant negative offset (-712mV). Not that I really needed an accurate GND coupling anyway."
-
#791 Reply
Posted by
Algoma
on 15 Nov, 2021 15:44
-
my apologies, I should have written that better for proper translation.
There are three coupling modes supported by each input of the Oscilloscope, AC, DC and GND
The third input mode, GND, will generally allow you to verify your vertical trace alignment, without having to disconnect your probe clip from the signal you're measuring. The scope uses an internal relay to disconnect your probe, and reconnect that input to what is supposed to be zero volts. this can be used for reference and alignment with other signals when needed.
In my case, its incorrectly showing me a negative voltage when connected to it's internal Ground reference. Its just as easy for me to simply touch the probe to any other ground reference point.
-
#792 Reply
Posted by
blackbile
on 15 Nov, 2021 16:15
-
Ok, I see now.
-
#793 Reply
Posted by
Pley
on 17 Nov, 2021 20:49
-
Teria como atualizar o firmware do DSO2C15 para utilizar a função WAVE GEN usando o firmware do DSO2D15? Se tiver, como posso obter este firmware?
-
#794 Reply
Posted by
blackbile
on 18 Nov, 2021 08:59
-
Yes you can - I did it on my DSO2C10 -, BUT it depends on that the opamp, D/A converter and the relay has been soldered on your board or not!
-
#795 Reply
Posted by
blackbile
on 18 Nov, 2021 18:49
-
I didn't flash the latest fw package (20210726 I got it with this version) and now I checked the GND coupling what you were talking about: yes, I have appr. -200mV too not 0V !!!
-
#796 Reply
Posted by
ars_ha3hz
on 23 Nov, 2021 11:21
-
You can post a private message in this forum group, but you cannot reply to it.
You will receive a warning if you do respond. Private messaging is free at groups.io.
-
#797 Reply
Posted by
vistorik
on 04 Dec, 2021 12:44
-
It was found that on number of motherboards, after device reboot after using platform-toos-3102/3202, the dds_calibration.dat calibration file is restored from PT24C02. Data to this file is not available in PT24C02 on all motherboards. Below are the PT24C02 dumps for three different motherboards - b000, 3200 and 3202. Calibration file data are present only in two dumps - 3200 and 3202, this is a string of characters in the penultimate 16 bytes of the dump, marked with a red frame. There is no such string in the b000 dump and the calibration file could not be restored from such a dump. In dump 3202, apart from dump 3200, the motherboard number is also present. It remains unclear how two 8-byte sequences of the calibration file (marked with a red frame) are obtained from the marked string in PT24C02 damp, and whether it is possible to get the calibrations file from the PT24C02 content without using platform-tools. Many thanks to David for his dso3kb_Eeprom_backup.upk.
-
#798 Reply
Posted by
vistorik
on 04 Dec, 2021 19:36
-
For FW 3202 the order /lib/firmware now contains 3 files:
psram_board_test.fs.bin
SCOPE_TOP_V3002.bin
SCOPE_TOP_V3202.bin
The file SCOPE_TOP_V3202.bin is the same as the file psram_board_test.fs.bin and is the same as file psram_board_test.fs.bin from old FW 3202; the file SCOPE_TOP_V3002.bin is the same as the file psram_board_test.fs.bin from FW 3102.
This FW could be updated using dso3kb_FW3002_3202.upk.
-
#799 Reply
Posted by
DavidAlfa
on 04 Dec, 2021 23:11
-
I know. What's the use of that file? There're already upks to set any fw version.