$20 LCR ESR Transistor checker project

[hiei27]

i don't know, i just assumed that newer firmware improved things like speed and precision, am i wrong? Oo

[indman]

i don't know, i just assumed that newer firmware improved things like speed and precision, am i wrong? Oo

No, the speed and accuracy will remain the same on the new firmware. My advice is not to touch the factory firmware, but rather wash the board and use a health tester. There is no need to interfere with the operation of a working device again.

[hiei27]

what do you mean for "health tester"? something like a multimeter?

[indman]

This is a poor translation into English. I meant your tester, use it with factory firmware.

[hiei27]

oohh i understand, thanks man 

[Yuriy_K]

i don't know, i just assumed that newer firmware improved things like speed and precision, am i wrong? Oo

There are some of my firmwares for the color display on page 277. Your board has 6 contacts for connecting the programmer (located vertically, below MEGA328)

When setting up the ESR readings in the k-firmware for Mega328 with a low R0 value (below .10 Ohm), I encountered damage to some film capacitors several times smaller than normal ones. Such capacitors can be classified as Low Esr.
Here is an example of measurements on different firmware...

[hiei27]

mmhh i will probably end up building one from scratch, using this one as it is and maybe arranging the ports to better suit my taste and my poor eyesight lol. do you have any recommendation for wich schematics/file/chip i should go for?

[Yuriy_K]

Two pages earlier, an example of assembling a TTester on Arduino Mega2560 with a 2.8" TFT SPI 240x320 display is shown. This resolution is maximum for k-firmware, for m-firmware the display resolution is higher.

[hiei27]

so u suggest going with the mega2560 or there's something more complete?

EDIT: for more complete i mean something that has enough memory to support most of the functions and addons, like the zener diode tester

[Yuriy_K]

The top of the previous page shows my changes for checking zener diodes and quartz resonators and vacuum quartz. Read about the memory sizes of the Mega2560.

[hiei27]

that seems nice, do you have a complete building guide with the gerber or similar for the pcb design?

[UltimateX]

Thank you, Indman.  I will give the firmware you attached a try.      The original version is 1.07k.

[UltimateX]

Hi Indman,

The firmware you attached seems to be compatible; however, my tester appears to be be having trouble completing the self test calibration mode.  The message "Not Calibrated" appears after attempting to calibrate the tester, plus it appears after measuring a component.  With test pin connections 1,2 and 3 shorted, the self test mode starts and then shows the sequence in the attached photos.  The display first shows an odd character then eventually gets stuck after the first stage, which is to measure the resistance between the pins.

I presume that I need to edit the Makefile that you included to fix these issues but would you have an suggestions for any of the changes I might make?

Thanks!

[hapless]

As silly as this question may sound, do you actually confirm "Selftest mode..?" by pressing the button or do you let it time out?

[indman]

I presume that I need to edit the Makefile that you included to fix these issues but would you have an suggestions for any of the changes I might make?

You don't need to make any changes, I already wrote earlier that this firmware has been tested on clones just like yours!
First of all, you need to carefully read the documentation for this project in order to correctly calibrate and operate this device! So hapless is right when he asks you a simple question - do you quickly press the Test button when the question mark appears on the display?

[prashk20]

Hello madires, indman, other members,

I am proposing addition of a Power Monitor hardware option that I have built to the main build. First of all thank you for maintaining the project and keeping such an active community around the project.

I had built a component tester and besides testing components, I also use it often to measure power consumption of devices running at different voltages. To do this, I had builtin a DCDC boost circuit on my tester. Recently, I added an INA226 module to my tester. INA226 is a popular and highly accurate shunt resistor based voltage (0-36V) and current measurement IC. It talks over I2C and, the option presented here, fully integrates with the Component Tester build on 328p. The Power Monitor menu item that I added displays 4 lines on the page - Battery Voltage, VOUT, IOUT and Power. The availability of this INA226 module seems good https://www.aliexpress.us/item/3256807703253714.html and it can easily be added to a tester using only 4 connections - SDA, SCL, 5V and GND. Power to Shunt and Load can be externally supplied.

