Installed A7501 in 8s, can't bind with V911

More
23 Sep 2013 04:15 #14000 by SLMcc
I removed the A7501 module from the Tx that came with my RTF V911 and installed it in my 8s following the procedure in the .pdf. I went into the TX.ini file with Notepad++ and set

enable-a7105=A13
has_pa-a7105=1

In my model setup screen I set it to Flysky. I put the battery in the heli and the light flashes fast like it did with the stock Tx. Then I push the Re-Int and the binding screen comes up on the Tx. After the 3 seconds the Tx beeps and light on the heli changes from a fast blink to a slow blink. It doesn't go solid like it did with the factory Tx and it doesn't react to any stick movements. :( It's like it wants to bind but now quite?

Any ideas what's wrong?

Please Log in or Create an account to join the conversation.

More
23 Sep 2013 16:18 #14020 by SLMcc
I got a decent pic of the install. I can't see anything wrong but maybe somebody else does?

The white / blue wire on the left on pin 1 that goes out of the picture and comes back in is the one connected to TMS.
Attachments:

Please Log in or Create an account to join the conversation.

More
24 Sep 2013 04:38 #14028 by SLMcc
Here's a copy of my TX.ini, bold added. I can select FlySky and I've tried the WL Toys 9x9 option ON (it's off by default) but that didn't change anything, I still can't get it to bind. Is there something in the .ini I'm missing? I really want to fly. :(

current_model=1
language=0
music_shutdown=0
mode=2
brightness=2
contrast=5
volume=10
vibration=0
power_alarm=0
batt_alarm=3300
batt_critical=3800
batt_warning_interval=30
splash_delay=35
[modules]
enable-cyrf6936=B12
has_pa-cyrf6936=1
enable-a7105=A13
has_pa-a7105=1

enable-cc2500=None
has_pa-cc2500=0
enable-nrf24l01=None
has_pa-nrf24l01=0
[calibrate1]
max=3813
min=530
zero=2171
[calibrate2]
max=3549
min=354
zero=1951
[calibrate3]
max=3698
min=489
zero=2093
[calibrate4]
max=3867
min=569
zero=2218
[touch]
xscale=189176
yscale=144869
xoffset=-384
yoffset=-23
[autodimmer]
timer=20000
dimvalue=1
[countdowntimersettings]
prealerttime=30000
prealertinterval=10000
timeupinterval=10000
[telemetry]
temp=farenheit
length=feet

Please Log in or Create an account to join the conversation.

More
24 Sep 2013 09:45 - 24 Sep 2013 09:48 #14033 by matrixFLYER
Last edit: 24 Sep 2013 09:48 by matrixFLYER.

Please Log in or Create an account to join the conversation.

More
24 Sep 2013 17:30 #14040 by SLMcc
Hi, yes I used notepad++ to edit it and pnotepad to verify it. I can select FlySky so I think the .ini is correct. I figured I'd post it in case I was missing something.

Please Log in or Create an account to join the conversation.

More
26 Sep 2013 14:39 #14072 by SLMcc
Update, the good: After 4 days I finally had it working. Being out of ideas and out of desperation I replaced all the wiring. I finally got it to bind. It was unflyable though. The servo movement was extremely jerky. I found a 911.INI here, copied, pasted and renamed it to model1.ini and it bound and the servos were much smoother. Enough so I could mostly hover in the house.

The bad: As I still want sure it was 100% I had the module and wiring out the top of the Tx case. I got a bit too close and hit the module and wiring with the blades. Cut the throttle, checked the heli no issues. I look at the radio and the screen is just black. :sick: It won't do anything. I had to taketthe battery out to get it to shut off. Checked the wiring all aver and it seems fine. Turn it back on and it just beeps and goes black. Take the battery out again, set the throttle stick up some, turn it on and I get the warning screen so I know at least the radio isn't completely dead. Pull throttle down and it locks the radio up. Did that a couple times just to be sure.

Off to the computer I go. Reflash the firmware and test. Same behavior. Format the USB file system, edit the Tx.ini file and replace the model.ini file. No change. Flash the firmware again, format and replace file system. Don't do anything else, turn it on and it works. Edit Tx.ini and it still works. Try to set up a model with FlySky and as soon as I select the protocol the screen goes black, power switch doesn't work, etc.

My only guess now it that when the blades hit the module it ruined it. Does that sound possible?

Please Log in or Create an account to join the conversation.

More
04 Oct 2013 19:41 #14242 by Martian
I would order a new module - make sure you get one with a power amp. Then put it in.

Too many "what ifs" right now. Not worth risking an expensive transmitter over a cheap module that may have been damaged.

HELIs: V929, MCX2, MSR, Nano CP X
TX: Devo 10 (Deviation 3.0.0)

Please Log in or Create an account to join the conversation.

More
04 Oct 2013 21:02 #14247 by SLMcc
I ordered one a few days ago off eBay from a seller I've bought from before with good results. Now just waiting for it to show up from China so I can get it installed and try again.

I miss flying my 911's and I'm thinking about ordering my first CP, a Walkera Super CP or Blade mCP X since I could fly it with the 8s.

Please Log in or Create an account to join the conversation.

More
23 May 2018 10:17 #69373 by han04
i have same module transmitter v911 blue pcb instaled my devo 7e , but canot bind v911 receiver .
maybe coz transmitter modul blue board cant bind v911

Please Log in or Create an account to join the conversation.

Time to create page: 0.037 seconds
Powered by Kunena Forum