- Posts: 277
Ultimate Devo F12E (devof12e-XMS) builds
- Wene001
- Offline
For help and for the great work
i`ve edited last post.
A2 works fine for me
Please Log in or Create an account to join the conversation.
- xuyuan
- Offline
- Posts: 7
Wene001 wrote: +1 to the list of 4MB F7 Transmitters
EDIT: I tried to use the A2 pin for my a7105 CSN Line and all seems to work fine.
(No error messasges, i`ve tested FrskyX EU, Bayang and Flysky protocol)
Shutdown seems to be normal (1-2Seconds)
That's interesting! I checked the code again and played around with A2 on and off.
The A2 can be set to low and set to high again with in 10ms, but more than 20ms does turn off the TX.
And if I run 10ms on, 10ms off in loop, the leds around button starts to blink.
I guess that A2 is connected to a relay, and it is still on when average voltage is high enough.
Further checking SPI code, the CSN pin does go on and off all the time, maybe that's just enough to hold on ...
but dangerous or?
Maybe deviation developer can clarify that A2 is safe to use or not.
Please Log in or Create an account to join the conversation.
- Wene001
- Offline
- Posts: 277
Please Log in or Create an account to join the conversation.
- vlad_vy
- Topic Author
- Offline
- Posts: 3333
* Improve FrskyX extended telemetry error recovery, from hexfet
* Fix decimal placing for several telemetry values, from TheRealMoeder
DevoF12E-4MB, Devo F7-4MB and Devo F4-4MB, based on Nightly Builds:
Files deleted, see below...
Please Log in or Create an account to join the conversation.
- xuyuan
- Offline
- Posts: 7
Wene001 wrote: on the hardware side it looks that A2 is connected to nothing
maybe the connection is in the other layer of PCB?
the hardware connection in wiki states "output to 0 to shut off Tx" for A2 in all devo TX, e.g.
www.deviationtx.com/wiki/hardware/devof7
Please Log in or Create an account to join the conversation.
- Italy
- Offline
- Posts: 4
I'm new.
I have installed 4MB memory on my Devo F4. All right!
I have installed two additional modules: NRF24L01; A7105; All right!
However, I can only use protocols that do not have auto-binding.
Protocols that have self-binding can not use them, because they are labeled as "re-initialize!"
How can I bind these protocols?
Thanks for the help
Please Log in or Create an account to join the conversation.
- Italy
- Offline
- Posts: 4
However, an observation is needed:
The field has two values << Bind >> and << Re-init >>.
The <<Re-init >> value is typical of a module not installed!
This is fortifying!
The field should have three values:
<< Bind >> With Fixed ID
<< Re-init >> When the module is not installed and then the protocol can not be used.
<< Auto >> When the protocol can be used but we have to do the self-Binding.
Greetings
Please Log in or Create an account to join the conversation.
- Wene001
- Offline
- Posts: 277
Use Notepad++ to edit the file.
Protocols that have a * in the menue are not configured properly and cannot be used
Please Log in or Create an account to join the conversation.
- Wene001
- Offline
- Posts: 277
Of course there could be a via under the Chip.xuyuan wrote: maybe the connection is in the other layer of PCB?
At least for me its working this way without noticeable problems
Please Log in or Create an account to join the conversation.
- vlad_vy
- Topic Author
- Offline
- Posts: 3333
Italy wrote: The field should have three values:
<< Bind >> With Fixed ID
<< Re-init >> When the module is not installed and then the protocol can not be used.
<< Auto >> When the protocol can be used but we have to do the self-Binding.
Greetings
<<Bind>> for protocols with manual bind
<<Re-init>> for protocols with auto bind. Auto bind process usually start for some time after power on (Tx and Rx).
const char *show_bindtext_cb(guiObject_t *obj, const void *data)
{
(void)obj;
(void)data;
return PROTOCOL_AutoBindEnabled() ? _tr("Re-Init") : _tr("Bind");
}
Please Log in or Create an account to join the conversation.
- Italy
- Offline
- Posts: 4
By scrolling through the menu, how do I know if it is a protocol I can use in auto-binding or a protocol that I can not use because the module is not installed?
Please Log in or Create an account to join the conversation.
- vlad_vy
- Topic Author
- Offline
- Posts: 3333
Please Log in or Create an account to join the conversation.
- Italy
- Offline
- Posts: 4
Please Log in or Create an account to join the conversation.
- RubenRC
- Offline
- Posts: 62
Mavic Pro | ARFun 95 | KingKon Tiny7 | Beeductrix | Inductrix FPV | Nano QX2
DEVO F12E | Devo F7
Please Log in or Create an account to join the conversation.
- vlad_vy
- Topic Author
- Offline
- Posts: 3333
Please Log in or Create an account to join the conversation.
- RubenRC
- Offline
- Posts: 62
Mavic Pro | ARFun 95 | KingKon Tiny7 | Beeductrix | Inductrix FPV | Nano QX2
DEVO F12E | Devo F7
Please Log in or Create an account to join the conversation.
- vlad_vy
- Topic Author
- Offline
- Posts: 3333
* Frskyx sequence number algorithm improvement, from hexfet
DevoF12E-4MB, Devo F7-4MB and Devo F4-4MB, based on Nightly Builds:
Files deleted, see below...
Please Log in or Create an account to join the conversation.
- vlad_vy
- Topic Author
- Offline
- Posts: 3333
* Add one txid to DM002 protocol, from goebish
* Add missing "break" to make mux delay working again, from TheRealMoeder
DevoF12E-4MB, Devo F7-4MB and Devo F4-4MB, based on Nightly Builds:
Files deleted, see below...
Please Log in or Create an account to join the conversation.
- vlad_vy
- Topic Author
- Offline
- Posts: 3333
It can be enabled for all Devo transmitters, but I don't know if it has any sense.
Please Log in or Create an account to join the conversation.
- FDR
- Offline
Anyway, I think that now we can make new standard targets for the large flash versions with flash type auto detection.
What do you think do all 3 transmitters (F4, F7, F12E) need an additional build, or only the F12E?
Please Log in or Create an account to join the conversation.
- Home
- Forum
- Development
- Builds
- Ultimate Devo F12E (devof12e-XMS) builds