Date   

Re: Stacking multiple TNC-Pi9k6's #tnc

N5XMT
 

Unfortunately on the 9K6 you can't.  Hardcoded in the code


On Fri, Oct 16, 2020 at 10:23 AM <mskurnik@...> wrote:
Can I use pitnc_setparams to set the I2C address instead on one connected, then connect the other one and use both.  If not I can just run the arduino sketch like you said.


Re: Stacking multiple TNC-Pi9k6's #tnc

KN6FOA
 

Can I use pitnc_setparams to set the I2C address instead on one connected, then connect the other one and use both.  If not I can just run the arduino sketch like you said.


Re: Stacking multiple TNC-Pi9k6's #tnc

N5XMT
 

If you want to run 2 TNC-PI9K6's you can't run both i2C unless you modify the code and reflash one of them for a different i2C address.  Then you can run one serial, the other i2C

On Oct 16, 2020, at 01:28, mskurnik@... wrote:
I've seen a few topics on here about using multiple TNC-Pi9k6's with a raspberry pi but when I connect 2 TNCs I only see 1 TNC when looking at i2cdetect.  How do I get both TNCs to show up in i2c or as discrete serial ports?

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- 1e --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

1e is the TNC and 48 is a UPS

pitnc_getparams Version 0.0.0.5
KISS Data Frame
 
   TNC Software Version          30
01 TXDelay - Zero means use ADC 160
02 Persistance                   30
03 Slottime (in 10 mS)            0
04 TXTail                         0
05 Full Duplex - Not used       255
06 Our Channel (Hex)             ff
07 I2C Address (0 = async) Hex   0c
08 Mode Speed                     0
09 RX Level (Config)              4
10 TX Level                       0
11 RX Level (Actual)            170
13 Centre Freq                  810
6 1e a0 1e 0 0 ff ff c 0 4 0 aa 51 c0 sum 55
** Checksum Error - Sum = 55 Should be Zero


Re: Stacking multiple TNC-Pi9k6's #tnc

Jim WB9QPM
 

Run the Arduino program. Open the SM_Teensy sketch.

Edit the I2C address in the source. Rebuild the sketch. Upload the TNC.

Stacked TNC require a unique I2C address for each.

73,
Jim WB9QPM


Stacking multiple TNC-Pi9k6's #tnc

KN6FOA
 

I've seen a few topics on here about using multiple TNC-Pi9k6's with a raspberry pi but when I connect 2 TNCs I only see 1 TNC when looking at i2cdetect.  How do I get both TNCs to show up in i2c or as discrete serial ports?

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- 1e --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

1e is the TNC and 48 is a UPS

pitnc_getparams Version 0.0.0.5
KISS Data Frame
 
   TNC Software Version          30
01 TXDelay - Zero means use ADC 160
02 Persistance                   30
03 Slottime (in 10 mS)            0
04 TXTail                         0
05 Full Duplex - Not used       255
06 Our Channel (Hex)             ff
07 I2C Address (0 = async) Hex   0c
08 Mode Speed                     0
09 RX Level (Config)              4
10 TX Level                       0
11 RX Level (Actual)            170
13 Centre Freq                  810
6 1e a0 1e 0 0 ff ff c 0 4 0 aa 51 c0 sum 55
** Checksum Error - Sum = 55 Should be Zero


WinRPR

Jerome Kutche
 


Re: Getting a Uputronics GPS Hat to work with Chrony?

 

This is using an Adafruit Ultimate GPS Hat (similar for the DRAWS™)

Added to /boot/config.txt (again specific to the Adafruit Ultimate GPS Hat):
dtoverlay=pps-gpio,gpiopin=4


cat /etc/chrony/chrony.conf
# Welcome to the chrony configuration file. See chrony.conf(5) for more
# information about usuable directives.
refclock SHM 0 refid GPS precision 1e-3 offset 0.5 delay 0.2 poll 3 trust require
refclock SHM 2 refid PPS precision 1e-9 poll 3 trust
pool 2.debian.pool.ntp.org iburst

