Phasor Connected-systems
engineering
Open logbook Power Electronics Connectivity Automation hola@phasor.cl

Archive pillar

Electronics & Firmware

This pillar classifies what we publish about hardware, embedded systems, firmware, interfaces and their associated tests. It describes an area of the archive, not a product or a contracted service.

What this pillar classifies

  • Hardware design decisions and their technical justification.
  • Firmware and embedded systems: structure, artefact version and execution conditions.
  • Interfaces between hardware and software, with their assumptions stated.
  • Bench tests: setup, instrument, procedure and calibration status when it is documented.

State of the archive in this pillar

There is no published technical piece in this pillar yet. The page exists to fix the scope and the evidence standard, not to anticipate content: once a piece can support its mandatory fields, it will be published here.

A piece enters this pillar when it can identify the artefact and its version, the procedure, the test conditions, the limits of interpretation, the sources and a publishable technical owner. While any of those fields cannot be supported, the piece stays an internal record.

What this pillar does not claim

Without specific evidence, conditions and publishable sources, this pillar does not claim a finished product, certification, broad compatibility, field robustness, security, availability or service life.

Share the technical context to define the question and the evidence needed.

hola@phasor.cl ↗
Logbook

Articles

We write about what we build: design decisions, real problems and technical lessons.

Four pillars

What we do

We turn connected-systems problems into prototypes, products and verifiable technical decisions.

01

Custom development

We design and implement systems with the hardware, firmware and software the problem requires.

02

Consulting

We join existing teams to measure, diagnose and make evidence-based decisions.

03

Applied R&D

We explore alternatives, build tests and document what we learn to reduce uncertainty.

Contact

Let's talk about your system.

Tell us what you are trying to measure, communicate or automate. We answer directly and discuss the problem.

A direct reply from the people who build · Español / English