Author Topic: FNIRSI-1013D "100MHz" tablet oscilloscope (Read 1472876 times)

Atlan · « **Reply #1925 on:** February 09, 2024, 10:00:36 am »

fixed errors, and added some new errors

v0.023m
Long time base 100ms/div to 50s/div. In the waveform view mode, the range is from 20ms to 50s/div (multiple zoom options)
Long time base uses a memory of 3000 samples per channel.
Trigger options: Normal and single with the option of setting the trigger level and type of edge. Auto free run mode, no triggered.
In the long mode, the menu of measured values is not displayed.

write notes on errors.

Atlan · « **Reply #1926 on:** February 09, 2024, 05:34:20 pm »

ok fix it 3 error. erasing the display when turning on or off the time or voltage cursor. Correction of the cursor scale time-wrong value in short base, it no longer shows GHz, Bad sampling value for 500ms 5s and 50s
v0.023n

Atlan · « **Reply #1927 on:** February 10, 2024, 05:51:41 pm »

Yesterday when I decided to use an oscilloscope to measure the switched power and I discovered the 3 errors that are removed in the 0.023n version.

Today I wanted to check the multiplexing speed of the display, and I found out that it is in the red range when set to 1V.
It will be necessary to solve the problem with the shift of the signal in DC mode.
Nothing can replace real tests

Atlan · « **Reply #1928 on:** February 15, 2024, 07:14:41 pm »

Quote from: cool2000 on February 14, 2023, 11:34:56 am

It seems that RMS measurement implemented in the version v0.006 requires some changes for the saved WAVE files. Currently it doesn't show correct value.
Possible solutions could be: save calculated RMS value with the other WAVE file settings or recalculate RMS value from the file samples after loading.

only 1 year and 1 day

fix in v0.023o

The value was not saved in the wav file, added. (rms value)
Fixed screen clearing after exiting waveview mode.
FIxed wrong frequency in autoset mode

engineer.r152 · « **Reply #1929 on:** February 16, 2024, 09:02:25 am »

Good afternoon! Atlan, thank you for your hard work. A bug has been found in version v0.023o. When the stopped pulse is stretched or compressed, it is reset to 0 value.

Atlan · « **Reply #1930 on:** February 16, 2024, 12:11:02 pm »

Fixed. V0.023p
The correct switching of the sampling frequency when switching from stop to run also works.

If you reduce or expand the signal in the stop, the run will be displayed in the current setting during the transition.

engineer.r152 · « **Reply #1931 on:** February 16, 2024, 08:39:54 pm »

Another problem has been discovered, the displacement of the zero level of the beam during the transition to the ACQ long period.

Atlan · « **Reply #1932 on:** February 17, 2024, 07:54:06 am »

Make video.

Now I am modifying the program so that it does not wait for the end of the transfer. Quite a lot of interventions in the program.

PC:
I would say that a field[730] was created for the displayed data on the display. But is it not used anywhere? Channel1pointsbuffer and 2

engineer.r152 · « **Reply #1933 on:** February 17, 2024, 04:42:17 pm »

https://youtu.be/J_cZJTdngeQ?feature=shared

pcprogrammer · « **Reply #1934 on:** February 17, 2024, 07:05:52 pm »

Quote from: Atlan on February 17, 2024, 07:54:06 am

PC:
I would say that a field[730] was created for the displayed data on the display. But is it not used anywhere? Channel1pointsbuffer and 2

I think it was intended to be used for the wave file storage. The buffer is being filled when a channel trace is displayed on the screen. See "void scope_display_channel_trace(PCHANNELSETTINGS settings)" function in scope_functions.c, but by the looks of it that is it.

Atlan · « **Reply #1935 on:** February 17, 2024, 08:18:40 pm »

In next version firmware will is bug fixed.

arne2501 · « **Reply #1936 on:** February 18, 2024, 10:52:41 am »

hi, when i try to change the time and date, it shows ? you can't change it.

Atlan · « **Reply #1937 on:** February 18, 2024, 02:38:18 pm »

Quote from: arne2501 on February 18, 2024, 10:52:41 am

hi, when i try to change the time and date, it shows ? you can't change it.

Touch the buttons to set the time and date

The work has progressed, so hopefully there will be a new firmware release soon.

arne2501 · « **Reply #1938 on:** February 18, 2024, 02:47:26 pm »

it's not working for me, when i change it, it sets hours 45 minutes 85 day 45 month 25 year 20165
when i change it, it shows 3?:7?:7?

arne2501 · « **Reply #1939 on:** February 18, 2024, 02:58:55 pm »

see pictures it doesn't work.

arne2501 · « **Reply #1940 on:** February 18, 2024, 03:19:35 pm »

i try with version 0.023p and its the same problem, even with version 0.019 it's not working. it keeps showing the 3?:7?:7?

Atlan · « **Reply #1941 on:** February 18, 2024, 03:38:18 pm »

Broken or wrongly connected RTC module
https://www.eevblog.com/forum/testgear/fnirsi-1013d-100mhz-tablet-oscilloscope/1600/

