- Developers - lists.chirpmyradio.com

Re: [chirp_devel] Modernizing
by Dan Smith 10 Jun '18

10 Jun '18

(re-adding the list since you dropped it) > Thanks Dan - Snark accepted, passion expected. 😊 \o/ > I dug back through the archives for over a year and hadn't seen ay discussion around this, so while it may be a repeat, it's worth rehashing as technology trends change. Moving technology targets are a thing I have to deal with constantly, annd we often find that an idea that was discarded last year makes more sense this year as the technology evolves. It's fine. It has come up and been discussed. People may just not be paying attention to to this thread as a result, is all. > While Python 3 may be a psychological thing (in my opinion) for attracting contributors, the ability to improve the UI is a user concern. Yes, you can use PyGObject with 2.7, you can also use it with 3.5. I'm not necessarily married to GTK as the sole framework for the UI when there are many other options out there. If you are, then I'd like to know, because if I start working on UI related work then I don't want to have it be throwaway. Nope, I'm not married to GTK. I didn't know GTK before I started on chirp (and it probably shows), but it was the defacto framework for my platform, and worked elsewhere so it was an easy choice. Since then, I've spent plenty of time fighting with it (especially getting a native, non-X11, set of libraries compiled and working on MacOS, which I'm now afraid to touch). Thus, other frameworks that may be more cross-platform have certainly crossed my mind whilst waging said fights. > That's also why I thought it would be better to modernize the backend code before tackling the UI, because regardless of the future UI design, Python 2.7 is not going to be supported indefinitely, and if we do decide to go down a path that requires python 3.x (let's say 3.5 for now to avoide the XP quesiton, more on that below) then at least the rest of the code is ready. I realize there is less immediate gain in making that change, but that's my service engineering bias coming through - I like to focus on the fundamentals and worry about prettifying later. The modernizing the backend benefits me regardless of the progress on the UI (so long as we don't modernize past 2.7 of course), so I'm happy for you to work on that. I just meant you may spend a lot of time working on that before you get to the point where you can work on the UI. > I also have gone down the path of working on UI first and been crestfallen when I realized that some assumptions I made about how things would work when I got the the functional code work required significant refactoring of the UI. The reverse is rarely true - if you write code that can be unit tested, it's rarely a major problem to get a UI framework to consume it, and in fact knowing what the functional code looks like can help inform UI decisions. > Thanks for including Jim and Rick. They are the other folks I was thinking specifically that I would like to hear from, but your opinion on who the key stakeholders are is more relevant than mine, which are based largely on reading the list for the past year or so. > > "people show up all the time complaining about our process (or something else), having never submitted a patch" - Is that not indicative of a problem with the process 😊 No, because regardless of the process, someone will be comfortable with something else. In almost every community I've ever participated in, regardless of if it was patch-on-list, gerrit, github, launchpad, etc.. A certain slice of people show up and hate on the process. Purists who use text-based readers and refuse to use a web browser, and young kids who don't even have an email account. > Re gridview - that's one example, but its a big one. Maybe it's fixable in the current model, not sure. I seem to recall asking about this a couple of years ago and being told that it wasn't fixable because it was inherent in how GTK worked. I think the "click to highlight, then click to adjust" behavior is somewhat inherent in the gridview, and I don't think GTK3 will change it, but I could be wrong. It feels very natural to me, so I'm not sure why it feels so unnatural to others, but I guess it's what you're used to. > Things like hitting tab which in most windows apps moves you to the next cell but in chirp moves you off of the grid vew, This is just sloppy tab order handling in our code, AFAIK. GTK3 isn't going to do this for you by default and is fixable in the current stuff. > or how if I encounter an error (e.g. I type a frequency incorrectly) the entire grid reloads and I have to go find the memory I was working on again This behavior is in chirp code and can be fixed. It's been a long time, but I think it's just because at the point when we detect that error, the easiest thing to do is to revert the value is reload the whole thing. It could be finer-grained, I've just never heard anyone complain about it. > (assuming that it didn't glitch out and completely blank the page which sometimes happens and I think is actually a GTK bug as I can't find anything in chirp which would cause it). Yeah, I've never seen this, so maybe it's a GTK on windows thing I guess. > I'll look into fixing a few of my pet peeves that seem more manageable though (ctrl+c/ctrl+x in a cell does nothing, if I click on a frequency of an unused memory and do absolutely nothing then there's no need to throw an error, I *think* we can detect that nothing in that record was changed and decide it's still unused, but it would probably require moving the population of default options to a different point in the code). The copy/paste in a cell is probably because I'm grabbing those keys at a higher level so I can copy a whole memory, perhaps preventing the inate plaintext behavior in the widget itself. > I won't submit via patchbomb though. I really don't like the idea of having a plaintext app password sitting on my hard drive. Yes, it's just an app password, but an app password is enough to start using my account as a spambot until google or Microsoft ban me if my PC gets compromised. Heh, okay, that's what app passwords are for, but as you wish. You can email patches from your client if it bothers you. > As to the XP discussion, I am typing this and doing my chirp development on a PC that is now 11 years old. Windows 10 runs better on it than XP ever did. 7 and 8 were not great, but 10 is fantastic on old hardware. > I'm fine sticking with 3.5 for a time to keep XP support alive, but i'd like to at least do something to encourage people to upgrade (e.g. implement a new whizbang feature that only works on supported Windows versions). Especially if we continue asking people to store mail passwords in plaintext on an insecure, unsupported OS. 😊 I've yet to encounter something I can't get to work on Windows 10, I've gotten the full suite of MARS software running, used all manner of logging, sdr, antena deisgn, etc... software, and the only time I have had to make a special accomodation is when I was trying to run native dos apps, which I believe also requires workarounds on xp. I can't imagine that the people who have all kinds of special software setup on XP are the same people who are emailing you about how to download or how to submit a bug. I would suspect that the people who fall into those buckets are more likely to be users who just want to program their Baofeng to use GMRS frequencies. Well, I doubt we're going to agree on this, but even if I /was/ interested in buying 10 for my spare machine that I use for random tasks, and even if I did find 10 anything less than maddening to use, it's the large XP userbase that is the important thing here. Assuming you're not going to be buying them memory and OS upgrades, we can just agree to disagree right? Punishing users that haven't upgraded just because we think they should change isn't something I'm into, just FYI. > I also just saw Jim's reply. Specifically to Jim's point, there are numerous guides that cover mapping mercurial workflows to git, however we could also move to git and allow you to continue using the mercurial client via a plugin for hg if you are more comfortable with that. I can personally help you with the move, if that's a path that we go down. > > I will start submitting using hg, that's fine. I was suggesting GitHub for the modernizing process so that I can keep my hg repo setup for patching, and so that we can have multiple people working on the upgrade code without destabilizing the mainline code. When we have patches that are ready to go into the mainline code, then I will submit those patches via hg until and unless we move to git. This will also give me a good spot to start helping Jim and others who don't know git learn how to use git or use hg-git (or is it git hg, I lost track 😊). I'll start doing some thinking and planning for a switch to git. I'm glad Jim is willing to try it, and I can keep a mercurial mirror of the tree for the foreseeable future if it helps the existing developers. > BTW - in git, attaching images to a patch should work just fine. By default, git will treat them as a binary file and just show that they are there without trying to diff them. BTW - in mercurial, this works fine as well. Mercurial can even generate git-format patches with binary encoding. See 'hg export --git' when you start working on your patches :) --Dan

1 0

[chirp_devel] Modernizing
by Derek Chauran 09 Jun '18

09 Jun '18

I have been thinking about this for a while, but Terrence's API/module & Dan's feedback have spurred me to put it out there. What are people's thoughts on starting to port Chirp to Python 3/GTK+, and moving to GitHub? Both are things that I think would help encourage more people to develop for Chirp. Most young and enthusiastic developers don't want to work with old versions of a programming language. As to the GitHub question, while it may seem like a small thing, I also believe that comfort level with the development process is important to attract developers. GitHub has massive adoption, and most developers I know have some degree of comfort working in git environments, whereas I get blank stares when I mention mercurial. There are a few discussion points that jump out at me. I'll throw them out there to start the discussion, but I know there are many other points to be made. 1. No XP support past Python 3.5. I think this is actually a good thing. I have never used XP for anything HAM radio related and it has not held me back. As technology enthusiasts, I tihnk it's silly that many hams still client to an old, unsupported and insecure OS. I have old EF Johnson land mobile radios that i can program from Windows 10 using DOSBox. Given that Chirp is a major part of the amateur radio world, deciding to no longer support an OS that the maker doesn't even support would be a factor in getting people to upgrade. 2. With Python 3, we get GTK3+. GTK+ has many enhancements that will help with some of the kunkiness inherent in the version of GTK that Chirp is built agianst. (see e.g. GIMP for windows). Of course, if Terrence's API idea pans out, then there are many other GUI options for Python 3 (PyQT, Kivy, Tkinter, etc...) 3. Git is too complex - while this can be true, when it comes to developing on GitHub, there are established patterns and simple commands to accomplish most tasks. This complexity also comes with flexibility. If I am working on a major change in git (say, upgrading from Python 2.7 to 3.6), but I run across a small bug in the production code that I want to fix, git makes it easy to put aside my other changes and fix the quick bug. During my daily workflow at work, I often switch between several branches in a repo, wiith a small set of commands. There are something like 5 commands that I use on a day to day basis with git. (git pull, git push, git checkout, git commit). Conversely, I find the patchbomb process to be a bit convoluted vs pull requests. Of course, there is also a mercurial plugin that allows mercurial users to work against GitHub repos: https://bitbucket.org/durin42/hg-git/overview [https://d301sr5gafysq2.cloudfront.net/a6f25d658c68/img/repo-avatars/default…]<https://bitbucket.org/durin42/hg-git/overview> durin42 / hg-git — Bitbucket<https://bitbucket.org/durin42/hg-git/overview> This is the Hg-Git plugin for Mercurial, adding the ability to push and pull to/from a Git server repository from Hg. This means you can collaborate on Git based projects from Hg, or use a Git server as a collaboration point for a team with developers using both Git and Hg. The Hg-Git plugin can ... bitbucket.org 4. Git is destructive - This is not really true. In fact, the opposite is true. When you roll back a commit in HG, that commit is gone. In GIT, that commit is still available via the reflog for 30 days. The main repo will be controlled with gated checkins anyhow. 5. Github comes with its own documentation/hosting system with native support for markdown. 6. Python itself is hosted on GitHub. 7. GitHub makes it easy to share branches, so we can have multiple people collaborate on large projects (e.g. upgrading Python). 8. Time - moving to GitHub is fairly straightforward. They provide examples of exporting from HG into git. That said, unless Dan wants to (temporarily) hand over control of the repo, it's his time, not mine so I cannot speak for him there. Once that move is complete, again the python work can be staged in a separate brach and worked on as time permits while being set aside for other features that need attention in mainline. Anyhow, I'd love to hear what other people's thoughts are on this. I don't want to go down a path that will be outright rejected 😊 Thanks, Derek

4 7

Re: [chirp_devel] Modernizing
by Tyler Tidman 09 Jun '18

09 Jun '18

Derek: It's really awesome that you (and others) have been discussing/considering such improvements. I also feel that CHIRP is a super valuable tool with a friendly and savvy community which is why I keep on reading the devel list and try to promote CHIRP to others whenever I can. I am ashamed to admit that my personal todo list items related to CHIRP have been ignored for a while now due to time and other pressures, however, your proposal is getting my creative juices flowing. Python2 is, technically, EOL in a mere 1.5 years and I'm pretty sure my own scripts are likely going to still need updating by then given all my other distractions. I like the idea of incremental improvements to move to Python3 even without considering any of the fancier GUI stuff. Although, kivy might be a neat add-on later too. It might be fun to fight with more Python2-to-3 migrations after work too :) I know there used to be a dedicated CHIRP CLI tool at one point but I'm not certain what happened to it. Such things would be really handy while trying to update half a dozen radios at one sitting, say, a couple days before a weekend thing-a-thon when somebody adds a new repeater and I'm too lazy and/or busy packing to fuss around with clicking on things to update them all again. An API would be pretty slick. I have often wished to use my usual git tools, workflow and feature branches while working on CHIRP things--it would likely have made it easier in the past for me to find some time in-between other tasks to work on stuff. Using the hg-git backend would be very nice and would also allow others to retain their hg tools, workflow and so on as well. I do not want to add any additional burden to Dan's life either so I will understand if such a drastic backend change doesn't get implemented anytime soon. The patch process works alright but it does mean that I don't tend to rebase very often or work on a lot of different issues at the same time and it does also mean that I can't easily share feature branches between my home computer and work computer. It's not hg's fault, it's mine (probably)--I've been using git daily for over a decade so it's a bit hard for me to go back to doing things with patch. I have maintained my own git clone of CHIRP using git-hg (not to be confused with hg-git) to provide a more convenient interface for browsing stuff, however, this clone isn't sustainable for long term use as the commit IDs aren't deterministric unless the hg-git backend is used so I treat my clone more as a disposable thing. I like most of the added features of GitHub and the convenient pull-request review interface but, as it's all just git underneath, it does make it fairly easy to push another copy to GitLab and/or Bitbucket for when the borg eventually comes to assimilate all your private repos. I really don't care whether it's hosted on GitHub, GitLab, Bitbucket, Gitosis or whatever; Just that I can use the same git command-line stuff to let me browse the history and keep track of my junk that's still in progress. So, in short, I like where you're going with this and I will try to help. I do hope that some of your proposed changes might help improve my velocity when trying to do refactors in CHIRP. I would also really love to be able to learn by doing with the help of code review comments and perhaps have some more directed and interactive sessions collaborating on a refactor rather than just letting my private feature branches languish on my machine. Thanks and 73, Tyler VA3DGN On 08/06/18 03:00 PM, chirp_devel-request(a)intrepid.danplanet.com wrote: > Message: 1 > Date: Fri, 8 Jun 2018 08:44:20 +0000 > From: Derek Chauran <af7ux(a)outlook.com> > Subject: [chirp_devel] Modernizing > To: "chirp_devel(a)intrepid.danplanet.com" > <chirp_devel(a)intrepid.danplanet.com> > Message-ID: > <MWHPR13MB0896ACF6D5270D897D27668EE1670(a)MWHPR13MB0896.namprd13.prod.outlook.com> > > Content-Type: text/plain; charset="utf-8" > > I have been thinking about this for a while, but Terrence's API/module & Dan's feedback have spurred me to put it out there. > > What are people's thoughts on starting to port Chirp to Python 3/GTK+, and moving to GitHub? Both are things that I think would help encourage more people to develop for Chirp. Most young and enthusiastic developers don't want to work with old versions of a programming language. As to the GitHub question, while it may seem like a small thing, I also believe that comfort level with the development process is important to attract developers. GitHub has massive adoption, and most developers I know have some degree of comfort working in git environments, whereas I get blank stares when I mention mercurial. > > There are a few discussion points that jump out at me. I'll throw them out there to start the discussion, but I know there are many other points to be made. > > 1. No XP support past Python 3.5. I think this is actually a good thing. I have never used XP for anything HAM radio related and it has not held me back. As technology enthusiasts, I tihnk it's silly that many hams still client to an old, unsupported and insecure OS. I have old EF Johnson land mobile radios that i can program from Windows 10 using DOSBox. Given that Chirp is a major part of the amateur radio world, deciding to no longer support an OS that the maker doesn't even support would be a factor in getting people to upgrade. > 2. With Python 3, we get GTK3+. GTK+ has many enhancements that will help with some of the kunkiness inherent in the version of GTK that Chirp is built agianst. (see e.g. GIMP for windows). Of course, if Terrence's API idea pans out, then there are many other GUI options for Python 3 (PyQT, Kivy, Tkinter, etc...) > 3. Git is too complex - while this can be true, when it comes to developing on GitHub, there are established patterns and simple commands to accomplish most tasks. This complexity also comes with flexibility. If I am working on a major change in git (say, upgrading from Python 2.7 to 3.6), but I run across a small bug in the production code that I want to fix, git makes it easy to put aside my other changes and fix the quick bug. During my daily workflow at work, I often switch between several branches in a repo, wiith a small set of commands. There are something like 5 commands that I use on a day to day basis with git. (git pull, git push, git checkout, git commit). Conversely, I find the patchbomb process to be a bit convoluted vs pull requests. Of course, there is also a mercurial plugin that allows mercurial users to work against GitHub repos: https://bitbucket.org/durin42/hg-git/overview > [https://d301sr5gafysq2.cloudfront.net/a6f25d658c68/img/repo-avatars/default…]<https://bitbucket.org/durin42/hg-git/overview> > > durin42 / hg-git ? Bitbucket<https://bitbucket.org/durin42/hg-git/overview> > This is the Hg-Git plugin for Mercurial, adding the ability to push and pull to/from a Git server repository from Hg. This means you can collaborate on Git based projects from Hg, or use a Git server as a collaboration point for a team with developers using both Git and Hg. The Hg-Git plugin can ... > bitbucket.org > > > 4. Git is destructive - This is not really true. In fact, the opposite is true. When you roll back a commit in HG, that commit is gone. In GIT, that commit is still available via the reflog for 30 days. The main repo will be controlled with gated checkins anyhow. > 5. Github comes with its own documentation/hosting system with native support for markdown. > 6. Python itself is hosted on GitHub. > 7. GitHub makes it easy to share branches, so we can have multiple people collaborate on large projects (e.g. upgrading Python). > 8. Time - moving to GitHub is fairly straightforward. They provide examples of exporting from HG into git. That said, unless Dan wants to (temporarily) hand over control of the repo, it's his time, not mine so I cannot speak for him there. Once that move is complete, again the python work can be staged in a separate brach and worked on as time permits while being set aside for other features that need attention in mainline. > > Anyhow, I'd love to hear what other people's thoughts are on this. I don't want to go down a path that will be outright rejected ? > > Thanks, > Derek >

1 0

Re: [chirp_devel] chirp_devel Digest, Vol 86, Issue 5
by David Spoelstra 08 Jun '18

08 Jun '18

I think this is a great idea! I've been putting off making a few changes because I would have to install and learn mercurial and everything I do is in git. Also, what you said about running the newest programming languages is true. However, I urge you to think even further! I've been thinking about Chirp running on a web-based platform! You could use GDocs for most of the interface. Combine that with Javascript and Electron (electronjs.org) and now you have an app that would run on all platforms (Linux, Mac, Win) with no additional work. More and more apps are moving to this model. For example, Slack and Visual Studio Code are Electron apps. The WebUSB API makes it easy to talk to and run USB dongles with Javascript. -David, N9KT On Fri, Jun 8, 2018 at 3:06 PM <chirp_devel-request(a)intrepid.danplanet.com> wrote: > Send chirp_devel mailing list submissions to > chirp_devel(a)intrepid.danplanet.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://intrepid.danplanet.com/mailman/listinfo/chirp_devel > or, via email, send a message with subject or body 'help' to > chirp_devel-request(a)intrepid.danplanet.com > > You can reach the person managing the list at > chirp_devel-owner(a)intrepid.danplanet.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of chirp_devel digest..." > > > Today's Topics: > > 1. Modernizing (Derek Chauran) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 8 Jun 2018 08:44:20 +0000 > From: Derek Chauran <af7ux(a)outlook.com> > Subject: [chirp_devel] Modernizing > To: "chirp_devel(a)intrepid.danplanet.com" > <chirp_devel(a)intrepid.danplanet.com> > Message-ID: > < > MWHPR13MB0896ACF6D5270D897D27668EE1670(a)MWHPR13MB0896.namprd13.prod.outlook.com > > > > Content-Type: text/plain; charset="utf-8" > > I have been thinking about this for a while, but Terrence's API/module & > Dan's feedback have spurred me to put it out there. > > What are people's thoughts on starting to port Chirp to Python 3/GTK+, and > moving to GitHub? Both are things that I think would help encourage more > people to develop for Chirp. Most young and enthusiastic developers don't > want to work with old versions of a programming language. As to the GitHub > question, while it may seem like a small thing, I also believe that comfort > level with the development process is important to attract developers. > GitHub has massive adoption, and most developers I know have some degree of > comfort working in git environments, whereas I get blank stares when I > mention mercurial. > > There are a few discussion points that jump out at me. I'll throw them out > there to start the discussion, but I know there are many other points to be > made. > > 1. No XP support past Python 3.5. I think this is actually a good > thing. I have never used XP for anything HAM radio related and it has not > held me back. As technology enthusiasts, I tihnk it's silly that many hams > still client to an old, unsupported and insecure OS. I have old EF Johnson > land mobile radios that i can program from Windows 10 using DOSBox. Given > that Chirp is a major part of the amateur radio world, deciding to no > longer support an OS that the maker doesn't even support would be a factor > in getting people to upgrade. > 2. With Python 3, we get GTK3+. GTK+ has many enhancements that will > help with some of the kunkiness inherent in the version of GTK that Chirp > is built agianst. (see e.g. GIMP for windows). Of course, if Terrence's API > idea pans out, then there are many other GUI options for Python 3 (PyQT, > Kivy, Tkinter, etc...) > 3. Git is too complex - while this can be true, when it comes to > developing on GitHub, there are established patterns and simple commands to > accomplish most tasks. This complexity also comes with flexibility. If I am > working on a major change in git (say, upgrading from Python 2.7 to 3.6), > but I run across a small bug in the production code that I want to fix, git > makes it easy to put aside my other changes and fix the quick bug. During > my daily workflow at work, I often switch between several branches in a > repo, wiith a small set of commands. There are something like 5 commands > that I use on a day to day basis with git. (git pull, git push, git > checkout, git commit). Conversely, I find the patchbomb process to be a bit > convoluted vs pull requests. Of course, there is also a mercurial plugin > that allows mercurial users to work against GitHub repos: > https://bitbucket.org/durin42/hg-git/overview > [ > https://d301sr5gafysq2.cloudfront.net/a6f25d658c68/img/repo-avatars/default… > ]<https://bitbucket.org/durin42/hg-git/overview> > > durin42 / hg-git ? Bitbucket<https://bitbucket.org/durin42/hg-git/overview > > > This is the Hg-Git plugin for Mercurial, adding the ability to push and > pull to/from a Git server repository from Hg. This means you can > collaborate on Git based projects from Hg, or use a Git server as a > collaboration point for a team with developers using both Git and Hg. The > Hg-Git plugin can ... > bitbucket.org > > > 4. Git is destructive - This is not really true. In fact, the opposite > is true. When you roll back a commit in HG, that commit is gone. In GIT, > that commit is still available via the reflog for 30 days. The main repo > will be controlled with gated checkins anyhow. > 5. Github comes with its own documentation/hosting system with native > support for markdown. > 6. Python itself is hosted on GitHub. > 7. GitHub makes it easy to share branches, so we can have multiple > people collaborate on large projects (e.g. upgrading Python). > 8. Time - moving to GitHub is fairly straightforward. They provide > examples of exporting from HG into git. That said, unless Dan wants to > (temporarily) hand over control of the repo, it's his time, not mine so I > cannot speak for him there. Once that move is complete, again the python > work can be staged in a separate brach and worked on as time permits while > being set aside for other features that need attention in mainline. > > Anyhow, I'd love to hear what other people's thoughts are on this. I don't > want to go down a path that will be outright rejected ? > > Thanks, > Derek >

