Everypin
56 subscribers
15 photos
3 videos
24 links
Everypin will be tested
https://github.com/everypinio/
Download Telegram
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.
Please open Telegram to view this post
VIEW IN TELEGRAM
๐Ÿ”ฅ10
This media is not supported in your browser
VIEW IN TELEGRAM
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
๐Ÿ”ฅ8โค3โคโ€๐Ÿ”ฅ1
Channel photo updated
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
๐Ÿ”ฅ6โคโ€๐Ÿ”ฅ1
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.
โšก7โค2๐Ÿ”ฅ1
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.
๐Ÿ”ฅ6โค2
๐Ÿš€ ๐—ฃ๐˜„๐—ฟ๐—•๐—น๐—ผ๐—ฐ๐—ธ ๐Ÿฏ๐Ÿฎ๐Ÿฏ ๐—ถ๐˜€ ๐—น๐—ถ๐˜ƒ๐—ฒ ๐—ผ๐—ป ๐—–๐—ฟ๐—ผ๐˜„๐—ฑ ๐—ฆ๐˜‚๐—ฝ๐—ฝ๐—น๐˜†!

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
๐Ÿ”ฅ6โคโ€๐Ÿ”ฅ2โค1
Media is too big
VIEW IN TELEGRAM
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
๐Ÿ”ฅ4โค2
๐—•๐˜‚๐—ถ๐—น๐—ฑ ๐˜€๐—บ๐—ฎ๐—ฟ๐˜๐—ฒ๐—ฟ ๐˜๐—ฒ๐˜€๐˜ ๐—ณ๐—ถ๐˜…๐˜๐˜‚๐—ฟ๐—ฒ๐˜€ ๐˜„๐—ถ๐˜๐—ต ๐—ฃ๐˜„๐—ฟ๐—•๐—น๐—ผ๐—ฐ๐—ธ ๐Ÿฏ๐Ÿฎ๐Ÿฏ

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
๐Ÿ”ฅ4โšก1โค1
This media is not supported in your browser
VIEW IN TELEGRAM
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
๐Ÿ‘3๐Ÿ”ฅ2โคโ€๐Ÿ”ฅ1
Media is too big
VIEW IN TELEGRAM
๐๐จ๐ญ ๐ž๐ฏ๐ž๐ซ๐ฒ ๐ž๐ฅ๐ž๐œ๐ญ๐ซ๐จ๐ง๐ข๐œ๐ฌ ๐ญ๐š๐ฌ๐ค ๐ง๐ž๐ž๐๐ฌ ๐š ๐Ÿ๐ฎ๐ฅ๐ฅ-๐ฌ๐ข๐ณ๐ž ๐›๐ž๐ง๐œ๐ก ๐ฉ๐จ๐ฐ๐ž๐ซ ๐ฌ๐ฎ๐ฉ๐ฉ๐ฅ๐ฒ โšก

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
๐Ÿ”ฅ4โค1
This media is not supported in your browser
VIEW IN TELEGRAM
๐—ฃ๐˜„๐—ฟ๐—•๐—น๐—ผ๐—ฐ๐—ธ ๐Ÿฏ๐Ÿฎ๐Ÿฏ ๐—ณ๐—ถ๐—ฟ๐—บ๐˜„๐—ฎ๐—ฟ๐—ฒ ๐—ถ๐˜€ ๐—ป๐—ผ๐˜„ ๐—ผ๐—ฝ๐—ฒ๐—ป ๐˜€๐—ผ๐˜‚๐—ฟ๐—ฐ๐—ฒ.

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
๐Ÿ‘4โšก2โค1๐ŸŽ‰1๐Ÿ‘พ1