Monitoring
Equipment status, programs, values and active events in real time.
Kare Signal
Kare SignalMake automation data visible and usable
Bring robot, PLC and other automation status, faults, history and production data into one environment.
Kare Signal
A data layer on top of existing automation
Kare Signal is built as a whole that fits the customer’s equipment. It collects status, events and process data from different devices, turns them into history, and makes the information usable in production, maintenance and automation.
When needed, Signal can also transfer non-time-critical production and process data between systems from one place.
History & diagnostics
Faults, events, runtime data and process values for later review.
Data integrations
Defined data between devices and systems, managed from one place.
Monitoring and diagnostics
See what is happening now — and what happened before the issue
Live status
See the device connection, operating mode, running program, key values and active events in one view.
Fault history
Store faults and events in history and see what happened in the system before and during a stop.
Runtime monitoring
Follow equipment run, stop and fault times relative to a defined production time.
Process data
Select the process values that matter on the equipment and follow them live or store them for later review.
Data integration
Non-time-critical data from one system to another, centrally
Signal can transfer defined production and process data between devices and systems. The source, target and data are defined in Signal, after which the transfer happens centrally.
Example
KUKA Robot
JOB.nProductType
Kare Signal
Data mapping
Beckhoff PLC
MAIN.nProductType
Signal complements automation — it does not replace it
Kare Signal sits on top of the actual automation. Fieldbuses, safety, motion control and other time-critical or deterministic communication remain the responsibility of the PLC, robot and automation system.
Signal focuses on presenting data, storing history, diagnostics, and system-to-system transfer that does not require fieldbus-level real-time performance.
Built around the equipment you have
Signal is connected to the environment the customer already has
Commissioning starts by choosing the equipment, data sources and uses that are needed. The solution can begin with one machine or robot and later expand around the rest of production.
- On-site installation
- On the customer’s production network
- Historical storage
- Browser / HMI
Equipment and automation
Signal is connected to the machines, robots, PLC systems and data sources whose information is needed.
Data from different equipment in one environment
Bring the relevant states, events and process values into the same view, regardless of manufacturer.
Views for the job
Use the data in a browser, on a production dashboard, or as part of an existing HMI.
Examples of current integrations
KUKA KRC
Robot status, operating mode, program data, system and user messages, and selected KRL variables.
KUKA Fleet
AMR status, faults, battery data and operating history in the same Signal environment.
Beckhoff ADS
PLC variable read, storage and defined non-time-critical data transfer through Signal.
Other environments can be implemented according to the use case and the equipment in place.
What data from your equipment should be made visible?
Signal can be built around one robot, machine or cell and later expanded to the rest of the equipment.
- On-site installation
- On top of existing automation
- Expandable with the equipment