Date   

Re: Setting up auto time with draws gps #ntp #chrony #gps #clock #battery

Art - KC7SDA
 

I did the setup as described in the wiki.... with a battery installed and no gps antenna chronyc sources says that gps is unreachable

cgps shows no fix BUT it has the correct date/time

the time offset from cgps shows -1022.something (bounces between 2 numbers).

I also ran all commands in the verify_time.sh script. chronyd is running and the date/time is off (about half an hour or so as I shut the pi down several times).

please note that the reason for the clock to set itself on boot is because it might take minutes (or never) for the gps to acquire a signal, and that's a waste of time for the user who may never get their clock updated.


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

 

There is a peculiarity in Yaesu's implementation for the SQ pin on the DIN-6 connector.  Bryan could provide more detail.

However, I think people will have more success by disconnecting the squelch line.   This is relatively easy to do at the plug end of the cable.

Remove the  pin (#6), using needle nose pliers and rocking it back and forth until it breaks off.  You may break the plastic 'key' in the process, and may have to straighten out any other pins you bumped in the process.  Just make sure you orient the cable properly when plugging it back into the FT-817.  This will also unmute the speaker.


Re: State of GPSD on boot and PPS2 #pps #gpsd #chrony

 

If the gpsd has been enabled, it should start on boot.
sudo systemctl enable gpsd
The PPS2 is likely a configuration issue in /etc/chrony/chrony.conf  send your version along for review.



On Thu, Dec 27, 2018 at 5:32 PM Basil Gunn <basil@...> wrote:

First thanks for all the data. It would also be good to see the output of
this script.
cd
n7nix/gps/verify_time.sh

So just some observations from my setup which is a clean boot of the
DRAWS image.

My gpsd also does not start automatically. I will look into that.
It does start when I run gpsmon

If I look for any pps devices I only have one.
Perhaps you can do the following & see what you get.

ls /dev/pps*
/dev/pps0

When I google 'raspberry pi PPS2' it comes up with:
Duracell PPS2 Instant USB charger
Are you powering your RPi with an external battery pack?

Thanks,
/Basil



Daniel VE3NI <dgoodier@...> writes:

> Hi,
>

>
> First let me apologize for what will be a long email.
>

>
> There has been lots of good discussion and learning going on about the DRAWS hat.
>

>
> I have been hoping that someone else might be experiencing this issue and would bring up to the group for discussion but so far no one has so it is possible that I am the only one.
>

>
> I have the DRAWS hat with the GPS antenna.
>

>
> I have experienced this issue on both beta5 and beta6.
>

>
> I use the ./app_config.sh core command to configure my system.
>

>
> I modify /etc/chrony/chrony.conf to uncomment the refclock PPS /dev/pps0 lock GPS trust prefer line and add the lines to broadcast to the local network and allow client on the local network to sync to the rPi.
>

>
> Upon reboot if I check the state of GPSD is shows:
>

>
> pi@draws:~ $ sudo systemctl status gpsd
>
> gpsd.service - GPS (Global Positioning System) Daemon
>
>    Loaded: loaded (/lib/systemd/system/gpsd.service; indirect; vendor preset: enabled)
>
>    Active: inactive (dead)
>
> pi@draws:~ $
>

>
> In addition when I check the state of CHRONY after the reboot I see:
>

>
> pi@draws:~ $ sudo systemctl status chrony
>
> chrony.service - chrony, an NTP client/server
>
>    Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
>
>    Active: active (running) since Thu 2018-12-27 16:33:04 EST; 3min 56s ago
>
>      Docs: man:chronyd(8)
>
>            man:chronyc(1)
>
>            man:chrony.conf(5)
>
>   Process: 562 ExecStart=/usr/sbin/chronyd (code=exited, status=0/SUCCESS)
>
> Main PID: 607 (chronyd)
>
>    CGroup: /system.slice/chrony.service
>
>            +-607 /usr/sbin/chronyd
>

>
> Dec 27 16:33:03 draws systemd[1]: Starting chrony, an NTP client/server...
>
> Dec 27 16:33:04 draws chronyd[607]: chronyd version 3.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS
>
> Dec 27 16:33:04 draws chronyd[607]: Frequency 6.975 +/- 0.038 ppm read from /var/lib/chrony/chrony.drift
>
> Dec 27 16:33:04 draws systemd[1]: Started chrony, an NTP client/server.
>

>
> It is only when I either specifically start the GPSD (sudo systemctl start gpsd) or open a terminal window and run gpsmon that the GPSD and CHRONY status are what I expect.
>

>
> pi@draws:~ $ sudo systemctl status gpsd
>
> gpsd.service - GPS (Global Positioning System) Daemon
>
>    Loaded: loaded (/lib/systemd/system/gpsd.service; indirect; vendor preset: enabled)
>
>    Active: active (running) since Thu 2018-12-27 16:37:28 EST; 7s ago
>
> Main PID: 1318 (gpsd)
>
>    CGroup: /system.slice/gpsd.service
>
>            +-1318 /usr/sbin/gpsd -N -n /dev/ttySC0 /dev/pps0
>

>
> Dec 27 16:37:28 draws systemd[1]: Started GPS (Global Positioning System) Daemon.
>

>
> pi@draws:~ $ sudo systemctl status chrony
>
> chrony.service - chrony, an NTP client/server
>
>    Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
>
>    Active: active (running) since Thu 2018-12-27 16:33:04 EST; 4min 57s ago
>
>      Docs: man:chronyd(8)
>
>            man:chronyc(1)
>
>            man:chrony.conf(5)
>
>   Process: 562 ExecStart=/usr/sbin/chronyd (code=exited, status=0/SUCCESS)
>
> Main PID: 607 (chronyd)
>
>    CGroup: /system.slice/chrony.service
>
>            +-607 /usr/sbin/chronyd
>

>
> Dec 27 16:33:03 draws systemd[1]: Starting chrony, an NTP client/server...
>
> Dec 27 16:33:04 draws chronyd[607]: chronyd version 3.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS
>
> Dec 27 16:33:04 draws chronyd[607]: Frequency 6.975 +/- 0.038 ppm read from /var/lib/chrony/chrony.drift
>
> Dec 27 16:33:04 draws systemd[1]: Started chrony, an NTP client/server.
>
> Dec 27 16:37:51 draws chronyd[607]: Selected source 2001:4168:1::1
>
> Dec 27 16:37:51 draws chronyd[607]: System clock wrong by 9.542856 seconds, adjustment started
>
> Dec 27 16:38:01 draws chronyd[607]: System clock was stepped by 9.542856 seconds
>
> Dec 27 16:38:01 draws chronyd[607]: Selected source PPS
>
> Dec 27 16:38:07 draws chronyd[607]: Can't synchronise: no required source in selectable sources
>

>
> Any suggestion as to which step I might have missed?  It almost looks like it is waiting for a request before it starts.  I know that I can force it to start on reboot by adding commands to systemd but would like to know if it is working by design before I make any changes.
>

>
> This brings leads me to by question.
>

>
> Where is PPS2 coming from?  PPS2 is not defined in my chrony.conf file but does show up when I run chronyc sources.
>

>
> pi@draws:~ $ sudo systemctl status chrony
>
> ? chrony.service - chrony, an NTP client/server
>
>    Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
>
>    Active: active (running) since Thu 2018-12-27 16:33:04 EST; 13min ago
>
>      Docs: man:chronyd(8)
>
>            man:chronyc(1)
>
>            man:chrony.conf(5)
>
>   Process: 562 ExecStart=/usr/sbin/chronyd (code=exited, status=0/SUCCESS)
>
> Main PID: 607 (chronyd)
>
>    CGroup: /system.slice/chrony.service
>
>            +-607 /usr/sbin/chronyd
>

>
> Dec 27 16:33:04 draws chronyd[607]: chronyd version 3.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS
>
> Dec 27 16:33:04 draws chronyd[607]: Frequency 6.975 +/- 0.038 ppm read from /var/lib/chrony/chrony.drift
>
> Dec 27 16:33:04 draws systemd[1]: Started chrony, an NTP client/server.
>
> Dec 27 16:37:51 draws chronyd[607]: Selected source 2001:4168:1::1
>
> Dec 27 16:37:51 draws chronyd[607]: System clock wrong by 9.542856 seconds, adjustment started
>
> Dec 27 16:38:01 draws chronyd[607]: System clock was stepped by 9.542856 seconds
>
> Dec 27 16:38:01 draws chronyd[607]: Selected source PPS
>
> Dec 27 16:38:07 draws chronyd[607]: Can't synchronise: no required source in selectable sources
>
> Dec 27 16:38:09 draws chronyd[607]: Selected source PPS
>
> Dec 27 16:38:17 draws chronyd[607]: Can't synchronise: no required source in selectable sources
>

>
> pi@draws:~ $ chronyc sources
>
> 210 Number of sources = 7
>
> MS Name/IP address         Stratum Poll Reach LastRx Last sample
>
> ===============================================================================
>
> #x GPS                           0   3   377     6   -131ms[ -131ms] +/-  102ms
>
> #- PPS                           0   3   377     7  -6012ns[-6012ns] +/-  571ns
>
> #- PPS2                          0   4   377    10  -6152ns[-6152ns] +/-  439ns
>
> ^- t1.time.tw1.yahoo.com         2   6   377   116  -3401us[-3401us] +/-   94ms
>
> ^- moe.nexellent.net             2   6   377    62  -1831us[-1831us] +/-   80ms
>
> ^- 2001:470:1f0e:9b0:fed::1      2   6   377     2  +4267us[+4267us] +/-   80ms
>
> ^- ns2.admincmd.com              2   6   377     1   +642us[ +642us] +/-   72ms
>
> pi@draws:~ $ chronyc tracking
>
> Reference ID    : 50505300 (PPS)
>
> Stratum         : 1
>
> Ref time (UTC)  : Thu Dec 27 21:38:05 2018
>
> System time     : 0.000000005 seconds fast of NTP time
>
> Last offset     : +0.000018873 seconds
>
> RMS offset      : 0.000018873 seconds
>
> Frequency       : 6.975 ppm fast
>
> Residual freq   : +0.841 ppm
>
> Skew            : 0.059 ppm
>
> Root delay      : 0.000000 seconds
>
> Root dispersion : 0.001019 seconds
>
> Update interval : 8.0 seconds
>
> Leap status     : Normal
>

>
> . . . .  ONE HOUR LATER . . . selected source becomes PPS2
>

>
> pi@draws:~ $ sudo systemctl status chrony
>
> ? chrony.service - chrony, an NTP client/server
>
>    Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
>
>    Active: active (running) since Thu 2018-12-27 16:33:04 EST; 1h 4min ago
>
>      Docs: man:chronyd(8)
>
>            man:chronyc(1)
>
>            man:chrony.conf(5)
>
>   Process: 562 ExecStart=/usr/sbin/chronyd (code=exited, status=0/SUCCESS)
>
> Main PID: 607 (chronyd)
>
>    CGroup: /system.slice/chrony.service
>
>            +-607 /usr/sbin/chronyd
>

>
> Dec 27 16:33:04 draws systemd[1]: Started chrony, an NTP client/server.
>
> Dec 27 16:37:51 draws chronyd[607]: Selected source 2001:4168:1::1
>
> Dec 27 16:37:51 draws chronyd[607]: System clock wrong by 9.542856 seconds, adjustment started
>
> Dec 27 16:38:01 draws chronyd[607]: System clock was stepped by 9.542856 seconds
>
> Dec 27 16:38:01 draws chronyd[607]: Selected source PPS
>
> Dec 27 16:38:07 draws chronyd[607]: Can't synchronise: no required source in selectable sources
>
> Dec 27 16:38:09 draws chronyd[607]: Selected source PPS
>
> Dec 27 16:38:17 draws chronyd[607]: Can't synchronise: no required source in selectable sources
>
> Dec 27 17:37:33 draws chronyd[607]: Selected source PPS2
>
> Dec 27 17:37:41 draws chronyd[607]: Can't synchronise: no required source in selectable sources
>
> pi@draws:~ $ chronyc sources
>
> 210 Number of sources = 7
>
> MS Name/IP address         Stratum Poll Reach LastRx Last sample
>
> ===============================================================================
>
> #x GPS                           0   3   377    11   -128ms[ -128ms] +/-  102ms
>
> #- PPS                           0   3   377    11   -452ns[ -452ns] +/-  549ns
>
> #- PPS2                          0   4   377    15   -365ns[ -365ns] +/-  282ns
>
> ^- t1.time.tw1.yahoo.com         2   9   377   361  -3063us[-3076us] +/-  103ms
>
> ^- moe.nexellent.net             2   9   377   184  -1854us[-1864us] +/-   79ms
>
> ^- 2001:470:1f0e:9b0:fed::1      2   9   377   377  +4241us[+4228us] +/-   70ms
>
> ^- ns2.admincmd.com              2   9   377   183   +470us[ +459us] +/-   72ms
>
> pi@draws:~ $ chronyc tracking
>
> Reference ID    : 50505332 (PPS2)
>
> Stratum         : 1
>
> Ref time (UTC)  : Thu Dec 27 22:37:26 2018
>
> System time     : 0.000000000 seconds fast of NTP time
>
> Last offset     : +0.000000060 seconds
>
> RMS offset      : 0.000000060 seconds
>
> Frequency       : 6.989 ppm fast
>
> Residual freq   : +0.000 ppm
>
> Skew            : 0.003 ppm
>
> Root delay      : 0.000000 seconds
>
> Root dispersion : 0.000083 seconds
>
> Update interval : 0.0 seconds
>
> Leap status     : Normal
>
> pi@draws:~ $
>

>
> So where is PPS2 coming from and how to have GPSD start running automatically?  Inquiring minds would like to know.
>

>
> Let me know if you require any further information.
>

>
> Cheers es 73,
>
> Daniel  VE3NI / NI2D





--


John D. Hays
Edmonds, WA
K7VE

   


Re: State of GPSD on boot and PPS2 #pps #gpsd #chrony

Basil Gunn
 

First thanks for all the data. It would also be good to see the output of
this script.
cd
n7nix/gps/verify_time.sh

So just some observations from my setup which is a clean boot of the
DRAWS image.

My gpsd also does not start automatically. I will look into that.
It does start when I run gpsmon

If I look for any pps devices I only have one.
Perhaps you can do the following & see what you get.

ls /dev/pps*
/dev/pps0

When I google 'raspberry pi PPS2' it comes up with:
Duracell PPS2 Instant USB charger
Are you powering your RPi with an external battery pack?

Thanks,
/Basil



Daniel VE3NI <dgoodier@...> writes:

Hi,



First let me apologize for what will be a long email.



There has been lots of good discussion and learning going on about the DRAWS hat.



I have been hoping that someone else might be experiencing this issue and would bring up to the group for discussion but so far no one has so it is possible that I am the only one.



I have the DRAWS hat with the GPS antenna.



I have experienced this issue on both beta5 and beta6.



I use the ./app_config.sh core command to configure my system.



I modify /etc/chrony/chrony.conf to uncomment the refclock PPS /dev/pps0 lock GPS trust prefer line and add the lines to broadcast to the local network and allow client on the local network to sync to the rPi.



Upon reboot if I check the state of GPSD is shows:



pi@draws:~ $ sudo systemctl status gpsd

gpsd.service - GPS (Global Positioning System) Daemon

Loaded: loaded (/lib/systemd/system/gpsd.service; indirect; vendor preset: enabled)

Active: inactive (dead)

pi@draws:~ $



In addition when I check the state of CHRONY after the reboot I see:



pi@draws:~ $ sudo systemctl status chrony

chrony.service - chrony, an NTP client/server

Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)

