Is there a plan for wireless transfer of MODEL?

as title

Is the wireless transfer feature (copy a model from my TX to my friend's TX) coming?

Currently is it a must to have a PC to transfer model?

Thanks

Before we can realize it wireless: would it be an option to transfer models by wire through the trainer connection? It will be a one-way communication but probably better than nothing...

It would be great if model exchange feature is available without a PC.

A suggestion:

Would it be easy to add this in USB page?
- press ENT to enable usb function,
- press and hold ENT to enable model receive feature

file received will overwrite current model data, of course, with confirmation.

when either function is enabled, screen and TX is locked.

I think this may minimize the GUI effort.

I don't think the gui will be a challenge.
More will be the development of a transfer protocol with some kind of securing the transfer (crc32-checksums could be used, as already implemented for the tx config).
An additional problem: because the used filesystem driver can not create new files there will be no other way than to overwrite existing model configs. Maybe we could declare some config files for this purpose (e.g. give them a special model name like "for_transfer" and allow only those model files to be overwritten (will have a new name thereafter)).
For creating more model files the pc must still be used.

is it the STM32 working like the microcontroller?
-- if there is a byte received, write it to the flash, inc the pointer, wait for the next byte.

Or you need to wait for the whole data stream and have some CRC checking?

kenkenlau wrote: is it the STM32 working like the microcontroller?

The STM32 in fact IS the micro controller.

-- if there is a byte received, write it to the flash, inc the pointer, wait for the next byte.

Or you need to wait for the whole data stream and have some CRC checking?

This depends on the implementation. The crc check can not made before the complete data the crc check sum belongs to is transferred.
I am not sure if the serial transfer can work asynchronously but I highly expect this. Until now I have not implemented such timing dependent or interrupt controlled things for deviation so I do not really know what is necessary.
I could imagine a procedure for sending / receiving when the tx functions are of as you mentioned above.

Question: is the Devo's serial port bidirectional (and for PPM only a mono cable is allowed)? This would make the transfer easier. The hardware connections written in the article's section imply this.
Maybe a silly question and answered long ago but I did not care about this topic until now... and someone mentioned that he has taken the signals from the pcb because of something weird with the jack (I think in the bluetooth thread).

rbe2012 wrote: Maybe a silly question and answered long ago but I did not care about this topic until now... and someone mentioned that he has taken the signals from the pcb because of something weird with the jack (I think in the bluetooth thread).

That is me indeed

The port is bidirectional. But I dont know how the RX-IRQ works in STM32