December 2019 - Developers - lists.chirpmyradio.com

[chirp_devel] Add new radio Icom IC-E90/T90/T90A
by Jaroslav Skarvada 21 May '20

21 May '20

Hi, attached is the patch adding support for Icom IC-E90/T90/T90A radios and memory map for this radio. The radio is a bit tricky - it has multiple special channels and TV channels (well analog TV is a bit off-topic today, but I wanted to support all features of this radio). I added TV channels as a subdevice, because I have no better idea how to do it. Also I had to modify the icf driver a bit, because it seems the clone status doesn't work with this radio. Maybe I am just missing something here, but I wasn't able to persuade my radio to behave this way. The proposed icf driver change should be harmless for other ICOM radios, because it's adding new option and the memory size calculation should be backward compatible. One test from the testsuite is failing: ./run_tests.py -d 'Icom_IC-E90' Icom IC-E90 Detect PASSED: All tests Icom IC-E90 Settings PASSED: All tests Icom IC-E90 Clone PASSED: All tests Icom IC-E90 Edges FAILED: Field `name' is ` ', expected `' Icom IC-E90 BruteForce PASSED: All tests Icom IC-E90 CopyAll PASSED: All tests Icom IC-E90 Banks PASSED: All tests Icom IC-E90 TV Detect PASSED: All tests Icom IC-E90 TV Settings PASSED: All tests Icom IC-E90 TV Clone PASSED: All tests Icom IC-E90 TV Edges FAILED: Field `name' is ` ', expected `' Icom IC-E90 TV BruteForce PASSED: All tests Icom IC-E90 TV CopyAll PASSED: All tests Icom IC-E90 TV Banks SKIPPED: Banks not supported ---------------------------------------------------------------------- Results: TOTAL : 14 FAILED : 2 SKIPPED: 1 PASSED : 11 CRASHED: 0 But by inspection of the logs (see bellow) I am not sure whether there is a bug in my driver or in the test suite: ---- Begin test Edges ---- Field `name' is ` ', expected `' ### Wanted: vfo:0 tmode: name: <SPACE> power:None duplex: skip: tuning_step:5.0 number:0 comment: immutable:[] rx_dtcs:23 dtcs_polarity:NN extd_number: mode:AM dtcs:23 offset:600000 freq:1495000 cross_mode:Tone->Tone ctone:88.5 empty:False rtone:88.5 ### Got: vfo:0 tmode: name: <SPACE> power:None duplex: skip: tuning_step:5.0 number:0 comment: immutable:[] rx_dtcs:23 dtcs_polarity:NN extd_number: mode:AM dtcs:23 offset:600000 freq:1495000 cross_mode:Tone->Tone ctone:88.5 empty:False rtone:88.5 ---- End test Edges ---- I added <SPACE> where there was ' ' in the log for the problem to be clearly visible. So it seems the "wanted" is the same as the "got". It's the same for the 'TV' subdevice thanks & regards Jaroslav

3 17

[chirp_devel] Patch for #7119 BF-888 "Refused to enter programming mode."
by Nicklas Lindgren 02 Mar '20

02 Mar '20

Hi, Sorry if this becomes a duplicate message. I was at first but subscribed to the list with the correct email, and my first message didn't come through. About the patch: This change fixes the problem with my two radios, but i can't be sure that its the same problem that the original reporter of the bug has. I'm a bit concerned about raising the timeout globally. I can't rule out that it has any other consequences, but at the same time i don't imagine anything depends on a particular serial read timeout. -- Nicklas Lindgren 59D8 27AD 2632 F349 9B20 F5CB D363 3177 0A12 1B95

4 7

[chirp_devel] Using TOX to test on MS Windows
by Eric A. Cottrell 03 Jan '20

03 Jan '20

Hello, I initially used MS Windows to develop some changes to CHIRP. I am having a problem with TOX. It appears that it can not find the chirp modules and the version numbers. I tried building and testing under Linux and things worked fine. I noticed the zip file is named for the version under Linux and unknown with zeros under windows Is CHIRP only meant to be developed using Linux or do I have a setup problem? 73 Eric --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 9

[chirp_devel] [PATCH] [vx8] #129, #1735 (same issue): fix for incorrect channel initializations
by Bernhard Hailer 02 Jan '20

02 Jan '20

