- Posts: 277
Ultimate Devo F12E (devof12e-XMS) builds
- Wene001
-
- Offline
Less
More
14 Jul 2017 13:53 #63439
by Wene001
Replied by Wene001 on topic Ultimate Devo F12E (devof12e-4MB) builds
Thanks Vlad
For help and for the great work
i`ve edited last post.
A2 works fine for me
For help and for the great work
i`ve edited last post.
A2 works fine for me
- xuyuan
-
- Offline
Less
More
- Posts: 7
14 Jul 2017 21:25 #63446
by xuyuan
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.
Replied by xuyuan on topic Ultimate Devo F12E (devof12e-4MB) builds
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.
- Wene001
-
- Offline
Less
More
- Posts: 277
15 Jul 2017 05:34 #63457
by Wene001
Replied by Wene001 on topic Ultimate Devo F12E (devof12e-4MB) builds
on the hardware side it looks that A2 is connected to nothing
- vlad_vy
-
Topic Author
- Offline
Less
More
- Posts: 3333
15 Jul 2017 06:55 - 01 Aug 2017 13:47 #63458
by vlad_vy
* 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...
Replied by vlad_vy on topic Ultimate Devo F12E (devof12e-4MB) builds
* 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...
Last edit: 01 Aug 2017 13:47 by vlad_vy.
- xuyuan
-
- Offline
Less
More
- Posts: 7
15 Jul 2017 23:08 #63475
by xuyuan
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
Replied by xuyuan on topic Ultimate Devo F12E (devof12e-4MB) builds
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
- Italy
-
- Offline
Less
More
- Posts: 4
17 Jul 2017 18:46 #63496
by Italy
Replied by Italy on topic Ultimate Devo F12E (devof12e-4MB) builds
Good morning
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
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
- Italy
-
- Offline
Less
More
- Posts: 4
17 Jul 2017 19:36 #63497
by Italy
Replied by Italy on topic Ultimate Devo F12E (devof12e-4MB) builds
I understand how to make auto-binding with the following video.
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
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
- Wene001
-
- Offline
Less
More
- Posts: 277
17 Jul 2017 21:27 - 17 Jul 2017 21:30 #63499
by Wene001
Replied by Wene001 on topic Ultimate Devo F12E (devof12e-4MB) builds
Do you have uncommented the Modules in Hardware.ini?
Use Notepad++ to edit the file.
Protocols that have a * in the menue are not configured properly and cannot be used
Use Notepad++ to edit the file.
Protocols that have a * in the menue are not configured properly and cannot be used
Last edit: 17 Jul 2017 21:30 by Wene001.
- Wene001
-
- Offline
Less
More
- Posts: 277
17 Jul 2017 21:31 #63500
by Wene001
At least for me its working this way without noticeable problems
Replied by Wene001 on topic Ultimate Devo F12E (devof12e-4MB) builds
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
- vlad_vy
-
Topic Author
- Offline
Less
More
- Posts: 3333
18 Jul 2017 03:39 - 18 Jul 2017 03:42 #63505
by vlad_vy
<<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).
Replied by vlad_vy on topic Ultimate Devo F12E (devof12e-4MB) builds
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");
}
Last edit: 18 Jul 2017 03:42 by vlad_vy.
- Italy
-
- Offline
Less
More
- Posts: 4
18 Jul 2017 12:20 #63510
by Italy
Replied by Italy on topic Ultimate Devo F12E (devof12e-4MB) builds
Protocols for uninstalled modules are referred to as << Re-init >> exactly as protocols for installed modules that require auto-bind.
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?
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?
- vlad_vy
-
Topic Author
- Offline
Less
More
- Posts: 3333
18 Jul 2017 13:47 - 18 Jul 2017 13:50 #63511
by vlad_vy
Replied by vlad_vy on topic Ultimate Devo F12E (devof12e-4MB) builds
There is * (asterisk) in front of protocol names for not installed modules.
Last edit: 18 Jul 2017 13:50 by vlad_vy.
- Italy
-
- Offline
Less
More
- Posts: 4
18 Jul 2017 14:49 #63512
by Italy
Replied by Italy on topic Ultimate Devo F12E (devof12e-4MB) builds
Thanks
- RubenRC
-
- Offline
Less
More
- Posts: 62
20 Jul 2017 18:42 #63533
by RubenRC
Mavic Pro | ARFun 95 | KingKon Tiny7 | Beeductrix | Inductrix FPV | Nano QX2
DEVO F12E | Devo F7
Replied by RubenRC on topic Ultimate Devo F12E (devof12e-4MB) builds
Can I is my devo.fs file from my f12e on F7 or do I need to use the F7 and add my models in it and reapply? I can't get DSM2 or DSMX to work. I get a message saying missing mod when I try using those protocols.
Mavic Pro | ARFun 95 | KingKon Tiny7 | Beeductrix | Inductrix FPV | Nano QX2
DEVO F12E | Devo F7
- vlad_vy
-
Topic Author
- Offline
Less
More
- Posts: 3333
21 Jul 2017 05:18 #63539
by vlad_vy
Replied by vlad_vy on topic Ultimate Devo F12E (devof12e-4MB) builds
No, devo.fs for Devo F12E and Devo F7 are totally different. Try to use Devo protocol, if it's OK, you need renew "protocol" folder in devo.fs with protocols for corresponding firmware. At other case you have problem with CYRF6936 module connection.
- RubenRC
-
- Offline
Less
More
- Posts: 62
21 Jul 2017 05:54 #63541
by RubenRC
Mavic Pro | ARFun 95 | KingKon Tiny7 | Beeductrix | Inductrix FPV | Nano QX2
DEVO F12E | Devo F7
Replied by RubenRC on topic Ultimate Devo F12E (devof12e-4MB) builds
Vlad, I figured that out before I read your post. My Devo F7 is up and running! Thanks for the help I pulled the OG Devo.fs file from the nightly build and just moved my models into the folder and ran the build, copy and pasted and vola no more protocol error and my birds are bound and flying high!
Mavic Pro | ARFun 95 | KingKon Tiny7 | Beeductrix | Inductrix FPV | Nano QX2
DEVO F12E | Devo F7
- vlad_vy
-
Topic Author
- Offline
Less
More
- Posts: 3333
01 Aug 2017 13:49 - 18 Aug 2017 04:27 #63662
by vlad_vy
* Frskyx sequence number algorithm improvement, from hexfet
DevoF12E-4MB, Devo F7-4MB and Devo F4-4MB, based on Nightly Builds:
Files deleted, see below...
Replied by vlad_vy on topic Ultimate Devo F12E (devof12e-4MB) builds
* Frskyx sequence number algorithm improvement, from hexfet
DevoF12E-4MB, Devo F7-4MB and Devo F4-4MB, based on Nightly Builds:
Files deleted, see below...
Last edit: 18 Aug 2017 04:27 by vlad_vy.
- vlad_vy
-
Topic Author
- Offline
Less
More
- Posts: 3333
18 Aug 2017 04:29 - 23 Aug 2017 05:01 #63856
by vlad_vy
* 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...
Replied by vlad_vy on topic Ultimate Devo F12E (devof12e-4MB) builds
* 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...
Last edit: 23 Aug 2017 05:01 by vlad_vy.
- vlad_vy
-
Topic Author
- Offline
Less
More
- Posts: 3333
22 Aug 2017 13:59 - 22 Aug 2017 14:15 #63896
by vlad_vy
Replied by vlad_vy on topic Ultimate Devo F12E (devof12e-4MB) builds
Now I can enable auto detection of flash memory type. At the moment, supported flash memory chips: Microchip SST25VFxxxB and SST25VFxxxA, ISSI IS25CQxxx, Winbond W25QxxBV. I can't test all supported flash memory chips, but I tested and it works for SST25VF032B and SST25VF016B.
It can be enabled for all Devo transmitters, but I don't know if it has any sense.
It can be enabled for all Devo transmitters, but I don't know if it has any sense.
Last edit: 22 Aug 2017 14:15 by vlad_vy.
- FDR
-
- Offline
22 Aug 2017 15:04 #63897
by FDR
Replied by FDR on topic Ultimate Devo F12E (devof12e-4MB) builds
Can it be fitted into the original F12E build to support both the devo.fs and those larger flash chips, or that would need different builds?
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?
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?
Time to create page: 0.162 seconds
-
Home
-
Forum
-
Development
-
Builds
- Ultimate Devo F12E (devof12e-XMS) builds