Chief Delphi
Page 5 of 6 < 1234 5 6 >
Show 100 post(s) from this thread on one page

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Programming (http://www.chiefdelphi.com/forums/forumdisplay.php?f=51)
-   -   pic: Thousands of manhours of work... coming '07 (http://www.chiefdelphi.com/forums/showthread.php?t=50699)

Billfred 31-12-2006 16:19
Re: pic: Thousands of manhours of work... coming '07
 
Other question of interest to me: Is this system adaptable to some of the growing numbers of omnidirectional robots? Even in such a grunt-heavy game as Aim High, you still saw a small number of teams take it sideways in various forms--and interest in them seems to be pretty high, going by the number of CAD drawings and prototypes I've seen on ChiefDelphi.

chris31 31-12-2006 16:22
Re: pic: Thousands of manhours of work... coming '07
 
Quote:
Originally Posted by Mike (Post 546533)
Thanks for the input all,

We'd like to bring this topic back into focus. The competing systems are an interesting discussion, and will be a fun topic once the full capabilities of both are revealed. Matt and I are confident in what we have developed, and are looking for others to invest in that confidence.

So, who would be willing to beta test?
Im willing, I have to check with the team though. Any idea on when schematics and all will be posted since kickoff is just around the corner.

Mike 31-12-2006 16:32
Re: pic: Thousands of manhours of work... coming '07
 
Quote:
Originally Posted by Billfred (Post 546542)
Other question of interest to me: Is this system adaptable to some of the growing numbers of omnidirectional robots? Even in such a grunt-heavy game as Aim High, you still saw a small number of teams take it sideways in various forms--and interest in them seems to be pretty high, going by the number of CAD drawings and prototypes I've seen on ChiefDelphi.
The current revision is designed to work on robots based on the typical (and currently dominant) drive systems.

The next version (not this season) will be able to handle any type of drive system, however. As of now, our mantra is "Jack of all trades, master of none."

Quote:
Originally Posted by chris31 (Post 546543)
Im willing, I have to check with the team though. Any idea on when schematics and all will be posted since kickoff is just around the corner.
Our time schedule estimates that beta testers will receive full plans and schematics some time before the end of Week 1. However, they will be given all the information we currently have ASAP. For the amount of work that you could get done by week one, the current information is more then plenty.

Adam Richards 31-12-2006 16:35
Re: pic: Thousands of manhours of work... coming '07
 
Quote:
Originally Posted by Mike (Post 546533)
Thanks for the input all,

We'd like to bring this topic back into focus. The competing systems are an interesting discussion, and will be a fun topic once the full capabilities of both are revealed. Matt and I are confident in what we have developed, and are looking for others to invest in that confidence.

So, who would be willing to beta test?
As long as you can get me the schematics in week 1, I should be more than able to get my team to assist. I'll just need to talk to the programming mentor and programming lead first.

Matt Krass 31-12-2006 16:56
Re: pic: Thousands of manhours of work... coming '07
 
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 31-12-2006 17:09
Re: pic: Thousands of manhours of work... coming '07
 
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]-:::-

magical hands 31-12-2006 17:19
Re: pic: Thousands of manhours of work... coming '07
 
Quote:
Originally Posted by Mike (Post 546518)
Matt and I never mentioned camera data.
Not you but some other people on the post mentioned so I assumed you guys have that feature.

Quote:
Would you rather be required to pay $XXX more in order to purchase a PDA to attach to the bot?
You don't necessarily have to purchase a PDA, I am 110% sure every team has atleast 1 laptop in pit area. Why not make better use of that laptop and have it embedded on control system. Now you can do your programming as well as use it as an onboard computer.

Quote:
$200 price limit. Why have binary switches if we already have a fully loaded/embedded computer? If the computer is on the robot, how are we supposed to see the information in realtime?
Why Binary swtiches? When you are in autonomous mode you are running an autonomous(); That means you are not linked to anything not even radio control so you can't communicate. In such situations you do need something onto the robot such as "Binary Switches" to tell your Autonomous(); what to do when certain switches are on and off. Correct me if I miunderstood the concept please because certainly I could be wrong.

