Answers.Body: <p>I did not have that problem but I checked that error from programmer's perspective. The source seems to originate <a href="http://www.complang.tuwien.ac.at/cvsweb/cgi-bin/cvsweb/gforth/arch/arm/nxt/nxt_avr.c?rev=1.1;content-type=text%2Fplain" rel="nofollow">here</a> athough it can be also <a href="https://github.com/earl/gforth-mirror" rel="nofollow">found mirrored</a> on GitHub where the complete package can be downloaded. After short analysis of few files it looks that the message you quoted is sent on re-initialized link (connection). The link is reinitialized automatically if its state is either uninitialized or failed.</p>
  
  <p>If you can observe <em>exactly the same</em> time till each failure, then it looks this can be rather software issue than a hardware one. It can be still related to what you wrote in the question (one end of the link shut down after 5 minutes) or it can be related to some other software-based conditions. Try with trivial scenarios first. Also ensure that the firmware of all involved devices is up-to-date.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-20T14:22:18.547Z
Answers.LastActivityDate: 2016-08-20T14:22:18.547Z
Answers.UserDisplayName: miroxlav
Body: <p>I have an NXT brick that will always shut down after 5 minutes. No, it is not the sleep timer. Documentation from the NXT Hardware SDK, page 17, states that if the ARM7 processor does not send back communication to the AVR microcontroller within 5 minutes of power up, it will shut down the ARM7. Here is the message: "\xCC" "Let's samba nxt arm in arm, (c) LEGO System A/S"</p>
  
  <p>Has anyone had a 5 minute shut down problem not solved by resetting the sleep timer and have you solved it?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2013-10-22T06:34:11.077Z
Comments.Text: Is this "five minutes" measured while a program is running, or from the beginning of the NXT brick startup?
Comments.UserDisplayName: shea
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-01-08T21:59:47.620Z
Comments.Text: You might want to try updating the firmware on the NXT brick.
Comments.UserDisplayName: bsaat
Tags: <mindstorms><nxt>
Title: NXT shuts down in 5 minutes
UserDisplayName: user3050
ThreadText: # NXT shuts down in 5 minutes
  
  (Asked by: username_0 on 2013-10-21)
  
  I have an NXT brick that will always shut down after 5 minutes. No, it is not the sleep timer. Documentation from the NXT Hardware SDK, page 17, states that if the ARM7 processor does not send back communication to the AVR microcontroller within 5 minutes of power up, it will shut down the ARM7. Here is the message: "\xCC" "Let's samba nxt arm in arm, (c) LEGO System A/S"
  
  Has anyone had a 5 minute shut down problem not solved by resetting the sleep timer and have you solved it?
  
  **Tags:** mindstorms, nxt
  
  > **Comments:**
  > **username_1**: Is this "five minutes" measured while a program is running, or from the beginning of the NXT brick startup?  
  > **username_2**: You might want to try updating the firmware on the NXT brick.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2016-08-20. Score: 1
  
  I did not have that problem but I checked that error from programmer's perspective. The source seems to originate [here](http://www.complang.tuwien.ac.at/cvsweb/cgi-bin/cvsweb/gforth/arch/arm/nxt/nxt_avr.c?rev=1.1;content-type=text%2Fplain) athough it can be also [found mirrored](https://github.com/earl/gforth-mirror) on GitHub where the complete package can be downloaded. After short analysis of few files it looks that the message you quoted is sent on re-initialized link (connection). The link is reinitialized automatically if its state is either uninitialized or failed.
  
  If you can observe *exactly the same* time till each failure, then it looks this can be rather software issue than a hardware one. It can be still related to what you wrote in the question (one end of the link shut down after 5 minutes) or it can be related to some other software-based conditions. Try with trivial scenarios first. Also ensure that the firmware of all involved devices is up-to-date.
  
  
  ---
  
  