[chirp_users] New Daily Build
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-20170607
A list of the changes included in this build (since the last daily) follows:
Changes for Build #487 [Angus Ainslie angus@akkea.ca] [FT1D] Fix test for backtrack code - issue #4877
[Angus Ainslie angus@akkea.ca] [FT1D] fix the PEP8 warnings in the backtrack settings - issue #4877
Changes for Build #488 [Keith Williamson hkwilliamson@gmail.com] [vx8] Mod to radio memory layout to accommodate diffs between models. Fixes #4881 Split the memobj aprs struct into three structs: shorter aprs struct, aprs_msg_macro struct and aprs2 struct. The aprs_msg_macro[] struct and aprs2 struct are parameterized differently in the VX8Radio class and VX8DRadio class _mem_params. Updated all dereferences of memory elements formerly part of the aprs struct that are now part of either the aprs2 struct or the aprs_msg_macro[] struct. There are no behavioral changes to Chirp with this patch.
[Keith Williamson hkwilliamson@gmail.com] [vx8] Simple refactor that moves most VXDRadio class functions to VXRadio parent class. Fixes #4881 This is the first of two groundwork patches for adding Settings support for the VX-8R. This patch produces no change in functionality.
[Keith Williamson hkwilliamson@gmail.com] [vx8] Fix issue with VX-8R download from radio. Fixes #4883 This patch ensures that the functions from the correct radio class are called when downloading from the radio. This is achieved by defining distinct MODELs for the VX-8R, VX-8DR, and VX-8GE and deleting their VARIANTs. This patch is also accompanied (out-of-band) with test image files for each of the radios.
[Pavel Milanes (CO7WT) pavelmc@gmail.com] [PATCH][tk270.py] Increase OEM band edges by 4.0%, fix #4709
Some of this model's variants are in ranges near ham bands but outside them by the OEM stated range, for example from 150 to 174 Mhz, or 148 to 174 Mhz, in the case of the UHF we has the variants in the 450 to 490 Mhz or the 406 to 430 Mhz.
I make some characterizations and most of the radios can work safely with a 4% increment of the stated range safely and will allow to work near ham bands. (real range is bigger but we stick to a safe value)
Related also to #4789, see this for real edges data measurements. With improvements an corrections suggested on the chirp_devel mailing list
[Pavel Milanes (CO7WT) pavelmc@gmail.com] [tk760.py] Increase OEM band edges by 4.0%, fix #4789
Some of this model's variants are in ranges near ham bands but outside them by the OEM stated range, for example from 150 to 174 Mhz, or 148 to 174 Mhz, in the case of the UHF we has the variants in the 450 to 490 Mhz or the 406 to 430 Mhz.
I make some characterizations and most of the radios can work safely with a 4% of the stated range safely and will allow to work near ham bands. (real range is bigger but we stick to a safe value)
This patch was based on the discussions about issue #4709 and improvements from the chirp_devel mailing list comments.
[Pavel Milanes (CO7WT) pavelmc@gmail.com] [tk760g.py] Increase OEM band edges by 4.0%, fix #4789
Some of this model's variants are in ranges near ham bands but outside them by the OEM stated range, for example from 150 to 174 Mhz, or 148 to 174 Mhz, in the case of the UHF we has the variants in the 450 to 490 Mhz or the 406 to 430 Mhz.
I make some characterizations and most of the radios can work safely with a 4% of the stated range safely and will allow to work near ham bands. (real range is bigger but we stick to a safe value)
This patch was based on the discussions about issue #4709 and fixes due to chirp_devel recomendations
participants (1)
-
Build System