Developing a universal module

More
10 Apr 2013 14:38 #8828 by RandMental
Replied by RandMental on topic Developing a universal module
Just for interest - i have never been able to download from the sourcecodedownloads.com site. It eventually asks for the Auth code and then invariably comes up with some generic error message like "Network Error".

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

More
10 Apr 2013 14:52 #8829 by DarkWolf
Replied by DarkWolf on topic Developing a universal module
PB, I see that the V922 uses NRF24L01E and the Anylink is NRF24L01.. Does that mean that I could simply pick up an Anylink external mod and hook it up PPM and it would work with the V922? I don't mind having a strap on module at all. Would put the V922 back on the buy list for sure.

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

More
10 Apr 2013 17:10 #8831 by PhracturedBlue
Replied by PhracturedBlue on topic Developing a universal module

DarkWolf wrote: PB, I see that the V922 uses NRF24L01E and the Anylink is NRF24L01.. Does that mean that I could simply pick up an Anylink external mod and hook it up PPM and it would work with the V922? I don't mind having a strap on module at all. Would put the V922 back on the buy list for sure.

No. There are 2 parts: a) the chips used for communication b) the protocola (software) used for communication.

generally if to radios use different chips there is no possibility of them talking. However even if they use the same chips, they can't talk unless they can speak the same protocol. That is where deviation comes in. All of the following: DEVO, WK2x01, DSM, and J6Pro use the same chips but different protocols. Deviation has code for each protocol and so can communicate with all of those. The same now applies for the other chips:
A7105: Flysky and Hubsan
CC2500: FrSky and Skyartec
NFR24L01: V922, Anylink, NE260, MJX

This thread is only about the hardware (how do we support the chips). the question of protocol comes next and needs to be evaluated case by case.

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

More
10 Apr 2013 19:19 - 10 Apr 2013 19:20 #8835 by blackmoon
Replied by blackmoon on topic Developing a universal module
Ihmo, the best way, as you already stated it, would be a "little" MB where all modules be plugged.

With maybe a mcu and some logic to drive them, this would in the end be faster and will mostly work.

Only thing is the space constraint inside the transmitters.

Developing one rf module is already a big deal, not talking about 4 or 5 on the same pcb.
Last edit: 10 Apr 2013 19:20 by blackmoon.

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

More
10 Apr 2013 19:39 - 10 Apr 2013 19:41 #8837 by ColdFire
Replied by ColdFire on topic Developing a universal module
Reliability and compliance are the other issues ... though not sure if multiple modules put on a single PCB already violate the compliance requirement

blackmoon wrote: Ihmo, the best way, as you already stated it, would be a "little" MB where all modules be plugged.

With maybe a mcu and some logic to drive them, this would in the end be faster and will mostly work.

Only thing is the space constraint inside the transmitters.

Developing one rf module is already a big deal, not talking about 4 or 5 on the same pcb.

Last edit: 10 Apr 2013 19:41 by ColdFire.

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

More
11 Apr 2013 11:20 #8844 by Wene001
Replied by Wene001 on topic Developing a universal module
On the other side having one extern antenna to use every chipset for longrange would be very, very fine

Greetz

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

More
11 Apr 2013 14:22 #8855 by jpshu
Replied by jpshu on topic Developing a universal module
PhracturedBlue
I have A7105 data about "FIFO mode", Include demo code for A7105, I have updated to my netware disk, please you download it.
pan.baidu.com/share/link?shareid=464899&uk=2855534891

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

More
11 Apr 2013 16:38 #8859 by victzh
Replied by victzh on topic Developing a universal module
A7105 is implemented for FlySky and Hubsan long ago.

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

More
11 Apr 2013 19:37 #8870 by PhracturedBlue
Replied by PhracturedBlue on topic Developing a universal module

jpshu wrote: PhracturedBlue
I have A7105 data about "FIFO mode", Include demo code for A7105, I have updated to my netware disk, please you download it.
pan.baidu.com/share/link?shareid=464899&uk=2855534891

As I said above, I'm interested in the 'Direct Mode' document, because I haven't seen anyone use it, and I am wondering if I can use it for some other things, so seeing an example would be helpful. I do not need the 'FIFO' document as we already have working code using that procedure.

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

More
12 Apr 2013 03:22 #8881 by jpshu
Replied by jpshu on topic Developing a universal module
PhracturedBlue
I have updated "direct mode" demo code for a7105 to my netware disk, please you download it.
pan.baidu.com/share/link?shareid=471838&uk=1260881382

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

More
12 Apr 2013 04:21 #8882 by PhracturedBlue
Replied by PhracturedBlue on topic Developing a universal module

jpshu wrote: PhracturedBlue
I have updated "direct mode" demo code for a7105 to my netware disk, please you download it.
pan.baidu.com/share/link?shareid=471838&uk=1260881382

Thanks, it looks good. I haven't dug through the code, but looks promising.

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

More
12 Apr 2013 13:59 #8899 by SadSack
Replied by SadSack on topic Developing a universal module
jpshu thanks again, at some point you'll ask me for something :)

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

