New software and hardware will be announced here

updated both brickv & brickd on a RPi5 running Bookworm.

The brickd start error:
brickd: error while loading shared libraries: libudev.so.1: ELF load command address/offset not page-aligned

Updated using:
 

echo ------------------
echo Brick Daemon
echo ------------------

sudo apt-get -y install libusb-1.0-0 libudev0 pm-utils
sudo wget https://download.tinkerforge.com/tools/brickd/linux/brickd_linux_latest_armhf.deb
sudo dpkg -i brickd_linux_latest_armhf.deb
echo Done

echo ------------------
echo Brick Viewer
echo ------------------
sudo apt-get install -y python3 python3-pyqt5 python3-pyqt5.qtopengl python3-serial python3-tz python3-tzlocal
sudo wget https://download.tinkerforge.com/tools/brickv/linux/brickv_linux_latest.deb
sudo dpkg -i brickv_linux_latest.deb
echo Done

custom_backend_modules = ESP32 Brick
                         Mqtt
                         Mqtt Auto Discovery

custom_frontend_modules = Device Name
                          Mqtt

custom_frontend_components = Proxy
                             Network Group $ Open
                               Mqtt
custom_frontend_status_components = Device Name
                                    Mqtt

and set default_envs = esp32

Successfully build and uploaded to the ESP32 Brick > firmware 2.1.0+68fe6da7 (created 10/26/2025 07:51:19 PM)

In the ESP32 brick web interface enabled MQTT, set broker IP and removed topic prefix.
After reboot, the log shows:
7,151 | mqtt             | Connected to broker at mqtt://ip-address:1883.

Tested to set the color of the rgbled, but nothing happens:
mosquitto_pub -I esp32-Zji -t tinkerforge/request/rgb_led_v2_bricklet/Jng/set_rgb_value -m '{"r":0,"g":127,"b":130}'

Opened 2 terminals:
1. Running moqsquitto broker. Log entry:
1761511274: New client connected from 127.0.0.1:50612 as esp32-Zji41609 (p2, c1, k60).
1761511274: Client esp32-Zji41609 disconnected.

2. Running mosquitto_sub -v -t 'tinkerforge/#'. Log entries:
tinkerforge/request/rgb_led_v2_bricklet/Jng/set_rgb_value {"r":0, "g":127, "b":120}
tinkerforge/request/rgb_led_v2_bricklet/Jng/set_rgb_value {"r":0,"g":127,"b":130}

and some MQTT related:

tinkerforge/mqtt/config_modified {"modified":3}
tinkerforge/mqtt/config {"enable_mqtt":true,"broker_host":"NNN.NNN.NNN.NNN","broker_port":1883,"broker_username":"","broker_password":"","global_topic_prefix":"","client_name":"esp32-Zji","interval":1,"protocol":0,"cert_id":-1,"client_cert_id":-1,"client_key_id":-1,"path":"","read_only":false}
tinkerforge/mqtt/state {"connection_state":2,"connection_start":7780,"connection_end":0,"last_error":0}
tinkerforge/mqtt/auto_discovery_config_modified {"modified":3}
tinkerforge/mqtt/auto_discovery_config {"auto_discovery_mode":0,"auto_discovery_prefix":"homeassistant"}

Have also tried several topic prefix, but no state change.

Any idea what is missing?
 

I put the latest trixie image with desktop on a raspberry pi 4.

When i try to install brickd ,after made the latest update and upgrades, 

with sudo apt install brickd

i receive an error with libgpiod  version 2 not supported in trixie. 

and i cannot install brickd with libgpiod 3version 3.

Can you tell ne if there is a fix/work around to install brickd on trixie  rasbian.

Thanks

Patrick

In Updates / Flashing, the extension tab lets me select "WIFI EXtension 2.0 (0.0.0) @ Master Brick 3.1 [UID] (2.5.2)", and I can select firmware and hit Flash. Doing so pauses on "Connecting to bootloader" for about a minute before giving me "Error during Extension flashing: Failed to connect to ESP8266". I have tried multiple different cables and multiple master bricks, and all give the same problem. Is it just a bad extension module?

It looks like a great solution for our building, but not being able to use third party chargers (even if the functionality were limited) is simply disqualifying.

I get this error in the /var/log/brickd.log

