Operational data: Cumulative

These counters typically increment and persist over the long term. They might reset only upon major component replacement or complete system overhaul.

Examples:
Total operating hours of the hoist, total hoisting cycles, total number of starts of the hoisting movement, total distance travelled.

Numerical values.

Individual 32-bit Unsigned Integers (binary).

Examples of units: Seconds, meters.

240 bytes per retrieval.

Yes.

Values are  generated continuously in the sense that its value is updated and stored whenever the hoist is used.

No.

Value is updated and stored only when the hoist is used.

Data is accessible over the HMI embedded into the condition monitoring unit. It is also available in YKC if TRUCONNECT gateway is included in the rope hoist product.

Operational data: Cyclic/Event-Based

 Individual operations or recent, specific events.  Often, this data might be logged per cycle or when a significant change occurs.

Examples:
Load change in the latest hoisting cycle, maximum hoisted load.

Numerical values.

Individual 32-bit Unsigned Integers (binary).  

Real.

Examples of units: Kilograms.

12 bytes per retrieval.

Yes.

Values are  generated continuously in the sense that its value is updated and stored whenever the hoist is used.

No.

Data is accessible over the HMI embedded into the condition monitoring unit. It is also available in YKC if TRUCONNECT gateway is included in the rope hoist product.

Operational data: Real time measurements

 Load. Position of the hook. Speed.

Numerical values.

Individual 32-bit Unsigned Integers (binary).  

Examples of units: Kilograms.

56 bytes per retrieval.

Yes.

Values are updated and stored continuously.

Yes.

Values are updated and stored continuously, in a real-time.

Data is accessible over the HMI embedded into the condition monitoring unit.

Health & Performance Indicators (Derived/Aggregated)

These often provide more actionable insights by aggregating or processing the raw operational data.

Examples:
Hoist DWP%, Brake DWP%, DWP% of the electrical components, exceeding of design limits.

Numerical values.

Individual 32-bit Unsigned Integers (binary).

Percentage.

32 bytes per retrieval.

Yes.

Values are  generated continuously in the sense that its value is updated and stored whenever the hoist is used.

No.

Value is updated and stored only when the hoist is used.

Data is accessible over the HMI embedded into the condition monitoring unit. It is also available in YKC if TRUCONNECT gateway is included in the rope hoist product.

Environmental data

Ambient temperature  extremes (min/max). Continuous measurements.

Numerical values.

32-bit Unsigned Integer (binary).

Examples of units:
Celsius.

24 bytes per retrieval.

Yes.

Continuous for extremes, when extreme values are exceeded.

Yes.

Real-time for the continuous measurements coming from the sensors.

Data is accessible over the HMI embedded into the condition monitoring unit. Part of it is also available in YKC if TRUCONNECT gateway is included in the rope hoist product.

Fault/event data

Fault log.

 32-bit Unsigned Integer (binary).

240 bytes  per retrieval.

Yes.

Values are  generated continuously in the sense that its value is updated and stored whenever the fault or event occurs.

No.

Data is accessible over the HMI embedded into the condition monitoring unit. It is also available in YKC if TRUCONNECT gateway is included in the rope hoist product.