New handheld touch DSO, Fnirsi 2C53P, claimed 50MHz/250MSps (April 2024)

[tunk]

- dual channel
- 4.3" 480*272 touch display
- 50MHz, 250MSa/s
- 10mv/div - 10v/div
- 10ns/div - 10s/div
- storage depth up to 64kByte
- signal generator: sine 10MHz, other 3MHz, 0.1-3.0V, duty cycle 0-100%
- digital multimeter
- 4000mAh lithium battery, type-C USB
- size 145x98x35mm

Manual: https://img.wqdres.com/res/0/20240314/43cc9b1cc9ee47d5a7759b015dcd415e.pdf

[tunk]

Starting to show up at aliexpress for $105 (a bit too much?):
https://www.aliexpress.com/item/1005006907937828.html

[csuhi17]

It looks a bit better, I'm not saying it's great, but if it's really going to be around $100, worth it.
And of course if the parameters are real.
We know how Fnirsi tends to lie and talk big.
64kByte is only 8k points.

Which is not visible from the picture.
It has persistence mode 1s and infinite.
math function, basic operations between two channels.

I would like to know what they thought about the data saving function in the multimeter mode.

The display could have been a little bigger, at least 6", then it would be better.

[BrokenYugo]

That they bothered including 20MHz bandwidth filters is nice. Compared to something like the DSO 2512G this seems like a better deal if the firmware is functional.

[csuhi17]

The above link is already live, allowing orders to be sent to Hungary.
For the math function, what can be "-1, -2, |1|, |2|" what can it be used for?

[pcprogrammer]

The above link is already live, allowing orders to be sent to Hungary.
For the math function, what can be "-1, -2, |1|, |2|" what can it be used for?

It supports maybe a third trace with the outcome of:
ch1 + ch2
ch1 - ch2
ch1 * ch2
ch1 / ch2
inverse of ch1
inverse of ch2

The |1| I'm not sure about. Maybe absolute value or average?

The specs for the scope might be correct though. Using overclocked ADC's it can do 250MSa/s and the 64Kbyte as total sample memory might be accurate depending on the FPGA used in the thing.

Fun toy, yes, but worth the price it is selling for, don't think so. For me at the moment 123,27 euro. 

[csuhi17]

It will depend on its performance, it is possible that it will be a match for the owon HDS42s if it meets the expectations.
250Ms/s is not much, but it does not say whether it is halved when using two channels.
For some, even that will be a lot.
Just don't have another 1013d/1014d series.
I look forward to the tests with great interest.

I would cry if the |1| would mean
It would turn an AC sine signal into a full-wave rectified sine.

[csuhi17]

I found a test on the Internet, only a few pictures and text.
I managed to interpret it in such a way that the first series may have some physical problem, and whoever bought it just now will most likely have to return it. 

https://www.mydigit.cn/forum.php?mod=viewthread&tid=451205

[Aldo22]

Do you really need so many "counts" with a DC accuracy of 0.5%+3?
The good old cheap AN870 has 0.05%+3, so the "counts" make more sense.

It's always a bit the same with these many new scopemeters:
They are neither particularly good (handheld) scopes, nor particularly good meters.
And they are not really cheap either.

[tunk]

Firmware update, May 10th 2024 (app+FPGA): https://www.fnirsi.com.cn/download/digit

[csuhi17]

I'll upload some more pictures later.
My first impression of the device before I even turned it on.
Good packaging, feels good in the hand, odorless.

After switching on, the image is good, the display is clearly visible.

After I started some basic tests.
My feelings:  Uhh, ah, 

[pcprogrammer]

I see an Anlogic FPGA, a MTX2088 ADC, but can't see the processor. Is it hidden under the shield?

With only the one ADC chip it is at max 250MSa/s on only one channel. 125MSa/s at best when both channels are enabled.

[csuhi17]

I forgot.

[pcprogrammer]

Still no processor. 

Could they have done it all in the FPGA I wonder. The eagle 4 series has more capabilities, but still.

