Got the Bot Board II and Atom Pro 28 yesterday and tried out a quick sample program (the 3-sound test from the Bot Board tutorual)…
and was amazed it took so LONG to compile and write the program out to the board. I’m using the board as received, powered as it will
be when it’ll be hooked up to the SSC-32 (7.2V 220maH LiPo and all VL=VS jumpers in place). Board is connected to PC via USB>Serial
interface that came with the Parallax BOE I used to run.
My past experience has been with the Parallax IDE, BOE and BS2 and uploading programs was very fast. Is it this IDE that’s slow,
the baud rate, the sheer size difference of the Atom processor???
I am hoping that Nathan(AcidTech) of BasicMicro will answer this.
I have not studied the Basic Stamp in detail to know if you are simply downloading your program or if it also downloads all of the supporting functions (interpreter as well). The BAP downloads everything. Which is nice as if they update things in the library your chip is updated as well. It also allows you to use the c compiler and have complete control of the processor.
It often depends on what serial connection you are using to download to the Atom Pro, as well as system drivers and settings. As a side note, on a different processor board (Axon2) they found that it takes about 3 times longer to do downloads to their board if you are running XP with SP3 than it does on SP2 or Vista or Windows7… Now back on track.
What chip set is in the USB to serial converter? If it is FTDI, make sure latency is set to 1 in the advanced driver settings.
As for why some 2006 posts are listed before yours, they are sticky posts (note the different icon).
The fact is the Atom is a superior product in speed and performance, and takes more resources to program than the stamp. That being said there are things that you can do to speed it up. If your USB/virtual serial port driver has receive and transmit buffers make sure they are the same. I.e. both are 14 instead of one being 16 and one being 14. As Kurt said if you have latency in the driver, I doubt it but if you do, make it the minimum.
It should take no more than 30 seconds to program after compileing has finished. If it is taking longer your USB to serial adapter(if oyu are using one) may have the latency set very high. If it’san FTDI based USB to serial adapter you need to open Devivce manager, right click on the FTDI serial port, click properties, then port settings,then advanced. Change Latency to 1. After closing all the windows restart Studio if it was already open. No programming should be fairly quick.
If you think 30 seconds is to long(and thats only on a large program) then I guess it’s just too slow for you. Sorry.
Changed the Latency to 1 (this IS a FTDI driver) and the baud from 9600 to 115200 - couldn’t find anywhere in either Device Manager OR BMS where
I could change Receive and Transfer buffers…still get LESS THAN 30 SECONDS for the whole upload process!
Thanks again!
Now if I can just get a sequence to work on the SSC…that’s some weird coding. No wonder you charge $40 for the Visual Sequencer.
I blew out the firmware (and reloaded ) twice now! About ready to give up and get the sequencer.
Yep, sequencer is your friend. I am not very good at it, but I have played around some. Also a little while ago, I was working on making the phoenix code run on an Arc32. As part of that I wanted to run sequences that Zenta created using PEP. I could not use SEQ to do that (at least not yet). So I created my own downloader that could use the output from PEP or an EEPROM file and download it, using a VB application and code running on the Arc32. While I was at it I wrote a BAP28 program that allowed me to also use the VB app and the Bap28 to write sequences out to the SSC-32’s EEPROM. More detail up on the thread: viewtopic.php?f=8&t=6042&start=34
hii every1
i got hexapod robot CH3-R with ssc-32 and botboard II pro 28
how i can write a program to make the robot move by specific degrees and speed ?!
hope to share with me an example to learn from !
thank u
The BotBoard ideally communicates with the SSC-32 using serial commands of the following format: #1P1500S500"
You can read more about these commands in the SSC-32 user guide under “Command Types and Groups” lynxmotion.com/images/html/build136.htm