Hi Björn,
I got it working with some tests (at least to change the backup value). You can get my workflow from my download area at this link: . From the resulting script, you must change the following values with your one:
my_access_key
my_secret_key
my_serial_number
Soc_backup_value (this value is included 2 times)

Then you can import the resulting JSON file in your N8N and try it. It isn’t still in the best version, but it can be a start point.
In a few words, you must change the URL string and include the same query both in the secret and the HTTP PUT body.

Hope this helps you.

Hi Paul. I think the speed you achieved is already a good number and it is similar to a test from another user on the Wiznet blog (https://maker.wiznet.io/scarlet/projects/boost-your-w5100s-evb-pico-with-hardwired-tcp-ip/).
On the theory side, the Pico runs at 125MHz (125Mbps), but the SPI clock divides this by 2 (to get a clean signal border) -> now around 60Mbps. On top of this, internal buffers (shared between the CPU sockets) gives you another limitation.
Another limitation comes from the MicroPython framework, which takes a number of cycles to send a bit on the wire. For example, if you would transmit data from a C firmware I think it would give you a some speed improvements, but you would lose the MicroPython simplicity and you wouldn’t get so big speed improvements.

At the end, i think thath reaching 8-10 Mbps is a great result for Raspberry Pi Pico with the WIZnet Ethernet HAT

I’ve been working on a door access control system using the PICO and WIZNET Ethernet hat, I really like both devices. However, I can’t get the Ethernet have to connect at 100Mb/s, ( it’s fine at 10Mb/s ) and this is not a problem for my application using MQTT, but the system is up and running, but the 10Mb/s connection speed is an itch I’d like to scratch. Have you noticed the same behaviour ? Or is it just a problem between my Wiznet and TPLink swich ?

About my project: I have a Pico 2 with a Wiznet hat managing a cheap ( from Amazon ) RFID card reader over the Weigand protocol. The PICO sends MQTT requests when a Card is presented to a back-end system that interfaces with a MySQL db that provides user authorisation, and card validity. Once the credentials are authorised, the Acknowledge is sent back to the card reader, but also to another PICO and WIznet device to manage the electronic door lock. This is because the external card reader is physically distant from the internal door lock.

Next thing, I’d like to try is audio, since the PICO 2 is idle 99% of the time, I think it could handle digitised speech too.

Anyway, interested to hear your feedback on the WIZnet 10/100 Mb/s issue

Glad it helped you too, Andy. Thank you for your feedback!

Yesterday a fellow announced he had built ROS 2 native on PiOS Trixie Desktop. While I was disappointed with the ROS 2 visualization running on my Pi5 robots, the Raspberry Pi 5 seems to be able to just barely handle what I ask of it with ROS 2 over Ubuntu server. (Stating NAV2 sometimes crashed due to 140% load, but not always.)

My robots have been powered by Raspberry Pi for 8 years, and every year a new OS, or new Pi, or new ROS configuration or change of all three. Up until recently, none of my robots ever saw more than 80% load, but I feel that with ROS or LLMs (with a MCP manager) my Pi 5 may have finally hit the performance/power wall. (My oldest Pi3 robot gets 8 hours playtime on a charge, while my newest Pi5 robot only gets 1-2 hours on a battery twice the capacity. I always want my bots to be fully autonomous so performance/ power is the decider.)

Thank you for your feedback, Noa. That’s more distance than what I could expect!

Thank you Hans, enjoy your forum on Raspberry PI!