Answers.Body: <p>There are a few options for the cause of the error. It could be at the microprocessor level, meaning that the execution of the program is wrong, or it could be at the motor driver port, meaning that the NXT tries to drive the motor attached to the specific port but can't due to some electrical failure.</p>
  
  <p>The first option can be eliminated by using other forms of output (e.g. screen) instead or along with the motors, the second can be analyzed by swapping motor ports and testing them individually.</p>
  
  <p>However, in any case you probably won't be able to repair it yourself, so you should contact Lego instead if the existence of the error is certain.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-22T14:30:35.160Z
Answers.LastActivityDate: 2014-10-22T14:30:35.160Z
Answers.UserDisplayName: zovits
Body: <p>I have an issue that I am hoping someone might be able to resolve:</p>
  
  <p>We're using Mindstorms in the classroom as part of a STEM program, and have one NXT brick that won't execute programs correctly. The program is a simple move/turn/move program and the program works on other bricks. </p>
  
  <p>It will move forward and seems to attempt the turn but then just stops.</p>
  
  <p>Working programs from other groups also don't execute correctly on this particular brick so we eliminated a programming error. </p>
  
  <p>We have tried soft reset, hard reset, and updated the firmware all with no effect. </p>
  
  <p>I'm hoping it doesn't mean we have one totally useless robot. Any help is appreciated!</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-10-22T13:59:16.597Z
Comments.Text: Does it behave in a similar way if you use different ports for the motors?
Comments.UserDisplayName: Zhaph - Ben Duguid
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-10-22T14:13:39.610Z
Comments.Text: Without more information, it seems like one of the following is to blame:  bad ports, bad motors/devices, bad wires, bad power, or bad NXT.  The easiest way to test these would be to create simple programs and test things one at a time.
Comments.UserDisplayName: Nick2253
Tags: <nxt><programming>
Title: NXT brick not executing programs correctly
UserDisplayName: mr.l
ThreadText: # NXT brick not executing programs correctly
  
  (Asked by: username_0 on 2014-10-22)
  
  I have an issue that I am hoping someone might be able to resolve:
  
  We're using Mindstorms in the classroom as part of a STEM program, and have one NXT brick that won't execute programs correctly. The program is a simple move/turn/move program and the program works on other bricks.
  
  It will move forward and seems to attempt the turn but then just stops.
  
  Working programs from other groups also don't execute correctly on this particular brick so we eliminated a programming error.
  
  We have tried soft reset, hard reset, and updated the firmware all with no effect.
  
  I'm hoping it doesn't mean we have one totally useless robot. Any help is appreciated!
  
  **Tags:** nxt, programming
  > **Comments:**
  > **username_1**: Does it behave in a similar way if you use different ports for the motors?  
  > **username_2**: Without more information, it seems like one of the following is to blame:  bad ports, bad motors/devices, bad wires, bad power, or bad NXT.  The easiest way to test these would be to create simple programs and test things one at a time.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2014-10-22. Score: 2
  
  There are a few options for the cause of the error. It could be at the microprocessor level, meaning that the execution of the program is wrong, or it could be at the motor driver port, meaning that the NXT tries to drive the motor attached to the specific port but can't due to some electrical failure.
  
  The first option can be eliminated by using other forms of output (e.g. screen) instead or along with the motors, the second can be analyzed by swapping motor ports and testing them individually.
  
  However, in any case you probably won't be able to repair it yourself, so you should contact Lego instead if the existence of the error is certain.
  
  
  ---
  
  