The Bricklet features 4 I/O pins that can be independently configured as digital inputs or outputs. Each input pin can additionally be configured with a pull-up or as interrupt source. Via terminal blocks all signals can be accessed. Two additional terminal blocks deliver 3.3V and GND.
Human interfaces, such as switches, push-buttons and LEDs are typical applications of this Bricklet.
The IO-4 Bricklet 2.0 has a 7 pole Bricklet connector and is connected to a Brick with a 7p-10p Bricklet cable.
|Current Consumption||30mW (6mA at 5V)|
|I/O Voltages||Fixed 3.3V|
|Maximum Output Current||50mA** (per output pin), 100mA (3.3V fixed output pin)|
|Maximum API Calls*||set-value (1kHz), get-value (0.5kHz), callbacks (1kHz)|
|Dimensions (W x D x H)||35 x 35 x 14mm (1.38 x 1.38 x 0.55")|
* depends on your system (OS, CPU etc.)
** 50mA per pin, but max 130mA over all pins
To test a IO-4 Bricklet 2.0 you need to have Brick Daemon and Brick Viewer installed. Brick Daemon acts as a proxy between the USB interface of the Bricks and the API bindings. Brick Viewer connects to Brick Daemon. It helps to figure out basic information about the connected Bricks and Bricklets and allows to test them.
Connect the IO-4 Bricklet 2.0 to a Brick with a Bricklet Cable.
If you connect the Brick to the PC over USB, you should see a new tab named "IO-4 Bricklet 2.0" in the Brick Viewer after a moment. Select this tab. If everything went as expected the Brick Viewer should look as depicted below.
After this test you can go on with writing your own application. See the Programming Interface section for the API of the IO-4 Bricklet 2.0 and examples in different programming languages.
Each channel can be configured as input/output and in case of an input pin as pull-up. The current state is depicted in a table.
A laser-cut case for the IO-4 Bricklet 2.0 is available.
The assembly is easiest if you follow the following steps:
Below you can see an exploded assembly drawing of the IO-4 Bricklet 2.0 case:
Hint: There is a protective film on both sides of the plates, you have to remove it before assembly.
See Programming Interface for a detailed description.
|Visual Basic .NET||API||Examples||Installation|