Explore the marketplace. Items labelled Example are fictional. Video reviewed means a human has reviewed the introduction, not the engineering qualifications. Sign in to contact a client about a published project. Project payments are not open.YOUR ENGINEER
Open for proposals

Write firmware for a two-actuator test bench

Implement a repeatable bench sequence for two low-voltage actuators on an existing development board.

Kestrelpin Mechatronics

Taipei, Taiwan Remote

Posted

This is an example brief. Its company, dates, budget, assignment and progress illustrate a project; they do not represent available or commissioned work. Proposals cannot be submitted.

The brief

The work and the intended result

We have a bench harness, an agreed development board and two low-voltage actuators. The firmware must execute four test sequences, read two position inputs and stream timestamped results over a serial connection. Include configurable timing values and a clear stopped state when a test condition is not met. This is supervised bench-test software; production machine control, safety functions, a custom PCB and a desktop application are excluded. Remote access to the bench will be scheduled for two test sessions.

Duration
2 weeks
Commitment
Approx. 40 hours total
Location
Remote

What you’ll deliver

  • A documented state machine and firmware for four agreed sequences
  • Serial configuration and results messages with a compact protocol description
  • Eight bench tests covering normal operation and defined fault inputs
  • Source code, build instructions and a recorded handover demonstration

Expertise needed

  • Embedded C or C++ experience with digital and analogue I/O
  • Comfortable separating test sequencing from independently provided protective measures
  • Ability to diagnose timing behaviour using supplied serial logs and bench observations
  • Embedded systems
  • C++
  • Firmware testing
  • Automation

A running start

What’s already in place

  • Development-board details, pin assignments and actuator datasheets
  • The four sequence definitions and expected timing ranges
  • A technician for two scheduled remote bench-test sessions

Project milestones

To shape together
  1. 01

    Agree the state machine

    Review inputs, stop conditions and message formats before implementing the sequences.

  2. 02

    Implement and exercise the firmware

    Build the four sequences and run the eight agreed cases with the bench technician.

  3. 03

    Deliver a repeatable build

    Rebuild from the handover instructions and confirm that each test result is traceable to its configuration.

To agree before starting

A shared definition of done

Confirm the deliverables, review checks and response window together so everyone knows what a successful handover looks like.

Suggested acceptance criteria

  • Every agreed deliverable is included in the handover, in the agreed file formats.
  • Assumptions, limitations and open questions are documented alongside the work.
  • The project owner reviews the work against the brief and returns one consolidated feedback list before approval.

When the scope changes

Record the requested change, its reason and its effect on deliverables, budget and timing. Both parties agree the revised scope in writing before the additional work begins.