Vibration monitoring on the press drive: predict failures of the motor – do not wait until idle.

Capture multi-sensor data such as vibration & temperature on the drive, evaluate it with AI and plan maintenance.
You want to know at any time whether your press drive is running stable? That's what you're setting up for. Multi-sensor system one. With this you can Failures Timely Forecasts Plan your budget optimally.
Throughout Wireless sensors It is especially easily The multi-sensor system retrofitting. The gateway and data infrastructure provide data management. The AI At the beginning of the project, certain Evaluations shall be carried out. More complex evaluations are quickly integrated. The Browser cockpit Only show you the Results which you really need.
sensor node, data infrastructure, evaluation algorithms or data retrieval. All system components Coming from one hand. They are coordinated for smooth operation. If you would like to request an individual solution or need support, you can ask us. No matter which system component.
Multi-sensors are for your AI and data evaluation as Additional senses.
Instead of just "vibration yes/no" you get a Overall picture your motor from various sensor information (vibration, temperature, ...) at the measuring point. By Detected Your AI Imminent standstill better. With this information you can Proactive exchange parts, instead of you on one Annual assessment to leave.


You place the sensor nodes at the relevant points of your drive train, for example on the engine, gearbox, bearing or clutch. You start without complex wiring and without long downtimes.
You put the gateway into operation and start the data collection. You get a data stream directly from the plant and create transparency about the status during operation.
You see trends and abnormalities in the browser. From this, you deduce whether you will be active in the next maintenance interval and which measures you plan.
If in a particle board plant you Main press Wanting to secure, hardly a path leads to one Vibration monitoring past the press drive. Because the press drive is often the critical bottleneck: As soon as the motor or drive train fails, there is no "any system", but often The whole line – with high downtime costs, high internal coordination and massive pressure on maintenance and production.
This is precisely why this use case is not about "more data", but about Make the condition visible:
In this section you will read which job you want to solve around the press drive, why annual assessments in everyday life lead to blurred decisions, which requirements a retrofit solution must meet – and how you can orbit sense READY in a pilot in such a way that measured values become real predictability.
You are responsible for ensuring that the press drive runs reliably. Your job is, between maintenance intervals to be able to assess whether the drive is working stably – or whether a risk is building up that you have to take into your planning early on.
In practice, this means that you do not want to hear "in 5-8 months it could be critical" once a year, but you want answers to questions such as:
Especially with large presses, this is crucial: An unplanned standstill can be extremely expensive, and a replacement on the main drive can take a very long time. The sooner you see the condition and trend, the sooner you can take measures to ensure that production, spare parts and service providers Without escalation fit together.
Many particle board plants assess the large press and its press drive once a year. That gives you a snapshot. However, your operation is constantly changing: load change, shift operation, temperature, material, start-up and shutdown phases. If you do not see the course, you plan with uncertainty.
This uncertainty produces typical effects:
The core problem is: Between the Service intervals The condition is unknown. And that's where the stress comes from. As soon as the press drive fails unplanned, you have to find causes under time pressure, coordinate measures and justify costs – even though you had little chance of seeing the development clean beforehand.
The solution is not "yet another report" but Condition monitoring As a continuous process: vibrations, temperature and context signals show you whether something is building up – long before it pops.
You want to quickly find out if an approach to your press works. You need clear signals that you can use in everyday life. And you don’t want to start a months-long integration project.
A practical retrofit solution for Vibration monitoring on the press drive Therefore, usually meets these requirements:
1) Fast start without plant conversion
You want to retrofit sensors, test measuring points and see the first trends within a short time – without a shutdown project.
2 2 Unique diagnostic signals instead of data lettuce
You want to know if a bearing is running healthy or if a typical pattern of wear/damage is building up. Right here is Vibration analysis strong, because bearing states can often be clearly depicted in vibrations.
3) Context for load and operating states
Vibrations alone are good – but in the factory you also want to understand why A signal changes. Changing loads is everyday life. If you can also classify load/operating states cleanly, your evaluation will be more stable and your planning better.
4) Low coordination with IT and operations
You want a solution that you can operate without permanently committing internal resources – and the results must be traceable for maintenance and production.
The orbit sense READY You use it as a continuous system: Capture → Transmission → Visualization → (optional) model/logic.
Detection at the drive (measurement points in practice)
For the press drive, typical measuring locations are where changes in state are best shown – especially in the case of bearing and drive problems:
What is important is less "the one perfect point", but a setup that gives you Reproducible trends delivers. Therefore, it is helpful to quickly test measurement points in the pilot and to select them so that the signal is stable and meaningful.
Assembly: fast retrofit, clean coupling
You have several options to get the vibrations clean into the sensor:
Multi-sensor technology: not only vibration, but context
Orbit detects not only vibrations, but several signals per sensor node – this is exactly what is an advantage in the factory because you get operational context:
Data chain:
The nodes run battery-operated and transmit wirelessly to a gateway. In the browser cockpit you see raw data (for analysis) and condensed signals (for everyday life). This gives you a clean end-to-end chain from measurement point to visualization – without needing a large-scale integration.

