Date   

Re: wlgw-check.sh

 

Thank you for the power advice. It looks like I might be able to mod the script to read and save the current power setting, set it to medium for the gateway interrogation, then set it back to the original power. The following works with my rig to set H, M and L respectively:

pi@husky:~/auto-rmsgw-find $ /usr/local/bin/rigctl -r /dev/ttyUSB0 -m 234 L RFPOWER 1.000000
pi@husky:~/auto-rmsgw-find $ /usr/local/bin/rigctl -r /dev/ttyUSB0 -m 234 l RFPOWER
1.000000
pi@husky:~/auto-rmsgw-find $ /usr/local/bin/rigctl -r /dev/ttyUSB0 -m 234 L RFPOWER 0.500000
pi@husky:~/auto-rmsgw-find $ /usr/local/bin/rigctl -r /dev/ttyUSB0 -m 234 l RFPOWER
0.500000
pi@husky:~/auto-rmsgw-find $ /usr/local/bin/rigctl -r /dev/ttyUSB0 -m 234 L RFPOWER 0.000000
pi@husky:~/auto-rmsgw-find $ /usr/local/bin/rigctl -r /dev/ttyUSB0 -m 234 l RFPOWER
0.000000
pi@husky:~/auto-rmsgw-find $ 


I should set up a gateway. let me read about what the responsibilities are. I can only get to one gateway without using a digipeater. Our network is baroque. I like how you get a dynamic picture of the network with this script. Not sure how to incorporate digipeaters other than a static list of gateways with their bridging digipeater.

David KE7RGP


Re: wlgw-check.sh

Basil Gunn
 

A couple of things.
The wlgw-check.sh script can utilize the duty cycle on your TM-V71a A LOT. I recommend
only using medium power.

Just checked in a fix for this:
./wlgw-check.sh: line 236: [: missing `]'
here:
https://github.com/n7nix/auto-rmsgw-find/commit/9ebb02da8b142a918fe3a4873c1965ca71c76e52

The following line sets the TM-V71 memory channel back to the frequency my RMS
Gateway runs on. Modify that line & any other frequencies in the
freqlist_digi.txt file to suite your needs.

set_memchan_index 35

Yikes, not a lot of RMS Gateways near your! If you want to use your
RPi/DRAWS board as an RMS Gateway I'll help you set it up.

./rmslist.sh 60 DN06ig

Using distance of 60 miles & grid square DN06IG

Callsign Frequency Distance Baud
WA7FC-10 144990000 12 1200
AL1Q-10 145070000 50 1200

/Basil n7nix


David Lowry <huskyrunnr@...> writes:

Success! I'll try to lay off the bandwidth here on the board for awhile ...

pi@husky:~/auto-rmsgw-find $ ./wlgw-check.sh
Using existing /home/pi/tmp/rmsgw_stats.log
We are here: lat: 46.262408333, lon: -119.330283333

Refreshing RMS List

Using VFOA as data radio
In Mem channel mode
Current Chan: 35, name: , chan freq: , Frequency: 144390000
./wlgw-check.sh: line 236: [: missing `]'

Start: 2020 01 03 13:47:28 PST: grid: DN06ig, debug: , GW list refresh: true, connect: true, cron: false

