OK i did the deletes .
Actually with all the published image files (plug and play files) there is no reason for typing any of this in.
But then it seemed the pre made files were not being published .
Things are simpler now...

The developer of wifibroadcast ,befinitiv now has pre-made images available:They are for 2.4ghz for the time being.https://befinitiv.wordpress.com/2015...pi-fpv-images/ Download here https://github.com/befinitiv/rpi_wifibroadcast_image_builder/releases

These files will get you up and running with WiFi Broadcast. They operate on the 5.8ghz band on wifi channel 155. They have been tested using the RPi A+ on transmit and the RPi2 B on receive using the TP-Link TL-WDN3200. Each require a 8gb class10 micro sd card. First download this SD Formatter 4.0 for Windows and Mac.. https://www.sdcard.org/downloads/formatter_4/ Use it to reformat cards used in the RPi's Next download Win32 Disk Imager. This program is required to write the provided image files to your sd cards. http://sourceforge.net/projects/win3...atest/download And of course the files. Please unzip first Transmit download (2.3 gb) https://drive.google.com/file/d/0B6_TvnfyzYBRdl95amswVld6ekk/view?usp=sharing Receiver download (2.3 gb) https://drive.google.com/file/d/0B6_TvnfyzYBRV3R6VzJJTFVMVlk/view?usp=sharing

Hi Thomas. RC Groups is not going to allow me to store the *.img files. These guys are like 8gb each. They make this project plug and play for most users. I have a web site account with a provider but not sure if I can run a FTP site there. . I'm having a problem with my post above. There are couple of instructions which have a http:// which this forum is underscoring them as a web link. The worse part of it is some of them actually have an underscore in the address already. How can I make the forum stop doing this??

I have this system working on 5.8 ghz now. If anyone is interested I will add the necessary instructions. They do require you to purchase the TL 3200 dual band dongles I am willing to post the IMG files if someone knows of a place to host them Right now we are talking about 16gb total. I believe they can be reduced to less than half that size if I knew how to compress them. Still 7 gb is a lot

