- Home
- Product Categories
- PICAXE
- SparkFun USB Programmer for PICAXE
SparkFun USB Programmer for PICAXE
The PICAXE USB programmer allows PICAXE micros to be programmed from any platform (Windows and Linux). The programmer uses the FT232R and will show up on your computer as a new COM port. Under windows - you'll need to install FTDI drivers but it's really easy!
This board is effectively the same thing (once you add the miniUSB cable and 3.5mm audio cable) as the PICAXE USB Programming Cable. The difference is this board has two on-board LEDs to show the serial data (TX and RX) being passed back and forth. Why buy this board? Because blinky things are better.
SparkFun USB Programmer for PICAXE Product Help and Resources
Core Skill: Programming
If a board needs code or communicates somehow, you're going to need to know how to program or interface with it. The programming skill is all about communication and code.
Skill Level: Competent - The toolchain for programming is a bit more complex and will examples may not be explicitly provided for you. You will be required to have a fundamental knowledge of programming and be required to provide your own code. You may need to modify existing libraries or code to work with your specific hardware. Sensor and hardware interfaces will be SPI or I2C.
See all skill levels
Core Skill: Electrical Prototyping
If it requires power, you need to know how much, what all the pins do, and how to hook it up. You may need to reference datasheets, schematics, and know the ins and outs of electronics.
Skill Level: Noob - You don't need to reference a datasheet, but you will need to know basic power requirements.
See all skill levels
Comments
Looking for answers to technical questions?
We welcome your comments and suggestions below. However, if you are looking for solutions to technical questions please see our Technical Assistance page.
Customer Reviews
No reviews yet.
"Why buy this board? Because blinky things are better."
Why do you even need to say that? Every person looking at this site knows that already :)
I'm surprised at the amount of problems people are having, but then maybe I was just lucky. I got this working successfully on Windows XP Media Center Edition, Windows 7, Ubuntu 9.10 and Puppy 5.2.5. Make sure to download and install the drivers yourself before plugging the cable in.
If you just can't get it working, try uninstalling the drivers, running CCleaner and re-installing the drivers. Then plug it in. I have used this programmer successfully with the 08M, 14M and 20X2 (firmware versions C.0, C.1 and C.2).
Thank you SparkFun!!1!
I have ordered mine and will receive this upcoming week (08/05/13). The issues seem to be Windows XP/Vista/7/8 and all Macs. Fortunately I use Ubuntu 13.04 and will be able to let the linux crowd know whether it works or not. I don't suspect I will have any issues as I plan on flashing the FT232R to work with PICAXE right out of the box. Also I will be desoldering the Audio Jack and substituting it for a more appropriate header. For more info on the Headers swap, refer to my previous post mentioned below. Hope this helps any of you out in your buying decision.
The comments here are not hugely encouraging. Has anyone had success with this gizmo on a Mac w/ MacAXEpad?
I just purchased one of these and received it yesterday 4/1/13. I am running on a MacBook Pro with Mountain Lion (10.8.3) and FTDI kernel extension 2.2.18. I was able to get this to work with a PicAxe 08M2 and AxePad 1.5.0.
I had to solder a jumper wire (from pin to pin) on the FTDI chip to connect RTS to CTS (I didn't have to connect DSR to DTR in order to get it to work, but I did anyway for my final solution.) I eventually found this hint somewhere on the web, so thanks to that poster. It would be nice if this board gets rev'ed to have some pads or holes to connect RTS to CTS and DSR to DTR for the Mac users. It worked fine without modification on my Windows XP side. I'm thinking that the AxePad SW doesn't configure handshake on the port properly or something.
I also had to bring up my VM with windows XP and run FTDI's FT_Prog to program the FTDI chip to properly drive the Tx/Rx LEDs - they weren't configured properly when I received it and were constantly on (SparkFun may want to investigate.) I have programmed my PicAxe several times after making these modifications.
You did what? How? Why wasn't I warned about this? Those are tiny pins. By the way, THANKS. This really helped me.
Thanks! I ended up going with the expensive cable instead to avoid the headaches (I hope...).
Blink. Blink. Blink. Blinky Better! Its Scientifical! :P This looks great. Thank you SF for the cheaper board. I am using for a Science Fair experiment, and looks like it is going to work great!
what type of PICAXE, how many pins?
I think it can be any...
Quick question: The boards that I use my Picaxes in have the recommended download circuit, which consist of 1 10k and 1 22k resistors. These will not interphere with this programmer, will they? Thanks, Andres
Is it possible to use this to provide power your PICAXE project with the USB as the power source? Also, perhaps I'm totally missing something-- Couldn't the TX and RX go straight from the FT232R to the PICAXE eliminating the need for the 3.5mm audio jack?
This is what I am really wanting to know. I looked at the schematic they have and my thinking is just make a cable/dongle with 5V/GND/Tx/Rx so basically 4 wires, and rig them up to a USB cord. Essentially it's the same thing. I'm still going to get the board but remove that audio jack and swap for headers or something. There's a via on the board so it might require putting them in two chunks. My thinking is to take a 6-female header across it to bridge that gap with only using one cable/device. You'd have an extra pin. From the looks of it an extra pin/slot won't interact or mess with the board in any way.
In any case, it's worth considering because this board is really nice but that 3.5mm audio jack is just horrible looking and really is an extra thing I'll have to buy; not something I'm interested in regardless of the price. Extra crab on my desk is extra crab, whether it's $10 dollars or 10 cents makes no difference.
Should I work this out I will post it.
I have one of those for my PICAXE but I was wondering if I can rewire it to program my ATmega328p chips.
I'm having problems also. Using either iBook G4 or MacBook Pro, it doesn't work. Tried with homemade Picaxe board and board from Picaxe, doesn't work and so purchased a AXE027 USB cable and it worked on both boards. Didn't matter whether it was an old driver (the one downloaded from the Picaxe website) or the most current website (FTDI website). Sparkfun needs to get this sorted out.
Why is VCCIO tied to 3.3v? On the official USB PICAXE cable, it is tied to 5v.
Is it a mistake in the schematic? Is it a design mistake? Is it better to use 3.3v IO levels?
I have a 3.3v SFE "FTDI Basic"; can I use that to program PICAXEs? Do I need to worry about the fact that TTL UART, and RS232 use opposite logic levels?
I installed the FDTI drivers on both my Macintosh (10.5) and Vista machines. This adapter works fine on the Vista machine, but it doesn't work at all on the Mac. The MacAxePad can find the chip, but it can't program to it.
Can't get this to work under either XP or Vista. I've uninstalled it in XP, but it allways wants to automaticly install when I hook it up, even when removing the drivers and dll's in system 32.
How about using CCleaner to clean up any other files that may be hanging around on your system? It's saved me more than once.
I got one of these this week, and I love it, two important tips to point out if it doesn't work right out of the box
1. Make sure you solder together your starter kit or PCB properly, it will report "hardware not found" if any pins on the chip don't connect properly, and double check the program/run jumper is soldered properly.
2. I made this device operate properly under Ubuntu and XP Pro, please refer back to tip one before chasing USB ports, drivers and other PC related issues if you get "hardware not found on USBxxxx" type errors.
P.S. It's good to be Evil
great little programmer. it didnt work at first but once i reflashed the FTDI (got from sparkfun support) it starting working like a dream. i haven't had any problems since with any of my PicAxes (08M,14M,18x,40X2).
Worked great. Drivers were easily available. I used the executable driver installer on my Windows 7 machine and the cable programmed fine but, the little lights both stay on continually. No blinky. :(
Works fine with 08M chips and Windows XP
Try swapping the TX & RX leads if it does not seem to work and the chip input pin is always 2.7V using the PICAXE port test. More info http://forum.sparkfun.com/viewtopic.php?p=91939#91939
BTW: Would be better if the stereo plug was a male rather than female plug for use with PICAXE breadboard adaptor, or include the breadboard adaptor circuit and header pins on this board.
kewakl: _Works. Windows Vista 32 Home Premium.
**I did NOT let Windows automatically install the drivers **
Used the VCP driver here.
Picaxe Programming Editor(PE) 5.2.7
PE had no problem detecting or programming the Picaxe firmware for
28x1 fw A.6
28x2 fw B.0
I have a few other Picaxe chips. When I build the programming circuit for them, I will report back with success/failure._
Works (detecting and programming) for
14m fw 9.A
20x2 fw C.0
I have some 08m chips
will have to check with this DL breakout and report back.
Works. Windows Vista 32 Home Premium.
**I did NOT let Windows automatically install the drivers **
Used the VCP driver here.
Picaxe Programming Editor(PE) 5.2.7
PE had no problem detecting or programming the Picaxe firmware for
28x1 fw A.6
28x2 fw B.0
I have a few other Picaxe chips. When I build the programming circuit for them, I will report back with success/failure.
stay away from this. tried it on 3 separate computers and still won't work. 1st one is window 7 RC, recongized driver automatically, both the serial converter and virtual com port is showing up fine, but when time comes to reprogram, logicator/basic program keep saying can't find hardware. 2nd one is window 7 RTM, have to manually install driver from FTDI, seems ok from device manager, but again, downloading is no go. Last tried it on a window xp sp3. Installed FTDI driver, device manager shows it's ok, still doesn't work. Save some headache and go with the authentic AXE027 cable.
I agree, stay away. It seems it works for some people and not for others.Tried on a XP and Visa computer, both serial and virtual com show up, but it won't recognise the Picaxe project board. Can't tell you the amount of frustration I put into this thing. Worse than that, Sparkfun never responded to an e-mail I sent them about it. I will get the authentic AXE027, but from Robot Shop. I won't deal with Sparkfun again.
Well this device can talk with my Picaxe 28x1 but can't program it. seems to be a flaw with the 28x1 chip... I am able to use the macaxe program to have the Assembled 28-pin standard project board report the version of chip to the computer but I when I try to progam it fails. I had to get the old serial port out to finish up progaming... Not overly happy with Picaxe at this time...
NATE
I'm having similar problems. It seems to communicate just fine, reporting the firmware version of the picaxe, but downloading any programs is a no go. I'm very disappointed but open to the possibility that it may be something else I'm doing wrong. I have posted in the forum if anyone has any ideas.
I just received my AXE027 usb cable and it works like a charm. I'm using a MacBook Pro (13") with a breadboarded programming circuit for a picaxe08M. Of course, I wish I had just ordered the AXE027 to begin with. :-)
It'd be nice if SparkFun moved to the micro-usb standard. More robust and will be the new standard of the future, with MiniUSB being deprecated.
While many cellphone device manufacturers are making micro-b the new 'standard' the main purpose is to make devices thinner, rather than for any real convenience. This is also to be the new cellphone standard, so you don't need 4 cables for 4 different makes of cellphone, just one. as this board has no need to be thinner or shoved into a cellphone, i very much support its use of mini-b, especially given i have who knows hwo many mini-b cables laying around.
Good feedback, but that's like asking the US to change all their power cords from 2-prong to 3-prong. Is microUSB all that much better for the general electrical device? SparkFun will change! Change will happen. But it's going to take a long time.
TBH, I've yet to see a MicroUSB device, cord, or socket in the wild. I'd think that the MiniUSB as used here is sturdier and more resistant to wear or breakage from (ab)use.
There really isn't a reason to move th MicroUSB, as the connector fits on this board, and fits rather nicely. Now, if it were a USB-B connection, then I might advocate moving to MiniUSB; however, each standard USB plug serves a purpose, and I really don't think that having a smaller plug would be of any benefit whatsoever.
MicroB is sturdier than MiniB and is rated for many, many more insertion/removal cycles. It'll also be the standard for charging cell-phones in the future, so we'll see much more of it.
The Kindle uses the Micro-B, so perhaps you've seen it there...
I have MicroUSB in my BlackBerry and it is rather fragile than sturdy. Anyways, does the size matter so much?
"...any platform (Windows and Linux)"? How about Mac?
Yes, the board will work under Mac OSX. That's the great thing about FTDI - they support most platforms (Windows, Linux, Mac). But I'm not sure if the PICAXE software runs on Mac? Oh - yea, it looks like the do have some software for Mac:
http://www.rev-ed.co.uk/picaxe/software.htm