The CAN Bricklet is discontinued. We are selling our remaining stock. The CAN Bricklet 2.0 is the recommended replacement.
The CAN Bricklet can be used to extend the features of Bricks by the capability to send and receive CAN data in a CAN bus.
The baudrate can be configured between 10kbit/s and 1Mbit/s. It is possible to apply filters to match for frames with a specific identifier.
|Current Consumption||30mW (6mA at 5V, idle)|
|Baudrate||10kbit/s - 1Mbit/s|
|Maximum Throughput||1000 frames per second*|
|Filters||Disabled / Accept all / Match / Match data / Match extended|
|Dimensions (W x D x H)||45 x 35 x 14mm (1.77 x 1.38 x 0.55")|
* 1000 frames per second equals to 44kbit/s to 128kbit/s depending on the size of the frames.
To test a CAN 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 CAN Bricklet to a Brick with a Bricklet Cable. Connect a CAN device to the CAN-L, CAN-H and GND terminals.
If you connect the Brick to the PC over USB, you should see a new tab named "CAN Bricklet" in the Brick Viewer after a moment. Select this tab. If everything went as expected you can now see the data that is send over the connected CAN bus.
After this test you can go on with writing your own application. See the Programming Interface section for the API of the CAN Bricklet and examples in different programming languages.
A laser-cut case for the CAN Bricklet is available.
The assembly is easiest if you follow the following steps:
Below you can see an exploded assembly drawing of the CAN 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|