The uOSC project reminded me of the Firmata project for Arduino. It is similar in that it is also an abstraction layer for the micro controller hardware and moves the coding from the micro controller to the host computer and in the process hides much of the low-level complexities of the hardware. It is different in that uOSC puts more emphasis on performance and timing accuracy than Firmata on Arduino can offer.
That said, you need to be familiar with OSC and still need to know about port pins, adc and pwm to make any good use of such a shift in paradigm.
It also (re)opens the debate of the Sensor Interface vs. Single Board Computer point-of-view in looking at hardware like Bit Whacker or Arduino. uOSC or Firmata places the application on the host and reduces the hardware to a sensor interface, whereas this hardware can also be used (and has a big reputation) as a stand-alone physical computing device in its own right, if programmed in its native language stored in on-chip Flash memory.
That said, I think uOSC is a great way to open up the world of physical computing to the MAX/MSP community and other users fluent in OSC but not so much in low-level coding.
Great job, Andy!
Slides from my talk are up, as promised, and some of the other links I mentioned…
At CNMAT, Music and Research a mutually reinforce each other. Part of the overall concept behind micro-OSC is to try to minimize user error when building new interfaces. Eliminating the need for the end user to write microcontroller firmware is therefore a goal of the project. Nearly the full feature set of USB-enabled PIC microcontrollers (ADC, PWM, GPIO, etc) are made available to the user through higher-level host-computer based software. The home page for micro-OSC, including a download link is found here, and there is some documentation here.
Support for several microcontroller boards is provided with micro-OSC: