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

dfw_ee · « **Reply #1975 on:** February 21, 2024, 03:28:52 pm »

Quote from: pcprogrammer on February 21, 2024, 07:36:28 am

Quote from: dfw_ee on February 20, 2024, 07:53:59 pm
Thanks for the info. Isn't it possible to use your bit banged I2C code on github to reprogam the touch panel configuration instead of connecting other hardware? It seems that is what happened in the first place. Once again thanks for the help!

Sure it is, but you have to write it yourself. The code can be small enough to do it in the bootloader. Just take that project and remove the loading of the next code and stick in the I2C bit with the needed touch panel configuration. All the needed bits and pieces can be found in what I wrote. It might even still be in the new firmware disabled with a define.

Yes, I knew it was on me to write it. I thought I saw a pretty clear path to modifying fnirsi_1013d_fwb.bin to write the configuration file instead of reading it and not copying the firmware to a file. I just wanted to make sure there wasn't some bug that you had found previously that would prevent this path. Thanks!

Atlan · « **Reply #1976 on:** February 21, 2024, 03:38:05 pm »

Download zip. https://github.com/Atlan4/Fnirsi1013D/tree/main
Ideally, the one that contains all 3 folders for the oscilloscope. It contains parts of the code that you should be able to touch, just try to remove them or call them correctly. IF you have a backup, maybe the PC would be able to tell which part of the code needs to be loaded. Purely theoretically, I can generate a bin here, but without a guarantee. Which you write in the IO for touch panel.

fnirsi_1013d_scope/touchpanel.c
https://github.com/pecostm32/FNIRSI_1013D_Firmware/blob/main/fnirsi_1013d_scope/touchpanel.c

dfw_ee · « **Reply #1977 on:** February 21, 2024, 03:43:13 pm »

Quote from: Atlan on February 21, 2024, 09:19:33 am

Quote from: pcprogrammer on February 21, 2024, 07:36:28 am
Quote from: dfw_ee on February 20, 2024, 07:53:59 pm
Thanks for the info. Isn't it possible to use your bit banged I2C code on github to reprogam the touch panel configuration instead of connecting other hardware? It seems that is what happened in the first place. Once again thanks for the help!

Sure it is, but you have to write it yourself. The code can be small enough to do it in the bootloader. Just take that project and remove the loading of the next code and stick in the I2C bit with the needed touch panel configuration. All the needed bits and pieces can be found in what I wrote. It might even still be in the new firmware disabled with a define.

#ifndef USE_TP_CONFIG
#ifdef SAVE_TP_CONFIG
void save_tp_config(void)
{
//Create a file for the touch panel configuration. Fails if it already exists
if(f_open(&viewfp, "FNIRSI_1013D_tp_config.bin", FA_CREATE_NEW | FA_WRITE | FA_READ) == FR_OK)
{
//Write the touch panel configuration to the sd card
f_write(&viewfp, tp_config_data, sizeof(tp_config_data), 0);

//Close the file to finish the write
f_close(&viewfp);
}
}
#endif
#endif
...

Thanks!

dfw_ee · « **Reply #1978 on:** February 21, 2024, 03:50:17 pm »

Quote from: Atlan on February 21, 2024, 03:38:05 pm

Download zip. https://github.com/Atlan4/Fnirsi1013D/tree/main
Ideally, the one that contains all 3 folders for the oscilloscope. It contains parts of the code that you should be able to touch, just try to remove them or call them correctly. IF you have a backup, maybe the PC would be able to tell which part of the code needs to be loaded. Purely theoretically, I can generate a bin here, but without a guarantee. Which you write in the IO for touch panel.

fnirsi_1013d_scope/touchpanel.c
https://github.com/pecostm32/FNIRSI_1013D_Firmware/blob/main/fnirsi_1013d_scope/touchpanel.c

Hi Atlan, it would be fantastic if you could generate a bin saving me having to get the build set up

Can you set it up to read in a fixed filename that has the touch screen config? If the filename could be FNIRSI_1013D_tp_config.bin as it is saved from the backup tool and using that format would be useful to a lot of people that wind up in my predicament.

Thanks!

