where in the Arbotix AVR code is it talking to the XBEE serial port?

[stephen.hazel]

Ok, I'm making slow progress on my bluetoothed android phone to bluetooth bee'd arbotix board.
Almost got the android app to pair to another and sending back and forth some text.
Then I try android=>bluetooth bee=>arbotix.


I went browsing through arbotix-0014.zip and couldn't find WHERE in the heck it's talking to the
X BEE's serial port.
Can somebody point that out to me, please? Like a .c filename and path within that arbotix-0014 dir?

From what I'm gathering, ya have one little arduino app on the AVR and it doesn't change much if at all.
It's loading servo specs=>flash=>XBEE serial port=>other PC connected XBEE=>pythonSerial_WhateverYaCallIt=>python GUI, right?

I see where it's doing the AX12 serial bus. But not where it's messing with the XBEE one??

thanks for any pointers,

...Steve

[Tyberius]

Check the Commander library. It's inside the Robocontroller library (which I believe is going to be merged with the Arbotix library soon).

[lnxfergy]

An XBEE is just a serial device -- it's the default Serial on the arbotix. If you're using the PyPose sketch as a reference, it makes calls directly to Serial.read/write() in the sketch. If you're using a NUKE-exported sketch, it uses the Commander library (part of http://code.google.com/p/robocontroller/).

-Fergs

[stephen.hazel]

Ok, I got that Commander thingy.
But =it= seems to use some HardwareSerial.h and probably some other .cpp files...

Where do I come across THOSE babies?

So where's the top level of all this arduino arbotix stuff?
I found this arbotix/core/arbotix/main.cpp
But how do I know what all tentacles are included in this thing?

Thanks for your help tho - i REALLY appreciate it.
I think a droided arbotix would be PRETTY dang cool...

[stephen.hazel]

ohhhhhhhh k. Those little .pde files are actually c++.
I blew em all away lookin only for cpp

This dang arduino business will probably drive me insane.
Seems like in order to make cpp easier, they've made cpp harder (well, messier at least)

Ok, I'm good - thanks mucho.

[Tyberius]

Basically a lot of the integrated functions of the arduino IDE draw upon core 'arduino library' dependencies. Easier on the front end, but messier on the back end when you go digging through code.