publishing an intermediate release 3.1.0?

rbe2012 wrote: ...
How can we see if the switches are integrated if they are not active? There is no way to detect an open line inside the tx... So we have to store somewhere the information that this tx has the switches mod done.
...

I don't think you have to add anything to the tx.ini file. The user would know what mods have been done to his transmitter.
The switches (connected or not) could have fixed names, and it is up to the user to select the switches for his configuration.

This is pretty much like the differences between any two tx's, they have different types and number of knobs and switches, and if you don't have them you can't use them.

The only difference is that on an unmodded tx you could select switches you don't have.

For the first time users of Deviation, those switches could perhaps be marked with '*' to point out that they are optional hardware.

Oh, and by the way, great idea with the 3.1 release.

Nice, I can contribute to test out the 3.1.0 pre-release in my normal flight.

Ok, just to be clear. The plan is to use the latest nightly (as it is) to be the 3.1 release?

I will soon have an 8s to go along with my 12s and will be updateing to the latest nightly. Or will there be changes to the latest nightly before it goes to 3.1 status?

Kdean wrote: Ok, just to be clear. The plan is to use the latest nightly (as it is) to be the 3.1 release?

I will soon have an 8s to go along with my 12s and will be updateing to the latest nightly. Or will there be changes to the latest nightly before it goes to 3.1 status?

I think the plan is that the current nightly plus the few critical bug fixes will be the 3.1, then the programmers can look at adding features.

RRacer wrote:

rbe2012 wrote: ...

........I don't think you have to add anything to the tx.ini file. The user would know what mods have been done to his transmitter...

the point here is to avoid causing any confusion to the casual user that has NOT done the mod...

cmpang wrote:

RRacer wrote:

rbe2012 wrote: ...

........I don't think you have to add anything to the tx.ini file. The user would know what mods have been done to his transmitter...

the point here is to avoid causing any confusion to the casual user that has NOT done the mod...

Yes, that's why I suggested this:

RRacer wrote: For the first time users of Deviation, those switches could perhaps be marked with '*' to point out that they are optional hardware.

It will be fairly obvious that you have selected the wrong switch when you try to flick it and it's not there!

Kdean wrote: Ok, just to be clear. The plan is to use the latest nightly (as it is) to be the 3.1 release?

I will soon have an 8s to go along with my 12s and will be updateing to the latest nightly. Or will there be changes to the latest nightly before it goes to 3.1 status?

We will fix the most important issues in the nightlies, but not add additional features.
Even if the nightlies are stated to be more stable than the 3.0.0 is there are a few things which are not working correctly or can lead to a reset in bad conditions. Because we know them we can not ignore them...

I have copied it to the new repo.
EDIT: ...and fixed it.

rbe2012 wrote: Ok. I have made the first step and cloned PhracturedBlue's repository into a new clean one called deviation-3.1 .

I have fixed the first issues:

1. PB #422: rename virtual channels in Devo10
2. PB #421: Devo10 German language file causes chrashes
3. Edit: PB #409: Bigbox nut fully implemented on Devo7e/10
4. PB #413: emulator for Devo6
5. PB #414: rework chantest_page
6. PB #423: Trim page doesn't save trim step changes
7. PB #411: Italian language file truncated
8. Bargraphs not working for Devo7e/10

The list is empty now... for a short while.

Here is the list of bugs reported in PBs repo:
#32: Nine-Eagles binding with non-telemetry module
#56: Model won't re-connect when Tx is rebooted.
#60: Fixed ID is not the same assigned by Walkera radios
#195: Virt channel as a source
#334: devo10-v3.0.0 rebooted
#352: AR7200BX Compatibility Issue
#356: Errors.txt is not generated on Devo12
Edit: fixed #360: Currently selected model not saved as current model
#370: Devo 12 sliders
#373: Devo 7e Hangs going to menu
#374: Devo 7e Reboots on moddel resett
#375: DEVO 8s start bug
#382: Devo 12 reboot with telemetry
Edit: fixed #383: Touch screen position
#386: Dev08s Reset while using Flysky V911 protocol
#387: devo10 hangs at bootup
#388: Standard Mixer GUI
#389: Devo 12 Issue
Edit: fixed #402: Telemetry box changed after model change
Edit: fixed #404: toggle_select.c miscalculates scrollbar
Edit: fixed #409: Devo10 reboot in main page config nightly build 07/07/2013
Edit: fixed #411: Italian language file truncated
Edit: fixed #412: 320x240: ok/cancel on reorder page
Edit: fixed #414: Devo6: button test page error due to missing trim buttons
Edit: fixed #415: Wrong elements selected in listbox
Edit: fixed #417: display.c can not handle header_time if no RTC found
#419: Flysky protocol option always Off after reboot on Devo7e
#420: Fatal reboot on DEVO 8S and 2.1.1 deviation
#421: Devo 10 German Language file causes crashes
#422: DEVO 10 - Rename virtual channels
#423: Trim page doesn't save trim step changes
The green colored are already fixed, for the blue colored I have solutions.

I have solutions for #404, #412, #415 and #417 which I can add.
I also have done some work for increasing the accuracy of the touchscreen (#383) in Devo12 which was reported to be bad. I would like to add this too.

What about the rest?
And above only the bugs are listed. What about the proposals, enhancements...?

I have a small fix for V202 protocol, can I make pull request against your repo?

One of the first rules of QA, if you can't reproduce it, it never happened!

I would say that priority one is squash bugs that result in a reboot or loss of control, those things are what causes accidents and injuries.

FDR wrote: #419: Flysky protocol option always Off after reboot on Devo7e
I don't see any protocol options for Flysky at all...

There is one: "WLToys V9x9" can be on or off...

I would say, don't care about those, which you can't reproduce...

Agreed, but I will need some help with Devo7e and Devo10 transmitter (Devo6 has minor imprtance from my point of view).

Thank you for your evaluation.
I will restart work on deviation on Monday (perhaps some hours on Sunday).

What kind of time frame are we looking at for this release? The 8s will be here next week so it will be my first test subject to the 3.1 firmware.

#352: AR7200BX Compatibility Issue
I am using current nightly build with this Rx without any problem. So I think we can just skip this one.

FDR wrote:

rbe2012 wrote: There is one: "WLToys V9x9" can be on or off...

Strange! It is there in the emu_devo10, but missing from the 8 and 12!

I just looked into the code. I will check this.

Kdean wrote: What kind of time frame are we looking at for this release? The 8s will be here next week so it will be my first test subject to the 3.1 firmware.

My personal idea:
I can spend two more days for intense working on deviation (Monday and Tuesday next week), the other days I will have to work and care for the family... I hope I can solve some more issues (esp. #360, #389 which are annoying vlad; take a look in #402 but no way for testing due to a lack of Spektrum telemetry receivers here). Maybe I have a chance to confirm that #352 (AR7200BX) is no general problem this weekend.

So I hope the main issue fixing work will be done until the end of next week so we can publish a 3.1-alpha. We should take one week or two for testing and release the final 3.1 in mid-November.