Active: active (running) since Thu 2018-12-27 16:33:04 EST; 3min 56s ago

Docs: man:chronyd(8)

man:chronyc(1)

man:chrony.conf(5)

Process: 562 ExecStart=/usr/sbin/chronyd (code=exited, status=0/SUCCESS)

Main PID: 607 (chronyd)

CGroup: /system.slice/chrony.service

+-607 /usr/sbin/chronyd



Dec 27 16:33:03 draws systemd[1]: Starting chrony, an NTP client/server...

Dec 27 16:33:04 draws chronyd[607]: chronyd version 3.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS

Dec 27 16:33:04 draws chronyd[607]: Frequency 6.975 +/- 0.038 ppm read from /var/lib/chrony/chrony.drift

Dec 27 16:33:04 draws systemd[1]: Started chrony, an NTP client/server.



It is only when I either specifically start the GPSD (sudo systemctl start gpsd) or open a terminal window and run gpsmon that the GPSD and CHRONY status are what I expect.



pi@draws:~ $ sudo systemctl status gpsd

gpsd.service - GPS (Global Positioning System) Daemon

Loaded: loaded (/lib/systemd/system/gpsd.service; indirect; vendor preset: enabled)

Active: active (running) since Thu 2018-12-27 16:37:28 EST; 7s ago

