From the factory
to the field.
Your responsibility doesn’t end when a charger ships. Neither should your ability to support it.
Test every unit
Run OCPP checks before shipping and keep a record of each charger’s test results, firmware version, and readiness.
Connect through Pirx
Route OCPP communication through Pirx while your customers continue using their existing charging backend.
Monitor and update
Keep track of deployed chargers, investigate problems, and manage firmware updates without taking over the customer’s charging operation.
Your chargers leave the factory.
Your visibility shouldn’t.
Every charger has a history. Know how it performed before shipping, which firmware it’s running, and what happens after installation.
When something goes wrong, you have the information to understand it and the tools to act.
A test record for every unit
Keep individual test results linked to each charger. Know what was tested, which firmware was installed, and whether the unit was ready to ship.
Test on one. Roll out to all.
Verify a firmware release before deploying it across your installed base. Manage rollouts by charger model and firmware version, with visibility into deployment progress.
Spot patterns before the tickets arrive
See recurring problems across chargers, models, and firmware versions. Identify issues affecting your installed base before they become widespread support cases.
Your customers keep
their backend.
Your customers have their own charging platform, and they should be able to keep it.
Pirx connects your chargers to their existing OCPP backend through a proxy. Their charging operations continue on the platform they chose, while you gain the hardware visibility needed to diagnose problems and support your products.
Your hardware.
Their charging business.
You need insight into your chargers, not control over your customers’ business. Pirx keeps those responsibilities separate.
Focused on hardware data
Access the technical information you need to understand charger behavior, investigate faults, and manage firmware, without taking over customer accounts, payments, or charging operations.
Updates with customer consent
Manage firmware updates with your customers’ approval. Keep visibility into what was deployed, where, and whether the update succeeded.
Frequently asked questions
Do my customers need to use EOSVOLT?
No. Pirx works with your customers’ existing OCPP backends. They can keep their charging platform while you use Pirx to manage and support your hardware.
Can we test chargers before shipping?
Yes. Pirx lets you run OCPP checks on individual chargers and maintain a test record for each unit before it leaves the factory.
Can we update firmware after deployment?
Yes. Pirx supports firmware rollout management, allowing you to deploy updates to connected chargers with the appropriate customer approval.
What information can we see from deployed chargers?
You can monitor hardware status, firmware information, and OCPP communication to help diagnose charger problems, based on the data available through the Pirx connection.
Can we identify problems affecting multiple chargers?
Yes. Pirx helps you spot recurring issues across charger models and firmware versions, making it easier to investigate and prioritize fixes across your installed base.
Explore
the connected capabilities.
Pirx test bench
Connect a real charger and get a scored report with every finding, its evidence and what to change. Fix the firmware before the charger meets a production backend.
Supported hardware
Connect supported AC and DC chargers over OCPP, and manage monitoring, remote commands, and firmware for every model.
Intelligence
Follow charger health across your network. Group repeated faults into issues, find the chargers that need attention, and read why a session failed.