$20 LCR ESR Transistor checker project

[madires]

Just a brief one in the m-firmware's readme file. It's an ever changing story Maybe someone would like to create and maintain a comparison chart.

[mauroh]

Hi Markus,
    in this days I was a little busy, but I prepared the setup to verify the servo checker function.
As you can see in the attached pictures, I'm comparing the behaviour of the super cheap servo tester with the new function you implemented on the m firmware.

As you suspected I have the same issue also with the PWM and Square Wave function that are also implemented differently from the 1.25m (this was working fine with this 2 functions).

Changing  Step <<= Enc.Velocity; with Step = Enc.Velocity;  It helps a bit during the sweep mode, but It looks like there is something wrong in the evaluation of the rotation speed and no matter how I rotate slow or fast the encoder, it jumps a lot.
In manual mode each step of the encoder it change the "position" of 0.01ms and it is painful to use...

Mauro

[madires]

What type of rotary encoder do you got? With detents? How many Gray code pulses per detent or step?

[indman]

Hi!
If it is interesting to someone, then I added the schematic diagram for TC-1 clone.
On the diagram not all elements are designated and there can be small errors, excuse!
https://yadi.sk/d/wtrds6Nt3EaQXY
Several versions of the schematic diagram for Fish8840(Box) are also added
https://yadi.sk/d/DM5MA--L3E48as
All thanks to the participant of the Russian-speaking forum mr.sleska!

[mauroh]

Hi Markus,
    my encoder is the standard one that comes with the Banggood DIY Kit:
http://www.banggood.com/DIY-M12864-Graphics-Version-Transistor-Tester-Kit-LCR-ESR-PWM-With-Case-p-997023.html?rmmds=detail-top-buytogether
It has detents, with 20 steps/turn.

I connected a logic analizer to the PD1 and PD3 where the encoder is connected/configured and attached you can see the pulses I get for each step during a full rotation and for a single step.
As you can see for each step I got one pulse, than  the firmware send something to the display.

Just as a comparison I attached also the same acquisition for a full rotation of the encoder scrolling the menu on the k firmware.

Mauro

[madires]

Mauro, could you please add a few lines of code to Servo_Check() in extras.c for debugging. Look for

Code: [Select]

      Flag &= ~UPDATE_PULSE;            /* clear flag */
    }

    /* PWM frequency/period */

and insert between "Flag &= ~UPDATE_PULSE;" and the curly bracket:

Code: [Select]

      Flag &= ~UPDATE_PULSE;            /* clear flag */
LCD_Space();
DisplayValue(Enc.Velocity, 0 , 0);
    }

That should display the rotary encoder's turning speed of the previous turn (1-7) behind the pulse length (or sweep time). 1 is slow and 7 is very fast. Which speed values do you get?

[mateusps]

The tester tries to tell you that it measures 5V on probe pin #1 while it expects 0V. Possibly caused by some short.

Finally found the short

https://youtu.be/4AN6rInz5s8?t=269

[Tech_JA]

Great job! 

[mauroh]

Hey mateusps,
     you should add some music to that video with a dramatic voice over and you will get a mini thriller, at least it wasn't the butler Mr.Bad Soder 
 Nice job finding the short 


Markus:
   I added the Enc.Velocity and also the displayed Velocity jumps a lot. I get
1    moving the encoder one step at a time and waiting a second before the next step 
5-6 moving the encoder really slowly without pause

I also noticed that it jumps more going on one direction and a bit less in the other.

If you need I'll try to put toghether a video but not at the mateusps level

Mauro

[madires]

Ok, so we know now that there's an issue with the detection of the turning speed with that particular rotary encoder. What have you set for ENCODER_PULSES in config.h?

[mauroh]

#define ENCODER_PULSES   2

I tryed 1 but than it jumps scrolling the main menu.

Mauro

[madires]

Could you please also try ENCODER_PULSES 4?

[asadullah mir]

