$20 LCR ESR Transistor checker project

[gtroc71]

Thank you so much Jacques and Madires.
Appreciate your fast response

[Radio Tech]

Wow,
Looks like I have been slacking here. And a lot of catching up to do. Had forgotten all about this thread.
I have 2 of these now but one is dead. Maybe I will have a go at learning to update the firmware in mine and repairing the dead one.
So much to go back and read
I did not even know about the self calibrate lol.

[Radio Tech]

This was my first one I purchased.  And my first fail 
While testing some 100uf caps at 350 volts one of the caps did not get enough discharge time. When I connected the test leads the tester failed to come on. At least this is what I think happened.



In the pic you can see a programmer I purchased a few months back and have yet to use it.
So I think my first attempt is to grab the schematic of this tester and install a header on the board.
I will attempt to communicate with the processor.

Been a long time (1990) since I have even attempted to read and program Atmel chips.  And even then it was a complete different beast back then.
At least this may give me a chance to learn a few things.




As said in my above post I have a lot of catching up to do. And a lot of back reading. If anyone would like to give some pointers I am all ears

[Radio Tech]

Well perhaps I was wrong about the controller being dead. After installing the pin header I was able to read the contents from the Atmega 168 chip.

After doing this I noticed something that was not happening before.  When ever I connected the battery to the device and hit the test button nothing happened. No display no red LED.
But now when I hit the test button for a couple of seconds I get a message on the LCD.

"BAT 4.8V empty"

I know my battery is good and test at 9 volts. So I but my DMM across the battery leads and when you hit the test button the voltage drops from 9 to 4 volts.

Looks like I need to check some on board components and see if any are failing.



Perhaps I should had started another thread instead of tying this one up.


Edit to say, looks like I can read the chip but when I programmed the chip I just get a black bar now when I press the test button.

[hapless]

I did a quick test and the firmware seems to work (shuts down the tester because the voltage is too low), but I get nothing on the screen, so it will need some modifications  , which, unfortunately, I won't be able to get started on for at least a month. If I manage to get this firmware to work on my tester, I will post the changed files.

Looks like I won't be doing that after all. Had a little time on my hands and tried it out. The firmware is for strip-grid layout, which is not a problem, but the way it displays information seemed to look good from the screenshots, but up close and personal, I didn't like it at all. So I see no reason to try hacking it. On the other hand, I like the fact that they tried to use the screen in a more logical way for a graphical LCD. Something to think about when I actually get to do some coding.

Markus, Karl-Heinz, neither of you answered previously. If I make changes, is there a way to submit them to you without the use of SVN?

Edit to say, looks like I can read the chip but when I programmed the chip I just get a black bar now when I press the test button.

Does it turn off as soon as the button is released?

[madires]

Markus, Karl-Heinz, neither of you answered previously. If I make changes, is there a way to submit them to you without the use of SVN?

Send them directly to Karl-Heinz via email

[Radio Tech]

Does it turn off as soon as the button is released?

Yes, The string of bars are only present while holding the test button.
As said before this is my first attempt at programming so this is a new learniing curve for me. I am using Extreme AVR burner and dont think I am doing it right. I read something in the "testers" manual about having to set fuse bytes. So with that I am sure I am doing something wrong.

[hapless]

Send them directly to Karl-Heinz via email

Will do, thanks!

Yes, The string of bars are only present while holding the test button.
As said before this is my first attempt at programming so this is a new learniing curve for me. I am using Extreme AVR burner and dont think I am doing it right. I read something in the "testers" manual about having to set fuse bytes. So with that I am sure I am doing something wrong.

You need to burn both flash and EEPROM for the tester to work. Looks like flash didn't get programmed that time. I wouldn't recommend messing with fuse bits until you figure out what most of them do.

[Radio Tech]

You need to burn both flash and EEPROM for the tester to work. Looks like flash didn't get programmed that time.

I really think you are correct. Although the program says it is doing both somehow I do not think it is.

I wouldn't recommend messing with fuse bits until you figure out what most of them do.

Agreed and I have not touched those settings yet.

Back in the early 90's is the last time I have even played with any Atmels. And even then it was just a flash. So I am a complete noob when it comes to them. Since this tester is dead I thought perhaps this would be a good learning tool on the programming and learn a bit on how these testers work.  Even if I brick the chip I have the equipment and the knowledge to replace them.

I did notice something about the tester. The dead one has a 8MHz crystal on board and the new one has no crystal.  Both testers are identical other than the missing crystal.

Overthe next few days as time allows I plan to do a bit of reading up on AVR programming and watch a few YT vids.

[madires]

I wouldn't recommend messing with fuse bits until you figure out what most of them do.

Agreed and I have not touched those settings yet.

You need to set the fuse bits only once for a brand new ATmega. The Makefile includes the logic to select the correct fuse settings and to call avrdude. For the k-firmware you simply call 'make fuses', 'make fuses-crystal' or 'make fuses-crystal-lp' based on the clock source. For the m-firmware it's just a 'make fuses'.

[Radio Tech]

You need to set the fuse bits only once for a brand new ATmega. The Makefile includes the logic to select the correct fuse settings and to call avrdude. For the k-firmware you simply call 'make fuses', 'make fuses-crystal' or 'make fuses-crystal-lp' based on the clock source. For the m-firmware it's just a 'make fuses'.