Edit: I guess they did. See: https://www.cnx-software.com/2018/09/04/licheetang-anlogic-eg4s20-fpga-board-targets-risc-v-development/
and https://github.com/Edragon/Datasheet/blob/master/EG4S20_DataSheet_V1.4.pdf

[csuhi17]

I can't prove it, because the usual method doesn't work for this waste.
The single trigger does not work with a fast time base.


if I pause it, I can't zoom in on it more than a certain time base.

There is a problem with the low frequency, I think it is physical and not software.

I haven't gotten to the DMM and signal generator part yet, I need to take a break to calm down.

maybe
It is possible that the processor is at the bottom of the board, I did not remove it.


There is 12.8 MB of space for images and the update, which is also deleted after the update.

a few pictures.

Square signal 1Hz 10Hz 1kHz 5Mhz and 10Mhz
At 10Hz you can see what the single trigger looks like, this was the best picture out of my 10 attempts. Some had no sign at all.

[csuhi17]

A little comparison with the Owon HDS272.
I am not uploading a picture of Fnirsi, in the case of two channels or with BW limit turned on, because the signal has not changed at all.

I forgot to mention that I used a BNC-BNC cable with a 50 Ohm termination on the scope side.
To be safe, I also checked with Rigol, the signal was a nice square with 50% noise.

[Aldo22]

@csuhi17
Do I understand correctly that it cannot measure the frequencies at 5MHz and 10MHz?

Edit: For comparison 20MHz square from DSO2512G

[csuhi17]

In the pictures above, I focused on the shape of the wave.

There is a problem with the other frequencies, it seems.

I compared the two devices with the square wave so that I could see the difference between the "250MSa/s" Fnirsi and the 250MSa/s Owon, otherwise I can't even estimate the real sampling speed.

The Single trigger does not work, it captures signals randomly.
Sometimes the square signal resembled something like an EKG.

The four images below are the same square wave. 500mVpp 5Mhz
A little problem between 80nS and 200nS time base

[csuhi17]

1mh 4
3rd month 13

A 1 MHz signal needs 4 samples on the display to measure the frequency correctly.
13 for 3Mhz.
My other instruments can tell the frequency from one period.
It measures the 5 MHz frequency as 425.24 kHz, 8 periods are not enough for it. 

This made me cry. the math operation has "-1" that's ok. there is inversion on the other scopes as well.
But the |1| well. for what?

There is a change in amplitude for the two time bases, I don't understand why. 40ns-20ns

The highest frequency I could measure with it is 10Mhz, but it takes 44 periods to calculate it.
This is worse than the 1013D-1014D series.

[Atlan]

You are unteachable.  What did you expect from fnirsi?

[csuhi17]

You are unteachable.  What did you expect from fnirsi?

I was hoping that they wouldn't lie about this weak device.  My brother needed a small basic scope, he tried everything I have and it didn't work for him.  A simple electrician, he needs a few basic things.  I thought that if it knows what they wrote about it, especially since they mentioned the separate memory in it, then it will be fine.  But this is the last one.  I'll write to them, and I'll see what they answer... Unfortunately, I don't have time to deal with it now, the controller just arrived for the engine.

When I apply 500mVpp sine to the input and set an offset for it, it appears for a moment that the signal jumps.
But he came right back after that.
It's like being in AC coupling all the time.
If the Sine signal is slow, its amplitude is apparently smaller.
528mVpp at 1Khz
75mVpp at 1Hz
7.5mVpp at 100mHz

This is much worse than the 1013d-1014d series.
Everyone stay away from Fnirsi oscilloscopes.
I hoped that after DPOX180H the quality would only go up, but no. 

[csuhi17]

The bottom looks like this.
From up to down
EA3036C 3Y6DEM
??
U74HC4053G-P16-R
GS8092

[pcprogrammer]

It looks like it is using a separate processor, but which one that is again the question. 

By the looks of it the 64 pin chip is connected to the display and via the two resistor packs to the FPGA.  So maybe they moved away from the Allwinner controllers to something cheaper or newer.

