View Single Post
  #2   Spotlight this post!  
Unread 18-01-2015, 20:43
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,113
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Double Solenoid Problem

Quote:
Originally Posted by Nunez4296 View Post
The VI for the code is an edited Tank Drive example written for a 6 CIM tank with ball shifters and a compressor.
Examples are meant to show you how to do things and try them out. They are not intended to be edited significantly, and they certainly should not be turned into a program for your competition robot. One of the LabVIEW tutorials should tell you how to take what's in an example and put it in a true robot project.

Quote:
I'm not sure what a "refnum" is, could you elaborate please?
The principal output of an Open vi is a RefNum that defines the resource that was opened. Every other vi that uses that resource -- a Motor Set, a Joystick Get, etc. -- takes the RefNum as an input.

In the typical robotRIO project, all of the Opens are done in Begin.vi, and all of the RefNum values are saved using the RefNum Registry using RefNum Set functions. In Teleop.vi, and in every other place needing to use them, the RefNum values are retrieved from the Registry using RefNum Get functions.

Quote:
The solenoid open is outside of the loop and is set for a double solenoid.
That's not enough detail for me to be able to ask better questions. I need to know what all of its inputs are.

Quote:
The other issue that we are running into is that after a few minutes of driving and shifting, the robot will cycle power and we will loose connection.
What makes you think it is cycling power? Does the Robot Signal Light turn off? Do you get any indication on the Driver Station of the battery voltage dropping? Do the DS logs show the reason for the lost connection? Are you using the USB connection, a wired ethernet cable, or wireless? I apologize for the flood of questions, but I think you're going to have to give a lot more information before you can get good help.
Reply With Quote