# This directive specify the location of the file containing ID/key pairs for
# NTP authentication.
keyfile /etc/chrony/chrony.keys

# This directive specify the file into which chronyd will store the rate
# information.
driftfile /var/lib/chrony/chrony.drift

# Uncomment the following line to turn logging on.
#log tracking measurements statistics

# Log files location.
logdir /var/log/chrony

# Stop bad estimates upsetting machine clock.
maxupdateskew 100.0

# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock. Note that it can’t be used along with the 'rtcfile' directive.
rtcsync

# Step the system clock instead of slewing it if the adjustment is larger than
# one second, but only in the first three clock updates.
makestep 1 3

Add broadcast and allow stanzas as needed.

On Mon, Oct 12, 2020 at 1:54 PM Greg Engle <gfe@...> wrote:

Ok, how did you get there?

 

Mine is showing a ? in the source state.

 


--
John D. Hays
Kingston, WA
K7VE

 


Re: Getting a Uputronics GPS Hat to work with Chrony?

Greg Engle
 

Ok, how did you get there?

 

Mine is showing a ? in the source state.

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of John D Hays - K7VE
Sent: Monday, October 12, 2020 12:11 PM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Getting a Uputronics GPS Hat to work with Chrony?

 

Some just like a bit more precision -- here is a Raspberry Pi + Adafruit HAT

chronyc sources -v
210 Number of sources = 6

  .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
 / .- Source state '*' = current synced, '+' = combined , '-' = not combined,
| /   '?' = unreachable, 'x' = time may be in error, '~' = time too variable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
#- GPS                           0   3   377    10    +28ms[  +28ms] +/-  111ms
#* PPS                           0   3   377    10   -193ns[  -65ns] +/-  205ns
^- 2001:49f0:d04c:1::2           2   9   377   490  -5846us[-5851us] +/-   41ms
^- 2001:470:e439:1::10           2  10   377   603   +706us[ +699us] +/-   54ms
^- x.ns.gin.ntt.net              2  10   377   605  -5024us[-5032us] +/-   38ms
^- srcf-ntp.stanford.edu         2  10   377   928    -11ms[  -11ms] +/-   56ms

 

On Mon, Oct 12, 2020 at 11:50 AM David Ranch <rpi4hamradio-groupsio@...> wrote:


Hello John,

From the table included in https://gpsd.gitlab.io/gpsd/gpsd-time-service-howto.html#_1pps_quality_issues , the bottom summary says that accuracy delta would only be say 100mS of a time delta.  I don't see how that could be a problem for 99.9% of most HAM use cases.  Maybe I'm missing something here?

--David
KI6ZHD



On 10/12/2020 09:47 AM, John D Hays - K7VE wrote:

The most accurate time, using Pulse Per Second or PPS, will use a GPS with PPS.  This is not something you achieve with a USB GPS.

The NW Digital Radio DRAWS™ HAT or Adafruit Ultimate GPS HAT are two examples of GPIO attached GPS with PPS.

 

On Mon, Oct 12, 2020 at 9:40 AM MIKE RICHARDS <mike@...> wrote:

Hi Greg,

I've written a tutorial that might help. Lots of people have used it successfully.

Chrony with Uputronics GOPS

Regards,

Mike - G4WNC


 

--

John D. Hays
Kingston, WA

K7VE

 

 

 

 


 

--

John D. Hays
Kingston, WA

K7VE

 

 

 


Re: Getting a Uputronics GPS Hat to work with Chrony?

Jason A. Powell <jason.powell.us@...>
 

There's a mailing list for everyone:


I'll admit to being a bit obsessed with precise time myself. I recently built a Stratum-1 NTP server using the Adafruit Ultimate GPS hat: https://www.adafruit.com/product/2324.

Why? Because I could! :)

Jason
KD8FMR

On Mon, Oct 12, 2020 at 3:14 PM John D Hays - K7VE <john@...> wrote:
Some just like a bit more precision -- here is a Raspberry Pi + Adafruit HAT