[csuhi17]

The low frequency distortion was because the coupling was somehow stuck in AC mode.
I switched it to DC to no avail.
OK after switching several times.

1Vpp sine wave:
Good up to ~32.5Mhz with 1 channel
750mVpp at 40Mhz and 340mVpp at 50Mhz.
good up to ~18Mhz with two channels
756mVpp at 35Mhz and 370mVpp at 50Mhz

The single trigger only works with 2uS and above, not with a faster time base.
Fnirsi also confirmed this...

when you pause it and set it to a faster time base, the wave does not change on the display, you cannot pull the wave apart. Fnirsi has not yet given an answer to this.

I played with it a bit, but I couldn't find the 64K memory, compared to the HDS272s, which only has 8k...
It can be similar to 1013d and 1014d.

The part of the multimeter is semi-usable, I did not find a "relative" function in it, not for any measurement.
Similar in accuracy to Owon DMMs.
I like the trend graph. It lasts 1 minute and 25 seconds.

Its signal generator can be used, but at higher frequencies it mixes in a little DC offset.

There are still many problems with this, I hope Fnrisi will not approach it like the previous one, releasing two updates and then trashing it.
 
However, some of the controls are very annoying.

[Aldo22]

I played with it a bit, but I couldn't find the 64K memory, compared to the HDS272s, which only has 8k...

"kByte" is not the same unit as "kpts".

Confusing, but at least they named it correctly this time.
Others write 64k, so you can only guess.

[csuhi17]

I played with it a bit, but I couldn't find the 64K memory, compared to the HDS272s, which only has 8k...

"kByte" is not the same unit as "kpts".

Confusing, but at least they named it correctly this time.
Others write 64k, so you can only guess.

I'm a bit confused by this.

Is 1ps not 1 byte for an 8-bit oscilloscope?
So 64kbyte is not equal to 64k samples?

I no longer know for which scope it was written as 128kBit, I knew that it was only necessary to divide by 8 for that type.

[Aldo22]

I'm a bit confused by this.

Is 1ps not 1 byte for an 8-bit oscilloscope?
So 64kbyte is not equal to 64k samples?

I no longer know for which scope it was written as 128kBit, I knew that it was only necessary to divide by 8 for that type.

You're probably right, I confused it with kBit myself. 
But of course it's still true that it's not the same unit in principle.
You can see that if the scope has more or less than 8bit vertical resolution (or ADC? There is a trap everywhere...)

[pcprogrammer]

I played with it a bit, but I couldn't find the 64K memory, compared to the HDS272s, which only has 8k...

"kByte" is not the same unit as "kpts".

Confusing, but at least they named it correctly this time.
Others write 64k, so you can only guess.

I'm a bit confused by this.

Is 1ps not 1 byte for an 8-bit oscilloscope?
So 64kbyte is not equal to 64k samples?

I no longer know for which scope it was written as 128kBit, I knew that it was only necessary to divide by 8 for that type.

For the 1013D and 1014D it specs 240Kbit which is not even correct since it uses only 4KByte per channel of which only 3Kbyte is effectively used. So of the available 240Kbit in the original FPGA (The Altera one) only 8192 bits are used for storing the samples.

[UniSoft]

MTX2088 ADC

This is Dual Channel 8-bit, 100Msps ADC... (analog AD9288)
datasheet

but can't see the processor. Is it hidden under the shield?

MCU is on bottom side, and it is Synwit SWM34SRET6
datasheet

[pcprogrammer]

MTX2088 ADC

This is Dual Channel 8-bit, 100Msps ADC... (analog AD9288)
datasheet

but can't see the processor. Is it hidden under the shield?

MCU is on bottom side, and it is Synwit SWM34SRET6
datasheet

How did you find the MCU make and model? On csuhi17 his pictures the marks on the chip are removed.

The ADC is most likely the same as used in the 1013D, 1014D and some of the other scopes FNIRSI makes. They can be overclocked but have not tried it myself, because it would require reprogramming the FPGA in the scopes I have. There we assumed it to be the AD9288 or a clone of it, but the markings have been removed, until now in this one where it is still there.