pcprogrammer · « **Reply #1979 on:** February 21, 2024, 04:04:34 pm »

Quote from: Atlan on February 21, 2024, 02:35:32 pm

I'm thinking about what it's good for... Or what it could be used for. If the trigger was turned off, it would be possible to collect the set number of samples with this system. The question is what time_base_cnt the clock - does it depend on the sampling frequency?

About 0.023x works, so far no one has reported a problem. We'll see what the user does with the touchscreen, because the oscilloscope code contains things to write to the touchscreen.

The time_base_cnt depends on the sample clock. Every sample written increases this counter. So on a low sample rate it takes its time to collect the samples. It is possible to disable the trigger and have the system just take in a bunch of samples. Does not work on normal trigger mode. Has to be auto.

engineer.r152 · « **Reply #1980 on:** February 21, 2024, 04:19:45 pm »

Version 0.23x has indeed been fixed, but at a frequency of 50KSa/2 ms and below, a zero-level ripple has appeared
https://youtu.be/YTPkPzBNzJI?feature=shared

Atlan · « **Reply #1981 on:** February 21, 2024, 04:56:19 pm »

That's a feature

I see that it moves nicely even with 2 channels. Have you modified the power supply, i.e. cut the 4.2V to the 3V stabilizer and installed a 5V step up to power the 3V stabilizer? Attention 5V must not reach the inverters for the display. I see that there is quite a lot of interference on 2 channels.

engineer.r152 · « **Reply #1982 on:** February 21, 2024, 05:48:18 pm »

No, I haven't installed it, I'm waiting for it to arrive from China. Have you done anything else about nutrition?

Atlan · « **Reply #1983 on:** February 21, 2024, 05:57:48 pm »

I added some capacitors, but it seems to me that the situation has worsened

Quote from: dfw_ee on February 21, 2024, 03:50:17 pm

Quote from: Atlan on February 21, 2024, 03:38:05 pm
Download zip. https://github.com/Atlan4/Fnirsi1013D/tree/main
Ideally, the one that contains all 3 folders for the oscilloscope. It contains parts of the code that you should be able to touch, just try to remove them or call them correctly. IF you have a backup, maybe the PC would be able to tell which part of the code needs to be loaded. Purely theoretically, I can generate a bin here, but without a guarantee. Which you write in the IO for touch panel.

fnirsi_1013d_scope/touchpanel.c
https://github.com/pecostm32/FNIRSI_1013D_Firmware/blob/main/fnirsi_1013d_scope/touchpanel.c

Hi Atlan, it would be fantastic if you could generate a bin saving me having to get the build set up Can you set it up to read in a fixed filename that has the touch screen config? If the filename could be FNIRSI_1013D_tp_config.bin as it is saved from the backup tool and using that format would be useful to a lot of people that wind up in my predicament.

Thanks!

dfw_ee Upload your backup file here to the forum
FNIRSI_1013D_tp_config.bin

Atlan · « **Reply #1984 on:** February 21, 2024, 06:41:29 pm »

Instructions and description

FNIRSI 1013D alternative firmware v0.023x ANG.doc (299.5 kB - downloaded 77 times.)

BreakingOhmsLaw · « **Reply #1985 on:** February 21, 2024, 08:49:38 pm »

I feel that the real question here is: how the hell did they come up with that brand name?
Was there a committee that sat down together in a room and said "Yeah, FNIRSI! That's the one, we'll roll with that. FNIRSI!"

It sounds like something you catch on a vacation in a jungle, or like an off brand hemroid cream.

bffargo · « **Reply #1986 on:** February 21, 2024, 09:15:05 pm »

Quote from: BreakingOhmsLaw on February 21, 2024, 08:49:38 pm

I feel that the real question here is: how the hell did they come up with that brand name?
Was there a committee that sat down together in a room and said "Yeah, FNIRSI! That's the one, we'll roll with that. FNIRSI!"

It sounds like something you catch on a vacation in a jungle, or like an off brand hemroid cream.

There actually is a meaning behind it. Dave or someone reviewing a recent product explained it. I wish I could remember the details, but it was letters from their full company name or something like that. If I find the video I'll post the link.

