graupner – tim.jagenberg.info

05.03.201422.01.2017

Updating an old Remote Control

I recently replaced the controller of my old Graupner mc-17 remote control with a current ARM Cortex-M4 @ 96MHz (Teensy 3.1). Yesterday I soldered the sockets for the LCD, the buttons, and the ammeter which gives me access to almost all peripherals (only the power switch and the additional linear channel are still missing). I already found an Arduino library for the LCD controller NEC mPD7225, thanks tronixstuff, but the display which Graupner used differs from the standard one. Basically the LCD works, but the demo sketch just gives scrambled output. I guess I’ll have to reverse-engineer this application specific LCD.

10.02.201422.01.2017

New Tinker Toys

In the recent weeks I found more time for tinkering and received a whole range of new toys: Two bread-board friendly micro-controller boards (Embedded Artists’ LPC1343 QuickStart Board and PJRC Teensy 3.1), the Pi NoIR Camera, two XBee Pro S2B serial RF modules, and plenty of other i2c sensors and generic tinkering supplies. On the EA QuickStart Board, which uses the same MCU as the r0ket, I’m running the microBuilder LPC1343 Code Base and the Teensy 3.1 is Arduino compatible which enables me to make use of a huge range of ready-made libraries for pretty much all my breakout boards.

One of my current projects is to exchange the micro-controller of my old Graupner mc-17 remote control with the Teensy 3.1. I removed the old processor board and added contacts to all the existing connections: 2X6 poles for analogue measurements of the sticks and trims, and 2X8 poles for the LCD controller and the buttons. The LCD controller is a NEC mPD7225 for which I already found a data sheet. Via the 12bit analogue output of the Teensy, I can even drive the old analogue ammeter at the front of the remote! 🙂

Let’s see how well this mc-17 > Teensy 3.1 > XBee ~ XBee > Teensy 3.1 remote control chain works 😉

Cheers
Tim

21.08.201222.01.2017

Ready for a traditional RC flight

The EasyStar II airframe is ready for the first flight. As I’m still implementing the MAVLink protocol for the RaspberryPi remote control (RaspberryPylot), the first flight will be a traditional RC flight. I hope my (very) old mc-17 is still up for this!