Date   

[New post] DRAWS Production Update

 
Edited

 


k7udr posted: "As we come to the end of February all parts are in house or in transit. Once the last few parts arrive we will secure a 5 day assembly turn. At that time we'll provide a ship date. We have ramped up our capability to meet demand, and should be able to "
 

New post on NW Digital Radio

 

DRAWS Production Update

by k7udr

As we come to the end of February all parts are in house or in transit. Once the last few parts arrive we will secure a 5 day assembly turn. At that time we'll provide a ship date.

We have ramped up our capability to meet demand, and should be able to maintain stock going forward.

Thanks for your patience.

 
k7udr | February 25, 2019 at 2:07 pm | Categories: DRAWS | URL: https://wp.me/p2mAAP-1zD
 

 

 


Re: direwolf frame size #ax25 #direwolf

 



--


John D. Hays
Edmonds, WA
K7VE

   


direwolf frame size #ax25 #direwolf

jgindc1@...
 

I am sending/receiving Winlink messages using a Raspberry pi with the DRAWS hat. All is well as long as the messages/attachments are short, less than a couple of kBytes.

When attempting to send longer messages/attachments, each transmission increases in time starting at about 4 seconds then climbing up to about 14-15 seconds at which time I get a fail message - "Exchanged failed: read udr0: connection timed out". I would like to set a limit to the maximum transmission period.

I am unsure at which software level the maximum packet/frame length is determined. I have looked at direwolf.conf but did not see any reference to frame or packet length.

Any suggestions would be gratefully received.

John KM7LJ


Re: DRAWS™ Manager Demo #drawsmanager

Steve Stroh
 

Nice work John!

Looks reasonably intuitive.

I suggest that you add:
* On screen PTT indicator
* Button to toggle PTT on / off
* Button and slider for various test tones, including varying tones so you can adjust for twist
* Ability to define your own radio on the drop down menu.

The telemetry is great, but why crowd it into a couple of lines at the very bottom? Break it out and make it more prominent.

Also, display the version of DRAWS driver(s) and the version of Rasperian. 

Overall, this is a great tool for DRAWS!

On Sun, Feb 24, 2019 at 15:03 John D Hays - K7VE <john@...> wrote:

See - 

https://www.youtube.com/watch?v=v5C3cWVVz_A

--
Steve Stroh (personal / general): stevestroh@...


DRAWS™ Manager Demo #drawsmanager

 

See - 

https://www.youtube.com/watch?v=v5C3cWVVz_A


Re: IMPORTANT: Do not upgrade #kernel on #kernel #beta8

Art - KC7SDA
 