# HG changeset patch # User Bernhard Hailer <ham73tux(a)gmail.com> # Date 1577395355 28800 # Thu Dec 26 13:22:35 2019 -0800 # Node ID 826a0f4b373066fb73e255e1f82b1cf190830763 # Parent c3c7ee53893ff6ff83798bd9cc0a424dae201d3f [vx8] #129, #1735 (same issue): fix for incorrect channel initializations Users complained that under certain circumstances 2m repeaters with negative offsets were not programmed correctly and resulted in a frequency offset or even an incorrect transmit/receive mode. Both issues #129 and #1735 essentially describe that same problem for the Yaesu VX-8. I ran into the same issue with a VX-8DR I just got - which made me dig into Chirp :-) Two bytes were found to be initialized differently when manually programmed, both were marked "unknown". After a few experiments these bytes could be (at least partially) identified. (A side product was that I found the bit responsible for narrowband transmit - that will be used in another patch fixing issue #1615 to enable this radio for Chirp's "NFM" mode). Tested with a VX-8DR. 73 Bernhard AE6YN diff --git a/chirp/drivers/vx8.py b/chirp/drivers/vx8.py --- a/chirp/drivers/vx8.py +++ b/chirp/drivers/vx8.py @@ -152,7 +152,9 @@ #seekto 0x328A; struct { - u8 unknown1; + u8 unknown1a:2, + half_deviation:1, + unknown1b:5; u8 mode:2, duplex:2, tune_step:4; @@ -167,7 +169,12 @@ tone:6; u8 unknown6:1, dcs:7; - u8 unknown7[3]; + u8 pr_frequency; + u8 unknown7; + u8 unknown8a:3, + unknown8b:1, + rx_mode_auto:1, + unknown8c:3; } memory[900]; #seekto 0xC0CA; @@ -494,7 +501,9 @@ def _wipe_memory(mem): mem.set_raw("\x00" * (mem.size() / 8)) - mem.unknown1 = 0x05 + mem.pr_frequency = 0x1d # default PR frequency of 1600 Hz + mem.unknown8b = 1 # This bit must be 1, but its meaning is unknown + mem.rx_mode_auto = 1 # rx auto mode bit defaults to 1 @directory.register @@ -701,6 +710,7 @@ _mem.duplex = DUPLEX.index(mem.duplex) _mem.mode = MODES.index(mem.mode) _mem.dcs = chirp_common.DTCS_CODES.index(mem.dtcs) + # Radio doesn't do that when programmed manually, but tox needs it: _mem.tune_step = STEPS.index(mem.tuning_step) if mem.power: _mem.power = 3 - POWER_LEVELS.index(mem.power)

2 3

[chirp_devel] [PATCH] Patch for "run_all_test.bat"
by Jim Unroe 31 Dec '19

31 Dec '19

# HG changeset patch # User Jim Unroe <rock.unroe(a)gmail.com> # Date 1577819050 18000 # Tue Dec 31 14:04:10 2019 -0500 # Node ID 96d3ba788e5a75fabf39f74ee0545e683ac8f16d # Parent c3c7ee53893ff6ff83798bd9cc0a424dae201d3f Patch for "run_all_test.bat" This patch fixes the run_all_tests.bat" batch file so that it will properly access and run the "run_test.py" tests. #7505 diff --git a/run_all_tests.bat b/run_all_tests.bat --- a/run_all_tests.bat +++ b/run_all_tests.bat @@ -1,3 +1,3 @@ @echo off -python tests\run_tests +python tests\run_tests.py python tools\cpep8.py

1 0

[chirp_devel] TOX setup issue?
by Jim Unroe 31 Dec '19

31 Dec '19

I've been rebuilding my CHIRP Developers Environment PC. While I've been doing it, I've been taking the time to document the steps that are needed to fully setup the environment in both Windows and Linux (distros based on Ubuntu). I've run into an issue in my Linux environment while setting up tox. Here is my issue... So I am starting out on an SSD with a fresh installation of the OS. The first thing I do is install all or the required packages that will need. With that out of the way, from my home folder I clone the CHIRP repository to my local machine... hg clone http://d-rats.com/hg/chirp.hg and CD into that folder... cd chirp.hg At this point I perform a "diff" command... ~/chirp.hg$ hg diff ~/chirp.hg$ and nothing is returned (which is good). So now I give tox a go... ~/chirp.hg$ tox I get the prompt back after a successful run and then perform another "diff". ~/chirp.hg$ hg diff This is where the problem arises. Every *.po file in the ~/chirp.hg/locale folder has been changed If I save a copy of the *.po files prior to running tox and copy them back in the locale folder (or download them from the repository) and run the "diff" command again, all is good. What would be causing this? Am I doing something wrong? Jim KC9HI

1 0

[chirp_devel] TOX tests on Mac.
by Nicolas Pike 30 Dec '19

30 Dec '19

