Your PCB bring-up and debugging assistant. Import your netlist and BOM, connect your oscilloscope, and get guidance on what to measure next — with each capture bringing you closer to the faulty net or component.
The 1.2 V core rail droops 180 mV whenever the Ethernet PHY
wakes — and +3V3_PHY failed outright. Both rails share
U7. Probe U7.SW next: I expect missing
switching activity. Confidence this is a dead regulator or its
enable line: 82%.
A recreation of the YProbe main window — board tree, judged capture, comparison verdicts, and the assistant's next move.
Use the instrument already on your bench
Have another SCPI oscilloscope? Upload its manufacturer's programming-guide PDF in YProbe to configure it from the documented commands and check it against your instrument. You can also import waveform files or evaluate the workflow in the simulator. See programming-guide setup or check tested models.
YProbe connects board context, bench measurements and the decisions made between them. The result is a debugging record you can inspect, repeat and hand to another engineer.
Import the netlist and a CSV or Excel BOM. YProbe builds a graph of nets, components, rails, drivers and loads, then checks every suggested net and component against the design before it reaches the session.
YProbe configures supported scopes, reads their settings back, screens unstable probe contact and judges each parameter against the expected signal before it becomes diagnostic evidence.
Measurements, hypotheses and rework stay attached to the board. Compare sessions, identify what changed the outcome, and send a signed probe task to a technician without sending the netlist or BOM.
Every step answers one question and makes the next measurement more valuable.
Load the netlist and BOM. YProbe maps rails, buses, components, drivers and loads into a graph it can reason over.
Describe the symptom in plain language: a dead rail, failed USB enumeration, missing clock or fault that appears only after warm-up.
YProbe ranks the next probe point, prepares the scope or DMM, and judges the result against the expected signal and board topology.
Hypotheses narrow after every accepted measurement until a suspect net or component is supported by a traceable chain of evidence.
Bring-up, intermittent failures, repair and remote triage share one problem: the evidence lives in too many places. YProbe keeps it connected.
Verify rails, startup order, clocks and buses in a repeatable sequence instead of rebuilding a checklist for every revision.
PCB bring-up workflow →Monitor droops, dropouts, glitches and recoveries over time, then carry the event into the diagnostic record.
Intermittent-fault workflow →Record removed parts, replacements, lifted pins and fly-wires, then see which nets were fixed, regressed or never rechecked.
See short hunting and rework evidence →Package signed probe tasks and expected signals while keeping the netlist, BOM and diagnostic reasoning on the designer's side.
Remote PCB debugging →Single captures can't catch a rail that misbehaves once every few minutes. Monitor mode streams captures for as long as you need and logs a wall-clock-stamped event only when something actually crosses a threshold.
Swapped a resistor, pulled a cap, lifted a pin, fly-wired two pads — log it once and it stays on the record. Every PASS/FAIL is persisted per board too, so the tool can tell you what your rework actually did instead of leaving that to your memory and a spreadsheet.
| +3V3_PHY | FAIL → PASS | FIXED |
| +1V2_CORE | FAIL → PASS | FIXED |
| USB_DP | PASS → FAIL | REGRESSED |
| I2C1_SDA | FAIL → FAIL | STILL FAILING |
| SPI2_MISO | — → FAIL | NEW FAILURE |
| nRST_MCU | FAIL → not re-measured | CHECK |
C47 removed → +3V3_PHY FAIL → PASS · high confidence · the hypothesis that blamed C47 is now confirmed
The AI can propose a hypothesis. It cannot bypass the netlist, accept a rejected capture or silently promote unvalidated hardware into evidence.
Every capture is classified as contacted, floating, intermittent, clipped or unknown, and a cross-capture tracker requires consecutive agreement before it locks. If the verdict is floating or intermittent at the blocking confidence threshold (0.65 at full sensitivity), the capture is blocked from producing a PASS/FAIL, from entering the session record, and from reaching the AI as board evidence.
Every AI-returned net and component name is resolved against the imported design before it can reach the session or screen. Unknown names are rejected, so a fluent answer cannot create a probe point that is absent from the board.
Each instrument connection is labelled simulated, bench-validated, self-tested, manually selected, unvalidated or guessed. A guessed dialect blocks automated capture until a checked programming-guide setup succeeds, the user selects a profile deliberately, or the pairing passes the bench self-test.
Every plan includes the PCB bring-up and debugging workflow. The plan ladder changes board volume, collaboration, telemetry and deployment — not the quality of the diagnosis. Prices shown are provisional US dollars per user, billed monthly unless stated otherwise.
Free trial
Two board designs, hosted diagnosis, the full simulator and a renewable seven-day evaluation key.
Request early beta accessFrom $50 / user / mo
Hosted diagnosis, ten or more board designs, with remote technician workflows available when needed.
Request early beta accessFrom $200 / user / mo
Multiboard systems and no product telemetry, with private endpoints, offline operation and site licensing for Enterprise.
Talk to usPricing is provisional while YProbe is in early access; annual figures reflect the planned ~2-months-free discount.
Evaluate at your bench's pace — hardware projects don't finish in a week.
7 days · renewable
Solo bring-up and repair, one board at a time.
billed monthly
Bring your contract manufacturer into the loop.
billed monthly
For engineers debugging boards every week.
billed monthly
High-volume benches and busy labs.
billed monthly
Priced on board volume, not seats.
annual · committed boards / month
On Light+ and above, remote debugging includes free technician clients. The CM's technician installs YProbe at no charge — only the designer needs a subscription. The technician sees probe points and expected signals, and never receives your netlist, BOM, or the AI's reasoning. Results come back signed, and verdicts are recomputed on your side.
| Feature | Trial | Light | Light+ | Pro | Pro+ | Enterprise |
|---|---|---|---|---|---|---|
| Price | Free · 7 days | $50/mo | $100/mo | $200/mo | $400/mo | Contact us |
| Board designs / month | 2 | 10 | 10 | 50 | Unlimited | Unlimited · site license |
| Multiboard systems | — | — | — | ✓ | ✓ | ✓ |
| Remote debugging (designer ⇄ factory) | — | — | ✓ | ✓ | ✓ | ✓ |
| AI diagnosis | Hosted | Hosted | Hosted | Hosted | Hosted | Your LLM / private endpoint / fully offline |
| Data sharing | Anonymized session summaries (required) | Category-level fault telemetry (can be disabled) | Category-level fault telemetry (can be disabled) | No product telemetry | No product telemetry | No product telemetry · contractual (DPA) |
| Support | Community | Standard | Standard | Standard | Priority | Priority + dedicated |
Can't find your answer? Write to support@yprobe.com.
YProbe is in early access. The desktop app is built and running on real hardware; the hosted account and billing backend is what gates the public release. Request early beta access and describe your oscilloscope. We review each request before issuing a single-use invitation.
One unique netlist. Debugging the same design any number of times in a month uses one slot — ten physical units of the same board are still one design. Your monthly count resets each billing cycle.
Trial: anonymized session summaries — fault categories, measurement verdicts and fix categories, with net names anonymized. Your netlist and BOM are never uploaded as part of sharing. Light / Light+: category-level fault telemetry only (e.g. "I²C · no ACK · missing pull-up" on a "clock generator IC" — no part numbers, no net names, no design data), and you can turn it off in Settings. Pro and Pro+ send no product telemetry, but their hosted AI requests still process the structured board context needed for the diagnosis. Enterprise can use a private endpoint or run fully offline. Read the data-handling summary.
Yes, on hosted tiers — and we'd rather say so plainly than bury it. The structured board context needed for a diagnosis is processed by our server per request to run the AI analysis. Your design files themselves stay on your machine. Enterprise customers can route AI to their own private endpoint or run fully offline, so nothing leaves their network. See the exact data boundaries by plan and deployment.
You compose a signed task package; the technician runs a free YProbe client that shows probe points and expected signals — never your netlist, BOM, or the AI's reasoning. Results come back signed, and verdicts are recomputed on your side. Tasks can be conditional ("if task 3 fails, probe this next"), so the queue keeps the technician moving across time zones while you sleep.
No. All plans include hosted AI — no API keys, no per-token bills, nothing to configure. Enterprise can optionally bring their own LLM endpoint, including a local model for air-gapped labs.
A VISA connection is necessary for live control, but it is not sufficient by itself: automated capture also needs a compatible SCPI control and waveform-readout profile. Rigol and selected Siglent generations are bench-validated; Keysight, Tektronix and other Siglent profiles are available but remain labelled unvalidated until proven on hardware. Unknown instruments are blocked from automated capture unless a checked programming-guide setup succeeds, you deliberately select a profile, or the pairing passes the bench self-test. You can upload your SCPI oscilloscope's programming-guide PDF through Hardware → Configure from programming guide…. Waveform import and the simulator remain available. See the compatibility and validation matrix.
Monthly plans: yes, effective at the end of the billing period. Annual plans (including Enterprise) renew yearly.
Tell us who you are and which oscilloscope you use. We review every request manually; approved participants receive a single-use invitation and the desktop build so they can evaluate a real board or the simulator.