Let's Make Robots!

Problems with usb programming cable

Hello, I am having trouble with picaxe USB programming cable (AXE027). I bought it to use on my lappy but it does not work properly. I installed all the drivers, checked everything many times but it still says "hardware not found on COM port" when I try to program the chip.

The picaxe programming editor says that usb cable is "ready for use", also the programming circuit is fine, since it works on serial cable. This makes me confused.

Any ideas?

Comment viewing options

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

The problem seems to lie in the SD21 board. I tried puttin the programming circuit on a breadboard and program the 18m2 with the USB cable. It worked flawlessly.

However, the SD21 built-in programming function is somewhat different and is likely to accept only the direct serial connection. This is the only explanation I can think of, since when a chip is inserted in the SD21 and programmed with a serial cable, there are no problems, whereas I get "hardware not found" when using USB cable.

Thus, thanks for your help, the problem is partially solved.

I would still appreciate any tips on how to make the programming work on SD21 directly using the USB cable. Thanks.

Did you try disabling FIFO buffers for virtual serial port created by usb cable?

Are you programming the 18m2 on a breadboard? Perhaps the chip isn't properly powered up?

The thing is, when I put the serial cable in from my PC then the circuit of 18m2 works well, but when I put the USB cable to the exact same circuit it somehow does not recognise the hardware. :?

does that usb cable have the FTDI chip built-in?   I think the FTDI chip creates another com port for your laptop to use, so when you plug it in or unplug, your laptop should see that happening and it should create a new com port when plugged in, and take it away when you unplug it.   can you see that happening in the Windows Device Manager?  (assuming its Windows).   verify all that without the robot being plugged into the cable.    

and of course you need to change com ports in your editing s/w to use the new com port, different from the serial port which is always there.   is there an Auto setting on the com port selection in the editor?

by the way, congrats on your recent accomplishments.

Yeah, the FTDI is built-in. But I am using the created com port.

As it was said before, the connection seems to be established well, but the picaxe 18m2 refuses to be programmed, while there is no problem with 28x1.

Thanks ;)

Being able to program one chip and not the other makes me feel it is not a hardware problem.

The Picaxe Programming Editor needs to see which chip it is working with.

You can hit View - Options and on the Mode tab, you will see which picaxe the Programming Editor is currently set for and if it is wrong, change it there.  Another way would be simply to enter a first line to the programs that identifies the chip it will connect to. That will tell the Programming Editor that you have switched chips.

#picaxe 18M2 ; should be entered as the first command line of any 18M2 programs.

#picaxe 28X1 ; should be entered as the first command line of the 28x1 programs.

 

Hope that helped.

Dan M

 

Is the chip brand new or there already a program in it? I'm sure that you have tried this but to make sure: did you try starting program upload and resetting the chip? What else I was going to suggest... hmmm... ah, I would try to explicitly define the chip in your program with #picaxe 18m2 preprocessor command.

what is Prog editor version?

The newest one (5.3.3). You think I should try downgrading the software?