Functionality of Power Monitor Menu Item -
  - Displays measured VOUT, IOUT and Power on lines 2, 3 and 4, respectively
  - Value units automatically switch between V/A/W and mV/mA/mW
  - Buzzer beeps if Power crosses a preset threshold. Single Test Button press
    will disable/enable the beeps
  - Displays Battery voltage on line 1
  - If TP_LOGIC ADC is defined and it measures a voltage then first line changes
    to Voltmeter until the voltage is present across Logic Probe resistors
  - Long press will zero out current IOUT value until device power-off
  - Displays negative current and power values as well. Voltage can only be positive

Memory consumption of Power Monitor Menu Item = 1936B Program + 4B Data

I have fast-forwarded my build over to 1.54m firmware. Attached are pictures of how the Power Monitor Menu looks at end of this post.

My build is here: https://github.com/pk17r/Ultimate_Tester/tree/prash/ComponentTester-1.54m/Files
I have added writeup to readme "INA226 Power Monitor (hardware option)" here https://github.com/pk17r/Ultimate_Tester/blob/bcab0b34073d7272fe1bae77c265b6b5dcac8bf3/ComponentTester-1.54m/Files/README#L2188
I am also showing a comparison of which files have been modified.

Differences of my build with 1.54m for Power Monitor Option are:
 - config.h: #define INA226_POWER_MONITOR   // to enable or disable the Power Monitor option
    - functions.h:  added 3 functions for INA226 and function for Power Monitor menu item
    - INA226.c:   the C file for INA226, a modified form of open source Arduino Library created by Rob Tillaart with license attached
    - Makefile:    add INA226.c to build objects
    - README:      add INA226 Power Monitor (hardware option) description
    - tools_misc.c:    add Power Monitor Menu Item Function
    - user.c:      add Power Monitor Menu Item
    - var_english.h:   add strings used by Power Monitor option
    - variables.h:     add strings used by Power Monitor option


Other differences v/s 1.54m on my build, not relating to Power Monitor option:

 - config.h: #define MAINMENU_AT_POWER_ON   // to go to Main menu at startup
    - main.c: skip to main menu at startup when MAINMENU_AT_POWER_ON option is enabled

 - config.h: #define SW_MENUITEM_TEST_COMPONENT     // to display a menu item "Test Component" at top of main menu, replaces "Exit" menu item at bottom of main menu
    - user.c: add SW_MENUITEM_TEST_COMPONENT menu item
    - main.c: add SW_MENUITEM_TEST_COMPONENT test component re-direct

- font_8x8_vf.h: add example of how to make number 2 and add external power symbol
- font_8x12t_win1251_vfp_h: correct example of how to make number 2 and add external power symbol
- font_8x16_vfp.h: add external power symbol

What do you think?

Thanks,
Prashant

[indman]

What do you think?

I think this will be a good and useful addition for version 1.55m madires!

[madires]

Nice! Looks like I have to get an INA226 module.

[prashk20]

Great! 

Thank you madires and indman!

I would love to see the Power Monitor function working at your end when you guys get yourself an INA226 module. I would love to see your suggestions or recommendations on the Power Monitor Menu as well. If you need anything from me, please feel free to let me know.

Thank you!

cheers! 
Prashant

[indman]

Other differences v/s 1.54m on my build, not relating to Power Monitor option:
 - config.h: #define MAINMENU_AT_POWER_ON   // to go to Main menu at startup
 - main.c: skip to main menu at startup when MAINMENU_AT_POWER_ON option is enabled

Madires, is it possible to enter the main menu immediately when you first turn on the tester if you quickly press the Test button 2 times? Or will this disrupt the tester's operating mode? If this is possible, then the MAINMENU_AT_POWER_ON option will not be necessary.

