Hi,
I was trying to solve "Obstacle_course" challenge in "Learning RobotC Tables" virtual worlds.
But I am unable to get the "RemBot" to track the black line which is the 3rd task in this challenge.

Following is the code written by me:
#pragma config(Sensor, S1, touchSensor, sensorTouch)
#pragma config(Sensor, S2, compassSensor, sensorVirtualCompass)
#pragma config(Sensor, S3, lightSensor, sensorLightActive)
#pragma config(Sensor, S4, sonarSensor, sensorSONAR)
#pragma config(Motor, motorA, gripperMotor, tmotorNormal, PIDControl, encoder)
#pragma config(Motor, motorB, rightMotor, tmotorNormal, PIDControl, encoder)
#pragma config(Motor, motorC, leftMotor, tmotorNormal, PIDControl, encoder)
//*!!Code automatically generated by \'ROBOTC\' configuration wizard !!*//

// This is for the NXT model, not TETRIX

/**********************************
**\\
|* ROBOTC Virtual World
*|
|*
*|
|* DO NOT OVERWRITE THIS FILE
*|
|* MAKE SURE TO \"SAVE AS\" INSTEAD
*|
\\**********************************
**/

task main()
{
forward(100);
untilTouch(S1);
stop();
wait(0.5);
pointTurn(left);
wait(0.54);
stop();
wait(0.5);
forward(100);
untilDark(15, S3);
lineTrackForRotations(35, 63, S3);
}

*********************************
Is it a problem with the threshold
value or is it a BUG? Kindly help.
Regards

For testing out thresholds, we introduced the "Line Utility" table. Try calculating your threshold and testing out your line tracking behavior by itself, there.

Thanks for the reply jbflot. But the robot tracks the line like a beauty in "Line Utility" table and other tables too except in this "Obstacle Course".
The following images can give a better insight to the problem.




So this last image shows the robot getting out of the track!
The threshold values are correct, but I sense there is a bug in this Table exactly at that point.

Hi,

Is it mandatory for you to use Natural Language in ROBOTC?

--
Alex Kolotov

Koal,

I am sure there are reasons for the use of NL. I am not sure adding the full ROBOTC language to the mix is a good idea at this point. This stuff should work

- Xander

Xander,

May be I said wrong. I would like to understand what was the reason to use NL. I see that it could be an educational reasons because NL is easier to teach. But if teaching of RobotC is not aim but they need to just learn robotics in RVW - other languages could be concerned.

Yesterday I spent some time to go through this challange by using nxc4rvw, so, probably they can use it also

--
Alex Kolotov

Natural Language was requested by middle school teachers. They thought that if kids had to learn how to navigate the IDE plus learn the code that it would be overwhelming.

We believe that NL provides a good first step, but also believe that kids need to transitioned out of it very early because it can lead to problems with their code quickly.

From what I've seen kids pick up programming pretty quickly.

Robin

Robin Shoop is right. That's exactly why we want to use NL. Otherwise the Robot tracks the line completely when written in RobotC language.

It is out of the main topic but anyway...
Let's look on another sort of NL:



etc.

How difficult will it be to learn? For me, it is similar to RobotC NL.

In my experience, once you learn how to program well in one language, learning subsequent ones tends to go much faster. My guess is that you'd be able to pick up languages, like the one you're sharing.