Everypin

𝗣𝘄𝗿𝗕𝗹𝗼𝗰𝗸 𝟯𝟮𝟯 𝗳𝗶𝗿𝗺𝘄𝗮𝗿𝗲 𝗶𝘀 𝗻𝗼𝘄 𝗼𝗽𝗲𝗻 𝘀𝗼𝘂𝗿𝗰𝗲.

The actual firmware running on the device is now available on GitHub — from SCPI and USB to hardware control.

𝐓𝐚𝐤𝐞 𝐚 𝐥𝐨𝐨𝐤 𝐢𝐧𝐬𝐢𝐝𝐞. 𝐁𝐮𝐢𝐥𝐝 𝐢𝐭. 𝐄𝐱𝐩𝐥𝐨𝐫𝐞 𝐢𝐭. 𝐈𝐦𝐩𝐫𝐨𝐯𝐞 𝐢𝐭. 💜

𝗥𝗲𝗮𝗱 𝘁𝗵𝗲 𝗳𝘂𝗹𝗹 𝘂𝗽𝗱𝗮𝘁𝗲 𝗼𝗻 𝗖𝗿𝗼𝘄𝗱 𝗦𝘂𝗽𝗽𝗹𝘆 → https://www.crowdsupply.com/everypin/pwrblock-323/updates/the-code-behind-pwrblock-323-is-now-open?utm_source=telegram&utm_medium=social&utm_campaign=Open+source&utm_content=Open+source

#PwrBlock323 #EVERYPIN #OpenSource #OpenSourceHardware #OpenSourceFirmware #EmbeddedSystems #FirmwareDevelopment #ElectronicsEngineering #HardwareEngineering #TestAutomation #STM32 #GitHub

𝐍𝐨𝐭 𝐞𝐯𝐞𝐫𝐲 𝐞𝐥𝐞𝐜𝐭𝐫𝐨𝐧𝐢𝐜𝐬 𝐭𝐚𝐬𝐤 𝐧𝐞𝐞𝐝𝐬 𝐚 𝐟𝐮𝐥𝐥-𝐬𝐢𝐳𝐞 𝐛𝐞𝐧𝐜𝐡 𝐩𝐨𝐰𝐞𝐫 𝐬𝐮𝐩𝐩𝐥𝐲 ⚡

Sometimes you’re bringing up a board, debugging a prototype, or working with the same DUT again and again. You know what it needs — you just want a compact and convenient way to power it.

That’s one of the two use cases PwrBlock 323 was designed for from the start: everyday bench work and integration into automated test systems.

The idea is simple — use the same programmable power supply while developing at your desk, and later integrate it into your test or production setup when the project grows.

PwrBlock 323 is now on Crowd Supply https://www.crowdsupply.com/everypin/pwrblock-323/updates/sometimes-you-just-need-power-pwrblock-323-on-the-bench

#PwrBlock323 #Everypin #ElectronicsEngineering #HardwareEngineering #BenchPowerSupply #HardwareTesting #TestAutomation #EmbeddedSystems #Prototyping #ElectronicsLab #TestEngineering #HardwareDevelopment

CM4 vs CM5 — a curious DFT difference

We mapped the test points on both Raspberry Pi Compute Modules and found an interesting difference.

CM5 gives you direct access to power, USB, boot control, UART, and Ethernet — enough to build a pogo-pin fixture for flashing and production testing.

CM4 has plenty of test points too, but we couldn’t find USB, 5 V, or boot control among them.

So what were the CM4 test points actually designed for? Factory testing? Direct eMMC access? Something else?

Check out interactive testpoint maps for these SoMs:
CM5 → https://everypinio.github.io/cm5-flash-jig/test-points/cm5/
CM4 → https://everypinio.github.io/cm5-flash-jig/test-points/cm4/

Same idea. Two generations. Very different approach to DFT.

