Gallery

The shots that make it real.

A curated evidence reel for the physical product, release pipeline, validation videos, and the hardware path behind the final Velo baseline.

A physical product, not a mockup

Exhibit: Installed-device photos anchor the site in a real doorway scenario.
Evidence: Whiteboard mounting, hook objects, LCD surface, and compact enclosure are visible in the first screen.
Why it matters: Shows this is a physical embedded product, not a web mockup.

A UI connected to the room

Exhibit: Screen, Wi-Fi, weather, reminder, and hook context photos show the product workflow.
Evidence: The interface is presented as a working embedded surface instead of a static render.
Why it matters: Connects the UI to the physical reminder behavior.

A repeatable release pipeline

Exhibit: Release tool generate/upload screenshots, Node-RED flow evidence, and WinSCP VM proof are grouped here as the delivery trail.
Evidence: The same workflow builds slot A, builds slot B, signs manifests, routes cloud responses, uploads artifacts, and verifies endpoints.
Why it matters: Shows the delivery process is repeatable by a reviewer.

Failure behavior under camera

Exhibit: Fallback, bad package, network timeout, and V1.0.26 success videos are grouped here as the validation reel.
Evidence: The evidence includes success, rejection, timeout handling, and confirmed-slot recovery.
Why it matters: Shows Velo was tested against failure, not only success.

Final narrated demo

The whole project, shown end to end.

This is the complete presentation recording for reviewers who want the full Velo story in one place: product behavior, cloud flow, signed OTA, fallback, and validation.

Video

Final presentation

Complete narrated Velo final demo

Full project walkthrough with voice narration

The complete recording introduces the team, demonstrates the installed device, walks through cloud behavior and hook LEDs, and explains the signed A/B OTA, fallback, bad-release rejection, and final validation story.

Product workflow

The device behaves in the room.

This reel keeps the product proof separate from the OTA lab: screen, installation context, and physical hook behavior appear as one finished embedded system.

Video

Product reel

Final Velo workflow under camera

Touch UI, room context, and hook feedback in one device

The final product video shows Velo as a working embedded surface: installed in the room, driven by the real LCD UI, and tied back to the physical hook reminder behavior.

Video

Physical feedback

Hook LEDs respond to real reminder state

Selected hooks light while inactive hooks stay dark

The hook LEDs make the UI visible in the room, proving the final product behavior survived the OTA and fallback work.

Update proof reels

Five recordings that make the OTA story tangible.

The update story is shown under real device conditions: success, fallback, signed-policy rejection, bad-package rejection, and timeout handling.

Video

Success reel

V1.0.26 signed OTA survives hardware reset

Installed, rebooted, and stayed on V1.0.26

Full device video showing the real OTA path, including hardware RST after the update stayed confirmed.

Video

Recovery reel

V1.0.27 fallback returns to confirmed V1.0.26

Trial image fails safely

A fallback demonstration package boots as a trial, then returns to the confirmed baseline instead of bricking.

Video

Security reel

Bad-signature release is refused

Unsafe release metadata stops before trust

The negative manifest path shows that a release must satisfy the signed policy boundary before it can be treated as a normal upgrade.

Video

Negative reel

V1.0.27 bad package fails install

Check can pass; install still refuses bad bytes

A deliberately bad package proves the payload gate catches unsafe firmware before trial boot.

Video

Fault reel

Network timeout stops the upgrade path

0x7 timeout handled without unsafe progress

A real unstable-network capture shows the updater stops instead of forcing an uncertain install.

Media board

Seven stills that widen the engineering story.

Velo update screen showing V1.0.26 installing from V1.0.25.

Install state

OTA install reaches the device screen

Velo update screen showing a V1.0.26 update available from V1.0.25.

Update UI

OTA screen reports V1.0.26 availability

Velo Wi-Fi screen showing connected network state.

Network UI

Wi-Fi setup reaches the connected state

Velo custom PCB photographed as a complete board.

Hardware

The final PCB before it disappears into the enclosure

Velo screen showing an early V1.0.0 success state.

Milestone

V1.0.0 success screen from the early release path

Assembly

Assembly view from the front side

Mechanical proof

Assembly view from the back side

Release-tool evidence

The build, upload, and cloud trail is visible.

The desktop tool and Node-RED backend turn the project into a repeatable release system instead of a hand-built firmware demo.

Image

Tooling

A/B release generated by the Velo tool

Slot A and slot B packages generated

The release tool builds both inactive-slot artifacts and writes signed manifests for the cloud endpoint.

Image

Upload

Release uploaded and verified

VM upload complete

The upload log verifies artifact URLs, latest manifests, and the fw/check responses for both slot directions.

Image

Cloud proof

VM received both slot artifacts

A/B artifacts visible on server

WinSCP shows slot A and slot B RPS files plus the latest manifests in the HTTP directory.

Image

Cloud flow

Node-RED routes the live product backend

Weather, reminder, OTA, and rollback endpoints are wired

The Node-RED flow shows the backend path behind live location/time/weather responses, OTA manifest selection, and firmware report handling.

Image

Device UI

Device sees the cloud release

Local check finds V1.0.26

The embedded update UI confirms the cloud manifest is visible from the actual device path.