ChanConn
RMS GW Freq Dist Name Index Stat Stat Time Conn
Set VFO radio band to 2M
./wlgw-check.sh: line 236: [: missing `]'
Connected to AX.25 stack
Child process
wl2kax25: ---

wl2kax25: <[WL2K-5.0-B2FWIHJM$]
wl2kax25: sid [WL2K-5.0-B2FWIHJM$] inboundsidcodes -B2FWIHJM$
wl2kax25: <;PQ: 91349643
wl2kax25: Challenge received: 91349643
wl2kax25: <CMS via WA7FC >
wl2kax25: >[UnixLINK-0.8-B2FIHM$]
wl2kax25: >;PR: 97165653
wl2kax25: >; WA7FC-10 DE KE7RGP QTC 0
wl2kax25: >FF
wl2kax25: <FQ [2]
Child process exiting
EOF on child fd, terminating communications loop.
Closing ax25 connection
Child exit status: 0
Waiting for AX25 peer ... timeout
WA7FC-10 144990000 12 NET-11 n/a OK 28 1
Number of gateways: in array: 1, in list 1 /home/pi/tmp/rmsgwprox.txt

Finish: 2020 01 03 13:47:56 PST: Elapsed time: 0 min, 28 secs, Found 1 RMS Gateways, connected: 1

Setting radio back to original memory channel 35
pi@husky:~/auto-rmsgw-find $


Re: #ax25 #ax25

Basil Gunn
 

Paul,
A few days ago I updated the ax.25 lib/apps/tools packages to the latest
versions ... and forgot to update the core_install.sh script. I'll
change it so the package names are not hard coded in that script.

The install scripts are for the use case where you are starting from a
clean raspbian buster image. The supplied image (http://nwdig.net/downloads/)
has already run all the install scripts and only requires configuration.

This link points to the best instructions to follow for configuring a
UDRC/DRAWS image: nwdr14.zip

https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started

Install scripts are mainly used by me to create an new image from
raspbian. The install scripts are not as refined as the configuration
scripts which have been run by more people.

I've checked in a fix to the core_install.sh script but perhaps you can
get back to me what you are trying to do & what your expectation is.

You can get my core_install.sh fix by:
cd
cd n7nix
git pull

/Basil


Paul Noa <pauljnoa@...> writes:

Attempting a core_install using the alternate method on my unit number 2, I used the "Install Everything" method on Unit number 1 with success.

However this time I am experiencing an issue with the core install see below:

root@raspberrypi:/home/pi/n7nix/config# ./core_install.sh
Initial core install script
HAT product id: 4
=== Check build tools
Build Tools packages installed.
=== Check for non essential packages
Non essential packages installed.
=== enable modules
=== Modify /boot/config.txt

File: /boot/config.txt NOT modified: prod_id=4

=== Install libax25, ax25apps & ax25tools
Installing from this directory /home/pi/n7nix
dpkg: error: cannot access archive './ax25/debpkg/libax25_1.1.0-1_armhf.deb': No such file or directory
dpkg: error: cannot access archive './ax25/debpkg/ax25apps_1.0.5-1_armhf.deb': No such file or directory
dpkg: error: cannot access archive './ax25/debpkg/ax25tools_1.0.3-1_armhf.deb': No such file or directory
Check ax25 config dir
ax25 directory /usr/local/etc/ax25 DOES NOT exist, ax25 install failed

Any suggestions other than going directly to Direwolf ?

Thanks in advance for your support.

Paul


Re: wlgw-check.sh

 

Success! I'll try to lay off the bandwidth here on the board for awhile ...

pi@husky:~/auto-rmsgw-find $ ./wlgw-check.sh
Using existing /home/pi/tmp/rmsgw_stats.log
We are here: lat: 46.262408333, lon: -119.330283333
 
Refreshing RMS List
 
Using VFOA as data radio
In Mem channel mode
Current Chan: 35, name: , chan freq: , Frequency: 144390000
./wlgw-check.sh: line 236: [: missing `]'
 
Start: 2020 01 03 13:47:28 PST: grid: DN06ig, debug: , GW list refresh: true, connect: true, cron: false
 
ChanConn
RMS GW     Freq Dist Name Index Stat Stat Time  Conn
  Set VFO radio band to 2M
