Advanced Search

Yes , you are right about all the information, but actually both protocols have been hacked (by Hexfet ) and included into DeviationTx.
The most important question...
What version do you have installed at your Devo 7E?
You need one of the latest version of Deviation Tx team, better the last build from Hexfet at the Syma X11 protocol thread.

sbstnp wrote: I don't get it how it's the radio's fault if you turn it off? It looks to me that the receiver or the FC is misbehaving, if at all.

Personally, I think the failsafe issues are an Rx issue, not a Tx issue. However, since the OrangeRx sets failseafes at bind time, it could be a binding problem. Given that I see different behaviors based on my Tx configuration at bind time, I'm wiling to believe this could be a problem. Be interesting to know if the Rx does the same thing with a licensed Tx.

I don't have the knowledge to fix this. Some of the people participating in this thread do, and are also contributing to the team nightlies, so it could get fixed in a team build. While PBR won't take money for deviationTx work (and I understand why), possibly others aren't so reluctant to turn a hobby into a job. You might try offering a bounty on this bug.

There is some development going on on the firmware. However, with PBR taking a sabbatical, there's not really any central point of collection, and the updates aren't showing up in places only he can update.

I've tried to get everyone who's working on things too coordinate, with a bit of success. If you search the forum for "team" , you'll find references to it. The most important thread is the announcement of the nightly builds .

Changes since the last PBR nightlies include more protocols, module support fixes, GUI improvements, fixes for various GIT issues on PBR's repository, and a new "multirotor" model mode (needs better icons, though). There is some discussion about some DSM telemetry fixes as well, though I haven't checked on that discussion in a while.

mwm wrote: Let me add a data point. I noticed that the Rx on my 200SRX was blinking instead of it's usual solid light. While this Rx is telemetry-capable, it doesn't report transmission issues, but provides vibration and setting reports from the flight control board.

When I bind this Rx with telemetry ON, I get a blinking light on the receiver. Turning telemetry off doesn't change that.

When I bind it with telemetry OFF, I get a solid light on the receiver. Turning telemetry back on doesn't change that.

Using 6 channels at all times.

