Hi @grahammalyon -
That’s looking like you don’t have a USB lowlight camera connected, or at least not a functional one! Could your system be affected by Technical Bulletin 12?
This was suggested to me but I have plugged it into a computer and its working fine I have also tried the other USB ports on the board should I try a clean install on the Pi? If so how would I go about it? Or is there something else I should try first? Many thanks 
Are you using the cable the camera comes with? The Raspberry Pi is quite sensitive to the USB port signal integrity, so extended cables, not using twisted pairs for the data wires, or routing the wires too close to switching power electronics (like ESCs) can cause the camera to fail to be detected.
Hi @grahammalyon -
To have a look at what might be going on, please share a screenshot of the contents of dmesg.
- Go to BlueOS terminal, type
red-pilland press enter - type
dmesgand press enter - Share screenshot (cntrl-cmd-shft-4 on mac copies selected area to clipboard, or use snip on windows)
Do this with the camera already connected - if TB12 or a bad cable applies, you’ll see lots of messages about usb deivce being connected / disconnected, new video devices being created with higher and higher numbers
Yes set up just as it should be
You indeed have a faulty camera. It is connecting and disconnecting intermittently for over-current, probably caused by a short circuit in the camera itself or its cable.
Hi @grahammalyon -
@rafael.lehmkuhl is correct, some aspect of the camera or its cable is causing the device to not stay connected. Please reach out via the help center, report a problem with a product, and include your order number to receive assistance! If your camera is affected by TB12 (determined by order#), a replacement is due.
Terrific thank you I really appreciate your help.
Hello, Mr. Tony White, I encountered these issues while debugging the Blue OS webpage.
1. The parameters on the QGC platform are not mapped to the web interface.
2. The video stream can be viewed on the QGC, but it cannot be seen on the web page (it shows a black screen).
Blue OS is 1.4.2
Cockpit (Desktop version)
Hi @LIUXU -
You should not have the udp prefix in the allowed WebRTC address list - it just needs to be the address of the vehicle (no port either.)
Do you have a broken heart icon in the upper right of BlueOS? You’re saying the parameters don’t load on the autopilot parameters page? Or are you saying QGC does not change the parameters that are viewed in BlueOS?
Updating to the latest stable BlueOS, 1.4.3, may help, as 1.4.2 is very old.
What version of Cockpit are you using? Is a stream preview for your video page found on the video streams page?
Sorry, I didn’t notice the message in time.
Thank you very much. The issue with the video has been resolved.
There is a broken heart icon on the top right corner of BlueOS. Meanwhile, QGC can view the relevant voltage and compass parameters.
Cockpit— Cockpit-win-x64-1.18.2.exe
In the Cockpit section of the webpage, the compass parameters remained unchanged.
@LIUXU just to confirm: the video issue was solved when you removed the udp:// prefix on the IP in the “Allowed WebRTC IPs” field?
Yes,Video recovery after deleting fields.
Hi @LIUXU -
That broken heart indicates that BlueOS is not connected to an autopilot - so no connection is expected in Cockpit. It should also not be connecting in QQGC!
Can you share what autopilot and firmware version you’re trying to use? How is it connected to the Raspberry Pi?
Your video stream seems to be configured for a very low resolution, and does it have vertical noise artifacts like in the preview image you shared?
- The firmware version of the Pix flight controller seems to be 2.0.4, connected to the Raspberry Pi 4B through USB-C.
- But when I was debugging the motor in QGC, I could still see the camera transmitting video footage.
- The video stream should have noise artifacts, but I was not aware of this issue at first. I thought it was a problem with my camera.
Hi @LIUXU -
What flight controller are you using? Note that it needs to be connected to one of the 4 standard USB ports on the Pi, the USB-C connector on the Pi is not for data!
If those video artifacts continue, they are likely an issue with your camera - make sure it is getting a clean 5V!
QGC and Cockpit will show video regardless of the status of the flight controller - the video stream is handled by BlueOS/Pi not ArduSub!
The model of the flight controller is: pixhawk2.4.8 — The firmware version is: ardusub-v2.px4
Currently, all my hardware connections are made according to this diagram.
After updating to the Blue OS 1.4.3 version, the issue “That broken heart indicates that BlueOS is not connected to an autopilot” has been resolved.
At the same time, another problem occurred where videos couldn’t be played.
Now, where should I start to investigate and solve the problem?
Hi @LIUXU -
It looks like you’ve changed or removed your original stream 1 and stream 2. You can either click the edit (pencil) icon and delete them, making your available stream 3 stream 1, OR you can simply change the video widget source to stream 3, under the top level cockpit menu for edit layout.