Date   
Re: NWDR15 Image observations

Bernard f6bvp
 

Hi Basil,
I downloaded new nwdr15 image and ran initial setup.
Then I performed app-config.sh core
Following Getting Started Guide I verified ALSA settings with alsa-show.sh
and after becoming root
sudo su
./ax25-start 
replied :
User name (pi) does not exist. must be one of:

I must have forgotten something.

73 de Bernard, f6bvp



Re: #direwolf #direwolf

Basil Gunn
 

Can you provide the login password or direct me where to get it
Please.
Google is your friend
https://lmgtfy.com/?q=aprs+passcode&pp=1&s=l

1. Your questions don't have anything to do with udrc or draws. You
would be better off asking them on the direwolf groups.io site.
https://groups.io/g/direwolf/topics

2. If you use the NWDR image the APRS server password is automatically
calculated & added to the direwolf configuration when running the
initial config script.

3. There are many places to get your APRS server login passcode.
The nwdr image uses a C program from Xastir. Look at
n7nix/direwolf/config.sh around line 230.

# Get the n7nix repo
git clone https://github.com/nwdigitalradio/n7nix
# Go to the directory containing the callpass source code

cd n7nix/direwolf/
gcc -o callpass callpass.c
# run the program
./callpass <your_callsign>
Passcode for <your_callsign> is <some_5_digit_number>

4. The gps on the DRAWS hat requires gpsd version 3.18.1 or higher to
operate properly. You most likely got your gpsd from the Debian
repositories which is about 2 years old. Verify your gpsd version number:

gpsd -V

5. Not really motivated to support people that want to build their own
custom image from scratch. Not that you shouldn't, just that I don't want
to support you doing it. What is your compelling argument for not
using the supplied image?

/Basil

Re: #direwolf #direwolf

Paul Noa
 

WB2OSZ,

Ha! 
Didn't realize I was talking to the author of Direwolf!  Thank you very much for all of your hard work developing this app.

In  an effort to set up Direwolf, I may have not understood but I need a login and password for Igate.  I see my my callsign i.e. KO4BCZ  on the T2USANW aprsc status server but it is not verified.

Does Tha explain why I am not in APRS.FI database as well?

Can you provide the login password or direct me where to get it Please.

Best regards,

Paul

On Sun, 26 Jan 2020 at 08:14, WB2OSZ <wb2osz@...> wrote:
It looks like your passcode is too long.
Your ILOGIN configuration should look similar to this:

ILOGIN WW9WWW-9 12345

The last part should be five digits. 

Re: #direwolf #direwolf

 

It looks like your passcode is too long.
Your ILOGIN configuration should look similar to this:

ILOGIN WW9WWW-9 12345

The last part should be five digits. 

Re: Problems with Winlink handshaking on VHF and no power to transmitter on HF

Basil Gunn
 

Please read the following to see if that helps with your HF problems
ALSA settings for IC-7000
https://github.com/nwdigitalradio/n7nix/blob/master/docs/RADIO_APP_NOTES.md#ALSA-settings-for-IC-7000

Did setting the correct gpio pin in FLdigi rather than using FLrig solve
your problem?
/Basil n7nix


Basil Gunn <@basil860> writes:

OK. I have refreshed my system with the V15 image and am back to the
same problem on HF as stated before (no pwer out or rig key on FLDigi,
WSJTX, JS8Call, etc.).
Pick one program at a time, for FLdigi using a DRAWS hat:

Fldigi configuration ->Rig->GPIO

Select BCM 12 for left mDin6 connector
Select BCM 23 for right mDin6 connector

Read this for reference:
https://nw-digital-radio.groups.io/g/udrc/wiki/UDRC%E2%84%A2-and-fldigi-Setup-Page#Set-up-PTT

Here is what I reassembled and making an
assumption of what commands you would want to see:
NOW an unsolved mystery. With the same IC-7000 and ax25 stopped via
the AX.25-control script I can’t get WSJTX, Fldigi, JS8Call to key
the transmitter and send audio. Running
n7nix/deviation/measure_deviate.sh –c left keys the radio and I get
power out (modulated rig input). Issuing the measure_deviate –c left
–l 5 doesn’t key the transmitter for 5 seconds – it just keeps going
for the full 30 seconds. So this utility can key the transmitter with
audio input to the transmitter.

When I try JS8Call, WSJTX, FLDigi the transmitter is not keyed or
audio sent to the Mic in. I am using FLRig for the radio interface
BUT PTT is turned off in FLRig (no CAT/RST/DTR etc). FLRig is talking
to the radio OK (reading VFO/Mode)

For JS8Call the settings are: Radio Rig-FLRig FLRig, PTT VOX, Mode
USB, Split none. Audio input is plughw:CARD=idrc,DEV=0 and output the
same. The software reads data from the radio just fine and decodes
OK. Pressing the Tune button gives indication from the software of
transmitting (Red Tune button and TX button red) but the radio isn’t
keyed or transmitting.

Similar things are happening with FLDigi (receives/decodes OK but no
transmission). It is setup as rig control by FLRig and FLRig not
keying the modem. Soundcard devices has PortAudio selected with
Capture: udrc:bcm2935-i2s-tlv320aic32x4 hifi tlv320aic32x4-hifi-0
(hw: 1,0) as the only option to choose from and Playback the same
only there are 4 options here (alsa0,1 alsa 0,2 dmix). Hitting the
Tune button on FLDigi gives the indication from the software that it
is tuning or transmitting text (in the waterfall) but the rig doesn’t
key or transmit.

#direwolf #direwolf

Paul Noa
 

Ok folks,

I have installed Direwolf with a DRAWS hat using the basic Raspbian image with desktop only.

1) My APRS info is getting through IGate but is unverified and is not present APRS.fi raw data, presumably because its not verified.
2) the fixed info I entered in Direwolf.conf shows up but not the actual GPSD position ??
3) I get the following message on startup specifically the Warning I am not sure what to do about:

pi@raspberrypi:~ $ direwolf
Dire Wolf version 1.5
Includes optional support for:  gpsd cm108-ptt
 
Reading config file direwolf.conf
WARNING: strlcpy result length 11 exceeds maximum length 7.  (config.c config_init 4025)
Audio device for both receive and transmit: plughw:CARD=udrc,DEV=0  (channels 0 & 1)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 48000 sample rate / 3.
Channel 1: 1200 baud, AFSK 1200 & 2200 Hz, E+, 48000 sample rate / 3.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
GPSD: Location fix is now 3D.
 
Now connected to IGate server noam.aprs2.net (44.10.10.10)
Check server status here http://44.10.10.10:14501
 
[ig] # aprsc 2.1.5-g8af3cdc
[ig] # logresp KO4BCZ unverified, server T2SJC
[ig] KO4BCZ>APDW15:!3009.37NR08134.58W&
[0L] KO4BCZ>APDW15,WIDE1-1,WIDE2-1:!3009.37NS08134.58W#PHG6160UDRC
 
Any Comments that would help would be much appreciated.

Paul
KO4BCZ

Re: Nixtracker

 

Understood. I can plug in a cable. Thanks for helping sort through a bit of confusion.

david

Re: Nixtracker

Basil Gunn
 

I haven't tested my hostap scripts in some time & the systemd folks have been
continuously mucking with network underpinnings for a number of years.

I need to verify my WiFi networking scripts that switch between
client & host are doing what they should.

/Basil

Awesome!! So is the hostap mode part of NWDR image and how to enable
it? That is WiFi without my home router correct/ hotspot is that the
correct term?. I tried to do a hotspot switch from other instructions
and only partly succeeded. If it is already part of NWDR XX I don’t
need to do anything? Thanks Basil.

Re: Nixtracker

 

Awesome!! So is the hostap mode part of NWDR image and how to enable it? That is WiFi without my home router correct/ hotspot is that the correct term?. I tried to do a hotspot switch from other instructions and only partly succeeded. If it is already part of NWDR XX I don’t need to do anything? Thanks Basil.

Re: Nixtracker

Basil Gunn
 

Hi David,
Short answer:
For a display I use an Android Samsung Galaxy TAB A running a browser.

nixtracker is a fork of Dan Smith's dantracker that used a hard wired
LCD display. nixtracker is a heavily modified dantracker that runs in a
browser so that it can be used over the network. In my truck I run an
RPi in hostap mode & connect my phone or Android pad to the RPi via
WiFi.

It does not use maps. If you want to see what it basically looks
like see Eric Schott's links under n7nix dantracker links here:
https://github.com/n7nix/nixtracker
or a youtube here:
https://www.youtube.com/watch?v=Pg-buSHbZVc

/Basil n7nix

David Lowry <huskyrunnr@...> writes:

