Go to Post when answering a question you throw out other teams names (thunder chickens and killer bees)...and a distinguished guest raises his hand and asks if he heard right when I said thunder chickens and asks for an explanation of what a thunder chicken is. - Devon27 [more]
Home
Go Back   Chief Delphi > Technical > Control System > FRC Control System
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #1   Spotlight this post!  
Unread 23-02-2009, 15:50
ChuckDickerson's Avatar
ChuckDickerson ChuckDickerson is offline
Mentor / Bayou & CMP Division LRI
FRC #0456 (Siege Robotics)
Team Role: Mentor
 
Join Date: May 2004
Rookie Year: 2004
Location: Vicksburg, MS
Posts: 877
ChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond repute
Is this normal?

This is kind of hard to explain but is it normal to have to cycle the power on the robot and/or the Wireless N game adapter several times before communication will be established between the cRIO and the Drivers Station? This is not a new “problem” for us as it has existed since we first got our electronics in December. EVERY time we start up the robot we have to either cycle the power or pull the plug on the wireless N game adapter to get things communicating. Most of the time two or three cycles of just the game adapter does the trick but sometimes we have to shut off the main breaker and count to 10 before powering it back up. Early on it was irritating. Now it is just plain frustrating because it takes quite a bit of time and effort to get the robot/cRIO and the Driver Station talking. Once everything starts talking it is fine until you power off and back on again. I just can’t imagine that this is normal. If it is then there will be a lot of wasted time trying to get the robots communicating with the field at the beginning of each match. I’m not talking about the boot up delay either. With our system you could wait an hour and it won’t start talking unless you cycle the power just right, hold your breath and have all of the freshman jumping on their left foot facing North.

Are other teams having these sort of issues? Anyone know what we should try?
Reply With Quote
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
AnalogChannel as both an accumulator AND a normal input? Jared Russell C/C++ 2 31-01-2009 10:14
<R06> normal wear and tear Darkcrosbone Rules/Strategy 54 27-01-2009 18:03
PID vs Normal loops 3DWolf Programming 20 14-12-2007 13:41
Hobbies, normal and unusual Jill1022 Chit-Chat 61 29-04-2005 08:33
Well, is it normal for me not to be in FIRST Robotics and post here? JKis6622 Chit-Chat 3 13-03-2004 15:46


All times are GMT -5. The time now is 05:34.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


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