- Posts: 19
Source code bug report about DEVO7E binding....
- galee
- Topic Author
- Offline
DEVO7E seems something wrong about binding when use FIXID...
These days, I'm writing a Chinese Version for DEVO7E, the whole GUI is rewritten to reduce size, and the protocols is porting from PhracturedBlue's Deviation source.
When porting to devo.c (located at src\protocol), I found there may be a writing mistake:
I thought the code means when Model.fixed_id is zero, the tx will generate a random id and use_fixed_id will be zero (clear by initialize line 507), but when Model.fixed is set, use_fixed_id should be no-zero.
And there is another place make me confuse... function bind() line 491, is it mean whatever the Model.fixed is, the use_fixed_id is always 1?
Hope for answer~
Please Log in or Create an account to join the conversation.
- galee
- Topic Author
- Offline
- Posts: 19
Please Log in or Create an account to join the conversation.
- yoshi163
- Offline
- Posts: 9
Please Log in or Create an account to join the conversation.
- ColdFire
- Offline
- Posts: 45
"And there is another place make me confuse... function bind() line 491, is it mean whatever the Model.fixed is, the use_fixed_id is always 1?"
if (PROTOCOL_AutoBindEnabled())
PROTOCOL_Init(0);
else
PROTOCOL_Bind();
and
case PROTOCMD_CHECK_AUTOBIND: return Model.fixed_id ? 0 : (void *)1L;
So which means bind function is only called whenever Model.fixed_id != 0
"but when Model.fixed is set, use_fixed_id should be no-zero."
It probably does not matter (though it is worth to make clear) for the value to be set here because bind function will set it to non-zero anyway.
galee wrote: As I metioned in the topic : www.deviationtx.com/forum/3-feedback-que...e6b-zip-doesn-t-work
DEVO7E seems something wrong about binding when use FIXID...
These days, I'm writing a Chinese Version for DEVO7E, the whole GUI is rewritten to reduce size, and the protocols is porting from PhracturedBlue's Deviation source.
When porting to devo.c (located at src\protocol), I found there may be a writing mistake:
I thought the code means when Model.fixed_id is zero, the tx will generate a random id and use_fixed_id will be zero (clear by initialize line 507), but when Model.fixed is set, use_fixed_id should be no-zero.
And there is another place make me confuse... function bind() line 491, is it mean whatever the Model.fixed is, the use_fixed_id is always 1?
Hope for answer~
Please Log in or Create an account to join the conversation.
- ColdFire
- Offline
- Posts: 45
galee wrote: here is some snapshot about the Chinese firmware, is there anybody can give me a Traditional Chinese 12dot font file? If has pls send to This email address is being protected from spambots. You need JavaScript enabled to view it.
Please Log in or Create an account to join the conversation.
- galee
- Topic Author
- Offline
- Posts: 19
so I wrote another firmware, if you are chinese too, can visit 5IMX to get newest message.
Please Log in or Create an account to join the conversation.
- galee
- Topic Author
- Offline
- Posts: 19
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
As for the rest, I'm sorry, but I will not support you until your code is open-sourced. The license for Deviation is very clear. If you are using parts of deviation for your code you must license it under the GPLv3. Otherwise you are free to use the documentation I've written in the docs/ directory as the basis for writing your own protocol code from scratch.
Once you've made your code available, I'll be happy to discuss how deviation works.
Please Log in or Create an account to join the conversation.
- galee
- Topic Author
- Offline
- Posts: 19
Please Log in or Create an account to join the conversation.
- ColdFire
- Offline
- Posts: 45
galee wrote: Yes, I will open the source in few days. another question, I don't know how to post it , may I email it to you, or post in this forum as a attachment?
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
All that use_fixed_id does is select whether the upper nibble of pkt[10] is 0x00, 0x80, or 0xc0
From Devo.txt:
The upper nibble 0x00 corresponds to non-fixed-id, and 0x80 corresponds to using a fixed-id
An upper nibble of 0xc0 is used to indicate fixed-id binding is in progress
As you noted we should have set 'use_fixed_id = 1' when Model.fixed_id is non-zero. This bug has been there since last August though. Apparently Walkera Rx ignore the difference in this byte when using a fixed id.
Please Log in or Create an account to join the conversation.
- galee
- Topic Author
- Offline
- Posts: 19
it'ok now... but it seems not a good modification, the code can be more pretty...
Please Log in or Create an account to join the conversation.
- dc59
- Offline
- Posts: 799
Please Log in or Create an account to join the conversation.
- PhracturedBlue
- Offline
- Posts: 4402
Please Log in or Create an account to join the conversation.
- galee
- Topic Author
- Offline
- Posts: 19
Please Log in or Create an account to join the conversation.
- galee
- Topic Author
- Offline
- Posts: 19
Please Log in or Create an account to join the conversation.
- dehalo
- Offline
- Posts: 35
Please Log in or Create an account to join the conversation.
- galee
- Topic Author
- Offline
- Posts: 19
Thank u again very much.
And during debug of DSMX, I found the 'model' has been set to zero, I try to change the model add to CYRF_MfgId[2] instead of CYRF_MfgId[3], it seems work well.
Please Log in or Create an account to join the conversation.
- HappyHarry
- Offline
- Posts: 1136
phil
Please Log in or Create an account to join the conversation.
- cctsao1008
- Offline
- Posts: 5
where can I get the file system ?
thank you.
Please Log in or Create an account to join the conversation.
- Home
- Forum
- Development
- Protocol Development
- Source code bug report about DEVO7E binding....