• Welcome to Redshift Project Depot.
 
Main Menu

Recent posts

#91
Robot Software / Re: Robot Hardware Testing Tas...
Last post by Benjamin K - February 11, 2018, 04:11:57 PM
Autonomous Mode Testing

       
  • Adjust MIN_SPEED in RotateAngle(), DriveDistance(), and CalculateSonarDistance() commands
  • Adjust MAX_SPEED in RotateAngle(), and DriveDistance()
  • Adjust the Speed constants in AutoAction()
  • Test the Robot do scale and switch commands(Robot on right and left) for autonomous. When the robot is aligned
  • Do the same with the robot pointing slightly to the left
  • Do the same with the robot pointing slightly to the right
  • Test Baseline
  • Do Left Switch and Right Switch from center positions
#92
Robot Hardware / Spare Parts
Last post by Saharsh Y - February 11, 2018, 01:45:49 PM
Arm
Claw

  • Coasters
  • Snowblower Motor

    • We Already have a lot of these, but we don't know of they work
Wrist

  • ⅜ Keyed Shaft

    • 3/32 Key Way(Standard)
    • Hi-Carbon Steel
    • 3 Feet

      • Will Cut Down To Size
  • Seat Motor

    • Have 1 Spare Already
    • Currently being used in 2 places on the robot

      • Number of places being used might increase

        • Claw might need more torque
        • Very versatile, so it won't be surprising of they are used somewhere else
    • Need to get 2 more

      • Just in case
#93
Robot Software / Re: Robot Hardware Testing Tas...
Last post by Louis L - February 11, 2018, 01:18:04 PM
Quote from: Vanshika C on February 10, 2018, 04:29:15 PM
What about using the current to stall the motor to keep the arm in place (don't know if I'm describing this quite right)?

The current plan is to NOT do this; let the PID do the job of holding position. It'll probably bounce.
#94
Robot Software / Re: Hardware interface map
Last post by Louis L - February 11, 2018, 10:56:58 AM
Removed the two potentiometers tied to the MXP board. These are routed to an SRX for PID use so we can read their values back over the CAN bus if we need to. Replace them with 2 additional sonars.
#95
Robot Software / Re: Robot Hardware Testing Tas...
Last post by Vanshika C - February 10, 2018, 04:29:15 PM
What about using the current to stall the motor to keep the arm in place (don't know if I'm describing this quite right)?
#96
Robot Software / Robot Hardware Testing Tasks
Last post by Matt S - February 10, 2018, 03:37:18 PM
This thread is meant for discussing the different test cases or tasks that we will use for testing the robot hardware.

Arm:

       
  • Find the maximum and minimum potentiometer values of the arm and extension
  • Find extension for home
  • Find extension for intake
  • Check accuracy of home angle, intake angle, switch angle, low scale angle, high scale angle, and climber angle
  • Run fine-tuning, and test it for full range (have wrist retracted when home), and adjust speed if necessary.   Make sure that arm also does not exceed 16 inch boundary
  • Move arm to all major positions, and make sure that the PID holds the arms position (adjust as needed)
  • Do cube tests later with claw
Claw:

       
  • Check that home position is working as intended
  • Check leveling at various positions
  • Check that the wrist can fold back fully with arm at various angles
  • Check that the wrist can change positions with a cube
  • Check that gripper limit switches work as intended (fully open, fully closed)
  • Check that gripper can grab a cube and stall the motor
  • Check that the gripper can drop a cube
  • Check that gripper can grab a cube in various positions
#97
Our District Events are 3 days on paper but really have 2 days of actual competition. The first day is really just 5 hrs whereby a team can set up their pit, do some work on their robot, get it inspected and maybe get on the field to tune/align/calibrate/test/practice.

This year, no team will have their autonomous L/R message processing tested in-house prior to the competition. The only way to test it will be at a week-zero event or during load-in. This makes the load-in even more important.

People who need to be at the Load-in (not in any order)

       
  • Drive team (Peter, Isha, Sarah, Xilonen, Matt)
  • Software team (Ben K, Matt)
  • Pit setup (Zach)
  • Other (Stav)
#98
Robot Software / Re: Hardware interface map
Last post by Louis L - February 09, 2018, 10:24:17 AM
Removed the pressure sensor from the Gripper. Steffen's testing showed it would be difficult to use due to the uneven surface on the milk crate Cube. The sensor requires that an additional contact surface be used but that would still have to be properly mated to the sensor to have it work just right.
#99
Imagery / Re: Team Avatar
Last post by Louis L - February 07, 2018, 10:24:41 PM
Since we had no takers, I made one using a piece of our logo.
#100
Arcadia / Re: 2017-2018 Implementation
Last post by Saharsh Y - February 06, 2018, 08:42:42 PM
Here are some of the notes that were taken during the content meeting.

We were also planning on recording students speak out some of the content, maybe even record their faces and not just audio.


I attached a link to the document where notes were taken because when I copy paste the information, the forum removes formatting.

https://docs.google.com/document/d/1SXDEQhQn9dv5B6FC4Amoc5YFS4TqfJ5L5WjEifDrCC4/edit?usp=sharing

https://goo.gl/FaaBj9