Date   

Re: It was "fine", then... strange behavior #betaimage #setup #draws

Gayland Gump
 

I haven't the sophisticated knowledge of how the DRAWS & UDRC perform their magic but I have the following observations.  

Out of the box, the DRAWS would not work with my Yaesu 857D when running fldigi. I believe that the PTT wasn't working immediately after I did the initial configuration of fldigi but I can't be sure.  Thinking back a couple years or so when I first got my first UDRC I began to suspect the ALSA settings.  Examining the UDRC settings and comparing them to the DRAWS I tried changing a couple of the parameters on the DRAWS to correspond to those on the UDRC.  After a couple changing a single parameter at a time with no change in outcome.  

I realized that on the UDRC I had the on board audio turned on.  In order to model the working UDRC, I decided to activate the onboard audio using the "dtparam=audio=on" parameter in the /boot/config.txt file on the DRAWS.  I had no definite rationale for doing this other than to eliminate another difference in the UDRC and DRAWS configurations.  The impact of making that change in situ on the DRAWS was disastrous as on a reboot the system was entirely un-useable.  I immediately reversed that change and returned to pursuing the ALSA settings.

As my earlier approach of changing single ALSA parameters had not yielded any change in fldigi's performance, I did a wholesale change of the DRAWS alsa settings to those that were currently in place on my working UDRC.  After completing these changes, the DRAWS was able to transmit and receive.  There are still some issues though.

First, there is a significant difference in SNR reports on the UDRC vs the DRAWS.  DRAWS levels appear to be 10 or more DB lower than those being reported by fldigi on the UDRC.  As all I do to obtain these observations  is move the 6-pin DIN connector back and forth between the UDRC and DRAWS using identical ALSA settings, I'd like to know what might be causing the differences in the SNR reports between those devices.

Another difference, which I note between the DRAWS and UDRC which may well be related to the level differences is in the fldigi waterfall display.  To the best of my knowledge the applicable waterfall settings on the DRAWS and the UDRC but the displays are significantly different.   I've got my UDRC set so that the waterfall shows a constant noise level.  Lots of others seem to prefer having a noiseless screen that only display's stronger signals.  I find that by leaving the display set so that it displays noise I am able to visually identify some weak FSQ signal patterns.  

I'd also like to know what it takes to get the on board audio working on the DRAWS after all some of the software running on the DRAWS provides audio cues that it might be nice to use.  Of course assuming that those cues can be delivered to the on board audio for presentation.

I want to applaud all of NWDR's efforts at bringing us some very cool and useful tools.  I also recognize that providing documentary support for these tool is extremely challenging given the resources available.   Given the constraints, I know that it is a lot to expect that NDWR keep in mind that we users including early adopters often don't have the necessary depth of knowledge that NDWR folks have and expecting us to know about non-standard applications (e.g. chrony vs ntp) or even basic linux system operations need to be carefully considered assumptions.

Finally, I'd like to find out if NWDR has any ideas why I'd be seeing the differences in SNR that appear between the DRAWS and UDRC?  What have I overlooked or just don't know about?

Thanks again for your time and attention.

Gayland
KG7GCF


On Wed, Dec 19, 2018 at 7:07 AM Jack Spitznagel <kd4iz@...> wrote:
Basil, John, All,

Initially, Beta 5 seemed to work out of the box but I ran into some DRAWS audio and keying strangeness that is baffling me after 3 tries at installing from newly flashed microSD cards and following Basil's latest procedure on GitHub. Hope you can provide insight. Rig is a CAT controlled IC-7000.

Tested Direwolf with Xastir and YAAC with both RX and TX successfully, but noticed the audio was a bit hot - signal here looked normal on the SpecLab so I left it alone.

