Regarding the servo check function, AFAIK the center position should be for a pulse width of 1.5ms, the lowest and highest value varies for each servo.
The cheap servo checker available on ebay has 3 functions:
- center
It provide a signal with 1.5ms pulse width every 20ms. This is very useful setting up the RC models
- manual
Rotating the knob it provide the signal depending by the position of the knob from 1 to 2 ms
- Auto
It sweep between the min and max pulse width continuously from 1 to 2 ms
See, I am a fast learner!
Cheers for your assistance, take it easy, I'll come back in about 10 hours or so. Sleep time now... zzzzzz
I tried searching this thread, it's a NIGHTMARE to find what I need!
I should remind everybody, if you are responding to a post immediately before (or even a ¡few before) yours, there is no need to 'Quote' their entire post. This makes the forum more difficult to read. Especially, when a post three pages long and full of pictures, gets quoted over and over again. Please use 'Reply' instead. Also if you're responding to just one particular sentence, you can trim out everything else.
(I realize that one of the problems is that the reply button is only at the top and bottom of the page. On other forums I've seen it conveniently placed at the end of each post. I think I might mention it to the mods.)
So it seems I was on the right track?
I did a test "make" from the folder named above, and also saw the "107%" error for the main .hex
I think you are on the right track.
Where did you get your toolchain? What is your compiler version?
The oversized hex files has been brought up a few times. It's always caused by one of two problems. Either the wrong format (Intel) is being specified to AVRDUDE. I don't think that's your case since you're using a makefile. Yes, the other cause is using the wrong version of compiler (AVR-GCC). The solution that people suggested was either using an older version, or using the one included with the Arduino IDE (free one, not AVR Studio). I have been using the latest build (6.2.0) without problem. Since you are familiar with Linux, try cloning the 'gcc-avr' repository.
Here's a link with details.
Okay, I managed to find a suitable "make.exe" copy @ ftp://ftp.equation.com/make/32/make.exe - I put it on my Desktop for the moment, to test it, and added that location to my PATH - it now builds fine, at only 93.2% program space
Mr hapless, master of LCR firmwares, [...]
Heh, that's very kind of you, but there are people around here who are much more deserving of the title...[...] I used your "TransistorTester (as above, but no flipping).zip" on my device which was originally on the "Mtester" firmware, and it works a treat... but one thing I have noticed is this - the characters seem to be shifted too far to the right by 0.5-1 characters - do you know how I would resolve this? The typeface is nice and bold - maybe a little TOO bold, at the expense of the chars flowing off the right hand side of the LCD.
The fonts are monospaced, so it's the width of the characters that matters, otherwise bold ones can be the same width as the thin ones. It's more of a matter of taste. As madires pointed out, the problem is with the offset that was deliberately used so that the exact same issue would be fixed for devices that have their screens rotated 180 degrees. I'm attaching a build that should fix this for you, but it doesn't use the exact same Makefile, so please let me know if I accidentally broke something.
Note: I made some (very few) slight changes to the output of the code. They are not even worth mentioning, but don't be surprised if you see that "Version1.13" now has a space in it or that "4 * ->|-" shows as "4 x ->|-".[...]
i have brushed it with IPA, top&bottom side of it, and have some progress after that.
[...]
maybe my tester is still not work normally?
I'm very happy that it's finally starting to work, but you need to need to give it at least one more go with water (try to dry it as quickly as possible!) and then alcohol. Clean very thoroughly. You'll probably also want to clean between the pins of the MCU, too (just in case). Just make sure it's completely dry before powering up the board, and, of course, be gentle enough not to damage anything while you're at it.
@vrishuvorlaz I wasn't picking on you. It's just something I noticed in general, and you provided a good opportunity to bring it up, since you were complaining about being able to find information. Quoting something that was said on a previous page, as you just did, is justified because that's exactly what it's for. But don't defend laziness or blame somebody else, because it's inexcusable. There's no bug. If you are replying to the most recent post, then the reply button is right under your nose. No scrolling required. I'm not pedantic, I simply think we should be courteous to all the other users of the forum who might need help, like you. I don't think think this needs further explaining.
EDIT: Do you see the new 'Reply' button there next to 'Quote'. Dave liked the idea and added it.
Anyway a better servo tester should support analog and digital servo:
50Hz analog servo signal period 20ms
125Hz digital for steering gear signal period 8ms
250Hz digital servo signal period 4ms
Also the Auto sweep is important because you can test the speed responce of the servo, changing the sweep time.
Thankfully the maker of my LCR-T4 tester had the good sense to mark the ISP port for programming - the legend is UNDER the LCD, you just need to de-solder the LCD backlight LED and lift... and you see it..
Thankfully the maker of my LCR-T4 tester had the good sense to mark the ISP port for programming - the legend is UNDER the LCD, you just need to de-solder the LCD backlight LED and lift... and you see it..What is even nicer is that he made it so a standard socket can be attached to the back. Note that the labels you see on the top side are actually mirror image of a standard 6 pin ISP connector
Graham
Basically just breakout boards for an ATmega644/1284.
I have built several testers based on the Atmega328, and want to expand it.
I would like to incorporate the various adapters, ( opto, options etc)
Is there up to date docs on this?
It's a "IC Transistor Tester Detect Meter Maintenance Digital led Tester MOS PNP NPN "
It tests 74xx and 4xxx chips.
This is great!!!
I have few spare servo and ESC from my RC helicopters/multicopters secondary hobby ready to test the new firmware
Yep, the firmware measures the voltage at PC4 and if it's around 2.5V it assumes it's the external voltage reference. The pull-up resistor makes sure that PC4 is outside the expected voltage range, and 100k or 220k would be fine also. The m-firmware behaves the same way, but HW_REF25 (config.h) controls if the code get's included or not.
What is the procedure if not using the voltage reference, but relay extension is used? No pull-up resistor?
I'm having some trouble getting my AY-AT tester to work, it keeps displaying the message "Probing" "Battery? 1: 4996v" (using the Trendy 1.25 firmware) - The original chinese firmware was similar, but stuck in the 'short probes!' message. I've tried with another atmega328 but the result is the same
Any clues on how to fix this?