We are having an issue when we try to deploy our code. We get two lines of errors:
[crio] task 0x2869fd8 (mdns resolve) deleted: errno=0 (0) status=0 (0)
[crio] task 0x2bff138 (mdns resolve) deleted: errno=0 (0) status=0 (0)
Then the process just stops and we get solid act/link lights on both the crio and the bridge and the PC
Were there any other messages in the console window?
Can you verify that you can ping the cRIO? You should open a CMD window on your PC that is connected to the robot and type “ping 10.x.y.2” where x.y are your team number. If you don’t get a response, there is a connectivity problem.
You might also try to disable the windows firewall on your system to see if that helps.
Let us know what happens after you try those things.
Yes we can ping the crio and the pc itself. The dipswitches are all electronic and are set off in the flashing utility. We even reflashed with the image a second time in case it was corrupted. I printed a copy of some other people’s error messages and it appears we are not even starting to load the code. My programming teams thinks they may have forgotten to install or update a couple things. We are also istalling all the software on the Classmate to assure it is not a laptop issue.
We did a quick build on Saturday and it actually created more issues than if we followed the step by step instuctions. If you have any other suggestion, let me know and I’ll post back tonight with any updates and post the entire output file.
Our rookie team is treading same waters. We may have a corrupted Crio and of course we cannot deploy our java code. If your team was able to get it worked, can you let us know how to’s?
Note: Yesterday some of our team members fried two of the jaguars …
Try hitting the “play” (green triangle) button rather than the debug button. It looks like its a debugger issue and not a deployment issue. I think you can also use F6.
Did you try connecting the Debugger? See the instructions starting on the bottom of page 9 of Getting Started with Java (or run the program without debugging the way Brad posted above)
We get the same error whether we run in debug mode or not. Happens on both development laptops as well as the classmate. After we perform this procedure we get the connected light and robot code light in driver’s station but the jaguars do not go solid green and nothing happens.
Actually, the status code of 0 at the end of your previous log is not an error. Are you sure that your program isn’t deploying? Is it possible that the program just has an error in it and isn’t doing what you’re expecting?
Can you try one of the default programs like the simple robot template, and put in some print statements and see if anything comes out on the console? Also, you might want to take out some of the motor code to make it easier.
Have you tried Enabling the robot with the Driver Station? Did you rework your DB-37 cable? What is the light next to the 2 pin header on the Digital Sidecar doing? Are all 3 lights on the Digital Sidecar brightly lit?
This is the sample code suggested to use in the getting started package. I’ll check the lights in the AM. When we enable it nothing happens. We did not do anything with the DB37, should we have?
DB37 Rework
Please note that many, if not all, of the DB37 cables shipped in the 2012 Kickoff Kits were assembled incorrectly. We have posted more information about the issue as well as instructions to fix the cables here.
Ok, we managed to get the problem fixed. The Crio is now working and the robot can now move in tank drive. The fix for the DB37 cable was all that we needed.
Thank you all for the help. :7
We had had the same error as mentioned in this thread, We took the advice and checked our cable and there was an issue, but that didn’t solve that. We are running off of Java on Linux. We also reimaged our cRio to be compiled with LabView and the code compiled onto the robot. The java compiler freezing hasn’t changed whether the cable was attached or not.