Then disabled AX.25/direwolf (script) and configured fldigi and wsjt-x. Both programs worked in receive but the TX audio to the IC-7000 was very "hot". Put fldigi in tune then to bring the ALC reading as close to zero as possible by reducing audio levels with the PCM drive control. As audio level is reduced - the ALC starts to "pump", as did the power out indication - unexpectedly, there was a increase of noise on audio and harmonic spikes got higher as level of signal was reduced. Returned levels to where they had been and meter indications returned to where they were before. Was able to have a PSK31 QSO and got no comment about the signal quality.

I re-enabled AX.25/Direwolf using the script. Now both Xastir and YAAC no longer would transmit audio. When the rig is keyed, the TX LED on the rig flashes 3-4 times quickly and there is no modulation of the FM carrier. Reboot did not change behavior. Going back to non-AX25 mode, now fldigi would key the radio, but  no modulation occurred.

Re-installation of the DRAWS beta 5 from the ground up (x2) did not help - none of the programs transmit audio and symptoms are the same.

To be sure rig was OK, I hooked up an old SIgnaLink to a laptop, ran HRD and it drove and keyed the rig just fine. So I have to assume that the problem is software or DRAWS hardware related.

Where should I be looking to fix the audio? The keying?
Settings should not so brittle. Thanks in advance,
--
J Spitznagel - KD4IZ
Science River LLC
KD4IZ


Re: It was "fine", then... strange behavior #betaimage #setup #draws

Basil Gunn
 

In general for debugging problems:

Send output of:
~/bin/showudrc.sh
~/n7nix/debug/alsa-show.sh

Use the following instructions for measure_deviate.sh to verify PTT &
transmit paths.
https://github.com/nwdigitalradio/n7nix/tree/master/deviation

Using another radio listen to the tone produced by the
measure_deviate.sh script.

The most common problem, if the tones do not sound right, is the output is
being over driven causing it to clip.

Receive path:
Tune a radio to the APRS 1200 baud freq. 144.390 MHz
run the following in a console:

tail -f /var/log/direwolf/direwolf.log

You should see received packets scrolling by.

Let us know what you find & thanks for testing the DRAWS hat.

/Basil

Jack Spitznagel <kd4iz@frawg.org> writes:

Basil, John, All,

Initially, Beta 5 seemed to work out of the box but I ran into some
DRAWS audio and keying strangeness that is baffling me after 3 tries
at installing from newly flashed microSD cards and following Basil's
latest procedure on GitHub. Hope you can provide insight. Rig is a CAT
controlled IC-7000.

Tested Direwolf with Xastir and YAAC with both RX and TX successfully, but noticed the audio was a bit hot - signal here looked normal on the SpecLab so I left it alone.

Then disabled AX.25/direwolf (script) and configured fldigi and wsjt-x. Both programs worked in receive but the TX audio to the IC-7000 was very "hot". Put fldigi in tune then to bring the ALC reading as close to zero as possible by reducing audio levels with the PCM drive control. As audio level is reduced - the ALC starts to "pump", as did the power out indication - unexpectedly, there was a increase of noise on audio and harmonic spikes got higher as level of signal was reduced. Returned levels to where they had been and meter indications returned to where they were before. Was able to have a PSK31 QSO and got no comment about the signal quality.

I re-enabled AX.25/Direwolf using the script. Now both Xastir and YAAC no longer would transmit audio. When the rig is keyed, the TX LED on the rig flashes 3-4 times quickly and there is no modulation of the FM carrier. Reboot did not change behavior. Going back to non-AX25 mode, now fldigi would key the radio, but no modulation occurred.

Re-installation of the DRAWS beta 5 from the ground up (x2) did not help - none of the programs transmit audio and symptoms are the same.

To be sure rig was OK, I hooked up an old SIgnaLink to a laptop, ran HRD and it drove and keyed the rig just fine. So I have to assume that the problem is software or DRAWS hardware related.

Where should I be looking to fix the audio? The keying?
Settings should not so brittle. Thanks in advance,


Re: ntpd not installed on beta 5 #ntp #chrony #ntpd

David [kg5eiu]
 

These CR1220s work well in mine:


73!!  David (KG5EIU)


On Dec 19, 2018, at 3:06 AM, f6bvp <f6bvp@...> wrote:

