Deviating a JoySway

Binding works great. Changing the ID and hitting reinit breaks the connection. Going back to the old ID reconnects. Binds fine with or without an id.

Checked that all four channels are still working, and result in the same throws on my test servo - at least as well as I could tell with the ruler I had at hand.

It tomorrow is a good day for it, I should be able to test it with a wet boat.

Yeah, I saw that one in use in initialize, but figured cutting and pasting random() for a one-time test was easier than trying to find documentation on it.

Anyway, it works fine. Range test out to 120 yards with the micro Rx in the Caribbean. At which point, I'm standing on my neighbors porch and can barely see the thing to figure out if it's responding or not. I can't even get that far away on my pond. My V911 gave out at about half that with the same Tx/Rf module combo.

Much better than the RTS Tx on the water. No control problems whatsoever, and having dual rates on the rudder meant full throw was no longer a water brake.

I'd like to see how well it works with the DF65, but hesitate to ask someone on the other side of the world to test it outside of a nightly build.

Seems like merging this broke the 7E build. Trying to select that protocol on a 7E with an A7105 and NRF24L01 reboots the 7E. You can find an errors.txt file in issue #619 in the bug tracker: www.deviationtx.com/mantisbt/view.php?id=619

I've assigned that issue to you.

Sorry to reply at this thread, but I don't know how to provide feedback at Mantis Bug Tracker.
I can confirm the issue rebooting the 7e when cycle through protocols.
I'm using a custom build including latest DeviationTx code, plus some experimental changes regarding 2 new protocols under development (Hontai protocol and YD-829 protocol).
Could be related with the flash size limit reached at Devo 7e?
My environment is building just fine using GNU Arm GCC tools 4.8 Q1, but I know other versions has problems building now.

Your login here should work on the Mantis bug tracker, and hopefully you can reply there as well as here.

What module(s) do the new protocols use, and what other modules do you have installed in your 7e? And what protocol do you select when that causes the crash?

And yes, building with the 4.9 version of the arm toolchain started overflowing the 7e when the select_source branch was merged in.

Hi mwm
I have installed nRf24l01 and A7105.
The new protocols added, are using nRf24l01 module, but this not should the problem because Greenfly is using only the oficial nightly build, not my modified code with this 2 new protocols.
The issue is reproducible always when you try to select next protocol after Hubsan, so Joysway protocol.

Edit. Finaly I provided feedback at Mantis Bug Tracker.

Thanks PB.