Go to Post The Tekin's used to constantly suffer from spontaneous combustion, it was extremely frustrating how often they would go. - Kingofl337 [more]
Home
Go Back   Chief Delphi > Technical > Programming > Java
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 01-02-2017, 19:00
JoeyDaPanda's Avatar
JoeyDaPanda JoeyDaPanda is offline
Registered User
AKA: Joey
FRC #6324 (The Blue Devils)
Team Role: Programmer
 
Join Date: Nov 2016
Rookie Year: 2017
Location: Salem NH
Posts: 5
JoeyDaPanda is an unknown quantity at this point
VictorSP causes "Robots don't quit!"

Basically the title. When we use VictorSP's in Eclipse it gives us the "Robots dont quit" error in the driver station. The console updates so quickly so we cant copy it out. Any help appreciated.
Reply With Quote
  #2   Spotlight this post!  
Unread 01-02-2017, 19:19
cgmv123's Avatar
cgmv123 cgmv123 is offline
FRC RI/FLL Field Manager
AKA: Max Vrany
FRC #1306 (BadgerBOTS)
Team Role: College Student
 
Join Date: Jan 2011
Rookie Year: 2011
Location: Madison, WI
Posts: 2,089
cgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond repute
Re: VictorSP causes "Robots don't quit!"

"Robots don't quit" (at least in this context) likely means you're not sending commands to the Victors fast enough. Try disabling MotorSafety using:
Code:
VictorSP.setSafetyEnabled(false);
__________________
BadgerBOTS Robotics|@team1306|Facebook: BadgerBOTS
2016 FIRST Championship Tesla Division | 2016 Wisconsin Regional Engineering Inspiration Award

2015 FIRST Championship Carson Division | 2015 Wisconsin Regional Chairman's Award

2013 FIRST Championship Curie Division | 2013 Wisconsin Regional Chairman's Award

2012 FIRST Championship Archimedes Division | 2012 Wisconsin Regional Engineering Inspiration Award, Woodie Flowers Finalist Award (Lead Mentor Ben Senson)

Reply With Quote
  #3   Spotlight this post!  
Unread 01-02-2017, 20:57
tomy tomy is offline
Registered User
FRC #3038 (I.C.E. Robotics)
Team Role: Mentor
 
Join Date: Jan 2009
Rookie Year: 2009
Location: Stacy, Minnesota
Posts: 511
tomy has a spectacular aura abouttomy has a spectacular aura about
Re: VictorSP causes "Robots don't quit!"

Quote:
Originally Posted by cgmv123 View Post
"Robots don't quit" (at least in this context) likely means you're not sending commands to the Victors fast enough. Try disabling MotorSafety using:
Code:
VictorSP.setSafetyEnabled(false);

That wouldn't be legal for comp would it?
Reply With Quote
  #4   Spotlight this post!  
Unread 01-02-2017, 21:04
Bkeeneykid's Avatar
Bkeeneykid Bkeeneykid is offline
#wheatcoastneatcoast
AKA: Devin Keeney
FRC #1982 (Cougar Robotics); Season Long Fantasy FIRST (F3)
Team Role: Leadership
 
Join Date: Feb 2015
Rookie Year: 2015
Location: Lenexa, Kansas
Posts: 367
Bkeeneykid has much to be proud ofBkeeneykid has much to be proud ofBkeeneykid has much to be proud ofBkeeneykid has much to be proud ofBkeeneykid has much to be proud ofBkeeneykid has much to be proud ofBkeeneykid has much to be proud ofBkeeneykid has much to be proud ofBkeeneykid has much to be proud of
Re: VictorSP causes "Robots don't quit!"

Quote:
Originally Posted by tomy View Post
That wouldn't be legal for comp would it?
This is completely legal. There's no rule that require you to have safety enabled on your motor controllers (or that you even use the three official languages, so issues arrive with that). It simply means that your motor controllers will not continue to move your motors if they get disconnected and stop being updated. It's usually a good idea to keep this on, but not always.

If you can use NetConsole or RioLog to copy out the error exactly, that would be nice. The "Robots Don't Quit!" error simply means your code has crashed and is now restarting.
__________________

F4 Network Website Designer

2010-2012: A Whole Buncha FLL Teams; Team Spirit, Gracious Professionalism Award winner
2015-Current: FRC 1982, Captain, Electrical Lead
Beginning FIRST Volunteer

Moderator on the FIRSTwiki
Reply With Quote
  #5   Spotlight this post!  
Unread 01-02-2017, 21:05
cgmv123's Avatar
cgmv123 cgmv123 is offline
FRC RI/FLL Field Manager
AKA: Max Vrany
FRC #1306 (BadgerBOTS)
Team Role: College Student
 