I did not install a battery yet  in my DRAWS hat.
None of the button batteries I have in stock fits into the case.
Could someone give me a model reference or number.

Bernard


Le 19 déc. 2018 à 07:20, Basil Gunn <basil@...> a écrit :


From some google-fu:

Note that the chrony service does not change the time. The often
misconception is that the chrony service is setting the time to the one
given by the NTP server.  This is incorrect – what actually happens is
that based on the answer from the NTP server, chrony just tells the
system clock to go faster or slower.  For this reason, sometimes even
though the time is wrong and the NTP server is working, the time does
not get corrected immediately.

If your system time is off by a lot you can try this.
To step the system clock immediately, bypassing any adjustments in
progress by slewing, issue the following command as root:

chronyc makestep

Also check out entries in:
https://github.com/nwdigitalradio/n7nix/blob/master/VERIFY_CONFIG.md
Look for "Check GPS"

Also send me the console output from this script.
https://github.com/nwdigitalradio/n7nix/blob/master/gps/verify_time.sh

/Basil

Gayland Gump <kg7gcf@...> writes:

I believe it ran for a few hours without the update, in fact I was
surprised when I finally noticed that the date and time were so off.  I did
not do anything with chrony nor the gps other than install the battery and
hooked up the antenna.

Gayland
KG7GCF


On Tue, Dec 18, 2018 at 5:56 PM Basil Gunn <basil@...> wrote:


FYI,  I installed a battery before I first powered up the DRAWS but the
time did not update even with a network connection and the gps antenna
installed.

My experience is that it can sometimes take 10 minutes for chronyd to
sync.
/Basil


I ended up setting it manually using the date command.  Haven't
been back to it to see if it has held will try to get around to that
soon.

Gayland
KG7GCF









Re: ntpd not installed on beta 5 #ntp #chrony #ntpd

Basil Gunn
 

If not already present adding
chronyc makestep
in n7nix install core script could be usefull to perform initial
system time adjustment when GPS is not yet switched. This is my case
for I did’not put any antenna for indoor use.
Yes. Exactly what I was going to do.
Just want to make sure that is sufficient to solve Gayland's problem.
/Basil



Le 19 déc. 2018 à 07:20, Basil Gunn <basil@pacabunga.com> a écrit :


From some google-fu:

Note that the chrony service does not change the time. The often
misconception is that the chrony service is setting the time to the one
given by the NTP server. This is incorrect – what actually happens is
that based on the answer from the NTP server, chrony just tells the
system clock to go faster or slower. For this reason, sometimes even
though the time is wrong and the NTP server is working, the time does
not get corrected immediately.

If your system time is off by a lot you can try this.
To step the system clock immediately, bypassing any adjustments in
progress by slewing, issue the following command as root:

chronyc makestep

Also check out entries in:
https://github.com/nwdigitalradio/n7nix/blob/master/VERIFY_CONFIG.md
Look for "Check GPS"

Also send me the console output from this script.
https://github.com/nwdigitalradio/n7nix/blob/master/gps/verify_time.sh

/Basil


It was "fine", then... strange behavior #betaimage #setup #draws

Jack Spitznagel
 

Basil, John, All,

Initially, Beta 5 seemed to work out of the box but I ran into some DRAWS audio and keying strangeness that is baffling me after 3 tries at installing from newly flashed microSD cards and following Basil's latest procedure on GitHub. Hope you can provide insight. Rig is a CAT controlled IC-7000.

Tested Direwolf with Xastir and YAAC with both RX and TX successfully, but noticed the audio was a bit hot - signal here looked normal on the SpecLab so I left it alone.

Then disabled AX.25/direwolf (script) and configured fldigi and wsjt-x. Both programs worked in receive but the TX audio to the IC-7000 was very "hot". Put fldigi in tune then to bring the ALC reading as close to zero as possible by reducing audio levels with the PCM drive control. As audio level is reduced - the ALC starts to "pump", as did the power out indication - unexpectedly, there was a increase of noise on audio and harmonic spikes got higher as level of signal was reduced. Returned levels to where they had been and meter indications returned to where they were before. Was able to have a PSK31 QSO and got no comment about the signal quality.

