My CH3-R robot worked fine when i plugged it to a DB9 port on my desktop. But when i try to plug it into my laptop with a USB-Serial adapter, the ATOM compiler bugs: When i click on the “Compile” it does it fine. But when i click on the “program” button there are 2 errors possible: either it starts writing then i get “Error connecting to ATOM”, either it finishes assembling the file and i get “Available Program Memory on Device exceeded”.
I already got the first error message on the first computer, but charging the battery pack resolved it. But this method doesn’t seem to do anything when i connect the robot to the laptop.
I don’t understand the second error message, because when i program the same file on the old computer it works…
But on the first message: Error connecting to ATOM.
There have been many threads on this one. Not all USB-Serial adapters are created equal. You might do a search on the forum here on this. It would help to know which one you are using. There are suggestions in different threads on changing the timeouts and the like.
On the second error message, it would help to know additional information. Like are you running the same version of the IDEs on both machines? Which one? Do you have them both configured the same way for which type of chip? Example: BasicAtom28? On the machine that it compiles OK, how big are you?
It might be the USB serial adaptor. I have seen this problem before from other people and it always seems to be the usb adaptor that has the problem. I’m not sure which type of adaptor is known to be good. Perhaps some here will respond with a better answer than I can provide.
I’m using this usb-to-serial adapter: bafo.com/p-psc-usb.asp (the last one on the page). I bought that one because they had it in stock. I’ll have a look at what other people have, and change if i have to.
The desktop and the laptop both run on windows XP SP2, and the settings in the ATOM program are the default ones (exept for the transfer speed that i changed to 115.2kps).
The robot has a Mini Atom Bot Board with a BASIC Atom 28. I don’t think it’s useful to say that there is a SSC-32 board and that i don’t use a PS2 controller.
I’m going to go search the forum for the usb-to-serial problem.
As others have said what version of the IDE are you using on both computers. The different IDEs have different syntax on some commands which could be causing your second error. Posting the code that is causing the error is the fastest way to get an answer on that. On the USB to Serial adapter try adjusting the rest hold time in the advanced comport settings for the IDE. Also if you have a USB to Serial adapter that has a latency adjustment in it’s settings set the latency as low as possible.
I’m using AtomMirco IDE IDE 02.2.1.1 (that is the 2002 copyright version) on both computers.
I didn’t find where i could set the latency, but i did change the com-port speed to 115200bps (it was slower before, now both the Atom program and the serial converter are set to the same speed, but it doesn’t seem to work any better)
I also noticed that all the files that i have written myself never got the second error message. It only happens with one file: The default one that i modified! (but it works fine on the desktop!)
Hello. I tried a few things: first powered up the USB hub, then i plugged the usb-to-serial device directly into the computer. But none of them solved my problem.
Now i downloaded and installed the latest MBAtom IDE compiler: 05.3.1.0. I noticed that in the settings we can check for hardware. I clicked on it and it didn’t find anything plugged in any coms. Its weird because when i click on “program”, the bot board beeps like it always has when i clicked on the “program” button (which probably means that it did find the hardware!). Any Advices?
thanks
If Iunderstood one of your earlier posts you have a BAFO USB to serial. It is one that looks like a big DB9 serial connector where you plug a USB cable into it and then into your computer. I believe that this is the same one I am running on my machine right now. (Although this machine is running VISTA) Earlier I did have it working as well on my portable running XP sp2.
If you connect it now to your desktop machine does it still work properly? That would rule out things like bad battery, board died, etc.
I believe that you meant to say, that you first tried plugging your USB serial adapter into a powered USB hub that you had connected to your PC. I also assume that this USB hub had it’s own power supply. For example I am using the LINKSYS HI Speed 4 port USB hub.
If you go into the device manager of your machine, do you find a comm port associated with your adapter. If so what drivers is it using? Mine is using ser2pl.sys from prolific technology version 2.0.2.1. Have you ever used any other USB to serial adapters on this machine? I had a problem on one machine that I had used some different adapters. One turned out to be a prolific knockoff one and the software interfered with using the BAFO adapter. On this portable I had much better luck with the FTDI based adapter.
When your run the new IDE, try brining up the setup dialog and click on the advanced comm settings. Try different values for the Reset Hold time. Mine is set to 25. I have not run it lately on the ATOM as I mainly work/play using the PRO. It sounds like when you click on the check for hardware that it is at least able to reset your board so it may be somewhat there…
I can’t test the serial converter on the old PC because i moved, and the old computer stayed over there. How ever i will try it on the new desktop we purchased (Parkard bell running under vista, and doesn’t have any serial ports either )
This is the first time i use a usb-to-serial converter, and no i have no other devices that have serial connectors.
I checked the device manager. It finds the serial converter plugged in com8, and “This device is working properly”. The driver: USBSER34.SYS, the provider is WCH, version 2.10 and it is not digitaly signed.
I tried updating the driver to the one you are using but i get an error message: this driver doen’t contain information about your hardware.
Forgot to mention: my USB hug is a Targus ACH63EU, hi speed 4 connectors. It is powered by a second USB A that we plug into the computer.
Now my usb-to-serial conerter is plugged directly into the computer (bypassing the hub)
This looks very much like the adapter I am using on my Dell desktop machine (it does not have any serial ports…).
If you look at the other side of the adapter it has a sticker with a serial number.
It also has another stickr with a couple of symbols followed by 3902B568
I still wonder if you are getting enough power from either your hub or your portable. As best I can tell this adapter gets its power from 1 or 2 usb connections to the host computer. So if the usb adapters on your portable does not provide enough power, then you may not have much luck. At least I know that the BAFO adapter did not work on my portable comptuer (Dell running XP SP2), until I ran it with a wall wart powered USB HUB. I have not tried it on my new desktop without this HUB yet, but it might work as the USB adapter can provide power to the devices…
Not sure what else I can tell you, maybe someone else has some other suggestions.
I have the exact same device, though I am using it with MacOS X. The driver you want is for the PL2303. Prolific, the company that makes the chip is very good with making their drivers available for a multitude of platforms, including MacOS X, Linux, MS-Windows and sometimes BSD. The download page is here:
Prolific (com tw): /eng/downloads.asp?ID=31
BTW If you are using Vista then they indicate “Prolific will not be providing Vista drivers for end-user. Please contact the vendor of your cable for Vista driver availability”. I suspect this may have something to do with Vista requiring signed drivers.
If you are using MacOS X, then there is another driver available for the same chipset, but in open source form (GPL license):
sourceforge project: osx-pl2303
PS I will update the URLs when I have been on the site for more than 1 day. In the meantime you will have to do some leg work yourself - sorry.