Common Issues Quick Reference
This section lists some of the most common faults encountered during daily use of the QE3 Screen Remote Controller, together with their possible causes and recommended quick sol…
3 min read · English documentationThis section lists some of the most common faults encountered during daily use of the QE3 Screen Remote Controller, together with their possible causes and recommended quick solutions, so that frontline staff and users can quickly troubleshoot them.
| Fault Symptom | Possible Cause | Quick Solution |
|---|---|---|
| Cannot power on | The battery is depleted | Connect the charger, wait for a while, and then try powering on again |
| Cannot power on | Device hardware or system fault | Refer to “Detailed Troubleshooting Examples”; if the issue cannot be resolved, contact technical support |
| Powered on but unable to connect to the device/terminal | The device at the other end is not powered on or not ready | Confirm that the unmanned platform / robot terminal is properly powered on and has completed its self-test |
| Powered on but unable to connect to the device/terminal | Pairing or binding has not been completed | Complete the pairing process again by following the steps in “Device Pairing (Reserved)” or the corresponding documentation provided with the device |
| Powered on but unable to connect to the device/terminal | Signal interference or excessive distance | Move away from sources of interference, reduce the distance, and check the antenna connections |
| Data link video feed is not displayed | The data link module/app is not properly connected | Check the connection status of the data link module and app; restart the relevant module if necessary |
| Data link video feed is not displayed | Weak signal or severe obstruction | Move closer to the aircraft or adjust the antenna, and avoid obstructions |
| Screen touch is insensitive or unresponsive | Interference from the screen protector or a screen hardware fault | Check and replace the screen protector; if restarting does not improve the issue, contact ROBOSN technical support |
| Battery runtime is noticeably shorter | Excessive brightness, too many background apps, or low ambient temperature | Reduce the load as appropriate; shorter runtime in low-temperature environments is common, so reduce high-load use or move the device to a room-temperature environment; close unnecessary background apps |
| Battery runtime is noticeably shorter | Natural battery aging | Monitor battery health and arrange a replacement if necessary |
| Charging is slow or does not work | The charger/cable is incompatible or damaged | Preferably use the recommended power adapter and cable; try replacing the cable and charger |
| Charging is slow or does not work | Poor contact or foreign objects in the port | Inspect and clean the Type‑C port, and keep it dry and clean |
| No image during HDMI screen casting | Screen casting or HDMI output is not enabled in the mission app (MacroSilicon USB Display) | First enable screen casting/HDMI output in MacroSilicon USB Display, and then check whether an image appears on the external display |
| No image during HDMI screen casting | The HDMI cable is not fully inserted or the display is not set to the corresponding input | Reconnect the HDMI cable and confirm that the display is set to the correct HDMI input source |
| No image during HDMI screen casting | Incompatible resolution or poor cable quality | Try lowering the output resolution or replacing the cable with a high-quality HDMI 2.0 cable |
| Network connection fails | Incorrect configuration or an IP conflict | Check the network settings and, if necessary, change the static IP address to avoid conflicts |
| Network connection fails | Unstable network environment | Try again in a more stable network environment, preferably using a wired network |
| System is noticeably slow or unresponsive | Excessive system load or insufficient storage space | Restart the device, remove unnecessary apps and data, and reserve sufficient storage space |
| LQ10 stream reception issue | MTU mismatch | Ensure that the camera's MTU setting matches the MTU setting of the data link/data transmission system |
If the quick solutions above do not resolve the issue, refer to the subsequent “Detailed Troubleshooting Examples” for further troubleshooting, or obtain support as described in “Contact Information and After-Sales Service Process.”
