|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: New CRIO in the KOP next year?
Quote:
They actually had a much cost reduced version on display at the booth so it isn't a rumor. |
|
#2
|
|||
|
|||
|
Re: New CRIO in the KOP next year?
Quote:
If it's a lot smaller and lighter, that's a big advantage. The cRIO is a boat anchor and not well suited to a size and weight limited robot where inches and ounces are precious. |
|
#3
|
|||||
|
|||||
|
Re: New CRIO in the KOP next year?
Quote:
![]() The cRio does have an interesting design, not quite how I would do it, but it takes up far less real estate on our electronics board than the power distribution and speed controllers do, as usual. We took the time to figure out how to mount the cRio down low, with the connections easily accessible, and it really wasn't a size/weight issue at all. |
|
#4
|
|||
|
|||
|
Re: New CRIO in the KOP next year?
Quote:
Anyway, to explain what was in the NI booth, we actually had three generations of the cRIO. The drop test was the original generation of modular system. It consists of a cpu module, a backplane module, and the I/O modules. The backplane has the FPGA and comes in four and eight slot sizes. This rectangular packaging allowed the controller to fly to around 4000 ft in a rocket -- slides into the tube like a loaf of bread along with the battery. The FRC cRIO is called the integrated unit. It is lower weight and lower cost because the cpu and backplane are integrated into one PCB. It wasn't officially released when discussions about its use began. The third generation on demo is often referred to as the single board RIO. It has the module connectors on the edges to flatten the product from a loaf of bread into a pizza, and in fact doesn't come with a housing since it is designed to be integrated into a cabinet on large machinery, etc. This product was also under development when discussions began, but wouldn't be released early enough, doesn't have an enclosure, etc. Greg McKaskle |
|
#5
|
||||
|
||||
|
Re: New CRIO in the KOP next year?
It is a fraction of the weight of the cRIO
|
|
#6
|
|||
|
|||
|
Re: New CRIO in the KOP next year?
We also face the need to take demo robots out on tour, and it is a shame to have $3K street value of electronics sitting idle for most of the year or from year to year.
The cRIO does not lend to quick mount/dismount from one robot to the next. (OTOH, I'd love to see your quick change design on your robot). The daughter boards make it a little easier to reuse the modules. But I was (and still) am surprised about how kludgey the new system is to wire. I'd love to give high marks to the Power Distribution system. The spring loaded connections are nice, we did not have a failure all year. Which is good, because it's a real pain to need 6" of clearance around the board to get a screwdriver and a hand into the space to be able to maniuplate the connector. (Why yes, I'd love to see your custom Z bent tool you came up with) |
|
#7
|
|||
|
|||
|
Re: New CRIO in the KOP next year?
I would think that it is going to include a new one, however after hearing how much NI had to donate to incorporate them into last year's kit, I don't know how long they could keep it up. Although, I don't know how much of the MSRP is already a hefty markup.
|
|
#8
|
|||
|
|||
|
Re: New CRIO in the KOP next year?
Quote:
|
|
#9
|
|||||
|
|||||
|
Re: New CRIO in the KOP next year?
Quote:
Or you could go all out like we did this year, and make the entire electronics subsystem a self-contained box. A pair of anderson powerpole connectors for each motor, a DB-25 for connection to sensors and the signal light, and four mounting holes. (The battery does need to be mounted outside the box.) Our second control system, built to the same design, was occasionally connected to the competition robot's sensors using a DB-25 extension cable for program testing. Quote:
|
|
#10
|
|||
|
|||
|
Re: New CRIO in the KOP next year?
Basically, the KOP has remained consistent from year to year. The elimination of a Control System would be a substantial deviation from the 'norm'.
Until this past weekend, we hadn't given it a second thought about not being supplied another Control System next year. After hearing about the large contribution NI has made to provide these components and software to the teams, a duplication of this KOP item may not be included each year. Being this system is going to be used in the coming years, our Team will definitely want to have at least (1) additional complete system for spare and testing. If we're not going to receive another within the 2010 KOP, we'll re-allocate some funds to purchase another soon. But, by no means, can we justify doing this if it the system will be supplied in the 2010 KOP. Anyone know who the FIRST contact would be on this issue? Please send a link to this thread so our concerns can be noted. |
|
#11
|
|||||
|
|||||
|
Re: New CRIO in the KOP next year?
Based on this post on Bill's Blog about reusing components from the new control system, it appears that there are plans to reuse the cRIO and some other components from year to year. I remember seeing somewhere later about a plan for every other year to get a new cRIO, but that may have been someone's idea and not an official announcement.
That being said, there have been the DS issues this year that are getting teams a new DS for next season. What effect this will have on the rest of the system being used remains to be seen... |
|
#12
|
|||||
|
|||||
|
Re: New CRIO in the KOP next year?
Quote:
Quote:
Quote:
And, if the fact that the original KOP cRIOs were 100% donated should make a difference in next years team fees, then why were the fees not reduced this year?? |
|
#13
|
|||||
|
|||||
|
Re: New CRIO in the KOP next year?
I've had it in the back of my mind all season that we would not get a new cRio next year.
As to the KoP price vs. what's in it....I've never been bothered by the robot parts cost, it's relatively trivial compared to what we spend on travel. Yes, I'm involved in fundraising for the team. |
|
#14
|
||||
|
||||
|
Re: New CRIO in the KOP next year?
Quote:
A significant barrier to team entry and continuation is the cost of the program. If teams could realize an optional cost reduction in exchange for reuse of some of the more durable parts, I would be all for that. Personally, I would like to see the cRIO and its IO modules reused year-to-year (with option to replace at FIRST discounted prices, as NI currently offers), but be issued new PD, sidecars, bumpers, etc. The connections made at the IO modules to the bumpers/sidecars are quick and easy to change out and would make moving the cRIO between robots easy. I like this approach not only for cost reasons, but for "green" reasons. |
|
#15
|
|||||
|
|||||
|
Re: New CRIO in the KOP next year?
Quote:
Quote:
-dave ** Because it will be the Board, not the FIRST staff, that will make this decision. Right now, the Board is seriously disconnected from the teams in FIRST. They don't understand how "small" costs like these really impact this community. There is little direct, personal understanding of the impact of their decisions on the teams. During the recent combined Board Of Directors / Executive Advisory Board meeting in Atlanta, the question was asked "how many of you work directly with a team and have experience as a mentor?" Out of the entire room of people, only one hand went up. I think that is a huge problem. . |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| New robot controller next year? | KenWittlief | Rumor Mill | 94 | 12-10-2003 21:23 |
| New programming language next year? | Mike Alighieri | Programming | 131 | 13-09-2003 20:51 |
| New Video Codec for Animation next year. | Kyle Fenton | 3D Animation and Competition | 12 | 21-09-2002 02:54 |
| Next year: Make the game understandable | archiver | 1999 | 23 | 23-06-2002 22:53 |
| Any new regionals next year? | Anthony S. | Regional Competitions | 31 | 26-06-2001 07:45 |