FNIRSI-1013D "100MHz" tablet oscilloscope

[Atlan]

This is the output of this function uint32 scope_do_baseline_calibration(void).  The subroutine tries to set the pwm output so that the value at the output of the converter corresponds to the middle of the ADC 127 range. Try to measure the reference voltage on the AD converter, what is its value.  And measure the voltages at the AD converter input. The operational amplifier on one of the channels may be damaged or the resistors on the BNC connector may be damaged.

[Atlan]

If I record like this, then after starting the picture freezes and does not change in any way.
(Attachment Link)

Why are you uploading the ddd configuration there?  Is this the configuration you got when backing up your oscilloscope?

[TA4DIL]

https://disk.yandex.com/d/KkDi8qfnYb_WbA
Hello friends, I am a retired Electronics Engineer and I also deal with RF Techniques and I am a Class A Licensed Amateur Radio Operator. My call sign is TA4DIL. After experiencing the problem of loading the latest Stock Firmware and modified Firmware onto the SD Card, I was unable to overcome this problem with the forms and what was explained here, and finally my Oscilloscope stopped seeing the SD card, I had backed up the original SD card and I had never damaged the original SD card, when I put the SD Card back in, I saw that it worked and I started to experiment on the damaged card again and finally succeeded, here I will try to explain in detail how to fix these problems.
 
First, remove your SD card that does not work or has failed to load from the Oscilloscope and insert it into a card reader and insert it into your computer. Open the Disk Management shown in the picture and first delete all the volumes if there are additional partitions, do not give a name as a volume label, also delete the naming that says New Volume there, you should leave it blank and delete it, the result will be the only unit Raw, only the drive letter (F) will remain visible. Then format it again by selecting Fat32 with the format option, if there is no Fat32 option, download the HP_USB_Disc_Format program and format your SD Card that is Raw as Fat32 with it, again in the Computer Disk Management, delete the Volume of your SD card that is Fat 32 in the File Section and then create a Partition, select the entire disk as a new volume without creating any partitions, select Fat32 and click OK, we save our card. If this is not done, continuous loading errors occur, we remain on an oscilloscope opening screen that does not open and never starts with the screenshot of the old firmware files we have tried, or the loading button is not active at all. As a result of this process, many firmware uploads are successful within seconds.
     
Copy the files in the Original SD Card that we backed up as a result of the above process, except for the (System Volume Information) files, and drop them into the SD Card from which we performed the Recovery process.Download the file with the extension (fnirsi_1013d.bin v0.025x.txt) and shorten its extension like this (fnirsi_1013d.bin) and drop it into the SD Card
Copy the (fnirsi_1013d_scope) folder that you extracted from (v0.025x update code for maxlight settings & change roll mode & fix oveload red line.zip) to the SD Card with its contents, then in the computer view settings, in the options, show hidden files, uncheck the hide protected operating system folders option and make the hidden protected files visible.
   
Plug the Memory Card into the Oscillator and run it, wait a bit for it to load our new files, connect it to the computer via USB, switch to the Connect to Computer mode from the menu and extract and run the FNIRSI_Firmware_Loader.exe v1.1.3 Firmware Loading tool from the Zip file. Change the number values in the marked area seen in the picture. (My backup SD Card is 1GB). We select our SD Card in FNIRSI_Firmware_Loader.exe, we show our new (fnirsi_1013d.bin) firmware file, which we shortened the (fnirsi_1013d.bin v0.025x.txt) extension, in the loader, we finish the flashing process with the numerical order.
   
And this is the result, it came with extra features, I didn't have the opportunity to test and try it, only the Calendar clock display works incorrectly, it gives an error when the time change is reflected on the screen and I put it in passive mode because I saw the wrong time stamp, it has a slightly slower Auto set response than the original, the graphic curve is not as sharp and clear as the original, I get an error in calibration
       
And this is the result, it came with extra features, I didn't have the opportunity to test and try it, only the Calendar clock display works incorrectly, it gives an error when the time change is reflected on the screen and I put it in passive mode because I saw the wrong time stamp, it has a slightly slower Auto set response than the original, the graphic curve does not look as sharp and sad as the original, I don't know how to fix the calibration error, I want to try it like this, when the original SD Card is inserted, everything works with the original software with factory settings as before, I patiently wait for advice, suggestions and updates and for it to be developed with a more stable firmware, I would be very happy if you notify me if I made a mistake. Because I may have definitely made a small installation error somewhere, but I didn't want to pass without saying that I recovered my FINIRSI 1013D Oscilloscope device that I ruined in this way, I wanted to be useful by sharing my experience so that this could be a recovery suggestion for friends whose devices became inoperable.
  I tried to give notification with pictures but I could not add pictures. I made a statement as a World Document and added pictures. I stored everything I used and everything I needed on my Yandex disk. There are upload instructions with pictures in the link I gave.
