<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>buena respuesta! ;-)<br><br><div><div id="SkyDrivePlaceholder"></div>> Date: Thu, 27 Sep 2012 15:08:08 -0300<br>> From: xxopxe@gmail.com<br>> To: butia-list@fing.edu.uy<br>> CC: iaep@lists.sugarlabs.org; yamaplos@gmail.com; tony_anderson@usa.net<br>> Subject: Re: [Butia-list] [IAEP] XO robotics<br>> <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>> > http://www.fing.edu.uy/inco/proyectos/butia/images/pistaButia.jpg 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>> Butia-list site list<br>> Butia-list@fing.edu.uy<br>> https://www.fing.edu.uy/mailman/listinfo/butia-list<br></div> </div></body>
</html>