Understanding Machine Signals in Good Solutions
Understand the different types of machine signals supported by Good Solutions, what information they collect, and how they are used to monitor production performance.
What Is a Machine Signal?
A machine signal is information generated by production equipment that Good Solutions can use to understand what is happening in production.
Signals can originate from sensors, machine controllers, IoT devices, or other connected systems.
For example, a machine might generate:
- A pulse every time a product is completed.
- An ON/OFF signal indicating whether the machine is running.
- A pulse when a product is rejected.
- A signal when a product requires rework.
Good Solutions interprets these signals according to their configuration.
Different signal types serve different purposes, so choosing the correct type is essential.
Overview of Machine Signal Types
| Signal type | Purpose |
|---|---|
| Cycle Signal | Count production cycles and support cycle-time and stop analysis |
| Counter Signal | Count produced amounts without using the signal for stop detection |
| Production Time Signal | Identify when a machine is running or stopped |
| Extended Cycle Signal | Support production counting scenarios where standard cycle counting is unsuitable |
| Scrap Signal | Automatically register scrapped quantities |
| Rework Signal | Automatically register reworked quantities |
| Scrap Difference Signal | Calculate scrap from the difference between production counters |
1. Cycle Signal
A Cycle Signal registers a pulse each time a production cycle is completed.
For example, a machine producing one unit every ten seconds might generate one pulse for each completed unit.
Good Solutions can use this information to:
- Count production cycles.
- Calculate cycle times.
- Determine produced amounts.
- Detect production stops when cycle times are sufficiently short.
Amount per Cycle
One machine cycle does not always correspond to one finished product.
For example, a machine might produce four products during each cycle.
In this case, the configured amount factor allows Good Solutions to calculate the correct production quantity.
Example:
- 100 registered cycles
- 4 products per cycle
- Total produced amount: 400 units
The relationship between cycles and produced amounts must be configured correctly to ensure accurate reporting.
2. Counter Signal
A Counter Signal is used to count produced amounts without using the signal itself for stop detection.
It works similarly to a Cycle Signal, but its purpose is production counting rather than determining whether the machine is running.
Counter Signals are particularly useful when a separate Production Time Signal is used to monitor machine availability.
Example:
A machine produces one completed product every two minutes.
A Counter Signal registers each completed product, while a separate Production Time Signal indicates whether the machine is running.
Together, these signals provide both production quantities and running/stopped information.
3. Production Time Signal
A Production Time Signal indicates whether a machine is running.
It is typically an ON/OFF signal:
- ON: The machine is running.
- OFF: The machine is not running.
Good Solutions uses this information to identify production time and stops.
This signal is particularly important for machines with longer production cycles, where the absence of a cycle pulse does not necessarily indicate a production stop.
Example
A machine requires three minutes to complete one production cycle.
If Good Solutions only monitors completed cycles, it may be difficult to distinguish normal production from an actual stop.
A separate Production Time Signal provides information about whether the machine is running between completed cycles.
Important: A Production Time Signal provides running/stopped information but does not, by itself, count produced quantities. A separate Counter Signal can be used when production amounts are also required.
4. Extended Cycle Signal
An Extended Cycle Signal supports production counting scenarios where standard cycle counting is not optimal.
For example, a machine may produce several units during a single operation, making a simple one-pulse-per-product configuration unsuitable.
The exact configuration depends on how the machine provides production information.
This signal type is available under Settings → Machine Data → Extended Cycle Signal Connections in GS Desktop.
5. Scrap Signal
A Scrap Signal automatically registers rejected or discarded production quantities.
For example, a sensor on a production line may generate a pulse each time a defective product is removed.
Good Solutions can use the signal to register scrap against the associated Measure Point.
The configuration can include:
- The incoming I/O signal.
- The relevant Measure Point.
- A Scrap Reason.
- A Scrap Factor that determines the quantity registered for each signal.
Example:
If one scrap pulse represents two rejected products, the factor can be configured so that each pulse registers two scrapped units.
Automatic scrap registration reduces the need for manual reporting and supports more accurate quality analysis.
6. Rework Signal
A Rework Signal automatically registers products requiring additional processing.
It operates similarly to a Scrap Signal, but the information is recorded as rework rather than scrap.
A Rework Signal can be configured with:
- An I/O input.
- A Measure Point.
- A Rework Reason.
- A Rework Factor.
This allows Good Solutions to collect rework information directly from production equipment.
7. Scrap Difference Signal
A Scrap Difference Signal is used when scrap can be determined by comparing production quantities at different points in a process.
For example:
- 1,000 units enter a production process.
- 980 units are registered at a later point.
- The difference is 20 units.
A Scrap Difference configuration can register this difference as scrap.
In the documented configuration, the difference is calculated after the Article or Order run has stopped.
This method can be useful when directly counting individual rejected products is difficult.
How Signals Are Connected to Measure Points
Machine signals must be associated with the correct Measure Point.
This connection tells Good Solutions where the production data belongs.
For example, a production line might have:
| Signal | Associated Measure Point |
|---|---|
| Cycle Signal | Packaging Line 1 |
| Production Time Signal | Packaging Line 1 |
| Scrap Signal | Packaging Line 1 |
| Rework Signal | Packaging Line 1 |
Several different signal types can therefore contribute information about the same Measure Point.
Where Are Signals Configured?
Machine signals are configured in GS Desktop → Settings → Machine Data.
The configuration process generally involves:
- Creating the appropriate signal connection.
- Selecting the incoming I/O interface and input.
- Associating the signal with a Measure Point.
- Configuring any relevant factors or reason codes.
- Saving and validating the configuration.
Key Takeaways
- Different machine signals provide different types of production information.
- Cycle and Counter Signals register production quantities.
- Production Time Signals indicate whether machines are running or stopped.
- Scrap and Rework Signals support automatic quality data collection.
- Scrap Difference Signals can calculate scrap by comparing production quantities.
- Correctly connecting signals to Measure Points is essential for accurate reporting.