Trackball diagnostic guide

Trackball: test the fault before changing parts or settings.

Test buttons, pointer movement and scrolling separately to distinguish sensor/ball contamination, switches, connection and software settings.

4 relevant tests3 first checksBrowser limits stated

Start with a clean baseline

Separate the local link from internet reachability and application performance. Wi-Fi marketing speed, Ethernet port speed, ISP speed and browser throughput are different measurements.

Live evidence

Relevant checks

First sequence

Do the high-signal checks before risky changes

  1. 1

    Clean the ball/sensor area according to manufacturer guidance

  2. 2

    Test buttons and movement separately

  3. 3

    Compare wired/wireless path if available

Decision points

What the result should change

If one client fails, others workPrioritize the client adapter, saved network, cable/port or device policy.
If all clients lose internet but stay associatedPrioritize WAN/modem/DNS/upstream status rather than each device.
If wired is stable and wi-fi is notPrioritize RF placement/interference/channel/client-band behavior.
Browser can help check
  • Observe pointer and button events
  • Test scroll events
Browser cannot prove
  • Measure ball bearings/sensor optics physically
  • Read proprietary DPI/profile memory

Repair boundary

Know when to stop browser troubleshooting

  • Do not factory-reset a managed or ISP-provisioned router before saving configuration and credentials.
  • Do not infer 2.5/10GbE from Wi-Fi class names; verify the exact physical ports.
  • Browser Network Information API values are hints and are not a replacement for router/switch counters.

Used-device inspection

What to verify before paying or signing off a repair

  • Verify exact WAN and LAN port speeds
  • Check Wi-Fi generation/bands supported by your actual clients
  • Check mesh/backhaul and VLAN/PoE needs before choosing hardware