Hey I was trying to get the ZomB dashboard to work on our classmate. I’m not sure if it’s related but not only is the robot unresponsive, I am also unable to re-image it. I’ve tried reinstalling the imager from the disk and putting on the updates but it still fails to image it. I’ve also tried the thing where you try to image it in safe mode and it reformats it but it still won’t work. It also gives me different error messages when I try it different times. They are included. It was also suggested that I somehow revert to the factory image and then try again but I was unable to find out how. I’m also unable to connect via ftp but I can ping it. Help?
error.txt (789 Bytes)
error2.txt (326 Bytes)
error3.txt (285 Bytes)
error4.txt (656 Bytes)
error.txt (789 Bytes)
error2.txt (326 Bytes)
error3.txt (285 Bytes)
error4.txt (656 Bytes)
Try setting the safe-mode switch to on and then try to do a full wipe and reimaging of the cRIO. The multiple errors you’ve been getting seem to be erratic (I got them as well when trying to emergency reimage my team’s cRIO), so just keep trying.
Maybe someone knows for sure what they’re coming from? I can understand what they’re saying, but it’s still an internal problem somewhere.
Nope. Still didn’t work. I’ve tried that before too. Am I suppose to name is something specific? I’ve tried Crio CRio and cRIO but they didn’t work. Is it even relevant?
Posting for a programming mentor on our team…
We’re having a similar problem with our 2008 cRio. We’ve discovered that we can’t seem to get the CAN bus plugin for the black jag bridge to work. We’re using Java as our coding language and if I disable the console port on the cRio to free it up to be used for the CAN bus, the cRio becomes non-responsive including our ability to get at the ftp ports. We can still ping it. No other response though.
If we disconnect the CAN bus and reenable the cRio’s console serial port, it seems to act as normal.
Maybe this will help you debug your problem.
We’ve ordered a 2CAN in hopes that we can work around the problem.
Trying to Help
Hmmm. I managed to rule out one of the error messages (something about having a wrong input parameter). You need to name the crio “Crio” or it won’t work.
OK, I got past another error (I guess it’s called Error 60). I had to disable the wireless thing on my laptop. Now the Error that comes up is 15550. I googled the error message and found this: http://digital.ni.com/public.nsf/allkb/0C3DADDE199AE8F9862574BE0059F494 I don’t think it’s frc related but maybe someone can make sense of it or find some other solution
Nvm… I restarted my laptop and it will image now >_< strange.
imaging can be a big task for a cpu, glad it worked for you… if it happens again i suggest using the no-app switch instead of safe mode… thats what they had us do last year… it works much better in my opinion… once you start imaging it goes into safe mode automatically
Keep in mind that the No App switch only keeps the cRIO from starting up LabVIEW programs. A deployed C++ program will run regardless of the state of the switch.