This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
premade images #8
Comments
|
I don't have any SD images now, because there are a lot of possible configurations that I'll need to support. For quick start you can use image from https://github.com/bortek/EZ-WifiBroadcast/wiki. On raspberry pi run:To start capture RTP stream from raspberry pi camera run: To broadcast RTP stream: On your host machine run:To receive RTP stream: To play RTP stream: |
|
Would this be a good use for docker? |
|
@dagar |
|
You might want to try semaphoreci for docker builds. I believe it will take care of your authentication with docker hub outside of the repo. |
|
Prebuilt binaries for raspberry pi: |
|
Hi, I want to test your version of wifibroadcast with low latency. < For quick start you can use image from https://github.com/bortek/EZ-WifiBroadcast/wiki. But I don't know what to do with your prebuilt binaries. I can't find where to replace them in borteks image ! I need a little help, please ... ps : have you ever think of sharing your code with bortek ? Perhaps he could include it for next updates. (I'm sad when I see people working each on its own side ...) |
|
You can only get modified kernel (from /boot) from these images. And use clear image with this kernel and wifibroadcast binaries. Prebuild wifibroadcast binaries for raspberry pi are in "Releases" section. Or you can build it manually if you have linux with docker installed. Run |
|
I tested my setup but on the groundstation I get the error: erroneus pipline: no element "avdec_h264" after trying to play the RTP stream. Another problem is that it says "unable to decode package #xxxxxx" |
|
What is your pipeline? |
|
I have did it like here: https://dev.px4.io/en/qgc/video_streaming_wifi_broadcast.html |
|
|
Okay after installing gstreamer1-libav it works to decode the video but.. I can see only 1/4 of the screen the remaining screen is green. What I can see is blurred and it updates very slow every 2 secounds. On the terminal i can see that it looses a lot of packages but it detected a session then i get a lot of unable to decrypt.. |
|
1142666 PKT 0:0:0:0:0:0 |
|
Do you have patched kernel (rtl2800 driver) on TX side?
to /etc/NetworkManager/NetworkManager.conf |
|
why dont you just make a image that can be put straight onto a sd card rather than making people deal with all these patches. |
|
Becase there are a lot of different hardware with multiple linux distributions on it. I use NanoPI NEO2 and have patch for its latest kernel (attached to message above) |
|
yes but few people are going to be running a configuration like that, even if its just compatible with raspberry pi boards it would cover 90%+ of people wanting to try your version of wifibroadcast. |
|
I can understand that he does not want to create an image for a raspberry pi as you can use ez-wifibroadcast. Furthermore using a raspberry pi has a lot disadvantages, due to the fact that the RaspPi is heavy, huge and expensive for it's performance. |
|
but are you not still needing to use a pi to encode the video? |
|
I use pi zero only as video encoder and link it with neo2 via usbnet. |
|
whats the advantage to doing it like that if the pi can do everything anyway. |
|
|
Three independent usb busses can connect wifi card, LTE modem and pi zero (via usb net) without any external usb hub and provide fair 480mbit/s for every usb channel. |
|
why cant the video encoding be done on the neo2? |
|
|
Okay finally it works even without kernel patches. |
|
So, what's the working process in case I have two RPIs and using PiCamera, and have 18.12.1 image downloaded.
|
|
|
Cool. |
|
It run in background by default as systemd service (wifibroadcast@drone or wifibroadcast@gs) |
|
It's really the correct software I'm looking for. Will try it soon. |
|
Hi @svpcom , maybe it´s interesting to take a look at https://github.com/HD-Fpv/Open.HD_Image_Builder . That´s a collecting of scripts which create a fresh Open.HD image. |
|
I know about OpenHD, but it just a collection of bad-structured shell scripts around RPI+pi camera only. The problem of most security ip-cameras is a high latency (it can be up to several seconds). For FPV you need machine-vision cameras. |
|
Well, even if the Image builder is not structured to the highest level it is at least working. Maybe you could create some structured shell scripts? I like your solution, but takes quite some steps to get it running. Just for my understanding: Which component inside an IP camera takes that long (encoder, network etc...)? |
|
@Seeelefant I prefer to follow classic UNIX way - make small services but not monolithic system. WFB can be build by Most of security cameras are proprietary SoC, so even if you know what part is bad you unable to fix it. They don't have any public docs, so I don't want to invest my time to hacking device which can be EOL on the next year. |
|
Hi to all, I'm now able to build an image which should work on both drone and gs side with a few modifications on each side. My setup :
Both Pis are ethernet connected with my desktop, and I can ssh to them. The 2 Pis are booting perfectly, and the 2 wifi boards are up and in monitor mode. But using "wfb-cli gs" on the gs Pi, I can see that all 3 connections failed (refused by the other side) So if someone has time to read my guide and find what is wrong or missing, I will share my image as soon as it will work. Thanks for your help !! |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
could you provide some pre made SD images to make trying your system easer?
The text was updated successfully, but these errors were encountered: