A7105 bind lockups

I added the 7105 to my Devo 10, and am having some odd issues when binding. Sometimes when it binds - not clear exactly what triggers it - the Tx will lock up hard. So hard that pulling the power supply is the only way to get it to shut off.

It only seems to happen if I either 1) push the "Re-init" button with no bind ID, or 2) Switch to a model that has a not-None bind ID. I also believe it only happens if there is a model to bind to.

I'm not positive about that I've correctly capture either all the preconditions for this, or all the conditions that it could happen under.

I've been flying with it for a while - I was just doing the "turn on the aircraft, turn on the Tx, let it bind" stuff before (they're all WLToys things that expect to work that way, so I do it that way even though I know it's not a good idea). Never had any issues flying, or any problems until I decided to try setting a bind ID on some to see if that would work better.

Checking the solder joins doesn't reveal any obvious issues (well, other than that I'm not very good at such), checking the pins on the A7105 & CYRF module for shorts shows nothing odd except that ground seems to show up on the pin directly "below" it.

Is this actually normal and I should just live with it (seems unlikely)? Anyone got any hints as to which things I might try resoldering short of all of them to fix it? Anyone who's checked the source think switching to the last nightly might help?

Oh yeah - this only happens with the FlySky protocol. The others I use (Walkera and Blade) work fine.

Thanks.

Using the last nightly (or the 3.1.0-beta) is of course a good idea to exclude that you ran into an issue which was fixed already. The last nightly is known to be more stable than 3.0.0, but you will have to redesign your main screen with the new GUI.

vlad_vy wrote: Check if yout A7105 module has pin 8 (RXEN) grounded (8 to 3).

The A7105 (which is the module I used, from a V911 Tx) only has 6 pins, so it's not shorted. The 9-pin version of the 7105 is the XL7105. I had to open the thing up and look to figure out that this was the case.

Since the A7105 doesn't seem to have a RXEN pin listed, could it be pin 4 (which isn't listed as connected)?

Something about the A7105 (aka V911) Tx module I should check on?

thanks,
Mike

I installed 3.10 beta 8 on it. No more bind lockups. So either 1) this was an issue that was fixed in 3.10, or 2) I tweaked something mechanical while poking at the A7105 to not check pin 8.

More reports on running 3.10 with the FlySky protocol in the beta thread.

Thanks to all who replied.

I had a similiar issue. I found that if I put the Devo8 in FMODE1 it would bind and not lockup. If it was in FMODE0 I would have the same problem you had using the 3.0 build

gigrichj wrote: I had a similiar issue. I found that if I put the Devo8 in FMODE1 it would bind and not lockup. If it was in FMODE0 I would have the same problem you had using the 3.0 build

Does FMODE1 have do this for all your models, or just one? And does it have a non-zero output? I have one weird config that uses mix0 and mix2 as outputs, with mix1 as an input (basically, driving a device in two directions) that locked up with mix0 but not mix1. Once.