|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
needy CRIO
Okay- I was apparently having an update issue earlier. I couldn't re-image the Crio because I didn't run my updates in the proper order... for different software... >.<
Anyhow, that has been resolved but I still am still having issues with the Crio. I tried to re- image it but it got stuck rebooting. The driver station, when I tried to connect, showed I had robot and bridge but no DS radio. Should I: attempt to re image again / hard reset the Crio / or some other third thing? If I reset the Crio- does anyone know how? I obviously can't just hit the reset button. This is FIRST after all. |
|
#2
|
||||
|
||||
|
Re: needy CRIO
I changed my subnet to 255.255.255.0 and the switches were there so i reimaged and got the following error:
Unable to complete operation because of unexpected error: Error -2147220309 occurred at nisyscfg.lvlib:Restart.vi:1 Possible reason(s): NI System Configuration: (Hex 0x800404AB) Failure to send command. Complete call chain: nisyscfg.lvlib:Restart.vi:1 ConfigUtility.lvlib:2012_FormatSystem.vi ConfigUtility.lvlib:ReImageTarget.vi ConfigUtility.lvlib ialog.vi |
|
#3
|
||||
|
||||
|
Re: needy CRIO
This might be a dumb question, but meh whatever.
Are you making sure the cRIO isn't in safe mode? |
|
#4
|
||||
|
||||
|
Re: needy CRIO
|
|
#5
|
|||||
|
|||||
|
Re: needy CRIO
You probably don't have a "DS radio", and you probably don't need it. That was a Linksys router used to create the robot network for the black Linksys bridge to connect to. It was necessary because the old QuikByte blue box driver station only had wired Ethernet capability. It was configured at IP address 10.te.am.4, and that's what the "DS radio" Communications indicator on the Driver Station diagnostics tab is looking for.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|