How HUCKEPACK gets from pressure to alarm
Measure. Pressure sensors at the hydraulic pump give a continuous reading of line pressure.
Connect. periNODE adapters turn each sensor into a network device. The reading leaves the sensor as an encrypted IP data stream over Single Pair Ethernet (SPE): one thin cable carrying data and power, which suits a vehicle.
Process on the vehicle. A periMICA edge computer mounted on the pump stores the readings and runs the HUCKEPACK analysis. The dashboard is a web page, readable from any browser on site. When pressure climbs towards a set threshold, the system raises an alarm on screen and sends a notification to the control centre.
Beyond the vehicle. A cellular gateway forwards the data to a cloud database for long-term records: a complete history of pumping activity for comparing jobs, spotting wear patterns and planning maintenance. Monitoring, dashboard and alarms work on the vehicle without a connection.
The whole system runs from the vehicle battery and needs no additional enclosures. The sampling is continuous and fast enough to catch a blockage as it develops, which is what matters here.
The pump's control system keeps running the pump
Perinet does not touch the machine control. HUCKEPACK is an independent monitoring and data path installed beside it. Alarms go to people, and the operator decides what to do: stop the pump, or clear a developing blockage by pumping back and forth before it sets. HUCKEPACK gives the early warning. It is not a safety controller and it does not act on the pump.
That separation is what makes this a retrofit rather than an engineering project. The setup goes onto new and existing vehicles alike, with no changes to the pump's hydraulics, electronics or control software, and the installation happens on the vehicle.
Developed with a concrete-pump operator and a university institute
A concrete-pump operator developed HUCKEPACK together with a university institute for construction materials. Perinet supplied the sensor topology, the hardware and the communication firmware; the HUCKEPACK software does the analysis. The system is in daily use on the operator's pumps.
Why not read it from the machine bus?
If the pump manufacturer already exposes the measurement you need through an accessible interface, use it. That is the shortest path.
Where it does not, or where the fleet mixes manufacturers and model years, an independent sensor and data path avoids a machine-bus integration project. The person building the monitoring gets the measurement on an IP interface, as MQTT and REST, instead of having to work with the vehicle's CAN bus and whatever each manufacturer has put on it. The pump keeps its bus; the monitoring gets its own path.
This is also what makes the approach portable across construction equipment monitoring more broadly: the same path works on any machine with a measurable signal, regardless of who built it.
Where the same approach fits
Mobile and heavy equipment: hydraulic pressure on cranes, lifting platforms, forklifts and other construction machinery.
Fixed high-pressure lines: pumping stations and water networks where a developing fault shows up as a pressure trend.
Any machine that has to work anywhere: measurement, processing and alarms on the vehicle, with the network as an addition rather than a requirement.