Ok, just got sensors and servos for my robot. I am using a picaxe 28x1 . Here’s the thing, I know there is a bug in the picaxe a.4 firmware and it may cause servo problems. When I do the servo command (servo 0,150 etc.) the servo does not do anything. When I plug in the battery pack (I am using two power sources) the servo buzzes a little bit thats all. I assume that this is because of the buggy firmware. When researching this bug on LMR I discovered that some people got their servo to work by using servo 7,150 when the servo was plugged into digital input 0. How ever I am using pin 7 with the motors. So what do you guys think, do i have the bug? If so is there anyway to get my servo to work without having to go through the trouble getting a replacement?
grounded
do the two batteries have common ground?
?
do you mean are they both connected to ground on the chip? if so yes
What version of firmware do you have?
If it is 4, try manually moving the servo anti-clockwise while unpowered. When connected and servo command issued does the servo move clockwise? Does my pulseout alternative work? see https://www.robotshop.com/letsmakerobots/node/3026
Oh and you could try outputting a servo command to 0 to see if it fixes the servo on 7
just tried it
Well I tried the anti-clockwise servo thing and the pulsout alternative , and still the servo doesn’t do anything. 
I don’t know if it makes a difference, but the 28 x1 is fairly new. I just got it for christmas
firmware
I’m not quite sure what firmware is installed. Oh, and when the batteries are in and I plug in the servo it rotates one way until it hits the end then buzzes.
The version of the firmware
If it doesn’t say when you compile/download then there is an option to find out what version of firmware is installed in the IDE that Rev-Ed provide for Windows. Is there an options button where you select the chip type. If so is there a Firmware button in there? If not then you’ll have to look yourself (perhaps Google can help you) or wait for a Windows user to help.
uh oh…
I found the firmware button and it says it is firmware version 3… that can’t be good
it’s not
all workarounds aside: get a replacement from Santa’s supplier.
Ok
Will do. For the replacement do I ask for just a new picaxe 28x1 chip?
i had the exact same
i had the exact same problem, solved it with new batteries and this code:
servo 0,125
pause 1000
servo 0,075
pause 1000
end
there might be a mistake in that code but you get the idea,
tels the servo to go somewere and thene a pause, for some reason the servo comand doesnt work by it self.
Hope that helped.
thanks…
Well thanks for trying, but it didn’t work. Does version a.3 have same bug as a.4?
I didn’t know there was a
I didn’t know there was a problem with A.3 firmware - I wouldn’t jump to any conclusions yet.
Did you get the servo upgrade pack and install the resistor array? If not have you removed the darlington drivers and used a resistor instead?
Are you sure that you are connecting the servo correctly?
Are you sure the power supply is connected correctly?
ok
Well here you go,
I am almost completely positive I have the second power supply and servo wired correctly. This is because when I take a battery out of the second power supply and then put it back in I get a small little movement/twitch from the servo.
I removed the darlington, but no resistor yet.
Ant: I do not have any real code, just doing things like
servo 0, 175
pause 1000
servo 0,200
pause 1000
and trying to get a response from the servo
sorry, but thank you
Alright, sorry guys I had another stupid mistake stopping the servo from working. Put a 15k resistor in input 0 where the darlington use to be and got the servo to work perfectly.
thanks!
I thought I shouldn’t make another post
Hi, instead of making another post I figured I may as well ask my question here:
Just wired sharp Ir sensor to my robot and connected the remaining analogue inputs to v. However when I do this,
main:
readadc 1,b1
debug
goto main
When I put my hand in front of the sensor and move it outwards I only get a slight if no change (255 to 254) in the debug menu. Any ideas?
well I have the analogue
well I have the analogue sensor, the right type. I am pretty sure it is connected to the right things.
woops.
Ant, looks like you saved my robot again
I was saying readadc 1,b1 but really the first pins are 0 so saying readadc 0,b1 worked.
Thanks