chronyc sources -v
210 Number of sources = 6

  .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
 / .- Source state '*' = current synced, '+' = combined , '-' = not combined,
| /   '?' = unreachable, 'x' = time may be in error, '~' = time too variable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
#- GPS                           0   3   377    10    +28ms[  +28ms] +/-  111ms
#* PPS                           0   3   377    10   -193ns[  -65ns] +/-  205ns
^- 2001:49f0:d04c:1::2           2   9   377   490  -5846us[-5851us] +/-   41ms
^- 2001:470:e439:1::10           2  10   377   603   +706us[ +699us] +/-   54ms
^- x.ns.gin.ntt.net              2  10   377   605  -5024us[-5032us] +/-   38ms
^- srcf-ntp.stanford.edu         2  10   377   928    -11ms[  -11ms] +/-   56ms


On Mon, Oct 12, 2020 at 11:50 AM David Ranch <rpi4hamradio-groupsio@...> wrote:

Hello John,

From the table included in https://gpsd.gitlab.io/gpsd/gpsd-time-service-howto.html#_1pps_quality_issues , the bottom summary says that accuracy delta would only be say 100mS of a time delta.  I don't see how that could be a problem for 99.9% of most HAM use cases.  Maybe I'm missing something here?

--David
KI6ZHD




On 10/12/2020 09:47 AM, John D Hays - K7VE wrote:
The most accurate time, using Pulse Per Second or PPS, will use a GPS with PPS.  This is not something you achieve with a USB GPS.

The NW Digital Radio DRAWS™ HAT or Adafruit Ultimate GPS HAT are two examples of GPIO attached GPS with PPS.

On Mon, Oct 12, 2020 at 9:40 AM MIKE RICHARDS <mike@...> wrote:
Hi Greg,

I've written a tutorial that might help. Lots of people have used it successfully.

Chrony with Uputronics GOPS

Regards,

Mike - G4WNC


--
John D. Hays
Kingston, WA
K7VE

 




--
John D. Hays
Kingston, WA
K7VE

 


Re: Getting a Uputronics GPS Hat to work with Chrony?

 

Some just like a bit more precision -- here is a Raspberry Pi + Adafruit HAT

chronyc sources -v
210 Number of sources = 6

  .-- Source mode  '^' = server, '=' = peer, '#' = local clock.
 / .- Source state '*' = current synced, '+' = combined , '-' = not combined,
| /   '?' = unreachable, 'x' = time may be in error, '~' = time too variable.
||                                                 .- xxxx [ yyyy ] +/- zzzz
||      Reachability register (octal) -.           |  xxxx = adjusted offset,
||      Log2(Polling interval) --.      |          |  yyyy = measured offset,
||                                \     |          |  zzzz = estimated error.
||                                 |    |           \
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
#- GPS                           0   3   377    10    +28ms[  +28ms] +/-  111ms
#* PPS                           0   3   377    10   -193ns[  -65ns] +/-  205ns
^- 2001:49f0:d04c:1::2           2   9   377   490  -5846us[-5851us] +/-   41ms
^- 2001:470:e439:1::10           2  10   377   603   +706us[ +699us] +/-   54ms
^- x.ns.gin.ntt.net              2  10   377   605  -5024us[-5032us] +/-   38ms
^- srcf-ntp.stanford.edu         2  10   377   928    -11ms[  -11ms] +/-   56ms


On Mon, Oct 12, 2020 at 11:50 AM David Ranch <rpi4hamradio-groupsio@...> wrote:

Hello John,

From the table included in https://gpsd.gitlab.io/gpsd/gpsd-time-service-howto.html#_1pps_quality_issues , the bottom summary says that accuracy delta would only be say 100mS of a time delta.  I don't see how that could be a problem for 99.9% of most HAM use cases.  Maybe I'm missing something here?

--David
KI6ZHD




