Date   

Re: DRAWS™ Manager Demo #drawsmanager

Charlie Hein
 

I'm not sure I follow, John.

"What is the response to
which node
which npm"

Are there specific commands I should know?

Charlie


Re: which instance of 'direwolf.conf' should I be using?

Basil Gunn
 

I've been told that I need to configure the Pi to NOT use
the radio ports on the DRAWS card, but instead use the USB connection
to connect to my FT-991A's internal sound card.

I've sorted out the new ttyUSBx ports and the CODEC audio card that
lives on this connection and I'm manually putting it into the .conf
file to connect to the radio in lieu of how the config script set
things up.
OK. Good luck.
I assume you found the direwolf config file here: /etc/direwolf.conf


Re: DRAWS™ Manager Demo #drawsmanager

 

What is the response to

which node
which npm


On Wed, Jul 29, 2020 at 10:08 AM Charlie Hein <chein@...> wrote:
Here's the output from the command:

pi@nvdpi:~ $ sudo systemctl status draws-manager
● draws-manager.service - DRAWS™ Manager - A web application to manage the DRAW™
   Loaded: loaded (/etc/systemd/system/draws-manager.service; enabled; vendor pr
   Active: failed (Result: exit-code) since Wed 2020-07-29 11:31:46 CDT; 30min a
  Process: 1709 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)
 Main PID: 1709 (code=exited, status=1/FAILURE)
 
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! errno 1
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! webapp@0.0.1 start: `node ./bin/www`
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! Exit status 1
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR!
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! Failed at the webapp@0.0.1 start scrip
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! This is probably not a problem with np
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! A complete log of this run can be foun
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR!     /root/.npm/_logs/2020-07-29T16_31_
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Main process exited, co
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Failed with result 'exi
lines 1-17/17 (END)...skipping...
● draws-manager.service - DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration.
   Loaded: loaded (/etc/systemd/system/draws-manager.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-07-29 11:31:46 CDT; 30min ago
  Process: 1709 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)
 Main PID: 1709 (code=exited, status=1/FAILURE)
 
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! errno 1
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! webapp@0.0.1 start: `node ./bin/www`
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! Exit status 1
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR!
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! Failed at the webapp@0.0.1 start script.
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! A complete log of this run can be found in:
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR!     /root/.npm/_logs/2020-07-29T16_31_46_715Z-debug.log
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Main process exited, code=exited, status=1/FAILURE
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Failed with result 'exit-code'.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
 
pi@nvdpi:~ $ 
 



--
John D. Hays
Kingston, WA
K7VE

 


Re: DRAWS™ Manager Demo #drawsmanager

Charlie Hein
 

Here's the output from the command:

pi@nvdpi:~ $ sudo systemctl status draws-manager
● draws-manager.service - DRAWS™ Manager - A web application to manage the DRAW™
   Loaded: loaded (/etc/systemd/system/draws-manager.service; enabled; vendor pr
   Active: failed (Result: exit-code) since Wed 2020-07-29 11:31:46 CDT; 30min a
     Docs: https://github.com/nwdigitalradio/draws-manager
  Process: 1709 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)
 Main PID: 1709 (code=exited, status=1/FAILURE)
 
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! errno 1
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! webapp@0.0.1 start: `node ./bin/www`
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! Exit status 1
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR!
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! Failed at the webapp@0.0.1 start scrip
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! This is probably not a problem with np
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! A complete log of this run can be foun
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR!     /root/.npm/_logs/2020-07-29T16_31_
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Main process exited, co
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Failed with result 'exi
lines 1-17/17 (END)...skipping...
● draws-manager.service - DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration.
   Loaded: loaded (/etc/systemd/system/draws-manager.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-07-29 11:31:46 CDT; 30min ago
     Docs: https://github.com/nwdigitalradio/draws-manager
  Process: 1709 ExecStart=/usr/bin/npm start (code=exited, status=1/FAILURE)
 Main PID: 1709 (code=exited, status=1/FAILURE)
 
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! errno 1
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! webapp@0.0.1 start: `node ./bin/www`
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! Exit status 1
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR!
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! Failed at the webapp@0.0.1 start script.
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! A complete log of this run can be found in:
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR!     /root/.npm/_logs/2020-07-29T16_31_46_715Z-debug.log
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Main process exited, code=exited, status=1/FAILURE
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Failed with result 'exit-code'.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
 
pi@nvdpi:~ $ 
 


Re: DRAWS not found

Keating Floyd
 

I believe I was following the getting started guide - but it is possible I did an upgrade first.  I will do exactly as you suggest!

Keating

On Wed, Jul 29, 2020 at 11:40 AM Basil Gunn <basil@...> wrote:
Keating,

Using the same Raspberry Pi version & DRAWS hat version as you I booted
a fresh NWDR16 image and could not replicate your symptom.

The first thing to do after booting a new image is to run
aplay -l
which will tell you if the driver and overlays have loaded properly.
This is described in the Getting Started Guide
https://nw-digital-radio.groups.io/g/udrc/wiki/8921

What where the steps you took after your first boot of a new image?
ie. did you run apt-get update, or raspi-config, or pi-wiz setup?

I would like you to try and replicate what I did which is to burn the
image, boot & run aplay -l so that we can figure out what is causing
your problem.

 $ udrcver.sh
Found a DRAWS

     HAT ID EEPROM
Name:        hat
Product:     Digital Radio Amateur Work Station
Product ID:  0x0004
Product ver: 0x0204
UUID:        4a0b1dce-358e-4b50-a372-1118a9ecbfed
Vendor:      NW Digital Radio

pi@raspberrypi:~ $ piver.sh
 Pi 4 Model B, Rev 1.1, 4GB mem, Mfg by Sony UK
 Has WiFi

pi@raspberrypi:~ $ aplay -l | grep udrc
card 2: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]