I re-enabled AX.25/Direwolf using the script. Now both Xastir and YAAC no longer would transmit audio. When the rig is keyed, the TX LED on the rig flashes 3-4 times quickly and there is no modulation of the FM carrier. Reboot did not change behavior. Going back to non-AX25 mode, now fldigi would key the radio, but  no modulation occurred.

Re-installation of the DRAWS beta 5 from the ground up (x2) did not help - none of the programs transmit audio and symptoms are the same.

To be sure rig was OK, I hooked up an old SIgnaLink to a laptop, ran HRD and it drove and keyed the rig just fine. So I have to assume that the problem is software or DRAWS hardware related.

Where should I be looking to fix the audio? The keying?
Settings should not so brittle. Thanks in advance,
--
J Spitznagel - KD4IZ
Science River LLC
KD4IZ


Re: ntpd not installed on beta 5 #ntp #chrony #ntpd

 

Battery is CR1220 NON RECHARGEABLE


Re: ntpd not installed on beta 5 #ntp #chrony #ntpd

Bernard f6bvp / ai7bg
 

If not already present adding 
chronyc makestep
in n7nix  install core script could be usefull to perform initial system time adjustment when GPS is not yet switched. This is my case for I did’not put any antenna for indoor use.

Bernard


Le 19 déc. 2018 à 07:20, Basil Gunn <basil@...> a écrit :


From some google-fu:

Note that the chrony service does not change the time. The often
misconception is that the chrony service is setting the time to the one
given by the NTP server.  This is incorrect – what actually happens is
that based on the answer from the NTP server, chrony just tells the
system clock to go faster or slower.  For this reason, sometimes even
though the time is wrong and the NTP server is working, the time does
not get corrected immediately.

If your system time is off by a lot you can try this.
To step the system clock immediately, bypassing any adjustments in
progress by slewing, issue the following command as root:

chronyc makestep

Also check out entries in:
https://github.com/nwdigitalradio/n7nix/blob/master/VERIFY_CONFIG.md
Look for "Check GPS"

Also send me the console output from this script.
https://github.com/nwdigitalradio/n7nix/blob/master/gps/verify_time.sh

/Basil


Re: ntpd not installed on beta 5 #ntp #chrony #ntpd

Bernard f6bvp / ai7bg
 

I did not install a battery yet in my DRAWS hat.
None of the button batteries I have in stock fits into the case.
Could someone give me a model reference or number.

Bernard

Le 19 déc. 2018 à 07:20, Basil Gunn <basil@pacabunga.com> a écrit :


From some google-fu:

Note that the chrony service does not change the time. The often
misconception is that the chrony service is setting the time to the one
given by the NTP server. This is incorrect – what actually happens is
that based on the answer from the NTP server, chrony just tells the
system clock to go faster or slower. For this reason, sometimes even
though the time is wrong and the NTP server is working, the time does
not get corrected immediately.

If your system time is off by a lot you can try this.
To step the system clock immediately, bypassing any adjustments in
progress by slewing, issue the following command as root:

chronyc makestep

Also check out entries in:
https://github.com/nwdigitalradio/n7nix/blob/master/VERIFY_CONFIG.md
Look for "Check GPS"

Also send me the console output from this script.
https://github.com/nwdigitalradio/n7nix/blob/master/gps/verify_time.sh

/Basil

Gayland Gump <kg7gcf@gmail.com> writes:

I believe it ran for a few hours without the update, in fact I was
surprised when I finally noticed that the date and time were so off. I did
not do anything with chrony nor the gps other than install the battery and
hooked up the antenna.

Gayland
KG7GCF


On Tue, Dec 18, 2018 at 5:56 PM Basil Gunn <basil@pacabunga.com> wrote:


