Guide / 05
Use Motion Symptoms to Narrow the Fault
Write observable desk-motion symptoms in enough detail to distinguish a possible controller problem from a supply, handset, cable, column, or mechanical issue.
Describe the request and response
Begin every diagnosis note with the command requested and the response observed. ‘Pressed up; both legs began; left stopped after one second; handset stayed lit’ is much more useful than ‘desk broken.’ It locates the problem in a sequence rather than assigning blame to the nearest component. Record the desk height if known, the load on the surface, and whether the response changes in the other direction.
Separate sound from motion. A click, hum, relay sound, or silence can each be useful evidence, but none alone names a failed part. Note where the sound seems to come from and whether it repeats. Avoid putting hands near moving columns or under a loaded desktop while trying to locate it. Observation should not require placing yourself in a pinch zone.
Take a short video only if it can be done safely from a clear position and without encouraging repeated fault cycling. One well-framed recording of a symptom may help a manufacturer far more than ten reset attempts. Stop if motion becomes uneven, harsh, or otherwise concerning.
Look for symmetry without forcing it
A two-leg desk should normally show coordinated movement, but an asymmetry is a symptom, not a command to keep driving the other leg. If one side lags, stops, or travels differently, release the control and inspect from a safe position with power removed. Continued operation can rack the frame, strain the desktop, or make an original cable issue worse.
Note whether the asymmetry occurs at the same height, only in one direction, only with a particular load, or immediately after power is applied. A repeatable height can point toward an obstruction or cable path. A response that changes after a documented reset can suggest a control-state issue. These are clues for further assessment, not proof of a component diagnosis.
Do not try to level an uneven desk by manually lifting one side unless the manufacturer’s instructions explicitly describe a safe method. The frame may store load or move unexpectedly. Preserve the observation and seek the desk family’s support procedure.
Separate handset behavior from system behavior
A handset can be illuminated, blank, frozen, or partially responsive. Record exactly which condition occurs. A blank display does not automatically mean a bad handset; it can reflect the supply, controller, cable seating, or a protection state. A lit display with no motion tells a different story but still does not identify a single failed part without documentation.
If the desk manual specifies a reset or initialization sequence, follow it only after basic safety checks and only for the matched equipment family. Record the sequence and result. Do not borrow reset instructions from a similar-looking controller or a generic video, because a held button or travel sequence can mean different things across systems.
Avoid opening the handset or controller to chase a symptom unless authorized repair guidance and competence support the work. External labels, connectors, and documented behavior are safer evidence sources than improvised internal inspection.
Inspect accessible mechanics with power removed
With the desk unplugged and stable, inspect accessible cable paths, mounting hardware, crossbars, and obvious obstructions. Look for a loose connector, a pinched lead, a cable that has been pulled from strain relief, or an item caught in the frame. Do not disassemble lifting columns or reach into mechanisms that may be under load. The purpose is to find visible, low-risk evidence, not to turn a symptom check into a mechanical teardown.
Consider changes to the desk environment. A new cable basket, under-desk drawer, monitor arm, or storage box can interfere with travel or add load. Document these changes without assuming they caused the fault. If the symptom appeared after a move, include whether the desk was transported upright, whether cables were disconnected, and whether the frame was reassembled.
Mechanical observation can rule out a simple obstruction, but it cannot prove the controller is sound. Keep the result in the matrix as observed evidence, then combine it with identifiers and support guidance before replacing components.
Use load information carefully
A desk that moves empty but stops with ordinary equipment may have a load, balance, mechanical, or control issue. Record the approximate arrangement rather than guessing a precise weight. Note whether heavy equipment is centered, whether a monitor arm changes the load during travel, and whether the symptom appears near a particular height. Do not use repeated loaded cycles as a test when the desk is already behaving abnormally.
Capacity numbers are not a diagnosis tool. A stated desk capacity can include assumptions about balanced placement and normal operation. It does not tell you that a controller, column, or frame is healthy at every load below the number. Treat a changed load response as a reason to stop and seek system-specific guidance.
If a desk is visibly out of level or a leg is not extending normally, remove nonessential surface items only when it can be done safely and without leaning under the frame. The goal is to reduce risk while preserving the symptom record.
Build a decision tree from evidence
A simple decision tree starts with safety: any heat, odor, damaged insulation, sparking, breaker event, severe asymmetry, or structural instability is an immediate stop. The next branch is power: does the documented supply show expected status, and are accessible connections intact with power removed? Then comes control response: does the handset behave, and does the desk respond in either direction? Each branch should refer to a documented check rather than an improvised test.
The controller-box branch belongs later in the tree. It becomes plausible when the system identifiers are known, supply and cable evidence has been considered, and manufacturer guidance points to the controller as a service item. A box is not exonerated because it looks clean, nor condemned because it is easy to reach. The evidence needs to point there.
Write the tree in terms of next actions, not self-diagnoses. ‘Ask support to evaluate controller X with leg set Y after observed one-leg stop’ is actionable. ‘Controller dead’ often is not. A decision tree earns its value by making uncertainty visible and keeping powered experiments bounded.
Know when to stop diagnosing
DIY observation has a boundary. Stop when there is mains-side damage, unclear wiring, a structural fault, repeated uncommanded behavior, or any result that cannot be made safe with the desk disconnected. Stop as well when you lack a documented compatibility path for a proposed replacement. More experimentation will not turn an unknown pinout or damaged component into a safe system.
A qualified technician or the original manufacturer can use your record more efficiently when it contains symptoms, labels, port photographs, and recent changes. The record is not an admission of failure; it is what turns a handoff into a specific technical question. Keep the original components available until the next path is confirmed.
The best diagnosis note is modest. It says what happened, what was observed, what was not changed, and why the next step needs documentation. That restraint can prevent a small fault from becoming a damaged desk or an unsafe installation.
End the observation at a safe boundary
End the symptom session with the desk disconnected if any uncertainty remains. Write the last safe state, the most recent command, and the component identifiers available. That boundary preserves a clean handoff and prevents a later attempt from being mistaken for part of the original fault pattern.
A symptom record should also state the conditions that were not tested. Perhaps the desk was left unloaded, a memory function was deliberately avoided, or only a short movement was observed because the frame appeared uneven. Those limits prevent another reader from overinterpreting silence in the notes. Diagnostic restraint is useful evidence: it shows that a risky test was intentionally omitted rather than forgotten, and it points the next person toward the least disruptive safe check.
Make one observation worth sharing
A useful observation contains time, direction, motion, sound, and stop point. It should be specific enough that a support person could recognize what was not tested and why. Avoid editing the account into a theory after the fact. The closer the note stays to what the desk did, the easier it is to decide whether a controller replacement is justified or whether the evidence belongs with a different component or mechanical check. Note environmental details that affect repeatability, such as whether the frame was against a wall, a drawer was open, or a new accessory was attached. Context can show why an apparently intermittent event is actually linked to a particular position or route. Include what happened after the control was released; a continued sound, a clean stop, or a delayed indicator change can be meaningful context for a documented diagnostic path.
Keep the next handoff concise
When a symptom record is complete, stop adding speculative fixes to it. Share the labels, video or notes, and the exact condition under which the desk was left. A focused record lets another person decide on the appropriate service path without separating observations from several rounds of conjecture.