Try to fix Devo/DSM range issue

Start
Prev
1
Next
End

RandMental
Topic Author
Offline

16 Apr 2014 07:18 - 16 Apr 2014 07:18 #22447 by RandMental

Try to fix Devo/DSM range issue was created by RandMental

PhracturedBlue pushed 1 commit to PhracturedBlue/deviation
2014-04-09
2f438bf - Try to fix Devo/DSM range issue.

Hi PB

I haven't had time to follow all the recent developments and discussions on the forum, but noticed this update on bitbucket.

Is there any reason to distrust V4.0.1 or the latest nighties regarding DEVO and DSM protocols and what is this change trying to fix?

RM

Last edit: 16 Apr 2014 07:18 by RandMental.

Please Log in or Create an account to join the conversation.

FDR
Offline

16 Apr 2014 09:15 #22450 by FDR

Replied by FDR on topic Try to fix Devo/DSM range issue

AFAIK that was OK in the v4.0.1, and went wrong later because of the mods needed for the universal module...

Please Log in or Create an account to join the conversation.

RandMental
Topic Author
Offline

16 Apr 2014 12:26 - 16 Apr 2014 13:27 #22452 by RandMental

Replied by RandMental on topic Try to fix Devo/DSM range issue

Thanks FDR,

Edit: I worked through the code and my concern about the reset which was removed in this change was unfounded, it was implemented as a separate function, called before the init calls.

PB, what do you suggest and what is the confidence level on DSMX and DEVO on the nighties? I fly rather larger models (Heli's and Planes) and need the max range we have come to expect from 150mW

RM

Last edit: 16 Apr 2014 13:27 by RandMental.

Please Log in or Create an account to join the conversation.

PhracturedBlue
Offline

16 Apr 2014 13:42 - 16 Apr 2014 13:43 #22455 by PhracturedBlue

Replied by PhracturedBlue on topic Try to fix Devo/DSM range issue

The protocol code for Devo/DSM haven't changed, just the initialization code has. So once bound, you shouldn't notice any difference. that said:
a) I am not 100% confidence in module initialization. I have sometimes seen that the module is not detected properly when turning on the Tx, or cycling power quickly. This has no risk on flying, since the module detection only happens on power-up.
b) The code has not seen as much testing as 4.0.1. Unless you specifically need the new features in the nightly builds, I would recommend staying with the release for larger models.

Last edit: 16 Apr 2014 13:43 by PhracturedBlue.

Please Log in or Create an account to join the conversation.

RandMental
Topic Author
Offline

16 Apr 2014 13:57 #22457 by RandMental

Replied by RandMental on topic Try to fix Devo/DSM range issue

Thanks PB,

I guess it is then 4.0.1 for now. My V1.3 MultiMode PCBs are on their way and ATTINY's already arrived. I'll then join you on the Nighties again when my module is ready.

RM

Please Log in or Create an account to join the conversation.

MacGyverek
Offline

16 Apr 2014 20:46 #22481 by MacGyverek

Replied by MacGyverek on topic Try to fix Devo/DSM range issue

PhracturedBlue wrote

The protocol code for Devo/DSM haven't changed, just the initialization code has. So once bound, you shouldn't notice any difference

What with version 4795163 ?? You makes some changes with init code only in version 1e2cebf. What if you will roll back to 479516 ??

In my opinion better if you make one stable version before multimodule version.
Nightly have few fixed important bugs, for example:
- Fix crash holding R+ on standard menu.
- Make Devo telemetry more robust
- Add Temperature to DSM telemetry config. Fix DSM telemetry alarms
- reorder channels based on protocol

and many..many....

Please Log in or Create an account to join the conversation.

PhracturedBlue
Offline

16 Apr 2014 23:17 - 16 Apr 2014 23:46 #22488 by PhracturedBlue

Replied by PhracturedBlue on topic Try to fix Devo/DSM range issue

The entire protocol stack was refactored since 4.0.1. I am not going to go back and patch 4.0 at this time. While the actual protocol implementation hasn't changed, a lot of the low-level code was moved around, and the effort to try to make a 4.0.2 patch and to ensure it is as stable as 4.0.1 is more than I have to spend. 4.0.1 has proven to be very stable, and the bugs that exist in it are minor. My recommendation remains to stay with 4.0.1 unless you really need the changes in the nightly builds.