If you need robust flashing solution for CM4 or CM5 check here (https://bit.ly/4zUaHcx)

#Everypin #RaspberryPi #CM4 #CM5 #DesignForTest #HardwareTesting #TestFixture #PogoPins

𝗕𝘂𝗶𝗹𝗱 𝘀𝗺𝗮𝗿𝘁𝗲𝗿 𝘁𝗲𝘀𝘁 𝗳𝗶𝘅𝘁𝘂𝗿𝗲𝘀 𝘄𝗶𝘁𝗵 𝗣𝘄𝗿𝗕𝗹𝗼𝗰𝗸 𝟯𝟮𝟯

Why add another bench power supply, extra cables, and more setup steps?

With PwrBlock 323 mounted directly on the fixture backplane, programmable DUT power and control become part of the fixture itself. Add a Raspberry Pi to the same backplane, and programming, I²C, GPIO, and power are all integrated into one system.

Less wiring. Faster integration. More repeatable fixtures.

PwrBlock 323 turns power control into a building block for automated testing.

🔗 PwrBlock 323:
https://everypin.io/hardblocks/pwrblock-323

See how we integrated it into a CM5 programming fixture:
https://www.crowdsupply.com/everypin/pwrblock-323/updates/how-we-integrated-pwrblock-323-into-a-cm5-programming-fixture

#Everypin #PwrBlock323 #HardwareTesting #TestFixture #CM5

Reliable connectivity for CM5 flashing

Flashing Raspberry Pi CM5 at scale puts serious wear on standard board-to-board connectors, leading to unreliable contact and failed flashing.

That’s why Eloprint developed a robust production fixture for repeatable CM5 connection, while Everypin provided the automation layer.

The system:
- checks CM5 power;
- automates flashing;
- verifies successful boot;
- records every result.

The workflow runs on HardPy, our open-source testing framework, and uploads production data to the cloud for traceability, remote monitoring, and analytics.

Read more about the CM5 Flash Jig (https://everypin.io/solutions/cm5-flash-jig)

#RaspberryPi #ComputeModule5 #CM5 #Manufacturing #ProductionTesting #TestAutomation #HardwareTesting #OpenSource #Traceability #HardPy #Everypin #Eloprint

🚀 𝗣𝘄𝗿𝗕𝗹𝗼𝗰𝗸 𝟯𝟮𝟯 𝗶𝘀 𝗹𝗶𝘃𝗲 𝗼𝗻 𝗖𝗿𝗼𝘄𝗱 𝗦𝘂𝗽𝗽𝗹𝘆!

We built PwrBlock 323 to bring programmable DUT power directly into automated test fixtures and HIL setups.

⚡ 1–32 V
⚡ Up to 3 A / 92 W
💻 SCPI + Python-friendly control
🔌 USB-C PD powered
🛠 Designed for automated testing

After months of prototyping and testing, we’re now raising funds to manufacture the first production batch.

Check out the campaign and support PwrBlock 323:

https://www.crowdsupply.com/everypin/pwrblock-323



And if you know someone building hardware test fixtures — please share it with them.

#everypin #pwrblock #hardblocks #crowdfunding #crowdsupply

HardPy 0.24.0 — what's new

Two new features are landing in the operator panel.

Reports storage menu
A new menu in the panel header lets you see at a glance where test reports are being stored and how to fix any configuration problems. It shows the status of StandCloud and the active local backend (CouchDB or JSON files), turns red when there is a blocking issue, and provides direct links to the CouchDB panel, the local JSON folder, or the documentation.

Test history
Previous test runs are now accessible directly in the operator panel — no need to open CouchDB or inspect JSON files manually. The history table shows the run name, start time, result, and serial number, with expandable rows for full details. A "Show more" button handles pagination.
Note: test_history is disabled by default. Each test run creates a new document in the database, so database growth needs to be considered before enabling it. To turn it on, set frontend.test_history: true in your config.

HardPy 0.23.0 is out ⚡️

What’s new:

• Test reports are now 30% shorter thanks to removing empty fields
• The CouchDB initialization process has been updated to avoid the noisy error logs caused by the previous setup
• A few minor fixes were also included

A small release, but a cleaner and smoother one.

HardPy 0.21 released

We’ve published a new HardPy release focused on the operator clarity for semi-automated test stands.

What’s new

• The ability to customize the text on buttons in dialog boxes. This works with both the Confirm button and the Pass/Fail buttons. Translations are ignored for custom buttons. (PR #253)


Why it matters

In semi-automated test stands, generic buttons like “Confirm / Pass / Fail” can be ambiguous.
Now you can make the UI say exactly what you need (“Fire”, “Smoke”, “Retry measurement”, etc.), which reduces operator confusion and helps keep the process consistent.
Full release details

Channel photo updated

HardPy 0.20.0 released

We’ve published a new HardPy release focused on improving reliability and making result storage more flexible.

What’s new

• Fixed an issue with saving test reports to CouchDB. In some cases reports were not persisted correctly; this is now resolved.
(PR #243, thanks @rici4kubicek)

• Added support for storing test results in JSON files as an alternative to CouchDB. This makes HardPy easier to use in offline setups, local development, or simple test stands where a database is not required.
(PR #239)

• Added documentation describing how to configure and use the new JSON storage backend.
(PR #244)

Why it matters

This release removes a reliability issue in CouchDB-based setups and gives you more freedom in how you store test results, especially for lightweight or offline test environments.

Full release details

We are pleased to announce the release of HardPy 0.16!
Below are the changes in this and the previous release, 0.15:

⭕️Multiple instances support: Run multiple HardPy instances with a single CouchDB database instead of requiring separate databases for each instance.
🟣Charts on operator panel: Display charts directly on the operator panel for real-time visualization.
🔴Enhanced database structure: The updated structure now supports:
- Sub-unit specifications for the Device Under Test (DUT)
- Storage of measurements and production process data
- Equipment information used during testing
🟡Console launch with arguments: Launch HardPy from the console with custom arguments that can be applied during testing.

For detailed documentation and examples, visit our documentation page.

👋 Hello, Hallo, Salut, Hola, 您好, こんにちは, Привет! 😎

HardPy 0.14 release is here!

This update brings multilingual support to the operator panel, now available in additional six languages:
- German (Deutsch)
- French (Français)
- Spanish (Español)
- Chinese (中文)
- Japanese (日本語)
- Russian (Русский)

You can easily configure the language in the hardpy.toml file.

New Feature: The operator panel now displays the total testing time, giving you better control over your workflow.

Minor bugs have also been fixed.

Need your support! 🙏

Team, we're growing HardPy on Reddit - just published a tutorial on electronics testing automation with real examples.

Would be awesome if you could:
- Drop an upvote
- Leave a comment
- Share your experience

Every vote helps promote the framework and attract new contributors!

🎯 WEBINAR ALERT: July 31st

Join our upcoming webinar where Era Wallet will share their HardPy implementation journey, challenges faced, and lessons learned.

Here’s a sneak peek of what we’ll cover:
Discover how the Era Wallet team reduced onboarding time, mitigated security risks, and eliminated the need for factory visits—all thanks to HardPy, our open-source automation framework.

About Era Wallet:
Era Wallet is an elegantly designed, ultra-thin, fully air-gapped hardware wallet, that allows users to manage up to 10 multi-chain wallets on a single device. It features advanced random generation, secure NFC-Card backups, and offline transaction decoding are just a few of its features. ERA Wallet supports Bitcoin, EVM chains, Tron and Solana with other chains planned. Strict security standards and requirements make quality control a serious challenge.

Challenges:
🟡 Security risks — Operators could see secret keys
🟡 Slow onboarding — New hires required 2 weeks of training
🟡 Costly downtime — Engineers had to travel just to diagnose failures
🟡 Fragile processes — Dozens of scattered CLI scripts

Solutions with HardPy:
✔️ Eliminated credential exposure — Full isolation of critical data
✔️ 2-day training — New hires become productive 85% faster
✔️ Debug from anywhere — Remote diagnostics saved thousands in travel costs
✔️ Unified control — All scripts centralized with versioning

The Results?
🚀 Faster releases | 🔒 Fewer security incidents | 💸 Lower operational costs

P.S. What’s the biggest workflow pain point your team faces? Let us know in the comments—we might cover it in the next post!

👉Check out HardPy on GitHub.

⚡️HardPy 0.12.1 Release⚡️

1. Test Dependencies: You can now configure tests to run based on the results of multiple other tests. This feature works for both individual test cases and entire test modules.

2. Dependency Error Handling: When dependencies are incorrectly specified or missing from the test plan, HardPy now automatically ignores them instead of failing.

3. Critical Test Marker: Added a critical marker that stops all subsequent test execution when a critical test or module fails.

4. Test Stand Numbering: Introduced the set_stand_number function to assign numbers to test stands.

5. Enhanced Documentation: Added comprehensive documentation for the report schema (runstore database in CouchDB).