FYI, I installed a battery before I first powered up the DRAWS but the
time did not update even with a network connection and the gps antenna
installed.
My experience is that it can sometimes take 10 minutes for chronyd to
sync.
/Basil


I ended up setting it manually using the date command. Haven't
been back to it to see if it has held will try to get around to that
soon.

Gayland
KG7GCF


Re: ntpd not installed on beta 5 #ntp #chrony #ntpd

Basil Gunn
 

From some google-fu:

Note that the chrony service does not change the time. The often
misconception is that the chrony service is setting the time to the one
given by the NTP server. This is incorrect – what actually happens is
that based on the answer from the NTP server, chrony just tells the
system clock to go faster or slower. For this reason, sometimes even
though the time is wrong and the NTP server is working, the time does
not get corrected immediately.

If your system time is off by a lot you can try this.
To step the system clock immediately, bypassing any adjustments in
progress by slewing, issue the following command as root:

chronyc makestep

Also check out entries in:
https://github.com/nwdigitalradio/n7nix/blob/master/VERIFY_CONFIG.md
Look for "Check GPS"

Also send me the console output from this script.
https://github.com/nwdigitalradio/n7nix/blob/master/gps/verify_time.sh

/Basil

Gayland Gump <kg7gcf@gmail.com> writes:

I believe it ran for a few hours without the update, in fact I was
surprised when I finally noticed that the date and time were so off. I did
not do anything with chrony nor the gps other than install the battery and
hooked up the antenna.

Gayland
KG7GCF


On Tue, Dec 18, 2018 at 5:56 PM Basil Gunn <basil@pacabunga.com> wrote:


FYI, I installed a battery before I first powered up the DRAWS but the
time did not update even with a network connection and the gps antenna
installed.
My experience is that it can sometimes take 10 minutes for chronyd to
sync.
/Basil


I ended up setting it manually using the date command. Haven't
been back to it to see if it has held will try to get around to that
soon.

Gayland
KG7GCF


Re: Suggested pre-installed apps for the 'final' image and bugs

Basil Gunn
 

I just loaded beta5 and going through it, I'll make a list here of
suggested apps for the final image (or at least that people should
consider installing)

- geany: great little text editor, multiple language support
Not to sound too dogmatic but text editors are personal and I've had
this discussion a few too many times already. Put whatever editor you
want on your installation but it most likely will not be in the
nw digital radio RPi image.

current bugs I've found:
- wget https://sourceforge.net produces 'certificate not trusted'
Not sure what you are talking about. There are no wget of any files in
the configuration script of the image. The whole point of making the
image is so you don't have to do that.

I'm going to manually go through the rest of my script later but so
far that looks like the biggest deal that I can see.
/Basil


Suggested pre-installed apps for the 'final' image and bugs

Art - KC7SDA
 

I just loaded beta5 and going through it, I'll make a list here of suggested apps for the final image (or at least that people should consider installing)

- geany: great little text editor, multiple language support 

current bugs I've found:
- wget https://sourceforge.net produces 'certificate not trusted'

I'm going to manually go through the rest of my script later but so far that looks like the biggest deal that I can see.


Re: ntpd not installed on beta 5 #ntp #chrony #ntpd

Gayland Gump
 

I believe it ran for a few hours without the update, in fact I was surprised when I finally noticed that the date and time were so off.  I did not do anything with chrony nor the gps other than install the battery and hooked up the antenna.  

Gayland
KG7GCF


On Tue, Dec 18, 2018 at 5:56 PM Basil Gunn <basil@...> wrote:

> FYI,  I installed a battery before I first powered up the DRAWS but the
> time did not update even with a network connection and the gps antenna
> installed.

My experience is that it can sometimes take 10 minutes for chronyd to
sync.
/Basil


> I ended up setting it manually using the date command.  Haven't
> been back to it to see if it has held will try to get around to that soon.
>
> Gayland
> KG7GCF




Re: ntpd not installed on beta 5 #ntp #chrony #ntpd

Basil Gunn
 

