MegunoLink

I've connected to my Uno using RFDigital's wireless inventors shield and their usb rf dongle.
This configuration successfully echos bytes sent to the Uno from MLP.

Next I set up the Arduino Upload Monitor and tried uploading a small tweak to the test program.
The following errors were given:

MegunoLink Pro AVRDude Wrapper
------------------------------
"C:\Program Files (x86)\Arduino\hardware\tools\avr\bin\avrdude" "-CC:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf" -q -q -patmega328p -carduino -PCOM3 -b115200 -D -Uflash:w:C:\Users\Roger\AppData\Local\Temp\build85611b728330f523d0d9439e640147c2.tmp/test_rf_serial.ino.hex:i
"-CC:\Program Files (x86)\Arduino\hardware\tools\avr/etc/avrdude.conf" -q -q -patmega328p -carduino -PCOM3 -b115200 -D -Uflash:w:C:\Users\Roger\AppData\Local\Temp\build85611b728330f523d0d9439e640147c2.tmp/test_rf_serial.ino.hex:i
: stk500_getsync() attempt 1 of 10: not in sync: resp=0x00
: stk500_getsync() attempt 2 of 10: not in sync: resp=0x00
: stk500_getsync() attempt 3 of 10: not in sync: resp=0x00
: stk500_getsync() attempt 4 of 10: not in sync: resp=0x00
: stk500_getsync() attempt 5 of 10: not in sync: resp=0x00
: stk500_getsync() attempt 6 of 10: not in sync: resp=0x00
: stk500_getsync() attempt 7 of 10: not in sync: resp=0x00
: stk500_getsync() attempt 8 of 10: not in sync: resp=0x00
: stk500_getsync() attempt 9 of 10: not in sync: resp=0x00
: stk500_getsync() attempt 10 of 10: not in sync: resp=0x00
Invalid library found in C:\Users\Roger\Documents\Arduino\libraries\examples: C:\Users\Roger\Documents\Arduino\libraries\examples
Invalid library found in C:\Users\Roger\Documents\Arduino\libraries\examples: C:\Users\Roger\Documents\Arduino\libraries\examples

It looks like it's not getting the serial connection, but why?
Same results for IDE 1.0.6 and a recent update to 1.6.6

Thanks

Just got a reply from RFDigital
"The RFD21815 and RFD21807 is not suitable to load code wirelessly to an Arduino. The parts you have are best for sending serial data back and forth like a wireless pipe."

So it looks like it's a hardware issue. Hope this helps others avoid the same problem