Machine I/O
Running state, part-count pulses and other suitable discrete signals can provide a simple path for equipment that does not expose useful controller data.
CONNECTIVITY
ClearRivet is designed to work with a practical range of production-data sources. The connection method is selected during commissioning based on the equipment, network and required data.
WHY IT MATTERS
The goal is production visibility, not control-system replacement. Connection design should minimise production risk and prefer read-only data access where controller protocols are used.
Running state, part-count pulses and other suitable discrete signals can provide a simple path for equipment that does not expose useful controller data.
Where supported and approved, ClearRivet can use read-only controller data to capture machine state, counts and other production values.
OPC UA and Modbus are supported integration paths for suitable equipment. Final tag/register mapping and network access are validated during commissioning.
CLEARRIVET APPROACH
The goal is production visibility, not control-system replacement. Connection design should minimise production risk and prefer read-only data access where controller protocols are used.
COMMON QUESTIONS
Production monitoring should normally use the minimum access necessary. Read-only integration is preferred unless a specific approved function requires otherwise.
Often yes. Legacy equipment can sometimes be monitored using discrete signals or external sensing when useful controller data is unavailable.
No. Controller model, protocol availability, network rules and tag/register access vary. Compatibility is confirmed during technical scoping.
EXPLORE CLEARRIVET
See it. Then prove it.