Hi.

The images in that pdf (DE-19 Manjaro.pdf) are very indistinct, making it very difficult to make out any detail.

Some Linux OS's have dmesg -WH available.? That, as well as waiting for something to happen, it avoids splurging the past system log entries to the screen due to the upper case 'W'.
(The upper case 'H' also makes for a more human readable output, on later Debian based OS's at least.)

Or you can just ls /dev/tty* before and after you plug the lead into the computer, and see what new port appears after you plugged the lead in.

Debian types can also use sudo adduser $USER dialout? to add themselves (as the 'logged in' user) to the Dialout group.? (There seems to be way too many ways to perform that task!)


Also, use a FTDI based USB-Serial bridge lead for the radio (or anything else) and you can reliably use "udev rules" (There is lots of info on the web about that) based on the 'unique serial number' (a uniqe alpha numeric string, that FTDI conveniently use) so your radio, rotator, PA or whatever else, is 100% reliably detected and assigned a symlink such as /dev/ttyDE19 Making things very much easier to plug together without stress or confusion, especially if you have more than one USB-Serial based gadget in use!

To my knowledge so far, no other USB to Serial chipset maker provides that most valuable detail.? Some can interface with an EEPROM to do the same, but that is not usually retrofitable to pre-built cables.

The problem with all the other makers, and USB in general, is that at any time the OS, windows or 'nix, re-enumerates things due to a change in the connected architecture or a restart, some or already connected devices can be re-assigned a different /tty/USBx value! (An all too common problem when RF gets into and corrupts the USB subsystem at either end of the cable, and you have more than one such USB-Serial type device in use.)

This is what I use for one such udev rule:-
# CI-V cable for IC-R9000 using a genuine FTDI based cable.
SUBSYSTEM=="tty", ATTRS{serial}=="A10NDGR5", SYMLINK+="ttyICR9k"

That lives in:-?? /lib/udev/rules.d/99-shack.rules? (A new rule file, specific to my shack PC, running a Debian based OS.)

(The specific cable also has a hand written label at the USB end, to remind me what is on the other end!)

You ideally need to be root to add/edit that file, sudo might work to give temp access to your editor, but take care either way, mistakes can break things...? (Better to add a new file than edit an existing, as then it is then easy to revert things if for whatever reason a mess was made...)

After the rule has been added, and still as root, do ...

# udevadm control --reload-rules && udevadm trigger
(Or do a reboot, if you cant access the root account.? Using sudo as a regular user doesnt work either.)

(Loging out/in doesnt invoke processing the udev rules.)

Anyway, when done and working right...
It then shows up as /dev/ttyICR9k in my system, and any software that needs to use it, regardless of what port on the PC, or external hub it is plugged into., with 100% reliability...

I'd be surprised if you cannot do that with Arch Linux (and derivatives) as well, maybe not in the exact same way as above, but for Ham Radio use, it's well worth getting to grips with...

Comments corrections additions etc welcome...

73.

Dave G0WBX.


--
Created on and sent from a Unix like PC running and using free and open source software:

Yep, that looks much better.

Should easily help someone now I think.

Well done.

73.
Dave G0WBX.

--
Created on and sent from a Unix like PC running and using free and open source software:

开云体育

Hi.

Nice tutorial Sir, well done.

You might want to tell WSJTx, that the mode is USB, and to "Fake It" for Split.

That moves the rig's TX frequency when needed, so as to keep the TX audio frequency in the higher part of the rigs passband, letting it's filters remove any audio harmonics.

Such things are plaguing 20m in particular, spreading/splattering FT8 harmonic signals above (and below!) the FT8 sweetspot, wrecking other mode users.?? (There are other modes than FT8!)

Well worth keeping the output power down if you ever run any PSK mode, to at most a 1/4 of what the rig is capable of, again to prevent splatter and intermod' signals spreading either side of your intended transmit frequency.? With other modes (MFSK like) it's usually a disipation limit in the rigs PA that needs care taking over.

Qpwgraph.? I personally have a love/hate relationship with that?(v0.3.9) as despite following all the instructions, and saving the setup, each time I launch it and reload the setup, the patchbay display is a still mess of tangled green spaghetti.? It is also very difficult to differentiate between any of several identical audio interfaces, renaming is not supported.? (It also doesn’t exit cleanly, if you launch it from a command line, when it exits, you have to use ctl+c to recover the command line!.)

For a simple installation on a Pi, I'm not sure it's a "needed" feature anyway.

I just use Pavuctl to set the levels, and the app's own controls to select the device(s), but once setup, exit it to save on CPU cycles.

Enjoy all the available digimodes, Olivia in particular can give you a "conversational" QSO over great distances, where you can hardly hear or see the signals.? Don't forget to use the TxID and RxID facilities in Fldigi if you use the not so common modes.

JS8Call too, is very good.? (Again, mode is USB, and enable "Fake It" for Split, so the heartbeat feature works "cleanly".)

You have plenty of tools in the box to play with...

Running LMDE 6 here on an intel platform.? Three radio's and no less than 5 Audio I/O devices!

73.

Dave G0WBX.