Greetings,

A new daily build of CHIRP is available.  This includes changes made
directly to the tree yesterday, and may include additional features,
bug fixes, and/or bugs.  If you are interested in trying it, grab it
from the following location:

  http://trac.chirp.danplanet.com/chirp_daily/daily-20200718


A list of the changes included in this build (since the last daily)
follows:

Changes for Build #628
[Dan Smith <[email protected]>] [uv5r] Remove experimental designation

This driver is one of the most feature-complete and well-tested
of all in the chirp tree. It's been marked as experimental for years,
and I think it's safe to remove that designation at this point.

Closes #8099

[Dan Smith <[email protected]>] Add TIDRADIO TD-H6 and TD-UV5R

Closes #8097

[Dan Smith <[email protected]>] Add Tenway UV-82 Pro alias

Closes #8095

[Martin Cooper <[email protected]>] Invert default return from 
_detect_23cm_unit

Fixes #8085

[Iain White <[email protected]>] Change FTM7250D driver 'rf.valid.bands' to 
range of 108MHz to 580 MHz     Fixes #8059

[Jim Unroe <[email protected]>] [BF-A58S] baofeng_w970i.py driver update 
support for band limts

This patch updates the current tri-band radio model suppport to fully
implement the available band limit settings.

Related to these and similar Baofeng tri-band models:
BF-A58S
UV-82III
BF-UVF10

related to #8063

[Jim Unroe <[email protected]>] [BF-A58S] baofeng_w970i.py driver cleanup

This patch cleans up the current tri-band radio model suppport in
preperation for fixing the band limit support in the following patch.

Related to these and similar Baofeng tri-band models:
BF-A58S
UV-82III
BF-UVF10

related to #8063

[Iain White <[email protected]>] Add FTM7250D image file for testing:  
Yaesu_FTM-7250D_R.img   Issue #6525


_______________________________________________
chirp_users mailing list
[email protected]
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to [email protected] at [email protected]
To unsubscribe, send an email to [email protected]

Reply via email to