arne2501 · « **Reply #1942 on:** February 18, 2024, 05:03:37 pm »

the unit is new, i bought it, 3 days ago?

bffargo · « **Reply #1943 on:** February 18, 2024, 05:15:19 pm »

Quote from: arne2501 on February 18, 2024, 05:03:37 pm

the unit is new, i bought it, 3 days ago?

Read the post linked above. It doesn't come with real time clock. It's a mod you have to do if you want it by adding an extra circuit and soldering it in. It doesn't work on base hardware without the mod.

arne2501 · « **Reply #1944 on:** February 18, 2024, 05:18:39 pm »

okey thanks, now i understand. i will install it. thanks for the response.

Atlan · « **Reply #1945 on:** February 19, 2024, 02:14:43 pm »

It is interesting that no one complained that it still deletes the calibration data, even when it is announced that only the default data will be uploaded. FIXED
It should already work, that is, unless there are changes regarding the calibration or the location of the values on the SD card. It will not be necessary to recalibrate the input divider. You can perform the baseline calibration whenever you need.

v0.023s allows the code to run without waiting for the conversion to finish in the FPGA. This means that the time on the display is not frozen, and the T cursor and V cursor buttons work as they should.

Again, the bigger the changes in the code, the more likely it is that there will be more errors. So test it.

P.S. I did not notice a signal shift when switching from short to long mode.
I have a working manual for the firmware, but it is not finished or translated, and I don't even want to deal with it. Maybe when there is free time for that.

Atlan · « **Reply #1946 on:** February 19, 2024, 02:28:22 pm »

Quote from: engineer.r152 on February 16, 2024, 08:39:54 pm

Another problem has been discovered, the displacement of the zero level of the beam during the transition to the ACQ long period.

Take a photo of the calibration data

engineer.r152 · « **Reply #1947 on:** February 19, 2024, 07:07:17 pm »

Strangely, two oscilloscopes have the same level problem.

Atlan · « **Reply #1948 on:** February 19, 2024, 10:36:17 pm »

It's interesting that it doesn't make me 2 pieces. We'll see if anyone else can be found

v0.023t

dfw_ee · « **Reply #1949 on:** February 20, 2024, 04:11:15 am »

Is there a utility to restore the tp configuation after it is saved with this tool? Somehow one of my units now has the touch screen coordinates backwards. I was able to fix this running your code with the config file but this doesn't help with the original firmware of course. I didn't have to use your config file previously either before this issue cropped up. I don't know how this came about but I compared my original FNIRSI_1013D_tp_config.bin to one that I got from the fwb tool after this issue cropped up and there are a few bytes different between the files. I would really like to get this back working with the original firmware as well.

Thanks

Quote from: pcprogrammer on November 12, 2021, 11:58:00 am

Here is the tool plus the steps to make it work.

!! I take no responsibility if anything goes wrong !!

Steps for making the FNIRSI-1013D firmware backup on a Linux machine:
Connect the scope to the computer via USB.
Turn on the scope and start the USB connection via the main menu option.
Wait until the file manager window opens. (Only if auto mount is working properly)
Close the file manager window.
Open a terminal window (ctrl + alt + t) and type the "lsblk" command (!do not use the quotes!) and check which device the scope is on. (~8GB disk)
Copy the files from the card to have a backup on your computer.
Un-mount the partition. ("sudo umount /dev/sdc1" in my case)
Just to be more safe make a backup with dd. ("sudo dd bs=4M if=/dev/sdc of=sd_card_backup.bin" again in my case)
Open gparted and check if the device is properly formated. (Use right mouse and information to see the sector info)
If not delete the partition and make a new one leaving 1M free at the start. Format is fat32.
When the partition remounts after the previous step un-mount it again.
Use dd to place the backup package on the SD card. ("sudo dd if=fnirsi_1013d_fwb.bin of=/dev/sdc bs=1024 seek=8")
This will re-mount the partition. Un-mount the partition again. ("sudo umount /dev/sdc1" in my case)
Turn of the scope and turn it back on. This will start the backup process.
Wait until it is done and the scope is mounted again. File manager window should open after a while.
Copy the three files to the computer. (FNIRSI_1013D_full_flash_backup.bin, FNIRSI_1013D_tp_config.bin, FWB_FSI_1013.bin)
Turn off the scope and turn it back on. It should start normally.

When the scope showed the "!! special touch panel detected !!" message please upload the "FNIRSI_1013D_tp_config.bin" file in this thread.

If your scope uses a smaller or bigger SD card be warned that this is not tested yet. Only 8GB cards have been tested.

See the attached image for info on the sd card sectors. Screen cap from gparted.

Remove the .txt extension from the firmware backup package file.


EEVblog® Main Site	EEVblog® on Youtube	EEVblog® on Twitter	EEVblog® on Facebook	EEVblog® on Odysee

Author Topic: FNIRSI-1013D "100MHz" tablet oscilloscope (Read 1472876 times)

Share me