I wonder why they choose the bigger FPGA for this scope, instead of the most likely cheaper ones used in the other scopes.

[UniSoft]

How did you find the MCU make and model? On csuhi17 his pictures the marks on the chip are removed.

Yes, the marks was removed but not complete (not deep enough), and still can see the mark.
drop of alcohol makes the magic

[tunk]

A long and thorough youtube review by ElectroBananas: https://youtu.be/03tuX4vN9GE

Screen dumps from the video:

[DaneLaw]

..........

What's the name of this handheld camera-based magnifying glass?

[tautech]

..........

What's the name of this handheld camera-based magnifying glass?

Gurgle image search finds it on Amazon and AliExpress:
https://www.aliexpress.com/item/1005006652751189.html?gatewayAdapt=4itemAdapt

[DaneLaw]

..........

What's the name of this handheld camera-based magnifying glass?
..

Gurgle image search finds it on Amazon and AliExpress:
https://www.aliexpress.com/item/1005006652751189.html?gatewayAdapt=4itemAdapt

Roger that     thx.

Looks to be quite a span between the offerings, from around 16 to 60 bucks € (incl. EUVAT) with more or less identical hardware  https://www.aliexpress.com/item/1005006741973129.html?
// perhaps there are hardware differences, as some do claim 100x while others 50x - but these x-magnifying ratings on cheap Chinese gadgets are usually as informative as putting your tongue out the window, in the hope of landing the daily news.
Though, It could be handy, such a small self-contained handheld-magnifying lup, if it doesn't drain its battery too fast while in limbo.
- time will tell.. took the plunge on one as it could also be a gift for my elderly mom, who often have issues reading small text.

[tunk]

A video review by Kerry Wong, summed up as: Very disappointing, not recommended.
https://youtu.be/W9v-gkCJYGI

[tunk]

A video review by Learn Electronics Repair, summed up as: Cannot trust what you see on the screen.
https://www.youtu.be/NjtfyVPaW70

[Seekonk]

Anyone tried the 1.7 update yet?

[csuhi17]

Anyone tried the 1.7 update yet?

I tried it, but I didn't notice any significant changes.
Among the compressed files of the update, there is a text file, which describes which errors have been fixed.
I didn't notice any changes on the trigger, it's the same garbage.

[Dave_g8]

Hi,
I see that changes are being made to the FPGA as well as the firmware.
It will be interesting to see if the issues eventually get resolved.

APPV1.7+FPGAV1.5
1. Modify the oscilloscope probe ratio from not saving when powering down to saving when powering down.
2. Fix multimeter curve display bug
3. Modify the conditions for the multimeter’s buzzer to sound
4. Optimized triggering

[Seekonk]

1.7 still doesn't include 100X probe setting.  I was testing some resistors. When I got to the fourth it read infinity. tried everything, had to power down.  On the meter max/min, I got volts for the high and ohms for the low.  Can't see the scope has improved.  AUTO seems to always come up right.  Get too far from that and it is a random image generator.  How did they think it wouldn't be noticed.

[Piton]

Hello. I recently received this device - a complete disappointment. Maybe I got one like this, but it has problems. The problem is with the second channel: noise appears at certain values ​​of the sweep in the middle position of the beam, when the generator is turned on, starting from a frequency of 5-10 MHz and higher, the signal goes directly to the second channel, the higher the frequency, the higher the level of this signal, the frequency meter does not work correctly, you need to turn the channel on and off so that the correct readings appear. Firmware 1.8.? - I don't remember the last digit exactly. It is not on the site, the last one is 1.7. I tried to reflash it - it does not want to, apparently it is not possible to flash it to the previous ones. Opened a dispute, the Chinese guy promised to return $25

[csuhi17]

I think that is very little.
This device is not even worth 50 USD in my opinion.
The first channel of my copy is unusable, the second one is okay, but since it has a lot of bugs, it is lying on my desk like a paperweight.

