<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 2006 CES Report: First look at the Mindstorms NXT (Part 1)</title>
	<atom:link href="http://nxtbot.com/blog/2006/01/05/2006-ces-report-first-look-at-the-mindstorms-nxt-part-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://nxtbot.com/blog/2006/01/05/2006-ces-report-first-look-at-the-mindstorms-nxt-part-1/</link>
	<description>Covering the world of consumer and personal robotics</description>
	<lastBuildDate>Wed, 21 Jul 2010 20:10:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: haz</title>
		<link>http://nxtbot.com/blog/2006/01/05/2006-ces-report-first-look-at-the-mindstorms-nxt-part-1/comment-page-2/#comment-999</link>
		<dc:creator>haz</dc:creator>
		<pubDate>Fri, 02 Jun 2006 14:46:14 +0000</pubDate>
		<guid isPermaLink="false">http://nxtbot.com/blog/?p=9#comment-999</guid>
		<description>LEGO you are awesome! I cannot wait as my family are going to the worldwide opening!I have not tried earlier versions so don`t let me down!</description>
		<content:encoded><![CDATA[<p>LEGO you are awesome! I cannot wait as my family are going to the worldwide opening!I have not tried earlier versions so don`t let me down!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Murphy</title>
		<link>http://nxtbot.com/blog/2006/01/05/2006-ces-report-first-look-at-the-mindstorms-nxt-part-1/comment-page-2/#comment-997</link>
		<dc:creator>Michael Murphy</dc:creator>
		<pubDate>Thu, 01 Jun 2006 15:53:11 +0000</pubDate>
		<guid isPermaLink="false">http://nxtbot.com/blog/?p=9#comment-997</guid>
		<description>check out http://bricxcc.sourceforge.net/ They have test release out for NXT. They have a text based language called NBC running on it. Hopefully something like NQC will be next...

