Case Active

Campus IoT Kit Upgrade (Alias)

Redeveloped ESP32 + MicroPython education hardware kits with platform-linked teaching workflows, while contributing common libraries and examples to the Aily Blockly ecosystem.

Published: Dec 1, 2025 · Updated: Feb 5, 2026

My role

Device assessment, MicroPython toolchain development, and teaching-workflow integration

Starting point

Devices, firmware, and curriculum were maintained separately, making onboarding and on-site troubleshooting dependent on individual hardware knowledge.

Problem to solve

Legacy hardware was hard to extend, while curriculum updates and device behavior drifted apart, increasing maintenance cost.

Constraints

Existing ESP32 devices and teaching environments had to remain compatible
Network conditions and instructor technical experience varied by site
The collaboration is ongoing, so client data and full business configuration cannot be disclosed

Key decisions and implementation

Standardized device communication and introduced script-based configuration, then linked it to automated curriculum generation. Also contributed common libraries and program examples to Aily Blockly (an AI-driven embedded IDE) as an ecosystem co-builder.

Delivered results

Established one onboarding and configuration process for new devices
Put curriculum examples and device capabilities into a reusable versioned structure
Created troubleshooting records and handoff notes for field use
Contributed common libraries and example programs to Aily Blockly ecosystem

Publishable evidence

Public Aily Blockly libraries repository
ESP32 and MicroPython curriculum toolchain implementation
Device configuration, examples, and troubleshooting documentation

Inspect public evidence→

Evidence and confidentiality boundary

Collaboration is ongoing, so only technical method and directional outcomes are disclosed.

Additional context

The key was not “adding AI to hardware,” but putting devices, content, and field operations into one maintainable workflow.

Human conversation

Clarify the problem before deciding whether development is needed.

Add me on WeChat or send an email. Xiaofeng personally reviews the business context.

Useful context

Your business and users
The most repetitive or error-prone step
The outcome you want
Your rough timing

Read and replied to by Eric Xiaofeng personally. No instant-response or auto-generated solution promise.

Talk on WeChat

Scan the QR code or copy the WeChat ID

ericodingf

Send requirements by email

Best for background, reference material, and a more structured brief

sheacoding@gmail.com →