On 10/12/2020 09:47 AM, John D Hays - K7VE wrote:
The most accurate time, using Pulse Per Second or PPS, will use a GPS with PPS.  This is not something you achieve with a USB GPS.

The NW Digital Radio DRAWS™ HAT or Adafruit Ultimate GPS HAT are two examples of GPIO attached GPS with PPS.

On Mon, Oct 12, 2020 at 9:40 AM MIKE RICHARDS <mike@...> wrote:
Hi Greg,

I've written a tutorial that might help. Lots of people have used it successfully.

Chrony with Uputronics GOPS

Regards,

Mike - G4WNC


--
John D. Hays
Kingston, WA
K7VE

 




--
John D. Hays
Kingston, WA
K7VE

 


Re: Getting a Uputronics GPS Hat to work with Chrony?

David Ranch
 


Hello John,

From the table included in https://gpsd.gitlab.io/gpsd/gpsd-time-service-howto.html#_1pps_quality_issues , the bottom summary says that accuracy delta would only be say 100mS of a time delta.  I don't see how that could be a problem for 99.9% of most HAM use cases.  Maybe I'm missing something here?

--David
KI6ZHD




On 10/12/2020 09:47 AM, John D Hays - K7VE wrote:
The most accurate time, using Pulse Per Second or PPS, will use a GPS with PPS.  This is not something you achieve with a USB GPS.

The NW Digital Radio DRAWS™ HAT or Adafruit Ultimate GPS HAT are two examples of GPIO attached GPS with PPS.

On Mon, Oct 12, 2020 at 9:40 AM MIKE RICHARDS <mike@...> wrote:
Hi Greg,

I've written a tutorial that might help. Lots of people have used it successfully.

Chrony with Uputronics GOPS

Regards,

Mike - G4WNC


--
John D. Hays
Kingston, WA
K7VE

 



Re: Getting a Uputronics GPS Hat to work with Chrony?

Greg Engle
 

I should have added:

 

Without a network connection chronyc sources -v

Has the PPS0 and NEMA listed but with a ? and not recognized

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of MIKE RICHARDS
Sent: Monday, October 12, 2020 9:38 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Getting a Uputronics GPS Hat to work with Chrony?

 

[Edited Message Follows]

Hi Greg,

I've written a tutorial that might help. Lots of people have used it successfully.

Chrony with Uputronics GPS

Regards,

Mike - G4WNC


Re: Getting a Uputronics GPS Hat to work with Chrony?

Greg Engle
 

Mark,

 

I used your page for a puck GPS and it worked well once I figured out I had to use

/dev/serial/serial-by-id to identify it.

 

All the tools used to make sure it works, work but it’s not updating the time.

 

Greg NZ6E

 

From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> On Behalf Of MIKE RICHARDS
Sent: Monday, October 12, 2020 9:38 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: [RaspberryPi-4-HamRadio] Getting a Uputronics GPS Hat to work with Chrony?

 

[Edited Message Follows]

Hi Greg,

I've written a tutorial that might help. Lots of people have used it successfully.

Chrony with Uputronics GPS

Regards,

Mike - G4WNC


Re: Getting a Uputronics GPS Hat to work with Chrony?

 

The most accurate time, using Pulse Per Second or PPS, will use a GPS with PPS.  This is not something you achieve with a USB GPS.

The NW Digital Radio DRAWS™ HAT or Adafruit Ultimate GPS HAT are two examples of GPIO attached GPS with PPS.

On Mon, Oct 12, 2020 at 9:40 AM MIKE RICHARDS <mike@...> wrote:
Hi Greg,

I've written a tutorial that might help. Lots of people have used it successfully.

Chrony with Uputronics GOPS

Regards,

Mike - G4WNC



--
John D. Hays
Kingston, WA
K7VE

 


Re: Getting a Uputronics GPS Hat to work with Chrony?

MIKE RICHARDS
 
Edited

Hi Greg,

I've written a tutorial that might help. Lots of people have used it successfully.

Chrony with Uputronics GPS

Regards,

Mike - G4WNC


