I think it would be better done in assembly, IMHO unless if you include Port Input/output opcodes into your code.  Because Axe is very limited in the way it can send data through ports.  It DOES have decent control over the link port, but not pitch perfect for all circumstances -- so my advice is to make the actual sending snippets in assembly, assemble, disassemble to hex, and copy the snippets in order

If you do it like that it is very helpful to put something like 5 NOPs in between snippets for you to tell them apart.

Good luck!

Not a bad protocol there.  You are using the I/O port, right?

UP !

Now I've no arduino card, and I'll never buy one if I don't know what and how to made with !
I had a second crazy project, with the RC system of my old nikko rc car :
A prgm to pilot the car with car, and maybe a bw camera ...

I would just get an arduino uno (Considering you can't program a mini, IIRC, unless you have an FTDI cable).  You have to realize, though, although this would be cool, many people wouldn't use it everyday.  Of course, that's not to say you shouldn't continue it, but for your own reasons, not necessarily for other users. Plus, this seems to be very coffee pot-specific, too.  I would say, continue it as a project for yourself, but not necessarily for everyone else.

Also, The Send( and Get( commands won't work, unless you have the arduino acknowledge them like another calc.  You'll have to talk to quigibo about the exact specs of that.