Edit

Note Viewer


Electrical & Code 2019

Attendance

Note Info

Students
Mentors
Date & Time
Location & Author
  • David S.

  • Adam P.

  • 3/2/2019

  • 8 hours

  • Aquiferland

  • Bryn G.


Notes

Concern that if any of our sensors stop working, then stuff could break...

Vasista suggests that we should have buttons that can turn individual sensors off so that they are ignored with code and everything is done manually as not to brake anything.

Would it be sufficient to just run regular tests in the pit before and after matches?

Any other ideas?

I just realized: My old team had a deep mistrust of networktables so I hadn't considered this, but it works, so toggle switches in Shuffleboard would be another option. -V

Work Completed

  • Changed all buttons to match what Sam & Marlow had requested
  • Switched over to use Vasista's new xbox controller class... it works really well so far
    • Can make our own buttons so we made joystick up (reads greater than 0.9) as a button on driver 2  for example
  • Organized all of our extra sensors into a bin; same with connectors and other stuff to make packing less painful come Tuesday night

Hatch: 

 

Cargo: 

  • Got setpoints working
  • 135 degrees: cargo ship from the front; 55 degrees: cargo ship from the back; 35 degrees: rocket ship from the back; 5 degrees: intake from almost on the ground
  • Pot is working well but the coupler it is attached to cracked so it is slipping causing the voltages to change; this should be fixed soon and the set points should go back to working shortly
  • Soft limits in code work :)

 

Climber:

  • Rebent trigger (limit switch) on climber? I'm not sure if it was ever rebent but I believe that they all work now
  • Tested climber manually but not automatic yet
  • Set climber encoders to zero themselves in robot init, but the back encoder was skipping around, need to look into this!!!

Challenges

  • Cargo pot slipping
  • Climber encoder not working

Work for Next Meeting

GENERAL:

  1. Continue organizing all of the stuff for comp (ie. motor controllers, PDP, other components, crimps, etc.)
  2. Put new images and such on the extra roborio just in case
  3. Continue the schematic for the electrical system using the schematic software stuff --> talk to Malia & Caden about this if you are interested

ELECTRICAL:

  1. Ethernet switch has power wires run to it but they don't work. I don't know why, someone needs to troubleshoot it. For now the limelight's ethernet is running right to the radio. - Adam
  2. Finish assumbling second light sensor array+arduino+polycarb holder, test to verify it works
  3. Take an hour or so and re-route all of the wires on the practice robot :)

CODE:

  1. Test climber on hab and see how ultrasonics behave. If they aren't reliable we may need to switch to using current sensing for front, then read DT encoders for determining when to raise back
  2. Continue investigating overrun warnings. Try disabling LiveWindow telemetry, suggested by Dustin on CD. If that doesn't help do a full cProfile and post code/profile for him to look at
  3. PRIORITIES: 
    • 1b. climber stils moving at the same speed
      • Discussed to use positional pid
      • From Adam: 
        There's no overshoot or acceleration to speak of, so honestly PID is prob overkill for climber. You could just make a command that sets the front and back speeds to X, then monitors the encoder positions every call to execute.  If they differ more than some threshold value, lower the speed sent to the faster one by 10% or something.
    • 3. 1 step climber process
    • 4. Drive to vision targets using limelights

 

COMP BOT:

  1. Pneumatics (comp bot)
    • Check regulator and be sure the flow direction is correct
    • Fix leak on hatch mechanism
    • Get cargo arm brake working
  2. Comp Bot electrical system (TO DO AT COMP)
    • Make sure all climber switches close as expected
    • Make sure 3d printed climber touchplates all touch switches as expected. Might need blots replaced by rivets.
    • Mount, connect and test line sensor array
    • check if encoders are working
    • change pot values
    • the ultrasonic sensors
    • arduino & light sensor array
  3. Code
    • calibrate line sensor array on field, update arduino code with that data
    • calibrate limelight thresholds on field

On Schedule?

If we get climber semi-automatic tomorrow, then yes we are on schedule; if not, I have no idea...