Go to Post our electronics boards had begun to look like we'd planted a wire bush and it grew - daltore [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 Rating: Thread Rating: 2 votes, 5.00 average. Display Modes
Prev Previous Post   Next Post Next
  #4   Spotlight this post!  
Unread 14-12-2009, 20:19
1951-44U's Avatar
1951-44U 1951-44U is offline
ROAR.
AKA: Phil Chang
FRC #0025 (Raider Robotix)
Team Role: Programmer
 
Join Date: Oct 2008
Rookie Year: 2007
Location: NBTHS
Posts: 34
1951-44U has a spectacular aura about1951-44U has a spectacular aura about1951-44U has a spectacular aura about
Re: cRIO Does Not Communicate, Yet Can Be Pinged and Re-Imaged

Quote:
Originally Posted by kamocat View Post
My best guess is that your deployment didn't set the real-time application to run as startup, and so when you reboot the cRIO, it doesn't automatically run your code.
I'm sure you know that in reimaging the cRIO, all your code is removed.

Please describe in more detail your procedure for testing connectivity with the driver station? Are you deploying code to the cRIO first, or are you just booting up the system?
We use WindRiver/C++, so we download the code. What happened was that we fixed the "No Code" error and was able to do a good bit of programming, but it was getting late and we wanted to resume a few days later. So we turned everything off and put it away, without deleting or re-imaging anything, so the old program was still there. When we set up everything (DS, Robot, Laptop), the robot refused to connect with the DS once we turned it on. The status light didn't blink at all, which I found suspicious.

First thing I did was ping IP's, and checking all the IP's of the DS and the cRIO, found no problem. I could also re-image the robot from the laptop, which would declare successful on the laptop but upon reboot of the robot after reimaging with default code in it, the robot still refuses to connect. We did this several times. We also tried it with wireless modem. We confirm that the wireless bridge and router are connecting and communicating with each other, but still can't control the robot with the DS.


Quote:
Originally Posted by Greg McKaskle View Post
A cRIO that is running the OS can be pinged and it will respond. If it is not also running a robot code will also respond to the FRC protocol and will show as having robot code.

The cascading lights last year were not on the digital breakouts, but on the relay module, and that was a "feature" of the default project image and could have been in your code as well I suppose.

Greg McKaskle
Yea, the lights on the relay module was what I was referring to. Do they signify anything (e.g. Digital Relay Module active and working? Data transmission?, etc.)?

Last edited by 1951-44U : 14-12-2009 at 20:22.
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
Code deploys but does not save to cRIO Bill Taylor NI LabVIEW 11 15-02-2012 20:30
Crio network light does not light when camera plugged in Bongle Programming 16 16-01-2009 11:00
DS and cRIO Not Maintaining Communications Will_Sica FRC Control System 0 10-01-2009 13:39
RC will not communicate with OI Ryank Electrical 3 08-01-2008 17:00
Yet another NASA sponsored contest... And look, you can even win a Segway!! Elgin Clock Math and Science 5 17-09-2003 12:26


All times are GMT -5. The time now is 08:59.

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