publishing an intermediate release 3.1.0?

vlad_vy wrote: I'm not sure that it will be nice feature. You can forget about switched off RF and then to scratch one's head thinking why nothing works.

Well, it would be obvious, wouldn't it?? Most RX's will start blinking if there is no signal. Plus there could be a warning on the display like blinking TX signal strength or beeps during switch on or .....

@FDR:

That's exactly what I don't want to do. Switching protocols often means switching assigned channels. Just switch the TX on/off, simple and easy....

As far as I have seen the rf chips are not shut down when changing the protocols (one open bug in my repo). So selecting PPM will probably not help.

Screw off the antenna (possible at least for the 6/8/12 and I believe 10) and you should be fine.

EDIT: as I have learned now: don't do that if you don't want to risk hardware failure.

Taking off the antenna while you are for example transmitting with 100mW, will definitely blow up the RF power amp. So if you take off the antenna, and by mistake increase the power, magic smoke will be the result.

Is it not possible to switch off the RF by software? If it isn't possible, just forget about it. If it is possible, maybe think about it or maybe something for the next release.

Pattaya01 wrote: Is it not possible to switch off the RF by software? If it isn't possible, just forget about it. If it is possible, maybe think about it or maybe something for the next release.

What about pressing e.g. the DN button while switching the Tx on? Many transmitters do allow this procedure for range testing purposes and do signaling it with a beep every x seconds. Additionally it could be displayed "Range" instead of (x)xxmW.

Hi,
from a user point of view I can't see any problems with setting the tx-Power to "0". It is less dangerous than setting the Power to "100µW" where you have the possibility to fly and loose control in mid air.

Although I think we shouldn't implement new features in the 3.1.0 release which may have the potential of introducing new bugs.

Today I bought DEVO8s. I want upgrade this radio to Deviation TX 3.1. Can you add upgrade files to bitbucket.org/PhracturedBlue/deviation/downloads ??
I make a final version with MinGW DeviationTX but I not sure if all is ok.

Thx

Pattaya01 wrote: Taking off the antenna while you are for example transmitting with 100mW, will definitely blow up the RF power amp. So if you take off the antenna, and by mistake increase the power, magic smoke will be the result.

Thanks for clarification - I have done so earlier but maybe I was only lucky not having lost something... I mostly run only at 10mW what could have reduced the risk.
I have edited my post above so nobody should try that.

For inteferrence with Wifi, just change the Channel or use auto channel assignment in the Wifi router can solve.the problem. No need to switch off the RF signal.

victzh wrote: I need 2-3 days - middle of work week, you know And if there is a person with 2 working Devos with nRF24L01 and Hisky models to check the interference, that would be great they'd help me in it - my second Devo is not modded yet. I hope there will be no problems - I am going to use FH algorithm similar to DSMX, which should spread frequency efficiently, but to have a test would be great.

I currently have two nRF modded Devo7e with two HiSky helis (FBL100 and FBL80) in my possession. So I am likely your person for testing your addition. We should continue the discussion in the HiSky protocol thread going forward.

@PB so glad to see you back. And hitting the ground running.

2 questions:

- Where can I find the change log for the nightly builds?

- Is there a target date for releasing version 3.1?

I can help answer your first question

goto the following link:
https://bitbucket.org/PhracturedBlue/deviation/commits

Commit "ID" matches the build version name

... and the second:
Deviation-3.1 will probably never released. PB will publish a new version but he mentioned somewhere that the number will be higher.
Since there are not longer only bugfixes integrated (and all my patches are included) I think this is the right way. The new gui for itself gives a good reason for 4.0.

Clear on both questions. Thanks.

PS: any target date for 4.0? (Sorry for asking..)

You can find it here: deviation-3.1/3ace550 (please remove the commented lines at the end).
This works for the WK_protocols, but should be easily transferred for every other protocol if it is useful (but I was only asked for these protocols).
I can send you a patch if needed.

I would like to help with some of the documentation updates... Specifically the Overview, Installation, and File System sections for the Devo 6/8/12 manual.

As a relatively new user, there were a number of questions / issues I had when getting started, that weren't clear, or explicitly stated in the manual. Many of these were probably overlooked due to your familiarity with the project. (or time constraints)

Here are my edits so far. Take a look and let me know your thoughts. I extracted the manual .pdf file into MS Word, made my changes, and then exported it back out as .pdf. Since I am new, I don't know how you handle updates, or merge changes such as this to the "official" manual file.