Date   
Re: #ax25 #ax25

Basil Gunn
 

Really hard to tell what's going on when you give me snippets of the
console output. What you've shown me shows a complete install failure.

Are you installing from a clean NWDR14.img file?
Did you follow these instructions?
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started

Are you still trying to run install scripts using a clean Raspbian
buster image?

I recommend starting from the NWDR14.img and following the Getting
Started instructions. If you run into problems show me the entire
console output.

/Basil

Paul Noa <pauljnoa@...> writes:

On Sat, Jan 4, 2020 at 07:10 PM, Basil Gunn wrote:


I need to see the console output.
NWDR14 will be going away shortly & if there is a problem with the new
scripts, I need to fix it.
inflating: direwolf-dev/tnc-test-cd-results.png finishing deferred symbolic links: direwolf-dev/debian/changelog -> ../CHANGES.md make: *** No targets specified and no makefile found. Stop. make: *** No rule to make target 'install'. Stop. make: *** No rule to make target 'install-conf'. Stop. copying direwolf config file from source to /etc/direwolf.conf cp: cannot stat '/root/direwolf.conf': No such file or directory mv: cannot stat '/root/direwolf.conf': No such file or directory cp: cannot stat '/usr/local/bin/direwolf': No such file or directory Direwolf: config file NOT installed! copying direwolf config file from package to /etc/direwolf.conf cp: cannot stat '/usr/share/doc/direwolf/examples/direwolf.conf*': No such file or directory gzip: /etc/direwolf.conf.gz: No such file or directory core_install.sh: direwolf install failed!

Re: #ax25 #ax25

Paul Noa
 

On Sat, Jan 4, 2020 at 07:10 PM, Basil Gunn wrote:
I need to see the console output.
NWDR14 will be going away shortly & if there is a problem with the new
scripts, I need to fix it.
  inflating: direwolf-dev/tnc-test-cd-results.png finishing deferred symbolic links: direwolf-dev/debian/changelog -> ../CHANGES.md make: *** No targets specified and no makefile found. Stop. make: *** No rule to make target 'install'. Stop. make: *** No rule to make target 'install-conf'. Stop. copying direwolf config file from source to /etc/direwolf.conf cp: cannot stat '/root/direwolf.conf': No such file or directory mv: cannot stat '/root/direwolf.conf': No such file or directory cp: cannot stat '/usr/local/bin/direwolf': No such file or directory Direwolf: config file NOT installed! copying direwolf config file from package to /etc/direwolf.conf cp: cannot stat '/usr/share/doc/direwolf/examples/direwolf.conf*': No such file or directory gzip: /etc/direwolf.conf.gz: No such file or directory core_install.sh: direwolf install failed!

Re: #ax25 #ax25

Paul Noa
 

On Sat, Jan 4, 2020 at 07:10 PM, Basil Gunn wrote:
Which radio? (make, model number)
It would be good to have your transmit sensitivity which will allow you
to calculate the alsa values for optimum deviation.

ie. from the Kenwood manual
1200 bps: Transmit data input (PKD) sensitivity is 40 mV p-p , input impedance is 10 kΩ.
9600 bps: Transmit data input (PKD) sensitivity is 2 V p-p , input impedance is 10 kΩ.

Also does your radio have a data connector?
I will be using a Hyteria TM800-U , yes it has a data port. 
I have reached that step yet next week most likely.

Re: #ax25 #ax25

Paul Noa
 

~ $ systemctl status chronyd
● chrony.service - chrony, an NTP client/server
   Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2020-01-04 17:46:43 EST; 1h 32min ago
     Docs: man:chronyd(8)
           man:chronyc(1)
           man:chrony.conf(5)
 Main PID: 474 (chronyd)
    Tasks: 2 (limit: 2200)
   Memory: 1.6M
   CGroup: /system.slice/chrony.service
           ├─474 /usr/sbin/chronyd -F -1
           └─480 /usr/sbin/chronyd -F -1
 
Jan 04 17:46:43 asawizard systemd[1]: Starting chrony, an NTP client/server...
Jan 04 17:46:43 asawizard chronyd[474]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +S
Jan 04 17:46:43 asawizard chronyd[474]: Frequency -0.274 +/- 0.349 ppm read from /var/lib/chrony/chrony.drift
Jan 04 17:46:43 asawizard chronyd[474]: Loaded seccomp filter
Jan 04 17:46:43 asawizard systemd[1]: Started chrony, an NTP client/server.
Jan 04 17:47:16 asawizard chronyd[474]: Selected source 184.105.182.7
Jan 04 17:47:16 asawizard chronyd[474]: System clock wrong by 8.212573 seconds, adjustment started
Jan 04 17:47:25 asawizard chronyd[474]: System clock was stepped by 8.212573 seconds
Jan 04 17:48:31 asawizard chronyd[474]: Selected source 108.61.56.35
lines 1-22/22 (END)    

