Deviation v5.0.0 build with latest protocols

More
02 Dec 2016 14:19 #56447 by aMax

vlad_vy wrote: ...........................cut............

P.S. If it all has any sense. From the begining I do it for myself only. And up to now I have illusion that I do it for myself only, since I have almost zero responce from users.


I understand your feelings, but wintertime is not the ideal season for excessive testing outdoors. So you may not get much responce
for the main protocols beside the toys...;)

Anyways, I am glad you did some changes that where requested for a long time.
Keep going.

Devo7e, TaranisQ X7, R9M , 4in1 MM, Futaba FC18plusV3.2 & DFT/FLD-02

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

More
02 Dec 2016 14:24 #56448 by MacGyverek
Replied by MacGyverek on topic Deviation v5.0.0 build with latest protocols
I using your build with dsmx fixes and all working good, without any issue. But if some version working good, then I don't make a updates for new version (like for Frsky protocol and toys protocol). Question: What is changed in version "Fixed touch on XY graphs"?? This changes its for DEVO8S ??

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

More
02 Dec 2016 14:33 #56450 by vlad_vy
Replied by vlad_vy on topic Deviation v5.0.0 build with latest protocols
"Fixed touch on XY graphs" - if you touch XY graph by stylus, it call XY graph properties. It worked at v4.01, but somewhere on the way to v5.0.0 this function stop to work. It's for Devo6, Devo8 and Devo12.

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

More
02 Dec 2016 15:41 - 02 Dec 2016 15:45 #56454 by victzh
Vlad,

if you take a look at what changed since v5.0.0 in the BRANCH_5.0, the modifications are really minimal:
github.com/DeviationTX/deviation/compare/v5.0.0...BRANCH_5.0

PhracturedBlue fixed 5 bugs, added back one box. Me and goebish fixed protocols, this is already covered in your code.

We can make another branch, but I think it's OK to base it on BRANCH_5.0 - these fixes are in the 5.0 release anyways.
Last edit: 02 Dec 2016 15:45 by victzh. Reason: Change commit into tag for clarity

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

More
02 Dec 2016 16:45 #56457 by vlad_vy
Replied by vlad_vy on topic Deviation v5.0.0 build with latest protocols
I will look to BRANCH_5.0 once again. Last time it was about two months ago.

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

More
02 Dec 2016 18:00 #56459 by vlad_vy
Replied by vlad_vy on topic Deviation v5.0.0 build with latest protocols
Tested locally with BRANCH_5.0. Do not fit to Devo7e, overflowed by 28 bytes. That's why I revert some code back to v5.0.0.

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

More
02 Dec 2016 18:09 - 02 Dec 2016 18:11 #56460 by aMax
FrskyD8....short question, has the scaling for the rssi value on the telemetry display been recalculated?
With version 2016-11-02 I have little less, now 121 to prior 115 at two meter distance.

Devo7e, TaranisQ X7, R9M , 4in1 MM, Futaba FC18plusV3.2 & DFT/FLD-02
Last edit: 02 Dec 2016 18:11 by aMax.

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

More
02 Dec 2016 18:46 #56462 by vlad_vy
Replied by vlad_vy on topic Deviation v5.0.0 build with latest protocols
You need ask hexfet at Protocol Development.

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

More
02 Dec 2016 19:00 #56463 by hexfet
No change. It's just the raw RSSI byte received in the telemetry packet, same as it has been.

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

More
03 Dec 2016 06:42 - 15 Dec 2016 10:43 #56479 by vlad_vy
Replied by vlad_vy on topic Deviation v5.0.0 build with latest protocols
Fixed alignment of stick calibration text on 320x240 screen

PhracturedBlue

(03.12.2016) Firmware DFU file only, you can get other components from official v5.0.0 release.
www.deviationtx.com/downloads-new/category/398-deviation-5-0-0



Files deleted, see below...
Last edit: 15 Dec 2016 10:43 by vlad_vy.

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

More
03 Dec 2016 14:58 - 05 Dec 2016 10:08 #56482 by vlad_vy
Replied by vlad_vy on topic Deviation v5.0.0 build with latest protocols
Now source code for "Deviation v5.0.0 build with latest protocols" can be found at main repository -> BRANCH_5.0

