View Single Post
  #3   Spotlight this post!  
Unread 14-02-2015, 21:38
cstelter cstelter is offline
Programming Mentor
AKA: Craig Stelter
FRC #3018 (Nordic Storm)
Team Role: Mentor
 
Join Date: Apr 2012
Rookie Year: 2012
Location: Mankato, MN
Posts: 77
cstelter will become famous soon enough
Re: PID Commands and PID Editors

Our subsystem controllers would show up in Live Window, but then when hitting the green/red enable button, nothing would happen. We had print statemenets in the usePIDOutput and returnPIDInput and they were never called with the enable flag being green or red. Perhaps we were just trying to use it wrong. I'm not sure. During Teleop though, we saw the PID subsystems were running fine.

This was using SFX Live Window. We finally just pushed past the problem by using some SmartDashboard.putNumber/getNumber calls for P, I, D, and Setpoint and a special command that reads them and then reset the PID.

We have about 4 more PIDs to tune, so figuring out the problem would save us a bit of effort. Anyone have similar experience?

We use RobotBuilder and the calls to LiveWindow.addActuator (not addSensor as suggested in previous case) are automatically generated.

Does anyone have a suggestion?

In scanning PIDCommand (we have only two) I don't see that RobotBuilder automatically puts one on LiveWindow. Is there a difference between calling AddActuator with 3rd argument getPIDController() and calling AddSensor? If so, perhaps this is just a bug in RobotBuilder's boilerplate for PIDSubsystem.
Reply With Quote