Trace the circuit into Linux and the product you want to build.
Equidna
Hardware and firmware
Ask Equidna how to connect an LED to your Raspberry Pi 5 I/O board and wire the software into Dataplicity.
Example engineering task. Bring the board drawing and component specifications; verify the wiring and result on your hardware.
Explore hardware and firmware help →Supply the board, revision and schematic. Separate established mappings from questions that need measurement.
Illustrative engineering path · validate against the supplied board
Review the interface, driver, permissions and application requirements against that evidence.
Container mappings and runtime preparation are separate choices
Test a fresh measurement, fault, restart and recovery, then compare the real behaviour with the reported product state.
Reference product view · integration required
Equidna assists with reasoning and test design. Your team retains hardware validation, safety and engineering approval.
See the full workflow and requirements →Illustrative engineering example: a level-monitor manufacturer needs a sensor fault to be distinguishable from stale data or loss of connectivity.
Supply the manufacturer, model, revision, processor/module, OS image and relevant schematic or netlist. Ask the specialist to cite the drawing and flag missing details. Similar carriers can have different power paths and pinouts.
Follow the connector pin, intervening components, voltage and processor mapping into the Linux interface. Keep physical header numbering, GPIO identifiers and Linux line names distinct. Review drivers, device-tree requirements, pull-ups and level shifting against the actual drawing.
Set architecture, libraries, verified device/interface, permissions, persistence, logging and restart behaviour. If using a container, identify necessary mappings and privileges; broad privileges are not a substitute for understanding the hardware.
Publish selected readings, quality and fault state; define validated settings/actions and outcomes. Test a real measurement, restart, outage and recovery, recording both physical behaviour and what the customer application reported.
Bring source material and the intended customer behaviour, rather than asking for a guessed generic board configuration.
“Trace SENSOR_IRQ from this connector through the drawing to the Linux interface. Cite the sheet or netlist, separate known mappings from uncertainty, and propose the measurements and integration tests we need.” This is illustrative text, not a captured assistant transcript.
Ask about cabling, grounding, filtering and interface choices for your environment. Check advice against authoritative component/board sources and your own validation process. Use your schematic and PCB tools to make changes.
Keep teammates involved in requirements and tradeoffs; use the appropriate conversation for each task.
Discuss the verified interface with Nutria when designing the customer workflow and Pingüino when investigating running equipment. A missing reading can be a sensor, application, stale-data or connection problem; model the difference.
Work together with a specialistA private specialist conversation and an invited room assistant have different access. Shared-room help is read-only under the sponsor’s authority and granted history; linking a board, canvas or device does not automatically grant full object access.
Conversation scope and permissionsBegin before you have a device or a deployed fleet.
Equidna is offered to the same web-app audience as Pingüino on Standard, Business+ and Enterprise within configured access. Supply exact external evidence and product requirements. Usage allowances still apply.
Plans and specialist accessYour team approves the design, verifies wiring on the exact hardware, runs bench tests and qualifies the container or RAUC runtime. Keep safety logic and final engineering approval in your own process.
Start with the exact source evidence and the result you need to test.
