Member Since: February 16, 2011

Country: United States


Spoken Languages

english français castellano

Programming Languages

asm X86 C C++ Pascal PHP SQL


http://www.dplomat.com http://www.jmd-tech.com

  • I’ve got some of those i bought about 15 years ago at a local dealer, both N/O and N/C versions.

    The one on RS picture looks like my N/O versions (plastic inner cylinder of pushbutton) while Sparkfun’s one looks like my N/C (metal inner cylinder)

    At the time i preferred the N/C that are very sensitive while the N/O needs to have the button pushed on its full course to be on.

    I had those stored in unoptimal conditions (humidity), and while the N/O degraded (needs some force to close the circuit and huge contact resistance varying with push-force), i was surprised to find the N/C kept all their binary and responsive touch, maybe N/C contact are somewhat more moisture-resistant.

  • I suppose the way to go from Arduino would be:
    -use Ardupilot code
    -convert to plain C++ AVR code with Makefiles etc
    -generalize a bit the hardware handling code “drivers” for gyro/accel/compass (maybe an intermediate step would be Ardupilot ported to Arduino + 9DOF IMU, I’m in the process of doing this as i’ve got one but have very few spare time…)
    -port the code to LPC2148 MCU
    About the servos, either you must use digital servos conneted to I²C but that would mean much wiring in I²C, not toot good for using the bus with fast sensors, an I²C IO expander or soldering wires to GPIO pins and implement PWM.
    If one day I manage to have 9DOF IMU + Ardupilot working well I might upgrade to this awesome unit as the HW specs of the ATmega (2k SRAM!!) is the next obvious limiting factor

  • looks like space-wise the Li-Ion is better, but when weight matters LiPo is better

  • Maybe a bit overkill for this use, but it can power a chinese bluetooth mouse for two full days of intensive use:
    review and upgrade of 6D rechargeable bluetooth mouse

  • I’ve just received mine some days ago, was the first time i play with I²C devices.
    I’m using an Arduino board with a protoshield, makes a very straightforward prototyping platform with a large community so there are a lot of examples on the net for reading I²C devices and printing the output to serial (in fact serial over USB) console text.
    Makes it an easy trasition to standalone ATmega TQFP32 platform when you have a production-ready design (and lightweight requirement i suppose)
    I’ve found this for the accelerometer:
    I’ve adapted it a bit to read also the gyro and compass values.
    Now those are raw values but i’m in the process of writing a small unit to init at optimal settings and output values as SI units.
    For the Open Log i just cheched it’s page and i can only backup Nate’s reply to your comment, neither hard nor trivial.

No public wish lists :(