Re: #ax25 #ax25

Paul Noa
 

NO the gps is not working I read some messages under the #gpsd and did this:

sudo systemctl enable gpsd && sudo systemctl restart gpsd
Synchronizing state of gpsd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable gpsd
A dependency job for gpsd.service failed. See 'journalctl -xe' for details.

~/n7nix/debug $ ./btest.sh -g
*** Running as user: pi ***
Verify gpsd is returning sentences: Sentence count: 3
Test nmea sentence:

Nothing else happened

Re: #ax25 #ax25

Basil Gunn
 

No luck with your fix core_install.sh
I need to see the console output.
NWDR14 will be going away shortly & if there is a problem with the new
scripts, I need to fix it.

so regardless, I started fresh with the NWDR14 image and everything
went well!
Is the gps working?
https://github.com/nwdigitalradio/n7nix/blob/master/docs/VERIFY_CONFIG.md#check-gps
or run
cd
cd n7nix/debug
./btest.sh -g

, no errors, at least to the point of testing AX25 with a radio
attached which I do not have ready just yet.
Which radio? (make, model number)
It would be good to have your transmit sensitivity which will allow you
to calculate the alsa values for optimum deviation.

ie. from the Kenwood manual
1200 bps: Transmit data input (PKD) sensitivity is 40 mV p-p , input impedance is 10 kΩ.
9600 bps: Transmit data input (PKD) sensitivity is 2 V p-p , input impedance is 10 kΩ.

Also does your radio have a data connector?

/Basil


Thanks!

However, when I run gpsmon I do not get the screen with the satellites but :

tcp://localhost:2947 JSON slave driver> (82) {"class":"VERSION","release":"3.19","rev":"3.19","proto_major":3,"proto_minor":14} (171) {"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/ttySC0","activated":"2020-01-04T22:56:30.339Z","native":0,"bps":9600,"parity":"N","stopbits":1,"cycle":1.00}]} (122) {"class":"WATCH","enable":true,"json":false,"nmea":false,"raw":2,"scaled":false,"timing":false,"split24":false,"pps":true}

And as expected my mapping software does not see the GPS signal either probably related.
Any Ideas??

Paul

Re: #ax25 #ax25

Paul Noa
 

Basil,

No luck with your fix core_install.sh so regardless, I started fresh with the NWDR14 image and everything went well!, no errors, at least to the point of testing AX25 with a radio attached which I do not have ready just yet.

Thanks!

However, when I run gpsmon I do not get the screen with the satellites but :

tcp://localhost:2947 JSON slave driver> (82) {"class":"VERSION","release":"3.19","rev":"3.19","proto_major":3,"proto_minor":14} (171) {"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/ttySC0","activated":"2020-01-04T22:56:30.339Z","native":0,"bps":9600,"parity":"N","stopbits":1,"cycle":1.00}]} (122) {"class":"WATCH","enable":true,"json":false,"nmea":false,"raw":2,"scaled":false,"timing":false,"split24":false,"pps":true} 

And as expected my mapping software does not see the GPS signal either probably related.
Any Ideas??

Paul



Re: #ax25 #ax25

Basil Gunn
 

My goal was to have functionality limited to the DRAWS Core and AX25
Direwolf, which is why I proceeded from a clean image and attempted to
configure only those portions. Can I presume that the image you
referred has all functionality, not limited to just DRAWS Core and
AX25 Direwolf?
While the nwdr14 image has a lot in it, not much is running and is
perfectly safe to run headless ax.25 apps.

The image contents is for support reasons extensive.
I believe you will find it much easier to use the image and just run
core config.

https://github.com/nwdigitalradio/n7nix/blob/master/docs/DRAWS_CONFIG.md#initial-configuration

The above doc is the same as the Getting Started Guide in the groups.io
udrc wiki.
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started

Ran your Script:

Re: #ax25 #ax25

Paul Noa
 

Basil,

My goal was to have functionality limited to the DRAWS Core and AX25 Direwolf, which is why I proceeded from a clean image and attempted to configure only those portions.  Can I presume that the image you referred has all functionality, not limited to just DRAWS Core and AX25 Direwolf? 

Ran your Script:

:~/n7nix $ git pull
remote: Enumerating objects: 23, done.
remote: Counting objects: 100% (23/23), done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 16 (delta 12), reused 16 (delta 12), pack-reused 0
Unpacking objects: 100% (16/16), done.
From https://github.com/nwdigitalradio/n7nix
   3b1d2f6..d719c2a  master     -> origin/master
Updating 3b1d2f6..d719c2a
Fast-forward
 ax25/ax_verchk.sh         | 51 +++++++++++++++++++++++++++++++++++++++++++--------
 config/core_install.sh    | 14 +++++++++++---
 docs/RMSGW_DAILY_CHECK.md |  2 +-
 3 files changed, 55 insertions(+), 12 deletions(-)

Thanks, I will test the config now.
Paul

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