I've been flying a Phantom 1.1.1 (for practice) and a Phantom 2 with a Zenmuse Gimbal and FPV (for filming) since early January, which given the weather here in the NYC area, has been a challenge in itself. I'm a photographer, not an RC enthusiast.
Over the weekend, I migrated both Phantoms to the Futaba 8FG with FASST (a frequency-switching system that is pretty much interference proof.) The process took about four hours and was relatively painless--thanks mainly to a downloadable data file containing complete Naza-M programming for the 8FG (more on that in a moment).
I live in an urban environment. Flying with FPV, I've been increasingly frustrated with the 300m "safe limit" for the DJI transmitter. Knowing that even at 300m there are probably 500 active wi-fi transmitters between me and my Phantom 2 (with about $2,000 of additional goodies aboard) is disconcerting. Obviously, the farther the Phantom, the weaker the signal from the stock DJI TX, and the greater the likelihood of a flyaway.
I've been thinking about the Futaba 8FG with its FASST frequency-switching system that by all accounts is virtually impervious to radio interference.
At first I assumed that in order to switch to the Futaba 8FG, I'd have to replace the RXs in both Phantoms. In the RC Forums I learned that the dual-antenna RX on both my Phantom 1.1.1 and the Phantom 2 are FASST compatible -- meaning that the existing RX can be "bound" to the 8FG (and presumably all of the higher-end Futaba TXs).
Still after watching various You Tube videos on programming a Futaba, it was obvious that setting up a TX from scratch to fly a Naza M V2 was well-beyond my abilities. Which is when I discovered the Aerial Pixels pre-programmed settings file for the 8FG. Cost: $1!
http://aerialpixels.com/support/futaba- ... ing-s-bus/
I used the file for the "Naza M / Futaba 8FG" since there's no option for a Naza M V2. It worked just fine! The same Aerial Pixels file worked for the Naza M V2 on both my Phantom 1.1.1 and Phantom 2. No adjustments necessary, except for the slight "Trim" fine-tuning mentioned below which is almost certainly an issue unique to my particular TX.
By following the Aerial Pixels instructions recipe-style, in a few hours I was able to set up the Futaba 8FG for both Phantoms, bind the Futaba TX to the DJI RXs, run the Naza M V2 Assistant apps for both the Phantom 1 and Phantom 2, and take both drones for test flights -- during which everything functioned flawlessly.
The throttle joy stick on the Airplane version of the Futaba 8FG that I bought doesn't automatically center. (For some reason, the "A" version is recommended for multi rotors over the H, or Helicopter version.) But I emailed Futaba service, and two days later, a kit containing a tiny spring, rocker arm and bracket was in my mailbox -- gratis! It took about ten minutes studying the right-hand joy stick to figure out how the return spring works and another ten minutes to install it. Futaba's part number for the return spring kit is 6528769.
There's a good You Tube video demonstrating how to bind a Futaba TX to the Phantom 2's stock RX. It takes about 30 seconds.
Binding the Phantom 1.1.1 is a little trickier, but still only takes a minute or so. It goes like this: turn the TX off, leave the Phantom battery OUTSIDE the battery compartment and connect it. Inside the battery compartment on the underside of the RX board you'll see a red LED. Next to it is a small black button. Hold the button with a screwdriver tip for two seconds. The LED will begin to blink. Turn on the Futaba (be sure to select the YES option that turns on radio transmissions) with your newly uploaded Phantom 1 program selected as the active MODEL, if the blinking red RX LED goes out, you're bound!
Of course, you need to use the Assistant Software to calibrate the joy sticks and make sure all functions -- including IOC, Gimbal, and Fail Safe Return to Home are working properly. The Aerial Pixels program attaches the Gimbal control to one of the 8FG dials, which is a nice touch and makes vertical pans much, much smoother. Also, the RTH Failsafe is programmed to switch "SF," so you can activate Failsafe without turning off the TX. I couldn't see the benefit of this until I realized it takes quite a bit of warmup time and fumbling through menus to actually get the 8FG transmitting.
The only serious hitch I encountered was a -17% error in my throttle at the centered "hover" position on the Phantom 2 (ie. with the throttle centered, the Phantom 2 would slowly descend instead of holding altitude.)
After much fruitless online research, I discovered by trial and error that the little Trim levers next to the joy stick boxes are designed for fine-tuning this kind of problem. I pushed the Trim lever until the throttle arrow centered and turned green in the Assistant app. Problem solved -- or so I thought.
When I went to start up the Phantom, nothing happened. The trouble with adding too much positive trim to the throttle, I discovered, is that the joy stick can no long reach the zero throttle position needed to start and stop the motors. I was, however, able to find a compromise trim position that allows the Phantom to hover without descending -- and still lets me start and stop the motors.
I was willing to fly the Phantom 1 (without a camera) out over Long Island Sound this morning. I'll test the Phantom 2 a little more throughly in the park before heading out on any long FPV "missions." But radio interference aside, the other benefits of the Futaba 8FG I've already discovered are:
1. smoother Gimbal (vertical) pans as well as horizontal (yaw) pans resulting from a much stiffer joy stick that is far easier to control in fine increments.
2. more fluid flights overall thanks to increased control afforded by the high-quality of the Futaba potentiometers. I can now yaw far more slowly and smoothly without also getting unwanted throttle increases and decreases. The same goes for pitch control where I can now go forward, crab, and fly sideways more slowly and smoothly -- and do it without unwanted changes in speed or direction.
3. it will take a few more test flights before I'm comfortable sending the Phantom 2 out over water or on a distant FPV. But when the time comes, I'll surely be far less apprehensive about a random wi-fi network -- or another unseen RC pilot -- seizing control of my Phantom.
Hope this is useful to any fellow newbies contemplating a TX upgrade!
Over the weekend, I migrated both Phantoms to the Futaba 8FG with FASST (a frequency-switching system that is pretty much interference proof.) The process took about four hours and was relatively painless--thanks mainly to a downloadable data file containing complete Naza-M programming for the 8FG (more on that in a moment).
I live in an urban environment. Flying with FPV, I've been increasingly frustrated with the 300m "safe limit" for the DJI transmitter. Knowing that even at 300m there are probably 500 active wi-fi transmitters between me and my Phantom 2 (with about $2,000 of additional goodies aboard) is disconcerting. Obviously, the farther the Phantom, the weaker the signal from the stock DJI TX, and the greater the likelihood of a flyaway.
I've been thinking about the Futaba 8FG with its FASST frequency-switching system that by all accounts is virtually impervious to radio interference.
At first I assumed that in order to switch to the Futaba 8FG, I'd have to replace the RXs in both Phantoms. In the RC Forums I learned that the dual-antenna RX on both my Phantom 1.1.1 and the Phantom 2 are FASST compatible -- meaning that the existing RX can be "bound" to the 8FG (and presumably all of the higher-end Futaba TXs).
Still after watching various You Tube videos on programming a Futaba, it was obvious that setting up a TX from scratch to fly a Naza M V2 was well-beyond my abilities. Which is when I discovered the Aerial Pixels pre-programmed settings file for the 8FG. Cost: $1!
http://aerialpixels.com/support/futaba- ... ing-s-bus/
I used the file for the "Naza M / Futaba 8FG" since there's no option for a Naza M V2. It worked just fine! The same Aerial Pixels file worked for the Naza M V2 on both my Phantom 1.1.1 and Phantom 2. No adjustments necessary, except for the slight "Trim" fine-tuning mentioned below which is almost certainly an issue unique to my particular TX.
By following the Aerial Pixels instructions recipe-style, in a few hours I was able to set up the Futaba 8FG for both Phantoms, bind the Futaba TX to the DJI RXs, run the Naza M V2 Assistant apps for both the Phantom 1 and Phantom 2, and take both drones for test flights -- during which everything functioned flawlessly.
The throttle joy stick on the Airplane version of the Futaba 8FG that I bought doesn't automatically center. (For some reason, the "A" version is recommended for multi rotors over the H, or Helicopter version.) But I emailed Futaba service, and two days later, a kit containing a tiny spring, rocker arm and bracket was in my mailbox -- gratis! It took about ten minutes studying the right-hand joy stick to figure out how the return spring works and another ten minutes to install it. Futaba's part number for the return spring kit is 6528769.
There's a good You Tube video demonstrating how to bind a Futaba TX to the Phantom 2's stock RX. It takes about 30 seconds.
Binding the Phantom 1.1.1 is a little trickier, but still only takes a minute or so. It goes like this: turn the TX off, leave the Phantom battery OUTSIDE the battery compartment and connect it. Inside the battery compartment on the underside of the RX board you'll see a red LED. Next to it is a small black button. Hold the button with a screwdriver tip for two seconds. The LED will begin to blink. Turn on the Futaba (be sure to select the YES option that turns on radio transmissions) with your newly uploaded Phantom 1 program selected as the active MODEL, if the blinking red RX LED goes out, you're bound!
Of course, you need to use the Assistant Software to calibrate the joy sticks and make sure all functions -- including IOC, Gimbal, and Fail Safe Return to Home are working properly. The Aerial Pixels program attaches the Gimbal control to one of the 8FG dials, which is a nice touch and makes vertical pans much, much smoother. Also, the RTH Failsafe is programmed to switch "SF," so you can activate Failsafe without turning off the TX. I couldn't see the benefit of this until I realized it takes quite a bit of warmup time and fumbling through menus to actually get the 8FG transmitting.
The only serious hitch I encountered was a -17% error in my throttle at the centered "hover" position on the Phantom 2 (ie. with the throttle centered, the Phantom 2 would slowly descend instead of holding altitude.)
After much fruitless online research, I discovered by trial and error that the little Trim levers next to the joy stick boxes are designed for fine-tuning this kind of problem. I pushed the Trim lever until the throttle arrow centered and turned green in the Assistant app. Problem solved -- or so I thought.
When I went to start up the Phantom, nothing happened. The trouble with adding too much positive trim to the throttle, I discovered, is that the joy stick can no long reach the zero throttle position needed to start and stop the motors. I was, however, able to find a compromise trim position that allows the Phantom to hover without descending -- and still lets me start and stop the motors.
I was willing to fly the Phantom 1 (without a camera) out over Long Island Sound this morning. I'll test the Phantom 2 a little more throughly in the park before heading out on any long FPV "missions." But radio interference aside, the other benefits of the Futaba 8FG I've already discovered are:
1. smoother Gimbal (vertical) pans as well as horizontal (yaw) pans resulting from a much stiffer joy stick that is far easier to control in fine increments.
2. more fluid flights overall thanks to increased control afforded by the high-quality of the Futaba potentiometers. I can now yaw far more slowly and smoothly without also getting unwanted throttle increases and decreases. The same goes for pitch control where I can now go forward, crab, and fly sideways more slowly and smoothly -- and do it without unwanted changes in speed or direction.
3. it will take a few more test flights before I'm comfortable sending the Phantom 2 out over water or on a distant FPV. But when the time comes, I'll surely be far less apprehensive about a random wi-fi network -- or another unseen RC pilot -- seizing control of my Phantom.
Hope this is useful to any fellow newbies contemplating a TX upgrade!
