Really appreciate all the advice in there. I will definitely have to try out importing/exporting via Excel.
Ignition sense is also planned, it seems very smartly designed with the power off timeout feature. I do wish there was some equivalent of "Power memory" for ignition sense, e.g. if I manually turn off the radio while the ignition is on it stays off until I press the power button again.
As for the replay/recordings, you have the HHCH, so you don't need a license to add the SD card to the head. Cards are cheap, just buy and insert (same for KCH-20R head). You also get BT programming via the head without having to add KWD-5003BT bluetooth data.
The KCH-21RM (HHCH) comes with Bluetooth but it does not have the SD card slot unlike the 20R. Best I can tell from D1N I have to have the optional feature license to put an SD card in the deck.
It's that connector between the coiled tail and the rest of the cable that is huge.
Yes, that thing is gigantic. It is relatively easy to release (not accidentally, it has a twist locking mechanism), which makes me wonder what happens if someone ever unplugs it while the radio is operating.
The thing that is impressive about Armada, it allows 255 entries, which is way more than one would ever need.
255 would go a long way, at least for simplex freqs where I'd be able to match any tone someone was operating on the fly.
On the amateur side, there is one linked repeater system in my area where different tones can be used to control the routing of the transmission through the link system. Though each node in the system uses a different set of tones. Ideally each channel gets its own OST list with only the tones for that node—thought sounds like that's not how anyone's OST implementation is designed (I guess the commercial/fire department users all have one set of tones synchronized statewide). I just ended up programming several channel banks for each repeater with all the variants of TX tone, with all but the first set to exclude from scan.
I have zones broken into state sections/groups of counties
I'm still torn on how to lay out the zones. My current design is one zone for each location/system type. When scanning sometimes I also want to layer in a simplex zone which, so the multi-zone works well there. Possibly I can also do that with pre-programmed scan lists.