Unable to connect to Real Time Target

[gamegeek1995]

The IP target for the robot is correct, I changed the imaging to "run at startup", Remote Dashboard was selected, and we restarted the entire coding project using what we the links you provided said to use. We also put in a test Jaguar and our regular Victor 888 motor, and neither worked. I guess we'll have to wait until after the update to see if we can get it running, because I'm honestly out of ideas entirely (save for going back to Java & Netbeans, perhaps).

[Greg McKaskle]

The update only fixes what is broken.

Please describe what you are doing, what works, and what doesn't.

Greg McKaskle

[gamegeek1995]

All of the information that I have for our robot.

Electrical: Standard battery, Power Distribution Board, circuit breakers, wires to the Victor 888 & to the Jaguar. Fan wires on Victor 888 are wired and the fan runs when power is connected.
cRIO is hooked up, all lights are lit and communication is constant (able to ping, ect.)
Digital Sidecar appears to be hooked up, have yet to go over it with a multimeter as we did with the motors, but it is hooked up exactly as the guides online showed.
Orange "safety light" is not lit at any time
Wifi is placed and powered, but not currently used.
The motor controllers connect to two large motors below our electrical panel.

Software:
cRIO Imaged with our team number (10.47.1.2), for LabVIEW Software, with "Run at startup" selected. None of the toggle switches are on. It is also not in safe mode.

