pic: Thousands of manhours of work... coming '07

[Andrew Blair]

I think what needs to be recognized here is the spirit of the rule, and not the wording. This is intended, like Kevin's code, to be a free, openly available tool that has been developed to increase the capability, and improve the learning curve of new, or limited resource teams. And, when it comes to software, most teams have limited resources.

[Karthik]

Originally Posted by Barry Bonzack

If we are unable to use code created before the six weeks in a copy/paste action as discussed here, how would that that rule apply to generating code from a program that was written with hundreds of hours before the six weeks?

This is a mistaken assumption. The thread you linked discusses R71, which deals with limitations on using code from the robots of previous years.

Originally Posted by Section 5, 2006 FRC Manual

<R71> Unaltered software modules developed during prior competitions may not be directly re-used. Just as designs for hardware COMPONENTS may be reused from one year to the next, software algorithms and designs may be reused. However, the specific lines of code must be customized for each robot each year.

Noticed the bolded text. This rule prevents a team from using identical blocks of code from prior years. It does not prevent a team from using code developed outside of the competition. Code like Kevin Watson's or what Mike and Matt have developed is legal according to my interpretation of the 2006 rules.

Of course, the rules on this topic may change for 2007. We'll find out in a few days.

[Matt Krass]

We appreciate the feedback and interest you've all displayed. We're working to get the beta test approved and your interest is very helpful, please keep it coming. Once it's all squared away and the beta is approved we'll release the official beta details and start emailing invites.

[magical hands]

Hey you guys can surely add 1219 to your beta test. We would love to try that control system and help give as much feed back possible If you guys want you can contact team 1219 on following e-mail jigarjuhi [at] yahoo dot ca

Couple of questions though! Are we allowed to modify your control system to suit our robot? for example your control system might be designed for 4 wheel drive but what if we have 6 wheel drive?

Also, if team chooses to implement your control system but what if later on they choose not to use it? is that fine? or you have to stick to the plan?

-:::-Jigar Patel [1219]-:::-

[Matt Krass]

Unfortunately due to unforeseen constraints, we will be unable to run the beta test this build season. A lack of availability of parts and funds as well as technical difficulties prevent us from being able to fairly distribute the technology. However you will see updates from us as we develop it further. This also allows us the opportunity to add in a few planned features, such as the ability to use a second, lower-rate gyro (perhaps even the KoP gyro) to measure vertical tilt and account for travel up and down slopes.

Thanks for all your feedback, knowing you're interested makes us want to work that much harder.

[Mike]

Originally Posted by Matt Krass

A lack of availability of parts

A little more information on that, as I'm sure it is affecting many other teams right now:

Due to the EU RoHS directive, which took affect Jan 1, 2007, you more or less can not get the ADXRSxxxEB series gyro board. The 401 seems to be an exception, however the 80 degrees/second maximum isn't near the speed of an average FRC robot.


We are using the ADXRS300EB for development, and although we could more than likely find a currently RoHS compliant gyroscope, with the amount of time it would take for us to purchase and receive the gyro as well as modify all of our code/documentation it would be too tight of a squeeze.

Rest assured that when this is fully completed, it will be a great system.

Thanks for the understanding,
Mike