- Posts: 296
Devo 12S DSMX Range and Telemetry Questions
30 Jan 2015 11:44 #28238
by Indigo
Replied by Indigo on topic Devo 12S DSMX Range and Telemetry Questions
Thank you linux-user and vlad_vy for explaining that line of code. 
Please Log in or Create an account to join the conversation.
05 Feb 2015 01:12 #28404
by SM510
Replied by SM510 on topic Devo 12S DSMX Range and Telemetry Questions
Hi, i'm new my english is not the best, and dont know if its the rigth topik, so sorry but had the sam prolems with range at vbar with tow satelites and devo 8s. i taked this last sulution and everithing works fine (DSMX), but now i insalled a tm1000 (pin out the data cabel, no backup lipo) and now jups the display for volage 1 everytime from 7,4v (BEC) to 24v (Lipo) in voltage 2 nithing happens 0v. i hav try reinstall the update, one groundline for all, rebind without sensor and and and... now is my question is it posebil that its somthing rong with the telmetie protokol, or ist my mistake 
my setup
Goblin 500
2 new generation dsmx satelites
Vbar 5.3pro bind on 22ms
hobbywing platinum v3 100
tm1000 with volta and tempratur sensor
Devo 8s v4.0.1-22961b6
my setup
Goblin 500
2 new generation dsmx satelites
Vbar 5.3pro bind on 22ms
hobbywing platinum v3 100
tm1000 with volta and tempratur sensor
Devo 8s v4.0.1-22961b6
Please Log in or Create an account to join the conversation.
07 Feb 2015 13:38 - 07 Feb 2015 13:39 #28433
by cmpang
I've done a through test on this build, running my r/c boat continuously for two hours in the pond I used to played, with my usual test setting on 3mW Tx output, without any problem. That results that the DSMX protocol with Telemetry OFF is NOW on par (if not better) with my trusty Devo protocol. The amber light did flash at times, but no data link lost as shown my the red led for the whole two hours testing period.
Previous readers may recall my Devo 7e with R601 works in range to 1Km..
So at this point, a big thanks to Indigo, and please confirm that nothing has been changed in the Devo part so that I can shift all my 7e (three sets) to this build for happy flying..
cmPang
Replied by cmpang on topic Devo 12S DSMX Range and Telemetry Questions
Indigo wrote: I'm currently working on DSMX Telemetry problems with Thomas Heiss.
The problems are caused by data integrity issues in receiving telemetry data .
Deviation could also be transmitting occasional bad packets, so I have also added a fix for #594: Data integrity of Channels array
Anyway it would be good to have a number of people test this. Downloads are available here:
bitbucket.org/Indigo1/deviation/downloads
Reversing that change (ie. Enabling On/Off for telemetry mode on Devo7e), makes the module file size too large (max size is 4KB). However, I found another way to reduce code size so Telemetry On/Off should now work.aMax wrote: hardware.c/2014-05-21/
Allow use of txid override on Devo7e. Devo7e will always be in telemetry mode now
I've done a through test on this build, running my r/c boat continuously for two hours in the pond I used to played, with my usual test setting on 3mW Tx output, without any problem. That results that the DSMX protocol with Telemetry OFF is NOW on par (if not better) with my trusty Devo protocol. The amber light did flash at times, but no data link lost as shown my the red led for the whole two hours testing period.
Previous readers may recall my Devo 7e with R601 works in range to 1Km..
So at this point, a big thanks to Indigo, and please confirm that nothing has been changed in the Devo part so that I can shift all my 7e (three sets) to this build for happy flying..
cmPang
Please Log in or Create an account to join the conversation.
14 Feb 2015 06:27 #28662
by cmpang
I have tested DSMX working flawlessly with on this build. As it has fixed the bug in DSM protocol, will it be Incorporated into future nightly builds ?
Big thanks to Indigo anyway...
cmPang
Replied by cmpang on topic Devo 12S DSMX Range and Telemetry Questions
Indigo wrote: I'm currently working on DSMX Telemetry problems with Thomas Heiss.
....
Anyway it would be good to have a number of people test this. Downloads are available here:
bitbucket.org/Indigo1/deviation/downloads
Reversing that change (ie. Enabling On/Off for telemetry mode on Devo7e), makes the module file size too large (max size is 4KB). However, I found another way to reduce code size so Telemetry On/Off should now work.aMax wrote: hardware.c/2014-05-21/
Allow use of txid override on Devo7e. Devo7e will always be in telemetry mode now
I have tested DSMX working flawlessly with on this build. As it has fixed the bug in DSM protocol, will it be Incorporated into future nightly builds ?
Big thanks to Indigo anyway...
cmPang
Please Log in or Create an account to join the conversation.
15 Feb 2015 05:25 #28701
by Indigo
Replied by Indigo on topic Devo 12S DSMX Range and Telemetry Questions
You're welcome, thanks for testing and providing feedback. 
I changed a binding flag in the code about 4 days ago. It works for some people but not others. In next version just uploaded, I've added a 3rd option to DSM2/DSMX Telemetry config setting. For those who have binding problem with Telemetry "On", try changing setting from "On" to new "B2" option.
Either "On" or "B2" will work. Some models prefer one over the other. "B2" is the special case. Why did I call it "B2" I hear you ask? Believe it or not the size of the DSM2/DSMX protocol file on Devo7e is such a tight squeeze only 2 characters would fit, B2 is named after the binding code 0xb2.
I've also included in this build some important patches that will benefit Devo10/7e.
Yes, it will be included in nightly's soon. I will submit a pull request for this before I start working on displaying the new Telemetry values.
Enjoy!
That's great. Did you use a recent build?cmpang wrote: I have tested DSMX working flawlessly with on this build. As it has fixed the bug in DSM protocol, will it be Incorporated into future nightly builds ?
I changed a binding flag in the code about 4 days ago. It works for some people but not others. In next version just uploaded, I've added a 3rd option to DSM2/DSMX Telemetry config setting. For those who have binding problem with Telemetry "On", try changing setting from "On" to new "B2" option.
Either "On" or "B2" will work. Some models prefer one over the other. "B2" is the special case. Why did I call it "B2" I hear you ask? Believe it or not the size of the DSM2/DSMX protocol file on Devo7e is such a tight squeeze only 2 characters would fit, B2 is named after the binding code 0xb2.
I've also included in this build some important patches that will benefit Devo10/7e.
Yes, it will be included in nightly's soon. I will submit a pull request for this before I start working on displaying the new Telemetry values.
Enjoy!
Please Log in or Create an account to join the conversation.
09 Mar 2015 09:26 - 09 Mar 2015 10:11 #29481
by Thomas.Heiss
Hi all,
had a first testing deviation-devo10-v4.0.1-c0b203a_v2.zip.
I tried to bind AR600 + AR6210 with TM1000 in DSMx mode.
On AR600 + AR6210 was successful with "B2". "ON" does not work as stated before.
ON AR8000 I was successfull with "ON" or "B2"
On 200QX I was successful with "ON".
Do you mind further explaining to me what options should be send on a bind for
- 7CH
- AR600
- AR6210
- AR8000 (will have to re-test bind)
> 8CH
either
- telemetry ON
- B2
- OFF
for old + new code?
My feeling is that I get confused about the "&&" combination in the code anyways.
I can't tell for sure at this time what valid possible option scenarios are.
Why does have a user even have to think about "Am I using a 6CH RX + telemetry...oh then I have to choose "B2" because it will NOT work with "ON"" or the user has to test out like me?
I had to re-read this thread just for this case
You would also have to update the Wiki, Manual just tell users about when to use "B2".
If telemetry (TM1000) is bind related to 6CH I would suggest - if possible - to check RX channel numbers and use the right bind mode option (probably 0xb2 in that case).
What was the problem again?
That "0xb2" bind option does not work all the time for some (BNF) receivers?
I bound the AR600 (StrykerQ) with Telemetry "ON" with deviationTX-devo10-v4.0.1-92e1705 and it was working.
However it does NOT work with deviation-devo10-v4.0.1-c0b203a_v2.zip.
Bound AR8000 before with telemetry "ON" (92e1705), works again it c0b203a, even with "B2".
Found some bugs which I will add to the second DSM thread.
Greetings
Thomas
Old code:
New code
Diff
Replied by Thomas.Heiss on topic Devo 12S DSMX Range and Telemetry Questions
vlad_vy wrote:
Indigo wrote: When binding, if protocol is DSMX and number of channels is 7 or less it sends a different code within the binding packet. Presumably to tell rx that telemetry data is not needed.
Not that case. If telemetry enabled, it send 0xB2, without that telemetry unit does not work with 6-7 channels Rx.
But, it can be problem for other Rx (e.g. 7200BX). For that case it sends 0xA2 if telemetry disabled.
Hi all,
had a first testing deviation-devo10-v4.0.1-c0b203a_v2.zip.
I tried to bind AR600 + AR6210 with TM1000 in DSMx mode.
On AR600 + AR6210 was successful with "B2". "ON" does not work as stated before.
ON AR8000 I was successfull with "ON" or "B2"
On 200QX I was successful with "ON".
Do you mind further explaining to me what options should be send on a bind for
- 7CH
- AR600
- AR6210
- AR8000 (will have to re-test bind)
> 8CH
either
- telemetry ON
- B2
- OFF
for old + new code?
My feeling is that I get confused about the "&&" combination in the code anyways.
I can't tell for sure at this time what valid possible option scenarios are.
Why does have a user even have to think about "Am I using a 6CH RX + telemetry...oh then I have to choose "B2" because it will NOT work with "ON"" or the user has to test out like me?
I had to re-read this thread just for this case
You would also have to update the Wiki, Manual just tell users about when to use "B2".
If telemetry (TM1000) is bind related to 6CH I would suggest - if possible - to check RX channel numbers and use the right bind mode option (probably 0xb2 in that case).
What was the problem again?
That "0xb2" bind option does not work all the time for some (BNF) receivers?
I bound the AR600 (StrykerQ) with Telemetry "ON" with deviationTX-devo10-v4.0.1-92e1705 and it was working.
However it does NOT work with deviation-devo10-v4.0.1-c0b203a_v2.zip.
Bound AR8000 before with telemetry "ON" (92e1705), works again it c0b203a, even with "B2".
Found some bugs which I will add to the second DSM thread.
Greetings
Thomas
Old code:
if(Model.protocol == PROTOCOL_DSMX) {
#ifdef MODULAR
packet[12] = 0xb2;
#else
packet[12] = num_channels < 8 && Model.proto_opts[PROTOOPTS_TELEMETRY] == TELEM_OFF ? 0xa2 : 0xb2;
#endif
} else {
packet[12] = num_channels < 8 ? 0x01 : 0x02;
}New code
if(Model.protocol == PROTOCOL_DSMX)
packet[12] = num_channels < 8 && Model.proto_opts[PROTOOPTS_TELEMETRY] != TELEM_B2 ? 0xa2 : 0xb2;
else
packet[12] = num_channels < 8 ? 0x01 : 0x02;Diff
if(Model.protocol == PROTOCOL_DSMX) {
-#ifdef MODULAR
- packet[12] = 0xb2;
-#else
- packet[12] = num_channels < 8 && Model.proto_opts[PROTOOPTS_TELEMETRY] == TELEM_OFF ? 0xa2 : 0xb2;
-#endif
- } else {
+ if(Model.protocol == PROTOCOL_DSMX)
+ packet[12] = num_channels < 8 && Model.proto_opts[PROTOOPTS_TELEMETRY] != TELEM_B2 ? 0xa2 : 0xb2;
+ else
packet[12] = num_channels < 8 ? 0x01 : 0x02;
- }Please Log in or Create an account to join the conversation.
Time to create page: 0.083 seconds
-
Home
-
Forum
-
News, Announcements and Feedback
-
Feedback & Questions
- Devo 12S DSMX Range and Telemetry Questions