Configure an IoT Device in Good Solutions
Learn how to configure an IoT device in GS Desktop, identify its machine inputs, and prepare it to collect production signals.
Overview
Good Solutions can collect production data directly from machines using IoT devices.
An IoT device receives signals from production equipment and makes them available to Good Solutions. These signals can provide information about:
- Completed production cycles
- Machine running and stopped states
- Produced quantities
- Scrap and rework
Before these signals can be used, the IoT device and its inputs must be configured in GS Desktop.
This article explains how to prepare an IoT device for production data collection.
NOTE! The configuration of RS IoT devices is normally performed with the help of a Good Solutions Customer Success Manager or technical specialist. We recommend that you discuss with them when configuring your IoT devices.
Before You Begin
Make sure you have:
- Access to GS Desktop with the necessary configuration permissions.
- An IoT device connected to the machine and available in GS Desktop.
- Information about which physical inputs are connected to which machine signals.
- The name of the Measure Point that the machine belongs to.
Tip: Document the physical input connections before starting. Knowing which input represents a cycle pulse, running state, or quality signal makes configuration considerably easier.
Step 1: Locate the IoT Device
- Open GS Desktop.
- Navigate to Settings → Machine Data.
- Locate the RS-IoT/RSBlackBox section.
- Find the IoT device you want to configure. A newly registered device may be named New I/O-interface.
- Select the device.
- Click Open.
The device configuration opens.
Step 2: Configure the Machine Inputs
- Open the Inputs section.
- Locate the physical input connected to the machine signal.
- Rename the input to describe its purpose.
For example:
| Input | Suggested name |
|---|---|
| Input 1 | Packaging Line – Cycle |
| Input 2 | Packaging Line – Running |
| Input 3 | Packaging Line – Scrap |
| Input 4 | Packaging Line – Rework |
Use names that make it easy to identify both the machine and the signal.
This is particularly important when several machines or Measure Points are connected through different IoT devices.
Step 3: Verify the Incoming Signal
GS Desktop provides a Debug option for checking incoming signal changes.
- Locate the input you want to test.
- Enable Debug.
- Generate a signal from the machine.
- Check that the expected rising and falling signal edges are detected.
- Repeat the test if necessary.
For example, if you are configuring a Cycle Signal, run a few production cycles and verify that the corresponding input changes are detected.
Important: Disable Debug after completing the test. Leaving Debug enabled can generate unnecessary processing and contribute to server overload.
Step 4: Configure the Input Type
The IoT device must interpret the incoming signal correctly.
Two important input settings are:
IsCounterInput
Enable IsCounterInput when configuring an input used for cycle counting.
This identifies the input as a counter input for collecting production pulses.
Pulse Input Status
Enable Pulse Input Status for an input used as a machine running signal.
This setting is used for Production Time Signals that indicate when the machine is running or stopped.
| Signal purpose | Input setting |
|---|---|
| Cycle Signal | IsCounterInput |
| Production Time / Running Signal | Pulse Input Status |
Important: Pulse Input Status should be enabled for running signals, not Cycle Signals.
Step 5: Save the Configuration
Once the inputs have been named, tested, and configured:
- Confirm that the input settings match the connected machine signals.
- Make sure Debug has been disabled.
- Click Save and Close.
The IoT device is now configured and ready for its inputs to be used in signal connections.
What Happens Next?
Configuring the IoT device prepares the physical inputs, but it does not complete the production data configuration.
You must also create the relevant signal connections and associate them with Measure Points.
For example:
- A Cycle Signal connection associates production pulses with a Measure Point.
- A Production Time Signal connection associates running/stopped information with a Measure Point.
- Scrap and Rework Signal connections associate quality-related signals with production.
These connections are configured separately under Settings → Machine Data.
Verify Your Configuration
Before continuing, confirm that:
- The correct IoT device has been selected.
- Each input has a recognizable name.
- Incoming signals have been tested.
- IsCounterInput is configured for the relevant cycle inputs.
- Pulse Input Status is configured for the relevant running signals.
- Debug is disabled.
- The configuration has been saved.
Common Problems
No incoming signal is detected
Check that the correct IoT device and physical input have been selected. Verify that the machine is generating the expected signal.
The wrong input is being triggered
Review the physical input connections and input names.
The signal is detected but production data is missing
The IoT device may be configured correctly, but the corresponding signal connection or Measure Point association may still be missing.
Debug remains enabled
Disable Debug after testing to avoid unnecessary processing.
Key Takeaways
- IoT devices provide a connection between machine signals and Good Solutions.
- Inputs should be clearly named according to their purpose.
- Debug can be used to validate incoming signals but must be disabled afterward.
- Cycle and running signals require different input settings.
- Signal connections must be created separately to associate the inputs with Measure Points.