Let's Make Robots!

PIC-AIM

Remote controlled, extremely precise (yeah, right!) 2-axis laser death ray

This started out as a top secret destruction weapon to be placed on the moon with plans of taking the world hostage, in order to make a trillion dollars... (...mmm... I think I´ve seen this movie before...)... and it ended up being a laser pointer mounted on a two axis jig, made out of Futaba servos. It is controlled by a hacked, 22-year-old IBM analogue joystick.   
Now back to reality: This really started as a comment by user chench (http://letsmakerobots.com/user/5049) to a forum post of mine, (http://letsmakerobots.com/node/27588) suggesting an analogue gauge. The neuron that was handling that idea collided with another one that was taking its time to decide what to do with a spare laser pointer I have. Presto-pronto an idea was born. 
A hacked 2 axis analogue joystick going straight to 2 ADC pins. That value mathematically translated to servo values (thank´s to Chench´s formula) and the laser pointer cable-tied to the horn. Let´s not forget the bracket I improvised to attach on servo to the other.
I am using a Picaxe 18X and here´s the code:
init: 
servo 4,75
servo 5,75
main:
readadc 1,b1
readadc 0,b0
let b2=b0/2+75
let b3=b1/2+75
servopos 4,b2
servopos 5,b3
goto main
The problem I´m having (take a look at the video) is that of servo jitter. As fas as I can tell, it is caused by the instability of the ADC reading coming from the joystick, even when I don´t touch it. I have gone though many posts in the Picaxe forum trying to find a solution, with no real luck. The best I can think of, is writing code to round up the values. According to the debug screen, my instability is smaller than value 5 (inside of the 0-255 range).
 Any ideas, community? H-E-L-P!

UPDATE (July 25th, 2011)
Finally I have been able to integrate the new 3A power supply to the old experiment and the jitter is more under control than before. See secong video near the top. Next step is to tie down all unused inputs and change the pots in the joystick as suggested by many "colleagues" in the forum.
Thanks to all!

UPDATE (July 26th, 2011)
At this point, and after today´s experiments, I believe it is safe to say that I have tried out every suggestion posted here and on the Picaxe forum. "We" have managed to reduce the jitter an awful lot, but it is still there. Take a look at the third video uploaded. Here´s an unofficial list of everything I´ve tried, hoping that it will be useful to someone else who decides to go this route.
  • I´ve run the servos and the logic from the same power supply and from different ones. The last one I´ve used for the servos alone was 3A properly regulated.
  • I have made sure that, if using 2 PS, that the GNDs were common.
  • I have switched the pots from the hacked joystick from 100KΩ to brand new and noiseless 10KΩ.
  • I have tied all unused inputs from the Picaxe down via 10KΩ resistors.
  • I have tried to implement filtering in the code.
...and none of this has truly solved the problem.
The jitter has diminished considerably... but it is still there. I don´t think it is going to get any better than this, so I´ll move on to other things.

I want to express my most heartfelt gratitude to all those who took the time to read the thread and chime in ideas.


UPDATE (Sep 4th, 2011)
Down in the commentary section, Dan M. (among others) suggested trying servopos commands on their own, isolating them from the readadc commands. I has taken me a while, but finally I got around to trying it out. This is in the context of another experiment. However all the boards and servos are exactly the same as the PIC-AIM project, with the exception of the joystick. 
The idea come to me while watching one of Chris the Carpenter´s recent videos, a quick demo on a GGBot. That particular bot, while asleep, has the PING))) sensor looking straight down. When you wake it up, the turret tilts up for distance sensing in autonomous mode. I don´t know if that is only for personality sake or not. However, I thought that it would look cool to have just one (Sharp, in this case) sensor to determine distance and to make sure that there is floor ahead of the robot. You can watch what I have come up with in the last video uploaded.
With this experiment, it becomes obvious that the hardware is not the problem. I can also discard the joystick as a source of jitter, because I´ve changed all the pots in it. Conclusion: I don´t think my approach can be built like I wanted, at least not without the addition of a servo controller, like LordGG suggested in the comments. 

