Advanced Search

As far as I know, you can't create a pull request on bitbucket except from a repository on bitbucket, which means you need an account.
So unfortunately I believe the answer yes. Actually, you should have done that first.

You'll want to create an account, and then create a clone of the repository on bitbucket. Now you can use the URL of your repository to push your changes to it. I'd advise editing .hg/hgrc to set the default path to that URL, as you may want to push to it more than once. Once you've got the changes on bitbucket, you can create the pull request.

If you're thinking about doing more work on the manual, you might add a note asking to be added to the team so you can merge your own changes in the future.

Click the "Links" Link on the left. You'll find a link labelled "deviationTx team repository". Follow that, and you'll get the list of team repositories, and the manual is in "deviation-manual".

Hey you Deviation team,
Let me feed back a little after exploring my Walkera Devo10 upgraded to Deviation.
This is just so good
I have successfully binde 3 of my really important kinds of receivers:
. Walkera 2801, several older but fully active helis
. Devo (7), current quads and OpenPilot things
. Spektrum, future fixed wings, quads and Helis with Satellite receivers
See picture attached.
If, I had bought this Deviation upgrade software for 100 USD, then I would be very happy, really happy consumer. However, I did not spend anything, it was for free.
The interface in TX is more clear, logical, consistent, predictable and well documented (lets not get it to talks of Walkera documentation) than the Walkera standard.
The range of what I now can control wit my Devo 10 Transmitter - old things - current models - and future projects, is greatly enhanced and future prove.
This works for me. Why should it not work for others
THANKS A LOT!

Any chance you could grab the sources and make the changes yourself to show us? It's written with LibreOffice, which is free.

If you're going to do that, it would be even better if you could clone the manual from the team deviationTx repository, make push the changes to your version, and create a pull request.

If you have any questions about doing any of these things, don't hesitate to ask. If you'd rather not, could you use the "Bug Tracker" link on the left and open an issue there with this information?

There's plenty of room for the multimodule in a Devo 10. SebyDocky's tutorial video shows how he put it in his.

Is there an AFHDS 2 protocol module available for deviationTx? It's not in the latest version of the team repository. And I cant seem to find docs on the DataBus.

The superbit stuff looks interesting, but CYRF modules seem awfully dear.

To use an existing protocol, I need a protocol that deviationTx supports, Rx's, and documentation on how to build my own sensors. So far, the best bet seems to be just going with DSM Rx's and using the reverse engineered sensor docs. But adding a robotics style protocol to deviationTx sounds like more fun.

Wene001 wrote: i think indigos patches are at the moment not in the team nightlies

Yes, that is correct. We need to first make sure there are no problems before we add this Telemetry update to team nightlies.

FYI: I did a merge with team nightly 2015-03-24 before publishing these recent test builds so it will have all but the most recent updates.

i think indigos patches are at the moment not in the team nightlies

Today I have builded the latest Deviation Team firmware with 7-ch HiSky patch. Tested on HCP80V2 - 3D/6G switch work correctly.

Is the complete DSM work merged into the team nightlies?

FDR wrote: I was talking about the code change, but I don't know if it is in the trunk...

I know we got at least one such mod into the team trunk.

What's the license on these icons? I'd like to add them to the team build, but we need an appropriate license.

rafael wrote: BTW, is there a way to use 6 icons on a mixed FMODE switch? With ELEV D/R and FMODE I got 6 flight modes, but I don't know how to display one different icon for each mode..

The way to get six icons now is to use multiple toggles on the main page. You can try putting them in the right place and having blank icons on the switches when another switch is setting the mode, but that doesn't seem to work very well.

I've got a pull request in to the team repository that rewrites the toggle code to handle displaying multiple icons based on more than one switch. It needs some code cleanup before being merged, and I've been dealing with health issues so haven't gotten to that yet. It was designed to handle such things, though may take some virtual channels to create the appropriate switches. If you'd like to try it out, I can create a build for your Tx - just tell me what it is. Be warned that model files written by this won't have toggle icons at all if loaded into versions without it.

OK, I finally found a way to get the GIMP program to save in RGB565, although I had to install a script and some palettes, then use other options for it to work. The result isn't exactly the best in the world, but if anyone wants to make any adjustments to it, they're welcome to it.