FYI, I installed a battery before I first powered up the DRAWS but the
time did not update even with a network connection and the gps antenna
installed.
My experience is that it can sometimes take 10 minutes for chronyd to
sync.
/Basil


I ended up setting it manually using the date command. Haven't
been back to it to see if it has held will try to get around to that soon.

Gayland
KG7GCF


Re: ntpd not installed on beta 5 #ntp #chrony #ntpd

 

The RTC is part of the GPS and is set by the GPS, make sure your GPS is receiving to get the RTC set, you can use gpsmon or cgps to check the gps.  Then gpsd and chrony need to be running for the system clock updates.

On Tue, Dec 18, 2018 at 4:51 PM Gayland Gump <kg7gcf@...> wrote:
FYI,  I installed a battery before I first powered up the DRAWS but the time did not update even with a network connection and the gps antenna installed.  I ended up setting it manually using the date command.  Haven't been back to it to see if it has held will try to get around to that soon.

Gayland
KG7GCF


On Tue, Dec 18, 2018 at 4:35 PM Basil Gunn <basil@...> wrote:

Bernard,

I have been playing around with chrony for a few hours now and I've
convinced myself that chronyd should work fine with or without a gps
antenna connected.

If you look at the output of this command without a GPS antenna:

sudo timedatectl

it should have "Network time on: yes"

I have experienced chrony sometimes taking several minutes to get the
local time correct. I think installing the battery on the DRAWS board
could help that behavior. Let me know if you see other time related
problems.

/Basil



f6bvp <f6bvp@...> writes:

> Ok. I reinstalled chrony for it had been removed when installing ntp.
> This time command
> systemctl status chrony
> showed that it was started as ntp client/server and
> chrony sources command found 6 sources while gps is not activated.
>
> Thanks,
>
> 73 de Bernard f6bvp
>
>
>> Le 18 déc. 2018 à 17:20, John D Hays - K7VE <john@...> a écrit :
>>
>> Chrony works without GPS as a client on the Internet.
>>
>>> On Tue, Dec 18, 2018, 08:13 Basil Gunn <basil@... wrote:
>>>
>>> > I noticed that on my compass beta-5 system the time was not set
>>> > correctly despite I did perform initial country, keyboard
>>> > etc...configuration.  Thus I apt-get installed ntp and after one or
>>> > two minutes the console clock did display local time correctly.
>>>
>>> That's true & I need to fix that.
>>>
>>> Currently time defaults to using chrony & the gps.  Chrony is another
>>> implementation the Network Time Protocol. You should notice that when
>>> you install ntp, chrony is removed.
>>> I need to look into using chrony without a gps.
>>>
>>> /Basil
>>>
>>>
>>>
>>
>>
>
>





--


John D. Hays
Edmonds, WA
K7VE

   


Re: ntpd not installed on beta 5 #ntp #chrony #ntpd

Gayland Gump
 

FYI,  I installed a battery before I first powered up the DRAWS but the time did not update even with a network connection and the gps antenna installed.  I ended up setting it manually using the date command.  Haven't been back to it to see if it has held will try to get around to that soon.

Gayland
KG7GCF


On Tue, Dec 18, 2018 at 4:35 PM Basil Gunn <basil@...> wrote:

Bernard,

I have been playing around with chrony for a few hours now and I've
convinced myself that chronyd should work fine with or without a gps
antenna connected.

If you look at the output of this command without a GPS antenna:

sudo timedatectl

it should have "Network time on: yes"

I have experienced chrony sometimes taking several minutes to get the
local time correct. I think installing the battery on the DRAWS board
could help that behavior. Let me know if you see other time related
problems.

/Basil



f6bvp <f6bvp@...> writes:

