![]() |
Re: **FIRST EMAIL**/Invitation to Beta test the New Control System
1511 Submitted with 191, 378, 1126, 1405, 1507, 1551, 2228 & 2340 (anyone recognize the Ruckus committee & our labview teams?? - lol). We are acting as the leaders, so we just submitted our award info and the essay is based mostly off our team experience since it just seemed easier for the form and to keep the characters short.
Good luck to all the teams that get a system... its going to be a crazy preseason! |
Re: **FIRST EMAIL**/Invitation to Beta test the New Control System
Hi Kim (and anyone else who submitted for more than 3 teams)
just wondering: what your rational was in submitting for so many teams? do you plan on moving the controller between those teams evenly? or perhaps all those teams are the one's who are in your area and will benefit from your team having a controller and giving classes on it? My team contemplated a joint submission with another team, but the situation In Israel is slightly different: http://www.iris.org.il/images/usa.gif (I don't know what iris.org.il is all about and I don't necessarily approve of the content. I just googled "Israel size comparison") we hope to have 50 teams next year, but all those teams are at the very most a 5 hour drive away (from where my team is located). so we just stated that we plan to have "Controller weekend(s)" for all teams at our place. I'm just hoping First will send us (any team in Israel) a controller... Good Luck! -Leav Edit: Quote:
|
Beta Test poll
Upon reading here that several teams submitted joint applications, I became curious as to how many applications have more than one team listed. I started a poll in another forum since I couldn't add a poll to this thread. Please post your number in the poll and then comment on how that came to be. Please vote even if you are a single team application such as is the Toltech application.
Poll |
Re: **FIRST EMAIL**/Invitation to Beta test the New Control System
Quote:
We will likely be the center team, hosting the controller, but we had plans of having saturdays where other teams could bring their robot in, demos at Ruckus, webcast trainings and phone conferences to involve teams further out, and a lot of documentation on our wiki & forums. We will be inviting all of the teams that want to drive out here to be involved in any/all of the process, but these were just the teams that we have been interacting with for Ruckus planning and the teams that have been attending our Labview training all summer. I think for us, it just made sense, we can run the Beta testing, but bring in expertise from all the other teams in the area to help out and assist in problems as welll as taking time to teach as many teams as we can. |
Re: **FIRST EMAIL**/Invitation to Beta test the New Control System
Quote:
Labview is obviously Rolling Thunder's forte. I've gotten to know SparX programmers enough to know they are C gurus, even diving into the adc library to modify it. They sound like perfect candidates to help develop the open source C++ libraries as a C++ lead team. Your collaboration has the potential to do more "Beta Testing" than any of the other recipients by developing thoroughly in both languages and comparing first hand. Obviously, the choice between Labview and C++ is the most important decision programming teams face this year. I am not trying to make that decision for anyone, or give anyone more work/confusion. Just a idea I would like all the Beta Testing collaborations to consider. Good Luck to all teams as we break new ground, Brian <SIDE RANT> I don't see the major advantage to installing the cRIO controls system on multiple bots. Without multiple power distro blocks, digital sidecars, etc... it is an intense electrical task to move the cRIO between robots. Even if you build a modular panel, it still is time consuming to switch. IMHO, no matter how many teams you have: -Use 1 testbed bot -Load it with sensors and mechanisms -Maximize precious uptime for your programmers </SIDE RANT> |
Re: **FIRST EMAIL**/Invitation to Beta test the New Control System
Several of the Milwaukee teams plan to work together (if one of us gets it) but submitted seperately to try to increase our odds.
|
Re: **FIRST EMAIL**/Invitation to Beta test the New Control System
Speaking of programming in various languages and diversifying the results, is anyone planning on having students programming in Python? Just curious.
|
Re: **FIRST EMAIL**/Invitation to Beta test the New Control System
Quote:
|
Re: **FIRST EMAIL**/Invitation to Beta test the New Control System
Update through the FRC Blog this morning...
Quote:
|
Re: **FIRST EMAIL**/Invitation to Beta test the New Control System
we were suppose to hear by september 1st :(
|
Re: **FIRST EMAIL**/Invitation to Beta test the New Control System
Quote:
|
Re: **FIRST EMAIL**/Invitation to Beta test the New Control System
do volunteers benefit from Labor Day?
|
Re: **FIRST EMAIL**/Invitation to Beta test the New Control System
Quote:
What difference does a day make? |
Re: **FIRST EMAIL**/Invitation to Beta test the New Control System
I do believe there is a little kidding involved.
|
Re: **FIRST EMAIL**/Invitation to Beta test the New Control System
I think all the evaluators deserve a tremendous thank you. I can't imagine trying to evaluate 159 essays in 15 days or less. That's 10 a day, as a volunteer. I have a feeling that at least some of them will be giving up part of their holiday to work on this.
I'm very glad I'm not in their position. |
| All times are GMT -5. The time now is 01:08. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi