$20 LCR ESR Transistor checker project

[UltimateX]

Thanks both.  I will first try AVRDudesshell2019 to see if that helps to write the fuses reliably. I will come back with the result.

[UltimateX]

Okay, I couldn't find a AVRDudesshell2019, so I just installed AVRDUDESS 2.14.  It successfully and reliably sets the fuse bits - I can set and read them as you showed now.  However, the fault still persists even with the fuse bits set as you showed.   How do I change the fuses to try to use the internal clock rather than the crystal? 

[indman]

Try setting E2 for LOWFUSE instead of F7. This is an internal 8MHz oscillator. Do not change the other fuses.
Also show me a screenshot of the AVRDudess 2.14 window after you write the firmware files, I am interested in the messages that appear in the black box at the bottom of the window.

[UltimateX]

Which firmware version did you want me to install on the blank 328P?  The copy of the firmware from the original 328P or the 1.12k firmware you posted?

[indman]

Better that firmware I gave you. Although the firmware you read from the original ATMega328 practically repeats it.

[UltimateX]

I used the original firmware (not sure which version it is) - it now works!  Thank you hapless and indman!    So I need to replace the original 8MHz crystal with an 8 or 16MHz crystal oscillator, correct?  Do you think I can upgrade to the latest firmware, i.e. 1.49m?

[indman]

So I need to replace the original 8MHz crystal with an 8 or 16MHz crystal oscillator, correct? Do you think I can upgrade to the latest firmware, i.e. 1.49m?

Try first to unsolder the original crystal, clean its legs well and solder it back. Don't forget to return F7 for the external quartz.
I think you do not need to update the firmware, you need to learn how to work with this firmware, it is also quite functional and stable, provided that you have no hardware problems.

[UltimateX]

Thanks indman.  I will try this now...

If I have to replace the crystal, is there a benefit to replacing the 8MHz crystal with a 16MHz crystal?

[indman]

If I have to replace the crystal, is there a benefit to replacing the 8MHz crystal with a 16MHz crystal?

Yes, there are, but not so global. When replacing the crystal at 16MHz you will need a new author's firmware for this frequency. You will find the details in the author's manuals.

[UltimateX]

I removed, cleaned and reinstalled the 8MHz crystal, but the white screen fault returns.  I will order a 8MHz and a 16MHz crystal as I may want to experiment with 16MHz firmware and new versions of the firmware.  Thank you very much for your help and advice.  It is very much appreciated!   

[ayubando]

I removed, cleaned and reinstalled the 8MHz crystal, but the white screen fault returns.  I will order a 8MHz and a 16MHz crystal as I may want to experiment with 16MHz firmware and new versions of the firmware.  Thank you very much for your help and advice.  It is very much appreciated!   

Check the screen pinout connection match with the new firmware pin connections

[ayubando]

I removed, cleaned and reinstalled the 8MHz crystal, but the white screen fault returns.  I will order a 8MHz and a 16MHz crystal as I may want to experiment with 16MHz firmware and new versions of the firmware.  Thank you very much for your help and advice.  It is very much appreciated!   

Check the screen pinout connection match with the new firmware pin connections

Check the screen pinout connection match with the new firmware screen pin connections settings

[hapless]

I removed, cleaned and reinstalled the 8MHz crystal, but the white screen fault returns.  I will order a 8MHz and a 16MHz crystal as I may want to experiment with 16MHz firmware and new versions of the firmware.  Thank you very much for your help and advice.  It is very much appreciated!   

Check the screen pinout connection match with the new firmware pin connections

Check the screen pinout connection match with the new firmware screen pin connections settings

As well as clock speed and rotation, and offset and feature set... if you're the one compiling the firmware 

ayubando, this forum allows you to edit your own posts, so no need to double-post to make corrections.

[Yuriy_K]

For this display, a flashing with a change in font orientation. At the request of the Russian version ...

Replaced the archive with the firmware based on the results of debugging

[kiltro]