> Ok. I reinstalled chrony for it had been removed when installing ntp.
> This time command
> systemctl status chrony
> showed that it was started as ntp client/server and
> chrony sources command found 6 sources while gps is not activated.
>
> Thanks,
>
> 73 de Bernard f6bvp
>
>
>> Le 18 déc. 2018 à 17:20, John D Hays - K7VE <john@...> a écrit :
>>
>> Chrony works without GPS as a client on the Internet.
>>
>>> On Tue, Dec 18, 2018, 08:13 Basil Gunn <basil@... wrote:
>>>
>>> > I noticed that on my compass beta-5 system the time was not set
>>> > correctly despite I did perform initial country, keyboard
>>> > etc...configuration.  Thus I apt-get installed ntp and after one or
>>> > two minutes the console clock did display local time correctly.
>>>
>>> That's true & I need to fix that.
>>>
>>> Currently time defaults to using chrony & the gps.  Chrony is another
>>> implementation the Network Time Protocol. You should notice that when
>>> you install ntp, chrony is removed.
>>> I need to look into using chrony without a gps.
>>>
>>> /Basil
>>>
>>>
>>>
>>
>>
>
>




Re: ntpd not installed on beta 5 #ntp #chrony #ntpd

 

I will add that if you go into /etc/chrony/chrony.conf and modify the line for PPS and add prefer to the end, that should give you the most accurate time when the GPS is running.

refclock SHM 2 refid PPS precision 1e-9 poll 3 trust prefer


On Tue, Dec 18, 2018 at 4:35 PM Basil Gunn <basil@...> wrote:

Bernard,

I have been playing around with chrony for a few hours now and I've
convinced myself that chronyd should work fine with or without a gps
antenna connected.

If you look at the output of this command without a GPS antenna:

sudo timedatectl

it should have "Network time on: yes"

I have experienced chrony sometimes taking several minutes to get the
local time correct. I think installing the battery on the DRAWS board
could help that behavior. Let me know if you see other time related
problems.

/Basil



f6bvp <f6bvp@...> writes:

> Ok. I reinstalled chrony for it had been removed when installing ntp.
> This time command
> systemctl status chrony
> showed that it was started as ntp client/server and
> chrony sources command found 6 sources while gps is not activated.
>
> Thanks,
>
> 73 de Bernard f6bvp
>
>
>> Le 18 déc. 2018 à 17:20, John D Hays - K7VE <john@...> a écrit :
>>
>> Chrony works without GPS as a client on the Internet.
>>
>>> On Tue, Dec 18, 2018, 08:13 Basil Gunn <basil@... wrote:
>>>
>>> > I noticed that on my compass beta-5 system the time was not set
>>> > correctly despite I did perform initial country, keyboard
>>> > etc...configuration.  Thus I apt-get installed ntp and after one or
>>> > two minutes the console clock did display local time correctly.
>>>
>>> That's true & I need to fix that.
>>>
>>> Currently time defaults to using chrony & the gps.  Chrony is another
>>> implementation the Network Time Protocol. You should notice that when
>>> you install ntp, chrony is removed.
>>> I need to look into using chrony without a gps.
>>>
>>> /Basil
>>>
>>>
>>>
>>
>>
>
>





--


John D. Hays
Edmonds, WA
K7VE

   


Re: ntpd not installed on beta 5 #ntp #chrony #ntpd

Basil Gunn
 

Bernard,

I have been playing around with chrony for a few hours now and I've
convinced myself that chronyd should work fine with or without a gps
antenna connected.

If you look at the output of this command without a GPS antenna:

sudo timedatectl

it should have "Network time on: yes"

I have experienced chrony sometimes taking several minutes to get the
local time correct. I think installing the battery on the DRAWS board
could help that behavior. Let me know if you see other time related
problems.

/Basil



f6bvp <f6bvp@free.fr> writes:

Ok. I reinstalled chrony for it had been removed when installing ntp.
This time command
systemctl status chrony
showed that it was started as ntp client/server and
chrony sources command found 6 sources while gps is not activated.

Thanks,

73 de Bernard f6bvp


Le 18 déc. 2018 à 17:20, John D Hays - K7VE <john@hays.org> a écrit :

Chrony works without GPS as a client on the Internet.