DriverStation shows green lights for communication, joysticks (we've tested atonimously and with joysticks), and robot code. Under "setup", team number is set as 4701, and Remote Dashboard light is perpetually lit. Dashboard IP is 10.47.1.6

The LabVIEW project's name is "AlanAndersonGuideProject-temp3.lvproj" (a documentation method, and it's our third attempt. Don't ask, this was made by a frustrated coder.)
Under items:
My Computer
-Sim Support Files (have not touched any of these subsets, so I'll leave it as this)
-Robot Simulation Readme.html (not using the simulation at the moment)
-Dependencies (untouched)
-Build Specifications (untouched)

RT CompactRIO Target (10.47.1.2)
-Team Code (Inside is "Begin, Autonomous Independent, Teleop, Test, Disabled, Vision Processing, Periodic Tasks, Robot Global Data, and Finish".vi) (all of these have been untouched)
-Support Code (Inside is Elapsed Times.vi)(untouched)
- Robot Main.vi (untouched)
-Simple Motor Control.vi
This code has the following:

-BEGIN BLOCK OF CODE

FRONT PANEL
stop
[Stop Button]
output
<up and down arrows> [0] (when running our code, we changed this value from 0 to 1 with no effect.)

BLOCK DIAGRAM
Starting from the bottom left and moving up the wire (which I'm informed is actually a while loop?)-
an [i], with nothing connected to it.
A green/brown wire, connected to [watchdog], which is set to OPEN, which reaches across to [watchdog] SET ENABLE, then to [watchdog]CLOSE.
[watchdog]SET ENABLE has a pure green line to the left of it, leading to an [f] which changed to [T] when I clicked on it (true/false?)
a pink wire, which connects all three [watchdog]s in the order I listed.

On the left of the "while loop" is something that says [DrwStn] Start COM. It's not connected tot eh while loop. On the same level as it, to the right, is a watch symbol with "10" connected to it. It is also not connected to the loop. Then a [stop] box, with a green wiring connecting it to the right side of the while loop. On this green line, there is a stop sign connected. On the right, connected directly where the green line and while loop meet, there is [DrwStn] STOP comm (way to be consistent with capitalization, lol)

Back on the left side of the while loop, moving up is a brown wire connected to the left to [Motor] Open Jaguar (Jaguar), which has 2 blue wires readying "Digital Module 1" and "PWM 1" (it is connected to slot 1 on our Digital Sidecar). It also has a pink wire connected it to it, linking it to the while loop. The pink and brown wires go to [Motor] Set Output in the middle of the while loop, which also has Output[DBL] 1.23 connected to it. On the right of [Motor] Set Output is the pink and brown wire connected it to [Motor] Close, which is also on the while loop.

Finally, at the top of the while loop, on the left is a red wire connecting to [Joystick] Open, which has a blue wire leading to the left which goes to USB 1. This red wire connects to [Joystick] Get Axis, and this attatched to a blue wire which leads to Axis 1. Back at [Joystick] Get Axis, there is a red wire which leads to [Joystick] Close.

This is the code we've been trying to run on the robot (with the only changing variables being the Jaguar to a Victor, and the changing of PWM slots.)

-END BLOCK OF CODE


-Dependencies (untouched)
-Build Specifications (inside is FRC Robot Boot-up Deployment)



Some possible idea's I've developed: Digital Sidecar? Is it working right, and how do I test this?

[Alan Anderson]

It sounds like you properly created a 2013 competition robot project, but then you just copied in that example instead of using the programming framework. Remove the Simple Motor Control.vi from your project and follow the tutorial instructions included in LabVIEW. Until you start doing fancy stuff, all your robot programming will be in the Team Code VIs.

You say the orange BFL (Big Flashy Light) remains unlit. Does the green LFL (Little Flashy Light) on the Digital Sidecar next to its connector also remain unlit? What about the three green power LEDs on the Digital Sidecar? What size circuit breaker is feeding the Digital Sidecar power input?

[Greg McKaskle]

Good job describing things. This allowed for us to better troubleshoot. Hopefully Alan's suggestion works for you. If not, describe what you want it to do and what seems to fail.

Greg McKaskle

[DELurker]

Originally Posted by Greg McKaskle

The known issues list explains that his is caused by the current version of the SmartDashboard implementation on the robot. A patch is expected to be released early next week, and there is a simple workaround which is to close the dashboard application and any other SmartDashboard clients you may be running such as the Java SmartDashboard or RoboRealm.

The issue occurs when the code is deployed as a startup app, and you then attempt to abort it and kick it out, typically to run something else. The session handler for SmartDashboard refuses to quit and the RT system puts up the Waiting ... dialog.

Greg McKaskle

Greg, could you post a link to the known issues list? Our team has been fighting this problem for several days as well, but we were unaware of the known issues list.

[gamegeek1995]

Originally Posted by Alan Anderson

You say the orange BFL (Big Flashy Light) remains unlit. Does the green LFL (Little Flashy Light) on the Digital Sidecar next to its connector also remain unlit? What about the three green power LEDs on the Digital Sidecar? What size circuit breaker is feeding the Digital Sidecar power input?

Not sure what the LFL is (and I'd honestly be surprised if the 'F' stands for flashing )- I don't see any small green flashy lights. The three green power LEDs on the Digital Sidecar are lit though, and the 20amp Circuit breakers that came with our kit are installed above its WAGOs. We're about to go through the tutorials for LabVIEW and try to understand this infernal GUI language.

Question: Is there a way to check if our issue is the ribbon cable?
Edit: So, we didn't put the ribbon cable in a press. We just did that and will test our stuff again to see if it will work. I'm glad I randomly decided to browse the forums and find the Java post about that being their issue. Now I feel like I'm the dumbest human being in the world. I'll tell you if it works.
Edit2: UPON CONNECTING THE NEW RIBBON CABLES, THE BIG ******* ORANGE LIGHT BEGINS TO BLINK. To the Cliffs of Dover!
EDIT3: AFTER RUNNING ROBOTMAIN.VI, IN THE PROGRAM I DESCRIBED EARLIER (NO CHANGES), THE ROBOT MOVESSSS AND IT MOVESSS CORRECTLYYYYYYYYYYYY YESSSSSSSS VICTORRYYYYYYYYYYYYYYYY!!!!11!!111!!1!!

[gamegeek1995]

Got the wireless router config'd and it runs autonimously. Thanks for the help guys

[Greg McKaskle]

I found the known issues list here ... http://wpilib.screenstepslive.com/s/...software-notes

Greg McKaskle

[DELurker]

Originally Posted by Greg McKaskle

I found the known issues list here ... http://wpilib.screenstepslive.com/s/...software-notes

Greg McKaskle

Thanks. I've forwarded the link on to our programming and controls teams.