FNIRSI-1013D "100MHz" tablet oscilloscope

[coppercone2]

that sounds like it might be a bad socket

[Atlan]

I bought a film and stuck it on the display. 20x100cm https://www.aliexpress.com/item/1005005179170765.html?spm=a2g0o.order_list.order_list_main.234.96651802iflMid

[boojum]

I bought a film and stuck it on the display. 20x100cm https://www.aliexpress.com/item/1005005179170765.html?spm=a2g0o.order_list.order_list_main.234.96651802iflMid

I'm waiting for this one to be delivered https://aliexpress.ru/item/1005005978848349.html?sku_id=12000035147348074

[_AVP_]

No, when I write orig FW (through USB) - it starts every time, even if I don't touch SDcard. Maybe need to add some delays in FW to access SD?

[pcprogrammer]

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

No, when I write orig FW (through USB) - it starts every time, even if I don't touch SDcard. Maybe need to add some delays in FW to access SD?

Original firmware loads from FLASH using the SPI interface, but does check the SD card on being there and having a valid partition based on a FAT format. This is only a short interaction with the SD card.

To see if there is a problem you can try reading and writing images or waveforms when running the original firmware to see if this works as intended.

The SD card works with a dedicated interface and sets its speed based on the type of card in the socket. The new firmware uses the build in F1C100s boot loader to load the first bit of code, and then this code takes over to load the splash screen, and then the actual firmware is loaded.

A video of what your system does when starting the new firmware could help in determining the problem.

It might well be that the F1C100s has problems, or maybe bad connections.

[Atlan]

Try the firmware version 0.006, in the new versions I also modified the code for the startartup screeen, so I made a mistake somewhere.

If someone has time.  It can measure the deviation of the measured voltage with a 10x probe.  If I have calibrated to 1x

[tokar]

v0021g.
I did not switch the probe input to 10x. I switched
only in the oscilloscope menu.
_______________________________________
Range    |   Uin     |      1x     |     10x    |     100x   |
---------------------------------------------------------------
5v/div    |     10v   |      10v   |    100v   |   1,00kv  |
---------------------------------------------------------------
2,5v/div |      5v    |      5v     |     50v    |    500v    |
---------------------------------------------------------------
 1v/div   |      1v    |       1v    |     10v    |    100v    |
---------------------------------------------------------------
0,5v/div |      1v    |       1v    |     10v    |    100v    |
---------------------------------------------------------------
0,2v/div |     0,4v  |      0,4v  |       4v    |      40v    |
---------------------------------------------------------------
0,1v/div |    0,25v |     0,25v |      2,5v   |     25v    |
---------------------------------------------------------------

[Atlan]

That's what switching the probe was all about.  Because I don't think there will be 1:10

[tokar]

With the probe at the 1:10 position, I also tried it at a sensitivity of 5V/div.  The readings agree, only the values ​​are 10 times smaller. 
And please make the problem statement more detailed.  Otherwise, the problem of triple translation and double perception arises.

[Atlan]

Probe 10x, oscilloscope 10x, and bring the voltage to the probe and compare with what the oscilloscope shows.

[tokar]

I'm sorry, but only tomorrow.  There is currently no access to the device.  Can someone make a table so as not to keep Atlan waiting?

[Atlan]

It's not urgent.  Now I'm working on autosetup.

[tokar]

Source Uin, U_calibr - battery.  P6100 probes, included at 10x.  Channel menus are included at 10x. Manual mode selection.

[_AVP_]

I tried to save/view pictures/waveforms - all works. On orig FW and custom all is OK. Problem only when it starts. I see splashscreen and 70/30% normal start or "SD error". On orig FW it never give an error.  It works same on any SD card.
Video of start in zip.

[pcprogrammer]

I tried to save/view pictures/waveforms - all works. On orig FW and custom all is OK. Problem only when it starts. I see splashscreen and 70/30% normal start or "SD error". On orig FW it never give an error.  It works same on any SD card.

I don't know what can be wrong here. The fact that it shows SD error tells me that it fails in the actual scope firmware part after already loading lots of data from the SD card, only to fail when mounting the file system.

I wonder what happens if you erase the new scope software by clearing sector 8 on the SD card, but leave the rest of the card untouched and then use it with the original firmware, if it still works normally or also fails once in a while with the SD error.

[Atlan]

Why is the calibration constant chosen, which results in a value of 235 units?(for AD 128 value) (it reduces the range of the AD converter to 220bit) At the same time, the area for displaying the signal is 0-402 units.  Why was such a calibration value not chosen that would give a result of 201, ie the center of the display.

[pcprogrammer]

Ask FNIRSI.

I just copied it from the original source and paid no further attention to it. My goal was to get something operational that was close to the original. Started with improvements on the sampling part of the code, but lost interest due to the total crappiness of the hardware.

[Atlan]

Beta v0.022d Version for testing, adjusted 50% trigger setting.
Auto setup used from flood code (with all the errors it has )
It does not contain hardware signal shift. (I don't know if it is necessary)
Automatic setting of the time base is not implemented.

Try it if it works.

[gadak]

Hello, please advise, after calibration according to the instructions above, when connecting the dura ch1 marker 1 is lower and the difference in readings of 0.3 volts (actual value is 15.06 volts on the lab power supply), is this how it should be? What is the problem?

[gadak]

Two screen

[gadak]

Also when I pressed autoset this is what happened, Vrms shows 15 volts correctly. I tried to go to the calibration menu when the probes are pulled out and calibrate, the channel indicators ch1,ch2 are aligned, but when reconnecting the probes to measure the voltage, everything goes astray on the photo you can see.

[Atlan]

 Make a video.  I don't see a problem in the photo.  Without the voltage connected, the yellow line should point to the yellow cursor (blue to blue), by connecting the voltage the line will show the voltage (moved away from the yellow cursor) (blue)

[gadak]

Uh, thank you. Got it. That's right. And 0.2 V difference between ch1 and ch2 is normal.

[Atlan]

V0.022f Autosetup with DC and AC mode support. Automatic detection of sampling frequency. Changing the colors of V-cursor data and position dY.

I started working on the option: Long time base
It will take some time because you have to create a menu and arrange for switching between Short time base and Long time base.
But first I have to try it.

P. S. Does anyone use current probes?  Is it necessary to add the possibility of displaying A instead of V somewhere?

[Atlan]

The RTC module is not required for the function of the alternative software.  And it is disabled by default.
Even if you turn it on by mistake, nothing happens except for incorrect time data.  So if you don't save something with such a wrong time.  (I didn't try)

Trying the firmware takes some time, which I don't have.  So that's why versions come out more often so that someone can try it out, even if it's not fully functional.

V0.  022f should actually be a usable version, suitable for work.

How do it:
https://youtu.be/LVI45oJHTK8?si=DPj073HgD5Jeuydx

Loader.zip
https://github.com/Atlan4/Fnirsi1013D