That's great news - thanks for ferreting this out! I can see a lot of ways to make certain standard blocks smaller, but I'm most curious as to what *else* they will end up doing. Optomizing the compiler seems a good option, but I'm not sure if there's anything else in the works.As to efficient coding, yeah... that's a learning curve we're all climbing (unless, perhaps, you are coming at this from LabVIEW).-- Brian Davis
Teams can maximize memory space by: Downloading the newest firmware from inside the NXT software Deleting unused programs Deleting unused sound and graphic files Deleting preinstalled files and programs Create subroutines to reduce the number of programming blocks neededI feel an urge to say "Duh".
Some feedback from an earlier club meeting: The students (3rd - 6th grade ) were told to delete or re-use the program names to avoid memory buildup while stepping through the programming exercises. One thing that was not obvious to them was accumulation of sound and graphic files albeit the reuse or deletion of programs
lol, ditto maniac. -Jonathan
"...In addition, LEGO is developing a number of new, additional programming blocks that will be more memory efficient...."Anyone has an idea what these can be?
RobotC has compressed sound, that might help. What might help NXT-G too is a better optimized kernel, and less overhead per block.I understand LEGO tried to cut corners to make sure they can release the product on time, and that's how they launched a solution that works, full well knowing this could be improved. And I have to say that NXT-G is pretty good for a version 1.0.I just wish LEGO provided some sort of roadmap, even if they cannot commit to time scales right now.FilipbNXT.com
I've used NBC which generates executables that are 1/10 the size of NXT-G executables.Has anyone done a benchmark on RobotC sizes - both executable and compressed sound file sizes? Is RobotC going to lose it's "free" status and become a commercial product?
Post a Comment