1 0

Re: [chirp_devel] A module that provides Chirp functionalities to custom python scripts #5859
by Terence Paddack 07 Jun '18

07 Jun '18

Dan, Thanks for the suggestions and words of encouragement. I will work on this over the summer and re-submit when it's done. I knew it still needed some work, so I hadn't really given much thought to it's potential applications in the UI. I am open to suggestions regarding the name, but (if possible) I'd like to keep it short. As I get deeper into implementing your suggestions I may have some follow-up questions, is that cool? Regards, -- Terence C. Paddack MS, MLS(ASCP)CM

2 1

[chirp_devel] How to Make an Issue as Duplicate
by Rick DeWitt 06 Jun '18

06 Jun '18

Dan- While I'm working on the FT-450D driver patch fixes I have attached an image file for you to play with. But one question: How do I mark those 'old' issue #'s as duplicate? I don't see that as a Status option. I can mark the newest ones Rejected and say 'Duplicate of xxx' in the Notes field.....? -- Rick DeWitt AA0RD Sequim, Washington, USA 360-681-3494

2 1

[chirp_devel] Build test results: Successful
by Build System 06 Jun '18

06 Jun '18

Tested changes: Changes for Build #744 [Dan Smith <dsmith(a)danplanet.com>] Fix Jetstream 270MH offset and mode/power bugs The mode bit is elsewhere, and the power field is actually two bits. Also, the offset for the start of the alpha tags was wrong, causing the tags to be out of sync with the memory channels. #5865 [Tom Hayward <tom(a)tomh.us>] [id880] Fix typo in charset definition. #281 [Tom Hayward <tom(a)tomh.us>] [thf6a] Support full charset (ASCII). Fixes #141 [Tom Hayward <tom(a)tomh.us>] [id880] Support full charset. Fixes #281 [Tom Hayward <tom(a)tomh.us>] [vx5] Support full charset (ASCII). Fixes #292 [Tom Hayward <tom(a)tomh.us>] [id31a] set used bit when creating new memory, clear when deleting. Fixes #269 [Tom Hayward <tom(a)tomh.us>] Support PyGTK < 2.22 in bank edit. Fixes #231 [Tom Hayward <tom(a)tomh.us>] [d710] [v71] [d72] Fix tone list (not all tones are supported). Fixes #212 [Dan Smith <dsmith(a)danplanet.com>] [vx7] Fix setting memory power levels on 220MHz band Fixes #214 [Dan Smith <dsmith(a)danplanet.com>] fips: Pennsylvania FIPS code was wrong. #117 [Marco Filippi <iz3gme.marco(a)gmail.com>] Consider lower bound frequency of each valid_band as valid Fix bug #181 [Tom Hayward <tom(a)tomh.us>] tmd700: allow 8-char names. Fixes #176 [Dan Smith <dsmith(a)danplanet.com>] Fix the "blind deletion" problem, as well as properly direct copy/paste Fixes #172 [David Griffith <dave(a)661.org>] Bug #155 fix: VX-7 1.25m power levels [David Griffith <dave(a)661.org>] New INSTALL and README files Fixes #122 [Tom Hayward <tom(a)tomh.us>] thd72: only use hardware flow on OS X. Fixes #166 [Marco Filippi <iz3gme.marco(a)gmail.com>] [FT817] Tone freq not set correctly Same as #88 for FT857, to avoid code duplication fix code have been moved from ft857 to its ancestor class Fix bug #163 [Tom Hayward <tom(a)tomh.us>] Fix Mac .app so paths with spaces work. Fixes Bug #145 Full log: [...truncated 165 lines...] test_remove_memory_from_mapping_wrong_bank (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_set_memory_index (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_set_memory_index_bad_bank (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_set_memory_index_bad_index (tests.unit.test_mappingmodel.TestIcomIndexedBankModel) ... ok test_auto_tone_mode_cross (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_dtcs (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_dtcs_pol (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_dtcs_rx (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_tone (tests.unit.test_memedit_edits.TestEdits) ... ok test_auto_tone_mode_tsql (tests.unit.test_memedit_edits.TestEdits) ... ok test_init (tests.unit.test_platform.Win32PlatformTest) ... ok test_serial_ports_bad_portnames (tests.unit.test_platform.Win32PlatformTest) ... ok test_serial_ports_sorted (tests.unit.test_platform.Win32PlatformTest) ... ok test_apply_callback (tests.unit.test_settings.TestSettingContainers) ... ok test_radio_setting (tests.unit.test_settings.TestSettingContainers) ... ok test_radio_setting_group (tests.unit.test_settings.TestSettingContainers) ... ok test_radio_setting_multi (tests.unit.test_settings.TestSettingContainers) ... ok test_changed (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_boolean (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_float (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_integer (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_list (tests.unit.test_settings.TestSettingValues) ... ok test_radio_setting_value_string (tests.unit.test_settings.TestSettingValues) ... ok test_validate_callback (tests.unit.test_settings.TestSettingValues) ... ok test_delete_hole_with_all (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_delete_hole_with_all_full (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_delete_hole_with_hole (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_delete_hole_without_hole (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_insert_hole_with_space (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok test_insert_hole_without_space (tests.unit.test_shiftdialog.ShiftDialogTest) ... ok ---------------------------------------------------------------------- Ran 151 tests in 0.067s OK unit runtests: commands[1] | python ./share/make_supported.py /dev/null driver create: /chirp.hg/.tox/driver driver inst: /chirp.hg/.tox/dist/chirp-0.3.0dev.zip driver installed: chirp==0.3.0.dev0,mercurial==3.7.3,pluggy==0.6.0,py==1.5.3,pyserial==3.0.1,six==1.11.0,tox==2.9.1,virtualenv==15.2.0 driver runtests: PYTHONHASHSEED='1776514870' driver runtests: commands[0] | python -munittest -vb tests test_banks (tests.TestCase_BaofengBFT1) Testing Baofeng BF-T1 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BaofengBFT1) Testing Baofeng BF-T1 brute force ... ok test_clone (tests.TestCase_BaofengBFT1) Testing Baofeng BF-T1 clone ... ok test_copy_all (tests.TestCase_BaofengBFT1) Testing Baofeng BF-T1 copy all ... ok test_detect (tests.TestCase_BaofengBFT1) Testing Baofeng BF-T1 detect ... ok test_edges (tests.TestCase_BaofengBFT1) Testing Baofeng BF-T1 edges ... ok test_settings (tests.TestCase_BaofengBFT1) Testing Baofeng BF-T1 settings ... ok test_banks (tests.TestCase_IcomICT8A) Testing Icom IC-T8A banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_IcomICT8A) Testing Icom IC-T8A brute force ... ok test_clone (tests.TestCase_IcomICT8A) Testing Icom IC-T8A clone ... ok test_copy_all (tests.TestCase_IcomICT8A) Testing Icom IC-T8A copy all ... ok test_detect (tests.TestCase_IcomICT8A) Testing Icom IC-T8A detect ... ok test_edges (tests.TestCase_IcomICT8A) Testing Icom IC-T8A edges ... ok test_settings (tests.TestCase_IcomICT8A) Testing Icom IC-T8A settings ... skipped 'Settings not supported' test_banks (tests.TestCase_TYTTH9800) Testing TYT TH-9800 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_TYTTH9800) Testing TYT TH-9800 brute force ... ok test_clone (tests.TestCase_TYTTH9800) Testing TYT TH-9800 clone ... ok test_copy_all (tests.TestCase_TYTTH9800) Testing TYT TH-9800 copy all ... ok test_detect (tests.TestCase_TYTTH9800) Testing TYT TH-9800 detect ... ok test_edges (tests.TestCase_TYTTH9800) Testing TYT TH-9800 edges ... ok test_settings (tests.TestCase_TYTTH9800) Testing TYT TH-9800 settings ... ok test_banks (tests.TestCase_KenwoodTK8102) Testing Kenwood TK-8102 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_KenwoodTK8102) Testing Kenwood TK-8102 brute force ... ok test_clone (tests.TestCase_KenwoodTK8102) Testing Kenwood TK-8102 clone ... ok test_copy_all (tests.TestCase_KenwoodTK8102) Testing Kenwood TK-8102 copy all ... ok test_detect (tests.TestCase_KenwoodTK8102) Testing Kenwood TK-8102 detect ... ok test_edges (tests.TestCase_KenwoodTK8102) Testing Kenwood TK-8102 edges ... ok test_settings (tests.TestCase_KenwoodTK8102) Testing Kenwood TK-8102 settings ... ok test_banks (tests.TestCase_IcomID51Plus) Testing Icom ID-51 Plus banks ... ok test_brute_force (tests.TestCase_IcomID51Plus) Testing Icom ID-51 Plus brute force ... ok test_clone (tests.TestCase_IcomID51Plus) Testing Icom ID-51 Plus clone ... ok test_copy_all (tests.TestCase_IcomID51Plus) Testing Icom ID-51 Plus copy all ... ok test_detect (tests.TestCase_IcomID51Plus) Testing Icom ID-51 Plus detect ... ok test_edges (tests.TestCase_IcomID51Plus) Testing Icom ID-51 Plus edges ... ok test_settings (tests.TestCase_IcomID51Plus) Testing Icom ID-51 Plus settings ... ok test_banks (tests.TestCase_BTECHMURSV1) Testing BTECH MURS-V1 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BTECHMURSV1) Testing BTECH MURS-V1 brute force ... ok test_clone (tests.TestCase_BTECHMURSV1) Testing BTECH MURS-V1 clone ... ok test_copy_all (tests.TestCase_BTECHMURSV1) Testing BTECH MURS-V1 copy all ... ok test_detect (tests.TestCase_BTECHMURSV1) Testing BTECH MURS-V1 detect ... ok test_edges (tests.TestCase_BTECHMURSV1) Testing BTECH MURS-V1 edges ... skipped 'No mutable memory locations found' test_settings (tests.TestCase_BTECHMURSV1) Testing BTECH MURS-V1 settings ... ok test_banks (tests.TestCase_YaesuFT2800M) Testing Yaesu FT-2800M banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_YaesuFT2800M) Testing Yaesu FT-2800M brute force ... ok test_clone (tests.TestCase_YaesuFT2800M) Testing Yaesu FT-2800M clone ... ok test_copy_all (tests.TestCase_YaesuFT2800M) Testing Yaesu FT-2800M copy all ... ok test_detect (tests.TestCase_YaesuFT2800M) Testing Yaesu FT-2800M detect ... ok test_edges (tests.TestCase_YaesuFT2800M) Testing Yaesu FT-2800M edges ... ok test_settings (tests.TestCase_YaesuFT2800M) Testing Yaesu FT-2800M settings ... skipped 'Settings not supported' test_banks (tests.TestCase_BTECHUV5001) Testing BTECH UV-5001 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BTECHUV5001) Testing BTECH UV-5001 brute force ... ok test_clone (tests.TestCase_BTECHUV5001) Testing BTECH UV-5001 clone ... ok test_copy_all (tests.TestCase_BTECHUV5001) Testing BTECH UV-5001 copy all ... ok test_detect (tests.TestCase_BTECHUV5001) Testing BTECH UV-5001 detect ... ok test_edges (tests.TestCase_BTECHUV5001) Testing BTECH UV-5001 edges ... ok test_settings (tests.TestCase_BTECHUV5001) Testing BTECH UV-5001 settings ... ok test_banks (tests.TestCase_BTECHUV25X2) Testing BTECH UV-25X2 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BTECHUV25X2) Testing BTECH UV-25X2 brute force ... ok test_clone (tests.TestCase_BTECHUV25X2) Testing BTECH UV-25X2 clone ... ok test_copy_all (tests.TestCase_BTECHUV25X2) Testing BTECH UV-25X2 copy all ... ok test_detect (tests.TestCase_BTECHUV25X2) Testing BTECH UV-25X2 detect ... ok test_edges (tests.TestCase_BTECHUV25X2) Testing BTECH UV-25X2 edges ... ok test_settings (tests.TestCase_BTECHUV25X2) Testing BTECH UV-25X2 settings ... ok test_banks (tests.TestCase_TYTTHUV3R25) Testing TYT TH-UV3R-25 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_TYTTHUV3R25) Testing TYT TH-UV3R-25 brute force ... ok test_clone (tests.TestCase_TYTTHUV3R25) Testing TYT TH-UV3R-25 clone ... ok test_copy_all (tests.TestCase_TYTTHUV3R25) Testing TYT TH-UV3R-25 copy all ... ok test_detect (tests.TestCase_TYTTHUV3R25) Testing TYT TH-UV3R-25 detect ... ok test_edges (tests.TestCase_TYTTHUV3R25) Testing TYT TH-UV3R-25 edges ... ok test_settings (tests.TestCase_TYTTHUV3R25) Testing TYT TH-UV3R-25 settings ... skipped 'Settings not supported' test_banks (tests.TestCase_IcomID880H) Testing Icom ID-880H banks ... ok test_brute_force (tests.TestCase_IcomID880H) Testing Icom ID-880H brute force ... ok test_clone (tests.TestCase_IcomID880H) Testing Icom ID-880H clone ... ok test_copy_all (tests.TestCase_IcomID880H) Testing Icom ID-880H copy all ... ok test_detect (tests.TestCase_IcomID880H) Testing Icom ID-880H detect ... ok test_edges (tests.TestCase_IcomID880H) Testing Icom ID-880H edges ... ok test_settings (tests.TestCase_IcomID880H) Testing Icom ID-880H settings ... ok test_banks (tests.TestCase_YaesuFT70D) Testing Yaesu FT-70D banks ... ok test_brute_force (tests.TestCase_YaesuFT70D) Testing Yaesu FT-70D brute force ... ok test_clone (tests.TestCase_YaesuFT70D) Testing Yaesu FT-70D clone ... ok test_copy_all (tests.TestCase_YaesuFT70D) Testing Yaesu FT-70D copy all ... ok test_detect (tests.TestCase_YaesuFT70D) Testing Yaesu FT-70D detect ... ok test_edges (tests.TestCase_YaesuFT70D) Testing Yaesu FT-70D edges ... ok test_settings (tests.TestCase_YaesuFT70D) Testing Yaesu FT-70D settings ... ok test_banks (tests.TestCase_RetevisRT26) Testing Retevis RT26 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_RetevisRT26) Testing Retevis RT26 brute force ... ok test_clone (tests.TestCase_RetevisRT26) Testing Retevis RT26 clone ... ok test_copy_all (tests.TestCase_RetevisRT26) Testing Retevis RT26 copy all ... ok test_detect (tests.TestCase_RetevisRT26) Testing Retevis RT26 detect ... ok test_edges (tests.TestCase_RetevisRT26) Testing Retevis RT26 edges ... ok test_settings (tests.TestCase_RetevisRT26) Testing Retevis RT26 settings ... ok test_banks (tests.TestCase_BaofengUV6R) Testing Baofeng UV-6R banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BaofengUV6R) Testing Baofeng UV-6R brute force ... ok test_clone (tests.TestCase_BaofengUV6R) Testing Baofeng UV-6R clone ... ok test_copy_all (tests.TestCase_BaofengUV6R) Testing Baofeng UV-6R copy all ... ok test_detect (tests.TestCase_BaofengUV6R) Testing Baofeng UV-6R detect ... ok test_edges (tests.TestCase_BaofengUV6R) Testing Baofeng UV-6R edges ... ok test_settings (tests.TestCase_BaofengUV6R) Testing Baofeng UV-6R settings ... ok test_banks (tests.TestCase_WouxunKGUV6) Testing Wouxun KG-UV6 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_WouxunKGUV6) Testing Wouxun KG-UV6 brute force ... ok test_clone (tests.TestCase_WouxunKGUV6) Testing Wouxun KG-UV6 clone ... ok test_copy_all (tests.TestCase_WouxunKGUV6) Testing Wouxun KG-UV6 copy all ... ok test_detect (tests.TestCase_WouxunKGUV6) Testing Wouxun KG-UV6 detect ... ok test_edges (tests.TestCase_WouxunKGUV6) Testing Wouxun KG-UV6 edges ... ok test_settings (tests.TestCase_WouxunKGUV6) Testing Wouxun KG-UV6 settings ... ok test_banks (tests.TestCase_PuxingPX2R) Testing Puxing PX-2R banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_PuxingPX2R) Testing Puxing PX-2R brute force ... ok test_clone (tests.TestCase_PuxingPX2R) Testing Puxing PX-2R clone ... ok test_copy_all (tests.TestCase_PuxingPX2R) Testing Puxing PX-2R copy all ... ok test_detect (tests.TestCase_PuxingPX2R) Testing Puxing PX-2R detect ... ok test_edges (tests.TestCase_PuxingPX2R) Testing Puxing PX-2R edges ... ok test_settings (tests.TestCase_PuxingPX2R) Testing Puxing PX-2R settings ... skipped 'Settings not supported' test_banks (tests.TestCase_YaesuFT817ND) Testing Yaesu FT-817ND banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_YaesuFT817ND) Testing Yaesu FT-817ND brute force ... ok test_clone (tests.TestCase_YaesuFT817ND) Testing Yaesu FT-817ND clone ... ok test_copy_all (tests.TestCase_YaesuFT817ND) Testing Yaesu FT-817ND copy all ... ok test_detect (tests.TestCase_YaesuFT817ND) Testing Yaesu FT-817ND detect ... ok test_edges (tests.TestCase_YaesuFT817ND) Testing Yaesu FT-817ND edges ... ok test_settings (tests.TestCase_YaesuFT817ND) Testing Yaesu FT-817ND settings ... ok test_banks (tests.TestCase_IcomIC2820H) Testing Icom IC-2820H banks ... ok test_brute_force (tests.TestCase_IcomIC2820H) Testing Icom IC-2820H brute force ... ok test_clone (tests.TestCase_IcomIC2820H) Testing Icom IC-2820H clone ... ok test_copy_all (tests.TestCase_IcomIC2820H) Testing Icom IC-2820H copy all ... ok test_detect (tests.TestCase_IcomIC2820H) Testing Icom IC-2820H detect ... ok test_edges (tests.TestCase_IcomIC2820H) Testing Icom IC-2820H edges ... ok test_settings (tests.TestCase_IcomIC2820H) Testing Icom IC-2820H settings ... ok test_banks (tests.TestCase_JetstreamJT220M) Testing Jetstream JT220M banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_JetstreamJT220M) Testing Jetstream JT220M brute force ... ok test_clone (tests.TestCase_JetstreamJT220M) Testing Jetstream JT220M clone ... ok test_copy_all (tests.TestCase_JetstreamJT220M) Testing Jetstream JT220M copy all ... ok test_detect (tests.TestCase_JetstreamJT220M) Testing Jetstream JT220M detect ... ok test_edges (tests.TestCase_JetstreamJT220M) Testing Jetstream JT220M edges ... ok test_settings (tests.TestCase_JetstreamJT220M) Testing Jetstream JT220M settings ... skipped 'Settings not supported' test_banks (tests.TestCase_AlincoDJ596) Testing Alinco DJ596 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_AlincoDJ596) Testing Alinco DJ596 brute force ... ok test_clone (tests.TestCase_AlincoDJ596) Testing Alinco DJ596 clone ... ok test_copy_all (tests.TestCase_AlincoDJ596) Testing Alinco DJ596 copy all ... ok test_detect (tests.TestCase_AlincoDJ596) Testing Alinco DJ596 detect ... ok test_edges (tests.TestCase_AlincoDJ596) Testing Alinco DJ596 edges ... ok test_settings (tests.TestCase_AlincoDJ596) Testing Alinco DJ596 settings ... skipped 'Settings not supported' test_banks (tests.TestCase_JetstreamJT270MH) Testing Jetstream JT270MH banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_JetstreamJT270MH) Testing Jetstream JT270MH brute force ... ok test_clone (tests.TestCase_JetstreamJT270MH) Testing Jetstream JT270MH clone ... ok test_copy_all (tests.TestCase_JetstreamJT270MH) Testing Jetstream JT270MH copy all ... ok test_detect (tests.TestCase_JetstreamJT270MH) Testing Jetstream JT270MH detect ... ok test_edges (tests.TestCase_JetstreamJT270MH) Testing Jetstream JT270MH edges ... ok test_settings (tests.TestCase_JetstreamJT270MH) Testing Jetstream JT270MH settings ... ok test_banks (tests.TestCase_BTECHUV2501220) Testing BTECH UV-2501+220 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BTECHUV2501220) Testing BTECH UV-2501+220 brute force ... ok test_clone (tests.TestCase_BTECHUV2501220) Testing BTECH UV-2501+220 clone ... ok test_copy_all (tests.TestCase_BTECHUV2501220) Testing BTECH UV-2501+220 copy all ... ok test_detect (tests.TestCase_BTECHUV2501220) Testing BTECH UV-2501+220 detect ... ok test_edges (tests.TestCase_BTECHUV2501220) Testing BTECH UV-2501+220 edges ... ok test_settings (tests.TestCase_BTECHUV2501220) Testing BTECH UV-2501+220 settings ... ok test_banks (tests.TestCase_BTECHUV50X2) Testing BTECH UV-50X2 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BTECHUV50X2) Testing BTECH UV-50X2 brute force ... ok test_clone (tests.TestCase_BTECHUV50X2) Testing BTECH UV-50X2 clone ... ok test_copy_all (tests.TestCase_BTECHUV50X2) Testing BTECH UV-50X2 copy all ... ok test_detect (tests.TestCase_BTECHUV50X2) Testing BTECH UV-50X2 detect ... ok test_edges (tests.TestCase_BTECHUV50X2) Testing BTECH UV-50X2 edges ... ok test_settings (tests.TestCase_BTECHUV50X2) Testing BTECH UV-50X2 settings ... ok test_banks (tests.TestCase_IcomICT7H) Testing Icom IC-T7H banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_IcomICT7H) Testing Icom IC-T7H brute force ... ok test_clone (tests.TestCase_IcomICT7H) Testing Icom IC-T7H clone ... ok test_copy_all (tests.TestCase_IcomICT7H) Testing Icom IC-T7H copy all ... ok test_detect (tests.TestCase_IcomICT7H) Testing Icom IC-T7H detect ... ok test_edges (tests.TestCase_IcomICT7H) Testing Icom IC-T7H edges ... ok test_settings (tests.TestCase_IcomICT7H) Testing Icom IC-T7H settings ... skipped 'Settings not supported' test_banks (tests.TestCase_BaojieBJ9900) Testing Baojie BJ-9900 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BaojieBJ9900) Testing Baojie BJ-9900 brute force ... ok test_clone (tests.TestCase_BaojieBJ9900) Testing Baojie BJ-9900 clone ... ok test_copy_all (tests.TestCase_BaojieBJ9900) Testing Baojie BJ-9900 copy all ... ok test_detect (tests.TestCase_BaojieBJ9900) Testing Baojie BJ-9900 detect ... ok test_edges (tests.TestCase_BaojieBJ9900) Testing Baojie BJ-9900 edges ... ok test_settings (tests.TestCase_BaojieBJ9900) Testing Baojie BJ-9900 settings ... skipped 'Settings not supported' test_banks (tests.TestCase_IcomIC2300H) Testing Icom IC-2300H banks ... ok test_brute_force (tests.TestCase_IcomIC2300H) Testing Icom IC-2300H brute force ... ok test_clone (tests.TestCase_IcomIC2300H) Testing Icom IC-2300H clone ... ok test_copy_all (tests.TestCase_IcomIC2300H) Testing Icom IC-2300H copy all ... ok test_detect (tests.TestCase_IcomIC2300H) Testing Icom IC-2300H detect ... ok test_edges (tests.TestCase_IcomIC2300H) Testing Icom IC-2300H edges ... ok test_settings (tests.TestCase_IcomIC2300H) Testing Icom IC-2300H settings ... ok test_banks (tests.TestCase_YaesuVX7) Testing Yaesu VX-7 banks ... ok test_brute_force (tests.TestCase_YaesuVX7) Testing Yaesu VX-7 brute force ... ok test_clone (tests.TestCase_YaesuVX7) Testing Yaesu VX-7 clone ... ok test_copy_all (tests.TestCase_YaesuVX7) Testing Yaesu VX-7 copy all ... ok test_detect (tests.TestCase_YaesuVX7) Testing Yaesu VX-7 detect ... ok test_edges (tests.TestCase_YaesuVX7) Testing Yaesu VX-7 edges ... ok test_settings (tests.TestCase_YaesuVX7) Testing Yaesu VX-7 settings ... skipped 'Settings not supported' test_banks (tests.TestCase_TDXoneTDQ8A) Testing TDXone TD-Q8A banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_TDXoneTDQ8A) Testing TDXone TD-Q8A brute force ... ok test_clone (tests.TestCase_TDXoneTDQ8A) Testing TDXone TD-Q8A clone ... ok test_copy_all (tests.TestCase_TDXoneTDQ8A) Testing TDXone TD-Q8A copy all ... ok test_detect (tests.TestCase_TDXoneTDQ8A) Testing TDXone TD-Q8A detect ... ok test_edges (tests.TestCase_TDXoneTDQ8A) Testing TDXone TD-Q8A edges ... ok test_settings (tests.TestCase_TDXoneTDQ8A) Testing TDXone TD-Q8A settings ... ok test_banks (tests.TestCase_WouxunKG818) Testing Wouxun KG-818 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_WouxunKG818) Testing Wouxun KG-818 brute force ... ok test_clone (tests.TestCase_WouxunKG818) Testing Wouxun KG-818 clone ... ok test_copy_all (tests.TestCase_WouxunKG818) Testing Wouxun KG-818 copy all ... ok test_detect (tests.TestCase_WouxunKG818) Testing Wouxun KG-818 detect ... ok test_edges (tests.TestCase_WouxunKG818) Testing Wouxun KG-818 edges ... ok test_settings (tests.TestCase_WouxunKG818) Testing Wouxun KG-818 settings ... ok test_banks (tests.TestCase_WACCOMMINI8900) Testing WACCOM MINI-8900 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_WACCOMMINI8900) Testing WACCOM MINI-8900 brute force ... ok test_clone (tests.TestCase_WACCOMMINI8900) Testing WACCOM MINI-8900 clone ... ok test_copy_all (tests.TestCase_WACCOMMINI8900) Testing WACCOM MINI-8900 copy all ... ok test_detect (tests.TestCase_WACCOMMINI8900) Testing WACCOM MINI-8900 detect ... ok test_edges (tests.TestCase_WACCOMMINI8900) Testing WACCOM MINI-8900 edges ... ok test_settings (tests.TestCase_WACCOMMINI8900) Testing WACCOM MINI-8900 settings ... ok test_banks (tests.TestCase_BaofengUV3R) Testing Baofeng UV-3R banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BaofengUV3R) Testing Baofeng UV-3R brute force ... ok test_clone (tests.TestCase_BaofengUV3R) Testing Baofeng UV-3R clone ... ok test_copy_all (tests.TestCase_BaofengUV3R) Testing Baofeng UV-3R copy all ... ok test_detect (tests.TestCase_BaofengUV3R) Testing Baofeng UV-3R detect ... ok test_edges (tests.TestCase_BaofengUV3R) Testing Baofeng UV-3R edges ... ok test_settings (tests.TestCase_BaofengUV3R) Testing Baofeng UV-3R settings ... ok test_banks (tests.TestCase_AnyToneTERMN8R) Testing AnyTone TERMN-8R banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_AnyToneTERMN8R) Testing AnyTone TERMN-8R brute force ... ok test_clone (tests.TestCase_AnyToneTERMN8R) Testing AnyTone TERMN-8R clone ... ok test_copy_all (tests.TestCase_AnyToneTERMN8R) Testing AnyTone TERMN-8R copy all ... ok test_detect (tests.TestCase_AnyToneTERMN8R) Testing AnyTone TERMN-8R detect ... ok test_edges (tests.TestCase_AnyToneTERMN8R) Testing AnyTone TERMN-8R edges ... ok test_settings (tests.TestCase_AnyToneTERMN8R) Testing AnyTone TERMN-8R settings ... ok test_banks (tests.TestCase_YaesuFT50) Testing Yaesu FT-50 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_YaesuFT50) Testing Yaesu FT-50 brute force ... ok test_clone (tests.TestCase_YaesuFT50) Testing Yaesu FT-50 clone ... ok test_copy_all (tests.TestCase_YaesuFT50) Testing Yaesu FT-50 copy all ... ok test_detect (tests.TestCase_YaesuFT50) Testing Yaesu FT-50 detect ... ok test_edges (tests.TestCase_YaesuFT50) Testing Yaesu FT-50 edges ... ok test_settings (tests.TestCase_YaesuFT50) Testing Yaesu FT-50 settings ... ok test_banks (tests.TestCase_IcomICP7) Testing Icom IC-P7 banks ... ok test_brute_force (tests.TestCase_IcomICP7) Testing Icom IC-P7 brute force ... ok test_clone (tests.TestCase_IcomICP7) Testing Icom IC-P7 clone ... ok test_copy_all (tests.TestCase_IcomICP7) Testing Icom IC-P7 copy all ... ok test_detect (tests.TestCase_IcomICP7) Testing Icom IC-P7 detect ... ok test_edges (tests.TestCase_IcomICP7) Testing Icom IC-P7 edges ... ok test_settings (tests.TestCase_IcomICP7) Testing Icom IC-P7 settings ... ok test_banks (tests.TestCase_IcomICW32E) Testing Icom IC-W32E banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_IcomICW32E) Testing Icom IC-W32E brute force ... ok test_clone (tests.TestCase_IcomICW32E) Testing Icom IC-W32E clone ... ok test_copy_all (tests.TestCase_IcomICW32E) Testing Icom IC-W32E copy all ... ok test_detect (tests.TestCase_IcomICW32E) Testing Icom IC-W32E detect ... ok test_edges (tests.TestCase_IcomICW32E) Testing Icom IC-W32E edges ... ok test_settings (tests.TestCase_IcomICW32E) Testing Icom IC-W32E settings ... skipped 'Settings not supported' test_banks (tests.TestCase_JetstreamJT270M) Testing Jetstream JT270M banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_JetstreamJT270M) Testing Jetstream JT270M brute force ... ok test_clone (tests.TestCase_JetstreamJT270M) Testing Jetstream JT270M clone ... ok test_copy_all (tests.TestCase_JetstreamJT270M) Testing Jetstream JT270M copy all ... ok test_detect (tests.TestCase_JetstreamJT270M) Testing Jetstream JT270M detect ... ok test_edges (tests.TestCase_JetstreamJT270M) Testing Jetstream JT270M edges ... ok test_settings (tests.TestCase_JetstreamJT270M) Testing Jetstream JT270M settings ... ok test_banks (tests.TestCase_YaesuFT8900) Testing Yaesu FT-8900 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_YaesuFT8900) Testing Yaesu FT-8900 brute force ... ok test_clone (tests.TestCase_YaesuFT8900) Testing Yaesu FT-8900 clone ... ok test_copy_all (tests.TestCase_YaesuFT8900) Testing Yaesu FT-8900 copy all ... ok test_detect (tests.TestCase_YaesuFT8900) Testing Yaesu FT-8900 detect ... ok test_edges (tests.TestCase_YaesuFT8900) Testing Yaesu FT-8900 edges ... ok test_settings (tests.TestCase_YaesuFT8900) Testing Yaesu FT-8900 settings ... skipped 'Settings not supported' test_banks (tests.TestCase_TYTTH9000144) Testing TYT TH9000_144 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_TYTTH9000144) Testing TYT TH9000_144 brute force ... ok test_clone (tests.TestCase_TYTTH9000144) Testing TYT TH9000_144 clone ... ok test_copy_all (tests.TestCase_TYTTH9000144) Testing TYT TH9000_144 copy all ... ok test_detect (tests.TestCase_TYTTH9000144) Testing TYT TH9000_144 detect ... ok test_edges (tests.TestCase_TYTTH9000144) Testing TYT TH9000_144 edges ... ok test_settings (tests.TestCase_TYTTH9000144) Testing TYT TH9000_144 settings ... ok test_banks (tests.TestCase_TYTTHUVF1) Testing TYT TH-UVF1 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_TYTTHUVF1) Testing TYT TH-UVF1 brute force ... ok test_clone (tests.TestCase_TYTTHUVF1) Testing TYT TH-UVF1 clone ... ok test_copy_all (tests.TestCase_TYTTHUVF1) Testing TYT TH-UVF1 copy all ... ok test_detect (tests.TestCase_TYTTHUVF1) Testing TYT TH-UVF1 detect ... ok test_edges (tests.TestCase_TYTTHUVF1) Testing TYT TH-UVF1 edges ... ok test_settings (tests.TestCase_TYTTHUVF1) Testing TYT TH-UVF1 settings ... ok test_banks (tests.TestCase_YaesuFT2D) Testing Yaesu FT2D banks ... ok test_brute_force (tests.TestCase_YaesuFT2D) Testing Yaesu FT2D brute force ... ok test_clone (tests.TestCase_YaesuFT2D) Testing Yaesu FT2D clone ... ok test_copy_all (tests.TestCase_YaesuFT2D) Testing Yaesu FT2D copy all ... ok test_detect (tests.TestCase_YaesuFT2D) Testing Yaesu FT2D detect ... ok test_edges (tests.TestCase_YaesuFT2D) Testing Yaesu FT2D edges ... ok test_settings (tests.TestCase_YaesuFT2D) Testing Yaesu FT2D settings ... ok test_banks (tests.TestCase_YaesuFT857897US) Testing Yaesu FT-857/897 (US) banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_YaesuFT857897US) Testing Yaesu FT-857/897 (US) brute force ... ok test_clone (tests.TestCase_YaesuFT857897US) Testing Yaesu FT-857/897 (US) clone ... ok test_copy_all (tests.TestCase_YaesuFT857897US) Testing Yaesu FT-857/897 (US) copy all ... ok test_detect (tests.TestCase_YaesuFT857897US) Testing Yaesu FT-857/897 (US) detect ... ok test_edges (tests.TestCase_YaesuFT857897US) Testing Yaesu FT-857/897 (US) edges ... ok test_settings (tests.TestCase_YaesuFT857897US) Testing Yaesu FT-857/897 (US) settings ... ok test_banks (tests.TestCase_YaesuFTM3200D) Testing Yaesu FTM-3200D banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_YaesuFTM3200D) Testing Yaesu FTM-3200D brute force ... ok test_clone (tests.TestCase_YaesuFTM3200D) Testing Yaesu FTM-3200D clone ... ok test_copy_all (tests.TestCase_YaesuFTM3200D) Testing Yaesu FTM-3200D copy all ... ok test_detect (tests.TestCase_YaesuFTM3200D) Testing Yaesu FTM-3200D detect ... ok test_edges (tests.TestCase_YaesuFTM3200D) Testing Yaesu FTM-3200D edges ... ok test_settings (tests.TestCase_YaesuFTM3200D) Testing Yaesu FTM-3200D settings ... skipped 'Settings not supported' test_banks (tests.TestCase_YaesuFT60) Testing Yaesu FT-60 banks ... ok test_brute_force (tests.TestCase_YaesuFT60) Testing Yaesu FT-60 brute force ... ok test_clone (tests.TestCase_YaesuFT60) Testing Yaesu FT-60 clone ... ok test_copy_all (tests.TestCase_YaesuFT60) Testing Yaesu FT-60 copy all ... ok test_detect (tests.TestCase_YaesuFT60) Testing Yaesu FT-60 detect ... ok test_edges (tests.TestCase_YaesuFT60) Testing Yaesu FT-60 edges ... ok test_settings (tests.TestCase_YaesuFT60) Testing Yaesu FT-60 settings ... ok test_banks (tests.TestCase_IcomIC2100H) Testing Icom IC-2100H banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_IcomIC2100H) Testing Icom IC-2100H brute force ... ok test_clone (tests.TestCase_IcomIC2100H) Testing Icom IC-2100H clone ... ok test_copy_all (tests.TestCase_IcomIC2100H) Testing Icom IC-2100H copy all ... ok test_detect (tests.TestCase_IcomIC2100H) Testing Icom IC-2100H detect ... ok test_edges (tests.TestCase_IcomIC2100H) Testing Icom IC-2100H edges ... ok test_settings (tests.TestCase_IcomIC2100H) Testing Icom IC-2100H settings ... skipped 'Settings not supported' test_banks (tests.TestCase_YaesuFTM350) Testing Yaesu FTM-350 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_YaesuFTM350) Testing Yaesu FTM-350 brute force ... ok test_clone (tests.TestCase_YaesuFTM350) Testing Yaesu FTM-350 clone ... ok test_copy_all (tests.TestCase_YaesuFTM350) Testing Yaesu FTM-350 copy all ... ok test_detect (tests.TestCase_YaesuFTM350) Testing Yaesu FTM-350 detect ... ok test_edges (tests.TestCase_YaesuFTM350) Testing Yaesu FTM-350 edges ... ok test_settings (tests.TestCase_YaesuFTM350) Testing Yaesu FTM-350 settings ... skipped 'Settings not supported' test_banks (tests.TestCase_LeixenVV898) Testing Leixen VV-898 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_LeixenVV898) Testing Leixen VV-898 brute force ... ok test_clone (tests.TestCase_LeixenVV898) Testing Leixen VV-898 clone ... ok test_copy_all (tests.TestCase_LeixenVV898) Testing Leixen VV-898 copy all ... ok test_detect (tests.TestCase_LeixenVV898) Testing Leixen VV-898 detect ... ok test_edges (tests.TestCase_LeixenVV898) Testing Leixen VV-898 edges ... ok test_settings (tests.TestCase_LeixenVV898) Testing Leixen VV-898 settings ... ok test_banks (tests.TestCase_QYTKT7900D) Testing QYT KT7900D banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_QYTKT7900D) Testing QYT KT7900D brute force ... ok test_clone (tests.TestCase_QYTKT7900D) Testing QYT KT7900D clone ... ok test_copy_all (tests.TestCase_QYTKT7900D) Testing QYT KT7900D copy all ... ok test_detect (tests.TestCase_QYTKT7900D) Testing QYT KT7900D detect ... ok test_edges (tests.TestCase_QYTKT7900D) Testing QYT KT7900D edges ... ok test_settings (tests.TestCase_QYTKT7900D) Testing QYT KT7900D settings ... ok test_banks (tests.TestCase_WouxunKGUVD1P) Testing Wouxun KG-UVD1P banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_WouxunKGUVD1P) Testing Wouxun KG-UVD1P brute force ... ok test_clone (tests.TestCase_WouxunKGUVD1P) Testing Wouxun KG-UVD1P clone ... ok test_copy_all (tests.TestCase_WouxunKGUVD1P) Testing Wouxun KG-UVD1P copy all ... ok test_detect (tests.TestCase_WouxunKGUVD1P) Testing Wouxun KG-UVD1P detect ... ok test_edges (tests.TestCase_WouxunKGUVD1P) Testing Wouxun KG-UVD1P edges ... ok test_settings (tests.TestCase_WouxunKGUVD1P) Testing Wouxun KG-UVD1P settings ... ok test_banks (tests.TestCase_IcomICV82U82) Testing Icom IC-V82/U82 banks ... ok test_brute_force (tests.TestCase_IcomICV82U82) Testing Icom IC-V82/U82 brute force ... ok test_clone (tests.TestCase_IcomICV82U82) Testing Icom IC-V82/U82 clone ... ok test_copy_all (tests.TestCase_IcomICV82U82) Testing Icom IC-V82/U82 copy all ... ok test_detect (tests.TestCase_IcomICV82U82) Testing Icom IC-V82/U82 detect ... ok test_edges (tests.TestCase_IcomICV82U82) Testing Icom IC-V82/U82 edges ... ok test_settings (tests.TestCase_IcomICV82U82) Testing Icom IC-V82/U82 settings ... skipped 'Settings not supported' test_banks (tests.TestCase_IcomICW32A) Testing Icom IC-W32A banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_IcomICW32A) Testing Icom IC-W32A brute force ... ok test_clone (tests.TestCase_IcomICW32A) Testing Icom IC-W32A clone ... ok test_copy_all (tests.TestCase_IcomICW32A) Testing Icom IC-W32A copy all ... ok test_detect (tests.TestCase_IcomICW32A) Testing Icom IC-W32A detect ... ok test_edges (tests.TestCase_IcomICW32A) Testing Icom IC-W32A edges ... ok test_settings (tests.TestCase_IcomICW32A) Testing Icom IC-W32A settings ... skipped 'Settings not supported' test_banks (tests.TestCase_YaesuVX3) Testing Yaesu VX-3 banks ... ok test_brute_force (tests.TestCase_YaesuVX3) Testing Yaesu VX-3 brute force ... ok test_clone (tests.TestCase_YaesuVX3) Testing Yaesu VX-3 clone ... ok test_copy_all (tests.TestCase_YaesuVX3) Testing Yaesu VX-3 copy all ... ok test_detect (tests.TestCase_YaesuVX3) Testing Yaesu VX-3 detect ... ok test_edges (tests.TestCase_YaesuVX3) Testing Yaesu VX-3 edges ... ok test_settings (tests.TestCase_YaesuVX3) Testing Yaesu VX-3 settings ... ok test_banks (tests.TestCase_FeidaxinFD268B) Testing Feidaxin FD-268B banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_FeidaxinFD268B) Testing Feidaxin FD-268B brute force ... ok test_clone (tests.TestCase_FeidaxinFD268B) Testing Feidaxin FD-268B clone ... ok test_copy_all (tests.TestCase_FeidaxinFD268B) Testing Feidaxin FD-268B copy all ... ok test_detect (tests.TestCase_FeidaxinFD268B) Testing Feidaxin FD-268B detect ... ok test_edges (tests.TestCase_FeidaxinFD268B) Testing Feidaxin FD-268B edges ... ok test_settings (tests.TestCase_FeidaxinFD268B) Testing Feidaxin FD-268B settings ... ok test_banks (tests.TestCase_BaofengUV5R) Testing Baofeng UV-5R banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BaofengUV5R) Testing Baofeng UV-5R brute force ... ok test_clone (tests.TestCase_BaofengUV5R) Testing Baofeng UV-5R clone ... ok test_copy_all (tests.TestCase_BaofengUV5R) Testing Baofeng UV-5R copy all ... ok test_detect (tests.TestCase_BaofengUV5R) Testing Baofeng UV-5R detect ... ok test_edges (tests.TestCase_BaofengUV5R) Testing Baofeng UV-5R edges ... ok test_settings (tests.TestCase_BaofengUV5R) Testing Baofeng UV-5R settings ... ok test_banks (tests.TestCase_BaofengUVB5) Testing Baofeng UV-B5 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BaofengUVB5) Testing Baofeng UV-B5 brute force ... ok test_clone (tests.TestCase_BaofengUVB5) Testing Baofeng UV-B5 clone ... ok test_copy_all (tests.TestCase_BaofengUVB5) Testing Baofeng UV-B5 copy all ... ok test_detect (tests.TestCase_BaofengUVB5) Testing Baofeng UV-B5 detect ... ok test_edges (tests.TestCase_BaofengUVB5) Testing Baofeng UV-B5 edges ... ok test_settings (tests.TestCase_BaofengUVB5) Testing Baofeng UV-B5 settings ... ok test_banks (tests.TestCase_BaofengBF888) Testing Baofeng BF-888 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BaofengBF888) Testing Baofeng BF-888 brute force ... ok test_clone (tests.TestCase_BaofengBF888) Testing Baofeng BF-888 clone ... ok test_copy_all (tests.TestCase_BaofengBF888) Testing Baofeng BF-888 copy all ... ok test_detect (tests.TestCase_BaofengBF888) Testing Baofeng BF-888 detect ... ok test_edges (tests.TestCase_BaofengBF888) Testing Baofeng BF-888 edges ... ok test_settings (tests.TestCase_BaofengBF888) Testing Baofeng BF-888 settings ... ok test_banks (tests.TestCase_LUITONLT725UV) Testing LUITON LT-725UV banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_LUITONLT725UV) Testing LUITON LT-725UV brute force ... ok test_clone (tests.TestCase_LUITONLT725UV) Testing LUITON LT-725UV clone ... ok test_copy_all (tests.TestCase_LUITONLT725UV) Testing LUITON LT-725UV copy all ... ok test_detect (tests.TestCase_LUITONLT725UV) Testing LUITON LT-725UV detect ... ok test_edges (tests.TestCase_LUITONLT725UV) Testing LUITON LT-725UV edges ... ok test_settings (tests.TestCase_LUITONLT725UV) Testing LUITON LT-725UV settings ... ok test_banks (tests.TestCase_YaesuFT817) Testing Yaesu FT-817 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_YaesuFT817) Testing Yaesu FT-817 brute force ... ok test_clone (tests.TestCase_YaesuFT817) Testing Yaesu FT-817 clone ... ok test_copy_all (tests.TestCase_YaesuFT817) Testing Yaesu FT-817 copy all ... ok test_detect (tests.TestCase_YaesuFT817) Testing Yaesu FT-817 detect ... ok test_edges (tests.TestCase_YaesuFT817) Testing Yaesu FT-817 edges ... ok test_settings (tests.TestCase_YaesuFT817) Testing Yaesu FT-817 settings ... ok test_banks (tests.TestCase_PolmarDB50M) Testing Polmar DB-50M banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_PolmarDB50M) Testing Polmar DB-50M brute force ... ok test_clone (tests.TestCase_PolmarDB50M) Testing Polmar DB-50M clone ... ok test_copy_all (tests.TestCase_PolmarDB50M) Testing Polmar DB-50M copy all ... ok test_detect (tests.TestCase_PolmarDB50M) Testing Polmar DB-50M detect ... ok test_edges (tests.TestCase_PolmarDB50M) Testing Polmar DB-50M edges ... ok test_settings (tests.TestCase_PolmarDB50M) Testing Polmar DB-50M settings ... ok test_banks (tests.TestCase_KYDNC630A) Testing KYD NC-630A banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_KYDNC630A) Testing KYD NC-630A brute force ... ok test_clone (tests.TestCase_KYDNC630A) Testing KYD NC-630A clone ... ok test_copy_all (tests.TestCase_KYDNC630A) Testing KYD NC-630A copy all ... ok test_detect (tests.TestCase_KYDNC630A) Testing KYD NC-630A detect ... ok test_edges (tests.TestCase_KYDNC630A) Testing KYD NC-630A edges ... ok test_settings (tests.TestCase_KYDNC630A) Testing KYD NC-630A settings ... ok test_banks (tests.TestCase_BTECHUV5X3) Testing BTECH UV-5X3 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BTECHUV5X3) Testing BTECH UV-5X3 brute force ... ok test_clone (tests.TestCase_BTECHUV5X3) Testing BTECH UV-5X3 clone ... ok test_copy_all (tests.TestCase_BTECHUV5X3) Testing BTECH UV-5X3 copy all ... ok test_detect (tests.TestCase_BTECHUV5X3) Testing BTECH UV-5X3 detect ... ok test_edges (tests.TestCase_BTECHUV5X3) Testing BTECH UV-5X3 edges ... ok test_settings (tests.TestCase_BTECHUV5X3) Testing BTECH UV-5X3 settings ... ok test_banks (tests.TestCase_BTECHUV50X3) Testing BTECH UV-50X3 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BTECHUV50X3) Testing BTECH UV-50X3 brute force ... ok test_clone (tests.TestCase_BTECHUV50X3) Testing BTECH UV-50X3 clone ... ok test_copy_all (tests.TestCase_BTECHUV50X3) Testing BTECH UV-50X3 copy all ... ok test_detect (tests.TestCase_BTECHUV50X3) Testing BTECH UV-50X3 detect ... ok test_edges (tests.TestCase_BTECHUV50X3) Testing BTECH UV-50X3 edges ... ok test_settings (tests.TestCase_BTECHUV50X3) Testing BTECH UV-50X3 settings ... ok test_banks (tests.TestCase_VertexStandardVXA700) Testing Vertex Standard VXA-700 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_VertexStandardVXA700) Testing Vertex Standard VXA-700 brute force ... ok test_clone (tests.TestCase_VertexStandardVXA700) Testing Vertex Standard VXA-700 clone ... ok test_copy_all (tests.TestCase_VertexStandardVXA700) Testing Vertex Standard VXA-700 copy all ... ok test_detect (tests.TestCase_VertexStandardVXA700) Testing Vertex Standard VXA-700 detect ... ok test_edges (tests.TestCase_VertexStandardVXA700) Testing Vertex Standard VXA-700 edges ... ok test_settings (tests.TestCase_VertexStandardVXA700) Testing Vertex Standard VXA-700 settings ... skipped 'Settings not supported' test_banks (tests.TestCase_YaesuFT1802M) Testing Yaesu FT-1802M banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_YaesuFT1802M) Testing Yaesu FT-1802M brute force ... ok test_clone (tests.TestCase_YaesuFT1802M) Testing Yaesu FT-1802M clone ... ok test_copy_all (tests.TestCase_YaesuFT1802M) Testing Yaesu FT-1802M copy all ... ok test_detect (tests.TestCase_YaesuFT1802M) Testing Yaesu FT-1802M detect ... ok test_edges (tests.TestCase_YaesuFT1802M) Testing Yaesu FT-1802M edges ... ok test_settings (tests.TestCase_YaesuFT1802M) Testing Yaesu FT-1802M settings ... skipped 'Settings not supported' test_banks (tests.TestCase_IcomIC2720H) Testing Icom IC-2720H banks ... ok test_brute_force (tests.TestCase_IcomIC2720H) Testing Icom IC-2720H brute force ... ok test_clone (tests.TestCase_IcomIC2720H) Testing Icom IC-2720H clone ... ok test_copy_all (tests.TestCase_IcomIC2720H) Testing Icom IC-2720H copy all ... ok test_detect (tests.TestCase_IcomIC2720H) Testing Icom IC-2720H detect ... ok test_edges (tests.TestCase_IcomIC2720H) Testing Icom IC-2720H edges ... ok test_settings (tests.TestCase_IcomIC2720H) Testing Icom IC-2720H settings ... skipped 'Settings not supported' test_banks (tests.TestCase_BTECHUV25X4) Testing BTECH UV-25X4 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BTECHUV25X4) Testing BTECH UV-25X4 brute force ... ok test_clone (tests.TestCase_BTECHUV25X4) Testing BTECH UV-25X4 clone ... ok test_copy_all (tests.TestCase_BTECHUV25X4) Testing BTECH UV-25X4 copy all ... ok test_detect (tests.TestCase_BTECHUV25X4) Testing BTECH UV-25X4 detect ... ok test_edges (tests.TestCase_BTECHUV25X4) Testing BTECH UV-25X4 edges ... ok test_settings (tests.TestCase_BTECHUV25X4) Testing BTECH UV-25X4 settings ... ok test_banks (tests.TestCase_IcomID51) Testing Icom ID-51 banks ... ok test_brute_force (tests.TestCase_IcomID51) Testing Icom ID-51 brute force ... ok test_clone (tests.TestCase_IcomID51) Testing Icom ID-51 clone ... ok test_copy_all (tests.TestCase_IcomID51) Testing Icom ID-51 copy all ... ok test_detect (tests.TestCase_IcomID51) Testing Icom ID-51 detect ... ok test_edges (tests.TestCase_IcomID51) Testing Icom ID-51 edges ... ok test_settings (tests.TestCase_IcomID51) Testing Icom ID-51 settings ... ok test_banks (tests.TestCase_KenwoodTHD72clonemode) Testing Kenwood TH-D72 (clone mode) banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_KenwoodTHD72clonemode) Testing Kenwood TH-D72 (clone mode) brute force ... ok test_clone (tests.TestCase_KenwoodTHD72clonemode) Testing Kenwood TH-D72 (clone mode) clone ... ok test_copy_all (tests.TestCase_KenwoodTHD72clonemode) Testing Kenwood TH-D72 (clone mode) copy all ... ok test_detect (tests.TestCase_KenwoodTHD72clonemode) Testing Kenwood TH-D72 (clone mode) detect ... ok test_edges (tests.TestCase_KenwoodTHD72clonemode) Testing Kenwood TH-D72 (clone mode) edges ... ok test_settings (tests.TestCase_KenwoodTHD72clonemode) Testing Kenwood TH-D72 (clone mode) settings ... ok test_banks (tests.TestCase_YaesuVX8DR) Testing Yaesu VX-8DR banks ... ok test_brute_force (tests.TestCase_YaesuVX8DR) Testing Yaesu VX-8DR brute force ... ok test_clone (tests.TestCase_YaesuVX8DR) Testing Yaesu VX-8DR clone ... ok test_copy_all (tests.TestCase_YaesuVX8DR) Testing Yaesu VX-8DR copy all ... ok test_detect (tests.TestCase_YaesuVX8DR) Testing Yaesu VX-8DR detect ... ok test_edges (tests.TestCase_YaesuVX8DR) Testing Yaesu VX-8DR edges ... ok test_settings (tests.TestCase_YaesuVX8DR) Testing Yaesu VX-8DR settings ... ok test_banks (tests.TestCase_RadtelT18) Testing Radtel T18 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_RadtelT18) Testing Radtel T18 brute force ... ok test_clone (tests.TestCase_RadtelT18) Testing Radtel T18 clone ... ok test_copy_all (tests.TestCase_RadtelT18) Testing Radtel T18 copy all ... ok test_detect (tests.TestCase_RadtelT18) Testing Radtel T18 detect ... ok test_edges (tests.TestCase_RadtelT18) Testing Radtel T18 edges ... ok test_settings (tests.TestCase_RadtelT18) Testing Radtel T18 settings ... ok test_banks (tests.TestCase_BaofengF11) Testing Baofeng F-11 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BaofengF11) Testing Baofeng F-11 brute force ... ok test_clone (tests.TestCase_BaofengF11) Testing Baofeng F-11 clone ... ok test_copy_all (tests.TestCase_BaofengF11) Testing Baofeng F-11 copy all ... ok test_detect (tests.TestCase_BaofengF11) Testing Baofeng F-11 detect ... ok test_edges (tests.TestCase_BaofengF11) Testing Baofeng F-11 edges ... ok test_settings (tests.TestCase_BaofengF11) Testing Baofeng F-11 settings ... ok test_banks (tests.TestCase_FeidaxinFD268A) Testing Feidaxin FD-268A banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_FeidaxinFD268A) Testing Feidaxin FD-268A brute force ... ok test_clone (tests.TestCase_FeidaxinFD268A) Testing Feidaxin FD-268A clone ... ok test_copy_all (tests.TestCase_FeidaxinFD268A) Testing Feidaxin FD-268A copy all ... ok test_detect (tests.TestCase_FeidaxinFD268A) Testing Feidaxin FD-268A detect ... ok test_edges (tests.TestCase_FeidaxinFD268A) Testing Feidaxin FD-268A edges ... ok test_settings (tests.TestCase_FeidaxinFD268A) Testing Feidaxin FD-268A settings ... ok test_banks (tests.TestCase_AlincoDJ175) Testing Alinco DJ175 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_AlincoDJ175) Testing Alinco DJ175 brute force ... ok test_clone (tests.TestCase_AlincoDJ175) Testing Alinco DJ175 clone ... ok test_copy_all (tests.TestCase_AlincoDJ175) Testing Alinco DJ175 copy all ... ok test_detect (tests.TestCase_AlincoDJ175) Testing Alinco DJ175 detect ... ok test_edges (tests.TestCase_AlincoDJ175) Testing Alinco DJ175 edges ... ok test_settings (tests.TestCase_AlincoDJ175) Testing Alinco DJ175 settings ... skipped 'Settings not supported' test_banks (tests.TestCase_BTECHGMRSV1) Testing BTECH GMRS-V1 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_BTECHGMRSV1) Testing BTECH GMRS-V1 brute force ... ok test_clone (tests.TestCase_BTECHGMRSV1) Testing BTECH GMRS-V1 clone ... ok test_copy_all (tests.TestCase_BTECHGMRSV1) Testing BTECH GMRS-V1 copy all ... ok test_detect (tests.TestCase_BTECHGMRSV1) Testing BTECH GMRS-V1 detect ... ok test_edges (tests.TestCase_BTECHGMRSV1) Testing BTECH GMRS-V1 edges ... ok test_settings (tests.TestCase_BTECHGMRSV1) Testing BTECH GMRS-V1 settings ... ok test_banks (tests.TestCase_RetevisRT22) Testing Retevis RT22 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_RetevisRT22) Testing Retevis RT22 brute force ... ok test_clone (tests.TestCase_RetevisRT22) Testing Retevis RT22 clone ... ok test_copy_all (tests.TestCase_RetevisRT22) Testing Retevis RT22 copy all ... ok test_detect (tests.TestCase_RetevisRT22) Testing Retevis RT22 detect ... ok test_edges (tests.TestCase_RetevisRT22) Testing Retevis RT22 edges ... ok test_settings (tests.TestCase_RetevisRT22) Testing Retevis RT22 settings ... ok test_banks (tests.TestCase_YaesuVX8R) Testing Yaesu VX-8R banks ... ok test_brute_force (tests.TestCase_YaesuVX8R) Testing Yaesu VX-8R brute force ... ok test_clone (tests.TestCase_YaesuVX8R) Testing Yaesu VX-8R clone ... ok test_copy_all (tests.TestCase_YaesuVX8R) Testing Yaesu VX-8R copy all ... ok test_detect (tests.TestCase_YaesuVX8R) Testing Yaesu VX-8R detect ... ok test_edges (tests.TestCase_YaesuVX8R) Testing Yaesu VX-8R edges ... ok test_settings (tests.TestCase_YaesuVX8R) Testing Yaesu VX-8R settings ... ok test_banks (tests.TestCase_AlincoDJG7EG) Testing Alinco DJ-G7EG banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_AlincoDJG7EG) Testing Alinco DJ-G7EG brute force ... ok test_clone (tests.TestCase_AlincoDJG7EG) Testing Alinco DJ-G7EG clone ... ok test_copy_all (tests.TestCase_AlincoDJG7EG) Testing Alinco DJ-G7EG copy all ... ok test_detect (tests.TestCase_AlincoDJG7EG) Testing Alinco DJ-G7EG detect ... ok test_edges (tests.TestCase_AlincoDJG7EG) Testing Alinco DJ-G7EG edges ... ok test_settings (tests.TestCase_AlincoDJG7EG) Testing Alinco DJ-G7EG settings ... skipped 'Settings not supported' test_banks (tests.TestCase_LeixenVV898S) Testing Leixen VV-898S banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_LeixenVV898S) Testing Leixen VV-898S brute force ... ok test_clone (tests.TestCase_LeixenVV898S) Testing Leixen VV-898S clone ... ok test_copy_all (tests.TestCase_LeixenVV898S) Testing Leixen VV-898S copy all ... ok test_detect (tests.TestCase_LeixenVV898S) Testing Leixen VV-898S detect ... ok test_edges (tests.TestCase_LeixenVV898S) Testing Leixen VV-898S edges ... ok test_settings (tests.TestCase_LeixenVV898S) Testing Leixen VV-898S settings ... ok test_banks (tests.TestCase_KYDIP620) Testing KYD IP-620 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_KYDIP620) Testing KYD IP-620 brute force ... ok test_clone (tests.TestCase_KYDIP620) Testing KYD IP-620 clone ... ok test_copy_all (tests.TestCase_KYDIP620) Testing KYD IP-620 copy all ... ok test_detect (tests.TestCase_KYDIP620) Testing KYD IP-620 detect ... ok test_edges (tests.TestCase_KYDIP620) Testing KYD IP-620 edges ... ok test_settings (tests.TestCase_KYDIP620) Testing KYD IP-620 settings ... ok test_banks (tests.TestCase_YaesuFT78007900) Testing Yaesu FT-7800/7900 banks ... ok test_brute_force (tests.TestCase_YaesuFT78007900) Testing Yaesu FT-7800/7900 brute force ... ok test_clone (tests.TestCase_YaesuFT78007900) Testing Yaesu FT-7800/7900 clone ... ok test_copy_all (tests.TestCase_YaesuFT78007900) Testing Yaesu FT-7800/7900 copy all ... ok test_detect (tests.TestCase_YaesuFT78007900) Testing Yaesu FT-7800/7900 detect ... ok test_edges (tests.TestCase_YaesuFT78007900) Testing Yaesu FT-7800/7900 edges ... ok test_settings (tests.TestCase_YaesuFT78007900) Testing Yaesu FT-7800/7900 settings ... ok test_banks (tests.TestCase_YaesuVX2) Testing Yaesu VX-2 banks ... ok test_brute_force (tests.TestCase_YaesuVX2) Testing Yaesu VX-2 brute force ... ok test_clone (tests.TestCase_YaesuVX2) Testing Yaesu VX-2 clone ... ok test_copy_all (tests.TestCase_YaesuVX2) Testing Yaesu VX-2 copy all ... ok test_detect (tests.TestCase_YaesuVX2) Testing Yaesu VX-2 detect ... ok test_edges (tests.TestCase_YaesuVX2) Testing Yaesu VX-2 edges ... ok test_settings (tests.TestCase_YaesuVX2) Testing Yaesu VX-2 settings ... ok test_banks (tests.TestCase_WouxunKGUV8DPlus) Testing Wouxun KG-UV8D Plus banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_WouxunKGUV8DPlus) Testing Wouxun KG-UV8D Plus brute force ... ok test_clone (tests.TestCase_WouxunKGUV8DPlus) Testing Wouxun KG-UV8D Plus clone ... ok test_copy_all (tests.TestCase_WouxunKGUV8DPlus) Testing Wouxun KG-UV8D Plus copy all ... ok test_detect (tests.TestCase_WouxunKGUV8DPlus) Testing Wouxun KG-UV8D Plus detect ... ok test_edges (tests.TestCase_WouxunKGUV8DPlus) Testing Wouxun KG-UV8D Plus edges ... ok test_settings (tests.TestCase_WouxunKGUV8DPlus) Testing Wouxun KG-UV8D Plus settings ... ok test_banks (tests.TestCase_WouxunKGUV8D) Testing Wouxun KG-UV8D banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_WouxunKGUV8D) Testing Wouxun KG-UV8D brute force ... ok test_clone (tests.TestCase_WouxunKGUV8D) Testing Wouxun KG-UV8D clone ... ok test_copy_all (tests.TestCase_WouxunKGUV8D) Testing Wouxun KG-UV8D copy all ... ok test_detect (tests.TestCase_WouxunKGUV8D) Testing Wouxun KG-UV8D detect ... ok test_edges (tests.TestCase_WouxunKGUV8D) Testing Wouxun KG-UV8D edges ... ok test_settings (tests.TestCase_WouxunKGUV8D) Testing Wouxun KG-UV8D settings ... ok test_banks (tests.TestCase_KenwoodTK272G) Testing Kenwood TK-272G banks ... ok test_brute_force (tests.TestCase_KenwoodTK272G) Testing Kenwood TK-272G brute force ... ok test_clone (tests.TestCase_KenwoodTK272G) Testing Kenwood TK-272G clone ... ok test_copy_all (tests.TestCase_KenwoodTK272G) Testing Kenwood TK-272G copy all ... ok test_detect (tests.TestCase_KenwoodTK272G) Testing Kenwood TK-272G detect ... ok test_edges (tests.TestCase_KenwoodTK272G) Testing Kenwood TK-272G edges ... ok test_settings (tests.TestCase_KenwoodTK272G) Testing Kenwood TK-272G settings ... ok test_banks (tests.TestCase_QYTKT8900D) Testing QYT KT8900D banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_QYTKT8900D) Testing QYT KT8900D brute force ... ok test_clone (tests.TestCase_QYTKT8900D) Testing QYT KT8900D clone ... ok test_copy_all (tests.TestCase_QYTKT8900D) Testing QYT KT8900D copy all ... ok test_detect (tests.TestCase_QYTKT8900D) Testing QYT KT8900D detect ... ok test_edges (tests.TestCase_QYTKT8900D) Testing QYT KT8900D edges ... ok test_settings (tests.TestCase_QYTKT8900D) Testing QYT KT8900D settings ... ok test_banks (tests.TestCase_KenwoodTK760G) Testing Kenwood TK-760G banks ... ok test_brute_force (tests.TestCase_KenwoodTK760G) Testing Kenwood TK-760G brute force ... ok test_clone (tests.TestCase_KenwoodTK760G) Testing Kenwood TK-760G clone ... ok test_copy_all (tests.TestCase_KenwoodTK760G) Testing Kenwood TK-760G copy all ... ok test_detect (tests.TestCase_KenwoodTK760G) Testing Kenwood TK-760G detect ... ok test_edges (tests.TestCase_KenwoodTK760G) Testing Kenwood TK-760G edges ... ok test_settings (tests.TestCase_KenwoodTK760G) Testing Kenwood TK-760G settings ... ok test_banks (tests.TestCase_YaesuVX6) Testing Yaesu VX-6 banks ... ok test_brute_force (tests.TestCase_YaesuVX6) Testing Yaesu VX-6 brute force ... ok test_clone (tests.TestCase_YaesuVX6) Testing Yaesu VX-6 clone ... ok test_copy_all (tests.TestCase_YaesuVX6) Testing Yaesu VX-6 copy all ... ok test_detect (tests.TestCase_YaesuVX6) Testing Yaesu VX-6 detect ... ok test_edges (tests.TestCase_YaesuVX6) Testing Yaesu VX-6 edges ... ok test_settings (tests.TestCase_YaesuVX6) Testing Yaesu VX-6 settings ... skipped 'Settings not supported' test_banks (tests.TestCase_IcomIC208H) Testing Icom IC-208H banks ... ok test_brute_force (tests.TestCase_IcomIC208H) Testing Icom IC-208H brute force ... ok test_clone (tests.TestCase_IcomIC208H) Testing Icom IC-208H clone ... ok test_copy_all (tests.TestCase_IcomIC208H) Testing Icom IC-208H copy all ... ok test_detect (tests.TestCase_IcomIC208H) Testing Icom IC-208H detect ... ok test_edges (tests.TestCase_IcomIC208H) Testing Icom IC-208H edges ... ok test_settings (tests.TestCase_IcomIC208H) Testing Icom IC-208H settings ... skipped 'Settings not supported' test_banks (tests.TestCase_IcomID31A) Testing Icom ID-31A banks ... ok test_brute_force (tests.TestCase_IcomID31A) Testing Icom ID-31A brute force ... ok test_clone (tests.TestCase_IcomID31A) Testing Icom ID-31A clone ... ok test_copy_all (tests.TestCase_IcomID31A) Testing Icom ID-31A copy all ... ok test_detect (tests.TestCase_IcomID31A) Testing Icom ID-31A detect ... ok test_edges (tests.TestCase_IcomID31A) Testing Icom ID-31A edges ... ok test_settings (tests.TestCase_IcomID31A) Testing Icom ID-31A settings ... ok test_banks (tests.TestCase_TYTTH7800) Testing TYT TH-7800 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_TYTTH7800) Testing TYT TH-7800 brute force ... ok test_clone (tests.TestCase_TYTTH7800) Testing TYT TH-7800 clone ... ok test_copy_all (tests.TestCase_TYTTH7800) Testing TYT TH-7800 copy all ... ok test_detect (tests.TestCase_TYTTH7800) Testing TYT TH-7800 detect ... ok test_edges (tests.TestCase_TYTTH7800) Testing TYT TH-7800 edges ... ok test_settings (tests.TestCase_TYTTH7800) Testing TYT TH-7800 settings ... ok test_banks (tests.TestCase_IcomIC2200H) Testing Icom IC-2200H banks ... ok test_brute_force (tests.TestCase_IcomIC2200H) Testing Icom IC-2200H brute force ... ok test_clone (tests.TestCase_IcomIC2200H) Testing Icom IC-2200H clone ... ok test_copy_all (tests.TestCase_IcomIC2200H) Testing Icom IC-2200H copy all ... ok test_detect (tests.TestCase_IcomIC2200H) Testing Icom IC-2200H detect ... ok test_edges (tests.TestCase_IcomIC2200H) Testing Icom IC-2200H edges ... ok test_settings (tests.TestCase_IcomIC2200H) Testing Icom IC-2200H settings ... ok test_banks (tests.TestCase_PuxingPX888K) Testing Puxing PX-888K banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_PuxingPX888K) Testing Puxing PX-888K brute force ... ok test_clone (tests.TestCase_PuxingPX888K) Testing Puxing PX-888K clone ... ok test_copy_all (tests.TestCase_PuxingPX888K) Testing Puxing PX-888K copy all ... ok test_detect (tests.TestCase_PuxingPX888K) Testing Puxing PX-888K detect ... ok test_edges (tests.TestCase_PuxingPX888K) Testing Puxing PX-888K edges ... ok test_settings (tests.TestCase_PuxingPX888K) Testing Puxing PX-888K settings ... ok test_banks (tests.TestCase_YaesuFT857897) Testing Yaesu FT-857/897 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_YaesuFT857897) Testing Yaesu FT-857/897 brute force ... ok test_clone (tests.TestCase_YaesuFT857897) Testing Yaesu FT-857/897 clone ... ok test_copy_all (tests.TestCase_YaesuFT857897) Testing Yaesu FT-857/897 copy all ... ok test_detect (tests.TestCase_YaesuFT857897) Testing Yaesu FT-857/897 detect ... ok test_edges (tests.TestCase_YaesuFT857897) Testing Yaesu FT-857/897 edges ... ok test_settings (tests.TestCase_YaesuFT857897) Testing Yaesu FT-857/897 settings ... ok test_banks (tests.TestCase_IcomIC2730A) Testing Icom IC-2730A banks ... ok test_brute_force (tests.TestCase_IcomIC2730A) Testing Icom IC-2730A brute force ... ok test_clone (tests.TestCase_IcomIC2730A) Testing Icom IC-2730A clone ... ok test_copy_all (tests.TestCase_IcomIC2730A) Testing Icom IC-2730A copy all ... ok test_detect (tests.TestCase_IcomIC2730A) Testing Icom IC-2730A detect ... ok test_edges (tests.TestCase_IcomIC2730A) Testing Icom IC-2730A edges ... ok test_settings (tests.TestCase_IcomIC2730A) Testing Icom IC-2730A settings ... ok test_banks (tests.TestCase_AnyToneOBLTR8R) Testing AnyTone OBLTR-8R banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_AnyToneOBLTR8R) Testing AnyTone OBLTR-8R brute force ... ok test_clone (tests.TestCase_AnyToneOBLTR8R) Testing AnyTone OBLTR-8R clone ... ok test_copy_all (tests.TestCase_AnyToneOBLTR8R) Testing AnyTone OBLTR-8R copy all ... ok test_detect (tests.TestCase_AnyToneOBLTR8R) Testing AnyTone OBLTR-8R detect ... ok test_edges (tests.TestCase_AnyToneOBLTR8R) Testing AnyTone OBLTR-8R edges ... ok test_settings (tests.TestCase_AnyToneOBLTR8R) Testing AnyTone OBLTR-8R settings ... ok test_banks (tests.TestCase_WouxunKG816) Testing Wouxun KG-816 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_WouxunKG816) Testing Wouxun KG-816 brute force ... ok test_clone (tests.TestCase_WouxunKG816) Testing Wouxun KG-816 clone ... ok test_copy_all (tests.TestCase_WouxunKG816) Testing Wouxun KG-816 copy all ... ok test_detect (tests.TestCase_WouxunKG816) Testing Wouxun KG-816 detect ... ok test_edges (tests.TestCase_WouxunKG816) Testing Wouxun KG-816 edges ... ok test_settings (tests.TestCase_WouxunKG816) Testing Wouxun KG-816 settings ... ok test_banks (tests.TestCase_YaesuFT8800) Testing Yaesu FT-8800 banks ... ok test_brute_force (tests.TestCase_YaesuFT8800) Testing Yaesu FT-8800 brute force ... ok test_clone (tests.TestCase_YaesuFT8800) Testing Yaesu FT-8800 clone ... ok test_copy_all (tests.TestCase_YaesuFT8800) Testing Yaesu FT-8800 copy all ... ok test_detect (tests.TestCase_YaesuFT8800) Testing Yaesu FT-8800 detect ... ok test_edges (tests.TestCase_YaesuFT8800) Testing Yaesu FT-8800 edges ... ok test_settings (tests.TestCase_YaesuFT8800) Testing Yaesu FT-8800 settings ... skipped 'Settings not supported' test_banks (tests.TestCase_IcomICQ7A) Testing Icom IC-Q7A banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_IcomICQ7A) Testing Icom IC-Q7A brute force ... ok test_clone (tests.TestCase_IcomICQ7A) Testing Icom IC-Q7A clone ... ok test_copy_all (tests.TestCase_IcomICQ7A) Testing Icom IC-Q7A copy all ... ok test_detect (tests.TestCase_IcomICQ7A) Testing Icom IC-Q7A detect ... ok test_edges (tests.TestCase_IcomICQ7A) Testing Icom IC-Q7A edges ... ok test_settings (tests.TestCase_IcomICQ7A) Testing Icom IC-Q7A settings ... ok test_banks (tests.TestCase_YaesuVX8GE) Testing Yaesu VX-8GE banks ... ok test_brute_force (tests.TestCase_YaesuVX8GE) Testing Yaesu VX-8GE brute force ... ok test_clone (tests.TestCase_YaesuVX8GE) Testing Yaesu VX-8GE clone ... ok test_copy_all (tests.TestCase_YaesuVX8GE) Testing Yaesu VX-8GE copy all ... ok test_detect (tests.TestCase_YaesuVX8GE) Testing Yaesu VX-8GE detect ... ok test_edges (tests.TestCase_YaesuVX8GE) Testing Yaesu VX-8GE edges ... ok test_settings (tests.TestCase_YaesuVX8GE) Testing Yaesu VX-8GE settings ... ok test_banks (tests.TestCase_IcomICT70) Testing Icom IC-T70 banks ... ok test_brute_force (tests.TestCase_IcomICT70) Testing Icom IC-T70 brute force ... ok test_clone (tests.TestCase_IcomICT70) Testing Icom IC-T70 clone ... ok test_copy_all (tests.TestCase_IcomICT70) Testing Icom IC-T70 copy all ... ok test_detect (tests.TestCase_IcomICT70) Testing Icom IC-T70 detect ... ok test_edges (tests.TestCase_IcomICT70) Testing Icom IC-T70 edges ... ok test_settings (tests.TestCase_IcomICT70) Testing Icom IC-T70 settings ... skipped 'Settings not supported' test_banks (tests.TestCase_TYTTHUV3R) Testing TYT TH-UV3R banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_TYTTHUV3R) Testing TYT TH-UV3R brute force ... ok test_clone (tests.TestCase_TYTTHUV3R) Testing TYT TH-UV3R clone ... ok test_copy_all (tests.TestCase_TYTTHUV3R) Testing TYT TH-UV3R copy all ... ok test_detect (tests.TestCase_TYTTHUV3R) Testing TYT TH-UV3R detect ... ok test_edges (tests.TestCase_TYTTHUV3R) Testing TYT TH-UV3R edges ... ok test_settings (tests.TestCase_TYTTHUV3R) Testing TYT TH-UV3R settings ... skipped 'Settings not supported' test_banks (tests.TestCase_YaesuFT1D) Testing Yaesu FT-1D banks ... ok test_brute_force (tests.TestCase_YaesuFT1D) Testing Yaesu FT-1D brute force ... ok test_clone (tests.TestCase_YaesuFT1D) Testing Yaesu FT-1D clone ... ok test_copy_all (tests.TestCase_YaesuFT1D) Testing Yaesu FT-1D copy all ... ok test_detect (tests.TestCase_YaesuFT1D) Testing Yaesu FT-1D detect ... ok test_edges (tests.TestCase_YaesuFT1D) Testing Yaesu FT-1D edges ... ok test_settings (tests.TestCase_YaesuFT1D) Testing Yaesu FT-1D settings ... ok test_banks (tests.TestCase_RetevisRT23) Testing Retevis RT23 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_RetevisRT23) Testing Retevis RT23 brute force ... ok test_clone (tests.TestCase_RetevisRT23) Testing Retevis RT23 clone ... ok test_copy_all (tests.TestCase_RetevisRT23) Testing Retevis RT23 copy all ... ok test_detect (tests.TestCase_RetevisRT23) Testing Retevis RT23 detect ... ok test_edges (tests.TestCase_RetevisRT23) Testing Retevis RT23 edges ... ok test_settings (tests.TestCase_RetevisRT23) Testing Retevis RT23 settings ... ok test_banks (tests.TestCase_PuxingPX777) Testing Puxing PX-777 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_PuxingPX777) Testing Puxing PX-777 brute force ... ok test_clone (tests.TestCase_PuxingPX777) Testing Puxing PX-777 clone ... ok test_copy_all (tests.TestCase_PuxingPX777) Testing Puxing PX-777 copy all ... ok test_detect (tests.TestCase_PuxingPX777) Testing Puxing PX-777 detect ... ok test_edges (tests.TestCase_PuxingPX777) Testing Puxing PX-777 edges ... ok test_settings (tests.TestCase_PuxingPX777) Testing Puxing PX-777 settings ... skipped 'Settings not supported' test_banks (tests.TestCase_IcomID800H) Testing Icom ID-800H banks ... ok test_brute_force (tests.TestCase_IcomID800H) Testing Icom ID-800H brute force ... ok test_clone (tests.TestCase_IcomID800H) Testing Icom ID-800H clone ... ok test_copy_all (tests.TestCase_IcomID800H) Testing Icom ID-800H copy all ... ok test_detect (tests.TestCase_IcomID800H) Testing Icom ID-800H detect ... ok test_edges (tests.TestCase_IcomID800H) Testing Icom ID-800H edges ... ok test_settings (tests.TestCase_IcomID800H) Testing Icom ID-800H settings ... ok test_banks (tests.TestCase_AlincoDR235T) Testing Alinco DR235T banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_AlincoDR235T) Testing Alinco DR235T brute force ... ok test_clone (tests.TestCase_AlincoDR235T) Testing Alinco DR235T clone ... ok test_copy_all (tests.TestCase_AlincoDR235T) Testing Alinco DR235T copy all ... ok test_detect (tests.TestCase_AlincoDR235T) Testing Alinco DR235T detect ... ok test_edges (tests.TestCase_AlincoDR235T) Testing Alinco DR235T edges ... ok test_settings (tests.TestCase_AlincoDR235T) Testing Alinco DR235T settings ... skipped 'Settings not supported' test_banks (tests.TestCase_YaesuVX5) Testing Yaesu VX-5 banks ... ok test_brute_force (tests.TestCase_YaesuVX5) Testing Yaesu VX-5 brute force ... ok test_clone (tests.TestCase_YaesuVX5) Testing Yaesu VX-5 clone ... ok test_copy_all (tests.TestCase_YaesuVX5) Testing Yaesu VX-5 copy all ... ok test_detect (tests.TestCase_YaesuVX5) Testing Yaesu VX-5 detect ... ok test_edges (tests.TestCase_YaesuVX5) Testing Yaesu VX-5 edges ... ok test_settings (tests.TestCase_YaesuVX5) Testing Yaesu VX-5 settings ... skipped 'Settings not supported' test_banks (tests.TestCase_FeidaxinFD288B) Testing Feidaxin FD-288B banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_FeidaxinFD288B) Testing Feidaxin FD-288B brute force ... ok test_clone (tests.TestCase_FeidaxinFD288B) Testing Feidaxin FD-288B clone ... ok test_copy_all (tests.TestCase_FeidaxinFD288B) Testing Feidaxin FD-288B copy all ... ok test_detect (tests.TestCase_FeidaxinFD288B) Testing Feidaxin FD-288B detect ... ok test_edges (tests.TestCase_FeidaxinFD288B) Testing Feidaxin FD-288B edges ... ok test_settings (tests.TestCase_FeidaxinFD288B) Testing Feidaxin FD-288B settings ... ok test_banks (tests.TestCase_YaesuFT2900R1900R) Testing Yaesu FT-2900R/1900R banks ... ok test_brute_force (tests.TestCase_YaesuFT2900R1900R) Testing Yaesu FT-2900R/1900R brute force ... ok test_clone (tests.TestCase_YaesuFT2900R1900R) Testing Yaesu FT-2900R/1900R clone ... ok test_copy_all (tests.TestCase_YaesuFT2900R1900R) Testing Yaesu FT-2900R/1900R copy all ... ok test_detect (tests.TestCase_YaesuFT2900R1900R) Testing Yaesu FT-2900R/1900R detect ... ok test_edges (tests.TestCase_YaesuFT2900R1900R) Testing Yaesu FT-2900R/1900R edges ... ok test_settings (tests.TestCase_YaesuFT2900R1900R) Testing Yaesu FT-2900R/1900R settings ... ok test_banks (tests.TestCase_RetevisRT21) Testing Retevis RT21 banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_RetevisRT21) Testing Retevis RT21 brute force ... ok test_clone (tests.TestCase_RetevisRT21) Testing Retevis RT21 clone ... ok test_copy_all (tests.TestCase_RetevisRT21) Testing Retevis RT21 copy all ... ok test_detect (tests.TestCase_RetevisRT21) Testing Retevis RT21 detect ... ok test_edges (tests.TestCase_RetevisRT21) Testing Retevis RT21 edges ... ok test_settings (tests.TestCase_RetevisRT21) Testing Retevis RT21 settings ... ok test_banks (tests.TestCase_YaesuFT817NDUS) Testing Yaesu FT-817ND (US) banks ... skipped 'Banks not supported' test_brute_force (tests.TestCase_YaesuFT817NDUS) Testing Yaesu FT-817ND (US) brute force ... ok test_clone (tests.TestCase_YaesuFT817NDUS) Testing Yaesu FT-817ND (US) clone ... ok test_copy_all (tests.TestCase_YaesuFT817NDUS) Testing Yaesu FT-817ND (US) copy all ... ok test_detect (tests.TestCase_YaesuFT817NDUS) Testing Yaesu FT-817ND (US) detect ... ok test_edges (tests.TestCase_YaesuFT817NDUS) Testing Yaesu FT-817ND (US) edges ... ok test_settings (tests.TestCase_YaesuFT817NDUS) Testing Yaesu FT-817ND (US) settings ... ok ---------------------------------------------------------------------- Ran 770 tests in 191.473s OK (skipped=109) style create: /chirp.hg/.tox/style style installdeps: pep8==1.6.2 style inst: /chirp.hg/.tox/dist/chirp-0.3.0dev.zip style installed: chirp==0.3.0.dev0,mercurial==3.7.3,pep8==1.6.2,pluggy==0.6.0,py==1.5.3,pyserial==3.0.1,six==1.11.0,tox==2.9.1,virtualenv==15.2.0 style runtests: PYTHONHASHSEED='1776514870' style runtests: commands[0] | python ./tools/cpep8.py ___________________________________ summary ____________________________________ unit: commands succeeded driver: commands succeeded style: commands succeeded congratulations :) Email was triggered for: Success Sending email for trigger: Success