Main PID: 1318 (gpsd)

CGroup: /system.slice/gpsd.service

+-1318 /usr/sbin/gpsd -N -n /dev/ttySC0 /dev/pps0



Dec 27 16:37:28 draws systemd[1]: Started GPS (Global Positioning System) Daemon.



pi@draws:~ $ sudo systemctl status chrony

chrony.service - chrony, an NTP client/server

Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)

Active: active (running) since Thu 2018-12-27 16:33:04 EST; 4min 57s ago

Docs: man:chronyd(8)

man:chronyc(1)

man:chrony.conf(5)

Process: 562 ExecStart=/usr/sbin/chronyd (code=exited, status=0/SUCCESS)

Main PID: 607 (chronyd)

CGroup: /system.slice/chrony.service

+-607 /usr/sbin/chronyd



Dec 27 16:33:03 draws systemd[1]: Starting chrony, an NTP client/server...

Dec 27 16:33:04 draws chronyd[607]: chronyd version 3.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS

Dec 27 16:33:04 draws chronyd[607]: Frequency 6.975 +/- 0.038 ppm read from /var/lib/chrony/chrony.drift

Dec 27 16:33:04 draws systemd[1]: Started chrony, an NTP client/server.

Dec 27 16:37:51 draws chronyd[607]: Selected source 2001:4168:1::1

Dec 27 16:37:51 draws chronyd[607]: System clock wrong by 9.542856 seconds, adjustment started

Dec 27 16:38:01 draws chronyd[607]: System clock was stepped by 9.542856 seconds

Dec 27 16:38:01 draws chronyd[607]: Selected source PPS

Dec 27 16:38:07 draws chronyd[607]: Can't synchronise: no required source in selectable sources



Any suggestion as to which step I might have missed? It almost looks like it is waiting for a request before it starts. I know that I can force it to start on reboot by adding commands to systemd but would like to know if it is working by design before I make any changes.



This brings leads me to by question.



Where is PPS2 coming from? PPS2 is not defined in my chrony.conf file but does show up when I run chronyc sources.



pi@draws:~ $ sudo systemctl status chrony

? chrony.service - chrony, an NTP client/server

Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)

Active: active (running) since Thu 2018-12-27 16:33:04 EST; 13min ago

Docs: man:chronyd(8)

man:chronyc(1)

man:chrony.conf(5)

Process: 562 ExecStart=/usr/sbin/chronyd (code=exited, status=0/SUCCESS)

Main PID: 607 (chronyd)

CGroup: /system.slice/chrony.service

+-607 /usr/sbin/chronyd



Dec 27 16:33:04 draws chronyd[607]: chronyd version 3.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS

Dec 27 16:33:04 draws chronyd[607]: Frequency 6.975 +/- 0.038 ppm read from /var/lib/chrony/chrony.drift

Dec 27 16:33:04 draws systemd[1]: Started chrony, an NTP client/server.

Dec 27 16:37:51 draws chronyd[607]: Selected source 2001:4168:1::1

Dec 27 16:37:51 draws chronyd[607]: System clock wrong by 9.542856 seconds, adjustment started

Dec 27 16:38:01 draws chronyd[607]: System clock was stepped by 9.542856 seconds

Dec 27 16:38:01 draws chronyd[607]: Selected source PPS

Dec 27 16:38:07 draws chronyd[607]: Can't synchronise: no required source in selectable sources

Dec 27 16:38:09 draws chronyd[607]: Selected source PPS

Dec 27 16:38:17 draws chronyd[607]: Can't synchronise: no required source in selectable sources



pi@draws:~ $ chronyc sources

210 Number of sources = 7

MS Name/IP address Stratum Poll Reach LastRx Last sample

===============================================================================

#x GPS 0 3 377 6 -131ms[ -131ms] +/- 102ms

#- PPS 0 3 377 7 -6012ns[-6012ns] +/- 571ns

#- PPS2 0 4 377 10 -6152ns[-6152ns] +/- 439ns

^- t1.time.tw1.yahoo.com 2 6 377 116 -3401us[-3401us] +/- 94ms

^- moe.nexellent.net 2 6 377 62 -1831us[-1831us] +/- 80ms

