After building and happily testing my brand new BOT120 using the Programming Editor (the 'bot behaved perfectly) I decided to tinker with Logicator 3.4.2.....
Things continued to work properly until I downloaded the Live ICE debug code. At that point the 'bot would no longer be recognized by Logicator OR Programming Editor.
I tried everything, the hold reset button and download option. Reinstalling the USB drivers for the axe027 cable (on Windows 7 64 bit). The cable COM port was properly being recognized by BOTH programs, but both programs were reporting that there was nothing at the end of the cable! Downloading that code apparently had overwritten the PICAXE BASIC code (and bootloader?) code in the 20X2 chip. (I "bricked" it!) The chip is soldered to the blue "motherboard" and there is no way (for me) to replace it.
After about a day of more wasted effort to revive the little 'bot I decided to give it away as a "push toy" for a small child. He is now happily pushing it on the floor (I think he has already worn the rubber off the wheels!) He has no idea the new "toy" he is playing with is probably the most expensive he will ever own as a child!
One way I could resolve this was to buy a second BOT120 as my cable was good and the place I purchased the 'bot from refused to refund the "bricked" little blue 'bot.... (I messed up and told them the 20X2 was "bricked".)
But I have decided NOT to do that and my tinkering with PICAXE chips is at
the end....
This is my first and last post on this forum and is an absolutely real story that unfortunately happened to me, so if there was another "fix" I will never know about it as I refuse to take back a child's new toy...
The BOT120 is still a fantastic little robot, just don't do what I did...
Things continued to work properly until I downloaded the Live ICE debug code. At that point the 'bot would no longer be recognized by Logicator OR Programming Editor.
I tried everything, the hold reset button and download option. Reinstalling the USB drivers for the axe027 cable (on Windows 7 64 bit). The cable COM port was properly being recognized by BOTH programs, but both programs were reporting that there was nothing at the end of the cable! Downloading that code apparently had overwritten the PICAXE BASIC code (and bootloader?) code in the 20X2 chip. (I "bricked" it!) The chip is soldered to the blue "motherboard" and there is no way (for me) to replace it.
After about a day of more wasted effort to revive the little 'bot I decided to give it away as a "push toy" for a small child. He is now happily pushing it on the floor (I think he has already worn the rubber off the wheels!) He has no idea the new "toy" he is playing with is probably the most expensive he will ever own as a child!
One way I could resolve this was to buy a second BOT120 as my cable was good and the place I purchased the 'bot from refused to refund the "bricked" little blue 'bot.... (I messed up and told them the 20X2 was "bricked".)
But I have decided NOT to do that and my tinkering with PICAXE chips is at
the end....
This is my first and last post on this forum and is an absolutely real story that unfortunately happened to me, so if there was another "fix" I will never know about it as I refuse to take back a child's new toy...
The BOT120 is still a fantastic little robot, just don't do what I did...