View Single Post
  #7   Spotlight this post!  
Unread 05-01-2016, 12:55
cpapplefamily cpapplefamily is offline
Registered User
FRC #3244 (Granite City Gearheads)
Team Role: Mentor
 
Join Date: May 2015
Rookie Year: 2015
Location: Minnesota
Posts: 242
cpapplefamily has a spectacular aura aboutcpapplefamily has a spectacular aura about
Re: PID with encoder

Quote:
SoftwareBug2.0
Quite Sloppy gear box. Is a likely problem. I did try to place the wheel attach on the ground to try and eliminate the backlash and is why I asked about setting the max speed. (answered possibly by GeeTwo)

Quote:
virtuald
I did just see the Velocity mode in RobotBuilder and was going to play some with changing that. I was not aware this is new for 2016.

Quote:
BL0X3R
We are using Command Based Java

As virtuald stated and I found it was set to velocity.

Is there any other system controlling the motor?
No this is a fresh program with only the few components declared.

Some of my ideas posted where me brain storming for tonight to get the community input. Thanks for the kind words too.

Quote:
phurley67
Graphing is a great idea. I need to show them how to get the data in the smartdashboard displayed this way and see the power of the tool. I remember myself doing this last spring when I was testing the new PDP current draw of each channel. Thanks for reminding me to show this to them.

Quote:
GeeTwo
Shakes yes like over shoot. I could not see if it made a revolution. Graphing and trying to use the "setOutputRange" the others have mentioned should help identify this. We did have the encoder channels swapped and seen the motor run away with the error growing not closing.


Thanks to all lots of great ideas given and confirmed.