^- 2001:470:1f0e:9b0:fed::1 2 6 377 2 +4267us[+4267us] +/- 80ms

^- ns2.admincmd.com 2 6 377 1 +642us[ +642us] +/- 72ms

pi@draws:~ $ chronyc tracking

Reference ID : 50505300 (PPS)

Stratum : 1

Ref time (UTC) : Thu Dec 27 21:38:05 2018

System time : 0.000000005 seconds fast of NTP time

Last offset : +0.000018873 seconds

RMS offset : 0.000018873 seconds

Frequency : 6.975 ppm fast

Residual freq : +0.841 ppm

Skew : 0.059 ppm

Root delay : 0.000000 seconds

Root dispersion : 0.001019 seconds

Update interval : 8.0 seconds

Leap status : Normal



. . . . ONE HOUR LATER . . . selected source becomes PPS2



pi@draws:~ $ sudo systemctl status chrony

? chrony.service - chrony, an NTP client/server

Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)

Active: active (running) since Thu 2018-12-27 16:33:04 EST; 1h 4min ago

Docs: man:chronyd(8)

man:chronyc(1)

man:chrony.conf(5)

Process: 562 ExecStart=/usr/sbin/chronyd (code=exited, status=0/SUCCESS)

Main PID: 607 (chronyd)

CGroup: /system.slice/chrony.service

+-607 /usr/sbin/chronyd



Dec 27 16:33:04 draws systemd[1]: Started chrony, an NTP client/server.

Dec 27 16:37:51 draws chronyd[607]: Selected source 2001:4168:1::1

Dec 27 16:37:51 draws chronyd[607]: System clock wrong by 9.542856 seconds, adjustment started

Dec 27 16:38:01 draws chronyd[607]: System clock was stepped by 9.542856 seconds

Dec 27 16:38:01 draws chronyd[607]: Selected source PPS

Dec 27 16:38:07 draws chronyd[607]: Can't synchronise: no required source in selectable sources

Dec 27 16:38:09 draws chronyd[607]: Selected source PPS

Dec 27 16:38:17 draws chronyd[607]: Can't synchronise: no required source in selectable sources

Dec 27 17:37:33 draws chronyd[607]: Selected source PPS2

Dec 27 17:37:41 draws chronyd[607]: Can't synchronise: no required source in selectable sources

pi@draws:~ $ chronyc sources

210 Number of sources = 7

MS Name/IP address Stratum Poll Reach LastRx Last sample

===============================================================================

#x GPS 0 3 377 11 -128ms[ -128ms] +/- 102ms

#- PPS 0 3 377 11 -452ns[ -452ns] +/- 549ns

#- PPS2 0 4 377 15 -365ns[ -365ns] +/- 282ns

^- t1.time.tw1.yahoo.com 2 9 377 361 -3063us[-3076us] +/- 103ms

^- moe.nexellent.net 2 9 377 184 -1854us[-1864us] +/- 79ms

^- 2001:470:1f0e:9b0:fed::1 2 9 377 377 +4241us[+4228us] +/- 70ms

^- ns2.admincmd.com 2 9 377 183 +470us[ +459us] +/- 72ms

pi@draws:~ $ chronyc tracking

Reference ID : 50505332 (PPS2)

Stratum : 1

Ref time (UTC) : Thu Dec 27 22:37:26 2018

System time : 0.000000000 seconds fast of NTP time

Last offset : +0.000000060 seconds

RMS offset : 0.000000060 seconds

Frequency : 6.989 ppm fast

Residual freq : +0.000 ppm

Skew : 0.003 ppm

Root delay : 0.000000 seconds

Root dispersion : 0.000083 seconds

Update interval : 0.0 seconds

Leap status : Normal

pi@draws:~ $



So where is PPS2 coming from and how to have GPSD start running automatically? Inquiring minds would like to know.



Let me know if you require any further information.



Cheers es 73,

Daniel VE3NI / NI2D


State of GPSD on boot and PPS2 #pps #gpsd #chrony

Daniel VE3NI
 

Hi,

 

First let me apologize for what will be a long email.

 

There has been lots of good discussion and learning going on about the DRAWS hat.

 

I have been hoping that someone else might be experiencing this issue and would bring up to the group for discussion but so far no one has so it is possible that I am the only one.

 

I have the DRAWS hat with the GPS antenna.

 

I have experienced this issue on both beta5 and beta6.

 

I use the ./app_config.sh core command to configure my system.

 

I modify /etc/chrony/chrony.conf to uncomment the refclock PPS /dev/pps0 lock GPS trust prefer line and add the lines to broadcast to the local network and allow client on the local network to sync to the rPi.

 

Upon reboot if I check the state of GPSD is shows:

 

pi@draws:~ $ sudo systemctl status gpsd

gpsd.service - GPS (Global Positioning System) Daemon

   Loaded: loaded (/lib/systemd/system/gpsd.service; indirect; vendor preset: enabled)

   Active: inactive (dead)

pi@draws:~ $

 

In addition when I check the state of CHRONY after the reboot I see:

 

pi@draws:~ $ sudo systemctl status chrony

chrony.service - chrony, an NTP client/server

   Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)

   Active: active (running) since Thu 2018-12-27 16:33:04 EST; 3min 56s ago

     Docs: man:chronyd(8)

           man:chronyc(1)

           man:chrony.conf(5)

  Process: 562 ExecStart=/usr/sbin/chronyd (code=exited, status=0/SUCCESS)

Main PID: 607 (chronyd)

   CGroup: /system.slice/chrony.service

           +-607 /usr/sbin/chronyd

 

Dec 27 16:33:03 draws systemd[1]: Starting chrony, an NTP client/server...

Dec 27 16:33:04 draws chronyd[607]: chronyd version 3.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS

Dec 27 16:33:04 draws chronyd[607]: Frequency 6.975 +/- 0.038 ppm read from /var/lib/chrony/chrony.drift

Dec 27 16:33:04 draws systemd[1]: Started chrony, an NTP client/server.

 

It is only when I either specifically start the GPSD (sudo systemctl start gpsd) or open a terminal window and run gpsmon that the GPSD and CHRONY status are what I expect.

 

pi@draws:~ $ sudo systemctl status gpsd

gpsd.service - GPS (Global Positioning System) Daemon

   Loaded: loaded (/lib/systemd/system/gpsd.service; indirect; vendor preset: enabled)

   Active: active (running) since Thu 2018-12-27 16:37:28 EST; 7s ago

Main PID: 1318 (gpsd)

   CGroup: /system.slice/gpsd.service

           +-1318 /usr/sbin/gpsd -N -n /dev/ttySC0 /dev/pps0

 

Dec 27 16:37:28 draws systemd[1]: Started GPS (Global Positioning System) Daemon.

 

pi@draws:~ $ sudo systemctl status chrony

chrony.service - chrony, an NTP client/server

   Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)

   Active: active (running) since Thu 2018-12-27 16:33:04 EST; 4min 57s ago

     Docs: man:chronyd(8)

           man:chronyc(1)

           man:chrony.conf(5)

  Process: 562 ExecStart=/usr/sbin/chronyd (code=exited, status=0/SUCCESS)

