Recognising BotBoarduino with Basic Micro Studio

Lynxmotion Electronics & Software
1

G’day,

I recently purchased the Lynxmotion A-Pod and have been constructing it over the last 2 days. I’ve just connected the BotBoarduino board, and powered it up. I tried to program it as per these instructions, but no avail:

lynxmotion.com/images/html/build157.htm

Every time I press “Find Processor”, it scans COM9, then returns “Could not find processor.”. I have taken the following troubleshooting steps to try to get it working:

I’m fairly positive the board is powered correctly. I’ve tried both onboard, and USB powered modes with no avail. In both modes the power LED is on, and there appears to be an example program running on the board (the LEDs are flashing, and the speaker chirps every 1.5-2 seconds).

I originally had FTDI drivers already installed on the computer because of my work with the Propeller Chip - and that seemed to automatically recognise the FTDI chip on the Botboarduino, and install the drivers for it. This created a serial com port, on port 9. I thought that this might be the issue, so I (successfully) replaced my drivers with the ones provided by Lynxmotion. Still no avail.

I’ve also tried fiddling with the Reset Hold Time value as per the instructions. I tried both changing it up and down (from 10 to 1000) - still no avail.

I’m out of ideas, anyone else care to pitch in some thoughts?

Thanks,

John

2

Hi John,

The build157.htm instructions are for the Bot Board with Basic Atom Pro 28 chip. Do you already have these parts? We’ve discontinued the Basic Atom Pro 28 a few months ago because the supplier doesn’t make them anymore.

If you already have a BotBoarduino board, you can follow these instructions upload the CH3R code:

This code however doesn’t give control of the head or tail of the A-Pod. If you make changes to the code that allow that, we’d be interested in seeing them!

Hope this helps,

3

Thanks for the help, I’ve successfully compiled and uploaded the code now! I had one or two issues, but I was able to mitigate them without too many issues.