MOTM

This raises an interesting question-   all of the MOTM gear we've come
to know and love comes with full schematics, and uses 'off the shelf'
components for the most part, meaning we'll *probably* have an easy time
repairing these modules as parts slowly fail over the many years to
come.  With a box like the MOTM-650, and its associated software, the
equivalent practice would be...

[cue spooky theremin music with strings...]

OPEN SOURCE

Now, I'm not an open source zealot, and I don't have any interest in
pushing Paul to move his trade secrets out into the public domain- a lot
of time and effort went into writing the firmware behind the 650, and
apparently also to writing the updater client.  But- in the interest of
true future-proof architechture, making both the firmware and the
updater open source would 'help.'  It wouldn't solve the problems
automatically, but it would potentially change the future landscape of
the module.

It's just some food for thought.

-Geoff

>you gonna publish the handshaking spec and protocol? there's no reason to
>keep it secret, and it keeps this box from becoming obsolete as the OSes
>change. Also, linux people can solve updater problem themselves.
>
>--mikes
>
>