Basil, when you use nixtracker mobile, what are you using for a display and is it hardwired to the RPi or not?

tia, David, Ke7rgp

Nixtracker

 

Basil, when you use nixtracker mobile, what are you using for a display and is it hardwired to the RPi or not?

tia, David, Ke7rgp 

Re: NWDR15 image release announcement

Basil Gunn
 

Two things about this release so far: Paclink-Unix won't run (out of
the box) because the wl2k.conf file hasn't been updated with the
callsign, gridsquare, axport, and Winlink password.
You need to actually configure paclink-unix. Please read:
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started
"More Packet Program Options"

The image announcement/install/getting started Wiki doesn't point to
the paclink setup information. Are Claws email, postfix, etc installed
in this image. No desktop icon exists for them.
Correct. Whatever the project installs is what you get. You can choose
Claw-mail from the system drop down menu. Config instructions for mutt,
claws-mail and rainloop exist here:

https://github.com/nwdigitalradio/n7nix/tree/master/email
I do not support ThunderBird or Alpine anymore.

Maybe this is covered in a Paclink-Unix thread but the message board
is getting too big to search easily -
Another sticky perhaps for paclink install/issues?
To install paclink-unix from the 'Getting Started Guide':

# If you want to send & receive Winlink messages
./app_config.sh plu

Thanks
Dave

Re: Problems with Winlink handshaking on VHF and no power to transmitter on HF

Basil Gunn
 

OK. I have refreshed my system with the V15 image and am back to the
same problem on HF as stated before (no pwer out or rig key on FLDigi,
WSJTX, JS8Call, etc.).
Pick one program at a time, for FLdigi using a DRAWS hat:

Fldigi configuration ->Rig->GPIO

Select BCM 12 for left mDin6 connector
Select BCM 23 for right mDin6 connector

Read this for reference:
https://nw-digital-radio.groups.io/g/udrc/wiki/UDRC%E2%84%A2-and-fldigi-Setup-Page#Set-up-PTT

Here is what I reassembled and making an
assumption of what commands you would want to see:

------------------------------

After installation of image V15

1/24/2020

YAAC works OK. Sends a receives packets.

Tried wl2kax25 connection. It failed due to config issues:

pi@DRAWS:/usr/local/etc $ wl2kax25 -c k2wvc-10

wl2kax25: Need to specify ax25 port
Pick one problem per email. wl2kax25 is a packet app and the answer is you have
not installed paclink-unix. This has nothing to do with your FLdigi
problem.

This paclink config was not called out as something that needed changing in the Wiki for installation.
I had to edit /usr/local/etc/wl2k.conf and add my callsign, gridsquare, axport ID, and WL2K password before it would work. Should this be in the Wiki for post install?
If you want Winlink functionality then you need to install paclink-unix.
app_config.sh plu
That is mentioned in the Getting Started Guide

Did Claws go away or is it separately installed to work with paclink?
It has been too long since I gave up on V14 and set it aside. Mutt is
in the image.
Claws-mail is part of the Winlink solution and is installed when you
install paclink-unix. The symptom you have is paclink-unix is not installed.

My V15 system works ok on VHF/Direwolf as verified by YAAC receiving
packets and sending a beacon copied by aprs.fi. I can also monitor the
packet traffic with tail –f /var/log/direwolf/direwolf.log and
listen –at.
The listen command line arguments have changed. To get a timestamp do
not specify -t.

I can send a beacon with: btest.sh –P udr0 successfully
------------------------------------------------------------------------------------------------------------

NOW an unsolved mystery. With the same IC-7000 and ax25 stopped via the AX.25-control script I can’t get WSJTX, Fldigi, JS8Call to key the transmitter and send audio. Running n7nix/deviation/measure_deviate.sh –c left keys the radio and I get power out (modulated rig input). Issuing the measure_deviate –c left –l 5 doesn’t key the transmitter for 5 seconds – it just keeps going for the full 30 seconds. So this utility can key the transmitter with audio input to the transmitter.

When I try JS8Call, WSJTX, FLDigi the transmitter is not keyed or audio sent to the Mic in. I am using FLRig for the radio interface BUT PTT is turned off in FLRig (no CAT/RST/DTR etc). FLRig is talking to the radio OK (reading VFO/Mode)

For JS8Call the settings are: Radio Rig-FLRig FLRig, PTT VOX, Mode USB, Split none. Audio input is plughw:CARD=idrc,DEV=0 and output the same. The software reads data from the radio just fine and decodes OK. Pressing the Tune button gives indication from the software of transmitting (Red Tune button and TX button red) but the radio isn’t keyed or transmitting.

