Digipeat and GPS

[Scott]

Hello 

Currently when digpi beacons with digipeater it will send the fixed position as defined 

during the initialization. 

# Beacon to RF
# PBEACON  compress=1 delay=00:05 every=20:00 symbol="digi" overlay=1 lat=33.183187 long=-84.268295 via=WIDE2-1  comment=" KJ4ZZB WIDE1 DigiPi http://digipi.org/ "

Since our digpi is connected to GPS and it is repositioned in various places during a deployment I want to use my GPS position. Apparently we can not rune GPS treace and Digipete simultaneously. 

So I ran sudo remount

edited the direwolf.digipeater.conf file (made a back up of course) and added two lines to make DW use the GSPD daemon and announce a position based on GPS 

# Use GPSD for DW digipeat Scott
GPSD localhost 2947

# change Pbeacon to use GPSD for digipeat Scott
# Beacon to RF
PBEACON  compress=1 delay=00:05 every=20:00 symbol="digi" overlay=1 via=WIDE2-1  comment=" KJ4ZZB WIDE1 DigiPi http://digipi.org/

Note I removed teh lat and long comments. 
# Our info
MYCALL KJ4ZZB-2
IGLOGIN KJ4ZZB-2  22192

# Beacon to RF -<< (commented out)
# PBEACON  compress=1 delay=00:05 every=20:00 symbol="digi" overlay=1 lat=33.183187 long=-84.268295 via=WIDE2-1  comment=" KJ4ZZB WIDE1 DigiPi http://digipi.org/ "

After saving my edits I rebooted and started digipete. 

My question is simple. Is this a proper thing to do?

In the AM I will go mobile and see what happens with APRS.FI. 

I am unable to fine a DW log to see what DW is actually sending . 

Thanks

Scott 

KJ4ZZB

[Scott Sheppard]

Craig et al

I am running APRS GSP Tracker 

I see this  Digipeater WIDE1 (probably W4BOC-1) audio level = 54(15/8)   FX.25   __+4_____

[0.3] ND1J-10>APDW16,W4BOC-1,WIDE1*,WIDE2-1:!3319.66NI08432.59W#PHG9250PI-DIREWOLF APRS IGATE/DIGI SENOIA GA

06:46:49  3D, 33.831970, -84.268172, 0.1 mph, nan°, 325.9 m

[0L] KJ4ZZB-2>APDW18,WIDE1-1:!3349.92NT08416.09W&360/000DigiPi igate/tracker http://digipi.org/

Is this acting as a digipeter, and I gate and announcing my position (KJ4ZZB-2) based on my GPS position. IF so then I am pleased. 

I am NOT seeing any results for KJ4ZZB-2 for Friday May 21 at 1:51 am (yet)

Thanks

Scott Sheppard

1702 Frazier Park Drive 

Decatur, GA 30033

732 861 3383 

sshe...@bellsouth.net

KJ4ZZB Call Sign

--
You received this message because you are subscribed to the Google Groups "DigiPi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digipi+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/digipi/a6b49fd6-b9fe-42ee-9526-ecaed8e1baf8n%40googlegroups.com.

[Craig]

Hi Scott - great question.

since WIDE1-1* has an asterisk next to it, it means that path was already
digipeated by somebody else (probably W4BOC-1), and DigiPi will therefore
not digipeat it again.

cool,
-craig
KM6LYW

To view this discussion visit https://groups.google.com/d/msgid/digipi/EBB5DA9C-5220-446D-8071-E7D36C11D684%40bellsouth.net.

[Craig]

Hi Scott, that's really close, to add a gps beacon checkout direwolf.tracker.conf or simply
add these lines to direwolf.digipeater.conf - then you'll have a digipeating tracker!! cool!

GPSD localhost

TBEACON delay=00:15 every=5:00 symbol="igate" overlay=T via=WIDE1-1 power=5 height=5 gain=3 comment="DigiPi igate/tracker http://digipi.org/"


(and remove PBEACON)

-craig
KM6LYW