Difference between revisions of "Firmware-72 Operation"
(Created page with "The USB-microDig can function in host mode, or stand-alone mode. Host mode is intended for using the USB-microDig with a computer that processes the sensor data and/or control...") |
|||
| Line 1: | Line 1: | ||
The USB-microDig can function in host mode, or stand-alone mode. Host mode is intended for using the USB-microDig with a computer that processes the sensor data and/or controls the actuator outputs, while stand-alone mode is intended for using the USB-microDig either on its own, where sensor data is mapped to actuator outputs, or together with other MIDI capable devices. | The USB-microDig can function in host mode, or stand-alone mode. Host mode is intended for using the USB-microDig with a computer that processes the sensor data and/or controls the actuator outputs, while stand-alone mode is intended for using the USB-microDig either on its own, where sensor data is mapped to actuator outputs, or together with other MIDI capable devices. | ||
| + | |||
| + | To set the USB-microDig mode, use the SET MODE command. | ||
| + | |||
| + | |||
| + | ==Standalone Mode== | ||
Stand-alone mode allows the USB-microDig to be used with its internal signal processing so that another MIDI capable device (which could be a computer) can directly use the calculated end result. Processing and mapping of sensor data, and control of actuator outputs happens in the USB-microDig itself, so once it has been programmed using our configuration software (free to download from our website) it can run by itself or it can be patched to MIDI-capable software or devices. This mode allows sensor inputs to be mapped to channel voice MIDI messages. Stand-alone mode commands (including STREAM and INTERVAL), contrary to host mode commands, change the settings stored in non-volatile memory as well as volatile memory. Stand-alone mode commands are executed in both modes of operation, even though in host mode no channel voice MIDI messages are output to reflect any changed settings. | Stand-alone mode allows the USB-microDig to be used with its internal signal processing so that another MIDI capable device (which could be a computer) can directly use the calculated end result. Processing and mapping of sensor data, and control of actuator outputs happens in the USB-microDig itself, so once it has been programmed using our configuration software (free to download from our website) it can run by itself or it can be patched to MIDI-capable software or devices. This mode allows sensor inputs to be mapped to channel voice MIDI messages. Stand-alone mode commands (including STREAM and INTERVAL), contrary to host mode commands, change the settings stored in non-volatile memory as well as volatile memory. Stand-alone mode commands are executed in both modes of operation, even though in host mode no channel voice MIDI messages are output to reflect any changed settings. | ||
| + | |||
| + | |||
| + | ==Host Mode== | ||
Host mode requires that the USB-microDig is connected with a host computer to control and store the USB-microDig settings, and process the sensor data and/or control the actuator outputs. In host mode unprocessed, raw sensor values are output only as system exclusive MIDI messages (ie. no stand-alone mode type channel voice MIDI messages processed from sensor values are output). When using Max/MSP software, host mode allows multiple iCube / oCube Max/MSP objects for each USB-microDig (to this end, some of the commands are echoed back to the host computer). Host mode commands (except STREAM and INTERVAL), contrary to stand-alone mode commands, do not change the settings stored in non-volatile memory but only the settings stored in volatile memory. Generally, host mode commands have the same effect in either mode of operation – see for details below. | Host mode requires that the USB-microDig is connected with a host computer to control and store the USB-microDig settings, and process the sensor data and/or control the actuator outputs. In host mode unprocessed, raw sensor values are output only as system exclusive MIDI messages (ie. no stand-alone mode type channel voice MIDI messages processed from sensor values are output). When using Max/MSP software, host mode allows multiple iCube / oCube Max/MSP objects for each USB-microDig (to this end, some of the commands are echoed back to the host computer). Host mode commands (except STREAM and INTERVAL), contrary to stand-alone mode commands, do not change the settings stored in non-volatile memory but only the settings stored in volatile memory. Generally, host mode commands have the same effect in either mode of operation – see for details below. | ||
| + | |||
| + | |||
| + | ==Flow Control== | ||
In host mode the USB-microDig can detect when the COM port is open by the use of hardware data flow control (using the RTS and CTS pins of the COM port, see also the COM command below). If the software application you are using doesn’t have hardware data flow control (such as the Max/MSP serial object) then the COM port can be open but the USB-microDig pauses data processing and the IN and OUT LED on the USB-microDig will keep on flashing once a second until it receives a byte (that your software application sent). Once a byte has been received data processing resumes and the IN and OUT LED will only be ON momentarily once every second when data is transmitted as per their definition above, even after the COM port is closed. | In host mode the USB-microDig can detect when the COM port is open by the use of hardware data flow control (using the RTS and CTS pins of the COM port, see also the COM command below). If the software application you are using doesn’t have hardware data flow control (such as the Max/MSP serial object) then the COM port can be open but the USB-microDig pauses data processing and the IN and OUT LED on the USB-microDig will keep on flashing once a second until it receives a byte (that your software application sent). Once a byte has been received data processing resumes and the IN and OUT LED will only be ON momentarily once every second when data is transmitted as per their definition above, even after the COM port is closed. | ||
| Line 10: | Line 21: | ||
When the USB-microDig is in stand-alone mode data processing is never paused, it ignores data flow control and the IN and OUT LED will not blink once a second but only when data is transmitted. | When the USB-microDig is in stand-alone mode data processing is never paused, it ignores data flow control and the IN and OUT LED will not blink once a second but only when data is transmitted. | ||
| − | |||
| − | |||
Revision as of 03:26, 3 November 2015
The USB-microDig can function in host mode, or stand-alone mode. Host mode is intended for using the USB-microDig with a computer that processes the sensor data and/or controls the actuator outputs, while stand-alone mode is intended for using the USB-microDig either on its own, where sensor data is mapped to actuator outputs, or together with other MIDI capable devices.
To set the USB-microDig mode, use the SET MODE command.
Standalone Mode
Stand-alone mode allows the USB-microDig to be used with its internal signal processing so that another MIDI capable device (which could be a computer) can directly use the calculated end result. Processing and mapping of sensor data, and control of actuator outputs happens in the USB-microDig itself, so once it has been programmed using our configuration software (free to download from our website) it can run by itself or it can be patched to MIDI-capable software or devices. This mode allows sensor inputs to be mapped to channel voice MIDI messages. Stand-alone mode commands (including STREAM and INTERVAL), contrary to host mode commands, change the settings stored in non-volatile memory as well as volatile memory. Stand-alone mode commands are executed in both modes of operation, even though in host mode no channel voice MIDI messages are output to reflect any changed settings.
Host Mode
Host mode requires that the USB-microDig is connected with a host computer to control and store the USB-microDig settings, and process the sensor data and/or control the actuator outputs. In host mode unprocessed, raw sensor values are output only as system exclusive MIDI messages (ie. no stand-alone mode type channel voice MIDI messages processed from sensor values are output). When using Max/MSP software, host mode allows multiple iCube / oCube Max/MSP objects for each USB-microDig (to this end, some of the commands are echoed back to the host computer). Host mode commands (except STREAM and INTERVAL), contrary to stand-alone mode commands, do not change the settings stored in non-volatile memory but only the settings stored in volatile memory. Generally, host mode commands have the same effect in either mode of operation – see for details below.
Flow Control
In host mode the USB-microDig can detect when the COM port is open by the use of hardware data flow control (using the RTS and CTS pins of the COM port, see also the COM command below). If the software application you are using doesn’t have hardware data flow control (such as the Max/MSP serial object) then the COM port can be open but the USB-microDig pauses data processing and the IN and OUT LED on the USB-microDig will keep on flashing once a second until it receives a byte (that your software application sent). Once a byte has been received data processing resumes and the IN and OUT LED will only be ON momentarily once every second when data is transmitted as per their definition above, even after the COM port is closed.
If the software application uses hardware data flow control, and the USB-microDig is in host mode, when the USB-microDig COM port is closed (by default when the USB-microDig is being connected) the USB-microDig pauses data processing and the IN and OUT LED will blink again once every second.
When the USB-microDig is in stand-alone mode data processing is never paused, it ignores data flow control and the IN and OUT LED will not blink once a second but only when data is transmitted.
