FNIRSI-1013D "100MHz" tablet oscilloscope

[Magua]

fnirsi_1013d.bin v0.024t
https://youtu.be/zgjDdCJl8MA?si=q-_W7qOnZ31SKzlc

[engineer.r152]

Good afternoon! The firmware is fnirsi_1013d_v0.024t. There are problems with saving waveforms in ACQ Long mode. I save the waveform on the video and false steps and a further continuation of the signal appear in the save done.
https://youtu.be/vl45CdwSL7U?feature=shared

[gadak]

In firmware 0.024t after pressing autoset the actual value is still different from the measured oscilloscope, also confirm it is not possible to view the recorded image and video oscillogram.
https://youtu.be/2Tv0On6prPk

[stedivid]

Good afternoon, everyone. Please share the factory firmware of the oscilloscope. accidentally deleted the firmware.

[pcprogrammer]

Good afternoon, everyone. Please share the factory firmware of the oscilloscope. accidentally deleted the firmware.

You can find a couple versions here.

[Atlan]

In firmware 0.024t after pressing autoset the actual value is still different from the measured oscilloscope, also confirm it is not possible to view the recorded image and video oscillogram.
https://youtu.be/2Tv0On6prPk

set 7.5V, connect DC voltage, press autoset. Check the AVG value and write it here. Open the channel menu, highlight AC and then back to DC (don't leave the channel menu). Exit the channel menu, and check the AVG value again and write it here. or video.

[Atlan]

Good afternoon, everyone. Please share the factory firmware of the oscilloscope. accidentally deleted the firmware.

Did you make a flash backup? then you have a problem. You will not have a calibrated oscilloscope.

[Atlan]

fnirsi_1013d.bin v0.024t
https://youtu.be/zgjDdCJl8MA?si=q-_W7qOnZ31SKzlc

fnirsi_1013d.bin v0.024u

[Magua]

fnirsi_1013d.bin v0.024u
The problem is probably something else
https://youtu.be/-bo5IEjTrlA

[tokar]

https://youtu.be/-bo5IEjTrlA

YouTube :  This is a restricted video

[engineer.r152]

There is a departure of the zero position of the beam after pressing the autoset button.
https://youtu.be/RiFy97TEnFI?feature=shared

[tokar]

On the original firmware in DC mode it works exactly like this: shifting the marker “0” to make maximum use of the screen size along the Y axis. When you press the Autoset button, it makes it possible to observe the DC+AC signal, with maximum amplitude, without additional settings.
https://youtu.be/PvyyLhLGvew

[Magua]

https://youtu.be/-bo5IEjTrlA

YouTube :  This is a restricted video

corrected

[engineer.r152]

A proposal to modernize the program. You can add a button that will return the beam to the zero position. On other oscilloscopes, this happens by pressing the beam displacement encoder. For example, you could click on the zone between V+ and V-

[madori]

Hi,
-Way lose Measure on long mode.
-have calibrated with good source and good multimeter, still have doubt,
-rpm calculation, during relative compresion start  (1000 / T) x 60= rpm/min   (have used hantek c650)

Is it there some shorted how and what, just get through all this forum pages. but..
-original firmware backup
-Improving hardware advice if needed
Using tricks

[gadak]

"set 7.5V, connect DC voltage, press autoset. Check the AVG value and write it here. Open the channel menu, highlight AC and then back to DC (don't leave the channel menu). Exit the channel menu, and check the AVG value again and write it here. or video."

I did as you wrote. I also noticed that the voltage drops by 0.3 volts when I connect the dipstick.
https://youtu.be/Hx_uuO6MV24

[madori]

https://youtu.be/pAHYxCXhiyA?si=nX7pqmRBsiu7Y2nP

[Atlan]

What should we learn from the video? 

Otherwise, I thought about whether the problem with the DC shift is also caused by the discharge of the battery.  Because pwm is fixed, but when the battery voltage is low, a different shift is made that does not match the calculation.  How many DC to 5V converter do you have?

[Ruskie]

Hello everyone. Apologies if this question has been asked, but for the nature of it I find it difficult to search.
I have received my 1013D brand new, and immediately patched successfully with the latest alternative fw I found on github. If that matters, I only "prepared" everything and applied the fw "main" .bin file.

Now, I am not an expert but when turning on the original fw I had this screen as in OriginalFW.jpg.
After installing the new fw I had this screen as in CustomFW.jpg.

Is it normal?
I figured out that the Trigger symbol is placed higher, with the new fw there is new option set by default to have Trigger auto-placed at 50%.
But what about the offset between the 1> / 2> channel symbols and their respective "empty" signals?
Is it correct that they are not aligned anymore?

EDIT: I found that performing calibration (Menu -> System setting -> Baseline calibration) it gets back to 1> and signal level to be on the same page.
Was that "my problem"? That is, after fw changes the oscilloscope need to be recalibrated? Thanks

[Atlan]

You have the 0.006 version there and it is currently 0.024s, see the back page.  There is a huge difference between them.
0.024t and higer is beta verzia
Manual is on page 82

[Ruskie]

You have the 0.006 version there and it is currently 0.024s, see the back page.  There is a huge difference between them.
0.024t and higer is beta verzia
Manual is on page 82

Oh! Wow! It's that I found a "FNIRSI alternative fw repository" on github and linked in a message from somebody here, so I assumed it was the most updated, thank you for the information.
However, I found the latest yesterday evening (if I'm not wrong it's 0.24s) and the manual you linked, and one thing that I can't really understand is this:

In the oscilloscope menu, click on the option Base line calibration.
The required calibration voltages for the ranges are:
   100mV/div 300mV
   200mV/div 600mV
   500mV/div 1.5V
   1V/div  3V
   2.5V/div 7.5V
   5V/div  15V
Use an analog voltage source, or battery voltage that has zero ripple.

Does this mean that the calibration process is no longer "self contained", and I need some "external tool" of some sort? If so, is there any more detailed explanation, in a document or video?

[csuhi17]

Does this mean that the calibration process is no longer "self contained", and I need some "external tool" of some sort? If so, is there any more detailed explanation, in a document or video?

This is how you should do it.

Added possibility to reset calibration values. (if a bad calibration occurs) Added notification of a faulty calibration if the offset cannot be set (only if there is some hardware problem, bad ad converter, missing ad converter, problem with the offset voltage setting)

Input divider calibration is enabled when the oscilloscope is turned on for the first time and baseline calibration is used.

Calling up the calibration of the input divider is possible only through the menu by resetting the calibration values. (or by deleting the data on the sd card where the configuration data is located. NEED SDCART READER No It can be done with a card stored in the oscilloscope. )

After successful calibration of the input divider and switching off the oscilloscope, the data is written to the SD card. (Unless you change the burnt components on the input circuits, it will no longer be needed - that is, if you do not erase, do not replace the sd card)

If the calibration is started again, only the base level calibration will be performed. i.e. 0 is found. (What sometimes needs to be done)

By uploading the firmware, the calibration of the input divider DOES NOT CHANGE.

[Ruskie]

This is how you should do it.

Apologies, this is for sure entirely my fault but... "how"?
From the video I can understand there is a voltmeter attached, ok... but what is connected to what is not visibile. Plus, the label on the scope says "set to 300mv"... but in the voltmeter you "measure", you don't "set" anything; so, do I need a signal generator as well, or a variable power source that I can set to those values?

[Atlan]

Yes

[Ruskie]

Yes

Thanks Atlan. This is it then. I am out of luck for now.  I have no variable power source.
Does this mean that if I flash the latest version of the fw it would give "wrong" figures unless I perform the calibration as described?