Similar things are happening with FLDigi (receives/decodes OK but no transmission). It is setup as rig control by FLRig and FLRig not keying the modem. Soundcard devices has PortAudio selected with Capture: udrc:bcm2935-i2s-tlv320aic32x4 hifi tlv320aic32x4-hifi-0 (hw: 1,0) as the only option to choose from and Playback the same only there are 4 options here (alsa0,1 alsa 0,2 dmix). Hitting the Tune button on FLDigi gives the indication from the software that it is tuning or transmitting text (in the waterfall) but the rig doesn’t key or transmit.

Here are some captures of various commands:

aplay –l of my system:

pi@DRAWS:~ $ aplay -l

**** List of PLAYBACK Hardware Devices ****

card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]

Subdevices: 7/7

Subdevice #0: subdevice #0

Subdevice #1: subdevice #1

Subdevice #2: subdevice #2

Subdevice #3: subdevice #3

Subdevice #4: subdevice #4

Subdevice #5: subdevice #5

Subdevice #6: subdevice #6

card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI]

Subdevices: 1/1

Subdevice #0: subdevice #0

card 0: ALSA [bcm2835 ALSA], device 2: bcm2835 IEC958/HDMI1 [bcm2835 IEC958/HDMI1]

Subdevices: 1/1

Subdevice #0: subdevice #0

card 1: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]

Subdevices: 0/1

Subdevice #0: subdevice #0

pi@DRAWS:~ $

arecord –l of my system:

pi@DRAWS:~ $ arecord -l

**** List of CAPTURE Hardware Devices ****

card 1: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]

Subdevices: 0/1

Subdevice #0: subdevice #0

pi@DRAWS:~ $

alsa-show:

pi@DRAWS:~/n7nix/deviation $ alsa-show.sh

===== ALSA Controls for Radio Transmit =====

LO Driver Gain L:[-6.00dB] R:[-6.00dB]

PCM L:[-22.50dB] R:[-22.50dB]

DAC Playback PT L:[P3] R:[P3]

LO Playback CM [Full Chip]

===== ALSA Controls for Radio Receive =====

ADC Level L:[-2.00dB] R:[-2.00dB]

IN1 L:[10 kOhm] R:[10 kOhm]

IN2 L:[Off] R:[Off]

CM L:[10 kOhm] R:[10 kOhm]

pi@DRAWS:~/n7nix/deviation $

I did a set-alsa-ic7000.sh and it changed values but didn’t fix anything. What am I missing?

Re: Problems with Winlink handshaking on VHF and no power to transmitter on HF

Dave Christensen
 

OK.  I have refreshed my system with the V15 image and am back to the same problem on HF as stated before (no pwer out or rig key on FLDigi, WSJTX, JS8Call, etc.).  Here is what I reassembled and making an assumption of what commands you would want to see:

------------------------------

After installation of image V15

1/24/2020

YAAC works OK.  Sends a receives packets.

Tried wl2kax25 connection.  It failed due to config issues:

pi@DRAWS:/usr/local/etc $ wl2kax25 -c k2wvc-10

wl2kax25: Need to specify ax25 port

wl2kax25: WARNING: gridsquare not specified in config file

Usage:  wl2kax25 -c target-call [options]

  -c  --target-call   Set callsign to call

  -a  --ax25port      Set AX25 port to use

  -P  --wl2k-passwd   Set password for WL2K secure login

  -t  --timeout       Set timeout in seconds

  -e  --email-address Set your e-mail address

  -s  --send-only     Send messages only

  -V  --verbose       Print verbose messages

  -v  --version       Display program version only

  -C  --configuration Display configuration only

  -h  --help          Display this usage info

pi@DRAWS:/usr/local/etc $

This paclink config was not called out as something that needed changing in the Wiki for installation.

I had to edit /usr/local/etc/wl2k.conf and add my callsign, gridsquare, axport ID, and WL2K password before it would work.  Should this be in the Wiki for post install?

 

Did Claws go away or is it separately installed to work with paclink?  It has been too long since I gave up on V14 and set it aside.  Mutt is in the image.

My V15 system works ok on VHF/Direwolf as verified by YAAC receiving packets and sending a beacon copied by aprs.fi.  I can also monitor the packet traffic with tail –f /var/log/direwolf/direwolf.log  and listen –at.