[madires]

Should be possible with some addtional code. It would make sense to add that as an option.

[prashk20]

Hello Madires, Indman,

I had not posted about accuracy of the INA226 sensor. Let me share that here. I have 2 DMMs, as shown in pictures below. I used left one for current and right one for voltage. I had calibrated them once with a dependable source, left one's error is -0.6%, right one's is -0.1%. Let me treat the DMMs + known error as ground truth.

Test 1: Low Current: 2.4mA
            Measured        Ground Truth                       Error
Current     2.4mA          2.39+0.6%=2.40mA           0%
Voltage     5.17V           5.164+0.1%=5.17V            0%

Test 2: Medium Current: 209.3mA
            Measured        Ground Truth                       Error
Current     209.3mA     207.3+0.6%=208.5mA        +0.4%
Voltage     5.14V          5.135+0.1%=5.14V             0%

Test 3: High Current: 1.07A
            Measured        Ground Truth                       Error
Current     1.07mA        1.056+0.6%=1.06A            +0.9%
Voltage     4.95V           4.928+0.1%=4.93V            +0.4%

Test 4: Different Voltages
Measured        Ground Truth                       Error
3.93V            3.930+0.1%=3.93V              0%
9.05V            9.051+0.1%=9.02V             +0.3%
12.04V          12.022+0.1%=12.03V          +0.1%
15.15V          15.136+0.1%=15.15V          0%


So, yes it is highly accurate with less than 1% error in measurements.


I did modify my INA226 module, reducing it's default shunt from 100mOhm to 20mOhm. Thereafter used 4-point Kelvin Measurement and some empirical tests to find out a more accurate shunt resistance value that my board has. Even more after that I introduced another voltage scaling parameter - INA_226_BUS_V_MULTIPLIER_e4 and found out it's value. Let me see if I can reduce the calibration parameters and make the settings more user friendly. Since the default shunt on these modules is 100mOhm (which is not great!), it would make sense to have default values for 100mOhm shunt rather than 21mOhm, that I have put. It would also make sense to add more information on how to calibrate one's module, if one wants to make it more accurate. Let me work a bit on it.

Thanks,
Prashant

[prashk20]

Hello Madires, Indman,

I have updated the above mentioned files and repository. A new much simpler and more accurate calibration process for INA226 is provided now. Default shunt is 100mOhm. config and calibration process:

#define INA226_POWER_MONITOR

