Project

General

Profile

Actions

Feature #6615

closed

A driver should be allowed to force a channel to be receive-only

Added by Daniel Clemmensen about 5 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
Start date:
03/16/2019
Due date:
% Done:

100%

Estimated time:
0.50 h
Chirp Version:
daily
Model affected:
(All models)
I read the instructions above:

Description

Many radios allow receive on frequency ranges that they refuse to transmit on. CHIRP currently has no way to indicate this.
in discussion with Dan Smith, the simplest way to implement this is for the driver to set the "duplex" field to "off" when the user enters anything that leads to an invalid TX frequency on the channel. RadioFeatures.valid_bands will continue to describe the valid RX bands and the UI will continue to enforce these bands for both TX and RX. duplex=="off" will be an additional restriction.

To support this, the automated test system module "run_tests.py" must be modified to treat a response of duplex == "off" as a legal response in all cases, even when the test case would otherwise expect another value.

This issue tracks only the change to run_tests. Driver changes can be made as desired after this change takes effect and can be handled as separate issues.

Actions

Also available in: Atom PDF