- Users - lists.chirpmyradio.com

Re: Retevis H777 Unable to Connect
by Joshua Morin 17 Jan '25

17 Jan '25

Hi Jim, Saw the latest build includes support for H777H_FRS model. Tried it this morning and it does not work. Windows machine gives error "No response from radio". Confirmed I am still able to read/write with OEM software. Josh

1 0

Fw: Uv25 programming
by Gary Chesshir 17 Jan '25

17 Jan '25

Sent from my T-Mobile 5G Device Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Gary Chesshir <gary_chesshir(a)hotmail.com> Sent: Friday, January 17, 2025 3:21:26 AM To: Gary Chesshir <gary_chesshir(a)hotmail.com> Subject: Fw: Uv25 programming Sent from my T-Mobile 5G Device Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: postmaster(a)outlook.com <postmaster(a)outlook.com> Sent: Friday, January 17, 2025 3:14:06 AM To: users(a)listschirpmyradio.com <users(a)listschirpmyradio.com> Subject: Undeliverable: Uv25 programming Delivery has failed to these recipients or groups: users(a)listschirpmyradio.com (users(a)listschirpmyradio.com)<mailto:users@listschirpmyradio.com> Your message couldn't be delivered. The Domain Name System (DNS) reported that the recipient's domain does not exist. Contact the recipient by some other means (by phone, for example) and ask them to tell their email admin that it appears that their domain isn't properly registered at their domain registrar. Give them the error details shown below. It's likely that the recipient's email admin is the only one who can fix this problem. For more information and tips to fix this issue see this article: https://go.microsoft.com/fwlink/?LinkId=389361. Diagnostic information for administrators: Generating server: MN2PR11MB4550.namprd11.prod.outlook.com users(a)listschirpmyradio.com Remote server returned '550 5.4.310 DNS domain listschirpmyradio.com does not exist [Message=InfoDomainNonexistent] [LastAttemptedServerName=listschirpmyradio.com] [MW2NAM12FT088.eop-nam12.prod.protection.outlook.com 2025-01-17T13:14:06.782Z 08DD36B93286D12E]' Original message headers: ARC-Seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=HQ9cEvIATPlFFCwy/qrX2BL4oOzVLTPO2dJCgkHeAVY4xWcq2e+vdLT7N2dgUnVUqtpNESN5o3UX/56z1eSgkIj/mPSCoosTPyEPVH1Dq4Pg/Be6GUEYSuOvNU5ggofplObuRxYppodyOPGqB2TWf7JU4a7HUkyaY1Yr5xrNnF3SLNOA52xK+t2CyaUnsCMyhXTkURpawbsHYvRC/QsZkOVK2ZknmuSpXr0H5d6OMnFswVTUY6S/RsJD1vFtlFT1c0LJbnPnRAVH59MHAqStoE17mEDe6SxIQRVddC6RYp2hPQR80e8W5tpoIS/eKMV5Vu3hKyAwdNqg7A6diMGisA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=6qLNscIihaI5QA5AuENHV8j1RTNEU9AnzWAPQfhPCYA=; b=Vwg6DDCLH7PSYHal3nJEAlm/yDOQfSGzEkQ0lWb2+fRoAAwbXk5UJ6HfVNg6JvkrOqcFOkDMbSs2Jd1pIlqd7z+fWU6gT5aCM5Zd9KTd38VnbHS8GBuG7zSSYtn26sHQHYpG944y6mK8ymoZSs+uI66bybBRIEW4jrBVYVMgFUfi7toYVbCR/ggjdY2qp44RHS/F8YlFVkpsm8A0r58cqhK6G7/n/+TDET6K7BGKW524ugbLVO+1DQlLnqWt/6g2ZP3Gukjm8RKq52KMtI6RQZYBvziaQ05O17p4qg2SqkqR5H7jrLnqGItErUYzQoLVIJg2R1wk3nhejgGcXcluog== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6qLNscIihaI5QA5AuENHV8j1RTNEU9AnzWAPQfhPCYA=; b=u5mOcD3RvfAYnLiceWFYKaYklVtF7DPY3L/Sc8Erl+LBXFNcCiQIXoo6beIWeiJsuFiiloPQdMGRp6oHjCBtlj6nPu/Aok05rxyaS2bu3O0RtYpReUaJoxP9YYXviOLEmzkBqKgBC8oqBmeEkltGy4QBRishAWiMbRXkJkZzZZrLkaBbz1rDO/YJZkU/NxJhd7jdXzQ7V+bizBkCekEl16UdaA/i1CT8LNkBWoFc9COLeRk4ZOmwczDgVMQO2aAvGTkkk5R8mF/6ZrftNtHyxIJ00gxWohoptcOhuJUqW84gynEQwIkHG2qQy4w7BbbI6lmekB+JgivtSA/nmCiFDw== Received: from MN0PR11MB6135.namprd11.prod.outlook.com (2603:10b6:208:3c9::9) by MN2PR11MB4550.namprd11.prod.outlook.com (2603:10b6:208:267::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.8356.17; Fri, 17 Jan 2025 13:14:05 +0000 Received: from MN0PR11MB6135.namprd11.prod.outlook.com ([fe80::3225:d4ad:74a:6d7a]) by MN0PR11MB6135.namprd11.prod.outlook.com ([fe80::3225:d4ad:74a:6d7a%3]) with mapi id 15.20.8356.010; Fri, 17 Jan 2025 13:14:05 +0000 From: Gary Chesshir <gary_chesshir(a)hotmail.com> To: "users(a)listschirpmyradio.com" <users(a)listschirpmyradio.com> Subject: Uv25 programming Thread-Topic: Uv25 programming Thread-Index: AQHbaODHxWK7ClOxSEGPqDiwQC1PIA== Date: Fri, 17 Jan 2025 13:14:05 +0000 Message-ID: <MN0PR11MB6135AFE7A4D8255F649C0C17801B2(a)MN0PR11MB6135.namprd11.prod.outlook.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-reactions: allow x-ms-exchange-messagesentrepresentingtype: 1 x-ms-publictraffictype: Email x-ms-traffictypediagnostic: MN0PR11MB6135:EE_|MN2PR11MB4550:EE_ x-ms-office365-filtering-correlation-id: a3cc224b-de2a-4458-e979-08dd36f8d1f8 x-microsoft-antispam: BCL:0;ARA:14566002|9400799030|461199028|14030799003|15080799006|8062599003|12050799009|7092599003|8060799006|19110799003|102099032|1602099012|440099028|10035399004|3412199025|4302099013; x-microsoft-antispam-message-info: =?us-ascii?Q?oHLpmA2/AU1CnZlNITaReAUuONWOPMA0PFNuF5nOUrsmF6gmjMMEkXgZt+mt?= =?us-ascii?Q?KG/NQhAX3S4s7N6R/N13SodaLn3nXdixEmP9QgrayWcuxD2Kpen++5M+siCE?= =?us-ascii?Q?1C27dxx4kVONb8QIj9NFh+Rp59PLvZb5dXqbIihb4b9vII1e8i4sqHKZq25u?= =?us-ascii?Q?sfJ0lzaCCuw3I1nitpExAq8mB5xgIemg5ieuCeg5pVPhexorVqeaoPunRa0P?= =?us-ascii?Q?v4LaJ7EYDKQ6eSbOQ2rV6JjGtUZ6UPWDrtz8ic3cBG+90d5/dzIZgW7oOUII?= =?us-ascii?Q?1ocRdNxUNwpizLMtVZf0npJ31vHD5g1jml8GXOp/b/aDdb+miq01Tu7OOS6Q?= =?us-ascii?Q?ZyeeTUUHj3f51Gvmpv2T3AWJO8K0YOsXDhO28elEXu5J+AZTJSFJOxjF6MPz?= =?us-ascii?Q?AFqGlO8MYMJkLzIYTYn1G+Nh/cYpzMfQy/CWFVWPaDwoZiZKnAbhSHuzW5nJ?= =?us-ascii?Q?JQxUtuLb5JZEETTssF71CDtvTYuzCkO98WO6bLJ1hGzB3C+hJZ4ejb59ebQ9?= =?us-ascii?Q?tjsdqM61zY/CytTd8Df81bzEpSPIZc8kT1EmHYbDT8Ut5TZ0RBqhJuEJTucm?= =?us-ascii?Q?T0HlTWs9Ty2pB3nD6g2sK+Mt5UVydwtgWqSPVsGydjizioC+CBHoa9cAfAlU?= =?us-ascii?Q?URcHy4VeNj7OlLfEvszrOpcWvkeQv614KnStNDWCcH1Z0JXZZsJTLQ3+Yt0h?= =?us-ascii?Q?PoTluW5IgQPwnXl9c/Rxg68NOHpU0mk8awbKcrNQUlcf3gqUA9BeS7FNj96r?= =?us-ascii?Q?fTDgoBMc+R+MV5olcAcDBX7QWcB9QY00e6TqSA4TpO8QKe31NWgqiOZpAATi?= =?us-ascii?Q?7C/lGTzY/xYtxu50nzxnSRjMuV+dQ9sAiMN+Gs2Qf0DhPVqgWJNZi42J73Qs?= =?us-ascii?Q?37EW8FjX1zhastE0W74FC4HtizZBNYHc/pJJdO5OLoH0Q/QGTILlesLpKSo8?= =?us-ascii?Q?Av3YmaMzcHvmrxpp2LTLP3W89eJqYymq6WJdUHONxH4dkD+HvuzC/fJFIy3t?= =?us-ascii?Q?taAsPUqgb0+nf32M6D8tnUDcJCTXp53kO8nkG6fcAjAd7ju6/ea8uzvHuXrJ?= =?us-ascii?Q?7WhiwMhZSfVYZ7z+DY76mw76qvd6JQ2KV6NykFnl6X7SqDNxMGew6V8tN21j?= =?us-ascii?Q?Nh8nxZX6GD+yknSkzgcM4OKte7MkB0aW41Nb3UkDXl5wuVA8KZegevlUu8bg?= =?us-ascii?Q?DM9OBuxagCLtQUCE4A05+qXCtcIW+ivqmT6UUJqfu3cMkhLsp9ojl76gxtY+?= =?us-ascii?Q?OuCgWMEdC5/jGAQCtQ5UP+lli6hB+dqXSnoBDdT8Zw=3D=3D?= x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?nToopkVDDdXjZHbomWRDbtcIJPh/9oFKoKo0+D4s4KcwAb+/Yd1anKqqv0QV?= =?us-ascii?Q?du5dy7IBILONOpWzRsGMqfMMTcACOHzKw90cb5twibBXS154D48AXW+LRAco?= =?us-ascii?Q?jzBoy3EhMzRGmrjfNcHjaWbM8Qt5aRcdYs8QKyiTQIy55aXmBSWP83EA4RkB?= =?us-ascii?Q?GFon0dWiQm/FGMLSpauge151qpXYOX7dI5fuo47ufJji+WnQa6QVltQGKKHH?= =?us-ascii?Q?4+3onsFA+s0yGpylAvQKuMixv2I9xbhaB/nKsOmf5s0CgymugUN5rm0nbuL6?= =?us-ascii?Q?kTD8h6a0Kp8F0GvGPf+yQhfXxoGfeqpqTEqQbM1UzvNwYBaVhwZcFUsmR0sn?= =?us-ascii?Q?xLThuNhoB8oYh3WEjpTjT6gr3tCMhNIrqBvK502KiEEcVQeHkyBTTU/JkRbm?= =?us-ascii?Q?Kr8XXmiqWor0CddpUPHXrJjsvb+6wzy4KwW4PcBOo1kNtrf+SSEs5LLJSSRh?= =?us-ascii?Q?kmOOyvRnqEtnM8hZb2tGUD/xaQBY25KOOicZkJe922LFMEgB4DLlL8DYBifa?= =?us-ascii?Q?xLCMWIJiZpOVR6ddpCy7ioURLGrHaQ6sIadCKnEzt7DxaxtNDONkuhigvU/1?= =?us-ascii?Q?pYQNf9+l+FMBDEa5vaj4on07lRB+Cwz5cz2Q0enltLqq+DmYuEL5pJ6exira?= =?us-ascii?Q?w4TcPn4yoGjPfTnnG3nWN3+FQpQQZr8h6MZmhWsWgKSU8P1Ugjy9XTi1B/+a?= =?us-ascii?Q?LH7CQyHhK8Sct6aSax+7S17TFJY6gjVBz1oavKbIVBv0VEeJtyTMsQ3wIUfB?= =?us-ascii?Q?heTuSi5fs45vDGXwZDxEaUu/YSedUDbfGdJSdtwuFYOke8BJYNSVHr6A4gnn?= =?us-ascii?Q?AUmw/cojVr3vo/f1Q8BhVl2Ls6Piksumq/7ZsGpioy67wWNp0hkhgLOg6StM?= =?us-ascii?Q?jH4dNXWe506CccDSUTO2Ra6e3Rmu+Hw1tRyBQESHk0w7Ow+PM6D1cT2lK7hQ?= =?us-ascii?Q?92ZHZ+cV/irYk84NJo6YFpTICP7HbMeNBU9iEyqKMEj2ZwDB7Hk7zEHTOWpT?= =?us-ascii?Q?CrTIMWg4LPMiiJ9MDCephG+G7PiXRTiZF5qf9b1oUOuxHozjkq5G2YG0lrBZ?= =?us-ascii?Q?C0e2Y4mqY7qAeQxC8OHXTaDH062xFKoGeAXUITmZy8y9PjZw5X6UZvmuJaZP?= =?us-ascii?Q?QIwmzwCGyUmn5mXZmE+9Z3v2LWPe4NX8gMc40zsO7eTumGbvstVg9oPCxjaz?= =?us-ascii?Q?YHCDkNBOW1eYq0VuCYnmMuPKG178VH6mWAcsmI+Bpa1m6HPcf4NxxabJtQR/?= =?us-ascii?Q?hSoKJyQ1PqDHJFAA/qZD?= Content-Type: multipart/alternative; boundary="_000_MN0PR11MB6135AFE7A4D8255F649C0C17801B2MN0PR11MB6135namp_" MIME-Version: 1.0 X-OriginatorOrg: sct-15-20-7719-20-msonline-outlook-d1079.templateTenant X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: MN0PR11MB6135.namprd11.prod.outlook.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-CrossTenant-Network-Message-Id: a3cc224b-de2a-4458-e979-08dd36f8d1f8 X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Jan 2025 13:14:05.8571 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000 X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4550