Thanks for that bit of info madires.
Have not used avrdude yet. The only program I have tried is Extreme AVR. If I remember correctly I think avrdude is a dos base program. Atleast that is what I remember from Youtube.
I will try and do some more reading and YT vids over the short week end.

[dadler]

I got one of these boxes off ebay, but the cheap 2mm banana jacks drove me nuts. So I swapped in some shrouded 4mm jacks to be able to use my Fluke leads:

[neslekkim]

I have the same unit, where did you find the shrouded connectors?

[Radio Tech]

Thats looks pretty nice.
Thinking about ordering another one of these. Maybe that one.

Anyway been serching for more info on programing.  Read till my head hurts.
Sure wish there were some yourtube videos on this tester and programming it. 
Know more about how would be nice, like do you program flash first or hex?  Have not been able to find this info. But I am sure I will 

[dadler]

I have the same unit, where did you find the shrouded connectors?

I got them at the corner electronics store. They are just standard Pomona shrouded jacks. I can get the part number if you want.

[madires]

Anyway been serching for more info on programing.  Read till my head hurts.
Sure wish there were some yourtube videos on this tester and programming it. 
Know more about how would be nice, like do you program flash fist or hex?  Have not been able to find this info. But I am sure I will 

It's programmed like any other ATmega via ISP. A quick search for "flashing atmega" at youtube lists a lot of videos. If you got an avrdude compatible ISP programmer and the make tool, a "make upload" will do the job.

[BlueBill]

If anyone has the latest m328p hex file for the M168 version (2x16 LCD) I'd appreciate it if you could attach a copy here.

edit: I found this, which contains a hex file. Is it the correct one?
http://www.mikrocontroller.net/svnbrowser/transistortester/Software/trunk/mega328_2X16_menu/

[madires]

If anyone has the latest m328p hex file for the M168 version (2x16 LCD) I'd appreciate it if you could attach a copy here.

edit: I found this, which contains a hex file. Is it the correct one?
http://www.mikrocontroller.net/svnbrowser/transistortester/Software/trunk/mega328_2X16_menu/

If your tester has an ATmega168, please compile the firmware for the ATmega168. The pre-compiled ATmega328 firmware is too large for the ATmega168 (16kB flash). The ATmega328 got 32kB flash.

[BlueBill]

It's got a 328p.

[madires]

It's got a 328p.

Ok, then it's the correct firmware. If you read the Makefile you'll see the enabled features.

[BlueBill]

Will the hex file set the config fuses correctly? I'm also using an Arduino in arduinoisp mode to program a blank ATmega328p, any hint using avrdude would be appreciated.

I'm a PIC programmer, AVR's are alien to me.

[madires]

Will the hex file set the config fuses correctly? I'm also using an Arduino in arduinoisp mode to program a blank ATmega328p, any hint using avrdude would be appreciated.

No, the hex doesn't include fuse settings. But you could use avrdude to set the fuses if required (actually just for a brand new ATmega). If the ATmega already runs a tester firmware you don't need to re-write the fuses.

[BlueBill]

I ran the make file, it created a hex file. The fuse settings are still 00 00 00 so they're not getting set. I'm also not able to program the eeprom.

avrdude -c arduino -p m328p -P /dev/cu.usbmodem1411 -U flash:w:TransistorTester.hex:a -U eeprom:w:TransistorTester.eep:a

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e950f
avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed
         To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "TransistorTester.hex"
avrdude: input file TransistorTester.hex auto detected as Intel Hex
avrdude: writing flash (23832 bytes):

Writing | ################################################## | 100% 3.83s

avrdude: 23832 bytes of flash written
avrdude: verifying flash memory against TransistorTester.hex:
avrdude: load data flash data from input file TransistorTester.hex:
avrdude: input file TransistorTester.hex auto detected as Intel Hex
avrdude: input file TransistorTester.hex contains 23832 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 3.06s

avrdude: verifying ...
avrdude: 23832 bytes of flash verified
avrdude: reading input file "TransistorTester.eep"
avrdude: input file TransistorTester.eep auto detected as Intel Hex
avrdude: writing eeprom (14 bytes):

Writing | ################################################## | 100% 0.06s

avrdude: 14 bytes of eeprom written
avrdude: verifying eeprom memory against TransistorTester.eep:
avrdude: load data eeprom data from input file TransistorTester.eep:
avrdude: input file TransistorTester.eep auto detected as Intel Hex
avrdude: input file TransistorTester.eep contains 14 bytes
avrdude: reading on-chip eeprom data:

Reading | ################################################## | 100% 0.03s

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0000
         0xff != 0x14
avrdude: verification error; content mismatch

avrdude: safemode: Fuses OK (H:00, E:00, L:00)

avrdude done.  Thank you.

Here's the TransistorTester I'm using.

[madires]

I ran the make file, it created a hex file. The fuse settings are still 00 00 00 so they're not getting set. I'm also not able to program the eeprom.

Didn't you use the pre-compiled firmware? Anyway, a few posts ago I explained how to use the Makefile to set the fuses. But since you've got an error while verifying the EEPROM, there's another issue.

[jimmc]

I've got the same (Banggood) version, the original fuse settings were...
L   0xFF
H   0xD9
E   0x04
LB   0x3F

I enabled  the brownout detection using...
(I know that there have been problems reported when using brownout detection but if the power glitches I'd prefer to know and fix it - No problems so far.)
L   0xFF
H   0xD9
E   0x07
LB   0x3C

I used the precompiled .hex & .eep files.

Jim