https://disk.yandex.com/d/KkDi8qfnYb_WbA

[bffargo]

As discussed previously in this thread:
* The original display "curve" is faked / overly smoothed data. The alternate firmware gives a better representation of the actual values sampled to the limit of quality of the ADC's
* The date/time display only works if you solder in a 3rd party real time DS3231 clock chip with backup battery for it to work.
* As to the calibration problems, you need a stable discretely settable power supply capable of producing 0V to 15V without more than a few mv of noise, otherwise your calibration will not be successful and error out. Consider powering a from a bank of LiIon cells to remove external noise sources. Use some good BNC adapters/T-connectors to share the voltage across both inputs when prompted.

[Destroyer93]

Hello everyone, excellent work you have done with the new firmware , here are some photos of the ADC of my oscilloscope and the FPGA (Purchased a few days ago), I think they forgot to scratch the reference , although ¨2515¨ doesn't sound familiar to me known from nowhere . Just a small doubt that I see that the original firmware does not do, in the absence of signal it is normal for a slight noise to appear of about 20 to 30 mv Rms? (I ask the question because it was horrible for me to be able to calibrate the Shift DC, because that slight noise did not disappear )
PS: Excuse the translation

[Atlan]

Please provide a photo of the noise and a photo of the diagnostic screen.  The battery was charged to the maximum.?

[Atlan]

Catalog of changes in released firmware

[Destroyer93]

Nope...it was at 40% or 35% when I noticed that detail of the noise, I'm loading it now. When finished I will do the test again and send you photos

[cte]

2415 looks more like a date code.

[Atlan]

Showing wrong frequency in an 500hz square wave after using auto set in dc coupling. Switching to ac returns to normal.

https://youtu.be/fQD3lfvMDII

I forgot about it. Can you check it on this firmware to see if it works properly, thanks

[SergeAv]

Hello friends. I have recently byed 1013D oscilloscope.
Please help me to understand why my scope slows down on that alternative firmware. As if ADC does not have enough sampling rate and the scope freezes at all. At the same time the device interface responds normally to touch.
When I switch the scope to the original firmware no similar problems are observed.
Video (a few second of normal behavior on original firmware first): https://youtu.be/lHXMj--6qGE
Picture of the diagnostic screen in attachment.
The current version of the alternative firmware is 0.025y, on versions 0.025u, 0.025x the scope behaves the same way.

[Atlan]

Upload firmaware page 101
"supergun777 upload this firmware, only for you. Take picture or upload video again, with oscillogram freezes. See rightup corner."

make video.
P.S. long memory is OFF ? 

[SergeAv]

P.S. long memory is OFF ? 

Bingo! It was a problem. It looks like I hit that button when I was familiarizing myself with the new firmware.
Thank you so much for your work...

[engineer.r152]

Hi, Atlan! And why is this mode needed, why is there an active button that confuses everyone? This is not the first time this has happened.

[Atlan]

Because I started working on it, then someone reported a bug, it was removed.  A long memory remained unfinished.   To be fair, it failed to work around the FPGA limitation.  I will release a new version where long memory will be banned.  I just have a usb-virtual com port programmed.  (I'm not doing very well yet)

[email hidden]

Hi. So I gave up playing with HEX TP. (unfortunately I'm not retired yet) Tried a simpler option and bought a new TP with GT911. It seems 1mm bigger, but it fits perfectly. https://www.aliexpress.com/item/1005007053823391.html?spm=a2g0o.order_list.order_list_main.5.3a6918022Bk3US
You could count the lines in the picture. The old one was 18x12, this one is 18x13. Delivery time six days. After connecting, I first loaded the flash of the new TP to be sure. The TP panel was flashing red, non-standard. I'll attach the contents if it's useful to anyone. Then I inserted the original card and found that the panel works perfectly. I didn't have to do anything at all and I have a working device again. I want to thank you very much for your help. The only problem I have is that I lost the screws. I had it disassembled for a long time. Thank you, thank you.

[pcprogrammer]

Hi. So I gave up playing with HEX TP. (unfortunately I'm not retired yet) Tried a simpler option and bought a new TP with GT911. It seems 1mm bigger, but it fits perfectly. https://www.aliexpress.com/item/1005007053823391.html?spm=a2g0o.order_list.order_list_main.5.3a6918022Bk3US
You could count the lines in the picture. The old one was 18x12, this one is 18x13. Delivery time six days. After connecting, I first loaded the flash of the new TP to be sure. The TP panel was flashing red, non-standard. I'll attach the contents if it's useful to anyone. Then I inserted the original card and found that the panel works perfectly. I didn't have to do anything at all and I have a working device again. I want to thank you very much for your help. The only problem I have is that I lost the screws. I had it disassembled for a long time. Thank you, thank you.

Good to hear that it is working again. Indeed a simpler solution then tinkering with the configuration of the other one.