UPDATE (Sep 17th, 2011)
For some reason this project of Rick100 came to mind today. I reread his post and downloaded his code for the Picaxe 08M and found what could be the solution to my problem. I quote a bit of his code:
'couldnt use servo and servopos commands because of jitter
'used pulseout for servo pulses and pause commands adjusted with oscope to get close on timing
I will try to adapt his approach for my project tonight.
I´ll keep you guys posted.
Andrés

UPDATE (Mar 18th, 2012)
SUCCESS, finally! I admit this has taken longer than anticipated, but you see, in between I started a company and got married, so I´m sure everyone will understand. The first video from the top shows the laser death ray in action.
I guess the only thing left now, is to figure out a way to get it to the moon so I can fulfil my plan of taking the world hostage, in order to make a trillion dollars...
Andrés

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Do you know the value of the pots in the joystick . I think the IBM PC joysticks had 100K pots and the Picaxe needs approximately 10k or lower  . I once changed the pots in an IBM joystick to 5K so I could use it with a pic .  You could also moniter the voltage going into the adc with a voltmeter to see if it's stable . Some of those joysticks had cheap pots and are just noisey .

Hey Rick,

You are indeed right. They are 100K. For the life of me, I don´t see how you can know that by memory. BIG thumbs up! I don´t see how that can be bad for the Pic, however. If you could explain further, I would be grateful.

About the values: using debug, I´ve learnt that the values fluctuate as much as +/- 5 at all times. Maybe changing the pots (regardless of their value) is the way to go. I remember punishing them back in the day... :D

Thanks a lot for your input!

Andrés

 I am not an analog guru so I can't explain in detail the affect of the higher pot resistance . I know it will take longer to charge the internal hold capaciter through the higher resistance . I assume it would also result in less accuracy .

 You might also try running your program with the servos disconnected and observing the analog values . This will tell you if the current draw and noise from the servos are affecting the readings . If I'm having trouble with a circuit , especially on a breadboard , I always put a volt meter on the power rails while its running . A lot of problems on breadboards are caused by bad connections .

Good luck .

Rick

I have tried to filter out some of the jitter with the code, like so:

init:
servo 4,75
servo 5,75
symbol TOLERANC = b13
toleranc = 9

main:
readadc 0,b0
readadc 1,b1
let b12=b0+toleranc
let b11=b0-toleranc
let b10=b1+toleranc
let b9=b1-toleranc
readadc 0,b2
readadc 1,b3
if b2>=b0 and b2<=b12 then main
if b2<=b0 and b2>=b11 then main
if b3>=b1 and b3<=b10 then main
if b3<=b1 and b3>=b9 then main
let b4=b0/2+75
let b5=b1/2+75
servopos 4,b4
servopos 5,b5
goto main

No luck.

I've only been using the PICAXE for a short while (maybe a week) so don't put to much into my suggestion....

Turn on 'debug' by adding the word 'debug' into your main loop.  Load/run the program and take a look at the b0 and b1 values.  My guess is that they are changing even without you touching the joystick.  These value changes in b0 and b1 (as you certainly know) get transfered into the b2 and b3 servopos statement.

A suggestion:  Set up a loop (a do while or do until depending on how like setting these things up) that helps take away the jittering of the b0 and b1 value.  Basically, read b0 and b1 but only jump to the respective servopos rountine is the b0 and b1 amount changes, say 2%.

I haven't used the MIN and MAX commands, but they maybe could help.

Good luck.

MIN and MAX are on page 23 of the 'picaxe manual2'.  Maybe not useful to you.

Found them, thanks! Was looking in the wrong place (insert ashamed smilie here). You are right. I don´t think they are a solution to my particular problem. However, I am always happy to learn new tricks!

Voltar,

I have researched all commands suggested by you. In the example below, I have achieved with 4 if-thens, the same as with 2 do-loop while. The Max and Min commands are still a mystery to me. They do not appear in the manual, you see. Are they proper commands?

Thanks,

Andrés  

Actually, Max and Min appear first on page 22 of the manual part 2, and then on page 23 in the middle there is a Heading "Max and Min".  I don't use them much, but when I do use them, is when I do maths for something like a servo position and do not want it below 75 or above 225 (or 245 to 265 for some servos)

Hey Dan M.

That is a good use of the MAX and MIN commands that I haven´t thought of. Thanks for sharing.

BTW sorry to hear about your younger brother. I did not mean to be disrespectful.

Andrés