HUSKYLENS 2 – High-Speed UART and I²C Communication Support
shingo243 2026-08-12 21:20:10 323 Views4 Replies Dear DFRobot Support Team,
I have some questions regarding the communication interfaces of the HUSKYLENS 2.
I am considering using the HUSKYLENS 2 for a high-speed line-tracking robot project. In this application, I would like to read the latest line-tracking result approximately every 1 ms, so communication latency is very important.
1. High-speed UART support
The maximum UART baud rate currently documented for the HUSKYLENS 2 appears to be 115200 bps.
Are there any plans to support higher UART baud rates in future firmware versions, such as:
230400 bps 460800 bps 921600 bps 1 MbpsAlternatively, is there any undocumented or experimental way to configure the HUSKYLENS 2 UART above 115200 bps?
For high-speed control applications, 115200 bps can become a communication bottleneck, so I would like to know whether higher-speed UART communication is technically possible on the HUSKYLENS 2 hardware.
2. I²C communication speed
I understand that the HUSKYLENS 2 supports I²C communication, but I could not find an official specification for the maximum supported I²C clock frequency.
Could you please confirm whether the HUSKYLENS 2 supports:
400 kHz I²C (Fast Mode) 1 MHz I²C (Fast Mode Plus)If these speeds are not officially supported, could you let me know whether they have been tested internally, or whether there is a recommended maximum I²C clock frequency?
3. I²C library implementation
I noticed that the official HUSKYLENS 2 library appears to configure the I²C clock to 100 kHz.
Is this 100 kHz setting simply a conservative/default setting, or is there a technical limitation in the HUSKYLENS 2 that prevents operation at 400 kHz or 1 MHz?
4. Recommended interface for high-speed control
For a line-tracking application where the host MCU would like to obtain the latest line position approximately every 1 ms, which communication interface and configuration would DFRobot recommend?
For example, would you recommend:
UART at 115200 bps
I²C at 400 kHz
I²C at 1 MHz
or another configuration?I would greatly appreciate any information regarding the maximum practical communication speed and the recommended configuration for low-latency, high-speed control applications.
Thank you very much for your support.
Best regards,
Below is the factual summary of the official response I received from DFRobot Technical Support.
UART Baud Rates
HuskyLens 2 supports 9600 and 115200 baud.
Main Processor
HuskyLens 2 uses the Kendryte K230 (dual‑core 1.6 GHz, 6 TOPS NPU).
Internal Architecture Disclosure
DFRobot stated that certain technical details are confidential.
They cannot confirm whether an auxiliary MCU (e.g., STM32) is used internally, as this information is not included in public documentation.
Future Firmware Plans
There are no current plans to support:
UART speeds above 115200
I2C Fast‑mode (400 kHz) or higher
If additional information becomes available, I will update this thread.
shingo243 HuskyLens 2 only supports 9600 and 115200 baud on UART — no 230400+ or 1 Mbps. The original HuskyLens had 1 Mbps, but the K230 in the HUSKYLENS 2 dropped it. The Wiki lists just those two rates.
For 1 ms polling: at 115200 a request/response frame is roughly 1–2 ms on the wire, but the K230 needs time to run inference and pack the result. The protocol doc shows the sensor returns BUSY (0x3D) if you hammer it too fast. I'd test with 5–10 ms first and see where the floor is before chasing 1 ms.If you want specific data, you can email the dfrobot technical support to ask
Jason.Miao I’m not happy that the time required just to exchange results stays the same, or even that the communication specs seem to be downgraded in HuskyLens 2 compared to the original.
I would like you to consider some kind of workaround or improvement that allows stable, higher‑speed communication if possible.
Also, where exactly should I contact technical support to ask about this?
Yeah, this is a hardware limit — the K230 UART controller in the HuskyLens 2 tops out at 115200, and the I2C bus is locked to 100 kHz in firmware with no documented fast-mode support. hardware-level questions, email [email protected]. They're the ones who can confirm whether a future firmware revision unlocks higher I2C clocks or if the K230 silicon itself is the bottleneck.
