I posted a while ago about trying to get the basic atom pro working with the ps2 controller. After searching the forums more thoroughly, I found that it’s necessary to move the connections to pins 12-15 and add a pullup resistor. However, I’m still having trouble connecting to terminal 1 whenever I run the program. No matter what I do, it always says “unable to connect to comport” even after it compiles the program. I’ve tried the latest two atom pro IDEs with no luck.
I’m using a regular serial cable. I’m not sure if there’s any cross-wired pins because I bought it at staples, but I’m not sure if this is the problem because I can program the thing just fine.
Are you writing a program, or loading a prewritten program?
The Atom uses the following IDE’s… (old 16bit) 2.2.1.1 or (new 32bit)5.3.0.0
The Atom Pro uses the following IDE’s… (old 16bit) 7.2.0.6 or (new 32bit)8.0.0.0
If you are using a prewritten program you must make sure it is compatible with the IDE you are using. In other words you must use the same IDE as the original program was written in.
I’m using the atom pro, and I’ve tried using the 7.2.0.6 and the 8.0.0.0. The program compiles fine onto the atom, and it runs just fine (as far as I can tell…I’ve tried a basic blinking LED test program, and it works), but I can’t connect to terminal 1, and I can’t figure out why. Would that be caused by the program, or the connection to the stamp<->computer?
I’ve tried all of the various pre-made programs, correcting those that need it so they compile without errors.
Do you select the correct comport from the dropdown list in the terminal window? Also you can’t be connected to a comport that is currently being used to program the module.
I was running the thing in debug mode, because that was the only way it would seem to run for some reason. But when you said that you can’t connect to a comport when you’re programming it, I tried to just hit “program” and it worked…then I connected to terminal 1 and it started firing off the right numbers!
Shoulda mentioned that I was running the thing in debug mode grumbles.
hehe, I’m thrilled it’s working now