On this page
Camera Not Showing
Standing at the aircraft with a camera that isn't publishing, there are three things you can actually do: reseat a cable, power-cycle the camera, or fix an address. The camera's page under Settings → Device → Cameras tells you which one to try rather than leaving you to guess, and names the address it is trying.
What the message means
| The page says | What that means | What to do |
|---|---|---|
| Nothing is plugged into the camera port | The camera port has no link at all. | Reseat the cable, or power the camera. Nothing about addresses matters until this is fixed. |
| No wired port on this device has a cable in | None of the drone’s Ethernet ports has a link. | Plug in the camera’s Ethernet cable, and its USB adapter if it uses one, and check the camera has power. |
| On a network this device has no address on | The camera is on a different subnet from every address the drone has. | Press the button under the message, which names the port. It gives that port an address on the camera’s network. |
| The cable is live but the camera is not answering | The network is fine, but nothing replies at that address. | The camera is powered off, or it lives at a different address. Press Scan for it. |
| Power-cycle the camera | The cable is live, but nothing at all arrives from the camera. | It hung or lost power. Pull its power. Its address is fine, so changing settings will not bring it back. |
| Likely changed address | Something is plugged in, but nothing answers at the configured address. | The camera moved, usually after taking a new address from a router. Press Scan for it. |
| Refuses the connection | The camera is up, but its RTSP port is closed. | The port in the address is wrong, or the camera is still booting. Press Change the port, or give it a minute. |
| Answers but sends no video | The camera accepts the connection, but no picture arrives. | The RTSP path or sign-in is wrong. Press Change the path or sign-in, or switch the transport to TCP. |
| No video from the Raspberry Pi camera | The ribbon-cable camera is not delivering frames. | Seat the ribbon the right way round at both ends, then reboot so the camera is detected. |
Check the address first
Fault messages name the address the drone is trying and, when it knows them, the port the camera is wired to and when it last sent video. A good share of camera problems are a drone looking confidently at the wrong place, so read that line before changing anything: if it isn't the address in your camera's own app, the fault is your configuration and not the camera.
When the camera moved
A camera that took a new address from a router gets the “likely changed address” message, and Scan for it under the message is the fix. It opens the camera wizard and searches RTSP ports 554 and 8554 on every network the drone can reach, then asks over ARP, so it finds cameras that have moved back onto the subnet they shipped with.
If the camera genuinely lives somewhere the scan can't reach, open I know my camera's address and type its Camera RTSP URL. It is in the camera's own app or manual, and on the Tested Cameras page for the models we have checked.
Flash your card in about 5 minutes
The Aircast Flasher downloads the image, sets Wi-Fi and hostname, and verifies the card.
On This Page