I usually make symlinks to each device based on the data in /dev/serial/by-id. Add those in the pi home directory and they are always correct and you can name them whatever you like. The symlink is pe

#hamlib

Yes. This is the simplest way to do these because if you need to relay it by voice, it's "paint by the numbers". Super simple. Date and Time stamps make the message unique along with the addressees.

#claws-mail

Scott, Typically, ICS-213s are normalized down to numbered lines per the PDF forms provided by the form owners. What gets transmitted OTA is simply the numeral followed by the data. See the attached s

#claws-mail

I can certainly add the current ICS-213 to my UI client for PAT. Are you simply using the numbered format for the OTA transmission? 1. 2. etc.

#claws-mail

I found after my board was fixed by NWDR that DRAWS manger values were not even close to appropriate for using FLDIGI, particularly on receive. I also had to recompile FLDIGI using configure defaults

I saw something similar when downloading it yesterday. On Win10 it was abysmally slow. With the same connection on Linux it was it's normally speedy self. The reader is left to his own conclusions.

Some communication please. It was sent many moons ago.

#draws

I have done multiple Etcher images lately on a Win10 machine that is at level 1809 IIRC. Maybe it's something in 1903. I do not allow Defender or any Firewalls to be running as it is largely an air-ga

zip definitely works, i did that yesterday.

FT-450D

#wsjt-x

Second that notion. There is a lot of what I consider unwanted fluff in this image since I don't care about packet radio. I would really like to have a clean image with only the necessary drivers and

#yaac #replacecompass #draws #install #js8call

sounds very much like my issue, only I have badly distored audio to the transmitter. mine is in a box ready to be mailed back for eval.

#wsjt-x

Noticed kernel 4.19 in his output. When I updated my Beta13 using the supplied scripts the kernel upgraded to a 4.19 version and then nothing worked. That may be a clue.

#yaac #replacecompass #draws #install #js8call

This happened to me after it had been working. I re-imaged the SD card and it came back to life. In my case, I had used some of the scripts to update the HF programs and some other things. After that

#yaac #replacecompass #draws #install #js8call

If no-one has any input I will package up my DRAWS for a return. It's a might expensive GPS hat at this point.

#draws

I think there is also a build shell script in Beta13 for ARDOP, but I have not used it.

#winlink

Over the air testing revealed that what I was seeing here is mirrored over 200 miles away, so it is not likely a local RFI issue on RX here. Then, I hooked up an external high quality sound card via U

#draws

Describe your problem and answer these questions: as in prev message Did you make your own cables? No, using cables provided with the DRAWS Which mDin6 connector are you using? Looking at the front of

#draws

DRAWS image Beta13 I am getting output audio which undulates when using either FLDIGI or JS8Call (or even when just using the TUNE button in FLDIGI). Has anyone run across this? My draws-manager has t

#draws