Contact person: SCOPE CHANGE - RESUBMIT INTEREST - Firmware Development for Premium Motorsport Device

Phone:Show

Email:Show

Location: Adelaide, Australia

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Scope Update — Re-Submit Interest (V1 ⇒ In-Car Prototype)

We’ve refined V1 to reach in-car prototype testing. Work starts now on the bench and continues onto our prototype PCB when it arrives. We may engage multiple freelancers at this stage to identify our lead firmware engineer. Price will influence the decision alongside capability and fit.

About us

You’ll join PCB designers, industrial designers, graphic designers, and mechatronics engineers. We’re adding firmware and software teammates. Milestone engagement; detailed acceptance criteria provided after NDA.

V1 (public) scope — just enough to evaluate

Fast boot to gauges (splash fast; live values shortly after power)

LVGL UI: one main layout + one alternate; day/night; auto-brightness

Classic CAN ingest: DBC-mapped; bench replay proven; brief real-bus check later

Alarms: on-screen warnings for key thresholds

Data logging: low-rate CSV to removable storage with safe shutdown

Settings: small JSON config (units/bitrate/theme/thresholds)

Factory/Test mode: screen test, loopback/demo values

Updates & assets: load configs/assets over USB; standard STM32 flashing flow

Clean handover: minimal build/run notes so a teammate can replicate

Security (capability): you understand STM32 protection basics (e.g., signed updates, RDP1, disabling SWD/JTAG) and can incorporate baseline protections when required.

(Full technical materials shared after NDA.)

Milestones to quote

M0 — Bench Trial (starts now)
Clean boot to first pixels; basic LVGL screen updating from a short DBC-mapped CAN replay; CSV logging that survives a power-yank. Short video + brief notes confirming repeatability and handover steps.
Gate: qualifies you for M1/M2.

M1 — Bench Feature Pack
Complete core device behavior (UI/themes/alarms/settings/factory mode/asset ingest) and be ready to add baseline protections when requested.

M2 — V1 In-Car Prototype (Full Gauge)
Install on our prototype PCB. Full gauge display and base functions working in-car; brief real-bus sanity pass confirms DBC mapping & live gauges. Short video + checklist + logs from a short drive.
Outcome: V1 ready for iterative track testing.

How we work

Short calls, crisp tickets, stage gates, evidence-based acceptance. Clean, readable, human-written code with concise docs.

Strict No-AI-Coding

Human-written code only. One-line attestation required.

Selection approach (transparent)

We reserve the right to hire more than one person at this stage to identify our lead firmware engineer. Price will have an impact alongside capability, delivery clarity, and fit.

Send (brief)

Your milestone plan and availability window

Two examples of bringing up a new embedded device

How you avoid “black screen” on first power

One-line attestation: human-written code

Any day-one risks you’d check

If you want to ship V1 into the car and grow with a capable, design-led team, confirm your interest and let’s talk." (client-provided description)