1 0

New chirp-next build
by donotreply＠chirpmyradio.com 17 Jan '25

17 Jan '25

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since the last build and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20250117 A list of changes since the last build are here: c97ccc75 Add diff-between-tabs developer function 5b178d50 tk8180: Fix tuning step encoding 229c8218 tk280: Fix tuning step encoding 497a9f44 tk280: Fix supporting duplex=split abf21c0c Improve keyboard navigation from setting group to editor fa75ee23 tk280: Fix saving radio version in metadata ed01c80c tk280: Improve performance by caching mappings a0339278 tk280: Fix battery save setting 4d9ba57e tk280: Fix memory format deprecated behaviors 2aedd6d1 Fix memory dragging off-by-N rows issue 3075cd43 tk280: Implement OST settings 0863e4e3 Add Kenwood TK-280,380 support d47b210e Improved keyboard navigation for settings editor 3ea12b3b Add MemSetting to streamline set_settings() in many cases c2ff1b04 Improve reporting of settings failures in tests a7b805ab radtel_t18: add Retevis H777H PMR version - fixes #11775 79fefdcb radtel_t18.py: add support for Radtel H777H FRS version - related to #11775 fc94f148 uv17pro: Fix exposing static banks on some models dc48c8a1 snapcraft: Install wheel instead of tarball 837aef0d Improve keyboard navigation and editing Issues addressed in this build: [Bug 11642] zone/bank assignments [Bug 4935] Radio not seen in Linux Mint [New Model 11775] Add support for Retevis H777H series radios --

