Yes I understand. I assume you do some math to make the position less accurate before building the transmit packet. It makes sense doing that instead of the documented method since I'd assume it takes a lot less code space. I think this is also how some software does it when sending compressed format.
The audio level is already higher than some commercial radioskf4hzu wrote: ↑Wed Sep 06, 2023 11:52 amYes I understand. I assume you do some math to make the position less accurate before building the transmit packet. It makes sense doing that instead of the documented method since I'd assume it takes a lot less code space. I think this is also how some software does it when sending compressed format.
Edited cause I read the 2nd part of your post wrong
Shown in this screen shot....
Screenshot 2023-09-06 074641.png
...at least on my RT3S the FM modulation level seems a little low. The "3(2/2)" should be 4 or 5 as the first digit. I'm not sure if there is a user-configurable setting that could correct this. I didn't see one when I checked.
It doesnt save code space, but just dopping characters doesn't give the same level of granularitykf4hzu wrote: ↑Wed Sep 06, 2023 11:52 amYes I understand. I assume you do some math to make the position less accurate before building the transmit packet. It makes sense doing that instead of the documented method since I'd assume it takes a lot less code space. I think this is also how some software does it when sending compressed format.
I had it set to 25KHz. Configuring for 12.5KHz does bring it up to level 4 which seems to be the lowest that I've seen from local stations.
Code: Select all
KF4HZU-7 audio level = 4(2/2) [NONE] _||||||__
[0.3] KF4HZU-7>APOG77,WIDE1-1,WIDE2-1:!2752.74N/08244.53W[RT3S
KK4EQF-12 audio level = 7(2/2) [SINGLE] _:_______
[0.1] KK4EQF-12>APMI06,WIDE2-2:@071258z2755.45N/08249.27W#Sharing The Beacon U=14.0V,T=0.0C
NB9X audio level = 4(1/2) [NONE] ||||||___
[0.2] NB9X>APW285,WIDE3-3:_09071451c111s001g001t086r000p000P000h00b10139wDAV<0x0d>
N4GD-10 audio level = 9(2/4) [NONE] ||||_____
[0.1] N4GD-10>KF4HZU:(UA res, f=1)
N4GD-10 audio level = 10(2/4) [NONE] ||||_____
[0.1] N4GD-10>KF4HZU:(I cmd, n(s)=0, n(r)=0, p=0, pid=0xf0)[WL2K-5.0-B2FWIHJM$]<0x0d>
KF4KUL-15 audio level = 6(1/2) [NONE] _|||_____
[0.2] KF4KUL-15>RW5S5Q,WIDE1-1,WIDE2-2:`nHgl{Wv/'"4'}|$-%z(!|!wo-!|3
MIC-E, VAN, Byonics TinyTrack3, En Route
N 27 53.5186, W 082 44.7513, 10 MPH, course 159, alt 52 ft
Seq=285, A1=453, A2=637
Yep it is DireWolf 1.6.0-413855e. I'm aware of how it worksVK3KYY wrote: ↑Wed Sep 06, 2023 8:17 pmWhere is that screenshot from ?
It looks a bit like DireWolf, which is dependant on the volume level you feed into your PC
Do you have other radios that transmit APRS and can you compare their audio level e.g. using Audacity on the PC to record the audio and look at the waveform
I've been working with TNCs, APRS and other digital modes since I got my license over 25 years ago. Packet radio is what got me in to this hobby.If you'd like it to function as many other radios and software packages do, then yes it is ok
I haven't personally seen anyone use settings beyond 1 or 2.Yep your method certainly allows more flexibility. It just has no way to indicate to other stations that the position is ambiguous/masked. Deleting characters is the standard that things understand. Perhaps offer both options if it isn't a significant cost in code space? I'm also very comfortable with metric measurements so no need to worry about how it translates. I prefer metric as it is just easier math.VK3KYY wrote: ↑Wed Sep 06, 2023 10:20 pmI can't imagine its worth reporting with masking of worse than 1 deg of accuracy. 1 deg is 111km , at the equator.
Also using values as powers of 10 of a degree gives roughly steps of 100m 500, 1km , 5km etc
Whereas dropping characters gives valus of accuracy like +- 66m or +-660m I'm not sure how this translates into miles
I think 660m is a bit less than half a mile.
Are you sure the clock is fine (and utc also), and of course your location.
