$20 LCR ESR Transistor checker project

[Davo013]

Davo013
To eliminate any errors during compilation, I checked it on my color display beforehand. The original font is terribly straining for the eyes, so I remade it for my own. Here are the results of checking various capacitors. All tests passed normally. There are no extraneous symbols. I rebuilt the firmware for your display, check the results...

I Just burned the firmware and at the same places the strange symbols came up...
It's not random
But i found something which might be something, or maybe not...

When i copied from the manual a line to a .txt file i saw this... check picz
Could it not be something like that? fi is shown as an arrow up
Maybe something using different platforms like mac, linux?? I'm not a real computer guy haha

I found because tried another attempt to compile, because the contrast is very dim, after burning the firmware i can hardly read the screen...
When adjusting the contrast it starts at 40, and you have to click many times.
Then it counts down from 128 when it's at "116" it's perfect, if click further on, the screen dims again...
At 63 it's at full brightness again and at "56" you will reach again the perfect balance
I Checked the Makeme file and i think it's this line:

# The contrast value can be predefined with the constant VOLUME_VALUE
# for ST7565 controller the value can be between 0 and 63, for the SSD1306 0 to 255 can be selected.
#CFLAGS += -DVOLUME_VALUE=25

Should it be like this to change?
# The contrast value can be predefined with the constant VOLUME_VALUE
# for ST7565 controller the value can be between 0 and 63, for the SSD1306 0 to 255 can be selected.
CFLAGS += -DVOLUME_VALUE=56

I still don't know how to compile haha i'm trying to understand how it all works

In the manual there was a tiny thing about compiling the Makeme file with AVR, and this lol

Chapter 9 To Do List and new ideas

5. Write User's guide for configuring the tester with the Makefie options and description of the
build chain.
This would make the manual really good though! the Makefile is like the engine computer from a car

[indman]

Davo013, You don't need to compile and invent anything right now. You need to get a working tester right now, right?
So, my advice - connect the programmer, make sure to perform the procedure of erasing the entire crystal in the program(I showed the option in red in your screenshot), then write the firmware Rev.804 from my archive, and set the fuses so (low: 0xF7, high 0xD9, ext: 0xFD).
If your device works fine, then you can further experiment with compyling your own firmware. If the tester works with errors, then you need to look for the reason further.

[Davo013]

That worked!

I can test now all the caps without the tester shuts down...
With the calibration i saw the first time 1 error with the characters
after the 2nd calibration it was gone.

[Davo013]

Within a few days some Chinese 328 will arrive...
Hopefully they are not fake... But you never know with damn Chinese crooks... I had some spare one's, but after cleaning with iso i had a black cotton swab :X
The seller where i bought them last week hag quite good reviews, but even that you cannot always trust... They somehow know almost know every dirty trick to rip you off for a few cents haha
Even parts that are originally 35cents, they sand it & rebrand 'm.... that's totally nuts though...

I was thinking to do an order at digikey, but can all the 328's go on the bside? i guess so, as long as it's a TQFP32...
The prices are quite different, and the specs look quite the same... only that FuSa series has more in & outputs which can maybe causes issues?
I guess you guys know more about it lol

ATMEGA328PB-AU €1.52 AVR® ATmega, Functional Safety (FuSa)
ATMEGA328PB-AN €1.54 AVR® ATmega, Functional Safety (FuSa)
ATMEGA328PB-AUR €1.59 AVR® ATmega, Functional Safety (FuSa)
ATMEGA328PB-ANR €1.64 AVR® ATmega, Functional Safety (FuSa)
ATMEGA328-AU €2.26 AVR® ATmega
ATMEGA328-AUR €2.34 AVR® ATmega
ATMEGA328P-AU €2.46 AVR® ATmega
ATMEGA328P-AUR €2.56 AVR® ATmega
ATMEGA328P-AN €2.61 AVR® ATmega
ATMEGA328P-ANR €2.69 AVR® ATmega

Awesome to see that there's a whole worldwide community behind such a device!
To bad those chines make a huge profit of it...
Ah well at least they sell it cheap! (most of them)
In my country all the sellers complain about the Chinese, but hey over here the flip the price's 3x or 4x for the same garbage out of China pffft and that's excl. shipping
If they weren't that greedy people will buy less directly from China