> ImportError: cannot import name Serial > > What part of the setup have I missed? You're missing python-serial. Can you add deps=serial to the [testenv:driver] section in tox.ini and see if that works? Added serial to tox deps and it gets a bit further, any thoughts? as before UNKNOWN-0.0.0.zp can't be write, and now we have no module named chirp. Is there something to be done with the build first? Thanks. Nicolas nicolass-Mac-mini:chirp.hg nicolas$ tox -e driver -- -d Icom_IC-2820H *GLOB sdist-make: /Users/nicolas/Documents/FT70CHIRP/chirp.hg/setup.py* *driver inst-nodeps: /Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/dist/UNKNOWN-0.0.0.zip* ERROR: invocation failed (exit code 1), logfile: /Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/driver/log/driver-4.log ERROR: actionid: driver msg: installpkg cmdargs: ['/Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/driver/bin/pip', 'install', '-U', '--no-deps', '/Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/dist/UNKNOWN-0.0.0.zip'] Processing ./.tox/dist/UNKNOWN-0.0.0.zip Complete output from command python setup.py egg_info: Traceback (most recent call last): File "<string>", line 1, in <module> File "/private/var/folders/yf/rh0gfjk57pzfvdls7z6nwnmr0000gn/T/pip-kuILg4-build/setup.py", line 5, in <module> from chirp import CHIRP_VERSION ImportError: No module named chirp ---------------------------------------- Command "python setup.py egg_info" failed with error code 1 in /private/var/folders/yf/rh0gfjk57pzfvdls7z6nwnmr0000gn/T/pip-kuILg4-build/ *driver installed: future==0.16.0,iso8601==0.1.12,libxml2-python==2.9.7,lxml==4.1.1,mercurial==4.5,pluggy==0.6.0,py==1.5.2,pycairo==1.15.3,PyYAML==3.12,serial==0.0.38,six==1.11.0,tox==2.9.1,virtualenv==15.1.0* _______________________________________________________________________________ summary _______________________________________________________________________________ ERROR: driver: InvocationError: /Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/driver/bin/pip install -U --no-deps /Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/dist/UNKNOWN-0.0.0.zip (see /Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/driver/log/driver-4.log) nicolass-Mac-mini:chirp.hg nicolas$

4 5

[chirp_devel] [PATCH] [UV-9R] Add Baofeng UV-9R
by Jim Unroe 30 Dec '19

30 Dec '19

# HG changeset patch # User Jim Unroe <rock.unroe(a)gmail.com> # Date 1577718271 18000 # Mon Dec 30 10:04:31 2019 -0500 # Node ID 8cc267ad96707fa0643f0239e4e415584b3dc345 # Parent c3c7ee53893ff6ff83798bd9cc0a424dae201d3f [UV-9R] Add Baofeng UV-9R This patch adds support for the Baofeng UV-9R which, unlike other "waterproof" models, supports 7-character channel names. #7499 diff --git a/chirp/drivers/baofeng_wp970i.py b/chirp/drivers/baofeng_wp970i.py --- a/chirp/drivers/baofeng_wp970i.py +++ b/chirp/drivers/baofeng_wp970i.py @@ -902,3 +902,11 @@ (200000000, 260000000), self._uhf_range] return rf + + +(a)directory.register +class UV9R(WP970I): + """Baofeng UV-9R""" + VENDOR = "Baofeng" + MODEL = "UV-9R" + LENGTH_NAME = 7

1 0

[chirp_devel] New developer - some obstacles
by Bernhard Hailer 23 Dec '19

23 Dec '19

