|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools |
Rating:
|
Display Modes |
|
#4
|
|||
|
|||
|
Re: Unable to connect to Real Time Target
I went through http://www.usfirst.org/sites/default...trolSystem.pdf
for the second time, this time configuring everything for 10.47.1.2. The only change is that, when building our LabView code, it restarted the cRIO first. Communication is lit, Joysticks are lit, and Robot Code is lit whenever we ran robot main or "run as startup" for the deployment. The Driver Station is enabled, but none of the joysticks do anything. Right clicking on "Basic Move.vi" and selecting "Deploy" allows it to go through a long deploying something or other. However, robot code light is red. Right clicking on FRC Robot Boot-up Deployment and selecting "Deploy" causes it to do the deploying, but shorter, then have a red light on Robot Code still. Right clickingon RobotMain.vi and selecting Deploy causes, once more, lots of deployment and results in a red robot code light. Right clicking on RobotMain.vi and selecting Run causes lots of deployment, a launching of the Robot Main.vi window (with a large Finish button), and a green light on robot code. When I hit "enable", neither joystick does anything and there is no noticable effect. Right clicking on BasicMove.vi and selecting Run causes it to "Load" a variety of what I can only assume to be modules. Then it deploys stuff, I hit enable (Teleoperated Enabled), and no joysticks do anything. Right clicking on Build Specifications and selecting "Build All" causes it to initialize a build for a large amount of time, then "the build is complete. You can locat the build at C;\users\developer\documents\labVIEW Data\2013 Robot Project\Builds I'm not sure if I'm supposed to do anything with that last build, or if I'm deploying the code wrong or something. I made this very detailed so hopefully it'll be more useful than the array of "robot code isn't working help plz". Edit: Upon closing LabView for the day, I got "During the last run of LabVIEW 2012 one or more internal warnings were detected and logged." Report ID: 61743539-83c4-4e8d-af0f-e67db3182bf2 Last edited by gamegeek1995 : 25-01-2013 at 17:04. |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|