#ifdef INA226_POWER_MONITOR
  #define INA226_I2C_ADDR                          0x40      /* 0x40 is address when A0=GND, A1=GND. For other address options, lookup "Table 6-2. Address Pins and Slave Addresses" in INA226 Datasheet  */
  #define INA226_R_SHUNT_MILLI_OHM                 100       /* Shunt Resistance in Milli Ohms, can be a float. Recommended shunt resistor resistance is of 20mOhms for 0-3A range, 10mOhms for 0-6A range, 2mOhms for 0-10A range  */
  #define INA226_CURRENT_LEAST_COUNT_MICRO_AMP     100       /* Least count is minimum resolution in measurement. Also decides Max_Measurable_Current = (32768 * INA226_CURRENT_LEAST_COUNT_MICRO_AMP / 1000000) Amps. Recommended value is 100, but increase this to get bigger range.  */
  #define INA226_I_OFFSET_MICRO_AMP                0         /* Offset current in microamps on shunt at no load that is added to measurement to make it zero. Can be negative */
  #define INA226_BUS_V_MULTIPLIER_e4               10000     /* Bus Voltage Manual Calibration Multiplier to increase accuracy in measurements. Only whole numbers accepted */
  #define INA226_P_THRESHOLD_mW_BUZZER             2500      /* Over-Power Alert Beeps: Sound buzzer if power goes over this threshold. HW_BUZZER needs to be enabled for this feature. Single Tap to disable/enable beeps. */
  #define I2C_RW                                             /* Requires I2C Read Support  */
  /* STEPS TO CALIBRATE INA226
   * 1. Set INA226_R_SHUNT_MILLI_OHM equal to shunt resistance in milli ohms. This is the shunt resistance between IN+ and IN- pins of INA226 in your setup.
   * 2. Set INA226_CURRENT_LEAST_COUNT_MICRO_AMP equal to your desired least count resolution for IOUT in micro amps. Expected values: 50, 100, 250, 500, 1000.
   * 3. Set INA226_I_OFFSET_MICRO_AMP = 0, INA226_BUS_V_MULTIPLIER_e4 = 10000.
   * 4. Build firmware and flash microcontroller (Your Component Tester).
   * 5. Attach a power supply with voltage 5-10V to INA226 on VBUS/IN+ and GND pins, without any load.
   * 6. Start Power Monitor. Long press Test Button and note ZERO IOUT value. Set INA226_I_OFFSET_MICRO_AMP = displayed ZERO IOUT value * 1000 (in micro amps). "ZERO IOUT -" means 0.
   * NOTE: Following adjustments shouldn't change values by more than 15-20%.
   * 7. Now measure VOUT using a reliable DMM. Set INA226_BUS_V_MULTIPLIER_e4 = 10000 / (Displayed VOUT on Power Monitor) * (DMM Measured VOUT). Can only be whole numbers.
   * 8. Now set DMM in current measurement mode. Use a resistor that will generate around 50-100mA IOUT measurement between IN- and GND pins with DMM in series with load. Note current measured on DMM.
   * 9. Update INA226_R_SHUNT_MILLI_OHM = INA226_R_SHUNT_MILLI_OHM * (Displayed IOUT on Power Monitor) / (DMM Measured IOUT), upto 2 decimal places.
   * 9. Set INA226_P_THRESHOLD_mW_BUZZER = Power threshold in milli Watt at which you want your Tester to sound Over-Power Alert Beeps.
   * 10. Build firmware and flash microcontroller. Your INA 226 is now calibrated. It should have less than 1% error in Current and Voltage measurements over a wide range like [5mA, 1A] and [5V, 20V].
   */
#endif

Process requires 2 times building and flashing the tester but this process is much more simpler and accurate. It is able to determine the mounted shunt resistance very accurately, leading to better accuracy. I have tested with 20mOhm and 100mOhm shunt resistances along with different current least count inputs. I look forward to when you get your INA226 and run the process. 
If you face any issues, please let me know.

Thanks,
Prashant

[UltimateX]

Okay, don't get excited!  I made a mistake as the 1.07k version automatically runs the self test with calibration and it states this neatly on one line, not across two lines.   I assumed the "_?" characters on the second line were spurious characters.  I did not know this was optional.  It is better to have the tester ask if the self test and calibration should be run as MOSFETs can be short across their three legs, which initiates the self test.  I would like to get this version of the firmware working and display formatted more like how it is shown on the 1.07k versio as it suits my purposes, plus I would like to have the self test question on one line.  I will see how I get on with this.  Thanks for you assistance. 

[RoGeorge]

Wanted to pick two BJT from a handful of jellybean PNPs, and noticed the values are inconsistent.
The version I have is this (probably LCR-T4):


Click to enlarge


Click to enlarge

Example of consecutive measurements (without removing the BJT form ZIF):

Code: [Select]

Beta  mV
436  630
433  632
432  631
434  630

another BJT
176  683
176  684
176  679
176  680

another BJT
480  626
478  626
476  626
474  631and so on.  The battery is a rechargeable "9V" NiMH, the instrument itself sees it as 8.52-8.54V at each new measurement.

The contacts of the BJT inside the ZIF socket seem firm enough.  The inconsistent measured values happens even when the BJT is left inside the ZIF and measured repeatedly.  What bother me the most is the inconsistency of Vbe.

Is this "normal" for the version I have?
What to do to get better repeatability?