/Basil n7nix

Keating Floyd <kc4hsi@...> writes:

> Hi, Basil, and thanks!
>
> Yes, I have a wireless keyboard dongle plugged in there.
>
> Keating
>
>
> On Tue, Jul 28, 2020, 9:36 PM Basil Gunn <basil@...> wrote:
>
>>
>> Keating,
>> I am looking into your problem.
>> Could you please tell me if you have anything plugged into the USB
>> ports on your RPi 4.
>> Thanks,
>> /Basil
>>
>> Keating Floyd <kc4hsi@...> writes:
>>
>> > Included is the output from showudrc.sh. I was concerned that I had a
>> problem with my image perhaps, but I own a second DRAWS, and it shows up
>> just fine.
>> >
>> > Thanks for a great product, and for your help.
>> >
>> > Keating
>> >
>> > ===
>> >
>> > root@pi4b4g01:/home/pi/n7nix/hfprogs# cat showudrc.sh_out
>> > ==== Sound Card ====
>> > No udrc sound card found.
>> > ==== Pi Ver ====
>> > Pi 4 Model B, Rev 1.1, 4GB mem, Mfg by Sony UK
>> > Has WiFi
>> > ==== udrc Ver ====
>> > Found a DRAWS
>> >
>> > HAT ID EEPROM
>> > Name:    hat
>> > Product:  Digital Radio Amateur Work Station
>> > Product ID: 0x0004
>> > Product ver: 0x0204




Re: DRAWS™ Manager Demo #drawsmanager

 

Look at the output of
systemctl status draws-manager

On Wed, Jul 29, 2020 at 9:57 AM Charlie Hein <chein@...> wrote:
Watched the Demo Video, got excited, but when I try to run draws-manager from either a desktop or localhost, I get this:

 

I've tried stopping and restarting draws-manager to no avail.

Charlie



--
John D. Hays
Kingston, WA
K7VE

 


Re: DRAWS™ Manager Demo #drawsmanager

Charlie Hein
 

Watched the Demo Video, got excited, but when I try to run draws-manager from either a desktop or localhost, I get this:

 

I've tried stopping and restarting draws-manager to no avail.

Charlie


Re: which instance of 'direwolf.conf' should I be using?

Charlie Hein
 

Hi Basil - I've been told that I need to configure the Pi to NOT use the radio ports on the DRAWS card, but instead use the USB connection to connect to my FT-991A's internal sound card.  I've sorted out the new ttyUSBx ports and the CODEC audio card that lives on this connection and I'm manually putting it into the .conf file to connect to the radio in lieu of how the config script set things up.

Charlie 


Re: DRAWS not found

Basil Gunn
 

Keating,

Using the same Raspberry Pi version & DRAWS hat version as you I booted
a fresh NWDR16 image and could not replicate your symptom.

The first thing to do after booting a new image is to run
aplay -l
which will tell you if the driver and overlays have loaded properly.
This is described in the Getting Started Guide
https://nw-digital-radio.groups.io/g/udrc/wiki/8921

What where the steps you took after your first boot of a new image?
ie. did you run apt-get update, or raspi-config, or pi-wiz setup?