Edit: They removed the EI and UI from the longer name from the company to come up with it. Here is some random context found so far showing it's a bit longer word in their company name. Perhaps a native speaker or one that can read the written glyphs can provide more info.
https://www.youtube.com/channel/UCONj2ghlwwgYnc_WJq29XYg

https://trademarks.justia.com/877/85/fnirsi-87785437.html
Shenzhen Feiniruisi Technology Co., Ltd.

dfw_ee · « **Reply #1987 on:** February 21, 2024, 10:37:05 pm »

Quote from: Atlan on February 21, 2024, 05:57:48 pm

I added some capacitors, but it seems to me that the situation has worsened

Quote from: dfw_ee on February 21, 2024, 03:50:17 pm
Quote from: Atlan on February 21, 2024, 03:38:05 pm
Download zip. https://github.com/Atlan4/Fnirsi1013D/tree/main
Ideally, the one that contains all 3 folders for the oscilloscope. It contains parts of the code that you should be able to touch, just try to remove them or call them correctly. IF you have a backup, maybe the PC would be able to tell which part of the code needs to be loaded. Purely theoretically, I can generate a bin here, but without a guarantee. Which you write in the IO for touch panel.

fnirsi_1013d_scope/touchpanel.c
https://github.com/pecostm32/FNIRSI_1013D_Firmware/blob/main/fnirsi_1013d_scope/touchpanel.c

Hi Atlan, it would be fantastic if you could generate a bin saving me having to get the build set up Can you set it up to read in a fixed filename that has the touch screen config? If the filename could be FNIRSI_1013D_tp_config.bin as it is saved from the backup tool and using that format would be useful to a lot of people that wind up in my predicament.

Thanks!

dfw_ee Upload your backup file here to the forum
FNIRSI_1013D_tp_config.bin

It is attached. Thanks!

engineer.r152 · « **Reply #1988 on:** February 22, 2024, 10:18:31 am »

https://youtu.be/glwu0KrXKts?feature=shared
A new bug on ACC LONG resets the waveform when trying to change the cursors

naiclub · « **Reply #1989 on:** February 22, 2024, 11:08:42 am »

Why don't you do FNIRSI_1014D? For example, adjust the scope measurement to 230V. Using a measuring tape X10 is enough. without needing to use the X100 cable

Atlan · « **Reply #1990 on:** February 22, 2024, 11:41:45 am »

Quote from: engineer.r152 on February 22, 2024, 10:18:31 am

https://youtu.be/glwu0KrXKts?feature=shared
A new bug on ACC LONG resets the waveform when trying to change the cursors

