My Makibox status

I have 2 Makiboxes.
1 stock Makibox A6 HT and
1 Makibox A6 HT  with an Airtripper V3 BSP extruder and E3D V5 hotend but missing a working mount for the E3D.

I have given up on the Makibox and am willing to sell both.
That Makible is in trouble with it's investors doesn't help the case.
An Ultimaker 2 is already ordered.
Nonetheless I'm sitting in the GPN Karlsruhe at the moment trying to get both to work reliably.

I upgraded the stock Makibox to the new firmware v42 with PID autotuning.
(You use PID autotuning with the M303 command described here.)
I'm using it to print this E3D v5+LM4UU mount for the other Makibox.



PID results of stock Makibox:
< 02:45:13:  Clasic PID --  PID settings:
< 02:45:13:   M301 P7627 I57 D630
< 02:45:25: ** PID Autotune Cycle: 5 **
< 02:45:25:  bias: 39 d: 39 min: 199.00000 max: 201.00000
< 02:45:25:  Ku: 49.65638 Tu: 12.33100
< 02:45:25:  Clasic PID --  PID settings:
< 02:45:25:   M301 P7627 I61 D587
< 02:45:25: PID Autotune finished !
< 02:45:25: Place the above command in console to change the PID settings.

Result: IT WORKS. Pretty rough movement, so low in detail but it works now!
Printing more replacement parts while it still works.

EasterHegg Basel 2012 - Decoded the Zoom H4n remote control protocol!!!

(Update: I'm doing the same for the new Zoom H5 too.)

For the next 4 days I am on EasterHegg and reverse engeneering the protocol spoken between the RC04 remote and the Zoom H4n audio recorder.
This posting is constantly being updated and rewritten with details as they come up.
Newsticker:

• Friday
• So far no luck with the OpenBench logic sniffer. 
• Can't figure out if the buffered inputs support 3.3V signals or only 5V signals. We are trying to verify this by connecting and disconnecting the on-board 3.3V supply to an input-pin to get a known signal.
• But we are out of chocolate and coffee!!!
• Saturday
• I fetched my pocket-oscilloscope from home but forgot 2 cables.
• Contacted "Nussgipfel" for an oscilloscope because he holds an oscilloscope-workshop tonight. So he must have a working device. Hope to verify that the signal is 3.3V and count it's frequency/bitrate to get the OpenBench to work on decoding it. 
• Hacked my pocket-Oscilloscope. Found a 5V signal (-0.5 to 4.5V and -1 to 4V) in the 600-800Hz range.

  Aus 2012-04-07_EasterHegg

• Decoded the signal

  Aus 2012-04-07_EasterHegg

• Batteries died while decoding the LED signals. Buttons are decoded.
• Sunday
• Trying to find Nussgipfel again to make screenshots of the undistorted waveforms and document my findings below.
• Found a second signal being transmitted with >100ms delay after the first signal. Need help analysing it.

  Aus 2012-04-07_EasterHegg

• checked the signal using a larger scope. Seems I had GND and Signal confused on the small one. Low<->High. May be RS232 after all? With start+stop -bit the signal checks out. 2.400 = 417 µs per bit seems to match our 0,4ms per bit.
• Making a break to eat some fondue down in the huuuuuuge bunker below this building. Planning to use a larger logic analyser later.
• ...
• Monday
• ...

---

Aus 2012-01-22_RC04

Observations:

The 4 connections between RC04 remote and H4n are labeled 3.3V, RX, TX and GND.

The single chip on the remote is labeled "D78f0500A"
It could be an NEC microcontroller µPD78f0500.
The number of pins and the pins connected to RX, TX and SCK seem to match.
The datasheet is in Korean but what I can make out is that this should be a 5MHz microcontroller that can run on 3.3V and 5V. No details from the datasheet cast and light on the strange encoding used(described below).

What I found out about the protocol being transmitted by the RC04 remote on the 2 lines "RX" and "TX" when certain buttons are pressed on the remote or the Zoom H4n lights up certain LEDs is as follows:

Findings:


 The protocoll is RS232 at 3.3V with 2400bps 8n1
The remote sends 2 sequences of 2 bytes with a small delay:
Record: 0x81 0x00 | 0x80 0x00
Play:   0x82 0x00 | 0x80 0x00
Stop:   0x84 0x00 | 0x80 0x00
ffwd:   0x88 0x00 | 0x80 0x00
rwd:    0x90 0x00 | 0x80 0x00
vol+:   0x80 0x08 | 0x80 0x00
vol-:   0x80 0x10 | 0x80 0x00
rec+:   0x80 0x20 | 0x80 0x00
rec-:   0x80 0x40 | 0x80 0x00
mic :   0x80 0x01 | 0x80 0x00
ch1 :   0x80 0x02 | 0x80 0x00
ch2 :   0x80 0x04 | 0x80 0x00

It receives a single byte that is a bitmask of the LEDs to light up:



? && 0x01 = record LED
? && 0x10 = MIC LED
? && 0x60 == CH1+CH2 LED = 0x20 + 0x40
? && 0x20 = CH1 green
? && 0x40 = CH2 green
? && 0x04 = CH1 red 0x16?
? && 0x08 = CH2 red


? && 0x24 = CH1 yellow (red+green)
? && 0x48 = CH2 yellow (red+green)




Links

• Easterhegg
• OpenBench
• DS0201  "DSO Nano" pocket oscilloscope (manual)
• µPD78f0500
• Photos (Sorry, rejected photos where uploaded too for some reason)
• Photos of the RC04 for the H4n
• All Videos (please subscribe)
• Andreas made a radio remote for the Zoom H4n based on these findings.

Next step: implement this in an ATTiny13 using a softUart. Maybe use a CMOS 4019 /
4052 or MAX4619 to trigger something else too.

(DE) Besuch beim CCC München

Gestern mal Gelegenheit gehabt die Räume des CCC in München zu besuchen.
Geil!
So stelle ich mir das sich für Freiburg vor.
Gemütliche Sofa Ecke, gut ausgestattete Werkstatt, kleine Küche, Serverraum und ein großer Tisch zum ruhig Arbeiten am Laptop.


Hab die Werkstatt gleich mal genutzt um den Gimbal an der Steadycam etwas tiefer zu setzen.
Ist jetzt bei gleichem Gewicht durch die größere Hebelwirkung besser ausbalanciert.
Mal sehen ob ich heute dazu komme, Test Aufnahmen zu machen...

Eindrücke von der Gullasch Programmier Nacht

Falls es wem aufgefallen ist,
ich blogge tatsächlich die letzten Tage gelegentlich.
Das liegt hauptsächlich an dem neuen Nexus One, was
es einem (mit passenden Apps) leicht macht mal eben ein paar Zeilen und ein
Photo in Blogger zu stellen.

Was wegen den Verbindungsabbrüchen eher schlecht als
recht funktioniert ist das hochladen vieler Photos auf
Picasa.
Trotzdem hier mal einige Eindrücke von der GPN10:
http://picasaweb.google.com/Marcus.Wolschon/GPN10Karlsruhe#