[indman]

To Davo013,
Atmega328PB completely replaces Atmega328P!!!

[Davo013]

To Davo013,
Atmega328PB completely replaces Atmega328P!!!

Ah okay, thnx! I thought I’d better ask  I couldn’t find much info about on this forum, and they have more connections on the same footprint…
Most info was about people having problems with the PB’s
You guy’s are the real specialists at these testers i’m just a noob with stuff haha
I’m more into tube amp gear and that kinda stuff 😂
The next coming week there will arrive some some parts from AliEpress the most stuff from Ali is fake, but I’m trying out my new strategy buying parts on Ali….
If I have to buy Parts on Digikey every it will cost me to much on shipping costs, or I have to buy more then 50 euro’s

[indman]

Davo013, This topic discusses the transistor tester project! Discussion of other devices and projects is inappropriate here so as not to clutter up an already extensive topic!

[madires]

I found a while ago a B-Side mod with a relay protection, but somehow I can’t find it anymore, and I didn’t make a book marker also…’ But I want to protect myself against destroying the tester and my tester with a charged capacitor through!

The discharge/protection relay is explained in Karl-Heinz' documentation (https://github.com/kubi48/TransistorTester-documentation) and supported by both OSHW firmwares.

[Davo013]

Sorry for that, i shall remove the post…

I found a while ago a B-Side mod with a relay protection, but somehow I can’t find it anymore, and I didn’t make a book marker also…’ But I want to protect myself against destroying the tester and my tester with a charged capacitor through!

The discharge/protection relay is explained in Karl-Heinz' documentation (https://github.com/kubi48/TransistorTester-documentation) and supported by both OSHW firmwares.

Thnx!

[Yuriy_K]

I assembled a stand for testing my ideas from the display left over after upgrading the Hiland M644. The ATMega 328 and HCF4060BE in DIP cases were a good fit for measuring vacuum quartz and ceramic resonators that the Hiland M644 cannot measure. Here are some measurement examples. I had to change the k-firmware a little...

[HumbleDeer]

I assembled a stand for testing my ideas from the display left over after upgrading the Hiland M644. The ATMega 328 and HCF4060BE in DIP cases were a good fit for measuring vacuum quartz and ceramic resonators that the Hiland M644 cannot measure. Here are some measurement examples. I had to change the k-firmware a little...

You may want to change "Frequency" to "Oscillator Freq." as to not confuse it with the Frequency Generator or Freq. Output ports.

[Yuriy_K]

You may want to change "Frequency" to "Oscillator Freq." as to not confuse it with the Frequency Generator or Freq. Output ports.

I try to leave the names intended by the Author of the k-firmware. I show how this circuit after a small addition allows you to measure frequencies from an external generator. Messages in Cyrillic are duplicated by measured readings in Latin. I think you will understand... I have not yet set the quartz frequency in the Ttester, for this reason the readings differ in the 5th digit. I am waiting for all elements of the circuit to work for at least 100 hours.

[madires]

Happy programming!

v1.53m:
- Fixed interrupt address issue in gcrt1.S (OPTIMIZE_VECTORS), mainly for avr-gcc 8.3.0 (thanks to horo@EEVblog).
- Updated Polish texts #2 (thanks to Jacon@EEVblog).
- Fixed source code management issue for Timer1 related global variables (reported by indman@EEVblog).
- Updated Polish texts (thanks to szpila@EEVblog).
- Added option to enable/disable self-test (SW_SELFTEST, suggested by indman@EEVblog).
- Added option to display measurement values of self-test/adjustment page-wise (UI_TEST_PAGEMODE, requires >= 6 text lines).
- Added convenience function Display_Value2() to reduce firmware size and changed all suitable function calls.
- Added 5V-Meter with selectable input impedance (SW_METER_5VDC, suggegsted by boneDragon@EEVblog). Optional beep when a threshold is exceeded (requires buzzer).
- Added option to display 4-digit values as value with prefix (UI_PREFIX, suggested by Kim Christensen@EEVblog and edgard22@EEVblog).
- Optional flyback diode is also shown for JFETs now (suggested by Yuriy_K@EEVblog). Fixed D/S reversal issue for p-channel JFETs with flyback diode.
- Updated Brazilian Portuguese texts (thanks to wandows@EEVblog).

