Posts Tagged ‘ Robotics ’

Tricopter: Now in Five Broken Pieces

Curse my impatience.

I got wired control pretty much working, so I went ahead and hooked up my XBees (wireless link) for testing. I had my hand on the chassis just in case, but I guess I didn’t apply enough pressure—it went full throttle on its own (I had barely touched the joystick) and flew off the counter. In two seconds, the tail rotor ripped through my sweatpants and scraped my calf, hit the chair, broke free of its axle and ricocheted into a corner (I spent a good 10 minutes trying to find the detached rotor piece). Somehow, I got three cuts on my left hand, and the acceleration was such that it snapped the chassis into four pieces. Granted, the chassis was made of scrap PCBs, but it was double-layered! All three propellers are shattered and useless.

Anyway, my mother freaked out.

The good news is that I think my motor shafts are okay. My electronics also survived the accident.

I’m probably very lucky that I still have the skin on my fingers and got away with only a few cuts and a welt on my calf. Before I started this chassis build, I cut my thumb pretty badly when I lost my grip on a motor that suddenly accelerated to full speed and landed in my hand (it stopped when it spun itself free of the battery). The jagged edges of the broken rotors would have done much more damage. Why do I never learn from mistakes?

TODO: clean up mess, order new propellers, rebuild chassis, test, test, and TEST CODE.


Raiderbot X Meeting 7, 35 Days to Robot Ship

Meeting time: 15:00 to 19:00
Hours logged: 47.86

We attached our 2005 game arm to the kitbot. It works! It’s a pretty big arm even though it doesn’t quite reach 10 ft. I can’t wait to see our four-bar linkage arm finished.

Ordering parts… We need another cRIO, but I can’t find cRIO-FRC. NI has something that looks similar, but I’m not entirely sure it’s the right one.

ES and DP are building a battery cart. I’m surprised at how complex they are planning for it to be, at least in the electronics and software aspects. It sounds like a great project. That said, I will need to keep an eye on them to make sure they don’t go for too much. I think they can finish, though.

Raiderbot X Meeting 6, 36 Days to Robot Ship

Meeting time: 10:00 to 18:00
Hours logged: 44.05

Nothing markedly eventful happened today. Logging here for the sake of logging.

Spent forever soldering the wattmeter leads to Anderson plugs (iron isn’t powerful enough for 6 gauge wire), but the wattmeter works. Battery test bot pulls 30 A with wheels freespinning on toat, 120 A at stall. Circuit breakers are breaking!

Filled out purchase orders. Searched but could not find AS5040 encoder breakout boards anywhere other than on their official website. We need to order photoswitches as well.

Subdomain randomagically works! I needed to change “NameVirtualHosts” back to “NameVirtualHosts *”. Emailed Mr. R and got sandbox subdomain registered.

Talked with Will about goals for next Wednesday.

Raiderbot X Meeting 5, 38 Days to Robot Ship

Meeting time: 10:00 to 18:00
Hours logged: 36.74


The idea this year is to overload the bots with sensors of all kinds. Current sensors on every wheel, arm joint, and main circuit breaker to graph power consumption. Proximity sensors to avoid collision with other bots and facilitate scoring (automate entire process!). Encoders, gyro, and accelerometer for inertial measurement. And of course, line trackers for line following. I foresee lots of debugging, though it should help that the programmers have switched to Java+Netbeans that allows for serial communication with the cRIO.

Team 955 will now be using Git for version control. Git repository created here on Github.

Rockwell Automation Photoswitches

There is a wiring diagram on the back of the sensor box. L.O. and D.O. are light output and dark output, respectively. Power supply should be between 10.8 V and 30 V. See this Chief Delphi thread for more information. In the end, hooking it up to the cRIO is as simple as soldering brown to positive, blue to ground, and either white or black to signal of a PWM cable (which is true when either is light/dark?) and connecting the combination to Digital I/O. It is NOT necessary to hook up bleeder resistors from the signal lines to VCC as it says in the datasheet.

The datasheet is very useful:

  • Green LED on: sensor powered.
  • Green LED off: sensor not powered, output active, SCP* active.
  • Yellow LED on: output on.
  • Yellow LED off: output off.
  • Yellow LED flashing: output SCP active
  • Orange LED on: margin** > 2.5.
  • Orange LED off: margin < 2.5

* Short-Circuit Protection
** The orange LED shows that the signal strength is at least 2.5 times that needed to trigger an output. Signal strength is greater with higher voltages (obviously). This can be useful to overcome dust on the lens. The sensor’s sensitivity can be adjusted also by turning the knob on the front panel of the sensor. With an oscilloscope, I found that at maximum sensitivity, the photoswitch is triggered by almost anything (e.g., the table, paper, my red 955 sweater, my jeans) even at 10.8 V. We will need to test and calibrate the photoswitches so they trigger only over the reflective tape.

