|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
"Signaling Device" reciever location?
I just finished reading the rules and then browsing through some of the IR Communication threads. One of the biggest problems that everyone has identified is that it might be difficult to communicate with the robot during the hybrid period with whatever IR signal.
After looking over the rules again, I was wondering if we would be allowed to put the IR receiver on the Operator Interface instead of the robot its self. If we could, it would make it easy to insure you can communicate with the robot for all 15 seconds of the hybrid period. Thoughts? It seems like this shouldn't be allowed, but I couldn't find a rule to quote that says it isn't... Maybe you all can? - Toby |
|
#2
|
|||||
|
|||||
|
Re: "Signaling Device" reciever location?
I believe that it must be on the robot, but I'm not 100% sure.
I know at the kick-off they demonstrated the IR receiver worked better while channeling the IR beam through a tube. I also think there are no limits on how powerful the IR beam can be, so you could try messing around with some very powerful TV remotes. Did they say if it was OK to have IR beam retransmitters? They work wonders on my television and could for the robot. |
|
#3
|
||||
|
||||
|
Re: "Signaling Device" reciever location?
Maybe you could, but it wouldn't be useful. You can't read inputs from the operator interface during autonomous (hybrid) mode.
|
|
#4
|
||||
|
||||
|
Re: "Signaling Device" reciever location?
Daniel, I believe you're right, because you'll have nowhere else to connect other than the Joy ports 1-4 which, in "hybrid" mode, would be disabled (to the best of my knowledge)
And Alex, I THINK that the IR extenders use RF waves, which then would make it illegal as it could potentially interfere with the radios used for controlling the robot, among other things. I could be wrong about this, I'm not sure, but to my knowledge they do run on Radio Frequency =S Last edited by Rohan_DHS : 06-01-2008 at 00:25. |
|
#5
|
|||||
|
|||||
|
Re: "Signaling Device" reciever location?
Ok, thank you for answering my question. =)
Last edited by Alex Dinsmoor : 06-01-2008 at 00:25. Reason: Misspelled |
|
#6
|
||||
|
||||
|
Re: "Signaling Device" reciever location?
Quote:
a wired IR repeater schematic http://www.cedarnet.org/smartware/Ha...ater/index.htm and some other cool IR stuff: http://www.hobbyprojects.com/quick_c...chematics.html hope those help you out ...forest |
|
#7
|
||||
|
||||
|
Re: "Signaling Device" reciever location?
Quote:
However, you would need to make an adapter board to connect the receiver. |
|
#8
|
||||
|
||||
|
Re: "Signaling Device" reciever location?
Quote:
this is what i gathered from kevin's new code that he has been working on for the new compiler. ...forest |
|
#9
|
||||
|
||||
|
Re: "Signaling Device" reciever location?
Quote:
and for the adapter board; is that legal (assuming that the OI data is sent during auto mode)? [EDIT]oops I guess Forest confirmed that before I posted. Thanks Forest[/EDIT] Last edited by Rohan_DHS : 06-01-2008 at 00:45. |
|
#10
|
||||
|
||||
|
Re: "Signaling Device" reciever location?
I haven't read the rules throughly enougth to know, but I'd guess not.
Last edited by EHaskins : 06-01-2008 at 17:15. Reason: fixed quote |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Championship Event - Where the "Random" Match Sorting Really "Shines" | Travis Hoffman | Championship Event | 57 | 19-04-2007 08:06 |
| New NEMO White Papers! "Creating a Killer Packet" and "25 Ways to Sponsor" | Jessica Boucher | Team Organization | 0 | 10-08-2005 10:55 |
| "Thunderbirds" Vs. "Team America" Which one will rule the box office? | Elgin Clock | Chit-Chat | 3 | 07-09-2004 19:53 |
| Conflict between "Initialize_Tracker()" and "pwm13 & pwm15"? Kevin? | gnormhurst | Programming | 3 | 22-02-2004 02:55 |
| Nationals Location "Pool" | Ricky Q. | Championship Event | 103 | 18-11-2002 14:18 |