[Vixiom]

hi, have you tried doing the inverse, controlling CC3D with RPi?

I'm not sure about the question ?

You want to have the rpi controlling CC3D for copter movement or for telemetry ? Anyway for both, I didn't do it (may be in the future  ).

[sonium]

Thank you for the link, I already see it before, it look great !

But as I want to be able to have the lightest on-field equipment, and dont bring laptop, raspberry with screen, usb batterie... I don't know if I will use it because it seem to need one raspberry pi to receive video too.

My main goal is to know what the copter is recording, if I'm able to perform it with my android it will be enough.

Anyway I will post future working solution, there's a lot of thing to do !

Just some comments because I had some similar ideas: I found the RPi good for recording/streaming video but too slow on the decoding/display side. I was able to use the faster GPU decoder, but found that it is not as fault-tolerant and therefore does a really crappy job with the wifi transmission.

[Vixiom]

Just some comments because I had some similar ideas: I found the RPi good for recording/streaming video but too slow on the decoding/display side. I was able to use the faster GPU decoder, but found that it is not as fault-tolerant and therefore does a really crappy job with the wifi transmission.

I did some try with an Rpi 3 and camera V1 then now with a rpi zero v1.2 and a V2 camera, for both it seem to work for recording.

But I notice for both some "scratch" on the video maybe due to the high resolution choosed, I will post on youtube my first try soon and perform other try with lower resolution/FPS.

Did you want to use it as FPV ?

[sonium]

Yes, FPV was the idea. I'm getting a latency of about 80ms with a 1296x730 resolution which doesn't make it competitive for racing, but hey - it looks nice.

I use the following pipeline for streaming and simultanous caputure:

raspivid -vf -hf -n --intra 5 --profile baseline -w 1296 -h 730 -b 4500000 -fps 49 -t 0 -o - | tee >(gst-launch-1.0 -v fdsrc !  h264parse ! rtph264pay config-interval=10 pt=96 ! udpsink host=192.168.1.11 port=5000) >(cat > capture.h264) > /dev/null

and display on Mac:
gst-launch-1.0  -v udpsrc port=5000 caps='application/x-rtp, media=(string)video, clock-rate=(int)90000, encoding-name=(string)H264' ! rtph264depay ! avdec_h264 ! videoconvert! video/x-raw,width=800,height=480 ! glimagesink

I think the main part of latency comes from the encoder on the RPi which is not optimized for low latency.

[Vixiom]

I use the following pipeline for streaming and simultanous caputure:

raspivid -vf -hf -n --intra 5 --profile baseline -w 1296 -h 730 -b 4500000 -fps 49 -t 0 -o - | tee >(gst-launch-1.0 -v fdsrc !  h264parse ! rtph264pay config-interval=10 pt=96 ! udpsink host=192.168.1.11 port=5000) >(cat > capture.h264) > /dev/null

and display on Mac:
gst-launch-1.0  -v udpsrc port=5000 caps='application/x-rtp, media=(string)video, clock-rate=(int)90000, encoding-name=(string)H264' ! rtph264depay ! avdec_h264 ! videoconvert! video/x-raw,width=800,height=480 ! glimagesink

Thank you I save it in my drone draft for future development 

Did you send telemetry via this link too ? How many range you reach with this setup ?

[sonium]

I have not tested the range yet, but I'll keep the telemetry on the oplink radio connection which will have the larger range in any case.