2024-01-16 18:06:36.731765 <I> <main_linux.c:375> Running on Linux system (sysname: Linux, release: 6.1.0-rpi6-rpi-2712, version: #1 SMP PREEMPT Debian 1:6.1.58-1+rpt2 (2023-10-27), machine: aarch64)
libusb: warning [libusb_init] installing new context as implicit default
2024-01-16 18:06:36.735775 <I> <bricklet.c:521> Using bricklet.* section in config file
2024-01-16 18:06:36.735783 <I> <bricklet.c:530> Found Bricklet port A (spidev: /dev/spidev0.0, driver: gpio, name: gpio23, num: 23)
2024-01-16 18:06:36.735835 <I> <bricklet_stack_linux.c:129> Using BCM2835 backend for Bricklets (Raspberry Pi detected)
2024-01-16 18:06:36.735855 <E> <vcgencmd.c:185> Could not open /dev/vchiq for writing: ENOENT (2)
2024-01-16 18:06:36.735858 <E> <bricklet_stack_linux_bcm2835.c:65> Could not read Raspberry Pi core_freq config

Is it possible to connect more than 4 bricklets in a single setup? I am using a Pi Zero 2W together with HAT Zero which has 4 bricklet connectors. So in essence... can I extend the initial 4 ports of the HAT?

I recently procured an AMT103 rotary incremental encoder for a brushless motor.

The outputs of the encoder are the A, B, and X channels, as shown in this photo and the corresponding CMOS voltage square waveforms are presented in this photo. For my project, I use 2048 PPR.

I want to connect the outputs of the encoder on a Bricklet. What bricklet would you suggest for this application? I was thinking of the IO-4 Bricklet 2.0 as a choice. Would this work?

Thanks a lot!

I have a tinkerforge weather station to which I added a CO2 bricklet, among other sensors. Recently, the CO2 bricklet has started displaying inaccurate values, sometimes dropping to 0 ppm, even though the minimum reading should be around 400 ppm. Do you have any idea what might be causing this issue? Should I consider replacing the bricklet?

I was testing the accelerometer and I got the following error. Any idea what could be the reasons? 

Error : 10.09.2024 14:45:04;Accelerometer Bricklet 2.0;25Ed;Acceleration;ERROR[Accelerometer Bricklet 2.0-Acceleration]: Did not receive response for function 255 in time (-1);

 

I am trying to generate a torque-current curve for the NEMA 17 stepper motor I have using the Voltage/Current Bricklet 2.0 and a Silent Stepper Bricklet 2.0. I have a lever arm attached to the stepper motor, which is powered with 24V. However, every time my motor is stalled (the arm hits a load cell), the motor jitters as if it is skipping steps (as expected).

Is there a way to make my motor not jitter when it is stalled and just draw the appropriate amount of current? What setting should I look into changing? Or is this not possible? Ideally, I'd like it to act like a stalled brushed or brushless motor and draw its stall current without vibrating so much at stall. 

Thank you!

based on the specifications documented on your website, the Laser Range Finder Bricklet 2.0 should be able to measure distances lower than 5 cm.
In my first tests, I couldn't measure distances lower than 5 cm though. Is this a technical limit?

Cheers
Claudio

Technical specifications:
Distance (Range, Resolution): 0-40m, 1cm
Accuracy <5m: ±2.5cm (nonlinearity present below 1m)

2024-07-27 13:21:51.398294 <I> <main_linux.c:385> Brick Daemon 2.4.6 started (architecture: arm64, pid: 2212, daemonized: 1)
2024-07-27 13:21:51.398344 <I> <main_linux.c:391> Running on Linux system (sysname: Linux, release: 6.1.21-v8+, version: #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023, machine: aarch64)
2024-07-27 13:21:51.409885 <I> <bricklet.c:274> Found supported HAT product_id 0x084e in device tree, using default HAT Brick config
2024-07-27 13:21:51.409905 <I> <bricklet.c:315> Found Bricklet port A (spidev: /dev/spidev0.0, driver: gpio, name: GPIO23, num: 23)
2024-07-27 13:21:51.409988 <I> <bricklet_stack_linux.c:87> Using spidev backend for Bricklets, because Raspberry Pi without BCM2835 detected
2024-07-27 13:21:51.411273 <I> <bricklet.c:315> Found Bricklet port B (spidev: /dev/spidev0.0, driver: gpio, name: GPIO22, num: 22)
2024-07-27 13:21:51.412419 <I> <bricklet.c:315> Found Bricklet port C (spidev: /dev/spidev0.0, driver: gpio, name: GPIO25, num: 25)
2024-07-27 13:21:51.413494 <I> <bricklet.c:315> Found Bricklet port D (spidev: /dev/spidev0.0, driver: gpio, name: GPIO26, num: 26)
2024-07-27 13:21:51.414650 <I> <bricklet.c:315> Found Bricklet port E (spidev: /dev/spidev0.0, driver: gpio, name: GPIO27, num: 27)
2024-07-27 13:21:51.415818 <I> <bricklet.c:315> Found Bricklet port F (spidev: /dev/spidev0.0, driver: gpio, name: GPIO24, num: 24)
2024-07-27 13:21:51.416855 <I> <bricklet.c:315> Found Bricklet port G (spidev: /dev/spidev0.0, driver: gpio, name: GPIO7, num: 7)
2024-07-27 13:21:51.417584 <E> <bricklet_stack_linux_spidev.c:263> Could not find line GPIO7
2024-07-27 13:21:52.417727 <I> <main_linux.c:579> Brick Daemon 2.4.6 stopped

Any ideas on what went wrong? Also downgrading to brickd 2.4.3 seems not available with aptget. There it did connect.

Regards
Amely

I am having a small problem with the GPS Bricklet 2.0 (FW 2.0.7).

When I set the fix LED configuration to 4 (PPS) this effectively switches the LED off.

With a GPS Bricklet 3.0 this works as expected: the LED blinks once per second.

Both Bricklets have a fix.

What am I doing wrong?

The LED Strip Bricklet 2.0 can be connected to the DC power supply line for the LEDs it controls. What is the maximum DC voltage the Bricklet can safely handle?

I can't find this in the docs.

I'm running into trouble connecting multiple master bricks over USB to my PC. I have 3 master bricks installed in different rooms in my attic, and connect those with USB cables to a powered USB Hub, which is connected to my PC. However, if I connect more then 3 master bricks to the HUB brickv can no longer connect to brickd. If I attach 2 master bricks, then connect with brickv, and then connect the 3rd master brick to the USB Hub, I can see the third brick appear in brickv less then a second after plugging it in. But If I then disconnect brickv and try to reconnect it fails, and keeps failing until I disconnect one of the bricks.

If i remember correctly I also get problems if I connect 2 master bricks with USB cables to 2 different USB ports on my Macbook.

Are there any such problems known to you?

These use-cases are quite important to my setup, so I would be more then happy to give more details on this problem in a Google Hangout or something.

Kind regards,

Geert Schuring.

This morning I wanted to order some parts including the HAT Brick, but the HAT Brick is listed as "out of stock".

Will it be available again, or will it be replaced with something else? And is there a timeline for this?

Any info would be welcome.

Is there really no way to reliably identify the user by the Android  smartphone?  I think that such a  Funcionality is super  important.

your documentation states: "The Ethernet Extension can be used together with a Step-Down Power Supply."
Does it mean that, when powering the stack with your Ethernet POE Extension and adding a Step-Down Power Supply to the bottom of the stack, I get stable 5V output voltage of the Step-Down Power Supply?

Cheers
Claudio

But further down the page:

Quote

 

Ethernet Master Extension with PoE is at the moment out of stock due to supply shortages of the RJ45 jack. We are ready for production but since the RJ45 jack is not available we can't start production. We expect that we can start production in February 2022.

 

My emphasis. Can somebody clarify?

I would like to know if you still plan to add Galileo reception to the GPS Bricklet 2.0. If yes, do you have a release schedule ?

I have not found any other news than these ones : https://www.tinkerforge.com/en/blog/gps-bricklet-20-is-now-available/. Are they the latest ?

Thanks in advance !

I don't see any examples how to extend callback listeners or create new ones. Just an example with no meaning in Java from the documentation.

device.addExampleListener(new BrickletServoV2.ExampleListener() {
    public void property(int value) {
        System.out.println("Value: " + value);
    }
});

For the servo there a 2 OOTB examples, but I want to create my own for getCurrentPosition or current used on the servo as example. How do I implement this properly ?

Regards,
Rik