I can send a beacon with: btest.sh –P udr0 successfully

------------------------------------------------------------------------------------------------------------

NOW an unsolved mystery.  With the same IC-7000 and ax25 stopped via the AX.25-control script I can’t get WSJTX, Fldigi, JS8Call to key the transmitter and send audio.  Running n7nix/deviation/measure_deviate.sh –c left keys the radio and I get power out (modulated rig input).  Issuing the measure_deviate –c left –l 5 doesn’t key the transmitter for 5 seconds – it just keeps going for the full 30 seconds.  So this utility can key the transmitter with audio input to the transmitter.

When I try JS8Call, WSJTX, FLDigi the transmitter is not keyed or audio sent to the Mic in.  I am using FLRig for the radio interface BUT PTT is turned off in FLRig (no CAT/RST/DTR etc).  FLRig is talking to the radio OK (reading VFO/Mode)

For JS8Call the settings are:  Radio Rig-FLRig FLRig, PTT VOX, Mode USB, Split none.  Audio input is plughw:CARD=idrc,DEV=0 and output the same.  The software reads data from the radio just fine and decodes OK.  Pressing the Tune button gives indication from the software of transmitting (Red Tune button and TX button red) but the radio isn’t keyed or transmitting.

Similar things are happening with FLDigi (receives/decodes OK but no transmission).  It is setup as rig control by FLRig and FLRig not keying the modem.  Soundcard devices has PortAudio selected with Capture:  udrc:bcm2935-i2s-tlv320aic32x4 hifi tlv320aic32x4-hifi-0 (hw: 1,0)  as the only option to choose from and Playback the same only there are 4 options here (alsa0,1   alsa 0,2   dmix).  Hitting the Tune button on FLDigi gives the indication from the software that it is tuning or transmitting text (in the waterfall) but the rig doesn’t key or transmit.

Here are some captures of various commands:

aplay –l of my system:

pi@DRAWS:~ $ aplay -l

**** List of PLAYBACK Hardware Devices ****

card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]

  Subdevices: 7/7

  Subdevice #0: subdevice #0

  Subdevice #1: subdevice #1

  Subdevice #2: subdevice #2

  Subdevice #3: subdevice #3

  Subdevice #4: subdevice #4

  Subdevice #5: subdevice #5

  Subdevice #6: subdevice #6

card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI]

  Subdevices: 1/1

  Subdevice #0: subdevice #0

card 0: ALSA [bcm2835 ALSA], device 2: bcm2835 IEC958/HDMI1 [bcm2835 IEC958/HDMI1]

  Subdevices: 1/1

  Subdevice #0: subdevice #0

card 1: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]

  Subdevices: 0/1

  Subdevice #0: subdevice #0

pi@DRAWS:~ $

 

arecord –l of my system:

pi@DRAWS:~ $ arecord -l

**** List of CAPTURE Hardware Devices ****

card 1: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]

  Subdevices: 0/1

  Subdevice #0: subdevice #0

pi@DRAWS:~ $

 

alsa-show:

pi@DRAWS:~/n7nix/deviation $ alsa-show.sh

 ===== ALSA Controls for Radio Transmit =====

LO Driver Gain  L:[-6.00dB]           R:[-6.00dB]

PCM              L:[-22.50dB]                R:[-22.50dB]

DAC Playback PT               L:[P3]                    R:[P3]

LO Playback CM                [Full Chip]

 

 ===== ALSA Controls for Radio Receive =====

ADC Level            L:[-2.00dB]          R:[-2.00dB]

IN1                         L:[10 kOhm]       R:[10 kOhm]

IN2                         L:[Off]                   R:[Off]

CM                         L:[10 kOhm]       R:[10 kOhm]

pi@DRAWS:~/n7nix/deviation $

 

I did a set-alsa-ic7000.sh and it changed values but didn’t fix anything.  What am I missing?

 

Re: NWDR15 image release announcement

Dave Christensen
 

Two things about this release so far:  Paclink-Unix won't run (out of the box) because the wl2k.conf file hasn't been updated with the callsign, gridsquare, axport, and Winlink password.  The image announcement/install/getting started Wiki doesn't point to the paclink setup information.  Are Claws email, postfix, etc installed in this image.  No desktop icon exists for them.  Maybe this is covered in a Paclink-Unix thread but the message board is getting too big to search easily - Another sticky perhaps for paclink install/issues?