I would like you to try and replicate what I did which is to burn the
image, boot & run aplay -l so that we can figure out what is causing
your problem.

$ udrcver.sh
Found a DRAWS

HAT ID EEPROM
Name: hat
Product: Digital Radio Amateur Work Station
Product ID: 0x0004
Product ver: 0x0204
UUID: 4a0b1dce-358e-4b50-a372-1118a9ecbfed
Vendor: NW Digital Radio

pi@raspberrypi:~ $ piver.sh
Pi 4 Model B, Rev 1.1, 4GB mem, Mfg by Sony UK
Has WiFi

pi@raspberrypi:~ $ aplay -l | grep udrc
card 2: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]

/Basil n7nix

Keating Floyd <kc4hsi@gmail.com> writes:

Hi, Basil, and thanks!

Yes, I have a wireless keyboard dongle plugged in there.

Keating


On Tue, Jul 28, 2020, 9:36 PM Basil Gunn <basil@pacabunga.com> wrote:


Keating,
I am looking into your problem.
Could you please tell me if you have anything plugged into the USB
ports on your RPi 4.
Thanks,
/Basil

Keating Floyd <kc4hsi@gmail.com> writes:

Included is the output from showudrc.sh. I was concerned that I had a
problem with my image perhaps, but I own a second DRAWS, and it shows up
just fine.

Thanks for a great product, and for your help.

Keating

===

root@pi4b4g01:/home/pi/n7nix/hfprogs# cat showudrc.sh_out
==== Sound Card ====
No udrc sound card found.
==== Pi Ver ====
Pi 4 Model B, Rev 1.1, 4GB mem, Mfg by Sony UK
Has WiFi
==== udrc Ver ====
Found a DRAWS

HAT ID EEPROM
Name: hat
Product: Digital Radio Amateur Work Station
Product ID: 0x0004
Product ver: 0x0204


Re: which instance of 'direwolf.conf' should I be using?

Basil Gunn
 

Charlie Hein <chein@bellsouth.net> writes:

I'm working on getting direwolf to run, and I find a bunch of
instances of the file in various places - none of which is in /home/pi
- which one is the one that I should be using?
On the NWDR image direwolf is pre-installed and the binary lives here:
$ which direwolf
/usr/local/bin/direwolf

The config file lives here:
$ ls /etc/direwolf.conf
/etc/direwolf.conf

Please read the Getting Started Guide in the groups.io udrc wiki:
https://nw-digital-radio.groups.io/g/udrc/wiki/8921

After you have run the core config (./app_config.sh core)
You start & stop direwolf with the ax-25 commands

ax25-stop
ax25-start
ax25-status

What exactly are you trying to accomplish? That is, why do you think you
need to edit the direwolf config file?

/Basil


which instance of 'direwolf.conf' should I be using?

Charlie Hein
 

I'm working on getting direwolf to run, and I find a bunch of instances of the file in various places - none of which is in /home/pi - which one is the one that I should be using?

Charlie


Re: DRAWS not found

Keating Floyd
 

Hi, Basil, and thanks!

Yes, I have a wireless keyboard dongle plugged in there.

Keating


On Tue, Jul 28, 2020, 9:36 PM Basil Gunn <basil@...> wrote:

Keating,
I am looking into your problem.
Could you please tell me if you have anything plugged into the USB
ports on your RPi 4.
Thanks,
/Basil

Keating Floyd <kc4hsi@...> writes:

> Included is the output from showudrc.sh. I was concerned that I had a problem with my image perhaps, but I own a second DRAWS, and it shows up just fine.
>
> Thanks for a great product, and for your help.
>
> Keating
>
> ===
>
> root@pi4b4g01:/home/pi/n7nix/hfprogs# cat showudrc.sh_out
> ==== Sound Card ====
> No udrc sound card found.
> ==== Pi Ver ====
> Pi 4 Model B, Rev 1.1, 4GB mem, Mfg by Sony UK
> Has WiFi
> ==== udrc Ver ====
> Found a DRAWS
>
> HAT ID EEPROM
> Name:    hat
> Product:  Digital Radio Amateur Work Station
> Product ID: 0x0004
> Product ver: 0x0204




Re: OK, How about connecting to the FT-991A?

Charlie Hein
 

Ok, I'll stop asking about the ports until I actually am forced to have to use one <grin>. 

Charlie


Re: DRAWS not found

Basil Gunn
 

Keating,
I am looking into your problem.
Could you please tell me if you have anything plugged into the USB
ports on your RPi 4.
Thanks,
/Basil

