VADCFLL-L Archives

First Lego League in Virginia and DC


Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Patrick & Cari Norton <[log in to unmask]>
Reply To:
Patrick & Cari Norton <[log in to unmask]>
Mon, 26 Oct 2009 09:58:07 -0400
text/plain (37 kB) , text/html (7 kB) , Firmware.JPG (37 kB)
I appreciate your reply.   No,  that doesn't seem to be our problem.  It was more of when we downloaded a program.  

Here's an update on what we've done... 

We have followed Nick Swayne's instructions for downloading the new firmware v1.28.  There seems to be some issues with v1.26, especially working with the newer NXTG software that has the datalogging capability (v2.0), which is what we have.  (More info on this problem here

This firmware can be downloaded from here:

It is in a compressed file format (rar),  so I had to download Winzip to extract it.  

I also had to put the extracted file in the directory where the firmware is located. 
On my computer it is C:\Program Files (x86)\LEGO Software\LEGO MINDSTORMS Edu NXT\engine\Firmware.  Here's one way to find out where your firmware is located on your computers.  If you go into NXTG, click "Update NXT Firmware", next to the BROWSE button it will tell you where to browse... That is the location of the firmware files.

Then I followed these instructions (from Nick- Thank you!)
 Connect your nxt to your computer.  Make sure the computer is 'connected' to the brick in the software.
 In the NXT-G software, go to tools, select UPDATE NXT, then browse to the location you have it saved.  Click on the "download" button.

So far (since Friday) we haven't had any more lockups.   Thank you to everyone who replied to my email.  

Cari N

----- Original Message ----- 
  From: Lion's Pride FLL Team 
  To: Patrick & Cari Norton 
  Sent: Monday, October 26, 2009 8:11 AM
  Subject: Re: [VADCFLL-L] NXTs Locking up

  Are you having a moving part go into a bind?  This will cause a lockup.  In otherwords do you have an arm raising or lowering programatically but the arm is physically being stopped before it completes its programmed movement.  
  Ken Cochran - Halifax

  On Fri, Oct 23, 2009 at 10:06 AM, Patrick & Cari Norton <[log in to unmask]> wrote:

    We've been experiencing a problem of our NXTs locking up frequently.  Has anyone else experienced this?

    We have several bricks and this happens on all the bricks, which I would think would indicate it isn't a hardware problem.  We haven't had this problem prior to this season.   Our firmware is up to date on all the bricks. We are using the 2.0 version that has the datalogging capability.

    We know how to reset the NXT brick and  after we reset it, it is fine for a time.  We have to remove the NXT brick to do so... this would be terrible if it happened at the tournament... especially as the announcer says 3-2-1 LEGO!  

    Any ideas of things to try? 
    Cari N

    To UNSUBSCRIBE or CHANGE your settings, please visit and select "Join or leave the list". 
    VADCFLL administrative announcements are sent via VADCFLL-ADMIN-L. Visit to subscribe. 

  Ken Cochran
  AKA: "Mr. Wonderful"
  LEGO Robotics
  Halifax County Middle School
  434 572 4155

  Sanity calms, but madness is more interesting.
   - John Russell

-- To UNSUBSCRIBE or CHANGE your settings, please visit and select "Join or leave the list".

-- VADCFLL administrative announcements are sent via VADCFLL-ADMIN-L. Visit to subscribe.