I am not aware of any range issues in the current nightly builds. I have no plans to roll back anything that is in the nightly build. (Note there is an open ticket #533 related to telemetry range. I haven't verified whether this is fixed now or not)

Last edit: 16 Apr 2014 23:46 by PhracturedBlue.

Please Log in or Create an account to join the conversation.

matrixFLYER
Offline

17 Apr 2014 18:07 #22511 by matrixFLYER

Replied by matrixFLYER on topic Try to fix Devo/DSM range issue

PhracturedBlue wrote: The entire protocol stack was refactored since 4.0.1. I am not going to go back and patch 4.0 at this time. While the actual protocol implementation hasn't changed, a lot of the low-level code was moved around, and the effort to try to make a 4.0.2 patch and to ensure it is as stable as 4.0.1 is more than I have to spend. 4.0.1 has proven to be very stable, and the bugs that exist in it are minor. My recommendation remains to stay with 4.0.1 unless you really need the changes in the nightly builds.

I am not aware of any range issues in the current nightly builds. I have no plans to roll back anything that is in the nightly build. (Note there is an open ticket #533 related to telemetry range. I haven't verified whether this is fixed now or not)

what ate the the changes in the nightly that one could need? thank you.

Please Log in or Create an account to join the conversation.

PhracturedBlue
Offline

17 Apr 2014 18:23 #22512 by PhracturedBlue

Replied by PhracturedBlue on topic Try to fix Devo/DSM range issue

Primarily:
* a bunch of new nrf24L01 protocols
* Support for the micro-font display on the devo10/devo7e
* Support for setting DSM* failsafe
* Telemetry display fixes for DSM*
* Support for the multi-module

There are other enhancements/bug fixes, but the above are the only reasons I can think of that would be worthwhile to move to 4.0.1 at this point.

Please Log in or Create an account to join the conversation.

MacGyverek
Offline

17 Apr 2014 19:18 #22518 by MacGyverek

Replied by MacGyverek on topic Try to fix Devo/DSM range issue

To PhracturedBlue...

Do you have any roadmap for nightly code??
Do you have any "to do list" ?? Do you finishing a code or you are on the half road??

Some bug fixes are important for many user. Now, you are focusing in multimodule mod. But in my opinion, many user not will be using this mod

And problem with range and telemetry are much important. This is only my opinion.

On the other hand....big thanks for your all work, for your knowledge.
It's a very good firmware, and DEVO it's a very good TX with your firmware.

Thanks once again. Sorry for my English.

Please Log in or Create an account to join the conversation.

SeByDocKy
Offline

17 Apr 2014 19:26 #22519 by SeByDocKy

Replied by SeByDocKy on topic Try to fix Devo/DSM range issue

MacGyverek wrote: To PhracturedBlue...

Do you have any roadmap for nightly code??
Do you have any "to do list" ?? Do you finishing a code or you are on the half road??

Some bug fixes are important for many user. Now, you are focusing in multimodule mod. But in my opinion, many user not will be using this mod And problem with range and telemetry are much important. This is only my opinion.

On the other hand....big thanks for your all work, for your knowledge.
It's a very good firmware, and DEVO it's a very good TX with your firmware.

Thanks once again. Sorry for my English.

I am thinking the opposite, main users are buying devo + deviationTX in order to instal extra module or in general MM ....

Please Log in or Create an account to join the conversation.

PhracturedBlue
Offline

17 Apr 2014 19:58 #22521 by PhracturedBlue

Replied by PhracturedBlue on topic Try to fix Devo/DSM range issue

The short answer is that:
a) I have very little time to work on Deviation these days.
b) What little time I have is mostly spent doing things that I have fun working on

So releases will tend to be few and far-between for the foreseeable future.

Please Log in or Create an account to join the conversation.

Thomas.Heiss
Offline

27 Nov 2014 22:43 #26607 by Thomas.Heiss

Replied by Thomas.Heiss on topic Try to fix Devo/DSM range issue

> Quote: "what are the changes in the nightly that one could need? thank you."

PhracturedBlue wrote: Primarily:
* Telemetry display fixes for DSM*

There are other enhancements/bug fixes, but the above are the only reasons I can think of that would be worthwhile to move to 4.0.1 at this point.

DSM FlightLog does not work as of Nightly-Build August. Needs re-fix.

www.deviationtx.com/forum/protocol-devel...sm-telemetry-support

Greetings

Thomas

Please Log in or Create an account to join the conversation.

Start
Prev
1
Next
End

Time to create page: 0.047 seconds

Force desktop display