View Single Post
  #4   Spotlight this post!  
Unread 20-12-2015, 22:31
Mr. Lim Mr. Lim is offline
Registered User
AKA: Mr. Lim
no team
Team Role: Leadership
 
Join Date: Jan 2004
Rookie Year: 1998
Location: Toronto, Ontario
Posts: 1,125
Mr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond reputeMr. Lim has a reputation beyond repute
Re: Formatting a Crio with 2014 image

Quote:
Originally Posted by de_ View Post
Thanks for the info. Unfortunately it did not work

So I retrieved 2 more cRIOs from storage, one 4 slot and one 8 slot.
The 8 slot behaved identically to the first unit (also an 8 slot) - "Rebooting CompactRIO device..."

The 4 slot unit was found by macc address and reported an unknown image. It did have a slightly different team ID for testing. Formating it to 1310 DID work with all the expected update messages.

I do note that when running the Network console to watch the cRIO consoles, on the 8 slot devices I see a number of threads (multiple Command Server TCP connection threads and FTP Server Connection Thread) terminating. This doesn't sound good as FTP is the method through which things are downloaded.

More head scratching...
For the 8-slot units, all I can suggest is trying to image them in safe mode by flipping the corresponding DIP switch.

Also, if they're really old units, they might lack the gasket that keeps swarf out of them. It might be worth opening them up and blowing them out. I've had at least one cRIO act completely wonky communications-wise, and was unimageable. Cleaning out its innards resolved the problem.
__________________
In life, what you give, you keep. What you fail to give, you lose forever...
Reply With Quote