$20 LCR ESR Transistor checker project

[indman]

NF6X, I, for example, it does not bother me in any way, and I will not and do not want to bother with hypotheses as to how and why details absolutely unnecessary for the project appeared. If you are so concerned about it, ask a Chinese engineer, such as FNIRSI, directly!

[Feliciano]

Agree. Please lets focus on the matter in question: how to make this work with OSHW firmware.

[indman]

Feliciano,you have checked the display connection and identified the controller pins. Are the rest of the peripherals connected in the standard way or are there also differences from the original circuit? There are a lot of unclear points on the schematic you showed earlier, the pins of the ATMega324 are not labeled. It would be nice if you could draw a more detailed circuit diagram.

[Feliciano]

Indeed:

I'm checking this soldered display, and uses a different pin mapping (from right to left bottom-view):
1=GND, 2=Vcc, 3=PB4 (44), 4=PB3 (43), 5=PB5 (1), 6=PB7 (3)

And not all the pins are labeled because I'm writing over an m328p schematic [WIP].

[indman]

That's understandable, that's not what I'm asking. To which ports are connected 6 measuring resistors, ION, calibration capacitor, IR detector?
This is all to be considered when customizing new firmware.

[2hry]

@Feliciano

Your tester looks like my JOYIT T7.
I have removed the Stc chip, and flashed m-firmware.
It is not working anymore, because the srv05 got damged, but i made some notes of the pinout.

LCD_RES          PB4           
LCD_DC           PB3
LCD_SCL          PB7
LCD_SDA          PB5
LCD_OFFSET_X     2               
LCD_OFFSET_Y     1               
LCD_FLIP_X                     

TP1              PA0
TP2              PA1
TP3              PA2
TP_ZENER         PA4
TP_REF           PA3
TP_BAT           PA5
TP_CAP           PA7

R_RL_1           PC0
R_RH_1           PC1
R_RL_2           PC2
R_RH_2           PC3
R_RL_3           PC4
R_RH_3           PC5

POWER_CTRL       PD7
TEST_BUTTON      PB2 
IR_DATA          PD3
ADJUST_RH        PC6

[indman]

I have removed the Stc chip, and flashed m-firmware.
It is not working anymore, because the srv05 got damged, but i made some notes of the pinout.

The tester can work without SRV05, unless, of course, the microcontroller is also damaged.
You could provide the firmware so Feliciano can test it on his clone.

[2hry]

I think the microcontroller is damaged.
It didnt start anymore and the srv05 got hot. So i removed it and the tvs, but it always measures a battery on pin2.

and compiled it in english again if anyone is interested.

[Feliciano]

Indeed 2hry firmware worked, and as madires suggested, without further hardware modifications. Thank you very much dears.

Now my unit is running 1.51m (STC no longer needed, removed). And with the hints on the pin assigments, I will work on the original configs for customization.

FWIW (maybe for the clones files), attached a comparison of some clones' PCBs (JOYIT, FNIRSI on the right).

PS: It also looks to me that 2hry's MCU is damaged.

[rddube]

Hello everyone,

Programmed my TT with version 1.51m and when I try to put it into L Monitor (inductance) it just stands on the screen in the photo and won't read anything and won't respond to the button press either.

What did I do wrong to not have it give my inductance readings?

Many thanks,

Raymond

[carl1961]

what version is this?

[rddube]

what version is this?

You mean the Ttester, it is version ST7565R .

[indman]

Programmed my TT with version 1.51m and when I try to put it into L Monitor (inductance) it just stands on the screen in the photo and won't read anything and won't respond to the button press either.

Enable the RLC Monitor mode in the firmware. Will the tester in this mode react to the connection of resistance, capacitance, inductance?

Feliciano, To which ports of the ATmega324 were pins 7 and 8 of the STC connected? I've almost updated the circuit diagram for FNIRSI's LCR-TC1.

[madires]

Your tester looks like my JOYIT T7.
I have removed the Stc chip, and flashed m-firmware.
It is not working anymore, because the srv05 got damged, but i made some notes of the pinout.

LCD_RES          PB4           
LCD_DC           PB3
LCD_SCL          PB7
LCD_SDA          PB5

Have you configured bit-bang SPI or hardware SPI? With that pin assignment hardware SPI should be possible.

[Feliciano]

@madires: I don't know about the firmware binaries 2hry shared, but with 1.46m I enabled bitbang for the old TC1 (now I recall you said hardware SPI was not possible) and I did the same for the new one; and with 1.51m I got undefined function errors when trying to enable the default hardware SPI for the FNIRSI, so I choosed bitbang as well.
Sidenote: I'm using 1.46m now because the same set of features represent 99.7% usage on that, and 100.6% (32980B) on the other. I was planning to try intermediate versions, or perhaps you can suggest what to remove for this particular unit in order to save some Bytes.

@indman: the STC was connected to traditional PD1 and PD2. I attach the updated draft diagram for comparison.

Thank you both.

[indman]

Have you configured bit-bang SPI or hardware SPI? With that pin assignment hardware SPI should be possible.

