Quote:
Originally Posted by Mark McLeod
From the statuses you've described it sounds like your PC communicates just fine with the roboRIO.
Is it just a problem with LabVIEW that you are describing?
Are you attempting to Run from Robot Main?
Are you able to use Build Specifications to Build and Run as startup?
Is there something else important that I didn't catch from your descriptions?
|
Firstly, I don't believe that it is an issue with the LabVIEW beings as though that I was able to get the code to work on our kit bot before we re-mapped the electronics to accommodate for the restrictions on our official robot. Secondly no I have not been running the code from Robot Main however I have and will continue to connect to the RoboRio in the VI tree before deploying any code what so ever. I am able to use the Build Specifications to Build the code. I am however unsure on what you mean by the phrase "Run as Startup." I'm wanting to say that you are referring to deploying that build to the RoboRio and being able to run it just fine however again I'm not exactly sure on what you mean by that. Finally, I don't think you have missed any details that I have mentioned in previous comments. I can ping the system however I just can't get it to respond to anything that I request it to do. One of our guys is saying that their could be the possibility that the board is dead in some ways but I personally don't think so, I simply think that there's a communication issue that's going on between the radio and the RoboRio because I can ping both the modem and the RoboRio just fine but simply can't connect through LabVIEW.