Multi-turn is an information scope that should retain its implementation conditions.
Keep the retention basis identifiable
Dynapar's cited encoder information identifies a battery-based multi-turn option. That product-specific architecture should not become a universal assumption about every absolute encoder. Primary reference: Dynapar identified multi-turn architecture.
Record single-turn and turn-count information separately. Ask what remains valid when external power is absent and what conditions support retention or tracking. The selected encoder, power arrangement and documentation determine that behavior; an absolute label alone leaves the implementation question incomplete.
A hypothetical power-loss comparison
Imagine two fictional offers claiming multi-turn position. One identifies a battery-supported condition, while the other identifies a different documented mechanism. Make a matrix of retained information, unpowered movement behavior, required support conditions and indicated faults. Do not assume the two implementations share every battery or restart requirement.
Keep the exact option designation with its supporting reference. This example selects no HM encoder, battery, service interval or retained-turn capacity. It does not prescribe disconnecting equipment or testing movement during an uncontrolled power interruption.
Specify the information that must stay valid
Ask which restart and service scenarios the project needs to support and how the proposed feedback handles each. Include replacement or reference-reset behavior in the applicable documentation rather than relying only on normal-operation positioning information.
Preserve the accepted architecture with the machine's coordinate mapping and relevant maintenance scope. The guide helps a buyer interpret multi-turn claims without asserting that all absolute encoders are battery-free, prescribing a retention duration or claiming that retained encoder turns automatically establish the validity of every physical reference after a mechanical change. Retain the exact option code in the restart evidence.
Customer Questions
Are all multi-turn encoders battery-based?
No. Identify the actual selected architecture.
Does absolute alone describe unpowered tracking?
No. Retain its documented conditions and information scope.
Does retained turn count prove every machine reference?
No. Preserve the coordinate mapping and service context separately.
Primary References
These references support the technical principles discussed in this guide. The worked examples and review questions are educational.
Discuss Your Machine Requirement
Share your product, container, required output and the evidence needed for your technical review.
Request a Technical Review