Keating Floyd <kc4hsi@gmail.com> writes:

Included is the output from showudrc.sh. I was concerned that I had a problem with my image perhaps, but I own a second DRAWS, and it shows up just fine.

Thanks for a great product, and for your help.

Keating

===

root@pi4b4g01:/home/pi/n7nix/hfprogs# cat showudrc.sh_out
==== Sound Card ====
No udrc sound card found.
==== Pi Ver ====
Pi 4 Model B, Rev 1.1, 4GB mem, Mfg by Sony UK
Has WiFi
==== udrc Ver ====
Found a DRAWS

HAT ID EEPROM
Name: hat
Product: Digital Radio Amateur Work Station
Product ID: 0x0004
Product ver: 0x0204


DRAWS not found

Keating Floyd
 

Hi, all.

Included is the output from showudrc.sh.  I was concerned that I had a problem with my image perhaps, but I own a second DRAWS, and it shows up just fine.

Thanks for a great product, and for your help.

Keating

===

root@pi4b4g01:/home/pi/n7nix/hfprogs# cat showudrc.sh_out 
==== Sound Card ====
No udrc sound card found.
==== Pi Ver ====
 Pi 4 Model B, Rev 1.1, 4GB mem, Mfg by Sony UK
 Has WiFi
==== udrc Ver ====
Found a DRAWS
 
     HAT ID EEPROM
Name:        hat
Product:     Digital Radio Amateur Work Station
Product ID:  0x0004
Product ver: 0x0204
UUID:        7499df1d-8bc8-401d-b978-97518d36967e
Vendor:      NW Digital Radio
 
==== sys Ver ====
----- image version
2020 06 08 11:50:00 PDT: SD image version: nwdr16
----- /proc/version
Linux version 4.19.118-v7l+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1311 SMP Mon Apr 27 14:26:42 BST 2020
 
