ICube Max Plugin-40 Intro

From I-CubeX Wiki
Revision as of 05:28, 13 March 2018 by Admin (talk | contribs) (Created page with "The iCube Max plugin, or external object, provides a user interface for the configuration via an I-CubeX digitizer's outputs. <b>Sensor types</b> Digitizer inputs can proc...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

The iCube Max plugin, or external object, provides a user interface for the configuration via an I-CubeX digitizer's outputs.


Sensor types

Digitizer inputs can process data from analog and digital I2C sensors.

Analog sensors output a voltage. Some sensors only output two voltages representing two captured states such as contact or no contact, motion or no motion, near or far, etc. Other sensors output a very high number of different voltages, limited by the noise level introduced at various stages such as the transmission of the voltage by the cable connecting the sensor to the digitizer, until conversion to a digital representation by the digitizer. The digitizer's resolution limits the number of different voltages and hence sensor states that can be captured. All digitizers have a maximum 10-bit resolution, except for the 32-input Digitizer which has a 12-bit resolution.

I2C sensors are operated by the exchange of pulse trains that represent a series of bytes as commands/messages. Since the sensor data they capture is digitally transmitted the resolution is determined by the sensor and not limited by any cable noise.


iCube ins and outs

The iCube has an inlet for commands and a data outlet for each sensor. It can be configured to have 1 - 32 data outlets. Commands can be sent to the oCube as list messages.

The iCube has a separate inlet to receive MIDI bytes and a separate outlet to output MIDI bytes. The iCube has a separate outlet for confirmation and error messages.