Michael</description>
		<content:encoded><![CDATA[<p>check out <a href="http://bricxcc.sourceforge.net/" rel="nofollow">http://bricxcc.sourceforge.net/</a> They have test release out for NXT. They have a text based language called NBC running on it. Hopefully something like NQC will be next&#8230;</p>
<p>Michael</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Irish Boy</title>
		<link>http://nxtbot.com/blog/2006/01/05/2006-ces-report-first-look-at-the-mindstorms-nxt-part-1/comment-page-2/#comment-994</link>
		<dc:creator>Irish Boy</dc:creator>
		<pubDate>Wed, 31 May 2006 17:39:35 +0000</pubDate>
		<guid isPermaLink="false">http://nxtbot.com/blog/?p=9#comment-994</guid>
		<description>I&#039;ve been using NQC to program RCXs (still old school). I&#039;m wondering if anybody knows if NQC still can be used to program the NXT. I&#039;ve been looking around and everything that I&#039;ve read is a software called Robolab, that is claimed to bridge RCX users to NXT. Is there anything that can bridge NQC to NXT?

Thanks.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been using NQC to program RCXs (still old school). I&#8217;m wondering if anybody knows if NQC still can be used to program the NXT. I&#8217;ve been looking around and everything that I&#8217;ve read is a software called Robolab, that is claimed to bridge RCX users to NXT. Is there anything that can bridge NQC to NXT?</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Forbzy</title>
		<link>http://nxtbot.com/blog/2006/01/05/2006-ces-report-first-look-at-the-mindstorms-nxt-part-1/comment-page-2/#comment-951</link>
		<dc:creator>Forbzy</dc:creator>
		<pubDate>Sat, 20 May 2006 08:25:59 +0000</pubDate>
		<guid isPermaLink="false">http://nxtbot.com/blog/?p=9#comment-951</guid>
		<description>Sounds awsome but I don&#039;t like the connection wires (silly telophone things) and the back compatibility issue.


Q: wiil it be possible to have two NXT&#039;s talk to each other?


if not I will stick with an RCX</description>
		<content:encoded><![CDATA[<p>Sounds awsome but I don&#8217;t like the connection wires (silly telophone things) and the back compatibility issue.</p>
<p>Q: wiil it be possible to have two NXT&#8217;s talk to each other?</p>
<p>if not I will stick with an RCX</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David vun Kannon</title>
		<link>http://nxtbot.com/blog/2006/01/05/2006-ces-report-first-look-at-the-mindstorms-nxt-part-1/comment-page-2/#comment-234</link>
		<dc:creator>David vun Kannon</dc:creator>
		<pubDate>Tue, 14 Feb 2006 20:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://nxtbot.com/blog/?p=9#comment-234</guid>
		<description>With all the speculation about the connectors, is it just possible that the picture has been flipped, and that the connectors really are Dec 6c or what ever?</description>
		<content:encoded><![CDATA[<p>With all the speculation about the connectors, is it just possible that the picture has been flipped, and that the connectors really are Dec 6c or what ever?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: luke drale</title>
		<link>http://nxtbot.com/blog/2006/01/05/2006-ces-report-first-look-at-the-mindstorms-nxt-part-1/comment-page-2/#comment-225</link>
		<dc:creator>luke drale</dc:creator>
		<pubDate>Sun, 12 Feb 2006 11:07:45 +0000</pubDate>
		<guid isPermaLink="false">http://nxtbot.com/blog/?p=9#comment-225</guid>
		<description>wow sounds great but i have an rcx, it would be cool if they could interact with each other.</description>
		<content:encoded><![CDATA[<p>wow sounds great but i have an rcx, it would be cool if they could interact with each other.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rale</title>
		<link>http://nxtbot.com/blog/2006/01/05/2006-ces-report-first-look-at-the-mindstorms-nxt-part-1/comment-page-2/#comment-203</link>
		<dc:creator>rale</dc:creator>
		<pubDate>Sun, 05 Feb 2006 21:22:17 +0000</pubDate>
		<guid isPermaLink="false">http://nxtbot.com/blog/?p=9#comment-203</guid>
		<description>How much will NXT cost in Europe</description>
		<content:encoded><![CDATA[<p>How much will NXT cost in Europe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://nxtbot.com/blog/2006/01/05/2006-ces-report-first-look-at-the-mindstorms-nxt-part-1/comment-page-2/#comment-198</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Fri, 03 Feb 2006 03:49:26 +0000</pubDate>
		<guid isPermaLink="false">http://nxtbot.com/blog/?p=9#comment-198</guid>
		<description>Derek Anderson Says: 
January 6th, 2006 at 6:38 am
Any idea why a proprietary 6 conductor modular jack with an offset lock was chosen? One of the reasons that the Mindstorms was so succesful was it’s hackability. Hopefully the connectors/cables will be inexpensively available so that we do not have to chop up existing sensors.
•••
The sensors don&#039;t have their own cables. You plug a cable into the back of the sensor. So, you just have to chop up cables.</description>
		<content:encoded><![CDATA[<p>Derek Anderson Says:<br />
January 6th, 2006 at 6:38 am<br />
Any idea why a proprietary 6 conductor modular jack with an offset lock was chosen? One of the reasons that the Mindstorms was so succesful was it’s hackability. Hopefully the connectors/cables will be inexpensively available so that we do not have to chop up existing sensors.<br />
•••<br />
The sensors don&#8217;t have their own cables. You plug a cable into the back of the sensor. So, you just have to chop up cables.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://nxtbot.com/blog/2006/01/05/2006-ces-report-first-look-at-the-mindstorms-nxt-part-1/comment-page-2/#comment-191</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 02 Feb 2006 00:04:02 +0000</pubDate>
		<guid isPermaLink="false">http://nxtbot.com/blog/?p=9#comment-191</guid>
		<description>Everyone is going all GAGA over this.  Let&#039;s take a more realistic view of it.  This is a very down to earth report...

1) NO backwards compatiblity.  You will need ALL NEW MOTORS &amp; SENSORS.  For people with an investment in the current mindstorms it leaves them out in the cold.  NICE GOING LEGO.  But, I can forgive this.

2) NXT

a)  - too little ram, too little flash.  There is just NO REASON in this day and age to have the device be SO limiting.  You won&#039;t be able to do any meaningful sampling unless connected to another device to dump data so no &quot;long autonomous&quot; missions :^(  WHY?

b)  It looks like they copied the  iPod design.  While  SOME people love the studless design, there&#039;s NO QUESTION that mounting the old RCX was much easier than mounting this thing will be.  I could forgive this, but it WILL be harder for kids to work with.

c) Buttons - when trying to mount this inside robots, the buttons are all clustered around the CENTER of the thing.  At least with the RCX, the buttons were near the edge so you didn&#039;t have to have access to the center of the unit as much.  AGAIN - that &quot;iPod look&quot;.  Some designs won&#039;t be bothered by this, others will!

What they SHOULD have done was to provide remotes (even as an option) that could be KEYED to a specific NXT module (how about setting an 8 or 16 bit code so the RC won&#039;t accidentally control a different one - then these codes could be apportioned out PRIOR to tournaments and teams could set them up ahead of time).  Or, it could be keyed to the serial number of the unit!!!

d) Keeping the limit to 3 outputs - WHY...  No good reason.

e) Keeping the input to only 4 - NOT BAD, considering the motors now
have rotation sensors. 

e) No way to run multiple sensors on a single port... This was one of the unique and innovative soloutions that kids USED TO have in FLL to create robots that would do things that worked well all the time.

f) Looking at closeups of the programming environment, it looks like RIS but instead of vertical programming, horizontal.  Robolab is an EXCELLENT environment.  Using big pictures on the icons &quot;looks pretty&quot;, but doesn&#039;t allow a sufficiently complicated program to fit on a single page easily.  Hopefully this was just a prototype and the real environment will be more Robolab like.

3)  Studless Design.  The previous poster thinks that using liftarms will fix his problem?  WHY?  Liftarms have ALWAYS BEEN AROUND.  They could have been using them all along!  I fail to see how having a new system will help  that.

The FACT that his team did not learn how to PROPERLY brace beam that were stuck together does NOT mean that their new robots will be any better.  I can say with 100% certainty, that beams with studs stuck together and BRACED are MUCH stronger than liftarms pinned together and, it&#039;s easier conceptually for children to understand studded designs.

Our team has built MANY structures of both styles and if teams had a hard time with the beams, building a strong structure with liftarms will be a LOT LOT harder (try it!). 

The question is:  how well will THESE motors be balanced as far as torque output be?  Do they have TRUE speed control, or is it once again, PWM.  As everyone should  know, PWM is NOT speed control at all - an unloaded motor will spin as fast at speed 1 as at speed 7, it all changes when the motors are put under load and the battery voltage changes!  True speed control using a closed loop system would allow robots to go TRULY straight and, it would make it much easier for EVERYONE.  Is this what we want?  If the goal is to make things easy, why not just market a new ROBOT kit every year with building instructions that teams can purchase.  Gone will be the TRUE engineering that comes with understanding the problem and overcoming it, not by having the answers handed to you!  Will there be some issues to deal with - time will tell when we REALLY see what these kits are made of!

4)  Motors - HUGE motors.  I would rather have had SEPARATE rotation sensors and SMALLER motors so that some design tradeoffs and intelligence still had to go into building a robot.  Having motors that are this huge, well, it violates the KISS principle, and it forces decisions onto builders that would be best left to the builder.

5) Sensors - they too look BIG.  And again, the studless design - why???  To &quot;look cool&quot; - sigh.

***********************************************

We have consistently been able to build FLL  robots that score 400 points on the table using the existing parts.  Our robots go straight (less than about 1/2&quot; left to right over a minimum of 4&#039; travel and a return to within 1&quot; of the starting position - I don&#039;t think the NXT will help that!).  Thinking that these new parts will help anyone make a better robot is, well, wishful  thinking.

Watching lego leave their legendary &quot;building block&quot; studded design is sad.  They are abandoning what made them great and, with the incompatibility, will  surely be alienating those who have invested heavily in the current technology.

But, sheik is in, the iPod sells, and it appears that&#039;s what they&#039;re going after.  Maybe I will be proved wrong, but there is no denying some of the facts I have listed above.  I know that in the fall, both RCX and NXT&#039;s will be allowed in FLL, but what about the next year?

What they SHOULD do is to have 2 separate categories to allow teams to compete against similar robots and NOT force teams to spend HUNDREDS  or THOUSANDS of additional dollars to replace their current and still working mindstorms pieces.

Steve</description>
		<content:encoded><![CDATA[<p>Everyone is going all GAGA over this.  Let&#8217;s take a more realistic view of it.  This is a very down to earth report&#8230;</p>
<p>1) NO backwards compatiblity.  You will need ALL NEW MOTORS &amp; SENSORS.  For people with an investment in the current mindstorms it leaves them out in the cold.  NICE GOING LEGO.  But, I can forgive this.</p>
<p>2) NXT</p>
<p>a)  &#8211; too little ram, too little flash.  There is just NO REASON in this day and age to have the device be SO limiting.  You won&#8217;t be able to do any meaningful sampling unless connected to another device to dump data so no &#8220;long autonomous&#8221; missions :^(  WHY?</p>
<p>b)  It looks like they copied the  iPod design.  While  SOME people love the studless design, there&#8217;s NO QUESTION that mounting the old RCX was much easier than mounting this thing will be.  I could forgive this, but it WILL be harder for kids to work with.</p>
<p>c) Buttons &#8211; when trying to mount this inside robots, the buttons are all clustered around the CENTER of the thing.  At least with the RCX, the buttons were near the edge so you didn&#8217;t have to have access to the center of the unit as much.  AGAIN &#8211; that &#8220;iPod look&#8221;.  Some designs won&#8217;t be bothered by this, others will!</p>
<p>What they SHOULD have done was to provide remotes (even as an option) that could be KEYED to a specific NXT module (how about setting an 8 or 16 bit code so the RC won&#8217;t accidentally control a different one &#8211; then these codes could be apportioned out PRIOR to tournaments and teams could set them up ahead of time).  Or, it could be keyed to the serial number of the unit!!!</p>
<p>d) Keeping the limit to 3 outputs &#8211; WHY&#8230;  No good reason.</p>
<p>e) Keeping the input to only 4 &#8211; NOT BAD, considering the motors now<br />
have rotation sensors. </p>
<p>e) No way to run multiple sensors on a single port&#8230; This was one of the unique and innovative soloutions that kids USED TO have in FLL to create robots that would do things that worked well all the time.</p>
<p>f) Looking at closeups of the programming environment, it looks like RIS but instead of vertical programming, horizontal.  Robolab is an EXCELLENT environment.  Using big pictures on the icons &#8220;looks pretty&#8221;, but doesn&#8217;t allow a sufficiently complicated program to fit on a single page easily.  Hopefully this was just a prototype and the real environment will be more Robolab like.</p>
<p>3)  Studless Design.  The previous poster thinks that using liftarms will fix his problem?  WHY?  Liftarms have ALWAYS BEEN AROUND.  They could have been using them all along!  I fail to see how having a new system will help  that.</p>
<p>The FACT that his team did not learn how to PROPERLY brace beam that were stuck together does NOT mean that their new robots will be any better.  I can say with 100% certainty, that beams with studs stuck together and BRACED are MUCH stronger than liftarms pinned together and, it&#8217;s easier conceptually for children to understand studded designs.</p>
<p>Our team has built MANY structures of both styles and if teams had a hard time with the beams, building a strong structure with liftarms will be a LOT LOT harder (try it!). </p>
<p>The question is:  how well will THESE motors be balanced as far as torque output be?  Do they have TRUE speed control, or is it once again, PWM.  As everyone should  know, PWM is NOT speed control at all &#8211; an unloaded motor will spin as fast at speed 1 as at speed 7, it all changes when the motors are put under load and the battery voltage changes!  True speed control using a closed loop system would allow robots to go TRULY straight and, it would make it much easier for EVERYONE.  Is this what we want?  If the goal is to make things easy, why not just market a new ROBOT kit every year with building instructions that teams can purchase.  Gone will be the TRUE engineering that comes with understanding the problem and overcoming it, not by having the answers handed to you!  Will there be some issues to deal with &#8211; time will tell when we REALLY see what these kits are made of!</p>
<p>4)  Motors &#8211; HUGE motors.  I would rather have had SEPARATE rotation sensors and SMALLER motors so that some design tradeoffs and intelligence still had to go into building a robot.  Having motors that are this huge, well, it violates the KISS principle, and it forces decisions onto builders that would be best left to the builder.</p>
<p>5) Sensors &#8211; they too look BIG.  And again, the studless design &#8211; why???  To &#8220;look cool&#8221; &#8211; sigh.</p>
<p>***********************************************</p>
<p>We have consistently been able to build FLL  robots that score 400 points on the table using the existing parts.  Our robots go straight (less than about 1/2&#8243; left to right over a minimum of 4&#8242; travel and a return to within 1&#8243; of the starting position &#8211; I don&#8217;t think the NXT will help that!).  Thinking that these new parts will help anyone make a better robot is, well, wishful  thinking.</p>
<p>Watching lego leave their legendary &#8220;building block&#8221; studded design is sad.  They are abandoning what made them great and, with the incompatibility, will  surely be alienating those who have invested heavily in the current technology.</p>
<p>But, sheik is in, the iPod sells, and it appears that&#8217;s what they&#8217;re going after.  Maybe I will be proved wrong, but there is no denying some of the facts I have listed above.  I know that in the fall, both RCX and NXT&#8217;s will be allowed in FLL, but what about the next year?</p>
<p>What they SHOULD do is to have 2 separate categories to allow teams to compete against similar robots and NOT force teams to spend HUNDREDS  or THOUSANDS of additional dollars to replace their current and still working mindstorms pieces.</p>
<p>Steve</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith A</title>
		<link>http://nxtbot.com/blog/2006/01/05/2006-ces-report-first-look-at-the-mindstorms-nxt-part-1/comment-page-2/#comment-163</link>
		<dc:creator>Keith A</dc:creator>
		<pubDate>Wed, 25 Jan 2006 17:45:29 +0000</pubDate>
		<guid isPermaLink="false">http://nxtbot.com/blog/?p=9#comment-163</guid>
		<description>This is a great step for LEGO.  The two things that really frustrated our Lego League team were the bricks falling apart and the bot drifiting due to unbalanced motors run open-loop.  Using the Technic pieces should fix the first problem and hopefully the new motors will fix the second.

It would be interesting to know more about the motor assemblys themselves.

1) The connection to/from the motors is said to be digital, does that mean that there are uPs in the motors?
2) If there are uPs in the motors, do they do the control loop or does the brick?
3) Is there a way to change the control loop?
4) The FAQ says the servo output is proportional to the velocity of the motor.  Is there any way to get the position (or does it just feed off a single pulse for each revolution?)
5) Someone also mentioned that there are no gears in the kit, but some of the examples look like they would need a good amount of torque -- does this mean that the motor is geared down in the assembly?  The pictures seem to show that there may be room.

Hopefully, when LEGO starts the Developer Program, they will start to make more details known...

Cheers,

Keith</description>
		<content:encoded><![CDATA[<p>This is a great step for LEGO.  The two things that really frustrated our Lego League team were the bricks falling apart and the bot drifiting due to unbalanced motors run open-loop.  Using the Technic pieces should fix the first problem and hopefully the new motors will fix the second.</p>
<p>It would be interesting to know more about the motor assemblys themselves.</p>
<p>1) The connection to/from the motors is said to be digital, does that mean that there are uPs in the motors?<br />
2) If there are uPs in the motors, do they do the control loop or does the brick?<br />
3) Is there a way to change the control loop?<br />
4) The FAQ says the servo output is proportional to the velocity of the motor.  Is there any way to get the position (or does it just feed off a single pulse for each revolution?)<br />
5) Someone also mentioned that there are no gears in the kit, but some of the examples look like they would need a good amount of torque &#8212; does this mean that the motor is geared down in the assembly?  The pictures seem to show that there may be room.</p>
<p>Hopefully, when LEGO starts the Developer Program, they will start to make more details known&#8230;</p>
<p>Cheers,</p>
<p>Keith</p>
]]></content:encoded>
	</item>
</channel>
</rss>