Please download at:
- https://github.com/madires/Transistortester-Warehouse/tree/master/Firmware/m-firmware
- https://github.com/kubi48/TransistorTester-source/tree/master/Markus (soon)

[indman]

Madires, Thank you very much for another gift to all of us and the great work you have done!
I have a small suggestion regarding the README file - it would probably be useful and correct if it indicated the number of the current firmware version, as you indicated in the CHANGES file?
For example, Last edit: 2024-08-01 (Current version 1.53m)

[tedris]

Hello, I am researching how to upload this file to the lcr meter t-7 (I wanted Finirishi brand original software, if the hex file arrives, I will upload it ready-made, if not, I will try this. It broke down due to the capacitor, I bought a new chip). After making the necessary corrections, how can I convert it to hex file in Windows? I can erase and read the Atmega 324pa chip, I use Atmel Studio 6. I have an Atmel USB Avrısp xpII programmer. I am a software developer, but this is my first time doing something like this. I would be happy if you send me a video or a summary. thanks.

[Feliciano]

Usually the Asian clone firmware is locked for reading, so we can't help you obtaining the "original" clone code. What we can help is providing the updated and official OSHW firmware, which last version could be obtained three posts above this one.

For the k-firmware, there's no ready-made binaries for the T7; for the m-firmware you could build one yourself following the instructions of the clones file, and burn it with your cable remembering to set the fuses according to your crystal. Or if you FNIRSI is like my last TC1, you could go back this thread a few months and follow the discussion we had porting the m-firmware to this particular variant.

[madires]

I have a small suggestion regarding the README file - it would probably be useful and correct if it indicated the number of the current firmware version, as you indicated in the CHANGES file?
For example, Last edit: 2024-08-01 (Current version 1.53m)

Wouldn't that be redundant when looking at the directory: ComponentTester-1.53m/README?

[indman]

Wouldn't that be redundant when looking at the directory: ComponentTester-1.53m/README?

I think it won’t be superfluous, but that’s my opinion. It doesn't look out of place in the PDF file. Especially since many people keep the manual file in different text formats separately from the main distribution.

[pepe10000]

Hello.

Attached the update of the Spanish language file with the latest news.

All the best.

[madires]

I think it won’t be superfluous, but that’s my opinion. It doesn't look out of place in the PDF file. Especially since many people keep the manual file in different text formats separately from the main distribution.

You've convinced me:

Code: [Select]

Last edit:   2024-08-07
For version: 1.54m


[tedris]

Hello, I learned how to compile the file in Linux. The questions I'm looking for answers to are: I couldn't find which codes I should use for my LCD screen. Because my screen model probably doesn't exist.

I noticed something like this: When define spi_hardware is turned on in config_644, it sees some variables as undefined and gives an error. When define spi_bitbang, it compiles without error and hex is created.
In summary, which code block will I use for the screen, clone or config? Secondly, why is the spi problem caused? Doesn't atmega324pa support it?

[madires]

Please use the display settings for the old TC-1 variant from the Clones file (ST7735, bit-bang SPI). The display wiring of your tester doesn't match the ATmega's SPI pins. So it needs bit-bang SPI for driving the display.

[tedris]

Thank you very much for your help, I will try it right away. There is a 16000 mhz cristal on the circuit. Should I choose 16 when editing the makefile?

[Feliciano]

You seem to have the original TC-1, with the additional power MCU (U4) that should be substituted or flashed with an alternate code when about to run the OSHW firmware.

And your Crystal is 16MHz, so you should declare that on one of the config files.

[tedris]

I tried all the LCD codes that belong to the code you gave, but the loading is successful in all of them, but the screen remains white. Since the 5v going to the atmega is cut off after a certain period of time while it is plugged into the usb, I connected 5v from outside and the screen does not turn off. But the screen comes completely white. My screen was mostly black. I tried a bunch of things but it didn't work. I use AVR 4 Software. My programmer is usb avrisp xpII. Nothing came out on the screen, even if it was wrong.