{"action":"opened","issue":{"url":"https://api.github.com/repos/DaleFarnsworth/codeplug/issues/22","repository_url":"https://api.github.com/repos/DaleFarnsworth/codeplug","labels_url":"https://api.github.com/repos/DaleFarnsworth/codeplug/issues/22/labels{/name}","comments_url":"https://api.github.com/repos/DaleFarnsworth/codeplug/issues/22/comments","events_url":"https://api.github.com/repos/DaleFarnsworth/codeplug/issues/22/events","html_url":"https://github.com/DaleFarnsworth/codeplug/issues/22","id":395689440,"node_id":"MDU6SXNzdWUzOTU2ODk0NDA=","number":22,"title":"add support for full range UHF on md380/390","user":{"login":"ZeroChaos-","id":1670905,"node_id":"MDQ6VXNlcjE2NzA5MDU=","avatar_url":"https://avatars2.githubusercontent.com/u/1670905?v=4","gravatar_id":"","url":"https://api.github.com/users/ZeroChaos-","html_url":"https://github.com/ZeroChaos-","followers_url":"https://api.github.com/users/ZeroChaos-/followers","following_url":"https://api.github.com/users/ZeroChaos-/following{/other_user}","gists_url":"https://api.github.com/users/ZeroChaos-/gists{/gist_id}","starred_url":"https://api.github.com/users/ZeroChaos-/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ZeroChaos-/subscriptions","organizations_url":"https://api.github.com/users/ZeroChaos-/orgs","repos_url":"https://api.github.com/users/ZeroChaos-/repos","events_url":"https://api.github.com/users/ZeroChaos-/events{/privacy}","received_events_url":"https://api.github.com/users/ZeroChaos-/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-01-03T19:06:10Z","updated_at":"2019-01-03T19:06:10Z","closed_at":null,"author_association":"NONE","body":"I have tested this on md380/md390.\r\n\r\nRecently, I randomly opened up settings.ini on the windows CPS and came across the following:\r\n```\r\n[FreqRange]\r\nfreq0=[136-174MHz]\r\ndata0=60134017\r\nfreq1=[350-400MHz]\r\ndata1=00350040\r\nfreq2=[400-480MHz]\r\ndata2=00400048\r\n```\r\n\r\nI found it interesting that it seemed to be encoding the limits of the radio, and thought it might be fun to open it up.  So I added: \r\n```\r\nfreq3=[350-520MHz]\r\ndata3=00350052\r\n```\r\n\r\nThen I edited a codeplug to change that key value in the header to match my newly opened setting and pushed it to the radio.  After this, I was able to program in all the frequencies I wanted with no issues (I wanted to use my hotspot on 433 and listen to the public safety on 49X).\r\n\r\nI believe this should be incorporated into your software in the following two ways:\r\n\r\n1.) When creating a new empty code plug (if supported), this full range should be offered as an option; with a pop-up warning that it will make it incompatible with unmodified windows cps.\r\n2.) Since there is no need to clear the radio to widen the supported frequencies, there should be an option to switch from any/all of the currently offered frequency ranges to this one, again with a pop-up warning that doing so will be incompatible with unmodified windows cps.\r\n\r\nYou could go futher, and allow user specified ranges if desired.  I didn't try to set the radio out of this range, as that's all it's been calibrated for, and I don't think it would be wise to do so, but you could allow a user to set any range inside 350-520, like 351-412, for whatever reason."}}
{"actor":{"display_login":"ZeroChaos-"}}