oh crud =(


Re: FT891, FT817, Audio Levels, I/O Fail , and Documentation #draws #ft817 #hfmodes

jgindc1@...
 

Basil,

Thanks for replying so quickly. Cutting the pin 6 squelch line did indeed solve the problem.

For some unknown reason I had associated the squelch issue with HF and did not check at VHF/UHF FM. 

Also thanks to John and Brian for additional info and references.

73, John KM7LJ


On Sat, Feb 23, 2019 at 7:22 PM Brian Badger <brian@...> wrote:
The advantage of cutting the black wire is that you can in-line a switch to restore squelch operation for non-HF modes.

Brian N0KZ


On Feb 23, 2019, at 8:13 PM, John D Hays - K7VE <john@...> wrote:

Or pull the pin in one end of the cable.

On Sat, Feb 23, 2019, 18:46 Brian Badger <brian@...> wrote:
This is correct.  In order to work with the 817, 857, and 897 in HF modes, the squelch line must be cut.   

I had asked if this could be done in software or by jumper and the answer at the time was that cutting the line was the only solution.

See msg 2079 — the SQL line is the black wire.

Brian
> On Feb 23, 2019, at 5:56 PM, Basil Gunn <basil@...> wrote:
>
>
> I had to disconnect the the squelch pin in my mDin6 cable to get the
> FT-817 to work. There are some notes for the FT-817 HF SSB based AFSK
> and 1200/9600 bps FM operation here:
>
> https://github.com/nwdigitalradio/n7nix/blob/master/docs/RADIO_APP_NOTES.md
>
> /Basil n7nix
>
>
> jgindc1@... writes:
>
>> Using the DRAWS hat, I have had good success with AX25 packet using a
>> Kenwood V71, for example, running XASTIR, or sending and receiving winlink
>> messages using PAT.
>>
>> However, when I substitute my FT-817 for the V71, using the same cables for
>> data and rig control, the DRAWS DIN-6 connection appears to "short" the
>> audio from the FT-817 to ground.
>
>
>




IMPORTANT: Do not upgrade #kernel on #kernel #beta8

 

We have determined that upgrading to kernel 4.14.98-v7+  is breaking access to the DRAWS™ HAT (UDRC) driver.

Please do not do a general 
apt-get update
apt-get upgrade
until we resolve this issue.

At the current time we can only recommend backing up your application configurations and reverting to a fresh copy of beta8, if you have already performed an upgrade.


John D. Hays
Director

  


Re: FT891, FT817, Audio Levels, I/O Fail , and Documentation #draws #ft817 #hfmodes

Brian Badger
 

The advantage of cutting the black wire is that you can in-line a switch to restore squelch operation for non-HF modes.

Brian N0KZ


On Feb 23, 2019, at 8:13 PM, John D Hays - K7VE <john@...> wrote:

Or pull the pin in one end of the cable.

On Sat, Feb 23, 2019, 18:46 Brian Badger <brian@...> wrote:
This is correct.  In order to work with the 817, 857, and 897 in HF modes, the squelch line must be cut.   

I had asked if this could be done in software or by jumper and the answer at the time was that cutting the line was the only solution.

See msg 2079 — the SQL line is the black wire.

Brian
> On Feb 23, 2019, at 5:56 PM, Basil Gunn <basil@...> wrote:
>
>
> I had to disconnect the the squelch pin in my mDin6 cable to get the
> FT-817 to work. There are some notes for the FT-817 HF SSB based AFSK
> and 1200/9600 bps FM operation here:
>
> https://github.com/nwdigitalradio/n7nix/blob/master/docs/RADIO_APP_NOTES.md
>
> /Basil n7nix
>
>
> jgindc1@... writes:
>
>> Using the DRAWS hat, I have had good success with AX25 packet using a
>> Kenwood V71, for example, running XASTIR, or sending and receiving winlink
>> messages using PAT.
>>
>> However, when I substitute my FT-817 for the V71, using the same cables for
>> data and rig control, the DRAWS DIN-6 connection appears to "short" the
>> audio from the FT-817 to ground.
>
>
>




Re: FT891, FT817, Audio Levels, I/O Fail , and Documentation #draws #ft817 #hfmodes

 

Or pull the pin in one end of the cable.


On Sat, Feb 23, 2019, 18:46 Brian Badger <brian@...> wrote:
This is correct.  In order to work with the 817, 857, and 897 in HF modes, the squelch line must be cut.   

I had asked if this could be done in software or by jumper and the answer at the time was that cutting the line was the only solution.

See msg 2079 — the SQL line is the black wire.

Brian
> On Feb 23, 2019, at 5:56 PM, Basil Gunn <basil@...> wrote:
>
>
> I had to disconnect the the squelch pin in my mDin6 cable to get the
> FT-817 to work. There are some notes for the FT-817 HF SSB based AFSK
> and 1200/9600 bps FM operation here:
>
> https://github.com/nwdigitalradio/n7nix/blob/master/docs/RADIO_APP_NOTES.md
>
> /Basil n7nix
>
>
> jgindc1@... writes:
>
>> Using the DRAWS hat, I have had good success with AX25 packet using a
>> Kenwood V71, for example, running XASTIR, or sending and receiving winlink
>> messages using PAT.
>>
>> However, when I substitute my FT-817 for the V71, using the same cables for
>> data and rig control, the DRAWS DIN-6 connection appears to "short" the
>> audio from the FT-817 to ground.
>
>
>




Re: no sound card.... again..... #beta #draws

Art - KC7SDA
 

my guess its something to do with the update/upgrade I did... I normally don't pay attention when I do it as, for the most part, I want everything upgraded....


Re: FT891, FT817, Audio Levels, I/O Fail , and Documentation #draws #ft817 #hfmodes

Brian Badger
 

This is correct. In order to work with the 817, 857, and 897 in HF modes, the squelch line must be cut.

I had asked if this could be done in software or by jumper and the answer at the time was that cutting the line was the only solution.

See msg 2079 — the SQL line is the black wire.

Brian

On Feb 23, 2019, at 5:56 PM, Basil Gunn <@basil860> wrote:


I had to disconnect the the squelch pin in my mDin6 cable to get the
FT-817 to work. There are some notes for the FT-817 HF SSB based AFSK
and 1200/9600 bps FM operation here:

https://github.com/nwdigitalradio/n7nix/blob/master/docs/RADIO_APP_NOTES.md

/Basil n7nix


jgindc1@... writes:

Using the DRAWS hat, I have had good success with AX25 packet using a
Kenwood V71, for example, running XASTIR, or sending and receiving winlink
messages using PAT.

However, when I substitute my FT-817 for the V71, using the same cables for
data and rig control, the DRAWS DIN-6 connection appears to "short" the
audio from the FT-817 to ground.


Re: FT891, FT817, Audio Levels, I/O Fail , and Documentation #draws #ft817 #hfmodes

Basil Gunn
 

I had to disconnect the the squelch pin in my mDin6 cable to get the
FT-817 to work. There are some notes for the FT-817 HF SSB based AFSK
and 1200/9600 bps FM operation here:

https://github.com/nwdigitalradio/n7nix/blob/master/docs/RADIO_APP_NOTES.md

/Basil n7nix


jgindc1@... writes:

Using the DRAWS hat, I have had good success with AX25 packet using a
Kenwood V71, for example, running XASTIR, or sending and receiving winlink
messages using PAT.

However, when I substitute my FT-817 for the V71, using the same cables for
data and rig control, the DRAWS DIN-6 connection appears to "short" the
audio from the FT-817 to ground.


Re: FT891, FT817, Audio Levels, I/O Fail , and Documentation #draws #ft817 #hfmodes

jgindc1@...
 

Using the DRAWS hat, I have had good success with AX25 packet using a Kenwood V71, for example, running XASTIR, or sending and receiving winlink messages using PAT.

However, when I substitute my FT-817 for the V71, using the same cables for data and rig control, the DRAWS DIN-6 connection appears to "short" the audio from the FT-817 to ground. Disconnected from DRAWS I see the FT-817 signal strength meter indicate the presence of a received signal and the audio is heard on the radio's loudspeaker. I am also using an oscilloscope to monitor the signal on pin 5 (1200 baud) from the FT-817.

When connected to the DRAWS DIN-6, left or right, the audio is not heard  in the loudspeaker (though the radio's signal strength meter still indicates the presence of a received signal), and the signal shown on the oscilloscope goes to zero.

Thinking that this might be a loading issue with the FT-817, I changed the in-line resistor values from 10k to 40k as confirmed via alsa-show:

 ===== ALSA Controls for Radio Receive =====
ADC Level       L:[0.00dB]      R:[0.00dB]
IN1             L:[Off]         R:[Off]
IN2             L:[40 kOhm]     R:[40 kOhm

No change.

I have the FT-817 mode in PKT and PKT RATE set to 1200baud.

I would be most grateful for any suggestions.

John KM7LJ


On Sun, Dec 23, 2018 at 10:47 AM Basil Gunn <basil@...> wrote:

I've been staring at the FT-891 & 817 Yaesu manuals and discovered the
following for those 2 radios: (Warning I do not own either of these
radios)

You need to match your Yaeseu radio configuration settings with the ALSA
settings used to config DRAWS.

FT-891
------

If your radio is set for DATA (PSK) operation use ALSA settings IN2_L &
IN2_R. Turn OFF IN1_L & IN1_L

If your radio is set for RTTY (FSK) operation use ALSA settings IN1_L &
IN1_R. TURN OFF IN2_L & IN2_L

See pages page 62-66 of manual FT-891_Advance_Manual_ENG_1806-F.pdf
Yaesu mDin6 pin 4 is labeled SHIFT, this is Discout on other radios.
Also see page 25 of manual FT-891_OM_ENG_EH065H201_1611A-BO-2.pdf


FT-817/818
----------
See page 41 FT-817ND_OM_ENG_E13771011.pdf

Different connections are used for 1200 & 9600 (AFOUT & DISCOUT)

ALSA settings
Use IN1_L IN1_R for 9600 baud (DISCOUT)
Use IN2_L IN2_R for 1200 baud or less (AFOUT)

Radio settings
Use Menu #40 (PKT RATE) to select DISCOUT or AFOUT
Also Menu #39 (PKT MIC) allows adjusting drive level.

/Basil




Re: no sound card.... again..... #beta #draws

 

We suspect something is breaking with kernel 4.14.98-v7+

Investigating 

On Sat, Feb 23, 2019, 10:25 Art - KC7SDA <nouse4anick@...> wrote:
so I booted up today and its not detecting the sound card.

I went through some of the scripts to try and trouble shoot... here's the output for ./showudrc.sh:
pi@draws:~/n7nix/bin $ ./showudrc.sh
aplay: device_list:270: no soundcards found...
==== Sound Card ====
No udrc sound card found.
==== Pi Ver ====
 Pi 3 Model B+ 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:        dbbff004-ed01-4794-bcf3-c3dd96e91705
Vendor:      NW Digital Radio

==== sys Ver ====
----- image version
2019 01 05 17:06:50 PST: SD image version: beta7
----- /proc/version
Linux version 4.14.98-v7+ (dom@dom-XPS-13-9370) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1200 SMP Tue Feb 12 20:27:48 GMT 2019

----- /etc/*version: 9.8

----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
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
No LSB modules are available.
Distributor ID:    Raspbian
Description:    Raspbian GNU/Linux 9.8 (stretch)
Release:    9.8
Codename:    stretch

---- systemd
   Static hostname: draws
         Icon name: computer
        Machine ID: 2f51e140e908474eaa86ae805f03a6d8
           Boot ID: 4c623613ec22478b96d093feede58f9c
  Operating System: Raspbian GNU/Linux 9 (stretch)
            Kernel: Linux 4.14.98-v7+
      Architecture: arm

---- modules
udrc                   16384  0
snd_soc_tlv320aic32x4    32768  0
snd_soc_core          188416  3 snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,udrc
snd_pcm                98304  4 snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_soc_core
snd                    69632  5 snd_compress,snd_timer,snd_soc_tlv320aic32x4,snd_soc_core,snd_pcm

-rw-r--r-- 1 root  6388 Feb 23 16:23 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4-i2c.ko
-rw-r--r-- 1 root 39084 Feb 23 16:23 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4.ko
-rw-r--r-- 1 root  6408 Feb 23 16:23 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4-spi.ko
-rw-r--r-- 1 root  8332 Feb 23 16:23 /lib/modules/4.14.98-v7+/updates/dkms/udrc.ko

---- kernel
||/ Name               Version      Architecture Description
+++-==================-============-============-=================================
ii  raspberrypi-kernel 1.20190215-1 armhf        Raspberry Pi bootloader
ii  udrc-dkms          1.0.5        armhf        DKMS source for the UDRC driver

---- compass
Compass preference file not found: /etc/apt/preferences.d/compass
---- compass apt sources list file
deb [arch=armhf,amd64] http://archive.compasslinux.org/ cedar main
---- compass package files
-rw-r--r-- 1 root  2201 Dec 31 18:44 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_InRelease
-rw-r--r-- 1 root 17567 Jul  3  2018 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_main_binary-amd64_Packages
-rw-r--r-- 1 root 43316 Dec 31 18:44 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_main_binary-armhf_Packages

----- Dire Wolf DEVELOPMENT version 1.6 A (Dec  9 2018)

==== boot config ====
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
# dtparam=audio=on

force_turbo=1
dtoverlay=
dtoverlay=draws

---- gpsd
● gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: ena
   Active: active (running) since Sat 2019-02-23 18:21:13 GMT; 1min 33s ago
  Process: 487 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (c
 Main PID: 503 (gpsd)
   CGroup: /system.slice/gpsd.service
           └─503 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0

Feb 23 18:21:13 draws systemd[1]: Starting GPS (Global Positioning System) Daemo
Feb 23 18:21:13 draws systemd[1]: Started GPS (Global Positioning System) Daemon

---- chrony
● gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: ena
   Active: active (running) since Sat 2019-02-23 18:21:13 GMT; 1min 34s ago
  Process: 487 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (c
 Main PID: 503 (gpsd)
   CGroup: /system.slice/gpsd.service
           └─503 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0

Feb 23 18:21:13 draws systemd[1]: Starting GPS (Global Positioning System) Daemo
Feb 23 18:21:13 draws systemd[1]: Started GPS (Global Positioning System) Daemon
-- 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
^+ 2600:1f16:7a3:8a22:a922:>     2   6    17    52  -1388us[ -953us] +/-   83ms
^+ christensenplace.us           2   6    17    52   +892us[+1327us] +/-   48ms
^+ excalibur.prolixium.com       2   6    17    52   +799us[+1234us] +/-   81ms
^* 2001:550:1d05:30::58e:3e>     2   6    17    53   -598us[ -163us] +/-   61ms
-- chrony tracking
Reference ID    : 52A63EA3 (2001:550:1d05:30::58e:3ef3)
Stratum         : 3
Ref time (UTC)  : Sat Feb 23 18:21:56 2019
System time     : 0.000000007 seconds slow of NTP time
Last offset     : +0.000435050 seconds
RMS offset      : 0.000435050 seconds
Frequency       : 4.581 ppm fast
Residual freq   : +44.933 ppm
Skew            : 4.489 ppm
Root delay      : 0.121314 seconds
Root dispersion : 0.003504 seconds
Update interval : 2.1 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
2600:1f16:7a3:8a22:a922:>   4   4     6    +65.188   6754.712  +2249us   703us
christensenplace.us         4   3     6     +0.019   4087.506   +623us   558us
excalibur.prolixium.com     4   3     6    -95.063   7074.659  -4081us   760us
2001:550:1d05:30::58e:3e>   4   3     6    +75.847   1112.933  +3376us   152us

---- sensors
-rw-r--r-- 1 root root 171 Nov 11 19:39 /etc/sensors.d/draws
ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
User ADC Differential:  +0.00 V 
+12V:                  +12.37 V 
User ADC 1:             +0.00 V 
User ADC 2:             +0.00 V 

pi@draws:~/n7nix/bin $
any idea why this is having an issue? it detects the hat, but not the sound card... i've just done an update/upgrade and nothing else.


no sound card.... again..... #beta #draws

Art - KC7SDA
 

so I booted up today and its not detecting the sound card.

I went through some of the scripts to try and trouble shoot... here's the output for ./showudrc.sh:
pi@draws:~/n7nix/bin $ ./showudrc.sh
aplay: device_list:270: no soundcards found...
==== Sound Card ====
No udrc sound card found.
==== Pi Ver ====
 Pi 3 Model B+ 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:        dbbff004-ed01-4794-bcf3-c3dd96e91705
Vendor:      NW Digital Radio

==== sys Ver ====
----- image version
2019 01 05 17:06:50 PST: SD image version: beta7
----- /proc/version
Linux version 4.14.98-v7+ (dom@dom-XPS-13-9370) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1200 SMP Tue Feb 12 20:27:48 GMT 2019

----- /etc/*version: 9.8

----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
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
No LSB modules are available.
Distributor ID:    Raspbian
Description:    Raspbian GNU/Linux 9.8 (stretch)
Release:    9.8
Codename:    stretch

---- systemd
   Static hostname: draws
         Icon name: computer
        Machine ID: 2f51e140e908474eaa86ae805f03a6d8
           Boot ID: 4c623613ec22478b96d093feede58f9c
  Operating System: Raspbian GNU/Linux 9 (stretch)
            Kernel: Linux 4.14.98-v7+
      Architecture: arm

---- modules
udrc                   16384  0
snd_soc_tlv320aic32x4    32768  0
snd_soc_core          188416  3 snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,udrc
snd_pcm                98304  4 snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_soc_core
snd                    69632  5 snd_compress,snd_timer,snd_soc_tlv320aic32x4,snd_soc_core,snd_pcm

-rw-r--r-- 1 root  6388 Feb 23 16:23 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4-i2c.ko
-rw-r--r-- 1 root 39084 Feb 23 16:23 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4.ko
-rw-r--r-- 1 root  6408 Feb 23 16:23 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4-spi.ko
-rw-r--r-- 1 root  8332 Feb 23 16:23 /lib/modules/4.14.98-v7+/updates/dkms/udrc.ko

---- kernel
||/ Name               Version      Architecture Description
+++-==================-============-============-=================================
ii  raspberrypi-kernel 1.20190215-1 armhf        Raspberry Pi bootloader
ii  udrc-dkms          1.0.5        armhf        DKMS source for the UDRC driver

---- compass
Compass preference file not found: /etc/apt/preferences.d/compass
---- compass apt sources list file
deb [arch=armhf,amd64] http://archive.compasslinux.org/ cedar main
---- compass package files
-rw-r--r-- 1 root  2201 Dec 31 18:44 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_InRelease
-rw-r--r-- 1 root 17567 Jul  3  2018 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_main_binary-amd64_Packages
-rw-r--r-- 1 root 43316 Dec 31 18:44 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_main_binary-armhf_Packages

----- Dire Wolf DEVELOPMENT version 1.6 A (Dec  9 2018)

==== boot config ====
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
# dtparam=audio=on

force_turbo=1
dtoverlay=
dtoverlay=draws

---- gpsd
● gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: ena
   Active: active (running) since Sat 2019-02-23 18:21:13 GMT; 1min 33s ago
  Process: 487 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (c
 Main PID: 503 (gpsd)
   CGroup: /system.slice/gpsd.service
           └─503 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0

Feb 23 18:21:13 draws systemd[1]: Starting GPS (Global Positioning System) Daemo
Feb 23 18:21:13 draws systemd[1]: Started GPS (Global Positioning System) Daemon

---- chrony
● gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: ena
   Active: active (running) since Sat 2019-02-23 18:21:13 GMT; 1min 34s ago
  Process: 487 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (c
 Main PID: 503 (gpsd)
   CGroup: /system.slice/gpsd.service
           └─503 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0

Feb 23 18:21:13 draws systemd[1]: Starting GPS (Global Positioning System) Daemo
Feb 23 18:21:13 draws systemd[1]: Started GPS (Global Positioning System) Daemon
-- 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
^+ 2600:1f16:7a3:8a22:a922:>     2   6    17    52  -1388us[ -953us] +/-   83ms
^+ christensenplace.us           2   6    17    52   +892us[+1327us] +/-   48ms
^+ excalibur.prolixium.com       2   6    17    52   +799us[+1234us] +/-   81ms
^* 2001:550:1d05:30::58e:3e>     2   6    17    53   -598us[ -163us] +/-   61ms
-- chrony tracking
Reference ID    : 52A63EA3 (2001:550:1d05:30::58e:3ef3)
Stratum         : 3
Ref time (UTC)  : Sat Feb 23 18:21:56 2019
System time     : 0.000000007 seconds slow of NTP time
Last offset     : +0.000435050 seconds
RMS offset      : 0.000435050 seconds
Frequency       : 4.581 ppm fast
Residual freq   : +44.933 ppm
Skew            : 4.489 ppm
Root delay      : 0.121314 seconds
Root dispersion : 0.003504 seconds
Update interval : 2.1 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
2600:1f16:7a3:8a22:a922:>   4   4     6    +65.188   6754.712  +2249us   703us
christensenplace.us         4   3     6     +0.019   4087.506   +623us   558us
excalibur.prolixium.com     4   3     6    -95.063   7074.659  -4081us   760us
2001:550:1d05:30::58e:3e>   4   3     6    +75.847   1112.933  +3376us   152us

---- sensors
-rw-r--r-- 1 root root 171 Nov 11 19:39 /etc/sensors.d/draws
ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
User ADC Differential:  +0.00 V 
+12V:                  +12.37 V 
User ADC 1:             +0.00 V 
User ADC 2:             +0.00 V 

pi@draws:~/n7nix/bin $
any idea why this is having an issue? it detects the hat, but not the sound card... i've just done an update/upgrade and nothing else.


Re: How do we setup dovecot and postfix to start at boot up?

Julie McGrew
 

Hi Basil,

Thank you very much for your quick response. I’m currently using claws mail and sending email via the winlink system using packet, pactor, and telnet.

Good to know the preferred process is systemd so I’ll wait and look forward to taking advantage of the scripts you are finishing up. No rush … just nice to know they will be coming in near future. :)

Many thanks,
julie
ac0wn

On Feb 22, 2019, at 2:45 PM, Basil Gunn <@basil860> wrote:


Hi Julie,

So for Debian/Raspbian, for better or for worse, the preferred method of
starting init processes is systemd and not the SYS V init.d
method. I am pretty close to being finished with some scripts that start
up paclink-unix dovecot & postfix so that you can use mutt, claws-mail
or rainloop as email clients for Winlink messaging. I have used this
setup for a number of years so I'm just cleaning up some of the scripts
I use to configure everything.

If you are just wanting to setup a local imap server on the RPi without
Winlink functionality I can help you out as that is my normal email
setup.

/Basil

Julie McGrew via Groups.Io <juliemcgrew=mac.com@groups.io> writes:

I see the scripts for dovecot and postfix in /etc/init.d

I have tried: "sudo update-rc.d dovecot defaults"

No joy .... after a reboot and using: "service --status-all" they are still not running. They are easy to start and stop manually, but I'd like them to start automatically at boot-up. Any assistance greatly appreciated. :)

73,
julie
ac0wn


Re: How do we setup dovecot and postfix to start at boot up?

Basil Gunn
 

Hi Julie,

So for Debian/Raspbian, for better or for worse, the preferred method of
starting init processes is systemd and not the SYS V init.d
method. I am pretty close to being finished with some scripts that start
up paclink-unix dovecot & postfix so that you can use mutt, claws-mail
or rainloop as email clients for Winlink messaging. I have used this
setup for a number of years so I'm just cleaning up some of the scripts
I use to configure everything.

If you are just wanting to setup a local imap server on the RPi without
Winlink functionality I can help you out as that is my normal email
setup.

/Basil

Julie McGrew via Groups.Io <juliemcgrew=mac.com@groups.io> writes:

I see the scripts for dovecot and postfix in /etc/init.d

I have tried: "sudo update-rc.d dovecot defaults"

No joy .... after a reboot and using: "service --status-all" they are still not running. They are easy to start and stop manually, but I'd like them to start automatically at boot-up. Any assistance greatly appreciated. :)

73,
julie
ac0wn


How do we setup dovecot and postfix to start at boot up?

Julie McGrew
 

I see the scripts for dovecot and postfix in /etc/init.d

I have tried:  "sudo update-rc.d dovecot defaults"

No joy .... after a reboot and using: "service --status-all" they are still not running.  They are easy to start and stop manually, but I'd like them to start automatically at boot-up.  Any assistance greatly appreciated.  :)

73,
julie
ac0wn


Re: [compass] Top shows node and nmp applications consumming a lot of CPU %

 

I am not seeing that level of CPU utilization.  I typically see 3-7% on one CPU core (press 1 when in top to see individual core utilization).  I am not at the same kernel.

It polls to collect sensor data once per second, so it should not be having any major impact on overall performance.  Complete source is at https://github.com/nwdigitalradio/draws-manager

The npm and node processes are part of the same draws-manager and turn on and off together.

It can safely, and probably should be, turned off (if your Pi is accessible via Internet) when not needed

Linux draws 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux


On Fri, Feb 22, 2019 at 10:29 AM f6bvp <f6bvp@...> wrote:
Hi John,

Congratulations. DRAWS-manager looks like a very interesting application.
However something should be done in order to make it charge less CPU load when run with kernel 4.14.98-v7+ for it uses very often more than 100% CPU load. npm is also using sometime 80% CPU on a RaspBerry Pi 3B+. Compilation or library issue ?

Bernard

Envoyé de mon iPhone

Le 22 févr. 2019 à 18:46, John D Hays - K7VE <john@...> a écrit :

Bonjour Bernard,

The node.js application is DRAWS™ Manager.  You can see it in a browser using the localhost or LAN IP address at port 8080.  E.g. http://localhost:8080  We are planning an instructional video shortly.  BTW, you may wish to get the latest updates to DRAWS™ Manager with:
cd /usr/local/var/draws-manager
sudo git pull

This utility is to help configure the DRAWS™ HAT using a browser rather than the command line alsamixer or other scripts.   In its current state, you need to run one of the N7NIX scripts to 'prime the pump', but then can make changes using the browser.

In beta-8, it is started by default upon boot.

To stop it:
sudo systemctl stop draws-manager
To disable it (prevent it from starting on next boot):
sudo systemctl disable draws-manager

As a reminder,  NW Digital Radio provides the beta images as a convenience to the operator.  We try to make them easy to load and use, but setup and configuration is the responsibility of the operator.  Each station's radio model and application mix is different and thus we cannot presume settings, but endeavor to provide general guidance on the setup of the DRAWS™ HAT as well as, as a courtesy, share our experience with various applications.



On Fri, Feb 22, 2019 at 5:56 AM f6bvp <f6bvp@...> wrote:
While running beta8 with DRAWS I had a look at top in order to see CPU occupancy.
I was noted two javascript applications : node and nmp are consuming an important % of CPU load.
I wonder why those applications are loaded by default and if they are indeed useful for direwolf APRS use ?

Thanks,

Bernard, f6bvp
https://radiotelescopelavillette.wordpress.com/



--


John D. Hays
Edmonds, WA
K7VE