Most TD-F10 faults are not solved by replacing the panel first. Start by separating four boundaries: power, local wiring, network access and device compatibility. That sequence prevents a project team from treating an installation problem as a software problem—or promising compatibility that was never tested.
1. Freeze the project facts before changing hardware
Record the panel model, hardware revision, firmware, installation room, power source, network path and the exact devices that should be controlled. Include the device model and firmware, not only “Zigbee” or “wireless”.
| Check | Record | Why it matters |
|---|---|---|
| Panel | Model, revision and firmware | Different revisions can expose different functions or recovery steps. |
| Device list | Model, device type, functions and firmware | A radio protocol label alone does not prove that the required function is supported. |
| Room conditions | Wall material, metalwork, heat and ventilation | Physical conditions can create intermittent touch, radio or display faults. |
| Network owner | Wi-Fi or Ethernet path, addressing policy and responsible party | It clarifies who can diagnose an offline panel after handover. |
2. When the panel is powered but offline
- Confirm supply voltage, terminal polarity and protection against the approved drawing.
- Check whether the panel received an address and whether the project network allows the required outbound connection.
- Test the same network path with an approved known-good unit, if available.
- Record firmware and the failure time before resetting anything.
- Only then re-provision the panel or replace the network component.
An offline status does not identify the cause by itself. It can be power quality, addressing, network policy, account ownership or a failed provisioning step.
3. When the screen is black, flickers or touch freezes
Determine whether the panel is fully unpowered or only failing to render. Check the power indicator, touch response, relay operation and connected audio output. If the panel is hot, verify ventilation and mounting depth before repeated restarts.
- Inspect the supply at the panel under load.
- Check that the installation box does not press against the rear housing or wiring.
- Confirm the panel is not enclosed beside a heat source or sealed without airflow.
- Capture the failure state and firmware before a factory reset.
- Use the approved recovery procedure; do not erase project ownership without a handover record.
4. When a device cannot be added or controlled
Do not call the issue “not compatible” until the exact device profile has been checked. Confirm device type, supported functions, firmware, pairing method, radio conditions and project account. Test one device in a representative room before scaling the same combination.
5. Questions to settle before an RFQ or pilot
| Project question | Evidence to request |
|---|---|
| How many devices must the panel connect? | Device register with room quantity and control relationships. |
| Is local relay control required? | Approved wiring diagram, channel assignment and project load limits. |
| Is PoE required? | Written confirmation of the supported power method for the selected hardware revision. |
| What installation box and supply are available? | Cut-out, mounting depth, supply specification and service-access photos. |
| What audio output is needed? | Speaker rating, location and acceptance test. |
6. Handover checklist for distributors and property teams
- As-built panel and device inventory, including room and firmware.
- Network and account ownership record.
- Power, mounting and ventilation checks.
- Tests for onboarding, command, state refresh, restart and offline recovery.
- Open compatibility items, exclusions and the process for adding a new device.
- Support route and minimum evidence required for diagnosis.
For a multi-unit project, repeat the agreed checks by apartment type and record exceptions. A clear exclusion is safer than an implied promise that every device or installation condition will behave identically.
This article consolidates recurring distributor and project-support questions into a field checklist. Product-specific electrical limits, supported device profiles and installation requirements must be confirmed against the approved TD-F10 technical documentation for the shipping revision.
7. Fault boundaries at a glance
8. Case record for support escalation
| Field | Example of what to record |
|---|---|
| Panel identity | Model, hardware revision, firmware and serial or batch. |
| Location | Apartment type, room, wall material, mounting depth and ventilation. |
| Power | Supply specification and the voltage measured at the panel under load. |
| Network | Wi-Fi or Ethernet path, addressing, network owner and account owner. |
| Device involved | Model, type, function, firmware and the room it sits in. |
| Symptom and time | What was observed, when it started and what changed before it. |
| Actions taken | Checks run, in order, and whether a reset or re-provision was performed. |
Escalate to the supplier only when the power, wiring and network boundaries are closed, and include this record with the request. For project-level commissioning of the same panel, see the MDU commissioning checklist, and for how panels sit alongside intercom and locks, see the video intercom and smart lock integration guide.
Frequently asked questions
What should I check first when a TD-F10 panel is offline?
Confirm supply voltage, polarity and protection against the approved drawing, then check addressing and whether the network allows the required connection. Record firmware and the failure time before resetting anything.
Should I replace the panel when the screen is black or touch freezes?
Not first. Determine whether it is unpowered or only failing to render, inspect the supply under load, mounting depth and ventilation, and capture the failure state before a reset. Use the approved recovery procedure.
Why can a Zigbee device fail to pair with the panel?
“Zigbee compatible” is only a starting condition. Confirm the device type, supported functions, firmware, pairing method, radio conditions and project account, and test one device in a representative room first.
Is a device “not compatible” if it fails to onboard?
Do not conclude that until the exact device profile has been checked. The committed scope should name tested device models, functions, firmware and pass criteria for onboarding, command, returned state and recovery.
What does an offline status tell me?
Not the cause. It can be power quality, addressing, network policy, account ownership or a failed provisioning step, so check each boundary in order.
Where do I find electrical limits and supported device profiles?
In the approved TD-F10 technical documentation for the shipping hardware revision. This article is a field checklist, and product-specific limits must be confirmed against that documentation.
Turn the guide into a project brief
Share the selected model, site conditions, interfaces and destination market so the next review stays within a written scope.
Request a project reviewEditorial review: Updated 25 October 2026 for search intent, scope and project usefulness.