A player's field test exposes the compliance gray zone in drone video transmission
Key points
- The same drone flies 2-3km at home in China but loses signal within a few hundred meters in Kuala Lumpur
- After a third-party app switches it to FCC mode, it still holds a signal at 2km in obstructed conditions
- Users changing RF settings themselves leaves the compliance line unclear
Today's main thread: one player's field test raises two issues — video transmission and compliance
Today the low-altitude sector has only one verifiable public lead, a user share on V2EX. The poster says his lito x1 drone, bought during the summer break, can fly 2-3km from his own rooftop in China; taken to Kuala Lumpur, it lost signal after a few hundred meters with no obstruction, for unknown reasons. He then downloaded a third-party app called redfly that he had seen on a short-video platform. After enabling "Australia FCC" mode, the spot where it had lost signal at a few hundred meters showed near-full bars, and it still held a signal at 2km behind a high-rise with obstruction. (Source: V2EX)
This is a personal experience post, not a product review, and it includes no instrument measurements. But it points to two things at once: consumer drone video transmission is strongly tied to regional RF settings, and users switching power modes themselves have already stepped onto the edge of local radio management rules.
Transmission range: the same machine, clearly different performance in two places
According to the poster, the same lito x1 reaches 2-3km from a rooftop in China but only a few hundred meters with no obstruction in Kuala Lumpur. He himself could not explain why, saying only that he was "not sure of the reason." (Source: V2EX)
It should be noted that this kind of comparison lacks records of flight altitude, antenna orientation, ambient noise and co-channel interference, so it cannot be directly attributed to a device defect or a regional difference. The judgment that later evidence could overturn is this: the rated video transmission range of consumer drones is often hard to reproduce in dense urban areas, and the urban RF environment and regional power limits are the two variables more worth watching.
Third-party app and FCC mode: clear effect, doubtful compliance
The redfly app used by the poster is a third-party app, and its effect comes from switching the RF configuration to "Australia FCC" mode. After the switch, the spot that had lost signal at a few hundred meters showed near-full bars, and it still held a signal at 2km in obstructed conditions. (Source: V2EX)
The problem is that regional limits on radio transmission power are set by local regulatory rules. When users rewrite the configuration through a third-party tool, they are bypassing the compliance settings the device shipped with. The post does not say whether this mode is legal in Malaysia, nor whether it affects the device warranty or flight safety. For ordinary users, "the signal got better" and "you can use it this way" are two different things.
Practical reminder: when carrying a drone across borders, first confirm local requirements for frequency bands and transmission power, then judge whether the video transmission range is "abnormal"; the risk of third-party RF configuration changes falls on the user.
The value and limits of this lead
As the only usable lead today, its value lies in putting two issues usually discussed separately — "video transmission range" and "RF compliance" — into the same scenario. Its limits are also obvious: a single user, a single model, no controlled measurements, so the conclusion can only serve as a starting point for observation. If a manufacturer later explains regional versions, or a regulator takes a clear position on third-party frequency changes, today's judgment can be revised. (Source: V2EX)