Skip to content

Releases: orulink-ai/WatcheRobot-public

Wiki website (continuous)

Pre-release

Choose a tag to compare

@github-actions github-actions released this 16 Oct 02:52
980e476

{
"repository": "orulink-ai/WatcheRobot-public",
"sourceRef": "e89a5fd3ae9fa9115e5122e252ab90fe5dd0b72b",
"archive": "watcherobot-wiki-e89a5fd3ae9fa9115e5122e252ab90fe5dd0b72b-39012714406-1.tar.gz",
"sha256": "c2708f4a164e3c0f13778d0cdcf1ee973dae5a723a28304a1aa90f7ca9bcc565"
}

WatcheRobot v0.1.2 · ESP32 OTA v0.5.5 / STM32 v0.1.4

Choose a tag to compare

@orulink-wugui orulink-wugui released this 08 Oct 09:22
646a977

WatcheRobot 官方固件

设备 OTA:ESP32 v0.5.5 / STM32 v0.1.4,签名系统 0.2.5。增加 GitHub 与两个镜像自动换源,无需选择地区;优化 About 首页、设备详情和圆屏底部留白。保留供电、二次确认、签名、哈希和回滚。

正式 OTA 已实机通过:v0.5.4 检测新版本、下载、确认、激活、重启到 v0.5.5,启动后双 MCU 验证成功,再次检查显示已是最新。

首次安装可继续使用附件 v0.5.3 PTL 包,然后在屏幕升级。最新完整 v0.5.5 包、说明与验收见 ESP32 v0.5.5。其他组件及历史下载保留,以组合清单和 SHA256SUMS 为准。

已安装受信 OTA 基础固件的设备,联网且主页空闲后检查版本,新版本提示但不自动安装。第三方镜像可能超时或缓存旧版本。CI 因计费限制未运行,真实断电、海外多运营商、多机长稳及离线密钥备份仍待完成。

WatcheRobot 系统 v0.2.8 · ESP32 v0.5.8 / STM32 v0.1.4

Choose a tag to compare

@Mr-KID-github Mr-KID-github released this 14 Oct 16:05
646a977

ESP32 v0.5.8:返回导航、关机显示与默认 PTL 更新配置

  • 合入 PR269:统一应用退出与返回主页顺序,完善 JoyInside HTTP 取消/恢复及快速重入边界,关机反馈优先停止已有显示活动再展示关机界面。
  • 后续源码构建和烧录默认使用 PTL;SSCMA 配置保留为历史注释,Kconfig 不再开放选择,构建阶段拒绝错误后端。
  • 普通构建自动配置官方系统更新验签公钥和 rollback;拒绝静默替换不同的非空公钥。直接烧录已有镜像时检查镜像中是否包含可信公钥。
  • 正式版本关闭 Debug CLI,使用 ESP-IDF 6.0.2;STM32 保持 v0.1.4,Himax 使用已验证的 PTL 桥接镜像。没有混入本地未完成的 JoyInside SDK 改动。

系统在线更新版本为 v0.2.8(ESP32 v0.5.8 + STM32 v0.1.4)。客户端更新包只写入 bootloader、分区表、OTA 初始数据和 App;完整六分段包会同时写入语音模型和 storage 救援资源。使用条件和操作步骤见 CLIENT_FLASH_GUIDE.zh-CN.md。

完成正式构建、资源预算、完整主机回归、实际 LVGL 菜单/关机测试及发布包与签名校验;本轮未重新烧录实机,真人听感、长时间运行和断电恢复仍沿既有台架验收流程处理。

系统 v0.2.7 · ESP32 v0.5.7 / STM32 v0.1.4

Choose a tag to compare

@Mr-KID-github Mr-KID-github released this 14 Oct 13:56
646a977

ESP32 v0.5.7:实时对话动作与情绪切换音频优化

  • 新增七份 chat_v1 本地完整对话动作,完善动作完成跟踪与停止失败后的资源所有权。
  • SDK 音频播放保留选择的情绪与 PCM 嘴型,设备上报使用唯一身份。
  • RTC 接收改为队列事件唤醒与有限批量解码,降低突发音频包在接收队列中的丢弃。
  • 表情使用前帧缓存与像素变化区,左右眼分区收紧,星形按行栅格化;慢帧按完成时间跳过错过的刷新期限,避免连续追赶占用音频资源。
  • 保持正式信任公钥、rollback 和系统更新约束,关闭 Debug CLI,不包含台架注入代码或未完成的 JoyInside SDK 改动。STM32 保持已发布 v0.1.4。

前阶段 host 和真机测试显示音频长间隔部分改善,尚未达到所有场景无卡顿;慢帧时实际表情帧率可能下降。真人听感、回声、多轮内存稳定性和热点网络握手仍需验收,不将构建或队列丢弃为零等同声学无卡顿。