This is on a Devo10 running the team nightlies (well, sorta - I've got some beta display code; no changes in the protocols directory, though).

Just tried this too.. re-binding with telemetry off. I get less flickering that way (only once or twice as opposed to regulary).. but still doesn't fix the inability to center yaw on a KK board and the constant left yawing.

Let me add a data point. I noticed that the Rx on my 200SRX was blinking instead of it's usual solid light. While this Rx is telemetry-capable, it doesn't report transmission issues, but provides vibration and setting reports from the flight control board.

When I bind this Rx with telemetry ON, I get a blinking light on the receiver. Turning telemetry off doesn't change that.

When I bind it with telemetry OFF, I get a solid light on the receiver. Turning telemetry back on doesn't change that.

Using 6 channels at all times.

This is on a Devo10 running the team nightlies (well, sorta - I've got some beta display code; no changes in the protocols directory, though).

I've moved those off a VM to a real machine that can send mail. I'd now like to make the log results available either to the public or to the developers - at least if they fail. Bitbucket doesn't support mail to team members, which would be the easy way.

Anyone have suggestions about where to put these things? I can host a mail list if anyone is interested. Or arrange to post them to my blog. Not clear that keeping them permanently is such a good idea, but it's possible. Any other suggestions?

I just noticed that this change doesn't seem to be in the team build.

Any chance you can add it? Would you like me to?

Anything else we've missed?

That's just a CC2500. The other RF module names - NRF24L01 and SI4432 are just search bait. I'm surprised they don't list A7105 on it as well. And this kind of thing is a real problem on Banggood, ebay and even Amazon these days. Since they put the search bait in the description as well as the title, there's no real way to tell what you're getting other than buying the damn thing.

There are bugs in that nightly build with module detection that cause problems with missing modules. The team deviationTx nightlies have fixes for those in them, but the distribution directory is sort of a mess. Switching to their latest should help with the missing modules issues, though. Since it also has nrf24l01 specific fixes in it, that's recommended if you want to use that module.

The only way to get all three modules working in one Tx is to use the multimodule. It sounds like you don't have one, so ordering an NRF24L01 won't do you much good unless you also order the MM PCB and parts, or take out one of the two you have. But the second BG link is the right module for either use.

Do not try using the CC2500 (or any RF module, for that matter) without an antenna attached. You risk ruining them if you do so.

Well, the 6s has a smaller screen, so maybe the bigger one on the 12s will be easier to use. You can use the 6 buttons, but they don't work as well on the 6s (and presumably the 12s - it's the same code) as they do on the 10. You have to hit ENT before they work, and it doesn't remember menu positions like it does on the 10 & 7e. The latest team builds have some work on that, so maybe it's better - I'm still running 4.0.1 on the 6s.

If you're talking about the HK DYI module, that should work fine. There is a telemetry capable version of that, but you'll have to figure out how to display the telemetry yourself.

I don't really see a lot of advantage to using either of these over just installing a CC2500. It uses fewer hookups, but you'll have to find them yourself. Maybe if you put this in something like the SLT adapter, so you could avoid having to solder on the 12s.

Hmm. I'm having range/binding issues with my Devo10 and the A7105 module. Are you seeing these issues with just the CYRF, or with the A7105, or something else?

Anyway: I believe the basic protocol is stable. The third party rewrites tend to either work as well as the original, or not at all. For instance, deviationTx is documented as not working with cheap DSM Rx's if you use more than 7 channels, even though Spektrum Tx's work fine under those conditions.

Telemetry is still being worked on. There is support for RSSI, but it's not been integrated into the main or team repositories yet.

You'll need a CC2500 module for it.

According to PBR's transmitter overview , the 12 has the best quality of any of the walkera Tx's. I'd be interested in knowing where you can get one for the price of a shipped Taranis.

mwm wrote: Harry, do you have code to contribute?

Anyway, I've already started making releases from the "team deviation" repo. And you can download them from GDrive .

Still have to verify that updates will get new builds automatically.

Also, I encourage everyone with changes to create pull requests there so we can at least consider integrating them!

no sorry, my coding isn't up to that kind of level yet, but many thanks to yourself and the other guys who are taking up the mantle

all i do is make builds available for the 7e that include features that aren't switched on at build time for the 7e in the official builds.

I took a crack at creating a patch from from both 4.0.1 & the last official nightly, and I don't think that's where this came from. Not sure how to go about getting them into the team nightlies at this point. Again, the .hg directory would help a lot. If nothing else, knowing where you started from would be a good start.

Very cool.Thank you. I've approved it, so 50% of the team thinks it's ready to merge. I gave you write permission to the repo when you asked for it, so you should do the merge as you're more likely to notice if it screws something up. If you want me to, let me know and I'll do it. There should be an automated build done tonight if you get it merged. Or if not, because we've tweaked the makefile.

Any chance of getting you to create a pull request for btoschi's code? I'm going to try and get SebyDocky's FrSky code into one tomorrow.

Thanks.

Going to the nightly should be transparent if you haven't modded your transmitter. If you have, you'll want to check on the new config file hardware.ini which describes such mods. Some of that is in tx.ini in 4.0.1.

4.0.1 is adds support for the multimodule and more protocols with the existing modules. It also includes some bug fixes & display tweaks. I run 4.0.1 on my 6s with no extra modules, and the team deviationTx nightly on my 10 with a multimodule in it.

The team deviationTx build is mostly more of the same as the nightly, but PhracturedBlue is apparently on sabbatical, so it's collecting changes form various other developers so we have fixes and enhancements from multiple people in a single build.

I've started nightly builds from the team deviationTx repository. So far, the changes are minor, but I'm hoping more developers will at least issue pull requests.

You can download them from GDrive .

Harry, do you have code to contribute?

Anyway, I've already started making releases from the "team deviation" repo. And you can download them from GDrive .

Still have to verify that updates will get new builds automatically.

Also, I encourage everyone with changes to create pull requests there so we can at least consider integrating them!

Guys starting in the next couple of days i'm going to be building from the new 'team deviationtx' repo, these guys have taken up the mantle while PB takes a well earned break. if you want me to share these builds let me know and i'll post them as usual.

When one of the people providing new code that I really respect said they didn't know how to create a bitbucket repository, etc., I figured that had to be fixed.

So here's my probably to long and detailed instructions on how to create a pull request for either PhracturedBlue or team deviationTx's deviationTx repository.

It probably needs a lot of work. The best way to suggest changes is to edit the sources on draftIn . However, suggestions here will be given the same weight.

You may add me to your team, id: Indigo1

If I understand you correctly, you want completed changes merged into a group repository: deviationtx / deviation

I've been trying to keep track of changes in multiple people's repositories/pull requests lately, and it's driving me a bit crazy.
In order to deal with this, I've created a team on bitbucket and cloned a copy of PhracturedBlue's repository into it .

My hope is that the people whose repos I'm trying to keep track of will start merging changes into this. I'll be doing that with mine very soon. If you're interested in doing so, please pm me here with your bitbucket id.

And yes, if PhraccturedBlue asks, I'll definitely turn the team & repos over to him!

Edit PB: I have agreed that mwm's repo is now the primary source code, and the nightly autobuilder will build from here. Downloads are available here:
www.deviationtx.com/downloads-new/category/13-nightly-builds