So here is my Team Associated RC18B2 buggy icon, all working on my Devo 7E, and I'll see if I can make it better as time goes by.

Please link a specific file that didn't work for you. Each file I've tried to download has worked fine.

EDIT: SOLVED! Only the newest 2 are available.

Thanks for all the work!

Indigo wrote: The nightly builds from deviationTx are now available here:

Nightly builds

While they're listed there none are available to d/l. I was looking to update to the newest nightly for me 7E (I also tried the 10 version and got the same error)

Message

Error while downloading file File not found on server

The nightly builds from deviationTx are now available here:

Nightly builds

mwm wrote: You can download them from GDrive .

Hi, repository is empty from some days ago, is it normal ?

Thanks

Some of the issues have been fixed in the team repository. For instance, 578 .

Do you have preferences for how these should be handled?

I no longer run servers at home - I'm doing the builds on my desktop. I did set up jenkins and get it to do some builds, but never converted to it. I'm using a shell script to do them.

I have a ubuntu 10.4 VM I used to use for builds, and doing an occasional build that way is ok. But doing development on it is a real pain. So I ported the build system to my desktop.

The Makefiles have a number of non-portable assumptions built into them. I got the easy ones out, but I'm not sure they can all be eliminated for both ARM & desktop builds, so dealt with some of them by creating an environment for deviation builds that is unusable for most other software. This also involved switching to GCC 5.0, whose new warnings turned up some interesting bugs.

I managed to get the windows binaries to build and execute, but they always come on in USB mode for some reason.

Any chance you can start a second set of nightlies from the team repository? Not only would that fix the issue with providing windows binaries, but it would also get the distribution off of Google Drive, which was temporary hack until you decided what was going to be done with this repository.

Ok, I've got a build that can be used to experiment with. The devo7e zip is attached. I've also attached a v959 model file for a devo6s that uses these features. Source can be found in ssh://hg@bitbucket.org/mwm/deviation-team, on the wltoys-bits branch.

Note 1: this is a build based on the latest team nightly build. Please install the file system as well as the DFU. If you've been running 4.0.1, you'll have to edit hardware.ini, not tx.ini, to enable your extra modules.

Note 2: This will turn the WLToys options OFF on all existing FlySky protocol models. Set it to V9x9 to get the old behavior.

The new feature is that the WLToys option now has two settings, "v9x9" which has the old code in it, and "Bits", which is the new behavior. The new code takes the value of channels 5-8, divides by 10, throws out the high order bits, and then ors those into the appropriate parts of channels 1-4, respectively.

The v959 model works properly for lights and camera control. I can't test flip, as my v959 hasn't been flight-worthy in quite a while (it's actually in pieces for another project). Camera control uses mix0 and mix2 to toggle video & photo modes. Lights are on GEAR1, and flip is on FMOD1. Note that these may need to be toggled on/off to trigger the device they control.

Here's my channel 8, done as three mixes so it's clear what's going on:

All the curves are fixed. We set the output to 0 in the first mixer, so everything is off by default. The second mixer, enabled by FMOD1, sets the output value to 10, which is flip mode. The third mixer uses an add mux to add the value of 20, for the lights.

The V915 uses the same two values in channel 8 for it's lights and "turbo" mode, except they are backwards: turbo uses 20, and the lights use 10. I managed to not notice that turbo was being enabled before, so we only need to find the camera control buttons on the V912.

I would be very surprised if they are set via channel 7. Don't test it until after you've exhausted 5, 6 and the other two values (40 and 80) for 8. And before you do, take the blades off your propeller.

Welcome back! Good to see you again.

I think items 2 & 3 can be addressed by the same issue: an official group repository that has more admins. I think more people with a commit bit would help as well. That's why I created team deviationTx - to try and get all the ongoing development work in one place while you were busy elsewhere. I think it's mostly been successful.

I'd like to see the team repository become the official one. That's why I made you an admin. However, that requires your blessing of the idea, as well of the rules for committing code (those are in the wiki). Until you decide about that, further discussion would be premature.

If you don't like that idea, let me know what you think should happen to the team, and I'll take care of it.