spillerrec wrote:There is a chart out there with some comparisons, I'm sure someone here has a link.
Read light sensor(3)
Read US sensor(4)
Read & Display Rotation Sensor(B)
Get random number (1-100) (RN to be used later)
Display value of:(Light Sensor+US Sensor+Rotation Sensor)*100/(RN)
Set motor speed for B and C to RN (Using Coast)
If RN > 50, Increase A by 1
If RN < 50, Decrease A by 1
If RN = 50, no change to A
Set motor A speed to A (if A<0, set direction to reverse)
Display Loop Count
Loop for 60 seconds
Show display for 10 seconds
It is worth noting that since those articles the 1.2x firmwares were released and that the NXC compiler have been significantly improved, so the speeds are not accurate anymore. But the NXT-G < NXC < RobotC order most likely haven't changed anyway...peter-cocteau wrote:It seems NXC is 5x faster than NXT-G and RobotC would be 135x faster than NXT-G !!!
NXC programs can use up to 128 tasks if I remember correctly, and the variables are limited by an max amount of about ~63k and a memory size of 32 KB. These are the limitations of the firmware, so NXT-G is subject to these too.peter-cocteau wrote:I think NXC would be a good thing to learn this kind of programmation. It may be fast enough. But In my program I use lot of task, variables and single array, may be NXC is too limited ?
Doc-Helmut, which language is this sample ?
I think Hitechnic blocks are made with labview? may be there is a way to minimize operation time?
Users browsing this forum: No registered users and 0 guests