Hi all,

Brand new to this, in fact, I have not even unwrapped the NXT 2.0 kit yet as it's got to wait for Christmas!

I do have a quick question though that I'm hoping someone will be able to answer...

If I install the RobotC firmware on the brick, will my kids still be able to program the robot using the standard lego GUI, or does that require a reflash of the original firmware?

You'll need to reflash but that is super easy and quick. It would take all of about 20 seconds, I think

Xander

Excellent and thanks for the quick reply!

I'm an old C tart at heart, and don't think I'll get the hang off the GUI looks very messy to me - hell, I'm probably more comfortable with assembler, but it's been soooo long since I coded anything, I'll be pleased with a 'Hello World'!

Let me help you with that



Tadaaah

Xander

Thank you kindly sir!

I'm just going to read through the code documentation now, but to jump right to the point, and get another question under my belt, what kind of memory management can you do in RobotC - Are arrays fixed size as declared in the code, or is there an equivalent of malloc or similar to create a run time, or is it more sophisticated than that nowadays?

My first 'project' is to get a robot to map the contents of an area with a view to building a compact map of obstacles in its memory so it knows to avoid them - obviously, I don't know how big the space is or how many objects will exist at compile time, so looking for some form of dynamic memory management.

Furtim,

There is no memory management. All arrays must be static. There are also no pointers, which can be a blessing -and- a curse There is a good tutorial here: http://www.robotc.net/blog/?p=108

As for variable space, I believe it's around 20-24K or so, so that's a pretty big map

Xander

Xander,

Thanks for the link - excellent tutorial.

Furtim.