./wlgw-check.sh: line 236: [: missing `]'
Connected to AX.25 stack
Child process
wl2kax25: ---
 
wl2kax25: <[WL2K-5.0-B2FWIHJM$]
wl2kax25: sid [WL2K-5.0-B2FWIHJM$] inboundsidcodes -B2FWIHJM$
wl2kax25: <;PQ: 91349643
wl2kax25: Challenge received: 91349643
wl2kax25: <CMS via WA7FC >
wl2kax25: >[UnixLINK-0.8-B2FIHM$]
wl2kax25: >;PR: 97165653
wl2kax25: >; WA7FC-10 DE KE7RGP QTC 0
wl2kax25: >FF
wl2kax25: <FQ [2]
Child process exiting
EOF on child fd, terminating communications loop.
Closing ax25 connection
Child exit status: 0
Waiting for AX25 peer ... timeout
WA7FC-10    144990000 12 NET-11           n/a   OK 28   1
Number of gateways: in array: 1, in list 1 /home/pi/tmp/rmsgwprox.txt
 
Finish: 2020 01 03 13:47:56 PST: Elapsed time: 0 min, 28 secs,  Found 1 RMS Gateways, connected: 1
 
Setting radio back to original memory channel 35
pi@husky:~/auto-rmsgw-find $ 
 


Re: wlgw-check.sh

 

Progress: somehow the rig was not allowing me to switch between vfo mode and memory mode, even with the buttons. wlgw-check.sh ran, found my one gateway. Looks like complaining about memory index 35. I'll look back on your instructions about that here on the message board.

pi@husky:~/auto-rmsgw-find $ ./wlgw-check.sh
Using existing /home/pi/tmp/rmsgw_stats.log
We are here: lat: 46.262408333, lon: -119.330283333
 
Refreshing RMS List
 
Using VFOA as data radio
In Mem channel mode
Current Chan: 0, name: , chan freq: , Frequency: 144390000
./wlgw-check.sh: line 236: [: missing `]'
 
Start: 2020 01 03 13:34:27 PST: grid: DN06ig, debug: , GW list refresh: true, connect: true, cron: false
 
ChanConn
RMS GW     Freq Dist Name Index Stat Stat Time  Conn
  Set VFO radio band to 2M
