------- WWW.SYSTRONIX.COM ----------
Real embedded Java and much more
+1-801-534-1017 Salt Lake City, USA
>As I previously mentioned, I pulled down a copy of the trackbot code.
>I should mention that I am running Trackbots with SunSPOT brains.
>Looking at the build scripts for TrackBot Common V2 raised a few
>about building the demo code:
>1. It looks like I need the aJile 4.X libraries/tools in order to
>build the demo code.
> Is this correct?
Here are some answers:
aJile runtime is *not* needed unless you want to build that option --
which for SPOT you don't.
> [I have older 3.16.9 versions of the libraries and tools for
>JStamp and JStik (from
> my JCX days) but I never upgraded to 4.X.]
> So I need to purchase updated libraries and tools?
>2. It looks like the code has two parts: code that goes on the SPOT,
> code that goes on the Trackbot.
There is only code on the SPOT which you build, deploy, and execute.
TrackBot code per se consists only of the TrackBot node runtimes
which is is written in C and loaded with the AVR programmer, and is
not at all any part of the application code Java build for SPOT.
> Does this mean that in order to create a running application, I
> 1. Create SPOT code
> 2. Create Trackbot code
> 3. Download code to the SPOT
> 4. Download code to the Trackbot? (using the AVR programmer?)
>I expect I'm confused about a couple of things....
These are reasonable questions. So apparently we need some better use
instructions. Actually there is a file in the project root:
SPOTDemoInstructions.txt which I am now updating. Please look at it
and also there will be new app notes here:
>Last week I upgraded my SPOTs to the latest blue release,
>but backed down to 080609 after reading your AppNotes.
>After reading the updated demo instructions, I had no problems
>deploying the demo code to the SPOT.
>When I ran the demos, the sensors seemed to be working as expected.
>However, the behavior of the robot in Avoid and Wander modes was not
>what I expected.
>The robot moves in starts, and stops, and sometimes reverses direction
>for no reason
This is TrackBot Common V2?
You can see the sensor state on the SPOT RGB LEDs - that should tell
you why the bot is avoiding something. I'm working on a better app
note of this code...
>I can see. I do know that the signal between a SPOT basestation in my
>a roving SPOT in the hallway only lasts for about 15 feet, nowhere
>near the expected 100 meters;
>so I wouldn't be surprised if the Trackbot is being confused by weird
>But I'd like to be sure.
The Common V2 doesn't need a base station... how does this work together?
The radio transmit power is programmable, and I think the default is
low output to 1) save battery and 2) not interfere unduly with other
SPOTs nearby such as in a typical lab. You can crank it up and should
get 100 meters line of sight if there is not a lot of other 2.4 GHz
signal in the area.