We have had similar problems in past years (I cannot believe most people
haven't experienced similar problems at varying levels), and have a
escalating approach to such problems:
a. Try downloading the program after repowering the brick;
b. Try downloading the program after deleting the program on the brick;
c. Try downloading the program after taking out the batteries on the brick
and reimstalling them;
d. Try restarting the Mindstorms software on the computer;
e Try restarting the computer at the OS level;
f. Try rewriting the program.
g. Try resetting the NXT brick (the reset button is hidden in one of the
holes near the battery cover).
h. Try threatening to boil the NXT in isopropyl alcohol in vacuum
conditions :-)
i. If all else fails, but no sooner, pull all your hair out, but out of
view of the kids.
Others may have developed more/fewer steps.
I don't think the built in compiler is bug free or memory minimizing (both
of which annoy me), but then software has never reached the levels of
reliability or operating perfection that we demand of toasters and microwave
ovens. This is 50+year problem, and the economic foundation of the software
services business.
Best,
Nari
*------------------------------------------------------------
Anant S Narayanan
McLean Robotics Institute
McLean VA 22102
202-421-3826 (cell)
[log in to unmask]
-----------------------------------------------------------*
On Thu, Oct 20, 2011 at 9:51 PM, Bobby p. Carder <[log in to unmask]>wrote:
> Ok...this is two in one day...but I swear there is a goblin wreaking havoc
> with our bot/program.
>
> This error occurred when we downloaded a program to the brick and it
> subsequently said that there is a "missing required file" and to reload the
> software or nxt driver. In nutshell, after reinstalling everything there
> is
> to reinstall, including firmware, software, etc and rebooting and praying
> to
> the Lego Gods for mercy after several hours of torture. We still got the
> error.
>
> Then we took our program to another computer and downloaded it to a
> different brick. Voila! It happened again. Ok..to shorten a very long
> story....we have deduced that the particular robot program we were working
> on is somehow corrupt (???). What is really bizarre is that every other
> program will give the same error if opened after the 'bad' program. But!
> If we close down the NXT software and reopen a new program (without opening
> the 'bad' program), it doesn't happen.
>
> Anyone ever seen this before? I can't find anything greyed out, nothing
> looks obvious...but I am new at this, it's pretty easy to trip me up. I
> guess the kids will just have to rewrite the program? But I am not
> confident that another program will do the same thing.
>
> Thanks for your help - Paul Carder, The Lost Marbles
>
> -- To UNSUBSCRIBE or CHANGE your settings, please visit
> https://listserv.jmu.edu/archives/vadcfll-l.html and select "Join or leave
> the list".
>
> -- VADCFLL administrative announcements are sent via
> VADCFLL-ANNOUNCEMENTS-L. Visit
> https://listserv.jmu.edu/archives/vadcfll-ANNOUNCEMENTS-l.html to
> subscribe.
>
-- To UNSUBSCRIBE or CHANGE your settings, please visit https://listserv.jmu.edu/archives/vadcfll-l.html and select "Join or leave the list".
-- VADCFLL administrative announcements are sent via VADCFLL-ANNOUNCEMENTS-L. Visit https://listserv.jmu.edu/archives/vadcfll-ANNOUNCEMENTS-l.html to subscribe.
|
