Thread: cRio limbo
View Single Post
  #7   Spotlight this post!  
Unread 07-06-2011, 08:39
Mark McLeod's Avatar
Mark McLeod Mark McLeod is online now
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,795
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: cRio limbo

Sounds like network problems where your laptop cannot communicate properly with the cRIO, so I'd first concentrate your efforts on things that cause those kinds of problems.
  • Laptop network settings (10.31.69.5)
  • Intermediate router/AP/bridge network settings (10.31.69.4)
  • cRIO status lights (there's nothing like a low battery)
  • FRC cRIO Imaging Tool cRIO search (a line at the top lists your cRIO when it finds it)
  • Network ping (from laptop to cRIO)
What are you running when you get these errors? The FRC cRIO Imaging Tool or LabVIEW?
The FRC cRIO Imaging Tool will tell you if you're getting through to the cRIO. Check to see what IP address is shown for your cRIO. You can connect your laptop directly to the cRIO port 1 for this test.

Do as Greg suggested and turn off wireless, etc., leaving only the Ethernet port enabled.
Connect an Ethernet cable between the laptop and the DLink and another between the DLink and the cRIO.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 07-06-2011 at 08:54.
Reply With Quote