Step by Step instructions for the RPI HD WiFi Video System
I hope this helps someone get their HD FPV system running. Right now its on 2.4g only.
It was written for those unfamiliar with the raspberry pi and Linux
Here we go.............
Hardware required
PARTS LIST:Video Rx: Raspberry Pi 2 Model B 1GB8GB micro SD cardTP-Link TL-WN722N Wireless USB adapter
Video Tx:Raspberry Pi Model A+ 256MB8GB micro SD cardTP-Link TL-WN722N Wireless USB adapter
RPI Camera
In addition you will need two 5vdc power supplies
An internet connection with a ethernet connector to hook up the RPI (raspberry pi) to the internet.
A keyboard, a mouse and a monitor with HDMI inputs
The 5volts is supplied to the RPI either via a micro usb cable or soldering wires on to pins or using the the male servo connector found on typical BEC boards .
First download this SD Formatter 4.0 for Windows and Mac.. https://www.sdcard.org/downloads/formatter_4/
Use this to format you sd cards for the RPI before running noobs.
Next you need to down load the Linux for RPI. This program is called NOOB and its easy to install.
Download the zip file at https://www.raspberrypi.org/downloads/noobs/
You can unzip the file directly to your sd card with winrar..
You will need to do this for both cards.
All programing will be done with RPI 2 B board since it has the necessary usb/nic connections.
*********************************************************************************************
Installing linux with the noobs sd card
Stick a noobs sd card into a RPI 2b board. You will need to have a keyboard/mouse/monitor/ethernet/TL-WN722N Wireless USB adapter hooked up..
Power the board up and NOOBS will autoexecute .
At the bottom of the screen select US language and make sure US keyboard shows up
IN the box select Raspbian then click install..
This installs the operating system and will take about half an hour..
*******************************************************************************************
******************************************************************************************
When the install completes a small window pops up notifying you to its success.
Clicking on this should bring up your new desktop........
This is called the graphical user interface (GUI) kinda looks like windows.
Next we need to bring up the Terminal program .
This archaic looking program reminds me of old DOS from 30 years ago.
Unfortunately we must use it to get our RPI's working and in the end its not all that bad ..
From now on everything we do will be via the terminal program.
There are 2 options for bringing up the Terminal.
Option 1. from the GUI the fourth icon from the left is a black square that actually represents a terminal monitor.
Clicking on this will bring up the terminal.
You should now have a black window with the prompt pi@raspberrypi - $ .
We will type our commands after the prompt.
If the font is too small for you ......click on edit / preferences.
Under the style tab you can increase the font to 17 ... OK it.
Option 2: The terminal program is also available under Menu / accessories / terminal
....................................................................................................................
Were ready to start the good stuff.
This will build the Transmitter image file......
Make sure the camera and WIFI stick is attached.
First we need to check the config file.
Bring up the terminal and type in these commands. (spaces and case sensitivity count)
pi@raspberrypi - $ cd /usr/bin
pi@raspberrypi - $ sudo ./raspi-config
You should now have the config screen
Use the arrow keys to navigate this menu.
Hit enter on the first line to expand the file system (most likely this has already been done by the NOOBS install.
Next arrow down to enable camera / select it / enable it.
Arrow down to finish.
Ok the reboot
...........................................................................................................
finally type in the cd command... This completes the configuration modifications.
pi@raspberrypi - $ cd
********************************************************************************************
The following are the necessary commands to type in.
the prompt is not shown below but will appear on your terminal.
You must be hooked up to the internet.
Commands are case sensitive. The fonts vary because I used copy and past from several web pages.
This was done to avoid typos.
Some commands may take up to a minute to complete and require you to respond with a "y" and enter.
---------------------------------------------------------------------------------------------------
sudo $HOME
sudo apt-get install mercurial
hg clone https://bitbucket.org/befi/wifibroadcast
sudo cp wifibroadcast/patches/AR9271/firmware/htc_9271.fw /lib/firmware
sudo apt-get install libpcap-dev iw
cd wifibroadcast
make
cd $HOME/wifibroadcast
cd
hg clone https://bitbucket.org/befi/wifibroadcast_fpv_scripts
cd wifibroadcast_fpv_scripts
cd init.d
sudo cp wbctxd /etc/init.d
sudo update-rc.d wbctxd start
cd
*********************************************************************
FYI The | character is located at "shift back slash "
This completes the Transmitter image !!
Reboot the board and the green light should be blinking on the WIFI stick after a few seconds.
BTW the GUI does not show any program status.
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.
Now we will build the receiver image
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.
We will be using the same RPI hardware set up used for the transmitter
Remove the camera cable as the camera is not used to receive
First remove the sd card that contains the transmitter files.
You might want to mark it so as to not mix it up with the receiver card later on.
Insert the sd card containing a fresh copy of NOOBS.
Power on the RPI which will auto execute.
Again make sure you select US english and the US keyboard..
Select Raspian from the main box and click install. its about a 30 min install..
When the install completes a small window pops up notifying you to its success.
Clicking on this should bring up your new desktop........
This is called the graphical user interface (GUI) kinda looks like windows.
Next we need to bring up the Terminal program .
-------------------------------------------------------------------------------
From the GUI the fourth icon from the left is a black square that actually represents a terminal monitor.
Clicking on this will bring up the terminal.
You should now have a black window with the prompt pi@raspberrypi - $ .
We will type our commands after the prompt.
If the font is too small for you ......click on edit / preferences.
____________________________________________________________
First we need to check the config file.
Bring up the terminal and type in these commands. (spaces and case sensitivity count)
pi@raspberrypi - $ cd /usr/bin
pi@raspberrypi - $ sudo ./raspi-config
You should now have the config screen
Use the arrow keys to navigate this menu.
Hit enter on the first line to expand the file system (most likely this has already been done by the NOOBS install.
Next arrow down to advanced options
enable ssh
Arrow down to finish.
OK the reboot.
...........................................................................................................
finally type in the cd command... This completes the configuration modifications.
pi@raspberrypi - $ cd
********************************************************************************************
The following are the necessary commands to type in.
the prompt is not shown below but will appear on your terminal.
You must be hooked up to the internet.
Commands are case sensitive. The fonts vary because I used copy and past from several web pages.
This was done to avoid typos.
Some commands may take up to a minute to complete and require you to respond with a "y" and enter.
_______________________________________________________________________
sudo cd $HOME
sudo apt-get install mercurial libpcap-dev iw
hg clone https://bitbucket.org/befi/wifibroadcast
cd wifibroadcast
make
cd $HOME
hg clone https://bitbucket.org/befi/hello_video
cp hello_video/video.c /opt/vc/src/hello_pi/hello_video
cd /opt/vc/src/hello_pi/
./rebuild.sh
cd
hg clone https://bitbucket.org/befi/wifibroadcast_fpv_scripts
cd wifibroadcast_fpv_scripts
cd init.d
sudo cp wbcrxd /etc/init.d
sudo update-rc.d wbcrxd start
cd
THATS IT !!
---------------------------------------------------------------------------------------------------
THE RPI's should auto execute
On the wifi sticks solid green led indicates its initialized green blinking led's means it transmitting or receiving data..
I use the smaller lighter RPI A+ for the transmitter
And the bigger RPI 2B for receiving
Good luck..

I got it to work.... after getting a bit more info i was able to successfully build the 2 image files. There are about 20 lines of entry for each the transmitter file and the receiver file. It takes an hour or so to program each card the image files once downloaded would take maybe 5 min each to load. I made my image files on a 8gb micro sd card. Even though the actual data is under 4gb once it is written to a 8gb card the new file size is 8gb. No a big deal except when trying to distribute these files on the internet. 16gb for both is a lot. If anyone is interested I could write up the procedures here.

Ok well I tried to read the threads translated with Google . I say tried because much of it translated so poorly I could not make much sense of it. Most Chinese instruction manuals are easier to understand. I tried to follow his instructions. I believe the tx stuff was ok but the with the rx build I got an error saying the command is no longer supported. It is a shame no one has posted some "dumb down " instructions. BTW that term is so appropriate. I am sure many are wishing to build this set up but the linux and cryptic language is a killer. I borrowed a pretty good linux video course covering the command line but it is so boring... I would send the guy $20 in paypay in a heartbeat for a current IMG file.. I have wasted a lot of time so far. I'll keep snooping around ... Maybe even get lucky..

Thanks for the reply. I understand your busy so late winter will be here before we know it. I'll pick up a couple of the 2.4 ghz sticks and try again. Getting it to work on 2.4 even if it is not the desired freq it would be an incentive to continue . I am surprised how there seems to be so few people publishing their files. The result is the average Joe is sticking with low def analog FPV. The Rcgroups thread basically consists of 2 guys trading a few scriopts and thats it. --tp

Hi Thomas. This is a great project especially if you have your Mr RC-Cam DIY HD Goggles to plug into. I picked up 2 of the RP 2 b boards and a A+ board. They said the TP-Link TL-WDN3200 wifi stick would work on 5.8ghz to avoid interference with the 2.4 ghz rc transmitter. So I got a couple of them too. I loaded up the files you pointed to and the results have been very poor. I can get a picture but the lag is presently about 30sec and the frame rate is maybe 10fps or so. Not good ! Hopefully you will get some spare time and design us a DIY setup that will work. Thanks again..

You should be able to read back the code (hex file) that you programmed into the chip. If you read out the same code as you put in it would verify the fact that the chip is indeed programmed and the chip is still functional. I use the following software IC-Prog it is free from http://www.ic-prog.com/index1.htm. It works with a very simple and low cost programmer I bought from this site. http://www.sparkfun.com/shop/index.php?sho...t=405095&cat=3& Its model SKU Number:PIC-PG2 and sells for $12.95 I have used this combination to program all of RC-Cam's projects. It has worked flawlessly.
I would expect if to be in a loop as any such program would loop back looking for appropriate input data.
The crystal runs the chips clock. With no clock the chip will not run. You could check the crystal oscillator with a Scope capable of 20 mhz, a frequency counter or even hear it on a shortwave receiver tuned to 20 mhz.
This is the flow of the program. As you can see it loops waiting for input.
Init:
Get PulsIn value of Neutral for the servo
Get Gain Value
Get Servo Direction
MainLoop:
If Autopilot ON then
GoTo Autopilot
Else
GoTo Passthru
EndIf
PassThru:
Pulsin Receiver
PulsOut Rudder
GoTo MainLoop
AutoPilot:
Get GPS Data
Do CheckSum of Data
Fill in Vars
If Correction needed then DoCorrection
GoTo MainLoop
DoCorrection:
If Direction Normal
Turn normal
Else if Direction Reverse
Turn Reverse
GoTo MainLoop
Tom

I did program the pic chip myself, but was able to purchase the etched circuit board from Mike. I do not believe the hex code is encripted or write protected. You should be able to verify that the pic chip has the correct code using your programmer. When the circuit is first powered up the led should light up for 3 seconds and then go out. Make sure the led is working. I was looking at the schematic last night and it seems to me that you could build up small parts of the circuit just to do some initial tests. It looked like you only needed the pic chip, a 20mhz crystal, a few resistors, a led, and a 5 volt source to power up the pic.
Have you tried that yet?
Have you verified the hex code programming?
Have you checked the 20mhz oscillator crystal is running?
Is the pic getting 5vdc?
The circuit does work. You should be able to get yours working too.
T.P.

Sorry I have not checked this forum for a while and was unaware of your last post.
If the Autopilot board does not get the proper sentenances from the gps it wont do anything. It is very picky. As far as I know only the garmin outputs the format it wil lwork with. Magellan will not work. Somewhere on this forum a text file was posted that could be imported into hyper terminal and sent out the serial port @ 4800 baud. I looked for it again and I can not find it. But it did allow you to at least test the board without a GPS. I will look again if you are still in need help.
UPDATE: read this thread there is the TXT file there also http://www.rc-cam.com/forum/index.php?showtopic=666
Tom