Playing and learning more about PHG circles, specifically with regards to directivity. Was comparing what I input to what YAAC displays and what aprs.fi displays. I noticed aprs.fi displays a cardioid pattern when given a gain direction. Looking at the APRS specs, it should not be a cardioid pattern, it should just offset the circle. YAAC correctly implements an offset circle.
However...
The degrees that the circle is offset in the YAAC display are incorrect.
Quick table:
Input---YAAC display
N (0/360)---E (90)
NE (45)---NE (45)
E (90)---N (0/360)
SE (135)---NW (315)
S (180)---W (270)
SW (225)---SW (225)
W (270)---S (180)
NW (315)---SE (135)
The direction control of the PHG circles only works with the Beacon Type set to "POSITION", not with "MicE" nor with "COMPRESSED".
Side note, the Monitor frequency does not seem to allow changes to "simplex" or "PL" fields.
Last edit: John 2015-01-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The geometry error is definitely a bug, and has been fixed for the next build (to be released soon). Same with the offset and PL fields for beacon definitions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Playing and learning more about PHG circles, specifically with regards to directivity. Was comparing what I input to what YAAC displays and what aprs.fi displays. I noticed aprs.fi displays a cardioid pattern when given a gain direction. Looking at the APRS specs, it should not be a cardioid pattern, it should just offset the circle. YAAC correctly implements an offset circle.
However...
The degrees that the circle is offset in the YAAC display are incorrect.
Quick table:
Input---YAAC display
N (0/360)---E (90)
NE (45)---NE (45)
E (90)---N (0/360)
SE (135)---NW (315)
S (180)---W (270)
SW (225)---SW (225)
W (270)---S (180)
NW (315)---SE (135)
The direction control of the PHG circles only works with the Beacon Type set to "POSITION", not with "MicE" nor with "COMPRESSED".
Side note, the Monitor frequency does not seem to allow changes to "simplex" or "PL" fields.
Last edit: John 2015-01-01
The geometry error is definitely a bug, and has been fixed for the next build (to be released soon). Same with the offset and PL fields for beacon definitions.