WIZnet

Device online.
Still invisible?

WIZnet’s W55RP20 SNMPv3 SDK is now on GitHub.

GET / SET / TRAP.
SNMPv3 auth + privacy.
Hardware TCP/IP offload.

Small Ethernet devices should not be black boxes in the field.

Link is in the first comment.

What should every embedded device expose first — uptime, link status, temperature, or firmware version?

The drone isn’t the hard part.
The link home is.

This Maker post looks at a Japanese engineering diary about routing Pixhawk MAVLink telemetry over LTE, 5G, and Starlink.

The real issue is not just “send data to the cloud.”

The airborne side may sit behind carrier-grade NAT, so the ground station cannot always open a session toward the drone first.

That is where WIZ-IP20 becomes interesting:
Pixhawk UART telemetry
to Serial-to-Ethernet
to IP backhaul.

Important note:
This is a design proposal / research diary, not a verified flight test.

Links are in the first comment.

For BVLOS telemetry, what would you solve first — NAT, latency, power, or link failover?

The machine speaks RS232.
The sensor speaks RS485.
The customer wants Ethernet.

WIZ-IP32 is a compact dual Serial-to-Ethernet module for this kind of retrofit job:
two serial ports, 10/100 Ethernet, TCP / UDP, Modbus, and configuration via AT commands, web page, or WIZS2E ConfigTool.

The practical idea:
keep the serial device logic,
add a wired Ethernet path,
avoid turning every retrofit into a full networking project.

Product link is in the first comment.

When adding Ethernet to an existing serial device, what usually breaks the schedule first — wiring, protocol mapping, configuration, or field reliability?

The AI gets the hype.
The control board does the work.

This STM32 Nucleo F446RE board is a hardware hub for a small autonomous vehicle platform:
motor PWM, relays, RS-485, digital I/O, RGB status, and W5500 Ethernet for wired telemetry, commands, and diagnostics.

The important split:
the STM32 handles local vehicle I/O.
Ethernet handles supervision, testing, and system integration.

Project link is in the first comment.

What would you debug first on a vehicle board — power, PWM, RS-485, or Ethernet?