Re: Stuck sequence counter?
Hi Andrew,
The station is mobile. It's an Emergency Communications Trailer, equipped with GPS among other things, and running an instance of Xastir to display APRS information when deployed.? The data mentioned is being sent by Direwolf only (Xastir is not aware of it) and? includes several voltage and temperature measurements for various equipment on board to insure the trailer's readiness for deployment, during times when it is sitting unattended. It may or may not be important, but it worked fine for several weeks until I did an "apt-get update" yesterday. The system gets a nightly reboot.
The bearing and speed you suggest perhaps makes sense as it is currently parked, but I need to automatically update position when it gets moved. If I look at raw data on APRS.fi, it is being sent. Maybe APRS.FI has changed somehow, and it is not related to Direwolf or my use of it...
Regards,
Charlie
|
Re: Stuck sequence counter?
You might try using PBEACON instead of TBEACON. Is this station actually mobile (such that you need to use TBEACON)? I would guess that the 360/000 is the bearing and speed reported by your GPS. But if it's a fixed station, you don't need course and speed of the station, and can just hard-code the latitude and longitude in the direwolf.conf file. ________________________________________ From: [email protected] < [email protected]> on behalf of charlie gale <charles@...> Sent: Wednesday, January 5, 2022 3:10 PM To: [email protected]Subject: [direwolf] Stuck sequence counter? I'm still learning APRS data formats, but I'm having trouble with this one. I have an instance of Direwolf running on a Raspberry Pi, whose purpose is to send some measurements, along with location, at regular intervals. I'm doing this with a TBEACON command: TBEACON delay=:15 every=20 SYMBOL="/#" DEST=CQ COMMENTCMD="tail -1 /mnt/ramdisk/data.txt" via=WIDE1-1,WIDE2-2 I have a separate program, in a distant location, that gets a feed from APRS-IS, and filters for this data, then processes it. A sequence number gets added to the beginning of the comment field by Direwolf for some reason - not sure why, but it's not a problem. However, once the sequence number hits 360, it stops incrementing, so the sequence number after that is always 360. I'm guessing APRS-IS assumes the information is duplicate, and does not send it out the feed, so my remote receiver sees no data. If I reboot, everything works great until we get to message 360 again. What gets added is 360/000 - see below. From APRS.IS raw data:VY1EMO-9<>>CQ,VY1IRL-1<>,WIDE1*,WIDE2-2,qAR,VY1YC-1<>:!6041.74N/13506.18W#360/0000.02V,0.02V,0.02V,5.25V,-32.4C,2.4'C Any thoughts?
|
Sorry Andrew, I am a beginner and your answer to my question which was however simple at the beginning, does not bring me anything, too complicated.
It should be understood that there are people who are new to APRS and who do not have the experience of many of you
I'm giving up . thank you.
Le 05/01/2022 à 19:02, Andrew P. a
écrit?:
Note that the Power and Height values are coded as increasing exponentially. For example, there really isn't a lot of difference in performance between a 25 watt transmitter and a 26 watt transmitter, so specifying a Power code value of 5 (for 25 watts) is close enough for anything between about 20 to 29 watts. This keeps the PHG encoding compact (as in shorter APRS packets that will have less likelihood of getting a bit error or colliding with another station's transmission). Similarly, the actual height value is 10 times 2 to the Nth power (where N is the 2nd digit in the PHG phrase). So, unless your station setup happens to land exactly on the PHG step values, it will only be an approximation when viewed on an APRS receiver (such as aprs.fi).
If you insist on showing that you are (for example) running exactly 27.35 watts into a 37.5 foot tall tower, you'll need to put that into free text in your beacon comment, because the PHG encoding just doesn't have that much precision.
Andrew, KA2DDO
author of YAAC ("Yet Another APRS Client")
________________________________________
From: [email protected] <[email protected]> on behalf of Don Rolph <don.rolph@...>
Sent: Wednesday, January 5, 2022 12:49 PM
To: [email protected]
Subject: Re: [direwolf] PHG
F6GDL:
Lynn's site allows you to calculate the values for phg.
The format for the direwolf.conf line for a pbeacon is:
PBEACON delay=11 every=4 overlay=S symbol="digi" lat=42^08.85N long=071^13.61W power=1 height=20 gain=1 comment="East Walpole MA"
So use Lynn's calculator to get the values and then put those values in on the PBEACON line. They should also work on the TBEACON line but I have not tried.
On Wed, Jan 5, 2022 at 11:15 AM Lynn Deffenbaugh <kj4erj@...<mailto:kj4erj@...>> wrote:
says PHG3200/ assuming a 0dB gain antenna.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 1/5/2022 10:53 AM, F6GDL wrote:
Hello everyone,
With Direwolf 1.7 on my raspberry, I cannot find the correct settings for "PHG". The "aprs.fi" site does not give me the right information.
I have 15 W, an antenna 10m from the ground and it is omnydirectional. What do you think should be put?
thank you
--
73,
AB1PH
Don Rolph
--
|
I think you don't understand my question or it's me.
The translation may not be good English / French and French /
English ...
My callsign you can see it though ....
You don't really answer my question. but it does not matter.
I don't have "direction" in Direwolf so I don't understand how to
put the 4 digits obtained with a calculator. Your link doesn't
explain it to me or I'm too stupid ...
Le 05/01/2022 à 18:19, Lynn Deffenbaugh
a écrit?:
If you
would supply your station's callsign-ssid, we could look at what
you are seeing on aprs.fi.
And if you look at the calculator link I sent, you would see why
there are 4 digits (struggling to not just say "because that's the
PHG specification").
PHG's digits are Power, Height, Gain, and Direction.? But for some
reason it's not called PHGD.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and
Win32
On 1/5/2022 12:02 PM, F6GDL wrote:
Obviously I had used a calculator ... but
the parameters obtained are completely wrong on aprs.fi.
For a power of 15w, for example, what should I indicate in
Direwolf? (3 ???)
In addition there are only three parameters (power, height and
gain) Why 4-digit PHG?
--
|
I'm still learning APRS data formats, but I'm having trouble with this one. I have an instance of Direwolf running on a Raspberry Pi, whose purpose is to send some measurements, along with location, at regular intervals. I'm doing this with a TBEACON command:??TBEACON delay=:15 every=20 SYMBOL="/#" DEST=CQ COMMENTCMD="tail -1 /mnt/ramdisk/data.txt" via=WIDE1-1,WIDE2-2? ?I have a separate program, in a distant location, that gets a feed from APRS-IS, and filters for this data, then processes it.?
A sequence number gets added to the beginning of the comment field by Direwolf for some reason - not sure why, but it's not a problem. However, once the sequence number hits 360, it stops incrementing, so the sequence number after that is always 360. I'm guessing APRS-IS assumes the information is duplicate, and does not send it out the feed, so my remote receiver sees no data. If I reboot, everything works great until we get to message 360 again. What gets added is 360/000 - see below.
From APRS.IS raw data:>CQ,,WIDE1*,WIDE2-2,qAR,:!6041.74N/13506.18W#360/0000.02V,0.02V,0.02V,5.25V,-32.4C,2.4'C
Any thoughts?
|
Re: Analysis of log files: Dire Wolf 1.7, libgps.so.29, gpsd 3.23.2~dev, MT3333 gps
email to gps users rejected because of size of log files.
Log files in zip format attached.
Change extension from zi_ to zip.
Ok I have done a preliminary?review of the log files at the time of the message storm in Dire Wolf.? log files dire3.log, gpsd3.log. and nmea3.log attached for independent?review.
It is perhaps easiest to track the behavior?by first reviewing the direwolf log file, dire3.log.? This was captured?using the command:
direwolf -t 0 -d g > dire3.log
One can see the behavior of the packets around the time of gps fix:
gps_read: time=1641399042 fix=1 lat=-999999.000000 lon=-999999.000000 trk=-999999 spd=-999999.0 alt=-999999
gps_read: time=1641399044 fix=1 lat=-999999.000000 lon=-999999.000000 trk=-999999 spd=-999999.0 alt=-999999
gps_read: time=1641399046 fix=1 lat=-999999.000000 lon=-999999.000000 trk=-999999 spd=-999999.0 alt=-999999
GPSD: Location fix is now 3D.
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
One observes before gps fix, time is incrementing by 2 at each entry.? After gps fix, we have about 100 messages all with the same time stamp.
After about 100 messages in the log we see:
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
Transmit packet queue for channel 0 is too long.? Discarding packet.
Perhaps the channel is so busy there is no opportunity to send.
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
Transmit packet queue for channel 0 is too long.? Discarding packet.
Perhaps the channel is so busy there is no opportunity to send.
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
Transmit packet queue for channel 0 is too long.? Discarding packet.
It appears that the Dire Wolf internal message queue has filled and messages are discarded.? This appears to limit the aprs?messages to on the order of 101 (although this can vary slightly).
Looking at the gpsd messages in gpsd3.log at the time of fix:
{"class":"TPV","device":"/dev/ttyUSB0","mode":1,"time":"2022-01-05T16:10:44.086Z","ept":0.005} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:44.086Z","rms":0.000,"major":99999.000,"minor":99999.000,"orient":0.000,"lat":99999.000,"lon":99999.000,"alt":99999.000} {"class":"TPV","device":"/dev/ttyUSB0","mode":1,"time":"2022-01-05T16:10:45.086Z","ept":0.005} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:45.086Z","rms":0.000,"major":99999.000,"minor":99999.000,"orient":0.000,"lat":99999.000,"lon":99999.000,"alt":99999.000} {"class":"TPV","device":"/dev/ttyUSB0","mode":1,"time":"2022-01-05T16:10:46.086Z","ept":0.005} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:46.086Z","rms":0.000,"major":99999.000,"minor":99999.000,"orient":0.000,"lat":99999.000,"lon":99999.000,"alt":99999.000} {"class":"TPV","device":"/dev/ttyUSB0","mode":1,"time":"2022-01-05T16:10:47.086Z","ept":0.005} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:47.086Z","rms":0.000,"major":99999.000,"minor":99999.000,"orient":0.000,"lat":99999.000,"lon":99999.000,"alt":99999.000} {"class":"TPV","device":"/dev/ttyUSB0","mode":3,"time":"2022-01-05T16:10:48.086Z","ept":0.005,"lat":42.147531667,"lon":-71.226743333,"altHAE":73.6000,"altMSL":107.5000,"alt":107.5000,"magvar":-14.4,"geoidSep":-33.900,"eph":32.110} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:48.086Z","rms":0.000,"major":35.000,"minor":21.000,"orient":23.700,"lat":33.000,"lon":24.000,"alt":142.000} {"class":"TPV","device":"/dev/ttyUSB0","mode":3,"time":"2022-01-05T16:10:50.000Z","ept":0.005,"lat":42.147530000,"lon":-71.226735000,"altHAE":75.7000,"altMSL":109.6000,"alt":109.6000,"epv":21.850,"magvar":-14.4,"speed":0.373,"climb":1.097,"epc":22.83,"geoidSep":-33.900,"eph":109.250,"sep":36.860} {"class":"TPV","device":"/dev/ttyUSB0","mode":3,"time":"2022-01-05T16:10:50.000Z","ept":0.005,"lat":42.147530000,"lon":-71.226735000,"altHAE":75.7000,"altMSL":109.6000,"alt":109.6000,"epv":21.850,"track":338.8800,"magtrack":324.5025,"magvar":-14.4,"speed":0.195,"climb":1.097,"epc":22.83,"geoidSep":-33.900,"eph":109.250,"sep":36.860} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:50.000Z","rms":1.500,"major":32.000,"minor":20.000,"orient":27.000,"lat":30.000,"lon":23.000,"alt":130.000} {"class":"TPV","device":"/dev/ttyUSB0","mode":3,"time":"2022-01-05T16:10:51.000Z","ept":0.005,"lat":42.147528333,"lon":-71.226735000,"altHAE":74.2000,"altMSL":108.1000,"alt":108.1000,"epv":22.080,"magvar":-14.4,"speed":0.185,"climb":-1.500,"epc":43.93,"geoidSep":-33.900,"eph":109.250,"sep":110.770} {"class":"SKY","device":"/dev/ttyUSB0","xdop":7.07,"ydop":1.03,"vdop":0.96,"tdop":5.50,"hdop":5.75,"gdop":9.68,"pdop":5.83,"nSat":15,"uSat":4,"satellites":[{"PRN":31,"el":72.0,"az":282.0,"ss":28.0,"used":false,"gnssid":0,"svid":31},{"PRN":32,"el":67.0,"az":93.0,"ss":29.0,"used":true,"gnssid":0,"svid":32},{"PRN":25,"el":45.0,"az":62.0,"ss":24.0,"used":true,"gnssid":0,"svid":25},{"PRN":26,"el":29.0,"az":193.0,"ss":0.0,"used":false,"gnssid":0,"svid":26},{"PRN":51,"el":29.0,"az":227.0,"ss":0.0,"used":false,"gnssid":1,"svid":138},{"PRN":3,"el":18.0,"az":319.0,"ss":0.0,"used":false,"gnssid":0,"svid":3},{"PRN":1,"el":10.0,"az":281.0,"ss":0.0,"used":false,"gnssid":0,"svid":1},{"PRN":29,"el":8.0,"az":105.0,"ss":0.0,"used":false,"gnssid":0,"svid":29},{"PRN":21,"el":4.0,"az":261.0,"ss":0.0,"used":false,"gnssid":0,"svid":21},{"PRN":70,"el":82.0,"az":345.0,"ss":0.0,"used":false,"gnssid":6,"svid":6},{"PRN":69,"el":31.0,"az":137.0,"ss":21.0,"used":true,"gnssid":6,"svid":5},{"PRN":79,"el":28.0,"az":36.0,"ss":27.0,"used":true,"gnssid":6,"svid":15},{"PRN":88,"el":1.0,"az":21.0,"ss":0.0,"used":false,"gnssid":6,"svid":24},{"PRN":76,"el":0.0,"az":0.0,"ss":0.0,"used":false,"gnssid":6,"svid":12},{"PRN":71,"el":0.0,"az":0.0,"ss":26.0,"used":false,"gnssid":6,"svid":7}]} {"class":"TPV","device":"/dev/ttyUSB0","mode":3,"time":"2022-01-05T16:10:51.000Z","ept":0.005,"lat":42.147528333,"lon":-71.226735000,"altHAE":74.2000,"altMSL":108.1000,"alt":108.1000,"epx":106.062,"epy":15.379,"epv":22.080,"track":338.8800,"magtrack":324.5025,"magvar":-14.4,"speed":0.195,"climb":-1.500,"epc":43.93,"geoidSep":-33.900,"eph":109.250,"sep":110.770} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:51.000Z","rms":1.100,"major":29.000,"minor":20.000,"orient":27.600,"lat":27.000,"lon":22.000,"alt":105.000} {"class":"TPV","device":"/dev/ttyUSB0","mode":3,"time":"2022-01-05T16:10:52.000Z","ept":0.005,"lat":42.147525000,"lon":-71.226733333,"altHAE":72.9000,"altMSL":106.8000,"alt":106.8000,"epx":106.062,"epy":15.379,"epv":22.080,"magvar":-14.4,"speed":0.395,"climb":-1.300,"eps":212.12,"epc":44.16,"geoidSep":-33.900,"eph":109.250,"sep":110.770} {"class":"TPV","device":"/dev/ttyUSB0","mode":3,"time":"2022-01-05T16:10:52.000Z","ept":0.005,"lat":42.147525000,"lon":-71.226733333,"altHAE":72.9000,"altMSL":106.8000,"alt":106.8000,"epx":106.062,"epy":15.379,"epv":22.080,"track":338.8800,"magtrack":324.5025,"magvar":-14.4,"speed":0.195,"climb":-1.300,"eps":212.12,"epc":44.16,"geoidSep":-33.900,"eph":109.250,"sep":110.770} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:52.000Z","rms":1.100,"major":26.000,"minor":19.000,"orient":30.000,"lat":25.000,"lon":21.000,"alt":89.000}
It appears that speed is not provided in the gpspipe -w file which shows up as speed="NaN" in the Dire Wolf logs.
There are also some PRN records which I have not perused.
I have not reviewed the NMEA files, since that is a gpsd internal behavior.
So:
Dire Wolf 1.7 with libgps.so.23, libgps.so.28, or libgps.so.29 all show basically the same behavior when reading gpsd during time of GPS fix with the MT3333 gps? unit.
This works as expected with gpsd 3.17 but not in gpsd 3.23.2~dev (or gpsd 3.22-400).
This suggests that a change in the message format going from 3.17 to 3.22-400 is triggering a problem in the Dire Wolf gpsd code which worked as expected under gpsd 3.17.
I will now start perusing the code, BUT I am quickly outrunning?my area of expertise.
My thanks to all for their help so far!
|
As for the 4 digits of PHG(D), it appears
that they ARE supported in the PBEACON/OBEACON statements of the
Direwolf configuration file.? From the docuemntation:
It's just that you don't need to mention
it for an omni-directional antenna because that is the default.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and
Win32
On 1/5/2022 1:13 PM, F6GDL wrote:
toggle quoted message
Show quoted text
ma question était pourtant simple au départ mais nous ne nous
comprenons pas. Problème de traduction peut-être.
Les réponses sont toujours un peu à coté de la question. j'ai
utilisé ce calculateur et d'autres? !!!
Pour une puissance de 15 w, il faut indiquer 3 dans "power" ?
et 10M pour la hauteur =? 2 dans Direwolf ?
mais sur aprs.fi, ?a ne donne pas les bonnes indications. Ce
que je ne comprends pas aussi, c'est pourquoi on obtient 4
chiffres alors qu'il n'y a que trois paramètres à indiquer dans
Direwolf.
Désolé, tout le monde n'a pas votre expérience.
Le 05/01/2022 à 18:49, Don Rolph a
écrit?:
F6GDL:
Lynn's site allows you to calculate the values for phg.
The format for the direwolf.conf line for a pbeacon?is:
PBEACON delay=11 every=4 overlay=S symbol="digi" lat=42^08.85N long=071^13.61W power=1 height=20 gain=1 comment="East Walpole MA"
So use Lynn's calculator to get the values and then put those values in on the PBEACON line. They should also work on the TBEACON line but I have not tried.
On Wed, Jan 5, 2022 at 11:15
AM Lynn Deffenbaugh < kj4erj@...>
wrote:
says PHG3200/ assuming a 0dB gain antenna.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows
Mobile and Win32
On 1/5/2022 10:53 AM, F6GDL wrote:
Hello everyone,
With Direwolf 1.7 on my raspberry, I cannot find
the correct settings for "PHG". The "" site does not
give me the right information.
I have 15 W, an antenna 10m from the ground and
it is omnydirectional. What do you think should be
put?
thank you
--
--
|
Presuming that we are talking about the
F6GDL object being transmitted by F6IKY-2, examination of the raw
packets shows that there is not even a PHG term being
transmitted.? It is no wonder that the aprs.fi station information
doesn't reflect the power that is being discussed here.
WinMain:2022-01-05T19:28:33.634 F6IKY-2>APU25N,TCPIP*,qAC,T2NUERNBG:;F6GDL *090904z4632.27N/00502.02E-Roland - La Genete
WinMain:2022-01-05T19:28:33.685 F6IKY-2>APFD71,TCPIP*,qAC,T2NUERNBG:;F6GDL *090904z4632.27N/00502.02E-Roland - La Genete
aprs.fi will continue to show the most
recent PHG information that it has received for a station,
regardless of how long ago that information was received.? But the
current packets are NOT specifying any new PHG information.
I further don't understand why these
objects are being transmitted by both a UI-View instance
(>APU25N) and a Direwolf instance (>APFD71)?
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 1/5/2022 1:13 PM, F6GDL wrote:
ma question était pourtant simple au départ mais nous ne nous
comprenons pas. Problème de traduction peut-être.
Les réponses sont toujours un peu à coté de la question. j'ai
utilisé ce calculateur et d'autres? !!!
Pour une puissance de 15 w, il faut indiquer 3 dans "power" ?
et 10M pour la hauteur =? 2 dans Direwolf ?
mais sur aprs.fi, ?a ne donne pas les bonnes indications. Ce
que je ne comprends pas aussi, c'est pourquoi on obtient 4
chiffres alors qu'il n'y a que trois paramètres à indiquer dans
Direwolf.
Désolé, tout le monde n'a pas votre expérience.
Le 05/01/2022 à 18:49, Don Rolph a
écrit?:
F6GDL:
Lynn's site allows you to calculate the values for phg.
The format for the direwolf.conf line for a pbeacon?is:
PBEACON delay=11 every=4 overlay=S symbol="digi" lat=42^08.85N long=071^13.61W power=1 height=20 gain=1 comment="East Walpole MA"
So use Lynn's calculator to get the values and then put those values in on the PBEACON line. They should also work on the TBEACON line but I have not tried.
On Wed, Jan 5, 2022 at 11:15
AM Lynn Deffenbaugh < kj4erj@...>
wrote:
says PHG3200/ assuming a 0dB gain antenna.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows
Mobile and Win32
On 1/5/2022 10:53 AM, F6GDL wrote:
Hello everyone,
With Direwolf 1.7 on my raspberry, I cannot find
the correct settings for "PHG". The "" site does not
give me the right information.
I have 15 W, an antenna 10m from the ground and
it is omnydirectional. What do you think should be
put?
thank you
--
--
|
How to Set Path to wxnow.txt file
Using the Windows version (latest)
In the manual it shows:
PBEACON LAT=42^37.14N LONG=71^20.83W SYMBOL="weather station" COMMENTCMD="tail -1 wxnow.txt"
It looks like this is set to the default directory for direwolf.. I want my software (wx-display) to write it's wxnow.txt file to my OneDrive directory, so I can access it from a different computer. Direwolf is running on a 2nd computer, WX-Display is running on the first computer and I have it writing the wxnow.txt file to:
c:\Users\hbasr_000\OneDrive\? ? ? ? (the root of the OneDrive file)
Do I just precede the wxnow.txt with a backslash and the full path?
Please check the statement below and let me know if it is correct.
PBEACON LAT=42^37.14N LONG=71^20.83W SYMBOL="weather station" COMMENTCMD="tail -1 c:\Users\hbasr_000\OneDrive\wxnow.txt"
If not, please correct it.
Thanks, 73 de Hasan, N0AN
|
ma question était pourtant simple au départ mais nous ne nous
comprenons pas. Problème de traduction peut-être.
Les réponses sont toujours un peu à coté de la question. j'ai
utilisé ce calculateur et d'autres? !!!
Pour une puissance de 15 w, il faut indiquer 3 dans "power" ? et
10M pour la hauteur =? 2 dans Direwolf ?
mais sur aprs.fi, ?a ne donne pas les bonnes indications. Ce que
je ne comprends pas aussi, c'est pourquoi on obtient 4 chiffres
alors qu'il n'y a que trois paramètres à indiquer dans Direwolf.
Désolé, tout le monde n'a pas votre expérience.
Le 05/01/2022 à 18:49, Don Rolph a
écrit?:
F6GDL:
Lynn's site allows you to calculate the values for phg.
The format for the direwolf.conf line for a pbeacon?is:
PBEACON delay=11 every=4 overlay=S symbol="digi" lat=42^08.85N long=071^13.61W power=1 height=20 gain=1 comment="East Walpole MA"
So use Lynn's calculator to get the values and then put those values in on the PBEACON line. They should also work on the TBEACON line but I have not tried.
On Wed, Jan 5, 2022 at 11:15
AM Lynn Deffenbaugh < kj4erj@...>
wrote:
says PHG3200/ assuming a 0dB gain antenna.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows
Mobile and Win32
On 1/5/2022 10:53 AM, F6GDL wrote:
Hello everyone,
With Direwolf 1.7 on my raspberry, I cannot find
the correct settings for "PHG". The "" site does not
give me the right information.
I have 15 W, an antenna 10m from the ground and it
is omnydirectional. What do you think should be put?
thank you
--
--
|
Note that the Power and Height values are coded as increasing exponentially. For example, there really isn't a lot of difference in performance between a 25 watt transmitter and a 26 watt transmitter, so specifying a Power code value of 5 (for 25 watts) is close enough for anything between about 20 to 29 watts. This keeps the PHG encoding compact (as in shorter APRS packets that will have less likelihood of getting a bit error or colliding with another station's transmission). Similarly, the actual height value is 10 times 2 to the Nth power (where N is the 2nd digit in the PHG phrase). So, unless your station setup happens to land exactly on the PHG step values, it will only be an approximation when viewed on an APRS receiver (such as aprs.fi). If you insist on showing that you are (for example) running exactly 27.35 watts into a 37.5 foot tall tower, you'll need to put that into free text in your beacon comment, because the PHG encoding just doesn't have that much precision. Andrew, KA2DDO author of YAAC ("Yet Another APRS Client") ________________________________________ From: [email protected] < [email protected]> on behalf of Don Rolph <don.rolph@...> Sent: Wednesday, January 5, 2022 12:49 PM To: [email protected]Subject: Re: [direwolf] PHG F6GDL: Lynn's site allows you to calculate the values for phg. The format for the direwolf.conf line for a pbeacon is: PBEACON delay=11 every=4 overlay=S symbol="digi" lat=42^08.85N long=071^13.61W power=1 height=20 gain=1 comment="East Walpole MA" So use Lynn's calculator to get the values and then put those values in on the PBEACON line. They should also work on the TBEACON line but I have not tried. On Wed, Jan 5, 2022 at 11:15 AM Lynn Deffenbaugh <kj4erj@...<mailto:kj4erj@...>> wrote: says PHG3200/ assuming a 0dB gain antenna. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 1/5/2022 10:53 AM, F6GDL wrote: Hello everyone, With Direwolf 1.7 on my raspberry, I cannot find the correct settings for "PHG". The "aprs.fi<>" site does not give me the right information. I have 15 W, an antenna 10m from the ground and it is omnydirectional. What do you think should be put? thank you -- 73, AB1PH Don Rolph
|
F6GDL:
Lynn's site allows you to calculate the values for phg.
The format for the direwolf.conf line for a pbeacon?is:
PBEACON delay=11 every=4 overlay=S symbol="digi" lat=42^08.85N long=071^13.61W power=1 height=20 gain=1 comment="East Walpole MA"
So use Lynn's calculator to get the values and then put those values in on the PBEACON line. They should also work on the TBEACON line but I have not tried.
On Wed, Jan 5, 2022 at 11:15 AM Lynn Deffenbaugh < kj4erj@...> wrote:
says PHG3200/ assuming a 0dB gain antenna.
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 1/5/2022 10:53 AM, F6GDL wrote:
Hello everyone,
With Direwolf 1.7 on my raspberry, I cannot find the
correct settings for "PHG". The "" site does not give
me the right information.
I have 15 W, an antenna 10m from the ground and it is
omnydirectional. What do you think should be put?
thank you
|
I think you don't understand my question or it's me.
The translation may not be good English / French and French / English ...
My callsign you can see it though ....
You don't really answer my question (15W = P9 ???). but it does not matter.
I don't have "direction" in Direwolf so I don't understand how to put the 4 digits obtained with a calculator. Your link doesn't explain it to me or I'm too stupid ...
|
If you would supply your station's callsign-ssid, we could look at what you are seeing on aprs.fi.
And if you look at the calculator link I sent, you would see why there are 4 digits (struggling to not just say "because that's the PHG specification").
PHG's digits are Power, Height, Gain, and Direction.? But for some reason it's not called PHGD.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
toggle quoted message
Show quoted text
On 1/5/2022 12:02 PM, F6GDL wrote: Obviously I had used a calculator ... but the parameters obtained are completely wrong on aprs.fi.
For a power of 15w, for example, what should I indicate in Direwolf? (3 ???)
In addition there are only three parameters (power, height and gain) Why 4-digit PHG?
|
Analysis of log files: Dire Wolf 1.7, libgps.so.29, gpsd 3.23.2~dev, MT3333 gps
Ok I have done a preliminary?review of the log files at the time of the message storm in Dire Wolf.? log files dire3.log, gpsd3.log. and nmea3.log attached for independent?review.
It is perhaps easiest to track the behavior?by first reviewing the direwolf log file, dire3.log.? This was captured?using the command:
direwolf -t 0 -d g > dire3.log
One can see the behavior of the packets around the time of gps fix:
gps_read: time=1641399042 fix=1 lat=-999999.000000 lon=-999999.000000 trk=-999999 spd=-999999.0 alt=-999999
gps_read: time=1641399044 fix=1 lat=-999999.000000 lon=-999999.000000 trk=-999999 spd=-999999.0 alt=-999999
gps_read: time=1641399046 fix=1 lat=-999999.000000 lon=-999999.000000 trk=-999999 spd=-999999.0 alt=-999999
GPSD: Location fix is now 3D.
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
One observes before gps fix, time is incrementing by 2 at each entry.? After gps fix, we have about 100 messages all with the same time stamp.
After about 100 messages in the log we see:
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
Transmit packet queue for channel 0 is too long.? Discarding packet.
Perhaps the channel is so busy there is no opportunity to send.
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
Transmit packet queue for channel 0 is too long.? Discarding packet.
Perhaps the channel is so busy there is no opportunity to send.
gps_read: time=1641399048 fix=3 lat=42.147532 lon=-71.226743 trk=nan spd=nan alt=108
Transmit packet queue for channel 0 is too long.? Discarding packet.
It appears that the Dire Wolf internal message queue has filled and messages are discarded.? This appears to limit the aprs?messages to on the order of 101 (although this can vary slightly).
Looking at the gpsd messages in gpsd3.log at the time of fix:
{"class":"TPV","device":"/dev/ttyUSB0","mode":1,"time":"2022-01-05T16:10:44.086Z","ept":0.005} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:44.086Z","rms":0.000,"major":99999.000,"minor":99999.000,"orient":0.000,"lat":99999.000,"lon":99999.000,"alt":99999.000} {"class":"TPV","device":"/dev/ttyUSB0","mode":1,"time":"2022-01-05T16:10:45.086Z","ept":0.005} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:45.086Z","rms":0.000,"major":99999.000,"minor":99999.000,"orient":0.000,"lat":99999.000,"lon":99999.000,"alt":99999.000} {"class":"TPV","device":"/dev/ttyUSB0","mode":1,"time":"2022-01-05T16:10:46.086Z","ept":0.005} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:46.086Z","rms":0.000,"major":99999.000,"minor":99999.000,"orient":0.000,"lat":99999.000,"lon":99999.000,"alt":99999.000} {"class":"TPV","device":"/dev/ttyUSB0","mode":1,"time":"2022-01-05T16:10:47.086Z","ept":0.005} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:47.086Z","rms":0.000,"major":99999.000,"minor":99999.000,"orient":0.000,"lat":99999.000,"lon":99999.000,"alt":99999.000} {"class":"TPV","device":"/dev/ttyUSB0","mode":3,"time":"2022-01-05T16:10:48.086Z","ept":0.005,"lat":42.147531667,"lon":-71.226743333,"altHAE":73.6000,"altMSL":107.5000,"alt":107.5000,"magvar":-14.4,"geoidSep":-33.900,"eph":32.110} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:48.086Z","rms":0.000,"major":35.000,"minor":21.000,"orient":23.700,"lat":33.000,"lon":24.000,"alt":142.000} {"class":"TPV","device":"/dev/ttyUSB0","mode":3,"time":"2022-01-05T16:10:50.000Z","ept":0.005,"lat":42.147530000,"lon":-71.226735000,"altHAE":75.7000,"altMSL":109.6000,"alt":109.6000,"epv":21.850,"magvar":-14.4,"speed":0.373,"climb":1.097,"epc":22.83,"geoidSep":-33.900,"eph":109.250,"sep":36.860} {"class":"TPV","device":"/dev/ttyUSB0","mode":3,"time":"2022-01-05T16:10:50.000Z","ept":0.005,"lat":42.147530000,"lon":-71.226735000,"altHAE":75.7000,"altMSL":109.6000,"alt":109.6000,"epv":21.850,"track":338.8800,"magtrack":324.5025,"magvar":-14.4,"speed":0.195,"climb":1.097,"epc":22.83,"geoidSep":-33.900,"eph":109.250,"sep":36.860} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:50.000Z","rms":1.500,"major":32.000,"minor":20.000,"orient":27.000,"lat":30.000,"lon":23.000,"alt":130.000} {"class":"TPV","device":"/dev/ttyUSB0","mode":3,"time":"2022-01-05T16:10:51.000Z","ept":0.005,"lat":42.147528333,"lon":-71.226735000,"altHAE":74.2000,"altMSL":108.1000,"alt":108.1000,"epv":22.080,"magvar":-14.4,"speed":0.185,"climb":-1.500,"epc":43.93,"geoidSep":-33.900,"eph":109.250,"sep":110.770} {"class":"SKY","device":"/dev/ttyUSB0","xdop":7.07,"ydop":1.03,"vdop":0.96,"tdop":5.50,"hdop":5.75,"gdop":9.68,"pdop":5.83,"nSat":15,"uSat":4,"satellites":[{"PRN":31,"el":72.0,"az":282.0,"ss":28.0,"used":false,"gnssid":0,"svid":31},{"PRN":32,"el":67.0,"az":93.0,"ss":29.0,"used":true,"gnssid":0,"svid":32},{"PRN":25,"el":45.0,"az":62.0,"ss":24.0,"used":true,"gnssid":0,"svid":25},{"PRN":26,"el":29.0,"az":193.0,"ss":0.0,"used":false,"gnssid":0,"svid":26},{"PRN":51,"el":29.0,"az":227.0,"ss":0.0,"used":false,"gnssid":1,"svid":138},{"PRN":3,"el":18.0,"az":319.0,"ss":0.0,"used":false,"gnssid":0,"svid":3},{"PRN":1,"el":10.0,"az":281.0,"ss":0.0,"used":false,"gnssid":0,"svid":1},{"PRN":29,"el":8.0,"az":105.0,"ss":0.0,"used":false,"gnssid":0,"svid":29},{"PRN":21,"el":4.0,"az":261.0,"ss":0.0,"used":false,"gnssid":0,"svid":21},{"PRN":70,"el":82.0,"az":345.0,"ss":0.0,"used":false,"gnssid":6,"svid":6},{"PRN":69,"el":31.0,"az":137.0,"ss":21.0,"used":true,"gnssid":6,"svid":5},{"PRN":79,"el":28.0,"az":36.0,"ss":27.0,"used":true,"gnssid":6,"svid":15},{"PRN":88,"el":1.0,"az":21.0,"ss":0.0,"used":false,"gnssid":6,"svid":24},{"PRN":76,"el":0.0,"az":0.0,"ss":0.0,"used":false,"gnssid":6,"svid":12},{"PRN":71,"el":0.0,"az":0.0,"ss":26.0,"used":false,"gnssid":6,"svid":7}]} {"class":"TPV","device":"/dev/ttyUSB0","mode":3,"time":"2022-01-05T16:10:51.000Z","ept":0.005,"lat":42.147528333,"lon":-71.226735000,"altHAE":74.2000,"altMSL":108.1000,"alt":108.1000,"epx":106.062,"epy":15.379,"epv":22.080,"track":338.8800,"magtrack":324.5025,"magvar":-14.4,"speed":0.195,"climb":-1.500,"epc":43.93,"geoidSep":-33.900,"eph":109.250,"sep":110.770} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:51.000Z","rms":1.100,"major":29.000,"minor":20.000,"orient":27.600,"lat":27.000,"lon":22.000,"alt":105.000} {"class":"TPV","device":"/dev/ttyUSB0","mode":3,"time":"2022-01-05T16:10:52.000Z","ept":0.005,"lat":42.147525000,"lon":-71.226733333,"altHAE":72.9000,"altMSL":106.8000,"alt":106.8000,"epx":106.062,"epy":15.379,"epv":22.080,"magvar":-14.4,"speed":0.395,"climb":-1.300,"eps":212.12,"epc":44.16,"geoidSep":-33.900,"eph":109.250,"sep":110.770} {"class":"TPV","device":"/dev/ttyUSB0","mode":3,"time":"2022-01-05T16:10:52.000Z","ept":0.005,"lat":42.147525000,"lon":-71.226733333,"altHAE":72.9000,"altMSL":106.8000,"alt":106.8000,"epx":106.062,"epy":15.379,"epv":22.080,"track":338.8800,"magtrack":324.5025,"magvar":-14.4,"speed":0.195,"climb":-1.300,"eps":212.12,"epc":44.16,"geoidSep":-33.900,"eph":109.250,"sep":110.770} {"class":"GST","device":"/dev/ttyUSB0","time":"2022-01-05T16:10:52.000Z","rms":1.100,"major":26.000,"minor":19.000,"orient":30.000,"lat":25.000,"lon":21.000,"alt":89.000}
It appears that speed is not provided in the gpspipe -w file which shows up as speed="NaN" in the Dire Wolf logs.
There are also some PRN records which I have not perused.
I have not reviewed the NMEA files, since that is a gpsd internal behavior.
So:
Dire Wolf 1.7 with libgps.so.23, libgps.so.28, or libgps.so.29 all show basically the same behavior when reading gpsd during time of GPS fix with the MT3333 gps? unit.
This works as expected with gpsd 3.17 but not in gpsd 3.23.2~dev (or gpsd 3.22-400).
This suggests that a change in the message format going from 3.17 to 3.22-400 is triggering a problem in the Dire Wolf gpsd code which worked as expected under gpsd 3.17.
I will now start perusing the code, BUT I am quickly outrunning?my area of expertise.
My thanks to all for their help so far!
|
Obviously I had used a calculator ... but the parameters obtained are completely wrong on aprs.fi.
For a power of 15w, for example, what should I indicate in Direwolf? (3 ???)
In addition there are only three parameters (power, height and gain) Why 4-digit PHG?
|
says PHG3200/ assuming a 0dB gain antenna.
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
On 1/5/2022 10:53 AM, F6GDL wrote:
toggle quoted message
Show quoted text
Hello everyone,
With Direwolf 1.7 on my raspberry, I cannot find the
correct settings for "PHG". The "aprs.fi" site does not give
me the right information.
I have 15 W, an antenna 10m from the ground and it is
omnydirectional. What do you think should be put?
thank you
|
Re: Using CM108 not decoding Packet
Install the latest version of DireWolf (v1.7 or later)
Edit direwolf.conf specify
?"PTT cm108"?
in the channel configuration section.
Comment out or delete other PTT options, and comment out "#ADEVICE USB".
?
Connect the interface containing the CM108 or CM119 USB audio IC.
When you start Direwolf, it should display something like:?
Dire Wolf DEVELOPMENT version 1.7 A (Mar 15 2021)
Includes optional support for:? cm108-ptt
Reading config file direwolf.conf
Config file line 210: Found "\\?\hid#vid_0d8c&pid_000c&mi_03#8&19177d61&0&0000#" when expecting GPIO number or device name like /dev/hidraw1.
Available audio input devices for receive (*=selected):
Invalid input (receive) audio device number 2.
? ? 0: Microphone (2- HP Webcam 3100)
? ? 1: Microphone (2- C-Media USB Head
Available audio output devices for transmit (*=selected):
Invalid output (transmit) audio device number 2.
? ? 0: Speakers/Headphones (Realtek(R)
? ? 1: Speakers (2- C-Media USB Headph
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Using \\?\hid#vid_0d8c&pid_000c&mi_03#8&12bab26f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} GPIO 3 for channel 0 PTT control.
Ready to accept KISS TCP client application 0 on port 8001 ...
Ready to accept AGW client application 0 on port 8000 ...
?
If you do not see "Includes optional support for:? cm108-ptt"
you did not compile correctly, or need to download the latest pre-compiled version.?
Notice it warns you if you have the wrong sound interface selected.
Note the numbers for the "C-Media" device, and edit direwolf.conf to use these numbers in the ADEVICE section:?
" ADEVICE? 1 1 " in my case.
?
If you have more than one C-Media USB audio device connected (USB headset), you will have to change
?"PTT cm108"?
to the more explicit;
?"PTT CM108 \\?\hid#vid_0d8c&pid_000c&mi_03#8&19177d61&0&0000# "
or as indicated in your startup message.
?
There is a cm108.exe utility in your direwold install folder,?
that you can run from the cmd prompt, that identifies all connected C-Media devices.?
?
|
Hello everyone,
With Direwolf 1.7 on my raspberry, I cannot find the correct settings for "PHG". The "aprs.fi" site does not give me the right information.
I have 15 W, an antenna 10m from the ground and it is omnydirectional. What do you think should be put?
thank you
|
Re: Using CM108 not decoding Packet
Great!? Btw, Direwolf v1.5 should work fine but v1.6
is even better.? I don't know which OS you're running but
Raspberry Pi Bullseye has v1.6 available.? If you don't want to
replace the OS, compiling Direwolf isn't very difficult and is
covered in the Direwolf UserGuide:
??
--David
KI6ZHD
On 01/04/2022 08:30 PM, Lot K6IRF via
groups.io wrote:
toggle quoted message
Show quoted text
Hi David,
? Thanks ! I had it setup this way "ADEVICE -? plughw:1,0"?
Without the dash in the middle made it worked!? I am using it on a
Raspberry Pi.
Thank You ! 73?
Lot / k6irf
|
N0YWB