Join Date: Jan 2011
Rookie Year: 2011
Location: Madison, WI
Posts: 2,089
cgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond reputecgmv123 has a reputation beyond repute
Re: VictorSP causes "Robots don't quit!"

Quote:
Originally Posted by tomy View Post
That wouldn't be legal for comp would it?
Under what rule? There are no restrictions on software as long as it
  1. Is publicly released before kickoff/developed after kickoff.
  2. Runs on a RoboRIO with the correct firmware/image requirements.
__________________
BadgerBOTS Robotics|@team1306|Facebook: BadgerBOTS
2016 FIRST Championship Tesla Division | 2016 Wisconsin Regional Engineering Inspiration Award

2015 FIRST Championship Carson Division | 2015 Wisconsin Regional Chairman's Award

2013 FIRST Championship Curie Division | 2013 Wisconsin Regional Chairman's Award

2012 FIRST Championship Archimedes Division | 2012 Wisconsin Regional Engineering Inspiration Award, Woodie Flowers Finalist Award (Lead Mentor Ben Senson)

Reply With Quote
  #6   Spotlight this post!  
Unread 01-02-2017, 21:24
tomy tomy is offline
Registered User
FRC #3038 (I.C.E. Robotics)
Team Role: Mentor
 
Join Date: Jan 2009
Rookie Year: 2009
Location: Stacy, Minnesota
Posts: 511
tomy has a spectacular aura abouttomy has a spectacular aura about
Re: VictorSP causes "Robots don't quit!"

Quote:
Originally Posted by tomy View Post
That wouldn't be legal for comp would it?
I meant it as a question not as a statement.
Reply With Quote
  #7   Spotlight this post!  
Unread 01-02-2017, 22:05
Joe Ross's Avatar Unsung FIRST Hero
Joe Ross Joe Ross is offline
Registered User
FRC #0330 (Beachbots)
Team Role: Engineer
 
Join Date: Jun 2001
Rookie Year: 1997
Location: Los Angeles, CA
Posts: 8,600
Joe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond repute
Re: VictorSP causes "Robots don't quit!"

Quote:
Originally Posted by cgmv123 View Post
"Robots don't quit" (at least in this context) likely means you're not sending commands to the Victors fast enough. Try disabling MotorSafety using:
Code:
VictorSP.setSafetyEnabled(false);
No, that would say that outputs not updated often enough. Like Bkeeneykid said, it means the code crashed. One common cause is resource overallocation (eg opening PWM 1 twice).
Reply With Quote
  #8   Spotlight this post!  
Unread 02-02-2017, 18:17
JoeyDaPanda's Avatar
JoeyDaPanda JoeyDaPanda is offline
Registered User
AKA: Joey
FRC #6324 (The Blue Devils)
Team Role: Programmer
 
Join Date: Nov 2016
Rookie Year: 2017
Location: Salem NH
Posts: 5
JoeyDaPanda is an unknown quantity at this point
Re: VictorSP causes "Robots don't quit!"

To anyone still lurking:

Just to make sure, where do I put the import and following code?

Currently the related code we have is in our Robot.java

Code:
VictorSP V1 = new VictorSP(1); // Left motor
VictorSP V2 = new VictorSP(0); // Right motor

V1.set(1); // Set speed to 1
V2.set(1); // Set speed to 1
Reply With Quote
  #9   Spotlight this post!  
Unread 03-02-2017, 22:42
otherguy's Avatar
otherguy otherguy is offline
sparkE
AKA: James
FRC #2168 (The Aluminum Falcons)
Team Role: Mentor
 
Join Date: Feb 2010
Rookie Year: 2009
Location: CT
Posts: 443
otherguy is a splendid one to beholdotherguy is a splendid one to beholdotherguy is a splendid one to beholdotherguy is a splendid one to beholdotherguy is a splendid one to beholdotherguy is a splendid one to beholdotherguy is a splendid one to behold
Re: VictorSP causes "Robots don't quit!"

Quote:
Just to make sure, where do I put the import and following code?
That depends on the type of project you've created. If it's a command based robot project, then hardware components (like motors) are usually encapsulated and controlled through a "Subsystem" class.

There's example code for subsystems here: https://wpilib.screenstepslive.com/s...ple-subsystems
and general information on the command based project here: https://wpilib.screenstepslive.com/s.../13809/c/88893

If you're using just a plain iterative robot project without calls to a Scheduler class / commands / subsystems, then the motor objects would typically be class variables of Robot.java, instantiated in the constructor, and the .set() methods would typically be called from within the TeleoperatedPeriodic() and AutonomousPeriodic() methods depending on what you're trying to do.


Regarding imports, those always go in the same place within a .java file. At the top preceding the line that specifies the class name. Eclipse will automatically put it in the right spot if you right click the red underlined text and select the add import option.
__________________
http://team2168.org
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 01:14.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi