-
instead of solving the problems this model has, they insert the "old" one into a new dress and try to fool everybody into buying another one with the same bugs
this is not a bug, this is a feature
-
instead of solving the problems this model has, they insert the "old" one into a new dress and try to fool everybody into buying another one with the same bugs
this is not a bug, this is a feature
-
I don't know how legitimate this method is.:
Fnirsi's sampling is 500Ms/s, i.e. there are 2ns between two samples.
The storage/memory depth is 120kp, that is, if you make a single shoot in 20us/div from a 50Mhz color signal, it should be smooth.
But if you zoom in on it
There is 10ns between two points and the total length of the signal is 20us*12div, that is, it is only 24k samples.
If you don't watch it in 20us/div, but in 200us/div, you will see it better with a 5Mhz signal.
I couldn't insert the picture into the text, 16 belongs to 18 and 19 to 20
-
I don't know how legitimate this method is.:
Well it sounds reasonable to me.
Fnirsi's sampling is 500Ms/s, i.e. there are 2ns between two samples.
The storage/memory depth is 120kp, that is, if you make a single shoot in 20us/div from a 50Mhz color signal, it should be smooth.
(Attachment Link)
But if you zoom in on it
(Attachment Link)
There is 10ns between two points and the total length of the signal is 20us*12div, that is, it is only 24k samples.
If you don't watch it in 20us/div, but in 200us/div, you will see it better with a 5Mhz signal.
(Attachment Link) (Attachment Link)
I couldn't insert the picture into the text, 16 belongs to 18 and 19 to 20
I tried to measure similarly, but under different parameters, and got the same results.
I single-trigger captured 240ms of a 1Mhz waveform (i.e: A full screen of data (12 divisions) at 20ms per division).
Then I zoomed in horizontally until I was able to measure the distance between data points. At 10uS I was getting exactly 1 data point per division. In fact, the oscilloscope didn't let me to go finer than 10uS per division (probably because at that point I was already at one data point per division).
So, 240 ms of waveform = 240000 us of data .... divided by 10us of separation between points = 24K points.
-
I found myself wishing on multiple occasions that I could scroll around more. The triggering options are so limited (no holdoff, no pulse triggers, no video triggers etc.) that it would be at least nice to have more memory so I can still see the part I was interested in.
-
Can you tell me about a device in this price category that can do what you wrote above?
Neither can the OWON HDS2202S, even though it is a nearly 300 USD device. -
A 15 year old entry level scope like the 1052E has all those trigger features, I assume it's not a hardware limitation? Guess there was just no budget for the software to add these things to ~100EUR scopes or they wanted to keep the UI simple?
-
A 15 year old entry level scope like the 1052E has all those trigger features, I assume it's not a hardware limitation? Guess there was just no budget for the software to add these things to ~100EUR scopes or they wanted to keep the UI simple?
They will release someday a new model with one or two new features. At least now they design a new case for the same model, and start selling as a new product. Profit is the objective. They all do that. we just have to adapt to these buggy and unfinished devices. I use them in situations were they could be destroyed, instead of using a good and expensive scope. -
I think they mostly focus on big, flashy things you can easily advertise like bandwidth or the digital phosphor display. It's harder to sell 'we implemented trigger holdoff' or 'we now have absolute position readout for trigger level and cursors'.
-
If you meant the Rigol DS1052E, I don't think it's in the same category. But it's fine.
The fact that he is 15 years old does not mean that he knows less. there are older but much better ones, just in a different price category.
I think advanced triggering also has hardware requirements, not just software.
Compared to the fact that it has a 24k memory depth of 500Ms or more, the trigger of the single is occasionally delayed.
Neither the 4/8k HDS272 nor the 15k? dso1511e+ I couldn't do it.
The tested signal is sine 10Mhz.
So I don't think any of the trigger options listed above could be used. Although a "persist" might have been feasible.
And the phosphoric property was simply colored in the line.
The small dots are just for decoration, I don't think they are real patterns.
In questionable circuits, it's good to measure with this first, it's not that expensive, but you can't trust it 100%.
-
New firmware V4 has been released.
Updated to V4. I didn't notice any deterioration. But I also didn’t notice the improvements that worried me.
-
Fixes:
1: The thickness of the waveform is reduced, making the waveform thinner and clearer.
2: The vertical lines of the square wave are brighter and more obvious
So just some further tweaks to the waveform display. Haven't tried it, but better than nothing, I guess. -
I've tried it, and I'm going back to the previous version:
-with no signal, the measurement bar is updating several times a second with nonsensical values
-the scope becomes very sluggish both in auto mode and pressing keys.
It takes almost a second to update after a V+ press,
pressing H+ gives a truncated trace for a second, only then refreshes.
quote author=Rooster Cogburn link=topic=377636.msg5081950#msg5081950 date=1695823642]
Fixes:
1: The thickness of the waveform is reduced, making the waveform thinner and clearer.
2: The vertical lines of the square wave are brighter and more obvious
So just some further tweaks to the waveform display. Haven't tried it, but better than nothing, I guess.
[/quote] -
I've tried it, and I'm going back to the previous version:
[/quote]
-with no signal, the measurement bar is updating several times a second with nonsensical values
-the scope becomes very sluggish both in auto mode and pressing keys.
It takes almost a second to update after a V+ press,
pressing H+ gives a truncated trace for a second, only then refreshes.
quote author=Rooster Cogburn link=topic=377636.msg5081950#msg5081950 date=1695823642]
Fixes:
1: The thickness of the waveform is reduced, making the waveform thinner and clearer.
2: The vertical lines of the square wave are brighter and more obvious
So just some further tweaks to the waveform display. Haven't tried it, but better than nothing, I guess.
there's no V4 on fnirsi website, maybe it's beta version? -
Hello, I received my DPOX180H a few days ago. I really thought I bought a good portable oscilloscope for the money and I became convinced to buy it by all those reviews on YouTube that praise it so much. Of course reading this thread, makes me have a lot of doubts whether I should start using it as I cannot accept that a device you tend to depend upon so much for certain type of troubleshooting, can perform so poorly. People here are even talking about a hardware mod (the two smd capacitors) to make it behave somewhat more reliably. No, until a proper firmware is out, which I admit I'm doubtful if this ever happens, I'll put it on a shelf out of sight. As if this oscilloscope wasn't a bad enough experience, today I received the FNIRSI DSO-TC3. I had bought it mainly because of its build quality, which is better than your standard Chinese 20 Euros device. My main use for this device would be the ESR meter. Guess what, everything works except of the ESR meter. It treats every capacitor as having practically no internal resistance, the perfect capacitor! Others have also recognized the problem but not the YouTube reviewers! It came with V0.3 of the firmware and I don't know if this is the culprit or whatever. Very disappointed by FNIRSI!
-
Hello, I received my DPOX180H a few days ago. I really thought I bought a good portable oscilloscope for the money and I became convinced to buy it by all those reviews on YouTube that praise it so much. Of course reading this thread, makes me have a lot of doubts whether I should start using it as I cannot accept that a device you tend to depend upon so much for certain type of troubleshooting, can perform so poorly. People here are even talking about a hardware mod (the two smd capacitors) to make it behave somewhat more reliably. No, until a proper firmware is out, which I admit I'm doubtful if this ever happens, I'll put it on a shelf out of sight. As if this oscilloscope wasn't a bad enough experience, today I received the FNIRSI DSO-TC3. I had bought it mainly because of its build quality, which is better than your standard Chinese 20 Euros device. My main use for this device would be the ESR meter. Guess what, everything works except of the ESR meter. It treats every capacitor as having practically no internal resistance, the perfect capacitor! Others have also recognized the problem but not the YouTube reviewers! It came with V0.3 of the firmware and I don't know if this is the culprit or whatever. Very disappointed by FNIRSI!
Don't believe in all youtube reviews, the majority are from people who get paid or receive free products from manufacturers, like influencers (liars) and that's what they do, lie to you so that you click and buy. The scope is nice for some tasks, but for others no way. -
Anyone know if there's a way to dim the screen on this thing? I'm sure default brightness would be great for daylight but when just testing something quickly of an evening it's damn bright. Might make the battery last a bit longer too.
-
When I wanted to buy the DSO-TC3, the videos I watched on YouTube were quite downgraded, so I didn't order one.
Does "HF rejection" work for anyone in the trigger menu? I don't see the effect.
Also, the HardBandwidth limit at CH1 does not seem appropriate either.
Shouldn't the frequency above 20Mhz be completely cut off?
For me, it reduced the 60Mhz signal from 800mV to 400mV. the slow 20kHz signal was not modified.
Is it possible that the error could have been caused by the fact that I replaced the capacitors? -
I've got a message from Fnirsi with this download link.
there's no V4 on fnirsi website, maybe it's beta version?
-
RAPo What's the point my friend, you already tested V4 and it's worse than what we already have!
-
It could be something specific to my situation
I would love to hear what other users experience.
Maybe some one needs thinner traces, I'm not really bothered.RAPo What's the point my friend, you already tested V4 and it's worse than what we already have!
-
RAPo It's like they try to heal an amputated leg with a band-aid!
-
Don't believe in all youtube reviews, the majority are from people who get paid or receive free products from manufacturers, like influencers (liars) and that's what they do, lie to you so that you click and buy.
Yep. Most people who go to youtube looking for "reviews" are looking for confirmation that they're making a good choice.
Saying bad things in a video means most people will stop watching it half way though. No Youtuber wants that.The scope is nice for some tasks, but for others no way.
Yep. Fnirsi doesn't really make anything that could be your only oscilloscope but they make a lot of things that can be useful for secondary jobs, or for taking to Arduino club (for example).
eg. I use a little toy 'scope because it doesn't take up much space on the bench when I'm doing things on camera. It's plenty good enough to just show a the shape of a wave and that's all I need.
(Having said that: ANY 'scope is better than no 'scope at all)
-
I've tried it, and I'm going back to the previous version:
-with no signal, the measurement bar is updating several times a second with nonsensical values
-the scope becomes very sluggish both in auto mode and pressing keys.
It takes almost a second to update after a V+ press,
pressing H+ gives a truncated trace for a second, only then refreshes.
quote author=Rooster Cogburn link=topic=377636.msg5081950#msg5081950 date=1695823642]
Fixes:
1: The thickness of the waveform is reduced, making the waveform thinner and clearer.
2: The vertical lines of the square wave are brighter and more obvious
So just some further tweaks to the waveform display. Haven't tried it, but better than nothing, I guess.
it is possible to downgrade?
what about "transparent menus" in new version? can be adjusted now? -
Yes, a downgrade is possible.
No idea about the transparent menus I'm back on V30.I've tried it, and I'm going back to the previous version:
-with no signal, the measurement bar is updating several times a second with nonsensical values
-the scope becomes very sluggish both in auto mode and pressing keys.
It takes almost a second to update after a V+ press,
pressing H+ gives a truncated trace for a second, only then refreshes.
quote author=Rooster Cogburn link=topic=377636.msg5081950#msg5081950 date=1695823642]
Fixes:
1: The thickness of the waveform is reduced, making the waveform thinner and clearer.
2: The vertical lines of the square wave are brighter and more obvious
So just some further tweaks to the waveform display. Haven't tried it, but better than nothing, I guess.
it is possible to downgrade?
what about "transparent menus" in new version? can be adjusted now?