Actions
Feature #11859
closedProvide a RX/TX frequency workflow like commercial users expect
Start date:
02/26/2025
Due date:
% Done:
100%
Estimated time:
Chirp Version:
next
Model affected:
All
I read the instructions above:
Yes
Description
CHIRP internally always uses duplex/offset, which is convenient and conventional for Amateur Radio. However, commercial users are more used to a RX/TX frequency model, and an increasing number of drivers in CHIRP actually only support that model internally anyway. The CHIRP UI could provide an option to use a RX/TX frequency workflow and hide the fact that duplex/offset is being used under the covers.
Updated by Dan Smith about 2 months ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset github|729c075dab223b13fdfbaeaec64159d356da52bb.
Actions