1 0

Alternate Programmng Methods
by ebills＠ncsmiths.com 14 Jan '25

14 Jan '25

I'm playing around with a TIDradioH3 which has both bluetooth programming and a dedicated usbc connection for programming. Curious if Chirp has usb to usb programming capability or bluetooth capability. Dick W4RS

5 4

Re: Trouble with Linux USB port (Dave B)
by Dave B 13 Jan '25

13 Jan '25

Hi again. You need to... sudo apt purge brltty If you've not already done so in the past... "brltty" is (I think) a Braile input device, for partially sighted users, often installed and active by default. It would appear the devices probably use a CH340 USB/Serial bridge chipset, hence the confusion. Also, if you've not already made yourself a member of the "dialout group"... sudo adduser $USER dialout. That will add "you" (the logged in user) to the "dialout" group, giving you permission to use serial ports, among other things. ("$USER" is a system variable that holds the logged in username.) Then, at least logout and log back in again for that change to take effect. If you wish, do a full restart just to be sure that brltty has gone. There is also often another background daemon "modem manager" that can cause similar issues. That can be disabled too, plenty on the web about that. Hope the above helps. Dave B.

1 0

Re: Trouble with Linux USB port
by Dave B 13 Jan '25

13 Jan '25

Hi. With recent Linux's, you can use... dmesg -WH in a command line session... Where nothing appears to happen but if you plug something in, you'll see what the OS does with it. If -WH errors, try -wH.. An initial splurge of info, then silence, untill you change what's plugged in. (Ctrl+C exits the dmesg thing, Ctrl+D will close the terminal session.) If you have a FTDI based adapter, you can create a udev rule, so it always shows up under a more easily recognizable device name, such as... /dev/ttyMyAdapter! Or other creative name, regardless of were you connect it. Lesser chipsets without a unique serial number, you can do similar tricks, but you have to decypher the "path" to the device, and as I've recently found, with some OS/PC Hardware combinations, that can change at each boot! Most application software these days will accept that sort of thing, CHIRP used to, but I've yet to try the latest incarnation. 73. Dave G0WBX.