Getting a Uputronics GPS Hat to work with Chrony?

Greg Engle
 

Anybody successful in getting this working to update the Pi clock?
Lots of information to set this up as a time server but I'm looking for a stand alone GPS for location and time for remote operation on WSJT-X.

It will show up with xgps, gpsmon and cgps -s
But I can't get it to update the clock in the PI

Ideas

Greg
NZ6E


Re: Unstable TNC-X with Raspberry Pi Kernel Error #pi #tnc

Kun
 

Yes. The latest Raspbian


Re: AEA Packratt TNC use with a Raspberry pi.

Jason A. Powell <jason.powell.us@...>
 

For those that want to do multiple TNCs off the same Raspberry Pi, this might be the way to go (varieties available from two to seven serial ports):


Jason
KD8FMR

On Sat, Oct 10, 2020 at 12:17 PM Jason A. Powell <jason.powell.us@...> wrote:
Try something like this—you'll just need so supply some inexpensive jumper wires.


On Sat, Oct 10, 2020 at 12:06 PM Mike Burch <mburch372@...> wrote:
Hello everyone, 

I would like to use my AEA Packratt 232 with a Raspberry pi as the pc portion for packet radio.   Reason: Just to use it and see it work again.  Do you think this could work with just a serial port hat on the Pi?    Would the available software support this project?  The tnc is in perfect condition and even has the timewave dsp daughter boards.   Than you in advance.   Mike K8MB. 


Re: AEA Packratt TNC use with a Raspberry pi.

Jason A. Powell <jason.powell.us@...>
 

Try something like this—you'll just need so supply some inexpensive jumper wires.


On Sat, Oct 10, 2020 at 12:06 PM Mike Burch <mburch372@...> wrote:
Hello everyone, 

I would like to use my AEA Packratt 232 with a Raspberry pi as the pc portion for packet radio.   Reason: Just to use it and see it work again.  Do you think this could work with just a serial port hat on the Pi?    Would the available software support this project?  The tnc is in perfect condition and even has the timewave dsp daughter boards.   Than you in advance.   Mike K8MB. 


Re: AEA Packratt TNC use with a Raspberry pi.

David Ranch
 


Hello Mike,

Yes, your PK232 will absolutely work with your Raspberry Pi.  You have a few approaches to consider:

  Hardware interfacing:
     - Easier: Buy a USB to serial adapter to connect to the PK232
     - Harder: wire the PK232 to a +3.3v to +5.0v level shifter to the Raspberry Pi's built in serial port, some minor Raspberry Pi OS configuration changes are required


  Software interfacing - your TNC can operate either in COMMAND mode or KISS mode
     - COMMAND mode with your TNC only requires a serial terminal program to communicate to the PK232.  Some program ideas are listed here (scroll down to the "Serial Terminal Programs" section:
         http://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#50.serialtroubler 

     - KISS mode is where you offload the TNC's AX25 stack into Linux's stack.  This is the most powerful approach but also the more complex to setup option (this is still what I personally recommend).  There is lots of documentation out there and I can give help here as well.

--David
KI6ZHD


On 10/10/2020 09:22 AM, Mark Griffith via groups.io wrote:
It works fine, but you'll need a terminal program for the Raspberry Pi.  There are not many available and all are very rudimentary.  Minicom is one that you can add using apt-get as well as putty which is probably better.

I used a USB to serial dongle which worked pretty well but a HAT will work.  The dongle is much easier to install, just plug it in.

Mark
KD0QYN


On Saturday, October 10, 2020, 11:03:08 AM CDT, Mike Burch <mburch372@...> wrote:


Hello everyone, 

I would like to use my AEA Packratt 232 with a Raspberry pi as the pc portion for packet radio.   Reason: Just to use it and see it work again.  Do you think this could work with just a serial port hat on the Pi?    Would the available software support this project?  The tnc is in perfect condition and even has the timewave dsp daughter boards.   Than you in advance.   Mike K8MB. 

701 - 720 of 13018