Not at the bottom of the closet, because it is a good example for me to buy a Fnirsi device only if I have already seen proof that the given device is stable and good.
On youtube, I don't understand why they mislead the masses, respect for the exception, Kerry Wong.
Few people test it normally, and many are obsessed with "Funcation"....

But I think this is just as bad as 1013D/1014D.

I didn't test the bug you brought up because I dropped the whole thing after a quick test of CH1.

Then when a normal update comes out, I'll take it out as soon as possible.

The update consists of two files, there is the APP and the FPGA.
What you find on the site is old, I don't think it will solve your bug, or at least you will generate more bugs with it.
My firmware: APP v1.7, FPGA V1.5

[Piton]

From the external generator everything is more or less normal, it shows the frequency correctly from 20 Hz, but the amplitude is slightly overestimated, and there is a difference in the readings by channels, the second one overestimates more than the first one. Well, there is still a faint hope for a new firmware.

[csuhi17]

Both channels are wrong for me, but CH1 more so.
The error is greater when measuring a higher frequency.
Approximately: CH1=+5%-20% and CH2=+5%-10%
The measurement of the CH1 frequency at a higher frequency is completely wrong, it cannot count.
Curosr and Calculation do not work at the same time.
The BW limit does not work, so if you want to measure the height of a square mark, you have to use a cursor.
There is a phenomenon when you set a time base and the measured voltage increases significantly for one of them. Not always.
Normal or single trigger does not work in the faster time base. Under 2us.
There are many trigger bugs.
I tried to trigger a rare 1Hz and 500us wide pulse with it in a 200us time base, but it didn't work.

There are more, but I can't remember them now.
Have you experienced something similar?

I also hope that they fix it, unlike their previous scopes.

[Piton]

I checked by frequency, both channels measure correctly up to 67 MHz. Single trigger also works up to 2 µS, I couldn't check 1 Hz, my generator gives only 10 ms. If you set 50%, signal distortion appears (ladder), you need to shift the trigger level, 100 pF capacitance shows about 30.

[Hootis Tigglebits]

All I could find was 2C53P_V1.7 on their site which has APP 1.7 and FPGA 1.5. I dont even know where to find which version of them I have. In settings and about it says V1.8.2.2.

Maybe I’m missing something, but is the only way to set the trigger voltage is by using the small triangle on the right edge of the screen?

Update: While playing with this toy some more it locked up. The only way I could turn it off www to hold the reset button. 🤦‍♂️

[battlecoder]

All I could find was 2C53P_V1.7 on their site which has APP 1.7 and FPGA 1.5. I dont even know where to find which version of them I have. In settings and about it says V1.8.2.2.

I'm a bit late to the party, but I also noticed this. My device says 1.8.2.2 but the highest firmware available online is 1.7. Considering that the changelog says that saving the probe ratio was implemented in v1.7 mine must be AT LEAST v1.7 (because it saves that setting).

I really wanted to like this device. I love the form factor and how stable it sits on the bench. The graph in multimeter mode is actually nice, and the frequency generator works "ok" (has some crossover distortion, but the fact that the amplitude can be changed is nice for testing small amplifiers and whatnot).

But the oscilloscope is terrible. The refresh rate is slow,  and the trigger is very inconsistent. Sometimes dragging the trace vertically changes whether it triggers successfully or not  I've also noticed that when using the auto trigger on a series of digital pulses, there's no way to scroll *before* the signal starts (doesn't seem to capture before that), but when I use normal trigger I can suddenly see a bit of the signal before the pulses. Also: The 20 MHz bandwidth limit also doesn't seem to have any effect. I could be here all day talking about weird inconsistencies in this device.

I hoped that after DPOX180H the quality would only go up, but no. 

Same. The DPOX180H is not *bad*. Definitely not perfect, but at least pretty usable. I've tried some glitch signals (from a training demo app) on all the scopes I have, and the DPOX180H performed well. The 2C53P? Missed every single glitch and struggled to trigger in even the most basic examples.