Note Viewer

• Took off light sensor array for billy to further test it...
  • Did not work when it came off
  • From Billy 
  • "Status report on the light sensors: it seems like the main issue at play here is power consumption. The first thing I did when I took the module off the robot (after verifying that it didn't work) was run the example code on it, which failed. When I removed the spliced-together power wire and had each sensor strip plugged into a different 5v pin, the code worked for a 16 sensor array again"
  • "Still having some issues with largers arrays declared in software in that their return values from the readline function seem weird. I'm going to try making them 3 different software objects and merging together the result tonight (March 1st), to see if the issue is in how I extended the memory in the library"
• Hatch mechanism using the pid tried to kill itself --> turns out the string pot wire came unplugged (need to find a good solution for this)
• Attempted cargo pid but it also tried to kill itself --> didn't get to look into this much because the robot was being worked on by mechanical people
• Plan is to have all mechanical changes (except for a new cargo intake) done on the robot Friday night so that Saturday & Sunday are completely devoted to code and driver practice

• These light sensors
• Wiresss

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. Mount & wire ultrasonics (Wed or Thurs after Chris (or someone else) makes mounts)
3. Second light sensor array+arduino+polycarb holder needs to be assembled. Parts are on computer table.

CODE:

1. Talk to Marlow & Sam about buttons and controls for the robot (as of now climber and drivetrain is on 1; hatch and cargo is on 2)
2. PRIORITIES: 
   • 1a. Hatch auto-alignment with lines
     • mount light array & arduino, finish code
     • get arduino issue fixed
     • Arduino is just sending the same value (12) across the i2c but at least it is sending something I guess
   • 1b. climber stils moving at the same speed
     • Discussed today 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.
   • 2. cargo set points (all the way down, all the way up, etc.)
     • Test did not work, need to check again and keep working on it
   • 3. 1 step climber process
   • 4. Drive to vision targets using limelights

OTHER:

1. Continue the schematic for the electrical system using the schematic software stuff --> talk to Malia & Caden about this if you are interested

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)
   • check if encoders are working
   • change pot values
   • the ultrasonic sensors
   • arduino & light sensor array

I mean no but that's how it is...