The datasheet recommends that the distance from the sensor to target to be at least 6 mm.

Standardized ordering process

Blanket POs from Will and Mr. A. Co-PMs and division leaders are the only ones authorized to order. Use order form on team website.


TETRIX parts list:
2 – Motor Mount, W739089
1 – Motor Shaft Hub, W739079
2 – DC Motor, W739083
1 – Gear Hub Spacers, W739090
1 – Tetrix Resource Kit*, W731900
1 – Battery Charger, W739059
1 – 12V NiMH Rechargeable Battery, W739057
1 – Power Switch, W739129

* The Tetrix Resource Kit contains the parts shown here. Unfortunately, I haven’t found a detailed list containing only the Resource Kit parts, so we have to use the detailed parts list we found earlier here to identify the kit parts.

The default kit seems to have enough parts in it for one minibot. Once the minibot team has a reasonably complete idea of how they want to build their two minibots, they’ll let me know of any additional parts they’ll need. We’ll see exactly what parts we have when the kit arrives (hopefully) later this week.

Sent an email to PHRED about the possibility of exchanging FTC parts for FRC parts. They apparently no longer plan to build a minibot.

Raiderbot X Meeting 4, 39 Days to Robot Ship

Meeting time: 15:00 to 21:00

We are two days behind schedule. I started a WOT (Weighted Objectives Table) discussion of the various lift concepts at 3:30. We started with seven concepts:

  • Single-jointed arm
  • Multi-jointed arm
  • Telescope (elevator)
  • Four-bar linkage
  • Eight-bar linkage
  • Scissor
  • 60/40 scissor

We narrowed it down to the four-bar linkage and the elevator and chose the four-bar linkage after a qualitative analysis using a pros/cons list for each. But I still wonder if this was necessary, because it took another 30 minutes of our time and I ran 45 minutes past my proposed deadline of 4:30. Why couldn’t we have reconsidered the two options using the three factors we had rated most highly? Will says some people just need more stake in things? Anyway, my bad for not calling them on it. Areas of improvement:

  • Do not let the loudest voices steer the discussion off-course.
  • Constantly think back to previous discussions and decisions. People were putting the WOT factors under the pros/cons lists, which is nonsense.
  • As always, be consistent, even when calling out for hands when rating the WOT factors. This is no time for jokes.

Will then separated us into four design groups for the lift, claw, base, and minibot.

Four-bar linkage: Mr. Groom found that making the shoulder pivot points’ distance shorter than that of the elbow pivot points allowed the claw to point down when the arm is down and point up when the arm is up. This should allow us to reach both the ground and the top peg as well as everything in between. This makes sense if we think about the four-bar linkage as a trapezoid and shifting the two bases—the linear displacement for the two lever arms is equal but the arm lengths are different, so angular displacements differ.

Minibot: make it as close as possible to a battery with motors glued on.

Preliminary design review planned for Saturday 17:00.

Raiderbot X Meeting 3, 41 Days to Robot Ship

Meeting time: 15:00 to 19:00.

We will have budget discussions every Tuesday after meeting.

FIRST Choice parts ordered, including the FTC Mini Kit for the minibot.

Talked more about end effectors, spent 30 minutes prototyping. Kushal and Damian made a pretty sweet prototype of a four-bar linkage arm.

I messed up here again and completely forgot that we’d planned to finish design decisions by end of the day today. Didn’t happen. Where’s my todo list? I need to make a Gantt chart soon.

Raiderbot X Meeting 2, 42 Days to Robot Ship

Meeting time: 15:00 to 19:00.

Continued talk about end effector design. We built prototypes and tested them in the shop, but just as Will was showing the old triangular scissor lift and I was wondering why there were suddenly so few people, my sister ran in and told me Mr. C (my youth symphony director) was looking for me.

Okay, major slip-up on my part.

Panicked, I promptly ran out of the shop, simultaneously realizing that I had left my violin in my locker and that that was why I felt something was awry as I walked away from my locker earlier today. In the orchestra room, I grabbed and opened a random violin case off the shelves only to discover a long-neglected violin with all four pegs loose and strings going everywhere (and collapsed bridge, needless to say). Fortunately, the next violin was in decent condition, albeit I had to play without a shoulder rest. It wasn’t my first time. It probably won’t be my last.

Halfway through rehearsal, I realized there was a (robotics) team budget meeting at 7:00 I had assured Will I would be at.

I hope never to be so stupid again.