Hello all.<div>Thanks for all the support with this project.</div><div>At Tony's suggestion, I downgraded the XO-1 to build 883 (11.3.0), and the the We Do works fine in TurtleBots.</div><div> </div><div>Walter shared his new We Do plug in, which worked fine with Turtle Art 160.</div> <div> </div><div>Thanks. Gerald <div class="gmail_quote">On Sat, Oct 6, 2012 at 2:18 PM, Walter Bender <<a href="mailto:walter.bender@gmail.com" target="_blank">walter.bender@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sat, Oct 6, 2012 at 2:08 PM, Dr. Gerald Ardito <<a href="mailto:gerald.ardito@gmail.com">gerald.ardito@gmail.com</a>> wrote: > Walter, > <div class="im">> I have been testing it out this afternoon. It works really well. > I only have one We Do here, so I can't test out if it sees different > devices. > > There is one quirky thing. When the script is running a motor, the Stop icon > disappears. Then, if you use ctrl-s to stop the script, the blocks > disappear. </div>You could just keep a motor=0 block around... I suppose I could auto-stop the motor when the program stops executing, but I think that might limit the utility somewhat. (The Stop Button is for the Turtle Art program, not the WeDo motor.) <div class="im"> > > And a question, how do you reverse the direction of the motor? </div>Should reverse with a negative number. enjoy. -walter <div class="HOEnZb"><div class="h5"> > Thanks. > Gerald > > > On Sat, Oct 6, 2012 at 11:46 AM, Walter Bender <<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a>> > wrote: >> >> On Sat, Oct 6, 2012 at 1:27 AM, Alan Jhonn Aguiar Schwyn >> <<a href="mailto:alanjas@hotmail.com">alanjas@hotmail.com</a>> wrote: >> > I think that you cannot check what sensor is connected.. >> > Butia have hotplug and show instantly that a sensor is connect. >> > Lego not have that, and the only check possible: get a value, if no >> > gives >> > errors, maybe >> > there are a sensor of that type connected.. >> > >> >>The usual approach would be to add a device input to the blocks... >> >>device 1, device 2, device 3 >> > >> > That can works, but I don't like it taking into consideration that you >> > have >> > put the port >> > where each sensor/motor is connected. >> > >> > I think in a special block that sets the brick that you want to use. >> > For example: >> > - you have 2 bricks connected >> > -if you want to: read color sensor from brick 1 in port 1 >> > -turn motor in port b of brcik 2 with power 100 >> > >> > The code will be: >> > >> > select brick (1) >> > read sensor (color, port 1) >> > select brcik (2) >> > turn motor (port b, 100) >> > >> > See that all the blocks no have changes, only uses the "select brick" to >> > set >> > in the system, which >> > brick get the next functions. >> > The important of this change: when you have only 1 brick, the code no >> > have >> > changes! >> > >> > Opinions? >> > >> > Regards! >> > >> > Alan >> > >> > ________________________________ >> > From: <a href="mailto:gerald.ardito@gmail.com">gerald.ardito@gmail.com</a> >> > Date: Fri, 5 Oct 2012 14:45:48 -0400 >> > To: <a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a> >> > CC: <a href="mailto:alanjas@hotmail.com">alanjas@hotmail.com</a>; <a href="mailto:iaep@lists.sugarlabs.org">iaep@lists.sugarlabs.org</a>; >> > <a href="mailto:support-gang@laptop.org">support-gang@laptop.org</a> >> > >> > Subject: Re: [IAEP] Turtle Blocks question >> > >> > Walter, >> > Agreed. >> > I am happy to continuing working with you on this. >> > Gerald >> > >> > On Fri, Oct 5, 2012 at 2:36 PM, Walter Bender <<a href="mailto:walter.bender@gmail.com">walter.bender@gmail.com</a>> >> > wrote: >> > >> > On Fri, Oct 5, 2012 at 2:30 PM, Dr. Gerald Ardito >> > <<a href="mailto:gerald.ardito@gmail.com">gerald.ardito@gmail.com</a>> wrote: >> >> Walter, >> > >> >> if we are crossing devices? >> > >> > Egon Spengler: Don't cross the streams. >> > >> > The usual approach would be to add a device input to the blocks... >> > device 1, device 2, device 3... But also, I should do a better job of >> > autodetecting which sensors are available. The whole thing should be >> > more dynamic. >> > >> > -walter >> > >> > -- >> > Walter Bender >> > Sugar Labs >> > <a href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a> >> > >> > >> > >> > _______________________________________________ IAEP -- It's An >> > Education >> > Project (not a laptop project!) <a href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a> >> > <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a> >> >> Attached is a BETA version of a new WeDo plugin that supports multiple >> devices. It follows a schema similar to what Alan proposes above. I >> only have one device, so it is not tested for multiple devices, >> however, it seems to work for one device and includes a new feature >> which tests for devices before each start, rather than just at launch, >> so devices and be plugged in and unplugged without having to restart >> Turtle Art. >> >> Feedback greatly appreciated. >> >> regards. >> >> -walter >> >> -- >> Walter Bender >> Sugar Labs >> <a href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a> > > -- Walter Bender Sugar Labs <a href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a> </div></div></blockquote></div> </div>