<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=3209473&amp;fmt=gif">
Skip to content
English - United States
  • There are no suggestions because the search field is empty.

What should I do if weight is not detected or measurements appear as predicted?

What should I do if weight is not detected or measurements appear as predicted?

Overview

In some scanning sessions, the turntable may fail to detect the client's weight, or the software may display predicted measurements instead of scanned ones. These are edge cases with straightforward resolutions.

Weight Not Detected

Steps:

  1. Select Retry to attempt the weight measurement again.
  2. If the turntable still does not detect weight, select the option to enter body weight manually using a value from a separate scale.
  3. Confirm the entered weight and continue with the scan.

Predicted Measurements Displayed

Predicted measurements are estimates generated by the software's algorithm when a scan cannot be fully measured. They are less accurate than directly measured values.

Common causes:

  • Loose or baggy clothing
  • Unfavorable lighting or scanning environment
  • Improper scanning posture

Steps:

  1. Review the 3D scan image to assess overall quality.
  2. If the scan looks poor or a procedural step was missed: select Scan Again and correct the issue (attire, posture, environment) before rescanning.
  3. If the scan looks good and all procedures were followed correctly: you may accept the scan to avoid unnecessary repeat scans.

Notes

  • Predicted measurements can influence body composition algorithm outputs, potentially reducing result accuracy. Rescan when in doubt.
  • Always confirm form-fitting attire and proper posture before scanning to minimize the likelihood of predicted measurements.

If this resolves your issue, no further action is needed.

If the problem persists, contact support and include: a description of the scanning environment, attire worn, software version, and whether the issue occurs consistently or intermittently.

Applies to: All Styku configurations