
An animated joint can look correct while representing the wrong unit, an old reading or a substituted default. A useful Perspective component needs a small input contract and a defined response when that input is no longer trustworthy.
Let Perspective resolve the binding
Keep tag paths in the consuming Ignition project. Perspective resolves bindings and supplies component properties; the renderer should not hide its own tag queries or HTTP polling behind the visual. This lets different projects reuse a component without adopting one installation’s tag structure.
The local Robot3D development contract uses props.joints.j1 through j6 for angles in degrees. For example, a project can bind props.joints.j1 to its own test tag. The existence of that contract does not establish successful live multi-axis operation: the project’s evidence report still lists real Tag Binding acceptance as pending.
Carry the meaning, not only the number
Ignition’s tag-reading documentation describes qualified values with value, quality and timestamp. Its quality-code reference distinguishes valid data from uncertain or failed conditions. Preserve that meaning at the presentation boundary instead of converting every input to a bare number.
| Contract field | Why it matters |
|---|---|
| Value | The observed angle or state |
| Unit | Degrees, radians or another documented quantity |
| Quality | Whether the observation can be represented as current |
| Capture/receive time | Whether the input is recent enough for its purpose |
| Source identity | Which object and data channel own the observation |
This is a recommended integration envelope, not a claim that every field already exists as a public Robot3D property. Map it deliberately to the actual component schema and retain any missing quality context in the surrounding HMI.
Reject malformed inputs explicitly
null, an empty string and an invalid number are not zero degrees. Reject non-finite values, validate joint count and use the reviewed unit conversion once. If the source reports radians and the property expects degrees, define degrees = radians × 180 / π in one documented place.
Separate input validation from visual interpolation. Smoothing valid observations can make motion easier to read, but it does not estimate a trusted actual pose between measurements or solve the controller’s kinematics. A smooth display can still be stale.
Decide what missing data looks like
A last-valid-pose display should say that it is retained and show communication status. Returning a model to a nominal pose may be visually convenient but can falsely imply the machine is physically Home. Treat any such fallback as a labelled display policy, never an actual position.
Do not remove an HMI’s quality overlay merely to make the view look clean. Do not equate a connected browser session with a healthy controller signal. The telemetry guide explains how connection state and sample freshness can disagree.
Review the contract in a test view
Use isolated test tags and a reviewed project, not production writes. Check each axis separately, the unit conversion, an invalid sample, quality loss, reconnection and multiple component instances. Test resize and navigation because a renderer that keeps running after unmount can leak GPU resources or duplicate listeners.
Record the component version and which tests actually passed. Schema, React props, renderer validation and documentation must change together when a property is renamed. The visualization owns appearance; controller commands, interlocks and safety functions remain outside its responsibility.