This is a feature, the second option is to turn it off. (I decided to let the user set the limits and then turn on the sampling. (there is not enough time to sample and render the entire display) Take a WAVe snapshot and you can measure there.

LunaC · « **Reply #1991 on:** February 22, 2024, 05:16:31 pm »

Actually I like that idea now that I try it but if in stop mode could it act differently( or do we need to just use the waveform)?

uncle_sem · « **Reply #1992 on:** February 22, 2024, 05:22:25 pm »

Today I tried to upgrade firmware 0.019d to version 0.023t and the oscilloscope stopped responding to the input signal, always showing a flat line on both channels. Calibration ended with an error. Firmware 0.023p worked fine, and when I installed 0.023t next, it also worked fine. Just for information for those who missed several intermediate versions of the firmware like me

Atlan · « **Reply #1993 on:** February 22, 2024, 07:17:09 pm »

ALWAYS provide legible photos of the working screen of the oscilloscope and the calibration menu with values. (or video) I don't have a crystal ball.

Because in a certain version, the data was moved to sector 709 (previously it was in 700). Data control has been added since a certain version and, if necessary, a prompt is displayed to 1. only upload default values or 2. default values and reset calibration data.
In each case, if a new firmware is installed, it is possible to call up the menu menu with calibration data via USB, and reset them.
I assume that there were 0 values, so that nothing was displayed.

The latest version is 0.023x

Quote from: LunaC on February 22, 2024, 05:16:31 pm

Actually I like that idea now that I try it but if in stop mode could it act differently( or do we need to just use the waveform)?

Long mode should only display the signal. That's what he was meant for. The original can't do anything. The possibility to save a wave and carry out the measurement in the browsing mode has been added here, as well as to move the signal from the memory to up to 3000 samples.

The signal is displayed and buffered, so it is possible to redraw the screen with the buffered signal when stopped and cursors will be available. We should think about whether it would be possible to do it this way. It would be a bit strange.

The priority is to finally solve the shift of the DC level, then I need a brain and a lot of time.

Atlan · « **Reply #1994 on:** February 22, 2024, 07:50:44 pm »

There are certainly differences. PC. what do you think, can I copy it directly there?

firmavare data:
uint8 tp_config_data[] =
{
0xFF, 0x20, 0x03, 0xE0, 0x01, 0x0A, 0xFD, 0x00, 0x01, 0x08, 0x28, 0x08, 0x5A, 0x3C, 0x03, 0x05,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x18, 0x1A, 0x1E, 0x14, 0x87, 0x29, 0x0A, 0x75, 0x77,
0xB2, 0x04, 0x00, 0x00, 0x00, 0x9A, 0x01, 0x11, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x50, 0xA0, 0x94, 0xD5, 0x02, 0x08, 0x00, 0x00, 0x04, 0xA1, 0x55, 0x00, 0x8F,
0x62, 0x00, 0x7F, 0x71, 0x00, 0x73, 0x82, 0x00, 0x69, 0x95, 0x00, 0x69, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x02, 0x04, 0x06, 0x08, 0x0A, 0x0C, 0x0E, 0x10, 0x12, 0x14, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02,
0x04, 0x06, 0x08, 0x0A, 0x0C, 0x1D, 0x1E, 0x1F, 0x20, 0x21, 0x22, 0x24, 0x26, 0x28, 0xFF, 0xFF,
0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x05, 0x01
};

backup data>
6D,20,03,E0,01,05,0D,00,01,0A,28,0F,50,32,03,05,00,00,00,00,00,00,08,17,19,1C,14,87,29,0A,66,
68,EB,04,00,00,02,00,02,11,00,01,00,00,00,00,00,00,00,00,00,5A,8C,94,C5,02,07,19,00,04,93,5E,
00,87,66,00,7C,70,00,72,7A,00,6B,86,00,6A,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,02,04,06,08,0A,0C,0E,10,12,14,FF,FF,
FF,FF,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,28,26,24,22,21,20,1F,1E,1D,0C,0A,08,06,
04,02,00,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,8D,00

polyman · « **Reply #1995 on:** February 23, 2024, 02:00:09 am »

Hello:

I would like to install the new firmware on my scope but I am having some issues and was wondering if some kind sould can help me climb out of it.
I am not messing around with the SD Card on the scope just yet. To validate my understanding of the process the setup is Linux, with a generic 4GB
SD card on /dev/sdb. I am following the instructions given in the README.md to write a firmware image (fnirsi_1013d.bin downloaded from the pecostm32
github repo) to the SD Card. The first problem I encounter is here:

> 10) If not delete the partition and make a new one leaving 1M free at the start. Format is fat32.

GParted does not allow me to leave 1MB free at the start even though the "Free space preceeding" field clearly says 1MiB. I can do 2MiB or more, but not 1.
I am not a fat32 expert but this seems to be related to the size of the card. GParted reports that the SD Card inside my oscilloscope is 8GB and has 4MB free
before the sdb1 partition. Question: Is the size of this free space a critical parameter?

After following the direction on how to prepare the SD card outlined in the YouTube video by Atlan titled "FNIRSI1013D fix sdcart problem with load firmware"
second problem is here:

> 12) Use dd to place the firmware package on the SD card. ("sudo dd if=fnirsi_1013d.bin of=/dev/sdc bs=1024 seek=8")

Once dd is done I can indeed mount the /dev/sdb1 partition but there is no content whatsoever in the partition and all the space in the card is reported
as available. If I understand the process correctly, I was supposed to find the files necessary to boot the scope, but alas there is nothing.

What am I missing?

Thanks
Polyman

Atlan · « **Reply #1996 on:** February 23, 2024, 06:10:56 am »