本版本正式构建与发布校验记录见同仓开发档案。固件包包含 SPIFFS 救援资源,SD 资源仍独立发布;普通 App OTA 不会补齐旧设备 storage 中缺失的动作,需沿既有资源安装流程处理。

系统 0.2.6 · ESP32 v0.5.6 真实下载进度

Choose a tag to compare

@Mr-KID-github Mr-KID-github released this 12 Oct 09:59
646a977

WatcheRobot 系统 0.2.6 / ESP32 v0.5.6

ESP32 v0.5.6,STM32 0.1.4 / 4219f4606346。下载页显示真实字节百分比、静态进度条与容量,最多每 250 ms 更新一次;停止传输时不重绘。下载、校验、安装、重启验证独立显示。

支持已安装可信 OTA 基础固件的 PTL 双 MCU 机器人。联网后在主页空闲时自动检查,连接电源后由屏幕二次确认升级;STM32 已匹配目标时验证后跳过重复擦写。首次迁移要求沿用 v0.5.0,旧固件及附件保持不变。

完整烧录包、Himax 包及源码说明。应用、SDK 等其他组件见历史综合下载。本 Release 使用独立附件集合,避免旧设备 64 KB 元数据限制。

签名清单和两个 raw OTA 镜像随附;手动烧录请使用源码 Release 的 ZIP 包。Host 6/6、真实 LVGL 2/2、正常构建与实机暂存校验通过。真实安装验收结果见后续验收附件。GitHub CI 因计费限制未执行;海外网络、真实断电、多机压力及密钥离线备份待量产验收。

实际公开 OTA 安装、重启双 MCU 验证及再次 CURRENT 已通过;详见 ESP32-v0.5.6-VALIDATION.md。

watche-v0.1.1

Choose a tag to compare

@orulink-wugui orulink-wugui released this 07 Sep 08:32

WatcheRobot v0.1.1

This is the stable WatcheRobot bundle prepared for public hands-on testing.

Included Versions

Component Version Release Asset
ESP32-S3 + Himax PTL firmware v0.4.1 WatcheRobot-S3-v0.4.1-PTL-paired.zip
Python SDK v0.1.8 watcherobot-0.1.8-py3-none-any.whl
SD card resources v0.0.8 watche-sd-resources-v0.0.8.tar
STM32 firmware v0.1.2 WatcheRobot-STM32-v0.1.2.zip
Windows desktop app v0.2.16 Watcher.Desktop_0.2.16_x64-setup.exe
macOS desktop app v0.2.16 Watcher.Desktop_0.2.16_aarch64.dmg
Android app v0.3.13 watcher-android-0.3.13.apk
iOS app v0.3.12 (2) Install with TestFlight

Recommended Setup Order

  1. Download the required assets and verify them with SHA256SUMS.txt.
  2. Assemble the robot, keep it powered off, and check all wiring.
  3. Flash the STM32 firmware on the feedback-servo control board inside the robot body with ST-LINK/SWD.
  4. Extract the PTL-paired ZIP, read skills/watche-ptl-release-flash/SKILL.md, and run the package verify command.
  5. Connect the Watcher head by USB and use the paired package to flash Himax first and ESP32-S3 second.
  6. Remove the Watcher head's SD card and connect it to the computer with a card reader. Format it as FAT32, extract the SD resource archive to the card root, safely eject it, and insert it while the robot is powered off. Do not write the SD card through the Watcher USB or serial ports.
  7. Power on the robot and complete the repository's first-start validation checklist.
  8. Install the desktop or mobile app for your platform.
  9. For Python development, install the SDK wheel with python -m pip install watcherobot-0.1.8-py3-none-any.whl.

Platform Notes

  • The Windows desktop installer targets x64 systems.
  • The macOS desktop installer targets Apple Silicon.
  • The Python SDK supports Python 3.10, 3.11, and 3.12.
  • PTL paired flashing requires Python 3.10+, the CH342 serial driver, and both the ESP32 control port and Himax vision port. It does not require ESP-IDF, an ARM compiler, Node, or Yarn.
  • The paired ZIP contains the ESP32-S3 and Himax binaries, flashing tools, and Skill. Its recovery flow can flash a blank or unresponsive Himax application through ROM/XMODEM without waiting for an old AT version response.
  • The iOS app is distributed through TestFlight and is not attached as a release asset.
  • Local-network SDK control uses a temporary pairing code and is intended for trusted networks.

Validation

The paired package passed package hash verification and an actual Windows hardware flash through a CH342 USB pair. Himax completed ROM/XMODEM transfer and produced PTL video-bridge telemetry after reboot. ESP32-S3 completed write verification, booted the included application, and reached the interactive launcher. STM32 was not written during this acceptance run; its archive, binary, OpenOCD configuration, and documented command were checked without accessing a target. SD-card writing was not tested; use a card reader and follow the repository guide.

If you encounter a problem during public testing, open an Issue with the device model, operating system, component versions, reproduction steps, and logs that are safe to share.