So many questions, but I need to say that RobotC is a great package!

I am using the demo and assume that it will expire in 30 days. I see no indication of how much time is left on the demo. Before I buy it, I am watching for a Mac version. I'm not sure of the time frame for releasing a Mac version.

Besides having a lot of fun, I noticed a couple of things:

I am using 2 ultrasonic sensors to track along the walls of a room. When I try to use a second sensor in Port 2 (S2), I don't get proper data from it. It isn't the sensor. Am I missing something?

Also, when I went back to using the Lego software, it warned me that I had changed the firmware and offered to "update it". Is this a problem?

Thanks, John L.

Hi John!

Thanks for the comments. Yes, your evaluation period will end in 30 days.

As far as your ultrasonic sensors, do you have the code that you were using? I'd like to try the same code on my robot and then I can see if there is anything wrong.

When you go back to the LEGO Mindstorms software, it will ask you to load the LEGO Mindstorms firmware. This is appropriate because when you use ROBOTC, you must use ROBOTC's firmware. Firmware is very easily interchangeable.

Please let me know if you have any other issues. Thanks John!

You should see something like the following when you start RobotC if you have not registered yet:


If you do not see this screen when you start RobotC, you do not have the most current version. If you downloaded from our website, but had a previous version installed, please do the following:

1. Uninstall "New" version (RobotC for Mindstorms)
2. Uninstall "Old" version (RobotC Beta 1.0.xx)
3. Re-install "New" version. (RobotC for Mindstorms)

This screen gives you a counter of how many days are left on your evaluation.

Let me know if this fixes the issue. Thanks.

Thanks for the posts,

I will try replacing the beta of RobotC with the final version and check the second ultrasonic sensor.

The code I used essentially took a line from one of the Ultrasonic Sample Programs, a const declaration that seems to associate a variable with S1. I added a similar statement with a different name and used S2 instead. The distance values from it are not meaningful. I will check this with the proper firmware.

If a problem remains, I will sure post the code that doesn't work.

Thanks again for the help.
John L.

There could be *something* about the Sonar Sensor if you feel your values are "sticking".

When the sonar sensors reports back a value, it reports back in centimeters. If the sonar sensor sends out a pulse but can't find an echo, it usually reports back a 255 (to denote no signal).

RobotC has a condition functionality built into using the Sonar sensor where it will ignore the 255 and continue to send you the last correct value. This works pretty well but can be a little misleading.

If you would like to try the sensor in the raw, unconditioned state, use the SensorRaw[sensor_name] instead of SensorValue[sensor_name].

Try it and post your findings. Thanks!

Hi Tim,

This is a problem that seems to catch out a lot of users (including me) until I saw a reference explaining it was an intentional design choice in the old bug fixes section. Although there is a work around for it ie using SensorRaw(sensor_name) instead, if it continues to catch people out it may be worth looking at ways to make this feature choice more obvious.

As a suggestion would it be better to make 'stickiness' on optional function within SensorValue or would this be too complicated given SensorValue deals with all the different sensors?

Thanks
James

I have downloaded the proper version of RobotC with the up to date firmware. Two sensors work fine.

What I thought I was experiencing was not so much a sticking value as a completely nonsensical value. But again, that was a late beta version.

The stickiness idea is interesting. I will watch for this as there will be times when I will have a vehicle go past an outside corner.

Great posts, thanks a lot,
John L.