Date   
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

Re: measure_deviate.sh not working on RPi4b

Basil Gunn
 

David, No problem. Always happy when I hear of a success. Also I will
fix the wiringpi version problem shortly. Thanks for that.
Seeing your beacons on aprs.fi from a few minutes ago.

2020-01-01 15:45:11 PST: KE7RGP-11>APUDR1,WIDE1-1,qAO,KE7RGP-1::KE7RGP :01 15:45:09 PST KE7RGP mesg_beacon test from host husky on port udr0 Seq: 1

/Basil

Never mind Basil, btest.sh and measure_deviation.sh are now both
working. Not sure what was going on awhile ago but I do need wiringpi
2.52 for the deviation script. Thanks and sorry for taking up your
time on the btest part of this.

Re: Update WSJTX #draws #wsjt-x

Basil Gunn
 

Showing console output always helps me understand the problem you may be
having.

cd
cd n7nix
git pull
cd hfprogs

# now run the hf version check program

./hf_verchk.sh

js8call: current version: 2.1.1, installed: 1.1.0
wsjtx: current version: 2.1.2, installed: 2.1.0
Library: libflxmlrpc IS loaded.
flxmlrpc: current version: 0.1.4, installed: 0.1.4
fldigi: current version: 4.1.08, installed: 4.1.08
flrig: current version: 1.3.48, installed: 1.3.48
flmsg: current version: 4.0.14, installed: 4.0.14
flamp: current version: 2.2.05, installed: 2.2.05
fllog: current version: 1.2.6, installed: NOT installed

# Now do the update
./hf_verchk.sh -u

# Run ./hf_verchk.sh again to verify

js8call: current version: 2.1.1, installed: 2.1.1
wsjtx: current version: 2.1.2, installed: 2.1.2
Library: libflxmlrpc IS loaded.
flxmlrpc: current version: 0.1.4, installed: 0.1.4
fldigi: current version: 4.1.08, installed: 4.1.08
flrig: current version: 1.3.48, installed: 1.3.48
flmsg: current version: 4.0.14, installed: 4.0.14
flamp: current version: 2.2.05, installed: 2.2.05
fllog: current version: 1.2.6, installed: 1.2.6

If wsjtx is still not updated I need to see all the console output from
the above.
/Basil

Justin Clark (KJ7JC) <jstnsclark@...> writes:

I have tried updating mu DRAWS but i still have WSJTX V2.1.0.

Any help on how i can update it to V2.1.2?

Re: measure_deviate.sh not working on RPi4b

 

Oh, ok, interesting on the three times suggestion.

Re: measure_deviate.sh not working on RPi4b

 

Yes, no movement on the Bird 43. Maybe there is an intermittent problem with the meter. I know there are other things to look at but that has been my go to.

Re: measure_deviate.sh not working on RPi4b

 

Never mind Basil, btest.sh and measure_deviation.sh are now both working. Not sure what was going on awhile ago but I do need wiringpi 2.52 for the deviation script. Thanks and sorry for taking up your time on the btest part of this.
David KE7RGP 

Re: measure_deviate.sh not working on RPi4b

Basil Gunn
 

Here are the steps that fix measure_deviate.sh but break btest.sh. I
went through a couple of cycles of turning ax25 on and off between
running the two scripts just to make sure.
Below is your btest.sh output which looks good. Can you be more specific
about what is broken? Are you not seeing your radio transmit? Also be
aware that when the AX.25 stack is first brought up the first 2 packets
transmitted are control packets and may not engage PTT. On start up
please run btest.sh at least 3 times before checking if your radio is
transmitting.

./btest.sh
*** Running as user: pi ***
Send a message beacon
Sent: /usr/local/sbin/beacon -c KE7RGP-11 -d 'APUDR1 via WIDE1-1' -l -s udr0 :KE7RGP :01 13:20:48 PST KE7RGP mesg_beacon test from host husky on port udr0 Seq: 0

Also I see your packets on aprs.fi and they look OK
https://aprs.fi/?c=raw&call=KE7RGP*&limit=50&view=normal

2020-01-01 13:26:46 PST: KE7RGP-11>APUDR1,WIDE1-1,qAR,KI7NLL::KE7RGP :01 13:26:44 PST KE7RGP mesg_beacon test from host husky on port udr0 Seq: 0%

/Basil n7nix

Update WSJTX #draws #wsjt-x

Justin Clark (KJ7JC)
 

I have tried updating mu DRAWS but i still have WSJTX V2.1.0.

Any help on how i can update it to V2.1.2?

Re: measure_deviate.sh not working on RPi4b

 

Here are the steps that fix measure_deviate.sh but break btest.sh. I went through a couple of cycles of turning ax25 on and off between running the two scripts just to make sure.

David KE7RGP

Re: measure_deviate.sh not working on RPi4b

Basil Gunn
 

On the Pi4b, the piwiz updater keeps giving an error, says a file is
“not (yet) available”. Seems a common problem and to try again. I got
tired of re-imaging the sd card and found these instructions to update
when encountering this problem:
I'll look into this. I usually run my RPis headless so don't run piwiz
updater. The configuration scripts I wrote do everything that piwiz
does.

This appears to work, or at least gives 20 minutes of verbosity.
Yes it's time to update the image so that doesn't happen.

measure_deviate does not work. I confirmed that gpio 12 (nor gpio 25)
gpio 23 not gpio 25

will go high. I’ve also tried manually setting the pins. All this
works with the Pi3 but not the Pi4b.
This is due to measure_deviate getting wiringpi from the Debian
repository instead of the authors personal repo. I'll fix that.

Looking at the WiringPi blog, they claim version 2.52 is needed and I
follow their wget instructions to load this version. This fixes
measure_deviate.sh but then btest.sh stops working.
Let me look at the console output when 'btest.sh stops working'
btest.sh doesn't use WiringPi so this is confusing. Make sure you are
starting ax25 back up (ax25-start) after using measure_deviate.
/Basil n7nix

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

Basil Gunn
 

Two problems:
with ax25 started I do a wl2kax25 - k2wvc-10 (a gateway on 2
met4ers). It connects but hangs after a Challenge is
received. Eventually it times out with jibberish and disconnects
Check /usr/local/etc/wl2k.conf
wl2k-password=
The winlink password you are using is invalid.

THE SECOND PROBLEM AS TO DO WITH NO HF AUDIO (AX25 STOPPED) on FLdigi,
JS8Call, etc. I can key the rig using FLdigi directed by the apps but
I am not generating any power. I ran measure_deviate.sh and it keys
the rig AND gives me 30 Watts out which is what I expect. I am using
the Left audio jack for both packet and HF - at lease that is what the
radio is connected to (IC-7000).
For FLDigi read this:
https://nw-digital-radio.groups.io/g/udrc/wiki/UDRC%E2%84%A2-and-fldigi-Setup-Page#Startup-and-set-levels-in-fldigi

The "Power" control in both apps is at the maximum. Below is a screen shot of WSJTX configs:

pi@kd7um-t2:~/bin $ arecord -l
**** List of CAPTURE Hardware Devices ****
card 1: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 []
Subdevices: 0/1
Subdevice #0: subdevice #0
pi@kd7um-t2:~/bin $

also touching any config parameter cause WSJTX to blow up and quit. I
am running WSJTX Version 2.1.0
Try running the latest version: 2.1.2

What am I missing? The apps both are hearing stations and they show up
in the app display so hearing works and talking (on HF) doesn't Thanks