New Zoyi multimeter+oscilloscopes - ZT-70xS, up to 50MHz/250MSps (nov 2022)

[OLderDan]

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...

[csuhi17]

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

[ajar171]

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?

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.

[ajar171]

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

[indman]

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.

[nigard25]

I have a 703s meter. The computer does not detect it. What could be the reason?

[ajar171]

I have a 703s meter. The computer does not detect it. What could be the reason?

Try holding F1, while powering on the meter

[OLderDan]

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.

[LinuxHata]

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.
 

[ajar171]

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.

[Phb]

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.

[bebopdk]

New version 1.57.

V157 Version Upgrade details:

1.Update: Fixed the triggering issue at 250ns

[dn1983]

For information. I've measured capacity of the battery: 2580mAh.

[chebo]

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.

[dn1983]

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

[ajar171]

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

[ajar171]

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.   

[OLderDan]

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. 

[Phb]

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.

[Phb]

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. 

You think it can be fatal enough to stay away from, and warrants going back to 1.4x?

[OLderDan]

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. 

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'

[Phb]

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).

[chebo]

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.

[chebo]

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?

[tol]

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?