3 4

Re: Trouble with Linux USB port
by Dave Baxter 13 Jan '25

13 Jan '25

Disable and remove BRLTTY. It's a not uncommon issue for that to mess with serial ports. Plenty online about that, and other pre-installed software that comes with the OS's these days. It doesn't affect many, but when it does, mayhem ensues! Hope that helps. Dave.

1 0

Re: Trouble with Linux USB port
by Gregory Beyer 13 Jan '25

13 Jan '25

> Yes I did follow the instructions, as stated in my OP. There is no > difference between running ls /dev/tty* before and after cable > plugin. No new device is added. I have no ttyACM device. Ran usermod > command, then rebooted. No joy. running ls against all of /dev, I do > find a usb directory (not ttyUSB) -- IDK if it relates to this problem. > > ls -la usb > total 0 > drwxr-xr-x 2 root root 60 Jan 12 12:03 . > drwxr-xr-x 21 root root 4880 Jan 12 12:15 .. > crw------- 1 root root 180, 0 Jan 12 12:04 hiddev0 > > "In some cases it may be necessary to enter the device (port) name > manually before chirp can see it." How would I do that? > > Thanks, > *________________________* > > *Greg Beyer > greg(a)beyerusa.net* > > > KQ4AVZ > > > ------------------------------------------------------------------------ > *From:* Jeffrey Vian via Users <users(a)lists.chirpmyradio.com> > *Sent:* Sunday, January 12, 2025 at 12:39 AM > *To:* CHIRP users list > *Cc:* Jeffrey Vian > *Subject:* [users] Re: Trouble with Linux USB port > >> Did you follow the instructions on this page? Especially steps 1 and 2. >> >> Are you certain that the port is getting the name you expected?. >> >> It may get a name ttyUSB0 or it may get something like ttyACM0. On >> some of >> my radios it gets USB and on others it gets ACM. I think that is >> related >> to the specific chipset in the programming cable (or maybe the linux >> distro >> used could be a factor) >> You may be able to run `ls /dev/tty*` before plugging in the cable and >> again after plugging it in to identify the name it actually is assigned. >> >> In some cases it may be necessary to enter the device (port) name >> manually >> before chirp can see it. >> It also may be necessary to add your user to the `dialout` group for >> access >> to the device. If you have not already done so the command `sudo >> usermod >> -a -G dialout <username>` should add the user to that group. Then a >> logout >> and back in will be required before the group assignment becomes active. >> >> Jeff >> KI7GJG >> >> >> >> On Sat, Jan 11, 2025 at 10:23 PM Gregory Beyer via Users < >> users(a)lists.chirpmyradio.com> wrote: >> >>> Hi, I'm having trouble with CHIRP not recognizing any USB ports. I'm >>> running LinuxMint 21, Mate. I've installed >>> chirp-20250110-py3-none-any.whl per the instructions at >>> /wiki/ChirpOnLinux. Other than needing to install python3-yattag, it >>> went smoothly. Love how fast chirp loads over the flatpak I used to >>> use >>> a long time ago! >>> >>> When I run chirp, and scroll through the ports, there are no USB ports >>> listed. Tried "Help me" and got "Unable to determine a port for your >>> cable. Check your drivers and connections." Under Mate System >>> Reports/System Information, I see the cable listed under USB hub 1: >>> Device-2: 1-2:40 info: QinHeng CH340 serial converter type: <vendor >>> specific> driver: usbfs rev: 1.1 speed: 12 Mb/s chip-ID: 1a86:7523. >>> I plugged my cable into a different USB port, cable appears under hub 2 >>> in the report. So, my OS is recognizing the cable, on either USB >>> port, but CHIRP does not. >>> >>> Even tho I'm not getting a permission denied error, I tried "sudo >>> usermod -a -G $(stat -c %G /dev/ttyUSB0) $USER" anyway, and got "stat: >>> cannot statx '/dev/ttyUSB0': No such file or directory." Same error >>> when I tried command for USB1 and USB2. >>> >>> Any suggestions on how I can resolve? >>> >>> Thanks much, >>> >>> *________________________* >>> >>> *Greg Beyer >>> greg(a)beyerusa.net* >>> >>> >>> KQ4AVZ >>> _______________________________________________ >>> Users mailing list >>> users(a)lists.chirpmyradio.com >>> https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com >>> >>> To unsubscribe, send an email to users-leave(a)lists.chirpmyradio.com >>> To report this email as off-topic, please email >>> users-owner(a)lists.chirpmyradio.com >>> List archives: >>> https://lists.chirpmyradio.com/hyperkitty/list/users@lists.chirpmyradio.com/ >>> >> _______________________________________________ >> Users mailing list >> users(a)lists.chirpmyradio.com >> https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com >> >> To unsubscribe, send an email to users-leave(a)lists.chirpmyradio.com >> To report this email as off-topic, please email >> users-owner(a)lists.chirpmyradio.com >> List archives: >> https://lists.chirpmyradio.com/hyperkitty/list/users@lists.chirpmyradio.com/