On Tue, Dec 18, 2018, 08:13 Basil Gunn <basil@pacabunga.com wrote:

I noticed that on my compass beta-5 system the time was not set
correctly despite I did perform initial country, keyboard
etc...configuration. Thus I apt-get installed ntp and after one or
two minutes the console clock did display local time correctly.
That's true & I need to fix that.

Currently time defaults to using chrony & the gps. Chrony is another
implementation the Network Time Protocol. You should notice that when
you install ntp, chrony is removed.
I need to look into using chrony without a gps.

/Basil



Re: kissattach ports address

Basil Gunn
 

Yes good idea.
/Basil

Bernard Pidoux <bernard.f6bvp@gmail.com> writes:

Hi,
I would prefere to have IP address
of AX25 ports being set as parameters rather that fixed IP values inside the script ax25-upd.
Something like :
PORT_1_ADDRESS=« 44.168.xx.xx »
PORT_2_ADDRESS=« 44.168.xx.yy »

and in the call to kissattach
${pseudo term}
${PORTNAME_1} $PORT_1_ADDRESS > /tmp/ax25-config.tmp


73 de Bernard f6bvp


Le 18 déc. 2018 à 17:00, John D Hays - K7VE <john@hays.org> a écrit :

Look at the Wiki. Chrony is installed in lieu of ntpd.

On Tue, Dec 18, 2018, 07:52 Bernard Pidoux <bernard.f6bvp@gmail.com wrote:
Hi,
I noticed that on my compass beta-5 system the time was not set correctly despite I did perform initial country, keyboard etc...configuration.
Thus I apt-get installed ntp
and after one or two minutes the console clock did display local time correctly.
Consequently I suggest to pre install ntpd on next compass draws releases.

Bernard, f6bvp




kissattach ports address

Bernard Pidoux
 

Hi,
I would prefere to have IP address 
of AX25 ports being set as parameters rather that fixed IP values inside the script ax25-upd.
Something like :
PORT_1_ADDRESS=« 44.168.xx.xx »
PORT_2_ADDRESS=« 44.168.xx.yy »

and in the call to kissattach 
${pseudo term}
${PORTNAME_1} $PORT_1_ADDRESS > /tmp/ax25-config.tmp


73 de Bernard f6bvp


Le 18 déc. 2018 à 17:00, John D Hays - K7VE <john@...> a écrit :

Look at the Wiki. Chrony is installed in lieu of ntpd. 

On Tue, Dec 18, 2018, 07:52 Bernard Pidoux <bernard.f6bvp@... wrote:
Hi,
I noticed that on my compass beta-5 system the time was not set correctly despite I did perform initial country, keyboard etc...configuration.
Thus  I apt-get installed ntp
and after one or two minutes the console clock did display  local time correctly.
Consequently I suggest to pre install ntpd on next compass draws releases.

Bernard, f6bvp





Re: ARDOP on the DRAWS

Basil Gunn
 

So I take it that there is not a script
or GUI UI that sets all the packages up from a checkbox list and some
data entry like my name, call sign and grid.
Not yet. That is our vision for config as well.

I am working to get a 20m Gateway up once the unit I order
this morning arrives
Nice!

1 Feb 2019 9or there abouts).Ed Bloom
ewbloom@verizon.netSent from Webmail access
-----Original Message-----
From: Basil Gunn <basil@pacabunga.com>
To: udrc <udrc@nw-digital-radio.groups.io>
Sent: Tue, Dec 18, 2018 10:43 am
Subject: Re: [udrc] ARDOP on the DRAWS



NEVER MIND!!! I overlooked ARDOP in the list.....But does not answer
the second question.....Does the Compass load have ARDOP loadedand
ready to use?Ed Bloom
Both arim 2.4 & latest version of ardop are installed on the image.
Not sure what you mean by "ready to use". You have to configure any of
the applications that are on the image.

I have successfully run arim with ardop on the RPi. Also I am working
on having paclink-unix use ardop as a transport.

/Basil

3421 - 3440 of 5716