github.com/DeviationTX/deviation/tree/BRANCH_5.0
Last edit: 05 Dec 2016 10:08 by vlad_vy.

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

More
04 Dec 2016 23:35 #56528 by SuperFLY
Replied by SuperFLY on topic Deviation v5.0.0 build with latest protocols
Guys I do not see the 5.0 DFU file in the download?

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

More
05 Dec 2016 04:22 #56529 by vlad_vy
Replied by vlad_vy on topic Deviation v5.0.0 build with latest protocols
I think that only "main" branch compiled for Nightly builds. I don't see any compilation listing for "BRANCH_5.0".

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

More
05 Dec 2016 17:21 #56554 by victzh
Actually, Travis CI builds every pull request and push to the main repository, BRANCH_5.0 including. It discards artifacts afterwards, but we can think of uploading them somewhere instead.

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

More
14 Dec 2016 09:13 #56808 by vlad_vy
Replied by vlad_vy on topic Deviation v5.0.0 build with latest protocols
It's impossible to use Fix telemetry items loading for CFlie and AFHDS 2A protocols for v5.0.0 build, it doesn't fit to Devo7e.

travis-ci.org/DeviationTX/deviation/builds/182605292

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

More
14 Dec 2016 16:21 #56820 by victzh
Isn't this TELEMETRY_SetTypeByProtocol redundant? Every protocol with telemetry sets telemetry type from initialization method to correct value through TELEMETRY_SetType. Why do we need this centralized call at all?

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

More
14 Dec 2016 17:04 - 14 Dec 2016 17:16 #56822 by vlad_vy
Replied by vlad_vy on topic Deviation v5.0.0 build with latest protocols
I think it used at time model setup, protocol selection do not initialize protocol, so we need call TELEMETRY_SetTypeByProtocol() for changing telemetry screen, telemetry config screen and telemetry variables for main screen boxes.

By the way, victzh, can you review warning at master branch:
target/common/stm32/spi_flash.c: In function 'CS_LO':

target/common/stm32/spi_flash.c:72:9: warning: implicit declaration of function 'SPISwitch_UseFlashModule' [-Wimplicit-function-declaration]

         SPISwitch_UseFlashModule();

         ^

target/common/stm32/spi_flash.c: In function 'SPIFlash_Init':

target/common/stm32/spi_flash.c:107:9: warning: implicit declaration of function 'SPISwitch_Init' [-Wimplicit-function-declaration]

         SPISwitch_Init();

github.com/DeviationTX/deviation/commit/...cf35176d317aff9e793e
Last edit: 14 Dec 2016 17:16 by vlad_vy.

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

More
15 Dec 2016 10:47 - 16 Dec 2016 08:43 #56834 by vlad_vy
Replied by vlad_vy on topic Deviation v5.0.0 build with latest protocols
Changed counters type to u32 or s32 for compacting binary ("config" folder only).

After that I can fit Fix telemetry items loading for CFlie and AFHDS 2A protocols to Devo7e.
travis-ci.org/DeviationTX/deviation/builds/182605292

(15.12.2016) Firmware DFU file only, you can get other components from official v5.0.0 release.
www.deviationtx.com/downloads-new/category/398-deviation-5-0-0



Files deleted, see below...
Last edit: 16 Dec 2016 08:43 by vlad_vy.

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

More
15 Dec 2016 17:17 #56854 by victzh
Vlad, I'm preparing large pull request with my SPI switch code, it handles this warning (as some others, already handled by your recent fixes - you was first :-) ).

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

More
15 Dec 2016 18:47 #56864 by victzh
We really need to test dropping out the call to TELEMETRY_SetTypeByProtocol, it should work for everything except FrSky - they for some reason do not set the type themselves.

Other protocols set the type soon enough after you selected them so this short period of incorrect telemetry type should not affect other pages.

Unfortunately, I have no telemetry capable receiver myself.

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

Time to create page: 0.052 seconds
Powered by Kunena Forum