The position of the potentiometer ranges from 0 (slider down) to 100 (slider up). A user can change the position of the potentiometer and it is possible to drive the potentiometer to any position with an integrated motor.
You can configure the potentiometer to hold the position. In this case it automatically drives back to the set-point when a user changes the position. If it is not configured to hold a position, the Bricklet will only drive to the set-point once and after that the user can control the position again.
The Motorized Linear Poti Bricklet has a 7 pole Bricklet connector and is connected to a Brick with a 7p-10p Bricklet cable.
|Current Consumption (motor off)||48.5mW (9.7mA at 5V)|
|Current Consumption (motor on)||465mW (93mA at 5V)|
|Mounting hole size||M3|
|Distance between mounting holes||120mm|
|Dimensions (W x D x H)||145 x 20 x 28mm (5.70 x 0.79 x 1.10")|
To test a Motorized Linear Poti 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 Motorized Linear Poti Bricklet to a Brick with a Bricklet Cable.
If you connect the Brick to the PC over USB, you should see a new tab named "Motorized Linear Poti Bricklet" in the Brick Viewer after a moment. Select this tab. If everything went as expected you can now control the position of the potentiometer with the GUI.
After this test you can go on with writing your own application. See the Programming Interface section for the API of the Motorized Linear Poti Bricklet and examples in different programming languages.
A laser-cut case for the Motorized Linear Poti Bricklet is available.
The assembly is easiest if you follow the following steps:
Below you can see an exploded assembly drawing of the Motorized Linear Poti 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|