EEVblog® Electronics Community Forum
Products => Test Equipment => Topic started by: tunk on November 28, 2022, 04:46:44 pm
-
Short youtube video with three new multimeter+oscilloscopes.
Guessing these are the specs:
- ZT-701S: 1ch, 24MSps, 3MHz, 64Kpts, 2.8" screen, 6000 count multimeter
- ZT-702S: 1ch, 48MSps, 10Mhz, 64Kpts, 2.8" screen, 9999 count multimeter
- ZT-703S: 2ch, 250MSps, 50MHz, 512Kpts, 3.5" screen, 25000 count multimeter
https://youtu.be/YNgsjPeb9O4
Edit: I guess these eventually will be rebranded as Anengs etc.
-
The ZT-702S is starting to show up at aliexpress from around $65.
It's also rebranded as Richmeters and Bside.
So now we're waiting for the introduction and pricing of the ZT-703S.
-
The ZT-702S is now on their web-page:
https://zotektools.com/products/zt-702s/ (https://zotektools.com/products/zt-702s/)
-
Already have this meter, but I see no reference to the two-channel version. Is this a marketing trick, first you do some mouth-watering, wait for some time so that people bite the bullet and the next higher version appears.
-
There is one crucial measurement missing: duty cycle.
-
The ZT-702S is now showing up as the Aneng AOS02:
https://aneng.aliexpress.com/store/919484/search?SearchText=aos02
-
The manual for the ZT-702S is now out:
https://www.dropbox.com/s/03cvx7b5zk33wr4/ZT-702S%20EN.pdf?dl=0 (https://www.dropbox.com/s/03cvx7b5zk33wr4/ZT-702S%20EN.pdf?dl=0)
-
I'm not quite sure about those "cheap" scopemeters.
I think that with a DSO1511G (https://de.aliexpress.com/item/1005001969702720.html) and Zoyi ZT219 (https://de.aliexpress.com/item/1005005544216192.html) , for example, I have better equipment for almost the same price.
I can use both functions at the same time and if one breaks, the other still works
What do you think?
-
There is one crucial measurement missing: duty cycle.
Is there any workaround to measuring the duty cycle?
-
Didn't find it :o
-
Didn't find it :o
I'm looking at the FNIRSI DSO-TC3 as an alternative (for lower frequency PWM work).
-
Didn't find it :o
I'm looking at the FNIRSI DSO-TC3 as an alternative (for lower frequency PWM work).
I do not recommend these.
See also: https://www.eevblog.com/forum/testgear/new-(toy)-dsolcr-meter-fnirsi-tc2-(june-2022)/msg4881002/#msg4881002 (https://www.eevblog.com/forum/testgear/new-(toy)-dsolcr-meter-fnirsi-tc2-(june-2022)/msg4881002/#msg4881002)
-
I'm looking at the FNIRSI DSO-TC3 as an alternative (for lower frequency PWM work).
The Zeeweii DSO154pro has much better specs and a lower price
(but no component tester). If you don't need component tester,
Fnirsi DSO152.
-
The Zeeweii DSO154pro has much better specs and a lower price
Yep. I've got a Zeeweii and it's really good.
-
Indeed.
-
The Zeeweii DSO154pro has much better specs and a lower price
(but no component tester). If you don't need component tester,
Fnirsi DSO152.
Yes, but I still wouldn't recommend these two.
The DSO152 is not up to date with 200kHz bandwidth and the DSO154pro doesn't even have a proper case.
I don't think these are good deals.
For me, the DSO1511G (https://aliexpress.com/item/1005001969702720.html) has the best price/performance ratio in the lowest price range.
You can get pretty far with it as an Arduino hobbyist.
If you would like two channels, there is the DSO2512G (https://aliexpress.com/item/1005003085753955.html) or the Fnirsi DPOX180H (https://www.banggood.com/de/FNIRSI-DPOX180H-Handheld-Phosphor-Digital-Oscilloscope-180MHz-3DB-50000wfms-or-s-Dual-Channel-20Mhz-Signal-Generator-ZOOM-XY-FFT-p-1988900.html) which also looks tempting, but I don't own one and for me the information about it is still contradictory.
-
The scope needs to display Duty Cycle or it's useless to me.
-
The scope needs to display Duty Cycle or it's useless to me.
Afaik all these Zeeweii and Fnirsi mentioned can do that.
-
The scope needs to display Duty Cycle or it's useless to me.
Afaik all these Zeeweii and Fnirsi mentioned can do that.
I didn't see any other photos of the Zeeweii with the Duty Cycle displayed. Thanks for posting.
I realize that the product listings which show only a subset of the device features can mislead me into thinking they don't support features not shown.
-
I didn't see any other photos of the Zeeweii with the Duty Cycle displayed. Thanks for posting.
I realize that the product listings which show only a subset of the device features can mislead me into thinking they don't support features not shown.
All of the mentioned Zeeweii can show the following 14 measurements:
Frequency,
Peak-to-Peak,
Duty cycle,
Amplitude,
RMS,
Average,
Period,
+Pulse width,
-Pulse width,
Max,
Min,
Top,
Base,
-Duty cycle
-
I didn't see any other photos of the Zeeweii with the Duty Cycle displayed. Thanks for posting.
I realize that the product listings which show only a subset of the device features can mislead me into thinking they don't support features not shown.
All of the mentioned Zeeweii can show the following 14 measurements:
Frequency,
Peak-to-Peak,
Duty cycle,
Amplitude,
RMS,
Average,
Period,
+Pulse width,
-Pulse width,
Max,
Min,
Top,
Base,
-Duty cycle
The Zeeweii covers all the bases. Does it have a feature for Auto Scale like the Fnirsi has?
-
The Zeeweii covers all the bases. Does it have a feature for Auto Scale like the Fnirsi has?
Yes, they all have "Auto" and my DSO2512G is very fast with it.
You can download the manual for the version you are interested in here:
http://www.zeeweii.com/support.html (http://www.zeeweii.com/support.html)
-
Yes it has an auto-button. And yes, you can display the duty cycle. See below for a square wave with +1,6% duty.
-
The Zeeweii covers all the bases. Does it have a feature for Auto Scale like the Fnirsi has?
Yes.
Yes it has an auto-button. And yes, you can display the duty cycle. See below for a square wave with +1,6% duty.
Try holding down the Auto button, it goes into auto-scale mode and continuously adapts the display to the signal.
-
It looks like there is new firmware available: https://zotektools.com/firmware-update/
"Optimized some functions and interfaces."
I havent tried it yet
-
The update went smoothly. can't exactly tell what is different. The multimeter interface feels a bit snappier. Alas, no duty cycle measurement.
It looks like there is new firmware available: https://zotektools.com/firmware-update/
"Optimized some functions and interfaces."
I havent tried it yet
-
In multimeter mode, is there a way to reset the Min, Max and AVG values (displayed at the bottom, above the function key soft labels), so that they all start at the next reading and then change from there (without changing ranges or to a different function)?
-
Is there any word on the ZT-703 yet? I can't really find any mentioning of it outside of this thread.
While searching around on AliExpress I found this:
Owon hds242/hds272/hds242s/hds272s
https://www.aliexpress.com/item/1005003913549473.html (https://www.aliexpress.com/item/1005003913549473.html)
Is this a rebranding of the ZT-70xS like the ANENG ones or something entirely different? If the latter, how does it compare and would you rather pick this up or wait for the 03 model?
-
The Owon is completely different. You can see just by looking. . Search for the huge thread on it here. The Owon is significantly better specs wise.
-
Is there any word on the ZT-703 yet? I can't really find any mentioning of it outside of this thread.
Apparently not
https://zotektools.com/oscilloscope-multimeter/
Is this a rebranding of the ZT-70xS like the ANENG ones or something entirely different? If the latter, how does it compare and would you rather pick this up or wait for the 03 model?
Depends on the (still unknown) price and what you need.
As a cheap handheld oscilloscope, I would prefer a ZEEWEII DSO2512G or a FNIRSI DPOX180H and buy a DMM separately
-
I had no idea the cheap handheld scope market had so much development since I last looked. The ZT-70xS is appealing because it costs like half of the other two, but that FNIRSI DPOX180H looks almost too good to be true. I don't care about the DMM functionality, not having it is actually preferred. I guess it mostly comes down to the software, which one will have the least UI annoyances and bugs...
-
I had no idea the cheap handheld scope market had so much development since I last looked. The ZT-70xS is appealing because it costs like half of the other two, but that FNIRSI DPOX180H looks almost too good to be true. I don't care about the DMM functionality, not having it is actually preferred. I guess it mostly comes down to the software, which one will have the least UI annoyances and bugs...
If you want it cheaper, then even the DSO1511G (https://de.aliexpress.com/item/1005004793136023.html) is better than the ZT-702S.
It has however like the ZT-702S only one channel.
-
While searching around on AliExpress I found this:
Owon hds242/hds272/hds242s/hds272s
https://www.aliexpress.com/item/1005003913549473.html (https://www.aliexpress.com/item/1005003913549473.html)
Is this a rebranding of the ZT-70xS like the ANENG ones or something entirely different? If the latter, how does it compare and would you rather pick this up or wait for the 03 model?
No, not even close to the same. The Owon is far and away the better portable scope, as one would expect at 4-5x the cost. I have both the Owon HDS2022S (200Mhz) and the 702S (as well as a DSO-TC3). Don't get me wrong, I like the 702S for what it is (I have a thing for cheap meters, especially Zoyi/Aneng) and wouldn't hesitate to use it for simple things especially if my Owon wasn't charged up or otherwise not available. It's lighter, more compact, and easier to grab quickly than the Owon, and if I were in a hostile environment I'd feel better about risking a $60 device than a $250 one. So they both have their place.
-
Ali prices for me shipped:
Zoyi ZT-702S - 60.62EUR
OWON HDS2102S - 120.52EUR (or 20EUR more for 70Mhz)
FNIRIS Dpox180h - 120.17EUR
I think both the Zoyi & Owon are reasonably priced relatively, but the Dpox180h seems like far better value considering how much more features it has. It's probably what I'd tend towards, but I'm highly skeptical that it actually reaches its specs and that even half of the software features actually work well enough to be usable. There's no proper review yet AFAIK.
-
The OWON is far better ...
-
The OWON is far better ...
Than the FNIRIS Dpox180h?
-
Yes
-
OWON HDS2102S - 120.52EUR (or 20EUR more for 70Mhz)
No, you slipped with the prices.
The HDS2102S is better, but it costs a lot more: 236,03 € at eleshop.
https://eleshop.de/owon-hds2102s-tragbares-oszilloskop.html
The Owon HDS242 is no better than the Fnirsi or Zeeweii, but still costs more.
This is the best for little money
https://de.aliexpress.com/item/1005004793136023.html
-
OWON HDS2102S - 120.52EUR (or 20EUR more for 70Mhz)
No, you slipped with the prices.
The HDS2102S is better, but it costs a lot more: 236,03 € at eleshop.
https://eleshop.de/owon-hds2102s-tragbares-oszilloskop.html
The Owon HDS242 is no better than the Fnirsi or Zeeweii, but still costs more.
This is the best for little money
https://de.aliexpress.com/item/1005004793136023.html
Your Ali link doesn't work for me / product not available, and I confused the 100Mhz and 40Mhz versions of that scope, sorry.
So it seems the FNIRIS Dpox180h is the best bang for the buck? I just don't trust it actually performs.
-
Your Ali link doesn't work for me / product not available, and I confused the 100Mhz and 40Mhz versions of that scope, sorry.
Not sure what you mean. There aren't any different versions of the DSO1511G
Does this link work?
https://www.aliexpress.com/item/1005004793136023.html (https://www.aliexpress.com/item/1005004793136023.html)
Or here ist the ZEEWEII Factory Store
https://www.aliexpress.com/store/1102327126 (https://www.aliexpress.com/store/1102327126)
-
No, just "Sorry, the page you requested can not be found:(" and a blurb about not being available for your shipping destination. You're in Switzerland? Since that's not EU/EEA, I guess that's it?
I mixed up the OWON HDS2102S and the OWON HDS242.
-
No, just "Sorry, the page you requested can not be found:(" and a blurb about not being available for your shipping destination. You're in Switzerland? Since that's not EU/EEA, I guess that's it?
Strange. ???
Yes, I am in Switzerland.
Then go to Aliexpress and Search for "ZEEWEII Factory Store"
For information also http://www.zeeweii.com/ (http://www.zeeweii.com/)
-
I guess they just don't want to ship to the EU. At those prices I think maybe the DSO2512g would be a better deal than the DSO1511G. I wonder where the 2ch higher BW 703S will land in terms of price.
-
I guess they just don't want to ship to the EU. At those prices I think maybe the DSO2512g would be a better deal than the DSO1511G. I wonder where the 2ch higher BW 703S will land in terms of price.
I see, but it only has to do with Germany.
If you select France as the destination country, for example, there is no problem.
No idea what it is about.
But you can just search in Aliexpress for "DSO1511G" or "DSO2512G", there are more dealers.
It was also available at Kaufland.
https://www.kaufland.de/product/419287165/ (https://www.kaufland.de/product/419287165/)
-
Sure, I don't need help buying any of those scopes, there are plenty of sellers that ship here, choosing is tricky part. Would be so great to have a YT video comparing like the 5 top candidates. The main issue is again do these features and specs actually work as advertised. If I compare a Rigol 1054Z to a Siglent 1104X-E I can be reasonably sure they actually do what they advertise, with the budget portable scope the real question is what can they actually do.
-
Would be so great to have a YT video comparing like the 5 top candidates.
I'm not sure if that would really help.
There are so many details to compare from different angles.
Better specs aren't all that matters.
Maybe you first think about what is important to you and how much you want to pay, then you can ask more specific questions to the owners of such devices.
But for sure all the mentioned are better oscilloscopes than the ZT-702S.
-
I see, but it only has to do with Germany.
If you select France as the destination country, for example, there is no problem.
No idea what it is about.
This is related to new waste management policy in Germany. They introduced some laws for imported goods, which some Chinese stores don't comply with.
-
This is related to new waste management policy in Germany. They introduced some laws for imported goods, which some Chinese stores don't comply with.
I always thought that was an EU wide thing when they introduced it last year. If you got a German IP these products don't even show up in search and if you got to the shop they show as having 0 products. Guess since it's been a year this will never be fixed and a huge chunk of products just won't be shipped here anymore.
Edit: So I double checked and this is EU wide and France has even implemented this law before Germany. But I guess this is handled by a different agency in each country and they're differences like in some countries you don't have to deal with this until you reach a certain threshold of sales. I'm sure the German authorities worked tirelessly to make this process as painful as possible.
-
I just got a Zoyi ZT-702S and so far it seems to work ok for low frequency applications (automotive, audio). Its build quality is well above average and both the menu and the button operation are quite logical and intuitive - this compared to the other non-brand toy oscilloscopes I have seen in the past. There is a saturation issue in case a high voltage (when compared to the V/div setting) is applied, since the waveform hints to overflow in the ADC codes. I am also missing either an anti-alias filter or a better tuned opamp feedback loop, since sinewaves above 1MHz are showing quite wobbly for me (let alone triangular or square). Perhaps those were corrected with newer firmware (?).
The Zeeweii indeed has better specifications on paper for the same price, but IMO the dual button press interface to execute mundane actions is a deal breaker for me. This was common to other toy oscilloscopes that I saw in the past. I don't know its overall build quality, but the other very similarly looking oscilloscopes I saw in the past were very subpar. Maybe this one is different.
-
The Zeeweii indeed has better specifications on paper for the same price, but IMO the dual button press interface to execute mundane actions is a deal breaker for me. This was common to other toy oscilloscopes that I saw in the past. I don't know its overall build quality, but the other very similarly looking oscilloscopes I saw in the past were very subpar. Maybe this one is different.
The DSO2512G is OK for the price and very easy to use. Everything is logical and you quickly get used to it. I have never been annoyed by this device.
But of course, if you want to pay more, you get more (hopefully).
-
If someone in the UK needs a ZT-702s, this is for sale at £34 (plus £5.15 shipping):
https://www.ebay.com/itm/166254908126 (https://www.ebay.com/itm/166254908126)
-
Will the firmware updates from the ZOYI site fit a device branded ANENG AOS02?
-
in their youtube guide someone commented that it is supported(aos02 in specifically mentioned).
But it seems the update adds more bugs than solves them so I wouldn't update myself.
-
But it seems the update adds more bugs than solves them so I wouldn't update myself.
The latest update (v. 51) added a visual description of lead placement in A/mA modes at EVERY switch to those modes (also between them).
-
I've found that my ZT-702S with firmware version 1.03.51 sometimes does not give the correct value for Vmin and Vmax, which then also affects the VPP value. This happens in oscilloscope mode with DC coupling and seems to be when the displayed waveform swings over a large vertical portion of the screen.
The problem is that the Vmin value shows far more negative than it actually is. Vmax can change to a strange value as well and can vary from reading to reading. I haven't seen the problem occur with AC coupling.
Here are some examples, (with the probe in 10X mode):
This is the scope's calibration output at 1.0V/div. Displayed values appear to be correct.
[attachimg=1]
This is the same calibration output at 500mV/div (and the 0V baseline moved down). Vmin has changed to -2.17V and Vmax to 0.99V.
[attachimg=2]
This is the calibration output at 500mV/div with AC coupling. Displayed values appear to be correct.
[attachimg=3]
This is a 5V 25.1kHz square wave at 2.0V/div. Displayed values appear to be correct.
[attachimg=4]
This is the same 5V 25.1kHz square wave at 1.0V/div. Vmin has changed to -4.87V, with the corresponding wrong VPP.
[attachimg=5]
Can anyone confirm this problem? Is it fixed in firmare version 1.03.55 (installed on recent units but not yet available for download)?
-
MLXXXp, please show one beam on the display without a signal if you set it to the center of the screen at the 500mV/siv DC limit. And then check the position of the beam at the limits of 1.0V/div and 2.0V/div. Will it change its position when switching ranges?
-
And then check the position of the beam at the limits of 1.0V/div and 2.0V/div. Will it change its position when switching ranges?
@indman,
No, there isn't a significant change in beam position when switching voltage ranges. The attached screen captures are with the probe shorted to its ground lead and the beam position and trigger set to the centre of the screen.
-
In multimeter mode, is there a way to reset the Min, Max and AVG values (displayed at the bottom, above the function key soft labels), so that they all start at the next reading and then change from there (without changing ranges or to a different function)?
Switch to scope mode then back. This works on Version 1.03.55 at least.
-
This works on Version 1.03.55 at least.
Is 1.03.55 available as a firmware update? The classic link https://zotektools.com/firmware-update/ (https://zotektools.com/firmware-update/) seems to still have v51. At least, the downloaded filename ends in "51(3)" and it's showing as 1.03.51 on my unit.
-
Can anyone confirm this problem? Is it fixed in firmare version 1.03.55 (installed on recent units but not yet available for download)?
Yes, I can confirm this issue on my unit with the same firmware as yours.
I can't upload images at this time, but if you raise the GND level of your waveform to 0V (center line), the problem goes away. As soon as you lower the GND level to something slightly below that, the Vpp wraps to -4.x V.
Later today I can upload some images that illustrate this, but give it a try.
-
but if you raise the GND level of your waveform to 0V (center line), the problem goes away.
The problem with this is, for a vertical range where the problem occurs, raising the GND level to where Vmin reads correctly causes the high part of the waveform to be off the top of the screen. This causes Vmax to become incorrect (and thus VPP to still be incorrect).
-
but if you raise the GND level of your waveform to 0V (center line), the problem goes away.
The problem with this is, for a vertical range where the problem occurs, raising the GND level to where Vmin reads correctly causes the high part of the waveform to be off the top of the screen. This causes Vmax to become incorrect (and thus VPP to still be incorrect).
Yes, of course this will happen. I just reported the boundary conditions that triggered this bug.
-
New Firmware available 1.03.58 !!
https://zotektools.com/firmware-update/ (https://zotektools.com/firmware-update/)
Had the pleasure to play with the ZT-702S from Zotek directly,
As most noteced the firmware on the website was old 1.03.51 and newer devices came with 1.03.55
After my review i told my Zotek contact and they just updated to the latest on the website today
1.03.58 is ready for download.
The review
https://www.youtube.com/watch?v=W89FpQM1T14 (https://www.youtube.com/watch?v=W89FpQM1T14)
Have fun :-+
-
1.03.58 is ready for download.
The 1.03.58 firmware still has the "Vmin/Vmax/VPP values with DC coupling" problem I reported recenty (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5092959/#msg5092959).
This firmware has replaced waveform period (Prd) with duty cycle (duty) in the more measurements (MoreMeas) display. Similar to the above problem, incorrect duty cycle values are given in DC coupling mode.
@tonyalbus Perhaps you could inform your Zotek contact about these problems?
This is the probe calibration output with a 10X probe
[attachimg=1]
-
My experience with 1.03.58 firmware so far:
It reset my unit to Chinese language and lost other remembered things like the last scope voltage scale and cursor position, backlight brightness, etc. DMM calibration was *not* lost.
It now remembers when I shut it down in DMM mode, and upon restart it returns to that mode. I think it messed up one time and booted into scope mode, but that could have been my quick fingers on the MODE button. I'll keep an eye out for any recurrences.
-
I just purchased a "ZT-703S" https://www.aliexpress.us/item/3256806076552722.html?spm=a2g0o.order_list.order_list_main.30.15d918026EtgUJ&gatewayAdapt=glo2usa (https://www.aliexpress.us/item/3256806076552722.html?spm=a2g0o.order_list.order_list_main.30.15d918026EtgUJ&gatewayAdapt=glo2usa)
What are the chances that this device is legitimate? Has anyone purchased this as well? It bothers me that the name of the store sounds like "snake oil".
-
I just purchased a "ZT-703S" https://www.aliexpress.us/item/3256806076552722.html?spm=a2g0o.order_list.order_list_main.30.15d918026EtgUJ&gatewayAdapt=glo2usa (https://www.aliexpress.us/item/3256806076552722.html?spm=a2g0o.order_list.order_list_main.30.15d918026EtgUJ&gatewayAdapt=glo2usa)
What are the chances that this device is legitimate? Has anyone purchased this as well? It bothers me that the name of the store sounds like "snake oil".
The ZT-703S with those specs (dual channel, 50Mhz) has been announced for some time, since the ZT-702S became known and popular, but it's not yet even showing on Zoyi's website.
https://zotektools.com/oscilloscope-multimeter/ (https://zotektools.com/oscilloscope-multimeter/)
Let us know if you get it. I have a ZT-702S and would probably upgrade it. Even though I have the far more serious and expensive HDS2202S, I really liked the little Zoyi for what it is.
-
I've got my 702s from the snakol store. Delivery went smooth an the product arrived in good order.
-
There's a reference to the ZT-703S at the top of Zoyi's News page
(images dated 1 December 2023):
https://zotektools.com/news-with-zoyi/
https://cloud-fc.mmldigital.com/631/01172128/33b330ef6505142dd16851a0023aa5d-1024x1024.jpg
-
I just purchased a "ZT-703S" https://www.aliexpress.us/item/3256806076552722.html?spm=a2g0o.order_list.order_list_main.30.15d918026EtgUJ&gatewayAdapt=glo2usa (https://www.aliexpress.us/item/3256806076552722.html?spm=a2g0o.order_list.order_list_main.30.15d918026EtgUJ&gatewayAdapt=glo2usa)
What are the chances that this device is legitimate? Has anyone purchased this as well? It bothers me that the name of the store sounds like "snake oil".
I'm curious, did your ZT-703S ship? I bought one over the weekend from the same link and it hasn't shipped yet. I'm hoping they just batch their shipments, but I'm also hoping that it actually gets here before the 22nd when I'm leaving for a few weeks - I'd really like to throw it in my bag and take it with me!
-
They just canceled my order.
-
They just canceled my order.
I ordered the ZT703S from the “SNAKOL” store on 11/29/2023. As of today it hasn’t been shipped, so I canceled this order. I received information that the money will be credit back to my CC in 6 - 20 business days, however when I check “Refund and return” I see “Refund_returns_list_not_order”, when I try to message this vendor I’m getting stupid robo response. It’s not possible to get a human response.
It was my 1st in my life order from a chine site, and obvious it was a mistake. Who’s the “Alieexpress”, I’m assuming it’s another chines snake oil…
BTW, did you receive you money back?
-
AliExpress themselves are a reputable vendor. I've cancelled several orders with them over the years and always got my refund. They are like Amazon, they handle the payments and refunds, not the seller, so it's unlikely you'll be scammed if it's never been shipped.
For years I've ordered constantly from the big three Chinese marketplaces, AliExpress, Banggood, and Temu. Thousands of dollars over dozens if not hundreds of orders.
-
It was my 1st in my life order from a chine site, and obvious it was a mistake. Who’s the “Alieexpress”, I’m assuming it’s another chines snake oil…
You're really unlucky. I'm sorry for you.
I've placed 40 orders on Aliexpress this year and haven't had a single problem.
Not a single delivery was late, not a single piece was defective, not a single wire was even a millimeter too short and not a single piece was missing from the bag.
I really can't say anything bad at all about Aliexpress or Banggood.
-
@Veteran68, @Aldo22
Thanks for your response. I hope the company will credit me back.
I ordered the ZT703S just for fun, to play with it, new gadget for ~$87 its not a fortune. But I don’t like when somebody is trying to make fool of another people.
About Amazon, when I order from Amazon and I don’t like it they will notify me in ~10 minutes after disputed transaction. If I need to speak with human they will call me.
-
I really can't say anything bad at all about Aliexpress or Banggood.
I don't think I've ordered from Bangood in years (if ever? I don't even remember anymore)
I have a few gripes with Aliexpress, but I've never lost money on a transaction. You do get a refund if things go sideways, but that's not the only place for issues.
My gripes:
Their misleading search where sellers can get an item to show up for an unreasonably low price by having different "color" options that are actually completely different products at completely different price points, but the search results show the cheapest price for the most expensive item of the available choices, and it makes the search results entirely useless and a nightmare to find a good price.
You search for: diamond ring
Search results: diamond ring - $0.05 (where the diamond ring is of the color "we send you a printed picture of a diamond ring on a piece of paper - $0.05" - the actual diamond ring is $1000, but the search doesn't show that (entirely contrived example, but you get the picture). Once one seller starts doing that, they all do, and now you can't find an actual price in the search at all - you have to dig through 15 or 20 different sellers and open up each product page and choose the right "color" option to find the actual item, and then compare the prices by hand in multiple tabs.
Unpredictable / Slow / expensive shipping, and useless search results related to that:
Some items ship free and show up in 5 days
Some items ship free and show up in 5 months
Some items shipping cost is more than the item, but it shows up in 5 days
Some items shipping cost is more than the item, and it shows up in 5 months
There's absolutely no consistency, and no real way to tell beforehand which way it's going to go. It's a total crapshoot. At some point, if it said "e-packet" shipping, it actually meant "e-packet shipping" which is pretty fast, but now everyone just lists all the shipping as "e-packet" and then sends it by slow boat anyway.
The search itself:
Search AliExpress right now for ZT703S - there's only one listing for an actual ZT703S (whether that listing is legit or not I guess is up for debate), but it will return hundreds of results that aren't that item at all. Search Amazon, and it returns 2 listings, for expensive pocket knives. Search ebay for ZT703S, and it returns "0 results". AliExpress search is like Facebook Marketplace search - useless, but it will fill the results with "pages of something" just to waste your time / keep you on the site.
Pricing (more recently):
Most sellers on AliExpress have jacked their prices way up to the point where a lot of stuff I look at now is cheaper on Amazon than it is on AliExpress, and I know I'll get it in a day or 2 from Amazon (along with a less painful return process), and combined with the other issues (especially the misleading pricing in the search), why even bother with AliExpress anymore. Amazon (or 3rd party sellers on Amazon) used to not carry a lot of stuff you could find on AliExpress, but now almost everything that's on AliExpress can also be found on Amazon now. And a lot of it can be found on EBay too. Ebay is usually cheaper for the same item (because you're not paying the Bezos tax, you're paying ebay tax which is a little less).
AliExpress USED to be really good and really cheap, even if the shipping times were all over the map. Now it's just Chinese Amazon with worse search, worse prices, and worse shipping!
That said, I still do order some stuff from AliExpress - when I really don't care about how long it will take to get to me, and I care more about saving $0.50 overall. But it's a lot less than it used to be.
-
About Amazon, when I order from Amazon and I don’t like it they will notify me in ~10 minutes after disputed transaction. If I need to speak with human they will call me.
Amazon isn't the best at returns either. I've had issues where I've had to call them multiple times to actually get money back, even after the item showed "received and processed" at the return depot for over a week. And these were not small / cheap items - it was a microscope that I returned because AmScope themselves had a better sale than buying the same thing through Amazon, and Amazon wouldn't match the price (we're talking >$200 difference in price for the exact same item). Funny how when you call, someone can click a button to return your money instantly, but if you don't call or forget about it, they just kind of forget about it too...
I've also had issues with QTY packs coming as only one item, and having to talk to someone multiple times to get it straightened out.
Amazon is far from perfect, but generally they are better than AliExpress. I still have the least issues overall with ebay (oddly - probably not everyone's experience)
-
Amazon isn't the best at returns either. I've had issues where I've had to call them...
Amazon is far from perfect, but generally they are better than AliExpress. I still have the least issues overall with ebay (oddly - probably not everyone's experience)
Of course, but the funds are immediately back in the account. Who cares about rest? :)
-
AliExpress USED to be really good and really cheap, even if the shipping times were all over the map. Now it's just Chinese Amazon with worse search, worse prices, and worse shipping!
It may depend on where you live, but for Switzerland, Amazon is usually of no interest.
For example, my last purchase on Aliexpress was a Hantek DSO2C10 for CHF 123.- ($130), delivery included (11 days).
On Amazon.de the scope costs CHF 226.- (~$260).
While the DSO2C10 is really amazing for hobbyists for $130, I wouldn't pay $260 for it.
That's not just a slightly higher price, that's a different price range. I would look for a Rigol in that range.
A DSO2512G is CHF140 on Amazon instead of CHF78 on Aliexpress (Regular price, sometimes < CHF70).
As I said, maybe it's better elsewhere, but for us Amazon is no competition (Plus they don't accept Paypal ;) ).
Oops, are we off-topic? ;)
-
From what i understand from Zotek, that they are now slowly sending the ZT-703S to reviewers who don't mind testing and updating it a few times.
"The initial batch could still have some imperfections and will have ongoing updates"
So i am suprized it is allready on AliExpress, while it is not yet on their own website.
Hope i receive mine soon, and ofcource will update here.
-
https://www.aliexpress.com/item/1005006262867474.html (https://www.aliexpress.com/item/1005006262867474.html)
Is it real?
-
https://www.aliexpress.com/item/1005006262867474.html (https://www.aliexpress.com/item/1005006262867474.html)
Is it real?
That's the same seller that's been discussed above, and their orders are being cancelled. I have a feeling they're not available for sale yet and this shady seller is just trying to get pre-orders in to secure early sales.
-
They actually responded to my chat with them yesterday (not with their stupid automated bot). They said it's in "Quality Inspection" and will be shipped soon.
[attachimg=1]
It sounds legit - it is a new product - they probably jumped the gun a bit listing it a little early. We'll see what "soon" means I guess.
-
I've got the same reply.
-
The seller promised to send the device last week. He didn't. Applied for a refund. Within 2 minutes a message from aliexpress that the money will be in my account within 2 days.
-
If you don't mind waiting for shipping:
Looks like they have reduced the price with about $6, now $71.09 and $74.69 (plus shipping).
https://www.aliexpress.com/item/1005006262867474.html (https://www.aliexpress.com/item/1005006262867474.html)
-
Today it's even lower, $66.09 and $69.69 (plus shipping).
And the ZT-702S is $47.63 plus shipping:
https://www.aliexpress.com/item/1005005496160073.html (https://www.aliexpress.com/item/1005005496160073.html)
-
It's currently showing $74.25 (with one probe) and $78.01 (with 2 probes) for me. Maybe it went on sale briefly and then they put it back to almost the regular price - when I ordered it it was $81 with 2 probes - not even worth arguing with them over $3
Still hasn't shipped (of course)
-
It's currently showing $74.25 (with one probe) and $78.01 (with 2 probes) for me. Maybe it went on sale briefly and then they put it back to almost the regular price - when I ordered it it was $81 with 2 probes - not even worth arguing with them over $3
Still hasn't shipped (of course)
There's a sale right now, $3 off per $30, up to $9. So $6 off the $78.01 price once added to your cart == $72.01. Still not convinced this is a reputable seller, though. Normally there are several sellers with these, including the official Zoyi store.
(https://www.morrisonline.us/images/Screenshot_2023.12.14_21h24m0s.png)
-
I got a 702 from Snakol on Aliexpress a while back. No problems with them.
-
My ZT703S order is marked shipped now! I guess they finally got them to ship.
-
My ZT703S order is marked shipped now! I guess they finally got them to ship.
Mine as well. I was considering cancelling yesterday when I saw it was in transit.
-
It's now on Zoyi's web-page:
https://zoyitools.com/product/zt-703s/
On their web shop it's $99 (which is a bit on the high side
when compared to the handheld Owons and Hanteks).
-
It's now on Zoyi's web-page:
https://zoyitools.com/product/zt-703s/
On their web shop it's $99 (which is a bit on the high side
when compared to the handheld Owons and Hanteks).
I have the Owon HDS2202S and the Zoyi ZT-702S -- I don't consider them in the same class at all, and each have their place. I don't even consider the Hantek a contender based on the poor reviews I've seen for the price paid.
I do agree that if you can swing the $150 (40Mhz) to $180 (70Mhz) for the lower Owon HDS models they are a much better instrument. But if you have a hard budget limit of <$100, I think you'd be hard pressed to find a better overall portable scope+DMM for the price than the 703S, even at MSRP. Especially at the $72 I paid for it, for a 50Mhz scope, it is a very good deal -- that's only a few dollars more than what the 702S still sells far. With the 703S now at 5x the bandwidth, 6x the sample rate, plus a second channel for only $10-$15 more -- assuming they didn't break anything -- it's a great deal, actually.
-
The ZT-703S indeed seems to be much better bargain than the ZT-702S. I wonder how they solved the mechanical trouble with the oscilloscope input. I have enough problems with the recessed BNC jack on my ZT-702S, as it is hard to twist any BNC connector to its jack to lock it. I can only wonder how it is with two channels.
-
I bought both a HDS2202S and the ZT703S, in case the ZT703S wasn't going to ship for a while - it will be interesting to compare them. Reading the forum threads on both of them (or the ZT702S), they both have some firmware issues / easy improvements that could be made.
I consider both of them "use it where you don't want to take the >$1000 Keysight scope - up a ladder, in the rain, when traveling, in the back of old greasy CNC machine control cabinets, etc etc.
There's just a lot of situations where you need more than a DMM, but don't want to risk a fancy expensive scope.
-
I bought both a HDS2202S and the ZT703S, in case the ZT703S wasn't going to ship for a while - it will be interesting to compare them. Reading the forum threads on both of them (or the ZT702S), they both have some firmware issues / easy improvements that could be made.
I consider both of them "use it where you don't want to take the >$1000 Keysight scope - up a ladder, in the rain, when traveling, in the back of old greasy CNC machine control cabinets, etc etc.
There's just a lot of situations where you need more than a DMM, but don't want to risk a fancy expensive scope.
As I pointed out above, the Owon HDS is in a differently class altogether from the Zoyi. It's like comparing Siglent to Hantek or FNIRSI. But that should also be evident from the price difference of 3-4x. Further to your point, I'll take the Zoyi where I wouldn't want to risk the Owon.
However for $70-$80, the Zoyi certainly performs well enough and definitely earns its place near the top of the "cheap" portable scope list. I expect were I to ever kill the 702S/703S, I'd be buying a replacement.
-
A couple of teardown pictures of the ZT-703S:
https://www-dt830-com.translate.goog/thread-8175-1-1.html?_x_tr_sch=http&_x_tr_sl=zh-CN&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=sc
-
OK, I had a little trouble getting the pictures from the forum board tunk referred to, but eventually was able to get them. I was curious how close or how different between models ZT-703S and the older ZT-702S.
There is blog site from a Kerry D Wong that goes into details what he could find on the ZT-702S
Source: http://www.kerrywong.com/2023/05/26/teardown-pictures-of-a-zotek-zoyi-zt-702s-handheld-oscilloscope/ (http://www.kerrywong.com/2023/05/26/teardown-pictures-of-a-zotek-zoyi-zt-702s-handheld-oscilloscope/)
I merge the picks to see a better side-by-side comparison what has changed.
[attach=1]
[attach=2]
-
Mine arrived a bit earlier than expected, attached are some higher resolution teardown photos.
Few things I noticed:
- It doesn't appear to be possible to disable the awful beep when switching functions
- Large amount of trigger jitter on non-repetitive waveforms, such as a calibration time-marker signal of 2us/div or higher.
- No mean voltage measurement function
- The bayonet of multiple BNC connectors I tried wasn't able to be rotated all the way into the locked position
(https://i.imgur.com/PzxXSaIl.jpg)
(https://i.imgur.com/91W4iLTl.jpg)
(https://i.imgur.com/p7eKPJ9l.jpg)
(https://i.imgur.com/nC5LFNjl.jpg)
(https://i.imgur.com/1y36U5Ul.jpg)
(https://i.imgur.com/3nrXAsel.jpg)
(https://i.imgur.com/hXXPQBtl.jpg)
(https://i.imgur.com/2ByZdldl.jpg)
(https://i.imgur.com/bMwqtYbl.jpg)
(https://i.imgur.com/Gxj2dSTl.jpg)
(https://i.imgur.com/dVVKjEGl.jpg)
High resolution images here: https://imgur.com/a/c2Oi1iY
-
Mine arrived a bit earlier than expected, attached are some higher resolution teardown photos.
Thanks for sharing.
- It doesn't appear to be possible to disable the awful beep when switching functions
Common in Chinese meters. I dislike this as well.
- Large amount of trigger jitter on non-repetitive waveforms, such as a calibration time-marker signal of 2us/div or higher.
I wonder if the 702 does that as well.
- No mean voltage measurement function
This was also present in the 702 as well.
- The bayonet of multiple BNC connectors I tried wasn't able to be rotated all the way into the locked position
Too bad. Do the provided probes can be locked?
-
- The bayonet of multiple BNC connectors I tried wasn't able to be rotated all the way into the locked position
Too bad. Do the provided probes can be locked?
The supplied probes do sort of jam into place and do seem somewhat secure, however it doesn't appear that these lock properly either. It might be worth looking into longer BNC connectors to replace the supplied ones.
Here are some images of the unit displaying a 50 MHz sine wave. The unit is set to high-speed acquisition mode in order to maximize the sample rate. The signal appears quite unstable.
(https://i.imgur.com/FD5Ne3wh.jpg)
When decreasing the frequency slightly, in this case 46 MHz, the signal clears up quite a bit.
(https://i.imgur.com/20lqW1wh.jpg)
-
A similar scenario, considering the paper bandwidth. My ZT702S (10MHz on paper) shows a very stable waveform at 1MHz, usable at 5MHz but at 10 it is quite jagged.
-
Mine arrived a bit earlier than expected, attached are some higher resolution teardown photos.
Nice humble brag that shipping in and to the Netherlands is far superior than shipping in the US (color me NOT shocked!). Mine is still somewhere between here and Shenzen :-DMM
-
Mine arrived a bit earlier than expected, attached are some higher resolution teardown photos.
Mine is still somewhere between here and Shenzen :-DMM
If you ordered from the same AliExpress Snakol store as the rest of us, you should have tracking that shows you where it is. Mine was in-state yesterday and should arrive by tomorrow.
-
Got mine today, firmware version 1.0.9, so many bugs!
The multimeter functions well, is very accurate and seems bug free other than it switches back to Volts DC when you change from scope mode to DMM. (The ZT-702 remembers the DMM settings.) It does not have a temperature measurement like the ZT-702 does but it have one interesting new feature -- you can set it to output a 115.2kb UART ASCII description of the currently displayed reading on the scope probe calibration lug!
The scope works well to 25Mhz at least, 50 Mhz is defiantly pushing it. Cursors are now available and work ok but reset when you leave scope mode and come back in. X-Y mode works but updates are painfully slow. You can choose to show up to 4 measurements per channel from the list (VPP, Vmax, Vmin, RMS, Duty, Prd, Freq and Fcnt -- seems to be trigger counts).
The signal generator is just awful: No amplitude setting, hard to change frequency, incredibly noisy, very limited range. It outputs on the probe calibration lug but turns off the scope function when running. You can output some of the signal generator options on the calibration lug when the scope is running using another menu option (Output Setting). I have no idea why these are not combined. On the positive side, the function generator is under a menu setting called "More Apps" along with and imgView app (let's you see screen shots you've saved). Maybe there's more stuff to come.
Some of the bugs:
- Sometimes it gets into modes that limit the range of the time base, using the "default" setting option fixes this.
- I see crazy results for Fcnt and sometimes for Freq on measurements.
- Power on always goes into scope mode.
- Attempting to set the signal generator below 4Hz crashes the instrument!
I sure hope that they have new firmware in the works!
-
If you ordered from the same AliExpress Snakol store as the rest of us, you should have tracking that shows you where it is. Mine was in-state yesterday and should arrive by tomorrow.
I did order from the Snakol store (it's the only store on Ali that seems to have it so far). I also ordered 3 other items on AliExpress the day prior that all arrived today, but the ZT703s still shows "Arrived at Linehaul office" on the same day as "departed from departure country / region" yesterday, so I'm not even sure it's on the boat yet... it must've slept in and missed the boat everyone else's meter got on.
-
Mine arrived yesterday as expected.
As noted by others, even though a recent FW update for the 702S remembers the last used mode (DMM or Scope), the 703S once again defaults to scope mode at powerup. Not a huge deal for me as this will be seldom used as a DMM considering how many others I have, but odd that they regressed the functionality in this newer model.
-
I expect new firmware will be released at some point. If you read back a couple of pages, someone that is getting sent a "review unit" said they indicated they knew there were firmware bugs and will release new versions at some point.
I really wish they'd just make the firmware open source - all the bugs would be fixed, and every last ounce of additional features possible would be added before the 100th unit got delivered!
I bet the firmware is similar to, but not exactly the same as the ZT702S - the one guy looking after it hasn't yet ported the diffs from the 702 firmware to the 703 firmware and recompiled it...
-
For reference/comparison,
Ordered ZT-703S w/2 probes from "SNAKOL Official Store" on AliExpress on 25 Dec 2023, arrived in USA on 5 Jan 2024.
-
I too ordered the 703S from snakol, it shipped fast and is already in the air. I expect to get it faster than the ali tracking info says.
-
My ZT703S finally arrived today.
One bug I found is with the frequency measurement when in "High" Run Mode is not accurate. I set the signal generator to 5khz sine (the max it goes to??). With measurements turned on on CH1, in "Normal" Run Mode, it shows the measured frequency at 5kHz, but in "High" run mode, it shows the frequency as 8.75kHz
Measuring with the cursors gives incorrect readings as well. In "High" mode, one cycle of the waveform measures as 114.3uS (~8.748kHz), and in normal mode one cycle of the signal measures as 200uS (5kHz).
I don't have another oscilloscope here to verify the output of the frequency generator in High vs Normal mode - maybe the bug is with the frequency generator in high mode, not the oscilloscope, and the scope is actually measuring correctly?? I could easily check if I was at home, but don't exactly have a lot of test equipment available while on vacation! I'm sure someone else could check this and see where the bug lies.
Also for a scope that's supposed to go to 50Mhz, the minimum timebase is 100us/div?? In the photos above from ddrl46, they have it in 10ns/div - mine says it's at a limit at 100us/div?? Edited: Oh, I see now, if the function generator is on anything other than probe calibrator output (square wave 1kHz), the minimum timebase is limited to 100us/div, but if you put the function generator to square wave 1kHz, then the timebase can go down to 10ns/div - RTFM!!
Another bug is triggering doesn't work properly at 100ns/div. Trigger on the probe compensation signal, start at 10ns/div and go up...
10ns, 25ns, 50ns all trigger correctly, 100ns doesn't (trigger is somewhere off the left edge of the screen), 250ns, 500ns, 1us, etc etc all trigger correctly again.
Definitely some bugs in the first firmware!
On the multimeter side, the continuity beeper is latching and quite quick, and the resistance autoranging seems ok-ish (about 2S to range from OL to low ohms shorting the probes together). Both issues that I think people were complaining about on the ZT702.
Sort of a minor thing, but I skimmed the manual too, and was quite surprised that the English is actually pretty good - it was definitely edited by someone that's a native English speaker, or at least a very good English speaker. There's only one or 2 instances of some odd phrasing - not even bad enough to call them Chinglish.
They definitely put some effort into this thing!
-
I’ve ordered the ZT-703S with 2 probes from "SNAKOL Official Store" on AliExpress on 27 Dec 2023, arrived to Spain on 5 Jan 2024.
-
My ZT703S finally arrived today.
One bug I found is with the frequency measurement when in "High" Run Mode is not accurate. I set the signal generator to 5khz sine (the max it goes to??). With measurements turned on on CH1, in "Normal" Run Mode, it shows the measured frequency at 5kHz, but in "High" run mode, it shows the frequency as 8.75kHz
Measuring with the cursors gives incorrect readings as well. In "High" mode, one cycle of the waveform measures as 114.3uS (~8.748kHz), and in normal mode one cycle of the signal measures as 200uS (5kHz).
I don't have another oscilloscope here to verify the output of the frequency generator in High vs Normal mode - maybe the bug is with the frequency generator in high mode, not the oscilloscope, and the scope is actually measuring correctly?? I could easily check if I was at home, but don't exactly have a lot of test equipment available while on vacation! I'm sure someone else could check this and see where the bug lies.
It might not be a bug (or a feature ;) ) it might just be the way the ZT-703S Oscilloscope works. The manual on page 19 says the following...
=====
* Run Mode:
The oscilloscope is equipped with two operating modes: Normal mode and High-Speed mode. Enter the forth menu, press F3 to toggle between them. Depending on the measurement signal, if the input signal is less than 30MHz, it is recommended to use Normal mode. If the measurement signal frequency is higher than 30MHz, it is advisable to switch to High-Speed mode.
Normal Mode: Maximum sampling rate 200MSa/s, Maximum measurement bandwidth 30MHz; Lower power consumption, more power-efficient.
High-Speed Mode; Maximum sampling rate 280MSa/s, Maximum measurement bandwidth 50MHz, Higher power consumption.
=====
The manual kind of hints not to use High Speed Mode under 30MHz.
Maybe they could reword it better to say something like
...it is recommended to use Normal mode to get more accurate results...
I assume there is some overlap like High-Speed Mode is accurate at say above 20MHz or 10MHz, but you tested at more than an order of magnitude lower at 8.75kHz so [I assume] it is just outside the range of accuracy for High-Speed Mode.
Note: This is my first scope, I cannot test this hypothesis (maybe others). I'm not a scope aficionado or expert...
-
In high speed mode, the cursors problem is caused because the scope changes the virtual, horizontal graticule without modifying the cursor positions. I think that changing the graticule spacing is the bug here, why are they doing that?
High speed mode does indeed improve the waveform display accuracy at higher frequencies at the expense of a minor increase in current draw from the battery, but I found that it only adds about 20ma
-
I have a feeling the bug is that in High mode, the firmware doesn't compensate for the higher sampling rate of the ADC, and then everything is wrong - the graticle, the cursors, and the measurements.
It's definitely not a "feature" - regardless of operating mode, a scope should never show the wrong frequency when displaying measurements.
As I said though, without another scope, I can't tell if the bug is in the function generator, or in the scope part, but it sounds like it's in the scope part. If I was at home, I'd be able to verify that in 30 seconds, both by measuring the output of the function generator, as well as feeding in a signal from an external function generator and verifying the measurement on another scope.
-
FYI: The English Manual PDF for the ZT-703S Zoyi/Zotek Oscilloscope&DMM can be found here:
https://zotektools.com/products/zoyi-zt-703s/ (https://zotektools.com/products/zoyi-zt-703s/)
Then scroll down and click "Download User Manual"
OR direct link from Dropbox here:
https://www.dropbox.com/scl/fi/qm8vlwby6lqrolhy36m8r/ZT-703S-EN.pdf?rlkey=iaqfg4i1jcn2gumccvhv6msx7&dl=0 (https://www.dropbox.com/scl/fi/qm8vlwby6lqrolhy36m8r/ZT-703S-EN.pdf?rlkey=iaqfg4i1jcn2gumccvhv6msx7&dl=0)
Whenever I get a new product I like to snag a PDF copy of the manual... Easier to find and easier to search...
-
I have a feeling the bug is that in High mode, the firmware doesn't compensate for the higher sampling rate of the ADC, and then everything is wrong - the graticle, the cursors, and the measurements.
It's definitely not a "feature" - regardless of operating mode, a scope should never show the wrong frequency when displaying measurements.
As I said though, without another scope, I can't tell if the bug is in the function generator, or in the scope part, but it sounds like it's in the scope part. If I was at home, I'd be able to verify that in 30 seconds, both by measuring the output of the function generator, as well as feeding in a signal from an external function generator and verifying the measurement on another scope.
I received my Zoyi 703s yesterday. And I checked the high-speed mode of the Zoyi with the generator of my Hantek2D72. At 5kHz and 2.5 volts. Zoyi displays the same thing in both modes: 5.2kHz. This leads to the conclusion that the fault lies in the Zoyi's generator. But it took me a lot longer than 30 seconds, I had to search and unpack my Hantek first ;) Maybe someone can check this additionally?
-
Ahakman: Another bug is triggering doesn't work properly at 100ns/div. Trigger on the probe compensation signal, start at 10ns/div and go up...
10ns, 25ns, 50ns all trigger correctly, 100ns doesn't (trigger is somewhere off the left edge of the screen), 250ns, 500ns, 1us, etc etc all trigger correctly again.
I tried that too, but didn't notice any problems at 100ns. Also tried with 1kHz probe compensation. But what I noticed is that when the autotrigger is triggered with DC input, the amplitude of the square wave signal goes above the screen. Below the center line the signal is displayed correctly. If you set the input to AC, it triggers correctly.
-
The ZT-702S oscilloscope does not show the end of charging on the display. The battery icon does not change. How to determine that charging has ended?
-
The ZT-702S oscilloscope does not show the end of charging on the display. The battery icon does not change. How to determine that charging has ended?
Buy a 703S ? :-DD
Crappy firmware.
My 703S should arrive tomorrow, so I get to try it then.
-
Buy a 703S ?
With even more crooked firmware? :-DD
-
Ahakman: Another bug is triggering doesn't work properly at 100ns/div. Trigger on the probe compensation signal, start at 10ns/div and go up...
10ns, 25ns, 50ns all trigger correctly, 100ns doesn't (trigger is somewhere off the left edge of the screen), 250ns, 500ns, 1us, etc etc all trigger correctly again.
I tried that too, but didn't notice any problems at 100ns. Also tried with 1kHz probe compensation. But what I noticed is that when the autotrigger is triggered with DC input, the amplitude of the square wave signal goes above the screen. Below the center line the signal is displayed correctly. If you set the input to AC, it triggers correctly.
I wasn't in auto trigger - I had manually set a trigger level, and then stepped through the timebase settings, and it doesn't trigger correctly at 100ns/div at all (or at least the trigger point is way off the screen somewhere).
I just took screenshots at a bunch of time bases, and interestingly, the screenshot at 100ns/div is also corrupted in a weird way.
You can see at all other timebases, the edge is in the middle of the display where it should be, but at 100ns/div, the edge is somewhere off the screen entirely.
There's definitely a bug there.
[attachimg=1]
-
The ZT-702S oscilloscope does not show the end of charging on the display. The battery icon does not change. How to determine that charging has ended?
On the ZT-703S, the icon flashes between the charging icon and the full battery icon when it's full.
Maybe that indicates it's intermittently charging the battery even though it's full - probably not good for the battery.
I wouldn't leave it plugged in for long times when the battery is full if it's continually trying to charge it "a little more".
-
I also have the 100ns error in manual trigger mode. Thanks Ahakman, great series of pictures, I get the same results. In high speed mode the following result occurs, a flickering correct result....
-
Related to the charging part.
I got my 703S
Icon in screen is like already said, when on charger the icon toggles between charge icon and batt level icon.
However, in the manual it says the lighted power button will go dark when it's done charging. My batt icon shows the full 4 bars ("full") but power button is still red. Will let it charge for a bit to see what happens.
Given today's cots IC's for batt charging & management, I suspect the batt can't overcharge, but perhaps the logic implemented for icon and light is not 100%.
Update: the longer I leave it on charger the more the power buttons starts to flicker. Initially a very faint flicker, but 30min later the flicker is more obvious. My guess, bad implentation of a comparator, or the full-charge threshold is set wrong.
Is there a hidden menu to see current firmware version?
-
I wouldn't say it's "hidden", other than that horizontally scrolling the menu wasn't obvious to me initially either until I glanced at the manual
Press "menu", press "right" 3 times, version is the right most entry.
If you press F4 (the soft key under version), I get
Serial Num:
xxxxxxxx
Boot:
V1.0.13
APP:
V1.0.9
-
My 703 says:
boot v1.0.14
app v1.1.0
My 703 boots to either Meter volts, or Scope. Whichever side was used last is what it boots to.
It does have the 100ns issue like all the others.
And if I change freq outside of 1kHz the unit won't allow me to even go down to 100ns.
-
Did Zoyi advertise the 703 as also a 50Mhz generator.
In the more-apps area there;s the Gen app, but seems I can only get around 325kHz.
There's definitely some odd bugs in my 703. After making some manual changes on scope settings, like signal type from the side port, I simply go back and hit AUTO. With the std 1kHz sq. wave the AUTO appears to step through some time divisions and then settles on one. But sometimes the whole scope part seems to crash / lockup, I then have to power off - on.
-
With the ZT-703S it seems like one of the differences between the older 702S model is that the 702S has a thermocoupler function. In the newer 703S this function no longer exist but they add in its place a new function called UART in Multimeter Mode. This is in Multimeter Mode you click the MENU button and it will then display (Language, Auto Off, Bk Light, Uart).
UART if you switch it to ON is supposed to display Multimeter readings through the COMM port.
Has anybody got this to work, and can you please explain how you were able to do it?
I tried a few times but couldn't get this to work on my Windows computer (it will not recognize or show the Comm port)
-
Are you connecting the signal generator output to a usb to serial adapter (or a real serial port)? It's not through the USB port, it's through the signal generator port.
I don't have a TTL USB to Serial adapter here to try it with, but if I measure that port in multimeter mode on AC voltage, I can see a slight increase in AC voltage when I turn the UART function on, and it goes back to zero when I turn UART off.
Yes, it's dumb they didn't do it through a built in usb-serial adapter.
[attachimg=1]
-
Thanks ahakman,
That explains some of the puzzle.
Yes, I was kind of expecting that when you plug the 703S via a USB cable it would show up on the Windows computer with a newly assigned COM port, similar to when you connect and Arduino or ESP32 device.
So I sacrifice an old USB cable and stripped it and connected the 2 USB data wires to the Multimeter Signal Generator Output Port. Having UART=ON, when I plug into the male end of the USB cable to Windows machine, it does not show as a COM port in Device Manager. But I did hear Device Manager give a Ding, like it recognized something (I could not easily find the change).
Things didn't work, its late, will try another day...
PS1: I have visions I might have to use old 9 pin RS-232 cable and hook up to old WinXP computer (that has the old serial ports)... Or maybe I can use a Serial Port to USB port cable... Please "Say it isn't so, Joe"
PS2: In Windows Device Manager if you do not see COM Ports, you might have to click View Menu > Show hidden devices.
-
Could you take screenshots of the meander with a frequency of 1 MHz and higher?
-
My batt icon shows the full 4 bars ("full") but power button is still red.
What did batt icon and power button show next?
-
Thanks ahakman,
That explains some of the puzzle.
Yes, I was kind of expecting that when you plug the 703S via a USB cable it would show up on the Windows computer with a newly assigned COM port, similar to when you connect and Arduino or ESP32 device.
So I sacrifice an old USB cable and stripped it and connected the 2 USB data wires to the Multimeter Signal Generator Output Port. Having UART=ON, when I plug into the male end of the USB cable to Windows machine, it does not show as a COM port in Device Manager. But I did hear Device Manager give a Ding, like it recognized something (I could not easily find the change).
Things didn't work, its late, will try another day...
PS1: I have visions I might have to use old 9 pin RS-232 cable and hook up to old WinXP computer (that has the old serial ports)... Or maybe I can use a Serial Port to USB port cable... Please "Say it isn't so, Joe"
PS2: In Windows Device Manager if you do not see COM Ports, you might have to click View Menu > Show hidden devices.
I do not have a 703 but my understanding is that it will output serial UART data at 3.3 or 5 Volts. That cannot be connected directly to a USB port. It might work if connected to the RxD pin of a PC 9 pin serial port. If the PC has only USB ports you will need a "USB to TTL" type interface.
-
PS1: I have visions I might have to use old 9 pin RS-232 cable and hook up to old WinXP computer (that has the old serial ports)... Or maybe I can use a Serial Port to USB port cable... Please "Say it isn't so, Joe"
Yes, you need to use a TTL RS232 to USB adapter if your computer doesn't have native serial ports. The meter will be outputting raw TTL RS232 - you can't connect that directly to a USB cable - they're not the same protocol at all.
It needs to go.
meter --> ttl rs232 to usb adapter -> usb port on computer
Even if you have native serial ports, you'd probably need a level shifter - I'm guessing the meter is outputting 3.3V signals, and a real serial port is expecting +/- 12V. Maybe some modern serial ports work directly with TTL, but even if so, 3.3V might be too low for reliable communication.
-
The ZT-702S oscilloscope does not show the end of charging on the display. The battery icon does not change. How to determine that charging has ended?
While charging, the On/Off button of my ZT-702S glows red. When the DMM is fully charged, the button simply powers off. The battery indicator shows as fully charged.
-
When the DMM is fully charged
How long does it take to fully charge?
-
When the DMM is fully charged
How long does it take to fully charge?
Unfortunately I rarely let it go to 0%, thus I don't remember the time for a complete charge.
Today it took about 1/2 hour to charge it from about three bars to full.
-
Yes, you need to use a TTL RS232 to USB adapter if your computer doesn't have native serial ports. The meter will be outputting raw TTL RS232 - you can't connect that directly to a USB cable - they're not the same protocol at all.
It needs to go.
meter --> ttl rs232 to usb adapter -> usb port on computer
Even if you have native serial ports, you'd probably need a level shifter - I'm guessing the meter is outputting 3.3V signals, and a real serial port is expecting +/- 12V. Maybe some modern serial ports work directly with TTL, but even if so, 3.3V might be too low for reliable communication.
Yes, a TTL RS232 to USB adapter works just fine. The meter outputs a 3.0 volt signal as you can see from the scope capture.
Here's are some sample output lines, note that there is no <CR> nor <LF> marking the line ends this is my edit. The meter sends about 3 lines per second so the delay between records can be used as a break. Also, the output doesn't specify AC or DC, this seems to be an oversight. Finally current is called "electricity"!
Voltage:-23.211 mV
Voltage:0.0003 V
Resistance:0.L KOM
Resistance:002.15 OM
beep:. OM
beep:000.04 OM
Diode:. V
Diode:00.001 V
Electricity:0.0000 A
-
What does it mean Coupling?
-
Yes, a TTL RS232 to USB adapter works just fine. The meter outputs a 3.0 volt signal as you can see from the scope capture.
Here's are some sample output lines, note that there is no <CR> nor <LF> marking the line ends this is my edit. The meter sends about 3 lines per second so the delay between records can be used as a break. Also, the output doesn't specify AC or DC, this seems to be an oversight. Finally current is called "electricity"!
Katie/KWASS:
Could you please tell what exact Baud settings you used?
Baud Rate: 115200
Data bits: ??[5, 6, 7, or 8]
Parity: ?? [even, odd, none, mark, space]
Stop bits: ??[1, 1.5, or 2]
Flow control: ??[hardware, software, none, Xon / Xoff]
Handshaking: ??[none, XON/XOFF, RTS/CTS, DSR/DTR]
Language: ??[ASCII, utf-8, other]
Delay: ??[some serial communication programs have this...]
I know that standard setting is Parity=N, Data bits=8, Stop bit=1, Flow control=None, but not sure with this company Zoyi since no exact documentation. I'm not sure they even used standard settings...
I was able to use a USB to TTL RS232 9-pin adaptor, but in the serial output programs I use the message is always garbled. So some setting(s) is(are) wrong.
-
I don't think I've ever seen a TTL usb to serial adapter have a 9 pin connector on them. Usually they have loose wires (flying leads), or raw solder pads that you solder your own wires to. Having a 9pin connector typically means it's a full RS232 voltage adapter, and NOT TTL.
You're probably getting garbled communications because 3V is not enough to reliably signal the USB to Serial adapter you have because it's not actually a TTL level adapter.
The settings will be 115200, 8, N, 1
No flow control
No handshaking
ASCII
and no delay (character delay is usually only for transmission - it introduces a slight delay between characters - it does nothing for reception)
-
I don't think I've ever seen a TTL usb to serial adapter have a 9 pin connector on them. Usually they have loose wires (flying leads), or raw solder pads that you solder your own wires to. Having a 9pin connector typically means it's a full RS232 voltage adapter, and NOT TTL.
You're probably getting garbled communications because 3V is not enough to reliably signal the USB to Serial adapter you have because it's not actually a TTL level adapter.
The settings will be 115200, 8, N, 1
No flow control
No handshaking
ASCII
and no delay (character delay is usually only for transmission - it introduces a slight delay between characters - it does nothing for reception)
That's exactly what I used for settings. For hardware, I used something like this from Amazon. It only has RX, TX and GND so there's no way to mess up the handshaking options! ;) https://www.amazon.com/DSD-TECH-3-5mm-Cable-Interface/dp/B07XXVF4RM (https://www.amazon.com/DSD-TECH-3-5mm-Cable-Interface/dp/B07XXVF4RM)
-
I just purchased it last year.
-
Yes, a TTL RS232 to USB adapter works just fine. The meter outputs a 3.0 volt signal as you can see from the scope capture.
Here's are some sample output lines, note that there is no <CR> nor <LF> marking the line ends this is my edit. The meter sends about 3 lines per second so the delay between records can be used as a break. Also, the output doesn't specify AC or DC, this seems to be an oversight. Finally current is called "electricity"!
Katie/KWASS:
Could you please tell what exact Baud settings you used?
Baud Rate: 115200
Data bits: ??[5, 6, 7, or 8]
Parity: ?? [even, odd, none, mark, space]
Stop bits: ??[1, 1.5, or 2]
Flow control: ??[hardware, software, none, Xon / Xoff]
Handshaking: ??[none, XON/XOFF, RTS/CTS, DSR/DTR]
Language: ??[ASCII, utf-8, other]
Delay: ??[some serial communication programs have this...]
I know that standard setting is Parity=N, Data bits=8, Stop bit=1, Flow control=None, but not sure with this company Zoyi since no exact documentation. I'm not sure they even used standard settings...
I was able to use a USB to TTL RS232 9-pin adaptor, but in the serial output programs I use the message is always garbled. So some setting(s) is(are) wrong.
If your adaptor has a 9 pin plug to fit a 9 pin SER socket on a PC, connecting that to the Zoyi will never work. For "TTL serial" a logical 1 is signalled by positive voltage and a 0 by zero (or close to zero) voltage. But true RS232 is different. A 1 is negative voltage and a 0 by positive voltage. That is why RS232 interface chips '188 and '189 are inverting.
-
Too bad it's not a dfu device using STM chipset, the STM driver is a simple USB to virtual COM.
-
I don't think I've ever seen a TTL usb to serial adapter have a 9 pin connector on them. Usually they have loose wires (flying leads), or raw solder pads that you solder your own wires to. Having a 9pin connector typically means it's a full RS232 voltage adapter, and NOT TTL.
You're probably getting garbled communications because 3V is not enough to reliably signal the USB to Serial adapter you have because it's not actually a TTL level adapter.
The settings will be 115200, 8, N, 1
No flow control
No handshaking
ASCII
and no delay (character delay is usually only for transmission - it introduces a slight delay between characters - it does nothing for reception)
That's exactly what I used for settings. For hardware, I used something like this from Amazon. It only has RX, TX and GND so there's no way to mess up the handshaking options! ;) https://www.amazon.com/DSD-TECH-3-5mm-Cable-Interface/dp/B07XXVF4RM (https://www.amazon.com/DSD-TECH-3-5mm-Cable-Interface/dp/B07XXVF4RM)
Did you cut off the 1/8" end and wire it to a USB-C male end? My 703 only has USB-C
Is there a 1/8" female to USB-C adapter made for just the serial lines?
-
Did you cut off the 1/8" end and wire it to a USB-C male end? My 703 only has USB-C
Is there a 1/8" female to USB-C adapter made for just the serial lines?
As noted earlier in this thread, the 703's UART communication occurs over the signal generator output. Not the USB-C port.
-
Did you cut off the 1/8" end and wire it to a USB-C male end? My 703 only has USB-C
Is there a 1/8" female to USB-C adapter made for just the serial lines?
As noted earlier in this thread, the 703's UART communication occurs over the signal generator output. Not the USB-C port.
What port / jack is the "generator output" port?
My 703 has one usb-c, and two BNC's at the top.
-
What port / jack is the "generator output" port?
My 703 has one usb-c, and two BNC's at the top.
They use the probe compensation loops next to the USB-C port
-
What port / jack is the "generator output" port?
My 703 has one usb-c, and two BNC's at the top.
They use the probe compensation loops next to the USB-C port
Lug gnd is tx- and signal lug is tx+ ?
So you just alligator clip it for serial data? That's an odd way to make a serial connection. Adding 1/8 phono would have been easy.
Is it the same lugs for Generator too? Or is one of BNC's the Generator?
My 703 Signal Generator stops at 344kHz.
Also, a slight bug. When exiting Signal Generator, it exits back to Scope default mode, not where the settings were, and, it knocks backlight down to 30%.
-
That's exactly what I used for settings. For hardware, I used something like this from Amazon. It only has RX, TX and GND so there's no way to mess up the handshaking options! ;) https://www.amazon.com/DSD-TECH-3-5mm-Cable-Interface/dp/B07XXVF4RM (https://www.amazon.com/DSD-TECH-3-5mm-Cable-Interface/dp/B07XXVF4RM)
Did you cut off the 1/8" end and wire it to a USB-C male end? My 703 only has USB-C
Is there a 1/8" female to USB-C adapter made for just the serial lines?
Not to the USB-C port. The serial output is on the probe calibration lug and the ground next to it. Very strange, but the serial data output seems to be just a throw-away idea. There's much wrong with the way they implemented this, but I suppose it's better than nothing.
-
Lug gnd is tx- and signal lug is tx+ ?
So you just alligator clip it for serial data? That's an odd way to make a serial connection. Adding 1/8 phono would have been easy.
Is it the same lugs for Generator too? Or is one of BNC's the Generator?
Yes, same lugs. Connect the TTL GND line to the GND (small) lug, and the RX line to the signal output (big) lug. Set your PC terminal to 115200/8/N/1. When UART mode is on the meter sends continuously.
It's crude, but it works.
-
Lug gnd is tx- and signal lug is tx+ ?
So you just alligator clip it for serial data? That's an odd way to make a serial connection. Adding 1/8 phono would have been easy.
Is it the same lugs for Generator too? Or is one of BNC's the Generator?
Yes, same lugs. Connect the TTL GND line to the GND (small) lug, and the RX line to the signal output (big) lug. Set your PC terminal to 115200/8/N/1. When UART mode is on the meter sends continuously.
It's crude, but it works.
But the TTL interface is needed, right?
Posted earlier --> https://www.amazon.com/DSD-TECH-3-5mm-Cable-Interface/dp/B07XXVF4RM (https://www.amazon.com/DSD-TECH-3-5mm-Cable-Interface/dp/B07XXVF4RM)
So with that adapter, we need some type of clip-on to 1/8 female to make it usable. A clip-on that slips on over the lugs, makes contact and retains connection.
Spring loaded pcb with pads, in a 3D printed case ?
Printed a concept connector. Slip boxes basically (one fits in the other). One side plugs into the lugs, the other side accepts 1/8" plug. Obviously would need to be bigger, and will need to house the connections.
Anyone interested in such?
-
Lug gnd is tx- and signal lug is tx+ ?
So you just alligator clip it for serial data? That's an odd way to make a serial connection. Adding 1/8 phono would have been easy.
Is it the same lugs for Generator too? Or is one of BNC's the Generator?
Yes, same lugs. Connect the TTL GND line to the GND (small) lug, and the RX line to the signal output (big) lug. Set your PC terminal to 115200/8/N/1. When UART mode is on the meter sends continuously.
It's crude, but it works.
But the TTL interface is needed, right?
Posted earlier --> https://www.amazon.com/DSD-TECH-3-5mm-Cable-Interface/dp/B07XXVF4RM (https://www.amazon.com/DSD-TECH-3-5mm-Cable-Interface/dp/B07XXVF4RM)
So with that adapter, we need some type of clip-on to 1/8 female to make it usable. A clip-on that slips on over the lugs, makes contact and retains connection.
Spring loaded pcb with pads, in a 3D printed case ?
Just cut off the 3.5mm plug and solder some alligator/crocodile clips to the leads. They work well with these lugs.
-
But the TTL interface is needed, right?
Posted earlier --> https://www.amazon.com/DSD-TECH-3-5mm-Cable-Interface/dp/B07XXVF4RM (https://www.amazon.com/DSD-TECH-3-5mm-Cable-Interface/dp/B07XXVF4RM)
So with that adapter, we need some type of clip-on to 1/8 female to make it usable. A clip-on that slips on over the lugs, makes contact and retains connection.
My USB to UART cable does not terminate in a 3.5mm plug, it terminates in female Dupont connectors, handy for fitting to header pins. Like this one:
https://www.amazon.com/gp/product/B014GZTCC6 (https://www.amazon.com/gp/product/B014GZTCC6)
For the 703S I used a pair of breadboard Dupont wires in between and just wedged the pins into the generator lug holes to test the UART feature. If I were actually doing some logging with it I'd fasten it with crocodile clips or some other fixed attachment.
If you have the 3.5mm version, then yeah you either cut off the plug and use the bare wires (or attach clips or pins or whatever). Or if you want to keep it intact, rig a female 3.5mm jack to bare wires to mate with it.
It's unlikely I'd use the 703S for logging or remote display, I was just testing out the feature since some were asking and I had a TTL cable handy. All of my bench DMMs and scopes have LXI (ethernet) connections, and for handhelds I have a couple of more serious DMMs plus an Owon HDS2202S scope with USB interfaces that I'd use before this one.
-
I suspected low interest in such connector. I'll drum up something from spare parts, just to have as a data cable for the 703. Perhaps a good additional to have when it comes time to sell off the unit. ;)
-
It looks like the learnelectronics YouTube channel is the first to give a review of the ZT-703S DMM/Oscilloscope.
https://www.youtube.com/watch?v=29ZmezkwnTM (https://www.youtube.com/watch?v=29ZmezkwnTM)
-
It looks like the learnelectronics YouTube channel is the first to give a review of the ZT-703S DMM/Oscilloscope.
https://www.youtube.com/watch?v=29ZmezkwnTM (https://www.youtube.com/watch?v=29ZmezkwnTM)
Does the 703S have X,Y mode?
-
Yes it has x-y but it seems to be slow.
Zoyi has now the official release
https://youtu.be/7oOIPuvy2qU?si=wwuMHl1cxUcE-zXd
I've ordered a 703S in their shop.
-
Yes it has x-y but it seems to be slow.
Zoyi has now the official release
https://youtu.be/7oOIPuvy2qU?si=wwuMHl1cxUcE-zXd
I've ordered a 703S in their shop.
Is this mode right?
-
From my experience using the SOYI 702s, the ohm measurement in the circuit is worse than the Uni-T 61X. The measurement is not very accurate and the result display is very slow. I think if I had the money I would probably move to the Owon-HDS242S which is very accurate. Plus it shows results quickly.
-
It looks like the learnelectronics YouTube channel is the first to give a review of the ZT-703S DMM/Oscilloscope.
These Youtube testers are a strange lot! ;D
I really don't know much about measuring equipment, but the first thing you get told when you buy a new oscilloscope is:
"Calibrate the probes" and the second thing you get told is "don't measure above 5/6MHz with a 1x probe".
"learnelectronics" has 160,000 subscribers and he does exactly that!
Then he wonders why the amplitude drops at 10MHz
He then says that he doesn't believe it can do 50MHz.
Why "believe" and not measure?
Also, what does a 500KHz sine test mean with a 50MHz oscilloscope?
Have I misunderstood something? I am not a native English speaker.
-
These Youtube testers are a strange lot! ;D
I really don't know much about measuring equipment, but the first thing you get told when you buy a new oscilloscope is:
Calibrate the probes and the second thing you get told is don't measure above 5/6MHz with a 1x probe.
"learnelectronics" has 160,000 subscribers and he does exactly that!
I've watched Richard for awhile. I like him but he is an odd fellow, and while he has considerable theoretical knowledge of fundamentals and an easy way of explaining things in a way that beginners & hobbyists can understand, he's awkward as hell when it comes to physically using/doing things. Be it soldering, using a hot air station, test equipment, probing, etc. He tilts me every time he grabs his hot air nozzle and starts waving it around, taking a minute and a half to desolder something. Or when he probes with his beat up Fluke 77 and can't seem to keep the probe tips in place while also pressing so hard his hands shake. I cringe when I watch him sometimes.
That said, his graph paper drawings and video series "All You Need to Know about XXX to Fix Stuff" are his best work, IMO, if you're a hobbyist trying to gain some practical theory quickly. It's just his hands-on work that gives me fits.
EDIT: My mistake, I misread the channel as "learnelectronicsrepair" which is Richards channel. "learnelectronics" is a different channel entirely. I've actually been a long-time subscriber to both.
-
@ Veteran68 et al.
I find the computing and electronics fields to be the most peer teaching fields out there. This is easy to teach others and tons of free (and not so free) resources out there (instructor videos, blogs, books, websites, forum boards, etc.). Because a lot of people are self-taught (and even if they learn formally get a Comp Sci or EE degree they still learn a lot more on own after formal training...), therefore people tend to be experts in some specific areas while being maybe lacking (or not as strong suit) in others.
I'm under the assumption Richard/learnelectronics guy started out in electronics from the USA Navy. So likely learned a lot on his own afterwards... He is likely popular because he knows more than first time electronics people and willing to share what he knows...
I'm looking forward on other ZT-703S reviews from other YouTubers... Especially on it's capabilities/limitations and a few Tips or Tricks...
-
Richard/learnelectronics writes that there is something wrong with his heart:
"Yes, I know my hands are large/fat. It's because of a heart condition I suffer from called Congestive Heart Failure. (...)
One of the symptoms is that it causes fluid retention, mostly in the hands, feet/ankles, and face.."
That explains his physical problems, but not the 1x probe.
-
ZT-703s Firmware v1.2.7 ~ 2024.01.15
-
Where did you get this from? Is there a change log?
-
That
Richard Paul vid is just a preview of the meter.
Does not appear to be a full test/compare vid.
Yeah, he perhaps missed a few things to highlight or look at, but it did not appear to me to be anything more than a quick setup and push the buttons.
-
My apologies, I read "learnelectronics" as "learnelectronicsrepair." Richard from learnelectronicsrepair is the guy I was referring to.
I've actually subscribed to both for awhile now. They're similar size channels in terms of subscribers, although learnelectronics has been at it longer and has about 3x as many videos.
Yes, Richard/learnelectronics writes that there is something wrong with his heart:
"Yes, I know my hands are large/fat. It's because of a heart condition I suffer from called Congestive Heart Failure. (...)
One of the symptoms is that it causes fluid retention, mostly in the hands, feet/ankles, and face.."
That explains his physical problems, but not the 1x probe.
Yes he did get his start in the US Navy, and unfortunately suffers from CHF. And even so, I don't find him as physically awkward as Richard from learningelectronicsrepair when it comes to being hands-on. As I mentioned, Richard excels at lecturing and diagramming the theory and fundamentals, while learnelectronics (I can't recall his name) is better at the hands-on aspects. Both are good channels in their own way.
-
..., while learnelectronics (I can't recall his name)...
I think his name is Paul, as some people in the comments thanked "Paul" for the video.
-
..., while learnelectronics (I can't recall his name)...
I think his name is Paul, as some people in the comments thanked "Paul" for the video.
Yes, now that you mention it, I do recall his name being Paul.
-
Anyone know the cpu/architecture these 702/703's are built on?
-
Where did you get this from? Is there a change log?
Katie/kwass et al., I started a nice post explaining on how to get the updated ZT-703S firmware upgrade, but thought better to install on mine first, but when I did I got the following error message.
[attachimg=1]
I'm trying to contact Zotek (maybe a few hours they will start work) to try and let them know there is an issue, figure out what this exactly mean, and if they can solve it...
In the meanwhile, here is what I was going to originally post... Maybe you have better luck than me...?
=====
Where did you get this from? Is there a change log?
@ Katie et al.,
If you go to Zoyi's website here:
https://zotektools.com/products/zoyi-zt-703s/
Click "Up Date the File" button/link
Then click "Update the file" button/link
It will take you to a Google Drive and if you click Download it will give you a file called something like:
ZOYI-703S-FW-V127(1).ZTK
I assume the *.ZTK extension is Zoyi's DMM firmware update extension.
To see how to update the firmware there is a YouTube video on how here (with older sister DMM 702S, assume same way to do firmware update)
Nutshell steps (at least for Windows, correct me if I'm wrong)
Turn off ZT-703S
Plug in USB-C cable from PC to ZT-703S
Press F1 and then Power (might have to hold)
On Windows computer should create a new Drive something like RAM E: (note drive letter might be different on your particular computer)
If you go to this new RAM Drive letter it should show a folder called "firmware"
Place the above file *.ZTK inside the "firmware" folder
On the ZT-703S it should show progression bar and "upgrading, do not power off"
=====
-
Same issue. The firmware file is 626K and there's only 592K of 608K total available.
The 702S firmware update was only 364K. Sounds like someone forgot to add a bit more flash memory to account for the 703S firmware size. Or else forgot to strip symbols or something from this build.
-
No issue here upgrading 703 to v127
702 latest appears to be v58, about half size of the 703 v127
But, no need to power up holding buttons.
Turn on 703
cable to PC
goto scope mode, menu, scroll to USB, select it
dump the ZTK into the "firmware" folder, it will then update with progress bar and then reboot
For the mem issue 703's, do you have any data or pic files in any of the folders?
-
No, there is nothing in the flash drive other than an empty firmware folder and the hidden system folder that Windows always adds. Besides that, the total folder capacity isn't big enough to contain the firmware update file. It's only 608K total, with 592K free. The firmware file is 626K.
(https://www.morrisonline.us/images/Screenshot%202024-01-17%20222251.png)
(https://www.morrisonline.us/images/Screenshot%202024-01-17%20222638.png)(https://www.morrisonline.us/images/Screenshot%202024-01-17%20222756.png)
How big is the RAM volume on your 703S?
-
@Veteran68 and everybody else...
Randy222 gave me a clue...
Do this FORMAT the device (this will clear out images)...
[attachimg=2]
Then in the oscilloscope Menu system go to USB and click the F3 button to Enter it...
Then Drag and Drop (copy) the ZOYI-703S-FW-V127(1).ZTK to the FIRMWARE folder
[attachimg=1]
ZT-703S "should" say upgrading do not power off...
Voila... It should be upgraded...
Note1: When I first tried upgrading firmware (which failed) it said RAM and then the newly assigned Drive Letter for the ZT-703S. This time after doing FORMAT it says FLASH and the newly assigned drive letter and gave more folders (Application, data, log, pic) in addition to firmware and System Volume Information folders.
Note2: I wish Zotek people would have a Change Log or History (of what changes they made) so we do not have to guess...
Note3: I also wish Zotek had it where you can go back older version (in case something goes wrong).
-
Same issue. The firmware file is 626K and there's only 592K of 608K total available.
The 702S firmware update was only 364K. Sounds like someone forgot to add a bit more flash memory to account for the 703S firmware size. Or else forgot to strip symbols or something from this build.
Addendum: After you go to Oscilloscope Mode, then press MENU and do a FORMAT of the ZT-703S, and then go to USB mode, in Windows File Explorer it will show something like FLASH E:\ and if you click properties, it will show unit memory has 16 MB.
[attachimg=1]
Note: Again, your drive letter might be different (like D:\ or F:\ or other) because likely windows auto assign next available free drive letter and your computer might be differently partitioned than mine)
-
Note2: I wish Zotek people would have a Change Log or History (of what changes they made) so we do not have to guess...
Take a look here: https://www-dt830-com.translate.goog/thread-8262-1-1.html?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp&_x_tr_sch=http (https://www-dt830-com.translate.goog/thread-8262-1-1.html?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp&_x_tr_sch=http)
Change Log for the prior version but not this latest one. There's a bunch of info about all the Zoyi products on this forum if you more up a level or two.
-
I did no formatting, my 703 is out-of-box, less the v127 I just installed.
My win10 shows 703 flash drive as "14.393MB capacity". I will assume the 703 has a 16MB ram/rom chip.
With v127 installed flash drive shows just north of 10MB as free, and just north of 3MB as used.
-
This is all very interesting. I wonder why some of ours show such a small 600K "RAM" volume when the apparent capacity should be ~16MB. As I said, and as you can see from my screenshots, other than some hidden 16K filesystem overhead there's nothing in mine.
When I get home today I'll try to format approach and see what happens. Odd that it doesn't come formatted out of the box, yet has the firmware folder in place like it's been prepared to received fw updates.
-
I did no formatting, my 703 is out-of-box, less the v127 I just installed.
My win10 shows 703 flash drive as "14.393MB capacity". I will assume the 703 has a 16MB ram/rom chip.
With v127 installed flash drive shows just north of 10MB as free, and just north of 3MB as used.
My hunch is that maybe you (Randy222) upgraded the firmware right away therefore you had no problem. Whereas Veteran68 and I maybe saved a few waveforms testing out the device. Because of this maybe this altered things and/or even though we deleted the waveform pics that they still took up some space or cache (not 100% certain on this). Anyway seems like if you do a FORMAT this clears out everything which then give you room to do the firmware install...
@Katie/kwass
That Chinese forum board DT830 link is actually referring to the new 703S. Seems like they are actively and quickly trying to find bugs and fix them as soon as possible.
One thing to note with the Ver 1.27 firmware upgrade, it seems to fix the problem in which if you were in MultiMeter Mode and you turn off the unit it will likely default to Oscilloscope Mode. Now whatever Mode you were in when you turned off the machine (or assume auto-off) that when you restart it will go to the last mode you were in (which is the way it should be)...
-
My hunch is that maybe you (Randy222) upgraded the firmware right away therefore you had no problem. Whereas Veteran68 and I maybe saved a few waveforms testing out the device.
Not the case for me. I'd saved nothing, ever. In fact since I got it I've done little beyond turn it on, and test the UART function as discussed before. I have a 702S already so was familiar already with the function, and hadn't had a use for this one yet (I collect far more than I use, I have somewhere around 35-40 handheld DMMs/scopes).
It's telling that our out-of-box experience is one where the volume is labeled "RAM", contains just a firmware folder, and is only 608K in capacity. Whereas post-format it's labeled FLASH, has multiple folders, and is 16MB in size. So either Randy's left the factory later and was formatted properly (possible, as mine was a preorder and may have been an early unit), or he'd already formatted it, perhaps not realizing or remembering. Curious to hear from others as to how theirs is formatted out of the box.
One thing to note with the Ver 1.27 firmware upgrade, it seems to fix the problem in which if you were in MultiMeter Mode and you turn off the unit it will likely default to Oscilloscope Mode. Now whatever Mode you were in when you turned off the machine (or assume auto-off) that when you restart it will go to the last mode you were in (which is the way it should be)...
Yes this was the main update with the last 702S firmware update. I noted earlier that I was surprised that the default had regressed in the 703S. I expect that the 703S and its delivered firmware were already in development/being finalized when the 702S update occurred, and they didn't merge their code before the 703S release.
-
v127 for 703 is very bad
I went into scope with prob set 10x ch1, changed freq to 1kHz sine 1v, back to scope and hit AUTO, it combed a few time scales to 100ms, then the unit seemed to freeze/crash and screen shut off to black, but 703 is still powered on! I press power button and flat line ch1 appears, then some just seconds later screen goes black again (Auto Off setting is set to OFF, I don't see any sleep or screen timer). Screen goes dark every 30sec.
(sine wave with DC coupling seems to be the culprit for AUTO with "crash", switch it to AC coupling and AUTO seems to be "ok")
1v on 10x probe config should not be hard for 702/703 to display, but weird stuff.
Also, using square wave, no longer can set freq or v or duty cycle. It's now just 1kHz 50%.
Measuring 1v sine, is off. 1v set, vpp says 860.0mv, or, the actual setting of 1v for the signal is off, not sure which.
Depending on volt scale chosen, the vpp measure changes, anywhere from 850mv all the way to 1.5v !
Set freq out sine 5kHz 1v (arbitrary setting), hit AUTO, then go into menu and cycle the Trigger Mode from Auto to Manual to Single and back to Auto, on the last back to Auto, scope sticks in STOP mode.
Scope will not allow you to turn off both channels at the same time.
I try the Calibrate menu item (open ports), it displays "Under Calibration" and then 5sec later a "Check Failure" notice (assume to mean claibrate failed). Where is the fail notice? It did not write any user accessible file into any folder when in USB mode.
Something not right with v127.
Timescale issue at 100ns seems to be fixed, I can tune all the way down to 10ns with the square wave.
Note: the F1 + power on is the same things as turning on USB from scope menu.
-
One thing to note with the Ver 1.27 firmware upgrade, it seems to fix the problem in which if you were in MultiMeter Mode and you turn off the unit it will likely default to Oscilloscope Mode. Now whatever Mode you were in when you turned off the machine (or assume auto-off) that when you restart it will go to the last mode you were in (which is the way it should be)...
It's not quite fixed. On the 702 you can switch from multimeter to scope and back and you'll be on the function/range that you had before, on the 703 this will reset to auto-ranging VDC every time. That needs to be fixed.
-
Note2: I wish Zotek people would have a Change Log or History (of what changes they made) so we do not have to guess...
Take a look here: https://www-dt830-com.translate.goog/thread-8262-1-1.html?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp&_x_tr_sch=http (https://www-dt830-com.translate.goog/thread-8262-1-1.html?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp&_x_tr_sch=http)
Change Log for the prior version but not this latest one. There's a bunch of info about all the Zoyi products on this forum if you more up a level or two.
Copied here for posterity. Last week's 1.19 release is also newer than what mine came with. Not at home right now but last night when trying this update I want to say my shipped version was 1.09.
2024.01.15 ZOYI-703S-FW-V127
has fixed several problems discovered by friends in the group,
but the details have not been announced yet
2024.01.08 ZOYI-703S-FW- V119
1. Fix the problem that the 100ns time base trigger position is incorrect.
2. Fix the problem that the time base will occasionally be confused when scaling the waveform after stopping in the single trigger mode.
3. Fix the abnormal measurement value in the rolling mode.
4. Fix the rolling mode.
5. Fixed the problem that the grid is occasionally eaten in scrolling mode
6. Fixed the problem that in multimeter mode, occasional garbled characters will appear when powering on
7. Fixed the problem after switching between different applications, the problem of language out of sync
8. Add the function of maintaining the current language after restoring the default settings
9. Fix the problem that the U disk cannot be opened occasionally
10. Unify the frequency unit
11. Fix the startup memory mode, the multimeter interface is turned off and turned on to start the multimeter. Turn off and on the oscilloscope in oscilloscope mode
12. Remove the "prompt that the trigger may be unstable"
13. Optimize the AUTO logic and fix some problems in AUTO mode, including possible crashes, stucks, timeouts, etc.
-
Note2: I wish Zotek people would have a Change Log or History (of what changes they made) so we do not have to guess...
Take a look here: https://www-dt830-com.translate.goog/thread-8262-1-1.html?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp&_x_tr_sch=http (https://www-dt830-com.translate.goog/thread-8262-1-1.html?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp&_x_tr_sch=http)
Change Log for the prior version but not this latest one. There's a bunch of info about all the Zoyi products on this forum if you more up a level or two.
Copied here for posterity. Last week's 1.19 release is also newer than what mine came with. Not at home right now but last night when trying this update I want to say my shipped version was 1.09.
2024.01.15 ZOYI-703S-FW-V127
has fixed several problems discovered by friends in the group,
but the details have not been announced yet
2024.01.08 ZOYI-703S-FW- V119
1. Fix the problem that the 100ns time base trigger position is incorrect.
2. Fix the problem that the time base will occasionally be confused when scaling the waveform after stopping in the single trigger mode.
3. Fix the abnormal measurement value in the rolling mode.
4. Fix the rolling mode.
5. Fixed the problem that the grid is occasionally eaten in scrolling mode
6. Fixed the problem that in multimeter mode, occasional garbled characters will appear when powering on
7. Fixed the problem after switching between different applications, the problem of language out of sync
8. Add the function of maintaining the current language after restoring the default settings
9. Fix the problem that the U disk cannot be opened occasionally
10. Unify the frequency unit
11. Fix the startup memory mode, the multimeter interface is turned off and turned on to start the multimeter. Turn off and on the oscilloscope in oscilloscope mode
12. Remove the "prompt that the trigger may be unstable"
13. Optimize the AUTO logic and fix some problems in AUTO mode, including possible crashes, stucks, timeouts, etc.
#13 seems to still be an issue in v127
-
Anyone know the cpu/architecture these 702/703's are built on?
702 is an Artery AT32F403AVGT7. 703 probably the same?
-
Anyone know the cpu/architecture these 702/703's are built on?
702 is an Artery AT32F403AVGT7. 703 probably the same?
An ARM Cortex M4F 32bit.
Thanks.
-
My 703 now turns screen off every 30sec, but I see no menu item to change that.
This seemed to happen after the unit appeared to have crashed while attempting Auto on a 1v sine 5kHz with probe settings 10x.
Anyone else have screen-off issue?
-
My 703 now turns screen off every 30sec, but I see no menu item to change that.
This seemed to happen after the unit appeared to have crashed while attempting Auto on a 1v sine 5kHz with probe settings 10x.
Anyone else have screen-off issue?
I think that is the "BL" setting in the menu. As I recall, 30/60/120s (or never)
-
My 703 now turns screen off every 30sec, but I see no menu item to change that.
This seemed to happen after the unit appeared to have crashed while attempting Auto on a 1v sine 5kHz with probe settings 10x.
Anyone else have screen-off issue?
I think that is the "BL" setting in the menu. As I recall, 30/60/120s (or never)
I only have Bk Light, for me is only a % for brightness. Other than that I have an auto-off menu item (set to off), auto-off powers off the device.
I seem to have a 30-sec screensaver that just turns the screen off black. I don't see where to change that. Has to be a bug in v127.
-
My 703 now turns screen off every 30sec, but I see no menu item to change that.
This seemed to happen after the unit appeared to have crashed while attempting Auto on a 1v sine 5kHz with probe settings 10x.
Anyone else have screen-off issue?
I turned my ZT-203S on Volt Meter mode. Did nothing (not testing just let it set) and it turned of in about 2 minutes. Since quyincog suggest the BL (back light time) setting I checked mine and it said 120s.
It seems like the BackLight turns off whole screen (to black) but if you quickly press Power button (or any key) it turns back on.
-
@ Randy222
Try:
Got to Oscilloscope mode
Press Menu
Press > (right arrow next Menu) 4 times (which should take you to the 5th menu tab).
there "should be a BL time above the F4 key
-
Adendum:
I think this is how it works "BL time" is sort of like auto turning off Screen in Windows in Power Saving Mode. And if you tap any key it quickly turns back on [the screen].
"Auto Off" is sort of like auto turning off (or more like Sleep mode because the unit boots pretty darn quick) in Windows Power Saving Mode... After it turns the meter off you have to long press the Power button (2 seconds) to reboot/turn on.
-
Found the BL menu item. |O on myself.
I will try to make the v127 crash again and see if it comes back with BL set to 30s.
-
Hi, i put some tests together, but somehow i have the feeling they changes something with the sampleing.
Still my sample from Zotek needs to arrive, not sure what version that will be, this was a pre release from teh store mentioned many times before.
i tested off video with the firmware 1.0.9 and then i could go above 46 MHz .. not very stable but i could.
now i did same test with 1.2.7 and, is was a no go...it was going allover the place... it was very stable upto 46 MHz though.. and that has improved a lot.
it seems they made a choice of going above 50 and shaking or stable upto 46... can agree with them.
anyone has firmware file from before 1.2.7 ? please share. i like to do more tests.
https://www.youtube.com/watch?v=FkXE9idzym4 (https://www.youtube.com/watch?v=FkXE9idzym4)
-
I don't have the installable firmware file, but my unit still has 1.0.9 on it as I haven't updated yet.
I'll be back home in a couple of days and able to run more tests with more test equipment when I'm back.
-
I keep the 703S just to have around.
I did order a FNIRSI Dpox180h
-
703S with the v127 FW
Anyone trying to Calibrate and it fails to calibrate?
-
Yes mine failed to, but then i found out, i had switched off 1 of the channels,
So switch both channels back on, or set it first to Defaul.. and than do a calibrate, then it will work.
Silly yes.
-
Thanks tonyalbus for that tip. You would think the meter would tell you "turn both channels on". If it's in the manual, well, I not read the manual fully.
-
Yeah manuals who reads those :)
i agree, there should be some sort of message or they just need to switch the channels on.. its silly.
when i got the failed message, i was just thinking, what i did last and that was switching the channel off.
but in the back of my mind i was thinking, neah that can not be it, that would be stupid... but it was. :-DD
-
Software error, either inform me about it or turn on the channels.
Fnirsi doesn't win.
-
Software error, either inform me about it or turn on the channels.
Fnirsi doesn't win.
What does this mean?
-
When in the low ohms range, is there a REL setting to zero out ends of the probes?
-
That it can be easily fixed in the new firmware.
Fnirsi will also have similar problems in the firmware.
-
Was using the Zoyi to measure my 1833C LCR meter in measurements.
Oddly, the Zoyi is useless on scope side if it's not in Auto mode. As soon as you change the V or T scale, the scope prints wrong frequency number. It was reading 1833C 100Hz a-ok in Auto mode, I change the T scale to see more or less cycles on the screen and the freq counter goes goofy.
And yes, I even made sure trigger was good to get good stable waveform on the screen.
Maybe the fnirsi dpox180h will be better? Will test that when it arrives in a few days.
-
Received my 'real' zt-703s sample from Zotek i had teh SNAKOL version before
What i see it that the BOOT version is newer from Zotek.
The firmware can be updated, but the BOOT i dont know. it is maybe a hardware version.
The serial number is way newer also and even the box it comes in has iproved
it looks very nice now istead of the 702s box with a sticker saying its a 703s.
[attach=1]
[attach=2]
[attach=3]
-
Received my 'real' zt-703s sample from Zotek i had teh SNAKOL version before
What i see it that the BOOT version is newer from Zotek.
The firmware can be updated, but the BOOT i dont know. it is maybe a hardware version.
The serial number is way newer also and even the box it comes in has iproved
it looks very nice now istead of the 702s box with a sticker saying its a 703s.
(Attachment Link)
(Attachment Link)
(Attachment Link)
I would like to ask, is the zt-703s still worth using or not?
-
one page back you find my review, decide yourself.
i don't understand the question i think maybe
If you are still deciding 702s or 703s, than i would think go for 703s.
-
Received my 'real' zt-703s sample from Zotek i had teh SNAKOL version before
What i see it that the BOOT version is newer from Zotek.
The firmware can be updated, but the BOOT i dont know. it is maybe a hardware version.
The serial number is way newer also and even the box it comes in has iproved
it looks very nice now istead of the 702s box with a sticker saying its a 703s.
Interesting. I have the SNAKOL version too, with the same older 1.0.13 BOOT version as you. My serial starts with 003700 -- I'm not certain if that makes it older than your 003900 serial or not, but since the new one has a smaller number at 002F00 then either it's not meant to indicate sequence... or they're counting down. Mine is updated to the latest 1.2.7 firmware.
I definitely got the old style box, which was the same box for the 702S (and other Zoyi meters I have), not the more modern looking one you got this time.
So the question is, are there material differences in hardware and performance between the SNAKOL version and the newer one? Not that this is a serious instrument for me, it's more of a novelty to add to my growing collection, but I'm curious. And also annoyed if Zoyi released to market a grossly immature product instead of waiting just another month or two to release the final version. And is SNAKOL complicit in anything here? It did seem a bit shady that they were pre-selling for so long without calling it a pre-sale.
-
when one buy before official release date from non official zoyi store one can expect an early model. thats the risk one takes.
but luckily the firmware updates work also on the early models.
but yes i want to open both to see if there is an real hardware difference.
-
Being back home now (actually been back most of the week, but was busy with other stuff), I decided to check out some more things on the ZT-703S
I still have the original 1.0.9 firmware on mine.
When running in "High" mode, the frequencies output by the generator accessed from the menu (Menu -> left -> F4) are WRONG other than the 1khz probe compensation signal, which is actually correct. In any other output mode though, the frequencies are wrong.
5.0 kHz => is actually 7.0 kHz
2.0 kHz => is actually 2.8 kHz
1.0 kHz => is actually 1.4 kHz
etc etc (same scaling factor of 1.4 is present at all frequencies).
Oddly, using the "other apps -> Gen", the frequencies are correct
But in Sine output mode, it doesn't meet the 2.5Vpp claim at all (more like 2.0Vpp) and above 400kHz, the waveform is very triangular, not sinusoidal. Same can be said for any of the "partial sinusoidal" waveforms - they get very triangular and aren't very sinusoidal.
Going the other way and looking at a signal from an external generator, I see some peculiar aliasing too:
Feed in a 20Mhz sine wave, at 10, 25, and 50ns/div, things look pretty good and the frequency reads correctly. At 100ns/div, the frequency measurement is wrong (probably due to the overall bug at 100ns/div). From 250ns/div through 200us/div things look ok-ish - what you'd expect, the waveform getting more and more "solid" as the timebase is too slow to see any detail in the signal. At some timebases, there is some overall AM-ish distortion of the overall envelope though - definitely some kind of periodic noise, or some kind of aliasing showing up. Then suddenly at 500uS/div, it looks like a pure sinewave again, perfectly triggered and stable, at a much lower frequency, but the frequency measurement shows 0 as it can't measure anything. Definitely misleading if you're looking at an unknown signal and manually moving through timebases to have such an aliased signal appearing.
Comparing the same signal on the Owon HDS2202S, you get none of that at any timebase with the same 20MHz sine signal being fed in - there are some "sinusoidal-ish" aliased signals at very slow timebases on the Owon (5ms/div), but they're not triggered and stable, but rolling, giving a good indication that that's not the true signal, and just an aliasing / sampling artifact.
On an Agilent DSO-X 2024, there is no hint of aliasing or any waveform that resembles a "slower sine" at any timebase right up to and beyond 1S/div.
If you compare sampling rate at timebases, the Agilent scope is using a far higher sampling rate at every timebase compared to the Owon. The ZT-703S doesn't seem to indicate sampling rate vs timebase at all, so it's really hard to know what it's doing.
With the cheap price of the Zoyi, or even the Owon HDS series, and it being potentially many people's "first scopes", they definitely leave a lot of "traps for young players" as Dave would say...
I'm not sure if there's anything else anyone wants me to measure before I upgrade the firmware - turns out I don't currently have a working function generator above 20Mhz, except for potentially with an SDR, or with a VNA not sweeping, but set to a fixed frequency. The wavegen in the DSO-X 2024 only goes to 20Mhz, and my proper RF sig gen needs repairs.
-
Received my 'real' zt-703s sample from Zotek i had teh SNAKOL version before
What i see it that the BOOT version is newer from Zotek.
The firmware can be updated, but the BOOT i dont know. it is maybe a hardware version.
The serial number is way newer also and even the box it comes in has iproved
it looks very nice now istead of the 702s box with a sticker saying its a 703s.
My 703 from snakol came in a box that shows and says "3-in-1 dual-channel" on face of box, and, the pic used appears to be the 703S ("25000 counts", etc) but the actual model on the pic is not there, but duly noted the side of the box has two models listed as check-boxes, 702 and 703, and the 703 is marked on my box. There's no "703S" sticker on a 702 box.
The 703 I got has boot v1.0.14, but I am not sure the boot version matters too much.
So it does appear the 703 I got from snakol was the latest from Zoyi when snakol shipped to me. Earlier 703's were likely just being rushed out using 1st rev firmware stuff and 702 boxing, but I don't suspect the actual 703 hardware is any different.
-
Being back home now (actually been back most of the week, but was busy with other stuff), I decided to check out some more things on the ZT-703S
I still have the original 1.0.9 firmware on mine.
When running in "High" mode, the frequencies output by the generator accessed from the menu (Menu -> left -> F4) are WRONG other than the 1khz probe compensation signal, which is actually correct. In any other output mode though, the frequencies are wrong.
5.0 kHz => is actually 7.0 kHz
2.0 kHz => is actually 2.8 kHz
1.0 kHz => is actually 1.4 kHz
etc etc (same scaling factor of 1.4 is present at all frequencies).
Well, "1.4" sounds like a math mistake in the old code.
Testing on the old FW is good for reference only.
Upgrade to the v1.2.7 FW and see what changes.
-
I did get fnirsi depox180h today.
Have to say, the 180h is like the light in light-&-day vs the scope of the Zoyi.
Didn't need instructions manual to learn the menu's, 10min of just pushing buttons, and now super ez to use it. Hidden menu's? Not sure yet.
Out of the box, no idea about FW versions, all the functions seems to work ok. BNC's twist on and lock, unlike Zoyi.
Signal gen a-ok up to 20MHz, and there's like ~8 or so signal profiles to choose from, and you can dial in the freq one digit at a time.
The one item of interest for me on the 180h, is the FFT. I need to test it some to see if it reads harmonics ok, but having FFT in a small handheld is something I have been looking for.
Now just need to Zo-tek folks to fix the bugs in the 702/703 FW.
-
Being back home now (actually been back most of the week, but was busy with other stuff), I decided to check out some more things on the ZT-703S
I still have the original 1.0.9 firmware on mine.
When running in "High" mode, the frequencies output by the generator accessed from the menu (Menu -> left -> F4) are WRONG other than the 1khz probe compensation signal, which is actually correct. In any other output mode though, the frequencies are wrong.
5.0 kHz => is actually 7.0 kHz
2.0 kHz => is actually 2.8 kHz
1.0 kHz => is actually 1.4 kHz
etc etc (same scaling factor of 1.4 is present at all frequencies).
Oddly, using the "other apps -> Gen", the frequencies are correct
But in Sine output mode, it doesn't meet the 2.5Vpp claim at all (more like 2.0Vpp) and above 400kHz, the waveform is very triangular, not sinusoidal. Same can be said for any of the "partial sinusoidal" waveforms - they get very triangular and aren't very sinusoidal.
Going the other way and looking at a signal from an external generator, I see some peculiar aliasing too:
Feed in a 20Mhz sine wave, at 10, 25, and 50ns/div, things look pretty good and the frequency reads correctly. At 100ns/div, the frequency measurement is wrong (probably due to the overall bug at 100ns/div). From 250ns/div through 200us/div things look ok-ish - what you'd expect, the waveform getting more and more "solid" as the timebase is too slow to see any detail in the signal. At some timebases, there is some overall AM-ish distortion of the overall envelope though - definitely some kind of periodic noise, or some kind of aliasing showing up. Then suddenly at 500uS/div, it looks like a pure sinewave again, perfectly triggered and stable, at a much lower frequency, but the frequency measurement shows 0 as it can't measure anything. Definitely misleading if you're looking at an unknown signal and manually moving through timebases to have such an aliased signal appearing.
Comparing the same signal on the Owon HDS2202S, you get none of that at any timebase with the same 20MHz sine signal being fed in - there are some "sinusoidal-ish" aliased signals at very slow timebases on the Owon (5ms/div), but they're not triggered and stable, but rolling, giving a good indication that that's not the true signal, and just an aliasing / sampling artifact.
On an Agilent DSO-X 2024, there is no hint of aliasing or any waveform that resembles a "slower sine" at any timebase right up to and beyond 1S/div.
If you compare sampling rate at timebases, the Agilent scope is using a far higher sampling rate at every timebase compared to the Owon. The ZT-703S doesn't seem to indicate sampling rate vs timebase at all, so it's really hard to know what it's doing.
With the cheap price of the Zoyi, or even the Owon HDS series, and it being potentially many people's "first scopes", they definitely leave a lot of "traps for young players" as Dave would say...
I'm not sure if there's anything else anyone wants me to measure before I upgrade the firmware - turns out I don't currently have a working function generator above 20Mhz, except for potentially with an SDR, or with a VNA not sweeping, but set to a fixed frequency. The wavegen in the DSO-X 2024 only goes to 20Mhz, and my proper RF sig gen needs repairs.
I think it did say in the manual not to use high mode below 30 MHZ or something?
-
customer review from Snakalstore:
....................
Additional feedback
28 Jan 2024
For information, Snakal Global Store and Snakal Instruments Store are the same seller with the same legal details.
-
Snakol == Snake Oil? :-DD
-
Has anyone tried the newest v1.28 FW update available on Zotek's website? http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
-
Has anyone tried the newest v1.28 FW update available on Zotek's website? http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
Has anyone tried it yet? And how does it compare to the previous version?
-
Has anyone tried the newest v1.28 FW update available on Zotek's website? http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
When I went to this site my antivirus program gave a virus warning.
So I'm not going to try it out...
-
Has anyone tried the newest v1.28 FW update available on Zotek's website? http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
When I went to this site my antivirus program gave a virus warning.
So I'm not going to try it out...
According to this
I'd like you to try and see how different it is from the previous version. Please help me explain.
-
Sorry for that. I have CrowdStrike Falcon on my PC and there was no alert for me, so I've downloaded the file and uploaded it to Virustotal. There's no harmful code detected, see attached picture. Unfortunately I cannot attach a .ztk file here, so I cannot share it.
Here are the checksums.
MD5: c95adc5abc8818221ccb45ccf80c4d8c
SHA-1: f10f17f20781f71f17ca3900403fda2db85ddcef
SHA-256: 836bfce13c9a509245e420a4008a0e6eb15909e5438cbce082432ce7da3d3d1a
SSDEEP: 12288:M20rqJdjWNGP/JOpKUaThf6je9sLNIQsvYlyzbTRzaDic:V7V8K1Tp6je26Qsv9Hgic
TLSH: T171D4AE4F2F1D1EFDB06E0D155FB861B089692A101E8970BAF14983B87D9ACB366714CF
File type: unknown
Magic: data
File size: 625.19 KB (640192 bytes)
fILE NAME: ZOYI-703S-FW-V128.ZTK
-
You can attach a zipped version of the ztk file.
-
There you go mate
-
You can attach a zipped version of the ztk file.
I put a Zip up for you mate.
Not for me as I don't have one of those Zoyis but I see that already at least someone else might be grateful.
-
Has anyone tried the newest v1.28 FW update available on Zotek's website? http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
How come it now says that page does not exist?
-
Has anyone tried the newest v1.28 FW update available on Zotek's website? http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
How come it now says that page does not exist?
It's because of the bad website. of the company has not been updated It's older than Google Chrome. Makes the user enter the website and get an error. The only way you can enter is with Brave or Fire Fox.
Or whoever enters for the first time, a pop-up will ask you to choose a language. Please don't choose English. Leave it like that.
-
Has anyone tried the newest v1.28 FW update available on Zotek's website? http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
How come it now says that page does not exist?
It's because of the bad website. of the company has not been updated It's older than Google Chrome. Makes the user enter the website and get an error. The only way you can enter is with Brave or Fire Fox.
Or whoever enters for the first time, a pop-up will ask you to choose a language. Please don't choose English. Leave it like that.
Hi, Thank you. Have you any idea what they have updated?
-
Has anyone tried the newest v1.28 FW update available on Zotek's website? http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
How come it now says that page does not exist?
It's because of the bad website. of the company has not been updated It's older than Google Chrome. Makes the user enter the website and get an error. The only way you can enter is with Brave or Fire Fox.
Or whoever enters for the first time, a pop-up will ask you to choose a language. Please don't choose English. Leave it like that.
Hi, Thank you. Have you any idea what they have updated?
I don't know because I don't have this model. I'd like to know as well.
-
Well be aware, Avast is giving me:[attach=1]
-
Well be aware, Avast is giving me: (Attachment Link)
According to this
-
Well be aware, Avast is giving me: (Attachment Link)
But user attached the 128 as a zip, so just grab that (a zip on eevb).
I was able to download from site, I also grabbed the zip. Same hash for ztk file. Did not install it yet.
Btw, if your own machine has malware software that blocks url's, you can always try to grab stuff from online tools, like reqbin site.
-
That szzotek.com link looks highly suspicious to me. Zotek's official website is zotektools.com. And whois shows they've anonymized their domain registration -- not that that alone is red flag, many legit business use a private registrar, as do I, but in light of all the other red flags it doesn't help with credibility. I'd suggest caution.
└─$ whois szzotek.com
Domain Name: SZZOTEK.COM
Registry Domain ID: 2009928071_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.paycenter.com.cn
Registrar URL: http://www.xinnet.com
Updated Date: 2024-01-23T07:52:25Z
Creation Date: 2016-03-07T04:18:09Z
Registry Expiry Date: 2028-03-07T04:18:09Z
Registrar: Xin Net Technology Corporation
Registrar IANA ID: 120
Registrar Abuse Contact Email: supervision@xinnet.com
Registrar Abuse Contact Phone: +86.4008182233
Domain Status: ok [url]https://icann.org/epp#ok[/url]
Name Server: NS1.ALIDNS.COM
Name Server: NS2.ALIDNS.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: [url]https://www.icann.org/wicf/[/url]
>>> Last update of whois database: 2024-02-03T21:45:33Z <<<
For more information on Whois status codes, please visit [url]https://icann.org/epp[/url]
NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.
TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.
The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.
Domain Name: szzotek.com
Registry Domain ID: 2009928071_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.paycenter.com.cn
Registrar URL: http://www.xinnet.com
Updated Date: 2024-01-23T07:52:25Z
Creation Date: 2016-03-06T16:00:00Z
Registrar Registration Expiration Date: 2028-03-06T16:00:00Z
Registrar: Xin Net Technology Corporation
Registrar IANA ID: 120
Registrar Abuse Contact Email: supervision@xinnet.com
Registrar Abuse Contact Phone: +86.4008182233
Reseller:
Domain Status: ok [url]https://www.icann.org/epp#ok[/url]
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: GD
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: CN
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: link at http://whois.xinnet.com/sendemail/szzotek.com
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin PostalCode: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: link at http://whois.xinnet.com/sendemail/szzotek.com
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech PostalCode: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: link at http://whois.xinnet.com/sendemail/szzotek.com
Name Server: ns1.alidns.com
Name Server: ns2.alidns.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-02-03T21:45:55Z <<<
For more information on Whois status codes, please visit [url]https://icann.org/epp[/url]
The Data in Paycenter's WHOIS database is provided by Paycenter
for information purposes, and to assist persons in obtaining
information about or related to a domain name registration record.
Paycenter does not guarantee its accuracy. By submitting
a WHOIS query, you agree that you will use this Data only
for lawful purposes and that,
under no circumstances will you use this Data to:
(1) allow, enable, or otherwise support the transmission
of mass unsolicited, commercial advertising or solicitations
via e-mail (spam); or
(2) enable high volume, automated, electronic processes that
apply to Paycenter or its systems.
Paycenter reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by this policy.!!
-
That szzotek.com link looks highly suspicious to me. Zotek's official website is zotektools.com. And whois shows they've anonymized their domain registration -- not that that alone is red flag, many legit business use a private registrar, as do I, but in light of all the other red flags it doesn't help with credibility. I'd suggest caution.
└─$ whois szzotek.com
Domain Name: SZZOTEK.COM
Registry Domain ID: 2009928071_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.paycenter.com.cn
Registrar URL: http://www.xinnet.com
Updated Date: 2024-01-23T07:52:25Z
Creation Date: 2016-03-07T04:18:09Z
Registry Expiry Date: 2028-03-07T04:18:09Z
Registrar: Xin Net Technology Corporation
Registrar IANA ID: 120
Registrar Abuse Contact Email: supervision@xinnet.com
Registrar Abuse Contact Phone: +86.4008182233
Domain Status: ok [url]https://icann.org/epp#ok[/url]
Name Server: NS1.ALIDNS.COM
Name Server: NS2.ALIDNS.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: [url]https://www.icann.org/wicf/[/url]
>>> Last update of whois database: 2024-02-03T21:45:33Z <<<
For more information on Whois status codes, please visit [url]https://icann.org/epp[/url]
NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.
TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.
The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.
Domain Name: szzotek.com
Registry Domain ID: 2009928071_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.paycenter.com.cn
Registrar URL: http://www.xinnet.com
Updated Date: 2024-01-23T07:52:25Z
Creation Date: 2016-03-06T16:00:00Z
Registrar Registration Expiration Date: 2028-03-06T16:00:00Z
Registrar: Xin Net Technology Corporation
Registrar IANA ID: 120
Registrar Abuse Contact Email: supervision@xinnet.com
Registrar Abuse Contact Phone: +86.4008182233
Reseller:
Domain Status: ok [url]https://www.icann.org/epp#ok[/url]
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: GD
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: CN
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: link at http://whois.xinnet.com/sendemail/szzotek.com
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin PostalCode: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: link at http://whois.xinnet.com/sendemail/szzotek.com
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech PostalCode: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: link at http://whois.xinnet.com/sendemail/szzotek.com
Name Server: ns1.alidns.com
Name Server: ns2.alidns.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-02-03T21:45:55Z <<<
For more information on Whois status codes, please visit [url]https://icann.org/epp[/url]
The Data in Paycenter's WHOIS database is provided by Paycenter
for information purposes, and to assist persons in obtaining
information about or related to a domain name registration record.
Paycenter does not guarantee its accuracy. By submitting
a WHOIS query, you agree that you will use this Data only
for lawful purposes and that,
under no circumstances will you use this Data to:
(1) allow, enable, or otherwise support the transmission
of mass unsolicited, commercial advertising or solicitations
via e-mail (spam); or
(2) enable high volume, automated, electronic processes that
apply to Paycenter or its systems.
Paycenter reserves the right to modify these terms at any time.
By submitting this query, you agree to abide by this policy.!!
http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
http://www.szzotek.com/h-col-101.html (http://www.szzotek.com/h-col-101.html)
http://www.szzotek.com/h-col-170.html (http://www.szzotek.com/h-col-170.html)
According to this
-
Has anyone updated? How is it? How is it different from .127? Please help me explain.
-
http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
http://www.szzotek.com/h-col-101.html (http://www.szzotek.com/h-col-101.html)
http://www.szzotek.com/h-col-170.html (http://www.szzotek.com/h-col-170.html)
According to this
"According to this" what?
You still don't address the fact that these are non-TLS links pointing to what appears to be a non-official Zotek website that trips people's malware software left and right.
EDIT: I see that if you choose the English site at the top of the home page, it does take you to zotektools.com. That alone doesn't guarantee legitimacy, but looks better. BTW the links you posted don't work for me.
-
http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
http://www.szzotek.com/h-col-101.html (http://www.szzotek.com/h-col-101.html)
http://www.szzotek.com/h-col-170.html (http://www.szzotek.com/h-col-170.html)
According to this
"According to this" what?
You still don't address the fact that these are non-TLS links pointing to what appears to be a non-official Zotek website that trips people's malware software left and right.
EDIT: I see that if you choose the English site at the top of the home page, it does take you to zotektools.com. That alone doesn't guarantee legitimacy, but looks better. BTW the links you posted don't work for me.
I'm sorry. I don't know a single thing about what it is. Or is it a virus?
-
http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
http://www.szzotek.com/h-col-101.html (http://www.szzotek.com/h-col-101.html)
http://www.szzotek.com/h-col-170.html (http://www.szzotek.com/h-col-170.html)
According to this
"According to this" what?
You still don't address the fact that these are non-TLS links pointing to what appears to be a non-official Zotek website that trips people's malware software left and right.
EDIT: I see that if you choose the English site at the top of the home page, it does take you to zotektools.com. That alone doesn't guarantee legitimacy, but looks better. BTW the links you posted don't work for me.
szzotek.com is suspicious, to say the least.
Now the webpage shows the 703s, that's odd.
Also, the fqdn has no 'A' records in DNS, just a CNAME to a host at faipod.com
ICANN has santioned that registrar Xin Net Technologies many times.
Why szzotek.com loads a ton of javascript from various "fai" urls is red flag for sure, for just posting links for some downloads.
You can see all this using the DIG online tool, lookup CNAME for the szzotek site, and, use Cloudflare Radar Scan to get all the details of the full URL's (webpage URI's) the user here posted.
-
I haven't installed the new software yet but I was using the 703S yesterday and I noticed that no matter what I set on the display menu tab, even if I set it to off, the display switches off at what appears to be the same period of time, I don't want it to switch off at all! most annoying when I am working on the bench, just in the middle of a measurement and the damn thing goes off!
-
I haven't installed the new software yet but I was using the 703S yesterday and I noticed that no matter what I set on the display menu tab, even if I set it to off, the display switches off at what appears to be the same period of time, I don't want it to switch off at all! most annoying when I am working on the bench, just in the middle of a measurement and the damn thing goes off!
As a rule for forums, please always list the FW #, because "new" changes day by day.
Was it the v128 from the suspect website, or v127 from official site?
I have 703 on v127. Goto scope, change output signal to sine (should just default to 5kHz), exit out and hit Auto, it basically crashes.
I not even sure why, when you turn off ch2 and you have signal on ch1, pressing Auto activates ch2 while it combs the freq to find best volt & time scales.
v127 seems to be problematic on the scope side of the code.
-
I haven't installed the new software yet but I was using the 703S yesterday and I noticed that no matter what I set on the display menu tab, even if I set it to off, the display switches off at what appears to be the same period of time, I don't want it to switch off at all! most annoying when I am working on the bench, just in the middle of a measurement and the damn thing goes off!
I cannot tell which menu item you are claiming to be changing. The two that I know of are the "BL time" setting in the oscilloscope menus and the "auto off" time in either set of menus. If those are all set the way you want them, I would probably do a "format" then a "default" and see if it behaves correctly after that.
-
If anyone orders the kit with the 703 plus two probes, take care when unpacking. For mine they just taped the bag with the extra probe to the front of the box containing the instrument, then coated the whole thing in tape and bubble wrap. One snip of the scissors and I now own a 6 piece oscilloscope probe cable.
-
If anyone orders the kit with the 703 plus two probes, take care when unpacking. For mine they just taped the bag with the extra probe to the front of the box containing the instrument, then coated the whole thing in tape and bubble wrap. One snip of the scissors and I now own a 6 piece oscilloscope probe cable.
In conclusion, what is it? Or are the scissors cutting the cable damaged?
-
> In conclusion, what is it? Or are the scissors cutting the cable damaged?
I cut the cable in several places while removing the bubble wrap. Not their fault, I should have been more careful. Though the second probe being outside of the box was unexpected.
-
> In conclusion, what is it? Or are the scissors cutting the cable damaged?
I cut the cable in several places while removing the bubble wrap. Not their fault, I should have been more careful. Though the second probe being outside of the box was unexpected.
I would like to express my condolences. Next time please use just a knife.:palm: :palm: :scared: :-[
-
I haven't installed the new software yet but I was using the 703S yesterday and I noticed that no matter what I set on the display menu tab, even if I set it to off, the display switches off at what appears to be the same period of time, I don't want it to switch off at all! most annoying when I am working on the bench, just in the middle of a measurement and the damn thing goes off!
I cannot tell which menu item you are claiming to be changing. The two that I know of are the "BL time" setting in the oscilloscope menus and the "auto off" time in either set of menus. If those are all set the way you want them, I would probably do a "format" then a "default" and see if it behaves correctly after that.
I did say it switches off after the same period of time so I guess it's the Auto off?
-
I haven't installed the new software yet but I was using the 703S yesterday and I noticed that no matter what I set on the display menu tab, even if I set it to off, the display switches off at what appears to be the same period of time, I don't want it to switch off at all! most annoying when I am working on the bench, just in the middle of a measurement and the damn thing goes off!
As a rule for forums, please always list the FW #, because "new" changes day by day.
Was it the v128 from the suspect website, or v127 from official site?
I have 703 on v127. Goto scope, change output signal to sine (should just default to 5kHz), exit out and hit Auto, it basically crashes.
I not even sure why, when you turn off ch2 and you have signal on ch1, pressing Auto activates ch2 while it combs the freq to find best volt & time scales.
v127 seems to be problematic on the scope side of the code.
The post is not about the firmware! and there is only 128 at the moment, it's about Auto shut of control.
-
If anyone orders the kit with the 703 plus two probes, take care when unpacking. For mine they just taped the bag with the extra probe to the front of the box containing the instrument, then coated the whole thing in tape and bubble wrap. One snip of the scissors and I now own a 6 piece oscilloscope probe cable.
I did, but at least my second probe was thrown inside the box next to the box the 703S was in! Sorry to hear your ended up being damaged.
-
If anyone orders the kit with the 703 plus two probes, take care when unpacking. For mine they just taped the bag with the extra probe to the front of the box containing the instrument, then coated the whole thing in tape and bubble wrap. One snip of the scissors and I now own a 6 piece oscilloscope probe cable.
I did, but at least my second probe was thrown inside the box next to the box the 703S was in! Sorry to hear your ended up being damaged.
Same with mine. 703 box and a probe in bag next to the 703 box.
I assume the box is same size for the 702 and it can't accomodate a 2nd probe, so instead of re-doing packaging for the 703 they just toss in an extra probe. In a world of save-money, makes sense.
-
I haven't installed the new software yet but I was using the 703S yesterday and I noticed that no matter what I set on the display menu tab, even if I set it to off, the display switches off at what appears to be the same period of time, I don't want it to switch off at all! most annoying when I am working on the bench, just in the middle of a measurement and the damn thing goes off!
As a rule for forums, please always list the FW #, because "new" changes day by day.
Was it the v128 from the suspect website, or v127 from official site?
I have 703 on v127. Goto scope, change output signal to sine (should just default to 5kHz), exit out and hit Auto, it basically crashes.
I not even sure why, when you turn off ch2 and you have signal on ch1, pressing Auto activates ch2 while it combs the freq to find best volt & time scales.
v127 seems to be problematic on the scope side of the code.
The post is not about the firmware! and there is only 128 at the moment, it's about Auto shut of control.
v128 from where?
Zotek site only has v127 for download, at the moment.
https://zotektools.com/firmware-update-703/ ------> https://drive.google.com/file/d/1j5GLloua8nbk5bFO4p7Zw5z5m3VUuqUF/view
-
New video:
https://www.eevblog.com/2024/02/07/eevblog-1597-zoyi-zt-703s-80-2ch-50mhz-oscilloscope-multimeter-review/ (https://www.eevblog.com/2024/02/07/eevblog-1597-zoyi-zt-703s-80-2ch-50mhz-oscilloscope-multimeter-review/)
I still think a DSO2512G plus an AN870 offers more bang for the buck.
-
I haven't installed the new software yet but I was using the 703S yesterday and I noticed that no matter what I set on the display menu tab, even if I set it to off, the display switches off at what appears to be the same period of time, I don't want it to switch off at all! most annoying when I am working on the bench, just in the middle of a measurement and the damn thing goes off!
As a rule for forums, please always list the FW #, because "new" changes day by day.
Was it the v128 from the suspect website, or v127 from official site?
I have 703 on v127. Goto scope, change output signal to sine (should just default to 5kHz), exit out and hit Auto, it basically crashes.
I not even sure why, when you turn off ch2 and you have signal on ch1, pressing Auto activates ch2 while it combs the freq to find best volt & time scales.
v127 seems to be problematic on the scope side of the code.
The post is not about the firmware! and there is only 128 at the moment, it's about Auto shut of control.
v128 from where?
Zotek site only has v127 for download, at the moment.
https://zotektools.com/firmware-update-703/ ------> https://drive.google.com/file/d/1j5GLloua8nbk5bFO4p7Zw5z5m3VUuqUF/view
See posts from naiclub on page 10, all I did was convert it to .zip
-
Review by EEVblog member Defpom.
Looks like he tested it with an old firmware version (1.1.0) so
some/most of the bugs he found may may be fixed in newer
updates.
https://youtu.be/MD0IkgcyF0o
-
I haven't installed the new software yet but I was using the 703S yesterday and I noticed that no matter what I set on the display menu tab, even if I set it to off, the display switches off at what appears to be the same period of time, I don't want it to switch off at all! most annoying when I am working on the bench, just in the middle of a measurement and the damn thing goes off!
As a rule for forums, please always list the FW #, because "new" changes day by day.
Was it the v128 from the suspect website, or v127 from official site?
I have 703 on v127. Goto scope, change output signal to sine (should just default to 5kHz), exit out and hit Auto, it basically crashes.
I not even sure why, when you turn off ch2 and you have signal on ch1, pressing Auto activates ch2 while it combs the freq to find best volt & time scales.
v127 seems to be problematic on the scope side of the code.
The post is not about the firmware! and there is only 128 at the moment, it's about Auto shut of control.
v128 from where?
Zotek site only has v127 for download, at the moment.
https://zotektools.com/firmware-update-703/ ------> https://drive.google.com/file/d/1j5GLloua8nbk5bFO4p7Zw5z5m3VUuqUF/view
See posts from naiclub on page 10, all I did was convert it to .zip
I still not following.
V127 is the latest available from Zotek site.
-
So DefPom reviewed a device with 1.1.0, but the latest is 1.1.127? Why would they send such an old version - were they getting rid of old protoypes/test devices?
-
Reviewers and online influencers often get pre-release/prototype models well in advance of GA. Dave just posted a video reviewing the ZT-703S and comparing to the ZT-702S -- his 702S was an early preview model and he managed to brick it by trying to flash it to the current firmware, which it apparently wasn't compatible with.
-
Reviewers and online influencers often get pre-release/prototype models well in advance of GA. Dave just posted a video reviewing the ZT-703S and comparing to the ZT-702S -- his 702S was an early preview model and he managed to brick it by trying to flash it to the current firmware, which it apparently wasn't compatible with.
Yeah I saw that. I don't get why they would ship defective products; I guess they assume enough people will just buy them anyway so it doesn't matter if they get negative reviews.
Edit: I was tempted to get a 702s after watching several reviews.
-
Reviewers and online influencers often get pre-release/prototype models well in advance of GA. Dave just posted a video reviewing the ZT-703S and comparing to the ZT-702S -- his 702S was an early preview model and he managed to brick it by trying to flash it to the current firmware, which it apparently wasn't compatible with.
I don't understand the point of the company sending an old prototype to someone for a review, they are guaranteed to get a bad write-up because there will be problems with it, and Bricking when you try to do a firmware update is the worst kind of review, everyone will be afraid to do updates!
-
So DefPom reviewed a device with 1.1.0, but the latest is 1.1.127? Why would they send such an old version - were they getting rid of old protoypes/test devices?
no. from the actual FW code, its "V1.2.7"
v127 for short.
Sorry for that confusion.
The latest being shipped appears to be BOOT: V1.0.14 with APP V1.2.7
The latest available is from Zotek wesbite, the links I already posted.
-
So DefPom reviewed a device with 1.1.0, but the latest is 1.1.127? Why would they send such an old version - were they getting rid of old protoypes/test devices?
no. from the actual FW code, its "V1.2.7"
v127 for short.
Sorry for that confusion.
The latest being shipped appears to be BOOT: V1.0.14 with APP V1.2.7
The latest available is from Zotek wesbite, the links I already posted.
Ah, thanks for the clarification. I wasn't sure what 127 was. ;D
-
Ah, thanks for the clarification. I wasn't sure what 127 was. ;D
But you went to the Zotek site to see the latest FW available, yes?
-
My 703S bought at https://thedmm.com/ just came in
It has Boot:V1.0.15, App:V1.2.8
(I've sold my 702S)
-
My 703S bought at https://thedmm.com/ just came in
It has Boot:V1.0.15, App:V1.2.8
(I've sold my 702S)
I waiting on Zoyi support to respond to me about v1.2.8
Odd the unit is shipping with 128 but only 127 available for download.
I wonder if v128 is tied to the 1.0.15 boot, my 703 came with v127 and v1.0.14 boot.
-
I will send an email to Tim from the ddmm.Com and report
back.
-
Is the 703s signal generator good enough for 10x probe calibration using square wave at 1kHz with latest firmware?
-
Yes, it is (although you cannot calibrate the 703S itself using the signal generator (for that, you have the use the square wave at the output).
Is the 703s signal generator good enough for 10x probe calibration using square wave at 1kHz with latest firmware?
-
I can confirm that V1.2.7 works with boot V1.0.15.
Then, I tried to upgrade using V1.2.8 on page 10.
Havoc did arise: the scope said updating and restarted.
After that, the initial screen was flashing on/off, and the scope wouldn't turn off.
I had to open the scope, remove the battery, wait for some seconds, reinstall V1.2.7 (by using F1+power on, exit F2), and reinstall V1.2.8 (all while on USB and battery removed).
The 703s is working again, phew.
-
Hello ;)
Does anyone know the changelog for v1.2.8 ?
Also i have boot 1.0.15
-
I can confirm that V1.2.7 works with boot V1.0.15.
Then, I tried to upgrade using V1.2.8 on page 10.
Havoc did arise: the scope said updating and restarted.
After that, the initial screen was flashing on/off, and the scope wouldn't turn off.
I had to open the scope, remove the battery, wait for some seconds, reinstall V1.2.7 (by using F1+power on, exit F2), and reinstall V1.2.8 (all while on USB and battery removed).
The 703s is working again, phew.
Yeah, I think this is why most are waiting for updates from the Zotek (Zoyi) website.
I still not seen procedure to update boot rom code. Boot v1.1.14 may not be compatible with some unknown App v1.2.8
-
By how many screens can the signal be shifted? How long can I view the course of the signal?
-
(I still can't sell zoyi702, no one is interested)
-
(I still can't sell zoyi702, no one is interested)
Why would anyone want it when 703S is available?
-
(I still can't sell zoyi702, no one is interested)
Why would anyone want it when 703S is available?
Why would anyone want a 703S? :-DD
It's all a question of price.
-
... or a scope in the form of a multimeter with a rudimentary x-y functionality.
-
Just ordered one after watching the view. While not a super scope; it's imo great to have a portable isolated (cause battery operated) one for on the side. It's like those €5,- multi-meters. Always nice to have 1 or 2 to just have.
I got a MSO5k for my other hobby stuff, that I turn on at least 4 times a year :p
But again, being able to measure without having to worry about shortening anything to ground is still pretty cool. And the portable aspect! For those needs, it's great. I must admit though, I am disappointment they only supplied a single probe :( Even for that price, they could have put in two in the box. Found out they have 'options' when ordering to get a two probe one, so canceled and reordered. Lets see. Still for €90,- it's a nice toy to have in the box.
-
Just ordered one after watching the view. While not a super scope; it's imo great to have a portable isolated (cause battery operated) one for on the side. It's like those €5,- multi-meters. Always nice to have 1 or 2 to just have.
I got a MSO5k for my other hobby stuff, that I turn on at least 4 times a year :p
But again, being able to measure without having to worry about shortening anything to ground is still pretty cool. And the portable aspect! For those needs, it's great. I must admit though, I am disappointment they only supplied a single probe :( Even for that price, they could have put in two in the box. Found out they have 'options' when ordering to get a two probe one, so canceled and reordered. Lets see. Still for €90,- it's a nice toy to have in the box.
Hi Olly, Exactly, I have a 500mhz 4 input Rigol on the bench, but for a quick look at something away from the bench it's ideal. I find some of the comments I have seen quite incredible, people expect the Earth for £75 or whatever, it's like when you sell a second-hand car fairly cheap and the buyer goes over every inch complaining about a little scratch here and a little dent there. I always say, Oh! you expected a brand new top of the range car for £800! You get what you pay for, especially in electronics, and I think for the price it's wonderful. Yes you will get the second probe thrown in the box beside the little box the scope/meter comes in so be careful when you open it.
-
Any word when v1.2.8 will be available from Zoyi site?
-
anyone was able to figure out how to turn off sounds yet? When changing mode, it beeps like hell - I hate that stuff.
-
I have updated the firmware using v1.2.8 from the szzotek.com website and it works well on my unit (boot v1.0.15) although I still cannot tell what is changed in this version :)
If someone from Zotek is reading this: PLEASE put in an option to mute the beeps and bring back the temperature reading!!! We will supply our own thermocouples!
-
Now is there a solution to the issue of measuring pairs of scopes? Has anyone tried it yet?
-
Im having the same issue with calibration, Check Failure. Did you fpund any solution?
-
Im having the same issue with calibration, Check Failure. Did you fpund any solution?
turn both channels on and do the calibration.
-
Im having the same issue with calibration, Check Failure. Did you fpund any solution?
Make a scope that can measure pairs. But why can only measure 1 channel? You are definitely deceiving consumers.
-
Well people forget that one channel is off. Plus this is my first scope so im not a pro.
-
Well people forget that one channel is off. Plus this is my first scope so im not a pro.
The firmware is bizarre in that regard.
If I hit "cal" then the code "should" prompt you with something like "disconnect all channels, then press MENU to continue", and then from there the cal code does it's thing, and it should turn on both channels at the start of it's routine.
That's what the code "should" do, but it's not coded that way.
Did Zoyi post up v1.2.8 code yet?
-
No. Latest version i could download from zotektools.com is ZOYI-703S-FW-V127(1).ZTK
-
The laser-wiped multimeter chipset in the ZT-703S could be a DTM0660L - at least it seems to have an identical pinout (see below). But there is no indication in the datasheet about 25000 counts capability. The SZ20 from Aneng also uses the DTM0660 and also claims 25000 counts:
https://www.eevblog.com/forum/testgear/aneng-goes-crazy-with-new-meters/msg4773944/#msg4773944 (https://www.eevblog.com/forum/testgear/aneng-goes-crazy-with-new-meters/msg4773944/#msg4773944)
(Aneng SZ20 probably aka Zoyi ZT-225, also 25000 counts)
Anyone familiar with this? Is there a special version of the DTM0660 with higher resolution or is it done with interpolation?
Datasheet DTM0660: https://drive.google.com/file/d/0B6fbSrbAyU1lUlhBQXY3bS1RLU0/view?resourcekey=0-j-BXh9QdU7HVI-Wgu3Gpew (https://drive.google.com/file/d/0B6fbSrbAyU1lUlhBQXY3bS1RLU0/view?resourcekey=0-j-BXh9QdU7HVI-Wgu3Gpew)
English translation: http://www.kerrywong.com/blog/wp-content/uploads/2016/04/DTM0660DataSheet.pdf (http://www.kerrywong.com/blog/wp-content/uploads/2016/04/DTM0660DataSheet.pdf)
Not important, I am just curious.
-
Did Zoyi post up v1.2.8 code yet?
No. Latest version i could download from zotektools.com is ZOYI-703S-FW-V127(1).ZTK
As was posted previously, 1.2.8 is available from the szzotek.com site, which is the Chinese language site for Zotek.
http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
-
V1.2.9 update content
1. Fixed the problem that when switching to multimeter mode, pressing F1 to F4 will cause the measurement items and the interface UI to be out of sync.
2. Optimize frequency measurement. When the frequency cannot be measured, the frequency value will become "--.--".
3. Optimize the AUTO strategy, which is faster and more accurate in identification.
4. Fix the problem that the frequency and time base are sometimes inaccurate in high-speed mode.
5. Fix the problem that the signal generator outputs an incorrect frequency in high-speed mode.
6. Fix the possibility that the U disk cannot be opened when FLASH prompts that there is insufficient memory.
-
Did Zoyi post up v1.2.8 code yet?
No. Latest version i could download from zotektools.com is ZOYI-703S-FW-V127(1).ZTK
As was posted previously, 1.2.8 is available from the szzotek.com site, which is the Chinese language site for Zotek.
http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
But why is it not on the regualt Zoyi site?
Even the domain registration info for szzotek is odd.
-
But why is it not on the regualt Zoyi site?
Even the domain registration info for szzotek is odd.
It's behind a private registry service, just like the western zotektools.com site, just a different one. That by itself isn't that uncommon (most of my domains are behind private registrars), although I would expect most legitimate businesses to expose their domain contacts. I was skeptical of szzotek too when it was first mentioned (pretty sure in this thread) and suggested caution, but did some digging and came to conclusion it was legitimately their China-facing site. If you answer the prompt about English, it actually redirects you to the zotektools site.
Many Chinese equipment manufacturers have different internally-facing sites. Also some of them (e.g. Rigol) will post firmware updates to some sites and not others. So this really isn't that unusual.
On a loosely related note, Darren Walker had a Zotek rep on his YT channel a week or so ago when he was unboxing the 703S and asked her about the Zoyi vs Zotek distinction. We all knew they were the same company, but she clarified that Zotek is the western facing brand while Zoyi is the internal to China/Asia brand. She said they weren't allowed to market as Zoyi outside of China, so adopted the name Zotek. She didn't explain why, I assume for trademark or other reasons.
-
I know its to much to ask for this but can this scope measure signal noise and ripple to some degree? For example on a atx power supply. If yes whats the best configuration in settings for this purpose?
-
V1.2.9 update content
1. Fixed the problem that when switching to multimeter mode, pressing F1 to F4 will cause the measurement items and the interface UI to be out of sync.
2. Optimize frequency measurement. When the frequency cannot be measured, the frequency value will become "--.--".
3. Optimize the AUTO strategy, which is faster and more accurate in identification.
4. Fix the problem that the frequency and time base are sometimes inaccurate in high-speed mode.
5. Fix the problem that the signal generator outputs an incorrect frequency in high-speed mode.
6. Fix the possibility that the U disk cannot be opened when FLASH prompts that there is insufficient memory.
Where did you get it from?
-
What annoys me most is that beeing not in use, negative values causes the digits jumping around, because the string is centered together with the minus sign.
1.2.9 firmware direct link: http://www.dt830.com/forum.php?mod=attachment&aid=NDU1MDl8NjVhZGVjYzJ8MTcwOTAzMDM2M3wwfDgzMzE%3D (http://www.dt830.com/forum.php?mod=attachment&aid=NDU1MDl8NjVhZGVjYzJ8MTcwOTAzMDM2M3wwfDgzMzE%3D)
The changelog thread and download links: http://www.dt830.com/thread-8331-1-1.html (http://www.dt830.com/thread-8331-1-1.html)
-
But why is it not on the regualt Zoyi site?
Even the domain registration info for szzotek is odd.
It's behind a private registry service, just like the western zotektools.com site, just a different one. That by itself isn't that uncommon (most of my domains are behind private registrars), although I would expect most legitimate businesses to expose their domain contacts. I was skeptical of szzotek too when it was first mentioned (pretty sure in this thread) and suggested caution, but did some digging and came to conclusion it was legitimately their China-facing site. If you answer the prompt about English, it actually redirects you to the zotektools site.
Many Chinese equipment manufacturers have different internally-facing sites. Also some of them (e.g. Rigol) will post firmware updates to some sites and not others. So this really isn't that unusual.
On a loosely related note, Darren Walker had a Zotek rep on his YT channel a week or so ago when he was unboxing the 703S and asked her about the Zoyi vs Zotek distinction. We all knew they were the same company, but she clarified that Zotek is the western facing brand while Zoyi is the internal to China/Asia brand. She said they weren't allowed to market as Zoyi outside of China, so adopted the name Zotek. She didn't explain why, I assume for trademark or other reasons.
I covered all this a few pages back. Registration of the name is kinda useless. Follow the DNS and stuff. No 'A' record, the name is just a CNAME to some other site.
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5316196/#msg5316196 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5316196/#msg5316196)
-
V1.2.9 update content
1. Fixed the problem that when switching to multimeter mode, pressing F1 to F4 will cause the measurement items and the interface UI to be out of sync.
2. Optimize frequency measurement. When the frequency cannot be measured, the frequency value will become "--.--".
3. Optimize the AUTO strategy, which is faster and more accurate in identification.
4. Fix the problem that the frequency and time base are sometimes inaccurate in high-speed mode.
5. Fix the problem that the signal generator outputs an incorrect frequency in high-speed mode.
6. Fix the possibility that the U disk cannot be opened when FLASH prompts that there is insufficient memory.
Where did you get it from?
https://www.mydigit.cn/thread-438809-1-1.html (https://www.mydigit.cn/thread-438809-1-1.html)
-
My 703S has a problem with the charging LED (underneath the translucid red power button). After a while it starts blinking randomly. Thinking the LED might have a problem, I put a green LED in parallel, and it blinks just like the red LED.
So it seems like the driving voltage itself is the culprit. I did not check the other side of the PCB, but from online sources I've seen no traces related to this LED.
This means its connections go through an intermediate layer that makes it very difficult to follow.
Anyone else having this problem? Any thoughts?
-
My 703S has a problem with the charging LED (underneath the translucid red power button). After a while it starts blinking randomly. Thinking the LED might have a problem, I put a green LED in parallel, and it blinks just like the red LED.
So it seems like the driving voltage itself is the culprit. I did not check the other side of the PCB, but from online sources I've seen no traces related to this LED.
This means its connections go through an intermediate layer that makes it very difficult to follow.
Any thoughts?
Well it must be going to the microcontroller. Can't you just find it with a continuity tester?
-
Interesting the FW keeps getting smaller, V129 much smaller.
V127.ZTK bytes: 641256
V128.ZTK bytes: 640192
V129.ZTK bytes: 561512
-
My 703S has a problem with the charging LED (underneath the translucid red power button). After a while it starts blinking randomly.
If the charging IC is a TP4056, from some datasheets it suggests
that it's "BAT PIN Connect 10u Capacitance; No battery".
-
There's no TP4056 in sight, just a chip marked 4086B which I assume is the charger. Pin 2 is connected to a 474 resistor (470 kohms) that unfortunately does not lead to the LED (I checked the continuity). It probably leads to the microcontroller, then to the on-screen battery indicator and the button LED. I suppose the microcontroller is underneath the metal shield and I would not mess around unless I really have to and I do something that is documented.
-
My 703S has a problem with the charging LED (underneath the translucid red power button). After a while it starts blinking randomly.
Same behaviour here. I think it happens when the cell is at 4.2V and the current falls below the „fully charged“ threshold. The flashing stops after a few minutes (and probably comes back when the threshold is reached again due to discharge and settling).
So nothing to worry about, just a messy implementation without proper hysteresis for 100% charged. I have seen this on other products as well.
-
Can this device handle x100 probe?
In the tech spec only x1 and x10 is mentioned, but on this official picture https://8164272.s21i.faiusr.com/2/ABUIABACGAAgrPLRrQYogsCewQMw0A840A8.jpg (https://8164272.s21i.faiusr.com/2/ABUIABACGAAgrPLRrQYogsCewQMw0A840A8.jpg) (source: http://www.szzotek.com/h-pd-127.html (http://www.szzotek.com/h-pd-127.html)) x100 can be seen in the lower right corner of the screen. Here https://8164272.s21i.faiusr.com/2/ABUIABACGAAgrPLRrQYos5WJ2AMw0A840A8.jpg (https://8164272.s21i.faiusr.com/2/ABUIABACGAAgrPLRrQYos5WJ2AMw0A840A8.jpg) too.
-
Just checked on my device, x100 not available (FW 1.2.9)
-
Interesting the FW keeps getting smaller, V129 much smaller.
V127.ZTK bytes: 641256
V128.ZTK bytes: 640192
V129.ZTK bytes: 561512
Maybe someone in the development team discovered the compiler optimisation level.
-
But why is it not on the regualt Zoyi site?
Even the domain registration info for szzotek is odd.
Who knows?! Even the official site just leads you to a google drive. And the v1.29 isn't available on either one, it just appeared on some Chinese forums...
-
Can this device handle x100 probe?
Handle or handle? It should work fine with a 100X probe, it just won't adapt the voltage scale to show the actual voltage it it doesn't have a 100X mode. You need to do the X100 calculation yourself in that case, just like we did with most analog scopes of yesterday.
-
But why is it not on the regualt Zoyi site?
Even the domain registration info for szzotek is odd.
Who knows?! Even the official site just leads you to a google drive. And the v1.29 isn't available on either one, it just appeared on some Chinese forums...
I get how and where v1.2.9 showed up. If it's not from the vendor then you don't know what you're getting, at least from that user-vendor perspective.
-
I get how and where v1.2.9 showed up. If it's not from the vendor then you don't know what you're getting, at least from that user-vendor perspective.
Well the changelog is there. If you mean in aspects of trust... you shouldn't trust a chinese vendor anyway. It's a multimeter with no network connectivity and got no camera and no microphone. It won't sniff data and it won't farm bitcoins. So you should be pretty safe.
I tried disassembling the firmware, but entropy says it's encrypted.
-
Is the warranty voided if you flash firmware that you get on websites other that official website?
-
Is the warranty voided if you flash firmware that you get on websites other that official website?
If the unknown FW bricks it, and you claim warranty, and they find odd fw installed, no warranty.
-
There are only very few persons on this planet writing software for this device and most likely they are all employed at Zotektools.com. Software seems to be encrypted and packed into some special format. Zero chance someone outside the team would spread experimental risky software without permission. On the other hand you can probably not brick the device with any other binary file that does not meet the package format.
If really the device bricks during or after the update I would simply return (if possible at all) as faulty without any comments on the software version. Would really someone take the effort and deeply dig into the (bricked) (single-chip) controller just to find out if an „official“ updates was installed?
-
C'mon guys, we're talking about cheap Chinese test equipment, typically purchased from Chinese marketplaces. Unless you're buying from Amazon or some established Western dealer, do you really expect warranty service at all, for any reason whatsoever? MAYBE you can get a damaged/DOA device replaced through the marketplace, if you're lucky. But getting service/support and a malfunctioning unit replaced later? Good luck.
And I say that as a Zoyi fan. I think they make pretty damn good gear in their price range. If it turns out they do provide timely support for such things, then I'll be an even bigger fan. But I have no real illusions about that.
-
C'mon guys, we're talking about cheap Chinese test equipment, typically purchased from Chinese marketplaces. Unless you're buying from Amazon or some established Western dealer, do you really expect warranty service at all, for any reason whatsoever? MAYBE you can get a damaged/DOA device replaced through the marketplace, if you're lucky. But getting service/support and a malfunctioning unit replaced later? Good luck.
And I say that as a Zoyi fan. I think they make pretty damn good gear in their price range. If it turns out they do provide timely support for such things, then I'll be an even bigger fan. But I have no real illusions about that.
True, but I do want it to work right, because I use it as a tool, and the "work right" code should come from the actual vendor, even if 26 other websites have the ZTK file that the vendor should be hosting on their site. ;)
-
It appears lots of people have bought from the SNAKOL site.
How about the ZOYI "Official Store?" Are they really "officially" the Zotek Tools store, whatever that means?
Anybody have experience with them?
-
It appears lots of people have bought from the SAKOL site.
How about the ZOYI "Official Store?" Are they really "officially" the Zotek Tools store, whatever that means?
Anybody have experience with them?
If you're talking about this store (https://www.aliexpress.com/store/1101356986), then yes I have experience buying a couple of other DMMs from them. SNAKOL was the first Ali store to list the ZT-703S for sale (preorders, basically) which is why they got a lot of early orders. It took awhile for Zoyi's store to list it.
-
Would really someone take the effort and deeply dig into the (bricked) (single-chip) controller just to find out if an „official“ updates was installed?
I'm reminded of: https://youtu.be/N0rOe59wKAc?t=41
"They got us workin' in shifts!"
-
Have you seen that the Aneng version is also out? https://www.aliexpress.com/item/1005006532737130.html (https://www.aliexpress.com/item/1005006532737130.html)
They don't sell it in a 2-probe version kit, price is in the same range as the Zoyi, but in the Aneng store you pay the shipping on top.
In the other official Zotek store https://thedmm.com/shop/zt-703s/ (https://thedmm.com/shop/zt-703s/) you can get the unit for $99 + $19 shipping if destination is in EU. In this price they offer an extra "waveform testing lead" + a 16 pcs testing leads set, 2 year warranty and automatic replacement of the unit instead of repair. This is quite a good package in my opinion.
-
Most Aneng products are Zoyi rebrands. They don't actually make their own stuff.
In the other official Zotek store https://thedmm.com/shop/zt-703s/ (https://thedmm.com/shop/zt-703s/) you can get the unit for $99 + $19 shipping if destination is in EU. In this price they offer an extra "waveform testing lead" + a 16 pcs testing leads set, 2 year warranty and automatic replacement of the unit instead of repair. This is quite a good package in my opinion.
Pretty sure that's not an "official" Zotek/Zoyi store. Just passing themselves off as such by trying to look official. TheDMM.com is a brand of zoyitools.com which states at the top of the page that they're an "agent" of Zoyi. The official Zoyi web site (outside of China/Asia) is zotektools.com. Zoyi is the company but they're not allowed to market outside of China as Zoyi, which is why they use the Zotek brand.
I see this with a number of Chinese dealers, pushing themselves as an official manufacturer site. It's pretty deceptive if you ask me, because at first glance it looks entirely official and people will be lured in by an assumption they are official. I see it in the test equipment space a lot, and also the 3D printer space with the likes of Creality -- for years that was a competing Creality "store" that was not affiliated with Creality in any way, but let people believe they were. They had a lot of customer service issues that Creality was constantly blamed for. Another example is siglent.eu, which some believe is Siglent's official Euro site, but is really a 3rd party distributor (a legitimate one, and they do have an "Authorized Distributor" badge on the web page, but it's just not obvious to everyone).
-
In the Measurements section, what is the difference between FCNT and FREQ? I'm translating the manual and I don't have the meter handy.
-
In the Measurements section, what is the difference between FCNT and FREQ? I'm translating the manual and I don't have the meter handy.
FCNT: hardware counter based on the trigger. It will display 0.000Hz when trigger level is set outside of waveform.
Freq: software analysis of the waveform in the display memory. It will display --.-- if it can not determine the frequency.
-
I cant seem to open any of those links for firmware 1.2.9
Does anybody have an alternate link or could upload it here?
-
I've attached the 7zip file with 1.29. I installed it on my 703S that had 1.10 and boot 1.0.14 (not the .15 boot) and it installed with no trouble.
-
EDIT: One major fault appears my lack of understanding behind a menu option. Earlier I complained the maximum delay time before the screen turns off was 120 seconds. It appears if you select the setting "OFF" this actually means the display stays on.
Another issue is the entire feature set of the multimeter is behind one button. I often cycle between continuity and diode mode, yet these plus two other functions are behind one button so I have to press press press to get to what I want, meanwhile three other buttons side next to it doing nothing.
A custom firmware community would be awesome.
Or a voice to the developers would be ideal but judging by my inability to navigate the chinese language forums I don't think my ideas will be heard.
-
Thank you
The steps were:
Older laptop with windows 10
.7z extracted
Zoyi 703 turned off and unplugged
F1 and Power button held together, turns on to USB DISK mode
then connect via USB to computer
Navigate to Flash -> firmware folder
Copy and paste ZOYI-703S-FW-V129.ZTK into this folder
Device immediately recognises a new update and it self flashes (no confirmation required)
-
I chose to remove the plastic screen guard and replace it with a glass screen protector instead.
My mind 'knew' the screen was the same size as the Canon R6 and I happened to have a spare glass protector on the shelf.
4 screws to loosen
Plastic pry tool into middle of black rubber either side of case and it pops
6 screws to remove from logic board and 1 from each BNC jack
Pop out thick guard, leave bezel in place
Apply glass screen protector (or even a matte one!)
Reassemble.
The unit looks more professional as the screen appears totally flat. It looks like the black levels are better and glare is more tolerable.
Can recommend
-
I just got my 703S and am really happy with it.. I bought it to work today to show it to colleagues and connected both channels to the test output expecting to see 2 identical traces
But whilst my yellow line show the correct waveform, the blue line is flat... After decreasing the amplitude, the wave came into view but its 10x smaller than the yellow channel..
I have swapped the probes between the channels and the cables are not the cause.. Its got nothing to do with the 10x switch on the probes.. And I have the 703 set to 1x... But even if I change it to 10x it doesnt' actually do much.
In order to see both traces, I have the yellow channel set to 1v per division (Peak to Peak 2.5v), and the blue trace to 100mV (peak to peak .25v).
The correct voltage I am measuring is 2.5v so the blue side is wrong.
As its exactly 10x, I am assuming that this is a software issue, but I can't work out what I am doing wrong.
Anyone else seen this?
Jon
-
Did you set the same sensitivity on both channels on the 703S?
I just got my 703S and am really happy with it.. I bought it to work today to show it to colleagues and connected both channels to the test output expecting to see 2 identical traces
But whilst my yellow line show the correct waveform, the blue line is flat... After decreasing the amplitude, the wave came into view but its 10x smaller than the yellow channel..
I have swapped the probes between the channels and the cables are not the cause.. Its got nothing to do with the 10x switch on the probes.. And I have the 703 set to 1x... But even if I change it to 10x it doesnt' actually do much.
In order to see both traces, I have the yellow channel set to 1v per division (Peak to Peak 2.5v), and the blue trace to 100mV (peak to peak .25v).
The correct voltage I am measuring is 2.5v so the blue side is wrong.
As its exactly 10x, I am assuming that this is a software issue, but I can't work out what I am doing wrong.
Anyone else seen this?
Jon
-
Did you set the same sensitivity on both channels on the 703S?
Where do I set the sensitivity? Do you mean the X1/X10 option on the probes? And the x1/x10 option in the settings?
If we are talking x1/x10, both probes are X1 and changing between X1 and X10 in the menu doesn't actually seem to do much, other than changing the voltage value..
Is there another option I have overlooked?
Edit: I think i have worked it out.. I didn't realize you could change between Ch1 and Ch2 in the menu.. And when I found this, noticed that the X1/X10 could be set independently.. Mine were different, so I have set both channels to X1 and its working now....
So ignore me... Thanks.
-
Yep, thats what I meant. Great, you've figured it out. Have fun with this lovely little device.
Did you set the same sensitivity on both channels on the 703S?
Where do I set the sensitivity? Do you mean the X1/X10 option on the probes? And the x1/x10 option in the settings?
If we are talking x1/x10, both probes are X1 and changing between X1 and X10 in the menu doesn't actually seem to do much, other than changing the voltage value..
Is there another option I have overlooked?
Edit: I think i have worked it out.. I didn't realize you could change between Ch1 and Ch2 in the menu.. And when I found this, noticed that the X1/X10 could be set independently.. Mine were different, so I have set both channels to X1 and its working now....
So ignore me... Thanks.
-
Is there any benifit of installing 1.29? I have 1.27 but I always like the idea of having the latest software.
Are there any new features? I notice that the TXT file inside the zip is not English, so is the firmware safe to install on an English device?
Edit: Ignore me again.. Just read back and saw the release log.. No harm in installing it, so I will give it a go when I get a minute.
-
Is there any benifit of installing 1.29? I have 1.27 but I always like the idea of having the latest software.
Are there any new features? I notice that the TXT file inside the zip is not English, so is the firmware safe to install on an English device?
Edit: Ignore me again.. Just read back and saw the release log.. No harm in installing it, so I will give it a go when I get a minute.
1.29 is bigger than 1.27
;)
-
I just got my 703s a couple of days ago and I must say, I'm very happy with it. My main use for it is as a repair tool on my bench for audio device repair and kit building. It's a pretty solid machine and once you use it the interface becomes easy to work with.
Hah! That yellow sticker over the ports used for amperage measurements made it quite clear not to forget to take it out of amp mode and not use those ports for measuring voltage. Of course I removed it right away as I needed to measure mA on a kit I'm building. And of course, after forgetting to change the leads back to the right ports I was taking voltage measurements like a dummy. I had my power supply set to 9 volts with current limiting at 400mA. I wasn't getting good voltage readings, go figure, lol. I'm happy to say that there was no damage to the DUT or the meter so there's some amount of protection there. All bets would have been off with no current limiting and it's not something I plan on doing again. But it survived.
All in all I am very happy with it and would buy it again. I do have a nice Siglent on the bench but I prefer having a sacrificial scope, lol. Plus, it's just so damned convenient when you just want quick measurements and an easy way to get a signal trace. 5/5 stars.
-
I just got my 703s a couple of days ago and I must say, I'm very happy with it. My main use for it is as a repair tool on my bench for audio device repair and kit building. It's a pretty solid machine and once you use it the interface becomes easy to work with.
Hah! That yellow sticker over the ports used for amperage measurements made it quite clear not to forget to take it out of amp mode and not use those ports for measuring voltage. Of course I removed it right away as I needed to measure mA on a kit I'm building. And of course, after forgetting to change the leads back to the right ports I was taking voltage measurements like a dummy. I had my power supply set to 9 volts with current limiting at 400mA. I wasn't getting good voltage readings, go figure, lol. I'm happy to say that there was no damage to the DUT or the meter so there's some amount of protection there. All bets would have been off with no current limiting and it's not something I plan on doing again. But it survived.
All in all I am very happy with it and would buy it again. I do have a nice Siglent on the bench but I prefer having a sacrificial scope, lol. Plus, it's just so damned convenient when you just want quick measurements and an easy way to get a signal trace. 5/5 stars.
Yes, but the scope needs to work right to be useful.
We are all still wondering if the mystery 1.29 has fixed anything?
-
Can anyone verify a distortion in some waveform views? I connected a 1:100 probe measuring mains voltage (220V) and got the following distortions every 13th cycle (I counted the cycles from one to the next appearence of the distortion by using the move function of the oscilloscope). A similar picture I got on connecting a DC-AC power-inverter that was powered by battery (so there is nothing wrong with my mains;-). 13 cycles of 50 Hz are every 260 ms, I guess. Maybe there is something in acquisition of the signal not so perfect? I used the normal mode (not highspeed-mode) and the actual newest 1.29 Firmware from the DT830-site in which they fixed some problems.
[attachimg=5]
Here are some more strange distortions, I collected:
[attachimg=2]
[attachimg=1]
Another bug in highspeed-mode not in normal mode with the 1.29 FW is the squashing of the waveform after pressing the cursor-button.
[attachimg=3]
[attachimg=4]
I hope that zoyi will fix that and maybe also implement the 1:100 Probe selectability for getting correct values with this kind of probe.
-
When I choose a bit of phosphor screen I view the same strange. Not all time but very often.
FW 1.2.9
-
Just received my Zoyi ZT-703S, purchased from the "ZOYI Official Store" on Aliexpress about 7 days ago. Surprised to see a Boot and FW not previously mentioned - BOOT: V1.0.16 & FW: V1.3.0
Literally just got it out of the box, so haven't been through it to try and determine what's different in this fw compared to 1.2.9...
-
Just received my Zoyi ZT-703S, purchased from the "ZOYI Official Store" on Aliexpress about 7 days ago. Surprised to see a Boot and FW not previously mentioned - BOOT: V1.0.16 & FW: V1.3.0
Literally just got it out of the box, so haven't been through it to try and determine what's different in this fw compared to 1.2.9...
Wondering if they (or someone) is just up'ing the version # in the same boot & FW files to make it seem like the device is coming super "fresh"?
This is why we really need the official vendor to post up some release notes and the downloads to the FW's.
-
When I choose a bit of phosphor screen I view the same strange. Not all time but very often.
FW 1.2.9
Jitter would look similar, difficult to see in your jpg. If you use the original bmp-file of the zt-703 screen-copy function and convert it directly to png for uploading here would show your curve more detailed...
I hope, Zoyi also implements in future firmware saving directly to png instead of bmp, would be possible to save 10x more screencopies in the limited memory of the zt-703. One guy in the dt-830 forum already asked for implementing that, beside some more functions ...
-
Hello...
I want to ask anybody who owns ZT-703S. It is able to save captured waveform into file? Not as a picture, but as text or binary file, which then can be parsed by software. I read the manual, and as I understood, it is only writes pictures into the memory. Looks like a joke. Who need picutres? I can photo a screen by phone. But, for example, if I need analyze some CAN/LIN/RS-485 data packets, it would be convenient to have possibility to record packets and analyze records on PC. And if waveform can be saved, how many samples?
-
Hello...
I want to ask anybody who owns ZT-703S. It is able to save captured waveform into file? Not as a picture, but as text or binary file, which then can be parsed by software. I read the manual, and as I understood, it is only writes pictures into the memory. Looks like a joke. Who need picutres? I can photo a screen by phone. But, for example, if I need analyze some CAN/LIN/RS-485 data packets, it would be convenient to have possibility to record packets and analyze records on PC. And if waveform can be saved, how many samples?
I have ordered one but not yet received it. I dont expect this option to be present, but I agree that this would be a very useful feature. The OWON multimeter scopes have that feature (and a PC app) but only 8k sampling memory vs 128k of the 703S.
-
Can anyone tell me whats the minimum value capacitance it can measure? Its not showing any digits on small ceramic capacitors.
-
Can anyone tell me whats the minimum value capacitance it can measure? Its not showing any digits on small ceramic capacitors.
Range Resolution Accuracy
9.999nF 0.001nF ± (5.0%+20)
Maybe above 0.020 nF.
But I don't understand what is the point of writing the pF value on the display, when the minimum inaccuracy is +20 count?!
-
Because i can add in series another capacitor that i know the exact value and then get the first cap value.
-
Because i can add in series another capacitor that i know the exact value and then get the first cap value.
Even so, the inaccuracy of the device does not disappear.
What I mentioned above.
If you want to measure a small value 0.03 nF capacitor whose true value you do not know.
And you connect a 1nF capacitor "in parallel" with it.
Then if everything is with 0% tolerance, it should be 1.03nF.
But due to the measurement inaccuracy of the instrument, you can measure here. ±(0.0515nF+0.02nF) that is
1.03nF-0.0715nF = 0.9585nF
and
1.03nF+0.0715nF = 1.1015nF
value between
But you won't be able to calculate from this how much the smaller 0.03nF capacitor is.
Since the inaccuracy is related to the measured values in %, if you try the same thing as described above with an 8nF, the inaccuracy will be greater, because of course the 5% of the 8nF is much larger than that of the 1nF.
With the 20 count inaccuracy, I don't understand why they didn't cut off the last, smallest digit and write 2 count instead.
I apologize if it is difficult to understand, I struggle a lot with google translate
-
Because i can add in series another capacitor that i know the exact value and then get the first cap value.
Even so, the inaccuracy of the device does not disappear.
What I mentioned above.
If you want to measure a small value 0.03 nF capacitor whose true value you do not know.
And you connect a 1nF capacitor "in parallel" with it.
Then if everything is with 0% tolerance, it should be 1.03nF.
But due to the measurement inaccuracy of the instrument, you can measure here. ±(0.0515nF+0.02nF) that is
1.03nF-0.0715nF = 0.9585nF
and
1.03nF+0.0715nF = 1.1015nF
value between
But you won't be able to calculate from this how much the smaller 0.03nF capacitor is.
Since the inaccuracy is related to the measured values in %, if you try the same thing as described above with an 8nF, the inaccuracy will be greater, because of course the 5% of the 8nF is much larger than that of the 1nF.
With the 20 count inaccuracy, I don't understand why they didn't cut off the last, smallest digit and write 2 count instead.
I apologize if it is difficult to understand, I struggle a lot with google translate
many meters have the same problem. The only meter that I have that really shows meaningful values down to a few pF (4.7pF) is an OWON clamp! meter. Most others show nothing if a small cap is measured.
-
Wouldn't the inaccuracy be the same for both caps? I mean if i add a known 10pf cap and it adds 7pf to the multimeter than i know its 3pf off so i calculate the same % for the unknown cap value also?
Example. Unknown cap shows 7pf. I add a known 10pf cap and it shows 14pf total. This way i know both caps have 10pf value
-
Which OWON version?
-
its an OWON CM210E (30€).
-
I don't know how much this will help you, I measured a 10pF ±0.5pF capacitor, so its value is actually between 9.5 and 10.5 pF.
My Aneng A3009 has a 0.000nF display
0.016nF measured.
And my Owon has 00.030nF
Which is a little outside of your spec.
Aneng, on the other hand, is much closer to reality. I don't have any other DMMs at the moment, just lots of Owons and an Aneng. :(
Zoyi should also be able to measure in the smallest measure range.
If you have several capacitors whose value you know, you can find out from where it works by moving towards the smaller value.
Wouldn't the inaccuracy be the same for both caps? I mean if i add a known 10pf cap and it adds 7pf to the multimeter than i know its 3pf off so i calculate the same % for the unknown cap value also?
Example. Unknown cap shows 7pf. I add a known 10pf cap and it shows 14pf total. This way i know both caps have 10pf value
If you think about it, no. The inaccuracy is given by simple math.
The Zoyi ha measures
1nF then the error is ± 0.07nF
At 10nF, the error is ±0.7nF
I have noticed that it will not always grow linearly. If I add a 0.05nF capacitor to the 10nF, sometimes only 0.02nF changes.
This cannot be called a measurement.
For measuring small values, it is worth using the measuring instrument created for it.
its an OWON CM210E (30€).
As far as I know, it also runs under the name Owon CM2100 /B.
B has bluetooth.
-
I measured a cap that has code 10 on it and it doesnt show value in zoyi. Even 2 caps in parallel dont show. Only 3 caps show value of 00.010
Meanwhile the bside esr02 pro shows 29pf for same 3 caps.
Could this be because i calibrated the zoyi? Is there a way to reverse the calibration, like format option or flashing new firmware?
Do i need to leave the multimeter probes attached during calibration so their resistance is canceled?
-
I very much doubt that the calibration procedure has any effect on the multimeter readings. Only the scope.
-
I measured a cap that has code 10 on it and it doesnt show value in zoyi. Even 2 caps in parallel dont show. Only 3 caps show value of 00.010
Meanwhile the bside esr02 pro shows 29pf for same 3 caps.
Could this be because i calibrated the zoyi? Is there a way to reverse the calibration, like format option or flashing new firmware?
Do i need to leave the multimeter probes attached during calibration so their resistance is canceled?
I very much doubt that the calibration procedure has any effect on the multimeter readings. Only the scope.
After using another shorter probe i was able to measure even 5pf capacitor. I think if the probe was better zoyi can measure down to its resolution 1pf. The default probe is to long maybee.
I hope future firmwares introduce a pf scale.
-
The only meter that I have that really shows meaningful values down to a few pF (4.7pF) is an OWON clamp! meter. Most others show nothing if a small cap is measured.
This is a false statement. Very many multimeters, when properly adjusted, show units of picofarads. Of course, given the factory error of such measurements. For example, I have the HP-890CN and HP-4070, which can display picofarads and are quite good. Look at the pictures I took earlier. In addition, if you want to measure such small capacitances more competently, you should use appropriate devices that exclude the influence of conductors, which contribute their capacitance and error to the measurement. I have also shown an example of such a simple device on the photo. ;)
-
After using another shorter probe i was able to measure even 5pf capacitor. I think if the probe was better zoyi can measure down to its resolution 1pf. The default probe is to long maybee.
I hope future firmwares introduce a pf scale.
If the one shown in the picture is the measuring probe that I also bought, then it is a waste. After the first few measurements, I threw it in the trash... :palm:
I didn't see it in your previous pictures.
-
It came with bside esr02 pro.
They show the correct value. Stock probes are way off.
-
Edmiri,What will this device show if the capacitance is connected directly to the input terminals without using tweezers and conductors?
-
It came with bside esr02 pro.
They show the correct value. Stock probes are way off.
That's why the REL button exists in most meters (it's the red one in ZT-703S, as far as I can tell)
With it you can remove any leads effect when measuring low capacitance or resistance values.
You can see "REL" on the display of the meters that indman show in Reply #358
-
Edmiri,What will this device show if the capacitance is connected directly to the input terminals without using tweezers and conductors?
If you were asking about bside than i already did that.It came with bside esr02 pro.
They show the correct value. Stock probes are way off.
That's why the REL button exists in most meters (it's the red one in ZT-703S, as far as I can tell)
With it you can remove any leads effect when measuring low capacitance or resistance values.
You can see "REL" on the display of the meters that indman show in Reply #358
I tried that and same results.
-
If you were asking about bside than i already did that.
No, I was asking what the ZT-703S would show since it is the one being discussed in this thread.
-
@ Edmiri
This is what I was trying to say, about using the REL button to zero readings to increase accuracy when measuring low values of capacitance or resistance
https://youtu.be/n58H1v0Wa5w?si=SQCfzxT2DQp3T7s2&t=1378
-
This is what I was trying to say, about using the REL button to zero readings to increase accuracy when measuring low values of capacitance or resistance
https://youtu.be/n58H1v0Wa5w?si=SQCfzxT2DQp3T7s2&t=1378
This is an unfortunate example of how small capacitance measurements should not be made using the REL button.
You can't hold such a small capacitor in your hands! And note that with the probes connected, the multimeter display shows only zeros when it is not touching them.
-
This is what I was trying to say, about using the REL button to zero readings to increase accuracy when measuring low values of capacitance or resistance
https://youtu.be/n58H1v0Wa5w?si=SQCfzxT2DQp3T7s2&t=1378
This is an unfortunate example of how small capacitance measurements should not be made using the REL button.
You can't hold such a small capacitor in your hands! And note that with the probes connected, the multimeter display shows only zeros when it is not touching them.
In that regard, it is indeed. But I didn't find another example were the REL button was used with this hand-scopes.
-
Mortymore, Yes it is. I watched several video reviews of the ZT-702 and ZT-703 on Youtube.
In all videos it is clearly visible that in capacitance measurement mode the display shows 00.000nF both with and without factory probes connected!
This tells us that the probes connected to the input terminals do not add any capacitance to the result on the display, and this can never happen.
Probes, like any conductors, have their own inductance,resistance and capacitance. The capacitance which will change as their position in space changes and in your hands.
Therefore, the readings on the 00.000nF display do not display real values, but relative ones even without pressing a button REL. This happens because at the factory, Chinese friends do not particularly bother themselves with carefully setting up and calibrating such cheap devices. Therefore, the technical characteristics contain such a huge error in this part of the range
9.999nF 0.001nF ± (5.0% + 20)
Although in fact the device can measure small picofarads quite accurately if you first add another capacitance to its measuring input, which he showed us in his examples Edmiri. The capacity of the tweezers, which is connected to the input terminals of the ZT-703, is apparently optimally suited for the device to actually display units of picofarads. I wonder what capacitance this tweezers will have if you measure it, for example, using BSide ESR02? :)
-
If you were asking about bside than i already did that.
No, I was asking what the ZT-703S would show since it is the one being discussed in this thread.
I tried a Electrolytic capacitor since the ceramic ones could make contact because of short legs.
Using stock probes 9.4uf
Direct contact 9.522uf
@ Edmiri
This is what I was trying to say, about using the REL button to zero readings to increase accuracy when measuring low values of capacitance or resistance
https://youtu.be/n58H1v0Wa5w?si=SQCfzxT2DQp3T7s2&t=1378
Yes I've tried and no results.
-
I tried a Electrolytic capacitor since the ceramic ones could make contact because of short legs.
Using stock probes 9.4uf
Direct contact 9.522uf
An electrolytic capacitor is not suitable for us to determine the required additional capacitance when measuring picofarads.
You can solder small pieces of conductors to short legs, for example, to the 30pF capacitance that you showed in your measurement example.
-
I see... It seem that this is another case of the meter displaying a perfect 0.000 if its its close to that, to make the user happy.
I bought recently a RC3563 battery tester, that acts like this.
So in low capacitance measurements, the "close to zero" messes the readings despite the Relative measurement is used.
Nice to be aware of that :o
-
Ceramic 33 cap.
Stock probes 0.011nf
Bside esr02 probes 0.033nf
Direct connection shows 00.000
Of i add another cap it shows the value. The connection is ok
The value of cap starts a bit low than it peaks at the values i wrote above.
-
Ceramic 33 cap.
Stock probes 0.011nf
Bside esr02 probes 0.033nf
Direct connection shows 00.000
Of i add another cap it shows the value. The connection is ok
The value of cap starts a bit low than it peaks at the values i wrote above.
This is how it should be, I explained the reasons in my message above. To make it more clear to you what I was explaining, I will show you a few photographs that I took today. I have tweezers that are very similar to yours, as well as probes with thin needles also similar to your factory ones.
I measured the intrinsic capacity of the tweezers and probes. Now, I hope, the reason for this behavior of the ZT-703 when measuring small picofarads is clear? :)
-
Ceramic 33 cap.
Stock probes 0.011nf
Bside esr02 probes 0.033nf
Direct connection shows 00.000
Of i add another cap it shows the value. The connection is ok
The value of cap starts a bit low than it peaks at the values i wrote above.
This is how it should be, I explained the reasons in my message above. To make it more clear to you what I was explaining, I will show you a few photographs that I took today. I have tweezers that are very similar to yours, as well as probes with thin needles also similar to your factory ones.
I measured the intrinsic capacity of the tweezers and probes. Now, I hope, the reason for this behavior of the ZT-703 when measuring small picofarads is clear? :)
We should expect to have some measured C of the probe set, but certainly the reading will depend on how the lead wires cross over each other and how close the ends are to each other. It is perhaps possible that the 16pf set could read 45pf if the leads were arranged differently? I don't think it would be good to REL at 45pf and then completely rearrange the leads to go measure a cap. If anything the whole thing needs to be in a jig, the measured leads C then REL'd by meter or by hand, and then DUT placed into the measuring jig.
-
I have tried repositioning the probe leads and had no diference. I also tried reel mode and same results.
Strange why it didnt read at all when connected directly to the input terminals.
Also why it needs some minutes of usage before the capacitance value raise. This is for both stock probe and Bside twezers. After it warmed up i read even 1pf capacitor using bside tweezers.
-
We should expect to have some measured C of the probe set, but certainly the reading will depend on how the lead wires cross over each other and how close the ends are to each other. It is perhaps possible that the 16pf set could read 45pf if the leads were arranged differently?
No,there won't be that much change in capacitance. Of course, it will vary in some limits from the position of wires in space, but such a capacitance of 45-50pF, which has tweezers, is unlikely to reach. I could be wrong of course, I just wanted to explain this effect with different probes, which observes Edmiri.
I have tried repositioning the probe leads and had no diference. I also tried reel mode and same results.
Strange why it didnt read at all when connected directly to the input terminals.
As I see from your last message, you still did not quite understand the meaning of what I was trying to show in my photos and in the message above. Perhaps because of my bad English? Sorry! Maybe someone else who understood what I wanted to say will explain it to you more clearly.
-
You we're very clear.
What i don't understand is why when i directly connect the capacitor to the multimeter without any probe, it doesn't show any value. Larger than 33pf ca0acitors show value, so this means the connection is ok.
-
What i don't understand is why when i directly connect the capacitor to the multimeter without any probe, it doesn't show any value. Larger than 33pf ca0acitors show value, so this means the connection is ok.
Once again, I'll try to explain to you why this is the case. You see the numbers 00.000nF on the display of the ZT-703S with no capacitance connected. In reality, this is not the case. Imagine that now your device displays a conditionally negative value (-00.033nF). When you connect a 33pF capacitance directly to the input pins, this conditionally negative value is compensated and you can see that the display shows no change, i.e. it shows 00.000nF. If you connect another capacitance directly to the input jacks, e.g. 100pF, you should see a result of about 00.067nF on the display, i.e. 100pF-33pF=67pF.
-
My observations.
The multimeter is a separate part of the circuit. The most common and widespread multimeter made on DTM0660/DTM1106. Therefore, any answers to the topic “how it works” and “what to do with it” can be found in topics about this chipset. There will be nothing new here. All the nuances, all the limitations stem from the capabilities of the DTM0660.
a) It can be calibrated at any time by recording what you need in I2C EEPROM. I remade the current shunt, calibrated it by writing down the settings at address 0x2A and got an “ideal meter for 4-20 mA”. In Russian it's "as easy as to send two bytes."
b) When switching to a multimeter, its mode will always be voltage measurement because no one bothers with maintaining the operating mode. Yes, in fact, this is unlikely to work out in this circuit design.
-
The multimeter is a separate part of the circuit. The most common and widespread multimeter made on DTM0660/DTM1106. Therefore, any answers to the topic “how it works” and “what to do with it” can be found in topics about this chipset. There will be nothing new here. All the nuances, all the limitations stem from the capabilities of the DTM0660.
The ZT-702S multimeter uses DM1109EN and EEPROM 24C02 chip. In the ZT-703S, the multimeter chip is still unknown since the markings have been erased and EEPROM 24C02. There are many similarities with the DTM0660, but there are also differences.
a) It can be calibrated at any time by recording what you need in I2C EEPROM. I remade the current shunt, calibrated it by writing down the settings at address 0x2A and got an “ideal meter for 4-20 mA”. In Russian it's "as easy as to send two bytes."
Not all calibration constants and configurations are stored in the I2C EEPROM, so for each device model the contents of the EEPROM will differ significantly. There are many things that are already pre-recorded at the factory into the main DM chip and their value cannot be changed or a special calibration procedure is required, which is known to the manufacturer!
-
This is odd. The Zotek website offers v1.27, and that's what people seem to be generally talking about. But the one I just got shows firmware 1.30.
Interesting bugs found so far: While showing it to a friend, first the trigger position indicator disappeared. Only the tiny green right arrow at the top right showed, but no amount of scrolling left and right brought the trigger position into view, and in fact, scroling was infinite since it kept wrapping around.
Shortly after that, the trigger mode button stopped working. It was just stuck in "Auto", no way to go to single shot any more. Toggling the unit off and on, and toggling between scope and multimeter mode, changed nothing. Resetting the scope to defaults fixed it.
Also, shouldn't there be a way to change the scale/position settings for channel 2? Selecting channel 2 in the menu affects nothing; the directional buttons still change channel 1. The only way I've found is to disable channel 1 temporarily; then they access channel 2.
One hopes for active bug fix updates. But again, why do I have newer firmware than what is downloadable?
Main dislike other than the issues above, is that the buttons need a pretty heavy press.
-
Also, shouldn't there be a way to change the scale/position settings for channel 2? Selecting channel 2 in the menu affects nothing; the directional buttons still change channel 1. The only way I've found is to disable channel 1 temporarily; then they access channel 2.
This sounds annoying... Will receive mine in the next few days. I will most likely use only 1 channel 95% of the time. What can we expect for around 80€ only? Lets see if we get more FW updates or if Zoyi rather releases a new scopemeter model.
-
Another question, is everybody's ZT703s as noisy as this one? Probe clipped to the calibrator output/ground lug, default square wave output, haven't messed with the calibration screws yet.
About 2-3 pixels of noise regardless of the vertical scale. Even with the probe grounded, at some vertical scales about 2 pixels of noise are present as in the last screenshot; at others the line is flat. Par for the course at this price level?
-
Another question, is everybody's ZT703s as noisy as this one? Probe clipped to the calibrator output/ground lug, default square wave output, haven't messed with the calibration screws yet.
About 2-3 pixels of noise regardless of the vertical scale. Even with the probe grounded, at some vertical scales about 2 pixels of noise are present as in the last screenshot; at others the line is flat. Par for the course at this price level?
I've noticed the same thing - and was wondering if it was just me...
My 3 cheapie ZeeWeii scopes don't show this much noise.
-
Glad that they don't show perfect lines, as they seem to show perfect zeros on multimeter, to make some users happy :palm:
https://www.youtube.com/watch?v=Znwp0pK8Tzk (https://www.youtube.com/watch?v=Znwp0pK8Tzk)
-
Glad that they don't show perfect lines, as they seem to show perfect zeros on multimeter, to make some users happy :palm:
Bingo,you think right! Beware if you see a straight, nice and noiseless sweep line on digital oscilloscopes, as well as absolute zeros on the display when measuring capacitance! ;)
-
Next one: I haven't found a way to display absolute voltages for the horizontal cursors; it only displays a delta.
As long as the voltage graticule is accurate (with the channel zero point arrow lined up visually) one can just place one cursor on, say, 0V and then read the absolute voltage for the other off the delta. But have I missed something?
-
Beware if you see straight lines on cheap oscilloscope that is. My previous experience with a digital scope, when I was still doing that sort of analog lab work, 30 years ago, was with a HP 54100. And that one really did give clean lines - at higher pixel resolution too - for DC values.
-
Watched the video above. Admittedly all the work with the old expensive early generation digital 'scope was in single-shot mode. And I don't have any screenshots left (hardcopy in those days - you hooked up a printer via HPIB) to really confirm that my memory is accurate.
-
Next one: I haven't found a way to display absolute voltages for the horizontal cursors; it only displays a delta.
As long as the voltage graticule is accurate (with the channel zero point arrow lined up visually) one can just place one cursor on, say, 0V and then read the absolute voltage for the other off the delta. But have I missed something?
STOP it then use the trigger level as a "cursor".
-
Is this more "don't expect too much from a cheap scope" stuff? I clipped both the probes (P2060) to the calibrator lug - and the ground clips to the ground lug - to finally adjust the compensation screws. Nice and rectangular, but... different amplitude? I figured OK, cheap probes, don't exactly do 10:1 attenuation (both were switched to 10X). But swapping the BNC connections didn't change anything. Channel 2 still shows the same, lesser amplitude.
-
Is this more "don't expect too much from a cheap scope" stuff? I clipped both the probes (P2060) to the calibrator lug - and the ground clips to the ground lug - to finally adjust the compensation screws. Nice and rectangular, but... different amplitude? I figured OK, cheap probes, don't exactly do 10:1 attenuation (both were switched to 10X). But swapping the BNC connections didn't change anything. Channel 2 still shows the same, lesser amplitude.
If you have not done so already, try doing the calibration.
-
It looks like new stock is sold with 1.3.0 Firmware. However it is still nowhere to be found online.
-
My ZT-703S arrived today, purchased from AliExpress. I was surprised it wouldn't turn on since the batteries are usually delivered with 50% charge. I opened it up and found that I have no battery inside!!!
I'm wondering if it's worth the effort of sending it back, or probably I'll just buy a battery and put it in myself. Does it matter if I install an ICR or IMR 18650? Are they interchangeable? Which should I be using in this?
-
They are both compatible, but I would use ICR. IMR is for high drain applications, it would be overkill for a scope.
-
I'm wondering if it's worth the effort of sending it back, or probably I'll just buy a battery and put it in myself. Does it matter if I install an ICR or IMR 18650? Are they interchangeable? Which should I be using in this?
What do you need to buy a battery for now? You can check if the device works by simply connecting an external 4.0V voltage to it, e.g. from a power supply unit.
If the device works in all modes, simply negotiate with the seller for compensation for the missing battery. If the device is not working, you should return it to the seller.
-
What do you need to buy a battery for now? You can check if the device works by simply connecting an external 4.0V voltage to it, e.g. from a power supply unit.
If the device works in all modes, simply negotiate with the seller for compensation for the missing battery. If the device is not working, you should return it to the seller.
Thanks. This is the first time I've used AliExpress. I just found the 'Message Center' and contacted the seller. I had connected power to it and it does work, so hopefully they can simply send me a battery.
Otherwise, I'm quite happy with the unit and how it works. Having grown up using hefty Tektronix CROs in the 80s, I'm still boggle-minded that I can have this in my hand for under $100.
-
I just wanted to post a PSA, most probably know this already but when buying anything of value from AliExpress please video record the opening of your package in one continuous shot all in frame.
I purchased the ZT-703 2x now from AliExpress the first one was returned to the seller because the package weight didnt match the discription during shipping and never made it out of china. The second one was flat out scammed and the seller sent me some gel pads that look like small shoe inserts or something. It came in a large order with several items. The recording i made was corrupt (not sure what happened) Luckily AliExpress refunded my purchase without it. Ended up buying a ADS1013D for 50$ off ebay for use in the mean time. Again just wanted to share my cautionary tale.
-
Just got my 703S. It took me some time to realize that the function generator available via the 'More Apps' menu does not work together with the scope functionality at all. Either use the scope or the enhanced function generator! The low frequency generator accessible via the 'Output' option on the other hand is always available. However it seems that setting some of the other waveforms (triangle etc) then imposes a 100us minimal timebase setting.
fw is 1.29
-
Just got my 703S. It took me some time to realize that the function generator available via the 'More Apps' menu does not work together with the scope functionality at all. Either use the scope or the enhanced function generator! The low frequency generator accessible via the 'Output' option on the other hand is always available. However it seems that setting some of the other waveforms (triangle etc) then imposes a 100us minimal timebase setting.
fw is 1.29
Did it ever work the other way? All I saw was freq gen made signal a bnc and the signal being generated was in the display.
Does the manual say it works any other way?
-
Just got my 703S. It took me some time to realize that the function generator available via the 'More Apps' menu does not work together with the scope functionality at all. Either use the scope or the enhanced function generator! The low frequency generator accessible via the 'Output' option on the other hand is always available. However it seems that setting some of the other waveforms (triangle etc) then imposes a 100us minimal timebase setting.
fw is 1.29
This issue is present in v1.27 too. In the below video a workaround is described:
https://youtu.be/T7kXdiVXet4?t=55 (https://youtu.be/T7kXdiVXet4?t=55)
You should turn on the signal generator through the More Apps menu, in this case you can go down to 10ns.
-
My ZT-703S arrived today, purchased from AliExpress. I was surprised it wouldn't turn on since the batteries are usually delivered with 50% charge. I opened it up and found that I have no battery inside!!!
I'm wondering if it's worth the effort of sending it back, or probably I'll just buy a battery and put it in myself. Does it matter if I install an ICR or IMR 18650? Are they interchangeable? Which should I be using in this?
Depending on seller, destination country, shipment method (passenger air vs cargo air vs sea), and probably some other variables, lithium chemistry batteries are considered hazardous and are banned from being shipped as regular cargo. I've had a number of items ship from China without their batteries, while others come with. Sometimes they tell you they're shipping sans batteries, and other times they do not. It's pretty much a lottery. Either some sellers are applying the regulations to everything they sell just to avoid hassling with who gets batteries and who doesn't, or they don't care about regulations and ship batteries regardless.
I'm not usually concerned about it, because typically if I'm ordering from AliExpress and the like it's because of a price advantage anyway, so the extra cost of a battery is a non-issue. Fortunately I maintain a supply of most common rechargeable formats including 18650's and a few different LiPo pouch types, so unless it's some exotic battery it's seldom much of an inconvenience for me. It would be courteous for the seller to clearly state in their listings that they ship without batteries, and what type is required, just so buyers can be prepared.
All that to say this is not unusual, and you're unlikely to get a battery from the seller, thought they might be generous enough to refund you a couple bucks to supply your own battery.
-
I just wanted to post a PSA, most probably know this already but when buying anything of value from AliExpress please video record the opening of your package in one continuous shot all in frame.
I purchased the ZT-703 2x now from AliExpress the first one was returned to the seller because the package weight didnt match the discription during shipping and never made it out of china. The second one was flat out scammed and the seller sent me some gel pads that look like small shoe inserts or something. It came in a large order with several items. The recording i made was corrupt (not sure what happened) Luckily AliExpress refunded my purchase without it. Ended up buying a ADS1013D for 50$ off ebay for use in the mean time. Again just wanted to share my cautionary tale.
Interesting. I was about to spend almost $1000 on an oscilloscope on AliExpress. Now you've got me wondering if it's a bad idea.
-
Depending on seller, destination country, shipment method (passenger air vs cargo air vs sea), and probably some other variables, lithium chemistry batteries are considered hazardous and are banned from being shipped as regular cargo. I've had a number of items ship from China without their batteries, while others come with. Sometimes they tell you they're shipping sans batteries, and other times they do not. It's pretty much a lottery. Either some sellers are applying the regulations to everything they sell just to avoid hassling with who gets batteries and who doesn't, or they don't care about regulations and ship batteries regardless.
I'm not usually concerned about it, because typically if I'm ordering from AliExpress and the like it's because of a price advantage anyway, so the extra cost of a battery is a non-issue. Fortunately I maintain a supply of most common rechargeable formats including 18650's and a few different LiPo pouch types, so unless it's some exotic battery it's seldom much of an inconvenience for me. It would be courteous for the seller to clearly state in their listings that they ship without batteries, and what type is required, just so buyers can be prepared.
All that to say this is not unusual, and you're unlikely to get a battery from the seller, thought they might be generous enough to refund you a couple bucks to supply your own battery.
There was no mention in the ad of it being 'sans battery', however, I just looked at the reviews and a lot of people have made the same comment. Anyway, no big deal. Online ordering is always a lottery and I'm pretty happy that the product arrived with two probes and that it works. :)
**UPDATE** I just got a return message from the seller saying they can't ship with a battery. So, I can just order an 18650 from AliExpress and hope they don't send me an empty package and say the same thing, lol.
BTW, do I need to use a 'protected' cell? I've never used an 18650 before and just saw a post about it.
-
The battery takes a long time to arrive. (more than 30 days) Because they probably go by train or ship. He was born from other things that go by air. The package with the battery is usually marked with a yellow sticker and a battery and fire pictogram.
-
Just got my 703S. It took me some time to realize that the function generator available via the 'More Apps' menu does not work together with the scope functionality at all. Either use the scope or the enhanced function generator! The low frequency generator accessible via the 'Output' option on the other hand is always available. However it seems that setting some of the other waveforms (triangle etc) then imposes a 100us minimal timebase setting.
fw is 1.29
Did it ever work the other way? All I saw was freq gen made signal a bnc and the signal being generated was in the display.
Does the manual say it works any other way?
No, the manual does not say anything about that but it also does not state that it is NOT possible to see the waveforms on the scope. Maybe it is just me, but it feels like you buy a car with a radio and then find out that you can listen to the radio only when the motor is off. The reviews were at least unclear or the reviewers were confused themselves. Just to make the facts clear again to the followers of this thread, as of FW 1.29, the only generator signal that allows for the full capabilities of the scope (no 100us limit) is the 1kHz square wave calibrator signal. Other signals up to 2-5kHz can be used with together with the scope function (100us limit). The extended generator options (up to around 100kHz etc) can only be used stand-alone in the separate App. If you encounter the 100us time base limit in your scopemeter and want to go back to normal, you need to go to the output menu (generator) and select the square wave option (the one were frequency and amplitude show no values ---)
Overall, the scopemeter works quite reliable with the 1.29 firmware. No crashes, little menu weirdness, triggering works fine and the operation in the single channel mode is fun. With two channels the operation is more cumbersome but also works ok.
-
I just wanted to post a PSA, most probably know this already but when buying anything of value from AliExpress please video record the opening of your package in one continuous shot all in frame.
I purchased the ZT-703 2x now from AliExpress the first one was returned to the seller because the package weight didnt match the discription during shipping and never made it out of china. The second one was flat out scammed and the seller sent me some gel pads that look like small shoe inserts or something. It came in a large order with several items. The recording i made was corrupt (not sure what happened) Luckily AliExpress refunded my purchase without it. Ended up buying a ADS1013D for 50$ off ebay for use in the mean time. Again just wanted to share my cautionary tale.
Interesting. I was about to spend almost $1000 on an oscilloscope on AliExpress. Now you've got me wondering if it's a bad idea.
A very bad idea in my opinion. One my find great and honest sellers in Aliexpress, but also many dishonest sellers, from those who sell garbage, item not as stated, cancel deals many days after purchase, and I even received an empty bag stating 10g of weight, hence, obviously empty, just for fun. Had to report that to authorities, as Pyapal requested, because Aliexpress didn't do anything for days, so I turned into Paypal, the only method I use to pay on Aliexpress.
Despite a deal can go smoothly, one has to think about support. I would never risk to spend $1000 in an item in Aliexpress and expect local support if needed.
Just my 2cents
-
Depending on seller, destination country, shipment method (passenger air vs cargo air vs sea), and probably some other variables, lithium chemistry batteries are considered hazardous and are banned from being shipped as regular cargo.
Most of the products I have ordered so far have come with a "built-in" rechargeable battery.
As far as I can see, the zt703s has an officially "replaceable" battery.
Maybe that's the difference?
Is there a difference in safety whether a battery is built-in (officially non-removable) or not?
P.S. I don't have a zt703s, I'm just guessing.
-
Cheap scope expectation management.
I have an old 15MHz analog scope. It is honestly 15MHz. If you put in a higher-bandwidth signal, you see a 15MHz low-pass filtered version of it. For example, a 6MHz square wave will look pretty rounded, but rock steady with no strange artifacts.
This thing claims to be 50MHz bandwidth, which may well be true, but I don't think there's anything even resembling a 50MHz "brick wall" low-pass filter. So if you sample a higher-bandwidth signal you can get some gruesome artifacts. I don't have access to high-quality lab equiment, specifically no function generator and no better quality scope to compare to. What I do have is a 3.6864MHz clock oscillator module which, based on lab experience in a past life, puts out a clean signal - it had better, being a clock source. Let's put it on (first pic).
Whoa! I could handle "ringing" on the edge, but every edge looks different! 10s persistence shows the variation.
Well, that's overmagnification. In high speed mode, this thing does something like 250Ms/s but at 50ns/div that's only about one sample every other pixel. So zoom out to 100ns/div (second picture). This shows several different "versions" of the rising and falling edges, now at roughly 1:1 ratio between horizontal pixels and samples.
Right, get a hold of yourself. This is not a $20K lab scope. This is a scopemeter. What do people use them for? Debug power supply issues, audio issues, and, in the old days, standard definition TV issues (that's the world my 15MHz analog scope was born into). I do still have a single SD video source in this house - an old video camera.
Third picture: Pretty! That's the 3.58MHz colour burst on the "front porch" of a scan line. Zoomed in (4th pic) it still looks pretty good, though not particularly sinusoidal. So back to reality. This thing totally does what hobbyist scopes need to do. You could debug a switching power supply with it, for example.
Just for laughs, back to the square wave at the same horizontal resolution (250ns/div) as the last capture. You can see the artifacts, but all in all it looks square wave-ish. Note the probe was compensation adjusted at 1KHz so it may not be perfect at this zoom level.
It's not the probes by the way. I tried a high quality, Tektronix 250MHz scope probe that I happened to have, and the waveforms look essentially the same.
-
Well, the version mystery is solved.
Zoyi states:
Just to let you know, the factory's latest version right now is 1.2.7. If someone says they got 1.3.0, that's actually an internal naming method by the engineering department.
In reality, both versions are the same. Whenever there's a new update, I'll let you all know here first.
See this video:
https://www.youtube.com/watch?v=aCMwXynzIV8 (https://www.youtube.com/watch?v=aCMwXynzIV8)
-
Whoa! I could handle "ringing" on the edge, but every edge looks different! 10s persistence shows the variation.
Totally to be expected. The sampling rate would need to be an exact integer multiple of the signal fundamental frequency to make every cycle display the same.
-
Anyone else getting BLOCKED from going to thedmm.com website?
It might just be my particular AntiVirus (AVG)... AVG is stating:
"We've safely aborted connection on thedmm.com because it was infected with URL:Blacklist"
-
That sounds like a bad joke :D It's great to release new firmware versions that don't change anything :D But it looks like product support exists.
-
It's funny that all three downloadable versions have different sizes, although Tim claims they are all the same!
-
Hello, what I have noticed is the occasional appearance of artifacts around the triggering edge. Besides, there are extra artifacts when persistence is turned on (as far as I remember - they have been mentioned within this thread). Also - there are problems with trigger level. To provide stable signal it must be set close to a signal base line. If it it set closer to the upper level but still below the signal amplitude then the oscilloscope looses synchronization. In fact the occasional artifacts around the triggering edge and problems with triggering are the most annoying. And the buzzer - is generates sound in multimeter mode while it remains silent in oscilloscope mode. There should be an option of controlling the sound in both modes at once. This is why I'm very much interested in release of an updated firmware :)
-
My hunch is that some of these versions might be beta version that their engineers are working on and they have not yet a stable (for release) version yet.
I think Tim (Zoyi/Zotek) might not have said it the best way...
-
Cheap scope expectation management.
I have an old 15MHz analog scope. It is honestly 15MHz. If you put in a higher-bandwidth signal, you see a 15MHz low-pass filtered version of it. For example, a 6MHz square wave will look pretty rounded, but rock steady with no strange artifacts.
I agree with the comment of managing the expectations of these devices.
Input signals with fast transitions can show ringing on the reconstructed displayed waveform due to sampling and interpolation. The sin(x)/x only works accurately for band limited signals presented to the ADC input.
In the Excel examples below, the blue dots show the sampled values and the red line the sin(x)/x interpolation.
The first case is with fast transitions and the second case is with slower (band limited) transitions presented to the sampling device.
[attach=3]
[attach=1]
The example below shows reconstructing a 7.1 MHz sine wave with a sampling rate of 40MSa/s.
[attach=2]
-
Hi. I have been a member for a long time, but I just rejoined because my membership seems to have lapsed; possibly for lack of posting, lol. Anyway, I thought you might like to know that the latest firmware for the ZOYI ZT-703S, version ZOYI-703S-FW-V132.ZTK is now available on the official website here: https://zotektools.com/firmware-update-703/ I have installed the firmware without any issues. I have not yet had time to see what has been updated, except that I notice I now also have a X100 probe option. ;D
-
Official update to 1.32 worked for me as well. Beside the 100x option, there seem to be no visible news in the menu. Not 100% sure, but the AUTO function seems to make better choices with offsets and sensitivity when using 1 channel vs 2 channel. The vpp,min,max measurements give readings that do not depend on the vertical offset anymore. RMS though does change with the vertical offset. Still, the measurements are off by a lot for spiky signals like pulses with a low rep rate. It looks as only a fraction of the displayed data is used for the measurements and thus the peaks while visible might get thrown out of the analysis.
-
a quick tip for the problem of the BNC connectors being too tight/short: Get a BNC T or 90deg adapter and file down the end of it by a few 100 microns. Probably leave it on the meter.
-
If I update to the new 1.32 (the thing now has "1.30" on it) and something stops working that previously worked
- will it accept a firmware downgrade?
- where can I get the older 1.27 release, just in case?
Goes without saying I'll keep the 1.32 upgrade file around for potential future use.
-
If I update to the new 1.32 (the thing now has "1.30" on it) and something stops working that previously worked
- will it accept a firmware downgrade?
- where can I get the older 1.27 release, just in case?
Goes without saying I'll keep the 1.32 upgrade file around for potential future use.
On the thedmm.com the link still points to v1.27 (at least yesterday it was, right now I cannot check it):
1. go to the website: https://thedmm.com/shop/zt-703s/ (https://thedmm.com/shop/zt-703s/)
2. Scroll down to the "Download File" button
3. Click on the button -> https://drive.google.com/file/d/1j5GLloua8nbk5bFO4p7Zw5z5m3VUuqUF/view?usp=drive_link (https://drive.google.com/file/d/1j5GLloua8nbk5bFO4p7Zw5z5m3VUuqUF/view?usp=drive_link)
-
Downgrading from 1.3.2 to 1.2.7 works without problems as long as the USB-Mode works. I just had temporary problems with the scope getting recognized in USB-Mode with FW Version 1.3.2. The USB-letter appeared and disappeared on my Windows 11 Desktop after a
split of a second! I reverted my last change in the setup options and the scope was recognized again. The change was switching off the 4th parameter in the measure-Menue (VMAX also seen in the following attachments) on Channel 2, don`t know if this caused the problem. I could not reproduce it. Probably a reset to default would have solved the USB-Problem also.
Anyhow, the FW 1.3.2 like the versions before still has the problem of sporadically showing distortions in the waveform like in this examples:
[attachimg=1]
[attachimg=2]
Has anyone made similar experience?
Short update:
I got the USB-recognition-problem also with FW 1.2.7 and independent of the number of parameters shown in the measure box. Maybe I have a faulty unit...
-
Anyhow, the FW 1.3.2 like the versions before still has the problem of sporadically showing distortions in the waveform like in this examples:
(Attachment Link)
(Attachment Link)
Has anyone made similar experience?
I was curious about this behaviour and did some experimenting. Used the built in generator with triangle and 100Hz to be in the same range as your signals. I can reproduce such signal shifts only if I set the the trigger horiz offset OUTSIDE the current time window. The 703 shows a small horizontal green arrow in this situation. Normally if the trigger is within the time window, there is also the trigger 'T' visible in this range pictogram at the top. Your last screenshots however show that the trigger is in the current time window and in this case I did not observe the effect. It is a bit of a problem that potential large horizontal offsets after zooming into a waveform in STOP/HOLD mode are not reset when you go back to RUN mode. I have to click quite a bit to get it back into range. Maybe a long-press on TRIG should better not only reset the trigger level but also the trigger offset.
-
I guess it is the same problem as I have observed.
1st picture: the signal (I've confirmed the signal purity with another oscilloscope):
2nd picture: What oscilloscope shows - 1st timebase settings (the frequency measurement is disturbed)
3rd picture: What oscilloscope shows - 2nd timebase settings
The problem occurs no matter if persistence is active. It also appears on second channel.
-
I was curious about this behaviour and did some experimenting. Used the built in generator with triangle and 100Hz to be in the same range as your signals. I can reproduce such signal shifts only if I set the the trigger horiz offset OUTSIDE the current time window. The 703 shows a small horizontal green arrow in this situation. Normally if the trigger is within the time window, there is also the trigger 'T' visible in this range pictogram at the top. Your last screenshots however show that the trigger is in the current time window and in this case I did not observe the effect. It is a bit of a problem that potential large horizontal offsets after zooming into a waveform in STOP/HOLD mode are not reset when you go back to RUN mode. I have to click quite a bit to get it back into range. Maybe a long-press on TRIG should better not only reset the trigger level but also the trigger offset.
I can confirm, that the artifacts appear reproducible on sweeping the horizontal trigger offset to the right and/or to the left border, also in run mode. Also the frequency reading changed to a wrong value while scrolling. After pressing the stop button I counted 130 ms distance with my setup (values and ranges in the picture) until the exact same distortion was showing up.
-
I find ZT-703S to be very useful and a great upgrade over ZT-702S. As its predecessor, it is very intuitive in use, but I'm missing an option to cycle through cursor modes by long pressing F4. Other Fn keys have well-thought-out long-press functionalities, only F4 has none.
-
Do you have cursors turned on by selecting menu and cycling through until where you can specify what cursor type? (Horizontal, vertical or both...) This has to be set prior to the F4 key selecting any cursors. If you don't, F4 won't do anything. I've had no problems with any of the firmware versions from 1.27 on, haven't tried prior versions.
I find ZT-703S to be very useful and a great upgrade over ZT-702S. As its predecessor, it is very intuitive in use, but I'm missing an option to cycle through cursor modes by long pressing F4. Other Fn keys have well-thought-out long-press functionalities, only F4 has none.
-
I'd like to post that like many others, when I received my 703S I was unable to get probes locked onto the BNC connectors.
I'm happy to report that after usage for awhile that the supplied probe goes on and locks as it should without undue twisting. I haven't used the second channel much so putting the probe on that and getting a lock is still problematic. My guess is should I use that connector more often it would loosen up a bit as well.
It shouldn't be an issue at all and I'm glad it resolved itself before I started modifying the case or probes.
-
Do you have cursors turned on by selecting menu and cycling through until where you can specify what cursor type? (Horizontal, vertical or both...) This has to be set prior to the F4 key selecting any cursors. If you don't, F4 won't do anything. I've had no problems with any of the firmware versions from 1.27 on, haven't tried prior versions.
Yes, but I don't understand, why they haven't assigned cycling through these menu options (cursors: none, horiz., vert., both) to F4 long-press. It would be way more convenient, than navigating through the menu. Especially, since there is nothing else assigned to F4 long-press.
-
Probably because you'd have to cycle through all the cursors, horizontal and vertical, to adjust the ones you want. If you're only interested in time then having horizontal cursors you don't use just adds info you don't need on screen. And, you may not want cursors visible at all. I think the approach is a good one given the limitations of a handheld but hey, I'm open to suggestions!
Yes, but I don't understand, why they haven't assigned cycling through these menu options (cursors: none, horiz., vert., both) to F4 long-press. It would be way more convenient, than navigating through the menu. Especially, since there is nothing else assigned to F4 long-press.
-
I find ZT-703S to be very useful and a great upgrade over ZT-702S. As its predecessor, it is very intuitive in use, but I'm missing an option to cycle through cursor modes by long pressing F4. Other Fn keys have well-thought-out long-press functionalities, only F4 has none.
Do you really use the cursor tool on this small instrument? Fo me the current F4 it is a total waste. I would rather suggest to have the trigger mode or measurement settings on this button.
Another one: The long press on F2 (move) should not only reset the vertical offset but also the horizontal offset.
-
Do you really use the cursor tool on this small instrument?
Yes, it is very useful for me. I was missing cursor functionality in ZT-702S. For me, it is one of the most crucial functions, way more useful than automatic measurements.
-
https://drive.google.com/file/d/1KHQ1eRaz8SKMaxU8eJanosP-IL7But85/view (https://drive.google.com/file/d/1KHQ1eRaz8SKMaxU8eJanosP-IL7But85/view)
ZOYI-703S-FW-V132.ZTK
-
Official update to 1.32 worked for me as well. Beside the 100x option, there seem to be no visible news in the menu. Not 100% sure, but the AUTO function seems to make better choices with offsets and sensitivity when using 1 channel vs 2 channel. The vpp,min,max measurements give readings that do not depend on the vertical offset anymore. RMS though does change with the vertical offset. Still, the measurements are off by a lot for spiky signals like pulses with a low rep rate. It looks as only a fraction of the displayed data is used for the measurements and thus the peaks while visible might get thrown out of the analysis.
Some info on what's new in Firmware 1.3.2 (by Tim - who left Zoyi):
1， Fix the inaccurate duty cycle measurement.
2， Add probe attenuation of X100.
3，Add voltage amplitude calibration, and include amplitude calibration test in the manufacturing process.
Source: comment section of this video: https://www.youtube.com/watch?v=DKtDI40kfBc&ab_channel=Tim1Tim2 (https://www.youtube.com/watch?v=DKtDI40kfBc&ab_channel=Tim1Tim2)
PS: Some time ago on this forum thread there was some speculation about the trustworthiness of firmware updates from various sources and the conclusion was more or less that the Zotek official Google Drive is the best. Now it's fun to see how untrustful are the members of the dt380.com Chinese forum with the zotektools.com website. As I learned on the forum they're getting the firmware updates directly from Zotek support in mail which they post/share in the forum. For them that's the only reliable source, and not the English Zotek site... :D
-
I guess it is the same problem as I have observed.
1st picture: the signal (I've confirmed the signal purity with another oscilloscope):
2nd picture: What oscilloscope shows - 1st timebase settings (the frequency measurement is disturbed)
3rd picture: What oscilloscope shows - 2nd timebase settings
The problem occurs no matter if persistence is active. It also appears on second channel.
Hi the aneng is going well? Is the hardware the same as zoyi 703s right? The firmwares update well? Thanks
-
Hi the aneng is going well? Is the hardware the same as zoyi 703s right? The firmwares update well? Thanks
I don't know about Aneng, but I have some BSIDE ZT-702S and Zotek firmware totally works. The only difference between Zotek/Zoyi-branded scopes and BSIDE is the splashscreen that doesn't say ZOYI but DIGITAL OSCILLOSCOPE.
That splashscreen does not change after flashing Zoyi firmware.
-
The measurement values in Scope mode seem to have more problems than I thought before when in DC input mode(FW1.32). I measured the switching on signal of my PSU at 12V setpoint. I set the scope to 100ms/div and 5V/div. The signal on the screen clearly shows the 12V amplitude of the voltage ramp. The vpp,max,min values are completely off and do depend on where I set the vertical offset.
Zoyi please fix this. I cannot imagine that this is hard to do.
-
Hi the aneng is going well? Is the hardware the same as zoyi 703s right? The firmwares update well? Thanks
I don't know about Aneng, but I have some BSIDE ZT-702S and Zotek firmware totally works. The only difference between Zotek/Zoyi-branded scopes and BSIDE is the splashscreen that doesn't say ZOYI but DIGITAL OSCILLOSCOPE.
That splashscreen does not change after flashing Zoyi firmware.
I see, I think that is just the bootloader splashscreen
-
Zoyi, Zotek, if you are reading this: this device could be for the scope world what Quansheng UV-5 is for the radio world!
Sell the hardware but make the firmware open source!
-
I had to sell mine because there were too many bugs in the software which made the oscilloscope not trustful. I'm sure that the producer will solve these issues, but this will take time.
The signal generator that operates exclusively with the oscilloscope was a cherry on top :)
Otherwise it would be a great inexpensive tool. Soon I will compare the ZOYI 703s with ZEEWEII DSO3D12, which I recently bought. The new one seems better in terms of user interface and the possibility of using multimeter, oscilloscope and generator simultaneously.
-
Zoyi, Zotek, if you are reading this: this device could be for the scope world what Quansheng UV-5 is for the radio world!
Sell the hardware but make the firmware open source!
Hahaha chinese are not very keen on opening firmware.. even if they are force to like with android
-
Hahaha chinese are not very keen on opening firmware.. even if they are force to like with android
Well, the radio I mentioned above is Chinese and sales exploded precisely because it can be flashed with custom
firmware that added LOTS of extra functionality. Zotek can, at least, leave the apps open source or publish a SDK.
There are four free app shortcuts besides the image viewer and the signal generator.
-
Hahaha chinese are not very keen on opening firmware.. even if they are force to like with android
Well, the radio I mentioned above is Chinese and sales exploded precisely because it can be flashed with custom
firmware that added LOTS of extra functionality. Zotek can, at least, leave the apps open source or publish a SDK.
There are four free app shortcuts besides the image viewer and the signal generator.
Unfortunatly if somnething opensource appears, it will be a new one created from scratch, like openwrt
Is not very common having multimeters upgradeable
-
Unfortunatly if somnething opensource appears, it will be a new one created from scratch, like openwrt
OpenWRT wasn't created from scratch. Originally it was based on GPL code that Linksys had to release.
There are code created from scratch for oscilloscopes (plus reverse engineering the hardware):
- Fnirsi 5012h, by EEVblog member atadarov:
https://www.eevblog.com/forum/projects/reverse-engineering-fnirsi-5012h/ (https://www.eevblog.com/forum/projects/reverse-engineering-fnirsi-5012h/)
- Fnirsi 1013d, by EEVblog member pcprogrammer (and later updated by others):
https://github.com/pecostm32/FNIRSI_1013D_Firmware (https://github.com/pecostm32/FNIRSI_1013D_Firmware)
https://www.eevblog.com/forum/testgear/fnirsi-1013d-100mhz-tablet-oscilloscope/2200/ (https://www.eevblog.com/forum/testgear/fnirsi-1013d-100mhz-tablet-oscilloscope/2200/)
-
Unfortunatly if somnething opensource appears, it will be a new one created from scratch, like openwrt
OpenWRT wasn't created from scratch. Originally it was based on GPL code that Linksys had to release.
There are code created from scratch for oscilloscopes (plus reverse engineering the hardware):
- Fnirsi 5012h, by EEVblog member atadarov:
https://www.eevblog.com/forum/projects/reverse-engineering-fnirsi-5012h/ (https://www.eevblog.com/forum/projects/reverse-engineering-fnirsi-5012h/)
- Fnirsi 1013d, by EEVblog member pcprogrammer (and later updated by others):
https://github.com/pecostm32/FNIRSI_1013D_Firmware (https://github.com/pecostm32/FNIRSI_1013D_Firmware)
https://www.eevblog.com/forum/testgear/fnirsi-1013d-100mhz-tablet-oscilloscope/2200/ (https://www.eevblog.com/forum/testgear/fnirsi-1013d-100mhz-tablet-oscilloscope/2200/)
Then that would be great... but I don't thin that will happen :(
PD: I just got my "zoyi 703S" now rebranded by aneng aos03 65 € in aliexpress with coupons and offers (battery included), not bad right? :D
-
New, v1.35 FW is published on the d380 forum.
http://www.dt830.com/forum.php?mod=attachment&aid=NDU2NjJ8YWQ0YmU0MmJ8MTcxNDA3OTU3MnwwfDg0MDA%3D (http://www.dt830.com/forum.php?mod=attachment&aid=NDU2NjJ8YWQ0YmU0MmJ8MTcxNDA3OTU3MnwwfDg0MDA%3D)
It is mentioned, that the AUTO function was improved in this version.
-
New, v1.35 FW is published on the d380 forum.
http://www.dt830.com/forum.php?mod=attachment&aid=NDU2NjJ8YWQ0YmU0MmJ8MTcxNDA3OTU3MnwwfDg0MDA%3D (http://www.dt830.com/forum.php?mod=attachment&aid=NDU2NjJ8YWQ0YmU0MmJ8MTcxNDA3OTU3MnwwfDg0MDA%3D)
It is mentioned, that the AUTO function was improved in this version.
The malware prevents me from downloading, is it safe?
-
Yes, it's safe for the PC and functional on the 703S, I flashed it yesterday.
-
The measurement values in Scope mode seem to have more problems than I thought before when in DC input mode(FW1.32). I measured the switching on signal of my PSU at 12V setpoint. I set the scope to 100ms/div and 5V/div. The signal on the screen clearly shows the 12V amplitude of the voltage ramp. The vpp,max,min values are completely off and do depend on where I set the vertical offset.
Zoyi please fix this. I cannot imagine that this is hard to do.
looks like this issue is fixed in fw 1.35. The min/max measurements still give funny results in roll mode and stopped. Btw, the trigger level value shown at the top is nonsense. Note , the trigger vert position on the Zoyi is always related to the screen coordinates. When you switch the vert sensitivity , the trigger arrow stays at the same position. A bit unusual for me, but for this small unit maybe not a bad choice.
-
I did some tests with the Zoyi and some other meters I have access to. The AD780 was trimmed to give a 2.5000V output on the (old) HP desktop meter. The film capacitors were measured with an Agilent 4294A impedance analyser at 10KHz. The table shows that my 703S gives the results closest to the ones by the more advanced equipment. Yet most of the meters tested do well enough for most situations. Even the 10$ T7 component tester gives great results!
[attachimg=1]
-
Good Day!
Just want to know if ZT-703S is a good multimeter+oscilloscope for a hobbyist like me. I am coming from a DSO150. Which is a better buy among these:
Zoyi ZT-703S ~ 37.80USD (New)
Owon HDS242S ~ 74.16USD (New)
Owon HDS2202S ~ 78.07USD (Used)
At double the price, does the owon variants have better features, accuracy, reliability?
Thanks!
-
I did some tests with the Zoyi and some other meters I have access to. The AD780 was trimmed to give a 2.5000V output on the (old) HP desktop meter. The film capacitors were measured with an Agilent 4294A impedance analyser at 10KHz. The table shows that my 703S gives the results closest to the ones by the more advanced equipment. Yet most of the meters tested do well enough for most situations. Even the 10$ T7 component tester gives great results!
Would you mind sharing what version firmware the Zoyi 703S used in your testing has? Thanks!
-
Would you mind sharing what version firmware the Zoyi 703S used in your testing has? Thanks!
fw was 1.32. I now tried 1.35 and there is no change in the results (as I would assume).
-
Good Day!
Just want to know if ZT-703S is a good multimeter+oscilloscope for a hobbyist like me. I am coming from a DSO150. Which is a better buy among these:
Zoyi ZT-703S ~ 37.80USD (New)
Owon HDS242S ~ 74.16USD (New)
Owon HDS2202S ~ 78.07USD (Used)
At double the price, does the owon variants have better features, accuracy, reliability?
Thanks!
Where did you find these prices? I can find just these lowest prices:
Zoyi 703s shipped to the Philippines is USD 75 on Aliexpress,
Owon HDS242S is USD 144 on Banggood at the moment
Be careful, because sometimes the price os other models are shown if you search for these products (e.g. Zoyi 702 and Owon HDS242 - which doesn't have signal generator)
The 2 products are close to each other in specs, but Owon is double the price. I'm not an electornics expert at all, but based on what I've read so far I found the Owon HDS242S far better than the Zoyi 703s.
Pros for Owon HDS242S compared to Zoyi 703s (for me):
- It seems it has the same hardare as the 70 MHz model, therefore the signal amplitude doesn't shrink even when measuring above 30MHz
- Usable signal generator (Zoyi 703s is very noisy -> low quality, signal output is not BNC)
- Works as described, it meets the specifications
- Has more probe settings e.g. x1000, x10000 (Zoyi has x100 starting since a recent firmware update)
- 4400 mAh battery capacity - 2x 18650 battery (vs. 3400 mAh, 1x 18650 battery in Zoyi)
- Horizontal scale: 5ns/div-1000s/div (Zoyi has 10ns/div-20s/div)
- Stable and accurate software (Zoyi has a lot of inaccuracy issues in the measurements)
Cons for Owon HDS242S compared to Zoyi 703s:
- Has only 8K memory (Zoyi has 128K)
- Multimeter part has "just" 20 000 counts (Zoyi has 25 000)
- It seems firmware is not being updated (Zoyi is continuously gettig FW updates - unfortunately it doesn't mean that all known issues are fixed)
- Somewhat lower bandwidth based on specs: 40 MHz (Zoyi _claims_ 50 MHz, but while you can measure in Owon's full specified bandwidth, with Zoyi's it's not the case)
- Only sold with 1 probe (Zoyi is sold with 2 probes as an option)
All in all I found the HDS far more superior than the Zoyi, but it also comes with an almost 2x price tag.
DISCLAIMER: I have very limited knowledge in electronics. This is solely my opinion and understanding based on the information from manufacturers or elsewhere I found on the Internet. I don't own any of these products.
-
Just as I was warming to this device it's let me down in testing in-circuit AC readings.
It shows a voltage then goes to 0, setting the range manually does nothing.
Use case: Macintosh Plus vintage computer power supply. Visual map of what expected in-circuit voltages should be in both AC and DC.
Uni-T 61 shows expected 20VAC on cathode and Zoyi 703 just couldn't lock on.
Was able to repeat this failure of flashing a reading then going to 0VAC on other test points too.
So I can't quite use this as a multimeter
-
Owon is more imprecise, but more reliable in my opinion.
Owon also has hardware errors, the HDS2202 series drains the battery quickly, consumes 1.3A current.
There are times when the message Low battery appears on the display, but the device continues to operate for an hour or so. :scared:
There is sometimes a slight DC offset, perhaps due to heating.
But it is true that the function generator is very good.
Its structure creates a professional feeling, it is quite tough.
It also has some good sides, for example 1Gs/s even with two channels. 8)
But for the rest, sampling is halved! From HDS242 to HDS2102
For 78 USD, I think it's worth it, even if you look at the small memory 8k. This is just my personal opinion.
I have not yet seen a video in which they tested whether the Zoyi use its 128k memory in all time bases.
Fnirsi has already surprised me... In a bad way... :palm:
To be honest, I have not yet seen a study in which they discuss the minimum amount of memory required for different measurements. :-//
-
Firmware version: V138.
Modifications:
- multimeter mode memory function, which will record the last measurement gear after turning on and off or switching modes,
- optimizing the AUTO function,
- repairing the closed channels that will be opened during automatic measurement,
- repairing the difference in true effective values
- inaccurate position measurement problem
-
I noticed that Fcnt works correctly only with squarewave signals. FW latest 138.
-
I have updated the firmware using v1.2.8 from the szzotek.com website and it works well on my unit (boot v1.0.15) although I still cannot tell what is changed in this version :)
If someone from Zotek is reading this: PLEASE put in an option to mute the beeps and bring back the temperature reading!!! We will supply our own thermocouples!
I really want this multimeter as a nice little all-in-one but the lack of thermocouple/temperature measurement is a big turnoff. That being said, the https://zotektools.com/products/zoyi-zt-703s/ (https://zotektools.com/products/zoyi-zt-703s/) website shows
"Temperature" under features and the image even has the probe icon printed above the jack unlike the 703S listings on Amazon and Aliexpress. Maybe we need to wait for the market to sell off the existing ones before we see the most recent version for sale?
-
zoyi said they had problems to implement both temperature sensor and two channel system at the same time
-
*** newbie here, sorry for any inconvenience ***
Is there any reason NOT to install firmware 1.38?
Seems the youtuber tim1tim2 is a insider of the manufacturer or at least related to https://thedmm.com/ (https://thedmm.com/) and didn't mention it at its channel at all!?
https://www.youtube.com/@tim1tim2 (https://www.youtube.com/@tim1tim2)
Last video is from may-01
-
*** newbie here, sorry for any inconvenience ***
Is there any reason NOT to install firmware 1.38?
Seems the youtuber tim1tim2 is a insider of the manufacturer or at least related to ...
I've installed it and found no troubles. I like the fact that it stays in the last mode you left it in. I did have one incident where I had left it overnight and I swore it had 3 bars of battery life. Went to turn it on the next day and it was dead as a door nail. Charged it back up and haven't had a problem sense. I'm not saying it's related to firmware 1.38 at all. Only that that had never happened before so who knows... I mention it in case anyone else has ever seen similar.
-
hi all! became the owner of 703s
Firmware 1.38 seems to have a problem with AutoRange at high frequencies
4mHz - ok
24mHz - not ok
took measurements from quartz oscillators on the device board
at a frequency of 24 MHz it begins to detect normally if you rearrange the x10 divider on the probe itself
on x1 does not see generation
---------------
Sorry for my English - I'm writing through an online translator
-
24mHz - not ok
at a frequency of 24 MHz it begins to detect normally if you rearrange the x10 divider on the probe itself
Hello!
The capacity of the probes in X1 mode is ten times greater than the capacity of the probes in X10 mode. Such a large capacitance greatly affects the operation of small circuits such as a quartz resonator.
Moreover. In X1 mode, the recommended frequency of the signals under study should be in the range of 5-10 MHz, then you should switch to X10 mode.
With best regards.
-
High resolution images here: https://imgur.com/a/c2Oi1iY
Thanks for the excellent photos!
Does it charge the battery to 4.34V? The charger IC is an ME4059D, which has a fixed charge voltage of 4.34V.
-
Does it charge the battery to 4.34V? The charger IC is an ME4059D, which has a fixed charge voltage of 4.34V.
The battery charges up to 4.25 volts. This may be the result of the built-in battery protection and therefore the charging LED blinks right before it is completed.
-
Firmware version: V138.
Modifications:
- multimeter mode memory function, which will record the last measurement gear after turning on and off or switching modes,
- optimizing the AUTO function,
- repairing the closed channels that will be opened during automatic measurement,
- repairing the difference in true effective values
- inaccurate position measurement problem
I have the 703S, and the features/money is quite impressive.
I would like to measure Pulse Width negative / Pulse width positive on single shot pulses. (monostable calibration checks)
Does anyone know if a firmware update plans to add Pulse Width negative / Pulse width positive ? (on single shot pulses ? )
138 seems to be the latest ?
-
Just pick up a zt-703s with FW 1.3.5. I found a problem. I measured my battery (8.22V) with reversed polarity, the MIN will max out at -1V. Updated to FW 1.3.8, it's better, I got -8V for MIN, but the actual reading should be -8.22V. On the other hand, MAX reading was fine and accurate. Is there anyone having this problem too?
-
Yes, there is such a problem too. Firmware 1.3.8, you will have to observe the polarity of the probes when measuring.
-
I just bought a new ZT-703s and, for the record, the board is marked "v2.2" (which is newer than anything I've seen online) and "202403 12", as shown in the image below (they even missed removal of some chip markings, revealing the clues "D" and "R"). The battery is still tightly-packed, but I'm probably not going to touch the spring.
It shipped with firmware 1.3.2, and I quickly updated it to the latest 1.3.8. I'm mainly using it to read voltages and check slow flicker noise (over the course of minutes) with the serial UART 3Hz-logging feature mentioned earlier in this thread.
I *believe* voltage readings are a little out of spec on this unit, reading 10.015V on what was once a 10.002V reference (but is now uncalibrated). I did not get a stamped QC card, which some online videos show to be included, so I wonder if this unit was even calibrated. In case anyone is in the Minneapolis area in USA with a precise voltage reference/meter and wants to look at this device (of course, it's really just a favor to me!), please contact me.
-
I received my ZT-703S yesterday.
I also got the "newer" version.
PCB version: v2.2
Boot version: V1.0.16
APP: V1.3.2 > updated to V1.3.8
And in my unit the marking on the chip is also partially visible (D and R visible).
One thing that is strange for me is that the metal can that covers the scope input is left partially open on the both sides. Is that so on the older models also?
Would it make any difference if i solder a copper tape over the openings, so it would be completely covered?
-
That made me curious to open mine that I ordered in March and received early April. Also v2.2, but date is 20240222. No visible D and R.
-
@xKertx
I didn't notice this before, but now see that my can is "partially open" too.
I imagine they did this to let heat out, so I would not cover it up with copper tape.
-
I havre just got the zt-703s from aliexpress.
but I have this problem. osiloscope seems working but multimeter mode does not start. it seems it is stuck like in video.
https://www.youtube.com/shorts/cMMDfdvmfbs (https://www.youtube.com/shorts/cMMDfdvmfbs)
does anyone have this problem?
-
I havre just got the zt-703s from aliexpress.
but I have this problem. osiloscope seems working but multimeter mode does not start. it seems it is stuck like in video.
https://www.youtube.com/shorts/cMMDfdvmfbs (https://www.youtube.com/shorts/cMMDfdvmfbs)
does anyone have this problem?
try updating the firmware
-
I havre just got the zt-703s from aliexpress.
but I have this problem. osiloscope seems working but multimeter mode does not start. it seems it is stuck like in video.
https://www.youtube.com/shorts/cMMDfdvmfbs (https://www.youtube.com/shorts/cMMDfdvmfbs)
does anyone have this problem?
try updating the firmware
I have done already it was 1.3.2 now 1.3.8 but same....
-
I'd pull the battery and let it sit for a bit. If that doesn't work I'd send it back, I've found nothing on mine that would make it non-responsive. Good luck!
-
I'd pull the battery and let it sit for a bit. If that doesn't work I'd send it back, I've found nothing on mine that would make it non-responsive. Good luck!
it didnt work also :(.
-
Please take a look at this post (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5325065/#msg5325065).
If the device starts again, do a reflash with newest firmware.
-
After a long time a new firmware on the horizon (V1.39):
ZOYI-703S-FW-V139 firmware.ZTK
https://www.szzotek.com/h-col-159.html (https://www.szzotek.com/h-col-159.html)
or direct download link:
http://8164272.s21d.faiusrd.com/0/ABUIABAAGAAgnOXYtAYo_OLtzAc?f=ZOYI-703S-FW-V139%E5%9B%BA%E4%BB%B6.ZTK&v=1721119388 (http://8164272.s21d.faiusrd.com/0/ABUIABAAGAAgnOXYtAYo_OLtzAc?f=ZOYI-703S-FW-V139%E5%9B%BA%E4%BB%B6.ZTK&v=1721119388)
I couldn't find any info about the improvements/updates in it.
-
The 1.39 changes are listed on the home page:
https://zotektools.com/firmware-update-703/
-
Has anyone tried the latest firmware - 1.3.9? For me auto range doesn't work when I'm measuring a mains 240V signal - works fine on 1.3.8? I've had to revert but interested of anyone else had any issues?
-
[attachimg=1]
1.3.9
-
I'm looking at the trace via the scope - not in multimeter mode.
-
It is working for me with 1.3.9 :
[attachimg=1]
-
1.3.9
*SAMPLE* appeared in the menu
*AUTO* mode works very poorly, the internal generator does not always detect
-
The *SAMPLE* function does not work well. The effect depends on the frequency of the signal and the scanning speed.
-
Well I just got this device but auto range seems very bad on 1.38 and 1.39. Almost worthless(?) Seemed to be much better on stock 1.32 it came with.
Is there older firmware files anywhere? Maybe I shouldn't have updated so quick.
-
;)
Attached are versions from 1.27 to 1.39
-
Same problem on mine, I updated the firmware without a solution, then I downgraded it to a version older than the one it came with and the problem was not solved, removing the battery for a long time also had no effect
-
Oh I think I see the problem now.
Set the function generator back to square wave. There's a limitation that the other waveforms prevent the scope from going below 100us/div. So it won't be able to detect most signals except lower frequencies.
-
If I remember correctly, this was not written in the early user manual, but now I found this line.
"Note: In the current mode, when the signal output waveform is pulse wave, sine wave, and sawtooth wave, the oscilloscope's maximum measurement time base is limited to 100us. If you switch to the restore time base, the signal output will be set to square wave."
Was this bug just swept under the carpet, or is there a proper explanation for why the signal generator behaves this way when you turn it on via the scope?
-
well, it is indicated in the dialog Menu|outoput|setting in Red that T/Div max to 100us/DIV.
So, not really under the carpet ;-)
-
1.3.9 generator cannot be turned off
-
I you set it to square wave you can set the horizontal scale to lower than 100us/Div
-
Same problem on mine, I updated the firmware without a solution, then I downgraded it to a version older than the one it came with and the problem was not solved, removing the battery for a long time also had no effect
If you mean multimeter does not open, it means something is wrong between osiloscope and multimeter chip communication. it may be a failed ic or bad soldering.
I have just returned my own scope because of it.
-
Mine isn't accurate in scope mode? Or am I doing something noob again? It always measures at least 0.2v lower than the DC voltage I'm measuring.
I tried calibration and resetting to defaults. I tried a different probe that didn't come with the meter. Same results.
-
My unit measures the voltage correctly, but the V1.3.9 firmware is really slow and sluggish.
Sometimes the menu freezes and buttons have about 2-3sec lag.
The auto range on the scope takes forever and usually it does not detect even its own 1Khz test signal.
I can see the signal in manual mode, but when i press auto, the voltage/time ranges goes up to 100v/25ns and obviously it can't show the test signal. So the auto function is totally unreliable and useless. It's almost impossible to capture a unknown signal in auto mode.
I really don't understand why they are wasting time to add new functions and "apps", when they should concentrate to get the basic stuff working reliably.
There is also a typo in the image viewer.
It says "Delate success" when i delete a screencapture.
-
I tested mine with a 9v battery, and in multimeter mode it said 9.0001v and in scope mode it measured around 9v, max measurement displayed voltage switched between 8.9 and 9v. I used the 1x mode on the probe since using x10 gave a slightly lower result, probably caused by not so precise resistors in the probe.
-
Still, I think the device is good, here are the latest tests. I use a homemade STM32 and SI5351 oscillator and a probe from a Soviet oscilloscope for testing.
The difference with the staff is striking.[/img]
-
Does everyone in mA mode measure AVG a thousand lower?
-
I have come up with new weird behavior.
i wonder anyone has same issue.
in mv mode when probes are open it just count up and up when I make short both probe then it turns 0 but again it count up and up.
-
i wonder anyone has same issue.
in mv mode when probes are open it just count up and up when I make short both probe then it turns 0 but again it count up and up.
This is not a problem but normal behavior of the multimeter. There would be a problem if the readings did not change.
The multimeter in mv mode has a high input resistance. If you short-circuit the probes and you see 0 on the display, this is normal.
-
I would like to use this oscilloscope for SMPS (240 Vac) measurements. There could be like 600-800 V on some components (diodes, mosfet, etc.).
I see here:
https://zotektools.com/products/zoyi-zt-703s/
that maximum input voltage is 300 V.
Is that valid for 1x or 10x probe?
I assume if it is valid for 1x probe, I can use 10x probe for 3000 V.
Or is that valid for 10x probe? I could not use it for the purpose I mentioned.
Or is it possible to use 100x probe? Will standard 100x probe fit to that nested connector?
-
The specification says
Maximum Input (DC+AC Peak)
Voltage
X1 range <150V,
X10 range <300V
I dont know why, it should be logical that 1x 150V and 10x 1500V or 1x 30V and 10x 300V. What is correct?
However, if you use 100x attenuation you can test higher voltages, that's what it seems to me.
-
I assume if it is valid for 1x probe, I can use 10x probe for 3000 V.
Or is that valid for 10x probe? I could not use it for the purpose I mentioned.
Or is it possible to use 100x probe? Will standard 100x probe fit to that nested connector?
Take a close look at the documentation for the P2060 probes that come with the ZT703!
I have highlighted in red the permissible max voltages for modes x1 and x10. And also study the important graph of the dependence of the permissible input voltage on the frequency of the input signal. A probe with a x100 divider is suitable for signals with an amplitude above 300V.
-
Or is it possible to use 100x probe? Will standard 100x probe fit to that nested connector?
You can use a 100x probe if the connector is basic bnc and fits physically. Bigger connectors wont fit because the connector on this scope is recessed.
Also, you will have to do the math all the time because all the readings will be off by 10x times.
The scopes settings have only two options 1x and 10x.
-
Also, you will have to do the math all the time because all the readings will be off by 10x times.
The scopes settings have only two options 1x and 10x.
You are mistaken, the latest firmware versions already have a x100 divider mode. I currently have version 1.3.8 installed.
Version 1.3.9 did not impress me.
-
You are mistaken, the latest firmware versions already have a x100 divider mode. I currently have version 1.3.8 installed.
Version 1.3.9 did not impress me.
Oh, i had to check it and yes, you are right.
My unit came with 1.3.2 and it didn't have it then. But it does now, after i updated it. Thats nice.
-
Setting x100 in 1.3.9 doesn't make any sense for this type of question. It's just a change of scale on the graph, the multimeter's properties don't change. Only the probe setting is important, and the graph itself can be set even x1 and calculated in your head.
-
There is a bug on 1.3.8 firmware. Power off in mA mode. Power on. It will keep switching between AC and DC current mode.
-
Setting x100 in 1.3.9 doesn't make any sense for this type of question. It's just a change of scale on the graph, the multimeter's properties don't change. Only the probe setting is important, and the graph itself can be set even x1 and calculated in your head.
Isn't this true with every scope?
The probe has the divider resistors and the settings on the scope will change the scale on the graph.
-
There is a bug on 1.3.8 firmware. Power off in mA mode. Power on. It will keep switching between AC and DC current mode.
I don't have the same error as you described. Show your video with this error.
Isn't this true with every scope?
The probe has the divider resistors and the settings on the scope will change the scale on the graph.
That's right, the scope correctly scales all measured voltages in x10-x100 modes, there is no need to recalculate anything!
-
So, is this scopometer actually suitable for measuring signals in SMPS? (in 230Vac system)
Or is there better ways or tools for this puspose?
-
So, is this scopometer actually suitable for measuring signals in SMPS? (in 230Vac system)
Or is there better ways or tools for this puspose?
It is risky with the included probe.
10x max 300V CATII.
I think it's worth buying a certified probe.
In 10x I can measure the mains 230VAC socket with it using the probe of my Micsig, it does not burn.
on the other hand, it would be safer with the 100x probe, or perhaps a differential measuring probe would be better.
Because if you want to use two channels, or if you're just messing around with the input, you can reach the outer part of the BNC with your hand...
-
There is a bug on 1.3.8 firmware. Power off in mA mode. Power on. It will keep switching between AC and DC current mode.
I don't have the same error as you described. Show your video with this error.
https://streamable.com/k7o5v9
-
What is the size of that hole with connectors? I mean what is the maximum diameter of probe that will fit in there?
-
What is the size of that hole with connectors? I mean what is the maximum diameter of probe that will fit in there?
The BNC connectors are in a 20x40mm rectangle.
A connector with a diameter smaller than 20 mm fits into the BNC.
Even the one that comes with it fits in uncomfortably.
-
Hi! Can i set null in multimeter mode with closed probes? (like in my agilent 1272)? my 703 indicates 0.1 Ohm and it's annoying :D
-
Hey guys,
I have a problem with my 703S.
I tried to compensate the probe by following the instructions on the manual and you tube videos.But I see a square wave on the display without any deviation at any condition.And no differences while screwing the adjustment screw.I tried this with three different probes.
The firmware version is 1.3.9.
Could you please let me know what is my mistake?
-
No expert, but did you set the probe switch to 10X?
-
I found a very interesting moment in my 703S. Everyone knows the "Aliasing" effect in oscilloscopes. This is when the sampling frequency of the oscilloscope
becomes equal to the frequency of the signal. So when feeding a meander with a frequency of 1 Mgz. at 703S, with a 5ms scan, "Aliasing" occurs,
a 165Hz meander is observed on the screen. This is observed in Normal mode, but when setting the High mode, this does not happen, the meander is only at
a frequency of 1 MHz. and a scan of 1.0 us. Does the 703rd really not reduce the frequency of discrediting in High mode when the scan time increases. The firmware version is 1.3.9. Who
thinks about this?
-
Any manual how to use osciloscopes? I bought this but I don't know anything about oscilos hehehe
BTW with 1.3.9 the signal generator doesnt work well
-
Any manual how to use osciloscopes? I bought this but I don't know anything about oscilos hehehe
BTW with 1.3.9 the signal generator doesnt work well
There are countless tutorials on the web and videos on Youtube. The forum owner himself has made many oscilloscope tutorials. This one is an Introduction.
https://www.youtube.com/watch?v=Iq4QlfH-oqk&list=PLvOlSehNtuHsCTtj-T_vkpTTbBXW4sB51&index=20 (https://www.youtube.com/watch?v=Iq4QlfH-oqk&list=PLvOlSehNtuHsCTtj-T_vkpTTbBXW4sB51&index=20)
If you'd rather read something, this is the first one coming up in a search. It looks pretty good.
https://learn.sparkfun.com/tutorials/how-to-use-an-oscilloscope/all (https://learn.sparkfun.com/tutorials/how-to-use-an-oscilloscope/all)
-
That's the solution 👍👍👍.
It worked . Thanks 🙏🙏
-
Another issue that drives me crazy while working with 703S . I want the display always be on . I am not worry about the charge !!! What should I do?
-
Another issue that drives me crazy while working with 703S . I want the display always be on . I am not worry about the charge !!! What should I do?
press the "MENU" button, navigate with the arrows to where "BL time" is, switch it to off.
There is an "Auto Off" which turns off the device after the set time.
-
Hi! what external software can be used with ZT-703S via usb connection?
-
Hi! what external software can be used with ZT-703S via usb connection?
Any file manager. That's all.
You can only retrieve saved screenshots or update the firmware via USB.
Even the multimeter readings must be read via the signal generator contacts. This will require a simple UART module with TTL levels.
-
Any developement for "MORE APPS"? hehehehe
-
Any developement for "MORE APPS"?
I hope not.
They should focus to the basic functions first, to get them working properly.
For example the "autoset" on the oscilloscope is useless, because it is so slow and unreliable.
-
Hello. Recently purchased a ZT-703S. I've upgraded to firmware V1.3.9. Is anyone else experiencing problems with the signal generator. Everything seems to be a square wave. |O
Also, is there an updated manual that has kept up with the revisions of the Firmware? Thanks. :)
-
Hello. Recently purchased a ZT-703S. I've upgraded to firmware V1.3.9. Is anyone else experiencing problems with the signal generator. Everything seems to be a square wave. |O
Also, is there an updated manual that has kept up with the revisions of the Firmware? Thanks. :)
I just upgraded my 703S to 1.3.9 last week, all the wave settings work for me. Scope --> Mode --> scroll to L or R to "Output", change wave there. Make sure you see the icon changing shape.
My 703S is BOOT:v1.0.14 and APP:v1.3.9
Verify your device did the actual upgrade.
As for the usefulness on this device, it's part of my bucket of meters, I use it for some things, don't use it for other things. It's not the only hand scope I have.
-
@Randy222 I was going in through More Apps, and the signal generator there and that is what was always generating a Square Wave, but then again, the keypress stream may be my fault. I tried your method and I was able to pull up different waveforms. The U.I. is a bit clunky. Still trying to get the hang of this scope-meter. :popcorn:
-
Just got my ZT-703S yesterday. It came with 1.32 and I immediately updated to 1.39. Auto range just doesn't seem to work at all on 1.39. It takes forever and just ends up on minimum time and 100V scales, so completely useless. When in AC mode it sometimes seems to work, but inconsistently.
I reverted to 1.32 and at least in the range I've been testing up to 1MHz, the auto-range captures the waveform and comes in ballpark range.
So, I'll be sticking with 1.32 for now. I think all the tweaking they have been doing in the latest firmware to get rid of the jitter in the high frequency range, may be affecting the auto-range? But that's just my ignorant guess.
Anyway, anyone interested in Auto-Range should try 1.32.
-
Anyway, anyone interested in Auto-Range should try 1.32.
Try v1.38. I decided on this version because Auto-Range does not work the same way as on v1.39 ;)
-
Anyway, anyone interested in Auto-Range should try 1.32.
Try v1.38. I decided on this version because Auto-Range does not work the same way as on v1.39 ;)
Thanks for the suggestion, I just tried 1.38 and see no difference to 1.39 concerning Auto Range on my unit. Reverted to 1.32 and it just works. Maybe there are hardware differences? I'll check my board version and post back if the board on my unit turns out to be an older version than the 2.2 that seems to be the current one.
FWIW my other scope is An OWON VDS1022i USB and auto-range seems to behave similarly to the 1.32, so that's good enough for me, since that's what I'm used to.
-
I'm on the same version 1.32 and foot.
I must say that because of this, I'm using the 703 less and less for oscilloscope purposes.
Thanks for the suggestion, I just tried 1.38 and see no difference to 1.39 concerning Auto Range on my unit. Reverted to 1.32 and it just works. Maybe there are hardware differences? I'll check my board version and post back if the board on my unit turns to be out an older version than the 2.2 that seems to be the current one.
FWIW my other scope is An OWON VDS1022i USB and auto-range seems to behave similarly to the 1.32, so that's good enough for me, since that's what I'm used to.
-
I'm on the same version 1.32 and foot.
I must say that because of this, I'm using the 703 less and less for oscilloscope purposes.
Sorry if this has been discussed before, but what is so problematic about V1.32 that you aren't using the 703 as a scope any more?
-
1.32 is oke the auto feature in higher version is slow and sometimes not even converging to the real values.
I'm on the same version 1.32 and foot.
I must say that because of this, I'm using the 703 less and less for oscilloscope purposes.
Sorry if this has been discussed before, but what is so problematic about V1.32 that you aren't using the 703 as a scope any more?
-
Thanks for confirming my observations.
When I received my unit with V1.32 I thought that maybe it was old stock, or they were too lazy to update it before shipping, but now I am starting to think it may have been intentional.
-
When using v1.32 and having ch2 disabled, it enables the ch2 every time when performing auto range. I think it's really annoying.
-
When using v1.32 and having ch2 disabled, it enables the ch2 every time when performing auto range. I think it's really annoying.
I just did several auto range tests with V1.32 and CH2 disabled before autorange and it is still disbaled after completing the autorange.
How do you know CH2 is being enabled?
-
How do you know CH2 is being enabled?
You will have the second (blue) line visible on the screen, and in the menu it says CH2 ON ::)
-
How do you know CH2 is being enabled?
You will have the second (blue) line visible on the screen, and in the menu it says CH2 ON ::)
OK, I was able to reproduce the problem. Once you disable it, it seems to stay that way even when you do multiple autoranges or power the scope OFF/ON. I couldn't find what exactly enables it.
Annoying little bug indeed! Thanks for pointing it out.
-
So, where is the ZT-701s?
Did they ever released that? :D
-
So, where is the ZT-701s?
Did they ever released that? :D
There are a few other competitors in the sub 5MHz, most of them presumably cheaper, smaller, etc... The production costs of the ZT-702s are probably similar to the ZT-701S, so my guess is they focused on the 702, which offers better build and features than the less populated competition in the sub 10MHz, and also on the development of the ZT-703s, again a very competitive product targeting the sub 50Mhz class.
It seems they are able to crank out model after model at dazzling speeds with better specs at a very competitive price cannibalizing their own products. The 701, just never even made it to market I guess in favor of the 702, the 702 isn't significantly cheaper than the 703 anymore, and when the next model, my guess is in the sub 100MHz hits the market for a similar price, the 703 will be history too.
-
The 701, just never even made it to market I guess in favor of the 702, the 702 isn't significantly cheaper than the 703 anymore, and when the next model, my guess is in the sub 100MHz hits the market for a similar price, the 703 will be history too.
Might the 702 or 703 have it's firmware modded by some coding guru? Wish it was open-sourced. Seems the hardware is worthy, but it's the programming that could be improved in a few key areas. :-BROKE
-
I agree, it would be something amazing!
-
The 701, just never even made it to market I guess in favor of the 702, the 702 isn't significantly cheaper than the 703 anymore, and when the next model, my guess is in the sub 100MHz hits the market for a similar price, the 703 will be history too.
Might the 702 or 703 have it's firmware modded by some coding guru? Wish it was open-sourced. Seems the hardware is worthy, but it's the programming that could be improved in a few key areas. :-BROKE
That would be sweet. Meanwhile we can continue betatesting for Zotek hoping they read this and fix things :-DD
-
What fuse rating do you all have on the mA plug?
Mine came with a 600mA fuse. Is that correct? Isn't it too high?
-
What fuse rating do you all have on the mA plug?
Mine came with a 600mA fuse. Is that correct? Isn't it too high?
Mine has 250mA written on it (don't know what the actual fuse is).
That's odd. If you google the zt-703s and zoom in at the photos, there are atleast three versions, 200mA, 250mA and 600mA.
So, are they using whatever fuses they can find cheaply? :wtf:
-
What fuse rating do you all have on the mA plug?
Mine came with a 600mA fuse. Is that correct? Isn't it too high?
Mine says 250mA next to the plug, but don't know the rating of the actual fuse inside.
-
What fuse rating do you all have on the mA plug?
Mine came with a 600mA fuse. Is that correct? Isn't it too high?
If you google the zt-703s and zoom in at the photos, there are atleast three versions, 200mA, 250mA and 600mA.
Oh I didn't even notice the label on the front is different in photos online. The Zoyi website shows photos of all three different labels.
Mine says 250mA on the front of the device. It has 600mA fuse inside. It's got a v2.2 PCB.
-
2.0
600 mA 250V in my case
But this is an ANENG instead of zoyi
-
My understanding of fusing is rather incomplete. Mostly recommendations are, follow manufacturer's recommendations, or that of the designer.
Well, there seems to be a good deal of variation in the fusing that has been supplied by the manufacturer, and to top that off, the manual (outdated) doesn't specify the fuses for replacement.
I was always of the understanding (mis-understanding?) that fusing existed to protect the circuitry in an electronics device. Further, that you'd want to use a fuse just slightly higher rated in current carrying capability than that consumed by the circuit it protects. And if one wished to provide some additional margin in that fusing, one could go to a rating as high as that which could be tolerated by the wiring, traces, and other components in the current flow-path.
If the device were to read mA current up to the spec of 250.00mA (from the outdated manual), then I could imagine the ideal fuse to use for the mA input path on the scope to be rated somewhere between 1.5x to 2.0x of this value, therefore between 370 to 500mA.
So I could see the manufacturer (or rebrander) utilizing a fuse of 600mA. I would imagine 200mA or 250mA to be too small.
Can someone provide the size / rating of the fuse that should be used in the circuit should it fail, and a source to acquire them?
My PCB is V2.2 and has a 250mA ceramic fuse that is 20mm long. I was thinking of replacing it with a 500mA rated fuse.
Perhaps the following (as an example):https://www.amazon.com/ZUPAYIPA-F0-5AL-Fast-Blow-0-5amp-Ceramic/dp/B07KZRR3GL/ref=sr_1_1?crid=SVXYPSC429GV&dib=eyJ2IjoiMSJ9.6vzKtaZjL9er9MqtA5o3gyBfOyZWQ22wWwdENLgskL1Hc6u5LKPXXUuEOk6xCvi8yTe44QZUXv-69vCTIcWFHFy6l_oVDFzmUHaQj9l89Kh_WXwFdTjRRgwl1LgeT-q2bNj38QeeZp6kdhplAR7JuRiuqZiomZboXPLww_4WQjO2n2tF4DxmO-4vGTdi4D36z-dKvMgeEvmUobCV66Rw2d3TKYIM4WAGgEN1dmiIbzi68-w798Jn0PVBmmm5_ur_3lyr1NcInvCrWjfC-UvwYcHfXofguqXTQvZb8UjIoZ4.CnWMkbGIyzco43HT6R9PxAj8rVGLU_lSpNcFX7I6mAY&dib_tag=se&keywords=Busmann%2Blow-current%2Bceramic%2Bfuses&qid=1725285390&s=industrial&sprefix=busmann%2Blow-current%2Bceramic%2Bfuses%2Cindustrial%2C84&sr=1-1&th=1 (https://www.amazon.com/ZUPAYIPA-F0-5AL-Fast-Blow-0-5amp-Ceramic/dp/B07KZRR3GL/ref=sr_1_1?crid=SVXYPSC429GV&dib=eyJ2IjoiMSJ9.6vzKtaZjL9er9MqtA5o3gyBfOyZWQ22wWwdENLgskL1Hc6u5LKPXXUuEOk6xCvi8yTe44QZUXv-69vCTIcWFHFy6l_oVDFzmUHaQj9l89Kh_WXwFdTjRRgwl1LgeT-q2bNj38QeeZp6kdhplAR7JuRiuqZiomZboXPLww_4WQjO2n2tF4DxmO-4vGTdi4D36z-dKvMgeEvmUobCV66Rw2d3TKYIM4WAGgEN1dmiIbzi68-w798Jn0PVBmmm5_ur_3lyr1NcInvCrWjfC-UvwYcHfXofguqXTQvZb8UjIoZ4.CnWMkbGIyzco43HT6R9PxAj8rVGLU_lSpNcFX7I6mAY&dib_tag=se&keywords=Busmann%2Blow-current%2Bceramic%2Bfuses&qid=1725285390&s=industrial&sprefix=busmann%2Blow-current%2Bceramic%2Bfuses%2Cindustrial%2C84&sr=1-1&th=1)
Or
https://www.amazon.com/Ceramic-HV510-600VAC-5x20mm-Multimeters/dp/B0BMWZMLF4/ref=sr_1_4?crid=3SE1WK2J9K2SB&dib=eyJ2IjoiMSJ9.8TcWDUFwbS8ofL-IB-a4igh2FHRnIzEZHG0ohdPuukEWaYUTB_uYaUAWkaYxiBo35UQcM13RSdUjRqvAmZTQdedRsaAKz_bq6l6dykaenaolWyr7xuF_VjrStKXxTYMCG_UjeRDt2lUJLkic3C6obx_hC6tIvSshZA30gkqYssjpa7tcQBYtfyLLX33TEWu7pzJNFNAosklzV_ErVQTv0ifzDnvgBsV1jdgbijj3sav4N2X3ZULlGN8B62VnpNZDkRx0bIRn6A3Cowtsohl9G7opGnprtMF3_Nn4MNrx9so.AuqZ3yOdMPQ7heMT4mxCuNjJBjVeI46mcaSH2DsqhsQ&dib_tag=se&keywords=500mA+20mm+ceramic&qid=1725286194&s=industrial&sprefix=500ma+20mm+ceramic%2Cindustrial%2C83&sr=1-4 (https://www.amazon.com/Ceramic-HV510-600VAC-5x20mm-Multimeters/dp/B0BMWZMLF4/ref=sr_1_4?crid=3SE1WK2J9K2SB&dib=eyJ2IjoiMSJ9.8TcWDUFwbS8ofL-IB-a4igh2FHRnIzEZHG0ohdPuukEWaYUTB_uYaUAWkaYxiBo35UQcM13RSdUjRqvAmZTQdedRsaAKz_bq6l6dykaenaolWyr7xuF_VjrStKXxTYMCG_UjeRDt2lUJLkic3C6obx_hC6tIvSshZA30gkqYssjpa7tcQBYtfyLLX33TEWu7pzJNFNAosklzV_ErVQTv0ifzDnvgBsV1jdgbijj3sav4N2X3ZULlGN8B62VnpNZDkRx0bIRn6A3Cowtsohl9G7opGnprtMF3_Nn4MNrx9so.AuqZ3yOdMPQ7heMT4mxCuNjJBjVeI46mcaSH2DsqhsQ&dib_tag=se&keywords=500mA+20mm+ceramic&qid=1725286194&s=industrial&sprefix=500ma+20mm+ceramic%2Cindustrial%2C83&sr=1-4)
-
Are you sure you read the current rating of the fuse correctly? It's easy to confuse with the 250V.
In my case PCB 2.2, I have a 20mm ceramic fuse rated for 600mA, 250V. And the print next to the plug says 250mA.
-
When manufacturers do this kind of stuff with fusing, they usually either use IF=Imax but with slow blow, or IF≈2Imax but with fast blow.
-
What fuse rating do you all have on the mA plug?
Mine came with a 600mA fuse. Is that correct? Isn't it too high?
This is wrong. There must be a 250mA fast-blow fuse - this is the upper current limit for this range, which is indicated in the technical specifications. It is unacceptable to install fuses with a higher trip current, you risk damaging the device!!! Chinese friends install the cheapest fuses and are not very concerned about this. ;)
-
What fuse rating do you all have on the mA plug?
Mine came with a 600mA fuse. Is that correct? Isn't it too high?
This is wrong. There must be a 250mA fast-blow fuse - this is the upper current limit for this range, which is indicated in the technical specifications. It is unacceptable to install fuses with a higher trip current, you risk damaging the device!!! Chinese friends install the cheapest fuses and are not very concerned about this. ;)
How do you know a current >250mA will blow the device? Where did you get the specifications from?
-
How do you know a current >250mA will blow the device? Where did you get the specifications from?
I say this because I have many years of experience using various multimeters. Do you have such experience?
The technical characteristics of the ZT-703S are indicated in its manual on the last pages.
-
How do you know a current >250mA will blow the device? Where did you get the specifications from?
I say this because I have many years of experience using various multimeters. Do you have such experience?
The technical characteristics of the ZT-703S are indicated in its manual on the last pages.
Well, I have been owning and using multimeters, since the 1980s...so that should give me some experience, but you may be right, that doesn't mean I'm technically competent... lol...
Anyway I just checked a Fluke in my endless collection of multimeters and it has a 440mA fuse....So, not all multimeters are limited to 250mA in their low current plugs. I'm also not aware of any standard that specifies such a limitation.
However, I totally agree that anything above 250mA should probably be measured using the 10A plug.
p.s.: those specifications are for measuring ranges, but don't specify the fuse rating nor the current limit of the circuitry.
-
p.s.: those specifications are for measuring ranges, but don't specify the fuse rating nor the current limit of the circuitry.
This is not indicated, but is implied by the number counts of readings on the multimeter(25000) and the OL readings if the current allowed for a given limit has exceeded its value.
-
Dave has covered this already. (Of course! :))
https://www.youtube.com/watch?v=WG11rVcMOnY (https://www.youtube.com/watch?v=WG11rVcMOnY)
Looks like if your meter has a 600mA then better get a proper rated fuse of 250mA.
-
Dave has covered this already. (Of course! :))
https://www.youtube.com/watch?v=WG11rVcMOnY (https://www.youtube.com/watch?v=WG11rVcMOnY)
Looks like if your meter has a 600mA then better get a proper rated fuse of 250mA.
Lovely, what a can of worms! I specially like the part at 29:30 where the document he's reading says "it's impossible for a fuse to fulfill both standards ratings"
Thanks for sharing.
-
This is wrong. There must be a 250mA fast-blow fuse - this is the upper current limit for this range, which is indicated in the technical specifications. It is unacceptable to install fuses with a higher trip current, you risk damaging the device!!!
So, you are saying that if you exeed the 250mA range by 1mA it should blow the fuse?
That doesn't sound normal to me. There must be some margin.
-
So, you are saying that if you exeed the 250mA range by 1mA it should blow the fuse?
That doesn't sound normal to me. There must be some margin.
No, you're wrong! 250mA is the rated current of the fuse. A 250mA fast fuse will blow at 1.5-2 times the rated current. At what current the Chinese 600mA fuse will blow we do not know? ;)
-
No, unless I'm mistaken, the demonstration (very non-intuitive to me but educational) is that the current rating of the fuse is generally the sustained current the fuse will tolerate flowing through it WITHOUT blowing. Further the demonstration shows that some fuses can tolerate 2x the current rating. And that there is quite a distribution in performance of one make of fuse, on top of, amongst / between manufacturers with the same ratings.
Yikes! I'm both better educated now, AND less sure of what to put in the meter.
I wonder if he repeated his experiment, but with an inductive load what would happen. >:D
I think I should probably re-think the use of a 2x fuse... :-DMM
What we don't know is the current carrying capability of the traces and electronics (ADC ?) performing the sampling on the input path.
-
How do you know a current >250mA will blow the device? Where did you get the specifications from?
I say this because I have many years of experience using various multimeters. Do you have such experience?
The technical characteristics of the ZT-703S are indicated in its manual on the last pages.
Nothing there about the figures in the range column being warnings such as "do not exceed or damage will be caused".
(60 years and counting of using multimeters.)
-
What we don't know is the current carrying capability of the traces and electronics (ADC ?) performing the sampling on the input path.
Let joesmith check it out if he's interested. I, for example, don't want to risk an appliance that I like for some reason! :)
Nothing there about the figures in the range column being warnings such as "do not exceed or damage will be caused".
(60 years and counting of using multimeters.)
Does the word MAX on the front of the device in front of the mA socket mean anything to you? 250V MAX 250mA MAX!!!
In your devices you can put any fuses and for any current, nobody forbids it.;)
-
What we don't know is the current carrying capability of the traces and electronics (ADC ?) performing the sampling on the input path.
Let joesmith check it out if he's interested. I, for example, don't want to risk an appliance that I like for some reason! :)
Nothing there about the figures in the range column being warnings such as "do not exceed or damage will be caused".
(60 years and counting of using multimeters.)
Does the word MAX on the front of the device in front of the mA socket mean anything to you? 250V MAX 250mA MAX!!!
In your devices you can put any fuses and for any current, nobody forbids it.;)
Do you seriously believe that the design and manufacturing tolerances on this meter (or any other DMM) are so tight that the maker can confidently say it will be damaged or some other bad thing will happen if subjected to even 5% beyond the MAX on the front panel?
-
Do you seriously believe that the design and manufacturing tolerances on this meter (or any other DMM) are so tight that the maker can confidently say it will be damaged or some other bad thing will happen if subjected to even 5% beyond the MAX on the front panel?
No, I'm not suggesting that. But usually Chinese multimeters are built on a single chip without any serious protection.
Have you never seen such cheap toys explode inside? The fuse remains intact, but all the measuring circuits are burned out! I've seen it several times. ;)
-
My interpretation of the 250mA MAX is simply this: If you want to measure more than 250mA, do not use this socket. Quite probably the meter will come to no harm at 500mA or even more. What is to be marked on the front panel? If it is OK at 500mA should the marking say 500mA MAX? But then customers will try to measure up to 500mA and complain that the reading is invalid.
250mA is the maximum that can be measured using that input. Not the maximum that can be tolerated. And no I'm not suggesting that the MAX be completely ignored.
-
My interpretation of the 250mA MAX is simply this: If you want to measure more than 250mA, do not use this socket.What is to be marked on the front panel? If it is OK at 500mA should the marking say 500mA MAX?
This is true if the user knows exactly what current he is going to measure. So a good tip is to always use socket "A" unless you know exactly the magnitude of the current to be measured. And if the user does decide to use the "mA" socket first and the current exceeds the 500mA value for a while. Are you sure that the measuring circuits of this device will withstand such a current if a cheap 600mA fuse is installed?
I, for example, am not at all sure and do not want to check it on my copy. I do not recommend doing such a check to other users.
-
I'm trying to save a screeshot, but the "Save failed" message pops up.
Any idea what's causing this?
I dont have any other screenshots saved at the moment, so there should be enough space for that.
It has been working before, but i'm not sure if it has been working with the latest software (v1.39). It might be that i tested it with older software.
-
The fuse ratings are like highway speed signs.
I take it as a suggestion and not literally. ???
-
I'm trying to save a screeshot, but the "Save failed" message pops up.
Any idea what's causing this?
I dont have any other screenshots saved at the moment, so there should be enough space for that.
It has been working before, but i'm not sure if it has been working with the latest software (v1.39). It might be that i tested it with older software.
I have version 1.3.8 installed on my device now and screenshots are saved normally. Check if you can access the memory partition of the device if you connect it as USB Media? Also try formatting that partition again.
-
Also try formatting that partition again.
Ah yes. I did the format on the scope and it's working again. Thanks!
-
Hey. I see you got a response. Yeah I'm on 1.3.9 and can do a save and view.
What's funny though, I tried to press Exit and that did not work.
Tried to go to the Menu and that did not work.
To get back to Scope Mode (from viewing the image of a prior save), I had to press the Mode key.
It seems the firmware is in a state of flux, and while some things are being worked on / improved, other things seem to be getting broken.
I wonder about their "regression testing", either in house, or by external individuals that can influence what is happening with the development of the firmware.
I'll write this again, it sure would be good for someone with the programming chops to enter into an NDA with the manufacturer and do some serious regression testing, and possibly some re-programming of the firmware.
-
What's funny though, I tried to press Exit and that did not work.
Tried to go to the Menu and that did not work.
To get back to Scope Mode (from viewing the image of a prior save), I had to press the Mode key.
Yes, on version 1.3.8 exactly the same condition. I wonder by Exit works on version 1.3.2? I'm too lazy to check it out. :)
-
Just tried it on 1.32 and it seems to have the same behavior, need to press Mode to exit.
-
The fuse ratings are like highway speed signs.
I take it as a suggestion and not literally. ???
I try to avoid the hole fuse issue altogether using clamp meters to measure current.
To stay true to your analogy, I just take an airplane instead of the road...no speed signs up in the sky...
-
I wonder about their "regression testing",
You are the testor. ;)
-
except, there is no formal means by which the issues I or someone else identifies makes it back to the people doing the programming and test. |O but I know what you mean.
it's a shame. I think there are a number of products built around the same hardware. i wonder if they too have similar problems. I suspect they do not.
this product could be great... :palm: i hope they keep issuing updates. but they really need a team dedicated to the product, and they should make it possible to submit bug reports for their products. :rant:
-
this product could be great... :palm: i hope they keep issuing updates. but they really need a team dedicated to the product, and they should make it possible to submit bug reports for their products. :rant:
It may just be limitations of the hardware and the coding just cannot compensate for, so they try and fix via code, but fixing one things breaks something else.
At some point we just classify this item as a no-buy and look for something else, or, just use it for the measurements it can do ok with.
-
Randy, that is one way to look at it. I find many of the problems are User-Interface related, and that is typical of complex systems, but can be dealt with. It seems the device misses the mark having 50Mhz bandwidth, and there are some issues with trace artifacts (like waveform discontinuities), and annoyances like a partially but inconsistent bargraph display, button labeled exit doesn't exit from the saved image display, long presses on Auto button will do nothing while a short-press does, Auto in 1.3.9 is cough, cough not working quite right... (this list by no means exhaustive)... But these issues (with the possible exception of the bandwidth spec not being met - not sure about that being impossible... might optimizations in coding help - not sure) are mostly all UI related and very fixable.
-
Apollo11fan, I appreciate your perspective and agree with the points being made.
That said, I try to consider the context from the manufacturer's side as well. Being relatively new in the oscilloscope market and offering highly competitive prices means they likely face hardware limitations and resource constraints. They may also outsource some work, which can complicate development and testing, especially when aiming for ambitious goals like the possible release (just guessing) of a 100Mhz scope at a similar price point .
For me, as someone who remembers when oscilloscopes were much more expensive and only found in labs, getting a two-channel 40+MHz battery-powered scope with a decent display and a multi-meter for $65 is impressive (probe(s) included). It may have quirks, but it functions as intended. For more serious work, however, this or any other affordable handheld meter might not be suitable. Spending a bit more on brands like Hantek or Owon might offer better options, though they have their own issues too.
Could you provide some examples of the trace artifacts you've encountered, like the waveform discontinuities? That would help in understanding the extent of the issues.
-
it's a shame.
this product could be great... :palm: i hope they keep issuing updates. but they really need a team dedicated to the product, and they should make it possible to submit bug reports for their products.
I completely agree with you. I used to consider the ZOYI company more reputable than the toy FNIRSI since many models of multimeters from this company passed through my hands. This, of course, is not Fluke, but the devices for their price category worked and now work successfully according to the stated characteristics. The ZT-703S leaves me with a very ambivalent impression. On the one hand, as far as the multimeter is concerned, I have almost no complaints about its operation; the characteristics are quite decent, and it is convenient to use. On the other hand, as far as the oscilloscope is concerned, the number of ridiculous and childish errors that can be detected in just a couple of minutes of working with the device is simply amazing. Does it seem like the multimeter and oscilloscope were created by two different teams of engineers?
I believe that a device with so many ridiculous errors in the software simply should not enter the market! Is it really so difficult for an engineer, after releasing the firmware, to check the operation of the main modes, functions and buttons that the user uses often and which must be performed without failure? This is truly a shame for this team! :palm:
-
I sense they likely ported the code from their line of multi-meters then added the o-scope feature, and that is why I think the multimeter part (with the exception of the bar-graph (there is no need for it) and the lack of a beep for diode testing) works fairly well.
If they outsourced the o-scope development, i might better understand the buggy nature of the UI. I wonder if the ANENG version of the o-scope AOS02 and 03 function similarly and have similar bugs. :popcorn:
-
Randy, that is one way to look at it. I find many of the problems are User-Interface related, and that is typical of complex systems, but can be dealt with. It seems the device misses the mark having 50Mhz bandwidth, and there are some issues with trace artifacts (like waveform discontinuities), and annoyances like a partially but inconsistent bargraph display, button labeled exit doesn't exit from the saved image display, long presses on Auto button will do nothing while a short-press does, Auto in 1.3.9 is cough, cough not working quite right... (this list by no means exhaustive)... But these issues (with the possible exception of the bandwidth spec not being met - not sure about that being impossible... might optimizations in coding help - not sure) are mostly all UI related and very fixable.
Could you provide some examples of the trace artifacts you've encountered, like the waveform discontinuities? That would help in understanding the extent of the issues.
-
I wonder if the ANENG version of the o-scope AOS02 and 03 function similarly and have similar bugs. :popcorn:
Yes. They have same software. Only difference is the badge on the front panel.
-
Could you provide some examples of the trace artifacts you've encountered, like the waveform discontinuities? That would help in understanding the extent of the issues.
Right, so I went back and used my 60Mhz DDS Signal Generator to supply a number of different waveforms at different frequencies, and did not see the discontinuities I had seen with pre-1.3.9 revisions of the firmware. They took the shape of part of the waveform having a flipped phase that didn't update. I don't see that now. That's good.
However, I do see that the measurement / estimation of frequency is non-existant for some frequencies based on the time scale chosen. Also, in general, unless the signal is of really low frequency, I seem to get better results using the high-sampling rate and leaving that setting alone. And finally, in V1.3.9, as others have mentioned Auto *one must press the button quickly or nothing happens* seems to fail.
Assuming the signal being checked is periodic, I wonder why the firmware can't remove the time-varying estimate of the mean of the signal to remove any DC offset, then simply look at zero crossings per unit time to estimate frequency and duty cycle or am I simplifying the approach too much? I'm personally not expecting these signal estimates to update really fast. Can't remember how quickly my Hantek DSO5202P updates, but it's pretty spot on with these measurements.
-
I didn't realize the issue with the discontinuous waveforms was documented by someone else in this YouTube video:
https://youtu.be/0r5H0t7_PqA
-
I don't know if i'm doing something wrong, but for some reason i get discontinuous waveform every time i freeze the waveform with trigger and then scrolling the display to left or right.
For example, few days ago i was looking at the output voltage rise when starting up a powersupply. And when i tried to scroll the display, on all the parts that were out of display originally the line dropped down to 0V.
Edit: i guess that was just a user error. :D
It think it just runs out of memory when scrolling.
-
Edit: i guess that was just a user error. :D
It think it just runs out of memory when scrolling.
To be honest, I'm trying to figure out what you are doing and wonder if there's some feature I missed.
Can you explain your sequence of key-presses, please and volt/div and time/div settings, plus more info on the use of the trigger?
I'd like to try to replicate the behavior. :horse:
Thanks.
-
Can you explain your sequence of key-presses, please and volt/div and time/div settings, plus more info on the use of the trigger?
Set the trigger to a single-shot at rising edge.
Turn on the voltage.
And try to scroll the captured waveform left or right.
https://youtu.be/v9MMkpMc7Gc?
-
Can you explain your sequence of key-presses, please and volt/div and time/div settings, plus more info on the use of the trigger?
Set the trigger to a single-shot at rising edge.
Turn on the voltage.
And try to scroll the captured waveform left or right.
https://youtu.be/v9MMkpMc7Gc?
Try to keep the arrow pressed, you can see that you can spin the entire memory several times :-DD
-
Try to keep the arrow pressed, you can see that you can spin the entire memory several times :-DD
Yes, i figured that out eventually. As i said, this was an user error. I'm still learning. ^-^
But, one thing that is still confusing to me is that the small preview window at the top left corner won't jump to beginning when the actual waveform starts over.
-
OK, this is extremely helpful. I hadn't tried a single scan w/trigger. I like it. Thank you.
So, one thing that would be helpful is a display top/left? of the actual time post-trigger that is being displayed as the trace is scrolled back and forth.
When it is scrolled back and forth, it would be great if:
There was a cursor marking the delta time since the trigger or perhaps the beginning of capture (configurable), and
Wrapping around the trace as it is scrolled? I think there should be a feature setting to turn that on/off.
-
Normally, the manufacturer should set a limit, Owon does not allow you to scroll any further, if you set the time base higher, you only see the signal in the memory, and next to it an empty field on two sides.
This is not a user error, but a Zoyi bug.
-
FWIW - if there is someone looking to get some basic background information on Oscilloscopes, this Tektronix guide is free for downloading
https://download.tek.com/document/03W_8605_7_HR_Letter.pdf
-
The currently selected cursor line disappears when time division is >= 200ms. It makes the cursor useless since I can't see where I'm trying to position it. The bug exists back to at least firmware 1.3.2.
-
I wanted to use the Rigol PVP3150 150MHz probe with this scope because it has 20MHz bandwidth in 1X mode and i thought it would be good for low voltages.
And while it seems to have much less noise, for some reason in 10X mode it shows annoying overshoot at the edges and the compensation adjustment wont help much.
The compensation kind of works, but the spike at the beginning remains no matter whitch position i turn the compensation screw.
Any ideas what could cause this?
I would have thought that a probe, that costs almost as much as this oscilloscope, would perform flawlessly. But atleast in this case the cheap probe that came with the scope works better.
Or, does it have something to do with the fact that the more expensive Rigol probe probably has lower capacitance and the cheap probe is somehow matched with the scopes input capacitance?
On the screenshot the CH1 is the probe that came with the ZT-703s and CH2 is the Rigol PVP3150.
-
FWIW I just tested with the only other probes I have that came with my Owon VDS1022i USB scope and they work just like the Zotek one. The Owon has a similar bandwidth spec, so I assume the probes are similarly specd.
-
Or, does it have something to do with the fact that the more expensive Rigol probe probably has lower capacitance and the cheap probe is somehow matched with the scopes input capacitance?
On the screenshot the CH1 is the probe that came with the ZT-703s and CH2 is the Rigol PVP3150.
Yes, there are some that cannot be compensated with it, I did this with the Fnirsi scope, I could not compensate with the factory one, and I had to sacrifice one of the Owons.
I tried a few that were at hand, and the Owon 350MHz undercompensates, the Rigol PVP2350 is good for me and other noname too.
He also writes the compensation value on his data sheet. for PVP2350 is from 6pF to 24pF.
-
ZT-703S Firmware v1.42
Added FFT function.
http://download.s21i.faiusr.com/8164272/0/0/ABUIABAAGAAgw8y4twYo5syA0wE?f=ZOYI-703S-9-19%E6%9C%80%E6%96%B0%E5%9B%BA%E4%BB%B6FW-V142.ZTK&v=1726883395 (http://download.s21i.faiusr.com/8164272/0/0/ABUIABAAGAAgw8y4twYo5syA0wE?f=ZOYI-703S-9-19%E6%9C%80%E6%96%B0%E5%9B%BA%E4%BB%B6FW-V142.ZTK&v=1726883395)
-
Link is dead.
-
copy and pasted link in new window worked for me! Initial thoughts are it seems to be improved, triggering, stability, etc..
-
:-+Thanks, that did the trick...
-
The generator function is stuck for me.
Same with the previous firmware.
OutPut is set to square wave, the three parameters for each ---
When I go to MoreAPPs->GEN, it is active.
I can't turn it off, if I change one of the parameters, it always goes back to sine after i exiting and entering again.
Version V1.0.1.
Has anyone had a similar problem, did you manage to fix it?
-
The generator function is stuck for me.
Same with the previous firmware.
OutPut is set to square wave, the three parameters for each ---
When I go to MoreAPPs->GEN, it is active.
I can't turn it off, if I change one of the parameters, it always goes back to sine after i exiting and entering again.
Version V1.0.1.
Has anyone had a similar problem, did you manage to fix it?
Not sure I understand....here's how it works for me:
When I press Menu I have two ways of generating a signal: 1) Output Setting 2) More Apps Enter/GEN. I think they are completely separate. Option 1) let's you use the scope simultaneously, option 2 doesn't.
When I use More apps/GEN, with the up down cursor I choose the waveform, pressing Menu switches the output ON/OFF, and F1 through F4 and left right cursor change the parameters. To exit the GEN mode I need to press the MODE button and the signal generation stops.
I'm on FW 1.32 GEN V 1.0.1
Not sure if this answers your question!?
-
Yes, thank you.
I didn't even dare to think that the signal generator part only works separately, I've watched videos and reviews of many cheap scopes, but so far this is the first one where you can't check the signal of the signal generator with its own scope. ???
Apart from the OutPut setting on the scope part, which in turn limits the properties of the scope.
I don't remember that this thing was mentioned in the comments, that is, that the scope and the GEN app do not work at the same time.
Then I'm happy, it's not that my device is defective. :phew:
-
Hi, I've recently put my hand on an XEAST XE703S, which is just another rebranded version of the ZOYI dual channel scopemeter.
Specs, description and EN manual: https://www.xeastek.com/xeast-thermal-imager-for-hunting-xe-c18-c19-day-night-aiming-lens-outdoor-adjustable-focus-clarity-lens-infrared-thermal-camera-1709356654564356.html (https://www.xeastek.com/xeast-thermal-imager-for-hunting-xe-c18-c19-day-night-aiming-lens-outdoor-adjustable-focus-clarity-lens-infrared-thermal-camera-1709356654564356.html)
It came with the v1.3.8 firmware (APP) and v1.0.16 BOOT.
It was a real bargain for ~50 USD (with 2 probes, incl shipping) as a special offer on TEMU, thanks to Electronics Repair School YT channel https://www.youtube.com/watch?v=dv_fwTILAjI&ab_channel=ElectronicsRepairSchool (https://www.youtube.com/watch?v=dv_fwTILAjI&ab_channel=ElectronicsRepairSchool).
V1.4.2 FW is also available from here: http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html) (stay on the China version and use translator). But I couldn't find release notes.
-
Thanks. The update went smoothly.
Only when problem when no signal on channel 1, pressing auto set the trigger to channel 2 even when that channel is off.
copy and pasted link in new window worked for me! Initial thoughts are it seems to be improved, triggering, stability, etc..
-
Thanks. The update went smoothly.
Only when problem when no signal on channel 1, pressing auto set the trigger to channel 2 even when that channel is off.
copy and pasted link in new window worked for me! Initial thoughts are it seems to be improved, triggering, stability, etc..
Have you set "Trig Source" from the menu ?
-
yes.
Have you set "Trig Source" from the menu ?
-
yes.
Have you set "Trig Source" from the menu ?
Ok. It's Working fine for me. Maybe a factory reset would help?
-
It's the same for me.
With active CH1 and inactive CH2, the source of the trigger is CH1.
There is no signal on either input and I press AUTO, then the trigger source switches to CH2.
If I press the MENU button and use the arrow to navigate to where I can set the trigger source, it switches back to CH1 automatically.
a little interesting, but not a big deal.
If I noticed correctly, AUTO now places it in the middle like the two channels, and you can finally see the signal in normal size, you don't need to adjust it. :clap:
-
It's the same for me.
With active CH1 and inactive CH2, the source of the trigger is CH1.
There is no signal on either input and I press AUTO, then the trigger source switches to CH2.
If I press the MENU button and use the arrow to navigate to where I can set the trigger source, it switches back to CH1 automatically.
a little interesting, but not a big deal.
If I noticed correctly, AUTO now places it in the middle like the two channels, and you can finally see the signal in normal size, you don't need to adjust it. :clap:
Are you saying Auto Range works well now?
-
No auto doesn't work well. See the image. And it is slow. You can see on the screen that it is running over the V/div settings very slowly.
-
No auto doesn't work well. See the image. And it is slow.
Slow and clumsy - these are the definitions of oscilloscope operation, which are the most suitable for ZT-703S.
The space of the large display is not utilized at all efficiently. The windows with measurement results only interfere with the normal perception of the signal. In general, after a long enough use of this device as an oscilloscope my opinion - slow, inconvenient, unpleasant. Unlike a multimeter, which is really convenient to use.
-
No auto doesn't work well. See the image. And it is slow. You can see on the screen that it is running over the V/div settings very slowly.
Is this with FW 1.42?
-
No auto doesn't work well. See the image. And it is slow.
Slow and clumsy - these are the definitions of oscilloscope operation, which are the most suitable for ZT-703S.
The space of the large display is not utilized at all efficiently. The windows with measurement results only interfere with the normal perception of the signal. In general, after a long enough use of this device as an oscilloscope my opinion - slow, inconvenient, unpleasant. Unlike a multimeter, which is really convenient to use.
What are you comparing it to, to have such a negative opinion?
-
What are you comparing it to, to have such a negative opinion?
I have at home and at work many different models of oscilloscopes of varying levels from amateur to professional. But pocket and toy oscilloscopes, which now flood the market, I did not have and hopefully will not. Perhaps I am too demanding in terms of comfort and convenience of work with such devices, but I have not been able to adapt to work normally on ZT-703S yet. ;)
-
In the latest firmware, there are no AUTO button errors, it pleases. And the FFT function is heavily clipped. Without frequency and level markers, it is useless.
-
No auto doesn't work well. See the image. And it is slow. You can see on the screen that it is running over the V/div settings very slowly.
True, I misled myself. :palm:
If there is no signal on the channels, it is placed in the middle.
If there is, then to the old wrong place.
But its speed is better, about 4 seconds. for 1kHz
-
Yes the images are from 1.4.2
No auto doesn't work well. See the image. And it is slow. You can see on the screen that it is running over the V/div settings very slowly.
Is this with FW 1.42?
-
No auto doesn't work well. See the image. And it is slow. You can see on the screen that it is running over the V/div settings very slowly.
I noticed in your pics the sig generator is outputting a 10Hz signal, yet you are capturing a 1 kHz one. Were you using an external source or is it yet another bug?
-
With FW 1.4.2:
>=200ms time division has changed some how. The waveform scrolls continuously from right to left. It used draw the waveform from left to right in a ring buffer manner. I don't know enough about scopes to know what this is about.
Auto range with CH1 enabled and CH 2 disabled leaves the trigger on CH 2. Have to switch CH 2 on and off to get the trigger back to CH 1.
-
For me, when AUTO mode is turned on, the trigger switches to channel 2, but after that it returns to 1. AUTO mode works at a signal level of 400mV.
-
Firmware v1.42
where are versions 1.40/1.41? :D
-
I used an external sig gen, so no error there.
No auto doesn't work well. See the image. And it is slow. You can see on the screen that it is running over the V/div settings very slowly.
I noticed in your pics the sig generator is outputting a 10Hz signal, yet you are capturing a 1 kHz one. Were you using an external source or is it yet another bug?
-
Autoset will change the trigger to the CH2 only if there is no input signal.
With the test signal it stays on CH1.
Autoset now works.
Yes the waveform is on the top of the screen and not centered, but long press on the Move button will bring it down.
But atleast it detects the signal.
With v1.38 and v1.39 it was completely useless.
I don't understand people complaining about clumsiness.
It's a 70€ device not a 700€ or 7000€. What did you expect?
-
I don't understand people complaining about clumsiness.
This is professional fatigue, snobbery. ;D
-
It's not unreasonable to expect the advertised features to work without bugs. This has been like beta testing a prototype. The price is irrelevant.
Anyways. I stumbled upon something I did not see documented anywhere. On the third menu in oscilloscope mode. Press the Auto button for 3 seconds. It brings up some kind of setting that allows you to set the y-axis position for each channel. I can't tell what it effect it's supposed to have. Perhaps simply another way to move the the y-axis.
-
I don't understand people complaining about clumsiness.
It's a 70€ device not a 700€ or 7000€. What did you expect?
I don’t understand people who buy crap and then try to make candy out of it?
I have a USB Owon VDS1022i, it cost me $65, even less than the ZT-703S, but working with it is much more comfortable and enjoyable than with this toy.
-
I don't understand people complaining about clumsiness.
It's a 70€ device not a 700€ or 7000€. What did you expect?
I don’t understand people who buy crap and then try to make candy out of it?
I have a USB Owon VDS1022i, it cost me $65, even less than the ZT-703S, but working with it is much more comfortable and enjoyable than with this toy.
Don't compare Owon with these.
Owon has been making scopes for a long time, and they rarely make such basic mistakes.
Is this Zoyi's second?!?!
-
I don't understand people complaining about clumsiness.
It's a 70€ device not a 700€ or 7000€. What did you expect?
I agree with you that one should compare these devices within their price range.
As much as I appreciate Zotek for inexpensive DMMs and the LCR Tweezer, I believe (from what I've seen) that Zeeweii and even Fnirsi with the DPOX provide more sophisticated low-cost handheld oscilloscopes.
-
Upgraded from 1.39 to 1.42 using the link posted above.
I agree, the FFT function would be much better if it supported cursor movement, and showed Amplitude and Frequency in a rectangular box as the cursors are moved, with the ability to toggle LOG mode for Y-Axis.
It's not bad... it's quite promising actually, but without at least the frequency displayed (when moving the horizontal cursor), it's not currently what I hope it could become.
See the image attached here. It appears that in 1.42, the discontinuous trace problem is back (circled in blue). |O
Back to the FFT, there's a good bit of code that goes into the fast fourier approximation to the z-transform and this depiction of the approximation to the magnitude of the power spectrum.
You'd really want that code space dedicated to existing oscope functionality first, then FFT being icing on the cake.
I am not complaining since these releases seem to be getting better and better, the device more valuable. I do not view this as a toy, but rather a tool, and ZOTI seems to be making it better and better with subsequent releases. YMMV.
-
Don't compare Owon with these.
Why not compare? These are products in the same price category under $100. ;)
Owon has been making scopes for a long time, and they rarely make such basic mistakes.
I agree with you on this, but I was hoping that ZOYI would do the oscilloscope part a little better, having enough experience in the development of multimeters. Unlike FNIRSI, which you also know well for its "quality". I see your signature in red - "Fnirsi oscilloscope = waste®ret." :)
-
I don't understand people complaining about clumsiness.
It's a 70€ device not a 700€ or 7000€. What did you expect?
I don’t understand people who buy crap and then try to make candy out of it?
I have a USB Owon VDS1022i, it cost me $65, even less than the ZT-703S, but working with it is much more comfortable and enjoyable than with this toy.
I'm not sure why you consider it a toy vs other scopes?! I think you are going too far with your criticism. It's certainly not a toy.
It's a multimeter, a function generator and a 2CH 40MHz oscilloscope, all in one. It has its faults and buggy software, but it is a tool that gets the job done within its limitations. On top of that it has decent build quality, big buttons and a nice display, it's ergonomics are better than many more expensive ones. As to the software, I personally like the menu navigation, given the limited number of buttons and the replacebale battery plus runtime are nice too...
It's a tool hobbyists and students could only dream of not too long ago.
As to the comparison with the Owon VDS1022i, which I own since 2019, if you are late to the game, you may have missed the total disaster that the software shipped on the CD was!!!... Thanks to some community developers now we have decent software, but not thanks to Owon... at least Zotek seems to keep trying...
-
I'm not sure why you consider it a toy vs other scopes?! I think you are going too far with your criticism. It's certainly not a toy.
I am well acquainted with how a good and inexpensive oscilloscope should work and have the opportunity to compare with other products and I honestly call such things toys, if they do not perform their functions, have a lot of childish errors in the software and they are uncomfortable to work with. That's my opinion and you don't have to agree with it.
As to the comparison with the Owon VDS1022i, which I own since 2019, if you are late to the game, you may have missed the total disaster that the software shipped on the CD was!!!... Thanks to some community developers now we have decent software, but not thanks to Owon...
No failure of software for OWON has ever happened! There have never been such elementary errors in functionality as the ZT-703S. With alternative software from florentbr it is certainly more comfortable to use VDS1022i, but also the latest official versions from OWON are quite workable.
-
I have a USB Owon VDS1022i, it cost me $65, even less than the ZT-703S, but working with it is much more comfortable and enjoyable than with this toy.
I think you are comparing apples and oranges. Ofcourse a USB scope is more comfartable to use. But it also requires more space because you need a computer with that. I haven't seen any handheld scope that isn't clumsy to use.
I'm not saying it's perfect. And i definetly dont think this is a professional tool.
But for the hobbyist it's a nice to have.
You have a working multimeter and oscilloscope in same package that is easy to carry with you.
But i agree that advertised functions should work.
-
No failure of software for OWON has ever happened!
Just to refresh your memory, here's the forum thread you were quite active on dealing with the numerous software bugs on the Owon back in 2019. https://www.eevblog.com/forum/testgear/owon-vds1022i-quick-teardown-(versus-the-hantek-6022be)/325/ (https://www.eevblog.com/forum/testgear/owon-vds1022i-quick-teardown-(versus-the-hantek-6022be)/325/)
Here's the list of some of the bugs in those versions I was referring to....
Delay in bringing up 'Display' menu
Math function broken Ch1 - Ch2 defaults to 5V range, changing it results in flat-line
Doesn't remember timebase settings across program close
Crash when zooming horizontal when in stopped mode
-
Here's the list of some of the bugs in those versions I was referring to....
These are not fundamental small mistakes! They have been fixed a long time ago and do not cause any problems in the operation of the device.
-
Here's the list of some of the bugs in those versions I was referring to....
These are not fundamental small mistakes! They have been fixed a long time ago and do not cause any problems in the operation of the device.
I do disagree with you. In those days the interface of the Owon software was sluggish, unresponsive and not intuitively structured and had bugs. In fact it was so unsatisfactory someone made an alternative software, which I use and never looked back. Glad to know Owon after all these years got their act together and fixed it.
In my mind it's not much different than Zotek when comparing similar stages of deveolpment in time.
I won't continue this discussion, since it's drifting into off-topic territory.
-
Even with these bugs, I find it more usable.
First of all, don't expect a perfect scope from a company that used to produce DMMs.
Their products are good for the price...
If you want perfect for the first time, don't buy these half-finished Euro items, but look for something that has been on the market for a while, there are videos, teardowns and everything is perfect.
Or, as was written before me, choose from the +1000 Euro category.
Anyways. I stumbled upon something I did not see documented anywhere. On the third menu in oscilloscope mode. Press the Auto button for 3 seconds. It brings up some kind of setting that allows you to set the y-axis position for each channel. I can't tell what it effect it's supposed to have. Perhaps simply another way to move the the y-axis.
I don't understand that setting option in the third menu either, I didn't notice that it does anything.
or dont save it.
Occasionally, the auto range would center CH1, but CH2 would always be two DIVs below.
I hope Zoyi provides an explanation soon.
-
Another bug (maybe related to the "discontinuous trace problem" mentioned above) is that the displayed waveform can completely drop pulses. I would guess the ADC data is just somehow getting misordered for display. Here is an example in video:
https://www.youtube.com/watch?v=JOzSh3wBu8s (https://www.youtube.com/watch?v=JOzSh3wBu8s)
I see similar problems on other time scales in "single-trigger mode". I see this bug on both firmware versions 1.3.8 and 1.4.2.
-
@nikbry
I believe the 10Hz spec is when using "AC coupling" mode, so it doesn't apply to my measurements. "DC coupling", which I used in the video, literally goes all the way to DC (0Hz).
-
I think it's a physical limitation, low memory and slow sampling rate. It happens very often with Fnirsi, it also happened rarely with my Owon.
I played with it a bit, and it seems that retriggering in a 100ms time base is approx. 4 seconds.
The guy messed it up in the video by placing the trigger completely on the left side.
IF he left it in the middle, it would have been seen that the trigger misses the first pulse and catches the second.
The fact that at the end he tried to zoom out or move the stopped recording to the right and did not find the first pulse was also misleading.
I can't tell for sure which part of the off-screen wave is real and which is junk.
Because we cannot see which is the end and the beginning of the memory.
I also rarely experienced this trigger error with Owon.
With Fnirsi, very often...
-
Would you repeat the experiment, but with and without Normal acquistion sampling enabled? >:D
-
Yes.
There is a small bug at 50 and 100ms.
With a single trigger, the wave is not completely saved, or we only see more on the display than what is in the memory maybe?
20ms is already good.
and a bug where if you capture a signal with single trigger, I press the hold/save button to capture a signal again, it doesn't always stay in single trigger mode.
switches to AUTO, if I press MENU and navigate to where the trigger settings are, it switches to Single again.
This part may be a bit incomprehensible.
-
bobuhito, I recently did an analysis of the fnirsi 2c23 error correction in the new 2c53t, and compared it with the work of the zoyi zt-703. I did not observe any problems with the trigger operation in the zoyi zt-703.
https://youtu.be/1E0RQBMMkVQ?si=Vl533En3Ao4EsyMk&t=111
-
bobuhito, I recently did an analysis of the fnirsi 2c23 error correction in the new 2c53t, and compared it with the work of the zoyi zt-703. I did not observe any problems with the trigger operation in the zoyi zt-703.
https://youtu.be/1E0RQBMMkVQ?si=Vl533En3Ao4EsyMk&t=111
I think I managed to understand Bobuhito's problem.
it is as if measurement points are no longer saved ~500ms after triggering with the 50 and 100ms time bases.
If you set single triggering and then switch the output of your signal generator to it, you can see that the continuous signal is only visible for 500ms after the trigger. then a straight line.
If you give it a continuous signal and then press the single trigger, you will see some kind of remnants from the memory after 500ms too.
Among my previous posts, this is exactly what you can see in the picture called 100ms.
Bobuhito could no longer see a second pulse when he set the delay between the two pulses to 500ms.
Some kind of bug.
Another annoying thing.
If I stop it with a single trigger or simply with the Hold button, then if I zoom in on the signal, the green arrow marking the trigger and the real trigger point move relative to each other, it does not follow.
-
@csuhi17
Yes, thanks for explaining it better.
I thought the video showing the missing pulse would speak for itself, but everyone's instinct naturally is to think this is somehow normal operation or user error...now, I hope Zoyi/Zotek can fix this bug soon with new firmware!
-
I was confused that the trigger was mentioned.
with fast signals, I noticed that occasionally it does not trigger on the first edge.
This error could have been clearly demonstrated with a continuous signal.
1. I set the single trigger.
2. I touch the measuring tip to the measuring point. Then you can see where the signal breaks.
-
V1.42 Software update details from zotektools.com:
- Added FFT mathematical function, replacing the original format key with an FFT switch.
- Optimized low-frequency AUTO speed and accuracy.
- Enhanced the scrolling scan mode.
- Improved the cursor display issue in scrolling mode.
-
Hello there,
I just got my ZT703s a few days ago. I really enjoy it, however a few downsides: the default probe is not so good, so I ordered better ones, but the standard BNC is too big to attach, it just "stucks" before fully clicking in (it can be used this way, but I wonder if I can "wear it in" by using pliers gently). The other problem is I can't use my computer to analyze the waveforms (properly).
So I am currently working on a Python script (with the help of ChatGPT) to scan BMP files and logic-analyze the signal.
That's when I noticed, that the BMP format is "corrupted": I can open it on Win10, but if I try to open it with anything else (online image converters, ImageMagick, OpenCV, PIL) I get the "Unsupported BMP header type (56)", "ImproperImageHeader" or on freeconvert.com: "length and filesize do not match" error.
My unit was shipped with firmware 1.3.9 and I updated to 1.4.2. Unfortunately, I don't have BMP exports from 1.3.9, so I can't test if the update caused this.
Using anything to convert it fails - except GIMP, which I just tried before posting.
The original reason to post was I couldn't convert however I tried, but after testing with GIMP, I post to let you know that this bug exists.
Also, if someone could try to convert a BMP from an older firmware with an online converter (e.g. https://www.freeconvert.com/ (https://www.freeconvert.com/)), we could narrow down the possibilities that could cause this behaviour.
Have a nice day,
Matt
(attached capture of a PS/2 keyboard 'A' key press - 0x1C)
-
I also have had problems with the BMP screenshots.
I used Photoshop to convert BMP to png or jpg, and it works.
-
https://www.eevblog.com/forum/testgear/fnirsi-1013d-100mhz-tablet-oscilloscope/msg5278324/?topicseen#msg5278324 (https://www.eevblog.com/forum/testgear/fnirsi-1013d-100mhz-tablet-oscilloscope/msg5278324/?topicseen#msg5278324)
I found easy working solution for fix BMP format :)
Just change only one byte - 56 to 40 here (i use binary hack for .bmp, change one byte at 0x0e offset )
After that Firefox, Telegram and Python successufllly recognized screenshots.
-
56 BITMAPV3INFOHEADER
Not officially documented, but this documentation was posted on Adobe's forums, by an employee of Adobe with a statement that the standard was at one point in the past included in official MS documentation[12]
https://en.wikipedia.org/wiki/BMP_file_format#DIB_header_(bitmap_information_header)
It is using a more obscure bitmap format. Searching BITMAPV3INFOHEADER shows quite a few results of problems with various image software not supporting it.
I wonder if they use the same code since this Zoyi meter and Finrisi have the same obscure bitmap format.
-
matefon: you can downgrade your firmware. In a previous post, someone uploaded many versions of the firmware.
Have you tried opening the .BMP using the program paint.net?
https://www.getpaint.net/download.html (https://www.getpaint.net/download.html)
-
Thanks for mentioning, I didn't know if I can downgrade.
I think the easiest automated solution would be what Atlan suggested (changing a byte).
Now I have problems with the analyzing code, ChatGPT can get something right, then it brokes edge detection, then it fixes edge detection but brokes visuals... I don't have experience in NumPY and OpenCV but maybe I will need to write my own code for this.
I also plan to use a Raspberry Pi Pico as a logic analyzer, and use the ZT703s to determine the signal voltage so I can use level shifters or voltage dividers on slower circuits.
P.s.: I went to a local electronic store today to get a BNC extender, so I can fit the probes, they didn't have it but we came up with a solution to get a BNC-RCA converter and an RCA-BNC converter together 8)
Maybe temporary solution, maybe not, I will see how it affects signal reception and how fragile does it make the on-device connector, as it is sticking out and I'm afraid I will broke it accidentally while using.
-
Also as an IT engineering student, I'd like to try debugging the firmware and add new features if I can. Does someone know about an open-source firmware for this? Or a way I can contribute? I suppose no, but worths to ask.
-
You can write x sin(x) interpolation for 1013D oscilloscope :D
-
the default probe is not so good, so I ordered better ones, but the standard BNC is too big to attach, it just "stucks" before fully clicking in
I think the real reason is that the plastic plate that is behind the bnc-connectors is too thick. Baybe if we remove it and sand the backside of it, to get it little thinner, maybe that could help.
I might try this next time i open my unit.
-
I think the real reason is that the plastic plate that is behind the bnc-connectors is too thick.
That is possible. Every manufactured component has a margin of error, and in my (and your) case it happens to be that the probe is sligthly larger, and the plastic is a little bit thicker.
I don't want to physically modify my unit just yet, so I'll be using my 'BNC extender' for now.
In a video somewhere I came across that the battery inside is not actually a 18650, but a larger one, so it puts stress on the battery holder string. Is it true?
-
You can see it yourself if you take it apart.
It is not difficult to disassemble, just 4 screws and carefully lift the bottom.
There is a plastic tab on both sides in the middle, which I managed to destroy, but it does not affect anything.
Mine came without a battery, I put an unprotected flat-top battery in it, I had to solder a button on it to make contact.
-
In a video somewhere I came across that the battery inside is not actually a 18650, but a larger one, so it puts stress on the battery holder string. Is it true?
As with every mechanical part, the 18650 cells also have tolerances, so the size may vary. And it also depends if the cell has a protection circuit or not.
Also, the battery holder might be little too short (i think it is designed for unprotected cells).
In my unit the original cell was little tight and i swapped it with a Panasonic 3400mAh protected cell (because i don't want any random chinese cells in my house) that was also little tight. So no difference here.
I just shortened the spring for about one turn and it's perfect now.
-
So the battery size problem varies between units. I know I could take it apart but I thought I would ask if this is a common problem.
Thanks for the answers.
-
In a video somewhere I came across that the battery inside is not actually a 18650, but a larger one, so it puts stress on the battery holder string. Is it true?
Mine has a protected 18650. You can tell because the length of unprotected 18650 is 65mm. Protected is a few mm longer. The cell holder in this device is definitely for unprotected cells.
The holder in mine is deformed because they jammed the unprotected cell in there. It's stuck real good. I'm afraid of trying to remove it. That's a problem for future me. :D
-
I think you meant "protected cell" which would be taller/longer. Mine came with a protected cell. Don't you think it's a good idea to use the same? In one Youtube video, the person cuts the spring...
-
I just disassembled mine, and oh lord, there was tension. I cut off 2.5 turns from the spring. There is still some tension, but if I cut more I can't put in another 18650 cell, as the spare cells I have are slightly smaller (probably not protected). This way I can change the battery and still have less tension in the plastic battery holder.
-
What is the capacity of the battery, who measured?
-
Didn't measure, but this is the label:
-
Measured the actual battery capacity, 2750 mA/h, resistance 79 mΩ.
-
How do you measure?
-
I just loaded Firmware 1.4.2 and now it completely ignores the Auto Off setting and just turns off after a few minutes |O
-
Have companies forgotten about regression testing? Seems ZOYI, or the contractors they have programming the device fix or enhance one thing, and break something else with regularity. Some of you should offer up your services as regression testers. I wrote this before: this product could be really great, but some entity needs to take control of their SW development, test and validation processes. :palm:
-
It definitely turns off, maybe the backlight turns off after 120 seconds? which is turned on in the menu in oscilloscope mode.
-
I know it's doing my head in, every few minutes I have to turn the damn thing back on, I mentioned it to a chap who I think works at Zoyi, on one of his Youtube vids, I dodn't know if he will take any notice of me.
-
I know it's doing my head in, every few minutes I have to turn the damn thing back on, I mentioned it to a chap who I think works at Zoyi, on one of his Youtube vids, I dodn't know if he will take any notice of me.
reset the device. set the black screen setting to 0. or off I don't remember. and automatic shutdown. turn it off. two separate settings.
-
I just loaded Firmware 1.4.2 and now it completely ignores the Auto Off setting and just turns off after a few minutes |O
I also have firmware 1.4.2 loaded and I don't see any problems with the unit auto shutting off.
There are 2 settings in the menu:
AutoOff and BLtime
Set AutoOff - OFF and BLTime - OFF and check if the unit turns off with these settings?
If I set AutoOff - 1min, then exactly after 1 minute the device signals "AutomaticShutdown" on the display and turns off.
-
Black screen setting? where's that, I will gladly try it mate
-
Black screen setting? where's that, I will gladly try it mate
BLTime ;D
suddenly I couldn't remember what it was called. I write with Google Translate from my phone at work.:palm:
-
No problem mate, but where is it? all I can see is Backlight in percentages and it just turns the brightness up and down, are we talking Multi-meter menu's or scope menu's?
-
Ok, I found it, in the scope meu's, I have set them both to off and have it beside me will wait and see, thanks guys
-
Looks like that's got it, Thanks Guys, this is why I love forums :-+
-
It would make more sense if the setting for backlight time was next to backlight brightness.
-
OK, good it's not broken. Just a usability design issue. Yeah, that is the sort of thing that can also benefit from some expertise in user interface design to make our interactions with the device more obvious and natural.
-
Trigger in version 1.4.2 does not work with time scale 250ns/div and less. So I can't observe 100-200-400ns pulses in good resolution.
It worked fine before... Amazing device...
-
Trigger in version 1.4.2 does not work with time scale 250ns/div and less. So I can't observe 100-200-400ns pulses in good resolution.
I can't confirm your conclusions. On my device with version 1.4.2, the trigger works normally over the entire duration range.
Show your video of the malfunction?
-
Trigger in version 1.4.2 does not work with time scale 250ns/div and less. So I can't observe 100-200-400ns pulses in good resolution.
It worked fine before... Amazing device...
Yes, the trigger does not work correctly in these modes. The pulse is displayed, but outside the screen. You have to search with the MOVE button.
-
Trigger in version 1.4.2 does not work with time scale 250ns/div and less. So I can't observe 100-200-400ns pulses in good resolution.
It worked fine before... Amazing device...
I checked all firmware versions, the trigger works correctly only version 1.3.8
-
Trigger in version 1.4.2 does not work with time scale 250ns/div and less. So I can't observe 100-200-400ns pulses in good resolution.
I can't confirm your conclusions. On my device with version 1.4.2, the trigger works normally over the entire duration range.
Show your video of the malfunction?
Give one pulse 1-10 uS. And you won't see him. He will be behind the screen.
-
Give one pulse 1-10 uS. And you won't see him. He will be behind the screen.
Yes, now I see the poor performance of the trigger. On version 1.3.8, the trigger operation is more reliable, so for now we will remain on this version. :)
-
Where do you get old versions?
-
Look at page 20.
-
is this one good enough for videogame consoles like snes and c64 etc
Zoyi ZT-703S
-
is this one good enough for videogame consoles like snes and c64 etc
Zoyi ZT-703S
Check out this: https://youtu.be/Po_2bXn6Ba8?t=976 (https://youtu.be/Po_2bXn6Ba8?t=976)
-
Trigger in version 1.4.2 does not work with time scale 250ns/div and less. So I can't observe 100-200-400ns pulses in good resolution.
I can't confirm your conclusions. On my device with version 1.4.2, the trigger works normally over the entire duration range.
Show your video of the malfunction?
Give one pulse 1-10 uS. And you won't see him. He will be behind the screen.
Would you mind sharing your exact experiment setup? I'm trying to reproduce the problem on FW 1.32 and can't. I must be missing something. Thanks
-
I have 703s model, how to turn off built-in generator?
it limits use of scope - "time base limitation"
I go to apps/more, set all outputs to OFF, but when back into that menu, one is always on.
And 2nd one has no way to be turned off?
-
I have 703s model, how to turn off built-in generator?
it limits use of scope - "time base limitation"
I go to apps/more, set all outputs to OFF, but when back into that menu, one is always on.
And 2nd one has no way to be turned off?
2nd one can't be switched off and must be in square wave mode to avoid the "time base limitation" on the scope.
-
The second generator is actually always on for a reason: reference signal. It is used to calibrate the scope probes.
Like nikbry mentioned, you should set it to square wave and you won't have troubles with it.
-
Trigger in version 1.4.2 does not work with time scale 250ns/div and less. So I can't observe 100-200-400ns pulses in good resolution.
I can't confirm your conclusions. On my device with version 1.4.2, the trigger works normally over the entire duration range.
Show your video of the malfunction?
Give one pulse 1-10 uS. And you won't see him. He will be behind the screen.
Would you mind sharing your exact experiment setup? I'm trying to reproduce the problem on FW 1.32 and can't. I must be missing something. Thanks
Setting up the signal generator:
1kHz pulse, 3Vpp, without offset, the width of the pulse is 991ns, my signal generator does not allow 1ms at a frequency of 1kHz.
Setting up the scope:
1V/Div, single trigger.
I will try it first in 500ns/div.
the second time in 250ns/div.
You can try the same with the normal trigger.
You start with 1us/div and switch to a faster time base.
500ns, 250ns, 100ns.
The pulse will disappear at 250ns/div and below.
single trigger will catch something, but you won't see the wave.
+ it seems that the waveform before the trigger is not saved.
I set the signal generator to 2Vpp pulse, 1MHz and 10% width.
I set the scope to 500ns/div and the trigger to approx. I set it to single trigger at 2V so that it does not trigger on the signal.
Then I set the voltage on the signal generator to 4Vpp.
And you can see that there is no 2Vpp before the trigger.
and at 250ns/div, that the trigger is delayed by 9 divisions compared to the signal.
-
Thanks for the explanation!
I assume, there is no way to turn off beep when changing the modes?
-
Trigger in version 1.4.2 does not work with time scale 250ns/div and less. So I can't observe 100-200-400ns pulses in good resolution.
I can't confirm your conclusions. On my device with version 1.4.2, the trigger works normally over the entire duration range.
Show your video of the malfunction?
Give one pulse 1-10 uS. And you won't see him. He will be behind the screen.
Would you mind sharing your exact experiment setup? I'm trying to reproduce the problem on FW 1.32 and can't. I must be missing something. Thanks
I tested firmware 1.38 and higher. The trigger works correctly only in 1.38. I have not tested it below this version.
-
Setting up the signal generator:
1kHz pulse, 3Vpp, without offset, the width of the pulse is 991ns, my signal generator does not allow 1ms at a frequency of 1kHz.
Setting up the scope:
1V/Div, single trigger.
I will try it first in 500ns/div.
the second time in 250ns/div.
You can try the same with the normal trigger.
You start with 1us/div and switch to a faster time base.
500ns, 250ns, 100ns.
The pulse will disappear at 250ns/div and below.
single trigger will catch something, but you won't see the wave.
+ it seems that the waveform before the trigger is not saved.
I set the signal generator to 2Vpp pulse, 1MHz and 10% width.
I set the scope to 500ns/div and the trigger to approx. I set it to single trigger at 2V so that it does not trigger on the signal.
Then I set the voltage on the signal generator to 4Vpp.
And you can see that there is no 2Vpp before the trigger.
and at 250ns/div, that the trigger is delayed by 9 divisions compared to the signal.
First off, thank you for taking the time to post your setup with screenshots and a detailed explanation, it helped a lot.
I've run your experiment and tested it with FW1.32 on the ZT703 and also on the OWON VDS1022i and could NOT replicate any of the trigger problems you mentioned, the behavior is also identical to the Owon's.
Does anyone remember the bugs 1.32 has? I do remember :high frequency jitter, low frequency waveform artifacts, cursor disappearance, CH2 activation after Auto Range. Anything else?
-
Why when i try to calibrate the probe nothing changes in the square wave form. I tried both probes.
-
Why when i try to calibrate the probe nothing changes in the square wave form. I tried both probes.
Calibration is done without probes connected.
Or, did you mean the probe compensation adjustment? Switch the probe to 1x mode.
EDIT: 10x not 1x :palm:
-
I tried to use my UNI-T UTG932E to replicate the problem with the trigger, but i'm getting this weird looking mess.
It looks normal when the trigger is in auto mode. But if i put it single-capture mode and turn on the function generator channel, it looks like in the screenshot.
Not sure which one of these cheap units is causing this. Is it the Uni-T or Zoyi ::)
-
Why when i try to calibrate the probe nothing changes in the square wave form. I tried both probes.
Calibration is done without probes connected.
Or, did you mean the probe compensation adjustment? Switch the probe to 1x mode.
It's the other way around, he needs to switch the probe to the 10x position ;)
I tried to use my UNI-T UTG932E to replicate the problem with the trigger, but i'm getting this weird looking mess.
You need to increase the pulse amplitude to 3Vpp
-
xKertx
The disturbance before the trigger in the wave is 99% the fault of your signal generator.
I copied your settings and with DG912Pro.
It triggered 12 periods later after the very first wave.
In other words, the tigger was delayed by almost 250 us.
The time base you use is not the same as what is wrong with us.
We notice the strange behavior with the trigger at 250nanosec and the faster one at 100ns, 50ns, 25ns, 10ns.
I did a few quick tests, the delay is not the same every time.
If you use your setting in normal trigger mode and start reducing the time base, that is, you speed it up.
From 25microsec to 100nanosec, you will find that at 250 nanosec and faster timebases the triggering is unstable. This is in 250MSa/s mode.
If you turn on the 280Msa/s mode, the trigger becomes unstable at 500nanosec, even if the peakdetect switch is on.
-
In the picture in which the wave in front of the trigger is not visible, I think it is lost, not because of the Zoyi.
When I change the amplitude of the signal, the Rigol DS912Pro turns off the output for 14ms. :palm:
Even when adjusting from 200mV to 210mV. :scared:
-
Hi, do you guys managed to calibrate the multimeter mode in ZT-703S? Mine is showing 928mA when putting 1A through it. Any thoughts?
-
Hi, do you guys managed to calibrate the multimeter mode in ZT-703S? Mine is showing 928mA when putting 1A through it. Any thoughts?
The multimeter chip resembles the well-studied DTM0660. That's why I simply saved the contents of the soldered-in I2C EEPROM. The address 0x2A contains the calibration coefficient for current with a limit of 2.5A. By changing it I adjusted the readings.
-
The multimeter chip resembles the well-studied DTM0660. That's why I simply saved the contents of the soldered-in I2C EEPROM. The address 0x2A contains the calibration coefficient for current with a limit of 2.5A. By changing it I adjusted the readings.
Ow, you are a lifesaver... Waiting for my eeprom reader/writer to arrive and I will try to change the coefficient.
-
Did you manage to find out which SPI microcircuit is in the 703 model? I calculated the dump.
The data seems adequate, but it is definitely not the 25 series, it looks like AT45XXXX
-
I wanted to use the Rigol PVP3150 150MHz probe with this scope because it has 20MHz bandwidth in 1X mode and i thought it would be good for low voltages.
And while it seems to have much less noise, for some reason in 10X mode it shows annoying overshoot at the edges and the compensation adjustment wont help much.
The compensation kind of works, but the spike at the beginning remains no matter whitch position i turn the compensation screw.
Any ideas what could cause this?
I would have thought that a probe, that costs almost as much as this oscilloscope, would perform flawlessly. But atleast in this case the cheap probe that came with the scope works better.
Or, does it have something to do with the fact that the more expensive Rigol probe probably has lower capacitance and the cheap probe is somehow matched with the scopes input capacitance?
On the screenshot the CH1 is the probe that came with the ZT-703s and CH2 is the Rigol PVP3150.
I went back to this post regarding the probe issue, because I'm seeing strange things myself. I'm feeding a 5V sine wave into the 10x probe, and am observing a significant voltage attenuation when going beyond 300kHz. I need to retest tomorrow more thoroughly, but when reaching the low MHz range I'm down to 4.6-4.7V. The 1X setting shows more accurate values - 4.8-5V
I connected my OWON probes and the attenuation is even worse, i.e., 4.3V
Given my ignorance I'm suspecting a problem with the scope's gain or maybe the probe itself!?
Can anyone shine some light on this? Thanks.
-
Can anyone shine some light on this? Thanks.
The included probes are extremely bad. Buy at least the P6100.
-
The included probes are extremely bad. Buy at least the P6100.
But problem is that other brand probes can't be compensated properly with this scope.
At least the Rigol PVP3150 150MHz probes didn't work properly.
-
But problem is that other brand probes can't be compensated properly with this scope.
At least the Rigol PVP3150 150MHz probes didn't work properly.
I'll try to check in the next few days with all the probes I have. What frequencies are you interested in?
-
Can anyone shine some light on this? Thanks.
In which time base did you measure the signal?
I measured 100kHz in 10microSec/div.(us)
It was 5.2Vpp and at 10x.
I increased the frequency to 400kHz, I did not change the time base.
And the automatic measurement says 4.2Vpp.
The wave on the display did not change significantly, it shrunk a little, but not to 4.2Vpp, measured with the cursor it was 5.1Vpp.
It behaves the same on both channels.
If I change the time base, the automatic measurement writes 5.2Vpp again.
In my case, the attenuation was a maximum of 0.3V. I looked up to 20MHz.
Measured with the Owon HDS120 in oscilloscope mode, 5.2Vpp.
I played with it a little more, I used the same 6100 100MHz measuring probe. I can't find the one I got for the Zoyi.
I simply connected the BNC to another scope, Owon HDS2202, Rigol DHO924S, Micsig to1104. All measured 5.9Vpp. Bad probe.
Measured with the device's own measuring probe, the signal is around 5.1V. Good probe.
It is possible that you only have the time base set incorrectly, try measuring it with the cursor.
-
Thank you everyone for the help and suggestions.
I did find a bit of time today to do a bit more testing.
I have come to the conclusion that the problem is with my new signal generator (if you can call it that) the (in)famous Feeltech FY3200S. The Vpp output specially on the sine wave seems to drop starting at 1kHz reaching 4.6Vpp (5Vpp setting) at 100kHz, but that's an issue to be dealt with in another thread.
When comparing the Zoyi and the Owon VDS1022i the differences were insignificant, also the Vrms measurements with a multimeter confirmed the voltage drop, all that made me suspect the signal generator. But the Zoyi definitely doesn't like the Owon probes, need to spend some more time investigating that.
Combine my ignorance and incompetence with three cheap untrustworthy pieces of equipment and the level of uncertainty of what's going on tends to infinity. |O
I wish I could justify buying "real" equipment.
Thanks for doing some tests for me and all the help and tips of using cursors instead of eyeballing and switching timebases, etc.
Sorry, for posting before doing some more thorough testing.
-
The multimeter chip resembles the well-studied DTM0660. That's why I simply saved the contents of the soldered-in I2C EEPROM. The address 0x2A contains the calibration coefficient for current with a limit of 2.5A. By changing it I adjusted the readings.
BTW, are you sure, that 703S has DTM0660? Because now I am reading, that the previous 702S had DM1109EN, and not DTM0660. The chip on 703S is unfortunately lasered out. Did you correct the coeficcients on the 703S itself?
-
I'll try to check in the next few days with all the probes I have. What frequencies are you interested in?
The 1khz test signal.
See post #604.
-
BTW, are you sure, that 703S has DTM0660? Because now I am reading, that the previous 702S had DM1109EN, and not DTM0660. The chip on 703S is unfortunately lasered out. Did you correct the coeficcients on the 703S itself?
I don't know what chip is used in the multimeter. It's definitely not DTM0660 since it can show 25,000 counts.
However, the data structure in EEPROM is similar.
The first thing I tried was changing the 16-bit value in the cell at address 0x2A and it worked.
The dump looks very similar to DTM0660, but since it works in tandem with the main controller, I didn't touch anything else.
-
again, the common opinion is DTM0600 and DM1106EN are cheap clones of Hycon HY12P66, that's why there are so cheap DMMs with them compared to the one that has original Hycon HY12P66 inside.
I don't think DTM0660L/DM1106EN are clones. You can see from the DTM0660L photo
(https://www.eevblog.com/forum/testgear/new-trms-uni-t-ut139c-dmm-is-available-now/?action=dlattach;attach=60031;image)
there are two logos on the chip, DreamTech / HyconTek.
(http://www.dreamtechintl.com.cn/templates/en2014/images//in_02.gif)
(http://www.hycontek.com/wp-content/themes/hycon/images/logo/logo.png)
Dream Tech International Ltd is just a trading company import the chips from Taiwan, and export the chips to the manufacturers in China. They do not produce any semiconductors.
HyconTek is just provided a DMM solution to the customers. You can order your customized chips from them.
Dream Tech International Ltd
http://www.dreamtechintl.com.cn/en/about/about-108.html (http://www.dreamtechintl.com.cn/en/about/about-108.html)
So isn't it?
-
Even 1.38 has a bug.
-
The multimeter chip resembles the well-studied DTM0660. That's why I simply saved the contents of the soldered-in I2C EEPROM. The address 0x2A contains the calibration coefficient for current with a limit of 2.5A. By changing it I adjusted the readings.
I did it! :D But it was not 0x2A, but 0x2E - 0x2F (Little Endian encoded) for 0-2,5A range, and 0x54 - 0x55 for 2,5 and above range.
-
I have detected what I think is a bug.
Using the signal generator I see that the amplitude changes when the frequency changes from 995Hz to 1KHz for senoidal and square waves as can be seen in the attached images.
-
:'( Ok, I just flashed my ZT-703S with newer firmware version 1.3.9
but when it was done it might have BRICKED the unit.
Right now, all it is doing is turning on and off the ZOYI logo and that is it. It will not let me in multimeter or oscilloscope mode. It will not let me even power off the device (even long pressed the Power button for say 20 seconds) no go. I've tried disconnecting the battery, but when reconnecting it will only turn on and off the ZOYI logo. It will not let me go to USB mode so I can reflash it with and older version.
Any suggestions on how to fix this? Like are there any special keys you need to press to get out of this and/or get back to the USB mode so I can reflash the unit.
Thanks.
-
Doin't worry, I have it every time I flash a new firmware.
Do this (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5325065/#msg5325065).
:'( Ok, I just flashed my ZT-703S with newer firmware version 1.3.9
but when it was done it might have BRICKED the unit.
Right now, all it is doing is turning on and off the ZOYI logo and that is it. It will not let me in multimeter or oscilloscope mode. It will not let me even power off the device (even long pressed the Power button for say 20 seconds) no go. I've tried disconnecting the battery, but when reconnecting it will only turn on and off the ZOYI logo. It will not let me go to USB mode so I can reflash it with and older version.
Any suggestions on how to fix this? Like are there any special keys you need to press to get out of this and/or get back to the USB mode so I can reflash the unit.
Thanks.
-
BIG THANKS to RAPo,
That was a scare... Thought I bricked my unit...
I believe the recovery steps are
- Remove Battery (by taking off back case)
- Wait for a minute
- Plug in USB cable (while battery is removed)
- Press Power Button (might still see flashing ZOYI logo)
- Press (maybe have to hold few seconds) F1 Key
This should put you into USB Mode which should allow you to see the ZT-703S as a Drive
- Go to the Firmware folder and copy the firmware from your computer hard drive to this firmware folder
Should see prompt on ZT-703 uploading the firmware - After a while new firmware should be updated on ZT-703S
- I then powered off, reinstalled the battery, and put back the DDM back cover.
Notes/Update(09May2026)
Had trouble loading ver. 6.12 (would say it couldn't upload file, so as workaround I copied firmware file first to LOG directory, then moved the file to the FIRMWARE directory and now it worked)
Another thing that "might" help is use USB directly to your computer port, not via a HUB.
-
:'( Ok, I just flashed my ZT-703S with newer firmware version 1.3.9
but when it was done it might have BRICKED the unit.
Right now, all it is doing is turning on and off the ZOYI logo and that is it. It will not let me in multimeter or oscilloscope mode. It will not let me even power off the device (even long pressed the Power button for say 20 seconds) no go. I've tried disconnecting the battery, but when reconnecting it will only turn on and off the ZOYI logo. It will not let me go to USB mode so I can reflash it with and older version.
Any suggestions on how to fix this? Like are there any special keys you need to press to get out of this and/or get back to the USB mode so I can reflash the unit.
Thanks.
Why did you choose 1.3.9 and not the latest 1.4.2?
-
The oscilloscope doesn't work right.
This is the signal generated and measured by Zoyi:
[attach=1]
And this is the signal measured by a Siglent oscilloscope:
[attach=2]
It is suppose than the signal amplitude is 2.5 Vpp but Zoyi measures just 2.3 Vpp, and Siglent measures 2.5 Vpp. My firmware is 1.4.2
I trust the Siglent oscilloscope.
Has someone notice any amplitude measurement error?
-
The built in signal generator is considered to be 'useless' or 'toy' by some testers. I don't own a signal generator (I don't need one for now), so the only use of the internal one was to calibrate the scope probes.
If you have a signal generator try comparing the ZT703s with the Siglent scope. I don't know for sure, but the internal electronics of the Zoyi may interfere with the scope when probing the internal generator?
-
The built in signal generator is considered to be 'useless' or 'toy' by some testers. I don't own a signal generator (I don't need one for now), so the only use of the internal one was to calibrate the scope probes.
If you have a signal generator try comparing the ZT703s with the Siglent scope. I don't know for sure, but the internal electronics of the Zoyi may interfere with the scope when probing the internal generator?
The signal seems a little noisy.
I don't have any signal generator either, but maybe you are right and the problem is that I am measuring with the same device which is generating the signal and there may be any kind of interference
-
I quickly tested my copy.
When I used its own generator, it was 2.4Vpp.
changing the time base also changes the measured value.
It measured 2.5Vpp in 200us/div.
I noticed that the accuracy of the measurement also depends on the time base, Zoyi can't always determine the voltage of the signal very well.
Sometimes it needs more samples.
This is a bug or a hardware limitation.
Using an external generator, the frequency was stable, and the voltage measured a fixed 2.5Vpp.
When you use the "signal generator" in oscilloscope mode, the properties of the oscilloscope deteriorate. It is no accident that it limits the minimum time base to 100us/Div.
If you have the opportunity, make a simple electronics that you can measure with your Siglent and Zoyi.
-
I quickly tested my copy.
When I used its own generator, it was 2.4Vpp.
changing the time base also changes the measured value.
It measured 2.5Vpp in 200us/div.
I noticed that the accuracy of the measurement also depends on the time base, Zoyi can't always determine the voltage of the signal very well.
Sometimes it needs more samples.
This is a bug or a hardware limitation.
Using an external generator, the frequency was stable, and the voltage measured a fixed 2.5Vpp.
When you use the "signal generator" in oscilloscope mode, the properties of the oscilloscope deteriorate. It is no accident that it limits the minimum time base to 100us/Div.
If you have the opportunity, make a simple electronics that you can measure with your Siglent and Zoyi.
I have measured a Vcd voltage. It was supposed to be a 5 Vdc.
[attach=1]
[attach=2]
[attach=3]
[attach=4]
The value obtained with the multimeter is right, but the values obtained with the oscilloscope are wrong, and the RMS value is the worst..
-
I have measured a Vcd voltage. It was supposed to be a 5 Vdc.
The value obtained with the multimeter is right, but the values obtained with the oscilloscope are wrong, and the RMS value is the worst..
The voltage measurements are not reliable, it's always better to use the cursors.
Could you please check if using the probe at 1x makes any difference?
-
I have measured a Vcd voltage. It was supposed to be a 5 Vdc.
The value obtained with the multimeter is right, but the values obtained with the oscilloscope are wrong, and the RMS value is the worst..
The voltage measurements are not reliable, it's always better to use the cursors.
Could you please check if using the probe at 1x makes any difference?
The probe was at 1x.
I didn't use the cursors, but the shown signal has the same amplitude than the values measured.
Anyway, I will do it again using the cursors.
-
The probe was at 1x.
I didn't use the cursors, but the shown signal has the same amplitude than the values measured.
Anyway, I will do it again using the cursors.
I meant using the cursors when analyzing periodic signals, with a DC signal it can be eyeballed easily.
My scope/probe combo is accurate in 1x up to 6MHz. In 10x mode I do have attenuation starting at 100kHz. If I calibrate the probe I can either adjust to minimize distortion or attenuation, but there's really no sweet spot, so I have to compromise.
-
Hello - does anyone know if Zoyi is working on an update to firmware 1.4.2 and if so, when we might expect it? Thanks.
-
Trying to understand the nature of the attenuation of the Zoyi I measured a 5Vpp sinewave from a signal generator using the Zoyi probe both on the Zoyi and the OWON VDS1022i. I measured in orders of magnitude from 1kHz up to 10MHz. The Owon measures approx 5Vpp through the entire range, the Zoyi does not.
These are the results:
-
Hello nikbry. I repeated your measurements and got 5 volts up to 1 MHz where it dropped to 4.9 and then at 10 MHz I got 4.7.
-
Hello nikbry. I repeated your measurements and got 5 volts up to 1 MHz where it dropped to 4.9 and then at 10 MHz I got 4.7.
Thanks for taking the time. Is your probe perfectly compensated?
As I said before my unit is extremely sensitive to the slightest variation in compensation of the probe. If I remove the distortion completely (perfect squares) then I get the attenuation shown in my screenshots. If I overcompensate the probe then I get results similar to yours.
-
The probe is properly compensated.
-
I have measured a Vcd voltage. It was supposed to be a 5 Vdc.
The value obtained with the multimeter is right, but the values obtained with the oscilloscope are wrong, and the RMS value is the worst..
The voltage measurements are not reliable, it's always better to use the cursors.
Could you please check if using the probe at 1x makes any difference?
Here you can see the same measure using cursors.
[attachimg=1]
You can notice the cursors show the same voltage than the oscilloscope measurements.
Something is wrong in the oscilloscope.
-
Trying to understand the nature of the attenuation of the Zoyi I measured a 5Vpp sinewave from a signal generator using the Zoyi probe both on the Zoyi and the OWON VDS1022i. I measured in orders of magnitude from 1kHz up to 10MHz. The Owon measures approx 5Vpp through the entire range, the Zoyi does not.
These are the results:
The same results that I obtained with a 5Vdc signal.
Is the country the problem? :-//
-
Hello nikbry. I repeated your measurements and got 5 volts up to 1 MHz where it dropped to 4.9 and then at 10 MHz I got 4.7.
Was your probe attenuated to 10x?
-
Yes at 10X.
-
Yes at 10X.
Ok, because the bandwidth changes.
-
Trying to understand the nature of the attenuation of the Zoyi I measured a 5Vpp sinewave from a signal generator using the Zoyi probe both on the Zoyi and the OWON VDS1022i. I measured in orders of magnitude from 1kHz up to 10MHz. The Owon measures approx 5Vpp through the entire range, the Zoyi does not.
These are the results:
The same results that I obtained with a 5Vdc signal.
Is the country the problem? :-//
I have no problems when using the probe at 1x. My issue is when using 10x, where I see attenuation unless I overcompensate the probe slightly.
I also tried with a P6100 probe and I need to overcompensate it too, so the issue seems to be the scope.
-
Trying to understand the nature of the attenuation of the Zoyi I measured a 5Vpp sinewave from a signal generator using the Zoyi probe both on the Zoyi and the OWON VDS1022i. I measured in orders of magnitude from 1kHz up to 10MHz. The Owon measures approx 5Vpp through the entire range, the Zoyi does not.
These are the results:
The same results that I obtained with a 5Vdc signal.
Is the country the problem? :-//
I have no problems when using the probe at 1x. My issue is when using 10x, where I see attenuation unless I overcompensate the probe slightly.
I also tried with a P6100 probe and I need to overcompensate it too, so the issue seems to be the scope.
This is the raising edge response of my probes. Each probe compensated for each channel. The signal is the output D12 of an Arduino Nano.
Siglent probe on channel 1, Zoyi probe on channel 2 and P6100 chinese probe on channel 3.
Without attenuation:
[attach=1]
10x attenuation:
[attach=2]
Without attenuation on the probe the Zoyi probe is the faster, but with the probe attenuated the faster is the Siglent one.
From 0% to 100% 10x probe:
[attach=3]
I think the Zoyi probe gives a 45MHz bandwith without attenuation on the signal. Or maybe there is something I have not considered.
I think the same than you: the problem is the scope because the frequency response of the probe is fast enough to not to have attenuation on the signal.
-
Serious bug found. I don't follow this thread carefully, so maybe I've missed such error report. Sorry if it is the case
The issue is quite serious: when probe is connected to calibration generator signal amplitude is decreasing sharply for time base LONGER than 5ms, and totally disappears at 50ms/div. The same behaviour on both channels.
Old 702 works ok.
Is it my device fault, or all works the same way?
Edit: it works ok in "peak" sample mode, hd makes plot a straight line.
-
Serious bug found. I don't follow this thread carefully, so maybe I've missed such error report. Sorry if it is the case
The issue is quite serious: when probe is connected to calibration generator signal amplitude is decreasing sharply for time base LONGER than 5ms, and totally disappears at 50ms/div. The same behaviour on both channels.
Old 702 works ok.
Is it my device fault, or all works the same way?
Edit: it works ok in "peak" sample mode, hd makes plot a straight line.
No issues here, neither in "Normal" nor "High" "Run Mode". FW1.32
-
it behaves the same way with me.
In 20ms/div the signal is smaller, in 50ms/div it disappears.
When you turn on Peakdetect, the signal looks good.
V1.4.2
-
Serious bug found. I don't follow this thread carefully, so maybe I've missed such error report. Sorry if it is the case
The issue is quite serious: when probe is connected to calibration generator signal amplitude is decreasing sharply for time base LONGER than 5ms, and totally disappears at 50ms/div. The same behaviour on both channels.
Old 702 works ok.
Is it my device fault, or all works the same way?
Edit: it works ok in "peak" sample mode, hd makes plot a straight line.
No issues here, neither in "Normal" nor "High" "Run Mode". FW1.32
Try to change "sample mode", not the "run mode".
-
it behaves the same way with me.
In 20ms/div the signal is smaller, in 50ms/div it disappears.
When you turn on Peakdetect, the signal looks good.
V1.4.2
My fw is older, but effect is the same.
So we have a bug. IMO quite nasty....
-
Try to change "sample mode", not the "run mode".
Where do I change that? Not sure FW1.32 has that Menu option!?
-
Try to change "sample mode", not the "run mode".
Where do I change that? Not sure FW1.32 has that Menu option!?
It's where you set the trigger settings.
"Sample" that you can convert to "HD" or "PEAK".
When set to HD, the wave is not visible.
-
Try to change "sample mode", not the "run mode".
Where do I change that? Not sure FW1.32 has that Menu option!?
It's where you set the trigger settings.
"Sample" that you can convert to "HD" or "PEAK".
When set to HD, the wave is not visible.
FW 1.32 doesn't have that menu option, it has trig position instead.
Here ¡s a screenshot at 200ms/div.
-
Try to change "sample mode", not the "run mode".
Where do I change that? Not sure FW1.32 has that Menu option!?
It's where you set the trigger settings.
"Sample" that you can convert to "HD" or "PEAK".
When set to HD, the wave is not visible.
FW 1.32 doesn't have that menu option, it has trig position instead.
Here ¡s a screenshot at 200ms/div.
-
Hello to all,
Yesterday I got some good news and since the halloween sales started on AliE I decided to order a ANENG AOS03 basically to use icw my UT210E, Since my UT71C is beeping continuesly.
I am a newbee on Scopes, I have a basic theory on how to use them, But I was wundering if anyone of you here can point me to a nice online tutorial that helps me making the most of this new hobbiest scope, without going to deep into all the special dealings dealing with professional scopes.
Also I want to go and try to go about finding the problem with my UT71C by trying what creates the pulse to let the piezo disk beep.
about the firmware, Can I use firmware for the zoyi zt703s for the aneng aos03, they are essentially the same machine (essentially or exactly?)
Additionally I was wondering if there are special things I need to do before using the scope tool, besides the things below here.
1) update / downgrade the firmware. -> and here, I have the question, which is the most stable / least buggy version at the moment> (1.42 / 1.39 / 1.38)
2) calibrate the scope probes (I have some myself, but i am not sure if they are going to be better / equal / worse, quality compared to the probes provided with the scope
I have read through most of the thread and because of that I figure I need to stay away from some measuring errors. Just not sure which ones, does anyone have any thoughts on this that could help a / some newbee's out?
Kind greats
Matthieu
ps: is there any talk about new up and coming firmware more recent then 1.4.2?)
-
I am a newbee on Scopes, I have a basic theory on how to use them, But I was wundering if anyone of you here can point me to a nice online tutorial that helps me making the most of this new hobbiest scope, without going to deep into all the special dealings dealing with professional scopes.
In my opinion, this and similar devices are not suitable as a first oscilloscope, which is necessary for a beginner.
The software and hardware of such devices contains a lot of errors and without having skills in work it will be difficult for you to determine who made a mistake - the user or the hardware part. As I wrote before and my opinion has not changed, the oscilloscope in this device has a toy interface, very clumsy and clumsy in operation.
The multimeter is several orders of magnitude better and more convenient in this instrument.
-
Lol, sorry, have to disagree with you… try giving a newbie something like a Tektronix 465 oscilloscope, and see how long they take to master it. The main lesson is, know your tools. As gar as your multimeter is concerned, went through 30+ years of juniors engineers and techs, trying not to scream out aloud "just use your f*****g oscilloscope" whilst they keep on using a multimeter. Know your tools. These new-fangled oscilloscope/multimeters are perfect to throw in your toolbox, bust like any other test instrument, know its use cases and limitations.
-
These new-fangled oscilloscope/multimeters are perfect to throw in your toolbox, bust like any other test instrument, know its use cases and limitations.
I completely disagree with your conclusions. If a device behaves unpredictably, it may confuse the user.
And it cannot in any way be considered a measuring instrument. This is nothing more than a toy.
-
These new-fangled oscilloscope/multimeters are perfect to throw in your toolbox, bust like any other test instrument, know its use cases and limitations.
I completely disagree with your conclusions. If a device behaves unpredictably, it may confuse the user.
And it cannot in any way be considered a measuring instrument. This is nothing more than a toy.
I think by far the biggest problem with the Zoyi is that there are too many FWs and all have plenty of bugs, it's a mess.
If we only had had one FW, by now we would have identified all the bugs and would know what to expect from it, and it would be predictable.
So, I chose FW 1.32 and have kept track of all the bugs, and now feel pretty confident in what to expect and where the problems are. I don't plan to update, unless Zotek by devine influence manage to fix the FW for good.
But if you update with every new (almost monthly) iteration of buggy FW, then of course, you end up with an unpredictable instrument.
Of course, identifying bugs in itself is a fun learning experience too...
-
@Indman,
Although I do understand what you come from and I understand that you say it with the best intentions but I feel I disagree too.
I started to try to explain why, but I ended up with a text that is honoust but that it can be seen as ungratefull and I don't want it to be like that at all.
So please try to forgive me ;)
Generally speaking though I feel a response (any forum/any topic) like in context of "what you do is wrong, you'd better do it my way".
Is not constructive, at least not for me anyway, no matter how right you may feel about your opinion.
Do take in account that there is always personal situations to consider that are important to the recieving end.
In my case a usb scope / are a student stope is not usefull to me both because of space, finances en personal mental (ADHD) way of working.
If I need to put a big device in my bench, I would need to take to much time to reorganise everything, not worth it for most jobs, so I would end up not using it.
This is a deep plunge for me and I feel like I have spend a large amount (for me anyway) for a tool I feel like I will actually use.
And I didn't make the choise in a day or so.
@ Nikbry, is this choise for FW 1.32 a conscious choise based on some criteria that were important to you or did you just stick with it over time more like randomly?
In the first case I could decide to start with 1.32 too. If it is the latter I'd could just start with what it comes with, or even the latest one and stick with it from there.
Generally speaking, is there a FW version that can be seen as "the least" buggy?
Anyway, I do feel like identifying bugs I read about in this thread, finding them will help me knowing when I would bump into them.
Also, is there some agreement on where I could find free online scope tutorial?
preferrably one that skips over the most basic stuff but does in form you enough to actually learn something from it, specifically on topic of debugging hardware?
kind greats
Matthieu
-
I am a newbee on Scopes, I have a basic theory on how to use them, But I was wundering if anyone of you here can point me to a nice online tutorial that helps me making the most of this new hobbiest scope, without going to deep into all the special dealings dealing with professional scopes.
In my opinion, this and similar devices are not suitable as a first oscilloscope, which is necessary for a beginner.
The software and hardware of such devices contains a lot of errors and without having skills in work it will be difficult for you to determine who made a mistake - the user or the hardware part. As I wrote before and my opinion has not changed, the oscilloscope in this device has a toy interface, very clumsy and clumsy in operation.
The multimeter is several orders of magnitude better and more convenient in this instrument.
I agree with you.
I had a good idea about this device, but this idea become worse as I discover/read bugs.
Lol, sorry, have to disagree with you… try giving a newbie something like a Tektronix 465 oscilloscope, and see how long they take to master it. The main lesson is, know your tools. As gar as your multimeter is concerned, went through 30+ years of juniors engineers and techs, trying not to scream out aloud "just use your f*****g oscilloscope" whilst they keep on using a multimeter. Know your tools. These new-fangled oscilloscope/multimeters are perfect to throw in your toolbox, bust like any other test instrument, know its use cases and limitations.
A real scope is much more difficult to know than this kind of devices, but it is more reliable. The main problem is that one needs to trust his measuring instrument and this does not happen because of the bugs. With experience and taking a reliable scope as reference one can know what are the bugs and take them in consideration in the measurements.
These new-fangled oscilloscope/multimeters are perfect to throw in your toolbox, bust like any other test instrument, know its use cases and limitations.
I completely disagree with your conclusions. If a device behaves unpredictably, it may confuse the user.
And it cannot in any way be considered a measuring instrument. This is nothing more than a toy.
I think by far the biggest problem with the Zoyi is that there are too many FWs and all have plenty of bugs, it's a mess.
If we only had had one FW, by now we would have identified all the bugs and would know what to expect from it, and it would be predictable.
So, I chose FW 1.32 and have kept track of all the bugs, and now feel pretty confident in what to expect and where the problems are. I don't plan to update, unless Zotek by devine influence manage to fix the FW for good.
But if you update with every new (almost monthly) iteration of buggy FW, then of course, you end up with an unpredictable instrument.
Of course, identifying bugs in itself is a fun learning experience too...
I have used only the last firmware and I can't compare with other versions, but due to the fact I see there are some bugs and I don't know all of them, I don't trust this device completely yet.
Could be interesting to discover bugs, but frustating at the same time because they make you feel you have made a wrong purchase.
I think if the manufacturers released the source code or information to allow the customers to improve the firmware, it would be better for the customer but at the same time would make sales rise.
-
@IC_Toaster
Yeah I do realise this is as much a oscilloscope as cheap hardwarestore MM stand to something professional multimeter.
So i know I will nevery completely trust a device like this, but for now I am oke with this. it's all a balance of personal pro's and cons.
I think if the manufacturers released the source code or information to allow the customers to improve the firmware,
it would be better for the customer but at the same time would make sales rise. >>> now that is something I can completely agree with.
Additionally would also cut on there development costs.. so all pro's / no con's at least non that I can see..
accept that it might help with reverse engineering??? and as the IC's are all laser etched it's seems to be one of there biggest concerns.
but about the firmware, anyone else owning the aneng version.
Can one use the zoyi FW?
this seems to be a question that has been asked before, but i haven't found an conclusive answer on yet (I might have just read over it though)
Kind greats
Matthieu
-
@IC_Toaster
Yeah I do realise this is as much a oscilloscope as cheap hardwarestore MM stand to something professional multimeter.
So i know I will nevery completely trust a device like this, but for now I am oke with this. it's all a balance of personal pro's and cons.
I think if the manufacturers released the source code or information to allow the customers to improve the firmware,
it would be better for the customer but at the same time would make sales rise. >>> now that is something I can completely agree with.
Additionally would also cut on there development costs.. so all pro's / no con's at least non that I can see..
accept that it might help with reverse engineering??? and as the IC's are all laser etched it's seems to be one of there biggest concerns.
but about the firmware, anyone else owning the aneng version.
Can one use the zoyi FW?
this seems to be a question that has been asked before, but i haven't found an conclusive answer on yet (I might have just read over it though)
Kind greats
Matthieu
If you don't need an accurate measuring instrument this device could be enough for you. Just keep in mind the limitations this device has.
I can't answer your question about the firmware, but I think this is just the same device with different label, so the firmware must be exactly the same. Maybe the booting screen is different with 'Aneng' word instead of 'Zoyi'
-
@ Nikbry, is this choise for FW 1.32 a conscious choise based on some criteria that were important to you or did you just stick with it over time more like randomly?
In the first case I could decide to start with 1.32 too. If it is the latter I'd could just start with what it comes with, or even the latest one and stick with it from there.
In my mind an oscilloscope has to do at least three things correctly:
1) Display the right waveform without distortions or artifacts (sine, square, AM, FM, pulse, etc)
2) Trigger reliably
3) Display data accurately and as precisely as possible
To answer your question:
FW 1.32
1) Displays the waveform correctly, except: a) with medium/high MHz signals a jitter becomes evident b) at very low frequencies and large time bases periodic signals show a somewhat randomly appearing distortion of the wave.
2) Trigger works reliably (FW 1.38 and upwards introduced trigger HD and Peak, and corrected the jitter. This broke the trigger function, specially with fast pulses. Autorange was broken too.)
3) The measurements done by the scope are mostly inaccurate for voltages and OK for frequency and period. I suggest you use the cursors to get a better quantification. This is true for all FW versions.
Some minor problems of FW1.32 are that when you autorange with no signal, CH2 activates itself. Also when holding an image the cursor lines sometimes disappear when moving them.
With FW1.32 you miss out on: the trigger peak/HD option, the FFT function, ...
The biggest problem with my unit and @IC_Toaster's seems to be a hardware one. In my case at 10x probe setting I do have a noticeable signal attenuation in @IC Toaster's it's even more severe.
The normal behavior of the Zoyi should be to see no attenuation up to 10MHz.
If you can, get access to a reliable signal generator (and ideally a second reliable oscilloscope) and test your unit to see how it behaves.
The Zoyi firmware works just fine on an Aneng.
A good beginner's exercise with an oscilloscope is to "design" RC low pass, high pass, band filters. Here are two links:
https://www.homofaciens.de/technics-base-circuits-rc-circuit_en.htm (https://www.homofaciens.de/technics-base-circuits-rc-circuit_en.htm)
https://www.electronics-tutorials.ws/filter/filter_1.html (https://www.electronics-tutorials.ws/filter/filter_1.html)
-
I cannot update the firmware from 1.3.9 to 1.4.2 because it says the disk is full. (it says 592k is free from the 608k, but the fw file is 636k)
How to overcome this issue?
-
I cannot update the firmware from 1.3.9 to 1.4.2 because it says the disk is full. (it says 592k is free from the 608k, but the fw file is 636k)
How to overcome this issue?
How about deleting some screenshots to free up space?
-
but about the firmware, anyone else owning the aneng version.
Can one use the zoyi FW?
this seems to be a question that has been asked before, but i haven't found an conclusive answer on yet (I might have just read over it though)
Yes, you can use zoyi FW. It's the same unit with different labels.
I personally think the latest FW works best.
Yes, it still has some bugs, but many bugs are fixed and the autoset works also.
I don't unerstand why would anyone want to use old firmware intentionally. The old FW does not have nothing that the latest FW don't have.
In addition to calibration, also remember to compensate the probes properly. And don't swap probes after that (use the colourcoded rings to identify them).
If you adjusted one probe to match CH1, then use it in CH1. And if you want to use it in CH2 then you would need to re-adjust it's compensation.
-
but about the firmware, anyone else owning the aneng version.
Can one use the zoyi FW?
this seems to be a question that has been asked before, but i haven't found an conclusive answer on yet (I might have just read over it though)
Yes, you can use zoyi FW. It's the same unit with different labels.
I personally think the latest FW works best.
Yes, it still has some bugs, but many bugs are fixed and the autoset works also.
I don't unerstand why would anyone want to use old firmware intentionally. The old FW does not have nothing that the latest FW don't have.
In addition to calibration, also remember to compensate the probes properly. And don't swap probes after that (use the colourcoded rings to identify them).
If you adjusted one probe to match CH1, then use it in CH1. And if you want to use it in CH2 then you would need to re-adjust it's compensation.
I'll try not to take your somewhat harsh comment offensively... I don't understand why people just install the newest firmware 1.42, even if it has critical issues like a faulty trigger. It must be the sign of the times of updating frenzy...
And YES the Autorange on 1.42 is much worse than on 1.32. Try it.
Also the issues I described with the attenuation have nothing to do with the probes or their compensation, this has been discussed by IC_Toaster and myself....
-
In my mind an oscilloscope has to do at least three things correctly:
1) Display the right waveform without distortions or artifacts (sine, square, AM, FM, pulse, etc)
I agree, but since now the oscilloscope does not reliably cope with this most important function №1, all other conditions become secondary. This is especially true for a portable instrument, as it is often the only tool an engineer has in the field. If I need to find a fault in the circuit, I do not have to guess what exactly distorts the shape of the signal - oscilloscope or some faulty element in the circuit. And I'm not going to pester people to provide me with a more reliable tool to analyze it. :-// Buy a toy to find bugs in it and play continuously with version updates that remove old bugs and add many new ones - these adventures are not for me. I apologize if my harsh comment offended anyone.
-
And YES the Autorange on 1.42 is much worse than on 1.32. Try it.
I have tried both. The autoset works fine with 1.42. Atleast on my unit.
Also the issues I described with the attenuation have nothing to do with the probes or their compensation, this has been discussed by IC_Toaster and myself....
I answered to spikey, who said is new to oscilloscopes.
But the same applies to all oscilliscopes, even expensive ones. If you swap the probe to other channel, you should to check the compensation.
I am a newbee on Scopes, I have a basic theory on how to use them...
Additionally I was wondering if there are special things I need to do before using the scope tool
-
To gazsiazasz (#776):
I had a similar issue that prevented me from capturing screenshots. When I tried, it showed that it failed to take a screenshot. I had a couple of pictures on the device, but for some reason all of them disappeared. When I tried to revert the firmware, my PC showed just the empty screenshot folder, nothing else. I panicked, but after a reset from the oscilloscope menu (I think it's called "reset settings" or something like that), I could take screenshots and USB mode works now just fine. After that, I couldn't reflash the latest firmware because it was saying I don't have sufficient memory. I installed 1.39 without a problem, then flashed 1.42.
I have no idea what caused the device to soft-brick itself.
-
@nikbry
thank you, a very informative and constructive response.
I actually have a signal generator i could use (fairly descent one I believe),
I also have some sort of USB scope, but I never seem to use this, it is (for me personally) to much of an hassle.. but at least I have some sort of fall back when I need to compare stuff..
even though its not the best one either, it misses a lot of option like bandwith/sample rate, also it is also fairly old by now so.
about the firmware version, I do tend to be someone that prefers the latest FM, but in case of a faulty trigger.. well, lets say I will be seriously rethinking things. seems rather important / critical to me.
@xKertx
thank you, I would've understand that one would need to check compensation when swapping probes,
but I gues it could've skipped my mind. So it is good you pointed it out to me. thank you.
Do you do have trigger issues with 1.4.2?
@Indman, I completely understand your point of view, and absolutely correct and essential for a professional, but for me I feel I can and will just have to deal with it for now.
I tried to look around for a good textbook on oscilloscope usage and bumped into the following:
* oscilloscopes: a manual for students engineers and scientists by David Herres
does anyone have any reccommendations on if this is worth the time and effort?
Kind greats
Matthieu
-
Do you do have trigger issues with 1.4.2?
I get the feeling that you didn't read the thread in detail...
Look at page 29 reply 706, which illustrates the trigger issue on FW 1.42
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/700/ (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/700/)
-
I cannot update the firmware from 1.3.9 to 1.4.2 because it says the disk is full. (it says 592k is free from the 608k, but the fw file is 636k)
How to overcome this issue?
I have about 10MB of free space with two pictures.
the other 3.4MB is some kind of hidden file.
Looking in the Windows file manager, I only have files in the "pic" folder, the others seem to be empty.
Do you do have trigger issues with 1.4.2?
I get the feeling that you didn't read the thread in detail...
Look at page 29 reply 706, which illustrates the trigger issue on FW 1.42
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/700/ (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/700/)
That post is partly wrong, I later wrote that my method was wrong.
I wanted to continuously give a 2V sine wave to the scope, set the trigger to 3V and check with a single trigger what the wave is like, how long the delay is between the green arrow of the trigger and the real first trigger point. And to see if there is any distortion.
Unfortunately, I didn't know my signal generator well enough, I didn't know that if I changed the voltage, it would turn off the output and then turn it back on. This is why my measurement is not correct.
I tested it with a 1kHz 5Vpp color, which I checked on my sure-to-be-good scope.
At 250ns there is a slight delay in the trigger.
That doesn't mean it's unusable.
-
@ Nikbry, is this choise for FW 1.32 a conscious choise based on some criteria that were important to you or did you just stick with it over time more like randomly?
In the first case I could decide to start with 1.32 too. If it is the latter I'd could just start with what it comes with, or even the latest one and stick with it from there.
In my mind an oscilloscope has to do at least three things correctly:
1) Display the right waveform without distortions or artifacts (sine, square, AM, FM, pulse, etc)
2) Trigger reliably
3) Display data accurately and as precisely as possible
To answer your question:
FW 1.32
1) Displays the waveform correctly, except: a) with medium/high MHz signals a jitter becomes evident b) at very low frequencies and large time bases periodic signals show a somewhat randomly appearing distortion of the wave.
2) Trigger works reliably (FW 1.38 and upwards introduced trigger HD and Peak, and corrected the jitter. This broke the trigger function, specially with fast pulses. Autorange was broken too.)
3) The measurements done by the scope are mostly inaccurate for voltages and OK for frequency and period. I suggest you use the cursors to get a better quantification. This is true for all FW versions.
Some minor problems of FW1.32 are that when you autorange with no signal, CH2 activates itself. Also when holding an image the cursor lines sometimes disappear when moving them.
With FW1.32 you miss out on: the trigger peak/HD option, the FFT function, ...
The biggest problem with my unit and @IC_Toaster's seems to be a hardware one. In my case at 10x probe setting I do have a noticeable signal attenuation in @IC Toaster's it's even more severe.
The normal behavior of the Zoyi should be to see no attenuation up to 10MHz.
If you can, get access to a reliable signal generator (and ideally a second reliable oscilloscope) and test your unit to see how it behaves.
The Zoyi firmware works just fine on an Aneng.
A good beginner's exercise with an oscilloscope is to "design" RC low pass, high pass, band filters. Here are two links:
https://www.homofaciens.de/technics-base-circuits-rc-circuit_en.htm (https://www.homofaciens.de/technics-base-circuits-rc-circuit_en.htm)
https://www.electronics-tutorials.ws/filter/filter_1.html (https://www.electronics-tutorials.ws/filter/filter_1.html)
I have attenuation even in DC.
Someone commented that it is importanto to know your measuring instrument. Of course it is, but you need also a reliable instrument to compare when the instrument under test is working right and when is having a bug. Otherwise you can't know a measuring instrument which has bugs.
but about the firmware, anyone else owning the aneng version.
Can one use the zoyi FW?
this seems to be a question that has been asked before, but i haven't found an conclusive answer on yet (I might have just read over it though)
Yes, you can use zoyi FW. It's the same unit with different labels.
I personally think the latest FW works best.
Yes, it still has some bugs, but many bugs are fixed and the autoset works also.
I don't unerstand why would anyone want to use old firmware intentionally. The old FW does not have nothing that the latest FW don't have.
In addition to calibration, also remember to compensate the probes properly. And don't swap probes after that (use the colourcoded rings to identify them).
If you adjusted one probe to match CH1, then use it in CH1. And if you want to use it in CH2 then you would need to re-adjust it's compensation.
I'll try not to take your somewhat harsh comment offensively... I don't understand why people just install the newest firmware 1.42, even if it has critical issues like a faulty trigger. It must be the sign of the times of updating frenzy...
And YES the Autorange on 1.42 is much worse than on 1.32. Try it.
Also the issues I described with the attenuation have nothing to do with the probes or their compensation, this has been discussed by IC_Toaster and myself....
I agree. The signal amplitud shown and the measurement given by the device coincide and it makes me think it is not a software problem. But it is important to determine when it happens to find a behaviour pattern in order to know our measurement instrument.
In my mind an oscilloscope has to do at least three things correctly:
1) Display the right waveform without distortions or artifacts (sine, square, AM, FM, pulse, etc)
I agree, but since now the oscilloscope does not reliably cope with this most important function №1, all other conditions become secondary. This is especially true for a portable instrument, as it is often the only tool an engineer has in the field. If I need to find a fault in the circuit, I do not have to guess what exactly distorts the shape of the signal - oscilloscope or some faulty element in the circuit. And I'm not going to pester people to provide me with a more reliable tool to analyze it. :-// Buy a toy to find bugs in it and play continuously with version updates that remove old bugs and add many new ones - these adventures are not for me. I apologize if my harsh comment offended anyone.
I think the same. In the field you need to trust your measurement instrument because in some situations you have only that device and depending on the result given by it you have to take decisions.
@nikbry
thank you, a very informative and constructive response.
I actually have a signal generator i could use (fairly descent one I believe),
I also have some sort of USB scope, but I never seem to use this, it is (for me personally) to much of an hassle.. but at least I have some sort of fall back when I need to compare stuff..
even though its not the best one either, it misses a lot of option like bandwith/sample rate, also it is also fairly old by now so.
about the firmware version, I do tend to be someone that prefers the latest FM, but in case of a faulty trigger.. well, lets say I will be seriously rethinking things. seems rather important / critical to me.
@xKertx
thank you, I would've understand that one would need to check compensation when swapping probes,
but I gues it could've skipped my mind. So it is good you pointed it out to me. thank you.
Do you do have trigger issues with 1.4.2?
@Indman, I completely understand your point of view, and absolutely correct and essential for a professional, but for me I feel I can and will just have to deal with it for now.
I tried to look around for a good textbook on oscilloscope usage and bumped into the following:
* oscilloscopes: a manual for students engineers and scientists by David Herres
does anyone have any reccommendations on if this is worth the time and effort?
Kind greats
Matthieu
You what to buy a book to learn to use oscilloscopes without having a serious oscilloscope. I think that won't work.
I cannot update the firmware from 1.3.9 to 1.4.2 because it says the disk is full. (it says 592k is free from the 608k, but the fw file is 636k)
How to overcome this issue?
I have about 10MB of free space with two pictures.
the other 3.4MB is some kind of hidden file.
Looking in the Windows file manager, I only have files in the "pic" folder, the others seem to be empty.
Do you do have trigger issues with 1.4.2?
I get the feeling that you didn't read the thread in detail...
Look at page 29 reply 706, which illustrates the trigger issue on FW 1.42
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/700/ (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/700/)
That post is partly wrong, I later wrote that my method was wrong.
I wanted to continuously give a 2V sine wave to the scope, set the trigger to 3V and check with a single trigger what the wave is like, how long the delay is between the green arrow of the trigger and the real first trigger point. And to see if there is any distortion.
Unfortunately, I didn't know my signal generator well enough, I didn't know that if I changed the voltage, it would turn off the output and then turn it back on. This is why my measurement is not correct.
I tested it with a 1kHz 5Vpp color, which I checked on my sure-to-be-good scope.
At 250ns there is a slight delay in the trigger.
That doesn't mean it's unusable.
I don't understand what you try to show there because I don't see any relationship between the three images. I must have lost something.
-
I wrote it because of the trigger bug.
Around post 706, it was said that one of two rapid pulses in a row is lost.
We didn't know if it was a memory bug or something else, so I'm testing it based on what I described above, which led me astray. I don't know my signal generator well enough. :palm:
In the current three pictures.
I recorded the beginning of a slow sine wave at 250ns/div. With single trigger. PIC_6520.png
In order to rule out the case when the previous waves in the memory are still visible.
Then I shrunk it to 100us/div setting.PIC_6521.png
In order to see how much the trigger is "delayed"
And how does the wave that is in the memory look like.
Occasionally, there can be quite a big difference between the first trigger point and the point triggered by zoyi. I have already measured a delay of 6-7us, 11us, 44us.
Zoyi has some memory management issues and I've noticed that it sometimes trashes the wave.
The third picture is just a check to make sure I don't make the same mistake as in my previous test. where I didn't know that my signal generator turns off the output for several ms if I change the voltage.
At PIC_6521.png you can see a cut on the wave, it was not done by my signal generator, it is some kind of bug of Zoyi.
I hope they fix it this year.
-
I wrote it because of the trigger bug.
Around post 706, it was said that one of two rapid pulses in a row is lost.
We didn't know if it was a memory bug or something else, so I'm testing it based on what I described above, which led me astray. I don't know my signal generator well enough. :palm:
In the current three pictures.
I recorded the beginning of a slow sine wave at 250ns/div. With single trigger. PIC_6520.png
In order to rule out the case when the previous waves in the memory are still visible.
Then I shrunk it to 100us/div setting.PIC_6521.png
In order to see how much the trigger is "delayed"
And how does the wave that is in the memory look like.
Occasionally, there can be quite a big difference between the first trigger point and the point triggered by zoyi. I have already measured a delay of 6-7us, 11us, 44us.
Zoyi has some memory management issues and I've noticed that it sometimes trashes the wave.
The third picture is just a check to make sure I don't make the same mistake as in my previous test. where I didn't know that my signal generator turns off the output for several ms if I change the voltage.
At PIC_6521.png you can see a cut on the wave, it was not done by my signal generator, it is some kind of bug of Zoyi.
I hope they fix it this year.
I think now I undestand what you mean.
I have also noticed that the signal is capturated quite after the triger point and the scope makes you think the signal is not captured but when you change the time base to a larger value you find the signal, as you represented.
Notice also that the maximun value of the signal at PIC_6512 is 2,5V but the measure says 1,8V.
I don't understand why the signal is cut either.
Because of what you have shown, could we can say it is unusable? What is the utility of a measuring instrument which cut the signals and give wrong measurements?
-
@IC_toaster
I am not looking for a book to learn to use a oscilloscope but to understand the theory behind it in more depth.
sorry if i wasn't clear in that. But generally speaking books tend to be ggod for theoretics.
But also, I am not buying a book, plenty of books are available through official site in pdf. this one is too (#no torrent)
But I read through it and it is definately not usefull, not forme at this point anyway.
@nikbry
and yeah, I didn't read the full thread completely. by the time i was on page 25 i started to read more and more diagnolly. so I acdmitt I missed that part. but thank you for pointing it out to me.
still the question remains does anyone know a good book for more in depth theories on oscilloscopes.
Kind greats
Matthieu
-
@IC_toaster
I am not looking for a book to learn to use a oscilloscope but to understand the theory behind it in more depth.
sorry if i wasn't clear in that. But generally speaking books tend to be ggod for theoretics.
But also, I am not buying a book, plenty of books are available through official site in pdf. this one is too (#no torrent)
But I read through it and it is definately not usefull, not forme at this point anyway.
@nikbry
and yeah, I didn't read the full thread completely. by the time i was on page 25 i started to read more and more diagnolly. so I acdmitt I missed that part. but thank you for pointing it out to me.
still the question remains does anyone know a good book for more in depth theories on oscilloscopes.
Kind greats
Matthieu
Not sure what you mean with "in depth theories on oscilloscopes", you should maybe state what you are interested in: mastering its use, designing one, practical applications with examples? Maybe the subject is worth starting its own thread instead of hijacking this one ....
-
What is the utility of a measuring instrument which cut the signals and give wrong measurements?
The usefulness of such a tool tends to zero and it cannot be called a measuring tool. It's just a toy.
-
Respectfully, and no offense in the slightest intended to Indman - the simplest of objects: a stick or a wooden box can be extremely handy tools. So is a pencil or piece of chalk.
Might we agree - we could put a junior technician in possession of the best in portable Fluke or Techtronix instrumentation, but if they didn't know how to use the devices, the outcome of their efforts with same would be dubious.
This class of device being produced now are experiencing growing pains. I'm a proponent of helping Zoyi discover and correct tool shortcommings where possible / practical, not dwelling on how these aren't multi-thousand dollar test equipment items used by highly experienced people, or devices of medium price-point beginners would have trouble affording out of the gate.
While there are going to be shortcomings and real compromises in terms of hardware for low-end equipment, the utility and the performance of this particular product we are discussing - aimed at people without a lot of extra $$$ comes down to software maturity.
In otherwords, before we shoot them, IMHO there is an opportunity space for additional development, test and validation that remains here.
-
Respectfully, and no offense in the slightest intended to Indman - the simplest of objects: a stick or a wooden box can be extremely handy tools. So is a pencil or piece of chalk.
Might we agree - we could put a junior technician in possession of the best in portable Fluke or Techtronix instrumentation, but if they didn't know how to use the devices, the outcome of their efforts with same would be dubious.
This class of device being produced now are experiencing growing pains. I'm a proponent of helping Zoyi discover and correct tool shortcommings where possible / practical, not dwelling on how these aren't multi-thousand dollar test equipment items used by highly experienced people, or devices of medium price-point beginners would have trouble affording out of the gate.
While there are going to be shortcomings and real compromises in terms of hardware for low-end equipment, the utility and the performance of this particular product we are discussing - aimed at people without a lot of extra $$$ comes down to software maturity.
In otherwords, before we shoot them, IMHO there is an opportunity space for additional development, test and validation that remains here.
Absolutely, amen to that! And thank you for expressing it so eloquently.
It’s like how pilots are taught to "fly the plane first!"—stay in control and question your instruments at all times.
Even the best Fluke or Tektronix tools are useless if the user doesn’t know how to use them or doesn't understand its limitations.
-
@nikbry
I meant, 'mastering its use', sorry if this wasn't clearly stated by me.
But I agree, it might be a thread high-jack, and that was definately not intended as such.
@apollo11fan
well thank you! very nicely stated.
Kind greats
Matthieu
-
Small other question,
From what I read in this thread, i understand that the probes this 'toy' comes with are not really good at all. Is this correct? I did read the recommendation to get a pair of p6100 probes, so I will look into that but now for the time being I have some Uni-T P03 probes 60Mhz probes. Can I judge this as even so slightly better then the ones the ZT703 comes with or not at all? Does anyone have any experience with UT probes? I looked for some reviews on them but didn't find any, none on any of there probes really.
Kind greats
Matthieu.
-
Small other question,
From what I read in this thread, i understand that the probes this 'toy' comes with are not really good at all. Is this correct? I did read the recommendation to get a pair of p6100 probes, so I will look into that but now for the time being I have some Uni-T P03 probes 60Mhz probes. Can I judge this as even so slightly better then the ones the ZT703 comes with or not at all? Does anyone have any experience with UT probes? I looked for some reviews on them but didn't find any, none on any of there probes really.
Kind greats
Matthieu.
Look at page 31, post #756 where @IC_Toaster did some tests comparing the P6100 to a Zoyi and a Sigilent.
-
Oke I recieved it today, and was ofcourse very happy.
But after a few hours trying to do just some basic stuff i have decided. it's going back.
so now it's time for me to read back on all the other alternate proposals that were made over time
anyway (not wanting to hijack the thread again, but general though of people here that are not on the Zeeweii Dso3d12?
seems similar, to wat Aldo22 suggested in a diff thread, the DSO1C81 . in his words, it seems to be more mature.
-
But after a few hours trying to do just some basic stuff i have decided. it's going back.
What happened that you came to this decision? Previously, you convincingly and solemnly assured that this instrument was created just for you! ;)
Who then will help Zoyi detect and correct tool deficiencies?
-
Never claim to be anywhere near skilled enough to do thaat. you would be much better at that IMHO.
Kind greatz
Matthieu
-
Hi everyone!
long time lurker here. Could not help myself and bought this instrument, although I have way too many test equipment.
The bugs are really annoying, so maybe there would be interest here, to make an open source firmware for this scopemeter?
After a quick check of the PCB, here is what I know:
MCU: STM32H7B0V <- confirmed with a JTAG ID scan
ADC: can only make out "2088", maybe MXT2088 (an AD9288 clone) <- MSPS and pinout does not really make sense here, so I am probably wrong MXT2088 it is... >:(
SPI Flash: PY25Q128HA (confirmed via SPI readout)
DMM chip: DTM0660L
Two shift registers as port expanders: HC595
Analog switches: 4051
MCU readout protection is enabled, but SWD is still enabled, so finding an exploit to read back the internal flash should work. Voltage glitching of the ST bootloader should also be an option.
The firmware updates are encrypted, but it does not look like a proper encryption after a quick check.
Attached is a screenshot of the internal RAM content, showing the framebuffer :)
Edit: ADC confirmed
-
Some information on the firmware update file format (ZTK):
16 bytes header:
0 to 3: file length - 16 (header length)
4 to 7: unknown, looks like 16 bit uint (bytes 6 and 7 always 0), maybe checksum
8 to 15: always "OSC7EF91"
starting at byte 16 is the firmware
The encryption looks like taking 8 byte blocks. It is not a real block cipher as statisctical analysis reveals, that the bytes
87 D0 A9 A6 1A D6 2A 78 decrypt to 0, when they are in the position 0 to 7 or 8 to 15 respectively
Simple XOR with byte swapping did not bring any usable result
edit: my assumption above, about the block cipher is probably wrong, as the 8 bytes above almost alway appear in the exact order.
The MCU supports DES, 3DES, AES in hardware, because of the 8 byte blocks, DES and 3DES are possible candidates
-
Some information on the firmware update file format (ZTK):
16 bytes header:
0 to 3: file length - 16 (header length)
4 to 7: unknown, looks like 16 bit uint (bytes 6 and 7 always 0), maybe checksum
8 to 15: always "OSC7EF91"
starting at byte 16 is the firmware
The encryption looks like taking 8 byte blocks. It is not a real block cypher as statisctical analysis reveals, that the bytes
87 D0 A9 A6 1A D6 2A 78 are 0, when they are in the position 0 to 7 or 8 to 15 respectively
Simple XOR with byte swapping did not bring any usable result
Thank you for trying to get the ball rolling...
Hopefully, someone can help in getting the project gain momentum.
Sadly, I'm thoroughly ignorant and useless in all matters regarding firmware development. But if any "monkey" tasks should arise, I'd be more than happy to contribute my share.
-
Maybe @tv84 could take a look at the encryption of the update file :)
I have unfortunately killed my SPI programmer, so can not read the contents of the SPI flash (hopefully there is some patchable code there) until a new one arrives.
Using the original bootloader would be the easiest way to put a different firmware on this meter.
-
I still have the meter here, as AE is very much not responding ont the return issue.
This is new to me, as my earlier experience has always been good to moderate, but now not so much.
Anyway, I believe I have a chip reader lying around. maybe I can help reading the SPI (with some help)
I will look into what I have later today, and make pictures / response to see if it is of any value.
Kind greats, Matthieu
Addition:
I have an:
* AVRdude compatible device, USB AVR programmer / SPI interface. (well if I can find this one)
* AVR USBASP programmer (https://stackoverflow.com/questions/16615640/using-usbasp-programmer-for-spi-communication)
* USB ISP programmer (same thing i believe, but got it with something)
https://nl.aliexpress.com/item/1289376766.html?spm=a2g0o.productlist.main.21.656e3ccak0V4NQ&algo_pvid=94913f6c-c923-434e-91e9-8da5841ae19f&algo_exp_id=94913f6c-c923-434e-91e9-8da5841ae19f-10&pdp_npi=4%40dis%21EUR%214.39%214.39%21%21%214.56%214.56%21%402103846917315105423918075e8df0%2158746620936%21sea%21NL%21706585505%21X&curPageLogUid=EDoHT7iZXxmw&utparam-url=scene%3Asearch%7Cquery_from%3A
* Bus Pirate -> this seems to me the best available option..
and a bunch of matching (flat)cables.
so if there is something here that I can use to read the SPI with your help, let me know.
-
Does anyone have any information on Zoyi's commitment to continue to release firmware updates for the 702 and 703 models? When I made an inquiry via their website, there have been nothing but crickets since. |O
-
Does anyone have any information on Zoyi's commitment to continue to release firmware updates for the 702 and 703 models? When I made an inquiry via their website, there have been nothing but crickets since. |O
Similar to famous FNIRSI, wait for the new version of ZT-704/705 from ZOYI to appear sooner :horse:
Have you not understood the strategy of these Chinese firms - they are not interested in supporting outdated models, it is more profitable for them to produce something new and raw! :D
-
This is apparent. Sad. Wasn't the ANENG hardware the same? Maybe they've produced a new version of the firmware that's compatible?
-
For time base slower than 100 ms (it means 200ms +) triggering mode can be only set to auto.
Pity, as slow tb is useful with single mode.
-
wait for the new version of ZT-704/705 from ZOYI to appear sooner :horse:
Have you not understood the strategy of these Chinese firms - they are not interested in supporting outdated models, it is more profitable for them to produce something new and raw! :D
Really?
There has been several updates, released approximately every 2-3 months.
-
Nice, but not working corectly :D
-
Hello to all,
As mentioned before, I had decided on sending my 703 back under the free return clause.
Unfortunately AE or the seller were being difficult and did not agree. Anyway..
The end of the story is that I have received a refund for the majority and didn't need te send it back, so I agreed
I unpacked it again and started fiddling with it this evening and I bumped into an issue I bumped into before but I believe it is nothing I have not read about here.
The issue is the signal-generator menu under F1.
The menu under F4, works, I can do anything there and it works.
Under F1, I can change everything but non of the changes seem to stick/have an effect.
That includes the turning off of the signal generator. I can not seem to turn it off.
In F1 I put it on "off", but when Exit it is still on, does anyone else have this issue with FW 1.4.2?
and or / Is there any different way to turn the signal gen off?
(I did read the manual, to see it there in a not-so-intuitive manner, but it seems like I did it all as should)
So currrently I am planning to flash the firmware but am not sure which version to choose for.
If it not an issue that is common I can try to reflash 1.4.2. but I can also for an older one. 1.3.2 / 1.3.8 / 1.3.9 .The latter one is a version I haven't read much on besides it being slow. and I read that 1.3.8 allready has the bad auto range. but I also believe that most people here still use. 1.3.8, but I could be wrong.
1 have read positive comment on both 1.3.8 and 1.3.2. but am not sure if there is any consensus on which would be the least bad of these two.
The only thing I know is that @nikbry seems to stick to 1.32. but it also seems like most still use 1.38.
At least untill they create the superb FW version.. if it will ever comes (sure hope so).
Anyway, thoughts are appreciated.
Additionally is there still links to either version 1.32 and 1.38
-
ZT-703S, FW1.39 (last). The error with determining the minimum and maximum values has not been fixed.
A little experiment. I generate the input pulse manually from the power supply. The voltmeter BM789 is in the Crest mode (we will check this mode at the same time).
[attach=1] [attach=2] [attach=3]
-
The issue is the signal-generator menu under F1.
The menu under F4, works, I can do anything there and it works.
Under F1, I can change everything but non of the changes seem to stick/have an effect.
I found this, it seems a firmware bug. Press “Default" and confirm, it will close the signal-generator output.
-
ZT-703S, FW1.39 (last). The error with determining the minimum and maximum values has not been fixed.
A little experiment. I generate the input pulse manually from the power supply. The voltmeter BM789 is in the Crest mode (we will check this mode at the same time).
(Attachment Link) (Attachment Link) (Attachment Link)
Latest FW is 1.42
-
Latest FW is 1.42
Oh! You are right! I'll download, install and double-check.
-
Additionally is there still links to either version 1.32 and 1.38
I have searched throught the thread, but didn't find a download link for either of them, I believe I prefer 1.32 but wpuld love to have them both.
Does anyone have the fila available (preferrably with a checksum to make sure the file is oke after the download. )
Kind greats
Matthieu
-
You were looking poorly or in the wrong place. Here is the link on page 20 of this topic
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5585305/#msg5585305 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5585305/#msg5585305)
-
Latest FW is 1.42
I have installed the latest version of the software.
[attach=1]
But I wouldn't say that anything has changed much.
[attach=2] [attach=3]
-
It only doesn't work with Single trigger?
Does it measure well in Normal and Auto mode?
-
Finally I had time to investigate further into this scopemeter.
First of all, the SPI flash is only used for data storage (mass storage USB mode), nothing of value is on it. They did not even bother to connect it via quad-SPI...
My assumption about the ADC being an MXT2088 (AD9288 clone) seems to be correct. All the signals measured are located there, where they should be according to the datasheet.
So this scopemeter has only 100MSPS in normal mode (verified the 100MHz clock on the ENC pins with a real scope :) ), the high speed mode is overclocking the ADC to 140MHz (MCU fmax/2)
I was wondering the whole time, how they got the advertised amount of data into an MCU with an fmax of 280MHz without using an FPGA. Well they did not... It is probably even sampling the two channels alternating, but did not bother to check this, as the 100MSPS is already a dealbreaker for me (bought it for measuring high-ish speed RS485 comms waveforms in the field)
Just another datapoint: when running at 100MSPS, the ADC is running 100 times a second with 100MHz bursts, so max 100 wafeforms/s, if the sampling is alternating, then 50 wfrms/s.
If there is interest, we could still make an open source firmware from scratch for this meter, but nobody knows how long this meter will be on the market. As already mentioned here, chinese manufacturers are quick to abandon products...
Since there are no magic tricks used to get 280MSPS / channel of data into the MCU here, I dont really care about the stock firmware anymore, and the PCB is simple enough to reverse...
Triggering is also only in software. With the low waveform/s count, I could set up the scopemeter with an AWG in a way it never triggered. I guess I got, what I paid for.
Edit: high speed mode clock measured
-
Finally I had time to investigate further into this scopemeter.
First of all, the SPI flash is only used for data storage (mass storage USB mode), nothing of value is on it. They did not even bother to connect it via quad-SPI...
My assumption about the ADC being an MXT2088 (AD9288 clone) seems to be correct. All the signals measured are located there, where they should be according to the datasheet.
So this scopemeter has only 100MSPS in normal mode (verified the 100MHz clock on the ENC pins with a real scope :) ), the high speed mode is overclocking the ADC to 140MHz (MCU fmax/2)
This device is made according to the ARM+ADC scheme, whereas most other manufacturers use the FPGA+ARM+ADC scheme. Therefore, this device does not work well. And the new firmware won't do anything.
-
This device is made according to the ARM+ADC scheme, whereas most other manufacturers use the FPGA+ARM+ADC scheme. Therefore, this device does not work well. And the new firmware won't do anything.
Exactly.
It could be made better, but it will never be a proper oscilloscope.
The only question is, it worth the time, to make a proper firmware for this device, or just wait for a scopemeter with at least an FPGA in it :-//
-
It could be made better, but it will never be a proper oscilloscope.
What compact proper oscilloscope would you recommend?
-
I just picked up a Zeeweii dso3d12 scope/meter. I'm liking it so far but I'm afraid I'm too new to scopes to put it through it's paces. Maybe something to look at?
Edit: From the specs it appears the Zeeweii is a better scope. The Zoyi is the better DMM. Again, from the specs. I've not tested the two in practice yet...
-
Edit: From the specs it appears the Zeeweii is a better scope. The Zoyi is the better DMM. Again, from the specs. I've not tested the two in practice yet...
Exactly!
In my opinion, even the cheapest Zeeweii oscilloscope is better than this Zoyi, from what I've read.
https://www.aliexpress.com/item/1005007394192248.html (https://www.aliexpress.com/item/1005007394192248.html)
But Zotek makes very good cheap DMMs. I love my ZT-225.
-
This device is made according to the ARM+ADC scheme, whereas most other manufacturers use the FPGA+ARM+ADC scheme. Therefore, this device does not work well. And the new firmware won't do anything.
Exactly.
It could be made better, but it will never be a proper oscilloscope.
The only question is, it worth the time, to make a proper firmware for this device, or just wait for a scopemeter with at least an FPGA in it :-//
Making a proper firmware sounds interesting, but if there are not expectations of getting a good working, it doesn't worth it. I don't have enought knowledge to help you in it.
-
It is a real shame, how they made this scopemeter. I really like the size and the UI concept, but it is unusable for my purpose.
If they would at least made a simple analog trigger circuit, it would only have costed them a few cents and I would be happy to pay more for a functioning trigger. There is enough room left on the PCB, and the MCU also hase enough unused DACs to set the trigger level. Even with an analog trigger, this would be a usable scope with some firmware tricks, altough even that would not give us a proper single mode trigger.
I have ordered myself an Owon HDS scope, because I need a proper single mode trigger. The saying is true: buy cheap, buy twice...
Edit: found it, a real analog trigger, at least for channel 1. I think I have to reverse the analog frontend to see, what they have built.
If the TFT supports auto-refresh, then a working single mode trigger is possible (at least on channel 1)
-
Update:
pinout of the MCU almost completely mapped (only 6 pins left) :)
I have to decode the communication between MCU and DMM chip.
Both channels have a basic analog trigger.
-
Will the complete scheme with the entrance part be redrawn?
-
It will have to be at least partly reversed. I think there is no need the redraw the DMM schematic, as it simply works and only communicates with the main MCU via UART
Maybe someone in the thread will be kind enough to reverse the analog frontend of the scope part, as I am still looking for the remaining MCU connections and decoding the communication to the DMM chip.
Also my backlight driver chip died (my mistake), so will need to look for a replacemant chip |O
-
A summary about the Zoyi ZT-703S:
- dual channel 100MSPS ADC (overclocked to 140MSPS in high speed mode), both channels sampled in parallel
- analog comparators as trigger for both channels (trigger level adjustement with DAC1_OUT1)
- external flash connected to SPI4, only used for screenshot storage
- DMM chip connected via UART5, 9600-8-N-1, 18 byte packets to the MCU
- LCD with 20MHz pixel clock, RGB565, DE mode, no HSYNC or VSYNC used. No SPI connection.
- Signal genarator uses the 1MSPS 12bit DAC, at 50kHz output only 20 DAC points/cycle
All the pins of the MCU and the HC595 found :)
Goals for an open source firmware:
DMM:
- recreate original functionality <- communication decoded
- switchable analog scale
- add CSV logging
- add graph history
- add CDC to the USB mode for remote control of the DMM
Scope:
- no overclocking
- proper triggering
- user control of sampling speed, memory depth
- equivalent sampling for repeating signals
- voltage calibration
Signal generator (do we really need this...):
- user stored waveforms in addition to the standard ones
There is one big IF for a properly working firmware, that is auto-refresh of the LCD. The LCD controller uses DMA and the main RAM for framebuffer, but we need these resources while doing high speed sampling. Here is where the missing FPGA would help...
I will use this post as a main place for updates.
-
Goals for an open source firmware:
DMM:
- recreate original functionality
- no analog scale
Even though the analog scale does work and is slow to update, I think it is needed and gives a vintage look to the DMM interface. The only nuance that I would change is to slightly increase the size of the numbers on the display, if of course this is possible. I bought the ZT-703 mainly because I really liked the DMM interface and how it worked.
-
A summary about the Zoyi ZT-703S:
- dual channel 100MSPS ADC (overclocked to 140MSPS in high speed mode), both channels sampled in parallel
- analog comparators as trigger for both channels (trigger level adjustement with DAC1_OUT1)
- external flash connected to SPI4, only used for screenshot storage
- DMM chip connected via UART5, 9600-8-N-1, 18 byte packets to the MCU
- LCD with 20MHz pixel clock, RGB565, DE mode, no HSYNC or VSYNC used. No SPI connection.
- Signal genarator uses the 1MSPS 12bit DAC, at 50kHz output only 20 DAC points/cycle
Goals for an open source firmware:
DMM:
- recreate original functionality
- no analog scale
- add CSV logging
- add graph history
Scope:
- no overclocking
- proper triggering
- user control of sampling speed, memory depth
- equivalent sampling for repeating signals
Signal generator (do we really need this...):
- user stored waveforms in addition to the standard ones
There is one big IF for a properly working firmware, that is auto-refresh of the LCD. The LCD controller uses DMA and the main RAM for framebuffer, but we need these resources while doing high speed sampling. Here is where the missing FPGA would help...
I would add, for the scope part, a right voltage measurement. I think my device measures around 0,2 V less than the real value.
-
Even though the analog scale does work and is slow to update, I think it is needed and gives a vintage look to the DMM interface. The only nuance that I would change is to slightly increase the size of the numbers on the display, if of course this is possible. I bought the ZT-703 mainly because I really liked the DMM interface and how it worked.
I would add, for the scope part, a right voltage measurement. I think my device measures around 0,2 V less than the real value.
Added to the list
-
You were looking poorly or in the wrong place. Here is the link on page 20 of this topic
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5585305/#msg5585305 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5585305/#msg5585305)
guess I was looking poorly then, I searched for the specific FW numbers like 1.32 and 1.3.2 and firmware and FW but this was not in the post itsef so I looked over it.
but thank you for pointing me to it and @kamil004 thank you for putting that here !
@ajar171
thank you for all the effort you are putting in :D
-
I found this, it seems a firmware bug. Press “Default" and confirm, it will close the signal-generator output.
@ Suntide, i am ot sure what you mean with the "default", and in which menu? F1 or F4 (I didn't find them in both and basically triedd out all the buttons.
ps: I am on FW 1.3.2 now.
kind greats
Matthieu
-
A summary about the Zoyi ZT-703S:
- dual channel 100MSPS ADC (overclocked to 140MSPS in high speed mode), both channels sampled in parallel
- analog comparators as trigger for both channels (trigger level adjustement with DAC1_OUT1)
- external flash connected to SPI4, only used for screenshot storage
- DMM chip connected via UART5, 9600-8-N-1, 18 byte packets to the MCU
- LCD with 20MHz pixel clock, RGB565, DE mode, no HSYNC or VSYNC used. No SPI connection.
- Signal genarator uses the 1MSPS 12bit DAC, at 50kHz output only 20 DAC points/cycle
All the pins of the MCU and the HC595 found :)
Goals for an open source firmware:
DMM:
- recreate original functionality <- communication decoded
- switchable analog scale
- add CSV logging
- add graph history
Scope:
- no overclocking
- proper triggering
- user control of sampling speed, memory depth
- equivalent sampling for repeating signals
- voltage calibration
Signal generator (do we really need this...):
- user stored waveforms in addition to the standard ones
There is one big IF for a properly working firmware, that is auto-refresh of the LCD. The LCD controller uses DMA and the main RAM for framebuffer, but we need these resources while doing high speed sampling. Here is where the missing FPGA would help...
I will use this post as a main place for updates.
It will be extremely great if you manage to create an open source firmware! You are cracks!
Also:
Multimeter mode:
-Remove that fucking needle XD
-
It would really help a lot, if someone would reverse the analog frontend of the scope part!
Only the part below the shielding cans up to the inputs of the ADC have to be redrawn, I have already found everything connected to the two HC595s, and the digital signals of the ADC are also done.
-
Latest FW is 1.42
I have installed the latest version of the software.
(Attachment Link)
But I wouldn't say that anything has changed much.
(Attachment Link) (Attachment Link)
It seems on the attached picture that the graph is showing the correct value: 2 divisons and 1 point on a 5V division setting is roughly 12V. So "only" the indicated min and max value seems to be wrong.
As far as I remember similar curve vs. displayed value issue was already mentioned earlier in this forum.
-
Latest FW is 1.42
I have installed the latest version of the software.
(Attachment Link)
But I wouldn't say that anything has changed much.
(Attachment Link) (Attachment Link)
It seems on the attached picture that the graph is showing the correct value: 2 divisons and 1 point on a 5V division setting is roughly 12V. So "only" the indicated min and max value seems to be wrong.
As far as I remember similar curve vs. displayed value issue was already mentioned earlier in this forum.
Yes, that's exactly what I was paying attention to - the discrepancy between the values of the displayed curve. And they still haven't fixed it.
-
Hello Guys, sorry to disrupt your thread.
Would you recommend this one ( Zoyi ZT 703S ) or similarly priced FNIRSI 2C53T - 50Mhz, FPGA ? As a beginner I am currently in a process of buying my first multimeter with oscilloscope capability/oscilloscope with DMM capability. I have just ordered Zoyi, but when it arrives I have 15 days to return it.
Please, does Zoyi have a big disadvantage because of the FPGA absence?
In datasheet I can see that FNIRSI has less accurate DMM. But otherwise, I am not so experienced so I have difficulty to decide which one to buy.
Btw your effort to create OSS FW for Zoyi is great! If I had more experiences, I would definitely participate and help you with this.
Thanks a lot for your help!
-
The chinese low budget test equipment manufacturers are quick to abandod their products, but Fnirsi is extremely fast in that regard. Zoyi already released at least 7 updates (what I know of), which can not be told about the Fnirsi products I own...
The 2C35T has the same oscilloscope (and signal generator) specs as the 703, so probably the same hardware, I can not imagine, that there is an FPGA in that meter. The UI is different, so you have to choose, what you like more, there are enough videos on youtube about both meters. IMO they are the same apart from the DMM and UI part.
I will for sure make the OSS UI similar to the Zoyi one, since I like it :)
-
@LucSVK
Hello Guys, sorry to disrupt your thread.
Would you recommend this one ( Zoyi ZT 703S ) or similarly priced FNIRSI 2C53T - 50Mhz, FPGA ? As a beginner I am currently in a process of buying my first multimeter with oscilloscope capability/oscilloscope with DMM capability. I have just ordered Zoyi, but when it arrives I have 15 days to return it.
Please, does Zoyi have a big disadvantage because of the FPGA absence?
In datasheet I can see that FNIRSI has less accurate DMM. But otherwise, I am not so experienced so I have difficulty to decide which one to buy.
Btw your effort to create OSS FW for Zoyi is great! If I had more experiences, I would definitely participate and help you with this.
Thanks a lot for your help!
Hey, I Have (very) recently been in your shoes!
Although I myself really dislike it when someone goes outside the offered choise option I would really suggest an
third option. the Zeeweeii DSO3D12.
I have bought the Zoyt/Aneng 703 but was very disappointed in the machine as most of the people here.
I am a beginner, just like you and found it is, besides the known bugs, really not inuitive.
Most of the issues are software based, hence the attempts to make an new FW version, which I personally are really looking forward too,
Anyway, untill this project is an reality, I personally prefer the zeeweeii.
have a look at this thread:
https://www.eevblog.com/forum/testgear/another-dsodmm-zeeweii-dso3d12-claimed-120mhz250msps/ (https://www.eevblog.com/forum/testgear/another-dsodmm-zeeweii-dso3d12-claimed-120mhz250msps/)
additionally, the 15 days return option, sounds very familiar, adn let me warn you. I tried to make use of this option and the seller did not accept..
I only got a partial refund, but didn't need to ship the 703 back. And I assume this is an common issue with the seller.
Most likely as they know a lot of people are dissatisfied and want to return it, so they stopped accepting.
So if they haven't shipped out yet, cancel the order now, and take your time to re-consider. between the 3 models.
ps: i know the zeeweeii doesn't look very nice compared the other two, but it works quite well.
I am not knowledged about the FNIRSI, but it never really drew my attention, but never really heard good reviews on it. did see that people are also working on a new FW for it predecessor so, to me that doesn't sound well.
Anyway, good luck with you choice.
Matthieu
-
Exactly.
The Zoyi and the Fnirsi are IMO the same hardware. They are both software only oscilloscopes, and the lack of a proper hardware can not be compensated in software.
The OSS FW idea for the Zoyi is a just fun project for me, hopefully there will be some collaboration too, but don't expect functionality (and speed) like in scope with proper hardware. I just want to get the most from the hardware I bought and have some fun :)
There are affordable scopes from Siglent or Rigol or a used scope from a more prestigous brand, that are not riddled with bugs in basic stuff like triggering. If you are a beginner, do yourself a favor, and buy a proper (even used) scope from a know good brand, so you will not be confused with buggy firmware.
Edit: Just checked, the 1054Z (hackabale to 100MHz) costs 343€ with 3 years of warranty, and free delivery in the EU. 4 channels, 1Gsps.
-
It would really help a lot, if someone would reverse the analog frontend of the scope part!
Only the part below the shielding cans up to the inputs of the ADC have to be redrawn, I have already found everything connected to the two HC595s, and the digital signals of the ADC are also done.
I wish I had the knoledge to help in something
-
Hi Ajar171, no the FNIRSI really has the FPGA.
Vendor promotes this on their website.
https://www.fnirsi.com/products/2c53t (https://www.fnirsi.com/products/2c53t)
✦ Excellent Design: The Oscilloscope adopts FPGA + MCU + ADC hardware architecture, built-in high-voltage protection module, adopts 2.8 inch LCD display, built-in 3000mAh Li-ion battery, standby time up to 6H, Type-C interface supports 5V/1A charging.
AFAIK it has the same HW inside as Fnirsi 2C53P in the package of the old 2c23T
For example FPGA should be GOWIN Semiconductor GW1N-UV2
It has nothing in common with Zoyi. It should be able to do 50Mhz on both channels simultaneously.
Thanks
---
Hey spikey1973
I will have a look at Zeeweeii DSO3D12. I briefly checked information on their site and it's 120Mhz 1CH, 60Mhz 2CH. So is it similar architecture like Zoyi? ( SW based?)
About the free return. Unfortunately it's on the way already. I bought it 2 -3 days ago from the Official Zoyi store on Aliexpress.
Aliexpress says:
You have 15 days from receiving the item(s) to return your order without explanation as long as:
- All items are in perfect condition and in the original packaging.
- Any safety seals are not damaged and all labels are retained.
Open a dispute within 15 days of receiving the order
Print a Free Return label
Go to the designated return point
Wait for your refund
https://sale.aliexpress.com/__pc/1BB5HiMxKx.htm (https://sale.aliexpress.com/__pc/1BB5HiMxKx.htm)
Did you open the dispute when you tried to return yours?
How much they refunded you?
So we will see.
FNIRSI 2C53T was released quite recently, maybe hasn't spred between people yet. But maybe it just isn't a good device
so people don't want it. Who knows.
Thanks
-
Hi Ajar171, no the FNIRSI really has the FPGA.
Vendor promotes this on their website.
https://www.fnirsi.com/products/2c53t (https://www.fnirsi.com/products/2c53t)
✦ Excellent Design: The Oscilloscope adopts FPGA + MCU + ADC hardware architecture, built-in high-voltage protection module, adopts 2.8 inch LCD display, built-in 3000mAh Li-ion battery, standby time up to 6H, Type-C interface supports 5V/1A charging.
AFAIK it has the same HW inside as Fnirsi 2C53P in the package of the old 2c23T
For example FPGA should be GOWIN Semiconductor GW1N-UV2
It has nothing in common with Zoyi. It should be able to do 50Mhz on both channels simultaneously.
Thanks
Storage Depth 1Kpts
I think this in too few memory.
About the Zeeweii:
http://www.zeeweii.com/productinfo/dso3d12.html (http://www.zeeweii.com/productinfo/dso3d12.html)
It has bigger screen and more storage memory.
-
Zeeweii looks like some kind of homemade product..
-
Zeeweii looks like some kind of homemade product..
Yes, I agree with you, especially the very jagged font, as if it was made by a not quite sober artist. It certainly discourages the user.
But as an oscilloscope it is much more convenient to use despite its somewhat toy-like appearance. I like that the measurement results are at the bottom of the screen and do not overlap the main waveform. It is a big plus that there is an additional buttons for convenient control of operating modes. ;)
-
Zeeweii looks like some kind of homemade product..
When I have to choose between a measuring instrument that looks stylish and one that works well and is easy to use, I don't have to think twice.
Of course, everyone has to decide for themselves.
-
When I have to choose between a measuring instrument that looks stylish and one that works well and is easy to use, I don't have to think twice.
Ideally, if these conditions, which you named, coincide in one product, but this happiness is now very rare or costs a lot of money! ;)
-
A summary about the Zoyi ZT-703S:
- dual channel 100MSPS ADC (overclocked to 140MSPS in high speed mode), both channels sampled in parallel
- analog comparators as trigger for both channels (trigger level adjustement with DAC1_OUT1)
- external flash connected to SPI4, only used for screenshot storage
- DMM chip connected via UART5, 9600-8-N-1, 18 byte packets to the MCU
- LCD with 20MHz pixel clock, RGB565, DE mode, no HSYNC or VSYNC used. No SPI connection.
- Signal genarator uses the 1MSPS 12bit DAC, at 50kHz output only 20 DAC points/cycle
All the pins of the MCU and the HC595 found :)
Goals for an open source firmware:
DMM:
- recreate original functionality <- communication decoded
- switchable analog scale
- add CSV logging
- add graph history
Scope:
- no overclocking
- proper triggering
- user control of sampling speed, memory depth
- equivalent sampling for repeating signals
- voltage calibration
Signal generator (do we really need this...):
- user stored waveforms in addition to the standard ones
There is one big IF for a properly working firmware, that is auto-refresh of the LCD. The LCD controller uses DMA and the main RAM for framebuffer, but we need these resources while doing high speed sampling. Here is where the missing FPGA would help...
I will use this post as a main place for updates.
This is an amazing project!
I’d be happy to help with C/C++ coding where needed, even though I don’t have experience in firmware development.
The technical details and goals you’ve outlined are super inspiring.
Let me know how I can contribute!
-
AFAIK it has the same HW inside as Fnirsi 2C53P in the package of the old 2c23T
For example FPGA should be GOWIN Semiconductor GW1N-UV2
It has nothing in common with Zoyi. It should be able to do 50Mhz on both channels simultaneously.
You are totally right, I have missed that part.
-
This is an amazing project!
I’d be happy to help with C/C++ coding where needed, even though I don’t have experience in firmware development.
The technical details and goals you’ve outlined are super inspiring.
Let me know how I can contribute!
Thanks for your kind offer!
I am still waiting for my new backlight driver to arrive. After replacing the dead chip, I can start getting the display and DMM part running.
-
@ajar171
I send you a few pm's on help with the reverse of the analog frontend of the scope part but there was no response.
didn't you read or are you not interested?
Kind greats
Matthieu
-
@ajar171
I send you a few pm's on help with the reverse of the analog frontend of the scope part but there was no response.
didn't you read or are you not interested?
Kind greats
Matthieu
You have a Zeeweii DSO3D12. Don't you?
There are some complaints about this Zoyi device, and maybe the most important one is the fact that this device doesn't have a FPGA.
I think if it is not more convenient to develop a firmware for the Zeeweii instead of for the Zoyi.
@ajar171 what do you think about it?
-
@spikey1973: sorry, I am used to get a popup window, when I get a message, so I did miss yours. Reply sent :)
@IC_Toaster: yes, I know this hardware has limitations. It is still good enough of for the purpose I bought it for (but not with the official firmware, with a broken trigger), but there have to be compomises. The priority for Zoyi was, to keep the display showing "something". I rather have a properly shown waveform, and simply switch the screen off, while waiting for a trigger (in single mode), than to show something on the screnn, that is not the reality.
Don't get me wrong, this meter still lacks and FPGA, and to be honest, I would not recommend anyone to buy it. I am still not 100% sure, that an inofficial firmware can save the scope part of this meter.
The DMM part is IMO pretty good with 25000 counts and 3 updates/s. I have paid more money for less, for a DMM from an other brand.
Reversing a frontend with 3 opamps, a relay and an analog switch, and 2 more opamps for the trigger is IMO a fun thing, even for a beginner. I am more then happy to help with this (as my dayjob allows to), if anyone needs it.
Update:
If anyone has a dead backlight driver chip (JAXA marking), it can be replaced with an AP5724WG, but the original feedback resistor (10 Ohm, 0603) has to be replaced with a 5 Ohm one to get the same brightness.
-
@spikey1973: sorry, I am used to get a popup window, when I get a message, so I did miss yours. Reply sent :)
@IC_Toaster: yes, I know this hardware has limitations. It is still good enough of for the purpose I bought it for (but not with the official firmware, with a broken trigger), but there have to be compomises. The priority for Zoyi was, to keep the display showing "something". I rather have a properly shown waveform, and simply switch the screen off, while waiting for a trigger (in single mode), than to show something on the screnn, that is not the reality.
Don't get me wrong, this meter still lacks and FPGA, and to be honest, I would not recommend anyone to buy it. I am still not 100% sure, that an inofficial firmware can save the scope part of this meter.
The DMM part is IMO pretty good with 25000 counts and 3 updates/s. I have paid more money for less, for a DMM from an other brand.
Reversing a frontend with 3 opamps, a relay and an analog switch, and 2 more opamps for the trigger is IMO a fun thing, even for a beginner. I am more then happy to help with this (as my dayjob allows to), if anyone needs it.
Update:
If anyone has a dead backlight driver chip (JAXA marking), it can be replaced with an AP5724WG, but the original feedback resistor (10 Ohm, 0603) has to be replaced with a 5 Ohm one to get the same brightness.
I think I wouldn't abre to reverse a frontend like this. Anyway I find interesting improving the device. But I just think that maybe could be more useful investing the time and effort on a device with better hardware.
If I can help you, tell me. But I feel I don't have much knowledge.
-
@spikey1973: sorry, I am used to get a popup window, when I get a message, so I did miss yours. Reply sent :)
@IC_Toaster: yes, I know this hardware has limitations. It is still good enough of for the purpose I bought it for (but not with the official firmware, with a broken trigger), but there have to be compomises. The priority for Zoyi was, to keep the display showing "something". I rather have a properly shown waveform, and simply switch the screen off, while waiting for a trigger (in single mode), than to show something on the screnn, that is not the reality.
Don't get me wrong, this meter still lacks and FPGA, and to be honest, I would not recommend anyone to buy it. I am still not 100% sure, that an inofficial firmware can save the scope part of this meter.
The DMM part is IMO pretty good with 25000 counts and 3 updates/s. I have paid more money for less, for a DMM from an other brand.
Reversing a frontend with 3 opamps, a relay and an analog switch, and 2 more opamps for the trigger is IMO a fun thing, even for a beginner. I am more then happy to help with this (as my dayjob allows to), if anyone needs it.
Update:
If anyone has a dead backlight driver chip (JAXA marking), it can be replaced with an AP5724WG, but the original feedback resistor (10 Ohm, 0603) has to be replaced with a 5 Ohm one to get the same brightness.
I think I wouldn't abre to reverse a frontend like this. Anyway I find interesting improving the device. But I just think that maybe could be more useful investing the time and effort on a device with better hardware.
If I can help you, tell me. But I feel I don't have much knowledge.
Most of us have humble devices... Yes you can get a much better hardware paying 300-400 €... of course! If you start focusing on a better device, finally you'll reach a way better hardware... but nobody owns, only the most freakie ones
But for a common person, getting a 60 € perfectly functionable osciloscope with a stable and functional firmware, would be great.. for common electronics, motherboards, VRM phases, BIOS, Arduino and that staff, this zoyi (aneng, etc..) is enough. (REPROMOD uses it)
I would really appreciate getting a better firmware than stock
-
@spikey1973: sorry, I am used to get a popup window, when I get a message, so I did miss yours. Reply sent :)
@IC_Toaster: yes, I know this hardware has limitations. It is still good enough of for the purpose I bought it for (but not with the official firmware, with a broken trigger), but there have to be compomises. The priority for Zoyi was, to keep the display showing "something". I rather have a properly shown waveform, and simply switch the screen off, while waiting for a trigger (in single mode), than to show something on the screnn, that is not the reality.
Don't get me wrong, this meter still lacks and FPGA, and to be honest, I would not recommend anyone to buy it. I am still not 100% sure, that an inofficial firmware can save the scope part of this meter.
The DMM part is IMO pretty good with 25000 counts and 3 updates/s. I have paid more money for less, for a DMM from an other brand.
Reversing a frontend with 3 opamps, a relay and an analog switch, and 2 more opamps for the trigger is IMO a fun thing, even for a beginner. I am more then happy to help with this (as my dayjob allows to), if anyone needs it.
Update:
If anyone has a dead backlight driver chip (JAXA marking), it can be replaced with an AP5724WG, but the original feedback resistor (10 Ohm, 0603) has to be replaced with a 5 Ohm one to get the same brightness.
I think I wouldn't abre to reverse a frontend like this. Anyway I find interesting improving the device. But I just think that maybe could be more useful investing the time and effort on a device with better hardware.
If I can help you, tell me. But I feel I don't have much knowledge.
Most of us have humble devices... Yes you can get a much better hardware paying 300-400 €... of course! If you start focusing on a better device, finally you'll reach a way better hardware... but nobody owns, only the most freakie ones
But for a common person, getting a 60 € perfectly functionable osciloscope with a stable and functional firmware, would be great.. for common electronics, motherboards, VRM phases, BIOS, Arduino and that staff, this zoyi (aneng, etc..) is enough. (REPROMOD uses it)
I would really appreciate getting a better firmware than stock
I know that it is possible to get a much better hardware paying 300-400€. Just I mean if for a little more, another device as the Zeeweii DSO3D12 has better hardware, maybe is better to try to improve that device instead of the Zoyi one.
Is it possible to get a perfectly functionable oscilloscope from this Zoyi? As you say, it would be great. I already have the Zoyi, so if I can help in some way just tell me.
I didn't know who repromod was. I see they have interesting videos.
-
Cannot help with any new firmware, but two EEVblog members have
made alternative firmware which may be used as a starting point:
- pcprogrammer (+others), Fnirsi 1013D/1014D:
https://github.com/pecostm32/FNIRSI_1013D_Firmware (https://github.com/pecostm32/FNIRSI_1013D_Firmware)
- ataradov, Fnirsi 5012H:
https://github.com/ataradov/open-5012h (https://github.com/ataradov/open-5012h)
https://www.eevblog.com/forum/projects/reverse-engineering-fnirsi-5012h/ (https://www.eevblog.com/forum/projects/reverse-engineering-fnirsi-5012h/)
pcprogrammer has also reverse engineered the Hantek DSO2000
and done some work on the FPGA used in the 1013D/1014D:
https://github.com/pecostm32/Hantek_DSO2000 (https://github.com/pecostm32/Hantek_DSO2000)
https://github.com/pecostm32/Anlogic_AL3-10_Analyzing (https://github.com/pecostm32/Anlogic_AL3-10_Analyzing)
-
any of those works with 703s?
-
No. I guess you first have to reverse engineer the hardware
and then adopt/rewrite the code to work with the ZT-703S.
-
No. I guess you first have to reverse engineer the hardware
and then adopt/rewrite the code to work with the ZT-703S.
Is it possible to get the source code to rewrite it?
-
Hello guys,
sorry for stupid questions. I've just went through this whole topic. Damn this device has a lot of problems.
But to be 100% sure.. Can this device measure signals close to 50 Mhz in high speed mode on both channels in the same time?? Has anybody tried this?
Thanks a lot
L.
-
Hello guys,
sorry for stupid questions. I've just went through this whole topic. Damn this device has a lot of problems.
But to be 100%.. Can this device measure signals close to 50 Mhz in high speed mode on both channels in the same time?? Has anybody tried this?
Thanks a lot
L.
5Vpp wave with BNC-BNC connection, with a Chinese 50Ohm termination from the scope.
All in highspeed mode.
For the two-channel images, both are sine for one.
For the remaining three, the yellow is the square signal. The blue is sine.
-
This is apparent. Sad. Wasn't the ANENG hardware the same? Maybe they've produced a new version of the firmware that's compatible?
I believe they only produce labels.
-
A summary about the Zoyi ZT-703S:
- dual channel 100MSPS ADC (overclocked to 140MSPS in high speed mode), both channels sampled in parallel
- analog comparators as trigger for both channels (trigger level adjustement with DAC1_OUT1)
- external flash connected to SPI4, only used for screenshot storage
- DMM chip connected via UART5, 9600-8-N-1, 18 byte packets to the MCU
- LCD with 20MHz pixel clock, RGB565, DE mode, no HSYNC or VSYNC used. No SPI connection.
- Signal genarator uses the 1MSPS 12bit DAC, at 50kHz output only 20 DAC points/cycle
All the pins of the MCU and the HC595 found :)
Goals for an open source firmware:
DMM:
- recreate original functionality <- communication decoded
- switchable analog scale
- add CSV logging
- add graph history
- add CDC to the USB mode for remote control of the DMM
Scope:
- no overclocking
- proper triggering
- user control of sampling speed, memory depth
- equivalent sampling for repeating signals
- voltage calibration
Signal generator (do we really need this...):
- user stored waveforms in addition to the standard ones
There is one big IF for a properly working firmware, that is auto-refresh of the LCD. The LCD controller uses DMA and the main RAM for framebuffer, but we need these resources while doing high speed sampling. Here is where the missing FPGA would help...
I will use this post as a main place for updates.
Also, in DMM a "zeroing" would be great. When I measure low resistance, I need to substract the cable resistance from the result every time.
I wonder if the scope could save data points to a file and not just pictures, so on PC it could be better analyzed. Or real-time analysis with a logic analyzer on PC.
-
This is an amazing project!
I’d be happy to help with C/C++ coding where needed, even though I don’t have experience in firmware development.
The technical details and goals you’ve outlined are super inspiring.
Let me know how I can contribute!
Thanks for your kind offer!
I am still waiting for my new backlight driver to arrive. After replacing the dead chip, I can start getting the display and DMM part running.
I'm an IT engineering student with no experience in such things, but if you release the project to GitHub I would be happy to help. At least try to help. :)
-
Also, in DMM a "zeroing" would be great. When I measure low resistance, I need to substract the cable resistance from the result every time.
This is already included in the functionality of the device and is called the “REL” button - read the documentation for the devices more carefully!
-
Now at zotektools.com laters firmware is 139.
-
Now at zotektools.com laters firmware is 139.
I see version 1.4.2 available for download.
-
Weird. Here it shoes 139
https://zotektools.com/firmware-update-703/
-
Weird. Here it shoes 139
https://zotektools.com/firmware-update-703/
Try here: https://zotektools.com/products/triple-in-one-instrument-combining-oscilloscope-multimeter-and-signal-source/
-
What newest version has no or few bugs?
-
What newest version has no or few bugs?
They all have bugs.
I think the latest (1.42) works best, but some may disagree.
-
It's strange. The company's website indicates 1.39 is the current revision. :-//
Are they just not bothering to post updated download links? |O
I hope they are working on bug fixes. :bullshit:
-
It's strange. The company's website indicates 1.39 is the current revision. :-//
Are they just not bothering to post updated download links? |O
I hope they are working on bug fixes. :bullshit:
https://zotektools.com/products/triple-in-one-instrument-combining-oscilloscope-multimeter-and-signal-source/
The "firmware download" link is directing to V1.42
-
Is it possible to compile the issues we encountered in version 1.4.2? Perhaps it could be possible to forward them collectively to ZOYI. From what I understand, they are interested in addressing the issues, but they might not be aware of their existence.
-
Is it possible to compile the issues we encountered in version 1.4.2? Perhaps it could be possible to forward them collectively to ZOYI. From what I understand, they are interested in addressing the issues, but they might not be aware of their existence.
They did not even answer to the Chinese seller who I bought this device from. But if you can contact them, this is reasonable to send them a list of bugs.
Here's one from me. In V142, when you have some calculations selected, make a screenshot:
[attach=1]
Now turn off the calculations and make another screenshot:
[attach=2]
You see a black rectangle where the calculations used to be. This will happen until you turn off and on the device.
-
Storage Depth 1Kpts
I think this in too few memory.
About the Zeeweii:
http://www.zeeweii.com/productinfo/dso3d12.html (http://www.zeeweii.com/productinfo/dso3d12.html)
It has bigger screen and more storage memory.
What storage depth does Zoyi ZT703S actually have?
And Zeeweii DSO3d12?
Edit: https://zotektools.com/products/triple-in-one-instrument-combining-oscilloscope-multimeter-and-signal-source/ (https://zotektools.com/products/triple-in-one-instrument-combining-oscilloscope-multimeter-and-signal-source/) says record length: 128KByte.. so if it's 8bit ADC then it's 128kpts? ( 1 point is 8 bits, 128KByte = 128 000Byte = 128 000 * 8 bits = 128 000 * 8 /8 points ? )
Fnirsi 2c53t says 1kpts
Zeeweii DSO3d12 - 128k .. means again 128kByte? Do you know how many bit ADC does Zeeweei have?
I am confused, maybe somebody can explain this.
Thanks L.
-
Zeeweii DSO3d12 - 128k .. means again 128kByte? Do you know how many bit ADC does Zeeweei have?
I am confused, maybe somebody can explain this.
...
My assumption about the ADC being an MXT2088 (AD9288 clone) seems to be correct.
AD9288 is 8bit ADC
Considering how much captured waveform can be zoomed in/out (timescale), the "128k point" assumption seems reasonable.
-
Based on similar discussions, it's somewhat less than that.
The question is whether the amount of usable memory is related to the time base.
If I remember correctly, for the Fnirsi 1013/14, it was written somewhere here that the number of samples saved depends on the time base, so the number in the specification is the best case.
Zoyi also writes: "record length: Max 128Kbyte"
From this, I can conclude that the 128Kbyte is not constant here either. :-//
Also, it is questionable whether there is a bug in it that prevents you from fully utilizing it.
Like for example in the Fnirsi 2C53P, where if you stop recording you cannot zoom in or out of the wave, you cannot move it sideways, etc... but according to its description it says "Storage Depth Up to 64kByte :blah:".
-
Mine has the BNC issue as well (BNC cables won't go on far enough to "click" into place, very frustrating).
How hard is it to remove the plastic behind the BNC connectors? I may go this route so I don't have to make a custom "connector saver" that fits the BNCs.
-
With the Zoyi, the only way to do a circular capture buffer (while the LCD is on), is to use the AHB SRAM1 and 2, which are 64K each, so 128kBytes combined.
With the 8bit ADC, maximum is 64k points when in dual channel, and 128k points in single channel. What the stock firmware does, is unknown, these are the maximum values.
Some update with my firmware is attached :)
-
Some update with my firmware is attached :)
From this picture, are we to understand that you've made enough progress on your custom firmware for the 703s to master the DMM functionality?
Awesome!
-
From this picture, are we to understand that you've made enough progress on your custom firmware for the 703s to master the DMM functionality?
Awesome!
Yes, all the original DMM functions work again, also found the frequency for AC voltage :). The DMM chip only sends its actual measured values, everything else is up to the main MCU, so I took the liberty to reorganize the soft button functions to my liking :)
Sorry for my potato phone camera pictures...
-
Hello 142 is higher size that 139 and for me it says not enough space when i try to copy it on device
-
With the Zoyi, the only way to do a circular capture buffer (while the LCD is on), is to use the AHB SRAM1 and 2, which are 64K each, so 128kBytes combined.
With the 8bit ADC, maximum is 64k points when in dual channel, and 128k points in single channel. What the stock firmware does, is unknown, these are the maximum values.
Some update with my firmware is attached :)
That's amazing! —thanks for sharing!
-
Hello 142 is higher size that 139 and for me it says not enough space when i try to copy it on device
First format the internal storage of the meter, the command should be in the oscilloscope menu (do not use your computer to format). When finished, swith to usb mode, that should also be in the scope menu
-
With the Zoyi, the only way to do a circular capture buffer (while the LCD is on), is to use the AHB SRAM1 and 2, which are 64K each, so 128kBytes combined.
With the 8bit ADC, maximum is 64k points when in dual channel, and 128k points in single channel. What the stock firmware does, is unknown, these are the maximum values.
Ok but 64k or 128k points sounds so much superior to 1k the FNIRSI 2c53t I wanted instead of zt703 claims .. It's very suspicious.
-
Ok but 64k or 128k points sounds so much superior to 1k the FNIRSI 2c53t I wanted instead of zt703 claims .. It's very suspicious.
If the Fnirsi really has an FPGA, then it has still better hardware, despite of the low memory size. I also have my doubts about the 250MSPS, thats probably just an overclocked MXT2088, like in the Zoyi... Zoyi and Fnirsi have a strange way of "calculating" the MSPS of their scopes anyway :palm:
I just don't like Fnirsi firmware and the absolute lack of updates.
-
Ok but 64k or 128k points sounds so much superior to 1k the FNIRSI 2c53t I wanted instead of zt703 claims .. It's very suspicious.
If the Fnirsi really has an FPGA, then it has still better hardware, despite of the low memory size. I also have my doubts about the 250MSPS, thats probably just an overclocked MXT2088, like in the Zoyi... Zoyi and Fnirsi have a strange way of "calculating" the MSPS of their scopes anyway :palm:
I just don't like Fnirsi firmware and the absolute lack of updates.
I think the most of the issues with this device are related to the scope. Bad voltage measurement, bad triggering and complex menus.
How did you get the firmware source code?
-
I think the most of the issues with this device are related to the scope. Bad voltage measurement, bad triggering and complex menus.
How did you get the firmware source code?
I started a new firmware from scratch, I don't want their sourcecode. I have reversed almost all of the hardware needed to make a new firmware from scratch.
This scopemeter is now a devboard for me. First I want to program the DMM part properly. After that comes the scope, where I have very specific needs (for work) and the hardware is totally capable of fulfilling these needs :)
Bad voltage measurement: this can be done properly relatively easily, although calibration will be required.
Bad triggering: can be made better, but the hardware is still very limited
Complex menus: yes, this has to be done better
-
I think the most of the issues with this device are related to the scope. Bad voltage measurement, bad triggering and complex menus.
How did you get the firmware source code?
I started a new firmware from scratch, I don't want their sourcecode. I have reversed almost all of the hardware needed to make a new firmware from scratch.
This scopemeter is now a devboard for me. First I want to program the DMM part properly. After that comes the scope, where I have very specific needs (for work) and the hardware is totally capable of fulfilling these needs :)
Bad voltage measurement: this can be done properly relatively easily, although calibration will be required.
Bad triggering: can be made better, but the hardware is still very limited
Complex menus: yes, this has to be done better
I feel I am not able to do all this. I have not idea, your skill surprises me.
-
Ok but 64k or 128k points sounds so much superior to 1k the FNIRSI 2c53t I wanted instead of zt703 claims .. It's very suspicious.
If the Fnirsi really has an FPGA, then it has still better hardware, despite of the low memory size. I also have my doubts about the 250MSPS, thats probably just an overclocked MXT2088, like in the Zoyi... Zoyi and Fnirsi have a strange way of "calculating" the MSPS of their scopes anyway :palm:
I just don't like Fnirsi firmware and the absolute lack of updates.
In the Fnirsi 2c53p thread people say 250MSPS is valid for OCed ADC. It has MXT2088 which is according to their datasheet 100MSPS. But they don't know if 250MSPS is for a combined value (125MSPS per channel) of the OCed ADC or what. It would make sense for 50Mhz oscilloscope.
Btw what is the FPGA in oscilloscopes used for?
-
In the Fnirsi 2c53p thread people say 250MSPS is valid for OCed ADC. It has MXT2088 which is according to their datasheet 100MSPS. But they don't know if 250MSPS is for a combined value (125MSPS per channel) of the OCed ADC or what. It would make sense for 50Mhz oscilloscope.
Btw what is the FPGA in oscilloscopes used for?
That is just not the way MSPS is advertised on a scope, this is just marketing BS. If everyone would do it like this, than my bench scope would have 8GSPS :palm:
Both are 100MSPS/channel, and are overclocked to 140MSPS (Zoyi) or 125MSPS (Fnirsi).
If you feed in a 50MHz signal, you have 2.5 (Fnirsi) and 2.8 (Zoyi) samples per waveform, the rest is just interpolation. Dave made a video about that:
https://www.youtube.com/watch?v=W4twnd-YQQ4 (https://www.youtube.com/watch?v=W4twnd-YQQ4)
The FPGA does all the realtime calculations, memory management, generates precise clocks, trigger detection, etc.
Edit: just to be fair to Zoyi (and I am sure Fnirsi did it the same way), it is possible, to route channel 1 to the 2nd input of the adc through an analog switch. This way it is possible to double the sample rate, but only, when using 1 channel.
-
Mine has the BNC issue as well (BNC cables won't go on far enough to "click" into place, very frustrating).
How hard is it to remove the plastic behind the BNC connectors? I may go this route so I don't have to make a custom "connector saver" that fits the BNCs.
I simply trimmed some plastic off the sleeve on the probe's connector with a sharp knife, and now it fits perfectly.
-
Any chance to download this custom firmware and test?
-
I don't know, probably it's a bug. The trigger place of the signal is shown correctly in the center up to 500 ns, but when we reduce the time scale to 250 ns or less, the trigger place is lost from the screen. It can be still found somewhere if we move the signal picture to the sides, but as we reduce the time scale it can be hardly made manually as it takes unreasonable amount of time (several minutes). Besides, the position of the marker on the scroll bar becomes lost (out of range) and it's even impossible to understand what part of the memory is shown at the moment. Moreover, getting back the trigger pointer to the center of the screen may takes minutes to roll it back with the arrows buttons - I couldn't find a button that could get it back at once (except reseting the hole device to defaults). I think it's the most annoying issue that I found in this device by the moment.
-
1) I would like to say hello, as a new user of ZOYI ZT-703S, which was purchased two days ago Version 1.4.2
2) After one day of use, the equipment seemed great for the price and what I expected from it. Oscilloscope tests with periodic signals from the generator up to 1 MHz showed me its capabilities in relation to the analog equipment I had in the years 1990-2000. Unfortunately, I later tested with single signals and came across problems .... I think the quality of the software is lacking in proper documentation. And that is why I need help from experienced people who own and understand this equipment.
3) In order not to discuss all the problems in one post, I will try to present the problems with version 1.4.2 successively
4) Here the first question in version 1.4.2 is the ability to set in the menu (Sample : Peak or HD) there is no such option in the documentation. How is the sample created in these modes? And how does it relate to the sampling period. I know the operation of a digital oscilloscope well enough to understand that for one channel, sampling at 100 MHz gives sampling every 10 ns. If we have a buffer of 128,000 samples, it gives us a recording time of 1800 micro sec. But how do we set the time base to 1 or 50 [ms]? Does the sampling period change? (the sampling period value should be displayed). How is the sample (HD) composed and how is it displayed. The documentation does not describe at all how it looks, and it is very important to understand what is displayed.
5) Additionally, if I view the graph (Hold key), I can scale (enlarge the waveform) to a certain range? so what is sampling or cheating.
6) In addition, I do not fully understand the way storage depth is presented on the screen (the bar on the left at the top in the documentation, item 2 Time Base Window). Is what is in gray recorded but not visible on the screen?
Please be very understanding, maybe I missed something reading the last very interesting posts, especially from jar171. I also understand that I didn't buy the equipment for 500 Euro, but I think that if you know the shortcomings of the equipment, you can fix it.
7) I can't find a list of errors detected by others in general.
8) In the next post I will address the problem of incorrect display of data from the fifo buffer. which led to my frustration
-
The second question/error is more difficult to present but I will try.
9) When I started testing a single trigger. A simple test of charging/discharging a capacitor through a resistor. I wanted to see if the trigger would work and understand how to buffer and then present data or position 2 of the Time Base Window)
I was getting strange recordings Figure 1 and 2, and I was expecting something like Figure 3 and 4 (this is a different mode of operation without triggering, so the question arises how it is assembled).
10) Analyzing Figures 1 and 2 I have the impression that the meter is not showing from the right place in the fifo buffer.
11) I also noticed that when I set the trigger location in time (green marker) after the red arrow, the oscilloscope records correctly. Figure 5 and 6
12) what does the red (triangle) marker (on the up window) mean?
-
I also noticed what "Tol" wrote in the previous post, that the trigger for the time base below 500ns triggers in the wrong place. To see the shift you have to press the Hold key and then increase the time base, then you will see the trigger shift (it is significant). You have to test it on a single peak, not a periodic signal. Maybe it is a buffering error.
What I wrote in the previous post if you know the shortcomings of the equipment you can fix it.
-
You have to test it on a single peak, not a periodic signal. Maybe it is a buffering error.
Yes, I also found that the single trigger gives more chances to find what you want. Your suggestion with the hold button is also helpful. However, let's take a look how the horizontal marker works. If we reduce the time scale, we can see that the green trigger marker always stays in a fixed place, while the real position of the triggered place moves to the left side. This is surely yet another bug. And I also have no idea what the red marker means, it feels like it's just the center of the screen marker? Before buying this oscilloscope I've watched a lot of reviews on youtube and some user showed very well that the scroll bar and the markers live their own life in different zoom levels and cannot be trusted, as well as the grid that shows unreal values in different zoom levels (I don't know if it was fixed in 142). To say the truth, it looks like the engineers tested this device in some lower zooms and decided that if it works fine there, there is no need to test other zoom levels.
-
By the way, I just looked at the screenshots above and found another nonsense. It shows a graph with the signal rise from 0V to 3V and the calculations window shows max 3.1V and min 3.0V. I have no idea where it takes these values from. Maybe the reason why nobody still made a full list of bugs is that all this firmware is a whole rotten bucket of bugs :)
-
Maybe the reason why nobody still made a full list of bugs is that all this firmware is a whole rotten bucket of bugs :)
These errors with the trigger and calculations have already been mentioned many times on previous pages, read carefully!
I also wrote that it is difficult to use oscilloscope as a measuring device in ZT-703, it is just a toy!
Waiting for custom firmware, because there is little hope for the manufacturer.
-
I don't know, probably it's a bug. The trigger place of the signal is shown correctly in the center up to 500 ns, but when we reduce the time scale to 250 ns or less, the trigger place is lost from the screen. It can be still found somewhere if we move the signal picture to the sides, but as we reduce the time scale it can be hardly made manually as it takes unreasonable amount of time (several minutes). Besides, the position of the marker on the scroll bar becomes lost (out of range) and it's even impossible to understand what part of the memory is shown at the moment. Moreover, getting back the trigger pointer to the center of the screen may takes minutes to roll it back with the arrows buttons - I couldn't find a button that could get it back at once (except reseting the hole device to defaults). I think it's the most annoying issue that I found in this device by the moment.
This is the way my device works.
Is the amplitude value right?
In my device the usual value is 0,2 - 0,3 volts less than the real value
-
Maybe the reason why nobody still made a full list of bugs is that all this firmware is a whole rotten bucket of bugs :)
These errors with the trigger and calculations have already been mentioned many times on previous pages, read carefully!
I also wrote that it is difficult to use oscilloscope as a measuring device in ZT-703, it is just a toy!
Waiting for custom firmware, because there is little hope for the manufacturer.
Exactly, my perception is more and more as a toy.
When you try almost any digital oscilloscope, you star to feel this device is a toy and not very reliable in some situations.
-
These errors with the trigger and calculations have already been mentioned many times on previous pages, read carefully!
I think we should point it out in every page of every forum. It is quite typical for Chinese manufacturers to abandon the firmware updates as a new version of hardware appears, which may happen every year. So we should take attention of the developers at least to the most terrible issues in hope they fix them in newer firmware, because I bet there will be no new firmware fixes as soon as they make zoyi 704 - they will just spend all their time to fix it's bugs and abandon 703 with all the bugs that it has at the moment because such small companies don't have enough people to support previous models of products... So the list of all the bugs is not a bad idea, the problem is to deliver this list to somebody who is responsible for the firmware development. Alternative firmware from users is also a good idea but we never know if it becomes better or worse that the original :) For example, I have no idea how to write firmware for oscilloscopes, and if the alternative firmware happens to miss some features that I need from the original version, I will have to use the original firmware anyway...
This is the way my device works.
Is the amplitude value right?
In my device the usual value is 0,2 - 0,3 volts less than the real value
The voltage is different on both channels in my device. Channel 1 always shows higher voltage than Channel 2. The difference is usually 0.1-0.2V, but it is MUCH higher when measuring higher voltage. I tried different probes and I reset the device to defaults, and calibrated several times, and swapped and calibrated the probes, but nothing helps. I think it may be caused by the resistors/capacities tolerance somewhere in the device channel lines, and this difference cannot be compensated in the settings.
In the second picture, it measures RMS 245V, while in the voltmeter mode it shows 220V, which is true voltage (I thought it could be because of different algorithms of RMS/TrueRMS measuring, but the difference is the same with clean sinus wave, so it's just the way it works.
-
And just to be fair, here is the same device with the same probes that shows 0.1-0.2V higher voltage than 3V (my multimeter measures 1.48*2=2.96V). But the first channel is higher anyway. I don't know why this happens. I found that the measurement precision depends on many things in this device, the values change when I zoom horizontally or vertically, and even when I change HD/PEAK mode, the values may also change.
I've got the most close-to-reality values when I closed the input sockets with a foil from a chocolate and made full re-calibration of the device. I'm not a specialist in such issues but I expect that the open sockets may grab some noise from the air that will make the calibration less precise. For example the second and the third photos show what happens when I just touch the probe (it is not connected to anything except my finger). It feels that I work as an antenna and receive a lot of energy from the air... Actually I can slightly light up LEDs when I touch them :)
-
I don't want to start a discussion about toys. IC_Toaster and Indman are almost right. But I wouldn't call ZT-703S a toy but an indicator... for which 20 years ago many would give a lot to have it lying on their table, even with such errors.
After three days I "feel" where the errors are in the software and my son (as a young "electronics engineer", he bought this indicator) can see\measure certain things with his own eyes, which is rather difficult to do with a voltmeter alone. During these few days he saw: interference on the amplifier power supply, phase shifts, the influence of the bias on the overheating of transistors working as switches.
I am attaching several images from CAN transmission in the car where I can check the voltage levels on the lines (and even the values in version 1.4.2 are appropriate). Possibility of recording data on a time basis of 2 ms and then scaling to the level of 10 micro sec.
It is obvious that there are errors in the software and the buffer indicator in the browsing mode contradicts logic, but it works according to this logic (sometimes you have to reset the meter).
It is obvious that my son would not be able to handle these errors without experience ... now he is already working.
Quite probably after a year he will stop being a "Young Electronics Engineer" and the indicator will remind him of those years and maybe I will use it sooner. But it is only a loss of 70 euros.
I see potential in this device for an amateur and I am waiting for the software to be changed.
For my part (let the other users of this indicator do it) I have already written a letter to the director and manager of this company what I think about the software. The motto of this company is "Need to get in touch with the team? We are all ears！" I wrote ... I am checking if it is true and waiting for a response ... and maybe it will not come.
-
Now if there is anyone who can answer me or point me to sources of information:
1) How do Samples work in this oscilloscope: (Peak or HD);
2) how does the sampling period change from the time base (and when there is then the possibility of scaling down almost 10 times);
3) how does the "scrolling mode" work, apart from the fact that they are for slow signals.
4) Here are words of admiration for "ajar171" for taking on such a difficult matter.
Secondly, to forum user "tol", as I wrote, he does not treat this device as an oscilloscope but as an indicator. Moreover, such effects as you describe may be the result of a mismatch or lack of appropriate load. Yesterday, my son and I measured a seemingly simple thing, a Graetz Bridge rectifier circuit, and the effect was the same as in your drawing. After loading with a lower resistance value, there was no such effect. But I am not an electronics expert, but a programmer.
-
The automatic measurement is bad, this has been written several times before, that's why you have to use the cursor.
If I calculated and measured correctly, then at 1V/Div sensitivity, the maximum measurable voltage is 9.3Vpp measured with the cursor and according to the automatic measurement it is only 8.6Vpp.
In other words, the automatic measurement is faulty for some reason, I think this must be a firmware bug.
In 1V/Div.
The smallest change that the device measures is 0.05V.
In other words, 50mV, 100mV 150mV. There is no value in between.
Theoretically, it is 8-bit stuff, but if I divide 9.3V by 0.05v, it only comes out to 186, not 256.
If I compare it to the voltage accuracy of DMMs, which is ±(%+digit).
so if I measure a wave that is definitely 3.00V with it, but it shows 3.2V, it is only a +4 digit difference, inaccuracy.
According to the description: "DC Gain Accuracy: ±3%"
It doesn't say what % it is, but I don't think it is the same for every time base.
According to the description:
Sweep speed range: 10ns/div – 20s/div
Sample rate range: 1.5Sa/s – 280MSa/s
If you swap the sample rate value, for example, then
Sweep speed range: 10ns/div – 20s/div
Sample rate range: 280MSa/s - 1.5Sa/s
The memory only says:
"record length: Max 128Kbyte"
From this I assume that it is not constant.
Since we can't save the wave as a file with it, only save images, so I don't know. :-//
I think the HD/Peak detect mode just thickens the lines and makes the part you can't see visible.
I tested it with a single trigger, zoomed in to the wave in HD and Peak detect mode, and I didn't see any difference in the faster time base.
But I hope I'm wrong.
-
If it is not done in the same way as with 1013D, the change on bit 0 and bit 1 is simply ignored.
-
This is the way my device works.
Is the amplitude value right?
In my device the usual value is 0,2 - 0,3 volts less than the real value
The voltage is different on both channels in my device. Channel 1 always shows higher voltage than Channel 2. The difference is usually 0.1-0.2V, but it is MUCH higher when measuring higher voltage. I tried different probes and I reset the device to defaults, and calibrated several times, and swapped and calibrated the probes, but nothing helps. I think it may be caused by the resistors/capacities tolerance somewhere in the device channel lines, and this difference cannot be compensated in the settings.
In the second picture, it measures RMS 245V, while in the voltmeter mode it shows 220V, which is true voltage (I thought it could be because of different algorithms of RMS/TrueRMS measuring, but the difference is the same with clean sinus wave, so it's just the way it works.
This is a disaster. One channel is wrong and the other is worse.
As it is not possible to see the samples value, I think it is difficul to deduce if the problem is the samples quantification, the values adquired by the A/D converter or the processing.
I don't think there is a different algorithm for each channel.
And just to be fair, here is the same device with the same probes that shows 0.1-0.2V higher voltage than 3V (my multimeter measures 1.48*2=2.96V). But the first channel is higher anyway. I don't know why this happens. I found that the measurement precision depends on many things in this device, the values change when I zoom horizontally or vertically, and even when I change HD/PEAK mode, the values may also change.
I've got the most close-to-reality values when I closed the input sockets with a foil from a chocolate and made full re-calibration of the device. I'm not a specialist in such issues but I expect that the open sockets may grab some noise from the air that will make the calibration less precise. For example the second and the third photos show what happens when I just touch the probe (it is not connected to anything except my finger). It feels that I work as an antenna and receive a lot of energy from the air... Actually I can slightly light up LEDs when I touch them :)
I have notice that the values change even if you move the reference down.
That you say that you introcude signal just touching the probe happens also in good oscilloscopes. Certain, you act as antenna and that signal is the electrical installation signal (50-60Hz).
I don't want to start a discussion about toys. IC_Toaster and Indman are almost right. But I wouldn't call ZT-703S a toy but an indicator... for which 20 years ago many would give a lot to have it lying on their table, even with such errors.
After three days I "feel" where the errors are in the software and my son (as a young "electronics engineer", he bought this indicator) can see\measure certain things with his own eyes, which is rather difficult to do with a voltmeter alone. During these few days he saw: interference on the amplifier power supply, phase shifts, the influence of the bias on the overheating of transistors working as switches.
I am attaching several images from CAN transmission in the car where I can check the voltage levels on the lines (and even the values in version 1.4.2 are appropriate). Possibility of recording data on a time basis of 2 ms and then scaling to the level of 10 micro sec.
It is obvious that there are errors in the software and the buffer indicator in the browsing mode contradicts logic, but it works according to this logic (sometimes you have to reset the meter).
It is obvious that my son would not be able to handle these errors without experience ... now he is already working.
Quite probably after a year he will stop being a "Young Electronics Engineer" and the indicator will remind him of those years and maybe I will use it sooner. But it is only a loss of 70 euros.
I see potential in this device for an amateur and I am waiting for the software to be changed.
For my part (let the other users of this indicator do it) I have already written a letter to the director and manager of this company what I think about the software. The motto of this company is "Need to get in touch with the team? We are all ears！" I wrote ... I am checking if it is true and waiting for a response ... and maybe it will not come.
When I received the Zoyi I was quite surprised because my last use of an oscilloscope was some years ago and I had used mainly analog oscilloscopes. So I found this device quite useful, but after seeing the bugs and have bought a Siglent my perception was changing.
I know this is more than a toy, but I feel, due to the lack of precision, that you need to know the bugs and have some criterion to discern if the values could be right or not.
-
The only difference (electrically) between the two channels is an analog switch (6\$\Omega\$) just before the ADC input (10k\$\Omega\$).
I could not find out, how they do the self-calibration, although I must admit, that I did not really looked into that yet. I have still 3 unknown pins on the MCU..
From the firmware side of things, I think that they push everything through the DFSDM of the MCU (I will do that for sure), wich does the Sinc filtering, mix/max detection and offset correction.
If fed with the wrong offset values, the poor filter will give us wrong output
-
Just some thoughts about the selfcal for discussion:
Each analog channels voltage divider can be set from 1000:1 to 1:1 in 12 steps.
I have no idea how a selfcal without an external (high) voltage fed into the BNC connector could work in a device where the highest internal voltage is that of the battery :-//
-
Moreover, such effects as you describe may be the result of a mismatch or lack of appropriate load. Yesterday, my son and I measured a seemingly simple thing, a Graetz Bridge rectifier circuit, and the effect was the same as in your drawing. After loading with a lower resistance value, there was no such effect. But I am not an electronics expert, but a programmer.
As far as I understand, this happens when being close to high voltage wires. The frequency of this parasite signal is 50Hz, this is exactly the same frequency used in high voltage lines in my country. Besides, this signal gets stronger when I get close to the places where the wires or electronic devices are placed and it is absent when I'm out of house. So this is not the problem of zoyi itself but a problem of the "dirty" environment, in terms of electromagnetic fields around us. It's possible that calibration in "clean" electromagnetic conditions may be important to this device. As far as I understand the main purpose of the calibration is to find the pattern of the internal noise in the device and eliminate it by software algorithms, so IMHO the cleaner the calibration conditions are, the better.
Anyway, I think this device is not so bad, I've bought it for just $50 and I need it mostly to play with esp32/raspberry and other hobby stuff. Now I can see PWM and this is what I couldn't do with a voltmeter. I think that everyone understands that the oscilloscope for $50 cannot work the same way as the oscilloscope for $5000. The fact that is has problems with measurements and correct trigger place display seems to be more software issue than hardware issue, we only need to encourage the developers to read this forum thread and respond somehow. I believe that many issues can be solved easily by somebody who has the source code and can modify it. The most difficult thing is to reach that person and tell him what needs to be fixed :)
-
1) How do Samples work in this oscilloscope: (Peak or HD);
I don't know how it works but I feel that it's just a kind of software noise filter. Maybe it's just a marketing trick to make the graph look more clean in comparison with the cheap oscilloscopes of competitors. What I see is that HD just shows some average line from what I see in the PEAK mode.
-
There are many topics discussed and very important…….
1) Thanks to csuhi17 with a good compilation of data, it is necessary to understand what we require from the device and directed me to some tests. But I would like to establish one basic thing, the sampling frequency for one channel. Ajar171 writes that "dual channel 100MSPS ADC (overclocked to 140MSPS in high speed mode), both channels sampled in parallel." and I agree with this, the given frequency of 200 - 280 is marketing for two channels. Maybe I am wrong and when we use one channel, two converters work for one channel, which I doubt.
2) Differences for Peak or HD Atlan is wrong "If it is not done in the same way as with 1013D, the change on bit 0 and bit 1 is simply ignored."
I am attaching several images in turn:
p1 is a test signal sin 25,000 Hz amplitude 10 : -10; we can see it nicely, it has 10 us and we measure it.
p2) we increase the base time to 5ms and we get what should be visible (sample Peak mode) it is good. we see too large a time base.
p3) we change to HD mode and we see a straight line ... so there is some averaging. I will definitely not use this mode when I see the signal for the first time.
3) Additionally, I am attaching another 3 drawings where:
p4 records the same signal based on 1ms;
p5 (hold key) o I increase to 10 us and I see a beautiful sine signal. I cannot decrease the time, there is a blockade.
P6 I do the recording based on 5ms and I can increase to 10us and the signal is the same as for p5
4) As csuhi17 wrote, without real data we are not able to properly determine what the sampling, buffer length or interpolation is, but these tests allow me to determine certain limits of the device.
6) I am attaching two additional drawings:
p7) shows the image at a base of 100ms and this is normal, the sampling has changed and hence such an image and the wrong frequency.
p8) very long time base... We change the sample mode Peak HD Peak during recording
-
I didn't want to discuss separate topics in one place
1) Ajar171 Unfortunately, I\We are not able to help you at all, we are waiting for the result like hyenas. Maybe if you found the time, you could present the diagram, give the firmware for testing, but I also doubt that it would help you. Rather us. Think about it. If you have time, answer question 3)
2) The topic of voltage measurement accuracy ... I don't quite understand what you require from this indicator. I have a +10 -10 sine (I don't know if it's correct) on the oscilloscope, the Amplitude is displayed halfway, i.e. about 128 bits, one percent (20 V) is 0.2, I assume that 3% 0.6 is OK and for small voltages it is OK.
3) Change of accuracy when shifting up or down (question to Ajar171 whether the shift is on the analog side), a diagram of the input path is needed. I think the shift is on the analog side because after shifting out of range the calculations are also cut off. I don't think the programmer averaged over bytes and after shifting and then subtracted the shift value. (difficult to explain).
4) As for the previous post (sampling test), it is obvious that switching to 140 MHz removed (illustrating) the intermediate frequency of 6.14 KHz. The question is still whether the sampling is 140 or 280 MHz
-
I didn't want to discuss separate topics in one place
1) Ajar171 Unfortunately, I\We are not able to help you at all, we are waiting for the result like hyenas. Maybe if you found the time, you could present the diagram, give the firmware for testing, but I also doubt that it would help you. Rather us. Think about it. If you have time, answer question 3)
2) The topic of voltage measurement accuracy ... I don't quite understand what you require from this indicator. I have a +10 -10 sine (I don't know if it's correct) on the oscilloscope, the Amplitude is displayed halfway, i.e. about 128 bits, one percent (20 V) is 0.2, I assume that 3% 0.6 is OK and for small voltages it is OK.
3) Change of accuracy when shifting up or down (question to Ajar171 whether the shift is on the analog side), a diagram of the input path is needed. I think the shift is on the analog side because after shifting out of range the calculations are also cut off. I don't think the programmer averaged over bytes and after shifting and then subtracted the shift value. (difficult to explain).
4) As for the previous post (sampling test), it is obvious that switching to 140 MHz removed (illustrating) the intermediate frequency of 6.14 KHz. The question is still whether the sampling is 140 or 280 MHz
1, there is not much to test at the moment, I am working on getting all the hardware stuff running properly. The firmware has currently no oscilloscope function at all, my focus is currently on the DMM part.
2, a vertical DC gain accuracy of ±3% is explicitly stated in the specs of this meter, so it is within specs. An oscilloscope is not intended to be a precision voltmeter anyway.
3, it is a result of the inaccuracy of the divider network (there are a lot of resistors in the signal path, even if they all have 0.1% accuracy, it adds up...) and the joke of a selfcal function. All filtering, averaging is done in HW, see the DFSDM block diagram (ignore the serial and parallel ADC part, the data is coming from the bus)
4, a 280MSPS is electrically possible only on channel 1 (it is still 140MHz ADC clock, but with a 180° clock phase shift), but I don't know (and don't care) if Zoyi uses it in the stock firmware.
I am not posting anything, that I have reverse engineered, because I don't know if it is even legal in Germany.
-
I am not posting anything, that I have reverse engineered, since I don't know if it is even legal in Germany.
I have heard before that it's legal in EU, not in the US...
https://www.tme.eu/en/news/library-articles/page/56932/reverse-engineering-what-is-it-and-is-it-legal/ (https://www.tme.eu/en/news/library-articles/page/56932/reverse-engineering-what-is-it-and-is-it-legal/)
In the European Union, reverse engineering is permitted – under the verdict of the Court of Justice issued in 2012 – for creating computer programs with operation analogous to the original program. In that verdict, the Court of Justice ruled that the functionality of software is not protected by copyrights within the territory of the EU, which opened the door to research and testing of original programs so as to reproduce (not copy) their behavior in another program.
-
I am not posting anything, that I have reverse engineered, since I don't know if it is even legal in Germany.
I have heard before that it's legal in EU, not in the US...
https://www.tme.eu/en/news/library-articles/page/56932/reverse-engineering-what-is-it-and-is-it-legal/ (https://www.tme.eu/en/news/library-articles/page/56932/reverse-engineering-what-is-it-and-is-it-legal/)
In the European Union, reverse engineering is permitted – under the verdict of the Court of Justice issued in 2012 – for creating computer programs with operation analogous to the original program. In that verdict, the Court of Justice ruled that the functionality of software is not protected by copyrights within the territory of the EU, which opened the door to research and testing of original programs so as to reproduce (not copy) their behavior in another program.
Happy new year everyone!
I know, that it is legal to RE a product that I have bought, I just don't know if it is allowed to publish or share the information obtained through RE. Sorry, but it is simply not worth the risk for me.
-
1) Ajar171 thank you for the New Year's wishes, may we be successful.
The next questions may be lame, but I think that you need to know the block structure of the tool to use it well and interpret data (errors). I am interested in the problem of trigger(s) and memorizing samples from ADCs (DFSDM). Synchronization of these blocks, because I see a big hardware and software problem here (not eliminated by the programmer of this device).
2) ad3 " All filtering, averaging is done in HW, see the DFSDM block diagram (ignore the serial and parallel ADC part, the data is coming from the bus) " I attached your drawing and led in Red the processing in Oscilloscope mode. In Blue DMM. I did this to make sure I understand you correctly. And I have further questions:
ad3.1 Where is the 128 kB of memory, I understand that it is a circular buffer (filled with DMA packets, where is the grouping of this data)?
ad3.2 Does HW supervise this (it has to, but how????)?.
ad3.3 I mean how is the data in this memory synchronized with time (is time measured successively by adding the ADC sampling time value?).
Ad3.4 Is this buffer filled all the time even when no trigger has occurred (I think so)
Ad3.5 How does HW know (synchronize) the trigger occurrence… but this problem after explaining how the trigger circuit works.
3T) In your list you wrote a few things about triggering in this device:
3T.1 You wrote that this is software triggering. Then that there are simple comparators there. How is that?
3T2 I imagine that the comparator detects exceeding the threshold (UweTrig). The HW circuit has a setting on the pin to interrupt the transition from state 0 to 1 or vice versa. And then it is necessary to precisely determine the current position of the data recording in the 128 kB buffer, i.e. precisely synchronize: the data positions at the time of the trigger. Then determine how many ADC samples must be saved after the trigger (here the position of the time trigger) to interrupt the measurement at the right time. If this time is too long, then the data is overwritten at the beginning of the samples, if the old data is too small. And this sometimes happens in the meter. This very very difficult for hardware and SW.
4) Here I would like to describe my observations of the measurement in the oscilloscope mode, one channel, single trigger. I know that you do not care how this software works, but if you specified the sampling frequency (maybe the amount of data), it would be a sure source of knowledge for us. In addition, I always think that a person can learn from the mistakes of others.
4.1 The oscilloscope with small time bases from 10 ns to 10 us always records 128 kB samples with the highest possible frequency (I think so). This gives an approximate recording time of +- 300 us (time trigger in the middle). You can see this by pressing the hold key, and then increasing the time base. Picture 2 and 3.
4.2 The problem with this meter is as follows:
4.2.1 when several triggers occur in a row, it incorrectly determines the data copying positions from the buffer;
4.2.2 if the trigger is triggered before the time of 320 us, the data is initially zeroed.
4.2.3 when the time base is less than 500 ns, there is a shift between the trigger position and the data (this situation can also occur on other bases).
4.2.4 I generally stopped going below 1 us with the time base, because the same data is recorded anyway, which I can later see in Hold mode.
AD4 "280MSPS is electrically possible only on channel 1 (it is still 140MHz ADC clock, but with a 180° clock phase shift)", does this mode require the same signal to be applied to the CH2 ADCs input or is it done internally
-
2) ad3 " All filtering, averaging is done in HW, see the DFSDM block diagram (ignore the serial and parallel ADC part, the data is coming from the bus) " I attached your drawing and led in Red the processing in Oscilloscope mode. In Blue DMM. I did this to make sure I understand you correctly.
The drawing is wrong, as stated above you should have ignored the serial and parallel ADC part. The DMM is a separate circuit, completely isolated from the scope and MCU part, it communicates with the MCU via a serial link.
And I have further questions:
ad3.1 Where is the 128 kB of memory, I understand that it is a circular buffer (filled with DMA packets, where is the grouping of this data)?
ad3.2 Does HW supervise this (it has to, but how????)?.
ad3.3 I mean how is the data in this memory synchronized with time (is time measured successively by adding the ADC sampling time value?).
Ad3.4 Is this buffer filled all the time even when no trigger has occurred (I think so)
Ad3.5 How does HW know (synchronize) the trigger occurrence… but this problem after explaining how the trigger circuit works.
Tha data has to be stored in AHB SRAM1 and 2, I don't see any other way at the moment. The ADC is connected to the GPIO Port D, wich is also in AHB domain. The rest is up to the DMA controller in circular buffer mode, the DMA has to run continously, while waiting for a trigger of course. The MCU used in this meter is a pretty capable one, it should be able of running this scope with some limitations (limitations, not bugs).
3T) In your list you wrote a few things about triggering in this device:
3T.1 You wrote that this is software triggering. Then that there are simple comparators there. How is that?
3T2 I imagine that the comparator detects exceeding the threshold (UweTrig). The HW circuit has a setting on the pin to interrupt the transition from state 0 to 1 or vice versa. And then it is necessary to precisely determine the current position of the data recording in the 128 kB buffer, i.e. precisely synchronize: the data positions at the time of the trigger. Then determine how many ADC samples must be saved after the trigger (here the position of the time trigger) to interrupt the measurement at the right time. If this time is too long, then the data is overwritten at the beginning of the samples, if the old data is too small. And this sometimes happens in the meter. This very very difficult for hardware and SW.
3T1: I did not find the comparators at first, took me some time to RE that part, I don't do this every day. They did some strange design decisions, those robbed me a lot of time.
3T2: Yes, that would normally be the job of the missing FPGA. I will see, how I want to do this exactly, I have an idea, but I will test it first, when I get there.
4) Here I would like to describe my observations of the measurement in the oscilloscope mode, one channel, single trigger. I know that you do not care how this software works, but if you specified the sampling frequency (maybe the amount of data), it would be a sure source of knowledge for us. In addition, I always think that a person can learn from the mistakes of others.
4.1 The oscilloscope with small time bases from 10 ns to 10 us always records 128 kB samples with the highest possible frequency (I think so). This gives an approximate recording time of +- 300 us (time trigger in the middle). You can see this by pressing the hold key, and then increasing the time base. Picture 2 and 3.
I can only tell you the maximum sampling rates: 100MSPS and 140MSPS, with both channels active. That is what I have measured myself. With a memory depth of 64kbytes@100MSPS, you get 644µs, that checks out.
I have erased the stock firmware from my meter, so I can not tell you how fast they are sampling apart from the max speeds.
4.2 The problem with this meter is as follows:
4.2.1 when several triggers occur in a row, it incorrectly determines the data copying positions from the buffer;
4.2.2 if the trigger is triggered before the time of 320 us, the data is initially zeroed.
4.2.3 when the time base is less than 500 ns, there is a shift between the trigger position and the data (this situation can also occur on other bases).
4.2.4 I generally stopped going below 1 us with the time base, because the same data is recorded anyway, which I can later see in Hold mode.
Exactly the reason, why I have erased the stock firmware.
AD4 "280MSPS is electrically possible only on channel 1 (it is still 140MHz ADC clock, but with a 180° clock phase shift)", does this mode require the same signal to be applied to the CH2 ADCs input or is it done internally
The input signal from channel 1 can be routed internally to the ADC input of channel 2.
-
I am not posting anything, that I have reverse engineered, since I don't know if it is even legal in Germany.
I have heard before that it's legal in EU, not in the US...
https://www.tme.eu/en/news/library-articles/page/56932/reverse-engineering-what-is-it-and-is-it-legal/ (https://www.tme.eu/en/news/library-articles/page/56932/reverse-engineering-what-is-it-and-is-it-legal/)
In the European Union, reverse engineering is permitted – under the verdict of the Court of Justice issued in 2012 – for creating computer programs with operation analogous to the original program. In that verdict, the Court of Justice ruled that the functionality of software is not protected by copyrights within the territory of the EU, which opened the door to research and testing of original programs so as to reproduce (not copy) their behavior in another program.
As far as I know, reverse engineering is legal everywhere
While you don't copy the original code, if the result is the same, totally legal
-
Has anyone identified the battery used in this DMM?
The ZT-703S charger can be either the ME4059D or, in newer revisions, the ME4086B. Both are designed to charge up to 4.34V, suggesting the battery should have a maximum voltage of 4.35V.
However, the battery's protection chip, a DW01 from XIN FEI HONG, is designed for 4.2V batteries and has an overcharge protection voltage of 4.3V. This implies the battery might actually be a standard 4.2V max type.
-
Guys, pls do you know how the baseline calibration works on ZT703S?
Maybe I am doing it wrong, but mine always ends with a message "check failed"
The baseline calibration is described on page 19 in the manual.
---
Baseline Calibration:
The instrument is factory-calibrated at 100%. However, if there is a
baseline offset due to large environmental temperature deviations or
prolonged periods of non-use, baseline calibration can be performed.
1. Enter the third menu, press F1, and the screen will prompt "Unplug
the plug and press the menu key to start calibration."
2. Press the MENU key to start the calibration.
During calibration, please note the following:
1. Do not connect the probe or input signal during calibration, as it
may cause calibration deviation or damage to the instrument.
2. Do not perform other operations during the calibration process.
Wait patiently until the calibration is complete.
Thanks a lot.
-
Guys, pls do you know how the baseline calibration works on ZT703S?
Maybe I am doing it wrong, but mine always ends with a message "check failed"
Enable both channel CH1 and CH2 in the menu and repeat the calibration. This feature has already been mentioned on the topic pages before.
-
Guys, pls do you know how the baseline calibration works on ZT703S?
Maybe I am doing it wrong, but mine always ends with a message "check failed"
Enable both channel CH1 and CH2 in the menu and repeat the calibration. This feature has already been mentioned on the topic pages before.
Thanks. It helped. Sorry, I tried to search for keywords calibration, baseline and so on but I wasn't able to find it.
-
Thanks ajar171 for his time and explanation of how the processing works in this meter for two modes.
1) I won't waste your time with additional questions because you are working on a completely new version and you have completely deleted the previous one. Switching to two different versions takes time and I understand that you are not able to determine the converter sampling or buffer width for individual time bases.
2) For me, this device lacks information on how the sampling frequency and buffer width change depending on the time base and the number of enabled channels. Such information gives me a preview of how short pulses will be detected depending on the base.
3) I had the opportunity to check the meter in this respect of peak detection and it is quite good. The youth tormented this device in a real situation where there was an error (a peak of several microseconds) of the load (current voltage converter) and the 703s detected it as well. I also checked what pulse widths it detects without losing in Scroll Mode: 200ms and more, for a time base of 200ms pulses with a time of 40 microsec.
-
Mine has the BNC issue as well (BNC cables won't go on far enough to "click" into place, very frustrating).
How hard is it to remove the plastic behind the BNC connectors? I may go this route so I don't have to make a custom "connector saver" that fits the BNCs.
I just removed the thick sticker at the bottom of the cavity of the two BNC connectors with a small screwdriver (see pictures before and after) and then was able to conect all my scope probes and BNC cables without any problems.
-
Hey deforme,
I had the same issue with my 703, i.e. that the multimeter stopped working, no measurements shows, no reaction to the F1-4 buttons.
In my case it was working at first but after using once, it stopped working.
However, I was able to fix it by applying some hot air to the DMM chip, which is labeled DM1109CEN (left to the battery). I heard it clicking like there was some tension. :-/O
-
As far as I know, reverse engineering is legal everywhere
While you don't copy the original code, if the result is the same, totally legal
Same in the U.S., reverse engineering is only illegal for the purpose of defeating copy protection. Which obviously only applies if someone distributes copies, but no one here I think has any interest in distributing the OEM firmware, or more specifically using it in competing products.
Same with hardware, without cloning there's no copyright issue and reverse engineering isn't a problem at all. There may be patents, but they don't prevent reverse engineering (in fact patents explain how things work) and doesn't prevent DIY projects.
I think it would be great to have open source instrument software. Did anyone figure out what the LQFP-100 is? STM32 of some flavor? Presumably something with an LCD controller on a set of pins, which would narrow it down substantially...
-
Ajar171 has mentioned it's something like .. STM32H7B0VBT
He attached a pinout at page 34 of this topic.
-
Just to set some things straight:
- I will upload the source of my firmware to github, when there is something usable to upload. Please wait until at least the DMM part is finished and working properly. The firmware is being written from sratch, no original code used, so it takes some time. I just don't want to post the schematics, that I have reversed.
- I have not recovered the decrypted firmware from the meter as it is just simply not worth any effort
- If you erase the firmware from the meter, there is no going back. It is not possible to install the stock firmware again, because we don't have the encryption keys. The stock firmware has to be erased, before flashing a third party firmware to the meter.
- To flash an inofficial firmware to this meter, an SWD debugger is necessary (something STM32Cube compatible, at least a 2€ ST-LinkV2 clone)
-
Can't you disconnect the original uP and install a new empty one?
-
Can't you disconnect the original uP and install a new empty one?
Sure, that is always an option :)
The MCU costs 6.2€ at Mouser if you buy a single piece, so it is not that expensive
-
1) ajar171 Thanks for the post starting with "Just to set some things straight:"
2) This post really describes the situation for a certain group of people (like me). The most important thing is that you can't go back to the original version.
3) Unfortunately, for some time we are doomed to the ZOYi company "as user tol said"
4) I really support and admire this project you are doing.
5) Out of curiosity, has anyone managed to get a response from ZOYi about the bugs... Because I haven't received one yet.
-
Just to set some things straight:
- I will upload the source of my firmware to github, when there is something usable to upload. Please wait until at least the DMM part is finished and working properly. The firmware is being written from sratch, no original code used, so it takes some time. I just don't want to post the schematics, that I have reversed.
- I have not recovered the decrypted firmware from the meter as it is just simply not worth any effort
- If you erase the firmware from the meter, there is no going back. It is not possible to install the stock firmware again, because we don't have the encryption keys. The stock firmware has to be erased, before flashing a third party firmware to the meter.
- To flash an inofficial firmware to this meter, an SWD debugger is necessary (something STM32Cube compatible, at least a 2€ ST-LinkV2 clone)
Thanks ajar!
Don't rush yourself... the firmware will be ready when it's completed.
Everybody is expecting with excitement, it's normal! But here in spain we have a saying: "Vísteme despacio que tengo prisa" ("Dress me slowly, I'm in a hurry").
Take the time you need, i'll will be great while you don't abandon the project ;)
thanks a lot
-
I await the open firmware with great interest. As soon as it becomes at least a little usable for use as an oscilloscope, I will install it for myself and join the development (if the code will not be too complicated, I am not good at C++, only at pure C)
-
It's a very good device, and I'm very satisfied with it. However, I'm unhappy with the resistance measurement. In my case, shorting the lead wire using the probe shows 0 ohm, but it actually seems to be expressing negative resistance. In this case, if the device can express negative resistance, I think the REL function can help me measure the resistance more accurately. Wait for the firmware update.
-
It's a very good device, and I'm very satisfied with it. However, I'm unhappy with the resistance measurement. In my case, shorting the lead wire using the probe shows 0 ohm, but it actually seems to be expressing negative resistance. In this case, if the device can express negative resistance, I think the REL function can help me measure the resistance more accurately. Wait for the firmware update.
My wires show 0.02-0.05 Ohm, never 0 or negative. And by the way, there is REL function, it is the red power button (short press).
-
It's a very good device, and I'm very satisfied with it. However, I'm unhappy with the resistance measurement. In my case, shorting the lead wire using the probe shows 0 ohm, but it actually seems to be expressing negative resistance. In this case, if the device can express negative resistance, I think the REL function can help me measure the resistance more accurately. Wait for the firmware update.
I wonder why are you so satisfied with this device. The device is in fact terrible. The scope part is buggy, there is a lot of info about this in this topic. DMM is maybe acceptable, but it's not so extraordinary. You can buy for example ZT225 which is 25 000 counts and I believe the same accuracy, as well, but has also temperature measuring, NCT etc. + some small but solid oscilloscope. For example if I had the information what I know right now, I wouldn't buy it. But unfortunately I wasn't able to return it back where it came from because of holidays. So right now I am stuck with this crappy device.
-
I got one of the ZT-703S's as an impuls buy, and I'm quite happy with it. It's a neat little device, that's "good enough".
I wouldn't use it for proper scoping (got a mso5000 for that), but to quickly checkout stuff, validate/verify things, see what's going on, it's perfectly fine. For the 'Arduino crowd' it's a fine scope.
For the regulars of this form, I get the critique, but I had the same with the DS1074. My statement was, these devices are dirty cheap, put them on every EE's desk. Useful and makes them feel valued. Have a proper scope in the lab for the die-hard EE's or critical measurements.
Mind you, we where an embedded linux shop, so we ran things at 'consumer speeds'. E.g. the most complex stuff being looked at was power supplies and their ripples/startup voltages, current dips, and the usual I2C and SPI inspection.
I would argue today, that the ZT-703S is even good enough for these tasks, except logical analyzer work, but the DS1074 etc where not great at those tasks either (they worked, most of the time).
As for ajar171's efforts, I bow deeply for you and wish you the best. I will be a happy tester once it becomes functional enough!!
I've reverse engineered PCB's (often from just photo's) in the past and done even drawn kicad schematics from it. So if time permits, I'd be happy to play with this for a bit. Obviously I don't want to fully duplicate your work :D
-
5) Out of curiosity, has anyone managed to get a response from ZOYi about the bugs... Because I haven't received one yet.
I wrote to zotektools.com and zoyitools.com, but got no answer. They are so busy accepting the payments that they don't have time to answer to their customers :) To say the truth, it feels like they are not willing to develop it further so they make it look as if they don't receive our bug reports, because if they answer something they will have to fix these bugs, otherwise it will be difficult to look as a professional manufacturer that they pretend to be. But if they don't answer anything they can always say that they don't know that there are any bugs in their products and they are clean. Just for the purpose of fun, you can write to them again, but this time don't say anything about the bugs, write that you want to place an order for 10000 pieces, I bet you will get an answer pretty much soon :)
-
I wrote to zotektools.com and zoyitools.com, but got no answer. They are so busy accepting the payments that they don't have time to answer to their customers :) To say the truth, it feels like they are not willing to develop it further so they make it look as if they don't receive our bug reports, because if they answer something they will have to fix these bugs, otherwise it will be difficult to look as a professional manufacturer that they pretend to be. But if they don't answer anything they can always say that they don't know that there are any bugs in their products and they are clean. Just for the purpose of fun, you can write to them again, but this time don't say anything about the bugs, write that you want to place an order for 10000 pieces, I bet you will get an answer pretty much soon :)
I also wrote to them several times with exactly the same result. But Brymen answered me almost immediately (I only had to remind them about myself once :D).
-
They are so busy accepting the payments that they don't have time to answer to their customers :)
That's why even earlier I wrote something like this :D
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5722843/#msg5722843 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5722843/#msg5722843)
-
That's why even earlier I wrote something like this :D
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5722843/#msg5722843 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5722843/#msg5722843)
Yes, it's typical for such companies to "solve" firmware issues by releasing new hardware version, but this doesn't gain much respect from the customers. Basically, there is limited number of people who are interested in such equipment, and once they are left with a buggy device and abandoned support, most of them will remember this bad experience and never buy the products of this company again. Once I had exactly the same situation with a TrendNet router, they knew there was a bug in their firmware but instead of fixing it they just suggested to buy a new model of their router! I've never bought any TrendNet product since that time and I never will! Zoyi seemed more promising in this respect as they had at least several firmware updated for 703, maybe they still work on it, who knows. At least when I bought it in November it had a fresh production date and the latest firmware pre-installed, so they still continue to produce these things and probably think that this model will still be interesting to customers for some time even when it's full of bugs :) Why they never answer to anyone - this is not smart for them to treat customers like this, but this is the way they work... I tried to write to their youtube channel, but I wouldn't expect miracles there :)
-
I got mine from the official Zoyi shop on Aliexpress and with the recent firmware 1.4.2 as well. But mine looks like already used. Somebody returned it before. So maybe they just refurbish returned units slightly, update bootloader / firmware and ship them to customers again, who knows.
But this isn't the problem, bugs are.
It's pity that they can't release firmwares for older devices as an OSS. This would be great, because somebody who wants to give it the effort could mine a hidden reserves from it and improve it.
-
I've just found this in the comment section of a youtube video by the guy tim1tim2 who used to be the marketing manager (if I remember correctly):
Q: Temperature measurement can be added?
"We originally planned to include it, but for some reason, the code for temperature and the code for waveforms conflicted with each other. We tried to resolve the issue for three months, but to no avail. In the end, we had no choice but to remove the temperature feature."
It clearly shows they are struggling with programming the device...
-
:palm: :-DD
-
It clearly shows they are struggling with programming the device...
:-DD
-
Can i use a ch341a to flash your firmware?
-
Can i use a ch341a to flash your firmware?
As far as I know, the CH341A does not have JTAG, it can only program EEPROM and FLASH chips through I2C or SPI. The CH347 should be able to do it, but I never tried that myself.
-
I have been following this thread. I own one and fall into the camp that feels it has value as is, and also feel that it is reasonably priced. I have a lab oscilloscope but it resides in a different part of the house from where I solder and assemble things ... the Zoyi lives there. (a link to my lab scope: https://www.eevblog.com/forum/beginners/help-with-a-simple-three-leds-lamp/msg5781355/#msg5781355 (https://www.eevblog.com/forum/beginners/help-with-a-simple-three-leds-lamp/msg5781355/#msg5781355))
Scopes are now like DMMs in that lots of folks own more than one.
-
May be someone knows, what is this - 'Signal output, time base limitation'. What does it mean?
https://youtube.com/shorts/iYAqnu6dGlY?si=5HcJ_Na9OHH24KzA
(how to insert here youtube video correctly?)
-
Is it posible to use zoyi zt-703s with sigrok using your firmware?
-
May be someone knows, what is this - 'Signal output, time base limitation'. What does it mean?
https://youtube.com/shorts/iYAqnu6dGlY?si=5HcJ_Na9OHH24KzA
(how to insert here youtube video correctly?)
Hi, the problem is that you set output signal of your signal generator to sine 1Khz instead of square 1Khz.
Go to menu and find output. Set square 1Khz and it should be ok.
-
May be someone knows, what is this - 'Signal output, time base limitation'. What does it mean?
https://youtube.com/shorts/iYAqnu6dGlY?si=5HcJ_Na9OHH24KzA
(how to insert here youtube video correctly?)
Hi, the problem is that you set output signal of your signal generator to sine 1Khz instead of square 1Khz.
Go to menu and find output. Set square 1Khz and it should be ok.
But what does this have to do with the internal generator if I'm looking at a completely different signal?
-
But what does this have to do with the internal generator if I'm looking at a completely different signal?
[/quote]
There are two signal generators in this device.
One that you can set in the oscilloscope app.
The other is a separate application.
If you use the one in the oscilloscope, it will degrade the oscilloscope parameters.
The device is probably not able to use both applications at the same time.
reset the signal generator in the scope to a square wave of 1 kHz.
-
Go to menu and find output. Set square 1Khz and it should be ok.
reset the signal generator in the scope to a square wave of 1 kHz.
Yes! You were right! As soon as I switched the internal generator to square, everything worked as it should! A clean signal appeared, and the sweep parameters began to switch correctly. Thank you very much. But for me it was a big surprise - I could not even imagine that there was some kind of correlation! On the contrary, I set the sine to remove the harmonics of the meander, which, as I thought, could cause some kind of interference. And look how it turned out...
-
I just got mine, love it so far. I hate the measure display placement, but if you only have 2 choices selected in ch1 at least the measurement boxes stack to the left. I wish measurements were displayed in a single line across the bottom.
I wonder which is convention for the directions to manipulate time base and v/div, I got used to my hantek, but now it is 'backwards' or maybe this is true correct way?!!
I also discovered cursors won't display if persistence is set anywhere above min (off) after fiddling for ages!
Has anyone actually tried to use the signal generator in the circuit being measured? Did you just use alligator test leads because the frequency is so low, or is there a lead I can buy\make?
-
I don't know, probably it's a bug. The trigger place of the signal is shown correctly in the center up to 500 ns, but when we reduce the time scale to 250 ns or less, the trigger place is lost from the screen. It can be still found somewhere if we move the signal picture to the sides, but as we reduce the time scale it can be hardly made manually as it takes unreasonable amount of time (several minutes). Besides, the position of the marker on the scroll bar becomes lost (out of range) and it's even impossible to understand what part of the memory is shown at the moment. Moreover, getting back the trigger pointer to the center of the screen may takes minutes to roll it back with the arrows buttons - I couldn't find a button that could get it back at once (except reseting the hole device to defaults). I think it's the most annoying issue that I found in this device by the moment.
long press the menu button will recentre the triangle.
-
long press the menu button will recentre the triangle.
Thanks, where did you find this information? Maybe there's something else I miss in there :)
-
I too spent far too long pressing the direction buttons to recentre the waveform, so i experimented!
-
Thanks, where did you find this information? Maybe there's something else I miss in there :)
https://www.dropbox.com/scl/fi/qm8vlwby6lqrolhy36m8r/ZT-703S-EN.pdf?rlkey=iaqfg4i1jcn2gumccvhv6msx7&e=1&dl=0 (https://www.dropbox.com/scl/fi/qm8vlwby6lqrolhy36m8r/ZT-703S-EN.pdf?rlkey=iaqfg4i1jcn2gumccvhv6msx7&e=1&dl=0)
Zt 703s user manual page 12
-
I seem to be stupid and don't understand something here, maybe someone can explain.
I have a signal like in the picture.
I used Cursor feature to measure period T, which is approximately 50 ns. This is also proved by the grid: 2 cells 25 ns each is 50 ns.
Now, frequency F = 1/T, which is 1/0.000000025=40Mhz.
So, why the oscilloscope shows 20Mhz, twice less? What is the real frequency in this example?
-
I seem to be stupid and don't understand something here, maybe someone can explain.
I have a signal like in the picture.
I used Cursor feature to measure period T, which is approximately 50 ns. This is also proved by the grid: 2 cells 25 ns each is 50 ns.
Now, frequency F = 1/T, which is 1/0.000000025=40Mhz.
So, why the oscilloscope shows 20Mhz, twice less? What is the real frequency in this example?
One cannot know unless the trigger level is set within the amplitude of the signal. ;)
-
1/20Mhz is 0,05us -- 50ns means 2 divisions with a 25ns base, or 5 divisions with a 10ns base
-
I seem to be stupid and don't understand something here, maybe someone can explain.
There are two options for measuring frequency.
One is "Freq", the other is "Fcnt".
As Tautech suggested, set the trigger on the signal, in the middle. :-+
If I try your method, then for me Freq alternates between 20MHz and 40MHz.
If the signal is not clean enough, there are intermediate values.
-
There are two options for measuring frequency.
One is "Freq", the other is "Fcnt".
As Tautech suggested, set the trigger on the signal, in the middle. :-+
If I try your method, then for me Freq alternates between 20MHz and 40MHz.
If the signal is not clean enough, there are intermediate values.
Seems to be my mistake in dividing values. In my case putting the trigger within the wave doesn't change anything, FREQ is always around 20MHz and FCNT is 424 kHz (not sure what this value means). I tried to find explanations and there was answer from kloetpatra in this forum that:
FCNT: hardware counter based on the trigger. It will display 0.000Hz when trigger level is set outside of waveform.
Freq: software analysis of the waveform in the display memory. It will display --.-- if it can not determine the frequency.
So it looks like the trigger position is not important for Freq but important for FCNT, however, as I understand, they are expected to show the same value, and in my case they don't.
-
I seem to be stupid and don't understand something here, maybe someone can explain.
I have a signal like in the picture.
I used Cursor feature to measure period T, which is approximately 50 ns. This is also proved by the grid: 2 cells 25 ns each is 50 ns.
Now, frequency F = 1/T, which is 1/0.000000025=40Mhz.
So, why the oscilloscope shows 20Mhz, twice less? What is the real frequency in this example?
The signal period is 50 ns, why do you divide by 25?
-
The signal period is 50 ns, why do you divide by 25?
[/quote]
I think it's because I'm inattentive :) I measured the value correctly, but divided by a wrong number. Maybe that 25 ns/cell mislead me... I'm happy that I'm not a space ship construction engineer, otherwise it would certainly fly to a wrong planet :)
-
Is there a firmware version that the trigger and cursor buttons automagically change colour to show which channel is being used like the vol/time and move buttons ? At the moment my workaround is to choose the channel on one of the first two buttons manually so it shows the correct colour. I know it doesn't affect the outcome, but it makes the UI feel more consistent!
Does the trigger actually do anything in normal mode compared to auto? It seems only in some random cases to function like on my hantec dso2d15 where single and auto function as expected. I know I read earlier a mention that the implementation of the trigger left a lot to be desired, but I seem to have great trouble seeing a difference in the waveform displayed other than T'D being shown when I switch between normal and auto.
Again, I love this device. I can sit on the verandah with my breadboard and z703 and my classpad and nerd out doing RC time constant math in the sunshine!
EDIT: i used the email link at the firmware update page to link to this thread and asked the question relating to the button colours. Will post back if i get a meaningful reply.
-
I opened my z703s to be greeted with a nasty surprise of deep corrosion on the metal shield, I can't see underneath if there is more damage but as it was brand new from Amazon I sent it back and a new one is on the way.
-
A little petition to member ajar171
Is there a chance to add extra functionality to diode testing, like a short beep sound when the DMM detected diode testing?
-
A little petition to member ajar171
Is there a chance to add extra functionality to diode testing, like a short beep sound when the DMM detected diode testing?
If You mean, to beep, when the voltage is below a threshold, then it is already done. It beeps 3 times / second as long as the voltage is below a set threshold (it is a hack, because the MCU has no control over the DMMs beeper, but it works :))
-
Any chance of your firmware working with sigrok software. I see some multimeters and oschiloscope in their list.
-
Any chance of your firmware working with sigrok software. I see some multimeters and oschiloscope in their list.
I have to check that, but whis has really low priority.
In DMM mode, the meter is already sending the measured value over USB-CDC (it can even be controlled), but someone would have to write an input plugin for sigrok.
-
Did you get any other responses on this message as I have a similar problem, the up down arrows will not move me to the amplitude field and I cannot therefore set the amplitude level. it is the same for the 'more apps' generator and the "Output Setting". I can only get to the "Output field" but not the "Freq", "Vpp" or "Duty" fields in the Output Generator. In the "More apps" generator I can adjust Frequency, signal type and duty cycle but not amplitude as the buttons F1-F4 never offer amplitude to be adjusted. I am on V1.4.2 of firmware
-
Problem. In Output (F4 key of menu) the up down arrows will not move me to the Freq, Vpp or duty fields and I cannot therefore set the amplitude level. The menu button when pressed, will allow me to set the signal type, sine square etc. it is the same for the 'more apps' generator and the "Output Setting". I can only get to the "Output field" but not the "Freq", "Vpp" or "Duty" fields in the Output Generator. The exit button (F4) will not allow me to exit either. In the "More apps" generator I can adjust Frequency, signal type and duty cycle but not amplitude as the buttons F1-F4 never offer amplitude to be adjusted. I am on V1.4.2 of firmware. How do you adjust the amplitude (Vpp) on the More apps Generator? Vpp seems fixed at 2.5V. Pretty useless.
Maybe I'm just doing it wrong. Really like some help.
-
Are you aware the more apps signal generator does not function when you are using the oscilloscope?
The output (button f4) fields can be accessed when you select (hit menu to change the box outline to yellow) another waveform than the standard 1khz square wave (adj sq wave, sine wave, tri wave,) then hit menu again and while the box outline is red move down and hit menu to change the selection while the box outline is yellow, then hit menu again to make the outline red and exit with the f4 button
-
While I love my z703s, there a couple of issues I have with it:
1/ won't hold normal trigger below 500ns on slow waveforms (below 85khz)
2/ rms measurement seems to use Vpp x .7071 when it should Vpp/2 x .7071**further tests suggest user error.
3/ cursors don't remember last position when switching modes.
4/ cursors don't display if persist is above min.
5/ on screen button colours don't auto match selected channel for trig and cursor.
6/ artifacts on screen when using persist and turning off a channel.
If anything happens with custom firmware I would love to see the on screen buttons drop down after a timeout like windows taskbar, then measurements could be displayed outside the grid (i would be happy to choose only 3 measurements at a time which would fit nicely in a horizontal row) or the actual height of the waveform grid could be extended to fill the space. (like the owon 272s) All in all I think the z703s is a keeper, even with my gripes!
-
If anything happens with custom firmware I would love to see the on screen buttons drop down after a timeout like windows taskbar, then measurements could be displayed outside the grid (i would be happy to choose only 3 measurements at a time which would fit nicely in a horizontal row) or the actual height of the waveform grid could be extended to fill the space. (like the owon 272s) All in all I think the z703s is a keeper, even with my gripes!
That is a great idea! Thanks!
-
Mate, my biggest qualification is enthusiasm, but if there is anything I can do to help with the custom firmware process feel free to message me. I understand the risks of flashing etc, but knowing that eventually the z703s will be forgotten by our Chinese overlords, if this wonderful device is to have a long life, a custom firmware will be the way.
-
Just a quick update
-
I love the time graph of voltage! Can you show some sort of time scale and will this work on current as well?
-
I love the time graph of voltage! Can you show some sort of time scale and will this work on current as well?
Sure ;) It works in all modes
-
Just a quick update
I find this graph quite more useful than the level marking than the stock firmware has.
You are doing a good job.
-
Great work. Whats the minimum s/div?
-
Great work. Whats the minimum s/div?
The technical minimum is 20s/div, because the meter takes 3 measurements/second and one division is 60 pixels wide. Currently the max is 1hour/div (so 1 minute/pixel), but that is only a software limitation.
For long term logging, the internal flash is used, also with 1 minute/entry limit, average,min,max recording in csv format, there the meter can save around 620.000 entries until the disk is full (that would be over a year of logging)
The trend plot can be switched off, if not needed, so the screen is not that cluttered.
-
I just got my owon hds272s, and I must say after a week with the z703s I am underwhelmed by the owon. I really miss having both cursors at the same time (for manually calculating rise time and rms) and wow does the owon run warm and compared to the z703s, you can almost watch the batteries discharge in front of your face (hyperbole warning!)
The z703s multimeter is a joy to use and very nicely placed information on the screen makes infromation easy to read where the owon multimeter feels like they had a couple of spare bytes left over so they left some rudimentary program on the flash. It is a shame really, clearly the owon oscilloscope is a superior beast, and I much prefer how the buttons disappear wwith a configurable timeout to allow for a larger grid to display the waveform.
It seems I am a zoyi fanboi now at 61, it all started with my much loved little green zt-102L purchased over a year ago, which is such a handy size and with so much functionality that it is always at hand near the work bench. Now it has a friend.
-
Great work. Whats the minimum s/div?
The technical minimum is 20s/div, because the meter takes 3 measurements/second and one division is 60 pixels wide. Currently the max is 1hour/div (so 1 minute/pixel), but that is only a software limitation.
For long term logging, the internal flash is used, also with 1 minute/entry limit, average,min,max recording in csv format, there the meter can save around 620.000 entries until the disk is full (that would be over a year of logging)
The trend plot can be switched off, if not needed, so the screen is not that cluttered.
Will an external storage be supported as well? For example USB flash drive?
Will it be possible to do more complex logging scenarios? For example not only voltage measurement, but for example voltage and then DMM would be automatically switched to current measurement and measure current?
Thanks L.
-
Could I ask for diagrams for a possible repair of the device. Thank you
-
for example voltage and then DMM would be automatically switched to current measurement and measure current?
How is this possible? This requires physical re-commutation of the device inputs and changing the device connection to the measured circuit!
-
for example voltage and then DMM would be automatically switched to current measurement and measure current?
How is this possible? This requires physical re-commutation of the device inputs and changing the device connection to the measured circuit!
Well, I am not sure if it's possible.
My idea was like this ..
The device has 10A, mA , COM and V/R/diode/Cap sockets
Physically it's possible to connect for example 10A and COM in series and add another test lead and connect it in parallel to measure the voltage
But I have no idea if it's possible to change DMM mode between A, V, R etc. from inside the firmware.
Not sure if something like this would damage the device.
I thought, that incorrect connection in AMP mode in parallel (for example between + and GND or ~ and GND ) would damage the device/burn the fuse, but not in series ( even though the device is switched to V measurement )
Also I have no idea whether for example 10A and COM are still live (connected together) even though the test mode is changed to Volts. Maybe they aren't .. I've never tested anything like this.
Maybe it's all impossible.
Quite recently I had some issue with my car. I needed to log voltage on the battery but also power drain for a few days. And I asked myself if it would be possible to measure this with just one device in the same time. But maybe it's impossible because of construction of the device or so.
-
Maybe it's all impossible.
Maybe, but not with this device. :)
https://www.eevblog.com/forum/testgear/dmm-simultaneous-voltage-and-current/ (https://www.eevblog.com/forum/testgear/dmm-simultaneous-voltage-and-current/)
-
From the software standpoint, it is easy enough, although pretty annoying because of the constant beeping:
10 switch to voltage mode, it beeps
20 take a voltage measuerement
30 swith to current mode, it beeps
40 take a current measueremnt
50 goto 10
From the electrical standpoint, please someone check, a snippet from the chips manual is attached.
USB host mode for connecting external storage would be possible in software, but the ZT703 does not put out 5V to its USB port, so you would need a power supply for an external drive.
I think it is just not worth it, as you can store over a year of logging data with 1 log entry/minute and even with 3 log entries/second you get 55hours of logging time (assuming 15MB free space avaiable on the internal drive)
If that is not enough, there is always the possibility of replacing the SPI flash with a bigger one...
-
USB host mode for connecting external storage would be possible in software, but the ZT703 does not put out 5V to its USB port, so you would need a power supply for an external drive.
I think it is just not worth it, as you can store over a year of logging data with 1 log entry/minute and even with 3 log entries/second you get 55hours of logging time (assuming 15MB free space available on the internal drive)
If that is not enough, there is always the possibility of replacing the SPI flash with a bigger one...
Sure, the only issue is that flash in the CPU can by simply overwritten too many times and can fail by time. After that you need to replace the CPU inside of the device. Isn't then better to use external storage whenever it's possible?
Wouldn't be possible just use small cheap USB hub and connect a power bank into it .. connect an external flash drive and this all would be connected into the DMM?
So you can log quite long time somewhere in the field??
-
Sure, the only issue is that flash in the CPU can by simply overwritten too many times and can fail by time. After that you need to replace the CPU inside of the device. Isn't then better to use external storage whenever it's possible?
Wouldn't be possible just use small cheap USB hub and connect a power bank into it .. connect an external flash drive and this all would be connected into the DMM?
So you can log quite long time somewhere in the field??
The flash inside the MCU is not used for data storage, it is way too small anyway.
The Zoyi has an onboard 16Mbyte SPI flash, wich is easy enough to replace if you wear it out (100.000 erase/write cycles are stated in the datasheet, so it should last for a long time)
Or you connect a laptop or a smartphone with USB, and log over the virtual com port, then you get virtually unlimited storage space.
-
Ah, they use "external" SPI flash. Ok, then it's better.
The concept with a powered USB HUB could be interesting (not sure if it could work), but sure, it's not worth it.
-
ajar171: could you fill us in on the progress you are making? I was really impressed by the replacement of the DMM function and the trace which you've indicated can be turned on/off. slick.
is your work available for download / install?
Are you allowing people to be beta-testers? If so, where do I sign up? :-DMM
-
ajar171: Do you have bigger schematic especially how is the circuit made around the COM plug?
I am looking at the schematic, but I don't see anything why it should be possible.
But I am just a beginner, so maybe somebody experienced will post his opinion.
Btw, is it possible somehow calibrate the ZT703S DMM ? Mine measures for example 13,14V instead of 13,10V. Not a lot, but still.
Mine looks like somebody sent it back before. So, maybe this is the reason.
Edit: It's 0,3%.
But I don't have a precise voltage source.
I took 2 different volt meter ( different models, different accuracy )
1 x Meterman 37XR and 1 x Chauvin & Arnoux 5220G and measured the same source of voltage.
They measured exactly the same voltage 13,10V. ZT703S 13,14V
Or AC 232V measured as 236V by ZT703S
Thx
-
Incredilbe job Ajar!
-
ajar171: Do you have bigger schematic especially how is the circuit made around the COM plug?
Here you go, the poorly translated datasheet is attached (found in the internet). I have no idea, how to enter calibration mode with the stock firmware. I also did not try to enter it with my firmware (becuase of the isolator between the DMM chip and the MCU, I think it is not possible, but I could be wrong here).
Here is a way to do it:
http://www.kerrywong.com/2016/03/19/hacking-dtm0660l-based-multimeters/ (http://www.kerrywong.com/2016/03/19/hacking-dtm0660l-based-multimeters/)
With Kerry Wongs method, you can directly edit the cal factors in the eeprom, description of the eeprom data is in the attached datasheet. Be sure to make a backup!
I would not try it, without having a known good voltage source.
-
Here is the content of the DMM eeprom from my meter (ZT703).
If someone would be so kind, and read the contents of the 24C02 of a ZT702 and post it here, maybe we could re-enable the temperature measurement in the ZT703.
Else I have to do it in software.
-
If someone would be so kind, and read the contents of the 24C02 of a ZT702 and post it here, maybe we could re-enable the temperature measurement in the ZT703.
Here is a screenshot with ZT-702S
-
This is strange.
According to the datasheet, the ZT703 should not have a continuity mode, but should have the temperature mode enabled, which is not the case.
The ZT702 should have and has both modes.
I have the feeling, that the DMM chip has a custom firmware for Zoyi and does not care about the enabled/disabled features in the eeprom.
Anyway, I will try to change the eeprom of the 703 to the 702 settings (adress range 0x80 to 0xBF) later and see what happens.
-
I have the feeling, that the DMM chip has a custom firmware for Zoyi and does not care about the enabled/disabled features in the eeprom.
You think correctly, very often the operating modes are already programmed in the main DMM chip. ;)
-
I have the feeling, that the DMM chip has a custom firmware for Zoyi and does not care about the enabled/disabled features in the eeprom.
You think correctly, very often the operating modes are already programmed in the main DMM chip. ;)
Then I will save myself the trouble of reprogramming the eeprom, and go the software route for the temperature measurement.
It is a basic voltage to temperature conversion with a lookup table anyway, not that big deal in software (there is probably working and tested open source code on github already...)
-
ajar171: could you fill us in on the progress you are making? I was really impressed by the replacement of the DMM function and the trace which you've indicated can be turned on/off. slick.
is your work available for download / install?
Are you allowing people to be beta-testers? If so, where do I sign up? :-DMM
I am working on getting FatFs and USB mass storage working again (I had to change how the SPI flash sector caching works, which broke FatFs and USB-MSC).
Then I have to make a menu framework for the new functions, because the meter is currently controlled over the serial connection (I am too lazy to use the buttons ;D), core DMM functions are done and working.
When DMM mode (including the new functions) is ready, than we can start beta testing :)
My warning again:
- there is no going back to stock firmware
- the firmware is being made on the PCB version 2.2, and I don't know if it works on other revisions, because I only have this meter. In the review video of Dave the version 1.8 can be clearly seen. I don't know, what they have changed
- as always, absolutely no warranty
-
I have the feeling, that the DMM chip has a custom firmware for Zoyi and does not care about the enabled/disabled features in the eeprom.
You think correctly, very often the operating modes are already programmed in the main DMM chip. ;)
Then I will save myself the trouble of reprogramming the eeprom, and go the software route for the temperature measurement.
It is a basic voltage to temperature conversion with a lookup table anyway, not that big deal in software (there is probably working and tested open source code on github already...)
Isn't an internal temperature sensor needed to be able to calculate the temperature based on the voltage of a thermocouple?
-
Isn't an internal temperature sensor needed to be able to calculate the temperature based on the voltage of a thermocouple?
For thermocouples, yes. For PT100 or PT1000 no.
The main MCU has an internal temperature sensor, which could be used for cold junction compensation.
This will introduce an error, because the MCU is physically far away from the cold junction (the terminals) and it is also heating itself up, so I think a user compensation temperature input will be required.
PT sensors are easy enough to implement, so I will save the thermocouple stuff for later :)
-
Yes, I understand. Thank you for your response, and congratulations on your amazing initiative!
-
Any update on the firmware? Plz post any video. This stuf is so exiting.
-
So, did the Chinese abandon the ZT703? They're probably making a 704 super full HD 1 GHz out of crap and sticks :-DD
-
Did domeone have a chance to test the v1.49 FW?
https://zotektools.com/products/triple-in-one-instrument-combining-oscilloscope-multimeter-and-signal-source/ (https://zotektools.com/products/triple-in-one-instrument-combining-oscilloscope-multimeter-and-signal-source/) -> Click on the green "Russian version firmvare" button
-
That's odd. Why make country specific firmware when current firmware already has menu option to change language (english/chinese). Why not just add additional languages to the existing menu.
-
Did domeone have a chance to test the v1.49 FW?
https://zotektools.com/products/triple-in-one-instrument-combining-oscilloscope-multimeter-and-signal-source/ (https://zotektools.com/products/triple-in-one-instrument-combining-oscilloscope-multimeter-and-signal-source/) -> Click on the green "Russian version firmvare" button
i just update but doesn't tested.
language : English/China/Russian.
Not much improvement.
In the 100ms/Div timebase, if I apply a few Hz wave to one of the inputs, there will be an anomaly in the wave.
AUTO still doesn't work well.
-
And I recently bought an old (but unused) Rigol 1052E and now I have no questions or misunderstandings, as was always the case with this ZOYI... )))
-
And I recently bought an old (but unused) Rigol 1052E and now I have no questions or misunderstandings, as was always the case with this ZOYI... )))
It's the right decision on your part! Toys for kids. Grown-ups need devices they can trust, not toys. :)
-
And I recently bought an old (but unused) Rigol 1052E and now I have no questions or misunderstandings, as was always the case with this ZOYI... )))
It's the right decision on your part! Toys for kids. Grown-ups need devices they can trust, not toys. :)
Please don't insult others, a grown man with three children, two wives and four mistresses has the right to buy and play with toys! :popcorn:
-
Please don't insult others, a grown man with three children, two wives and four mistresses has the right to buy and play with toys! :popcorn:
Ok! Two wives and four mistresses is a serious argument! :) :popcorn:
-
Hello everyone,
I have a ZOYI ZT-703S multimeter that I purchased about 3-4 months ago, and recently, the display has started having serious issues. The problems include:
The screen has lost sharpness, making it difficult to read measurements.
The resolution appears to have dropped, with text and numbers looking blurry.
Previous display elements leave ghosting effects, meaning that old readings are still faintly visible even after the screen updates.
Despite this, the multimeter's functions and measurements still work correctly. Based on my experience, this issue might be caused by a faulty LCD panel or a problem with the graphics processor.
Has anyone else experienced a similar issue with this model? If so, was there a way to fix it? I’m considering contacting the seller for warranty service, but I’d like to know if there are any possible DIY fixes before going through that process.
Any help or advice would be greatly appreciated!
-
Bad zebra strip connection is my guess.
-
I'll advise try to return the multimeter/oscilloscope. If you open it up and try to fix it, you might void the warrantee (why take chance). Maybe they will give you a new unit (might have to ship it back).
From the manual...
Limited Warranty and Scope of Rights and
Responsibilities
This product is eligible for a one-year
warranty from the date of purchase.
This warranty does not cover blown fuses,
damage to general accessories, or damage
caused by accidents, negligence, misuse,
modifications, pollution, and abnormal
operating environments.
Note: If there is a situation of freezing or
crashing during use, please restart.
Assume this might not be fun experience... Let us know how things goes. Good luck...
-
Bad zebra strip connection is my guess.
There's no zebra strip, it has flex connection.
-
I'll advise try to return the multimeter/oscilloscope. If you open it up and try to fix it, you might void the warrantee (why take chance). Maybe they will give you a new unit (might have to ship it back).
From the manual...
Limited Warranty and Scope of Rights and
Responsibilities
This product is eligible for a one-year
warranty from the date of purchase.
This warranty does not cover blown fuses,
damage to general accessories, or damage
caused by accidents, negligence, misuse,
modifications, pollution, and abnormal
operating environments.
Note: If there is a situation of freezing or
crashing during use, please restart.
Assume this might not be fun experience... Let us know how things goes. Good luck...
Warranty in aliexpress...
Good joke!
It took me months to claim a warranty for a mobile and the most i could get was a 80 € discount
-
Warranty in aliexpress...
Good joke!
It took me months to claim a warranty for a mobile and the most i could get was a 80 € discount
It's seller dependent. I had a problem with T3a soldering station and the seller send me a handle and after that a new motherboard
-
Hello, I had: when switching from a multimeter to an oscilloscope and vice versa, sometimes half the screen was displayed, the other half was dark. I dismantled, reconnected the train on the display, and the problem disappeared.
-
Hello, I had: when switching from a multimeter to an oscilloscope and vice versa, sometimes half the screen was displayed, the other half was dark. I dismantled, reconnected the train on the display, and the problem disappeared.
I have the exact same issue. I'll give your fix a try, thank you!!!
-
Hi all,
I recently got a 703s to add to my "collection" of low cost handhelds - however even after the latest upgrade (V142) mine does not display the correct trigger point in Normal or single trigger mode under the 500ns time div setting. At 500ns and above it works as expected, waveform is displayed correctly at the trigger level but under it's somewhere lost far on the "left" of the scope window and you have to scroll a lot to find it taking ages. I thought this was an old bug which had been fixed, but apparently not - can anyone confirm this?
Thanks!
-
mine only does this if the signal is less than 84kHz.
https://youtube.com/shorts/PKDjzDo-SVw?feature=share
I uploaded a short clip to youtube showing it in 250ns losing trigger below 84kHz, but have no idea how to include it in the post.
-
The screen has lost sharpness, making it difficult to read measurements.
The resolution appears to have dropped, with text and numbers looking blurry.
Previous display elements leave ghosting effects, meaning that old readings are still faintly visible even after the screen updates.
This look like absence of one of the power supply voltages at the LCD panel.
-
Warranty in aliexpress...
Good joke!
It took me months to claim a warranty for a mobile and the most i could get was a 80 € discount
Contact the manufacturer or their official store directly.
In recent years, I’ve had positive experiences with Chinese manufacturers like Owon, Zotek, and UNI-T.
-
A scope that doesn't trigger properly in any situation is rather useless IMHO. I hope they will release an update else it will just be another paperweight for my use cases. I have a cheapo "ZEEWEI" which cost half and works rather well unexpectedly.
FYI if I select 250ns/div and trigger in normal or single, I have to scroll back to the left (pressing the right arrow to move the current trigger point to the right) about 3.2ms to see center the correct trigger point. If I leave it there and do another single shot it will remain in the center (shifted). As soon as I try to move left or right it will disappear, and when I press OK to re-center I will find it centered! Certainly a bug or two here to fix.
Brief video showing it: https://youtube.com/shorts/XRGxF6oBQFs
-
i just update but doesn't tested.
language : English/China/Russian.
Something strange is happening
Today I tried to update the firmware, and I encountered the fact that there is less free space on the internal storage than the size of the firmware. At the same time, there are no files there at all, only firmware folder
-
Something strange is happening
Today I tried to update the firmware, and I encountered the fact that there is less free space on the internal storage than the size of the firmware. At the same time, there are no files there at all, only firmware folder
for me after one of the previous updates it contained several files and folders, the names were not consistent, they contained random characters.
I could not delete, modify or open them.
Now after the last update they disappeared and only a few folders with meaningful names remained.
According to disk management I have 10 MB of free space out of 14 MB.
I can't help you with what you should do in your situation.
-
uncle_sem https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5632455/#msg5632455 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5632455/#msg5632455)
-
Maybe someone has tried it... Is it possible to install old firmware over the new one?
-
cant find "format" option in 1.4.2 firmware. now in the place where the "format" was, there is "FFT"
-
Maybe someone has tried it... Is it possible to install old firmware over the new one?
YES, and this is the way I uploaded latest firmware version - first I uploaded 1.3.9 firmware, fortunately it fits and have format option, then I formatted it, and finally uploaded new firmware
-
sp3rat , Read the previous page carefully to avoid repeating the same questions.
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5833205/#msg5833205 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5833205/#msg5833205)
-
ADDENDUM...
I thank everyone who tried to help with advice on the repair. I didn’t want to attempt a repair, but I managed to start a return process – I need to return the device, and I should receive a full refund for the device and shipping costs. I say 'should' because so far, the process is going well for me.
I plan to buy a similar device again, but I’m not sure whether to buy the ZT-703S again or another similar device, or maybe even buy 2 devices – one multimeter and one oscilloscope.
I’m asking ZOYI device owners, especially owners of the ZT702S or ZT703S, if they’ve had any issues with device malfunctions (other than software errors).
Thanks for your responses.
Hello everyone,
I have a ZOYI ZT-703S multimeter that I purchased about 3-4 months ago, and recently, the display has started having serious issues. The problems include:
The screen has lost sharpness, making it difficult to read measurements.
The resolution appears to have dropped, with text and numbers looking blurry.
Previous display elements leave ghosting effects, meaning that old readings are still faintly visible even after the screen updates.
Despite this, the multimeter's functions and measurements still work correctly. Based on my experience, this issue might be caused by a faulty LCD panel or a problem with the graphics processor.
Has anyone else experienced a similar issue with this model? If so, was there a way to fix it? I’m considering contacting the seller for warranty service, but I’d like to know if there are any possible DIY fixes before going through that process.
Any help or advice would be greatly appreciated!
-
I’m asking ZOYI device owners, especially owners of the ZT702S or ZT703S, if they’ve had any issues with device malfunctions (other than software errors).
I personally did not have problems with my ZT-702S yet, but one of my channel subscribers reported that all multimeter functions on his 702 had failed - the oscilloscope still works fine.
I provided some tips to him but haven't heard back. Given his unit was bought a while ago, he has no recourse of return.
Unfortunately, uneven quality control is something that is common in cheap products, thus what works for one might not work for the next buyer.
-
Hi all, I've read thru all of the notes, sounds like these models have their issues. I have quite a few scopes and have seen these hand-helds for a while. Recently the Fnirsi 2C53T caught my eye. I want something small that I can use on my desk to align digital tape decks without dragging out a larger scope. I use my Siglent 1104XE with the mods, but even that is too large. I want something that I can set on the tape deck and do very uncomplicated tests. I just need two channels, one for triggering and the other for viewing RF below 20Mhz. Having that integrated in a volt meter of some accuracy would be handy. So are they complete junk or do they function ok within limits? And the 703s seems more popular than the 2C53T, any comments comparing the two?
Thanks
Jerry
-
Maybe not the 2C53T, but Fnirsi has a history of being economical with the specs.
There's also many others:
https://www.eevblog.com/forum/testgear/portable-oscilloscopes-list/ (https://www.eevblog.com/forum/testgear/portable-oscilloscopes-list/)
-
I'm testing my 703s and had a board sitting here with three, 3.0uf electrolytic caps on it. My ZOYI smart tweezers, pretty amazing device for the money, reads them perfectly but the 703s won't read them at all. I assume it is because of how the 793s reads the caps vs the 703s which uses an A/C signal?
Overall, the 703s is doing what I needed it to do. I can trace SPIDF signals fine and some other things for which I would normally drag out a larger scope.
Jerry
-
The test leads are to long. Try shorter ones. Also whait a bit and it will show the values.
-
tried very short leads, no luck. None of my other meters, except for the zoyi tweezers, will read the caps in-circuit on this board reliably. Sometimes my agilent U1252B will. Overall, still impressed with the 703s for the money.
-
How much does it not measure them, what's the difference?!
I quickly measured two 4.7u electrolytes and the Zoyi tweezer measured around 4.7uF at 100Hz, the ZT-703s measured around 5.1uF.
The factory Zoyi test leads were bad for me, I had to replace them.
-
it just counts up to OL. The caps are 3uf, approx. I don't have a problem with caps out of circuit. there is a wide range of voltages used by the meters I'm testing. Something is clearly conducting on this board when the voltage gets above about .3v but I don't see any diodes or transistors. The tweezers use AC sine wave and work perfectly. I'm using the 703s, agilent and a new SHS820X and none of them will read the caps except the tweezers.
-
I'm trying to save a file and pressing the hold/save key, I get a 'save failed' message. Doing something wrong?
Thanks
Jerry
-
I'm trying to save a file and pressing the hold/save key, I get a 'save failed' message. Doing something wrong?
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5632455/#msg5632455 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5632455/#msg5632455)
-
Firmware V1.5.5 has appeared, has anyone checked it?
-
V1.5.5 Version Upgrade details:
1. The measurement speed of AUTO has been optimized
-
Firmware V1.5.5 has appeared, has anyone checked it?
The icon for run mode is different and the trace seems to be less filtered at first glance, but I haven't recalibrated yet to see if that changes the jitter now shown. There is noticable glitching of the display when changing v\div and simply moving through the menu that wasn't there before. They didn't fix triggering slow signals being lost below 500ns and they didn't fix the cursor icon colour not changing to show which trace is selected or that cursors lose position if you change modes. I'm going back to previous firmware.
-
Auto is faster now. It struggles to detect at lower then 15hz.
-
The Single mode trigger bug is still present <=250ns. Anything you trigger in single mode at 250ns or faster won't trigger at the selecter trigger point. You need to scroll right a good deal (a few pages) to find the correct trigger point after the trigger. I'm amazed nobody has noticed this rather major bug - I wonder if it's only mine at this point!
https://youtube.com/shorts/XRGxF6oBQFs
-
The Single mode trigger bug is still present <=250ns. Anything you trigger in single mode at 250ns or faster won't trigger at the selecter trigger point. You need to scroll right a good deal (a few pages) to find the correct trigger point after the trigger. I'm amazed nobody has noticed this rather major bug - I wonder if it's only mine at this point!
And if you read the previous posts in the thread more carefully or search the topic?
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5664291/#msg5664291 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5664291/#msg5664291)
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5765033/#msg5765033 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5765033/#msg5765033)
-
The output settings got buggy in v1.5.5. Sometimes it jumps to the previous setting. The 5khz sine wave can sometimes be glitchy. Like the amplitude is jumping all over the place.
Overall it appears each firmware version is a small step forward and some steps back with new bugs. I wonder if they don't have enough unit testing to catch regressions.
-
I'm trying to save a file and pressing the hold/save key, I get a 'save failed' message. Doing something wrong?
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5632455/#msg5632455 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5632455/#msg5632455)
Format is removed on version 1.4.2 and FFT is added on that button. So if that is what you were referring to, I can't do a format. Maybe the latest firmware corrected it.
-
unless I am doing something wrong, the new firmware, 1.5.5? doesn't fit. No format button on the menus.
-
No format button on the menus.
You can restore factory settings, after it flash disk will be repaired.
-
I payed attention, that new menu appeared.
Menu -> SAMPLE: HD or PEAK.
Somebody knows, what does it mean?
-
Format is removed on version 1.4.2 and FFT is added on that button. So if that is what you were referring to, I can't do a format. Maybe the latest firmware corrected it.
1.4.2 / 1.5.5
menu -> MoreApps -> menu (ImgView) -> (There is nothing about Fn keys on the screen) F3 -> F3 (format)
-
1.4.2 / 1.5.5
menu -> MoreApps -> menu (ImgView) -> (There is nothing about Fn keys on the screen) F3 -> F3 (format)
This is in the style of Chinese logistics - hide the function important and warn others nothing about it! :-DD
-
Don't know how you found that menu. Just pressing function keys hoping for the best I guess. Thanks
p.s.: 1.5.6 is up there. Adds switchable Russian interface. Kak raz to, chto mne nuzhno.
-
Overall it appears each firmware version is a small step forward and some steps back with new bugs. I wonder if they don't have enough unit testing to catch regressions.
It's really true! :-//
What's the point of their new versions 1.5.6...1.5.7...1.5.8 if they don't fix old the gross bugs in the software? :palm:
-
Anyone got a link to ver 1.55 please?
-
Anyone got a link to ver 1.55 please?
1.55 - https://drive.google.com/file/d/1xgdgFe6GohxC1WyyIX2O0uyEkZHiOHiv/view
1.56 - https://drive.google.com/file/d/12Gxb3DFtqoraxpqkC3cRqKC9haMOEV1Y/view
-
Thank you.
-
Some information on the firmware update file format (ZTK):
16 bytes header:
0 to 3: file length - 16 (header length)
4 to 7: unknown, looks like 16 bit uint (bytes 6 and 7 always 0), maybe checksum
8 to 15: always "OSC7EF91"
starting at byte 16 is the firmware
The encryption looks like taking 8 byte blocks. It is not a real block cipher as statisctical analysis reveals, that the bytes
87 D0 A9 A6 1A D6 2A 78 decrypt to 0, when they are in the position 0 to 7 or 8 to 15 respectively
Simple XOR with byte swapping did not bring any usable result
edit: my assumption above, about the block cipher is probably wrong, as the 8 bytes above almost alway appear in the exact order.
The MCU supports DES, 3DES, AES in hardware, because of the 8 byte blocks, DES and 3DES are possible candidates
Yes, Firmware .ZTK is encrypted AES-128-ECB
Key: aff05338fa552bf2f2f05338fa552bf2 <- this is the wrong key
The key can decrypt and re-encrypt .ZTK and get an identical file, but after "unpacking" the firmware .ZTK is still XOR with a mask or function, or custom decode etc, but you can modify the byte, which could mean there is no CRC check?
decode_ztk.py:
from Crypto.Cipher import AES
import sys
KEY = bytes.fromhex("aff05338fa552bf2f2f05338fa552bf2")
def decrypt_ztk(infile, outfile):
with open(infile, "rb") as f:
data = f.read()
cipher = AES.new(KEY, AES.MODE_ECB)
decrypted = cipher.decrypt(data)
with open(outfile, "wb") as f:
f.write(decrypted)
print(f"[✓] ZTK decrypted → {outfile}")
if __name__ == "__main__":
if len(sys.argv) != 3:
print("Usage: decode_ztk.py input.ztk output.bin")
sys.exit(1)
decrypt_ztk(sys.argv[1], sys.argv[2])
python decode_ztk.py ZOYI-703S-FW-V156.ZTK decrypted.bin
encode_ztk.py:
from Crypto.Cipher import AES
import sys
KEY = bytes.fromhex("aff05338fa552bf2f2f05338fa552bf2")
def encrypt_bin(infile, outfile):
with open(infile, "rb") as f:
data = f.read()
if len(data) % 16 != 0:
raise ValueError("Input .bin size must be multiple of 16 (AES block size)")
cipher = AES.new(KEY, AES.MODE_ECB)
encrypted = cipher.encrypt(data)
with open(outfile, "wb") as f:
f.write(encrypted)
print(f"[✓] BIN encrypted → {outfile}")
if __name__ == "__main__":
if len(sys.argv) != 3:
print("Usage: encode_ztk.py input.bin output.ztk")
sys.exit(1)
encrypt_bin(sys.argv[1], sys.argv[2])
python encode_ztk.py decrypted_modified.bin patched.ZTK
-
User ajar171 hasn't logged into the forum for a month or more. I think he abandoned the custom firmware project.
lol, are you still waiting for your dad to get back from the shops when he ducked out to buy a pack of smokes? I am certain that not being active for a month could have far less drastic reasons than abandoning the project.
-
Reports on the mydigit.cn forum is a 906s is soon to be released. No specs yet
-
...My post was not for you, so you dont have to be so "kind". English is not my native language, so if my sentence sounded strange, yours written in Polish would probably sound strange too.
I wrote it to RedFox01 who quoted sjsr171 and will wait for an answer which will not come.
sorry mate, was just having fun. It wasn't language based, more of a country music theme.
-
is there a way to disable beeping on every function change in multimeter mode?
-
only for the oscilloscope mode, not the DMM-mode.
is there a way to disable beeping on every function change in multimeter mode?
-
Hi all...regards from polands. We have create application for zoyi 703s workiong with windows and working with OBS Studio.
Some screen is above:
[attach=1]
[attach=2]
For the transparent preview in obs we must add filter(chroma key) in obs to color black. Works as well.
I need some people for test it :)
-
Hi guys,
sorry for the long time away, my life got turned upside down because of some private issues.
I will try to pick up, from where I left off in the easter holidays, and also try to read and answer all the posts that I have missed.
-
only for the oscilloscope mode, not the DMM-mode.
is there a way to disable beeping on every function change in multimeter mode?
no, the beeper is directly controlled by the DMM chip. Turning it off is impossible in software, a beeping can be added in the scope mode (by a dirty hack), but then the DMM chip has to be powered on countinously, which just wastes power.
-
Yes, Firmware .ZTK is encrypted AES-128-ECB
Key: aff05338fa552bf2f2f05338fa552bf2 <- this is the wrong key
The key can decrypt and re-encrypt .ZTK and get an identical file, but after "unpacking" the firmware .ZTK is still XOR with a mask or function, or custom decode etc, but you can modify the byte, which could mean there is no CRC check?
I don't think its AES, the block size does not make any sense because "87 D0 A9 A6 1A D6 2A 78" is "00 00 00 00 00 00 00 00" decrypted, and that is only 8 bytes, where AES has a 16 byte block size. DES (and 3DES) has an 8 byte block, and is supported in HW by the MCU.
-
also there is no unpacking needed, the interrupt vector table can be clearly seen in the .ZTK file, it is just encrypted.
What keeps wondering me, is the .ZTK file size. The MCU used (on the PCB v2.2) has only 128k of flash memory, the update file is a multiple of that... Maybe they used different MCUs over the time of the production and have muliple firmware images in the update file?
-
It is possible, and what I managed to determine is that when you upload damaged firmware, a rescue mode is triggered, and a RAM/Firmware folder appears, about 600KB in size. You can manipulate GUI strings and replace them with others, as long as the byte size remains the same. I tried using Hashcat for testing, with my RTX 3060, the process would take around 4 days, or even up to 10 in some cases, but I’m not sure if I found the correct hashes.
-
My GPU is nowhere powerful enough to try a brute force attack (potato PC).
If you have the patience, you could try to DES decrypt (brute force) "87 D0 A9 A6 1A D6 2A 78", when it decrypts to "00 00 00 00 00 00 00 00", then we can try the key on the whole firmware. Brute force for 3DES would not make any sense.
The only interesting part of the firmware is the bootloader, the rest does not work properly anyway, and I don't know, if it is included in the update file. If the bootloader could be extracted from the update file, it would be possible to switch back and forth between firmwares.
If this is worth the time and effort (and also electrical power for your GPU) is up to you to decide. I personally don't need the firmware key or their bootloader.
-
If the bootloader could be extracted from the update file, it would be possible to switch back and forth between firmwares.
It would be great if you or someone else could do it.
-
Even if they are only using DES, searching the whole keyspace with an RTX3090 would take:
2^56 / 2787.3 MH/s = 299,2 days
An RTX4090 would need maximum 132 days and an RTX5090 91,6 days
On average you can find the key in half of that time.
Again, I don't have the hardware to do this.
Glitching the MCU is a much more pratical way.
-
After upgrading to version 156, the following problem appeared. What to do now?
https://youtu.be/NlBVoNhc078?si=AUQjqd4prCf1g7au
The device does not respond to any buttons.
-
Open up the device, take the battery out. Wait 10 seconds, power it up with USB. Reinstall the firmware while on USB power. Shut down and add back the battery. Close up the device, and power it up.
After upgrading to version 156, the following problem appeared. What to do now?
https://youtu.be/NlBVoNhc078?si=AUQjqd4prCf1g7au
The device does not respond to any buttons.
-
Open up the device, take the battery out. Wait 10 seconds, power it up with USB. Reinstall the firmware while on USB power. Shut down and add back the battery. Close up the device, and power it up.
Thanks a lot! I will try this on Monday at the office. I'll let you know the result.
-
https://github.com/danielmiessler/SecLists (https://github.com/danielmiessler/SecLists)
https://github.com/brannondorsey/naive-hashcat/releases/download/data/rockyou.txt (https://github.com/brannondorsey/naive-hashcat/releases/download/data/rockyou.txt)
https://crackstation.net/crackstation-wordlist-password-cracking-dictionary.htm (https://crackstation.net/crackstation-wordlist-password-cracking-dictionary.htm)
https://weakpass.com/wordlist (https://weakpass.com/wordlist)
https://www.openwall.com/wordlists/ (https://www.openwall.com/wordlists/)
https://github.com/mamatb/OneWordlistToListThemAll (https://github.com/mamatb/OneWordlistToListThemAll)
https://www.wordlists.dev/ (https://www.wordlists.dev/)
https://github.com/berzerk0/Probable-Wordlists (https://github.com/berzerk0/Probable-Wordlists)
there are plenty of such sites, which have passwords, you just need to write a script, at the beginning you just need to make a simulation of what the file looks like as false ;)
-
My GPU is nowhere powerful enough to try a brute force attack (potato PC).
If you have the patience, you could try to DES decrypt (brute force) "87 D0 A9 A6 1A D6 2A 78", when it decrypts to "00 00 00 00 00 00 00 00", then we can try the key on the whole firmware. Brute force for 3DES would not make any sense.
The only interesting part of the firmware is the bootloader, the rest does not work properly anyway, and I don't know, if it is included in the update file. If the bootloader could be extracted from the update file, it would be possible to switch back and forth between firmwares.
If this is worth the time and effort (and also electrical power for your GPU) is up to you to decide. I personally don't need the firmware key or their bootloader.
Correct me if I'm wrong, and I'm not good at cryptography, but it looks like the firmware uses AES-128 ECB.
GUI strings are composed of 2 blocks of 8-byte text, which fits AES encryption of 16-byte blocks:
78AB4746A80960D9BC0EA4AAA0C1AB33 = V1.5.6
78AB4746A80960D9AB00A774EF908ADE = V1.5.5
4AB547A5A82E35E9E3D92B6C834E4553 = V1.4.9
DEB87BB419C5412A245324A3D3EEAA26 = V1.4.2
2559D4F1E3E538F3 = V1.2.7
F9F9925DFC02AC2A = V1.2.8
DC3BAA85DE1EAC82 = V1.2.9
1D86350CF252E100 = V1.3.2
7E4FA23AE0F63BFF = V1.3.8
1A88E8D2F13DD44F = V1.3.9
V1.5.6 -> 245324A3D3EEAA2605D715391355B184 = FFT-CH2
V1.5.6 -> E31C013FA78A6BF6ACC543221F240DFE = CHINESE
V1.5.6 -> A1216476C9CECE796213E066BE0C9AA4 = Trig Source
V1.5.6 -> F191D84F18D2E8BA04B2E45E70C092E0 = Auto Off
V1.5.6 -> 9C3C490A77764867E5A23F2EC5841BD4 = Vertical
V1.5.6 -> 7BADED8E6D51ED8B12863980A355D38F = Channel
V1.5.6 -> FB1C51E1D0067FA99C86610A32B71342 = 120min
V1.5.6 -> 255B944F2A9366A2B887A32F6DF3F1A2 = 60min
V1.5.6 -> DB501172D322F31588C157A38B4507F1 = 60s
V1.5.6 -> 74CBE8D46197A2D233A6AB203F4C1557 = Version
V1.5.6 -> 140D8ED0EAF857F595B67DE8D060C15E = H and V
V1.5.6 -> E58074BBF918A3CA3BC9DC9D91B54466 = Uart
V1.5.6 -> 0982A1DBDBC9F3CF2C2D21B5D447A399 = OutPut
V1.5.6 -> D92BC62B312C1AC10476D4C76E89D263 = OFF
V1.5.6 -> 37367548364C4543D9199DD3C281E0E6 = ON
V1.5.6 -> 2D9F547C45BBF8F11F8438E6DE98F02D = language
V1.5.6 -> 47EA7D7161DAB7C41883CAA500BEB7C5 = Курс
V1.5.6 -> 337C7637621A198027A939A074F461ED = Hopm
V1.5.6 -> 36BE9B7685328028C37E3BB7BCED81BE = Настр
V1.5.6 -> E34ABBF74FE95B18F5DDA59A557BBF40 = Mode
V1.5.6 -> E8F579BA180CE3A97DD97F7C2608296E = ting
-
test on wrong key which was above, first change to hex to test raw
Artery chips in Zoyi 703s
Entropy 7.859423 bits per byte.
Optimum compression would reduce the size of this 696368 byte file by 1 percent.
Chi square distribution for 696368 samples is 230456.93, and randomly would exceed this value less than 0.01 percent of the times.
t Arithmetic mean value of data bytes is 127.4196 (127.5 = random).
Monte Carlo value for Pi is 3.137625904 (error 0.13 percent).
Serial correlation coefficient is -0.033368 (totally uncorrelated= 0.0).
-
Just do a statistical analysis of the Zoyi file and an other STM32 firmware encrypted with DES-ECB (8 byte block) and AES-ECB (16 byte block). You should always start witch statistics, when you are up against an unknown file.
You can clearly see the block size of the Zoyi encryption. Also the block "14 E9 50 27 CD 1E 18 38" keeps repeating in the vector table of the FW1.5.6 giving you a hint about the block size of the cypher.
This is not a password hash, you want to decrypt a file.
Anyway, if you can successfully decrypt the file, after removing the 16byte header, there must be "00 00 00 00 00 00 00 00" at the address 0x20. Also in the interrupt vector table every fourth byte should be 0x08 (eg. at addresses 0x03, 0x07, 0x0B, 0x0F, 0x33, 0x37, 0x3B, 0x3F, and so on), just look at the vector table in the documentation of the ARM CPU.
-
Anyone got an idea why I'm running into this issue? I've got the ZT-703S, currently on version 1.39, but when trying to update to 1.55 or 1.56, there doesn't seem to be enough storage available for the update file. Looking at their file sizes, the 1.39 file is 554 kb and the later ones are 681 kb. There aren't any other files such as screenshots on the device ...
-
Anyone got an idea why I'm running into this issue? I've got the ZT-703S, currently on version 1.39, but when trying to update to 1.55 or 1.56, there doesn't seem to be enough storage available for the update file. Looking at their file sizes, the 1.39 file is 554 kb and the later ones are 681 kb. There aren't any other files such as screenshots on the device ...
Already addressed earlier in the thread. In the menus, chose to format the storage first, then reboot to USB firmware update mode and it will work.
-
Anyone got an idea why I'm running into this issue? I've got the ZT-703S, currently on version 1.39, but when trying to update to 1.55 or 1.56, there doesn't seem to be enough storage available for the update file. Looking at their file sizes, the 1.39 file is 554 kb and the later ones are 681 kb. There aren't any other files such as screenshots on the device ...
Or restore default settings in menu.
-
Open up the device, take the battery out. Wait 10 seconds, power it up with USB. Reinstall the firmware while on USB power. Shut down and add back the battery. Close up the device, and power it up.
After upgrading to version 156, the following problem appeared. What to do now?
https://youtu.be/NlBVoNhc078?si=AUQjqd4prCf1g7au
The device does not respond to any buttons.
Unfortunately, nothing worked. I pulled out the battery, connected the USB cable from the computer. The computer did not see the device. When turning on the power, the Zoyi screensaver starts blinking endlessly on the device again. I sent the message to the Zoyi's support, but I'm not sure they will reply...
-
I pulled out the battery, connected the USB cable from the computer. The computer did not see the device.
Remove the battery and let the device lie in this form for 10 minutes instead of 10 seconds. Then reconnect to the USB.
-
I pulled out the battery, connected the USB cable from the computer. The computer did not see the device.
Remove the battery and let the device lie in this form for 10 minutes instead of 10 seconds. Then reconnect to the USB.
No result. The device lay on the table for a couple of hours without a battery. When connected via USB, the device is not detected and when the power is turned on, the ZOYI blinks. I think the bootloader has crashed. And without some kind of intervention in the flash memory, this cannot be done. But I do not understand anything about this... Although, perhaps, there is some special combination of buttons when turning on, which restores the default boot?...
-
Try: battery out. Press F1+On button and then insert the USB-C power. Hopefully, the scope/DMM starts up and gives you an opportunity to flash firmware.
-
Try: battery out. Press F1+On button and then insert the USB-C power. Hopefully, the scope/DMM starts up and gives you an opportunity to flash firmware.
Yes!!! This helped! Thank you very much!!! :-+ :-+ :-+
-
Good afternoon. Help me identify the charge controller in the zoyi 703s. I was on charge while working with an oscilloscope. I touched the power diode of the unit I was repairing. Through the ground of the oscilloscope - the charger wire, to the ground of the network, the zoyi 703s burned out. It stopped charging. Charge controller 4086B. I can't find any description of this controller. Help me find an analogue.
-
Good afternoon. Help me identify the charge controller in the zoyi 703s. I was on charge while working with an oscilloscope. I touched the power diode of the unit I was repairing. Through the ground of the oscilloscope - the charger wire, to the ground of the network, the zoyi 703s burned out. It stopped charging. Charge controller 4086B. I can't find any description of this controller. Help me find an analogue.
https://www.alldatasheet.com/datasheet-pdf/pdf/1152028/HMSEMI/HM4086.html (https://www.alldatasheet.com/datasheet-pdf/pdf/1152028/HMSEMI/HM4086.html)
HM4086B but in chinese
-
Thank you. But it seems to me that there is a second wiring here. Tomorrow I will try to draw and identify the power pins.
-
It seems that Zotek has already built another device, it is available on the market as Aneng AOS04 and Winapex 810B, Winapex is a sub-brand of Tooltop, probably in a while they will release a Zoyi ZT-704S, I believe that our ZT-703S must have already fallen into oblivion and we will continue to face the problems, at least this time I learned my lesson, I have the 702s and bought the 703s, I will not buy the 704.
-
It seems that Zotek has already built another device, it is available on the market as Aneng AOS04 and Winapex 810B, Winapex is a sub-brand of Tooltop, probably in a while they will release a Zoyi ZT-704S, I believe that our ZT-703S must have already fallen into oblivion and we will continue to face the problems, at least this time I learned my lesson, I have the 702s and bought the 703s, I will not buy the 704.
I don't think, that this meter is a successor to the ZT703. It is worse in every technical spec: single channel, 10MHz bandwidth, 48MSPS, 9999 count DMM.
Also they have square wave coming out of the power outlets at Aneng... :-DD
-
The UI is completely different. Maybe they restart another line of models with a better base to build off.
-
The specs of the AOS04 is very similar to the ZT-702S.
That together with the different UI suggests that it's not
made by Zoyi/Zotek. Also, there a separate thread about
this DSO/DMM:
https://www.eevblog.com/forum/testgear/new-dmmdso-aneng-aos04-1ch-10mhz50msps-(march-2025) (https://www.eevblog.com/forum/testgear/new-dmmdso-aneng-aos04-1ch-10mhz50msps-(march-2025))
-
But it seems to me that there is a second wiring here.
No wonder. Above was wrong hint.
Your chip is MicrOne ME4086B.
https://datasheet4u.com/pdf-down/M/E/4/ME4086-Microne.pdf
-
Tell me. has anyone managed to install the new firmware ZOYI-703S-FW-V156.ZTK?
Tell us how to do it.
-
The specs of the AOS04 is very similar to the ZT-702S.
That together with the different UI suggests that it's not
made by Zoyi/Zotek. Also, there a separate thread about
this DSO/DMM:
https://www.eevblog.com/forum/testgear/new-dmmdso-aneng-aos04-1ch-10mhz50msps-(march-2025) (https://www.eevblog.com/forum/testgear/new-dmmdso-aneng-aos04-1ch-10mhz50msps-(march-2025))
Actually your analysis makes perfect sense, it may be a new line, but I also got the feeling that it is not manufactured by Zotek, I have seen this interface on one of those cheaper devices, thanks for the link, I will read it now.
-
Tell me. has anyone managed to install the new firmware ZOYI-703S-FW-V156.ZTK?
Tell us how to do it.
Turn on the device while holding down the F1 key, it will display information with the ZOYI logo and the words "USB: Disk Driver", just connect the USB cable and you will see a kind of flash drive on the computer, drag the .ZTK file to the firmware folder on the drive that was mounted and wait for the device to update.
-
Yes, that's it. The wiring of the chip is the same as in the diagram. Thanks.
-
Just a quick update:
- USB-MSC works again (after I broke it |O)
- logging to flash works (also saves min/max, when averaging is active)
- averaging works
- envelope (min/max) display added (can be switched off), when the averaging is switched on
Now I have to make a bootlader and a startup file, because the firmware is already bigger, than the 128k flash of the MCU... >:(
-
Just a quick update:
- USB-MSC works again (after I broke it |O)
- logging to flash works (also saves min/max, when averaging is active)
- averaging works
- envelope (min/max) display added (can be switched off), when the averaging is switched on
Now I have to make a bootlader and a startup file, because the firmware is already bigger, than the 128k flash of the MCU... >:(
Great news! Since you are already planning to write your own bootloader and firmware, you might want to consider upgrading your MCU to the STM32H743VIT6 ;) It gives you significantly more flash (2MB vs 128kb), RAM and performance, and is probably compatible with STM32H7B0VB peripherals? :)
-
Just a quick update:
- USB-MSC works again (after I broke it |O)
- logging to flash works (also saves min/max, when averaging is active)
- averaging works
- envelope (min/max) display added (can be switched off), when the averaging is switched on
Now I have to make a bootlader and a startup file, because the firmware is already bigger, than the 128k flash of the MCU... >:(
just great! cant wait until you have the first proper version available. let us know how we can help!
cheers from hamburg
max
-
Great news! Since you are already planning to write your own bootloader and firmware, you might want to consider upgrading your MCU to the STM32H743VIT6 ;) It gives you significantly more flash (2MB vs 128kb), RAM and performance, and is probably compatible with STM32H7B0VB peripherals? :)
Sure, that would be an option, I will probably even do it for my meter, but not everybody wants to replace a 100 pin MCU in their meter. The firmware should work on a stock v2.2 PCB as it is and I am not keen on selling upgraded ZT-703s.
Maybe Dave would like to sell EEVblog ZT-703+ meters with a powerful MCU ;)
Anyway, the firmware has to be split between the internal and the external flash, at startup the external flash has to be copied to RAM.
Lots of work, because Zoyi cheaped out on the MCU...
-
i would offer replacing that chip if anyone needs help in the european area. its around 11€..
-
i would offer replacing that chip if anyone needs help in the european area. its around 11€..
A properly sized MCU would sure save me a lot of work (that could be spent on additional features and not on a custom bootloader). The core of the STM32H743 is even 200MHz faster, that chip is pretty powerful.
I cannot decide this myself, please post your opinions here.
-
The firmware should work on a stock v2.2 PCB as it is
That's right!
-
Or restore default settings in menu.
didn't work for me
-
Tell me. has anyone managed to install the new firmware ZOYI-703S-FW-V156.ZTK?
Tell us how to do it.
1. device turned off. push F1 and then power, connect to PC, upload new firmware to firmware folder
2. device turned on. scope mode - menu - right, right - F3 (USB) - connect to PC, upload new firmware to firmware folder
3. not enough space on internal drive to upload the firmware
device turned on. scope mode - menu - left - F1 (more apps) - imgview (enter with menu button) - any F1-F4 (menu usb|delete|format|exit appears) - F3 (format). after format completed push mode to exit app, turn off, and go to p.1 or p.2 - internal drive should be empty and have enough space
-
i would offer replacing that chip if anyone needs help in the european area. its around 11€..
A properly sized MCU would sure save me a lot of work (that could be spent on additional features and not on a custom bootloader). The core of the STM32H743 is even 200MHz faster, that chip is pretty powerful.
I cannot decide this myself, please post your opinions here.
i prefer replacing the mcu than brick my original mcu
-
A properly sized MCU would sure save me a lot of work ...
Part of the fun of programming on these devices and retro computers is learning and proving what can be done with limited resources. (Look at some of the amazing games they are still making for an Atari 2600, 50 years after release putting the original versions to shame). Too much code / compilers today just assumes unlimited storage, bandwidth and CPU power, and thus we get very bloated software across phones and computers that constantly require hardware updates to keep up.
An ability to get something done and "fit" in the confines of some particular device definitely something many can't do. I wish you the best on your efforts here to make it all work!
-
Part of the fun of programming on these devices and retro computers is learning and proving what can be done with limited resources. (Look at some of the amazing games they are still making for an Atari 2600, 50 years after release putting the original versions to shame). Too much code / compilers today just assumes unlimited storage, bandwidth and CPU power, and thus we get very bloated software across phones and computers that constantly require hardware updates to keep up.
An ability to get something done and "fit" in the confines of some particular device definitely something many can't do. I wish you the best on your efforts here to make it all work!
Sure it is fun to reach and work around the limits of the hardware, and 100MSPS dual channel oscilloscope is at the limit of an MCU without the help of an FPGA.
The HAL code of CumbeMX is very bloated, eating up a lot of flash, but I am not willing to go the bare metal programming route, just to rewrite everything for a different MCU later. So bloated CubeMX it is. Most of the flash space is eaten up by the fonts |O
My solution to the problem is using the external SPI flash as firmware storage, and copying everything from there into RAM at boot time. This way I have about 900kB of firmware space, that should be plenty enough.
This is a compromise, and this way the bootloader is only a sort-of bootloader, which has the limitation of not working anymore if a firmware update gets messed up (ex. power loss while updating).
In the unlikely case of a messed up firmware update, only recovery by JTAG is possible. This should not be a huge problem, because installing the firmware for the first time will require a JTAG adapter (at least an ST-Link) anyway.
The bigger MCU is still very tempting, because of the 480Mhz f_max of the core. I would just love to tell everyone, that my DMMs CPU is running at 400MHz ;) My first computer (C64) was running 400x slower....
-
My first computer (C64) was running 400x slower....
Just don't make the screen light blue on dark blue and we're okay :) I'd take cyan on white (VIC20) first!
Joking aside, for the font size issue, could you RLE that and then expand it on copy to RAM like you're planning? Add a second to boot up or something?
-
Just don't make the screen light blue on dark blue and we're okay :) I'd take cyan on white (VIC20) first!
Joking aside, for the font size issue, could you RLE that and then expand it on copy to RAM like you're planning? Add a second to boot up or something?
The screen will be yellow on light blue, so absolutely unreadable :P
At the moment I am more concentrated on making the features work. My normal workflow is getting stuff to work, and optimize for size or speed later, maybe it's wrong, but that is the way I like it :)
The fonts are already only 4 bits/pixel, I would estimate another 40% size reduction with RLE. I have all the memory I need for now, so I will save RLE for later :)
-
Rant on
Words can not describe how much I hate the intel hex file format.
Rant off
sorted it out. what a waste of time...
-
Tell me. has anyone managed to install the new firmware ZOYI-703S-FW-V156.ZTK?
Tell us how to do it.
I just wanted to add, if I may, that I upgraded from 1.42(6?) to 1.55 first, then to 1.56 and had no issues. Worked on the first try. Am wondering if this may have helped?
I do not have my HW version available, as I have never opened up my unit.
-
Has anyone tried the new firmware? Are there any easily reproducible and demonstrable issues? From what I understand, ZOYI is unaware of what's going on and is requesting video evidence.
-
Thanks guys! It's updating now. Fingers crossed :)
-
The Single mode trigger bug is still present <=250ns. Anything you trigger in single mode at 250ns or faster won't trigger at the selecter trigger point. You need to scroll right a good deal (a few pages) to find the correct trigger point after the trigger. I'm amazed nobody has noticed this rather major bug - I wonder if it's only mine at this point!
I contacted them about this issue many times through emails and even through their youtube channel, and they always write (after a VERY LONG delay) that they have high quality products and value our feedback very much, but now it's v1.5.6, more than a half of a year passed after I bought this device, and I still don't see any positive changes in the firmware, all the bugs are the same. What's even worse, they don't publish a detailed log of changes, so we cannot know what new bugs were added in the new version :( I don't understand their approach. Evidently the guys who developed this device are not stupid because a stupid guy cannot develop such a device. Still I don't understand is it really difficult to revise the bugs that were already found and verified by many users many months ago... instead of fixing bugs they changed the running icon to a green one and added a clumsy Russian translation. It's like software development in the beginning of the 2000s, if you are too lazy to add new features, but want to release a new version, just change icons and that's enough :)
I wonder what firmware version is considered the most reliable at the moment?
-
I wonder what firmware version is considered the most reliable at the moment?
There is no reliable firmware for this product! :( All versions have errors and bugs. I use version 1.3.8
For those people who choose the quick operation of the "Auto", version 1.3.2 is more suitable.
-
Has anybody encountered the following error with a ZT-702S:
When range switching up from 200mV to 500mV (relay is clicking) it sometimes shows grossly distorted waveforms going up down in range fixes it after 1-5 cycles, again on the switching up. Restarting the device also fixes it.
This shows the distortion sampling from the calibration output:
[attachimg=1]
The device is on the latest firmware (58).
Any ideas what could be wrong?
-
Has anybody encountered the following error with a ZT-702S:
My 703 once had a strange signal distortion on channel 2, when the signal dropped to -infinity periodically with no reason. The only thing that helped was complete reset to defaults and recalibration. After I recalibrated the device, I've never seen this issue again. So I don't know where it came from and were it has gone to :)
-
I've been playing with the 1.5.6 version and I found that the auto range works really fast in comparison with 1.4.x versions and it works correctly. Most signals are found within 1-3 seconds. I tested it with the ESP32 signal generator (up to 40 Mhz square and 1Mhz sine) and also with a GM328A generator. It does have difficulties with low frequency but I was able to autorange 10 herz from the second try and it took around 10 seconds. Sometimes it takes 3-4 tries to autorange 10-20Hz. Stable but slow autorange works from 30Hz and above. The autorange speed increases as the frequency increases. 500 Hz takes 3 seconds and 1+kHz is around 1 second or less. I don't have a professional signal generator so I tested with simple devices that I have. If you have different experience, please share your opinion, but I think it is more usable than it was before.
I also found that loosing the trigger at 250ns and below takes place only with frequency <= 80kHz. As I see it, 90kHz and above can be seen at 250ns with the correct trigger place. Please check if it's the same on your devices.
This bug is rather annoying and I want to make a video showing this bug and send it to Zoyi support and also upload it to youtube and send them the link. If you have other serious issues with the 1.5.6 firmware, let me know, and I will add it to my video if I am able to reproduce it.
-
Has anybody encountered the following error with a ZT-702S:
My 703 once had a strange signal distortion on channel 2, when the signal dropped to -infinity periodically with no reason. The only thing that helped was complete reset to defaults and recalibration. After I recalibrated the device, I've never seen this issue again. So I don't know where it came from and were it has gone to :)
I already tried this - unfortunately it did not help.
-
i would offer replacing that chip if anyone needs help in the european area. its around 11€..
A properly sized MCU would sure save me a lot of work (that could be spent on additional features and not on a custom bootloader). The core of the STM32H743 is even 200MHz faster, that chip is pretty powerful.
I cannot decide this myself, please post your opinions here.
I also prefer more powerful MCU.
-
I have already ordered the more powerful MCU, that RedFox01 suggested.
I only took a quick look, but they seem to be pin compatible.
Edit: the STM32H743VIT is not compatible with the ZT703 v2.2 PCB! It can be made to work, but the MSB of the green color is on the wrong pin. Also the "function generator" is a lost cause, it also on a wrong pin. I should have checked this first. All other compatible MCUs have the same f_max, so there is no advantage of replacing the MCU.
Got screenshots working, finally no more photos with my potato phone :)
-
For all the bugs this meeter has, I am amazed how well it was calibrated at the factory. I have a number of .1%, 10ppm resistors and it reads them nearly perfectly. The one issue I have though, is you need to have it in the correct range when you use the "Rel" function. I don't remember this being an issue with any other meters I have. For instance, if I null the meter and then try to read a 1k resistor, it is out of range. You need to select the correct range for the DUT and then hit "rel".
Jerry
-
You need to select the correct range for the DUT and then hit "rel".
Jerry
most Fluke are like this too and it is the same for the min/max feature..
-
Video:
https://youtu.be/pOL6pB-g_70
Firmware V1.5.6.
200 ms realtime picture shows that the testing assembly works perfectly.
reduce time to 100 ms.
test auto/normal/single trigger mode - all of them show garbage or unreliable. Single mode is slightly better, but skips every second button press.
Maybe I do something wrong, but it feels that the trigger system is very unreliable as it shows different results (or does not show anything) with every button pressing.
Your comments if it's OK or not are welcome.
-
At a scan rate of 200 ms or slower, synchronization does not work. Is this the case for everyone?
FW 1.5.6.
-
Only if the frequency is below 85khz do I lose sync at any time division smaller than 500ns.
-
thanks!
looking forward to your firmware :)
-
A properly sized MCU would sure save me a lot of work ...
Part of the fun of programming on these devices and retro computers is learning and proving what can be done with limited resources. (Look at some of the amazing games they are still making for an Atari 2600, 50 years after release putting the original versions to shame). Too much code / compilers today just assumes unlimited storage, bandwidth and CPU power, and thus we get very bloated software across phones and computers that constantly require hardware updates to keep up.
An ability to get something done and "fit" in the confines of some particular device definitely something many can't do. I wish you the best on your efforts here to make it all work!
Sure but out intention is to make a good firmware and make this device works the best, it is not worth losing thousands of hours and not having original recources of bootloader and so on
-
New version :)
[attach=1]
-
Sure but out intention is to make a good firmware and make this device works the best, it is not worth losing thousands of hours and not having original recources of bootloader and so on
Please don't get me wrong, I am thankful for any support I get :)
The first version of the bootloader is done and working now. It is not perfect, but it works, and it is a start.
It is just bad luck, that the more powerful MCU won't work as-is with the PCB. A PCB respin (only 2-3 pin changes needed) would make the more powerful MCU work, maybe Zoyi will consider it (hope dies last, as it is said in Germany ;D). With some bodge wires, it would work even with the v2.2 PCB, but I am too lazy to do it.
Good news: RTD (Pt100, Pt500, Pt1000, Pt2000) measurement is working
Edit: 4-20mA mode is also working now
-
It is possible, and what I managed to determine is that when you upload damaged firmware, a rescue mode is triggered, and a RAM/Firmware folder appears, about 600KB in size. You can manipulate GUI strings and replace them with others, as long as the byte size remains the same. I tried using Hashcat for testing, with my RTX 3060, the process would take around 4 days, or even up to 10 in some cases, but I’m not sure if I found the correct hashes.
@RedFox01: can you please explain step-by-step, how you got into the rescue mode?
-
New version :)
(Attachment Link)
I'm in, even without network, I love this quirky oscilloscope/multimeter!
-
Because I got asked, my progress (and some preliminary documentation) can be found here:
https://github.com/kmikl/open-zt703
-
Because I got asked, my progress (and some preliminary documentation) can be found here:
https://github.com/kmikl/open-zt703
I don't know how to program the STM32, but I hope that one of the good points of your work is that the original Zotek developers will learn your code and do the same in their original firmware :) Copy and paste is what they can do really well :)
-
I don't know how to program the STM32, but I hope that one of the good points of your work is that the original Zotek developers will learn your code and do the same in their original firmware :) Copy and paste is what they can do really well :)
They cannot use my code for the ZT703 as-is, because it is already bigger, then size of the flash inside the MCU (and I did not really touch the scope part yet, only did some testing...). Beacuse of their bad design decisions and the stupid firmware encryption, they are stuck with the 128k of flash. I do not want any feature or usability compromises, just to fit in the 128k of flash available.
I also don't want any nice looking MSPS numbers, and push the ADC far out of its specs for marketing, just to get way off voltage readings from the ADC in exchange.
-
I don't know how to program the STM32, but I hope that one of the good points of your work is that the original Zotek developers will learn your code and do the same in their original firmware :) Copy and paste is what they can do really well :)
They cannot use my code for the ZT703 as-is, because it is already bigger, then size of the flash inside the MCU (and I did not really touch the scope part yet, only did some testing...). Beacuse of their bad design decisions and the stupid firmware encryption, they are stuck with the 128k of flash. I do not want any feature or usability compromises, just to fit in the 128k of flash available.
I also don't want any nice looking MSPS numbers, and push the ADC far out of its specs for marketing, just to get way off voltage readings from the ADC in exchange.
as i said before, just a great project! will follow closely :) guess its time to find my stlink
-
Because I got asked, my progress (and some preliminary documentation) can be found here:
https://github.com/kmikl/open-zt703
You refused to add "switchable analog scale (bargraph)" for lack of flash memory size?
-
They cannot use my code for the ZT703 as-is, because it is already bigger, then size of the flash inside the MCU (and I did not really touch the scope part yet, only did some testing...). Beacuse of their bad design decisions and the stupid firmware encryption, they are stuck with the 128k of flash. I do not want any feature or usability compromises, just to fit in the 128k of flash available.
So have you added additional physical memory, or saved some of the available memory by getting rid of the encryption and other useless and ugly-designed code?
-
Because I got asked, my progress (and some preliminary documentation) can be found here:
https://github.com/kmikl/open-zt703
You refused to add "switchable analog scale (bargraph)" for lack of flash memory size?
No, I messed up there. I did not properly decode the bargraph data sent from the DMM chip to the MCU, and since I don't have the stock firmware anymore I can't do it. The "needle" position can can be calculated from the measured value too, but the bargraph data would have been the quick, easy and code size efficient way.
This feature is postponed for now, but You are correct, the strikethrough was wrong there. Corrected it.
Thermocouple mode, saving/recalling settings, and limits are the priority, so we can do a beta testing and bugfixing round as soon as possible.
-
So have you added additional physical memory, or saved some of the available memory by getting rid of the encryption and other useless and ugly-designed code?
The memory was on the board the whole time, it is the external SPI flash. Zoyi just cannot use it, beacuse of their design decisions, using the external flash would break the security. The MCU is perfectly enough, for what they wanted to achive and even for my firmware.
I would be glad to pay 5-10€ more for a faster MCU with more flash directly from Zoyi, even more, if they would put a big-ish (with at least 64kpoints/channel memory) FPGA between the ADC and MCU :)
I know, that they are competing in a tough market, but I would really like a scopemeter, with this housing, a big MCU and an FPGA and the possibility to add functions to the firmware, that I need myself.
Edit: there is an LCD-screen on the market in China, with the same form factor, but double the resolution. Sadly the board v2.2 does not support it as-is (would work with some bodge wires).
So to clarify, how my stuff works:
- the meter is powered on
- the bootloader in the internal flash verifies the checksum of the firmware in the external flash
- if the checksum is OK, the firmware from the external flash gets copied into the internal RAM
- execution is handed over to the firmware in RAM
I think their goal was, to stop other chinese manufacturers from copying their design easily, and not to hinder anyone making an alternative firmware for their meter. As far as I know, this goal is fulfilled :)
-
If someone would design an adapter PCB from TQFP-100 to a BGA variant of the STM32H743 plus an FPGA and also add 4 solder points for an additional SPI port (for the better LCD), we could make the best little scopemeter on the world :)
-
I would be glad to pay 5-10€ more for a faster MCU with more flash directly from Zoyi, even more, if they would put a big-ish (with at least 64kpoints/channel memory) FPGA between the ADC and MCU :)
As far as I know, Zotek is reading this thread and your dreams can become reality some day, but most likely they will abandon 703 and make 704 because it's easier for them to make a new model rather than fix bugs in old models. But this approach is not perfect because new 704 will surely have new bugs and the current story with good hardware and bad firmware will take place again. You will have to make reverse engineering from the beginning for the new hardware :) I think a great way of 703 development would be if you could cooperate with Zotek and become their consultant to fix existing bugs and make the best out of current 703 hardware using the official firmware, but they don't seem to have much interest in firmware development and bugs fixing, so it just goes as it goes.
I can understand why they encrypted the firmware, because Fnirsi 2C53T/2C23T is their direct competitor that has a lot of firmware bugs too, so it makes some sense to protect some good ideas from being stolen by the competitors. But that would be OK if the firmware was perfect and everyone would want to steal it, but now I'm not sure if Zoyi should steal the code from Fnirsi or Fnirsi should steal the code from Zoyi :) When I decided which one to buy, I choose Zoyi just because it had less firmware bugs at that moment, but now I'm not sure if it was the correct choice :) At the other hand, Fnirsi has the same horrible update approach, they make a new model every year and abandon previous models, leaving their users with lots of unfixed bugs that will never be fixed. This is why I will never buy Fnirsi hardware.
-
At a scan rate of 200 ms or slower, synchronization does not work. Is this the case for everyone?
FW 1.5.6.
I made a short video about this, please see. Have you met this phenomenon?
https://youtube.com/shorts/Cta1GJWkTtw?si=vsH-_A4qYfZAGS2O
-
I would be glad to pay 5-10€ more for a faster MCU with more flash directly from Zoyi, even more, if they would put a big-ish (with at least 64kpoints/channel memory) FPGA between the ADC and MCU :)
As far as I know, Zotek is reading this thread and your dreams can become reality some day, but most likely they will abandon 703 and make 704 because it's easier for them to make a new model rather than fix bugs in old models. But this approach is not perfect because new 704 will surely have new bugs and the current story with good hardware and bad firmware will take place again. You will have to make reverse engineering from the beginning for the new hardware :) I think a great way of 703 development would be if you could cooperate with Zotek and become their consultant to fix existing bugs and make the best out of current 703 hardware using the official firmware, but they don't seem to have much interest in firmware development and bugs fixing, so it just goes as it goes.
I can understand why they encrypted the firmware, because Fnirsi 2C53T/2C23T is their direct competitor that has a lot of firmware bugs too, so it makes some sense to protect some good ideas from being stolen by the competitors. But that would be OK if the firmware was perfect and everyone would want to steal it, but now I'm not sure if Zoyi should steal the code from Fnirsi or Fnirsi should steal the code from Zoyi :) When I decided which one to buy, I choose Zoyi just because it had less firmware bugs at that moment, but now I'm not sure if it was the correct choice :) At the other hand, Fnirsi has the same horrible update approach, they make a new model every year and abandon previous models, leaving their users with lots of unfixed bugs that will never be fixed. This is why I will never buy Fnirsi hardware.
Sure, the ZT703 won't get any hardware upgrades from Zoyi, a new hardware would mean a new model number, and that is absolutely correct. The hardware of the 703 is pretty good for the price, they have just limited themself with the 128k of flash, but at least they are using a genuine ST MCU. I am not fixing their bugs, because without seeing their code, I think the scope part of the stock firmware is fundamentally broken and unfixable with 128k of flash. I would be more then happy to cooperate with them to make my dream scopemeter :) I think they should make a cheap scopemeter as a competition to Fnirsi, and also make a more expensive, but capable one. Seeing the hardware of the 703, they are more, then capable of designing good hardware for a good price, so why not make a "professional" scopemeter?
I also have no problem with them encrypting their software. It's their software, so they should protect it, as good as they can. I had very bad experience with Fnirsi, Zoyi is at least trying to fix some of the bugs, Fnirsi abandonded all the stuff I bought from them in 6-12 months. I am not buying anything from Fnirsi anymore. If Fnirsi is the direct competition for Zoyi, then IMO Zoyi has already won :)
I also bought a scopemeter from Owon, which of course works, but the hardware is also much more capable (and costs a lot more), so no surprises there.
I really would like to make the 703 as capable as the hardware allows, becuse the overall design is nice, the MCU is good enough for the task and also why not :D
Here goes my wishlist for the 703 version 2:
- high resolution display (3.5", 640x480), no touch
- at least 400MHz MCU, with minimum 1MB of flash
- a big-ish FPGA, with lots of RAM (say Gowin GW2AR-18 <-- could do 32MPoints/channel >:D)
- original ADC from Analog or TI
-
I think they should make a cheap scopemeter as a competition to Fnirsi, and also make a more expensive, but capable one. Seeing the hardware of the 703, they are more, then capable of designing good hardware for a good price, so why not make a "professional" scopemeter?
Most likely they understand that there is some kind of price limit that divides 2 kinds of products: the cheaper "toys" for arduino amateurs that is also suitable for fast and approximate diagnostics and the expensive professional stuff for everything else. Not many users would want to buy something in between, that is not as cheap as 703 and just a bit less expensive than simple models from professional oscilloscope manufacturer that are quality proven and have reliable support and long time upgrades. Besides, there appear producers that already try to find their place in that middle, for example ZEEWEII DSO3D12, but it's more expensive and evidently many people still prefer to buy a cheaper 703 even if it has less powerful hardware.
I agree that Fnirsi is not worth buying until they change their update policy, you know it and I know it, but there are thousands of users who don't know it. Fnirsi often offers neat-looking colorful GUI in their devices and it attracts customers even if it is a set of lags and bugs. Besides, Fnirsi has a rather aggressive marketing spendings. I know that they send a lot of free devices to popular youtube bloggers in exchange for a video review (sometimes they are fair and sometimes they are not), so I think many people still buy Fnirsi even if their stuff is full of bugs. A few month ago I wanted to buy a transistor tester, I found LCR-P1 made by Fnirsi, and luckily I saw a review where a user tested diodes and that fnirsi showed all of them in reverse polarity! Other users confirmed that issue. Thanks to them I saved some money and bought an old gm328 which is twice cheaper and has most features of LCR-P1 but makes the measurements correctly :)
640x480 would be too cool for this kind of device. It requires more mcu resources, more memory and more money :) I think we can live with 320x240 fine, but what I hate in the current 703 implementation is that we cannot zoom to the top/bottom of the signal to see it in detail because the 0V level cannot be moved higher or below the visible area of the screen, so if we have a high-amplitude signal, we just can't zoom to its peaks to see what happens there. I would also change the way the measurements are shown because they cover almost the whole bottom half of the screen. I think Fnirsi solution is much better - they show the measurements on a transparent background, so the signal and the measurements can be printed on the same part of the screen and it's easy to read both because the text and the graph have different colors. Other things, I think, look rather neat in zoyi 320x240 screen (I don't mention the buggy and non-working horizontal scroll bar that they still can't fix of course).
-
As for the quality hardware and firmware from a "cheap" manufacturer, just look at Rigol. They also started as a "cheap" company, and look at where they are now.
Strange menu of the Zoyi: I have completely ignored it, and have gone my own way
-
As for the quality hardware and firmware from a "cheap" manufacturer, just look at Rigol. They also started as a "cheap" company, and look at where they are now.
Rigol quickly understood that they should listen to the users and make them happy to become successful. Zotek has some difficulties with understanding this :) As far as I understand they do believe that their firmware is perfect and if some user is unhappy with the product quality it is because this user does something wrong :)
-
... I would also change the way the measurements are shown because they cover almost the whole bottom half of the screen. I think Fnirsi solution is much better - they show the measurements on a transparent background, so the signal and the measurements can be printed on the same part of the screen...
Actually, the owon has a great menu implementation where the screen "shrinks" to allow menu display along the bottom, then resumes full zoom after a timeout to give a larger display for observation. The menu is kind of like windows taskbar with autohide.
-
As far as I know, Zotek is reading this thread and your dreams can become reality some day, but most likely they will abandon 703 and make 704 because it's easier for them to make a new model rather than fix bugs in old models.
YOOOOOOHOOOOO @ ZOYI/ZOTEK
In the spirit of making things better, (And this is all I dare say, standing against the giants of this forum).
While I do understand that English is not a first language....
When you can, this is from Rev 1.56 FW.
-
Actually, the owon has a great menu implementation where the screen "shrinks" to allow menu display along the bottom, then resumes full zoom after a timeout to give a larger display for observation. The menu is kind of like windows taskbar with autohide.
This is exactly, where a more powerful MCU or an FPGA would come in handy. There are simply no resources left to do nice animations. The MCU has to "race the beam" of the LCD, to draw the whole screen in the blanking period, but a double framebuffer would eat up too much RAM. At the moment I have enough RAM to spare for double buffering, but I am not doing it, because I can draw the screen without screen tearing artefacts and I am saving up RAM for later.
Altough I must admit, that I can only draw the screen with every option (averaging, graph display, envelope display, logging) turned on, with the help of compiler optimisations. In debug mode (no optimisation), there is already screen tearing visible. This is a trade-off between code readability and speed, where I have favored readability...
Edit: finally got limits working properly
-
There are simply no resources left to do nice animations.
I'm strictly against any animations in such devices. I think all the power of the mcu should be used for useful tasks. For example, I noticed that turning on the on-screen measurements makes the work of the oscilloscope very slow and unstable (it can skip fast signals), so the device hardly has enough power to do the basic tasks that it should do. When I just bought this device I turned on 4 possible real-time measurements but now I disabled them all and enable them only rarely when they are really needed.
For Zoyi developers:
In this respect I want to ask Zotek engineers to make a button that can quickly enable and disable pre-selected realtime measurements. Now we have to press menu button to reach "Measure" submenu, then select 4 items, then watch the measurements, then go to that menu again, deselect the 4 measurements, and it really takes a lot of time. One button for it will save a lot of time. For example, some buttons are not assigned for a long-press action. Long press of "F4" could quickly turn on/off the cursors, and long press of "MODE" could turn on/off the measurements. This would be more quick and handy than doing it through menus.
-
@RedFox01: can you please explain step-by-step, how you got into the rescue mode?
Nothing special, the device simply works normally without the SPI chip, and a RAM/firmware mode is available via USB. Alternatively, if the firmware upgrade with the SPI chip fails (e.g. due to corrupted firmware), after three attempts an "update failed" message appears, and the device switches to the RAM/firmware mode, which is most likely part of the bootloader. Of course, the MCU has RDP enabled, so the bootloader cannot be damaged by the firmware and is not updated, or at least it seems to me that the bootloader isn't updated
-
There are simply no resources left to do nice animations.
I'm strictly against any animations in such devices. I think all the power of the mcu should be used for useful tasks. For example, I noticed that turning on the on-screen measurements makes the work of the oscilloscope very slow and unstable (it can skip fast signals), so the device hardly has enough power to do the basic tasks that it should do. When I just bought this device I turned on 4 possible real-time measurements but now I disabled them all and enable them only rarely when they are really needed.
For Zoyi developers:
In this respect I want to ask Zotek engineers to make a button that can quickly enable and disable pre-selected realtime measurements. Now we have to press menu button to reach "Measure" submenu, then select 4 items, then watch the measurements, then go to that menu again, deselect the 4 measurements, and it really takes a lot of time. One button for it will save a lot of time. For example, some buttons are not assigned for a long-press action. Long press of "F4" could quickly turn on/off the cursors, and long press of "MODE" could turn on/off the measurements. This would be more quick and handy than doing it through menus.
A short press of the POWER/REL button could be used to turn measurements on/off, as REL has no function in scope mode. Thanks for the idea, noted :)
-
Here goes my wishlist for the 703 version 2:
- high resolution display (3.5", 640x480), no touch
- at least 400MHz MCU, with minimum 1MB of flash
- a big-ish FPGA, with lots of RAM (say Gowin GW2AR-18 <-- could do 32MPoints/channel >:D)
- original ADC from Analog or TI
Why not go a step further, a 7" bench scope.
That may be a winner if it's reasonable quality and can be sold for US$100-120.
-
Here goes my wishlist for the 703 version 2:
- high resolution display (3.5", 640x480), no touch
- at least 400MHz MCU, with minimum 1MB of flash
- a big-ish FPGA, with lots of RAM (say Gowin GW2AR-18 <-- could do 32MPoints/channel >:D)
- original ADC from Analog or TI
Why not go a step further, a 7" bench scope.
That may be a winner if it's reasonable quality and can be sold for US$100-120.
I have a proper bench scope and more then enough test equipment at home. I would not take my equipment even near the places I have to work at (shipyards / ships). For the field, I need a lightweight, small and somewhat precise multimeter, that fits in my backpack with the functions I have almost all finished, and a reliable oscilloscope with at least 2 channels, the 3.5" display is perfectly enough for my needs. The ZT703 hardware is almost perfect for my job (not hobby) needs, but one can always wish for something better ;)
Most of the time, I have to diagnose slow, old and simple 2 wire serial protocols with wiring and grounding issues. For this task I need a multimeter, a scope and a protocol decoder. The ZT703 should do all of these :)
-
The MCU has to "race the beam" of the LCD, to draw the whole screen in the blanking period, but a double framebuffer would eat up too much RAM.
So what you're saying my previous comment randomly about the amazing coding that occurs for the Atari 2600 now is essentially same to what you're needing to do too? ;) Best of luck to you for sure!
-
The MCU has to "race the beam" of the LCD, to draw the whole screen in the blanking period, but a double framebuffer would eat up too much RAM.
So what you're saying my previous comment randomly about the amazing coding that occurs for the Atari 2600 now is essentially same to what you're needing to do too? ;) Best of luck to you for sure!
Yes, I am old enough to know, what you were talking about... I would love to read that book of yours! It is part of the fun, but to be honest it is much easier now, then on an Atari or C64. I can run more then 1kB of C code with a lot of floating point math in the blanking period now (200MHz CPU and FPU speed to the rescue!) :) Compiler optimisations also help alot, becuase I am not willing to learn another assembly language. I probably also got lazy, have to focus more on code readability because of my job, and just want to get this meter working, as I want to, and as it should have been working from the factory.
Funny enough, the old habits die hard, I still always check for code size after compiling new features, as it would even matter...
-
If Zoyi really reads here, please fix the trigger channel colour to automagically change on the display instead of it being the last used channel's colour...
Then after lunchtime* if you could fix the bug where cursors lose their position if you change modes, I would be able to overlook the one other bug where triggering a signal less than 85kHz is lost at time divisions less than 500ns.
I love this little handheld bundle of fun(ctionality.)
*programmer humour.
-
This was more work, then anticipated, but at leas K-type thermocouples are working now. I just have to add the other types now.
The cold junction temperature has to be set in the menu, because the ZT703 has no reliable way of measuring it...
Edit: J, N, S, T also added :) These are the ones, I have seen in the wild myself, anyone needs other thermocouple types?
-
Great! :)
-
anyone needs other thermocouple types?
I think 99% of us are waiting for the oscilloscope firmware :) We all have many cheap and reliable multimeters, but we don't have a cheap and reliable oscilloscope! To say the truth, if I had your knowledge and skill, I would start to write new firmware from the oscilloscope part and if it becomes more reliable than the original firmware, it would be great and worthy even without the DMM part (imho). And when the ocsiloscope part is completely done, I would add the multimeter features. But it's my vision. Maybe you need the DMM part more than the oscilloscope part in your work, in this case your approach to make the DMM part first is reasonable.
-
anyone needs other thermocouple types?
I think 99% of us are waiting for the oscilloscope firmware :) We all have many cheap and reliable multimeters, but we don't have a cheap and reliable oscilloscope! To say the truth, if I had your knowledge and skill, I would start to write new firmware from the oscilloscope part and if it becomes more reliable than the original firmware, it would be great and worthy even without the DMM part (imho). And when the ocsiloscope part is completely done, I would add the multimeter features. But it's my vision. Maybe you need the DMM part more than the oscilloscope part in your work, in this case your approach to make the DMM part first is reasonable.
Yes, as it can be seen from my feature to-do list, it is very industry focused.The limit settings will also get some more industry focused presets.
I am almost finished with the DMM stuff, auto-off and auto-dim, and the needle thingy is left to do. If there is interest, we can do a DMM beta testing round, if not, then I will start with basic scope features, but I don't want to get the hopes up, first I will program the normal and single mode triggers, then comes the cursors next (because that is what I need the most). Signal auto detection and set-up has very low priority for me, because most of the time, I know exactly what signal to expect at the inputs.
-
You refused to add "switchable analog scale (bargraph)" for lack of flash memory size?
@indman: can You please make a screenshot of a DMM screen on the meter, where the needle thingy is visible? Does not matter wich mode, or value. Please upload as a zipped BMP, because the forum does not allow BMP files.
I want to shamelessly copy their design ;D As everyone can see from my screenshots, I am pretty bad at graphics design ;D
Thanks!
-
Sure, no problem. Is that quality BMP okay with you? :)
https://drive.google.com/file/d/1DPHXB68-hMtMV74s2SfAN6VgyQtDE0Yg/view?usp=sharing
-
Sure, no problem. Is that quality BMP okay with you? :)
https://drive.google.com/file/d/1nzkk_U6U7T9E5UsDlqMKrRAPFuNJiRjP/view?usp=sharing
Sorry, I mean a screenshot using the long press of the HOLD/SAVE button on the meter itself. Then You can copy the image to Your PC in the USB mode of the meter (should be accessible in the scope menu, I think app->image viewer-> usb?)
Thanks!
-
You'll have to excuse me for being a little blunt with the screenshot :-DD
I corrected the googledrive link in my previous post. :)
-
You'll have to excuse me for being a little blunt with the screenshot :-DD
I corrected the googledrive link in my previous post. :)
Perfect, exactly, what I needed :D This will be the first image used in the firmware :), everything up to this point is procedurally generated
Thank You!
-
@indman: I had to get rid of the red glow, it was eating crazy amount of resources. You still want this?
-
@indman: I had to get rid of the red glow, it was eating crazy amount of resources. You still want this?
Yes.This scale looks great on the display even without a red background. The needle can be made green or yellow, not necessarily red. :D
Another sentence for DMM - to move sound continuity to 1st place in the list? This function is most often used
-
Is is possible to make a kind of FAQ how your firmware upgrade should be made? I've made several devices with ESP32 devboard, but it was programmed using a USB cable. As far as I understand, it's not possible to upload your firmware to 703 using USB or flash memory, so I wonder what the update process is. Do we have to unsolder the STM32 and flash it using some specific hardware programmer and then solder it back?
-
@indman: I had to get rid of the red glow, it was eating crazy amount of resources. You still want this?
Yes.This scale looks great on the display even without a red background. The needle can be made green or yellow, not necessarily red. :D
Another sentence for DMM - to move sound continuity to 1st place in the list? This function is most often used
I think the scale is done. It even goes off the scale on overload :)
The needle is a little bit off at some parts of the scale, because the needle position is calculated linearly and the scale is round. I really did not want to the trigonometry calculations in the MCU for this meter display (it has other stuff to do), so it is like this.
To change the order of the F3 button functions, the DMMs EEPROM has to be edited. I cannot change that order in software, because switching between the 4 modes is the same command (no separete command for the different F3 button modes). The serial communication with the DMM chip is pretty "simple" to put it mildly, and very buggy. There is already a lot of code to deal with the bugs of the DMM chip, and there are still bugs left...
-
Is is possible to make a kind of FAQ how your firmware upgrade should be made? I've made several devices with ESP32 devboard, but it was programmed using a USB cable. As far as I understand, it's not possible to upload your firmware to 703 using USB or flash memory, so I wonder what the update process is. Do we have to unsolder the STM32 and flash it using some specific hardware programmer and then solder it back?
https://github.com/kmikl/open-zt703/blob/main/Documentation/Installation.md
-
https://github.com/kmikl/open-zt703/blob/main/Documentation/Installation.md
I've seen this but I don't understand what would be the physical connection between the 703 and the PC to write the new firmware. Step 3 in your manual says "connect" but this is not really obvious what and how should be connected (for those who have never worked with it).
-
I think the scale is done. It even goes off the scale on overload :)
That's good, but the arrow looks a little ugly right now, especially when it's at an angle.
I wonder how the arrow is made in the original, does it look more natural? I don't find fault and understand that the low screen resolution does not allow you to make it smoother.Maybe instead of a long arrow, draw a small triangle, the top of which will point to the measured value?
-
https://github.com/kmikl/open-zt703/blob/main/Documentation/Installation.md
I've seen this but I don't understand what would be the physical connection between the 703 and the PC to write the new firmware. Step 3 in your manual says "connect" but this is not really obvious what and how should be connected (for those who have never worked with it).
Sorry, You are totally right, it is just natural for me at this point, to have a debugger connected to the meter :) I can hardly imagine my meter, without wires sticking out of it, going to the J-Link adapter.
I have updated the manual. Please check, and reply with any questions or if there are mistakes somewhere
-
I think the scale is done. It even goes off the scale on overload :)
That's good, but the arrow looks a little ugly right now, especially when it's at an angle.
I wonder how the arrow is made in the original, does it look more natural? I don't find fault and understand that the low screen resolution does not allow you to make it smoother.Maybe instead of a long arrow, draw a small triangle, the top of which will point to the measured value?
What is missing, is anti-aliasing. I think the original needle is an image, where the graphics DMA (DMA2D) can do some blending (like with my fonts). I don't want to trow too many MCU resources (images are huge memory hogs) at the analog meter at this point in time, as I don't know yet, how much I will need in the future. The "needle" is now just simply 2 lines side-by-side drawn procedurally :)
If we trow away the curved scale, and use a linear one, (imagine staightening it out), the problem would be gone. Your feature, Your decision! ;)
-
If we trow away the curved scale, and use a linear one, (imagine staightening it out), the problem would be gone. Your feature, Your decision! ;)
I think you have more important things to do than to keep this arrow long. Let's leave it alone. If you future have any memory resources left, can we go back to it again? :D
-
I am thinking about postponing the auto-dim of the display and auto power-off. To be hones I hated these features on all of my DMMs, and since the ZT703 is rechargable, it is not a big problem, if the battery is empty. I would just add a low battery shut-off voltage for now.
I would like to start doing some scope stuff :)
-
Sorry, You are totally right, it is just natural for me at this point, to have a debugger connected to the meter :) I can hardly imagine my meter, without wires sticking out of it, going to the J-Link adapter.
Thank you. Now I understand that I need an external debugger to write the firmware. I found some on aliexpress, what do you think is the best choice for the price to upload the firmware?
https://aliexpress.com/item/1005005802567589.html
https://aliexpress.com/item/1005005303809188.html
I'm not a STM32 programmer so I hardly need some specific features and I don't want to buy expensive ones. I understand that the cheap ones are all 3.3v and I will have to add a resistor to reduce voltage to 3.0V.
I'm not going to flash anything right now, but if you finish the oscilloscope part before Zoyi fixes the non-working trigger issues, I think I will have nothing too loose then and I will try your version :) So far I'm not happy with the way the trigger works in the latest official firmware, basically, it doesn't work at all in some test experiments.
-
I have one of these:
https://www.aliexpress.com/item/1005003575620794.html (https://www.aliexpress.com/item/1005003575620794.html)
https://www.aliexpress.com/item/1005007075990822.html (https://www.aliexpress.com/item/1005007075990822.html)
You don't have to use the software I recommended, or an ST-Link V2, it is just simply what I use (for programming and debugging I use a J-Link). You just need something SWD capable, and being able to erase a chip, with the read protection enabled. Worst case scenario, I have to make a hex file, that just disables the read protection (and erases the MCU) for you, but that is easy enough to do. Then You can use any SWD capable debugger, with any software, that supports an STM32H7B0.
Before ordering anything, please check, that you have the board version 2.2, and an STM32 MCU in your meter. I have no idea, what they changed on the different board versions (I only have one), and for sure I won't port my code to any Artery, GigaDevice or whatever clone MCUs. I think that the v2.2 boards all have geniune SMT32s.
I will test my cheap ST-Link clone on my meter with series 1k resistors, just to be safe.
Edit: if you want to replace the MCU with a new/blank one to save the original firmware, then it is even easier. In that case any SWD capable debugger with any software that can flash an STM32H7 will work to install the bootloader. When the bootloader is running, USB is available. I don't know, which software can erase a protected ST MCU, the ST programmer can do it for sure. This is the reason, why I recommend it. The ST programmer software only supports ST-Link and J-Link.
If You have to work with ARM based MCUs a lot, You have to buy a J-Link (no affiliation, I have paid for my own). It is very, very expensive, but it works.
PS: if anyone in the future wants to use my firmware on a PCB version other, then 2.2, You are on your own. If You try it on a different PCB version, please give feedback here, but in any case, I can not help with other PCB revisions.
-
I have one of these:
https://www.aliexpress.com/item/1005003575620794.html (https://www.aliexpress.com/item/1005003575620794.html)
https://www.aliexpress.com/item/1005007075990822.html (https://www.aliexpress.com/item/1005007075990822.html)
Thank you. Are these ones good in case I need to program a new unused STM32?
I've just checked, I have V2.2 board. I can't see a STM32 but there is something different
[attach=1]
Is STM32 on the other side of the board?
I've found a cheap STM32 on aliexpress: https://aliexpress.com/item/1005005188963000.html?sku_id=12000039450654183 (https://aliexpress.com/item/1005005188963000.html?sku_id=12000039450654183)
It's STM32H750VBT6 IC. I'm not sure if it's compatible. I like the idea of saving the original chip with zoyi firmware, but I'm not sure if I have enough skill to replace the chip with such small pins and so little space around. I've got a heat fan to unsolder chips but I think that my hands will be shaking and I will spoil everything in this case. I think when the firmware is ready, somebody with more experience should make a youtube video showing how to replace it correctly :)
-
Is STM32 on the other side of the board?
Yes, it is on the other side of the board. And in the photo that you showed is DMM chip.
-
Yes, it is on the other side of the board.
The marks with the name are removed as the picture shows. So how can we determine that it's STM32 but not "Artery, GigaDevice or whatever clone MCUs"?
-
I've got a new wish to the wish list :)
When working with cursors in the official firmware, it only shows the delta voltage. I think it's evident that it should also show the voltage levels where the upper and lower cursors are set. It can be used to measure some parts of the signal more precisely in comparison with manual calculation of the grid lines.
[attachimg=1]
Also note the black rectangle in the left-bottom part of the screen when making a screenshot. I wrote about this bug half a year ago, and they still did not fix it. Sometimes I think that the programmer who wrote the original code for this device left the company, and the new programmers that work on this product now just cannot understand how this code works and how to fix it :) Otherwise I don't understand why they release new versions of firmware time after time, but all the initial and known bugs are still here...
-
Yes, it is on the other side of the board.
The marks with the name are removed as the picture shows. So how can we determine that it's STM32 but not "Artery, GigaDevice or whatever clone MCUs"?
Don't worry about that, You hava a v2.2 board, thats already good. The MCU programmer software would scream at you, if it detects a different chip, then expected.
-
I've got a new wish to the wish list :)
When working with cursors in the official firmware, it only shows the delta voltage. I think it's evident that it should also show the voltage levels where the upper and lower cursors are set. It can be used to measure some parts of the signal more precisely in comparison with manual calculation of the grid lines.
Also note the black rectangle in the left-bottom part of the screen when making a screenshot. I wrote about this bug half a year ago, and they still did not fix it. Sometimes I think that the programmer who wrote the original code for this device left the company, and the new programmers that work on this product now just cannot understand how this code works and how to fix it :) Otherwise I don't understand why they release new versions of firmware time after time, but all the initial and known bugs are still here...
Showing the cursors levels and a difference between them, is also IMO basic cursor functionality and Zoyi should have implemented it.
What even is that black rectangle, and why is it there? Making a screenshot is so simple, how could they mess that up? You just open a new file, copy a hard-coded BMP header into it, then just copy the framebuffer contents into the same file...
I just checked my code, ignoring the exception handling parts, it is literally 6 lines of C code...
-
Making a screenshot is so simple, how could they mess that up?
I think they messed up with the measurements update routines as this black rectangle is in the place where the measurements should be printed. They don't seem to check if the measurements are really enabled at the moment when the screenshot is made and clear this area in anyway, but measurement are not printed above as they were disabled. And as I wrote before, this black rectangle uselessly wastes a lot of space that can be used by the signal graph. The situation is twice worse when the measurements for 2 channels are enabled, we basically loose almost 1/3 of the whole screen area. So it's better to show measurements on the transparent background, just use a different color then the signal graph and they will look fine together in the same area.
-
I'm really amazed by this new firmware ideas, really like it and thanks everyone who's involved!
However, I have a little request. This multimeter has GIANT screen, but digits in multimeter mode are relatively small.
What if they can be made larger? If needed, I have enough design skills and can provide them in any logical format. Also, color customization would be great, like possibility to make them green, yellow, orange, etc - some folks have trouble seeing all the colors, you know.
-
Oh, and speaking about the thermocouples, I think, DS18B20 support would be nice, if technically possible.
-
New version 1.57.
V157 Version Upgrade details:
1.Update: Fixed the triggering issue at 250ns
Did somebody test it for bugs?
-
I'm really amazed by this new firmware ideas, really like it and thanks everyone who's involved!
However, I have a little request. This multimeter has GIANT screen, but digits in multimeter mode are relatively small.
What if they can be made larger? If needed, I have enough design skills and can provide them in any logical format. Also, color customization would be great, like possibility to make them green, yellow, orange, etc - some folks have trouble seeing all the colors, you know.
Font size: as You can see from my screenshots, when the graph or the analog meter is displayed, there is no more room left. I have chosen the highest font for the width, that I could find on my PC and is already a lot bigger, than in the stock firmware.
When everything is turned off, there is of course room to grow in height, but not in width. If You want to design a font for this mode (I would recommend doing it for the stats only mode), I can give You the character widths, that must be used. Fonts take up a lot of memory, the number 0 alone is 1449 bytes and memory is a precious resource here. We have 874k available in total for everything (171k is used at the moment).
Color changing: it can be done in the software of course, but it requires an extra memory access from the CPU, every time something is rendered into the framebuffer. Added to the wishlist, but lets wait with this feature, when everything works, and there are enough CPU cycles left over.
-
Oh, and speaking about the thermocouples, I think, DS18B20 support would be nice, if technically possible.
That would be pretty complicated. The DMM input can not commuicate with the DS18B20, and the "AWG" output is strictly output only, but the 1-Wire protocol is bidirectional. The only way it could maybe work, is to power the sensor in the parasitic power configuration (the user has to wire up the 4.7k resistor externally) from the "AWG" output, and use the scope input channel as an input, to get bi-dir communication going.
As a protocol decoder, 1-Wire could be done, but the meter talking directly to the sensor is IMO too mach hassle.
-
New version 1.57.
V157 Version Upgrade details:
1.Update: Fixed the triggering issue at 250ns
Did somebody test it for bugs?
Holy Crap, they really did fix it, you can get a stable trigger below 500ns with the 1khz test signal even!
-
New version 1.57.
V157 Version Upgrade details:
1.Update: Fixed the triggering issue at 250ns
Did somebody test it for bugs?
Holy Crap, they really did fix it, you can get a stable trigger below 500ns with the 1khz test signal even!
And what about slow signals? 1 Hz meander?
-
New version 1.57.
V157 Version Upgrade details:
1.Update: Fixed the triggering issue at 250ns
Did somebody test it for bugs?
Still a bit dodgy trying to auto range low frequency signals. About 15hz and lower don't always detect. High frequency seems alright since 1.56.
A DMM bug still exists. Power off in milliamp mode. Power on again. It will loop forever switching between AC and DC amp mode. They are getting the major bugs fixed. This is good. Maybe eventually they will get to the relatively minor annoyances such as this.
-
New version 1.57.
V157 Version Upgrade details:
1.Update: Fixed the triggering issue at 250ns
Did somebody test it for bugs?
Still a bit dodgy trying to auto range low frequency signals. About 15hz and lower don't always detect. High frequency seems alright since 1.56.
A DMM bug still exists. Power off in milliamp mode. Power on again. It will loop forever switching between AC and DC amp mode.
Not for me.
For me it stays in the set state.
When turned on it says which hole to use and stays in AC or DC depending on which one I turned off.
The refresh rate slows down a lot from 2ms/div to 200ms/div, when it switches to roll mode it's fine.
-
What about bug, when triggered impuls placed out of the screen? And necessary to move screen for searching it.
-
Off-screen trigger pulse not fixed.
-
Holy Crap, they really did fix it, you can get a stable trigger below 500ns with the 1khz test signal even!
I'm not so happy. They changed something but they did not test it in all zoom levels. I see ugly artifacts but only in some zoom levels, while most zoom levels are OK. I've got probes of different manufacturers, so it's surely not a probe problem. Please test and confirm.
Video: https://youtu.be/Z1T1bLFvc_E
-
What about bug, when triggered impuls placed out of the screen? And necessary to move screen for searching it.
The trigger still skips or misplaces single impulses.
-
A DMM bug still exists. Power off in milliamp mode. Power on again. It will loop forever switching between AC and DC amp mode. They are getting the major bugs fixed. This is good. Maybe eventually they will get to the relatively minor annoyances such as this.
No wonder. The DMM chip is terrible to communicate with. Nothing is documented, no separate commands for the measurement modes, if you send commands too quickly it just freezes. Sometimes it just simply freezes, without any apparent reason. Sometimes it goes out-of-sync for no reason. It is very unreliable.
This is exactly, why I dropped the feature of saving and restoring the last DMM measurement mode used on power up/down :(
-
Overall, this firmware is better than the last update for me me but now I notice mostly on ch2, but also to a less degree on ch1 that if i move the trace up or down, the noise shown changes dramatically every third time i move it. My spider senses tell me they have 'fnirsi' the displayed waveform to be more pretty than accurate in these last updates. I do like the new icon displayed for the trigger mode.
Still the trigger only shows the correct channel colour* icon if it happened to be the last channel selected or it has to be manually chosen by switching to the correct channel on the move or time selection.
Still the cursors lose place if you change modes and like the trigger only show correct colour* on the icon if the last chosen was the correct channel or if you manually select the correct channel in the move or time selection.
* it is colour dammit, not color!
-
Still the trigger only shows the correct channel colour icon if it happened to be the last channel selected or it has to be manually chosen by switching to the correct channel on the move or time selection.
Universally, since triggering capability was added to the earliest scopes, triggers are assigned to a channel and level adjusted for the operators needs.
In the modern DSO coloured display, the level indicators colour indicates what channel its assigned to.
-
Still the trigger only shows the correct channel colour icon if it happened to be the last channel selected or it has to be manually chosen by switching to the correct channel on the move or time selection.
Universally, since triggering capability was added to the earliest scopes, triggers are assigned to a channel and level adjusted for the operators needs.
In the modern DSO coloured display, the level indicators colour indicates what channel its assigned to.
perhaps you misunderstand me, my hantek dso2d15 certainly automagically colours the trigger channel correctly with no more input from me than selecting the channel that is the trigger. Also, the display does in fact correctly change colour in the top bit where it shows trigger direction and trigger level, so there just needs to be an extra bit added! Easy peasy...
-
I don't quite understand what you mean.
When both channels are active, I can choose from the menu which channel to trigger on.
The icons and numbers next to the battery symbol change color to the color of the channel.
If I switch it back, it follows normally.
Sometimes it happens that only half of them change to the other color.
The channel and edge symbol change color, not T:0mV.
It seems to me that it only happens when the channel or channels are on the center line and the trigger is 0mV
-
I think you have more important things to do than to keep this arrow long. Let's leave it alone. If you future have any memory resources left, can we go back to it again? :D
I could not let this problem alone.
Trowing some CPU cycles at it, anti-aliasing works. It is not perfect, but IMO looks much better now.
-
I don't quite understand what you mean.
When both channels are active, I can choose from the menu which channel to trigger on.
The icons and numbers next to the battery symbol change color to the color of the channel.
If I switch it back, it follows normally.
Sometimes it happens that only half of them change to the other color.
The channel and edge symbol change color, not T:0mV.
It seems to me that it only happens when the channel or channels are on the center line and the trigger is 0mV
Just a hint for Zoyi engineers: don't forget to reset the FGCOLOR register to the default value :)
-
Trowing some CPU cycles at it, anti-aliasing works. It is not perfect, but IMO looks much better now.
It is agreed, now it looks great. :-+
-
I have a 703s meter. The computer does not detect it. What could be the reason?
-
I have a 703s meter. The computer does not detect it. What could be the reason?
Try holding F1, while powering on the meter
-
This either means you have a fake z703s, or as so often explained in the previous posts, simply format the sd card from the 'hidden' menu option and you will have enough room.
-
For the font size. It is not only height or width that matters, the shape of digits also matters.
Currently you're using some Windows font as I guess, Tahoma, Verdana or something like that.
However, for physically lower resolution displays, there are fonts with different shapes of letters.
You can have look at Agilent OLED multimeters and compare their digits to yours.
Anyways, if you provide actual digit dimensions, I'll try my best.
Regarding the color change, I did not mean it to be dynamic or realtime, I mean that there might be
some option in the menu, from where you set the digit color. If this is not possible, then it might be possible
to make separate builds of firmware with green/yellow/pink/whatever colors of main digits.
For the DS18B20. In most equipment it is already wired with resistor, so only 2 wires are coming out.
Anyways, DS18B20 is really not an issue, it was just a thought.
-
For the font size. It is not only height or width that matters, the shape of digits also matters.
Currently you're using some Windows font as I guess, Tahoma, Verdana or something like that.
However, for physically lower resolution displays, there are fonts with different shapes of letters.
You can have look at Agilent OLED multimeters and compare their digits to yours.
Anyways, if you provide actual digit dimensions, I'll try my best.
Thank You for Your kind offer!
Sure I used a built-in Windows font, I don't know which one, becuse I am not at my private PC. I will post the font pixel sizes later, when I am at my PC again.
As You can see, I am not much of a graphics designer, I think I crammed too much information on the screen already (at least everyhing can be turned on or off).
Regarding the color change, I did not mean it to be dynamic or realtime, I mean that there might be
some option in the menu, from where you set the digit color. If this is not possible, then it might be possible
to make separate builds of firmware with green/yellow/pink/whatever colors of main digits.
The colors are hardcoded now, so the compiler bakes it in, the CPU just executes code. If I make the color changeable in any way, the CPU has to check a variable every time, which color to render.
The main measurement value is dynamic already becuase of the limits function (white or red), so there is no problem there, I can make that adjustable from the menu.
When the graph with average envelope display is enabled, the timing is already pretty tight and additional CPU cycles used in the rendering function could lead to display tearing artefacts.
I want to revisit that part later, to optimise the code for speed, so maybe I can free up some CPU time for selectable color schemes, where all colors can be changed (not just the main value).
Separate firmware versions, with hardcoded color schemes are of course no problem. The color definitions are already in a separate header file, so changing it is pretty easy.
For the DS18B20. In most equipment it is already wired with resistor, so only 2 wires are coming out.
Anyways, DS18B20 is really not an issue, it was just a thought.
Like I wrote, it is theoretically possible, and I would like to write a One-Wire decode anyway. I have to get the basic scope functions working properly, before thinking about any serial decoders.
If it can be made to work, there would be a connection needed from the AWG output lug of the meter to the sensor, wich is not very convenient...
We have to revisit this later.
-
Just sharing that I found FW 1.57 here....
https://zotektools.com/products/triple-in-one-instrument-combining-oscilloscope-multimeter-and-signal-source/
No release notes, details of changes made.
Will prob give it a try later this week.
-
New version 1.57.
V157 Version Upgrade details:
1.Update: Fixed the triggering issue at 250ns
-
For information. I've measured capacity of the battery: 2580mAh.
-
For information. I've measured capacity of the battery: 2580mAh.
This doesn't mean much. It is necessary to know at what battery voltage the controller switches off the device. This voltage just tells about the capacity used. It can be significantly lower than the capacity of the battery itself.
-
This doesn't mean much. It is necessary to know at what battery voltage the controller switches off the device. This voltage just tells about the capacity used. It can be significantly lower than the capacity of the battery itself.
I didn't measure the battery itself.
The algorithm was:
1. I discharged the oscilloscope.
2. Connected it to the power supply via device for measuring mAh.
3. And charged oscilloscope until it become full.
Final capacity was 2580mAh
[attachimg=1]
-
For the font size. It is not only height or width that matters, the shape of digits also matters.
Currently you're using some Windows font as I guess, Tahoma, Verdana or something like that.
However, for physically lower resolution displays, there are fonts with different shapes of letters.
You can have look at Agilent OLED multimeters and compare their digits to yours.
Anyways, if you provide actual digit dimensions, I'll try my best.
Regarding the color change, I did not mean it to be dynamic or realtime, I mean that there might be
some option in the menu, from where you set the digit color. If this is not possible, then it might be possible
to make separate builds of firmware with green/yellow/pink/whatever colors of main digits.
For the DS18B20. In most equipment it is already wired with resistor, so only 2 wires are coming out.
Anyways, DS18B20 is really not an issue, it was just a thought.
Font sizes:
' ': 26 x 63 pixels (space, not much to do here :))
'-': 26 x 63 pixels (minus sign)
'.': 24 x 63 pixels (decimal point)
'0' - '9' : 46 x 63 pixels (the actual digits)
I am currently using DejaVu Sans Condensed.
Only grayscale works, the font "image" will be converted to 4 bits/pixel alpha channel. So white is 100% color and black is 0% color. I am using the lcd-image-converter software for the conversion.
If I can help You with anything else, please let me know!
Edit: forgot 'L', also 46x63 pixels
-
For information. I've measured capacity of the battery: 2580mAh.
This doesn't mean much. It is necessary to know at what battery voltage the controller switches off the device. This voltage just tells about the capacity used. It can be significantly lower than the capacity of the battery itself.
The meter uses several LDOs to create the internal 3V rails, if that helps. At about 3.2 - 3.3V the power has to be switched off, because the screen backlight starts flickering, and the MCU gets unstable.
-
I went back to v1.42 firmware after finding another bug in the latest firmware that is weird enough to scare me about what is really going on under the hood! If you are on the latest (1.57 at time of post) try going to the output menu and watch for the weird glitch where the wave select box briefly flashes yellow then back to red the first time you select it.
-
On FW1.56, with CH 1 active only, run Auto Range, with no signal connected or in one of the devices confused states, once complete, the trigger indicates that its set on Ch 2 (even though CH2 is switched off). Scrolling back to the trigger menus, it will change from blue to yellow (Ch 2 to Ch1) on its own.
It appears to be just a font colour/indicator thing.
Giving 1.57 a try, just for the heck of it.
-
If you are on the latest (1.57 at time of post) try going to the output menu and watch for the weird glitch where the wave select box briefly flashes yellow then back to red the first time you select it.
Yup, I see it. Its there. :palm:
You think it can be fatal enough to stay away from, and warrants going back to 1.4x?
-
If you are on the latest (1.57 at time of post) try going to the output menu and watch for the weird glitch where the wave select box briefly flashes yellow then back to red the first time you select it.
Yup, I see it. Its there. :palm:
You think it can be fatal enough to stay away from, and warrants going back to 1.4x?
My stated fear is merely Aussie humour, but it is the first time I have noticed a bug that makes me wonder what the actual (insert word here) is going on, and as I have no real issues with the older firmware, I am prepared to wait. I did like the working auto with both channels placed correctly, and I like the newer run/TD/wait icon, and I really like that I can trigger below 85khz with time div less than 500ns with the latest firmware, but hopefully the next one will be 'it'
-
My stated fear is merely Aussie humour,
You got me there....
like that I can trigger below 85khz with time div less than 500ns with the latest firmware, but hopefully the next one will be 'it'
Indeed..... I managed to put some time in earlier this morning and saw that it worked from about 8Hz till about 70kHz (Which is all I have), and a few steps below 250ns (I think).
-
simply format the sd card from the 'hidden' menu option and you will have enough room.
So how do you access these hidden menu options?
P.S. I found. You just need to select "default" from the menu.
-
If you are on the latest (1.57 at time of post) try going to the output menu and watch for the weird glitch where the wave select box briefly flashes yellow then back to red the first time you select it.
I tried it, but I didn't find anything similar. Maybe it's just the button rattling?
-
I could not let this problem alone.
Trowing some CPU cycles at it, anti-aliasing works. It is not perfect, but IMO looks much better now.
I wonder what is the refresh rate for this arrow in your firmware? If it's the same frame rate like in the original (afair 3fps), it's just not worth to spend resources at, and it's better to throw these CPU cycles for something more useful :) I've got a Victor multimeter, it has a graph that refreshes MUCH faster than the numbers, and it may be useful sometimes to catch fast changes, but when the refresh rate of the graph is the same as the refresh rate of the numbers, what can it be used for?
-
I wonder what is the refresh rate for this arrow in your firmware? If it's the same frame rate like in the original (afair 3fps), it's just not worth to spend resources at, and it's better to throw these CPU cycles for something more useful :)
If this arrow is updated with the frequency of renewal of digits, still very often the arrow is more convenient. I do not need to peer the digits and quickly look at the position of the arrow. In addition, ajar171 makes it disconnected. Who does not like her will just turn it off. ;)
-
The algorithm was:
1. I discharged the oscilloscope.
2. Connected it to the power supply via device for measuring mAh.
3. And charged oscilloscope until it become full.
Final capacity was 2580mAh
You measured the energy used to charge the battery, but not it's capacity. You charged it with 5V while the battery is approximately 3.7V, you should convert mAh to mWh to compare. Besides, the oscilloscope has to convert 5V to the battery charging voltage that also incurs power losses sometimes up to 10-15%. The energy required to charge the battery is always higher than the energy that the battery can give back, so your measurements are not correct. The correct method is to completely charge the battery, remove the battery from the oscilloscope and discharge it using some li-pol discharger like my iMaxRC B606, it will tell you the true battery capacity. You can try to discharge it through your Keweisi using approx. 0.5-1A load, it may also give acceptable results if this meter supports voltages lower than 5V. You will have to make adapters for it of course. Just for information, I had such keweisi but I gave up using it because it had bad usb contacts and reduced the charging current a lot, maybe it can work better but the usb plug and socket have to be replaced, I was lasy to do it and bought a different model.
-
I wonder what is the refresh rate for this arrow in your firmware? If it's the same frame rate like in the original (afair 3fps), it's just not worth to spend resources at, and it's better to throw these CPU cycles for something more useful :) I've got a Victor multimeter, it has a graph that refreshes MUCH faster than the numbers, and it may be useful sometimes to catch fast changes, but when the refresh rate of the graph is the same as the refresh rate of the numbers, what can it be used for?
It does not matter how often You get new data from the DMM chip, when there is only a single frame buffer.
Step 1: the data arrives, it is prepared for rendering, here you have almost 1/3 of a second. Life is good, code readability is number 1 priority :)
Step 2: preparations are finished, now we have to wait for the screen banking period (interrupt driven)
Step 3: the interrupt fires, render quickly everything into the framebuffer, before the screen starts displaying the first line. Now this is the tight spot (the screen is refreshed with about 30Hz and the blanking is only a small part). You have to put everything into the framebuffer before the visible stuff gets sent to the display. Everything You see on the screen has to be there in this blanking period. The "needle" or the graph plot is drawn by the CPU only, no DMA help there. (DMA could be used, but that eats more RAM. RAM is reserved for scope stuff at the moment)
All of the above does not matter, because it works and to be honest, I also like it :) It can also be switched off, so everyone can customize the screen to his liking.
I don't really know at this point in time, how much RAM I will need for the features, that I want to implement. This is the reason, why I am so strict about MCU resources.
Now back to the scope stuff :)
-
You measured the energy used to charge the battery, but not it's capacity. You charged it with 5V while the battery is approximately 3.7V, you should convert mAh to mWh to compare. Besides, the oscilloscope has to convert 5V to the battery charging voltage that also incurs power losses sometimes up to 10-15%. The energy required to charge the battery is always higher than the energy that the battery can give back, so your measurements are not correct. The correct method is to completely charge the battery, remove the battery from the oscilloscope and discharge it using some li-pol discharger like my iMaxRC B606, it will tell you the true battery capacity. You can try to discharge it through your Keweisi using approx. 0.5-1A load, it may also give acceptable results if this meter supports voltages lower than 5V. You will have to make adapters for it of course. Just for information, I had such keweisi but I gave up using it because it had bad usb contacts and reduced the charging current a lot, maybe it can work better but the usb plug and socket have to be replaced, I was lasy to do it and bought a different model.
Correct and also, the LDOs in the meter need some overhead, so the meter has to be switched off at approx. 3.3V battery voltage. The battery could go lower, but the LDOs dont.
-
Now back to the scope stuff :)
Yes! :)
-
All of the above does not matter, because it works and to be honest, I also like it :) It can also be switched off, so everyone can customize the screen to his liking.
It just came to my mind that the performance is not extremely required in the DMM mode as there are not so many "useful" measurements to do there, and the speed of the MCU should be more than enough to do them all. So, yes, we can probably implement some auxiliary stuff such as jumping arrows :) It's the oscilloscope mode where all the MCU power should be used for the required "useful" calculations only but not for the neat graphics rendering, font smoothing, etc.
-
Correct and also, the LDOs in the meter need some overhead, so the meter has to be switched off at approx. 3.3V battery voltage. The battery could go lower, but the LDOs dont.
For the most complete use of the battery, it would be best to use a step-up converter so that it would output +5 V to the circuit at any battery voltage. And the battery itself would be disconnected by the controller at 2.5...3 V. But such a DC-DC converter can produce pulse interference, which will need to be eliminated somehow.
-
I found something I cannot understand at all:
The start address of the flash in the MCU is 0x0800 0000.
The reset vector of the Zoyi firmware points to 0x0802 0381, wich is outside of the advertised 128kBytes of flash (0x2 0000) this MCU should have.
If I try to write data to say 0x080F 0000 (way outside the 128k), the data gets written, and can be read back. :o
Even if I dump the entire 1Mbyte of flash bank starting from 0x0800 0000, there is no wraparound, the test data written before is clearly at the right address, and can only be found once in the dump.
The same goes for flash bank 2 (another 1Mbyte of flash).
WTF is going on here?
Edit: only the STM32H7B3 and A3 have 2Mbytes of flash, but B0 can be seen on my chip (they have lasered it away pretty poorly on my meter, so it can be sort-of read)
-
Edit: only the STM32H7B3 and A3 have 2Mbytes of flash, but B0 can be seen on my chip (they have lasered it away pretty poorly on my meter, so it can be sort-of read)
Computer history knows a lot of cases when more expensive chips were remarked and sold as less expensive chips just for marketing reasons. Sometimes the only thing that makes cheap stuff differ from expensive stuff is a simple limitation flag in firmware :)
-
If this translated to English accurately, you are not the first person to notice that the B0 chips (at least some, possibly all to that point) have 2MB of flash:
https://www.armbbs.cn/forum.php?mod=viewthread&tid=110883 (https://www.armbbs.cn/forum.php?mod=viewthread&tid=110883)
-
If this translated to English accurately, you are not the first person to notice that the B0 chips (at least some, possibly all to that point) have 2MB of flash:
https://www.armbbs.cn/forum.php?mod=viewthread&tid=110883 (https://www.armbbs.cn/forum.php?mod=viewthread&tid=110883)
Thanks, I was already thinking, that I messed something up.
Pretty brave from Zoyi relying on an undocumented feature for a commercial product. This also explains, why their bootloader tries to flash an update firmware 3 times, before failing. The B0 chips are maybe binned B3s, that failed factory flash testing above the 128k limit.
Now we have two options:
- concentrate on dumping their bootloader (and RE), so we can flash the alternative firmware using their bootloader and make switching between firmwares easy
- ignore this, and continue with alternative BL (already programmed with the 128k limit in mind |O) and loose the ability to go back to stock firmware, but don't rely on undocumented features. I am executing the program from RAM, which is of course much faster, then flash.
-
Hi all,
I've had the Zoyi ZT-703S for a week, and after trying almost everything, I can't get the signal generator to work. It only works with the default one (square wave). The other three waveforms (pulse wave, sine wave and sawtooth) don't work with any parameter (frequency, VPP, Duty), and the output signal is 0 V.
I have the latest firmware 1.5.7 installed.
I've tried reinstalling an older firmware with the same result.
Other functions, both the oscilloscope and the multimeter, work fine.
Any ideas?
Thanks.
-
Did you check both versions of the siggen? One is off the menu buttons, the other is within the MoreAPPs folder. Could one be overriding the other?
-
That is a great suggestion, the more apps sig gen won't output if you leave the app, and also there is a 100us limitation if you change the internal sig gen output from default 1khz square wave.
-
Yes, I have tested both versions of signal generator.
The one form the main menu works only with continious square wave, the others no output at all.
In the the apps menu the same, only generate output signal form square wave, freq+/- and Duty+/- also works. The other signals sin, triangle, half, full, sawtooth no output (0 Volts).
I can switch on and off the signal generator presing menu key but when I leave the apps siggen off and exit and enter again the apps siggen is on again.
Really extrange for me.
-
That is a great suggestion, the more apps sig gen won't output if you leave the app, and also there is a 100us limitation if you change the internal sig gen output from default 1khz square wave.
Yes, I know the 100us limitation but the issue is that thare are no output signal rather than the default scuare pulse.
-
The apps/signal generator is literally a separate piece of software. If You open it, the oscilloscope software stops running. If You close it (and return to the scope) it stops outputting the waveform.
This is a hardware limitation and there is no way around it (there goes the missing FPGA again).
The technical part:
The square wave is coming from a PWM output pin in scope mode and the signal generator output comes from a DAC pin.
The PWM output is generated by a timer, and does not need DMA or the CPU to do its job. The DAC needs DMA and the scope input too and they would need to share the same bus (would be a very bad idea).
Only triangle wave and noise output can be generated by the DAC in hardware without DMA and I have no idea, why Zoyi did not allow at least those 2 signals, while running the scope.
TBH, the two could work together, but only at very low sample rates, it is not worth the effort.
-
Tested with a professional oscilloscope Tektronix TDS 220 definitely signal generator doesn't work. Probably my ZT-703 came damaged internally. You can check it in this video. :-//
https://youtu.be/WDzrVXKuBy4
-
Tested with a professional oscilloscope Tektronix TDS 220 definitely signal generator doesn't work. Probably my ZT-703 came damaged internally. You can check it in this video. :-//
https://youtu.be/WDzrVXKuBy4
Sorry, I have misunderstood You! That is a defective output. Since the square-wave gets out of the meter, the output op-amp is at least working.
Try to send the unit back to the seller, if it does not work, maybe I can help You with a repair.
-
You can check it in this video. :-//
https://youtu.be/WDzrVXKuBy4
Based on this video...
I agree with ajar171, I would conclude that there is something gravely off wif your unit.
For the Sig Gen using "F4", I am sure what you are seeing is not what I am seeing on my unit.
For the "More Apps" Sig Gen, I am less sure, as I dont have another scope to view its output.
-
Now we have two options:
- concentrate on dumping their bootloader (and RE), so we can flash the alternative firmware using their bootloader and make switching between firmwares easy
- ignore this, and continue with alternative BL (already programmed with the 128k limit in mind |O) and loose the ability to go back to stock firmware, but don't rely on undocumented features. I am executing the program from RAM, which is of course much faster, then flash.
The first option is more preferable in the initial stages of the new firmware development. I think I don't have enough skills to resolder STM32. While the new firmware is not completely ready, I'm not sure that I want to overwrite the original bootloader and spoil the possibility to upgrade to new official releases, and I still hope that they will fix this never-ending trigger issue some day and the oscilloscope will become useful as it is :) At the other hand, the second option allows unlimited further improvements of the firmware and adding new features that Zoyi will never implement. So, you are the developer and it's up to you to decide. If it's possible to start the development using the 1st option so that many users could test it safely. And then, when the firmware proves to be reliable and better than the original, redesign the code for option 2. If this is not much extra work to do, this would be a great solution. In any way, it's up to you to decide because nobody knows how far you are going to climb with it. If you have tons of plans to implement, this 128 kb limit will be a problem of course.
-
Anyone got a link to ver 1.55 please?
1.55 - https://drive.google.com/file/d/1xgdgFe6GohxC1WyyIX2O0uyEkZHiOHiv/view
1.56 - https://drive.google.com/file/d/12Gxb3DFtqoraxpqkC3cRqKC9haMOEV1Y/view
Thank you, much appreciated
-
I knew it was only a matter of time before someone hacked the firmware on this device. I was thinking of buying one (as a desk MM/Scope) but now I will for sure. I'm super excited to see decoding is planned to be worked on.
I've done a fair bit of STM32 development. I'd love to jump into this project but I already have too much on the go.
Keep up the good work. Reach out if I can be of help.
-
If you are on the latest (1.57 at time of post) try going to the output menu and watch for the weird glitch where the wave select box briefly flashes yellow then back to red the first time you select it.
Thanks OlderDan, credit to you.
I decided to make a video on the "glitch".
https://www.youtube.com/shorts/y7THPaNuFa0 (https://www.youtube.com/shorts/y7THPaNuFa0)
-
If you are on the latest (1.57 at time of post) try going to the output menu and watch for the weird glitch where the wave select box briefly flashes yellow then back to red the first time you select it.
Thanks OlderDan, credit to you.
I decided to make a video on the "glitch".
https://www.youtube.com/shorts/y7THPaNuFa0 (https://www.youtube.com/shorts/y7THPaNuFa0)
Same "glitch" in my case.
Have you check if the signal generator really works?
Not for me, You can see may last post and the video
-
both the more apps and external work over all ranges and signal types, checked with the z703s and my dso2d15. I haven't checked since upgading and downgrading the firmware, but I have no reason to believe anything has changed.
-
Same "glitch" in my case.
Have you check if the signal generator really works?
Not for me, You can see may last post and the video
Would you be able to get a warranty claim from whoever you purchased it from?
Alternatively, you can try the information here to have your issue resolved.
http://www.szzotek.com/h-col-160.html (http://www.szzotek.com/h-col-160.html)
Its a mandarin based page, but you can use translate to access it. And the WeChat link seems interesting, although I have never tried it. The shipping from where you are from may not be be financially viable though.
-
Just made a new probe cover with a thinner bottom to fit standard connectors
https://www.thingiverse.com/thing:7053840 (https://www.thingiverse.com/thing:7053840)
-
Hi! I bought myself a ZT-703S. After 2 months of use, I noticed that the oscilloscope on channel 1 with the probe disconnected began to underestimate at x1 by 300 mV, and at x10 by about 3 V. When applying a signal, the signal shifts by 300 mV down along the y axis. The built-in calibrator does not help. I also tried to flash it to the previous firmware, the problem remained. Maybe someone has encountered such a problem.
-
........ channel 1 with the probe disconnected began to underestimate at x1 by 300 mV, and at x10 by about 3 V. When applying a signal, the signal shifts by 300 mV down along the y axis.
The built-in calibrator does not help. I also tried to flash it to the previous firmware, the problem remained. Maybe someone has encountered such a problem.
Have you tried the "Default" option and then the "Calibrate" (with probes disconnected) menu buttons?
As per the pict below?
-
Hi! Yes, I tried it, the calibration function showed calibration failure. I think I fed too much signal to the oscilloscope and didn't even notice, which led to this signal distortion. I'm on a business trip now and I don't have the opportunity to disassemble the 703 to make sure the amplifier circuits are working properly. I'll come back in a couple of days and look into this problem more thoroughly.
-
https://drive.google.com/file/d/1did2_dDTP_rK_eO7O9-joANWN-guBZ_P/view
V157 Version Upgrade details:
1.Update: Fixed the triggering issue at 250ns
-
probe disconnected began to underestimate at x1 by 300 mV, and at x10 by about 3 V
Are you located close to transmitter jamming GPS signal ?
-
Hello, recently i tried using the zt-703 to read a dual signal waveform (don't know if that's the correct term) but obviously it didn't work. Our work scope did read both waveforms in a single channel easily as you can see in the attached photos. It there a way that i could make the zt-703 do that or is it a hardware issue?
-
Hello, recently i tried using the zt-703 to read a dual signal waveform (don't know if that's the correct term) but obviously it didn't work. Our work scope did read both waveforms in a single channel easily as you can see in the attached photos. It there a way that i could make the zt-703 do that or is it a hardware issue?
How do you create such a waveform on one channel?
-
To be totally honest i am not sure ,we have to take some measurements and chance the capacitance of the circuit to try to ,among other things, align the 2 waveforms but i have no idea how they are generated as i am pretty new to this job and i am just learning the basics for now
-
To be totally honest i am not sure ,we have to take some measurements and chance the capacitance of the circuit to try to ,among other things, align the 2 waveforms but i have no idea how they are generated as i am pretty new to this job and i am just learning the basics for now
This has nothing to do with ZT-703. Also your second picture is so bad that you can't even read anything. How do you think someone in particular can help.
This is oscilloscope basics and is related to sample rate and waveform update rate.
If the time base setting is faster, the acquisition rate is faster than the screen is able to display. Then several acquisitions are overlayed and displayed at the same time. The behaviour will vary between different oscilloscope models. There are possibilities that prevent that:
- using the "Single" mode
- choosing a slower time base
- using the "trigger hold off" function to reduce the acqusition rate
-
To be totally honest i am not sure ,we have to take some measurements and chance the capacitance of the circuit to try to ,among other things, align the 2 waveforms but i have no idea how they are generated as i am pretty new to this job and i am just learning the basics for now
This has nothing to do with ZT-703. Also your second picture is so bad that you can't even read anything. How do you think someone in particular can help.
This is oscilloscope basics and is related to sample rate and waveform update rate.
If the time base setting is faster, the acquisition rate is faster than the screen is able to display. Then several acquisitions are overlayed and displayed at the same time. The behaviour will vary between different oscilloscope models. There are possibilities that prevent that:
- using the "Single" mode
- choosing a slower time base
- using the "trigger hold off" function to reduce the acqusition rate
I saw it when i went to post it but i don't have another picture and don't know when i'll get the chance to take another one. but what i wanted to show was that with the same signal one was showing one waveform while the other 2 waveforms. The desired result for me in this instance it to get 2 waveforms to show .And i am wandering if that is possible with the zt-703. The signal usually is in the range of 5-17Khz) and the voltage from some mV to 10V. Currently the waveform seems to go back and forth the 2 and seems unstable.
-
If the two waveforms are “real”, then measure them with both channels. If not, what do you want to do with that?
Normally, two signals on one channel add up as in the screenshot below (magenta).
-
I saw it when i went to post it but i don't have another picture and don't know when i'll get the chance to take another one. but what i wanted to show was that with the same signal one was showing one waveform while the other 2 waveforms. The desired result for me in this instance it to get 2 waveforms to show .And i am wandering if that is possible with the zt-703. The signal usually is in the range of 5-17Khz) and the voltage from some mV to 10V. Currently the waveform seems to go back and forth the 2 and seems unstable.
No, you will never have the ZT-703 showing this modulated waveform like the Fluke 190-202. You can use the "persist" function to overlay multiple waveforms. Compared to the $5000 Fluke the ZT-703 is a toy and still has many bugs. However, your observation is not a bug, rather a limitation of the hardware and the way they implemented the waveform display.
Currently the waveform seems to go back and forth the 2 and seems unstable.
sounds like an asynchronous triggering problem which is totally normal for such kind of signal.
https://www.youtube.com/watch?v=N2novzfmVQ0 (https://www.youtube.com/watch?v=N2novzfmVQ0)
-
I saw it when i went to post it but i don't have another picture and don't know when i'll get the chance to take another one. but what i wanted to show was that with the same signal one was showing one waveform while the other 2 waveforms. The desired result for me in this instance it to get 2 waveforms to show .And i am wandering if that is possible with the zt-703. The signal usually is in the range of 5-17Khz) and the voltage from some mV to 10V. Currently the waveform seems to go back and forth the 2 and seems unstable.
No, you will never have the ZT-703 showing this modulated waveform like the Fluke 190-202. You can use the "persist" function to overlay multiple waveforms. Compared to the $5000 Fluke the ZT-703 is a toy and still has many bugs. However, your observation is not a bug, rather a limitation of the hardware and the way they implemented the waveform display.
Currently the waveform seems to go back and forth the 2 and seems unstable.
sounds like an asynchronous triggering problem which is totally normal for such kind of signal.
https://www.youtube.com/watch?v=N2novzfmVQ0 (https://www.youtube.com/watch?v=N2novzfmVQ0)
Thank you, makes sense that those limitations exist in this price point, i was just making sure as i can't really understand how the fluke even does 2 signals in one channel work without them getting added to each other (like the person above suggests).
-
I'm beginning to understand. :-//
kloetpatra is right, this is a modulated waveform.
The Zeeweii DSO2512g can display something like that.
It depends on where the trigger is set.
With a stop, of course, you only see a single trace.
On the DSO2512g you don't need to activate persistence for this.
But I'm still not quite sure what that's good for.
@008nothing: Is that what you are looking for?
-
I'm beginning to understand. :-//
kloetpatra is right, this is a modulated waveform.
The Zeeweii DSO2512g can display something like that.
It depends on where the trigger is set.
With a stop, of course, you only see a single trace.
On the DSO2512g you don't need to activate persistence for this.
But I'm still not quite sure what that's good for.
@008nothing: Is that what you are looking for?
yup, i think that's what i was going for. Mostly out of curiosity as at work we have to use the fluke ones because of certifications e.t.c.
-
yup, i think that's what i was going for. Mostly out of curiosity as at work we have to use the fluke ones because of certifications e.t.c.
OK, but I suspect this is still some kind of triggering artifact.
The signal probably looks more like the attached screenshot (magenta). That's 17kHz and 5kHz added together.
-
Anybody knows if custom firmware project is dead?
-
I hope not.
-
Hello! Can you tell me the marking of these two components on the first input of the Zoyi ZT-703? 1: 8091 is ad8091, 2 is TVS diode? Did I understand correctly?
-
When they update the firmware do they update the manual, e.g. use of FFT?
-
I haven’t seen any updated manual for the ZT-703S corresponding to recent firmware updates.
Regarding the FFT feature: from what I’ve observed, the X-axis (frequency scale) seems to be tied directly to the selected timebase. For example, if you set the timebase to 20 µs/div, the FFT X-axis corresponds to 50 kHz/div. So the frequency range displayed changes depending on your timebase setting.
As for the Y-axis, it looks like they normalize the highest peak rather than displaying an absolute amplitude scale. So it’s more useful for identifying frequency components than for precise amplitude measurements.
Hope that helps!
-
I don't know why nobody mentioned it in this thread yet, but Zoyi used the wrong charge controller ME4086B which has charge termination at 4.35V. Correct 4.2V one would be ME4086A. Zoyi should definitely do a recall before they put houses on fire.
I wonder if newer devices use the correct one?
Big thanks to @BRN who found this issue. Definitely check out his thread: https://www.eevblog.com/forum/testgear/zoyi-zotek-zt-703s-fire-hazard-while-charging/ (https://www.eevblog.com/forum/testgear/zoyi-zotek-zt-703s-fire-hazard-while-charging/)
-
Instead of a recall, it would be enough if they supplied 4.3V charging voltage cells. Example SANYO UR18650ZTA or LG ICR18650 E1
-
I confirm the issue.
Charger NO BATTERY = 4.46V
Charger WITH BATTERY and the LED is flashing = 4.33V
Charger WITH BATTERY before turn off = 4.30V with several short peaks up to 4.50V during final 5-10 seconds, then turn off. The battery keeps 4.28V voltage that slowly reduces.
However, the battery is cold, it's just 1 degree Celsius higher than the environmental temperature (the device was open during the test and the battery was not discharged before the test, so it did not charge long). I don't think it will burn unless you change it with something that has no internal overcharge protection. Maybe it's a good idea to stop charging it at ~80% manually to prolong the battery life, but I understand that it is not convenient.
My guess is that it's not a design mistake. Most likely it's a marketing trick just to say in the reviews that their device works longer than the devices of the competitors, and no matter that the battery will die faster. The choice was made, the money was paid, that's the only thing that is important in the modern marketing :(
Besides, the trigger issues are not fixed in the latest firmware and I'm tired of waiting when they fix them. I've already started to look for another inexpensive multi-meter with tested firmware. ZEEWEII DSO2512G seems to have many good reviews, but some users noted that they probably changed some parts to cheaper ones in the last 1-2 years, and the modern devices have more noise than the devices that were initially produced under the same name. This is also a rather typical and disgusting Chinese marketing trick to sell absolutely different and cheaper hardware in the case and under the name of the hardware that was proved to be good some time ago.
-
I don't know why nobody mentioned it in this thread yet, but Zoyi used the wrong charge controller ME4086B which has charge termination at 4.35V.
Since this thread is also for the ZT-702S, it should be noted that the ZT-702S uses a TP4056 charge controller (or equivalent), specified for 4.2V. On mine, I measured 4.185V on the battery terminals without the battery installed. So, the ZT-702S doesn't have this problem and is safe for charging the cell provided with it.
-
Has the ZT-703S model shematic been clarified to see if there is any sensible point where the HC-05/HC-06 bluetooth serial circuit would be activated when the uart is turned on.
Previously added the HC-05/HC-06 bluetooth circuit to the multimeters so that the bluetooth circuit power is activated when a signal comes to the uart. The connection is unnecessarily complicated. When I don't want the bluetooth to always be on when the meter or backlight is on.
-
Here is a fix for this problem. It’s not my video- but I have a unit with the same problem, which is dry joints on the chip under the on/off button.
https://youtu.be/P6QntvNAdx8
-
Nevermind, it's 3V. There are two similar regulators on the board next to the signal generator output.
Could someone check the supply voltage for the DMM chip?
I also have one of these with a faulty DMM mode. The DMM chip supply rail on this one is only ~0,4 volts and the voltage regulator is running really hot. It's the SOT-23-5 right next to the battery holder on the right side.
I think the regulator is from Microne. It has a "wave" logo and marking P8XC on top of it, but I'm unable to deduce which one it is from that.
-
Maybe someone already wrote simple software to parse the 703 terminal output to something like:
date_time,value
date_time,value
date_time,value
...
??? It would be great to have it for Linux, but Win is also ok. I want to log the process to see how quickly my super-capacitors discharge and I thought this Zoyi could be used as a logger if there is some kind of software that can write such logs.
-
We made application working with PC for zoyi...
It is also option log to file...but with no date time...i think it is easy add.
[attach=1]
-
I've been cooperating with ChatGPT and it helped me a lot to write the following script :) Not from the first attempt, but finally it works:
#!/bin/bash
stty -F /dev/ttyUSB0 115200 cs8 -cstopb -parenb
LOG_FILE="zoyi_data.csv"
buffer=""
while IFS= read -r -n1 char; do
if [[ "$char" == " " ]]; then
if [[ -n "$buffer" ]]; then
if [[ "$buffer" == *:* ]]; then
key="${buffer%%:*}"
value="${buffer#*:}"
#timestamp=$(date +"%Y-%m-%dT%H:%M:%S") #ISO
#timestamp=$(date +%s); # linux timestamp
timestamp=$(date +"%Y-%m-%d %H:%M:%S")
output="$timestamp,$key,$value"
echo "$output"
echo "$output" >> "$LOG_FILE"
fi
buffer=""
fi
else
buffer+="$char"
fi
done < /dev/ttyUSB0
The output is a CSV file, you can build graphs in Excel-like spreadsheet software. Date/time format can be changed as you like (edit "timestamp=").
Output example (works not only with voltage but with other modes too):
2025-09-07 12:10:07,VVoltage,04.668
2025-09-07 12:10:07,VVoltage,04.667
2025-09-07 12:10:07,VVoltage,04.664
2025-09-07 12:10:08,VVoltage,04.663
2025-09-07 12:10:08,VVoltage,04.662
2025-09-07 12:10:08,VVoltage,04.661
2025-09-07 12:10:09,VVoltage,04.661
2025-09-07 12:10:09,VVoltage,04.660
2025-09-07 12:10:09,VVoltage,04.660
2025-09-07 12:10:10,VVoltage,04.660
2025-09-07 12:10:10,VVoltage,04.659
2025-09-07 12:10:10,VVoltage,04.658
2025-09-07 12:10:11,VVoltage,04.657
2025-09-07 12:10:11,VVoltage,04.658
2025-09-07 12:10:11,VVoltage,04.657
2025-09-07 12:10:12,VVoltage,04.657
2025-09-07 12:10:12,VVoltage,04.656
2025-09-07 12:10:12,VVoltage,04.656
2025-09-07 12:10:13,VVoltage,04.655
2025-09-07 12:10:13,VVoltage,04.654
2025-09-07 12:10:13,VVoltage,04.654
2025-09-07 12:10:14,VVoltage,04.653
2025-09-07 12:10:14,VVoltage,04.653
2025-09-07 12:10:14,VVoltage,04.652
2025-09-07 12:10:14,VVoltage,04.652
2025-09-07 12:10:15,VVoltage,04.652
2025-09-07 12:10:15,VVoltage,04.651
2025-09-07 12:10:15,VVoltage,04.651
2025-09-07 12:10:16,VVoltage,04.651
2025-09-07 12:10:16,VVoltage,04.650
2025-09-07 12:10:16,VVoltage,04.650
2025-09-07 12:10:17,VVoltage,04.649
2025-09-07 12:10:17,VVoltage,04.649
2025-09-07 12:10:17,VVoltage,04.649
2025-09-07 12:10:18,VVoltage,04.648
2025-09-07 12:10:18,VVoltage,04.648
2025-09-07 12:10:18,VVoltage,04.648
2025-09-07 12:10:19,VVoltage,04.647
2025-09-07 12:10:19,VVoltage,04.646
2025-09-07 12:10:19,VVoltage,04.646
2025-09-07 12:10:20,VVoltage,04.646
2025-09-07 12:10:20,VVoltage,04.645
2025-09-07 12:10:20,VVoltage,04.646
2025-09-07 12:10:21,VVoltage,04.645
2025-09-07 12:10:21,VVoltage,04.645
-
On firmware V157 on my device the waveform jumps a lot immediately after the trigger point on frequencies above ~30MHz.
Is it a known bug?
I flashed V149 and now it's OK!
-
I can't seem to find V149 anywhere :-\
Do you mind uploading it somewhere or sending it over? Thanks!
-
On firmware V157 on my device the waveform jumps a lot immediately after the trigger point on frequencies above ~30MHz.
Is it a known bug?
I flashed V149 and now it's OK!
Did you switch modes to high speed?
-
Hello, If someone need I have 9 extra 4086A in Romania.
-
I can't seem to find V149 anywhere :-\
Do you mind uploading it somewhere or sending it over? Thanks!
It's NOT my link, but you have it: https://drive.google.com/file/d/1aaglR_qXuagTngzffufRUz1cbYptBq_K/view
-
Did you switch modes to high speed?
Yes, I did.
On V149 it's able to display up to 70MHz, but I found some bugs with measurements display :(
Rise time is 6.6 ns in high and 10 ns in normal mode.
Does anyone have V156 or V155? Please, share it here!
-
156 as requested
-
Firmware V156 is all good.
But the V157 gives a wobbly signal after trigger point.
It's the same 50MHz signal in "high" sampling mode on the pictures.
All except the first pic are from the V157.
[attachimg=1][attachimg=2][attachimg=3][attachimg=4]
-
Is it a common behavior, or it's my faulty unit?
-
Is it a common behavior, or it's my faulty unit?
I can't say, without access to a 50mhz signal, but I hope not!
-
Is it a common behavior, or it's my faulty unit?
In normal mode the signal look AM modulated with firmware 1.56
In high mode too but to a much lesser extent, the bottom of the waveform wobbles 3/4 division and the top 1/4 division.
With firmware 1.57 it's like yours, rubbish.
-
Is it a common behavior, or it's my faulty unit?
In normal mode the signal look AM modulated with firmware 1.56
In high mode too but to a much lesser extent, the bottom of the waveform wobbles 3/4 division and the top 1/4 division.
With firmware 1.57 it's like yours, rubbish.
Thank you! I'm getting AM-like effect too. But it's fine when the frequency is reaching the Nyquist frequency limit (on primitive trigger and interpolation systems).
So the firmware V157 has a bug that leads to waveform distortions at high frequencies.
(Sorry for overemphasizing. I hope someone from zoyi will read this thread....)
PS: V156 is available here few posts up.
-
I don't think it's likely that they'll read it.
So far I've seen a few genuine comments and posts from Siglent, and from one of the Fnrisi scope makers.
If you want to be sure, report it to them directly.
-
I've sent them this info, let's see what will happen... 8)
-
FixyMixy, https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5899762/#msg5899762 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5899762/#msg5899762)
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5899778/#msg5899778 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5899778/#msg5899778)
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5874902/#msg5874902 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5874902/#msg5874902)
-
FixyMixy
Slowly, but they change things, but also add new bugs at the same time. My guess is that the device was initially developed by another team that left the company for some reason. The new team of programmers doesn't know how it works and moves slowly by the "method of tries and errors". This is typical for small Chinese companies. I've got a light quality meter Opple light master IV, it has the same issue - the Opple light master III was good, but the developers left the company. The new team released Opple light master IV and it works much worse than the previous version, because the new team doesn't understand completely how the initial code works, they stated it in various forums! Now the development of the light master IV is completely abandoned, although it looked really promising at the beginning. I hope Zoyi will not abandon 703 firmware development, but it really feels that they are not really interested in developing it :( There appeared a lot of newer pocket oscilloscopes with better specs recently, maybe they just understand that their device is not competitive anymore. Although I think it could be a great device for it's price if the firmware is made reliable, but look, the price for it dropped twice during the last year, it feels like they just want to get rid of its stock while people are still willing to buy it.
-
let's see what will happen... 8)
Nothing..
-
Is it a common behavior, or it's my faulty unit?
In normal mode the signal look AM modulated with firmware 1.56
In high mode too but to a much lesser extent, the bottom of the waveform wobbles 3/4 division and the top 1/4 division.
With firmware 1.57 it's like yours, rubbish.
Thank you! I'm getting AM-like effect too. But it's fine when the frequency is reaching the Nyquist frequency limit (on primitive trigger and interpolation systems).
So the firmware V157 has a bug that leads to waveform distortions at high frequencies.
(Sorry for overemphasizing. I hope someone from zoyi will read this thread....)
PS: V156 is available here few posts up.
Just to confirm, I got my ZT-703S a couple of weeks ago and first thing I did was loading the latest firmware (V1.57). Happy at first but then, when I checked sinusoidal wave-forms above a few MHz the triggering seemed very unstable.
Thanks to this forum (which I think is great btw :clap: ) I decided to go back to V1.56 and now I'm able to also see stable wave-forms until 30Mhz and probably above (30 is my signal generator's max freq).
So thanks to you guys I'm very happy that for me the scope is now working much better :)
But V1.57 for sure is not OK on my device so hopefully indeed Zoyi will patch this "glitch" soon...
-
PS,
With v1.56 I now get trigger issues when zooming inthe timebase to 250ns/div and less on low frequent square-waves which I think is why Zoyi did the v1.57 patch ::)
I think it only occurs at frequencies below 480kHz (in Hi Run-mode) or 340kHz (in Normal Run-mode).
And then, when lowering the frequency in small steps, I get some "sweet spots" where it can trigger again without those "ghost" traces. (like FixyMixy's post)
Below the "sweet spot" frequencies that are properly displayed:
Run-mode Hi: => 130kHz, 260kHz, 395kHz, 485kHz => above 485kHz always OK
Run-mode Normal:=> 96kHz , 188kHz, 280kHz, 340kHz => above 340kHz always OK.
Let's hope V1.58 will come soon ^-^
-
There appeared a lot of newer pocket oscilloscopes with better specs recently, maybe they just understand that their device is not competitive anymore.
I don't think there is any better alternatives under 100€ price range (i don't concider Fnirsi any better).
-
It's a pity that ajar171 has disappeared again. I had hoped that this person would be able to create a custom firmware for this device, but... I have no expectations from ZOYI in this regard. :--
-
I don't think there is any better alternatives under 100€ price range (i don't concider Fnirsi any better).
Have you considered ds4t252? Admittedly, there is no multimeter in it, and the FFT and the signal generator are rather limited, but as an oscilloscope it is fine. The touch interface is nice and intuitive once you get used to it, compact size.
-
Have you considered ds4t252? Admittedly, there is no multimeter in it, and the FFT and the signal generator are rather limited, but as an oscilloscope it is fine. The touch interface is nice and intuitive once you get used to it, compact size.
My arrived today. It's a great tool. 1mV maximum sensitivity!!! It's unique!
FFT and protocol decoding are very usefull!
Trigger is reliable, 2MB memory.
I'm very happy with it!
It would be very interesting to compare DS4T252 with the Zeeway DSO3D12.
-
Hi,
i received my ZT-703S today. Could anyone tell me where i could find a firmware newer than 139? When i download the firmware from the ZOYI Website, it is V139 .. and not 156 ?
Thanks
EDIT: Ok i found it. Google sent me to an old link on Zoyi website...
-
What version firmware has been determined to be the best of what they've released? 1.39 or 1.56 or other?
-
apollo11fan
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg6039727/#msg6039727 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg6039727/#msg6039727)
-
What version firmware has been determined to be the best of what they've released? 1.39 or 1.56 or other?
Unfortunately, there is no best firmware at the moment. The recent version has some bug fixes and also some new bugs additions (read a few pages back in this forum). Many users still prefer very old versions (1.4x) because they work faster and more predictable, although they are also pocketful of bugs, but these bugs are mostly known and can be taken into consideration during measurements. Some mid-versions (I don't remember what exactly) have malfunctioning AUTO feature (it just doesn't work). Personally, I have no idea what version to use (I mostly use it as a multimeter now), but according to what people write here, 1.56 is better than 1.57, so if you are not sure too, use 1.56.
-
None. We had an opportunity to save this device because a user here was building a custom firmware but i think he abandoned the project. Zoyi would rather make a new device rather than fix this one's firmware. This device is a toy.
-
...This device is a toy.
Well, it's definetly not a toy, because you can measure stuff with it. It is better than nothing and it can be useful tool if you know it's limitations and bugs.
Does anyone really think they can get a professional tool for 70 euros? You can add a zero to the price.
-
I agree, i'm very impressed what this tool can do for this amount of money. Just hoping that Zoyi will continue releasing firmware improvements for this nifty little gadget :-+
-
Does anyone really think they can get a professional tool for 70 euros? You can add a zero to the price.
A cheap pocket oscilloscope without serious bugs is not a miracle anymore. It could be a miracle 3-5 years ago, but not now.
I'm choosing between DSO3D12 and DS4T252, they are comparatively cheap, and the owners of both devices say they are really cool and don't have noticeable bugs and problems. To say the truth, I don't know which one to choose, but it feels like any of them will be better than 703 with the trigger issues that cannot be fixed during more than a year (and I'm not sure it will be ever fixed). I think Zoyi looses time and a lot of prospective customers when it ignores the bug reports of the users, because new devices of the kind appear every year. If they cannot compete by making new powerful hardware, they could at least compete as a producer of reliable low-price tools. Producers should take fast decisions in this growing market, and Zoyi seems to be very slow in reaction and doesn't seem to be a user-friendly company. It's really difficult (= nearly impossible) to reach them and discuss their products. Maybe their company faces bad times now, and they don't have funds or engineers for further development, I don't know. Although we all value that they at least tried to release a few firmware updates for us, but they didn't bother themselves to test them before releasing, this is very sad! Well, we were all waiting for a wonderful firmware update 1 year ago (and it didn't come), so if I could recommend their products then, I definitely wouldn't do it now. Anyway, if they ever make a good firmware version, I would be happy to test it, because I really like the shape and the user interface of this device, it is really very easy to use.
-
Does anyone really think they can get a professional tool for 70 euros? You can add a zero to the price.
A cheap pocket oscilloscope without serious bugs is not a miracle anymore. It could be a miracle 3-5 years ago, but not now.
I completely agree with your opinion. It’s not even a matter of price, but the fact that ZOYI, like the “famous” FNIRSI, very carefully do not notice feedback from customers. Or they simply ignore it. I also like the form factor of this device and I willingly use its multimeter, but when working with an oscilloscope I cannot trust its readings and what it displays on the display is in many cases questionable.
-
ZT-703S Firmware v1.6.3
https://download.s21i.co99.net/8164272/0/0/ABUIABBPGAAg3NLCxwYooJaX1AI.zip?f=703S-%E5%9B%BA%E4%BB%B62025.10.16.zip&v=1760602460
-
In the file it is mentioned that the 250ns trigger issue as well as the wave form on high frequencies is solved
-
In the file it is mentioned that the 250ns trigger issue as well as the wave form on high frequencies is solved
:-+
Curtesy of google image translate....
[attach=1]
-
ZT-703S Firmware v1.6.3
I've made a few fast tests with my NE555 device. Auto trigger works in some time base, and doesn't work in others. Normal/single mode is more usable (at least more chances to get the signal at the trigger place), but there are strange artifacts in 25 and 10 ns time base. How to test: hold the signal at 50ns and view it at 10 and 25 ns. You can see this corruption even with the internal test signal. Besides, the realtime view of 10 and 25 ns is also far from being perfect (waves). This is in the standard mode. High speed mode is even worse: it looses the trigger from 500ns and below. Yet again, they did not even test their "bug fix" in all time bases before releasing this frimware.
As always, new firmware = new bug: when I'm trying to make a screenshot, the device just restarts without a warning and seem to reset some parameters to the ones that were saved the last time you powered off the device in a normal way. I tried to reset to defaults, but I cannot save screenshots anyway...
-
Yet again, they did not even test their "bug fix" in all time bases before releasing this frimware.
Did you expect a miracle to happen? :-DD
-
Did you expect a miracle to happen? :-DD
To say the truth, I don't understand how they release their firmware. It took me 10 minutes to make simple tests in all time scales with different signals and I found all this (and more bugs that were mentioned before but still not fixed), so why can't they do the same before uploading the new firmware to their server? It's not a difficult task to attach the probe to some signal and check the result and correct triggering in all time scales by pressing left and right buttons - even a 3-years old kid can do it! In reality, it's something like this:
Chen: Did you change at least anything in the firmware since the last month?
Sio: Yep, I did.
Chen: OK, our users from eevblog.com are requesting a new firmware version, so I will upload it right away...
-
Why are you talking about the new version 1.6.3? The official website still has version 1.5.7.
-
Why are you talking about the new version 1.6.3? The official website still has version 1.5.7.
idolclub has shared a link for it a few posts ago so we discuss it to find new bugs. There is a chance that Zotek developers read this thread and will fix these bugs some day. At least it feels like the new firmware versions that they released lately try to fix the bugs that we discussed here just some time ago, so I encourage anyone to share the info about the bugs that you find in this forum.
-
Why are you talking about the new version 1.6.3? The official website still has version 1.5.7.
Here is: http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
(https://i.imgur.com/ftf2GSX.jpeg)
Regards... ;-)
... One question: which is the best version for ZT-703S...?
-
I see zoyi site only has the older v139 download. Where are the newer ones?
-
I see zoyi site only has the older v139 download. Where are the newer ones?
Zotektools site has V157
https://zotektools.com/products/triple-in-one-instrument-combining-oscilloscope-multimeter-and-signal-source/
-
Why are you talking about the new version 1.6.3? The official website still has version 1.5.7.
Here is: http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
(https://i.imgur.com/ftf2GSX.jpeg)
Strangely, I get this from the link..... which I know used to work some weeks ago....
[attach=1]
-
Strangely, I get this from the link..... which I know used to work some weeks ago....
This link is still working fine, I just checked.
-
Strangely, I get this from the link..... which I know used to work some weeks ago....
It's a browser issue. Happened to me as well. Clear all cookies and browsing history and try again or use a different browser. Strangely enough it was not working for me even in incognito window until I've cleaned-up everything. My browser was Chrome.
Address should be this: http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html)
On your screenshot the address is slightly different.
-
It's a browser issue. Happened to me as well.
On your screenshot the address is slightly different.
Thank you. You were spot on :-+. And indeed, mine was Chrome too. |O
Sorry for asking you on "helpdesk" issues.
I did try messing wif the address, because I noticed it was different... but it kept changing back to what you saw. I did not stop to think it was looking up local browing data.
Anyways, Thanks again.
-
It's a browser issue. Happened to me as well.
On your screenshot the address is slightly different.
Thank you. You were spot on :-+. And indeed, mine was Chrome too. |O
Sorry for asking you on "helpdesk" issues.
I did try messing wif the address, because I noticed it was different... but it kept changing back to what you saw. I did not stop to think it was looking up local browing data.
Anyways, Thanks again.
Try to open link with Mullvad browser... https://mullvad.net/en/browser
I use Vivaldi, but sometimes link work and sometimes don't work... I think that is because they are using http instead https...
Regards... ;-)
-
I think this is the "official" Zoyi page where there is a new V163 for the ZS-703S:
https://zotektools.com/oscilloscope-multimeter/ (https://zotektools.com/oscilloscope-multimeter/)
-
Is there any changelog?
-
Nope, I couldn't find the change log for V163, it still had the old V156 to V157 changelog...
-
After updating to V1.6.2 it keeps rebooting while taking a screenshot. The saved image is corrupted; only ~2/3 of the screen is saved. I've tried restoring default settings and formatting internal memory via the format option in the imgView APP.
(https://obrazki.elektroda.pl/1833267500_1761337702_thumb.jpg) (https://obrazki.elektroda.pl/1833267500_1761337702.png)
-
Maybe for you V163 solves your issue.
I went back from V157 to V156 and I'm aware of the quirks in this release. Because I found my way around these issues I prefer to wait a bit until I see in the change log what is fixed with V163 before I take the plunge and do the upgrade I think :-\
-
I got V164 from Zoyi and screenshots are working with it. Unfortunately it still suffers from wrong sine interpolation in 10 and 25ns as described in post #1344 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg6072009/#msg6072009) and the usual trigger problems.
-
Hmm, I loaded V163 and that one still has the reboot issue when taking a screenshot.
The triggering improved some but still has issues. And the Runmode High makes sinewaves above approx 25Mhz really unstable... :-BROKE
@SammysHP, from which site did you download V164?
The page I downloaded from still only has V163.
-
@SammysHP, from which site did you download V164?
The page I downloaded from still only has V163.
I've been in direct contact with Zoyi for half a year, testing and reviewing their devices. I reported most of the issues collected here, as well as many more that I discovered during testing.
https://www.sammyshp.de/betablog/tag/zoyi (https://www.sammyshp.de/betablog/tag/zoyi)
The V164 firmware isn't released yet, but it looks like it only fixes the screenshot issue and nothing else compared to V163.
-
@SammysHP, from which site did you download V164?
The page I downloaded from still only has V163.
I've been in direct contact with Zoyi for half a year, testing and reviewing their devices. I reported most of the issues collected here, as well as many more that I discovered during testing.
https://www.sammyshp.de/betablog/tag/zoyi (https://www.sammyshp.de/betablog/tag/zoyi)
The V164 firmware isn't released yet, but it looks like it only fixes the screenshot issue and nothing else compared to V163.
Do you know why Zotek can't fix these basic, known-from-the-beginning flaws? Is it a hardware or human problem?
-
Do you know why Zotek can't fix these basic, known-from-the-beginning flaws? Is it a hardware or human problem?
Not really, communication is difficult. I guess it's just how they work, the size of the team and their priorities. I'm not sure what priorities they have, but I think they do a lot of OEM stuff and their "own" models are more of a byproduct. With the right expectation, most of their devices are quite ok, sometimes with one or more annoying flaws, like the triggering, some artifacts and the battery charging issue of this model. I wish they would open-source their firmware to allow other developers to fix their mistakes, but that would be extremely unlikely.
-
The V164 firmware: https://zotektools.com/products/triple-in-one-instrument-combining-oscilloscope-multimeter-and-signal-source/ (https://zotektools.com/products/triple-in-one-instrument-combining-oscilloscope-multimeter-and-signal-source/)
-
I loaded V164 and at least the screenshot issue is fixed. :-+
Triggering still not perfect and runmode High is gives still very unstable traces at frequencies above say 20MHz or so (I didn't check very well yet)
Kind of weird that if you step down in frequency then at some point it goes from very unstable to suddenly back to stable.
-
The V164 firmware: https://zotektools.com/products/triple-in-one-instrument-combining-oscilloscope-multimeter-and-signal-source/ (https://zotektools.com/products/triple-in-one-instrument-combining-oscilloscope-multimeter-and-signal-source/)
Release notes says: Fixed the issue of automatic restart after saving waveforms in V1.6.3.
Source: http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html) -> ZT-703S firmware upgrade V1.6.4, 2025, 10.28.7z
-
Release notes says: Fixed the issue of automatic restart after saving waveforms in V1.6.3.
It's just my IMHO, but it feels like the latest versions have more lagging than the initial 1.3-1.4 versions. But it's just how I feel, I didn't make any tests.
-
This meter has become my go-to for repair work. I wanted a hand-held, ordered a Siglent SHS820X and couldn't believe how big it was when it arrived. I had ordered the Zoyi 703 at the same time. Anyway, the SHS820 stays in the nicely padded bag while the 703 sits on my desk. It's very accurate after having it a few months now and though sometimes the triggering is faulty, you can still see if data is there, clocks and oscillators, etc. I wish there was a significantly better meter in the same form factor for say, $300?
-
OWON HDS2202S
-
Is there any consensus as to the "best" firmware version to use before SHTF? I'm on v153 and haven't ran into any issues, I'm aware v156 is where the wheels started to fall off, not sure if it's worth installing a newer version.
This meter has become my go-to for repair work. I wanted a hand-held, ordered a Siglent SHS820X and couldn't believe how big it was when it arrived. I had ordered the Zoyi 703 at the same time. Anyway, the SHS820 stays in the nicely padded bag while the 703 sits on my desk. It's very accurate after having it a few months now and though sometimes the triggering is faulty, you can still see if data is there, clocks and oscillators, etc. I wish there was a significantly better meter in the same form factor for say, $300?
I also looked into this and concluded you basically can't get a better Scopemeter than the Zoyi with the same svelte figure. The OWON HDS series can provide a very significant bump in specs at the higher end but it is notably chunkier (and more expensive). You can basically put the Zoyi in your pocket but the OWON is a brick. I look forward to future developments in the budget-friendly multimeter-sized Scopemeter market.
-
Is there any way to fix the nasty red colors after voltages above 220 volts?
+ I'd like to remove the constant red background on up.
I don't understand why they did this? Is the device for children?
Or for people with very low intelligence?
This has significantly reduced the quality of the device, which is already far from perfect without this cheap Chinese fetish.
I didn't order background and font coloring!!!
I often work with high voltage. Do I have to constantly see this horror?????
I used the search function on the topic, but I'm tired of reading... Sorry.
Suggestions...
I'd like to see an oscilloscope option switch to the voltmeter probes in the new versions.
It looks really strange to have separate inputs and not be able to see both at the same time.
-
Is there any way to fix the nasty red colors after voltages above 220 volts?
Unfortunately, there is no open source firmware for this device. You will have to live with it. Or buy a different multimeter :)
One user here tried to make an alternative firmware (https://github.com/kmikl/open-zt703) some time ago (with some promising results), but he disappeared without a trace... all we could understand is that it is not an easy thing to make an alternative firmware for this device and probably it doesn't worth time and effort.
-
Unfortunately, there is no open source firmware for this device. You will have to live with it. Or buy a different multimeter :)
One user here tried to make an alternative firmware (https://github.com/kmikl/open-zt703) some time ago (with some promising results), but he disappeared without a trace... all we could understand is that it is not an easy thing to make an alternative firmware for this device and probably it doesn't worth time and effort.
"Lord, grant me the serenity to accept the things I cannot change, the courage to change the things I can, and the wisdom to know the difference." :D :D :D
-
Release notes says: Fixed the issue of automatic restart after saving waveforms in V1.6.3.
It's just my IMHO, but it feels like the latest versions have more lagging than the initial 1.3-1.4 versions. But it's just how I feel, I didn't make any tests.
Yep, I also noted it. If for instance you press multiple times to change the timebase then sometimes there seems to be a hick-up in response and the screen seems to momentarily freeze...
-
Yep, I also noted it. If for instance you press multiple times to change the timebase then sometimes there seems to be a hick-up in response and the screen seems to momentarily freeze...
It's not only GUI problem but signal viewing as well. For example, if you watch some slow signal in realtime (for example, a capacitor discharge), you can see how it freezes the signal every several seconds, not for a long time, but it's not really realtime anyway. I think the same freezing happens when grabbing faster signals, but we cannot see it because they are too fast. However, it may explain why the trigger skips many signals in my tests - the device is just periodically busy with some unknown stuff and it doesn't have enough CPU time to watch the trigger at the same time :) I want to install some really old firmware to see if the trigger skips signals there as often as in the latest firmware.
-
I want to install some really old firmware to see if the trigger skips signals there as often as in the latest firmware.
I currently have the old version 1.3.8 installed. I've discarded all the updates that came after it as junk.
1.3.8 also has a lot of bugs, so that's my opinion.
-
This is the only solutuon to this problem.
https://www.reddit.com/r/Damnthatsinteresting/s/20F0NaHAb4 (https://www.reddit.com/r/Damnthatsinteresting/s/20F0NaHAb4)
-
Does the ZT-703S have 512kpts or 128 kpts of memory depth? This thread and a few other sources say 512kpts, but the product page says 128kpts?
-
Has anyone figured out what the new "Sample: HD/Peak" setting actually does in the latest ZT-703S firmware?
I noticed that in HD mode the waveform looks much cleaner - less noise - but the scope sometimes seems to switch between a clean and a noisy state depending on the input signal. It makes me wonder if HD mode just enables some kind of automatic low-pass filtering when the high-frequency component is small.
On some signals, HD and Peak look completely identical, which really makes it seem like the device is dynamically changing modes based on the signal.
If that's true, it feels a bit like a software trick rather than real "high definition" sampling. Has anyone else observed this behavior or dug into how it actually works?
-
Does the ZT-703S have 512kpts or 128 kpts of memory depth? This thread and a few other sources say 512kpts, but the product page says 128kpts?
I think you can simply calculate this on the screen. Stop the sweep and stretch the signal so you can see the distance between the points. Then compress the signal so you can see its total stored length. Then divide one by the other to get the number of stored points.
-
Does the ZT-703S have 512kpts or 128 kpts of memory depth? This thread and a few other sources say 512kpts, but the product page says 128kpts?
I think you can simply calculate this on the screen. Stop the sweep and stretch the signal so you can see the distance between the points. Then compress the signal so you can see its total stored length. Then divide one by the other to get the number of stored points.
True!
Interestingly on measuring this, when I set to high speed mode and minimum time-base, I get a record length of 422.9uS, approximate calculation based on the stated rating of 280MSa/s confirms it's definitely around 128kpts, however if I go to calculate the sample rate from that (128,000/(422.9*10^-6)) I'm getting a sample rate of ~303MSa/S, which exceeds the spec quite nicely. It seems unlikely the record length would be some weird figure slightly less than 128k, or could there be a reason for that?
I can't seem to zoom in far enough to accurately measure the distance between points, as if I set the timebase higher the scope doesn't let me zoom in far enough to differentiate points.
-
How are you guys updating to 164? Mine says it needs another 92k to be able to hold the firmware file.
-
How are you guys updating to 164? Mine says it needs another 92k to be able to hold the firmware file.
Just erase everything from memory and try again.
-
How do I delete stuff in memory? When I plug it into pc all I see is a firmware folder. no other files other than that.
-
How do I delete stuff in memory? When I plug it into pc all I see is a firmware folder. no other files other than that.
Restore to defaults from oscilloscope menu
-
How are you guys updating to 164? Mine says it needs another 92k to be able to hold the firmware file.
same here, memory size too low, no memory to be deleted etc. switching on/off didn't help either, switching between normal and high runmode back and forth did the trick for me.
-
same here, memory size too low, no memory to be deleted etc. switching on/off didn't help either, switching between normal and high runmode back and forth did the trick for me.
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5874304/#msg5874304 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5874304/#msg5874304)
1.4.2 / 1.5.5
menu -> MoreApps -> menu (ImgView) -> (There is nothing about Fn keys on the screen) F3 -> F3 (format)
-
same here, memory size too low, no memory to be deleted etc. switching on/off didn't help either, switching between normal and high runmode back and forth did the trick for me.
https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5874304/#msg5874304 (https://www.eevblog.com/forum/testgear/new-zoyi-multimeteroscilloscopes-zt-70xs-up-to-50mhz250msps-(nov-2022)/msg5874304/#msg5874304)
1.4.2 / 1.5.5
menu -> MoreApps -> menu (ImgView) -> (There is nothing about Fn keys on the screen) F3 -> F3 (format)
That didn't work either,
only switching between normal and high runmode back and forth did it me.
-
my 703 has a weird problem I just noticed. Measuring straight DC and AC it is very accurate. When I try to measure a small AC value on a 15VDC supply, the AC displayed jumps all over the place. I've tested and scoped the DC supply and the AC is about 20mv. The meter display jumps up to 14v but generally flickers about .5V. In AC mode with the leads crossed, it reads 0V as it should. Thoughts?
Jerry
-
Does anyone know if the Zoyi firmware files can be installed in the Aneng branded variant as well?
-
Does anyone know if the Zoyi firmware files can be installed in the Aneng branded variant as well?
Yes. It's the same device with different labels.
-
I've just tested firmware ZOYI-703S-FW-V164 ( from http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html) ).
And still no luck: wobbly waveform above few MHz.
-
I've just tested firmware ZOYI-703S-FW-V164 ( from http://www.szzotek.com/h-col-159.html (http://www.szzotek.com/h-col-159.html) ).
And still no luck: wobbly waveform above few MHz.
For me some things improved compared to V1.57 like for instance better waveform display at higher frequencies and improved triggering on single events. But the triggering is still far from perfect depending on horizontal timebase, mainly in the ns range.
Also weird to me is that in the High Speed Run mode the frequencies above 20Mhz or so look worse compared to the Normal Run mode....
Somehow, in High Speed Runmode, at the higher frequencies, there seems to be noise on top of the waveform. Interestingly the waveform on channel 1 seems to improve if you also enable Channel 2, even when not using it???
For now I only use it in the Normal Run mode and have no big issues till frequencies around 30Mhz or so.
Hopefully the next firmware which will fix all issues without introducing new ones :popcorn:
But still love this meter for the simple scope functions and it's accurate multimeter functionality.
-
For me some things improved compared to V1.57 like for instance better waveform display at higher frequencies and improved triggering on single events. But the triggering is still far from perfect depending on horizontal timebase, mainly in the ns range.
Trigger issues are bad. But, IMHO, it's even more important to have accurate waveform representation. On V1.56 I can move (false) trigger point to see the sparse signal event, but it's real waveform, not made up by the bug.
-
I went back from V157 to V156 because V157 was really nok. V156 was better and you could work around most of the issues indeed. V164 is different (not better) but I think I leave it on till the next upgrade... :-\
-
I have noticed, if the signal is somewhat unstable at 100ns using both channels then pressing F3 (TRIG), will make triggering become stable, but if you leave F3 for another function, the signal becomes unstable again. Also just selecting the blue channel in "Vol/Time" will make the signal stable
I have FW 1.6.4
-
I have noticed, if the signal is somewhat unstable at 100ns using both channels then pressing F3 (TRIG), will make triggering become stable, but if you leave F3 for another function, the signal becomes unstable again. Also just selecting the blue channel in "Vol/Time" will make the signal stable
I have FW 1.6.4
This is a very strange version. If you catch the signal in normal mode in 50 us scale (and maybe others), hold it, and use cursors to measure the signal duration, it increases twice at your eyes and so do the measurements. For example, 100 us long signal shows and measures as 200 us signal!
[attach=2]
[attach=3]
Also, there are many other bugs, for example, if you catch the signal, it may look at the trigger correctly, but when you try to move it, the trigger changes its place unpredictably. At 2us long signals and 2us time scale, if you press CURSOR button to adjust cursors, the signal just disappears (actually goes far left beyond the screen). MOVE button has the same pitiful experience. This firmware is a garbage, I just wanted to measure the duration and the amplitude of my signal and I cannot do it... oh no, finally I could, but I wasted ~10 minutes for the task that can be completed in 30 seconds with a reliable oscilloscope :(
I installed ZOYI-703S-FW-V127.ZTK for comparison. There are many trigger issues as well, but you can't believe how fast it is in comparison with 158! I wish Zotek could make a new firmware without all that garbage in 158 that slows it down so horribly, just basic functionality, but reliable.
By the way, the shape of the signal is less neat in 127, which is probably closer to reality.
[attach=1]
158 seems to spend some CPU time for various filtering and it slows it down noticeably. I think most users would rather prefer the true shape of the signal than filtered, but I think it deals with marketing more, they think if the [really ugly] signal will look neat, it will increase sales, but I don't agree with it..
-
Helllo All, I am lot sadisfied with my ZT-703S with old firmware cant go lower of 100 usec in Time/dev, updated firmware to 156 after reading here
that last firmware 164 very slow and lot of bugs. Any suggestion wich fw version is the besat for fast performance in mesurement and best bandwith. 10nsec Time/Dev
Now with fw 156 minimum Time/Dev is 10nsec need testing others functions.
How to eneter in the FFT mode ?
In attachment fimwares 119,121,127,128,129,132,135,138,139,142,155,156,157,163,164 in one zip file the version 164 is the last frtom official ZOYI site.
-
Any suggestion wich fw version is the besat for fast performance in mesurement and best bandwith.
I tried something like 5 random versions starting from 1.27 and ending with the last version and was not satisfied with any of them. You can see the form of the signal but you cannot measure it correctly in many (all?) versions using the cursors or the grid in some zoom scales, it just shows wrong results and you never know when it shows correctly and when it lies. The problem is that there is no complete history file for firmware changes and we don't know what work was made in every version, it's difficult to understand how and when bugs appear and disappear. I think the only way for this device to become usable is to make the firmware open-source, so that professional programmers form all countries could revise it and fix all the bugs, but I'm sure Zoyi will not do it, they'd rather bury this device under tons of their bugs that they cannot fix.
BTW, I'm tired of waiting for a reliable firmware version, so I ordered DSO3D12 last week, I hope it will be better. Just for information, I use 1.42 now, this version is not so slow and horrible as the 1.5.x versions, but the measurements in some zoom levels seem to be also incorrect and there are trigger issues as well :( If you use this oscilloscope for some responsible work, I'd advice you to change it with something more reliable.
-
I will ask Zoyi for firmware logs changes this can help, its a pity that the mesurements are so no reliable.
Thank You for advice
-
For those of you who struggle with calibration, and it doesn't work, try to turn on both the yellow and blue channel, and make the calibration.
Now you will see a bar graph moving for quite some seconds, followed by "Success"
This will cure the DC offset problems
-
Regarding the 250ns problem: I don't know if anybody else experience that sinus, sawtooth, triangle, signals like that easily can be triggered, also in 10ns-250ns.
But if I try to trigger on a square wave BELOW 90kHz, then the trigger does not work from 10ns-250ns
As soon as the square wave frequency is higher than about 100kHz the trigger works fine
-
Regarding the 250ns problem: I don't know if anybody else experience that sinus, sawtooth, triangle, signals like that easily can be triggered, also in 10ns-250ns.
But if I try to trigger on a square wave BELOW 90kHz, then the trigger does not work from 10ns-250ns
As soon as the square wave frequency is higher than about 100kHz the trigger works fine
My scope (still running on V164) does kind of trigger on 80kHz square wave in 10ns-250ns time base but there's a huge difference between Runmode High or Normal and whether I select only channel 1 or both channels:
Runmode High with only Channel 1 enabled looks horrible. I'm avoiding Runmode High as much as possible for now...
-
If you struggle with fully attaching or removing the probes from the BNC connectors, you can remove the black sticker, which peels off easily - then the probes attaches easily
-
Yep, mine was way to tight too. I initially tought I would never be able to remove the BNC connector without breaking the unit...
So I just opened the casing and cut the BNC holes bigger so it fits properly.
For the people with a 3D printer, on thingyverse there is also someone who made a "leaner" probe cover with thinner bottom:
https://www.thingiverse.com/thing:7053840 (https://www.thingiverse.com/thing:7053840)
-
I haven't installed the new software yet but I was using the 703S yesterday and I noticed that no matter what I set on the display menu tab, even if I set it to off, the display switches off at what appears to be the same period of time, I don't want it to switch off at all! most annoying when I am working on the bench, just in the middle of a measurement and the damn thing goes off!
Did this get fixed as my 703 is on boot v1.0.16
app v1.6.4
Its doing the same and driving me nuts!.
-
For all the bugs this meeter has, I am amazed how well it was calibrated at the factory. I have a number of .1%, 10ppm resistors and it reads them nearly perfectly. The one issue I have though, is you need to have it in the correct range when you use the "Rel" function. I don't remember this being an issue with any other meters I have. For instance, if I null the meter and then try to read a 1k resistor, it is out of range. You need to select the correct range for the DUT and then hit "rel".
Jerry
If i remember my fluke 83 does the same!.
-
Does anyone have spare a ME4086A? Just let me know how much you want for IC+Shipping to germany
-
"Does anyone have spare a ME4086A? Just let me know how much you want for IC+Shipping to germany"
Keep this in mind:
https://www.eevblog.com/forum/testgear/zoyi-zotek-zt-703s-fire-hazard-while-charging/ (https://www.eevblog.com/forum/testgear/zoyi-zotek-zt-703s-fire-hazard-while-charging/)
AliExpress
https://www.aliexpress.com/item/1005009303293303.html (https://www.aliexpress.com/item/1005009303293303.html)
You can buy ICs from AliExpress, but I use an external charger because I don't trust the Chinese very much.
-
Does anyone have spare a ME4086A? Just let me know how much you want for IC+Shipping to germany
I don't have it but I asked a few random Aliexpress sellers from China and they are willing to send it, the price is USD 1.23 for one. Not sure about shipping fees to Germany though. I did not order it as there is really no need for it until you replace the battery that was installed by Zotek. This battery has internal overcharging protection and it seems to work. If the original battery is already dead and you want to replace it with a standard battery without protection, then you need to replace the chip as well to prevent possible fire.
-
AliExpress
https://www.aliexpress.com/item/1005009303293303.html (https://www.aliexpress.com/item/1005009303293303.html)
You can buy ICs from AliExpress, but I use an external charger because I don't trust the Chinese very much.
Unfortunately this item is not available in Germany.
This is the only item that is found when searching for "ME4086A": https://aliexpress.com/item/1005010452531322.html (https://aliexpress.com/item/1005010452531322.html)
there is really no need for it until you replace the battery that was installed by Zotek. This battery has internal overcharging protection and it seems to work.
The battery that came with my device it is not rated for 4.35V according to its datasheet. The protection circuit is triggering repeatedly when charging restarts (that causes the blinking of the power button), keeping the voltage well above 4.20V.
-
"This is the only item that is found when searching..."
I think you can order it, from the link you gave.
Here is what a user who purchased this IC wrote, from the link I attached and referring to the same IC:
"Charging as expected now to 4.17v in my zoyi zotek zt-703s."
Happy holidays!
-
Some measurements for using the ZT-703s - if anybody can use
-
Another finding: If you use the internal generator for, let's say sinus wave, then you cannot go lower than 100usec/division - but if you Hold the signal, you can go down to 1usec and "inspect" the signal.
I use FW 1.4.2 which I find the best one
-
Another finding: If you use the internal generator for, let's say sinus wave, then you cannot go lower than 100usec/division - but if you Hold the signal, you can go down to 1usec and "inspect" the signal.
I use FW 1.4.2 which I find the best one
Can you explain what you mean by "HOLD" the signal and tell us how you do it?.
-
Another finding: If you use the internal generator for, let's say sinus wave, then you cannot go lower than 100usec/division - but if you Hold the signal, you can go down to 1usec and "inspect" the signal.
I use FW 1.4.2 which I find the best one
Can you explain what you mean by "HOLD" the signal and tell us how you do it?.
Just press the "Hold/Save" button a short press.... :)
-
Can this thing output a sinewave from the sig genny at the same time in the scope xy mode?, it turns to squarewave as soon as the scope is turned on on mine !.
-
Can this thing output a sinewave from the sig genny at the same time in the scope xy mode?, it turns to squarewave as soon as the scope is turned on on mine !.
Mine can do it - fw 1.4.2
-
AliExpress
https://www.aliexpress.com/item/1005009303293303.html (https://www.aliexpress.com/item/1005009303293303.html)
You can buy ICs from AliExpress, but I use an external charger because I don't trust the Chinese very much.
Unfortunately this item is not available in Germany.
This is the only item that is found when searching for "ME4086A": https://aliexpress.com/item/1005010452531322.html (https://aliexpress.com/item/1005010452531322.html)
there is really no need for it until you replace the battery that was installed by Zotek. This battery has internal overcharging protection and it seems to work.
The battery that came with my device it is not rated for 4.35V according to its datasheet. The protection circuit is triggering repeatedly when charging restarts (that causes the blinking of the power button), keeping the voltage well above 4.20V.
If you want to avoid changing the charge protection IC, and you want to protect the battery, you can also just avoid charging the battery fully by keeping an eye on the charge current with a USB charge monitor, and stop the charging when the current starts dropping in the CV phase
-
Can this thing output a sinewave from the sig genny at the same time in the scope xy mode?, it turns to squarewave as soon as the scope is turned on on mine !.
Mine can do it - fw 1.4.2
You must use the limited sig. gen. menu on the oscilloscope mode "Output setting". Those changes can apply and persist while using the oscilloscope.
If you go though the "More apps" dedicated (and more capable) signal gen option, you can only use that while the app is open. The moment you leave, it will reset to the settings in the limited menu.
Does not depend on fw version.
-
If you want to avoid changing the charge protection IC, and you want to protect the battery, you can also just avoid charging the battery fully by keeping an eye on the charge current with a USB charge monitor, and stop the charging when the current starts dropping in the CV phase
I can tell you that it will not work. We usually connect the usb cable and go to do some other things, and forget about charging, so it will charge to full in 99% of all charges. The only thing why I don't replace the charge controller is that this device is several years on the market and nobody reported any fire issue or battery degradation yet, so the internal battery protection works fine. It's true that the charging voltage is too high for this type of the li-ion battery and the led blinks at the end, but I don't see any issues after 1 year of use, the battery still works as it should, so I think the replacement of the charging controller is not required unless someone replaces the original battery with some other one, that may not manage the higher charging voltage the same way as the original one does. It's more about the feeling to be on the safe side, I think. Maybe I will also replace the charging controller some day, but not sooner than I want to replace the original battery :) Or maybe I will replace the whole device with something better and throw it away until the day when the original battery becomes completely unusable :)
-
If you want to avoid changing the charge protection IC, and you want to protect the battery, you can also just avoid charging the battery fully by keeping an eye on the charge current with a USB charge monitor, and stop the charging when the current starts dropping in the CV phase
I can tell you that it will not work. We usually connect the usb cable and go to do some other things, and forget about charging, so it will charge to full in 99% of all charges. The only thing why I don't replace the charge controller is that this device is several years on the market and nobody reported any fire issue or battery degradation yet, so the internal battery protection works fine. It's true that the charging voltage is too high for this type of the li-ion battery and the led blinks at the end, but I don't see any issues after 1 year of use, the battery still works as it should, so I think the replacement of the charging controller is not required unless someone replaces the original battery with some other one, that may not manage the higher charging voltage the same way as the original one does. It's more about the feeling to be on the safe side, I think. Maybe I will also replace the charging controller some day, but not sooner than I want to replace the original battery :) Or maybe I will replace the whole device with something better and throw it away until the day when the original battery becomes completely unusable :)
You are probably right... :)
I have built myself an HA Esphome ESP32 controller circuit with current sensor, MOSFET switch and USB connections for the same purpose - can and are also used for other products that I don't want to be fully charged
-
I have built myself an HA Esphome ESP32 controller circuit with current sensor, MOSFET switch and USB connections for the same purpose - can and are also used for other products that I don't want to be fully charged
It's a good idea if you want to prolong the life of some really expensive devices. But most people don't bother about the life time of cheap devices. For example, I still keep a HP IPAQ h2210 Pocket PC on Windows Mobile 2003, it's 12 years old and it still works with the original li-ion battery (not too long though). It was really cool at those days. Do I need it now? NO! Do I use it now? NO! So the idea is that there always appears something better before the original battery of the device dies completely! Zoyi 703 with all it's oscilloscope bugs is surely not what you want to use in the year of 2035! yes, it has a fine working multimeter, but I bet you will replace it with something more cool in 3-5 years for sure, so I don't see any reason to try to prolong it's battery life by all means... I already ordered some other pocket oscilloscope and this buggy Zoyi seems to become an ordinary DMM for me in the future.
-
A device rated at 50MHz should be usable at that frequency, no? Even of the fast mode this struggles beyond 47~MHz and 50 is outright unusable.
There are lots of weird trigger bugs and just general trigger issues. Trigger missing the signal instead of the rising edge being centered. CH1 not centering even when CH2 is off.
The amplitude of signals are sometimes completely off between triggers (halved, or worse)? Then they're correct again on another random trigger.
Firmware v1.64, apparently the latest.
Do I have a lemon or is this the general experience? I'm leaning towards initiating a return while I can because for actual use, this is worthless at the current state. It's a toy.
No issues with the DMM but this isn't worth it as an 80$ DMM with a broken OSC.
-
A device rated at 50MHz should be usable at that frequency, no? Even of the fast mode this struggles beyond 47~MHz and 50 is outright unusable.
There are lots of weird trigger bugs and just general trigger issues. Trigger missing the signal instead of the rising edge being centered. CH1 not centering even when CH2 is off.
The amplitude of signals are sometimes completely off between triggers (halved, or worse)? Then they're correct again on another random trigger.
Firmware v1.64, apparently the latest.
Do I have a lemon or is this the general experience? I'm leaning towards initiating a return while I can because for actual use, this is worthless at the current state. It's a toy.
No issues with the DMM but this isn't worth it as an 80$ DMM with a broken OSC.
Agree with all you are writing - however I find v1.4.2 the best version, I have tried.
The oscilloscope IS usable, I think, but you have to know its limitations for now - and hope ZOYI are reading all what comes up in this forum for releasing a much better "final" FW.
It certainly have its trigger issues, but the way I work with it is to avoid triggering below 500nsec - instead I trigger at 500nsec, "Hold" the signal and zoom in to 250-10nsec and "Move" the signal to what I want to look at.
From 25usec timebase and all the way down to 10nsec, the scope will sample at 5nsec intervals (200MHz sample rate), so no data are lost by triggering at 500nsec - and the full sample window is about 600usec in total from 25usec to 10nsec.
The best part is the portability and battery powered and free from relating to ground. But you can also get this from other small scopes
If you come across a scope that is below 100€ and better performance and more "final" firmware, it would be really interesting to hear about
-
A device rated at 50MHz should be usable at that frequency, no? Even of the fast mode this struggles beyond 47~MHz and 50 is outright unusable.
There are lots of weird trigger bugs and just general trigger issues. Trigger missing the signal instead of the rising edge being centered. CH1 not centering even when CH2 is off.
The amplitude of signals are sometimes completely off between triggers (halved, or worse)? Then they're correct again on another random trigger.
Firmware v1.64, apparently the latest.
Do I have a lemon or is this the general experience? I'm leaning towards initiating a return while I can because for actual use, this is worthless at the current state. It's a toy.
No issues with the DMM but this isn't worth it as an 80$ DMM with a broken OSC.
Agree with all you are writing - however I find v1.4.2 the best version, I have tried.
The oscilloscope IS usable, I think, but you have to know its limitations for now - and hope ZOYI are reading all what comes up in this forum for releasing a much better "final" FW.
It certainly have its trigger issues, but the way I work with it is to avoid triggering below 500nsec - instead I trigger at 500nsec, "Hold" the signal and zoom in to 250-10nsec and "Move" the signal to what I want to look at.
From 25usec timebase and all the way down to 10nsec, the scope will sample at 5nsec intervals (200MHz sample rate), so no data are lost by triggering at 500nsec - and the full sample window is about 600usec in total from 25usec to 10nsec.
The best part is the portability and battery powered and free from relating to ground. But you can also get this from other small scopes
If you come across a scope that is below 100€ and better performance and more "final" firmware, it would be really interesting to hear about
Thanks for the tips.
The DSO3D12 is 95USD VAT included, it honestly might be a much better option from what I can find online, but obviously I do not have one to validate that. It seems portable enough even if it isn't technically a handheld. It's battery powered and small enough to fit in your hand.
I'm going to wait until the end of my return window, and see if a new firmware comes out that fixes these issues. Though I doubt it given the presence of some of these issues for months now..
-
I'm going to wait until the end of my return window, and see if a new firmware comes out that fixes these issues. Though I doubt it given the presence of some of these issues for months now..
If you still have time to return it, better do it. Unfortunately, Zoyi cannot make good firmware for it. As for DSO3D12, the positive side of it is that its firmware was disassembled and now anyone can improve it, there is already alternative firmware with better UI design and new features, so this device has some future even if the producers abandon its development some day. The funny thing is that it seems that there are no bugs to fix, as they only add new features that the developer couldn't implement in the original firmware, this means that the device is reliable from the box even with the original firmware. Unfortunately, it's not the case with 703, as only the producer can edit the firmware, and we are only allowed to choose between many versions, and all of them have various bugs. As it was already mentioned here, v1.4.2 is probably one of the most usable, at least because it doesn't slow down the oscilloscope as the latest 1.5.x versions do. But it also has trigger bugs and other issues. This device was promising 1 year ago because it had good hardware for its price, but now we all see that Zoyi failed in the firmware development, and IMHO it's not worth spending money on it today. Evidently, to make this device reliable, they need to hire professional programmers to write new firmware from the beginning or make the current firmware opensource to allow other users find and fix the bugs, but it feels that they will not take a chance with any of these options :(
-
I'm going to wait until the end of my return window, and see if a new firmware comes out that fixes these issues. Though I doubt it given the presence of some of these issues for months now..
I've just received DSO3D12 from China. My first impression: it is better than Zoyi in everything except DMM. The DMM works fine but is not convenient IMHO, it's longer and more difficult to switch the measuring modes than in a typical multimeter, so if you switch between Resistance and Voltage too often, you will hate it. I've heard they made a faster switch in the latest firmware but I still need to try it. The oscilloscope is surely better that Zoyi's, but some buttons look like they were placed randomly without any logic, so you will need time to get used to where the required buttons are and what they do. The trigger always works good in all time scales that I tested and the Auto button is very fast (~ 1 second). Zeeweii is faster than Zoyi both in GUI and when working with the signal. There are more features for measuring. Separate buttons for time and voltage are more convenient than switching those in Zoiy's menu. The only annoying thing is the waving in the beginning and in the end of the signal at high frequencies, kind of the Bart Simpson effect, but this may be typical for cheap oscilloscopes, I don't know. I wanted to compare both with the same signal in different time scales, but Zoyi's trigger doesn't work with many signals, so I cannot do it. Here is just a simple comparison (the same probe P6100 was used): the first pair of photos is 2Mhz internal DSO3D12 generator, and the second pair of photos is 10Mhz ESP32 generator at 2 bits resolution using ledcWrite(), so don't expect super quality. I don't have professional generators for comparison.
[attach=1]
[attach=4]
[attach=3]
[attach=2]
-
I'm going to wait until the end of my return window, and see if a new firmware comes out that fixes these issues. Though I doubt it given the presence of some of these issues for months now..
I've just received DSO3D12 from China. My first impression: it is better than Zoyi in everything except DMM. The DMM works fine but is not convenient IMHO, it's longer and more difficult to switch the measuring modes than in a typical multimeter, so if you switch between Resistance and Voltage too often, you will hate it. I've heard they made a faster switch in the latest firmware but I still need to try it. The oscilloscope is surely better that Zoyi's, but some buttons look like they were placed randomly without any logic, so you will need time to get used to where the required buttons are and what they do. The trigger always works good in all time scales that I tested and the Auto button is very fast (~ 1 second). Zeeweii is faster than Zoyi both in GUI and when working with the signal. There are more features for measuring. Separate buttons for time and voltage are more convenient than switching those in Zoiy's menu. The only annoying thing is the waving in the beginning and in the end of the signal at high frequencies, kind of the Bart Simpson effect, but this may be typical for cheap oscilloscopes, I don't know. I wanted to compare both with the same signal in different time scales, but Zoyi's trigger doesn't work with many signals, so I cannot do it. Here is just a simple comparison (the same probe P6100 was used): the first pair of photos is 2Mhz internal DSO3D12 generator, and the second pair of photos is 10Mhz ESP32 generator at 2 bits resolution using ledcWrite(), so don't expect super quality. I don't have professional generators for comparison.
(Attachment Link)
(Attachment Link)
(Attachment Link)
(Attachment Link)
This is incredibly helpful, thank you!
I have to say, the fit and finish of the DSO3D12 seems quite meh, and from teardowns it doesn't inspire much confidence. The UI does feel clunky from reviews as well, along with some weird priorities (voice control?)
I think I wouldn't be satisfied with either of these devices. It's a shame we can't get something the size/finish of the Zoyi with a functional firmware and perhaps slightly more capable hardware.
I am going to simply return the Zoyi as the end of the return window approaches.
-
I have to say, the fit and finish of the DSO3D12 seems quite meh, and from teardowns it doesn't inspire much confidence. The UI does feel clunky from reviews as well, along with some weird priorities (voice control?)
I think I wouldn't be satisfied with either of these devices.
Well, I don't say anything about its appearance (it's a working device for me but not a sculpture) but at least it does its job. What I like in it is fast and properly working Auto button and stable and correct trigger (BTW, it is automatic by default, so you don't need to bother with its setting like in Zoyi in many cases). Now I can catch the signals that I couldn't see with Zoyi, this is what I wanted when I paid money for it. If you need more for a higher price, check out DS4T252/DS4T1012, they have slightly better screen resolution, touch screen and advanced features - many users are happy and don't say anything bad about them. The price is not above the clouds but it is close to a desktop hantek with much better quality and features, this is one of the reasons why I finally bought Zeeweii - yes it's a toy in comparison with desktop oscilloscopes, but it's a cheap and working toy :)
As far as Zoyi is concerned, I'd also return it if I could, but it's more than 1 year old already, so it's stays as DMM for me, as its DMM satisfies my needs completely, I wouldn't recommend it as an oscilloscope for even simple needs though. Now when I have 2 devices at hand, I completely understand how much time I wasted with Zoyi trying to do the things that are really fast and simple with Zeeweii...
-
Now when I have 2 devices at hand, I completely understand how much time I wasted with Zoyi trying to do the things that are really fast and simple with Zeeweii...
Everything is learned in comparison! When I bought the ZT703, I was primarily hoping to get a working DMM without any problems, and it fulfilled my expectations.
I didn't have much hope for the oscilloscope, so I wasn't too disappointed either. :)
-
I didn't have much hope for the oscilloscope, so I wasn't too disappointed either. :)
And I hoped that the oscilloscope would work well because I already had several DMMs when I decided to buy Zoyi. There are much cheaper DMMs that work not worse than Zoyi's, so I think people who buy 703 are mostly interested to get a pocket oscilloscope in the first place, and the DMM is a kind of bonus :)
-
I didn't have much hope for the oscilloscope, so I wasn't too disappointed either. :)
And I hoped that the oscilloscope would work well because I already had several DMMs when I decided to buy Zoyi. There are much cheaper DMMs that work not worse than Zoyi's, so I think people who buy 703 are mostly interested to get a pocket oscilloscope in the first place, and the DMM is a kind of bonus :)
When I bought this Zoyi, I did it because I thought this was a cheap way to have a basic oscilloscope plus a DMM. As you said, there are a lot of DMMs that are cheaper and more accurate.
-
End of 703s?
https://imgur.com/a/3pnaK7n (https://imgur.com/a/3pnaK7n)
They write something here, but you need an invitation to register on the forum
https://www.mydigit.cn/thread-459243-1-1.html (https://www.mydigit.cn/thread-459243-1-1.html)
-
End of 703s?
https://imgur.com/a/3pnaK7n (https://imgur.com/a/3pnaK7n)
They write something here, but you need an invitation to register on the forum
https://www.mydigit.cn/thread-459243-1-1.html (https://www.mydigit.cn/thread-459243-1-1.html)
Meh, so there goes any hope of them fixing stuff once the new shiny toy is out... :horse:. Return it is then.
I doubt this 706s will come out anytime soon though given that the forum post is from 2024. But who knows.
It's also present in their "happy 2026" poster on the website as well if you pay attention. Not with the 702/703 in the middle - but to the upper left.
-
I think it will be soon released because it is on new years video on zotek web page.
-
Maybe they hired the dude who was working on the new firmware for the zt703.
-
An image from the Chinese forum that I was able to obtain;
Seems like the 706S will also be 50MHz, signal gen will apparently go up to 10MHz, and will have "VFC" (?) - this attached image is from 2024 so it might change. But the "VFC" marking on the one showcased in the new year video matches this early leak so it's probably the case.
Seems like it won't be a worthwhile upgrade vs 703S if the bandwidth is still 50MHz.
[attach=1]
-
Seems like it won't be a worthwhile upgrade vs 703S if the bandwidth is still 50MHz.
If it had 100Mhz, will you buy it when you know how the firmware of 703 is made and supported? ;-)
-
When I bought this Zoyi, I did it because I thought this was a cheap way to have a basic oscilloscope plus a DMM. As you said, there are a lot of DMMs that are cheaper and more accurate.
I bought one basically because Dave said it was OK for the money. I've only had it a few months and so far it has gotten the job done. I think it was a bit under AU$100.
-
VFC is probably voltage frequency converter.
https://www.eevblog.com/forum/testgear/vfc-on-a-multmeter/ (https://www.eevblog.com/forum/testgear/vfc-on-a-multmeter/)
-
VFC is probably voltage frequency converter.
https://www.eevblog.com/forum/testgear/vfc-on-a-multmeter/ (https://www.eevblog.com/forum/testgear/vfc-on-a-multmeter/)
I think it is Variable Frecuency Converter.
-
I don't understand why are they wasting time and energy to develop this crappy sig-gen and all the other bells and whistles when instead they should focus on getting the basics (the scope) working properly.
-
I don't understand why are they wasting time and energy to develop this crappy sig-gen and all the other bells and whistles when instead they should focus on getting the basics (the scope) working properly.
I understand this is not a waste of energy. It allow them selling more.
Many people don't have enough knowledge to know if that is a crappy sig-en or not, but they know what a sig-gen is, and that device has it.
I agree with you, but our interest is different from manufacturers interest.
-
Well obviously I don’t know much about the business side or marketing and i don't run a company. :D
I would think they’d sell more if they made products that are simpler but actually work and focused on building their brand. And maybe someone could even recommend their products to new users.
But by releasing half-baked, buggy products and adding all the unneccesary bells and whistles, they’re ruining their reputation (if there even was one). Once word gets out online about bad products, it’ll be tough to sell new stuff—unless they start a whole new company with new name.
-
Seems like it won't be a worthwhile upgrade vs 703S if the bandwidth is still 50MHz.
If it had 100Mhz, will you buy it when you know how the firmware of 703 is made and supported? ;-)
Maybe? Unsure. It does give a couple years of more software support so there is a small chance they get their sh*t together eventually and fix the bugs ;D
I wouldn't spend more than 60 USD on this toy though given their record. Thankfully my 703s is on its way back. Will report here later how the Ali return process goes.
-
It does give a couple years of more software support so there is a small chance they get their sh*t together eventually and fix the bugs ;D
Or they just took the Fnirsi production policy: when users start to say that some device is buggy, the producers just abandon it and release a new device, basically as buggy as the previous one, but as it's new, the users can hope that it will be better than the previous one. It's a never ending story of rapid good sales of bad products :) I think it works because these products are cheap. A user can buy one trusted device made by a respected company or 10 devices like this and "enjoy" something that kind of works (but it may be enough though for some simple applications). To say the truth, I would be satisfied with 703 if the trigger could work every time it should, but for some reason they cannot fix it. I don't think that this is a hardware problem, it is surely software problem, so if they cannot fix it now and start to sell a new device, I wouldn't expect any stable and predictable work from it... Or there is a little chance that they finally found good programmers who said something like "we will not fix this 703 cr@ppy firmware, let's start a completely new firmware for a new device". But I said that the chance of it is very little because a screenshot posted a few pages above shows 706 with exactly the same UI as 703 has, so maybe they slightly changed the hardware, but it looks like the firmware remains the same, just slightly adapted for the new hardware stuff.
-
Yeah I will wait for reviews and see if problems are fixed before buying any of their products again. Otherwise I'll filter them out going forwards like Fnirsi.
An update on the AliExpress return process as promised; the moment the return package was scanned in transit, AliExpress processed an "advance refund" without the stated inspection and other nonsense.
[attachimg=1]
-
AliExpress processed an "advance refund" without the stated inspection and other nonsense.
The inspection is needed because some unfair users return a bag with sand inside, so they keep the device and get the refund at once, and the seller looses both the device and the money. According to your screenshot, you could also do the same, but only once :)
-
Strange version of firmware is appeared on official web site:
ZOYI-703S-FW-V1612.ZTK.ztk_tmp
V164 Version Upgrade details::
Fixed the issue of automatic restart of waveform saving in V1.6.3
V1612 Version Upgrade details::
Improve cursor triggering issues
-
I've noticed, that beginning from version 1.6XX, line of signal is above zero.
[attachimg=1]
-
I've noticed, that beginning from version 1.6XX, line of signal is above zero.
(Attachment Link)
I noticed this on my unit as well as it shipped with 1.64.
I tried the calibrate option but the outcome was the same, above zero.
I don't have the unit anymore to test the just released firmware.
-
I don't have the unit anymore to test the just released firmware.
You can downgrade your firmware to the version 1.57 for example, and signal level will be OK.
-
Running a calibration on mine reset the voltage back to zero. I ran it on 1.6.12.
I had both channels enabled when starting the calibration. I remember someone mentioned to do this.
-
Running a calibration on mine reset the voltage back to zero. I ran it on 1.6.12.
I had both channels enabled when starting the calibration. I remember someone mentioned to do this.
Yeah I enabled channel 2 as well for the calibration on mine, didn't fix it for me on 1.6.4; so this is probably a bugfix in 1.6.12! :)
-
Talking about the multimeter part of the ZT-703s, there is a warning about which terminals to use when you are going to measure current - actually the warning should be when you press the button to measure voltage, because, you know, measuring voltage when the probes are inserted in "mA" or "A" terminals is not good
I have version v.1.4.2
-
Talking about the multimeter part of the ZT-703s, there is a warning about which terminals to use when you are going to measure current - actually the warning should be when you press the button to measure voltage, because, you know, measuring voltage when the probes are inserted in "mA" or "A" terminals is not good
I have version v.1.4.2
I think they actually added that due to the issue of erroneous readings when mA is selected and leads are in A and vice-versa.
-
Tried out the ZOYI-703S-FW-V1612.ZTK.ztk_tmp FW version for a couple of hours - until now I find it the best version, hope when it is not TMP any longer, it will be even better.
Trigger seems working, also below 500nsec, but still at times some general strange behavior, which is difficult to relate to something
Just noticed, it is not .tmp any longer!
Still some hiccups when in rolling mode (with an exact frequency of 0.65Hz = one hiccup per. 1.54sec --- very strange)
Sometimes, the trigger does not catch a pulse (NORMAL mode), even the repeat rate is 1Hz or slower. I guess the controller is doing something else the moment the pulse edge occurs, but still the most important thing must be to be armed for triggering. I just wonder, what it is doing - nothing is going on, it just should be focusing on the trigger! Maybe it is that 1kHz signal running in the background that needs attention, the moment the pulse edge occurs, so the controller does not see it
-
Tried out the ZOYI-703S-FW-V1612.ZTK.ztk_tmp FW version for a couple of hours - until now I find it the best version
Yeah, there are still some bugs remained, but the trigger became more predictable than in previous versions. It may still skip signals, but at least if it catches a signal, it is shown in the correct position. I think I'll keep this version. The strange waving to the bottom of the screen in 2 last zoom levels is still there sometimes (not all the time). I did not test it completely, but I think it's not as bad as the previous versions were.
-
I've noticed, that beginning from version 1.6XX, line of signal is above zero.
(Attachment Link)
I have same issue. Moreover, I have now realized I can not perform auto calibration, it always fails with "Check failed" message.
-
Try to reset to default.
-
I have same issue. Moreover, I have now realized I can not perform auto calibration, it always fails with "Check failed" message.
Try to enable both chanels before calibrate...
Regards... ;-)
-
I have same issue. Moreover, I have now realized I can not perform auto calibration, it always fails with "Check failed" message.
Try to enable both chanels before calibrate...
Regards... ;-)
Exactly, it is just strange that Zoyi does not enable both channels automatically when you make the calibration - Zoyi had 10 or more firmware updates to make this small improvement, which bother so many people - but still same problem. Somehow they must be aware of the issue - if they ever read eevblog.com. But why not just do it? - When selecting "default setup" it is no problem to enable both channels
-
Hello. I accidentally discovered a custom firmware for the Zoyi ZT-703S on GitHub.
https://github.com/kmikl/open-zt703
-
Hello. I accidentally discovered a custom firmware for the Zoyi ZT-703S on GitHub.
https://github.com/kmikl/open-zt703
its already known (check this thread), but unfortunately the guy did not continue to work on it. i am also not getting any response from him anymore via pm.
would love to support this somehow. cheap opensource scopemeter would be a dream.
max
-
Hello. I accidentally discovered a custom firmware for the Zoyi ZT-703S on GitHub.
https://github.com/kmikl/open-zt703
Yes, there was a very high hope that the device would get a new life with custom firmware and the results were impressive. But, alas, the author disappeared. :'(
-
Hello. I accidentally discovered a custom firmware for the Zoyi ZT-703S on GitHub.
https://github.com/kmikl/open-zt703
its already known (check this thread), but unfortunately the guy did not continue to work on it. i am also not getting any response from him anymore via pm.
would love to support this somehow. cheap opensource scopemeter would be a dream.
max
Sorry, I didn't know that. It's a shame the project wasn't continued.
-
Sorry, I didn't know that. It's a shame the project wasn't continued.
I'm not seeing any concrete evidence it was even started. There's no source there at all.
-
He didn't publish it.
-
The ZEEWEII DSO154Pro has a very convenient feature: when you press and hold the AUTO button for a couple of seconds, continuous auto-synchronization mode is activated, which means that you can measure in places with different signal shapes, frequencies, amplitude, and it automatically adjusts itself all the time, or, for example, the source changes the signal shape, frequency, amplitude, etc. on the fly, and the oscilloscope constantly adjusts itself without user intervention. This function is called RTAuto.
Does the 703s have this function, and if so, how do you enable it?
-
Does the 703s have this function?
No.
-
Anyone who owns a ZT-702S or ZT-Z03S or Aneng AOS02, or Aneng AOS03
Here is a 3D stand that works better than the built-in stand. I've printed this out a month ago and tested it. Also, it is nice that they have spots/slots to put your DMM Probes and Oscilloscope Probes.
https://makerworld.com/en/models/1401325-aneng-aos03-stand#profileId-1453352
I was going to make my own stand but accidently came across this. Assume most might not know about it because it is hard to search on because it is named after the Aneng AOS03 which is not as common as the ZT-703S or 702S
PS: Do not have access to a 3D printer, besides family/friends sometimes Libraries might have a Maker Lab, maybe you can print it there...
Cheers
-
I removed the built-in leg as when installed and not stretched it makes the multimeter wobbly. I don't get how they omitted this obvious defect. For use in standing position this 3d model ofc is far more convenient.
-
Would a couple of you please test your meter(s) by trying to measure AC on a DC value of 15V? I have one supply that on 15V, the AC should be displayed as 20mv, but my 703 jumps all over the place and never gives a good reading. My Agilent DMM (of course) and even my FNIRSI (not even attempting to spell that correctly) both measure around 20mv.
Thanks
-
Would a couple of you please test your meter(s) by trying to measure AC on a DC value of 15V?
-
Would a couple of you please test your meter(s) by trying to measure AC on a DC value of 15V? I have one supply that on 15V, the AC should be displayed as 20mv, but my 703 jumps all over the place and never gives a good reading. My Agilent DMM (of course) and even my FNIRSI (not even attempting to spell that correctly) both measure around 20mv.
Mine jumps around. Stays 0, but the decimal moves, then it flashes 5-something for a split second, repeats. My Fnirsi reads about 340mV while my vintage Tenma reads about 250mV.
-
If anyone is missing Format menu item on newer firmware version (>1.3.9) please check Apps -> Image Viewer -> F1
Format should be an option under F3 button
-
Would a couple of you please test your meter(s) by trying to measure AC on a DC value of 15V? I have one supply that on 15V, the AC should be displayed as 20mv, but my 703 jumps all over the place and never gives a good reading. My Agilent DMM (of course) and even my FNIRSI (not even attempting to spell that correctly) both measure around 20mv.
Thanks
Same behavior on mine. Same also on Aneng AN8007 and OWON CM2100. Trying to measure AC on a DC supply never settles.
-
Would a couple of you please test your meter(s) by trying to measure AC on a DC value of 15V?
What is the frequency of the AC signal?
Or is it simply noise? In that case, the TRMS DMM cannot do much with it.
-
I did some tests with a 19V DC laptop power adapter as I don’t have a 15V DC handy. My 703s presented the same behavior and it jumped all the time. My UT-61e presented the same behavior. I also tested it with my two Fluke 87s and both were able to show around 20mV in the AC range, although the last digit jumped back and forth and never settled.
I hope this helps.
Would a couple of you please test your meter(s) by trying to measure AC on a DC value of 15V? I have one supply that on 15V, the AC should be displayed as 20mv, but my 703 jumps all over the place and never gives a good reading. My Agilent DMM (of course) and even my FNIRSI (not even attempting to spell that correctly) both measure around 20mv.
Thanks
-
AC is US 60hz. all my other meters read it correctly as 20 to 23 mv. This is the first significant error I've found on an otherwise great meter. This is a common function as well. Everybody checks AC riding on a DC supply.
-
ZT-225 displays the value stably in AC/DC mode, but only with 10mVAC precision.
Nevertheless, it is a good indicator that there is a small AC component. Otherwise, it is really 00.00.
In pure AC mode, auto ranging does not work with 10VDC offset and 20mVrms ripple.
You have to select the range manually, then it is stable and accurate.
-
Would a couple of you please test your meter(s) by trying to measure AC on a DC value of 15V?
I used a signal generator set for 60Hz, 56.6mVpp (20mVac), ~10Vdc
The OWON HDS242 in multimeter mode was jumping allover in AC Autorange. If set for 200mV range it measured fine.
The other meters (OWON HDS160, FLuke 83;75, Iso-tec IDM505;507) didn't had any problem measuring the 20mVac in autorange mode.
-
Thanks to everyone who took the time to measure. Clearly setting it to a fixed range probably would solve the problem, and I'll test that tonight.
Thanks again
Edit: testing with manual range solved the problem.
-
At least one thing fixed with this multimeter lol:
[attach=1]
Now charges up to 4.2 V (checked already).
-
Was the thermal pad soldered of the original IC?
-
Yes, it was. Btw the charging current is above 1.1A so it's mandatory to solder this pad. The chip itself does not heat too much but the inductor next to it goes hot.
The link to Aliexpress product: https://www.aliexpress.com/item/1005010452531322.html (https://www.aliexpress.com/item/1005010452531322.html)
-
At least one thing fixed with this multimeter lol:
(Attachment Link)
Now charges up to 4.2 V (checked already).
This is a defect on the 703S?
-
Yes, it is.
The chip they used charges the 18650 battery up to 4.35V. At least they used protected cells so it theoretically should not charge more than 4.20V but for peace of mind and because it's cheap I ordered the correct chips and changed it.
You will probably need a hot air gun to desolder and solder back the new chip.
More info in this topic: https://www.eevblog.com/forum/testgear/zoyi-zotek-zt-703s-fire-hazard-while-charging/ (https://www.eevblog.com/forum/testgear/zoyi-zotek-zt-703s-fire-hazard-while-charging/)
-
Was the thermal pad soldered of the original IC?
It is also a ground pad. The chip wont work without it.
-
New product in the series - ZT-700 (no DMM). It isn't on their Chinese or English websites yet, but it's being sold on the official AliExpress store: https://aliexpress.com/item/1005011753712706.html
[attach=1]
-
New product in the series - ZT-700 (no DMM).
Maybe this warrants a new and separate thread?
The price seems high (US$50-55) - the ZT-701 has similar specs
and costs US$35-40, and the Zeeweii DSO1C81 has better specs
(80MHz/250MSpS) and costs US$40-50.
-
There's also an "upgrade model" ZT-703S+ of the 703S:
- 50 MHZ, 2ch, 280MSpS
- 10ns/div - 20s/div
- 20mV/div - 10V/div
- up to 128kByte record length
- signal generator, sine 10MHz, square/triangle/half/full 2MHz, sawtooth 200kHz
- DMM 25000 count
- screen 3.5"
- size 177x89x40mm, 380g, 3400mAh battery
Not obvious what the "upgrade" is (maybe they have "optimized" the hardware?).
Currently US$119 on eBay:
https://www.ebay.com/itm/177912574579 (https://www.ebay.com/itm/177912574579)
-
There's also an "upgrade model" ZT-703S+ of the 703S:
- 50 MHZ, 2ch, 280MSpS
- 10ns/div - 20s/div
- 20mV/div - 10V/div
- up to 128kByte record length
- signal generator, sine 10MHz, square/triangle/half/full 2MHz, sawtooth 200kHz
- DMM 25000 count
- screen 3.5"
- size 177x89x40mm, 380g, 3400mAh battery
Not obvious what the "upgrade" is (maybe they have "optimized" the hardware?).
Currently US$119 on eBay:
https://www.ebay.com/itm/177912574579 (https://www.ebay.com/itm/177912574579)
It has the V.F.C. markings in some of the renders, which matches what they previously leaked on their new year video as the "ZT-706s".
Perhaps they decided to rebrand it 703s+, which kinda makes sense since the specs are pretty much identical in terms of bandwidth etc.
It's on their second Ali store: https://aliexpress.com/item/1005011766989646.html (https://aliexpress.com/item/1005011766989646.html)
The only other 'improvement' is the slightly higher bandwidth on the signal gen, but nothing else. Still the same clunky overclock for high/normal modes etc.
Not worth looking into pretty much, just a Rev 2 of the 703.
Edit: official comparison: [attachimg=1]
-
Hi everyone,
Is there anyone who can adjust the time in automatic shutdown mode?
I set the time to any value, even when I turn it off, it shuts down in 30 seconds. Has anyone found a solution?
Version: 1.6.12
-
See if it doesn't fix after a reset.
-
Thanks, it's fixed now after resetting.
Also, it seems I need to turn off the BL TIME setting to keep the screen constantly on.
-
Lately this thread focused on the ZT-703S. It has been sustained that its firmware has several flaws, including triggering and/or reset issues, among others. It's also been stated the unsecure charging circuit. In any case, these combo gadgets shouldn't be regarded as professional devices at this price range (IMHO).
But what about the ZT-702S? Beside using an standard charger, being a single channel device should allow better resourses management for the developers. It that sense, has someone tried recent firmwares for it? hopefully with better results?
EDIT: FWIW there is a separate thread for the 702S (https://www.eevblog.com/forum/blog/eevblog-1540-the-$80-zotek-zt-702s-osciloscope-multimeter-review/), but no much participation there.
-
ZT-706S is coming, 66,000 counts.
-
ZT-706S is coming, 66,000 counts.
Do you know specification of ZT-706S?
-
ZT-706S is coming, 66,000 counts.
Where do you have that info from?
On the previous page it was suggested that it recently was released as the ZT-703S+.
-
ZT-706S is coming, 66,000 counts.
Do you know specification of ZT-706S?
-
ZT-706S is coming, 66,000 counts.
Do you know specification of ZT-706S?
If this does actually materialize, it makes the 703S+ even more absurd as a product.
-
So the new model also has that stupid bar graph.
-
Received the ZT-703S+ today, seems like there is not much changed internally between these models. My original ZT-703S has PCB revision 2.2 and this one has 2.5. Can't seem to find any major component differences. Seems like the difference is mostly in software and the color of the housing.
-
. Can't seem to find any major component differences. Seems like the difference is mostly in software and the color of the housing.
Yet another marketing trick. As programmers say, if you cannot make anything new, just change the icons and release the new version :)
-
Received the ZT-703S+ today
Could you please say, what is the software version in your device?
-
Received the ZT-703S+ today
Could you please say, what is the software version in your device?
BOOT: V1.0.17
APP: 1.6.9
-
My Zoyi ZT-703S multimeter has an offset of +-2V in oscilloscope mode. Calibration (with probe disconnected) doesn't solve it. It there a way to manually correct the DC offset somehow or another way to fix this?
-
Calibration (with probe disconnected) doesn't solve it.
Before calibration, you have to enable both channels.
-
Received the ZT-703S+ today, seems like there is not much changed internally between these models. My original ZT-703S has PCB revision 2.2 and this one has 2.5. Can't seem to find any major component differences. Seems like the difference is mostly in software and the color of the housing.
What about the charging chip? Is it still the wrong one?
-
Received the ZT-703S+ today, seems like there is not much changed internally between these models. My original ZT-703S has PCB revision 2.2 and this one has 2.5. Can't seem to find any major component differences. Seems like the difference is mostly in software and the color of the housing.
What about the charging chip? Is it still the wrong one?
Charge IC is still ME4086B. Battery used is also the same.
-
Can't seem to find any major component differences.
minor differences in components
[attach=1]
-
Can you measure the output voltage of the additional LDO located next to the SMPS?
-
Is the most recent version of the firmware V1.6.12?
What is the concensus of this revision?
Should I upgrade from: 1.4.2?
Thanks.
-
Is the most recent version of the firmware V1.6.12?
Yes
Should I upgrade from: 1.4.2?
Each version has some issues.
As for me, the most reliable version is 1.5.7
-
Wonderful. Thank you. I will try the version you have.
Do you know if there is a repository of past versions of the firmware?
Slava Ukraini.
-
Try to find it on this forum or google it.
-
Can't seem to find any major component differences.
minor differences in components
(Attachment Link)
Makes sense, the only differences are in the signal generator components.
-
It looks like there may be another bug in the newer firmware versions for the ZT-703S.
If you disable Channel 2 and use only Channel 1, at 10 ns/div and 200 mV/div (with a 10X probe), instead of a flat line you get some kind of noise/artifacts. However, if both channels are enabled, the issue disappears.
Firmware 1.5.7 works as expected, but the problem is present in 1.6.4 and 1.6.12.
Could someone please check if this is reproducible on your unit?
-
If you disable Channel 2 and use only Channel 1, at 10 ns/div and 200 mV/div (with a 10X probe), instead of a flat line you get some kind of noise/artifacts. However, if both channels are enabled, the issue disappears.
Could someone please check if this is reproducible on your unit?
On low frequency signal, or no signal:
I confirm random waveform fluctuations on solo CH1, about 0.5 vertical divisions at 25ns and 10ns horisontal, at any voltage per div, and in high sampling mode also.
When the second channel is turned on the problem vanishes.
It seems like sinc interpolation amplifies some noise.
CH2 does not have this problem.
On complex signal containing at ~30MHz harmonics or higher:
Regardless of number of enabled channels. At 25 and 10ns horizontal the waveform is very wobbly.
It seems like sinc interpolation works bad.
Single trigger could be chosen from 100ms up to 50ns horisontal. At 100ns and 50ns it misses ~avery third pulse.
Firmware - is v1.6.12 Long awaited synchronization fix, but NOT quite there for 50Mhz!
-
Received the ZT-703S+ today, seems like there is not much changed internally between these models. My original ZT-703S has PCB revision 2.2 and this one has 2.5. Can't seem to find any major component differences. Seems like the difference is mostly in software and the color of the housing.
The flagship features of the ZT-703S+ appear to be a far more capable signal generator. It’s now a user selectable amplitude (0.5v - 5v) with a frequency up to 10Mhz! (Up from a 500Khz fixed at 2.5v).
Isn’t this like 20x the frequency range of the ZT-703S? You are thinking this is just being done in software?
-
So the 706S is available here (https://www.aliexpress.com/item/1005012105196323.html (https://www.aliexpress.com/item/1005012105196323.html)), and the 703S+ available here (https://www.aliexpress.com/item/1005011775300304.html (https://www.aliexpress.com/item/1005011775300304.html)).
And to get this straight, the 703S+ is a 703S with an improved signal generator, and the 706S has the improved DMM, but the two are mutually exclusive?
Lol
-
So the 706S is available here (https://www.aliexpress.com/item/1005012105196323.html (https://www.aliexpress.com/item/1005012105196323.html)), and the 703S+ available here (https://www.aliexpress.com/item/1005011775300304.html (https://www.aliexpress.com/item/1005011775300304.html)).
And to get this straight, the 703S+ is a 703S with an improved signal generator, and the 706S has the improved DMM, but the two are mutually exclusive?
Lol
The 706 carries the improved signal gen from the 703S+ according to specs.
So we have 703S (25K DMM - toy sig gen) / 703S+ (25K DMM - capable sig gen) / 706S (66K DMM, capable sig gen).
Identical oscilloscope hardware on all three it seems.
Weird lineup.
-
At the rate these are being iterated on I'd hold out for the 707S with a 80MHz scope ;D, 706S is quite tempting though, is there any info as to how many bits the siggen DAC is? I'd be assuming 8, could save me buying a dedicated siggen if it's 12 though.
-
Hello! Please help me with a problem with my zt-703s device. It worked fine, I used it to measure 2032 batteries, and the firmware was updated. One day, I turned it on and it started up as usual, using the last mode I used, which was the constant power mode. Now, it beeps once a second and doesn't respond to buttons (only in F1+PWR mode do the buttons work), but it's still possible to take measurements in this mode. I tried formatting the flash drive and updating the firmware, but that didn't help. What should I do?
-
Probably won't work, take out the battery for maybe 5-10 minutes.
-
So the 706S is available here (https://www.aliexpress.com/item/1005012105196323.html (https://www.aliexpress.com/item/1005012105196323.html)), and the 703S+ available here (https://www.aliexpress.com/item/1005011775300304.html (https://www.aliexpress.com/item/1005011775300304.html)).
I've bought my 703S for 46$, but 706s is 105$ at start !! WHY !!?? :-//
[attach=1]
[attach=2]
-
So the 706S is available here (https://www.aliexpress.com/item/1005012105196323.html (https://www.aliexpress.com/item/1005012105196323.html)), and the 703S+ available here (https://www.aliexpress.com/item/1005011775300304.html (https://www.aliexpress.com/item/1005011775300304.html)).
I've bought my 703S for 46$, but 706s is 105$ at start !! WHY !!?? :-//
(Attachment Link)
(Attachment Link)
They raised all prices significantly since last year (or even early this year).
-
I've bought my 703S for 46$, but 706s is 105$ at start !! WHY !!?? :-//
(Attachment Link)
(Attachment Link)
Could be worse.
[attach=1]
-
So it seems that Zoyi is starting to follow in FNIRSI’s footsteps and instead of improving their previous device, they are releasing another one? Their multimeters turn out great, but they seem to have trouble making a good oscilloscope. I guess they are cutting costs too much and not using an FPGA, which is why there are issues like slow performance and artifacts/triggering problems.
//
And looks like it's not so cheap anymore.
-
At this point we wait for someone to do a teardown of the new ZT706s to understand what direction the company has taken |O
-
Seems there's a new v1.8 firmware?
https://www.dt830.com/forum.php?mod=viewthread&tid=8468&highlight= (https://www.dt830.com/forum.php?mod=viewthread&tid=8468&highlight=)
-
Inside this packet is the already known ZOYI-703S-FW-V1612.ZTK version
-
Zoyi sent me the ZT-706S to review, video will be published on Tuesday/Wednesday this week.
-
Seems there's a new v1.8 firmware?
https://www.dt830.com/forum.php?mod=viewthread&tid=8468&highlight= (https://www.dt830.com/forum.php?mod=viewthread&tid=8468&highlight=)
No, that's the date, the 8th of January.
There is no new firmware release.
-
Zoyi sent me the ZT-706S to review, video will be published on Tuesday/Wednesday this week.
It's ready... I guess.
https://www.youtube.com/watch?v=x6gxZIxMqMg (https://www.youtube.com/watch?v=x6gxZIxMqMg)
-
44:24 into the 706S review, the same charger IC model 4086B
-
My Zoyi 703+ motheboard V2.5 this Zoyi 706s motheboard V2.7, 42:17 into the 706S review,