The minimum required space is 1MB, yes, 8GB is basically 4MB. Nothing else matters. You will not see the files, if you want to see the bytes, use the HxD program for Windows.

When the card is turned on, the program from the card is loaded into the oscilloscope. It is advisable to make a Flash backup beforehand

Atlan · « **Reply #1997 on:** February 23, 2024, 07:47:48 am »

dfw_ee Check if the picture fits the transcript. check byte by byte.

0x6D, 0x20, 0x03, 0xE0, 0x01, 0x05, 0x0D, 0x00, 0x01, 0x0A, 0x28, 0x0F, 0x50, 0x32, 0x03, 0x05,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x08, 0x17, 0x19, 0x1C, 0x14, 0x87, 0x29, 0x0A, 0x66, 0x68,
0xEB, 0x04, 0x00, 0x00, 0x02, 0x00, 0x02, 0x11, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x5A, 0x8C, 0x94, 0xC5, 0x02, 0x07, 0x19, 0x00, 0x04, 0x93, 0x5E, 0x00, 0x87,
0x66, 0x00, 0x7C, 0x70, 0x00, 0x72, 0x7A, 0x00, 0x6B, 0x86, 0x00, 0x6A, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x02, 0x04, 0x06, 0x08, 0x0A, 0x0C, 0x0E, 0x10, 0x12, 0x14, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x28, 0x26,
0x24, 0x22, 0x21, 0x20, 0x1F, 0x1E, 0x1D, 0x0C, 0x0A, 0x08, 0x06, 0x04, 0x02, 0x00, 0xFF, 0xFF,
0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x8D, 0x00

pcprogrammer · « **Reply #1998 on:** February 23, 2024, 08:00:59 am »

Quote from: Atlan on February 22, 2024, 07:50:44 pm

There are certainly differences. PC. what do you think, can I copy it directly there?

firmavare data:
uint8 tp_config_data[] =
{
0xFF, 0x20, 0x03, 0xE0, 0x01, 0x0A, 0xFD, 0x00, 0x01, 0x08, 0x28, 0x08, 0x5A, 0x3C, 0x03, 0x05,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x18, 0x1A, 0x1E, 0x14, 0x87, 0x29, 0x0A, 0x75, 0x77,
0xB2, 0x04, 0x00, 0x00, 0x00, 0x9A, 0x01, 0x11, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x50, 0xA0, 0x94, 0xD5, 0x02, 0x08, 0x00, 0x00, 0x04, 0xA1, 0x55, 0x00, 0x8F,
0x62, 0x00, 0x7F, 0x71, 0x00, 0x73, 0x82, 0x00, 0x69, 0x95, 0x00, 0x69, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x02, 0x04, 0x06, 0x08, 0x0A, 0x0C, 0x0E, 0x10, 0x12, 0x14, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02,
0x04, 0x06, 0x08, 0x0A, 0x0C, 0x1D, 0x1E, 0x1F, 0x20, 0x21, 0x22, 0x24, 0x26, 0x28, 0xFF, 0xFF,
0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x05, 0x01
};

backup data>
6D,20,03,E0,01,05,0D,00,01,0A,28,0F,50,32,03,05,00,00,00,00,00,00,08,17,19,1C,14,87,29,0A,66,
68,EB,04,00,00,02,00,02,11,00,01,00,00,00,00,00,00,00,00,00,5A,8C,94,C5,02,07,19,00,04,93,5E,
00,87,66,00,7C,70,00,72,7A,00,6B,86,00,6A,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,
00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,02,04,06,08,0A,0C,0E,10,12,14,FF,FF,
FF,FF,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,28,26,24,22,21,20,1F,1E,1D,0C,0A,08,06,
04,02,00,FF,FF,FF,FF,FF,FF,FF,FF,FF,FF,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,8D,00

If the second set of data is from the touch panel that has now reversed coordinates due to being written with possibly the first set of data then it is quite clear. The range of data with these numbers "28,26,24,22,21,20,1F,1E,1D,0C,0A,08,06,04,02,00" differs from "0x00, 0x02, 0x04, 0x06, 0x08, 0x0A, 0x0C, 0x1D, 0x1E, 0x1F, 0x20, 0x21, 0x22, 0x24, 0x26, 0x28" and explains the reversal of the X direction.