If you monitor the press drive with vibration monitoring and context signals, your everyday life changes noticeably. Five concrete effects:
Especially the load recognition via magnetic field signatures and the indirect speed help to interpret measurement data better: You separate "signal changes because of load" from "signal changes because of state". This makes warnings more resilient and you get fewer false alarms.
You look into the cockpit and see the condition of the press drive as a course: stable, drifting or critical. You recognize early on when a risk builds up — and you can drag action into scheduled intervals instead of being surprised by unplanned downtime.
This relieves maintenance and production:
Thus, "Daueranspannung" becomes a plannable process: recognize state, derive measures, carry out standstills in a controlled manner.
You briefly describe your press and your drive structure (motor, bearing points, drive train, typical load conditions, maintenance intervals). We give you a clear assessment:
Pilot logic as it works in practice:
The First data Usually run after ca. 10 minutes one. With simple evaluation techniques (trends, basic checks) can be started immediately after installation. For robust predictive models, additional history is required depending on the target.
As a sensor node, we call our Multi-sensor. Each multi-sensor consists of a printed circuit board with 10 individual sensors: vibration/vibration (acceleration), gyro, magnetic field, temperature, humidity, air pressure, VOC/BVOC, eCO2, IAQ index and light. In addition, further external sensor parameters can be connected (depending on the setup).
As standard, a system with 5 sensor nodes is supplied. For a press motor, many customers start with 1–2 sensor nodes, to collect vibration data on the motor/bearing (plus optional temperature). For the whole press system often come Multiple points at bearing points/gearboxes/drives thereto. (This depends heavily on mechanics, accessibility and the expected error pattern.)
There are several mounting options – depending on how "fast" or "industrialized" it should be:
This depends heavily on the use case – especially on the Sample rate:
If a permanently high measuring load is required, the energy supply can also be ensured via the power grid by wiring.
In principle, yes. By default, we work with our sensor node ecosystem, but existing sensor technology can be integrated depending on the signal/interface – typically via MQTT or REST, or via the gateway with Bluetooth. If there is no direct standard connection, it is an integration project.
sensor node to gateway runs over Bluetooth Low Energy (BLE). Gateway to cloud typically runs over LTE or WLAN. The range depends on the environmental conditions; In practice, depending on the bandwidth/data load, we typically up to about 10 meters around the gateway.
This depends heavily on the use case or on the data rate:
Standard is the connection by LTE/WLAN into the cloud. If data is to remain local, the gateway can also transfer data to a Customer-side MQTT brokers or in one of the Customer-side database transferred. Typical integrations are MQTT and REST.
Typical: Mount sensor nodes → Name measurement points in the dashboard → Check data. For pure monitoring, this can be done within A few minutes. Standard data evaluation included. When a complex AI use case is implemented, data/target definition and acceptance are added.
Updates are usually carried out via Remote mechanisms (Gateway/Backend) so that the systems remain up to date.
For vibration are up to 800 Hz possible (in short also up to 12kHz). Other environmental sensors typically run slower.
In principle, they shall: Raw data. During processing (e.g. by AI), it can be decided whether Raw data stored or if only Aggregated/processed values (features/results) to the database and displayed in the dashboard.
By default, these data are Cloud on German, GDPR-compliant servers stored. Alternatively, the gateway data can also be Customer-side MQTT or one of Customer-side database supply.
If raw data is written to our internal database, the Memory duration configured will become. Typical guidelines are – depending on the amount of data and customer requirements – with ca. 1 to 12 months.
This can run on two tracks: you get Automatic evaluations (dashboards/alarms/models), and We support during setup and interpretation – depending on whether you prefer self-service or support in the project.
Typical: Define goal → collect data → test features/models → validate → put into operation. The duration of A few weeks (Anomaly/Trend) to several months (Regression/RUL), depending on how many relevant events/pauses exist as a learning base.
We offer a Update service (various terms possible, at least 2 years included), with which the system Remote update is kept up-to-date. Also included Fault analysis in many cases run very well remotely: For each system component, a Remote service order are requested to examine causes and to derive measures.

