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

Atlan · « **Reply #1925 on:** February 08, 2024, 05:34:26 pm »

The saved format of waw files does not have the correct display scale. Moreover, it does not fit with time per div with short time base. I will fix it. It will take a while. Still removing some bugs found.

Atlan · « **Reply #1926 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 #1927 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 #1928 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 #1929 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 #1930 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 #1931 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 #1932 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 #1933 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 #1934 on:** February 17, 2024, 04:42:17 pm »

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

pcprogrammer · « **Reply #1935 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 #1936 on:** February 17, 2024, 08:18:40 pm »

In next version firmware will is bug fixed.

arne2501 · « **Reply #1937 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 #1938 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 #1939 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 #1940 on:** February 18, 2024, 02:58:55 pm »

see pictures it doesn't work.

arne2501 · « **Reply #1941 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 #1942 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 #1943 on:** February 18, 2024, 05:03:37 pm »

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

bffargo · « **Reply #1944 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 #1945 on:** February 18, 2024, 05:18:39 pm »

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

Atlan · « **Reply #1946 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 #1947 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 #1948 on:** February 19, 2024, 07:07:17 pm »

Strangely, two oscilloscopes have the same level problem.

Atlan · « **Reply #1949 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


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

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

Share me