On such a small display 1.8 we should not notice any difference in speed, or are there any other important factors that indicate the usefulness of hardware SPI?

[Feliciano]

If code-wise hardware SPI would save some Bytes (vs software SPI), that alone would it be useful/worthy.

[rddube]

Programmed my TT with version 1.51m and when I try to put it into L Monitor (inductance) it just stands on the screen in the photo and won't read anything and won't respond to the button press either.

Enable the RLC Monitor mode in the firmware. Will the tester in this mode react to the connection of resistance, capacitance, inductance?

Feliciano, To which ports of the ATmega324 were pins 7 and 8 of the STC connected? I've almost updated the circuit diagram for FNIRSI's LCR-TC1.

Hello Indman, when I enable RLC Monitor, tester reacts to resistance, capacitance perfectly, when I try to test an inductor, it gives me a resistance reading... Thank you for your help!

[indman]

when I try to test an inductor, it gives me a resistance reading...

This means that the tester cannot determine the inductance because it is too small or its resistance is greater than 2 kOhm.

[madires]

Sidenote: I'm using 1.46m now because the same set of features represent 99.7% usage on that, and 100.6% (32980B) on the other. I was planning to try intermediate versions, or perhaps you can suggest what to remove for this particular unit in order to save some Bytes.

You could disable checks for rare components (SW_UJT, SW_SCHOTTKY_BJT).

[madires]

On such a small display 1.8 we should not notice any difference in speed, or are there any other important factors that indicate the usefulness of hardware SPI?

A slightly smaller firmware size, as Feliciano already pointed out. And the most visible impact would be a faster screen clearing.

[rddube]

when I try to test an inductor, it gives me a resistance reading...

This means that the tester cannot determine the inductance because it is too small or its resistance is greater than 2 kOhm.

But whatever size I put it always gives me a resistance reading. Can it not read a 1uh 1R0 inductor ? These are inductors around a CPU on a motherboard. What is the range that it can read? Many thanks.

[indman]

rddube,The lower range of inductance measurements on m-firmware starts at about 10 microHenry. If you want to measure inductance values ​​lower than 10 microHenry, you can build an additional LC meter attachment or use the resonant method in k-firmware.

[Feliciano]

A slightly smaller firmware size

I'm for it. So let's do the 1.51m exercise again (32980B vs X) and please help me troubleshoot my configuration. I enabled
SPI_HARDWARE both on config and config_644, and disabled SPI_BITBANG on the first. I thought that would be enough for the Make, but I get the following errors:

Code: [Select]

SPI.c: In function 'SPI_Clock':
SPI.c:388:10: error: 'SPCR' undeclared (first use in this function)
   Bits = SPCR;                            /* get control register */
          ^
SPI.c:388:10: note: each undeclared identifier is reported only once for each function it appears in
SPI.c:389:19: error: 'SPR1' undeclared (first use in this function)
   Bits &= ~((1 << SPR1) | (1 << SPR0));   /* clear clock rate bits */
                   ^
SPI.c:389:33: error: 'SPR0' undeclared (first use in this function)
   Bits &= ~((1 << SPR1) | (1 << SPR0));   /* clear clock rate bits */
                                 ^
SPI.c:406:18: error: 'SPI2X' undeclared (first use in this function)
     Bits = (1 << SPI2X);           /* set bit to double SPI speed */
                  ^
SPI.c:409:3: error: 'SPSR' undeclared (first use in this function)
   SPSR = Bits;                     /* update register */
   ^
SPI.c: In function 'SPI_Setup':
SPI.c:444:3: error: 'SPCR' undeclared (first use in this function)
   SPCR = (1 << SPE) | (1 << MSTR);
   ^
SPI.c:444:16: error: 'SPE' undeclared (first use in this function)
   SPCR = (1 << SPE) | (1 << MSTR);
                ^
SPI.c:444:29: error: 'MSTR' undeclared (first use in this function)
   SPCR = (1 << SPE) | (1 << MSTR);
                             ^
SPI.c:450:10: error: 'SPSR' undeclared (first use in this function)
   Bits = SPSR;           /* read flag */
          ^
SPI.c:451:10: error: 'SPDR' undeclared (first use in this function)
   Bits = SPDR;           /* clear flag by reading data */
          ^
SPI.c: In function 'SPI_Write_Byte':
SPI.c:469:3: error: 'SPDR' undeclared (first use in this function)
   SPDR = Byte;                     /* start transmission */
   ^
SPI.c:470:12: error: 'SPSR' undeclared (first use in this function)
   while (!(SPSR & (1 << SPIF)));   /* wait for flag */
            ^
SPI.c:470:25: error: 'SPIF' undeclared (first use in this function)
   while (!(SPSR & (1 << SPIF)));   /* wait for flag */
                         ^
make.exe: *** [SPI.o] Error 1

> Process Exit Code: 2


[madires]

If you enable SPI_HARDWARE in config_644.h you don't need to do that also in config.h (it will trigger a compiler warning). The error messages about undeclared register names could be caused by a missing header file. That should be avr/io.h (#include <avr/io.h> which is included in common.h). Try an additional #include <avr/io.h> in SPI.c.