FPVLAB

image
Page 1 of 3 123 LastLast
Results 1 to 10 of 24

Thread: EZ-WifiBroadcast, cheap digital HD transmission made easy!

  1. #1
    Navigator
    Join Date
    Dec 2014
    Posts
    96

    EZ-WifiBroadcast, cheap digital HD transmission made easy!

    Well, the headline already says it, Wifibroadcast made easy.


    The goal of this project is to make the usage of Befinitiv's Wifibroadcast (https://befinitiv.wordpress.com/wifi...ve-video-data/) easy for people who would be otherwise drawn away because it can become quite time consuming and frustrating setting everything up if you're not used to tinkering with linux.
    You just need to download the SD card image, put it on two SD cards, switch everything on and 15 seconds later you have a live HD picture.

    *** Always check the Github page https://github.com/bortek/EZ-WifiBroadcast for latest infos and instructions, this post may be outdated ***


    Features:
    ---------
    - Supports Pi1B+, Pi2B+, Pi3B+, Pi Zero, Odroid-W, Pi V1 and V2 cam (RX Pi needs to be atleast a Pi2)
    - max. possible resolutions (depending on cam used):
    1280x720p 60fps
    1296x972p 42fps
    1640x922p 40fps
    1920x1080p 30fps
    - max. possible video bitrate about 12Mbit
    - Latency ~140ms with 720p 48fps default settings, minimum possible latency roughly around 110ms
    - Support for 2.3/2.4/2.5Ghz bands and 5.2Ghz to 5.8Ghz bands
    - 2.4Ghz on 3dbi linear omni antennas: ~1km stable range with ~70mw wifi sticks, ~2km stable range with ~300mW high-power cards
    - 5Ghz on 3dbi linear omni antennas: ~250m stable range with 25mW wifi sticks, ~1km stable range with ~300mW high-power cards
    - Configuration can be done from Windows, no Linux knowledge required
    - Supports different configuration profiles selectable on the field via jumpers or DIP switches
    - Forwarding of video stream and telemetry data to 2nd display via: USB Tethering, Wifi Hotspot, Ethernet, Wifibroadcast relay mode
    - Fully dynamic and automatic detection of 2nd display, just plug it in or connect via Hotspot and it'll work
    - 2 wifi sticks transmit diversity on two different frequencies supported for bulletproof video link
    - 3 wifi sticks receive diversity support for Atheros, 5 wifi sticks receive diversity support for Ralink
    - Integrated OSD with support for Mavlink (not bi-directional), Frsky, LTM, NMEA GPS
    - .AVI Ground recording and .PNG screenshots automatically saved to USB stick
    - Quick startup, about 10 seconds until video is shown
    - No issues as with standard wifi, no disconnection, video freeze etc.
    - Graceful handling of signal degradation, no sudden loss of video
    - Live and responsive RSSI display with defective blocks and packetloss display
    - Handling similar to analog gear, just switch on and fly
    - Smooth and stutter-free video (thanks, mmormota)
    - Video reception is very stable even in difficult multipathing environments, no constant glitching like with analog
    - No expensive and large circular antennas required
    - OSD overlay rendered on the receiver will stay clear and functional even if video is too bad to fly
    - SD card reliability and general robustness tweaks (read-only filesystem, syslogging to SD disabled, etc.)
    - Debug logs and screenshot will be saved to sdcard in case of errors
    - RC over wifibroadcast via Joystick (not much tested yet)



    Wifi Cards:
    --------------
    You have a lot of choice. All wifi cards with one of the following chipsets should work:

    Atheros AR9271
    Atheros AR9280
    Atheros AR9287

    Ralink RT2070
    Ralink RT2770
    Ralink RT2870
    Ralink RT3070
    Ralink RT3071
    Ralink RT3072
    Ralink RT3370
    Ralink RT3572
    Ralink RT5370
    Ralink RT5372
    Ralink RT5572


    However, there might be whatever small issues that prevent those cards from working, so if you want to play it safe, choose one of the cards that have been tested by different people and definitely work:

    - CSL 300Mbit Stick (2.4/5Ghz, Diversity, RT5572 chipset)
    - Alfa AWUS036NHA (2.3/2.4Ghz, high power, Atheros AR9271 chipset)
    - TPLink TL-WN722N (2.3/2.4Ghz, Atheros AR9271 chipset)
    - Alfa AWUS051NH (2.4Ghz/5Ghz, high power, Ralink RT3572 chipset)
    - Alfa AWUS052NH (2.4Ghz/5Ghz, Diversity, high power, RT3572 chipset)

    On the other hand, if everybody gets the same cards, we'll never find out which other ones work. There are also very small and lightweight RT5370 cards available in china shops for under 4$. Aliexpress for example has a lot of cheap wifi cards in general. It would be nice if you report back your findings in case you tried a wifi card that is not listed here.


    Installation / Setup
    --------------------
    - Download the image and unzip it
    - Write it to two (minimum 2GB) SD Cards using Win32DiskImager or any other SD image write tool
    - That's it



    Configuration
    ------------------
    - Put SD Card in Windows computer or anything that has a text editor (Tablet, Smartphone) and edit wifibroadcast.txt
    - For first tests, leave default settings, only change frequency!



    Ground Recording
    -----------------------
    - Fly
    - Plug-in USB memory stick after flight - recorded video will be shown and video/screenshots/telemetry will be saved
    - Video recording time is limited to around 13mins with ramdisk temporary video storage. Longer recording times are possible with sdcard temporary storage, but this can currently cause video stuttering. Use a fast sdcard.


    Video display on android device via USB tethering
    -----------------------------------------------------------------
    - Download and install FPV_VR on your android device (link below)
    - connect android device via USB and set to to USB Tethering mode


    Video display on android device via Wifi Hotspot
    -----------------------------------------------------------------
    - Download and install FPV_VR on your android device (link below)
    - Enable WIFI_HOTSPOT in wifibroadcast config file
    - Change channel and SSID/password in apconfig.txt
    - connect to Wifi network name "EZ-Wifibroadcast" password "wifibroadcast"
    - Make sure Wifi Hotspot frequency is atleast 120Mhz far away from Wifibroadcast frequency


    Important:
    ---------------
    Although ofcourse nothing is perfect, version 1.4 has been extensively tested with all kinds of different hardware combinations and has been left running for days without any issues. Considering that the hardware and software is exactly the same, if there are issues, it's likely these are cause by some setup problem. Generally, if you experience an issue, always re-test with default settings to see if a configuration change caused it.

    If you experience any stability issues, dropouts or constant glitching, its likely that the reason is an unstable power supply or otherwise bad wiring or configuration. It's crucial for stable operation that the power supply is good and that there are no intermittent connections. 99% of problems reported are caused by a bad power supply and/or bad wiring.

    - Many (even expensive brandname) USB power supplies or portable power banks either don't deliver the advertised amps and/or don't maintain stable 5Volts.
    - The same applies for USB cables and connectors. Many connectors have bad tolerances (too thin, which makes them wiggle and prone to intermittent connections) and cables use 28AWG or even less which causes too much voltage drop, even on short 30cm cables.

    - Make sure that you supply the Pi with stable 5V. Use atleast a 2A BEC and short wires with atleast 20AWG (0.5mm˛).
    - Power the Pi through the GPIO Pins, not through the micro USB Port. Do not use USB cables and connectors, solder everything directly or use proper connectors like e.g. XH balancer connectors or similar.
    - Do not power high-output cards like the AWUS036NHA or AWUS051/052NH through the USB ports of the Pi, connect them directly to the BEC.
    - Consider adding a low-ESR electrolytic capacitor near to the Pi and high-output card to stabilize the power. If you have a high-power motor setup (race-quad for example), also consider adding low-ESR caps near to the ESCs or at the central PDB to make sure the BEC gets clean power.

    - Make sure the camera flat cable is properly inserted and fixed. Consider adding a drop of hotglue or tape to secure it.

    - Make sure the Pi do doesn't get too hot. If it reaches 80 degrees C, it will reduce CPU speed to prevent it from overheating. This will make the video stream stall/stutter or cause the video stream to be delayed several seconds! Consider adding a small heatsink if using it in an enclosed/bad ventilated setup.

    - Make sure the wifi cards don't get too hot. This will cause badblocks and/or the power output will be reduced significantly.

    - Keep some distance to components that carry high currents and emit electromagnetic fields like motors, ESCs, power wires etc.



    Dowloadlinks:

    V1.6RC3:
    on Freehoster (beware of ads): https://www.file-upload.net/en/downl....6RC3.zip.html

    V1.6RC2:
    on Google drive: https://drive.google.com/uc?id=0B8ke...xport=download

    V1.6RC1:
    on Freehoster: https://en.file-upload.net/download-...16rc1.zip.html

    V1.5
    on Google drive: https://drive.google.com/uc?id=0B8ke...xport=download

    V1.4
    on number3's Google drive:https://drive.google.com/open?id=0Bx...k9mLWR1b0JENDg
    on free file hoster: http://www.file-upload.net/download-...t-1.4.zip.html

    V1.3 beta
    on Bortek's Google drive: https://docs.google.com/uc?id=0B8ke2...xport=download
    on free file hoster: http://en.file-upload.net/download-1...3beta.zip.html

    V1.2:
    http://en.file-upload.net/download-1...t-1.2.zip.html

    V1.0:
    http://en.file-upload.net/download-1...t-1.0.zip.html

    (Sorry for the crappy filehosters, couldn't find anything better quickly. Consider
    using an adblocker like "uBlock Origin").


    EZ-Wifibroadcast Wiki with download links: https://github.com/bortek/EZ-WifiBroadcast/wiki
    EZ-Wifibroadcast Main Page: https://github.com/bortek/EZ-WifiBroadcast


    FPV_VR (Viewer for android devices connected to Pi via USB tethering made by Consti):
    https://play.google.com/store/apps/d....wilson.FPV_VR
    https://github.com/Consti10/myMediaCodecPlayer-for-FPV
    http://fpv-community.de/showthread.p...ast-OpenSource (german)



    Edit 2017-12-27: EZ-Wifibroadcast 1.6RC3 has been released.

    Changelog:
    - New feature: RSSI/packetloss graphing and logging
    - New feature: integrated airodump-ng wifi scanner
    - Increased wifibroadcast-1.txt GPIO config combinations from 8 to 16
    - Reverted back to stty serialport initialisation to fix issue with heartbeats getting lost
    - Rewritten telemetry rx: Should fix out-of-order delivery and packetloss for telemetry
    - Changed manual bitrate setting to kbit/s instead of bit/s
    - Measured bitrate display in video stream can be disabled in wifibroadcast-1.txt
    - Added debug option to wifibroadcast-1.txt
    - Removed confusing bitrate display during startup on RX
    - Changed txpower for Atheros back to 58 (was 56 accidentally in 1.6RC1 and RC2)
    - Changed Atheros Thresh62 parameter to 26
    - Added configurable mavlink forwarder: cmavnode or mavlink-routerd
    - cmavnode.conf moved to boot partition for easier access
    - Display error message in case of syntax errors in osdconfig.txt
    - Added various USB webcam drivers to the kernel (for experimenting)
    - raspivid default intrarefresh changed to "-if both"



    Edit: EZ-Wifibroadcast 1.6RC2 has been released.

    Changelog:
    - telemetry downlink fixes
    - replaced cmavnode with mavlink-routerd (supports UDP and TCP)
    - more debug logging
    - Version on boot-up and in readme.txt updated to reflect rc status


    Edit: EZ-Wifibroadcast 1.6RC1 has been released.

    Changelog:
    -Kernel, Pi firmware and Pi userland updated (Kernel 4.9.35, Raspbian 2017-07-05, Pi0W should work out-of-the-box)
    -Latency lowered slightly (Kernel 4.9.35 improves scheduling and jitter, wbc rx -d 1 works again)
    -Mavlink R/C support (thanks dino_de!)
    -Graupner/JR SUMD R/C support
    -Flysky IBUS R/C support
    -Multiplex SRXL / XBUS Mode B R/C support
    -Support for RTL8192CU cards added (only RX, not tested, for experimenting)
    -Support for RTL8812AU cards added (only RX, not tested, for experimenting)
    -Bitrate measuring on TX, simplifies FEC and bitrate settings, allows for higher bitrates
    -Bitrate display on RX, shows bitrate set on TX as well as live received bitrate on RX
    -New downlink and Uplink tx/rx should improve telemetry down- and uplink considerably
    -Frame header format optimized for minimum overhead (makes the frame format incompatible with v1.5)
    -OSD renders only (and instantly) when receiving attitude frames, artificial horizon is smoother and causes less CPU/GPU load
    -More efficient tx_rawsock using raw sockets instead of libpcap injection, higher bitrates possible with Pi0/1
    -CPU clock lowered to 900Mhz and overvoltage lowered to "3" for less heat and power consumption
    -Atheros short preamble mode: Improves CTS protection and R/C link, allows to use 11 Mbit datarate "long-range" mode
    -Atheros medium access parameter THRESH62 lowered from 28 to 24: should improves R/C link
    -Atheros medium access parameters SIFS, AIFS, CWMIN, CWMAX, etc. are configurable now
    -Increased max. framesize, Atheros wbc payload 1550 bytes, Ralink wbc payload 2278 bytes
    -Support for 802.11b 11mbit and 5.5mbit modes added (lower quality/higher range)
    -Support for CDC ACM added (for Pixhawk USB port)
    -Support for BCM2385 I2C and Toshiba TC358743 added (not tested, for B101 experimenting)
    -Made video UDP port configurable (for Missionplanner)
    -Cosmetic fix: cat write error message removed when ramdisk full
    -Cosmetic fix: socat init messages removed
    -Cosmetic fix: German "O" for "Ost" in OSD compass changed to english "E" for "East"
    -Cosmetic fix: OSD RC_RSSI option re-named to WBC_RC_RSSI
    -Bug fix: Serial telemetry data corruption due to wrong stty settings
    -Bug fix: Pi1A+ turned out not to be 100% stable at 1000MHz CPU clock
    -Bug fix: serial port (for telemetry) did not work on the new Pi0W

    Edit: EZ-Wifibroadcast Version 1.5 has been released

    Changelog:
    - New feature: Bi-directional Mavlink telemetry support (both over wbc and external devices e.g. 3DR dongles or LRS with telemetry) (untested!)
    - New feature: Telemetry output on Rx Pi serialport for antenna tracker etc.
    - New feature: RSSI forwarding to FP_VR android app
    - New feature: RTP video stream forwarding to allow video display in Tower app and QGroundControl app
    - New feature: R/C RSSI and lost packets display added to OSD
    - New feature: CTS protection mode (only for Atheros), improves link quality in environments with wifi interference
    - New feature: Telemetry logging to textfile for later review and debugging
    - New feature: OSD text size can be scaled now, outlines can be disabled for better readability on low-res displays
    - New feature: OSD: GPS/Baro altitude and groundspeed/airspeed can be configured (untested!)
    - New feature: Transmit power for Atheros cards can be set in /etc/modprobe.d/ath9k_hw.conf now (thanks to eosbandi)
    - Bugfix: Typo in OSD frsky telemetry parser
    - Bugfix: Wifihotspot would not work when USB memory stick plugged during boot-up
    - Bugfix: Wifihotspot 2.4GHz Channels 12 and 13 did not work
    - Cleaned up OSD/telemetry configuration, no more configuring blocksize etc.
    - Uplink, dual tx mode and R/C link functionality re-written and improved (untested!)
    - Configuration file clean-up, less options, easier to configure
    - Wifi medium access timing changed (less agressive, may behave better in environments with wifi interference, untested though)


    Edit: EZ-Wifibroadcast Version 1.4 has been released

    Changelog:
    - Display of good/lost packets to OSD for easier identification of interference
    - dbm display now grows/shrinks depending on signal strength
    - Default wifi bitrate reduced to 18mbit for ~3db higher sensitivity
    - Default video bitrate increased to 6Mbit for higher video quality
    - Default transmit power for Ralink cards is increased by 1db because of 18mbit wifi bitrate
    - added 802.11n and 802.11b bitrates for Atheros cards
    - Selectable configuration profiles via GPIO jumpers/switches
    - lots of changes to the scripts to allow for fully automatic and dynamic detection of secondary display devices
    - Forwarding of video stream and telemetry data to 2nd display via: USB Tethering, Wifi Hotspot, Ethernet, Wifibroadcast relay mode
    - Bugfix: Some USB memory sticks were not correctly detected
    - Bugfix: Video is now saved with correct fps if not using 48fps default setting
    - Bugfix: With two or three Atheros cards, one wouldn't come up or receive no packets sometimes, should work stable now for up to three cards
    - Bugfix: Ralink drivers caused a badblock every 10-20 seconds with Alfa AWUS051NH/052NH and other RT3572 based cards
    - Disabled LED blinking on Atheros cards to avoid potential stability issues
    - Raspberry Firmware upgraded to latest Raspbian release version
    - RX overtemperature and undervoltage are now displayed with meaningful symbols
    - Debug logs and screenshot will be saved to sdcard in case of errors
    - Long recording times possible again. Use with caution, may lead to video stuttering or freeze!
    - Recorded video will be played back while saving to USB
    - Cosmetic fixes and quiet mode


    Edit: EZ-Wifibroadcast Version 1.3 beta has been released

    It's still beta and not 100% finished, but I decided to release it now because testing of all the new functionality etc. would take too much time for me alone.

    Changelog:
    - Startup scripts completely rewritten. They run on TTY1-TTY10 now and show if transmission/reception of video and telemetry is running, status info on wifi cards, memory sticks and android device, etc. etc. (not perfect yet, but should work)
    - 2.5-2.7Ghz support for Atheros cards (Untested. Check which frequencies are allowed in your country and use some common-sense!)
    - New raspberry firmware which fixes OSD freeze-up
    - support for 2 TX cards for bullet-proof video link (tested, but needs more testing)
    - Included mmormota's stutter-free hello_video.bin versions (seems to work great, the -sleep versions need testing though)
    - USB tethering supported for display on android device (untested, but should work)
    - Made Rangarid's OSD configurable (see osdconfig.txt)
    - Added support for receiving telemetry data on RX serial port (for people with UHF telemetry transmission for example)
    - Added support for serial data uplink (untested, may need manual fixing)
    - Added support for RC over wifibroadcast via Joystick (tested, but needs more testing)
    - Added screenshot support on RX
    - Added dbm and packet/block display for video and telemetry data streams to OSD
    - Re-written USB memory stick logic completely to fix stuttering issue when recording:
    Video/Screenshots/Telemetry will now be saved to USB stick by simply plugging in the
    memory stick _after_ flight
    - OSD can be made translucent
    - OSD update interval configurable
    - Linux timer frequency increased to 1000Hz for less jitter and less badblocks in cases when one adapter has bad reception
    - Fixed DNS resolv.conf not being updated by dhcp
    - Login cleaned-up, no need to cancel stuff running on the console etc.
    - Give error message and refuse to run when unsupported frequency is configured instead of silently falling back to the
    lowest supported channel (to make sure users don't accidently use an undesired frequency)
    - Check_alive function added which automatically restarts hello_video.bin in case it should crash


    Edit: EZ-Wifibroadcast Version 1.2 has been released.

    Changes from version 1.0 to 1.2:

    - Befi's and Rangarid's OSD integrated
    - Raspbian Update to Kernel 4.11 and latest Raspberry Firmware / Userland (Pi Zero/V2 Cam)
    - Display of configured Frequency and FEC-Parameters at the bottom of the screen
    - Ralink: Different bitrates for video and telemetry possible
    - Ralink: Wifi bitrate can be configured via wifibroadcast.txt
    - Atheros: Wifi bitrate can be configured via module parameter
    - Ralink: TXPower can be configured via module parameter
    - Supports V2 Cam 1280x720 up to 75fps, 1640x922 up to 48fps
    - AIFS/Backoff parameters tweaked, Atheros chipsets now give about 10-15% more throughput, Ralink about 3%
    - Atheros LED behaviour tweaked, blinks faster now, is "more sensitive"
    - CPU/GPU/RAM overclocked and force_turbo activated for less/more stable Latency and higher possible bitrate on Pi1/Zero
    - USB Ethernet Tethering support activated in Kernel (for smartphones)
    - DHCP enabled on Ethernet interfac (system will contact the DHCP server with "wifibroadcast-tx" or "wifibroadcast-rx" hostname)
    - Bash-prompt shows ro/rw status of the filesystem, macros ("rw","ro") added for quick switching
    - Reduced TXPower for Atheros chipsets slightly (just to be on the safe side)
    - Reduced TXPower for Ralink chipsets to default level
    - Patched Atheros Firmware for additional Atheros Chipsets (AR9287, e.g. TPLink 822N V2)
    - TX shows some status infos after startup
    - video.c changed to 240fps for less latency/jitter
    - addedd fflush to rx prozess (just to make sure ...)
    - disabled Systemd journal daemon (used up CPU ...)
    - Kept software, tools and libs etc. in the image, should make modifying or adding own features to the image easier
    - Support for two TX wifi dongles. Experimental right now, not in the config file, has to be configured manually in Linux

    Bugfixes:
    - Potential rapidly raising latency, stuttering image on Pi1/Zero in some cases: overclocked CPU/GPU/RAM, force_turbo=1, enabled performance governoer, reduced bitrate to 4.5Mbit, video.c patched to 240fps, added fflush in RX process, removed systemd-journald

    - AWUSH051NH and 052NH did not work cleanly as TX on 5Ghz band: Reduced TXPower for Ralink chipsets



    Tested wifi dongles:
    AWUS036NH, AWUS036NHA, AWUS051NH, TL-WN722N, TL-WN822N V2, CSL 300Mbit stick

    (My favourites for 2.4Ghz are TL-WN722N and AWUS036NHA at the moment, for 5Ghz the AWUS051NH. The more I test with the CSL 300Mbit dongles, the less I like them, not much TXPower, unclean signal when TXPower raised, they seem to have problems with high power TX cards when used as an RX card (bad blocks when being to near) and somehow there seem to be more badblocks compared to the 722N when used on a wifi channel with other wifi networks.)


    Tested Raspberry Hardware:
    Pi 1 B+, Pi2 B+, Pi3 B+, Pi Zero 1.3, Odroid-W
    official Pi V1 Cam ("V1.3" on the PCB), official Pi V2 Cam ("V2.1" on the PCB)


    Note:

    TX: The CPUs on the Raspberry Pi 1 and Pi Zero are more or less maxxed out with standard settings (6Mbit bitrate, 8/4/1024 FEC). Two TX dongles, higher resolution/bitrate, or more error correction or smaller packet sizes will not work. Even if it seems to be working on first look with higher bitrates, it can happen that latency suddenly raises if the CPU is loaded to much (in situations with high bitrate, like fast scene changes). I'd recommend a Pi2 or 3 as a TX because of this, it has enough headroom to not be worried about CPU usage at all.


    RX: Raspberry Pi1 and Pi Zero are not supported anymore with version 1.4
    Last edited by lizard; 27th December 2017 at 11:30 AM.

  2. #2
    Navigator
    Join Date
    Dec 2014
    Posts
    96
    Just released EZ-Wifibroadcast 1.2

    It works amazingly well, I wonder why nobody replied.

  3. #3
    FPV, RC and more........ IdefixRC's Avatar
    Join Date
    Oct 2014
    Posts
    209
    Thumbs Up. Still have that on my to do and try list :-)
    FPV, RC, 3D Printing and more..........
    idefixrc.com | IdefixRC Homepage
    goo.gl/VIsUy6 | Link to my YouTube Channel
    goo.gl/cayWH5 | Link to my Thingiverse Page

  4. #4
    Instructor Pilot Channel 1's Avatar
    Join Date
    Nov 2013
    Location
    Out in the middle of nowhere.
    Posts
    4,884
    Quote Originally Posted by lizard View Post
    Just released EZ-Wifibroadcast 1.2

    It works amazingly well, I wonder why nobody replied.
    Building such is probably beyond the skill level of many who are used to P&P devices.

    Wayne
    Everybody loves a bunny.

  5. #5
    Navigator
    Join Date
    Dec 2014
    Posts
    96
    No Linux skills required, just copy the images to some SD cards and it'll work

  6. #6

    EZ-Wifibroadcast feedback

    Quote Originally Posted by lizard View Post
    Well, the headline already says it, Wifibroadcast made easy.


    The goal of this project is to make the usage of Befinitiv's Wifibroadcast (https://befinitiv.wordpress.com/wifi...ve-video-data/) easy for people who would be otherwise drawn away because it can become quite time consuming and frustrating setting everything up if you're not used to tinkering with linux.
    You just need to download the SD card image, put it on two SD cards, switch everything on and 15 seconds later you have a live HD picture.





    Features:
    ---------
    - Supports all Raspberry Pi models including Pi3, Pi Zero and also Odroid-W
    - Supports the new Pi V2 cam
    - Configuration can be done from Windows, no Linux knowledge required
    - Support for 2.4Ghz band (incl. Channel 14) and all three 5Ghz bands on Ralink and Atheros cards
    - Support for 2.3Ghz band on Atheros cards
    - TXPower increased (and verified) for both Atheros and Ralink cards
    - 2x transmit diversity support
    - 6x receive diversity support using 3 cards (more should also be possible, just haven't tested that yet)
    - Live RSSI display per card and defective blocks display
    - Ground recording to USB stick
    - Startup time reduced, now about 10-15 seconds depending on Pi model and Wifi cards used
    - SD card reliability and general robustness tweaks (read-only filesystem, syslogging to SD disabled, etc.)






    Wifi Cards:
    ----------
    You have a lot of choice. All wifi cards with one of the following chipsets should work:


    Atheros AR9271
    Atheros AR9280
    Atheros AR9287


    Ralink RT2070
    Ralink RT2770
    Ralink RT2870
    Ralink RT3070
    Ralink RT3071
    Ralink RT3072
    Ralink RT3370
    Ralink RT3572
    Ralink RT5370
    Ralink RT5372
    Ralink RT5572


    However, there might be whatever small issues that prevent those cards from working, so if you want to play it safe, choose one of the cards that have been tested by different people and definitely work:

    - Alfa AWUS036NHA (2.3/2.4Ghz, high power, Atheros AR9271 chipset)
    - TPLink TL-WN722N (2.3/2.4Ghz, Atheros AR9271 chipset)
    - ALFA AWUS051NH v2 (2.4Ghz/5Ghz, high power, Ralink RT3572 chipset)


    This ones also looks promising for high power needs:
    - Alfa AWUS052NH (2.4Ghz/5Ghz, Diversity, high power, RT3572 chipset)

    On the other hand, if everybody gets the same cards, we'll never find out which other ones work. There are also very small and lightweight RT5370 cards available in china shops for under 4$. Aliexpress for example has a lot of cheap wifi cards in general. It would be nice if you report back your findings in case you tried a wifi card that is not listed here.



    Installation / Setup
    --------------------
    - Download the image and unzip it
    - Write it to two (minimum 1GB) SD Cards using Win32DiskImager or any other SD image write tool
    - That's it



    Configuration
    -------------
    - Put SD Card in Windows computer or anything that has a text editor (Tablet, Smartphone) and edit wifibroadcast.txt



    Ground Recording
    ----------------
    - USB Stick must contain a folder called "video"
    - Plug USB stick to ground Pi before powering on
    - Before disconnecting power, disconnect all USB sticks and wait a few seconds for the recording to be stopped,´then power off



    Please report back if it works for you. Also if it doesn't



    Dowloadlinks:
    V1.2:
    http://en.file-upload.net/download-1...t-1.2.zip.html

    V1.0:
    http://en.file-upload.net/download-1...t-1.0.zip.html

    (Sorry for the crappy filehosters, couldn't find anything better quickly. Consider
    using an adblocker like "uBlock Origin").



    Edit: EZ-Wifibroadcast Version 1.2 has been released.

    Changes from version 1.0 to 1.2:

    - Befi's and Rangarid's OSD integrated
    - Raspbian Update to Kernel 4.11 and latest Raspberry Firmware / Userland (Pi Zero/V2 Cam)
    - Display of configured Frequency and FEC-Parameters at the bottom of the screen
    - Ralink: Different bitrates for video and telemetry possible
    - Ralink: Wifi bitrate can be configured via wifibroadcast.txt
    - Atheros: Wifi bitrate can be configured via module parameter
    - Ralink: TXPower can be configured via module parameter
    - Supports V2 Cam 1280x720 up to 75fps, 1640x922 up to 48fps
    - AIFS/Backoff parameters tweaked, Atheros chipsets now give about 10-15% more throughput, Ralink about 3%
    - Atheros LED behaviour tweaked, blinks faster now, is "more sensitive"
    - CPU/GPU/RAM overclocked and force_turbo activated for less/more stable Latency and higher possible bitrate on Pi1/Zero
    - USB Ethernet Tethering support activated in Kernel (for smartphones)
    - DHCP enabled on Ethernet interfac (system will contact the DHCP server with "wifibroadcast-tx" or "wifibroadcast-rx" hostname)
    - Bash-prompt shows ro/rw status of the filesystem, macros ("rw","ro") added for quick switching
    - Reduced TXPower for Atheros chipsets slightly (just to be on the safe side)
    - Reduced TXPower for Ralink chipsets to default level
    - Patched Atheros Firmware for additional Atheros Chipsets (AR9287, e.g. TPLink 822N V2)
    - TX shows some status infos after startup
    - video.c changed to 240fps for less latency/jitter
    - addedd fflush to rx prozess (just to make sure ...)
    - disabled Systemd journal daemon (used up CPU ...)
    - Kept software, tools and libs etc. in the image, should make modifying or adding own features to the image easier
    - Support for two TX wifi dongles. Experimental right now, not in the config file, has to be configured manually in Linux

    Bugfixes:
    - Potential rapidly raising latency, stuttering image on Pi1/Zero in some cases: overclocked CPU/GPU/RAM, force_turbo=1, enabled performance governoer, reduced bitrate to 4.5Mbit, video.c patched to 240fps, added fflush in RX process, removed systemd-journald

    - AWUSH051NH and 052NH did not work cleanly as TX on 5Ghz band: Reduced TXPower for Ralink chipsets



    Tested wifi dongles:
    AWUS036NH, AWUS036NHA, AWUS051NH, TL-WN722N, TL-WN822N V2, CSL 300Mbit stick

    (My favourites for 2.4Ghz are TL-WN722N and AWUS036NHA at the moment, for 5Ghz the AWUS051NH. The more I test with the CSL 300Mbit dongles, the less I like them, not much TXPower, unclean signal when TXPower raised, they seem to have problems with high power TX cards when used as an RX card (bad blocks when being to near) and somehow there seem to be more badblocks compared to the 722N when used on a wifi channel with other wifi networks.)


    Tested Raspberry Hardware:
    Pi 1 B+, Pi2 B+, Pi3 B+, Pi Zero 1.3, Odroid-W
    official Pi V1 Cam ("V1.3" on the PCB), official Pi V2 Cam ("V2.1" on the PCB)


    Note:

    TX: The CPUs on the Raspberry Pi 1 and Pi Zero are more or less maxxed out with standard settings (720p, 4.5Mbit bitrate, 8/4/1024 FEC). Two TX dongles, higher resolution/bitrate, or more error correction or smaller packet sizes will not work. Even if it seems to be working on first look, it can happen that latency suddenly raises if the CPU is loaded to much (in situations with high bitrate, like fast scene changes). I'd recommend a Pi2 or 3 as a TX because of this, it has enough headroom to not be worried about CPU usage at all.


    RX: Raspberry Pi1 and Pi Zero have just about enough CPU power for one RX dongle, that's it. Multiple RX dongles, OSD, and/or ground-recording to memory stick will not work reliably. Get atleast a Pi2.
    Congratulations!!! very good work...I have just 2 questions concerning telemetry datas received and video recorded. Telemetry datas, are there avalaible on the RXD pin of AMA0 on the GPIO?
    What player can I use to read the videos?
    Best regards

    Thanks for your respons

  7. #7
    Any chance that someone could upload this to another (working) filehoster? Torrent would be best obviously. No chance that I ever will finish the download from the posted filehoster. My internet isn't the fastest and I tried already so many times it's not funny anymore....

  8. #8
    Navigator
    Join Date
    Jan 2015
    Posts
    11
    Great project! Have you measured the latency glass to glass?

  9. #9
    Navigator faber's Avatar
    Join Date
    Feb 2013
    Location
    Tucson, Arizona Sir!
    Posts
    922
    Quote Originally Posted by eijowk View Post
    Great project! Have you measured the latency glass to glass?
    +1....

  10. #10
    Navigator
    Join Date
    Jul 2016
    Posts
    1

    AR9271 5Mhz bandwith and 2.3Ghz enabled

    Quote Originally Posted by lizard View Post
    Well, the headline already says it, Wifibroadcast made easy.


    The goal of this project is to make the usage of Befinitiv's Wifibroadcast (https://befinitiv.wordpress.com/wifi...ve-video-data/) easy for people who would be otherwise drawn away because it can become quite time consuming and frustrating setting everything up if you're not used to tinkering with linux.
    You just need to download the SD card image, put it on two SD cards, switch everything on and 15 seconds later you have a live HD picture.





    Features:
    ---------
    - Supports all Raspberry Pi models including Pi3, Pi Zero and also Odroid-W
    - Supports the new Pi V2 cam
    - Configuration can be done from Windows, no Linux knowledge required
    - Support for 2.4Ghz band (incl. Channel 14) and all three 5Ghz bands on Ralink and Atheros cards
    - Support for 2.3Ghz band on Atheros cards
    - TXPower increased (and verified) for both Atheros and Ralink cards
    - 2x transmit diversity support
    - 6x receive diversity support using 3 cards (more should also be possible, just haven't tested that yet)
    - Live RSSI display per card and defective blocks display
    - Ground recording to USB stick
    - Startup time reduced, now about 10-15 seconds depending on Pi model and Wifi cards used
    - SD card reliability and general robustness tweaks (read-only filesystem, syslogging to SD disabled, etc.)






    Wifi Cards:
    ----------
    You have a lot of choice. All wifi cards with one of the following chipsets should work:


    Atheros AR9271
    Atheros AR9280
    Atheros AR9287


    Ralink RT2070
    Ralink RT2770
    Ralink RT2870
    Ralink RT3070
    Ralink RT3071
    Ralink RT3072
    Ralink RT3370
    Ralink RT3572
    Ralink RT5370
    Ralink RT5372
    Ralink RT5572


    However, there might be whatever small issues that prevent those cards from working, so if you want to play it safe, choose one of the cards that have been tested by different people and definitely work:

    - Alfa AWUS036NHA (2.3/2.4Ghz, high power, Atheros AR9271 chipset)
    - TPLink TL-WN722N (2.3/2.4Ghz, Atheros AR9271 chipset)
    - ALFA AWUS051NH v2 (2.4Ghz/5Ghz, high power, Ralink RT3572 chipset)


    This ones also looks promising for high power needs:
    - Alfa AWUS052NH (2.4Ghz/5Ghz, Diversity, high power, RT3572 chipset)

    On the other hand, if everybody gets the same cards, we'll never find out which other ones work. There are also very small and lightweight RT5370 cards available in china shops for under 4$. Aliexpress for example has a lot of cheap wifi cards in general. It would be nice if you report back your findings in case you tried a wifi card that is not listed here.



    Installation / Setup
    --------------------
    - Download the image and unzip it
    - Write it to two (minimum 1GB) SD Cards using Win32DiskImager or any other SD image write tool
    - That's it



    Configuration
    -------------
    - Put SD Card in Windows computer or anything that has a text editor (Tablet, Smartphone) and edit wifibroadcast.txt



    Ground Recording
    ----------------
    - USB Stick must contain a folder called "video"
    - Plug USB stick to ground Pi before powering on
    - Before disconnecting power, disconnect all USB sticks and wait a few seconds for the recording to be stopped,´then power off



    Please report back if it works for you. Also if it doesn't



    Dowloadlinks:
    V1.2:
    http://en.file-upload.net/download-1...t-1.2.zip.html

    V1.0:
    http://en.file-upload.net/download-1...t-1.0.zip.html

    (Sorry for the crappy filehosters, couldn't find anything better quickly. Consider
    using an adblocker like "uBlock Origin").



    Edit: EZ-Wifibroadcast Version 1.2 has been released.

    Changes from version 1.0 to 1.2:

    - Befi's and Rangarid's OSD integrated
    - Raspbian Update to Kernel 4.11 and latest Raspberry Firmware / Userland (Pi Zero/V2 Cam)
    - Display of configured Frequency and FEC-Parameters at the bottom of the screen
    - Ralink: Different bitrates for video and telemetry possible
    - Ralink: Wifi bitrate can be configured via wifibroadcast.txt
    - Atheros: Wifi bitrate can be configured via module parameter
    - Ralink: TXPower can be configured via module parameter
    - Supports V2 Cam 1280x720 up to 75fps, 1640x922 up to 48fps
    - AIFS/Backoff parameters tweaked, Atheros chipsets now give about 10-15% more throughput, Ralink about 3%
    - Atheros LED behaviour tweaked, blinks faster now, is "more sensitive"
    - CPU/GPU/RAM overclocked and force_turbo activated for less/more stable Latency and higher possible bitrate on Pi1/Zero
    - USB Ethernet Tethering support activated in Kernel (for smartphones)
    - DHCP enabled on Ethernet interfac (system will contact the DHCP server with "wifibroadcast-tx" or "wifibroadcast-rx" hostname)
    - Bash-prompt shows ro/rw status of the filesystem, macros ("rw","ro") added for quick switching
    - Reduced TXPower for Atheros chipsets slightly (just to be on the safe side)
    - Reduced TXPower for Ralink chipsets to default level
    - Patched Atheros Firmware for additional Atheros Chipsets (AR9287, e.g. TPLink 822N V2)
    - TX shows some status infos after startup
    - video.c changed to 240fps for less latency/jitter
    - addedd fflush to rx prozess (just to make sure ...)
    - disabled Systemd journal daemon (used up CPU ...)
    - Kept software, tools and libs etc. in the image, should make modifying or adding own features to the image easier
    - Support for two TX wifi dongles. Experimental right now, not in the config file, has to be configured manually in Linux

    Bugfixes:
    - Potential rapidly raising latency, stuttering image on Pi1/Zero in some cases: overclocked CPU/GPU/RAM, force_turbo=1, enabled performance governoer, reduced bitrate to 4.5Mbit, video.c patched to 240fps, added fflush in RX process, removed systemd-journald

    - AWUSH051NH and 052NH did not work cleanly as TX on 5Ghz band: Reduced TXPower for Ralink chipsets



    Tested wifi dongles:
    AWUS036NH, AWUS036NHA, AWUS051NH, TL-WN722N, TL-WN822N V2, CSL 300Mbit stick

    (My favourites for 2.4Ghz are TL-WN722N and AWUS036NHA at the moment, for 5Ghz the AWUS051NH. The more I test with the CSL 300Mbit dongles, the less I like them, not much TXPower, unclean signal when TXPower raised, they seem to have problems with high power TX cards when used as an RX card (bad blocks when being to near) and somehow there seem to be more badblocks compared to the 722N when used on a wifi channel with other wifi networks.)


    Tested Raspberry Hardware:
    Pi 1 B+, Pi2 B+, Pi3 B+, Pi Zero 1.3, Odroid-W
    official Pi V1 Cam ("V1.3" on the PCB), official Pi V2 Cam ("V2.1" on the PCB)


    Note:

    TX: The CPUs on the Raspberry Pi 1 and Pi Zero are more or less maxxed out with standard settings (720p, 4.5Mbit bitrate, 8/4/1024 FEC). Two TX dongles, higher resolution/bitrate, or more error correction or smaller packet sizes will not work. Even if it seems to be working on first look, it can happen that latency suddenly raises if the CPU is loaded to much (in situations with high bitrate, like fast scene changes). I'd recommend a Pi2 or 3 as a TX because of this, it has enough headroom to not be worried about CPU usage at all.


    RX: Raspberry Pi1 and Pi Zero have just about enough CPU power for one RX dongle, that's it. Multiple RX dongles, OSD, and/or ground-recording to memory stick will not work reliably. Get atleast a Pi2.

    Hi, thanks a lot for you thread and image (i will test the v1.2 tomorrow morning)
    I use wifibroadcast for broadcast and fpv application. I wonder 2 things, how to use a less bandwith, like 5Mhz to have a better energy over the air. I found nothing about it to build it on the web or if anybody tried it. I think it is clearly the way to reach farest range and better collision avoiding. ues clearly !
    Also i found nowhere how to build correctly the patch to use 2.3Ghz. Did someone done it before ?

    THanks a lot !
    whynot a v1.3 with 5Mhz and 2.3Ghz supports !

    cheers

Page 1 of 3 123 LastLast

Similar Threads

  1. Replies: 18
    Last Post: 5th November 2016, 01:14 PM
  2. Cheap, easy OSD?
    By Julezflies in forum OSDs & Flight Controllers
    Replies: 2
    Last Post: 2nd July 2015, 01:07 AM
  3. Balancing your motors made easy
    By saucisse in forum RC TECH
    Replies: 2
    Last Post: 4th July 2013, 10:26 PM
  4. Cheap easy way to extend fatshark cord
    By Hockeystud87 in forum Fat Shark R/C Vision Systems
    Replies: 6
    Last Post: 4th June 2013, 11:48 PM
  5. Cheap & Easy: directional antenna for beacon
    By sircana in forum IFR - Video Link Discussion
    Replies: 39
    Last Post: 1st June 2013, 10:44 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •