Chief Delphi - Problems with cRIO

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)

- FRC Control System (http://www.chiefdelphi.com/forums/forumdisplay.php?f=176)

- - Problems with cRIO (http://www.chiefdelphi.com/forums/showthread.php?t=99747)

Problems with cRIO

We're having trouble connecting to our cRIO.

When trying an error like this appears:

Quote:

Unable to complete operatuib because of unexpected error: error -2145024809 occured at nisyscfg.lvliv:Initialize

(Helper).vi

Possible reason(s):

LabVIEW: (Hex 0x80070057) One or more arguments are invalid.

==============================

NI System Configuration: (Hex 0x80070057) Invalid Parameter.

Complete call chain:
nisyscfg.lvlib:Initialize (Helper).vi
2012_nisyscfg_Initilize.vi
ConfigUtiltiy.lvlib
DiscoverDevice.vi:
ConfigUtiltiy.lvlib:
ReImageTarget.vi
ConfigUtility.lvlib:Dialog.vi

And another error some other times:

Quote:

Unable to complete operation because of unexpected error:

Error 1 occured at TCP Read in NI_InternetTK_Common_VIs.lvlib: TCP Read xTP Reply.vi:14->
NI_InternetTK_FTP_VIs.lvlib:FTP Get Command Reply.vi:13->
NI_InternetTK_FTP_VIs.lvlib:FTP Open Session.vi->
ConfigUtility.lvlib:2012_FTPOpen.vi->
ConfigUtlity.lvlib:FRC 2012_FTP Get File.vi->
ConfigUtility.lvlib:OpenRemoteConfiguration.vi->
ConfigUtility.lvlib:ReImageTarget.vi->
ConfigUtility.lvlib:Dialog.vi

Possible reason(s):

LabVIEW: An input paramter is invalid. For example if the input is a path, the path might contain a character not

allowed by the OS such as ? or @.

We've no idea where this is coming from.

We're using the older, 2009 cRIO, not the cRIO-II.

Re: Problems with cRIO

I've seen the second error with an older cRIO, too.

I was able to get it to work eventually, but I haven't had time to experiment with variations yet.
Here are some of the things I did:

Disabled all NIC's but the one Ethernet port I was using for the cRIO
Did a Safe Mode reformatting (Safe Mode dip switch. reset the cRIO, run Imaging tool, turn Safe Mode switch back off, reset cRIO)
Followed by a regular Imaging

Re: Problems with cRIO

We've seen this error also.
If you run 'ipconfig' from the 'cmd' window and see multiple ip-addr's listed for your
ethernet port, the FIRST cRIO imaging tool fails.

You can delete the extra ip-addrs with 'netsh'.