RIG CTRL ERROR[0]: set memory index: 35, TOut: 5, error:set_mem: error = Feature not available
./wlgw-check.sh: line 236: [: missing `]'
Failed to set frequency: 144990000 for Gateway: WA7FC-10, read freq: 144390000
 
Call to wl2kax25 timed out
 
WA7FC-10    144990000 12 NET-11           n/a   to   5   0
Number of gateways: in array: 0, in list 1 /home/pi/tmp/rmsgwprox.txt
 
Finish: 2020 01 03 13:34:33 PST: Elapsed time: 0 min, 6 secs,  Found 1 RMS Gateways, connected: 0
 
Setting radio back to original memory channel 0
pi@husky:~/auto-rmsgw-find $ 


#ax25 #ax25

Paul Noa
 

Attempting a core_install using the alternate method on my unit number 2, I used the "Install Everything" method on Unit number 1 with success.

However this time I am experiencing an issue with the core install see below:

root@raspberrypi:/home/pi/n7nix/config# ./core_install.sh
Initial core install script
HAT product id: 4
 === Check build tools
Build Tools packages installed.
=== Check for non essential packages
Non essential packages installed.
 === enable modules
 === Modify /boot/config.txt
 
        File: /boot/config.txt NOT modified: prod_id=4
 
 === Install libax25, ax25apps & ax25tools
Installing from this directory /home/pi/n7nix
dpkg: error: cannot access archive './ax25/debpkg/libax25_1.1.0-1_armhf.deb': No such file or directory
dpkg: error: cannot access archive './ax25/debpkg/ax25apps_1.0.5-1_armhf.deb': No such file or directory
dpkg: error: cannot access archive './ax25/debpkg/ax25tools_1.0.3-1_armhf.deb': No such file or directory
Check ax25 config dir
ax25 directory /usr/local/etc/ax25 DOES NOT exist, ax25 install failed

Any suggestions other than going directly to Direwolf ?

Thanks in advance for your support.

Paul


wlgw-check.sh

 

Here is as far as I can get. The rig has no memory channels programmed. Is that still an issue? I think I put all files and scripts in the proper directories, at least there are no more complaints about it. Thanks for you time.
David KE7RGP

pi@husky:~/auto-rmsgw-find $ ./wlgw-check.sh -d
Using existing /home/pi/tmp/rmsgw_stats.log
Set debug flag
Found gpsd
We are here: lat: 46.262408333, lon: -119.330283333
Using grid square: DN06ig
 
Refreshing RMS List
 
Data is on band 0
Using VFOA as data radio
Set vfo mode to MEM
RIG CTRL ERROR: MEM mode=VFOA, error:set_vfo: error = Feature not available
pi@husky:~/auto-rmsgw-find $ 
 


Re: #hamlib commands fail with RPi4b #hamlib

Basil Gunn
 

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
persistent across plug events.
Yep, this is a good thing to do and the script dev-check.sh in repo
auto-rmsgw-find verifys that the symlink device name matches the
expected device name used in wlgw-check.sh.

/Basil


Re: #hamlib commands fail with RPi4b #hamlib

 

Thank you Mitch, I will study this approach.

david Ke7rgp 


Re: #hamlib commands fail with RPi4b #hamlib

Mitch Winkle
 

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 persistent across plug events.


On 1/3/2020 12:37, Basil Gunn wrote:
David Lowry <huskyrunnr@...> writes:

Thanks, Basil, I was using dmesg, lsusb and ls /dev/ttyUSB*. The cable
enumerated as ttyUSB0. Somehow, after unplugging and checking the
cable with chirp and windows, the rigctl commands worked. It was even
the same rigctl commands before and after chirp, I used the arrow up
key rather than retype the command. the rig had never seen chirp
before, maybe all the plugging and unplugging did something to the
rig. I had pc speed set to max.
If this problem occurs again run a new script I put in repo auto-rmsgw-find

cd auto-rmsgw-find
git pull
./dev-check.sh
# Expected output
Found 1 USB serial device(s) on this system.
Device: ttyUSB0, config: ttyUSB0: matches

# Expected output with no usb serial devices
./dev-check.sh
Found 0 USB serial device(s) on this system.

yes, I meant wlgw-check.sh in auto-rmsgw-find dir. Neat work!

If things go awry again, I’ll do a better job documenting. Right now, all is working.
Great to hear!

How should I easily copy the contents of auto-rmsgw-find to the pi in
one fell swoop? I was thinking make the same directory and git pull?
Then I need to run the make file for the c-program?
# Pick some place in your directory path ie. your home root, and clone the
repository

cd
git clone https://github.com/n7nix/auto-rmsgw-find

# Now go to the gridsq directory & build latlon2grid
cd auto-rmsgw-find/gridsq
make

# run some scripts
cd ..
./dev-check.sh

# If you have a gps
./wlgw-check.sh

# If you do not have a gps
./wlgw-check.sh -g <your_grid_square>

# Display command line options:
./wlgw-check.sh -h
Using existing /home/gunn/tmp/rmsgw_stats.log
Usage: wlgw-check.sh [-g <gridsquare>][-v][-h]
 If no gps is found, gridsquare must be entered.
   -g <gridsquare> | --gridsquare
   -d | --debug      display debug messages
   -r | --no_refresh use existing RMS Gateway list
   -s | --stats      display statistics
   -t | --test       test rig ctrl with NO connect
   -h | --help       display this message

/Basil n7nix





Re: #hamlib commands fail with RPi4b #hamlib

Basil Gunn
 

David Lowry <huskyrunnr@...> writes:

Thanks, Basil, I was using dmesg, lsusb and ls /dev/ttyUSB*. The cable
enumerated as ttyUSB0. Somehow, after unplugging and checking the
cable with chirp and windows, the rigctl commands worked. It was even
the same rigctl commands before and after chirp, I used the arrow up
key rather than retype the command. the rig had never seen chirp
before, maybe all the plugging and unplugging did something to the
rig. I had pc speed set to max.
If this problem occurs again run a new script I put in repo auto-rmsgw-find

cd auto-rmsgw-find
git pull
./dev-check.sh
# Expected output
Found 1 USB serial device(s) on this system.
Device: ttyUSB0, config: ttyUSB0: matches

# Expected output with no usb serial devices
./dev-check.sh
Found 0 USB serial device(s) on this system.

yes, I meant wlgw-check.sh in auto-rmsgw-find dir. Neat work!

If things go awry again, I’ll do a better job documenting. Right now, all is working.
Great to hear!

How should I easily copy the contents of auto-rmsgw-find to the pi in
one fell swoop? I was thinking make the same directory and git pull?
Then I need to run the make file for the c-program?
# Pick some place in your directory path ie. your home root, and clone the
repository

cd
git clone https://github.com/n7nix/auto-rmsgw-find

# Now go to the gridsq directory & build latlon2grid
cd auto-rmsgw-find/gridsq
make

# run some scripts
cd ..
./dev-check.sh

# If you have a gps
./wlgw-check.sh

# If you do not have a gps
./wlgw-check.sh -g <your_grid_square>

# Display command line options:
./wlgw-check.sh -h
Using existing /home/gunn/tmp/rmsgw_stats.log
Usage: wlgw-check.sh [-g <gridsquare>][-v][-h]
If no gps is found, gridsquare must be entered.
-g <gridsquare> | --gridsquare
-d | --debug display debug messages
-r | --no_refresh use existing RMS Gateway list
-s | --stats display statistics
-t | --test test rig ctrl with NO connect
-h | --help display this message

/Basil n7nix


Re: #hamlib commands fail with RPi4b #hamlib

 

Thanks, Basil, I was using dmesg, lsusb and ls /dev/ttyUSB*. The cable enumerated as ttyUSB0. Somehow, after unplugging and checking the cable with chirp and windows, the rigctl commands worked. It was even the same rigctl commands before and after chirp, I used the arrow up key rather than retype the command. the rig had never seen chirp before, maybe all the plugging and unplugging did something to the rig. I had pc speed set to max.

yes, I meant wlgw-check.sh in auto-rmsgw-find dir. Neat work!

If things go awry again, I’ll do a better job documenting. Right now, all is working.

How should I easily copy the contents of auto-rmsgw-find to the pi in one fell swoop? I was thinking make the same directory and git pull? Then I need to run the make file for the c-program?

david Ke7rgp 


Re: #hamlib commands fail with RPi4b #hamlib

Basil Gunn
 

verify that device is enumerated on your system
# To see which USB serial device has been enumerated

ls /dev/U*
Sorry not that, try following, coffee hasn't kicked in yet.

ls /dev/ttyU*
/dev/ttyUSB0


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

Basil Gunn
 

Hi Dave,
Sorry for the lag.

I had the correct Winlink password as I connected via telnet OK. I
tried the same gateway that failed yesterday and it worked. I suspect
that gateway could not validate my password. So, check that one off
the list.
Call sign of the gateway?

Regarding getting FLdigi and WSJT-X to transmit with audio - not
working and in fact when I have FLdigi and FLrig and Draws Manager
running my system hangs up rock solid and I have to power off to get
things running again. I think I am going to put DRAWS on pause,
perhaps wait until version 15 is available of start from scratch with
Version 14.
If you get a chance show me the output of:

free -m

When your system hangs, assuming you are running with a video monitor,
try ssh'ing into your system and running the above command.
Also keep cables plugged into your RPi away from your radio
antenna. ie. make sure the cables plugged into the DRAWS hat are not
laying on top of your feed line coax.

The radio was keying up (Using FLrig for PTT) but no audio - and in
fact it was picking up audio from the microphone rather than the data
jack from Draw to rig. Something has to be right because I can run
wl2k and connect to a gateway using the same radio I am using for
FLDigi. I did stop ax25 between the WL2K-VHF and trying FLDigi.

Thanks for your help. I can't imagine the load you are carrying trying
to improve the software surrounding DRAWS and answering questions from
dummies like me.
I haven't given up, I just need to give it a break.
OK. You have some things working and I'm pretty confident we can solve the
HF program config issues whenever you come back to it.

I have another Pi/Signalink setup that is working beautifully. I know
it can be done with Draws. Happy New Year
Thanks Dave!
/Basil n7nix


Re: #hamlib commands fail with RPi4b #hamlib

Basil Gunn
 

I don’t know where to go from here.
The script wlgw-check.sh uses rigctl and that uses a serial device

From the script
SERIAL_DEVICE="/dev/ttyUSB0"

verify that device is enumerated on your system. If you have
plugged/unplugged a USB serial device you will notice that the serial
device name changes ie. to /dev/ttyUSB1

# To see which USB serial device has been enumerated

ls /dev/U*

I‘ve been studying the very interesting auto-rmsgw-find.sh script. I
tried some of the rigctl commands with TM-V71a. Nothing but timeouts.
Most likely using the wrong serial port name ie. /dev/ttyUSB0

My cable is rts with the FTDI eeprom flashed to generic ID. Chirp on
windows reads the rig. On a whim, I threw on the RPi3b and all the
rigctl commands I tried work fine: “f”, “v”, “_”.

On the RPi4b, I had successfully installed and set up paclink-Unix. I
have not done so on the RPi3b.
For this script I am running everything on: Pi 3 Model B, Rev 1.2, Mfg
by Sony UK, it is the N7NIX-10 RMS Gateway.

Honestly, I don’t know what output would be useful to show here,
Always start with the console output showing the problem.

or whether I should take this issue to some Hamlib support group.


Re: #hamlib commands fail with RPi4b #hamlib

 

Well, switched back to the 4b and the rigctl commands now work. No idea ... 


#hamlib commands fail with RPi4b #hamlib

 

I don’t know where to go from here. I‘ve been studying the very interesting auto-rmsgw-find.sh script. I tried some of the rigctl commands with TM-V71a. Nothing but timeouts. My cable is rts with the FTDI eeprom flashed to generic ID. Chirp on windows reads the rig. On a whim, I threw on the RPi3b and all the rigctl commands I tried work fine: “f”, “v”, “_”.

On the RPi4b, I had successfully installed and set up paclink-Unix. I have not done so on the RPi3b.

Honestly, I don’t know what output would be useful to show here, or whether I should take this issue to some Hamlib support group.

David KE7RGP 


Re: Update WSJTX #draws #wsjt-x

Justin Clark (KJ7JC)
 

That did it!!! THANKS!

Your the man Basil!


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

Dave Christensen
 

I had the correct Winlink password as I connected via telnet OK.  I tried the same gateway that failed yesterday and it worked.  I suspect that gateway could not validate my password.  So, check that one off the list.

Regarding getting FLdigi and WSJT-X to transmit with audio - not working and in fact when I have FLdigi and FLrig and Draws Manager running my system hangs up rock solid and I have to power off to get things running again.  I think I am going to put DRAWS on pause, perhaps wait until version 15 is available of start from scratch with Version 14.

The radio was keying up (Using FLrig for PTT) but no audio - and in fact it was picking up audio from the microphone rather than the data jack from Draw to rig.  Something has to be right because I can run wl2k and connect to a gateway using the same radio I am using for FLDigi.  I did stop ax25 between the WL2K-VHF and trying FLDigi.

Thanks for your help.  I can't imagine the load you are carrying trying to improve the software surrounding DRAWS and answering questions from dummies like me.  I haven't given up, I just need to give it a break.  I have another Pi/Signalink setup that is working beautifully.  I know it can be done with Draws.  Happy New Year


Re: Script for Linux RMS Gateway daily report

Basil Gunn
 

A few weeks ago you mentioned a script for alerting who has used the
RMS gateway. Can you please share that script with me so I can do the
same?

Brendan KM4HRR
https://github.com/nwdigitalradio/n7nix/blob/master/docs/RMSGW_DAILY_CHECK.md

/Basil n7nix