[chirp_users] chirp_users Digest, Vol 109, Issue 2

Jeff wireless3.14159 at gmail.com
Wed Jan 3 16:44:19 PST 2018


I meant expert-level advice. Sheesh.

On January 3, 2018 7:29:59 AM MST, Jeff <wireless3.14159 at gmail.com> wrote:
>Dave, I hereby nominate your reply for the 2018 Chirp list hall of
>fame. Expect-level advice, yet lighthearted and fun to read. Two thumbs
>up with five stars on top. 
>
>On January 3, 2018 4:16:41 AM MST, Dave B <g8kbv at uku.co.uk> wrote:
>>Hi.
>>
>>Other than for software that just isn't available for anything other
>>than Windows, there is no reason whatsoever to try to use WINE to run
>>Chirp under Linux.
>>
>>Just go to:-  https://chirp.danplanet.com/projects/chirp/wiki/Download
>>
>>And follow the instructions how to get the version you need for your
>>OS.
>>
>>There is even a "Live CD" (bootable self contained system) version!
>>
>>As well as the ability to run it directly from a "tarball" file once
>>the
>>contents are extracted.
>>
>>https://chirp.danplanet.com/projects/chirp/wiki/Running_Under_Linux
>>
>>I do have some Windows specific programs that I need to use, that do
>>run
>>well under WINE, but sadly the DMR codeplug software from Motorola
>will
>>not install, as the installer needs .NET version whatever, and the
>Mono
>>equivalent tools are not compatible.
>>
>>All my other radio programming and configuring needs are happily done
>>via Chirp running natively under Linux.
>>
>>As to the serial port issue, it's a "symbolic link" that you create,
>>that in effect redirects references to (for example) COM1: to
>>/dev/ttyUSB0   Job done.   As you say, instructions are available how
>>to
>>do that from many sources.
>>
>>I would also dispute the assumption re the probably low importance of
>>the handshake lines.  Many radio's use them to enter programming mode,
>>enable some esoteric mode, and/or exit from such modes.
>>
>>It is best to use the version of Chirp, that is natively configured
>for
>>your OS, rather than try to bludgeon it into working via an
>abstraction
>>layer, that can itself impose "other feature" you may not want..
>>
>>73.
>>
>>Dave G0WBX.
>>
>>
>>
>>On 02/01/18 20:00, chirp_users-request at intrepid.danplanet.com wrote:
>>> From: Tom Consodine ND5Y <nd5y at yahoo.com>
>>> Subject: [chirp_users] USB serial ports and Linux/WINE
>>> To: chirp_users at intrepid.danplanet.com
>>> Message-ID: <7d46aaec-b155-f3f6-6697-f339bb204881 at yahoo.com>
>>> Content-Type: text/plain; charset=utf-8; format=flowed
>>>
>>> I have no problems using USB serial ports with Windows software
>>running 
>>> on Linux/WINE. One of the reasons I switched to Linux was one USB
>>cable 
>>> I have would work on Windows 7 but not on Windows 10.
>>>
>>> You have to configure the serial port permissions in Linux. There
>are
>>
>>> instructions for doing that on the Chirp web site.
>>>
>>> If you are using WINE 2.8 or later you might have to configure the
>>port 
>>> settings in WINE or manually make a "registry" key. There are 
>>> instructions for doing that on their web site at
>>>
>>>
>>https://wiki.winehq.org/index.php?title=Wine_User%27s_Guide&oldid=2519#Serial_and_Parallel_Ports
>>>
>>> Versions before that only require making a link in the wine folder
>to
>>
>>> the port.
>>>
>>> Older versions of WINE before about 1.7 don't support all the RS-232
>
>>> lines. This probably isn't an issue for radio programming cables
>that
>>
>>> only use TXD and RXD lines but it is if you need the RTS, CTS, DTR,
>>DSR 
>>> lines to work properly.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180104/b2e01df4/attachment-0002.html 


More information about the chirp_users mailing list