Hi Guys,   
I just found this thread and am very keen to build a tester for my lab. I have read past the first 15 pages and I am not sure which is the latest version correct to build. At 133 pages it is a long thread.  Can someone point me in the right direction, please?.  The full thread is too long to go through and I will probably miss the correct info/design.
I am familiar with MCS-51 I claim to be a pro there but know nothing about the AVR processor.
I have a  "stamp board" with an "ATmega128" chip mounted on it and all the pins brought out including the  AVR programming header I also have a programmer for this board.
I will design/etch my own PCB for the circuitry ( using the stamp as a daughter board no sweat.

Will the Atmega128 at 16 MHz do? Is the 128  compatible with the 328 etc?

Thanks for any help.

73

[madires]

The ATmega 128 isn't supported by the firmware yet and is has only a 2.56V bandgap reference. Please use a 328 or 664/1284. For the current circuit please see Karl-Heinz' documentation at https://github.com/svn2github/transistortester/blob/master/Doku/trunk/pdftex/english/ttester.pdf .

[asadullah mir]

That is disappointing. I have no use for these two boards I have had for a while.
I wonder if some worthwhile project exists to make good use of.
I have worked with the 8051 family for a long time and (Zilog earlier)  now am in the process of switching most of my work to Cortex stm32F10x family, as well as switching to C.
I know nothing about the AVR family though I understand they are good stuff.

[asadullah mir]

Ok, the first link may not be the same thing, but the second one sure sounds like it. I think. It's in German, but here's google's translation effort:

http://translate.google.ca/translate?sl=auto&tl=en&js=n&prev=_t&hl=en&ie=UTF-8&eotf=1&u=http%3A%2F%2Fwww.mikrocontroller.net%2Farticles%2FAVR-Transistortester

I built one last week, the fun part was persuading an Arduino to do the job of an AVR programmer

Have you posted the code using the  arduino which I am hoping is based on the cortex? Would love to make a working copy.

[Willem52]

Sorry, it makes no sense to me to quote and reply to a message of 4 years ago.
It seems a lot better to me to try to send a PM to the original poster.

[vidmo]

So I just wanted to brag, that I changed LCD in T4 version (that I broke before, because of that ridicules ribbon cable...) I covered it in my new blog. I had to change (and rebuild) firmware, because image was mirrored, but now it's fine.

[indman]

Hi, madires! I have a question on use of IR detector fixed.
In the config_328.h file there are such settings
* IR detector/decoder
 * - fixed module
 */#define IR_PORT PORTC/*port data register */
#define IR_DDR DDRC/*port data direction register */
#define IR_PIN PINC/*port input pins register */
#define IR_DATA PC6/*data signal */

I understand that it is settings for the ATMega324/644 processor?
If it is possible, then explain in more detail how to set up ports in these lines?

[madires]

The option for the fixed IR receiver module uses a dedicated pin instead of the probes/test pins. For example, if the IR module's data output would be connected to PB2, you would have to set:

Code: [Select]

#define IR_PORT          PORTB     /* port data register */
#define IR_DDR           DDRB      /* port data direction register */
#define IR_PIN           PINB      /* port input pins register */
#define IR_DATA          PB2       /* data signal */

The ATmega type doesn't matter. It could be also a 328. PC6 is just a placeholder. BTW, if someone got the clone with the fixed IR receiver module, I'd like to know which MCU pin is used for the data line.

[indman]

Madires, thanks for the response! I already gave the reference to the diagram of a clone TC-1 in the message #3303, i hope that it will help you

[hapless]

So it's PD3 then (that's where encoder often goes)  .

I don't have one of those, but just wanted to point out that, from the videos of the way it works, it looks to me like they are using an interrupt to jump to the IR measurement screen when signal is detected. Not a bad idea if they are able to reliably screen out false triggers.

[madires]

No, different pin assignments for ATmega 328 and 324/644/1284

[hapless]

Isn't PD3 still INT1 on 324?

If you're talking about encoder placement, I was talking about 328. If you were to use that same pin, it would have to be in put where encoders go now in kits.

[madires]

Yes, INT1 is PD3 on the 328 and 324/644/1284. But neither k nor m-firmware use interrupts for the rotary encoder. And the IR detector/decoder in the m-firmware also doesn't use a pin change interrupt. So they can use any I/O pins.