FNIRSI-1013D "100MHz" tablet oscilloscope

[Atlan]

What works?  It must work to get to the calibration reset via usb screen.  To see if the calibration is within limits.  I would like a picture with calibration data.  Well thank you.

[boojum]

I would like a picture with calibration data.

My results. (might be useful too)
Successfully calibrated with using 100% analog source - 4 x Li Ion + multi-turn potentiometer .

[tokar]

Calibration in version 021c.  Voltage source: battery.

[Atlan]

I hope that we can close the issue of calibration.  That it works for everyone, via usb menu!

The top photo is kind of blue. text in menu is white?

[boojum]

The top photo is kind of blue. text in menu is white?

Yeah. Text is white. It lloked blue probably because I was shooting at a bit of angle.

[facekim]

Hello, I get a calibration error in the last step of 15v.
I don't think my contribution will be of much use either, my mini power supply is 500mv, so maybe that's the reason for the error, anyway I'll send a photo of the data returned.

Thanks for your work.

[Atlan]

Use the led, for example the red one, it works as a zener and set it to 300mV with a 10k potentiometer.  The calibration ends with an error, because the range for the connected voltage is in numbers from 3000000-4000000.  As you can see in the picture, you are outside the limits for the 100mV/div range (300mV is expected at the input)

[Atlan]

v0.021e Small corrections to the calibration code. Added text if there is a problem with offset calibration. (which no one will ever see, unless there is a HW problem). Error notification, right at the problem calibration, not at the end of the calibration.

[bffargo]

I wanted to use the rd6006, but when I saw what it had on the output, I used an analog source.  See text up.

Thanks Atlan. I finally got mine calibrated. My bench 30V/5A SMPS box was extremely noisy (200+mv sometimes higher), so I switched to a linear one that was about 50-70mv noise, but actually fed that into an RD6006 to do the settings much easier digitally vs. analog dial.  Perhaps your input supply on the RD was noisy making it worse?

In any case I got it calibrated, but not after having 15V fail 3 times in a row. If I keyed in the following on the RD6006, I got the following metered at the BNC inputs: (I think these are the steps, but if not, you'll get the point)

RD Set = Actual metered V at BCN
.30 = .3006
.60 = .6004
1.50 = 1.503
3.00 = 3.001
7.5 = 7.499
15.0 = 14.97

So therefore I was naturally trying to up 15.0 to 15.03 on the RD6006 which then leveled off at 15.00x V at the BNC. But every time I did that it said calibration failed.  Therefore on the final time I just let it have the values above with the 15.0V sagging just the hair, and then it calibrated just fine not trying to force an exact perfect value.

I do have some more BNC splitters and stuff coming to make this much easier in the future with cleaner more-easy-to-redo setup. But thanks again.

Hello, I get a calibration error in the last step of 15v.

See my comment above for a failure a 15V as well until I stopped trying to "perfect it".

[Atlan]

The latest version will write immediately when a failure occurs.  Previously, they waited until the end and so wrote an error if it occurred.  It's a shame that you didn't take pictures of the values ​​when the failure occurred.

[tokar]

... Added text if there is a problem with offset calibration. (which no one will ever see, unless there is a HW problem)...

I created an error and saw the message.

[Atlan]

When calibrating the base, nothing should be connected to the BNC

v0.021f
I simplified the calibration process, in the case of an error, the number 4000001 appears in the calibration values.

[Atlan]

Correction of minor graphics errors, addition of the reaction of pressing the 50% button in the channel menu. Nothing important.

[Atlan]

In firmware 0.006 {also v0. 017d} automation works well in DC mode?  It also works for a DC signal, e.g. 5V from the battery?

Except for the error that the signal is not shifted from the center line.  .

[tokar]

v0017d:
CH1 & CH2 included. Calibration without connectors connected.
I press autoset - sensitivity of channels 1 & 2 - 500mV/div.
Voltage source: battery. The polarity is positive.
I apply 1v, autoset - sensitivity unchanged.
I supply 2V, autoset - sensitivity unchanged.
I supply 2.25V, autoset - sensitivity of CH1 - 500mV/div, CH2 - 50mV/div.
From “0” 4.5 cells, and an increase in sensitivity (a decrease is needed).
When 5V is applied (sensitivity 5V/div), the same thing happens: after pressing autoset, the sensitivity of CH1 is 500mv/div, CH2 is 50mv/div. And the oscilloscope voltmeter readings channel 1 - 2.26V, channel 2 - 467mV.

[Atlan]

Tokar: AC signals  is ok?

[tokar]

v0017d:
Channels 1 & 2 included. Calibration without connectors connected.
I press autoset - sensitivity of channels 1 & 2 - 500mV/div.
Modes AC, DC.
Voltage source sine generator 100Hz. There is no DS at the output.
I supply 40mV, autoset - sensitivity 50mV/div.
I increase it to the limit (70 mV rms), autoset - the sensitivity of channels 1 & 2 becomes 100 mV / div.
I increase it to the limit (155mV rms), autoset - the sensitivity of channels 1 & 2 becomes 200mv/div.
I increase it to the limit (290 mV rms), autoset - the sensitivity of channels 1 & 2 becomes 500 mV / div.
I increase it to the limit (740 mV rms), autoset - the sensitivity of channels 1 & 2 becomes 1v / div.
And so on...
I think everything is fine with AC.

[Atlan]

I see that in auto mode it does not set the offset according to the selected sensitivity.  It was also forgotten during the calibration.  Let's fix it.

The flood code of the auto-setting, the original firmware probably does not exist in C?

[Atlan]

Does the original firmware also detect whether it is AC or DC when you press "auto"?  Or does he leave this choice to the operator?

[pcprogrammer]

You can take a look at how far I got with the reversal. Noticed I did not upload the last state of affairs, so just did it now. https://github.com/pecostm32/FNIRSI-1013D-1014D-Hack/tree/main/Test%20code/fnirsi_1013d_original_scope

In the scope_functions.c there is a function scope_do_auto_setup. Not fully finished but maybe it helps.

[tokar]

Does the original firmware also detect whether it is AC or DC when you press "auto"?  Or does he leave this choice to the operator?

I applied AC + DC to channel 1, and only AC to channel 2. Visually (by the AC, DC icons in the channel menu) there is no search for whether channels belong to AC or DC. The polarity and complex signal level (AC + DC) in DC mode are taken into account. And the level of the AC signal (without DC) in AC mode.
And each channel (together or separately) can be expanded to fill the entire screen (Y=8 cells). And not Y=4.5 cells per channel before the limit, as is now implemented in modified firmware.

[Atlan]

What happens if you use only one channel, switched to AC.  And if you apply 1khz with an offset of e.g. 1V to the input (are you thinking of a dc+ac signal?)

 I will come across something interesting
scope_get_long_timebase_data

[tokar]

Fnirsi original.
Signals were given on all photos:
AC = 1v, 1kHz rms
DC = 1v

Photo 1 - AC mode, signal only AC.
Photo 2 - AC mode, signal AC+DC. 
Photo 3 - DC mode, AC+DC signal.
All oscillograms after pressing automatic.

[Atlan]

OK, thank you.  So the ac/dc mode must be selected by the user.

[_AVP_]

found one more problem - oscilloscope gives a SD error 3..5 times of 10 starts. Tryed  two different cards with 8Gb capacity. FW loaded by firmware loader. Tryed one more 32Gb card - no change. Rewrited config sector, did calibration - but it starts not often