Thanks
Dave

Re: NWDR15 image release announcement

 


I will add that there are a large number of applications that can use the DRAWS™ HAT. Almost none of which are developed or maintained by NW Digital Radio.  They have their own release schedules and can change their configuration requirements at will.  To manage all of that would require a development team.

Basil has done a great job providing basic configuration scripts, mostly for AX.25 configurations and some split channel operations.  However, unless there was a group that the application developers could work with to establish standards for configuration, many applications will continue to require individual knowledge and effort.

--


John D. Hays
Director

  


 

Re: NWDR15 image release changed to RPi Config backup

Basil Gunn
 

J P,

I'm not very motivated to write a configuration back-up program. The
following is my thinking, flawed as it may be.

1. I can regen any of my RPi units from a blank mSD card in 30 minutes
or less.
2. I keep a copy of my alsa settings for the 1/2 dozen radios that I
own in my personal wiki.
3. Most of the packet programs have single easy to find configuration
files, so that's easy. Most of the HF programs have directories of
configuration & state in locations I am challenged to locate, so that's
harder.

If I was going to have a configuration back-up utility I would use
rsnapshot:

repo: https://github.com/rsnapshot/rsnapshot
man page: https://linux.die.net/man/1/rsnapshot

which uses rsync. rsync allows you to back-up or copy files locally or
on a remote (Unix) computer. rsnapshot is similar to Apple's time machine
without the gui.

rsnapshot is what I use to back-up my Linux workstations with crontab
entries like the following for daily, weekly, monthly back-up file
rotation.

# m h dom mon dow command
30 2 * * * /usr/bin/rsnapshot daily
30 1 * * 6 /usr/bin/rsnapshot weekly
5 0 1 * * /usr/bin/rsnapshot monthly

If you send me a list of things you are running on your RPi, I will send
you a first cut of what I think the rsnap configuration file
(/etc/rsnapshot.conf) for your RPi would look like. Identify where you
want your back-up files to live ie. on another RPi devoted to backing
stuff up?

All of the above assumes you are running some Linux/Unix machine as well
as your RPi. I do not know or care what the Windows solution is, I don't
use Windows much. Windows is really not that much fun for me to use.

/Basil


J P Watters via Groups.Io <kc9kko=mac.com@groups.io> writes:

Basil or other gifted scripting author,

This is just a thought

If there was a first release of the new year that was going to SIGNIFICANTLY be a game changer, this is it. !!!!

Missing from your scripting is that Holy Grail Script that when run archives the configuration of the of all the installed APPS and the image configuration.

I only wish that I was a script coder that could write a script that would do that archive the configurations, AND also RESTORE the configuration from previously archived configurations.
alas, I am not such a gifed coder and at the mercy of those who are.
ie.
buconfig -l
This simply lists that configuration date and times that configurations were archived.
buconfig
when run without arguments, stores archived versions of the configuration files
buconfig -a -s /home/notmypi/
when run with the -a "archives the current configuration settings" and -s specifies the directory location that the archived configurations are stored.
"normally" the archived configuration files are stored in /home/pi/archivedconfigs
buconfig -r -d 2020-01-24-00:00
when run with the -r it restores the most recently saved configuration files
or when the -d specifies the date or date time, it restores the most recently saved configuration files after the specified date or datetime.
-----------
-s -d and other program flags can be used together to maximize the effectiveness of the configuration archive and restoration.
when run with flag "buconfig -a -d 2019-12-31" would archive the current configuration files stored as archived on 2019-12-31-2359
as to represent the last configuration for the year 2019.

Re: NWDR15 image release announcement

Steve, N9VW
 

JP,
If ever there was a teachable moment, this is it..!!! The underlying theme with the DRAWS product is to put the Amateur back into Amateur Radio.

You have already done most of the 'hard' part of coding, describing what it is to do. If you are just a little bit Linux literate, which I am going to presume you are to some degree since you are playing with this package. Scripts are really nothing magic nor difficult. There are more on-line references and tutorials to get you running with a BASH script in short order. It is easy stuff (why do you think we use it?) that gets the job done.

You can start with simple stuff and just build on top of that. I will toss a few hints your way to aid in your quest. You most likely will want to use a "CASE" statement to select your command line options and something like tar or gzip to collect all of the .conf files into a single file for ease of handling. I would make a "cp" of the files into a work directory first, the script can do that with ease.