----- /etc/*version: 10.4
 
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
 
----- lsb_release
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster
 
---- systemd
   Static hostname: pi4b4g01
         Icon name: computer
        Machine ID: 27ac1f0c20904cb7a960920e966db545
           Boot ID: a5894491276b45ce98a950a72d323b2c
  Operating System: Raspbian GNU/Linux 10 (buster)
            Kernel: Linux 4.19.118-v7l+
      Architecture: arm
 
---- modules
 
---- kernel
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name               Version      Architecture Description
+++-==================-============-============-=================================
ii  raspberrypi-kernel 1.20200601-1 armhf        Raspberry Pi bootloader
 
---- Codec drivers
Found: snd-soc-tlv320aic32x4-i2c.ko, OK
Found: snd-soc-tlv320aic32x4.ko, OK
 
Directory: /proc/device-tree/soc/i2c@7e804000/tlv320aic32x4@18 does NOT exist
 
Directory: /proc/device-tree/soc/i2c@7e804000 exists and status is disabled
 
---- syslog
 
---- dmesg
 
 
----- Dire Wolf DEVELOPMENT version 1.6 E (May 11 2020)
 
==== Filesystem ====
/dev/root        29G  5.0G   23G  19% /
 
==== boot config ====
 
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
 
[all]
#dtoverlay=vc4-fkms-v3d
 
# Flush all overlays, ie. deprecated overlays loaded from eeprom
dtoverlay=
# enable udrc/draws if no eeprom
dtoverlay=draws,alsaname=udrc
force_turbo=1
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
 
---- gpsd
/usr/local/sbin/gpsd
gpsd: 3.20 (revision 3.20)
● gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-07-28 20:23:18 EDT; 11min ago
  Process: 545 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
 Main PID: 552 (gpsd)
    Tasks: 1 (limit: 4915)
   Memory: 1.1M
   CGroup: /system.slice/gpsd.service
           └─552 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
 
Jul 28 20:23:18 pi4b4g01 systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jul 28 20:23:18 pi4b4g01 systemd[1]: Started GPS (Global Positioning System) Daemon.
Jul 28 20:23:18 pi4b4g01 gpsd[552]: gpsd:ERROR: SER: device open of /dev/ttySC0 failed: No such file or directory - retrying read-only
Jul 28 20:23:18 pi4b4g01 gpsd[552]: gpsd:ERROR: SER: read-only device open of /dev/ttySC0 failed: No such file or directory
Jul 28 20:23:18 pi4b4g01 gpsd[552]: gpsd:ERROR: initial GPS device /dev/ttySC0 open failed
Jul 28 20:23:18 pi4b4g01 gpsd[552]: gpsd:ERROR: SER: device open of /dev/pps0 failed: No such file or directory - retrying read-only
Jul 28 20:23:18 pi4b4g01 gpsd[552]: gpsd:ERROR: SER: read-only device open of /dev/pps0 failed: No such file or directory
Jul 28 20:23:18 pi4b4g01 gpsd[552]: gpsd:ERROR: initial GPS device /dev/pps0 open failed
 
---- chrony
-- chrony sources
210 Number of sources = 6
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
#? GPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
#? PPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
^+ 12.167.151.1                  3   6   377     3  +4222us[+5787us] +/-   84ms
^+ white.web-ster.com            2   6   377     2   +391us[+1955us] +/-   83ms
^+ propjet.latt.net              3   6   137    62   -863us[ +702us] +/-   80ms
^* darwin.kenyonralph.com        3   6   377     1   -576us[ +988us] +/-   40ms
-- chrony tracking
Reference ID    : ADFFD7D1 (darwin.kenyonralph.com)
Stratum         : 4
Ref time (UTC)  : Wed Jul 29 00:34:41 2020
System time     : 0.001551948 seconds fast of NTP time
Last offset     : +0.001564196 seconds
RMS offset      : 0.002272248 seconds
Frequency       : 17.748 ppm fast
Residual freq   : -0.755 ppm
Skew            : 0.606 ppm
Root delay      : 0.077438146 seconds
Root dispersion : 0.001088197 seconds
Update interval : 64.6 seconds
Leap status     : Normal
-- chrony sourcestats
210 Number of sources = 6
Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
==============================================================================
GPS                         0   0     0     +0.000   2000.000     +0ns  4000ms
PPS                         0   0     0     +0.000   2000.000     +0ns  4000ms
12.167.151.1                8   6   264     -6.991     32.712  +3768us  1367us
white.web-ster.com          8   6   265     +0.924     12.906   +272us   601us
propjet.latt.net            7   4   205     +1.758     46.233  -1055us  1453us
darwin.kenyonralph.com      8   5   266     -1.417     10.676  -1406us   463us
 
---- sensors
-rw-r--r-- 1 root root 171 Sep 19  2019 /etc/sensors.d/draws
rpi_volt-isa-0000
Adapter: ISA adapter
in0:              N/A  
 
 
---- throttle
temp=51.0'C
throttled=0x0
 
---- locale
Locale country codes consistent among WiFi cfg file, iw reg & X11: US
core_config.sh has been run 0 time(s)
 


Re: OK, How about connecting to the FT-991A?

 

I always recommend using a Radio’s internal sound card over any external interface.

On my home rig I have a TM-V71 and an Alinco 235 connected to DRAWS doing packet. I’m moving to the IC-7300 for HF via USB.

Bryan K7UDR

On Jul 28, 2020, at 1:33 PM, Charlie Hein <chein@...> wrote:

I've had the 991A for about two years now, really like the radio.  Frankly, the 991A was not top of mind for connecting to the Pi as I already have a battle-hardened digital setup in place for windows that I don't want to wreck (hence the need to back up configuration before experimenting with the DRAWS).  I have a separate existing packet setup that I'd like to turn into a more feature filled system (replacing the 20+ year old TNC with the DRAWS workstation). I need the Pi do do that because I don't want to pony up for another windows system to dedicate to that job when I already own the Pi.  Hence the DRAWS board.   I do *not in any way* want to tear that system down until the DRAWS workstation is fully configured and running in test bed (on the 991A since evidently my available HT's are not suitable), and so that's 99.999% of the reason I'm asking about hookup to the 991...

I tossed the extra wrinkle of the CAT connection into the mix just so I could try it out for fun (how well does it really work compared to my windows system???  hmmm...), but CAT functionality doesn't really fit into my more immediate plans.  I just like chasing thoughts down the rabbit hole.

Make more sense now?

Charlie


Re: OK, How about connecting to the FT-991A?

Charlie Hein
 

I've had the 991A for about two years now, really like the radio.  Frankly, the 991A was not top of mind for connecting to the Pi as I already have a battle-hardened digital setup in place for windows that I don't want to wreck (hence the need to back up configuration before experimenting with the DRAWS).  I have a separate existing packet setup that I'd like to turn into a more feature filled system (replacing the 20+ year old TNC with the DRAWS workstation). I need the Pi do do that because I don't want to pony up for another windows system to dedicate to that job when I already own the Pi.  Hence the DRAWS board.   I do *not in any way* want to tear that system down until the DRAWS workstation is fully configured and running in test bed (on the 991A since evidently my available HT's are not suitable), and so that's 99.999% of the reason I'm asking about hookup to the 991...

I tossed the extra wrinkle of the CAT connection into the mix just so I could try it out for fun (how well does it really work compared to my windows system???  hmmm...), but CAT functionality doesn't really fit into my more immediate plans.  I just like chasing thoughts down the rabbit hole.

Make more sense now?

Charlie


Re: OK, How about connecting to the FT-991A?

Andrew P.
 

True, but you also paid a lot for that radio to provide those extra USB interfaces, instead of some cheaper radio with only a data port (or even just speaker and mike jacks) and no built-in sound cards (don't remind me how much I paid for my Icom IC-7100 when it first came out., versus the new price now. ouch!). Considering the DRAWS board's GPS provides 1PPS for precision time setting (can't do that with a USB puck), plus it has not one but two sound cards on it for the two ports, it's cheaper than a GPS puck and a pair of SignaLinks and takes up less room and power, and you could be using two less expensive radios simultaneously (Kenwood TM-V71 or something even cheaper like a single-bander).

I assume you got the radio before the DRAWS board.

Andrew, KA2DDO

________________________________________
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of Charlie Hein <chein@bellsouth.net>
Sent: Tuesday, July 28, 2020 3:40 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] OK, How about connecting to the FT-991A?

Well Andrew, you might certainly make the case that I don't really need the DRAWS board at all for the 991A (although that's a really awful sales pitch to an owner of the radio I suppose, as an external USB GPS and a cheapie buck converter/regulator would be far less than the cost of the DRAWS board), but in this case I want very much to test the functionality of the ports that are are on the board and the ability of these ports to minimally control PTT and pass audio to the radio for packet radio. Ultimately I will very likely not be permanently setting up the 991A with the DRAWS workstation in this fashion, but for now my only other other option to get this up on the air and working for testing and software setup is to hook up to a hand held to test direct connection to the radio ports on the board, and I've been gently discouraged from trying this due to expected poor performance from the hand held.

Hope that makes sense.

Charlie


Re: OK, How about connecting to the FT-991A?

Charlie Hein
 

Well Andrew, you might certainly make the case that I don't really need the DRAWS board at all for the 991A (although that's a really awful sales pitch to an owner of the radio I suppose, as an external USB GPS and a cheapie buck converter/regulator would be far less than the cost of the DRAWS board), but in this case I want very much to test the functionality of the ports that are are on the board and the ability of these ports to minimally control PTT and pass audio to the radio for packet radio. Ultimately I will very likely not be permanently setting up the 991A with the DRAWS workstation in this fashion, but for now my only other other option to get this up on the air and working for testing and software setup is to hook up to a hand held to test direct connection to the radio ports on the board, and I've been gently discouraged from trying this due to expected poor performance from the hand held.

Hope that makes sense.

Charlie


Re: OK, How about connecting to the FT-991A?

Andrew P.
 

In the Yaesu case, why do you need the DRAWS card (except possibly for GPS and power)?

Just use the one USB link to the radio. Linux has generic USB sound and serial port drivers that should work with the Yaesu plug-and play (plug-and-pray?). Plug it in and see if an additional sound card and /dev/ttyUSBn devices appear.

Andrew, KA2DDO

________________________________________
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> on behalf of Charlie Hein <chein@bellsouth.net>
Sent: Tuesday, July 28, 2020 3:01 PM
To: udrc@nw-digital-radio.groups.io
Subject: [draws and udrc] OK, How about connecting to the FT-991A?

Hi folks - I've been gently steered away from trying to connect the DRAWS to my HT, so I'm looking now at connecting it up to my Yaesu FT-991A. I could use some experienced advice.

I'm a bit confused because when I operate from my Windows Laptop I only use the USB cable and utilize the sound card built in to the 991A. For the DRAWS board it seems I'll need to connect to the data port on the radio, and that it should be a direct pin for pin fit to the data jack on the radio. Does anyone know if there are any settings that I'd need to change on the 991 in order to use its data port, and if so what they would be? I think that if this is going to be a big change I'd like to make sure my current configs for the 991A are backed up for later, so if you have experience with this I'd appreciate your counsel.

Also, I'd think I would still need the USB connection for CAT control if I wanted to use a program that calls for it like WSJT-X for instance, but wouldn't that also give me another sound card that I really don't need? Where do you get the proper drivers for the RPi for this? I only see Windows drivers on the Yaesu site.

Charlie

701 - 720 of 5709