Main PID: 607 (chronyd)

   CGroup: /system.slice/chrony.service

           +-607 /usr/sbin/chronyd

 

Dec 27 16:33:03 draws systemd[1]: Starting chrony, an NTP client/server...

Dec 27 16:33:04 draws chronyd[607]: chronyd version 3.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS

Dec 27 16:33:04 draws chronyd[607]: Frequency 6.975 +/- 0.038 ppm read from /var/lib/chrony/chrony.drift

Dec 27 16:33:04 draws systemd[1]: Started chrony, an NTP client/server.

Dec 27 16:37:51 draws chronyd[607]: Selected source 2001:4168:1::1

Dec 27 16:37:51 draws chronyd[607]: System clock wrong by 9.542856 seconds, adjustment started

Dec 27 16:38:01 draws chronyd[607]: System clock was stepped by 9.542856 seconds

Dec 27 16:38:01 draws chronyd[607]: Selected source PPS

Dec 27 16:38:07 draws chronyd[607]: Can't synchronise: no required source in selectable sources

 

Any suggestion as to which step I might have missed?  It almost looks like it is waiting for a request before it starts.  I know that I can force it to start on reboot by adding commands to systemd but would like to know if it is working by design before I make any changes.

 

This brings leads me to by question.

 

Where is PPS2 coming from?  PPS2 is not defined in my chrony.conf file but does show up when I run chronyc sources.

 

pi@draws:~ $ sudo systemctl status chrony

? chrony.service - chrony, an NTP client/server

   Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)

   Active: active (running) since Thu 2018-12-27 16:33:04 EST; 13min ago

     Docs: man:chronyd(8)

           man:chronyc(1)

           man:chrony.conf(5)

  Process: 562 ExecStart=/usr/sbin/chronyd (code=exited, status=0/SUCCESS)

Main PID: 607 (chronyd)

   CGroup: /system.slice/chrony.service

           +-607 /usr/sbin/chronyd

 

Dec 27 16:33:04 draws chronyd[607]: chronyd version 3.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +SIGND +ASYNCDNS

Dec 27 16:33:04 draws chronyd[607]: Frequency 6.975 +/- 0.038 ppm read from /var/lib/chrony/chrony.drift

Dec 27 16:33:04 draws systemd[1]: Started chrony, an NTP client/server.

Dec 27 16:37:51 draws chronyd[607]: Selected source 2001:4168:1::1

Dec 27 16:37:51 draws chronyd[607]: System clock wrong by 9.542856 seconds, adjustment started

Dec 27 16:38:01 draws chronyd[607]: System clock was stepped by 9.542856 seconds

Dec 27 16:38:01 draws chronyd[607]: Selected source PPS

Dec 27 16:38:07 draws chronyd[607]: Can't synchronise: no required source in selectable sources

Dec 27 16:38:09 draws chronyd[607]: Selected source PPS

Dec 27 16:38:17 draws chronyd[607]: Can't synchronise: no required source in selectable sources

 

pi@draws:~ $ chronyc sources

210 Number of sources = 7

MS Name/IP address         Stratum Poll Reach LastRx Last sample

===============================================================================

#x GPS                           0   3   377     6   -131ms[ -131ms] +/-  102ms

#- PPS                           0   3   377     7  -6012ns[-6012ns] +/-  571ns

#- PPS2                          0   4   377    10  -6152ns[-6152ns] +/-  439ns

^- t1.time.tw1.yahoo.com         2   6   377   116  -3401us[-3401us] +/-   94ms

^- moe.nexellent.net             2   6   377    62  -1831us[-1831us] +/-   80ms

^- 2001:470:1f0e:9b0:fed::1      2   6   377     2  +4267us[+4267us] +/-   80ms

^- ns2.admincmd.com              2   6   377     1   +642us[ +642us] +/-   72ms

pi@draws:~ $ chronyc tracking

Reference ID    : 50505300 (PPS)

Stratum         : 1

Ref time (UTC)  : Thu Dec 27 21:38:05 2018

System time     : 0.000000005 seconds fast of NTP time

Last offset     : +0.000018873 seconds

RMS offset      : 0.000018873 seconds

Frequency       : 6.975 ppm fast

Residual freq   : +0.841 ppm

Skew            : 0.059 ppm

Root delay      : 0.000000 seconds

Root dispersion : 0.001019 seconds

Update interval : 8.0 seconds

Leap status     : Normal

 

. . . .  ONE HOUR LATER . . . selected source becomes PPS2

 

pi@draws:~ $ sudo systemctl status chrony

? chrony.service - chrony, an NTP client/server

   Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)

   Active: active (running) since Thu 2018-12-27 16:33:04 EST; 1h 4min ago

     Docs: man:chronyd(8)

           man:chronyc(1)

           man:chrony.conf(5)

  Process: 562 ExecStart=/usr/sbin/chronyd (code=exited, status=0/SUCCESS)

Main PID: 607 (chronyd)

   CGroup: /system.slice/chrony.service

           +-607 /usr/sbin/chronyd

 

Dec 27 16:33:04 draws systemd[1]: Started chrony, an NTP client/server.

Dec 27 16:37:51 draws chronyd[607]: Selected source 2001:4168:1::1

Dec 27 16:37:51 draws chronyd[607]: System clock wrong by 9.542856 seconds, adjustment started

Dec 27 16:38:01 draws chronyd[607]: System clock was stepped by 9.542856 seconds

Dec 27 16:38:01 draws chronyd[607]: Selected source PPS

Dec 27 16:38:07 draws chronyd[607]: Can't synchronise: no required source in selectable sources

Dec 27 16:38:09 draws chronyd[607]: Selected source PPS

Dec 27 16:38:17 draws chronyd[607]: Can't synchronise: no required source in selectable sources

Dec 27 17:37:33 draws chronyd[607]: Selected source PPS2

Dec 27 17:37:41 draws chronyd[607]: Can't synchronise: no required source in selectable sources

pi@draws:~ $ chronyc sources

210 Number of sources = 7

MS Name/IP address         Stratum Poll Reach LastRx Last sample

===============================================================================

#x GPS                           0   3   377    11   -128ms[ -128ms] +/-  102ms

#- PPS                           0   3   377    11   -452ns[ -452ns] +/-  549ns

#- PPS2                          0   4   377    15   -365ns[ -365ns] +/-  282ns

^- t1.time.tw1.yahoo.com         2   9   377   361  -3063us[-3076us] +/-  103ms

^- moe.nexellent.net             2   9   377   184  -1854us[-1864us] +/-   79ms

^- 2001:470:1f0e:9b0:fed::1      2   9   377   377  +4241us[+4228us] +/-   70ms

^- ns2.admincmd.com              2   9   377   183   +470us[ +459us] +/-   72ms

pi@draws:~ $ chronyc tracking

Reference ID    : 50505332 (PPS2)

Stratum         : 1

Ref time (UTC)  : Thu Dec 27 22:37:26 2018

System time     : 0.000000000 seconds fast of NTP time

Last offset     : +0.000000060 seconds

