Sunday, October 11, 2009
Digital Devices now available.
I may have to replace that 20 year old clock radio that is currently at my design table. You know, just to maintain continuity.
Saturday, October 10, 2009
Project Complete!
It works pretty well, so all I need to do is set it up and take some video.
Another teaser...my inspiration was Chalkbot. Well, maybe that was too much of a hint.
Friday, October 9, 2009
Fridays Robot Idea
This is on my list of future projects. The only thing I am worried about is what to do with all the products created during the testing phase. I have a feeling that my testing periods won’t last much longer than about 30 minutes.
A Plea For RobotC
My only problem is that they haven't released a way to communicate via Bluetooth between more than 2 NXTs. I am fortunate enough to have 4 NXTs. If I choose a project that uses all of them, I have to be very creative and figure out a way to communicate between them. Yes, I know NXT-G does it really well, but I find that things start to go bad when I create very large programs with lots of decisions and loops.
Thursday, October 8, 2009
HiTechnic Sensor Multiplexer
. You can add any HiTechnic or Lego supported sensor. This is in addition to the Touch Sensor Multiplexer.It looks pretty cool, and they claim you can have multiple multiplexers on a single NXT, so you can have up to sixteen sensors on one controller (WOW!). Throw in an IRLink to control some PF motors and an RCX and you have incredible power and control from a single NXT.
I already have several HiTechnic products and I find them to be very reliable. I have contacted them about technical support and they are great and usually get back to you quickly.
The drawback I see is that there are no NXT-G blocks to download yet, but they will be supporting LabVIEW 2009 and RobotC soon.
Now where did I put my wallet.....
Wednesday, October 7, 2009
Anti "WAIT" movement.
I watch a lot of videos, mostly on YouTube.com. There are usually dozens of NXT videos loaded daily and I try to look at the most interesting ones nearly every day. There are some incredible people with incredible ideas out there, and I thank God that we have such a utility to share. I always walk away from watching videos inspired.
But one thing that is a turn off is watching a robot with too many "wait-time" blocks. The Great Apes are fascinated by shiny things, my loving wife loves expensive things, my kids love noisy things and robotisists love moving things. Don't get me wrong, the "wait-time" block is great for debugging, but not good for final runs that will be recorded and put out for public consumption. The attention span shortens when watching an outstanding robot doing nothing.
A plug for Lego Education.
Plus, you can sign up for a free catalog. There's nothing like getting a Lego Robotics catalog in the mail and keeping it on the coffee table for perusing when not building.More Power with a Differential Gear
A way to get a good speed and lots of power is to use a differential gear in a different way. Everybody is familiar with using a differential gear to power the both driving wheels of a vehicle so the wheels will be powered while turning a different speed. The same can be done with motors. Rather than attaching wheels to the differential, attach motors. Then the motors can be run either independently or together. When only one motor is running, there is a gear ratio of 2:1, when together there is a 1:1 ratio with twice the power.
There are some drawbacks to this;
- Power will always travel path of least resistance. This means that if you have a high load and only one motor is turned on, you will likely just turn the rotor of the other motor. This means that you may be required to run both motors at all times. Another solution is to incorporate worm gears on each motor, giving you an extremely powerful but slow gear box.
- To maximize power, each motor should have its own power supply, so you should double up on battery boxes and controls.
- You may end up with extremely high power, so you might want to consider beefing up some of the power transmission elements. Two XL PF motors could easily twist and break an axle under a high load condition.
I have used this technique a few times, and once I connected four 9v motors to drive a very large heavy wheel. It works great, but can be a space hog.
Sunday, October 4, 2009
Non-Lego "Stuff"
I have considered a multi-NXT robot with lots of motors and sensors that are all completely hidden such as a human face or an amorphous shape. There would be no Lego elements visible to the eye. I recently found this stuff called Polymorph that looks cool. It is a plastic that melts at very low temperatures (hot water) and can be melted over and over and the re-usable nature really keeps with the Lego spirit. The cost is a little high at $20 per kg (about 2.2 lbs.) I might look into this more in the future.
Friday, October 2, 2009
Fridays's Robot Idea.
I saw in person a system like this at a trade show in Chicago. It is fascinating and I think that it can be done using the HiTechnic IRLink (yes, that again) with some remote control train motors or even standard remotely controlled PF motors. I would like to see several robot cells that each does something unique along with the system that connects them. This has the potential to be a massive system, and if anyone would like to devote a year or so to building a huge system, call me!
Skip ahead to about 0:48 to see the system in action.
Wednesday, September 30, 2009
Have you ever done this?
Monday, September 28, 2009
More uses with the PF Motors
I really like PF motors. They have plenty of power, they are easy to mount, and the hollow shaft makes customizing a project a breeze. Everything I build uses the NXT, so I needed a way to control the PF motors. Enter the HiTechnic IRLink. But the problem is there is no direct way to the position of the shaft, such as “turn the shaft 270 degrees.” Well, there are a couple of ways to get around that.
The first way is to add some gearing and include a clutch gear. Then design your project so that it will hit some stops. When the stops are hit, the clutch gear will give and your actuator will end in the desired position. Reversing the motor will run the actuator the other way until the other stop is hit. This is analogous to using a pneumatic cylinder. Stopping the cylinder midway through the stroke is a challenge, so we mostly use it in the extended and retracted position. As you build and test, measure the time it takes to complete the cycle from one end to the other and write that into your program and add some additional time, say about 0.25 or .50 seconds.
Here is a short video showing an example of how that might work.
The second way again uses the IRLink sensor, but adds an RCX and a rotation sensor or a couple of touch sensors. The touch sensors would be used in the same manner as above, but the touch sensors would be used as the stop.
The IRLink makes use of the RCX and the PF motors, so you can get motor control and feedback while using only one port of the NXT! Imagine, using a single program, you can have 3 servomotors, 8 PF motors, 3 9V motors, 3 sensors on the RCX and 3 sensors on the NXT. If that is not enough power for you…..
