You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|float getVoltage(void)|Gets the analog input reading, as an absolute voltage in Volt units.|
14
+
|float getVoltageSync(void)|This is very similar to getVoltage(), but will wait for a new sample to arrive before returning.|
15
+
|float getReference(void)|Gets the maximum value against which read() values are scaled.|
16
+
|float read(void)|Gets the analog input reading, as a scaled real value between 0 and 1.|
17
+
|float readSync(void)|This is very similar to read(), but will wait for a new sample to arrive before returning.|
18
+
|void setBuffer(int)|Initializes or destroys an internal buffer, used for queuing sampled data.|
19
+
|int getOverflowCount(void)|Gets the number of samples that have been dropped as a result of overflow.|
20
+
|int available(void)|Gets the number of samples currently in the buffer. Reading that many samples is guaranteed not to block.|
21
+
|float readBuffered(void)|Read a sample from the internal buffer. This method will block until at least one sample is available.|
22
+
|float getVoltageBuffered(void)|Read a sample from the internal buffer. This method will block until at least one sample is available.|
23
+
|float getSampleRate(void)|Gets the sample rate used for obtaining buffered samples.|
16
24
17
-
## Investigating connection issues
25
+
## PulseInput
18
26
19
-
When you plug an IOIO-OTG board into a USB port on your Linux machine, you can check which serial port has been
20
-
assigned to the device by using various commands and tools. Here are a few methods:
27
+
This interface represents PulseInput functionality, providing methods for pulse and frequency measurements.
21
28
22
-
## Check dmesg Logs:
29
+
`io = openPulseInput(pin [, 1])`
23
30
24
-
Open a terminal and run the following command to view the kernel logs:
31
+
| Name | Description |
32
+
|---------|---------------|
33
+
|float getDuration(void)|Gets the pulse duration in case of pulse measurement mode, or the period in case of frequency mode.|
34
+
|float getDurationSync(void)|This is very similar to getDuration(), but will wait for a new sample to arrive before returning.|
35
+
|float getDurationBuffered(void)|Reads a single measurement from the queue. If the queue is empty, will block until more data arrives.|
36
+
|float waitPulseGetDuration(void)|@deprecated Please use getDurationBuffered() instead.|
37
+
|float getFrequency(void)|Gets the momentary frequency of the measured signal. When scaling is used, this is compensated for here.|
38
+
|float getFrequencySync(void)|This is very similar to getFrequency(), but will wait for a new sample to arrive before returning.|
25
39
26
-
```
27
-
dmesg | tail
28
-
```
40
+
## DigitalInput
29
41
30
-
Look for lines related to the connected USB device. The assigned serial port might be mentioned in the logs.
42
+
This interface represents DigitalInput functionality, providing methods to read digital input pin values and wait for specific logical levels.
31
43
32
-
## Use lsusb
44
+
`io = openDigitalInput(pin [, 1])`
33
45
34
-
Use lsusb to list the connected USB devices and note the device ID.
46
+
| Name | Description |
47
+
|---------|---------------|
48
+
|int read(void)|Read the value sensed on the pin. May block for a few milliseconds if called right after creation of the instance.|
49
+
|void waitForValue(int)|Block until a desired logical level is sensed. The calling thread can be interrupted for aborting this operation.|
35
50
36
-
```
37
-
lsusb
38
-
```
51
+
## CapSense
39
52
40
-
## Use udevadm to get detailed information about the device:
53
+
This interface represents the CapSense functionality, allowing capacitance readings and threshold-based operations.
41
54
42
-
```
43
-
udevadm info -a -n /dev/ttyUSB0
44
-
```
45
-
Replace /dev/ttyUSB0 with the appropriate device file.
55
+
`io = openCapSense(pin [, 1])`
46
56
47
-
## Check /dev/ Directory:
57
+
| Name | Description |
58
+
|---------|---------------|
59
+
|float read(void)|Gets the capacitance reading. It typically takes a few milliseconds.|
60
+
|float readSync(void)|This is very similar to read(), but will wait for a new sample to arrive before returning.|
61
+
|void setFilterCoef(float)|Sets the low-pass filter coefficient. This coefficient is the typical time constant of the system.|
62
+
|void waitOver(float)|Block until sensed capacitance becomes greater than a given threshold.|
63
+
|void waitOverSync(float)|This is very similar to waitOver(float), but will wait for a new sample to arrive before returning.|
64
+
|void waitUnder(float)|Block until sensed capacitance becomes less than a given threshold.|
65
+
|void waitUnderSync(float)|This is very similar to waitUnder(float), but will wait for a new sample to arrive before returning.|
48
66
49
-
After connecting the device, run the following command to list the /dev/ directory:
67
+
## DigitalOutput
50
68
51
-
``
52
-
ls /dev/ttyUSB*
53
-
``
69
+
A pin used for digital output. A digital output pin can be used to generate logic-level signals. DigitalOutput instances are obtained by calling IOIO#openDigitalOutput. The value of the pin is set by calling write. The instance is alive since its creation. If the connection with the IOIO drops at any point, the instance transitions to a disconnected state, in which every attempt to use the pin (except close()) will throw a ConnectionLostException. Whenever close() is invoked the instance may no longer be used. Any resources associated with it are freed and can be reused. Typical usage:
54
70
55
-
This should show you the assigned serial port(s) for connected USB devices.
71
+
`io = openDigitalOutput(pin [, 1])`
72
+
73
+
| Name | Description |
74
+
|---------|---------------|
75
+
|void write(int)|The output. true is logical \"HIGH\", false is logical \"LOW\".|
76
+
77
+
## PwmOutput
78
+
79
+
A pin used for PWM (Pulse-Width Modulation) output. A PWM pin produces a logic-level PWM signal. These signals are typically used for simulating analog outputs for controlling the intensity of LEDs, the rotation speed of motors, etc. They are also frequently used for controlling hobby servo motors. PwmOutput instances are obtained by calling IOIO#openPwmOutput. When used for motors and LEDs, a frequency of several KHz is typically used, where there is a trade-off between switching power-loses and smoothness of operation. The pulse width is typically set by specifying the duty cycle, with the setDutyCycle method. A duty cycle of 0 is \"off\", a duty cycle of 1 is \"on\", and every intermediate value produces an intermediate intensity. Please note that any devices consuming more than 20mA of current (e.g. motors) should not by directly connected the the IOIO pins, but rather through an amplification circuit suited for the specific load. When used for hobby servos, the PWM signal is rather used for encoding of the desired angle the motor should go to. By standard, a 100Hz signal is used and the pulse width is varied between 1ms and 2ms (corresponding to both extremes of the shaft angle), using setPulseWidth. The instance is alive since its creation. If the connection with the IOIO drops at any point, the instance transitions to a disconnected state, in which every attempt to use the pin (except close()) will throw a ConnectionLostException. Whenever close() is invoked the instance may no longer be used. Any resources associated with it are freed and can be reused. Typical usage (fading LED):
80
+
81
+
`io = openPwmOutput(pin [, 1])`
82
+
83
+
| Name | Description |
84
+
|---------|---------------|
85
+
|void setDutyCycle(float)|Sets the duty cycle of the PWM output. The duty cycle is defined to be the pulse width divided by the total cycle period. For absolute control of the pulse with, consider using setPulseWidth.|
86
+
|void setPulseWidth(float)|Sets the pulse width of the PWM output. The pulse width is duration of the high-time within a single period of the signal. For relative control of the pulse with, consider using setDutyCycle.|
87
+
88
+
## Optional second argument
89
+
90
+
Option second argument `1` causes the following additional IOIO methods to be attached:
91
+
92
+
| Name | Description |
93
+
|---------|---------------|
94
+
| void beginBatch()|Start a batch of operations. This is strictly an optimization and will not change functionality|
95
+
| void disconnect()|Closes the connection to the board, or aborts a connection process started with waitForConnect()|
96
+
| void endBatch()|End a batch of operations.|
97
+
| void hardReset()|Equivalent to disconnecting and reconnecting the board power supply.|
98
+
| void softReset()|Resets the entire state (returning to initial state), without dropping the connection.|
99
+
| void sync()|Sends a message to the IOIO and waits for an echo.|
100
+
| void waitForConnect()|Establishes connection with the IOIO board.|
101
+
| void waitForDisconnect()|Blocks until IOIO has been disconnected and all connection-related resources have been freed so that a new connection can be attempted.|
0 commit comments