Go to Post In the long run, you don't remember your ranking points, you remember the lessons and friendships from when you were on a robotics team in high school. - smurfgirl [more]
Home
Go Back   Chief Delphi > Technical > Programming > C/C++
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
  #25   Spotlight this post!  
Unread 01-16-2012, 07:28 PM
rogerroger rogerroger is offline
Registered User
FRC #1111
 
Join Date: Jan 2012
Location: Edgewater
Posts: 2
rogerroger is an unknown quantity at this point
Re: Imaging tool for the new 4-slot cRIO

Quote:
Originally Posted by mikets View Post
Thanks for the info. I got it successfully formatted. Here is a quick way of how I did it without disabling/reconfiguring a lot of things on the network.
- Disabled the wireless adapter of my laptop.
- Configure my wired ethernet adapter on my laptop to have a static IP address of 10.xx.xx.6 with a mask of 255.255.255.0.
- Connect my laptop to the 4-slot cRIO directly with an ethernet wire. I don't need a cross over cable because either the 4-slot cRIO or my laptop has autosense.
- Power up the cRIO and ping it from my laptop to make sure it sees it (ping 10.xx.xx.2).
- Run the cRIO imaging tool and select all the options and firware you need and click Apply.
- When it finished, you are done.
- Remember to configure your laptop's ethernet adapter back to auto IP address and auto DNS.
By doing the above, the only network configuration I changed was my laptop's ethernet adapter. The resulting network will have only my laptop and the cRIO with a narrow mask of 255.255.255.0. So the enumeration of devices should be very quick.
Curious though, since the imaging tool already did enumeration of the cRIO and showed its proper IP address (10.xx.xx.2) and I have "selected" the cRIO, why can't the imaging tool just use the 10.xx.xx.2 IP address to communicate with the cRIO when formatting instead of trying to enumerate it again on a wider network mask (255.0.0.0)? Or at the very least, lengthen the timeout to allow enough time to enumerate the subnet. After all, the initial "scanning" allowed enough time to "find" the cRIO so there is no reason why "format reboot" cannot use the same timeout length.
This worked for our team. Thanks for the post.

Go FIRST!
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


All times are GMT -5. The time now is 09:32 AM.

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