<div class="gmail_quote">On Fri, Sep 28, 2012 at 4:39 AM, Caryl Bigenho <span dir="ltr"><<a href="mailto:cbigenho@hotmail.com" target="_blank">cbigenho@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">
<br><br><div><div></div>> Date: Thu, 27 Sep 2012 16:24:56 -0400<br>> From: <a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a><br>> To: <a href="mailto:xxopxe@gmail.com" target="_blank">xxopxe@gmail.com</a><br>
> CC: <a href="mailto:butia-list@fing.edu.uy" target="_blank">butia-list@fing.edu.uy</a>; <a href="mailto:yamaplos@gmail.com" target="_blank">yamaplos@gmail.com</a>; <a href="mailto:iaep@lists.sugarlabs.org" target="_blank">iaep@lists.sugarlabs.org</a>; <a href="mailto:christoph.derndorfer@gmail.com" target="_blank">christoph.derndorfer@gmail.com</a><br>
> Subject: Re: [IAEP] [Butia-list] XO robotics<div class="im"><br>> <br>> Hi,<br>> <br>> I would love to see you at the SF meeting to explain Butia to that audience.</div></div><div><br></div><div>+1 Caryl</div>
</div></div></blockquote><div><br></div><div>FWIW: I've been in touch with Andres Aguirre and the Butía team regarding such a session as I had heard that one of them had submitted a proposal to the summit organizers. Last I heard (but I still have to follow up with them to confirm) is that it looks like they unfortunately will have to participate via Skype as the cost of the trip is simply too high (flight alone costs ~$1400 according to Kayak). They have however sent me a full parts list and we were discussing maybe shipping a set of all the components to San Francisco so we could assemble a Butia during the summit (or Sugar Camp). Again, all of this was just under discussion and I've yet to follow up with them to figure out all the details.</div>
<div><br></div><div>Oh, last but not least: Tony suggested that I take some time to translate the Spanish setup instructions and associated documentation to English. So this is certainly an item that's on my to-do list for the Sugar Camp in San Francisco. At the same time I think that if we get around to building ourselves a butia while we're in town we could also document the process with a video and tons of photos. :-)</div>
<div><br></div><div>Cheers,</div><div>Christoph</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir="ltr"><div><div><div class="h5">> <br>
> It was my understanding in Montevideo, that the robot is controlled <br>> directly from Turtle Art. For me, the really great thing you have done <br>> is to strap the laptop on the robot platform. This is not for cute <br>
> pictures, it is really exciting for the student to see the robot obeying <br>> his or her instructions (right or wrong). The fact that the laptop is <br>> riding on the robot vehicle means that its movement is not limited by an <br>
> umbilical cord.<br>> <br>> As Yama states, we really need (for me, in English) a parts list and set <br>> of instructions for building the robot so that it can be done by any <br>> deployment. I had hoped that such a session would be conducted in SF as <br>
> I would dearly love to be able to set up a robot at the Saint Jacob <br>> school in Kigali in December. Naturally, we will also need some lesson <br>> plans for use of the robot to further the mandated curriculum in Science <br>
> (and mathematics).<br>> <br>> My example would be to have the student program the robot to approach a <br>> wall as closely as possible without touching it. This would involve some <br>> understanding of the ratio of the wheel diameter to its circumference, <br>
> the number of degrees the wheel advances for each forward step, and <br>> whole lot of other interesting concepts. For example, such a contest <br>> could lead to the issue of feedback; how to use a sensor so the robot <br>
> knows when it is close. Should this be visual (camera) or acoustic or <br>> the bending of a wire or ....<br>> <br>> Tony<br>> <br>> On 09/27/2012 02:08 PM, Jorge wrote:<br>> > On 27/09/12 13:35, Yama Ploskonka wrote:> 1) I wouldn't say better...<br>
> > rather, complementary, and certainly<br>> > > cheaper. Visiting the Butiá pages, the only picture I see showing an MCU<br>> > > <a href="http://www.fing.edu.uy/inco/proyectos/butia/images/pistaButia.jpg" target="_blank">http://www.fing.edu.uy/inco/proyectos/butia/images/pistaButia.jpg</a> is<br>
> > > showing an Arduino. Add a motor driver, and we are well above $30, plus<br>> > > shipping. The USBButiá board is maybe cheaper IF done in quantity by<br>> > > experts (then add labor).<br>
> ><br>> > Besides the microcontroller the USBButiá board provides standard<br>> > connectors for attaching sensors. It allows autodetecting what sensor<br>> > you connected and were (something like the NXT brick, but with a wider<br>
> > spectrum of attacheable stuff, more connectors, easier to hack, and<br>> > plug&play).<br>> ><br>> > We sidestepped the motor driver issue using digital servos.<br>> ><br>> > > MSP430 + (L293D OR some darlington array) can be "free" if you get them<br>
> > > as samples from TI, or less than $5 when purchased, /plus shipping/, the<br>> > > old bane. the advantage of using a darlington driver is that then you<br>> > > may use plain DC motors, which can be free if lucky with old electronic<br>
> > > parts (beautiful gear system available in old CDROM drives)<br>> > ><br>> > > 2) yop - the XO "drives" the vehicle with the MSP430 option also. Now, I<br>> > > put quote marks as I have no idea - yet - on how to send data direct<br>
> > > realtime from the XO to the robot, bypassing the MCU. What seems to be<br>> > > happening is that Butiá depends on sending code/program to the Arduino,<br>> > > and the the 'duino does the brains of the robot.<br>
> ><br>> > Nop, the control runs fully on the XO. MCU only interfaces<br>> > sensors&motors and supports the plug&play functionality. No user logic<br>> > runs on the MCU.<br>> > The user programs on the XO access sensors/actuators connected the MCU<br>
> > and whatever the XO provides (mic, cam, accelerometer if there is one)<br>> > transparently. The most frequent programming environment is TurtleArte<br>> > (kisds already know it), but there are also Python and Lua environments<br>
> > for when the problem or the user outgrows Turtle Art.<br>> ><br>> > In my opinion, what MCU is used is not actually important. What is<br>> > important is the programming environment, how it interfaces with<br>
> > whatever your robot offers, and the mechanism you provide for adapting<br>> > your robot for solving different problems.<br>> ><br>> > Jorge<br>> > .<br>> ><br>> <br></div></div>
<div class="im">> _______________________________________________<br>> IAEP -- It's An Education Project (not a laptop project!)<br>> <a href="mailto:IAEP@lists.sugarlabs.org" target="_blank">IAEP@lists.sugarlabs.org</a><br>
> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a><br></div></div> </div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Christoph Derndorfer<div><br></div><div><div>volunteer, OLPC (Austria) [<a href="http://www.olpc.at/" target="_blank">www.olpc.at</a>]<br><div>editor, OLPC News [<a href="http://www.olpcnews.com/" target="_blank">www.olpcnews.com</a>]<br>
contributor, TechnikBasteln [<a href="http://www.technikbasteln.net/" target="_blank">www.technikbasteln.net</a>]</div></div><div><br></div><div>e-mail: <a href="mailto:christoph@derndorfer.eu" target="_blank">christoph@derndorfer.eu</a></div>
</div><br>