I'm trying to run VW for Tetrix. I change the default from NXT to Tetrix and I see my Rangerbot. I open the sample program "Forward for Distance" and compile without any issues. When I run the program however, the Rangerbot appears to rear-up and I get a ROBOTC Exception Violation Report of type "Invalid internal management of sensor RAM buffer(73)" ; Error at PC: Task:main+0x0022. The Pragma appears to be correct.

Any ideas what I'm doing wrong?

Wow! That's a doozy.

What version of ROBOTC are you using? Which RVW are you using (and what version)? (The version number should be on the first screen. It might have none, which means its the first release.)

Ed

Have the same issue on LEGO NXT robot in RVW. Getting this error just when run a simple program like

task main()
{
motor[motorB]=100;
motor[motorC]=100;
wait1Msec(4000);
}

RobotC: 3.08; Build ver. Mar 7 2012

Interesting observation. I am running RVW in VirtualBox. If I just restart the virtual machine and run the program by the first time - it works perfectly. But if I press the button "play" in the window with Virtual World just after that - the error appears.

Thanks for the information. We'll look into it.

Hi,
any update on this error? I'm experiencing what's described above

thanks

I too am getting this error. Is there a fix? My concern is that I have 4 weeks to teach myself RobotC for Tetrix before the next semester starts and I begin teaching my first Robotics class. So I need to get this working in a Hurry!

Hi everyone, sorry about the delay in the response. This is a known issue we are working on for our next update, but the current work-around is to download the Arduino beta version 3.12 (which has the fix built in) and use that in the meantime. This will work for the NXT versions of ROBOTC; be wary if you are using VEX, though, as there are some known compatibility issues between the Arduino beta build and the VEX version of ROBOTC (which is why the 3.12 build is still in beta).

Let us know if this helps, or if you come across any other issues.

Just confirming that this is fixed in all of the latest builds of ROBOTC.