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.
Please open Telegram to view this post
VIEW IN TELEGRAM
โค3๐ฅ3๐3
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.
Below are the changes in this and the previous release, 0.15:
- Sub-unit specifications for the Device Under Test (DUT)
- Storage of measurements and production process data
- Equipment information used 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
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
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
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.
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.
everypinio.github.io
HardPy
โก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:
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
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
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
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
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
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
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