1 0

[chirp_devel] New FT-405D Driver
by Rick DeWitt 05 Jun '18

05 Jun '18

Attached is the patch file for the new Yaesu FT-450D driver. Please let me know what fails if it doesn't pass the style check, I scrubbed it as well as I can with Windows and Notepad++ and I am trying to keep notes of what fails. Ditto for the patch file format. Thanks! -- Rick DeWitt AA0RD Sequim, Washington, USA 360-681-3494

2 1

[chirp_devel] [PATCH] A module that provides Chirp functionalities to custom python scripts #5859
by Terence Paddack 05 Jun '18

05 Jun '18

# HG changeset patch # User Terence Paddack <terence.paddack(a)gmail.com> # Date 1528162132 18000 # Mon Jun 04 20:28:52 2018 -0500 # Node ID af8ce534bb949d2289c6f9b66650b333ea6e7ac5 # Parent 0cbedd969bad9e0635e58d138266add5edbf2779 A module that provides Chirp functionalities to custom python scripts #5859 diff -r 0cbedd969bad -r af8ce534bb94 README.chirpAPI --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/README.chirpAPI Mon Jun 04 20:28:52 2018 -0500 @@ -0,0 +1,204 @@ +readme.chirpAPI +Copyright 2018 Terence C. Paddack (KF5TOK) + +Introduction +chirpAPI is a Python library that contains functions that can be used to carry out many of the operations performed by Chirp that are usually only available in chirpW, which is the GUI version. It was inspired by chirpc -- the Chirp command line interface -- but has been rewritten from scratch to be an importable module rather than a completely self-contained command line interface. Since this is not a stand-alone program, it doesn't entirely replace chirpc. Instead, it is intended to provide application programmers with an interface to a number of the Python modules that Chirp uses to work its magic. chirpAPI is therefore, an Application Programming Interface (API). The remainder of this document will serve to provide examples of how chirpAPI can be used for this purpose. I will begin by demonstrating its basic functionality in the Python console. Once you have mastered the basics, you may well find that chirpAPI can serve as a suitable alternative to chirpc until somebody (maybe you) can incorporate it into chirpc or another similar command line interface someday. + +General Features of chirpAPI +The chirpAPI file is extensively commented with information about the purpose of each function, the required arguments (and data types of those arguments) of each function, usage examples of each function, and additional comments pertaining to the unique quirks of each function; I tried to provide enough information to allow you to incorporate these functions into your own custom python scripts. There are several different type of functions in the chirpAPI that can be classified according to how they work. + +The following functions extract data from Chirp libraries or your radio memory map and store them in a list for later inspection. For each of these functions, the output can be used by your Python script to make decisions, or it can be printed using the print_list function; an example will be provided under the section of this document entitled 'Using the chirpAPI -- A Tutorial'. + + list_ports + list_all_radios + list_vendors + list_radios + list_setting_groups + list_setting_options + list_settings + list_valid_modes + list_valid_bands + list_power_levels + list_tuning_steps + list_mem + +The following functions print data (into the Python console or command line terminal) from Chirp libraries or your radio memory map. The last three of these functions are special cases that require more specific arguments; they have been denoted with an asterisk (*). For example, print_mem_list is intended to be used in situations where print_mem does not show all of the necessary information to determine if the memory map has been properly edited by another function; print_mem_list requires the output from list_mem as an argument. The print_list function requires ouput from one of the list_ functions above as an argument. The print_search_results function is used to display the results from the search_settings function, so output from search_settings is required for print_search_results to function properly. + + print_all_radios + print_all_mem + print_settings + print_mem + print_power_levels + + print_mem_list* + print_list* + print_search_results* + +The following functions manipulate the memory map image file, and have been divided into three groups. All of these functions have been written to return a value of 0 indicating success or a value of 1 indicating failure. The first group in this section includes functions that download and upload memory map images. The second group in this section includes functions that manipulate entire memory channels. The third group of functions in the section alter specific attributes of a memory channel and save the changes to the memory map image. + + download_mmap + upload_mmap + + copy_mem_channel + erase_mem_channel + move_mem_channel + + set_mem_freq + set_mem_offset + set_mem_duplex + set_mem_name + set_mem_mode + set_mem_tenc + set_mem_tsql + set_mem_dtcsenc + set_mem_dtcssql + set_mem_dtcspol + set_mem_cross_tone + set_mem_tuning_step + set_mem_power + set_mem_skip + +The following functions were included in the API to reduce the number of lines of redundant code in the above-listed functions; they are not intended for use outside of this scope, but they could come in handy if you intend to step through a sequence of code in this API in the Python console for debugging purposes (hopefully you will not need to do that). + + setup_global_vars + write_memory + +The following funcions can be used to identify and edit a radio's other settings. search_settings can be used to find information that will allow you to use edit_setting. Once that information has been obtained, it can be hard-coded into your script; the only time the information needed to change a particular setting is likely to change is if the radio's driver is updated to reflect a change in supported radio settings. An example of the use of these two functions is provided under the section of this document entitled 'Using the chirpAPI -- A Tutorial'. + + search_settings + edit_setting + +Getting Started - Linux +Chirp can be installed on the Raspberry Pi or other Linux distros by following the instructions under the heading 'Other Linux Users' at the URL below. If you have already installed Chirp, and you're reading this file as part of that installation, you can proceed to the 'Using the chirpAPI -- A Tutorial' section of this document. Otherwise, the following page has instructions on how to install the latest daily build of Chirp on your system: + https://chirp.danplanet.com/projects/chirp/wiki/Download#Other-Linux-Users + +Getting Started - Windows +chirAPI can be used in Windows, but it is not necessarily for the faint of heart. Currently, chirpAPI requires Python 2.7.x (where x is the latest latest minor version) to be installed on your system; it will not work properly in Python 3. If you are using Windows, you will probably need install Python yourself. Here is a URL: + https://www.python.org/downloads/windows/ + +Next, to use chirpAPI in Windows, you will need to set up a Chirp development environment. Instructions can be found at the following URL: + https://chirp.danplanet.com/projects/chirp/wiki/DevelopersWin32Environment + +Once you have cloned the repository you can proceed to the tutorial below. + +Using the chirpAPI -- A Tutorial +Once you have Chirp and python successfully installed, open a command prompt and navigate to the directory where Chirp is installed. Among other files, chirpAPI and chirpw should be in that directory. Next, open a python console in your command prompt (if you are running Linux, you might need to do this as root since chirpAPI will be doing file I/O). If you are following along with the examples, from this point on, type the indented text into your python console (press the <Enter> key after each line). + +In Windows: + python + from chirpAPI import * + +In Linux: + sudo python + from chirpAPI import * + +Before you can download the memory map of your radio, you will need to find the exact, case-sensitive, name of your radio model as it is listed in Chirp. There are a number of ways to do this, but we will start by printing a list of all supported radio models: + print_all_radios() + +Scroll through the list of radios and find your model. You will need to type it into some of the downstream commands exactly as it appears in this list. Alternatively, you could store that string value in an intermediate variable to reduce keystrokes. In the examples below, I will be programming the ubiquitous Baofeng UV-5R. If you are using a different radio, substitute the string corresponding to your radio model in the line below: + model = 'Baofeng_UV-5R' + +Next, we will need to find the port to which your radio is connected. If your computer has more than one port in use, it may be difficult to know which one represents your radio programming cable. In this situation, I have had some luck with the following procedure. Leave your radio programming cable disconnected and enter the following: + temp = list_ports() + print_list(temp) + +Next, ensure that your radio is connected properly by following the same sequence of steps that you would normally follow when using the GUI version of Chirp. Enter the previous lines again, and note which new port appears. + temp = list_ports() + print_list(temp) + +Since I am using a Raspberry Pi to walk through this tutorial, my port may differ from yours. If you are using Windows, your port may follow the format COMx, where x is some integer value. Once you know which port to use, substitute that string value into the line below and proceed: + port = '/dev/ttyUSB0' + +Soon, we will download a memory map image from your radio. It will require you to input the name of the target image file to which the memory map will be saved. The following will store the name of your memory map file in an intermediate variable. I find this format to be useful. + image = 'Baofeng_UV-5R.img' + download_mmap(model, port, image) + +Next, we will visually inspect the memory map image: + print_all_mem(image) + +Now we can add a new channel for a hypothetical repeater on 146.860 MHz at channel 50 (if successful, the memory channel contents should print followed by the return value of 0 on the next line): + set_mem_freq(image, 146860000, 50) + +Now we can set a frequency offset of -600 KHz (again, the printed output should reflect our change to the memory channel): + set_mem_offset(image, -600000, 50) + +We can set a PL tone of 100.0 to channel 50 as follows: + set_mem_tenc(image, 100.0, 50) + +Let's assume the repeater is very close to our home QTH, so we want to transmit on low power. In order to figure out what our power options are use the following (this command prints the valid power levels for our radio model in dBm): + print_power_levels(image) + +According to the printed output, for the UV-5R, the lowest valid option is 30 dBm, so let's set that value to channel 50 now (printed output from this command should show 'Low' at the end of the new line of printed text): + set_mem_power(image, 30, 50) + + +Maybe we'd like to program the name of this repeater into the memory channel. If you want to know the maximum name-length supported by your radio you can use: + temp = get_valid_namelen(image) + print temp + +For the UV-5R the maximum name-length is 7 characters, so we want to keep our imput under that value. If we use a longer value, the following function will cut it down to the maximum length allowed. Observe: + set_mem_name(image, 'Way too long of a name', 50) + +You may also notice from the output printed after the last command that if your radio does not support lower-case characters (like the UV-5R) the name gets capitalized before it's saved to the memory channel. Let's try a better name this time: + set_mem_name(image, 'My-ARC', 50) + +What about all that QRM being generated by that other repeater on the same frequency just slightly not far enough away? Luckily, that repeater uses a different set of tones, so we can squelch out the interfering transmissions. For that, we need to use a different function than the one we used to set the PL tone. This one sets our PL tone and tone squelch tone simultaneously: + set_mem_cross_tone(image, 100.0, 100.0, 50) + +That last function can also set up CTCSS tones and/or DTCS codes in any combination. I suppose that could be useful in special situations. Now is a good time to mention that set_mem_cross_tone is not supported by all radio models. There are a few other functions in the API like that. In each case, I have tried to include printed output that explains the situation when it occurs. + +Here we will set our radio to transmit a DTCS code of 271 and use of CTCSS tone of 123.0 to open the squelch. Let's give it a try: + set_mem_cross_tone(image, 271, 123.0, 50) + +That's great and all, but what if our hypothetical repeater system requires that DTCS tone to have an inverted (or reversed) polarity. Here's how that can be accomplished: + set_mem_dtcspol(image, 'RN', 50) + +What if we want to adjust the carrier squelch level of our radio? Sure, that's something we can do in the Chirp GUI environment, by clicking on the 'Settings' tab, but can the chirpAPI handle such a tall order? As luck would have it, yes! First, a few words about radio settings: Chirp stores radio settings in an object, whose structure varies (based on radio drivers) from one radio model to the next. Have you ever noticed that different radios have different setting options, and that they are grouped in different ways in the Chirp GUI? I thought you might have. Since that's the case, our program can't always depend upon those settings being located in the same place in Chirp's data structure. In fact, the setting we're looking for may not even be there at all! So how do we find it, if it's even in there? I'm glad you asked. The next function searches the entire radio settings object for a keyword that is present in the setting's option description. Since we're looking for 'squelch', that's the search term we'll use. Depending on the number of matches and the size of the radio settings data structure, this command may take a number of seconds: + temp = search_settings(image, 'squelch') + +If you're following along on your UV-5R, you may have noticed that it did indeed take a little while. You may also have noticed that quite a few matches for the search term 'squelch' were found. Fortunately for me, and hopefully for you too, the one we're interested in is first on the list. The first line of actual results should look something like this: + 0: Basic Settings(0)-->Carrier Squelch Level(0): 9 + ^ ^ ^ ^ + | | | | +This is our result# | | | +Computers like to | | | +start counting at 0 | | | + | | | + This is the setting's | | + group number. We'll | | + need that value later. | | + | | + | | + This is the setting's | + option number. We'll | + need that too. | + This is the setting's + current value. Yours + may differ. + +A squelch level of 9 is kinda high, huh? Maybe we should set it lower in case we're on a simplex channel and want to hear more distant stations. Sure, we could do that pretty easily in the Baofeng's menu, but where's the fun it that? After all, if you've read this far down, you probably genuinely want to know how this thing works, right? The next function uses the group number and option number as a kind of address to know which setting it's supposed to change. Let's say that we want to set the squelch to 4: + edit_setting(image, 4, 0, 0) + +In case you were wondering, the first 0 is for the group number, and the second 0 is for the option number. If you're like me, you're more interested in programming with the chirpAPI than you are using it as a slow, typing-intensive way to program your radio. That being the case, you'll need more information than what I could realistically provide in this file. Currently, the best way to get the details is to open up chirpAPI in your favorite Python editor (or just a basic text-editor) and read the comments. There are plenty of them. + +Let's say you want to move the contents of our experimental memory channel to another memory channel location...maybe 25. That can be accomplished as follows: + move_mem_channel(image, 50, 25) + +Now, say you want to make a duplicate of it in channel 26: + copy_mem_channel(image, 25, 26) + print_all_mem(image) + +Maybe you want to delete channel 25, after all: + erase_mem_channel(image, 25) + print_all_mem(image) + +At this point, you can inspect the memory map image by opening the file in the GUI version of Chirp. It should, more or less, confirm that our changes have, in fact, been saved. If you look really closely, you may notice a few minor differences between what you see and what you expect to see based on the source code and output of the chirAPI; I know I have. It appears that once the commands from chirpAPI are sent to the radio's driver, it can sometimes interpret them a little differently to accomodate the radio's capabilities. In all cases where I have noticed such discrepancies, none of them resulted in unexpected changes in the function of the radio; your mileage may vary, so if you notice something not working properly, double-check it, triple-check it, then...bug report. I can't promise that I will personally be able to fix it in a timely manner -- I don't always have 2+ weeks to devote to full-time chirpAPI development -- but that's the beauty of the free software system; anybody can fix it -- even you. + +Assuming everything looks like it's supposed to and you are happy with the results, you can upload your memory map image file to your radio as follows: + upload_mmap(model, port, image) + +The speed of reading and writing memory maps can vary based on how large the memory map is, how fast the connection is between your radio and computer, and (I suspect) a variety of environmental factors. I have noticed that my bigger, fancier Chinese radios take much longer than my smaller, cheaper Chinese radios, so take that into consideration if you're looking to build a Raspberry Pi-controlled remote base for your home-brew repeater. + +I hope this tutorial has been useful in introducing you to the chirpAPI. I am excited about the possibilities that it opens up, and I look forward to seeing what you do with it. Remember to read the comments and use this tool responsibly. + +73 de KF5TOK \ No newline at end of file diff -r 0cbedd969bad -r af8ce534bb94 chirpAPI.py --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/chirpAPI.py Mon Jun 04 20:28:52 2018 -0500 @@ -0,0 +1,1206 @@ +# Copyright 2018 Terence C. Paddack (KF5TOK) +# +# This program is free software: you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation, either version 3 of the License, or +# (at your option) any later version. +# +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY; without even the implied warranty of +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with this program. If not, see <http://www.gnu.org/licenses/>. + +import serial +import collections + +from chirp import chirp_common, directory, settings +from chirp.drivers import * + +RADIOS = directory.DRV_TO_RADIO + +#The following list contains all of the attributes of a memory channel that will be listed by list_mem() +mem_attr = ['number', 'freq', 'name', 'tmode', 'rtone', 'ctone', 'dtcs', 'rx_dtcs', 'dtcs_polarity', 'cross_mode', 'duplex', 'offset', 'mode', 'power', 'skip', 'empty'] + +#Global Variables +rclass = '' +radio = '' +rf = '' + +class search_result(): +#This class is used by search_settings & print_search_results + def __init__(self): + self.query = '' + self.group = [] + self.option = [] + self.setting = [] + self.group_num = [] + self.option_num = [] + +def setup_global_vars(map_file): +#Assigns values to some variables that are used by multiple functions in this library +#Used by other functions in this library; not recommended for use by the end-user +#Required arguments: +# 1: map_file (string containing the name of the memory map file to which the changes will be written ex. 'QYT_KT8900D.img') +#Example Usage: setup_global_vars('QYT_KT8900D.img', mem, channel) +#Example Usage: setup_global_vars('Baofeng_UV-5R.img', mem, channel) +#Example Usage: setup_global_vars('Baofeng_BF-888.img', mem, channel) + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + else: + global rclass + global radio + global rf + rclass = directory.get_radio_by_image(map_file).__class__ + radio = rclass(map_file) + rf = radio.get_features() + ret_val = 0 + return ret_val + +def write_memory(map_file, mem, channel): +#Writes the contents of the memory channel object that it is passed into the memory map; +#Used by other functions in this library; not recommended for use by the end-user +#Required arguments: +# 1: map_file (string containing the name of the memory map file to which the changes will be written ex. 'QYT_KT8900D.img') +# 2: mem (mem class object containing all channel information to be written to the memory map) +# 3: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: write_memory('TYT_TH-9800.img', mem, channel) +#Example Usage: write_memory('QYT_KT8900D.img', mem, channel) +#Example Usage: write_memory('Baofeng_UV-5R.img', mem, channel) +#Example Usage: write_memory('Baofeng_BF-888.img', mem, channel) +#Comments: +# 1: WARNING: This function, which is used by most of the memory channel-editing functions, is NOT programmed to validate memory map contents! + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not isinstance(mem, chirp_common.Memory): + print "Type mismatch: mem must be a chirp memory object. You entered a '" + str(type(mem).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an int. You entered a '" + str(type(channel).__name__) + "'" + else: + setup_global_vars(map_file) + if mem.empty == True: + mem.empty = False + radio.set_memory(mem) + radio.save_mmap(map_file) + print_mem(map_file, channel) + ret_val = 0 + return ret_val + +def print_all_radios(): +#Prints all currently-supported radios +#Required arguments: none +#Example Usage: print_all_radios() + print "Supported Radios:\n\t", "\n\t".join(sorted(RADIOS.keys())) + +def print_list(input_list): +#Format and prints the contents of most lists generated by functions in this library that start with 'list_' +#Required arguments: +# 1: input_list (list whose contents are to be formatted & printed) +#Example Usage: print_list(temp) + if not isinstance(input_list, list): + print "Type mismatch: input_list must be a list. You entered a '" + str(type(input_list).__name__) + "'" + else: + for i in range(len(input_list)): + print str(i) + ': ' + str(input_list[i]) + +def print_all_mem(map_file): +#Prints the memory channel contents of the specified memory map +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +#Example Usage: print_all_mem('TYT_TH-9800.img') +#Example Usage: print_all_mem('QYT_KT8900D.img') +#Example Usage: print_all_mem('Baofeng_UV-5R.img') +#Example Usage: print_all_mem('Baofeng_BF-888.img') + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + else: + setup_global_vars(map_file) + start, end = rf.memory_bounds + for i in range(start, end + 1): + mem = radio.get_memory(i) + if mem.empty: + continue + print str(mem) + ' ' + str(mem.power) + +def print_settings(map_file, group_num): +#Prints the settings and options associated with the specified group of settings in the model's memory map file +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: group_num (integer corresponding to the group whose keys you want to list; these values are obtained by viewing the list by using list_settings_group(map_file) +#Example Usage: print_settings('QYT_KT8900D.img', 1) +#Example Usage: print_settings('Baofeng_UV-5R.img', 1) +#Example Usage: print_settings('Baofeng_BF-888.img', 0) + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(group_num) is int: + print "Type mismatch: group_num must be an integer. You entered a '" + str(type(group_num).__name__) + "'" + else: + options = list_setting_options(map_file, group_num) + settings = list_settings(map_file, group_num) + #Get the length of the longest string in the options list so we can justify the output text and make it look pretty + max_length = 0 + for i in range(len(options)): + length = len(options[i]) + if length > max_length: + max_length = length + #Loop through the lists and print them with some nice(-ish) formatting/text justification + num_digits = len(str(len(options))) + for i in range(len(options)): + print str(i).ljust(num_digits) + ': ' + str(options[i]).rjust(max_length) + ': ' + str(settings[i]) + +def print_mem(map_file, channel): +#Prints the contents of specified memory channel in the specified memory map file +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: channel (integer corresponding to the channel whose contents will be printed) +#Example Usage: print_mem('QYT_KT8900D.img', 19) +#Example Usage: print_mem('Baofeng_UV-5R.img', 1) +#Example Usage: print_mem('Baofeng_BF-888.img', 16) +#Bugs: +# 1: Does not display mem.rx_dtcs; this way of printing memory channel contents is a carry-over from chirpc. + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + setup_global_vars(map_file) + mem = radio.get_memory(channel) + print str(mem) + ' ' + str(mem.power) + +def print_mem_list(mem_list): +#Prints the contents of specified memory channel in the specified memory map file +#Required arguments: +# 1: mem_list (list, generated by list_mem, that contains memory channel information) +#Example Usage: print_mem_list('TYT_TH-9800.img', 20) +#Example Usage: print_mem_list('QYT_KT8900D.img', 19) +#Example Usage: print_mem_list('Baofeng_UV-5R.img', 1) +#Example Usage: print_mem_list('Baofeng_BF-888.img', 16) +#Comments: +# 1: This function prints memory channel information on mulitple lines in more detail than print_mem +# 2: Because it calls list_mem, it is slower than print_mem, but it does not suffer from the same lack of detail +# 3: This could be useful in situations where print_mem does not supply enough information + if not type(mem_list) is list: + print "Type mismatch: mem_list must be a list. You entered a '" + str(type(mem_list).__name__) + "'" + else: + for i in range(len(mem_attr)): + print mem_attr[i] + ': ' + str(mem_list[i]) + +def print_power_levels(map_file): +#Prints the valid power levels (in dBm) for a specified radio model; these values can be used with set_mem_power +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +#Example Usage: print_power_levels('TYT_TH-9800.img') +#Example Usage: print_power_levels('QYT_KT8900D.img') +#Example Usage: print_power_levels('Baofeng_UV-5R.img') +#Example Usage: print_power_levels('Baofeng_BF-888.img') + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + else: + setup_global_vars(map_file) + lvls = rf.valid_power_levels + for i in range(len(lvls)): + print lvls[i]._power + +def print_search_results(result): +#Formats & prints the contents of a search_result object obtained by using search_settings(map_file, search_str) +#Required arguments: +# 1: result (search_result object obtained by using search_settings function) +#Example Usage: print_search_results(temp) + if not type(result).__name__ == 'instance': + print "Type mismatch: result must be a search_result object. You entered a '" + str(type(result).__name__) + "'" + else: + num_digits = len(str(len(result.group))) + print 'Seach Results for: ' + result.query + print '# Group(group_num)-->Option(option_num): Setting' + for i in range(len(result.group)): + print str(i).rjust(num_digits) + ': ' + str(result.group[i]) + '(' + str(result.group_num[i]) + ')-->' + str(result.option[i]) + '(' + str(result.option_num[i]) + '): ' + str(result.setting[i]) + +def list_ports(): +#Returns a list of all currently-available ports +#Required arguments: none +#Usage example: temp = list_ports() +#Comments: +# 1: This is a hacked-together version of the code in chirp\platform.py. Initially, I had just called the list_serial_ports function in that file, but +# that caused an unexpected (and almost undetected) error when trying to import this API in a python console on a Raspberry Pi via SSH (this works now). + import re + from chirp.platform import win32_comports_bruteforce + from chirp.platform import natural_sorted + try: + from serial.tools.list_ports import comports + platform = 'linux' + except: + platform = 'win32' + if platform is 'linux': + ports = list(comports()) + elif platform is 'win32': + ports = win32_comports_bruteforce() + return natural_sorted([port for port, name, url in ports]) + +def list_all_radios(): +#Returns a list of all currently-supported radios +#Required arguments: none +#Usage example: temp = list_all_radios() + radio_list = [] + for radio in sorted(RADIOS.keys()): + radio_list.append(radio) + return radio_list + +def list_vendors(): +#Returns a list of all currently-supported radio brands +#Required arguments: none +#Example Usage: temp = list_vendors() +#Comments: +# 1: This code was lifted from chirp\ui\clone.py; it has been slightly modified from the original + vendors = collections.defaultdict(list) + for rclass in sorted(directory.DRV_TO_RADIO.values()): + if not issubclass(rclass, chirp_common.CloneModeRadio) and not issubclass(rclass, chirp_common.LiveRadio): + continue + vendors[rclass.VENDOR].append(rclass) + for alias in rclass.ALIASES: + vendors[alias.VENDOR].append(alias) + sorted_vendors = sorted(vendors.keys()) + return sorted_vendors + +def list_radios(vendor): +#Returns a list of all currently-supported radios made by the specified vendor +#Required arguments: +# 1: vendor (string containing the vendor of the radio models you want to list) +#Example Usage: temp = list_radios('TYT') +#Example Usage: temp = list_radios('Baofeng') +#Example Usage: temp = list_radios('MTC') +#Comments: +# 1: This code was lifted from chirp\ui\clone.py; it has been slightly modified from the original + if not type(vendor) is str: + print "Type mismatch: vendor must be a string. You entered a '" + str(type(vendor).__name__) + "'" + else: + models = [] + vendors = collections.defaultdict(list) + for rclass in sorted(directory.DRV_TO_RADIO.values()): + if not issubclass(rclass, chirp_common.CloneModeRadio) and not issubclass(rclass, chirp_common.LiveRadio): + continue + vendors[rclass.VENDOR].append(rclass) + for alias in rclass.ALIASES: + vendors[alias.VENDOR].append(alias) + models = sorted(vendors[vendor]) + radio_models = [x.MODEL for x in models] + return radio_models + +def list_setting_groups(map_file): +#Returns a list of setting groups (strings) associated with a particular model's memory map file +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +#Example Usage: temp = list_setting_groups('QYT_KT8900D.img') +#Example Usage: temp = list_setting_groups('Baofeng_UV-5R.img') +#Example Usage: temp = list_setting_groups('Baofeng_BF-888.img') + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + else: + setup_global_vars(map_file) + name = [] + groups = radio.get_settings() + for i in range(len(groups)): + name.append(str(groups[i].get_shortname())) + return name + +def list_setting_options(map_file, group_num): +#Returns a list of setting options (strings) associated with a particular group of settings in the model's memory map file +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: group_num (integer corresponding to the group whose keys you want to list; these values are obtained by viewing the list from list_settings_group(map_file) +#Example Usage: temp = list_setting_options('QYT_KT8900D.img', 1) +#Example Usage: temp = list_setting_options('Baofeng_UV-5R.img', 1) +#Example Usage: temp = list_setting_options('Baofeng_BF-888.img', 0) + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(group_num) is int: + print "Type mismatch: group_num must be an integer. You entered a '" + str(type(group_num).__name__) + "'" + else: + setup_global_vars(map_file) + options = [] + groups = radio.get_settings() + i = 0 + for element in groups[group_num]: + temp = str(element._shortname) + options.append(temp) + return options + +def list_settings(map_file, group_num): +#Returns a list of setting values associated with a particular group of settings in the model's memory map file +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: group_num (integer corresponding to the group whose keys you want to list; these values are obtained by viewing the list from list_settings_group(map_file) +#Example Usage: temp = list_settings('QYT_KT8900D.img', 1) +#Example Usage: temp = list_settings('Baofeng_UV-5R.img', 1) +#Example Usage: temp = list_settings('Baofeng_BF-888.img', 0) + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(group_num) is int: + print "Type mismatch: group_num must be an integer. You entered a '" + str(type(group_num).__name__) + "'" + else: + setup_global_vars(map_file) + settings = [] + groups = radio.get_settings() + group = groups[group_num] + for i in range(len(group)): + temp = group[group.keys()[i]].values()[0] + settings.append(temp) + return settings + +def list_valid_modes(map_file): +#Returns a list of the valid emission modes for a specified radio model; these values can be used with set_mem_mode +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +#Example Usage: temp = list_valid_modes('TYT_TH-9800.img') +#Example Usage: temp = list_valid_modes('QYT_KT8900D.img') +#Example Usage: temp = list_valid_modes('Baofeng_UV-5R.img') +#Example Usage: temp = list_valid_modes('Baofeng_BF-888.img') + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + else: + setup_global_vars(map_file) + modes = list(rf.valid_modes) + return modes + +def list_valid_bands(map_file): +#Returns a list of the supported bands of a specified radio model +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +#Example Usage: temp = list_valid_bands('TYT_TH-9800.img') +#Example Usage: temp = list_valid_bands('QYT_KT8900D.img') +#Example Usage: temp = list_valid_bands('Baofeng_UV-5R.img') +#Example Usage: temp = list_valid_bands('Baofeng_BF-888.img') + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + else: + setup_global_vars(map_file) + bands = list(rf.valid_bands) + return bands + +def list_power_levels(map_file): +#Returns a list of the valid power levels (in dBm) for a specified radio model; these values can be used with set_mem_power +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +#Example Usage: temp = list_power_levels('QYT_KT8900D.img') +#Example Usage: temp = list_power_levels('Baofeng_UV-5R.img') +#Example Usage: temp = list_power_levels('Baofeng_BF-888.img') + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + else: + setup_global_vars(map_file) + power_levels = [] + lvls = rf.valid_power_levels + for i in range(len(lvls)): + power_levels.append(lvls[i]._power) + return power_levels + +def list_tuning_steps(map_file): +#Returns a list of the tuning steps in KHz for a specified radio model; these values can be used with set_mem_tuning_step +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +#Example Usage: temp = list_tuning_steps('TYT_TH-9800.img') +#Example Usage: temp = list_tuning_steps('QYT_KT8900D.img') +#Example Usage: temp = list_tuning_steps('Baofeng_UV-5R.img') +#Example Usage: temp = list_tuning_steps('Baofeng_BF-888.img') + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + else: + setup_global_vars(map_file) + tuning_steps = list(rf.valid_tuning_steps) + return tuning_steps + +def list_mem(map_file, channel): +#Returns a list of memory attributes (types vary) of a single channel in the memory map of a radio +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: channel (integer corresponding to the channel whose contents will be printed) +#Example Usage: temp = list_mem('QYT_KT8900D.img', 19) +#Example Usage: temp = list_mem('Baofeng_UV-5R.img', 18) +#Example Usage: temp = list_mem('Baofeng_BF-888.img', 1) + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + setup_global_vars(map_file) + mem = radio.get_memory(channel) + memory_channel = [] + for i in range(len(mem_attr)): + temp = getattr(mem, mem_attr[i]) + memory_channel.append(temp) + return memory_channel + +def download_mmap(radio_model, serial_port, map_file): +#Downloads the memory map of a radio via a serial or USB port and saves it as a .img file +#Required arguments: +# 1: radio_model (string conforming to the model of the radio as defined in list_radios ex. 'QYT_KT8900D') +# 2: serial_port (string referring to the port connected to the radio ex. '/dev/ttyUSB0' in linux or 'COM7' in Windows) +# 3: map_file (string containing the name of the file to be created ex. 'QYT_KT8900D.img') +#Example Usage: download_mmap('TYT_TH-9800', 'COM7', 'TYT_TH-9800.img') +#Example Usage: download_mmap('QYT_KT8900D', 'COM7', 'QYT_KT8900D.img') +#Example Usage: download_mmap('QYT_KT8900D', '/dev/ttyUSB0', 'QYT_KT8900D.img') +#Example Usage: download_mmap('Baofeng_UV-5R', 'COM3', 'Baofeng_UV-5R.img') +#Example Usage: download_mmap('Baofeng_BF-888', 'COM3', 'Baofeng_BF-888.img') + ret_val = 1 + if not type(radio_model) is str: + print "Type mismatch: radio_model must be a string. You entered a '" + str(type(radio_model).__name__) + "'" + elif not type(serial_port) is str: + print "Type mismatch: serial_port must be an string. You entered a '" + str(type(serial_port).__name__) + "'" + elif not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + else: + rclass = directory.get_radio(radio_model) + s = serial.Serial(port=serial_port, baudrate=rclass.BAUD_RATE, timeout=0.5) + radio = rclass(s) + radio.sync_in() + radio.save_mmap(map_file) + print "Download Successful!" + ret_val = 0 + return ret_val + +def upload_mmap(radio_model, serial_port, map_file): +#Uploads the memory map into the radio via a serial or USB port +#Required arguments: +# 1: radio_model (string conforming to the model of the radio as defined in list_radios ex. 'QYT_KT8900D') +# 2: serial_port (string referring to the port connected to the radio ex. '/dev/ttyUSB0' in linux or 'COM7' in Windows) +# 3: map_file (string containing the name of the file to be uploaded ex. 'QYT_KT8900D.img') +#Example Usage: upload_mmap('TYT_TH-9800', 'COM7', 'TYT_TH-9800.img') +#Example Usage: upload_mmap('QYT_KT8900D', 'COM7', 'QYT_KT8900D.img') +#Example Usage: upload_mmap('Baofeng_UV-5R', 'COM3', 'Baofeng_UV-5R.img') +#Example Usage: upload_mmap('Baofeng_BF-888', 'COM3', 'Baofeng_BF-888.img') + ret_val = 1 + if not type(radio_model) is str: + print "Type mismatch: radio_model must be a string. You entered a '" + str(type(radio_model).__name__) + "'" + elif not type(serial_port) is str: + print "Type mismatch: serial_port must be an string. You entered a '" + str(type(serial_port).__name__) + "'" + elif not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + else: + rclass = directory.get_radio(radio_model) + s = serial.Serial(port=serial_port, baudrate=rclass.BAUD_RATE, timeout=0.5) + radio = rclass(s) + radio.load_mmap(map_file) + radio.sync_out() + print 'Upload Successful!' + ret_val = 0 + return ret_val + +def copy_mem_channel(map_file, source, destination): +#Copies the contents of the source memory channel into the destination memory channel of the given memory map image file +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: source (integer corresponding to the channel whose contents will be copied to another channel) +# 3: destination (integer corresponding to the destination channel into which source's contents will be copied) +#Example Usage: copy_mem_channel('TYT_TH-9800.img', 20, 22) +#Example Usage: copy_mem_channel('QYT_KT8900D.img', 1, 10) + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(source) is int: + print "Type mismatch: source must be an integer. You entered a '" + str(type(source).__name__) + "'" + elif not type(destination) is int: + print "Type mismatch: destination must be an integer. You entered a '" + str(type(destination).__name__) + "'" + else: + setup_global_vars(map_file) + mem = radio.get_memory(source) + mem.number = destination + radio.set_memory(mem) + radio.save_mmap(map_file) + ret_val = 0 + return ret_val + +def erase_mem_channel(map_file, channel): +#Erases the contents of the specified memory channel in the specified memory map file +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: source (integer corresponding to the channel whose contents will be erased) +#Example Usage: erase_mem_channel('TYT_TH-9800.img', 22) +#Example Usage: erase_mem_channel('QYT_KT8900D.img', 20) +#Example Usage: erase_mem_channel('Baofeng_UV-5R.img', 20) +#Example Usage: erase_mem_channel('Baofeng_BF-888.img', 20) + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + setup_global_vars(map_file) + mem = radio.get_memory(channel) + mem.empty = True + radio.set_memory(mem) + radio.save_mmap(map_file) + ret_val = 0 + return ret_val + +def move_mem_channel(map_file, source, destination): +#Moves the contents of the source memory channel into the destination memory channel of the given memory map image file +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: source (integer corresponding to the channel whose contents will be moved to another channel) +# 3: destination (integer corresponding to the destination channel into which source's contents will be moved) +#Example Usage: move_mem_channel('TYT_TH-9800.img', 20, 21) +#Example Usage: move_mem_channel('QYT_KT8900D.img', 10, 1) + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(source) is int: + print "Type mismatch: source must be an integer. You entered a '" + str(type(source).__name__) + "'" + elif not type(destination) is int: + print "Type mismatch: destination must be an integer. You entered a '" + str(type(destination).__name__) + "'" + else: + setup_global_vars(map_file) + copy_mem_channel(map_file, source, destination) + erase_mem_channel(map_file, source) + print_all_mem(map_file) + ret_val = 0 + return ret_val + +def get_valid_namelen(map_file): +#Returns an integer containing the maximum length of a memory channel name supported by the radio model +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +#Example Usage: get_valid_namelen('TYT_TH-9800.img') +#Example Usage: get_valid_namelen('QYT_KT8900D.img') +#Example Usage: get_valid_namelen('Baofeng_UV-5R.img') +#Example Usage: get_valid_namelen('Baofeng_BF-888.img') + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + else: + setup_global_vars(map_file) + valid_length = rf.valid_name_length + return valid_length + +def search_settings(map_file, search_str): +#Searches the radio's settings for options that contain the search_str; returns a nested list object containing the results of the search +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: search_str (string containing the text to find in the settings ex. 'squelch') +#Example Usage: temp = search_settings('TYT_TH-9800.img', 'squelch') +#Example Usage: temp = search_settings('QYT_KT8900D.img', 'squelch') +#Example Usage: temp = search_settings('Baofeng_UV-5R.img', 'squelch') +#Example Usage: temp = search_settings('Baofeng_BF-888.img', 'squelch') +#Comments: +# 1: Chirp stores radio settings in a RadioSettingGroup object, which varies (based on radio drivers) from one model to the next. +# 2: Output from this function contains (among other things) the 'address' for a particular setting. +# The 'address' values are found in parentheses after the Group Name and Option Name, respectively. +# 3: This search is not case sensitive, and appropriate search terms can be found by examining the main window-pane in the 'Settings' tab in the Chirp GUI. + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(search_str) is str: + print "Type mismatch: search_str must be a string. You entered a '" + str(type(search_str).__name__) + "'" + else: + setup_global_vars(map_file) + result = search_result() + result.query = search_str + groups = list_setting_groups(map_file) + for group_num in range(len(groups)): + options = list_setting_options(map_file, group_num) + settings = list_settings(map_file, group_num) + for option_num in range(len(options)): + temp = options[option_num].upper() + if search_str.upper() in temp: + result.group.append(groups[group_num]) + result.option.append(options[option_num]) + result.setting.append(settings[option_num]) + result.group_num.append(group_num) + result.option_num.append(option_num) + print_search_results(result) + return result + +def edit_setting(map_file, value, group_num, option_num): +#Edits the setting specified by option_num in the group specified by group_num in the radio's memory map +#Feed the output from search_settings into print_search_results to see the group_num and option_num for the setting you want to edit +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: value (value that you want to store in the setting...make sure the type is correct) +# 2: group_num (integer representing the group number that contains the desired options) +# 3: option_num (integer representing the option that corresponds to the desired setting) +#Example Usage: edit_setting('TYT_TH-9800.img', 4, 0, 1) #set beep volume to 4 +#Example Usage: edit_setting('QYT_KT8900D.img', 6, 0, 1) #set carrier squelch to 6 +#Example Usage: edit_setting('Baofeng_UV-5R.img', 8, 0, 0) #set carrier squelch to 8 +#Example Usage: edit_setting('Baofeng_BF-888.img', 5, 0, 13) #set carrier squelch to 5 +#Comments: +# 1: Chirp stores radio settings in a RadioSettingGroup object, which varies (based on radio drivers) from one model to the next +# 2: The last two arguments fed into this function serve as an address for a particular setting; these arguments can be found by examining output from the +# print_search_results function. The argument values are found in parentheses after the Group Name and Option Name, respectively. + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(group_num) is int: + print "Type mismatch: group_num must be an integer. You entered a '" + str(type(group_num).__name__) + "'" + elif not type(option_num) is int: + print "Type mismatch: option_num must be an integer. You entered a '" + str(type(option_num).__name__) + "'" + else: + setup_global_vars(map_file) + groups = radio.get_settings() + group = groups[group_num] + setting = group[group.keys()[option_num]].values()[0] + #Get the data type of the specified option + setting_type = type(setting.get_value()).__name__ + #Check settings's data type against value's data type + if not setting_type == type(value).__name__: + print "Type mismatch: value must be a '" + setting_type + "' type value. You entered a '" + type(value).__name__ + "'" + else: + setting.set_value(value) + radio.set_settings(groups) + radio.save_mmap(map_file) + #Everything from here down can be removed if you don't want to print confirmation output; removing the code below should increase speed + #Generate a search_result object and print it + groups = list_setting_groups(map_file) + options = list_setting_options(map_file, group_num) + settings = list_settings(map_file, group_num) + result = search_result() + result.query = options[option_num] + result.group.append(groups[group_num]) + result.option.append(options[option_num]) + result.setting.append(settings[option_num]) + result.group_num.append(group_num) + result.option_num.append(option_num) + print_search_results(result) + #Keep the line below, though + ret_val = 0 + return ret_val + +def set_mem_freq(map_file, frequency, channel): +#Programs a frequency into a channel in the radio's memory map +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: frequency (integer containing the frequency in Hz to be copied into the memory map) +# 3: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: set_mem_freq('TYT_TH-9800.img', 29600000, 20) +#Example Usage: set_mem_freq('QYT_KT8900D.img', 146520000, 20) +#Example Usage: set_mem_freq('Baofeng_UV-5R.img', 146520000, 20) +#Example Usage: set_mem_freq('Baofeng_BF-888.img', 446000000, 1) +#Comments: +# 1: This function does not check to see if the frequency falls within the radio's supported bands; this is by intention on the part of this code's author. +# This allows for extended reception as well as experimentation to advance your technical skills in the radio art. The onus is (and has always been) on you, +# the licensed amateur to use this code responsibly, ethically, and in keeping with your country's rules and the highest standards of the ham radio community. +# Transmission outside of the radio's manufacturer-approved bands may result in damage to your radio or the generation of (potentially-unlawful) spurious emissions. + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(frequency) is int: + print "Type mismatch: frequency must be an integer. You entered a '" + str(type(frequency).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + setup_global_vars(map_file) + mem = radio.get_memory(channel) + mem.freq = frequency + write_memory(map_file, mem, channel) + ret_val = 0 + return ret_val + +def set_mem_offset(map_file, offset, channel): +#Programs an Rx/Tx frequency offset into a channel in the radio's memory map +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: offset (integer containing the offset in Hz to be copied into the memory map) +# 3: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: set_mem_offset('TYT_TH-9800.img', 0, 20) +#Example Usage: set_mem_offset('QYT_KT8900D.img', -600000, 19) +#Example Usage: set_mem_offset('Baofeng_UV-5R.img', 600000, 20) +#Example Usage: set_mem_offset('Baofeng_BF-888.img', 5000000, 1) + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(offset) is int: + print "Type mismatch: offset must be an integer. You entered a '" + str(type(offset).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + setup_global_vars(map_file) + mem = radio.get_memory(channel) + if offset < 0: + #print("Negative shift detected!") + shift_dir = '-' + elif offset > 0: + #print("POSITIVE shift detected!") + shift_dir = '+' + elif offset == 0: + shift_dir = '' + mem.duplex = shift_dir + mem.offset = abs(offset) + write_memory(map_file, mem, channel) + ret_val = 0 + return ret_val + +def set_mem_duplex(map_file, tx_freq, rx_freq, channel): +#Programs the Tx and Rx frequency duplex pair into a specified channel in the specified radio memory map +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: tx_freq (integer containing the transmit frequency in Hz to be copied into the memory map) +# 3: rx_freq (integer containing the receive frequency in Hz to be copied into the memory map) +# 4: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: set_mem_duplex('TYT_TH-9800.img', 144490000, 145800000, 19) +#Example Usage: set_mem_duplex('QYT_KT8900D.img', 144490000, 145800000, 20) +#Example Usage: set_mem_duplex('Baofeng_UV-5R.img', 144490000, 145800000, 20) +#Example Usage: set_mem_duplex('Baofeng_BF-888.img', 144490000, 145800000, 14) +#Comments: +# 1: Invalid duplex values (determined by radio model) will be rejected and throw an error + ret_val = 1 + setup_global_vars(map_file) + mem = radio.get_memory(channel) + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(tx_freq) is int: + print "Type mismatch: tx_freq must be an integer. You entered a '" + str(type(tx_freq).__name__) + "'" + elif not type(rx_freq) is int: + print "Type mismatch: rx_freq must be an integer. You entered a '" + str(type(rx_freq).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + if not 'split' in rf.valid_duplexes: + print 'This feature requires your radio to support duplex modes; it appears that your radio model does not.' + else: + mem.duplex = 'split' + mem.freq = rx_freq + mem.offset = tx_freq + write_memory(map_file, mem, channel) + ret_val = 0 + return ret_val + +def set_mem_name(map_file, name, channel): +#Programs a memory channel name into the radio's memory map; truncates the name to the maximum length allowed by the radio model +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: name (string containing the channel name to be copied into the memory map) +# 3: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: set_mem_name('TYT_TH-9800.img', 'FM SIMPLEX', 20) +#Example Usage: set_mem_name('QYT_KT8900D.img', 'Chirp Rules!', 19) +#Example Usage: set_mem_name('Baofeng_UV-5R.img', 'TESTING', 20) +#Example Usage: set_mem_name('Baofeng_BF-888.img', 'Simplex', 1) #This appears to not be supported on the Baofeng_BF-888 +#Comments: +# 1: Truncates name length to the maximum name length allowed by the radio +# 2: Strings that contain invalid characters (determined by radio model) will be rejected and throw an error +# 3: If lower case characters are not valid, this function converts all characters to upper case prior to checking for invalid characters + ret_val = 1 + setup_global_vars(map_file) + mem = radio.get_memory(channel) + bln_invalid = False + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(name) is str: + print "Type mismatch: name must be a string. You entered a '" + str(type(name).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + if rf.has_name == False: + print 'This radio model does not support memory channel names. No changes have been made.' + return ret_val + if not 'a' in rf.valid_characters: + name = name.upper() + for i in range(len(name)): + if name[i] not in rf.valid_characters: + print "'" + name[i] + "' is an invalid character for this radio model. No changes have been made." + bln_invalid = True + if bln_invalid == False: + max_len = get_valid_namelen(map_file) + mem.name = name[0:max_len] + write_memory(map_file, mem, channel) + ret_val = 0 + return ret_val + +def set_mem_mode(map_file, mode, channel): +#Programs an emission mode into a channel in the radio's memory map +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: mode (string containing the emission mode copied into the memory map ex. 'FM' or 'NFM'; use list_valid_modes(map_file) to obtain the choices) +# 3: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: set_mem_mode('TYT_TH-9800.img', 'FM', 20) +#Example Usage: set_mem_mode('QYT_KT8900D.img', 'NFM', 20) +#Example Usage: set_mem_mode('Baofeng_UV-5R.img', 'NFM', 20) +#Example Usage: set_mem_mode('Baofeng_BF-888.img', 'NFM', 1) +#Comments: +# 1: This is written to use only the modes that are allowed by the radio model; invalid input should return an error + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(mode) is str: + print "Type mismatch: mode must be a string. You entered a '" + str(type(mode).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + if not mode in rf.valid_modes: + print 'Invalid mode detected. No changes have been made.' + else: + setup_global_vars(map_file) + mem = radio.get_memory(channel) + mem.mode = mode + write_memory(map_file, mem, channel) + ret_val = 0 + return ret_val + +def set_mem_tenc(map_file, tone, channel): +#Programs a CTCSS tone (to transmit) into a channel in the radio's memory map; see Comments below for more details +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: tone (float containing the tone in Hz to be copied into the memory map) +# 3: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: set_mem_tenc('TYT_TH-9800.img', 0, 20) +#Example Usage: set_mem_tenc('QYT_KT8900D.img', 100.0, 19) +#Example Usage: set_mem_tenc('Baofeng_UV-5R.img', 192.8, 20) +#Example Usage: set_mem_tenc('Baofeng_BF-888.img', 192.8, 16) +#Comments: +# 1: This function enables transmission of the specified CTCSS tone; it also disables tone/code squelch +# 2: If you want to transmit a CTCSS tone and use the same (or a different) tone or code for squelch, use set_mem_cross_tone instead +# 3: This has been written so that a tone of 0 will disable transmitting a CTCSS tone and it will disable tone/code squelch +# 4: If the channel had a DTCS polarity previously set, this function will resest it to 'NN' +# 5: This function catches invalid input tones/codes and reports them back with an error message + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif (not type(tone) is float) and (not type(tone) is int): + print "Type mismatch: tone must be a float or integer. You entered a '" + str(type(tone).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + setup_global_vars(map_file) + mem = radio.get_memory(channel) + if tone == 0: + mem.tmode = '' + else: + #check for invalid tone here + if not (tone in chirp_common.TONES): + print 'Invalid tone detected. No changes have been made.' + return ret_val + else: + mem.tmode = "Tone" + mem.rtone = tone + write_memory(map_file, mem, channel) + ret_val = 0 + return ret_val + +def set_mem_tsql(map_file, tone, channel): +#Programs a CTCSS tone (to open squelch) into a channel in the radio's memory map; see Comments below for more details +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: tone (float containing the tone in Hz to be copied into the memory map) +# 3: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: set_mem_tsql('TYT_TH-9800.img', 192.8, 2) +#Example Usage: set_mem_tsql('QYT_KT8900D.img', 123, 19) +#Example Usage: set_mem_tsql('Baofeng_UV-5R.img', 100.0, 1) +#Example Usage: set_mem_tsql('Baofeng_BF-888.img', 100.0, 1) +#Comments: +# 1: This function enables the use of the specified CTCSS tone for tone squelch; it also disables the transmission of a CTCSS tone +# 2: If you want to transmit a CTCSS tone and use the same (or a different) tone or code for squelch, use set_mem_cross_tone instead +# 3: This function has been written so that using tone of 0 will disable CTCSS tone squelch and it will disable transmitting a CTCSS tone +# 4: If the channel had a DTCS polarity previously set, this function will resest it to 'NN' +# 5: This function catches invalid input tones/codes and reports them back with an error message + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif (not type(tone) is float) and (not type(tone) is int): + print "Type mismatch: tone must be a float or integer. You entered a '" + str(type(tone).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + setup_global_vars(map_file) + mem = radio.get_memory(channel) + if tone == 0: + mem.tmode = '' + else: + #check for invalid tone here + if not (tone in chirp_common.TONES): + print 'Invalid tone detected. No changes have been made.' + return ret_val + else: + mem.tmode = "TSQL" + mem.ctone = tone + mem.rtone = tone + write_memory(map_file, mem, channel) + ret_val = 0 + return ret_val + +def set_mem_dtcsenc(map_file, code, channel): +#Programs a DTCS code (to transmit) into a channel in the radio's memory map; see Comments below for more details +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: code (int containing the DTCS code to be copied into the memory map) +# 3: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: set_mem_dtcsenc('QYT_KT8900D.img', 754, 19) +#Example Usage: set_mem_dtcsenc('Baofeng_UV-5R.img', 754, 1) +#Example Usage: set_mem_dtcsenc('Baofeng_BF-888.img', 754, 1) +#Comments: +# 1: This function enables transmission of the specified DTCS code; it also disables tone/code squelch +# 2: If you want to transmit a DTCS code and use the same (or a different) code or tone for squelch, use set_mem_cross_tone instead +# 3: This function catches invalid input codes and reports them back with an error message +# 4: This is written so that using a code of 0 will disable transmitting a DTCS code and it will disable tone/code squelch + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(code) is int: + print "Type mismatch: code must be a float. You entered a '" + str(type(code).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + setup_global_vars(map_file) + mem = radio.get_memory(channel) + if code == 0: + mem.tmode = '' + else: + #check for valid tones here + if not (code in chirp_common.DTCS_CODES): + print 'Invalid code detected. No changes have been made.' + return ret_val + else: + if not rf.has_cross: + #print 'This feature requires your radio to support cross-tone modes; it appears that your radio model does not.' + #return ret_val + mem.tmode = 'DTCS' + mem.dtcs = code + else: + mem.tmode = 'Cross' + mem.cross_mode = 'DTCS->' + mem.dtcs = code + write_memory(map_file, mem, channel) + ret_val = 0 + return ret_val + +def set_mem_dtcssql(map_file, code, channel): +#Programs a DTCS code (to open squelch) into a channel in the radio's memory map; see Comments below for more details +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: code (int containing the DTCS code to be copied into the memory map) +# 3: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: set_mem_dtcssql('QYT_KT8900D.img', 754, 19) +#Example Usage: set_mem_dtcssql('Baofeng_UV-5R.img', 754, 1) +#Example Usage: set_mem_dtcssql('Baofeng_BF-888.img', 754, 1) +#Comments: +# 1: This function enables the use of the specified DTCS code for code squelch; it also disables the transmission of a CTCSS tone and DTCS code +# 2: If you want to transmit a DTCS code and use the same (or a different) code or tone for squelch, use set_mem_cross_tone instead +# 3: This function catches invalid input codes and reports them back with an error +# 4: This function is written so that using code of 0 will disable transmitting a CTCSS tone / DTCS code, and it will disable tone squelch +# 5: Output from this code doesn't look like it works, but testing, and chirp GUI, confirm that it does; this is limitation of print_mem +# More information can be displayed by printing output from list_mem + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(code) is int: + print "Type mismatch: code must be a float. You entered a '" + str(type(code).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + setup_global_vars(map_file) + mem = radio.get_memory(channel) + if not rf.has_cross: + print 'This feature requires your radio to support cross-tone modes; it appears that your radio model does not.' + return ret_val + if code == 0: + mem.tmode = '' + else: + #check for invalid codes here + if not (code in chirp_common.DTCS_CODES): + print 'Invalid code detected. No changes have been made.' + else: + mem.tmode = 'Cross' + mem.cross_mode = '->DTCS' + if rf.has_rx_dtcs: + mem.rx_dtcs = code + else: + mem.dtcs = code + write_memory(map_file, mem, channel) + ret_val = 0 + return ret_val + +def set_mem_dtcspol(map_file, polarity, channel): +#Programs DTCS polarity for a given channel into the radio's memory map +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: polarity (string containing the DTCS polarity to be copied into the memory map; valid options are 'NN', 'NR', 'RN', 'RR') +# 3: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: set_mem_dtcspol('QYT_KT8900D.img', 'RR', 19) +#Example Usage: set_mem_dtcspol('Baofeng_UV-5R.img', 'RR', 1) +#Example Usage: set_mem_dtcspol('Baofeng_BF-888.img', 'RR', 1) +#Comments: +# 1: This function fails to write DTCS polarities to a memory channel when a DTCS code is absent in that channel; +# set DTCS for Tx or Rx prior to using this function. +# 2: This function will only set the polarity for Tx or Rx if a DTCS code has already been set; if a DTCS code is not set for one of them, +# this function will not set the polarity for it either; this appears to be how chirp is supposed to work. + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(polarity) is str: + print "Type mismatch: polarity must be a string. You entered a '" + str(type(polarity).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + setup_global_vars(map_file) + mem = radio.get_memory(channel) + if not polarity in rf.valid_dtcs_pols: + print polarity + ' is not a valid DTCS polarity option. No changes have been made.' + else: + mem.dtcs_polarity = polarity + write_memory(map_file, mem, channel) + ret_val = 0 + return ret_val + +def set_mem_cross_tone(map_file, tx_tone, rx_tone, channel): +#Programs CTCSS tones (for Tx and Tone Squelch) into a channel in the radio's memory map; switches the radio into cross-tone mode +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: tx_tone (float containing the tone in Hz (to be transmitted) to be copied into the memory map) +# 3: rx_tone (float containing the tone in Hz (for tone squelch) to be copied into the memory map) +# 4: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: set_mem_cross_tone('QYT_KT8900D.img', 192.8, 192.8, 19) +#Example Usage: set_mem_cross_tone('QYT_KT8900D.img', 754, 754, 19) +#Example Usage: set_mem_cross_tone('Baofeng_UV-5R.img', 192.8, 100.0, 1) +#Example Usage: set_mem_cross_tone('Baofeng_BF-888.img', 192.8, 100, 1) +#Comments: +# 1: This code has been modified to detect and differentiate CTCSS and DCS codes & select the appropriate cross-tone mode +# 2: Used this URL for reference: https://chirp.danplanet.com/projects/chirp/wiki/DevelopersToneModes +# 3: If Tx uses CTCSS and Rx uses DTCS, printed output may not show the full picture; print the output from list_mem for the full picture +# 4: Some radio models lack the capability to set different tones/codes for Tx and Rx; this function will alert you if that is the case. + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif (not type(tx_tone) is float) and (not type(tx_tone) is int): + print "Type mismatch: tx_tone must be a float or integer. You entered a '" + str(type(tx_tone).__name__) + "'" + elif (not type(rx_tone) is float) and (not type(rx_tone) is int): + print "Type mismatch: rx_tone must be a float or integer. You entered a '" + str(type(rx_tone).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + setup_global_vars(map_file) + mem = radio.get_memory(channel) + write_mem = False + if not rf.has_cross: + print 'This radio does not support cross-tone modes' + else: + mem.tmode = 'Cross' + if (tx_tone in chirp_common.TONES) and (rx_tone in chirp_common.TONES): + #Tx and Rx both use CTCSS tones + mem.cross_mode = 'Tone->Tone' + mem.rtone = tx_tone + mem.ctone = rx_tone + write_mem = True + elif (tx_tone in chirp_common.TONES) and (rx_tone in chirp_common.DTCS_CODES): + #Tx uses CTCSS and Rx uses DTCS + #Output from this code doesn't look like it works, but testing, and chirp GUI, confirm that it does + #This appears to be due to a limitation of print_mem() + mem.cross_mode = 'Tone->DTCS' + if rf.has_rx_dtcs: + mem.rx_dtcs = rx_tone + else: + mem.dtcs = rx_tone + mem.rtone = tx_tone + write_mem = True + elif (tx_tone in chirp_common.DTCS_CODES) and (rx_tone in chirp_common.TONES): + #Tx uses DTCS and Rx uses CTCSS + mem.cross_mode = 'DTCS->Tone' + if rf.has_ctone: + mem.ctone = rx_tone + else: + mem.rtone = rx_tone + mem.dtcs = tx_tone + write_mem = True + elif (tx_tone in chirp_common.DTCS_CODES) and (rx_tone in chirp_common.DTCS_CODES): + #Tx & Rx both use DTCS + mem.cross_mode = 'DTCS->DTCS' + if rf.has_rx_dtcs: + mem.rx_dtcs = rx_tone + mem.dtcs = tx_tone + write_mem = True + else: + print 'This radio does not support DTCS decoding' + elif (not tx_tone in chirp_common.TONES) and (not tx_tone in chirp_common.DTCS_CODES): + print 'tx_tone is not a valid CTCSS tone or DTCS code. No changes have been made.' + elif (not rx_tone in chirp_common.TONES) and (not rx_tone in chirp_common.DTCS_CODES): + print 'rx_tone is not a valid CTCSS tone or DTCS code. No changes have been made.' + if write_mem == True: + write_memory(map_file, mem, channel) + ret_val = 0 + return ret_val + +def set_mem_tuning_step(map_file, step, channel): +#Programs the tuning step of channel in the radio's memory map +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: step (float containing the tuning step in KHz to be copied into the memory map) +# 3: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: set_mem_tuning_step('TYT_TH-9800.img', 25.0, 20) +#Example Usage: set_mem_tuning_step('QYT_KT8900D.img', 25.0, 20) +#Comments: +# 1: This function has been modified to only accept valid tuning step values that can be obtained from list_tuning_steps; anything else throws an error +# 2: This function checks if the radio supports tuning steps and report back an error if it doesn't + ret_val = 1 + setup_global_vars(map_file) + mem = radio.get_memory(channel) + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif (not type(step) is float) and (not type(step) is int): + print "Type mismatch: step must be a float or integer. You entered a '" + str(type(step).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + elif not step in rf.valid_tuning_steps: + print 'step is not a valid tuning step option. No changes have been made.' + elif rf.has_tuning_step == False: + print 'This radio does not store tuning steps in radio memory channels. No changes have been made.' + else: + mem.tuning_step = step + write_memory(map_file, mem, channel) + ret_val = 0 + return ret_val + +def set_mem_power(map_file, power, channel): +#Programs the power level (in dBm) of channel in the radio's memory map; use list_power_levels to find valid values to use +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: power (int containing the power in dBm to be copied into the memory map) +# 3: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: set_mem_power('TYT_TH-9800.img', 43, 20) +#Example Usage: set_mem_power('QYT_KT8900D.img', 43, 20) +#Example Usage: set_mem_power('Baofeng_UV-5R.img', 30, 20) +#Example Usage: set_mem_power('Baofeng_BF-888.img', 36, 1) +#Comments: +# 1: This function has been modified to only accept valid power level values that can be obtained from list_power_levels; anything else throws an error + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(power) is int: + print "Type mismatch: power must be an integer. You entered a '" + str(type(power).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + setup_global_vars(map_file) + mem = radio.get_memory(channel) + if not power in rf.valid_power_levels: + print str(power) + ' is not a power level option; use "print_power_levels(map_file)" to display valid options.' + else: + mem.power = power + write_memory(map_file, mem, channel) + ret_val = 0 + return ret_val + +def set_mem_skip(map_file, skip, channel): +#Programs the scan skip preference of channel in the radio's memory map; valid 'skip' options are 'S' (skip this channel) and 'P' (channel is a priority) +#Required arguments: +# 1: map_file (string containing the name of the memory map file to be read ex. 'QYT_KT8900D.img') +# 2: skip (string (one character) containing either '', 'S', or 'P') +# 3: channel (integer corresponding to the channel whose contents will be edited) +#Example Usage: set_mem_skip('TYT_TH-9800.img', 'S', 20) +#Example Usage: set_mem_skip('QYT_KT8900D.img', 'S', 20) +#Comments: +# 1: There does not appear to be a way to use Chirp libraries to determine if a radio supports this feature without digging into individual drivers. +# If your radio lacks of support for this feature, it does not appear to result in any fatal errors. + ret_val = 1 + if not type(map_file) is str: + print "Type mismatch: map_file must be a string. You entered a '" + str(type(map_file).__name__) + "'" + elif not type(skip) is str: + print "Type mismatch: skip must be a string. You entered a '" + str(type(skip).__name__) + "'" + elif not type(channel) is int: + print "Type mismatch: channel must be an integer. You entered a '" + str(type(channel).__name__) + "'" + else: + setup_global_vars(map_file) + mem = radio.get_memory(channel) + if not skip in rf.valid_skips: + print str(skip) + " is not a valid option; enter one of the following: " + str(rf.valid_skips) + else: + mem.skip = skip + write_memory(map_file, mem, channel) + ret_val = 0 + return ret_val +

2 1

[chirp_devel] FT-450D Test Errors
by Rick DeWitt 31 May '18

31 May '18

OK, I am having a dilemma.. I have the new Yaesu FT-450D driver working 99.876% perfectly (+/- 10%). My problem is that it fails run_tests with two very specific issues- 1) The FT-450D uses a secondary 2-bit value to modify the base 'mode' for data modes. This causes the Brute Force test to fail the compare_mem test, since it doesn't know about that modifier. 2) The FT-450D supports a Memory Group on/off option that changes the memory display format from simple 0-500 channels, to 10 50-channel groups (Ex: MEM-02-01, for number 51). Since the radio does not store this info in any form of bank memory, I have chosen to use the Comment field to show the group index when that option is enabled. Therefore this causes run_tests Edges and Brute Force tests to fail compare_mem when it sets a blank channel name and I overwrite it. Since the driver works now for all upload and download configurations and modes, should I care that it fails these tests? -- Rick DeWitt AA0RD Sequim, Washington, USA 360-681-3494

2 2