VK3KYY wrote: ↑Sun Feb 28, 2021 2:56 am
I can see a Use Case for option 4, which is a kind of "follow" or "retain" option, so that once a TS is set from a Contact of manually, the firmware uses that TS until either you change to a TG which has a different override TS or you press * to manually change the TS.
Personally, I think I would probably use option / mode 4 in preference to the current system, even though ultimately the existing system is more logical.
Hi Roger.
I have the same opinion.
However I think that it can work well with normal TGs, rather than with those which are intended for special purposes such as disconnection (TG4000), status (TG5000), parrot (TG9990), and so on: with this last ones the matter is more complicated.
As things are now any TG programmed in the codeplug that has his timeslot, does not matter if like TS# or cS#, exhibits a different behavior depending on whether the override option is enabled or not.
In the same scenario the same TG inserted manually (by pressing #) has a still different behavior depending on whether it is typed on the fly or taken from pre-existing contacts in the codeplug.
It can therefore happen that using a given TG that has a given timeslot, for example going to perform a disconnection (TG4000) by manually entering it from the keyboard (by pressing #) the resulting timeslot will be the same as that of the TG in use, while taking it from the contacts not necessarily the timeslot it would be the desired one, it may be necessary to adjust it manually (by pressing *).
Not that the thing is to be considered a problem, not being too tiring nor complicated to adjust the timeslot so that it is the right one.
In the end it would only be necessary to pay a little more attention.
However, it would be more logical than in any circumstance (ie always), using a given TG and wanting to make a disconnection (TG4000), a status check (TG5000), try an echotest on the repeater (Parrot TG9990) and so on, the timeslot remains the same of the TG in use without the need to pay attention to it and possibly having to retouch it (by pressing *).
With the normal TGs the matter is pretty different and much simpler because once the timeslot has been selected there would be no need to modify it if not if you decide to change TG.
Therefore in those cases it would be necessary to set the timeslot only once without worrying that it can change unexpectedly, unless you decide to use TGs belonging to the special type described above.
These are simply and only thoughts, not a criticism, nor are these thoughts a change request for the firmware.
They are only a mere thoughts, nothing else.
73 best regards de Fabio IZ2EIB