New NXT EDU 2.1f3 Patch

[KRSC]

There seems to be a new NXT EDU 2.1f3 Patch for NXT-G from LEGO

http://cache.lego.com/en-gb/~/media/...20edu%2021.zip

From the Read Me:

The LEGO MINDSTORMS Education NXT 2.1 f3 patch fixes the following issues:

• Running a datalogging experiment more than once or importing a datalog file can result in extra datapoints
• Opening certain programs results in not being able to download any programs, error code 1003
• Intel Mac only - program canvas or diagram prints yellow
• Mac only, Adobe Flash later than 10.0 only - Severe usability issues, Mac OS crash dialog on exit

[dvz]

Thanks for the heads-up, and I remind everyone not to open any file from someone you don't know. Nothing personal, KRSC, but you are a one-time poster.

[Robomom]

Thank you for letting us know there is a patch available. We had backed off of using 2.1 because of the 1003 error problems. I called LEGO to ask if there was a place on their website to download the patch. They told me they haven't posted it on a specific page for people to find, but they will send a link to anyone that calls and asks for it. The rep said they prefer to do it that way so they can be sure to send the right link (Windows vs. Mac etc). I'd share the link he sent me for my Windows computer, but it is only good for 14 days. The number I called was 1-800-838-9647.

[KRSC]

You can find all the patches here:
http://education.lego.com/en-gb/pres...ion/downloads/
--Select Type-- | Software | Search
Then you can see 3 patches. I tested them and I think the 'NXT Patch' at the bottom of the page does not 'Upgrade your NXT software from 2.0 to 2.1 ...' but from 2.0 to 2.0f1.
So if you use this one first, it should be followed by the 'NXT EDU 2.0f3 Patch' and not by 'NXT EDU 2.1f3 Patch'. This worked for me.
And as you can see in the Read Me this should solve the 1003 error problems.

[eaglesc]

Originally Posted by KRSC

You can find all the patches here:
http://education.lego.com/en-gb/pres...ion/downloads/
--Select Type-- | Software | Search
Then you can see 3 patches. I tested them and I think the 'NXT Patch' at the bottom of the page does not 'Upgrade your NXT software from 2.0 to 2.1 ...' but from 2.0 to 2.0f1.
So if you use this one first, it should be followed by the 'NXT EDU 2.0f3 Patch' and not by 'NXT EDU 2.1f3 Patch'. This worked for me.
And as you can see in the Read Me this should solve the 1003 error problems.

I'd love to see 1003 errors lost into the mists of time!

Ok, so let's say you were to start with a 2.0 generic install, and had applied the 2.1 patch which was free for a while last year. Now the under Windows the properties on the nxt-g app tag it as 2.1, the chrome on the app still says 2.0. Which upgrade path is the right one in this case? I'll possibly look at this over the coming weekend -- I would beg anyone who is in this boat to post on their experiences. For some reason, I think this thread could lead to a very useful HOWTO.

Also, the url has a en-gb in it which I would guess maps to ENglish-GreatBritain . Is there an en-us analog? I tried simple substitution of en-us for en-gb in the URL and that doesn't work. (Sometimes it does for automagically generated content.)

[KRSC]

Originally Posted by eaglesc

Ok, so let's say you were to start with a 2.0 generic install, and had applied the 2.1 patch which was free for a while last year. Now the under Windows the properties on the nxt-g app tag it as 2.1, the chrome on the app still says 2.0. Which upgrade path is the right one in this case?

I did the same start (2.0 EDU generic install) and then applied the 'NXT Patch'. I think it is exactly the free patch from last year. You are right, the properties on the nxt-g app tag now shows 2.1 but in all other places you find 2.0f1. So you can only go on with the 'NXT EDU 2.0f3 Patch', the 'NXT EDU 2.1f3 Patch' will refuse to install. I think it only works with a recently bought 2.1 version, but it' s a guess.
The Read Me of the last patch says you can skip the first 'NXT Patch', but I didn't try it.

Originally Posted by eaglesc

Also, the url has a en-gb in it which I would guess maps to ENglish-GreatBritain . Is there an en-us analog? I tried simple substitution of en-us for en-gb in the URL and that doesn't work. (Sometimes it does for automagically generated content.)

I found international versions in the downloads with the en-gb url. That should work for you (I hope).

[stevekaip]

1st time poster here...this thread brings up a lingering question I've never had successfully answered. I have the 2.0 Retail version software. I am using 1.28 firmware. Should I be upgrading to 1.31 to at least get the on current FW?

[eaglesc]

Originally Posted by stevekaip

1st time poster here...this thread brings up a lingering question I've never had successfully answered. I have the 2.0 Retail version software. I am using 1.28 firmware. Should I be upgrading to 1.31 to at least get the on current FW?

I don't think the kids I coach had any problems with 1.31 firmware last year. I seem to remember issues on 1.28 but no details. I may remember 1.26 was problematic (crash/hang).

So, there's one anecdotal data point that 1.31 doesn't seem too bad. There ought to be a way to set up polls for this kind of stuff so community wisdom can be gathered. If (hypothetically) 90% of the poll respondents are on 1.31 and nobody seems to be screaming it might be a good upgrade. Even if the sampling is not scientific due to self-selection of responders, the information might still be worth capturing.

[Jeff Bartig]

1.26 was definitely a version of the firmware to avoid. If you ever performed light sensor calibration using the calibrate block, your brick would randomly lock up when running programs. The calibrate block creates a file on the brick that contains the calibration data. Anytime the brick runs a program, this file is accessed, even if the program doesn't use the light sensor. There is a bug in 1.26 that causes the brick to lock up when reading the calibration file. The only way I found to unlock the brick was to remove the battery briefly. It caused many hours of frustration for the team two years ago.

[ronmcrae]

Originally Posted by stevekaip

1st time poster here...this thread brings up a lingering question I've never had successfully answered. I have the 2.0 Retail version software. I am using 1.28 firmware. Should I be upgrading to 1.31 to at least get the on current FW?

A couple of points in response to the above....

(1) Though you didn't specifically ask about it, for everyones clarification the 2.0 Retail NXT-G software doesn't require any upgrade at this time - and there are none available. The issues corrected with the patches mentioned in this thread pertain only to the 2.0/2.1 Education NXT-G software. That 1003 problem definitely does now appear to be corrected once the patches are applied.

(2) At this time I'd suggest that teams should be using FW V1.31. No issues for us last year. FW 1.28 is also perfectly fine (used that the prior year), but avoid FW 1.26 at all costs. One change between 1.28 and 1.31 is an improvement to the LEGO color sensor color recognition algorithm, though this would only apply if using the color sensor in color sensor mode (assuming, of course, that the color sensor is even allowed this year!).