Erwin, in addition to what Basil has said, looking at your config.json file, I see some inconsistencies. I am not sure if they are causing the problems or not, but it is possible. The first is that mo

#upgrade #draws #configuration

Hello Basil, thanks, concerning the rig this was a misunderstanding from my side. So I checked it with your proposal - see below. Thought I found missing arguments - compared to another setting on ano

#upgrade #draws #configuration

Erwin, You only need to setup the ardop systemd service files ONCE and once only. After that the correct systemd files will run from boot and not need touching unless you change radios. First you need

#upgrade #draws #configuration

Hello Basil,Hello Basil, Thanks for your help and patience. I tried to find out what happens. First I did:pi@draws:~ $ cd pi@draws:~ $ ls -salt .wl2k total 12 4 drwxr-xr-x 35 pi pi 4096 Sep 1 21:33 ..

#upgrade #draws #configuration

Erwin, Please disregard the last link I sent you. The following link is the one to use for automatic startup for ardop/rigctld/pat using systemd service files. https://github.com/nwdigitalradio/n7nix/

#upgrade #draws #configuration

Erwin, Everything that you did looks fine. But until the config file problem is fixed you will not have a port 8080 LISTENER. I agree, something seems amiss with PAT config file. I have some severely

#upgrade #draws #configuration

Hello Basil did this: pi@draws:~ $ cd pi@draws:~ $ cd n7nix pi@draws:~/n7nix $ git pull remote: Enumerating objects: 22, done. remote: Counting objects: 100% (22/22), done. remote: Compressing objects

#upgrade #draws #configuration

Erwin, 1. Please update your local n7nix repo. That should fix the naming problem. cd cd n7nix git pull 2. Force an update of the ardop systemd service files. cd n7nix/ardop ./ardop_ctrl.sh -f -a kx2

#upgrade #draws #configuration

Hello Basil, thanks for your fast response. Tried your proposal: pi@draws:~ $ mgr-ctrl.sh status * draws-manager.service - DRAWSâ ¢ Manager - A web application to manage the DRAWâ ¢ HAT configuration.

#upgrade #draws #configuration

Hi Erwin, This is probably because DRAWS manager is running. Please run: mgr-ctrl.sh status If you see 'enabled' & 'active (running') then you will want to stop DRAWS-manager $ mgr-ctrl.sh status ● dr

#upgrade #draws #configuration

Hello Basil, thanks for the fast response - alle run flawless. Is ti necessary to put the kernel hold again on the image? One thing I faces was the PAT - I had the problem in the past #5725 nresolved.

#upgrade #draws #configuration

Erwin, First remove the kernel hold: sudo su apt-mark unhold $(apt-mark showhold) # verify apt-mark showhold # Should be no output # Then do a system update/upgrade apt-get update apt-get upgrade # re

#upgrade #draws #configuration

Hello on the forum, after few month I found time to play again with the DRAWS and want to finish my started installation. First of all I want to do an update -but this failed cause of PAT and WSJTX in

#upgrade #draws #configuration

Basil, No modem but the DRAWS. I didn’t see this on previous upgrades but if nothings hurt I’ll ignore unless I can edit something to make it go away. Richard KI5EVJ

#upgrade

Unless you have a Bluetooth Modem I would ignore it. I did an apt-get update; apt-get upgrade on 3 different kernels and found the same problem on each. Linux test21903212021 5.4.79-v7l+ #1373 SMP Mon

#upgrade

Doing some final configure steps and I got the following: Unpacking pi-bluetooth (0.1.17) over (0.1.16) ... Preparing to unpack .../rpi-eeprom_12.4-1_armhf.deb ... Unpacking rpi-eeprom (12.4-1) over (

#upgrade

If you have one of our beta images, you can quickly upgrade. From a terminal perform the following: cd /tmp wget https://s3.amazonaws.com/js8call/0.11.0/js8call_0.11.0-devel_armhf.deb sudo apt-get upd

#js8call #upgrade #release