2 1

Trouble with Linux USB port
by Gregory Beyer 12 Jan '25

12 Jan '25

Hi, I'm having trouble with CHIRP not recognizing any USB ports. I'm running LinuxMint 21, Mate. I've installed chirp-20250110-py3-none-any.whl per the instructions at /wiki/ChirpOnLinux. Other than needing to install python3-yattag, it went smoothly. Love how fast chirp loads over the flatpak I used to use a long time ago! When I run chirp, and scroll through the ports, there are no USB ports listed. Tried "Help me" and got "Unable to determine a port for your cable. Check your drivers and connections." Under Mate System Reports/System Information, I see the cable listed under USB hub 1: Device-2: 1-2:40 info: QinHeng CH340 serial converter type: <vendor specific> driver: usbfs rev: 1.1 speed: 12 Mb/s chip-ID: 1a86:7523. I plugged my cable into a different USB port, cable appears under hub 2 in the report. So, my OS is recognizing the cable, on either USB port, but CHIRP does not. Even tho I'm not getting a permission denied error, I tried "sudo usermod -a -G $(stat -c %G /dev/ttyUSB0) $USER" anyway, and got "stat: cannot statx '/dev/ttyUSB0': No such file or directory." Same error when I tried command for USB1 and USB2. Any suggestions on how I can resolve? Thanks much, *________________________* *Greg Beyer greg(a)beyerusa.net* KQ4AVZ

4 4

Retevis H777 Unable to Connect
by jmorin06＠gmail.com 11 Jan '25

11 Jan '25

Greetings! New CHIRP user here. I ordered (4) Retevis H777 radios and am trying to program them. Two radios are the "newer" version (with usb-c charging) while the other two are an "older" version. I am able to connect, download, and upload to the older version radios, but not the newer version radios. When I try, I get the error message "Error communicating with radio, no response from radio". Tried with all three of the H777 profiles (H777, H777 Plus, H777S). The first two profiles give the same error message already described. The third is a different error message "The radio did not accept program mode after five tries...". Radio is on, tried different computers (Mac and windows) also made sure I was using latest CHIRP build (10-Jan-2025). Nothing works... I am able to program with the Retevis CPS. The "newer" version does have some different features so maybe it needs a new profile/model in CHIRP? Before I submit a bug/new model request, I wanted to check here to see if anyone has advice or experience working with this "newer" H777 model. Thanks!

2 2