Just use the second set as the needed configuration, and don't test it on your own scope.

Atlan · « **Reply #1999 on:** February 23, 2024, 08:03:42 am »

3 different TP configurations.
The PC will tell you which one to upload.
Above all, don't try it just like that!!!! as always, no one guarantees anything, everything at your own risk.

uint8 tp_config_data1[] =
{
0xFF, 0x20, 0x03, 0xE0, 0x01, 0x0A, 0xFD, 0x00, 0x01, 0x08, 0x28, 0x08, 0x5A, 0x3C, 0x03, 0x05,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x18, 0x1A, 0x1E, 0x14, 0x87, 0x29, 0x0A, 0x75, 0x77,
0xB2, 0x04, 0x00, 0x00, 0x00, 0x9A, 0x01, 0x11, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x50, 0xA0, 0x94, 0xD5, 0x02, 0x08, 0x00, 0x00, 0x04, 0xA1, 0x55, 0x00, 0x8F,
0x62, 0x00, 0x7F, 0x71, 0x00, 0x73, 0x82, 0x00, 0x69, 0x95, 0x00, 0x69, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x02, 0x04, 0x06, 0x08, 0x0A, 0x0C, 0x0E, 0x10, 0x12, 0x14, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x02,
0x04, 0x06, 0x08, 0x0A, 0x0C, 0x1D, 0x1E, 0x1F, 0x20, 0x21, 0x22, 0x24, 0x26, 0x28, 0xFF, 0xFF,
0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x05, 0x01
};

uint8 tp_config_data2[] =
{
0xFF, 0x20, 0x03, 0xE0, 0x01, 0x0A, 0xFD, 0x00, 0x01, 0x08, 0x28, 0x08, 0x5A, 0x3C, 0x03, 0x05,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x18, 0x1A, 0x1E, 0x14, 0x8B, 0x2A, 0x0C, 0x75, 0x77,
0xB2, 0x04, 0x00, 0x00, 0x00, 0x9A, 0x01, 0x11, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x50, 0xA0, 0x94, 0xD5, 0x02, 0x08, 0x00, 0x00, 0x04, 0xA1, 0x55, 0x00, 0x8F,
0x62, 0x00, 0x7F, 0x71, 0x00, 0x73, 0x82, 0x00, 0x69, 0x95, 0x00, 0x69, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x18, 0x16, 0x14, 0x12, 0x10, 0x0E, 0x0C, 0x0A, 0x08, 0x06, 0x04, 0x02, 0xFF, 0xFF, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x24, 0x22,
0x21, 0x20, 0x1F, 0x1E, 0x1D, 0x1C, 0x18, 0x16, 0x13, 0x12, 0x10, 0x0F, 0x0C, 0x0A, 0x08, 0x06,
0x04, 0x02, 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x05, 0x01
};

uint8 tp_config_data3[] =
{
0x6D, 0x20, 0x03, 0xE0, 0x01, 0x05, 0x0D, 0x00, 0x01, 0x0A, 0x28, 0x0F, 0x50, 0x32, 0x03, 0x05,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x08, 0x17, 0x19, 0x1C, 0x14, 0x87, 0x29, 0x0A, 0x66, 0x68,
0xEB, 0x04, 0x00, 0x00, 0x02, 0x00, 0x02, 0x11, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x5A, 0x8C, 0x94, 0xC5, 0x02, 0x07, 0x19, 0x00, 0x04, 0x93, 0x5E, 0x00, 0x87,
0x66, 0x00, 0x7C, 0x70, 0x00, 0x72, 0x7A, 0x00, 0x6B, 0x86, 0x00, 0x6A, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x02, 0x04, 0x06, 0x08, 0x0A, 0x0C, 0x0E, 0x10, 0x12, 0x14, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x28, 0x26,
0x24, 0x22, 0x21, 0x20, 0x1F, 0x1E, 0x1D, 0x0C, 0x0A, 0x08, 0x06, 0x04, 0x02, 0x00, 0xFF, 0xFF,
0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x8D, 0x00
};


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

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

Share me