Zikro
Get started
Release history

What’s new in Zikro

Every change that reached the app, newest first — new checks, new fixes, and the parts of the library that grew.

Current version1.2.0
Released2 September 2026
Releases3
In this release1change
minor
v1.2.0Latest release
Added
  • 2.54 mm pin headers in every size from 2 to 20 pins, male and female, so boards whose header is not 4 or 15 pins can be described at all. A device with a connector the library does not carry has its port left out rather than approximated, so the missing sizes were silently costing whole ports on common breakout boards.
minor
v1.1.0
Added
  • Public changelog at /changelog, listing every release and what shipped in it, linked from the footer of every public page.
Fixed
  • The public compatibility page no longer shows "Zikro" twice in its browser tab and search result.
major
v1.0.0
Added
  • Guided connect-A-to-B builder: pick a port and conductor on each device and draw the wire, on a phone as well as a desktop.
  • Live findings on every connection, ranked Fatal, Broken, Degraded or Note, each explaining the mechanism in plain language rather than quoting a spec.
  • Findings carry the confidence of the profiles they came from, so a guessed or marketplace-sourced spec can never issue an unflagged Fatal.
  • Public compatibility page for any two devices in the library, shareable without an account.
  • Admin rules browser listing every seeded validation rule with its severity and explanation.
  • Computed passive fixes for the findings that have one — attenuator pad, speaker-to-line pad, stereo summing network, DC blocking capacitor, level shifter and I²C pull-ups — with real part values snapped to the E24 and E6 preferred series and the deviation reported.
  • Adjust a fix's assumptions (target attenuation, corner frequency, bus speed, rail voltage) and the schematic, the component values and the build steps recalculate as you drag.
  • Accept fixes into a project's build plan, then export it as a wiring diagram, a bill of materials with quantities rolled up, and numbered build steps. All three print together on one page.
  • An accepted fix is flagged stale when the finding it answers stops applying, so a fix is never silently dropped from a build plan you have already bought parts for.
  • Draft a device profile from a datasheet: upload the PDF or paste the listing you bought from, and the five-step authoring form comes back filled in instead of blank.
  • Every drafted number is shown against the phrase from the source it was read from, and anything the source did not state comes back blank and marked rather than guessed.
  • The drafted form is reviewed in the same stepper, with the same validation, as a profile written by hand. Nothing becomes a profile until you have checked it and pressed save.
  • A drafted profile is capped below high confidence, so a Fatal verdict built on a machine-read datasheet always reaches you carrying where it came from.
  • Drafts are private to their owner, admins included, and deleting one deletes the file it was made from. A draft that fails to read says why, in plain language, and can be retried or deleted.
  • Import a circuit you already drew in Wokwi: paste or upload its diagram.json and get a Zikro project with the boards placed, the wires drawn and the verdicts already computed.
  • The import shows what it would create before it creates anything. A part Zikro has never heard of is listed with a picker rather than guessed at, and every wire that cannot come across is named with the reason instead of quietly going missing.
  • Export an MCU project back to a Wokwi diagram, with each board where you had it. A project holding something Wokwi cannot draw is told so by name, rather than handed a diagram with the missing piece silently left out.
  • Share a profile you wrote with everyone else: submit it, and once a moderator has read it, it appears in a community library alongside your name.
  • A community profile can never claim high confidence, so a verdict built on somebody else's transcription always reaches you carrying where it came from.
  • Say whether a listed profile matched the unit you actually have. The tally sits beside the author's own confidence and is never folded into it — a crowd count cannot quiet a Fatal.
  • Fork any profile you can read, correct it against your own hardware, and offer the correction back. An accepted correction updates the profile in place, so its address and its history survive instead of the library filling up with near-identical copies.
  • Moderators get a queue with the whole profile in it, a correction shown beside what it would replace, and no way to reject something without saying why.
  • Power budget for every project: Zikro works out the supply rails in your wiring, adds up what each device takes against what the rail can deliver, and shows the margin on a Power tab beside Build and Export.
  • A rail asked for more than its supply can give raises a Broken finding that reaches the builder's findings panel and the project's dashboard badge like any other verdict, rather than sitting only on its own page.
  • A device that does not state what it draws is counted as unknown, never as nothing. The rail total is marked a lower bound and the page links straight to where the missing figure can be supplied.
  • Current draw and current supply can be recorded per conductor when authoring a profile, are read from a datasheet by the drafting step, and are shown wherever the absolute-maximum ratings already appear.