Anyone know what happened to those neet little tinkerkit IO modules?
I found a couple of references with Goolge but over a year old, tinkerkit.com needs a password, and I've had no response from an email (which may have gone to the wrong place as I can't get good contact details).
We designed someshing similar, with the same connectors, and have some modules ready now (using them in our country, Argentina). We are not full open source yet, but will progressively release sources):
Sensors:
Beacons and buzzers:
Motors:
And this is our new DuinoBot brain, wich is based on an ATMega32U4, without FTDI or any other chip:
We will release a LUFA based core and bootloader, both open source soon.
Rob: yes, we worked a lot on the connection system, so there are already these kind of modules:
3 wires: Same pin-out as RC/Servos and other standard analog and some digital sensors. The beacons, buzzers and other low current actuators that needs GND/Vcc/Data use this connector too.
4 wires: These connectors are reserved for intelligent sensors with Tx/Rx lines, such as ultrasonic (we are designing an open source one reprogramable with the Arduino IDE).
2 wires: These connectors are for motors, up to 1 Amp. continuous (we use 0.35 mm^2 cables, which is aprox. between AWG 22 and 21 so they can carry this current). The DuinoBot boards has two of these connectors for their HBridge outputs.
Also, we defined a 5 pin connection, which is for connecting boards to comm mocules, but with Reset line. So, a brain (like a DuinoBot) can be reseted from a comm module (like the FTDI or the Bluetooth module) for bootloading.
3 wires: Same pin-out as RC/Servos and other standard analog and some digital sensors. The beacons, buzzers and other low current actuators that needs GND/Vcc/Data use this connector too.
Julián,
how are you driving those modules? With PWM like servos or a different way? Are you just using for output the servo library if so?
I'm also interested in how data from sensor is read, do you use PWM with pulses between 1 and 2 ms here too?
Hi Korman, we are writing libraries (some of them are fully functional, but under testing right now) for all of them.
For example, the Sharp IR analog rangers has not linear output, so we wrote a class (will release all the sources soon soon, think in october) wich uses the analogRead, but has a table in flash to get the distance in [cm].
The analog sensors like the CNY70 can just be read with the standard analogRead().
The 3-pins connectors can also drive a standard R/C Servo. For these, nothing better than the starndard Servo library.
The buzzer (same page as the beacons), with the standard Tone library.
And for the motors (2 pin high current connectors) we wrote a DCMotor class that will be released soon too. It can drive any 3 pin HBridge (like the L293, L298, L6225, TB6612FNG, etc.).
The comm modules just uses the Print functions.
We tried to use the standard libraries as much as possible, but are writing clases when if it's necessary.
I can advance, that we had wrote some filter clases (low pass and high pass) for the advanced sensor users too. All this stuff will be released together.
Thank you, Julián, that clears it up. So your 3 wire connector is just compatible electrically, not also from a protocol point of view. Given the wide range of things you attach, that makes a lot of sense.
It's compatible electrically, but the kind of things you connect defines which library you will need. So you can use standard servos, third party sensors, DIY sensors, and our Multiplo sensors, and there is no problem. We will release libraries which facilitate the use in some non linear, or difficult sensors.
So, with things like the rangers, you only have to write something like this:
There must be something in the water, everyone is designing sensor/actuator systems, including myself. It seems though that most systems are compatable at least at the hardware level, ie the 3-wire GVS model (although still no info about the Tinkerkit modules that I can find), and just need appropriate libraries.
So that's good, as long as we have variety and don't all design modules that perform the same functions.
those motors are pretty nice. Good design, easy to create and assemble.
And attractive too! And good use of laser cutter technology (?)
I really like the layered construction technique; I wonder if some similar but uglier could be accomplished using PCB material and a typical PCB mill, and widely available servo gears?...
Many thanks scooterx3 and westfw for your kindly comments! I did not see them till today
Yes, they are lasser-cut, as the robots and the whole Multiplo building system, and the case for our DuinoBot. We are right now very very bussy, but will enrich the website as soon as we can (I think by december), and will release all the sensor libraries, as I told.