More
22 Apr 2013 04:57 #9114 by vlad_vy
Replied by vlad_vy on topic Developing a universal module

victzh wrote: Maybe someone is producing a chip, powerful enough to cover all protocol requirements (except DSSS ones)?


JR DMSS protocol is a combination of DSSS and FHSS protocols. Possible CC2520 chip can be used for both DSSS or FHSS protocols?

www.jrpropo.co.jp/english/propo/dmss/whats_dmss.html

www.archeli.com.au/forums/showthread.php?t=153157

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

More
08 May 2013 06:57 #9699 by victzh
Replied by victzh on topic Developing a universal module
No, Cypress Wireless USB (CYRF6936 used in Walkera DSSS products) modulation is quite specific, and CC2520 implements another specific standard, IEEE 802.15.4.

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

More
30 Sep 2013 12:15 - 30 Sep 2013 12:16 #14163 by MassiveOverkill
Replied by MassiveOverkill on topic Developing a universal module
I've reached out to a BT manufacturer that I just introduced Victor to, to see if they're willing to produce a module and how much it would cost. Right now I'd be happy to just see a WL Toys and FlySky module created. For Devo 7E owners an aftermarket module to bypass the stock one would be nice too as the diode mod really isn't mass-production friendly.
Last edit: 30 Sep 2013 12:16 by MassiveOverkill.

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

More
30 Sep 2013 13:05 #14167 by victzh
Replied by victzh on topic Developing a universal module
Wow! If they really could do this I think almost every protocol can be covered with 2 radio chips - CYRF6936 and one of the chips with direct mode. It is going to be very experimental.

Another approach is 4 RF chips, one PA, one RF switch and one controller. Parts cost are around $25, so target price is around $60-75.

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

More
14 Nov 2013 16:19 - 14 Nov 2013 16:30 #15580 by blackmoon
Replied by blackmoon on topic Developing a universal module
As I already have a A7105 module on both my devo10 and 7E.

I want to had two more modules, cc2500(skyartec), nRF24l01+(HiSky).

Currently I can only add one or the other so I came up with a pcb adapter + mcu (Attiny13).

Pcb isn't designed yet, I don't know how big it will be and if enough space is available on both transmitters.

On the 7E I think it will be very difficult to fit...

The Tiny13 should be enough to read both TMS and TCK pins, and enable three modules : A7105,CC2500, nRF24L01+

B12A13(TMS)A14(TCK)MODULE
100CYRF6936
001nRF24L01+
010CC2500
011A7105

I think it is possible to enable both TMS and TCK pins at the same time.

But how you do it in deviation ?

I take it isn't so simple as adding :

enable-a7105=A13 A14 (or even A13 && A14)
has_pa-a7105=1

The only place I find a reference A13 A14 is in tx.ini

I found this also in /config/tx.c
/* Section: TX Module */
static const char SECTION_MODULES[] = "modules";
static const char MODULE_ENABLE_PIN[] = "enable";
static const char MODULE_HAS_PA[] = "has_pa";
static const char * const MODULE_NAME[4] = {"cyrf6936", "a7105", "cc2500", "nrf24l01"};

But can't see how it read the values of A13 and A14 in the tx.ini.

If not this simple, how could one patch the firmware to enable both pins when a protocol using the A7105 is selected ?

Thank you.

Sorry for the image quality, it isn't like that on the original; forum compression ?




File Attachment:

File Name: Deviation_...dule.pdf
File Size:35 KB
Attachments:
Last edit: 14 Nov 2013 16:30 by blackmoon.

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

More
14 Nov 2013 17:43 #15581 by victzh
Replied by victzh on topic Developing a universal module
I am designing now similar system but with a little bit different approach. You can even get away with simple logic, ATtiny is not even necessary. I do not use this combo schema with two pins, I plan to receive and interpret a command for switch over. Mind you - chip select on all these chips is inverted, so it's active when LOW.

WRT space - I found that you can fit three extra modules on a daughter board inside Devo 7E, even easier if you remove the SMA and solder antenna feed directly to the board, and solder the board to daughter board. When I'm done with the layout I will publish it.

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

  • rbe2012
  • rbe2012's Avatar
  • Offline
  • So much to do, so little time...
More
14 Nov 2013 19:30 #15583 by rbe2012
Replied by rbe2012 on topic Developing a universal module
You can not simply write the A13 and A14 in one line - this will not be recognized since only the strings "A13" and "A14" are detected - nothing else (even "a13" will not).
If you want to create a new condition like "A13+A14" you will have to change the method reading the tx.ini and the code which activates a module since all data structures and functions expect one pin to be used.
This will be no easy task.

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

More
14 Nov 2013 19:59 #15587 by victzh
Replied by victzh on topic Developing a universal module
I would suggest moving these functions for activating the module into some separate place instead of making them macros. I would need similar functionality for my own module and can help to develop and propagate it through all the modules. It's not that many of them - 4 drivers for corresponding chips in src/target/common_devo/protocol .

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

Time to create page: 0.162 seconds
Powered by Kunena Forum