[OSC_dev] OSC Servers

[Christopher Graham]

The OSC server for my MultiWind device includes what I call the data
streaming interface.  This allows a client to configure the server to
send to it a steam of messages from particular sensors on the
instrument.  Each sensor streams to a particular node in the address
space of the client, with the nodes named based on the sensors.  The
client can also configure the sampling rate of the entire device and a
rate divider for each sensor that reduces its sampling rate by that
multiple.  The client can also configure preprocessing to be done per
sensor including hysteresis, scaling, and conversion of continuous data
to level triggered data.



All data streaming messages go to a root node of /ds for data
streaming, and the nodes below /ds are named based on the module on
which a given sensor is located, and the name of the sensor.  The
device hardware supports streaming at up to 1000 samples per second. 
All samples are scaled to floating point OSC parameters in the range of
0.0 to 1.0.



There are meta commands in the server namespace for controlling data
streaming including enabling and disabling certain sensors, setting the
calibration parameters, starting and stopping streaming, etc.  I've
also provided for the streamed messages to include time tags to
de-jitter the values that flow from the sensors on the device hardware,
though USB or Bluetooth, to the Device Gateway on the host, and then to
OSC.



In effect the OSC client can register for "callbacks" based on
sensor-read events at a specified sample rate, subject to scaling and
suppression of noise using hysteresis and possibly level based triggers.



- Chris


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.create.ucsb.edu/pipermail/osc_dev/attachments/20080214/ead79d2e/attachment.html