Date   

Re: PAT Mailbox #pat

Erwin OE1EKG
 
Edited

Thanks Basil,

I did the task like you proposed in your description - but failed. So I did I clean installation with the image 2.20, installed ARDOP and setalsa-kx2.sh again, changed settings for KX3 and the result is the same - see the output. Ardop waterfall is running and shows correct signals.

73 de Erwin, OE1EKG

Running your script and additional settings

cd

cd n7nix/email/pat

nano config.json

 

# change in config.json

  "mycall": "oe1ekg",

  "secure_login_password": „PASSWORD",

  "locator": "JN88de",

 

  "hamlib_rigs": {

  "KX3": {"address": "localhost:4532", "network": "tcp"}

    "rig": "KX3"

 

  "ardop": {

    "addr": "localhost:8515",

    "arq_bandwidth": {

      "Forced": false,

      "Max": 500

    },

    "rig": "KX3",

    "ptt_ctrl": false,

    "beacon_interval": 0,

    "cwid_enabled": true

73 de Erwin, OE1EKG

Running Settings 

pi@draws:~ $ cd
pi@draws:~ $ cd n7nix/config
pi@draws:~/n7nix/config $ ./bin_refresh.sh
 
 == Updating n7nix repo
Already up to date.
 
 == Updating local bin directory for user: pi
 
FINISHED copying desktop files
 
FINISHED copying bin files
 
FINISHED copying AX.25 files
script: /home/pi/bin/sensor_update.sh found
Already have iio_hwmon config for draws sensors
 
FINISHED updating sensor config file
pi@draws:~/n7nix/config $ cd
pi@draws:~ $ cd n7nix/email/pat
pi@draws:~/n7nix/email/pat $ ./pat_ctrl.sh status
 Status for draws-manager: NOT RUNNING and NOT ENABLED
 Status for pat: NOT RUNNING and NOT ENABLED
Port 8080 NOT in use
pi@draws:~/n7nix/email/pat $ ### Integrating script first time before start WSJTX and JS8Call
pi@draws:~/n7nix/email/pat $ # change baudrate for KX3 to 38400
pi@draws:~/n7nix/email/pat $ cd
pi@draws:~ $ cd n7nix/hfprogs
pi@draws:~/n7nix/hfprogs $ nano wsj_ctrl.sh 
pi@draws:~/n7nix/hfprogs $ ./wsj_ctrl.sh -a kx3 start
Setting radio name to: radio_kx3, rig name: KX3
 == rigctld-wsjtx systemctl unit file check
Service: rigctld-wsjtx, status: 3
Systemd service files found
Starting service: rigctld-wsjtx
Service: rigctld-wsjtx, status: 0
pi@draws:~/n7nix/hfprogs $ # Ardop start for KX3
pi@draws:~/n7nix/hfprogs $ cd
pi@draws:~ $ rigctld-wsjtx -m 2045  -r /dev/ttyUSB0 -s 38400 -P GPIO -p 12
 
^A^[c^C
pi@draws:~ $ 
pi@draws:~ $ cd
pi@draws:~ $ cd n7nix/email/pat
pi@draws:~/n7nix/email/pat $ nano config.json
pi@draws:~/n7nix/email/pat $ 
pi@draws:~/n7nix/email/pat $ cd
pi@draws:~ $ cd n7nix/email/pat
pi@draws:~/n7nix/email/pat $ ./pat_ctrl.sh status
 Status for draws-manager: NOT RUNNING and NOT ENABLED
 Status for pat: NOT RUNNING and NOT ENABLED
Port 8080 NOT in use
pi@draws:~/n7nix/email/pat $ cd ~/bin
pi@draws:~/bin $ ./piARDOP_GUI
qt5ct: using qt5ct plugin
qt5ct: D-Bus global menu: no

Edit final check:
pi@draws:~ $ cd
pi@draws:~ $ cd n7nix/ardop
pi@draws:~/n7nix/ardop $ ./ardop_ctrl.sh status | grep -i pat
ardop_ctrl.sh: Need to Install pat
Systemd unit file: /etc/systemd/system/pat.service NOT found.
proc pat: 1, NOT running
pi@draws:~/n7nix/ardop $ 


Re: PAT Mailbox #pat

Basil Gunn
 

Hi Erwin,

A couple of things.

1. If you get "error: localhost:8080", it is most likely that DRAWS
Manager is running and not allowing PAT to use that port. You can
confirm by:

# First make sure you have the most current n7nix repo (scripts).

cd
cd n7nix/config
./bin_refresh.sh

# Then run a script to determine if DRAWS manager is running:

cd
cd n7nix/email/pat
./pat_ctrl.sh status

That will tell you if DRAWS manager is running or some other process is
using port 8080. To kill DRAWS manager and free up port 8080:

mgr-ctrl.sh stop

2. paclink-unix & PAT are 2 separate winlink clients.
I would focus on PAT. I have found that paclink-unix & PAT point-2-point
listeners can NOT co-exist. I am working on a script that will allow
setting up either and change back if required. Currently you can stop
the paclink-unix listener by running:

cd
cd n7nix/email/pat
./listener_ctrl.sh -d

That will disable the paclink-unix listener and allow you to install a
PAT listener for point-2-point operation.

Hope that helps.
/Basil n7nix

All of the installation (2.02) is running - great. Now I want to
install PAT Mailbox. I went to the last description of a past post
from you but this was not running. I'm struggling were I can fix the
problem. I went through the description on your GITHUB
https://github.com/nwdigitalradio/paclink-unix and after to
http://bazaudi.com/plu/doku.php?id=plu:install_postfix but with no
positiv result. When I start the PAT-mailbox from the desktop icon but
it ends up in an error: localhost:8080 ... result "This site can’t be
reachedlocalhost refused to connect." What can I do next?

73 de Erwin, OE1EKG


PAT Mailbox #pat

Erwin OE1EKG
 

Hello Basil,

All of the installation (2.02) is running - great. Now I want to install PAT Mailbox. I went to the last description of a past post from you but this was not running. I'm struggling were I can fix the problem. I went through the description on your GITHUB https://github.com/nwdigitalradio/paclink-unix and after to http://bazaudi.com/plu/doku.php?id=plu:install_postfix but with no positiv result. When I start the PAT-mailbox from the desktop icon but it ends up in an error: localhost:8080 ... result "This site can’t be reachedlocalhost refused to connect." What can I do next?

73 de Erwin, OE1EKG


Re: NWDR20.2 & NWDR21 image release announcement

Erwin OE1EKG
 

Hello Basil,

after a long time I can write some feedback. First, the latest image 20.1 was the first one which was more ore less out of the box for me - straight forward and fast to implement - great job.

Today I gave the new image 21 a try. After the first boot I got 2 error screens that the HAT couldn't be found. Second, when I switch to VNC for the going forward in the installation and initialization of the programs the response (mouse, keyboard) was very slow - on LAN and WLAN VNC. So it is not workable. Only with a direct connection (mouse, keyboard, screen) to the raspy it is workable. I did a second fresh SD card but with the same problem. One remark, it is not possible - or I was not able to find out how to change the screen resolution. In the raspy-config the setting ist not available anymore.
Switched back to my 20.1 SD card it runs without a problem.

I have a Pi 4 so resources shouldn't be a problem.

73 de Erwin, OE1EKG


IC-706 and FT-817

K3VIN
 

Just an update and follow-up to all my requests for assistance setting up my hat. I have the both radios working on JS8 using the setalsa that Basil made for those radios! (Thanks if I failed to say that before!)

I received my cat cable for the 817 today and setting it up did not take long. I now can switch profiles in the JS8 software and use either radio I choose.

One thing I can't figure out:  My notifications do not work with the 817, although the output is set the same and is unchanged. Otherwise, both rigs are now digital-capable!

Kevin, K3VIN


NWDR20.2 & NWDR21 image release announcement

Basil Gunn
 

Yes 2 images.

After spending some time trying to upgrade nwdr20.1 image to the new
Raspbian release based on Debian Bullseye 11.1, I have concluded that
currently (Nov 14) it is not possible to do that. If you attempt to
follow some instructions on how to do a distribution upgrade you WILL
make your SD card unbootable.

Let me say that again. Updating your nwdr image from buster to
bullseye will render your SD card unbootable.

You can tell which Debian/Raspbian release currently being used by:

cat /etc/*release

On the download site: http://nwdig.net/downloads/ there 2 images in the
download directory nwdr20.2.img.xz, nwdr21.img.xz.

current_image.img.xz is a symbolic link to nwdr20.2.img.xz which is
based on buster and is a refresh of the nwdr20.1 image.

The nwdr21.img.xz image is based on bullseye and is a clean re-install
of all the programs. This means you may find problems and if you do I
will fix them ASAP.

Both images use Linux kernel 5.10.63-v7l+ #1459 and work with UDRC
II/DRAWS hats.

See ChangeLog file for more information.
https://github.com/nwdigitalradio/n7nix/blob/master/ChangeLog

Below is snippet from one of the many Internet sites on how to upgrade
from buster to bullseye

"It's worth noting from the start that upgrading Raspberry Pi OS from
Buster (based on Debian 10 Buster) to Bullseye (based on Debian 11
Bullseye) is not officially supported because there are important
changes between major Debian version upgrades, and the recommended way
to get it is to create a new SD card with the new release. The system
may break (some things may not work, it may not be able to boot, etc.)
when upgrading!"

/Basil n7nix


Re: 6-pin din

 

Which serial port?  The one on the accessory port or one attached via USB?

Once you identify which port in /dev, either an application can set the serial port baud rate or you can use stty -- read about it with man stty and info stty from the command line of a terminal.

On Sun, Nov 14, 2021 at 4:59 PM K3VIN <ka8yiu@...> wrote:

[Edited Message Follows]

well, since it mentioned squelch I decided to go ahead and break it off. Interestingly my 817 had no squelch with the cable plugged in if the pie and draws hat did not have power. Now I have squelch with the pie and hat not having power so it did give me a benefit regardless of if it’s necessary or not.

still a part two to one of my replies: where in the pi image do I adjust the baud rate for the 817? I need to use 9600 for an attachment on my accessory so I need to change it to 9600 for the hat.



--
John D. Hays
Kingston, WA
K7VE / WRJT-215

 


Re: 6-pin din

K3VIN
 
Edited

well, since it mentioned squelch I decided to go ahead and break it off. Interestingly my 817 had no squelch with the cable plugged in if the pie and draws hat did not have power. Now I have squelch with the pie and hat not having power so it did give me a benefit regardless of if it’s necessary or not.

still a part two to one of my replies: where in the pi image do I adjust the baud rate for the 817? I need to use 9600 for an attachment on my accessory so I need to change it to 9600 for the hat.


Re: 6-pin din

Loyd
 

K3VIN
you don't need to break off pin 6 as long as there is nothing connecting to it ,
Should be fine I have the connector with the pin in and nothing wired to it


Re: 6-pin din

Basil Gunn
 

But it is usually more standard
Only standard if you only own Yaesu radios. iCom & Kenwood radios do NOT
have this problem.

The cable without pin 6 can be used with other sound cards and other
radios for digital modes. It is only required for AllStar, EchoLink
or other voice modes.


Re: 6-pin din

Corky
 

That is done in the radio configuration portion of the application you are running (i.e., wsjt-x).

Thanks and 73,
-Corky, AF4PM


On Sun, Nov 14, 2021, at 8:48 AM, K3VIN wrote:

[Edited Message Follows]

No, I need to change the baud in the software, the alsa and linux settings, not the rig. That rig is all set.

Tnx

Kevin


Re: 6-pin din

Don Rolph
 

I use the 6 pin mini-din on the FT-817ND regularly with this pin enabled.  It is the squelch signal coming from the radio and is typically interpreted as the COS signal.

There is a challenge with some AllStar interfaces that the OS default handling of the COS/Squelch signal can cause the sound card output to permanently mute, requiring a manual reset of the sound level, which will then automatically mute again.

The COS/Squelch signal is typically necessary for voie modes (AllStar, Echolink), but is typically not needed for digital modes.

I am unfamiliar with the DRAWS design, but what is needed in general is the ability to disable the COS signal in the sound card.  Many of the interfaces have a jumper allowing one to disable this signal.  As a last resort, if the interface does not support disabling the COS/Squelch signal, then indeed removing the pin from the 6 pin mini-din works.

But it is usually more standard and less destructive to disable COS/Squelch handling at the interface card itself.

On Sun, Nov 14, 2021 at 10:18 AM John D Hays - K7VE <john@...> wrote:
This is a hardware issue with some Yaesu radios including the FT 817. 

They use that pin for an input and output and it is just best to disconnect it.

On Sun, Nov 14, 2021, 05:21 K3VIN <ka8yiu@...> wrote:
If I am reading this right, do I need to remove this pin from my cable into my 817? Does this also apply to other apps like JS8?

Running FLdigi with the Yaesu FT-817

Radio Configuration

Set Radio for Digital Mode Operation (SSB-Based AFSK)

  • Use a mDin6 cable without pin 6, Squelch connected (I wiggled pin 6 until it broke)
    • Looking into the male mDin 6 connector with the key on top, its the upper right hand pin
    • Verify this as it is easy to get it wrong



--

73,
AB1PH
Don Rolph


Re: 6-pin din

K3VIN
 
Edited

No, I need to change the baud in the software, the alsa and linux settings, not the rig. That rig is all set.

Tnx

Kevin


Re: 6-pin din

Don Rolph
 

It is menu item 40 which sets packet rate between 1200 and 9600 baud.

You also must set the radio into packet mode if you want to use packet o 2 meters.

On Sun, Nov 14, 2021 at 11:29 AM K3VIN <ka8yiu@...> wrote:
Follow-up question: I know I have seen it in the docs, but cannot find now. I need to adjust the baud rate for the 817. I am using the 706_817 alsa, and the 706 is working fine. I just can't remember nor find how to adjust the right connector for the 817.

Kevin



--

73,
AB1PH
Don Rolph


Re: 6-pin din

K3VIN
 

Follow-up question: I know I have seen it in the docs, but cannot find now. I need to adjust the baud rate for the 817. I am using the 706_817 alsa, and the 706 is working fine. I just can't remember nor find how to adjust the right connector for the 817.

Kevin


Re: 6-pin din

 

This is a hardware issue with some Yaesu radios including the FT 817. 

They use that pin for an input and output and it is just best to disconnect it.

On Sun, Nov 14, 2021, 05:21 K3VIN <ka8yiu@...> wrote:
If I am reading this right, do I need to remove this pin from my cable into my 817? Does this also apply to other apps like JS8?

Running FLdigi with the Yaesu FT-817

Radio Configuration

Set Radio for Digital Mode Operation (SSB-Based AFSK)

  • Use a mDin6 cable without pin 6, Squelch connected (I wiggled pin 6 until it broke)
    • Looking into the male mDin 6 connector with the key on top, its the upper right hand pin
    • Verify this as it is easy to get it wrong


6-pin din

K3VIN
 

If I am reading this right, do I need to remove this pin from my cable into my 817? Does this also apply to other apps like JS8?

Running FLdigi with the Yaesu FT-817

Radio Configuration

Set Radio for Digital Mode Operation (SSB-Based AFSK)

  • Use a mDin6 cable without pin 6, Squelch connected (I wiggled pin 6 until it broke)
    • Looking into the male mDin 6 connector with the key on top, its the upper right hand pin
    • Verify this as it is easy to get it wrong


Re: Soundcard

K3VIN
 

Fixed! Power out, but ALC may be too high.

Tnx all fer the help on this project! I'm sure I will be back for more!

73

Kevin, K3VIN


Re: Soundcard

K3VIN
 

IC-706 has PTT and is decoding JS8. I do not appear to be sending out any signal, which is probably an ALC or other setting in the rig that I have to figure out. This is the first time I am using this radio for digital.

I kept having trouble with a Hamlib error and the last time I went thru the setup, the rig shown as NONE in the settings as does my TS450s and my Rigblaster, and the PTT started working with no radio errors.

Kevin, K3VIN


Re: Soundcard

Basil Gunn
 

It is stopped. Sorry, but it it is in the CAT Control and RIG Options
I only get: /dev/tty, /dev/ttySC0, dev/ttySC1 and USB. None allow
CAT control or PTT.

My issue is really just getting PTT.
See my notes on PTT with js8call in the following link:

https://github.com/nwdigitalradio/n7nix/blob/master/docs/DRAWS_CONFIG_HF.md#js8call

I am decoding just fine.

81 - 100 of 6048