Give it a whirl, learn something new for 2020 and have a world of fun in the process. You will be amazed at how simple it all really is...;>

Happy Trails,
Steve VanWambeck, N9VW

On 1/23/2020 10:58 PM, J P Watters via Groups.Io wrote:
Basil or other gifted scripting author, 

This is just a thought

If there was a first release of the new year that was going to SIGNIFICANTLY be a game changer, this is it. !!!!

Missing from your scripting is that Holy Grail Script that when run archives the configuration of the of all the installed APPS and the image configuration. 

I only wish that I was a script coder that could write a script that would do that archive the configurations, AND also RESTORE the configuration from previously archived configurations. 
alas, I am not such a gifed coder and at the mercy of those who are. 
ie. 
buconfig -l
This simply lists that configuration date and times that configurations were archived. 
buconfig 
when run without arguments, stores archived versions of the configuration files
buconfig -a -s /home/notmypi/
when run with the -a "archives the current configuration settings" and -s specifies the directory location that the archived configurations are stored. 
"normally" the archived configuration files are stored in /home/pi/archivedconfigs
buconfig -r -d 2020-01-24-00:00
when run with the -r it restores the most recently saved configuration files 
or when the -d specifies the date or date time, it restores the most recently saved configuration files after the specified date or datetime.
-----------
-s -d and other program flags can be used together to maximize the effectiveness of the configuration archive and restoration.
when run with flag "buconfig -a -d 2019-12-31" would archive the current configuration files stored as archived on 2019-12-31-2359
as to represent the last configuration for the year 2019.

Re: NWDR15 image release announcement

J P Watters
 

Basil or other gifted scripting author, 

This is just a thought

If there was a first release of the new year that was going to SIGNIFICANTLY be a game changer, this is it. !!!!

Missing from your scripting is that Holy Grail Script that when run archives the configuration of the of all the installed APPS and the image configuration. 

I only wish that I was a script coder that could write a script that would do that archive the configurations, AND also RESTORE the configuration from previously archived configurations. 
alas, I am not such a gifed coder and at the mercy of those who are. 
ie. 
buconfig -l
This simply lists that configuration date and times that configurations were archived. 
buconfig 
when run without arguments, stores archived versions of the configuration files
buconfig -a -s /home/notmypi/
when run with the -a "archives the current configuration settings" and -s specifies the directory location that the archived configurations are stored. 
"normally" the archived configuration files are stored in /home/pi/archivedconfigs
buconfig -r -d 2020-01-24-00:00
when run with the -r it restores the most recently saved configuration files 
or when the -d specifies the date or date time, it restores the most recently saved configuration files after the specified date or datetime.
-----------
-s -d and other program flags can be used together to maximize the effectiveness of the configuration archive and restoration.
when run with flag "buconfig -a -d 2019-12-31" would archive the current configuration files stored as archived on 2019-12-31-2359
as to represent the last configuration for the year 2019.

Re: NWDR15 Image observations

Basil Gunn
 

Jim Erickson <jim@...> writes:

Wait until you get into the split channel stuff that Basil has been
working on. It’s game changing in that you can run APRS and FLdigi at
the same time, two different radios, same Raspberry Pi. Super Sweet.
Thanks Basil!
First, thank you Jim!
Second, attribution goes to Anna NH6Z as she created the split-channels
repo last April.

The scripts in the n7nix repo, split_install.sh, split_status.sh
split_toggle.sh, hopefully, make setting up Anna's stuff easier.

There is a difference in using the split-channels repo versus my scripts
in that the repo defaults to having HF use the left DRAWS mDin6
connector leaving the right connector for packet or udr0. This is
confusing (to me at least) because udr0 is normally on the left mDin6
connector. The scripts from the n7nix repository defaults to leaving
packet, udr0 on the left connector & using the right connector for HF.

Anyway I think it is kind of cool to have direwolf use only one of the
audio device ports & some HF program like FLdigi use the other. BTW, this
method should work for other sound card devices as well.

/Basil n7nix

------
73,
Jim
VA7SHG - Phone
VE7TGZ/VA7TGZ - Other

On Jan 23, 2020, at 09:59, Dave Christensen <dkc2030@...> wrote:

I had a little trouble finding the getting started stuff since it
wasn't a sticky message BUT I did find it and everything verifies OK
so far. The app to start and stop ax25 is a huge deal in simplifying
the operation of the HAT. Just ran it to change from APRS to FLdigi -
sweet.