[JasonStern]

I would definitely like to see a processor that can handle inputs better. first time i've dealt with an RC and i can't say im impressed. no negative numbers and no decimals were a nightmare, but worse of all was dealing with sensor inputs. one of the devices on our robot was designed to tell us if we were on the ramp and if we were on it straight. this device had near perfect accuracy with a PWM duty cycle style output, but only +- 10% with an analog output. I originally thought I could use the former mode with the rc, as the stamp has a function to support it, but I was discouraged to find that we have no direct inputs to the stamp and could not implement it. nor could we use the digital inputs of the rc as the stamp does not read them in fast enough. the sad part is that device only ran at 100hz, but the stamp's pathetic 38 hz is nearly a third of that! instead we had to use the analog inputs and sacrifice precision. not to a mention a similar problem (stamp to slow) kept us from using encoder wheels to track our robot.

FIRST, please, if you are going to continue auton modes, which I strongly hope you do, give the programmers and the electrical people on the teams more to work with. there may be a larger initial learning curve, but as someone else said, thats part of engineering. better now then years down the road when pbasic is even more obsolete!

P.S. something that would be nice is something similar to how you program lego bricks, at least their consumer version. the basic user can drag and drop control blocks in place and easily write code. However, the advanced user can bypass the gui and write code in text while having access to more advanced options. it would be a win/win situation for everyone!!