AirCopy: do we really need it?

[amelillo]

Hello,
I was wondering how many people actually use AirCopy. It's a useful function just if you have a fleet of rtx's you have to clone (for a team, a patrol, whatever).
But if you are an OM, it's way too probable you'll end up using Chirp and a dump to transfer memories from a handheld to another. Moreover, AirCopy sometimes fails and has to be repeated to get all the channels correctly transferred.
So, I thought, why not entirely removing the AirCopy function thus freeing up space for something else?
I don't know how much space would be freed up, but we could have a fourth memory bank for instance, or spectrum presets, whatever.
What do you think about it?
Cheers!
IZ5IMK

[Jekko76]

I don't feel so much the need of the aircopy function...

[goopaga]

I must agree with the above comments.

Aircopy is a nice feature, the first time looks like magic 😅, however besides few niche situations I'd rather sacrifice it in favour of more advanced features or freq. memories.

Great firmware anyway 💪 Good job Armel !

73 de IU4MJW

[amelillo]

Just a moment: reading "looks like magic" makes me think our colleague IU4MJW is rather referring to "frequency copy".
AirCopy can't look like magic; it's an agreed memory transfer.
Instead, Frequency Copy is the act of sniffing and storing a frequency and possible DTMF/CTCSS code from a nearby and potentially unaware radio operator; that actually looks like magic :-)
So, I'd rather keep the Frequency Copy function and remove the Air Copy, though I actually have no idea of the firmware space we could get back.

Alessandro IZ5IMK

[goopaga]

Absolutely, we are on the same page Alessandro !
I'm also referring to the AirCopy function (wireless transfer of radio settings/memory).

To me it's "magic" because it just works with no issues (generally) and the first time I did the transfer to a radio of a friend he was amazed like if I was a magician 🤣.

73

[armel]

Hi Guys,

First of all, sorry, but I use Aircopy quite often. I don't always have a PC (with Chirp) to duplicate memory channels from one K5 to another. I'm often in the wild, away from everything.

Second, the only version currently lacking memory for certain evolutions is the VoxLess version (for which the Aircopy function has already been removed). There's still some free memory left on the BandScope version, and even more on the Broadcast version.

Why remove certain features, only to replace them with... nothing ? This discussion therefore seems premature. It seems to me.

It can be revisited if, AND ONLY IF, memory starts to run out AND a better idea can be developed instead.

For the moment, this is not the case.

Last but not least, don't get your hopes up: removing the AirCopy feature won't work miracles for long.

Armel F4HWN.

[Jekko76]

Dear Armel,
It is a great news that you have still some memory free.
Like our friends here, I don't use AirCopy that much, but I use FREQUENCY COPY (f+4) really often.
It would be fantastic if, in any way you want, the firmware could store in memory not only ONE frequency but ALL frequencies that the radio find around.
We could imagine that it stores the frequencies always in the first free memory channel, for example.
Just think about it :)
Thank you again for your superb work!
IU4RWY

[f1ixx]

Hi all group

First, thank's Armel for work and your fabulous firmware.

I'm not use AirCopy, because erase all memory on RX talky.
I haven't thought about the code, but implante a function to
copy 1 memory or x memorys consecutive .
Example in airCopy mode :
1.RX talky set to wait memory 100 and wait data.
2.TX Talky set on memory 80 (send only 1 memory)
3.Send data on TX talky
or
1.RX talky set on memory 120 ans wait data
2.TX talky set on memory 20 BUT choose 10 memorys (consecutive)
3.Send data on TX Talky.

In the 2 cas, we have copy ALL options memory (CTCSS, DCS, step, mode,
power, name....) from TX talty to RX.

I'thinks it's big job and burn many octets and it's juste a idea.

Hoping not "pollute" this issue

Thank's to read me

Boris