Hello Chirp team, I'm playing with the Chirp code for the Yaesu VX- 8 driver for about two weeks now, and I think I have fixes for issues #1615 (NFM not working), #129 and #1735 (incorrect initializations causing frequency offsets). Using "python chirpw", these fixes appear to work. However, I can't get past two items before I commit my first patches. 1) I'm not able to run tox. The output on freshly downloaded from repository Chirp code is: F:\Programming\CHiRP\chirp.hg\chirp>tox GLOB sdist-make: F:\Programming\CHiRP\chirp.hg\setup.py unit inst-nodeps: F:\Programming\CHiRP\chirp.hg\.tox\.tmp\package\1\UNKNOWN-0.0.0.zip ERROR: invocation failed (exit code 1), logfile: F:\Programming\CHiRP\chirp.hg\.tox\unit\log\unit-7.log ================================== log start ================================== DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support Processing f:\programming\chirp\chirp.hg\.tox\.tmp\package\1\unknown-0.0.0.zip ERROR: Command errored out with exit status 1: command: 'F:\Programming\CHiRP\chirp.hg\.tox\unit\Scripts\python.EXE' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'c:\\users\\dl4mhk\\appdata\\local\\temp\\pip-req-build-6t1qd5\\setup.py'"'"'; __file__='"'"'c:\\users\\dl4mhk\\appdata\\local\\temp\\pip-req-build-6t1qd5\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base 'c:\users\dl4mhk\appdata\local\temp\pip-req-build-6t1qd5\pip-egg-info' cwd: c:\users\dl4mhk\appdata\local\temp\pip-req-build-6t1qd5\ Complete output (5 lines): Traceback (most recent call last): File "<string>", line 1, in <module> File "c:\users\dl4mhk\appdata\local\temp\pip-req-build-6t1qd5\setup.py", line 5, in <module> from chirp import CHIRP_VERSION ImportError: No module named chirp ---------------------------------------- ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output. =================================== log end =================================== driver inst-nodeps: F:\Programming\CHiRP\chirp.hg\.tox\.tmp\package\1\UNKNOWN-0.0.0.zip ERROR: invocation failed (exit code 1), logfile: F:\Programming\CHiRP\chirp.hg\.tox\driver\log\driver-7.log ================================== log start ================================== DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support Processing f:\programming\chirp\chirp.hg\.tox\.tmp\package\1\unknown-0.0.0.zip ERROR: Command errored out with exit status 1: command: 'F:\Programming\CHiRP\chirp.hg\.tox\driver\Scripts\python.EXE' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'c:\\users\\dl4mhk\\appdata\\local\\temp\\pip-req-build-ddeyne\\setup.py'"'"'; __file__='"'"'c:\\users\\dl4mhk\\appdata\\local\\temp\\pip-req-build-ddeyne\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base 'c:\users\dl4mhk\appdata\local\temp\pip-req-build-ddeyne\pip-egg-info' cwd: c:\users\dl4mhk\appdata\local\temp\pip-req-build-ddeyne\ Complete output (5 lines): Traceback (most recent call last): File "<string>", line 1, in <module> File "c:\users\dl4mhk\appdata\local\temp\pip-req-build-ddeyne\setup.py", line 5, in <module> from chirp import CHIRP_VERSION ImportError: No module named chirp ---------------------------------------- ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output. =================================== log end =================================== style inst-nodeps: F:\Programming\CHiRP\chirp.hg\.tox\.tmp\package\1\UNKNOWN-0.0.0.zip ERROR: invocation failed (exit code 1), logfile: F:\Programming\CHiRP\chirp.hg\.tox\style\log\style-7.log ================================== log start ================================== DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support Processing f:\programming\chirp\chirp.hg\.tox\.tmp\package\1\unknown-0.0.0.zip ERROR: Command errored out with exit status 1: command: 'F:\Programming\CHiRP\chirp.hg\.tox\style\Scripts\python.EXE' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'c:\\users\\dl4mhk\\appdata\\local\\temp\\pip-req-build-rk6uht\\setup.py'"'"'; __file__='"'"'c:\\users\\dl4mhk\\appdata\\local\\temp\\pip-req-build-rk6uht\\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base 'c:\users\dl4mhk\appdata\local\temp\pip-req-build-rk6uht\pip-egg-info' cwd: c:\users\dl4mhk\appdata\local\temp\pip-req-build-rk6uht\ Complete output (5 lines): Traceback (most recent call last): File "<string>", line 1, in <module> File "c:\users\dl4mhk\appdata\local\temp\pip-req-build-rk6uht\setup.py", line 5, in <module> from chirp import CHIRP_VERSION ImportError: No module named chirp ---------------------------------------- ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output. =================================== log end =================================== ___________________________________ summary ___________________________________ ERROR: unit: InvocationError for command 'F:\Programming\CHiRP\chirp.hg\.tox\unit\Scripts\python.EXE' -m pip install --no-deps -U '.tox\.tmp\package\1\UNKNOWN-0.0.0.zip' (exited with code 1) ERROR: driver: InvocationError for command 'F:\Programming\CHiRP\chirp.hg\.tox\driver\Scripts\python.EXE' -m pip install --no-deps -U '.tox\.tmp\package\1\UNKNOWN-0.0.0.zip' (exited with code 1) ERROR: style: InvocationError for command 'F:\Programming\CHiRP\chirp.hg\.tox\style\Scripts\python.EXE' -m pip install --no-deps -U '.tox\.tmp\package\1\UNKNOWN-0.0.0.zip' (exited with code 1) No module named chirp? What did I miss to do? 2) When trying to create a Windows executable using "run ./build/make_Win32_build.sh", it fails: this script is not present. Running Python 2.7.17 on Windows 10. Any input would be appreciated! 73, Bernhard AE6YN

2 3

[chirp_devel] New driver for Kenwood TM-D710G in true clone mode
by Rick DeWitt AA0RD 22 Dec '19

22 Dec '19

New true clone-mode driver for Kenwood TMD-710G. Uses PROG MCP mode for binary image download/upload. -- Rick DeWitt AA0RD Sequim, Washington, USA 98382 (360) 681-3494

2 4