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".

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.

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.

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.

On the other side having one extern antenna to use every chipset for longrange would be very, very fine

Greetz

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

A7105 is implemented for FlySky and Hubsan long ago.

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

jpshu thanks again, at some point you'll ask me for something

No, Cypress Wireless USB (CYRF6936 used in Walkera DSSS products) modulation is quite specific, and CC2520 implements another specific standard, IEEE 802.15.4.

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.

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.

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+

B12	A13(TMS)	A14(TCK)	MODULE
1	0	0	CYRF6936
0	0	1	nRF24L01+
0	1	0	CC2500
0	1	1	A7105

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

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 ?

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.

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.

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 .