RMS offset      : 0.000000060 seconds

Frequency       : 6.989 ppm fast

Residual freq   : +0.000 ppm

Skew            : 0.003 ppm

Root delay      : 0.000000 seconds

Root dispersion : 0.000083 seconds

Update interval : 0.0 seconds

Leap status     : Normal

pi@draws:~ $

 

So where is PPS2 coming from and how to have GPSD start running automatically?  Inquiring minds would like to know.

 

Let me know if you require any further information.

 

Cheers es 73,

Daniel  VE3NI / NI2D


Re: Setting up D-STAR repeater/ircdbbgateway on DRAWS #draws #dtarrepeater

 

Wait for an update of information on this application

On Thu, Dec 27, 2018 at 12:46 PM Jack Spitznagel <kd4iz@...> wrote:

Digital Voice repeater Gurus,

 

Are there any significant changes needed to the UDRC instructions for setting up dstarrepeater/ircdbbgateway on DRAWS or can the existing ones on the Wiki be used?

 

TIA,

 

KD4IZ

Jack Spitznagel

FM19oo

 

 


--
J Spitznagel
Science River LLC
KD4IZ



--


John D. Hays
Edmonds, WA
K7VE

   


Re: Setting up auto time with draws gps #ntp #chrony #gps #clock #battery

Steve, N9VW
 

Wouldn't the almanac become stale as well, say after 6 months? Wouldn't that be about the same thing as a cold start when the system is booted back up?

73 de N9VW, Steve

On 12/27/2018 10:34 AM, John D Hays - K7VE wrote:
On the go-kit.  The backup battery is only good for a cumulative 40 days with no power attached to the DRAWS™ HAT.  So if you have let it sit for 6-months, you will need to replace the battery and resync the RTC using the built-in GPS (w/Antenna).

I would suggest a blister pack of batteries in the go-kit.  They are relatively inexpensive and have decent shelf life.

On Thu, Dec 27, 2018 at 9:41 AM Budd Churchward <budd@...> wrote:
Sorry for not making myself clear. The clock problem was something I saw
while using the UDRC-II which has no GPS. The Rpi does a real lousy job of
keeping time all by itself. One of the best things about the new DRAWS is
that we now have a solution. The GPS and the RTC with back up battery are a
welcome addition to the digital controller. It looks like we need to give
the board a chance to see the satellites and set up the RTC. Then we can
tuck DRAWS into our Go-Kit and it will be ready when we need it. The back up
battery is an important part of this plan.

73 Budd WB7FHC
--


John D. Hays
Edmonds, WA
K7VE

   



Setting up D-STAR repeater/ircdbbgateway on DRAWS #draws #dtarrepeater

Jack Spitznagel
 

Digital Voice repeater Gurus,

 

Are there any significant changes needed to the UDRC instructions for setting up dstarrepeater/ircdbbgateway on DRAWS or can the existing ones on the Wiki be used?

 

TIA,

 

KD4IZ

Jack Spitznagel

FM19oo

 

 


--
J Spitznagel
Science River LLC
KD4IZ


Keying FreeDV with GPIO #draws #freedv

Jack Spitznagel
 

John, Basil, Bryan, adopters,

 

I am playing with setting up FreeDV (1.1).  Anyone successfully done it with DRAWS yet? I can get it to begin to receive, then it appears to stutter to a halt. I will have to compile the latest version (1.3.1-3) as the repository is on 1.1 and both bugfixes and features are missing. Before I waste a bunch of time on this, a key question:

 

PTT keying with GPIO requires something like a “/dev/hidraw0|1|3” declaration in the PTT box panel ahead of entry for GPIO pin #. I will use pin 12. What is the correct “/dev/*name* to put in the entry box?

 

Thanks for any hint you can provide.

 

KD4IZ

Jack Spitznagel

FM19oo

 

 

 

.


--
J Spitznagel
Science River LLC
KD4IZ


Re: Setting up auto time with draws gps #ntp #chrony #gps #clock #battery

 

On the go-kit.  The backup battery is only good for a cumulative 40 days with no power attached to the DRAWS™ HAT.  So if you have let it sit for 6-months, you will need to replace the battery and resync the RTC using the built-in GPS (w/Antenna).

I would suggest a blister pack of batteries in the go-kit.  They are relatively inexpensive and have decent shelf life.

On Thu, Dec 27, 2018 at 9:41 AM Budd Churchward <budd@...> wrote:
Sorry for not making myself clear. The clock problem was something I saw
while using the UDRC-II which has no GPS. The Rpi does a real lousy job of
keeping time all by itself. One of the best things about the new DRAWS is
that we now have a solution. The GPS and the RTC with back up battery are a
welcome addition to the digital controller. It looks like we need to give
the board a chance to see the satellites and set up the RTC. Then we can
tuck DRAWS into our Go-Kit and it will be ready when we need it. The back up
battery is an important part of this plan.

73 Budd WB7FHC
--


John D. Hays
Edmonds, WA
K7VE

   


Re: Cant turn off direwolf and ax25 #configuration #management #draws #direwolf #ax25

Basil Gunn
 

I appreciate your comments. It's a like visiting another country where no
one speaks English. It's easy to get lost. We stumble around and hope that
we end up somewhere safe. 😊. I probably should not have ventured into the
first order of draws but I couldn't resist because it's exactly what I
wanted to simplify my portable station. I have it working with wsjt-x and
js8call. I am proud of that.
Great to hear you have some things working.

On the other hand, if only experts had purchased the first edition, then
the developers would get a totally skewed impression.
Clear and simple user
Please know your problems & feed back are very important to us.

guides are going to he critical to the success of this project. This is a
human endeavour, not just technology.
I am using the wiki at groups.io now and if you check it out you should
see I've made an attempt to fix problems that you previously brought up.

https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Image-getting-started


I really want this to work. I think it's a brilliant idea and I support
their work completely.
Please keep using the forum for suggestions & feedback.
/Basil

Thanks again, Joeseph.
Bob Orrett. Ve3obo


On Thu, Dec 27, 2018, 09:04 Joseph Vilardo <@k3jv wrote:

Bob

I have been had more than once with the underscore. Depending on what you
view it with, printed or on a screen, it can disappear! I found that the
disappearing act is most vulnerable on a screen, the cursor can hide it.


Re: Unable to resolve hostname with RPi Draws

Basil Gunn
 

Use the program

*sudo raspi-config*

to set the hostname, and then reboot.
You do not have to use raspi-config and if you do then some things will not be
configured properly later on that require a valid mail name.

The initial script that you run, app_config.sh core,
prompts you for a host name change and sets:

- hosts
- hostname
- mailname

/Basil


Re: Setting up auto time with draws gps #ntp #chrony #gps #clock #battery

Budd Churchward
 

Sorry for not making myself clear. The clock problem was something I saw while using the UDRC-II which has no GPS. The Rpi does a real lousy job of keeping time all by itself. One of the best things about the new DRAWS is that we now have a solution. The GPS and the RTC with back up battery are a welcome addition to the digital controller. It looks like we need to give the board a chance to see the satellites and set up the RTC. Then we can tuck DRAWS into our Go-Kit and it will be ready when we need it. The back up battery is an important part of this plan.