Hi everyone!
Is this still possibile to find this Hiland M644 version? (I'm in Europe)
Are there any newer versions?

Thanks

[snapper]

sold out everywhere, maybe available at banggood from the beginning of august !

https://de.banggood.com/Original-Hiland-M644-Transistor-Tester-LCR-Diode-Transistor-Zener-Quartz-Measurement-p-1279042.html

[madires]

If you want to run the m-firmware with an NT7538 based display (ST7565 compatible) the reset timing needs to be adapted in function LCD_Init() in ST7565R.c:

Code: [Select]

  #ifdef LCD_RESET
    /* reset display */
      /* long reset for NT7538 (10µs/1µs) */
      /* trigger reset */
      LCD_PORT &= ~(1 << LCD_RESET);         /* set /RES low */
      wait20us();                            /* wait 20µs */
      LCD_PORT |= (1 << LCD_RESET);          /* set /RES high */
      /* wait for controller to perform reset */
      wait2us();                             /* wait 2µs */
  #endif

The next firmware version will have a setting to enable the long reset needed for the NT7538.

[supercap]

Hi all!
Sorry for my poor English...

I prototyped the tester with one breadboard, Arduino Mega 2560 why I want to learn how work the software (version 1.49m).
I'm using Visual Studio Code and PlatformIO.

I corrected all setting (hope so) in config.h file.
I put too, the right values on #define R_LOW and R_HIGH. matching the real resistor values.

I did the Self Test and I had this values:
T1 Vref 1176mV
T1 Vref 1176mV
T1 Vref 1177mV
T1 Vref 1177mV
T1 Vref 1177mV
T2 +Rl- 12 13 23 13 18 18
T2 +Rl- 12 13 23 13 17 18
T2 +Rl- 12 13 23 13 18 18
T2 +Rl- 12 13 23 13 17 18
T2 +Rl- 12 13 23 13 18 18
T3 +Rh- 12 13 23 -2 -9 2
T3 +Rh- 12 13 23 -2 -9 2
T3 +Rh- 12 13 23 4 -11 -4
T3 +Rh- 12 13 23 -11 3 -8
T3 +Rh- 12 13 23 1 -13 -1
T3 +Rh- 12 13 23 -6 2 -13
T5 Rh- 0 0 0
T5 Rh- 0 0 0
T5 Rh- 0 0 0
T5 Rh- 0 0 0
T5 Rh- 0 0 0
T6 Rh+ 4995 4992 4995
T6 Rh+ 4993 4996 4990
T6 Rh+ 4994 4994 4996
T6 Rh+ 4992 4996 4992
T6 Rh+ 4993 4994 4996

I measured few times a film capacitor like instructions.

Self Adjustment values and first problem:

A2 R0 12 13 23 109 109 175
A2 R0 12 13 23 109 110 175
A2 R0 12 13 23 109 110 175
A2 R0 12 13 23 111 110 174
A2 R0 12 13 23 109 110 176
A2 R0 12 13 23 111 108 176
A4 Ri- 27 27 27
A4 Ri- 27 27 28
A4 Ri- 27 27 27
A4 Ri- 27 27 28
A4 Ri- 27 27 27
A5 Ri+ 132 133 134
A5 Ri+ 132 133 134
A5 Ri+ 132 133 134
A5 Ri+ 132 133 134
A5 Ri+ 132 133 134
A6 C0 12 13 23 54 51 54
A6 C0 12 13 23 54 51 54
A6 C0 12 13 23 54 51 54
A6 C0 12 13 23 54 51 54
A6 C0 12 13 23 54 51 54

Ri- 3,7 Ohm
Ri+ 18,4 Ohm
C0 53 pF
R0 0,20 Ohm
Vref 1191mV
Vcc 5001mV
AComp -8mV

Now when I push the button appear the message "Error!"
I push again the button and the tester return on menu.

I tried to test some resistors and I get wrong values:
Resistor Value | Tester Value | Real Value
100                   49,7              97
148                   72                 149
470                   477               475
560                   556               555
4,7 K                 11,8 K           4,61K
6,8 K                 17,2 K           6,71K
100 K                48 K              99K

The tester can recognize diodes, transistor, triac, ecc. with no problems.

Maybe I miss something setup when I was reading the manual of Markus Reschke?
 

[madires]

An Ri- of 3.7 Ohms is too low. There's something wrong. Have you enabled ADC_LARGE_BUFFER_CAP in config.h? The error message for the self-adjustment is caused by a too high R0 for probes #2 and #3 (A2 R0 12 13 23 109 109 175). The limit is 150 (1.5 Ohms for both in series).

[supercap]

An Ri- of 3.7 Ohms is too low. There's something wrong. Have you enabled ADC_LARGE_BUFFER_CAP in config.h? The error message for the self-adjustment is caused by a too high R0 for probes #2 and #3 (A2 R0 12 13 23 109 109 175). The limit is 150 (1.5 Ohms for both in series).

Thank you Madires for you very fast reply.
Tomorrow I will check for the ADC_LARGE_BUFFER_CAP option.
About pin resistances, I will try to change the wires with not crimped one. This because I have found some days ago, one wire with inusual resistance...

[supercap]

I enabled ADC_LARGE_BUFFER_CAP and changed wires, now resistor values are ok!
Still present some problems on "big" capacitors:
Value | Tester Value | Real Value  | Type

100uF    76,12           100,4           electrolytic
220uF    165,9           225,0           electrolytic
47uF      39,19           51,25           electrolytic
10nF      10,26           10,53           polyester
330nF    316,2           318              polyester
150pF    155pF           154              tantalum

Maybe I miss something again... 

I can find somewhere a schematic diagram of this tester with all functions with Mega 2560 controller?

I wanna use this post too for make my big compliments for the clean code written by Madires. You did a really big work.

[indman]

Maybe I miss something again...

Yes, here is the part of the madires manual that will help you

"* Capacitors

The measurement of capacitance is split into three methods. Large caps >47µF
are measured by the charging cycle method with 10ms pulses. Mid-sized
caps between 4.7µF and 47µF are processed the same way but with 1ms charging
pulses. And small caps are done by the analog comparator method. That
way the accuracy of the measurement of caps is optimized.

Large capacitances require a correction. Without correction the measured values
are too large. IMHO, that is caused by the measurement method, i.e. the ADC
conversion after each charging pulse needs some time and the cap looses charge
due to internal leakage during the same time. Also the ADC conversion itself
needs some charge to operate. So it takes longer to charge the cap, and the cap
seems to have a larger capacitance. A discharge measurement later on tries to
compensate this, but is able to do it just partially. The correction factors (
CAP_FACTOR_SMALL, CAP_FACTOR_MID and CAP_FACTOR_LARGE in config.c) are choosen
to work with most tester models. In some cases you might have to change them."

[supercap]

Maybe I miss something again...

Yes, here is the part of the madires manual that will help you

"* Capacitors

The measurement ...

Large capacitances require a correction. Without correction the measured values
are too large. IMHO, that is caused by the measurement method, i.e. the ADC
conversion after each charging pulse needs some time and the cap looses charge
due to internal leakage during the same time. Also the ADC conversion itself
needs some charge to operate. So it takes longer to charge the cap, and the cap
seems to have a larger capacitance. A discharge measurement later on tries to
compensate this, but is able to do it just partially. The correction factors (
CAP_FACTOR_SMALL, CAP_FACTOR_MID and CAP_FACTOR_LARGE in config.c) are choosen
to work with most tester models. In some cases you might have to change them."

Thank you indman!
Yes I read this, but there is write "Without correction the measured values
are too large". In my case, I have small values not large one.
For this I was think about some other problems...

[indman]

Yes I read this, but there is write "Without correction the measured values
are too large". In my case, I have small values not large one.

You have a ARDUINO MEGA2560 and you have enabled the ADC_LARGE_BUFFER_CAP option, so you will need to correct capacitance readings on various bands anyway.

"CAP_FACTOR_SMALL, CAP_FACTOR_MID and CAP_FACTOR_LARGE in config.c"

Madires, there is a small error in Readme - instead of config.c, config.h is meant.

[supercap]

Thank you indman, with a little setup on CAP_FACTOR_LARGE option I resolved this problem too.
Now last problem...
If I try to use DATA_EEPROM for store data in EEPROM, my tester don't work.
My display appear empty, after some second appear the text "2: 5v".
Is like the firmware cant store the data in the right mode...
If i double press the button for enter in menu, appear ":", then the moving pointer "*".
Is like the text are not stored in EEPROM?