Mech - User contributions [en]

File:MATLAB Robotics Toolbox for ME449.zip

2015-10-29T05:19:36Z

Nelson Rosa: uploaded a new version of "File:MATLAB Robotics Toolbox for ME449.zip": added missing simulink folder

File:ME449-MATLAB-Robotics-Toolbox-Instructions.pdf

2015-10-29T05:01:56Z

Nelson Rosa: uploaded a new version of "File:ME449-MATLAB-Robotics-Toolbox-Instructions.pdf": trying to get new version to load

recent set of instructions.

2013-01-15T21:12:37Z

Nelson Rosa: /* Robot frame (2 people) */

Questions for the group:
Where should we host the project? (Google Docs, DropBox, GitHub, Google code, SourceForge, etc.)

Below is a list of projects. Each project will have a team lead responsible for keeping everyone on track.

==Power module (1 person)==
Build the charging station consisting of two metal pads, electrically isolated, with a smart charger on the back side of the wall. For now assume you are charging the 11.1 V batteries we have in the lab. The design challenge is in robustly delivering the power to the robot. A few ideas are:
* the wall has telescoping power leads to reach the robot.
* the robot has two spring-loaded contacts (springs, ball bearings?) to slide along the wall and make contact with the pads.
* the robot has contacts mounted on solenoids to extend and retract.
* add mechanical magnetic clamps to the two pads to be able to support the weight of the gibbot.
* Have the pads provide raw power and have the smart charger onboard

Milestone: Show batteries can be charged when the robot is in contacts with the module. Also, show a prototype circuit outputting the fully charged and recharge signals. Give PCB designer (see below) the inputs and outputs of module.

Deliverable: Working setup including, a PCB with LEDs to indicate charge level (battery gauge) capable of sending signals to PIC when fully charged and when batteries are low.

==Robot frame (2 people)==

motor
frame
magnet
must play nice with other modules

Mechanical: Select a material that can withstand falls of ~15 ft of a 10 lb robot. Select a motor that will allow the robot go uphill with weight of frame + batteries + electronics. Ideally the motor would be backdrivable. Is it possible to design a clutch mechanism? The links should be between 12-18 inches. The frame will most likely undergo a minor revision in the spring term once all other components are finalized. For the winter term, a base frame should be constructed that can test the motor such that the robot is capable of moving uphill. We can add weights inside the frame to test the expected payload.

Electrical: A motor model + motor control PCB module should be built. The module should be able to sense current and perform simple PID tracking.

Deliverables: Rugged frame (with padding inside for components?) that can withstand falling from sheet. With one link clamped (can use a vice with a rod sticking out to attach frame), frame should be able to use its motor to reach heights above the pivot link. PCB motor module with h-bridge, encoder circuit, and current sensing. PIC32 should have FF and FB model running (should have motor constant, Coulomb + viscous friction model, etc.).

Milestone: Frame (being) built and motor modeled. Give PCB redesigner (see below) the inputs and outputs of module.

Side Projects: Can frame deploy parachute for soft landing? Can a clutch be added? Should we pursue pancake motors? Use two motors at joint, one on each link, but with shafts coupled so only one needs to be active. The other is a generator while inactive, can we reuse the power generated to recharge the batteries?

==Vision (2 people)==
Build a vision system that can track the robot at all times. Assuming a steel sheet that is 6 ft x 8 ft, the camera needs to be calibrated so that it outputs real-world coordinates. This project will consist of:
* calibration of a wide-angle lens, special color filter
* robust wireless communication (IR, XBee, other)
* robust tracking, where should the LEDs be placed on the robot?

Tracking and communicating can be done on a webcam

Milestone: The receiver should be a function on the PIC that returns an (x, y) location using a unit of metric length. Camera should be chosen and calibrated. Give PCB redesigner (see below) the inputs and outputs of module.

Deliverables: For the camera, a Gibbot tracking algorithm as well as a calibrated lens for picking up the robot’s location.

==Smart Wall (2 people)==
Mechanical: For prototyping any size wall and material is fine.

Electrical: Wire up the LED sensors (1- or 2-inch spacing). For both run a calibration routine that can pick up the location of the robot. How large of a PCB can we order of the LED array? Build a PIC32 library that can take in the image and LED data and produce the robot’s location. The idea here is to build a prototype that is easy to scale up for spring term.

Deliverables: A mockup showing a gridded wall with an emitter/detector pair inside each grid pulsing its location (let’s call these guys the transmitters). Communications protocol should be a simple IR protocol (copy same one for TV remotes). Demo must show onboard Gibbot circuitry (the receiver) picking up the transmitter signal. Should also output data to PC via XBee. Must make sure that work can be scaled up to an 8ft. x 6 ft. wall. What are the power and component requirements as we scale up?

Milestone: Idea of artistic use for wall. small scale PCB circuitry showing receiver and transmitter talking to each other. The receiver should be a function on the PIC that returns an (x, y) location. Give PCB redesigner (see below) the inputs and outputs of module.

==PCB redesign (1.5 people)==
Electrical: current sensor, position sensor, gyro, accelerometer, ext. Flash for data logging, send info back to PC, easy to maintain and replace parts. PCB board, fix old board mistakes and add debug terminals (e.g., pads to quickly read the analog signals on scope)

Deliverables: PCB should be able to interface with rotary sensors, gyros, and accelerometers. There should also be a data logger to external flash present, so we can record and playback sensor info for debugging. Designer needs to also make sure that PCB modules of other projects will fit into PCB design and that modules can be easily tested. Documented library of functions with example code on usage. Documentation should also include resolution of sensors and conversion from sensor units to real world units.

Milestone: PCB components, size, and locations should be finalized. Final sizes should be given to the Frame project. Additionally, module sizes of other projects should be given to the respective module designers.

Side Projects: Can we replace the XBee with something smaller and faster?

==Rotary magnets (1 person)==
Build Kinea design magnet. Can we come up with a lower power design?

==EP magnets (1 person)==
Build and characterize an EP magnet. Do we get the expected power savings? For building an EP just follow Knaian thesis. 22.2 V batteries can provide up to 45 A continuous.

Deliverable: An EP magnet capable of 300 N holding force and a model of the magnet’s BH curve (don’t know exactly how to measure this).

Milestone: Ability to reverse polarity of Alnico magnet and holding force data of magnet when switched on.

==Inductive power module (1 person)==
Same specs as power module, but with inductive charging (i.e, with no physical contact between the wall and the robot). Challenges would be dealing with EMI. Could we get away with not using batteries and instead use supercapacitors with inductive charging?

==Wheel Carriage (1 person)==
Build wheel carriage prototype. If it works well think of integrating it into the gbot design for spring term.