73 Budd WB7FHC

-----Original Message-----
From: Basil Gunn
Sent: Wednesday, December 26, 2018 10:30 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Setting up auto time with draws gps


Budd Churchward <budd@...> writes:

My experience with NTP service is that you need to keep it active. If
you let it set the clock on the Rpi and then keep running without the
internet connection the time on the clock gets pretty far off quite
quickly. Like one day later it is way off.
It's a little confusing because the DRAWS image uses chronyd for the NTP
service and NOT ntpd.
So there are 3 situations:

No gps antenna
No Internet connection
No gps antenna or Internet connection

I have a script that dumps the world for chrony here:
n7nix/gps/verify_time.sh

It's also good to see how many satellites the gps is picking up with:
gpsmon

Usually if your clock is off by a lot & you are connected to the
Internet you can kick it in the butt as root with:

chronyc makestep

/Basil

Budd WB7FHC

From: John D Hays - K7VE
Sent: Wednesday, December 26, 2018 5:34 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Setting up auto time with draws gps

As has been discussed previously. NTP services like chrony slowly adjust the system clock based on information obtained from both ntp servers and refclocks (like the GPS and PPS).

Basil has created a script that verifies time at ~/n7nix/gps/verify_time.sh

The command line to do a quick update of the clock is: sudo chronyc makestep


You can verify your clocks with: chronyc sources -v


The battery backed RTC in the GPS must be set by the GPS once it has acquired the time reference from the satellites.

In my opinion, NTP time synchronization works best if the computer is not powered down and the Raspberry Pi is well suited to continuous operation at low power consumption. With the computer running continuously the chrony daemon can keep the system clock well synchronized whether using the GPS/PPS and/or network connections. (It ignores sources that are not reporting or are way out of sync.)



On Wed, Dec 26, 2018, 16:16 Art - KC7SDA <@nouse4anick wrote:

i think you have to have the battery installed for the rtc.... it takes a bit to get the signal and then set the clock.

I'm assuming you did the chrony and gps install as described in the wiki?


right port and Wsjtx #draws #configuration

Joseph Vilardo
 

I want to configure wsjtx on the Pi DRAWS image to function with my TS590. I think I have two options. One is to use the usb connection and the CODEC that is part of the ts 590 and use a usb port on the Rpi/Draws combo. Second option is to use the "right hand port" on the draws and connect to the TS590 through ACC socket 2 of the 590. ACC socket 2 gives me audio out, audio in an ptt. If I use port 2 on the Draws how do I make port active so wsjt sees this as the audio codec source? I am not sure there is an option in WSJT for the PTT on the GPIO of the pi as there is for FLDIGI?  I believe there is a dtr/rts option for PTT with wsjtx
I would prefer to use option 2 but it may be more trouble than what it's worth.
Joe


Re: Cant turn off direwolf and ax25 #configuration #management #draws #direwolf #ax25

Bob Orrett <boborrett@...>
 

Thanks Joeseph
I appreciate your comments. It's a like visiting another country where no one speaks English.  It's easy to get lost. We stumble around and hope that we end up somewhere safe. 😊. I probably should not have ventured into the first order of draws but I couldn't resist because it's exactly what I wanted to simplify my portable station. I have it working with wsjt-x and js8call. I am proud of that. 
On the other hand, if only experts had purchased the first edition, then the developers would get a totally skewed impression. Clear and simple user guides are going to he critical to the success of this project. This is a human endeavour, not just technology. 
I really want this to work. I think it's a brilliant idea and I support their work completely. 
Thanks again, Joeseph.
Bob Orrett.  Ve3obo 


On Thu, Dec 27, 2018, 09:04 Joseph Vilardo <jvilardo@... wrote:

Bob

I have been had more than once with the underscore. Depending on what you view it with, printed or on a screen, it can disappear! I found that the disappearing act is most vulnerable on a screen, the cursor can hide it.

There are some other, what I call nuances but an experienced Linux programmer calls "notation conventions"  in Basil's instructions. I am not an experienced Linux programmer and if I repeatedly try a command and get stumped, sometimes I trying variations of the commands until I get it to work. Many times I have to walk away and come back later.  The red tilde is still a mystery for me and if you print the instructions the red tilde show up as a mere suggestion, it is really hard to see.

I found some other anomalies in getting FLDIGI to work that are not shown in the instructions that I will try to get clarified by Basil but for now I have it running without issues but also not as the instructions tell you. I hate to burden the guy with "MY" concerns or problems when there are many guys wrestling with stopping direwolf and ax25 or just getting the image core verified.

If you venture into fldigi and run into problems let me know I have some minor changes that worked for me.

73 K3JV Joe

On 12/26/2018 9:25 AM, Bob Orrett wrote:
Finally after many frustrating  days, wsjtx and js8call are working with the draws hat. It was my fault and probably a rookie mistake but I will explain in case others are making the same mistake.  It is in Basil's script. I read the script each time that I loaded a new image but I misinterpreted  how to use it. 
There is a line that says, "if you want direwolf functionality, do this". Well , I didnt want direwolf so I didn't do the script below. A mistake! When I finally decided to run that script everything worked. I was always wondering  why I was never asked for a password (nwcompass). 
But even then it took many tries before i finally noticed that between "app" and "config" there is an underscore "_" not a dash"-". I have never seen and underscore in a command before and the print is very small. I realize now that i should get my email with the raspberry pi so that i can cut and paste instead of read and type. Linux doesn't help you when you make a typing error. Just says that the command does not exist. That make me think there is something wrong with the program, not my typing. 
I am a retired teacher and one thing i learned is that giving foolproof instructions is very difficult. There are often assumptions made by the reader and the writer that can result is complete misunderstandings. Adding the reason for a given command is a big help. Don't worry about insulting the reader, give hints and examples. Explain what the response to a given command should be.
Well, i feels good to be over this hurdle, on to the next. 
Bob ve3obo.


Re: Cant turn off direwolf and ax25 #configuration #management #draws #direwolf #ax25

Joseph Vilardo
 

Bob

I have been had more than once with the underscore. Depending on what you view it with, printed or on a screen, it can disappear! I found that the disappearing act is most vulnerable on a screen, the cursor can hide it.

There are some other, what I call nuances but an experienced Linux programmer calls "notation conventions"  in Basil's instructions. I am not an experienced Linux programmer and if I repeatedly try a command and get stumped, sometimes I trying variations of the commands until I get it to work. Many times I have to walk away and come back later.  The red tilde is still a mystery for me and if you print the instructions the red tilde show up as a mere suggestion, it is really hard to see.

I found some other anomalies in getting FLDIGI to work that are not shown in the instructions that I will try to get clarified by Basil but for now I have it running without issues but also not as the instructions tell you. I hate to burden the guy with "MY" concerns or problems when there are many guys wrestling with stopping direwolf and ax25 or just getting the image core verified.

If you venture into fldigi and run into problems let me know I have some minor changes that worked for me.

73 K3JV Joe