Quote:
Tom, is your system plug and play? :cool:
Yes our system is plug and play

Billfred 31-12-2006 17:21
Re: pic: Thousands of manhours of work... coming '07
 
Quote:
Originally Posted by Mike (Post 546544)
The current revision is designed to work on robots based on the typical (and currently dominant) drive systems.
Makes perfect sense to me.

I'll have to do some checking before committing, but this certainly sounds interesting.

Greg Marra 31-12-2006 17:31
Re: pic: Thousands of manhours of work... coming '07
 
Quote:
Originally Posted by magical hands (Post 546563)
You don't necessarily have to purchase a PDA, I am 110% sure every team has atleast 1 laptop in pit area. Why not make better use of that laptop and have it embedded on control system. Now you can do your programming as well as use it as an onboard computer.
Computers + high speed impacts = :(

magical hands 31-12-2006 18:45
Re: pic: Thousands of manhours of work... coming '07
 
Quote:
Originally Posted by Greg Marra (Post 546569)
Computers + high speed impacts = :(
Don't get me wrong but I didn't mean onboard meaning on robot. I meant it on control system lol :) Was my assumption correct or you meant something else?:confused:

Greg Marra 31-12-2006 20:28
Re: pic: Thousands of manhours of work... coming '07
 
Quote:
Originally Posted by magical hands (Post 546586)
Don't get me wrong but I didn't mean onboard meaning on robot. I meant it on control system lol :) Was my assumption correct or you meant something else?:confused:
Oh I understand what you mean now. You will use the laptop as a combination dashboard -slash- program-the-autonomous-mode-with computer.

177 used a dashboard with great effect last year. I highly recommend them. It gave us very good diagnostic information and let us check out all the key parts on our system with a single glance at the screen.

Andrew Blair 01-01-2007 00:39
Re: pic: Thousands of manhours of work... coming '07
 
Quote:
Originally Posted by Greg Marra (Post 546569)
Computers + high speed impacts = :(
Haha, frowny face indeed. As far as the LCD goes magical hands, I think it's just meant to be a really light, quick diagnostic device. Check modes, certain algorithm values (Such as PID), etc. Nothing big. If you are just using it for a relatively static auto. mode, then it is probably not even necessary. They do intend for it to be optional.

Tom Bottiglieri 01-01-2007 02:31
Re: pic: Thousands of manhours of work... coming '07
 
Quote:
Originally Posted by Andrew Blair (Post 546640)
Haha, frowny face indeed. As far as the LCD goes magical hands, I think it's just meant to be a really light, quick diagnostic device. Check modes, certain algorithm values (Such as PID), etc. Nothing big. If you are just using it for a relatively static auto. mode, then it is probably not even necessary. They do intend for it to be optional.
These are some things that flashed on the LCD when we started up last season:
Battery Voltage
Gyro Rate (to make sure it was calibrated correctly.)
Ultrasonic sensor distance (sometimes the plug came out and the distance was 0. We drove backwards...)

These things can be checked in another fashion, but in the heat of competition, its easy to miss something.

Greg Marra 01-01-2007 02:34
Re: pic: Thousands of manhours of work... coming '07
 
Quote:
Originally Posted by Tom Bottiglieri (Post 546658)
These are some things that flashed on the LCD when we started up last season:
Battery Voltage
Gyro Rate (to make sure it was calibrated correctly.)
Ultrasonic sensor distance (sometimes the plug came out and the distance was 0. We drove backwards...)

These things can be checked in another fashion, but in the heat of competition, its easy to miss something.
177 used a dashboard for exactly the same purposes, and we caught some otherwise extremely serious problems before they lost us a match. I think I am smelling an episode of The Blue Alliance here...

6600gt 01-01-2007 15:13
Re: pic: Thousands of manhours of work... coming '07
 
How much work is the ATMega16 actually doing?


All times are GMT -5. The time now is 20:41.
Page 5 of 6 < 1234 5 6 >
Show 100 post(s) from this thread on one page

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi