blackburried

It was the assignment statements. Somehow 2.0 wasn't able to understand 1.0's assignments, even though the graphic icon looks exactly the same. I replaced all the assignments in the block (with exactly the same assignments), and the code works again. Just to bolster the off-topic part of this thread, I too would rather have a text interface and a standard language syntax, especially over a GUI that may look pretty, but keeps screwing-up the code (i.e. I've spent 30 hours trying to figure out what's wrong in the above upgrade issue) and makes it difficult to program. The first thought of any CS grad is "I can make a better language" (the second thought is "I can make a program that does all my repetitive work automatically"), and the first thought of his boss should be to quickly gag those impulses. What does it teach my kid if I have to spend 30 hours making the GUI work so he can program graphically?

Good ideas, but no-go. First, "check for updates" does like every web link in 2.0: brings up a "Page Not Found" error at the Lego site. So, I went to http://mindstorms.lego.com/en-us/support/files/default.aspx#Patches and grabbed Legacy_Blocks_EN-US, which is the file: http://cache.lego.com/upload/contentTemplating/Mindstorms2SupportFilesDownloads/otherfiles/download14C944130FD52B93D53C058A20A3F5C4.zip And followed the readme to import the legacy devices. When I opened the program that worked under 1.0 and not 2.0, there were no new additions to any palette. When I re-compiled the program, it still didn't work. Further debugging showed that it may not be the light sensor value in error, it looks like either basic assignment or comparison operators quit functioning. This code was copied from "Line Follower Pro", which is the same as "Smooth Line Follower" that can be found elsewhere on the web. It self-calibrates by swinging 120 degrees and getting all the light sensor values in that range and setting a min and a max, as in the following pseudocode: min=4E5 max=0 <Rotate motors B and C in reverse directions> Do { light=<read light sensor> if light < min { min = light } if light > max { max = light } until <motor B has moved 120 degrees> The motor swings appropriately, but min and max come out as their initial values. That indicates that the comparison operators (">" and "<") quit working, or assignment ("=") quit working. If I compile/run the saved source "code" from 1.0, it works fine, as long a I don't try to edit it. If I at all try to edit that "code" (not even modify it, just touch an icon), and recompile it, the problems occur. I've seen the interface often screw-up "code" on it's own, but that's not the case. I've been through the "code" thoroughly to assure it's as it was. I've also re-downloaded the "Line Follower Pro" and "Smooth Follower" from the web, and they have the same problem (I do have to change the "color sensor" on the "Smooth Follower" to a "light sensor"). When I first upgraded to 2.0, it showed many of the program block's icons with "!" with some warning about compatibility issues and "click here for more", which clicking brings up the lego "page not found". This included all the mathematical comparison functions, so, not seeing the difference between the old and the new, I replaced with the new (and that goes for all icons with a "!" in them). Still no joy. I upgraded to the 1.29 firmware while still using 1.0 (so the NXT would be compatible with the 2.0 rev running at the school, until I found the Mac patch that allowed the educational version to install properly), and that firmware worked correctly w/ 1.0... so I don't think it's a firmware issue. I'm not sure what my options are... and my son's assignment is coming due quickly.

I used the educational 2.0 software with a 1.0 NXT, and all seems fine except for the light sensor... it no longer seems to register properly, even after calibration. Any idea how to get this to work? I'd hate to go back to 1.0 software... FORTRAN on punch cards in the 70's was more user friendly ;)