Page 1 of 1
2.1 software glitches?
Posted: 16 Nov 2011, 13:52
by bobalego
So the more I try to use the 2.1 software (which is all that is available now on the LEGO education website,) the worse it seems to work. Recently I have been finding this message appear while trying to place blocks into the palette: "Cannot find terminal hotpoint in wire (268D1D^+10080)" If this has anything to do with data wires, I am even more stuck as I am not attempting to use data wires when this occurs. Any ideas? I have had several other problems that have somewhat been addressed here or on the official site but once again the issues seem to keep popping up. This recent problem has only recently occurred and my laptop is less than one year old, HP G62. Thanks in advance to any suggestions.
Re: 2.1 software glitches?
Posted: 19 Nov 2011, 21:43
by timpattinson
NXT-G is slow and buggy on just about any computer.
Try to do things slowly as it is doing a lot of stuff behind the scenes, like recompiling all the time.
This page shows you how to write serious programs without glitching the editor.
http://www.teamhassenplug.org/NXT/NXTGTips/
This page is really useful, especially the Fix Broken Wires thing
http://www.teamhassenplug.org/NXT/NXTGAdditions.html
Re: 2.1 software glitches?
Posted: 05 Dec 2011, 20:04
by bobalego
Just noticed your help, thank you for the links they will be very useful for a number of reasons, unfortunately, it does not help me with the trouble I was having. Incidentally I closed the program and ran it again today and I did not have the same error message, so perhaps it was just necessary to do this?
Re: 2.1 software glitches?
Posted: 07 Dec 2011, 10:09
by bungeshea
bobalego wrote:Just noticed your help, thank you for the links they will be very useful for a number of reasons, unfortunately, it does not help me with the trouble I was having. Incidentally I closed the program and ran it again today and I did not have the same error message, so perhaps it was just necessary to do this?
Sometimes restarting NXT-G temporary fixes some of the bugs. Another thing you could try is rebuilding your program, that is, duplicating or copying/pasting small chunks of code and then recompiling it so you know what is causing the problem.