On 12/26/2018 9:25 AM, Bob Orrett wrote:
Finally after many frustrating  days, wsjtx and js8call are working with the draws hat. It was my fault and probably a rookie mistake but I will explain in case others are making the same mistake.  It is in Basil's script. I read the script each time that I loaded a new image but I misinterpreted  how to use it. 
There is a line that says, "if you want direwolf functionality, do this". Well , I didnt want direwolf so I didn't do the script below. A mistake! When I finally decided to run that script everything worked. I was always wondering  why I was never asked for a password (nwcompass). 
But even then it took many tries before i finally noticed that between "app" and "config" there is an underscore "_" not a dash"-". I have never seen and underscore in a command before and the print is very small. I realize now that i should get my email with the raspberry pi so that i can cut and paste instead of read and type. Linux doesn't help you when you make a typing error. Just says that the command does not exist. That make me think there is something wrong with the program, not my typing. 
I am a retired teacher and one thing i learned is that giving foolproof instructions is very difficult. There are often assumptions made by the reader and the writer that can result is complete misunderstandings. Adding the reason for a given command is a big help. Don't worry about insulting the reader, give hints and examples. Explain what the response to a given command should be.
Well, i feels good to be over this hurdle, on to the next. 
Bob ve3obo.


Re: Setting up auto time with draws gps #ntp #chrony #gps #clock #battery

 

Budd,

If you have the GPS attached as a refclock, and it is active, it is actually a better time source than the Internet ntp servers.



On Wed, Dec 26, 2018 at 9:24 PM Budd Churchward <budd@...> wrote:
My experience with NTP service is that you need to keep it active. If you let it set the clock on the Rpi and then keep running without the internet connection the time on the clock gets pretty far off quite quickly. Like one day later it is way off.
 
Budd WB7FHC
 
Sent: Wednesday, December 26, 2018 5:34 PM
Subject: Re: [udrc] Setting up auto time with draws gps
 
As has been discussed previously.  NTP services like chrony slowly adjust the system clock based on information obtained from both ntp servers and refclocks (like the GPS and PPS).
 
Basil has created a script that verifies time at ~/n7nix/gps/verify_time.sh
 
The command line to do a quick update of the clock is:   sudo chronyc makestep

You can verify your clocks with: chronyc sources -v

The battery backed RTC in the GPS must be set by the GPS once it has acquired the time reference from the satellites.
 
In my opinion, NTP time synchronization works best if the computer is not powered down and the Raspberry Pi is well suited to continuous operation at low power consumption.  With the computer running continuously the chrony daemon can keep the system clock well synchronized whether using the GPS/PPS and/or network connections.  (It ignores sources that are not reporting or are way out of sync.)

 
 
On Wed, Dec 26, 2018, 16:16 Art - KC7SDA <nouse4anick@... wrote:
i think you have to have the battery installed for the rtc.... it takes a bit to get the signal and then set the clock.

I'm assuming you did the chrony and gps install as described in the wiki?



--


John D. Hays
Edmonds, WA
K7VE

   


Re: Unable to resolve hostname with RPi Draws

 

Use the program 

sudo raspi-config

to set the hostname, and then reboot.


On Wed, Dec 26, 2018 at 10:15 PM Basil Gunn <basil@...> wrote:

> I think I screwed up during installation of draws beta 6. At one point
> I was asked for a hostname. So I made one up and entered "bobspi". Now
> I am often getting
>
>   "sudo: unable to resolve host bobspi"

Usually get this symptom if you set the hostname then do not do a
reboot. See instructions here:
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started
Note the "Now reboot your RPi" after you run ./app_config.sh core

What do you get when you run:

hostname

if you do not get 'bobspi' then reboot & type: hostname again.


> when I enter commands in the terminal.  I am not sure what problems
> this may be causing but I have been unsuccessful at getting gpsd to
> set my system time after a reboot and this host name problem may be
> the cause. I dont know.  Do I need to fix this?  How do I fix this?

as root run:
chronyc makestep

Then send me the output of:
cd
n7nix/gps/verify_time.sh

/Basil





--


John D. Hays
Edmonds, WA
K7VE

   


Re: Setting up auto time with draws gps #ntp #chrony #gps #clock #battery

Basil Gunn
 

Budd Churchward <budd@...> writes:

My experience with NTP service is that you need to keep it active. If
you let it set the clock on the Rpi and then keep running without the
internet connection the time on the clock gets pretty far off quite
quickly. Like one day later it is way off.
It's a little confusing because the DRAWS image uses chronyd for the NTP
service and NOT ntpd.
So there are 3 situations:

No gps antenna
No Internet connection
No gps antenna or Internet connection

I have a script that dumps the world for chrony here:
n7nix/gps/verify_time.sh

It's also good to see how many satellites the gps is picking up with:
gpsmon

Usually if your clock is off by a lot & you are connected to the
Internet you can kick it in the butt as root with:

chronyc makestep

/Basil

Budd WB7FHC

From: John D Hays - K7VE
Sent: Wednesday, December 26, 2018 5:34 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Setting up auto time with draws gps

As has been discussed previously. NTP services like chrony slowly adjust the system clock based on information obtained from both ntp servers and refclocks (like the GPS and PPS).

Basil has created a script that verifies time at ~/n7nix/gps/verify_time.sh

The command line to do a quick update of the clock is: sudo chronyc makestep


You can verify your clocks with: chronyc sources -v


The battery backed RTC in the GPS must be set by the GPS once it has acquired the time reference from the satellites.

In my opinion, NTP time synchronization works best if the computer is not powered down and the Raspberry Pi is well suited to continuous operation at low power consumption. With the computer running continuously the chrony daemon can keep the system clock well synchronized whether using the GPS/PPS and/or network connections. (It ignores sources that are not reporting or are way out of sync.)



On Wed, Dec 26, 2018, 16:16 Art - KC7SDA <@nouse4anick wrote:

i think you have to have the battery installed for the rtc.... it takes a bit to get the signal and then set the clock.

I'm assuming you did the chrony and gps install as described in the wiki?


Re: Link to DRAWS image not working?

Basil Gunn
 

There is a link to the download site here:
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-Started
click on 'Go to the download site'

It's this: http://nwdig.net/downloads/

The following also works but it just takes you to the above url.
images.nwdigitalradio.com/downloads

/Basil

Tom Velvin <@K7TMV> writes:

Julie,

You may have gotten the wrong URL. I get a 404 error too. The URL I am using is udrc@nw-digital-radio.groups.io and I also prescribe to the message streams.

I think that the beta6 image is on Git-hub but I haven’t taken the time to go out and look for it yet. It has been a busy day for me. I will get to it later this afternoon.

Tom

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of Julie McGrew via Groups.Io
Sent: Wednesday, December 26, 2018 1:55 PM
To: udrc@nw-digital-radio.groups.io
Subject: [udrc] Link to DRAWS image not working?

DRAWS™ Raspbian Images

Current images are at http://images.nwdigitalradio.com

Did I go to the wrong location? This link gives a 404 error on several different browsers.

Any direction much appreciated. :)

73,
julie /ac0wn