publishing an intermediate release 3.1.0?

Hexperience wrote: Often what looks like duplicate files and folders is for the compile process. The target variables need to be there or you might not be able to compile for that particular target.

Yes, but only a few files are needed (the content of the modelico and the media folder). Most files are created by the make process.
I am sure we could reduce the files, but they don't harm and they have no influence on building (except you forget some intermediate files somewhere when you build zips ).
When I have some time I will check this, but very likely I will keep the files anyway.

I removed the files (filesystem/devo10/layout/*.ini) from the repository after testing that they are really created newly.

I published a new beta-04 which has only an improvement in the boundary checking in Devo10 and Devo7e.
I have no way to test it out so I ask for your support. Please download the dfu at the usual location in my bitbucket-repo). Please use the attached lang.ger.txt file (save as lang.ger) as language file for German because it contains strings that seem to crash deviation on a real tx.
Go to tx menu, change language to German ("Deutsch"), go to model menu ("Modell Menü") and scroll down. If you get around and the tx does not reset the fix I made was good.

rbe2012 wrote: I removed the files (filesystem/devo10/layout/*.ini) from the repository after testing that they are really created newly.

Thanks rbe2012, these are just little things that bug me. That is why when I made my pull request I set status to Trivial. I also hate editing things more than once so the redundant files were bothersome.

I spend most of my time looking at the .ini files since I plan on expanding the documentation starting there. I think it will be the most useful to deviation "power" users. I am of very little value looking at C code since I never took any programming classes, I only know html and php reasonably well.

May be someone more knowledgeable than me can answer a question in PB's absense:

If you look at the protocol code, every protocol has empty deinitialization code. It leaves the chip on even if you switch model to one that uses another chip, so it takes power and can possibly interfere with other chips.

Do you think it would be useful to equip the protocol code with such a turn off, or handle it for the protocol at the level of chip driver?

vlad_vy wrote: RBE, can you add option to DSM2 protocol? 'Resolution' = 1024 (2048), by default '1024', unactive (grayed out), and activated if number of channels > 7. Also, have sense automatically switch resolution to 2048, and make unactive (grayed out), if number of channels > 12.

Yes I can, but didn't we want to implement only bugfixes?

victzh wrote: Do you think it would be useful to equip the protocol code with such a turn off, or handle it for the protocol at the level of chip driver?

Yes, of course. I have it somewhere on my list to examine what happens. If there is no shutdown it should be implemented, at least to avoid rf conflicts.

OK, I can cover all the nRF24L01 based protocols, namely V202 and can look into how to turn off other chips. Usually it is just reset the configuration to zero, or reset chip with a special signal, like CYRF_Reset() does.

It is a minor issue, people turn off their TXs often, but nevertheless for the purpose of cleanliness we better do this.

@rbe2012 I have a fix for V202 protocol in your pull request queue. It is very minimal, can you take a look at it, please?

Sorry for letting you wait for so long...

I merged your changes and uploaded a new beta-07.

No problem, I will have some more - proper de-initializing of V202, take a look at other protocols as well.

Yesterday I have uploaded the beta-08 to my repo. I am curious if there are still problems with reboots on Devo10.
I don't own one so I can't test and ask if somebody is willing to do.
Just install the beta-08 and the attached German language file (rename to lang.ger of course)



Switch language to German, walk through all pages and sub-pages and post the result (please even if everything is fine). There will be some strings shortened - don't worry about that, this will be fixed later when I have the results.

Just tried beta-8 on my Devo8S, and found the Button Monitor screen is just a mess. PB's nightly build do not have this problem.

This is no problem. It is an improvement.
All buttons are positioned where they are at the real tx. So it is much easier to get an overview.
As often it's a question of taste and personal preferences.

rbe2012 wrote: I have fixed some issues. Here is the actual list of open issues from PB:
Here is the list of bugs reported in PBs repo:

#387

devo10 hangs at bootup

probably defective hardware - won't fix

I just installed Beta 08 tonight on my Devo 10 and it works fine. I downloaded 3.0 when it was first released and the 12Aug nightly about a month ago. I never found any bugs with those either.

Lasakro, thank you for testing.
Would you do me an additional favor: use the German language file I have uploaded above and walk through the menus? You can do that blindly without knowing the German words, just start with a empty model and don't use it for flying because it is possible that the tx resets. It it crashes somewhere it is very likely that this will happen in the tx config or the main menu of model config.
Simply change back to English, there are those issues not reported.
I have only one report that an issue I try hard to fix is not gone, and I would highly appreciate to get a confirmation with a second tx.

rbe, I will do the same test this morning.

1. In Telemetrieeinstellung when changing Temperatur from Fahrenheit to Celcius the last 't' of Farenheit stays on screen until you scroll down. I believe this is the same in all languages. Would it make more sense to change the option to read C° / F°. As these symbols are universal there would never be a need to translate them. The degree symbol is 0176 in many ascii fonts.

2. When you select long ENT to get to the screen layout, is MOVE in the top right corner really Move in German? I cannot read German.

I did not have any unexpected crashes.

Using Beta 08 on the Devo 10 German was not available as a menu option. I overwrote that file with the lang.ger file above and still not listed as an option. Copied the file from 3.0 and same thing.