The Industrial Dual Analog In Bricklet can be used to extend the features of Bricks by the capability to precisely measure voltages. Both channels of the Bricklet are calibrated. The voltage measurement can used with an extremely high level of confidence.
With configurable events it is possible to react on changing voltages without polling.
|Current Consumption||15mW (3mA at 5V)|
|Measurement Range||-35V to +35V (DC)|
|Accuracy||0.1% / ±4mV full scale|
|Maximum Output Current||150mA (3.3V), 150mA (5V)|
|Dimensions (W x D x H)||40 x 40 x 11mm (1.57 x 1.57 x 0.43")|
The Industrial Dual Analog In Bricklet has an 8 pole terminal. Please see the picture below for the pinout.
To test a Industrial Dual Analog In Bricklet 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 Industrial Dual Analog In Bricklet to a Brick with a Bricklet Cable. Additionally connect a DC voltage you want to measure to the Bricklet. For testing purposes connect the 3.3V output pin to the IN0- pin and connect the GND pin to the IN0+ pin.
If you connect the Brick to the PC over USB, you should see a new tab named "Industrial Dual Analog In Bricklet" in the Brick Viewer after a moment. Select this tab. If everything went as expected you can now see the voltage in Volt and a graph that shows the voltage over time.
After this test you can go on with writing your own application. See the Programming Interface section for the API of the Industrial Dual Analog In Bricklet and examples in different programming languages.
A laser-cut case for the Industrial Dual Analog In Bricklet is available.
The assembly is easiest if you follow the following steps:
Below you can see an exploded assembly drawing of the Industrial Dual Analog In Bricklet 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|