Author Topic: Diy micro digital fpv system help needed!  (Read 717 times)

0 Members and 1 Guest are viewing this topic.

Offline StillNotAnEngineerTopic starter

  • Newbie
  • Posts: 1
  • Country: fi
Diy micro digital fpv system help needed!
« on: September 18, 2018, 08:50:12 am »
Hey I need a bit of help in my digital fpv project!

My goal is to make a video link with more range and encryption. Channel jumping for avoiding
interference would also be nice feature. I just don't know which parts I need and how to use
video encoders..

M-JPEG might be good for a fail proof system, but it needs more bandwidth. Maybe multichannel
parallel transmitter would be good?
H264 needs a better connection to work. A 2-way link might be needed to tell the transmitter to lower
quality when going out of range.

Hardware should be less than 10grams and parts under 30$ for the transmitter. Light and cheap
arm SBC with h264 encoding is necessary. If I have understood right, some of them don't have enough
documentation on how to use the encoder engine so I need help to find a chip and documentation for it.

Low part count is ideal for light weight solution. No money for 8 layer pcb and micro quadcopter
should be able to carry it. So integrated ram would be nice.

Potential chips I have found are V3s and AK3918. V3s is used in blueperry pi and lichee pi. Ak3918 in
banana pi d1. Both have features I don't need and are harder to get. I need to design a bit smaller
pcb and add few injection cabable wlan chips. Also code?

Any resources and help are appreciated.
 

Online Marco

  • Super Contributor
  • ***
  • Posts: 6971
  • Country: nl
Re: Diy micro digital fpv system help needed!
« Reply #1 on: September 18, 2018, 03:31:59 pm »
How about NanoPi Neo Air?

With software encoding I think you could do far better than with hardware encoding with a few tweaks, since you have low latency bidirectional communication. With a proper bidirectional protocol you can deal with packetloss far better than standard methods. For instance you can increase FEC depending on packetloss, re-request MBs as long as the display deadline hasn't been reached, without acknowledgement have the encoder not use MBs as a reference etc.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf