[OZAPRS] Proposed digi for Mt Nardi
Ray Wells
vk2tv at exemail.com.au
Tue Aug 10 13:59:06 EST 2010
Steve,
83m is 272 ft, close enough to the 300 I guessed.
800m is a tad higher than what SPLAT! (and Google earth) thinks it is
but still close enough, especially given the step sizes available for
HAAT and Power.
HAAT - Height Above Average Terrain
Pick 0dB gain and the nearest height and you won't be too far off. It's
only a guide.
Ray vk2tv
On 10/08/10 09:27, Steve Sharp wrote:
> The tech got back to me with the following:
> "Antenna Gain is going to be 3db to start with but then unity when we
> get around to putting the 2m repeater up there , HAAT not
> sure what it means but antenna hight is 83m above ground or 883m above
> sea level"
> Sound about right?
> Steve VK2POO
>
> On 10 August 2010 07:48, Ray Wells <vk2tv at exemail.com.au
> <mailto:vk2tv at exemail.com.au>> wrote:
>
> Hi Steve,
>
> From SPLAT!, the pgrogram that produced the plots, HAAT is 2073.38
> ft. I guessed an antenna height of 300 ft when I did the plots.
> Take the difference between 300 and the "real" antenna height and
> add/subtract from 2073 and you'll have your figure.
>
>
> Typical antennas gains are
> 1. dipole - probably 1dB in some direction, depending on distance
> from support mast
> 2. 2 x dipole - 3dB
> 3. 4 x dipole - 6dB
> 4. double extended Zepp (each dipole half = 5/8) 3dB
> 5. 3 halfwaves in phase = 3dB
>
> An error of 1-2dB in your "guess" will be mostly insignificant on
> the radius of the resulting coverage circle.
>
> Cheers ... Ray
>
>
> --==[ SPLAT! v1.2.1 Site Analysis Report For: Nardi ]==--
>
> ---------------------------------------------------------------------------
>
> Site location: 28.5447 South / 206.7138 West (-28� 32' 40" S /
> 206� 42' 49" W)
> Ground elevation: 2608.27 feet AMSL
> Antenna height: 300.00 feet AGL / 2908.27 feet AMSL
> Antenna height above average terrain: 2073.38 feet
>
> Average terrain at 0 degrees azimuth: 689.75 feet AMSL
> Average terrain at 45 degrees azimuth: 756.54 feet AMSL
> Average terrain at 90 degrees azimuth: 1060.91 feet AMSL
> Average terrain at 135 degrees azimuth: 1151.16 feet AMSL
> Average terrain at 180 degrees azimuth: 686.42 feet AMSL
> Average terrain at 225 degrees azimuth: 585.24 feet AMSL
> Average terrain at 270 degrees azimuth: 919.58 feet AMSL
> Average terrain at 315 degrees azimuth: 829.48 feet AMSL
>
> ---------------------------------------------------------------------------
>
>
>
>
> On 09/08/10 18:28, Steve Sharp wrote:
>> G'day Ray - project is on the move again - the GM300 has been
>> repaired and aligned and I have taken a look at the digi_ned link
>> you sent regarding PHG and I'm sure we can add it as soon as the
>> tech tells me the HAAT and gain of the antenna.
>> At this stage I have to program up the Foxdigi witht he site info
>> and post it away to the installer who will get it up on Nardi
>> next time he is workign at the site.
>> Hopefully this'll kick interest along and we'll get some others
>> up in the months to follow.....
>> 73 de Steve VK2POO
>> On 23 July 2010 13:36, Ray Wells <vk2tv at exemail.com.au
>> <mailto:vk2tv at exemail.com.au>> wrote:
>>
>> Hi Steve,
>>
>> PHG is (P)ower, (H)eight, (G)ain and is sent in a beacon as
>> in this UIDigi example from VK2RMC-1. Software that handles
>> PHG will display a coverage circle around the digi site based
>> of the information transmitted by the digi.
>>
>> Beacon1Text = !3056.77SS15243.92E#PHG5513/
>> Kempsey, NSW
>>
>> Beacon2Text = !3056.77SS15243.92E#PHG5513/
>> Kempsey, NSW
>>
>> Beacon3Text = :146.875-
>> *111111z3048.00S/15255.00Er R50k
>>
>>
>> The 5513 says
>> 5 25W
>> 5 antenna 320 feet above average terrain
>> 1 1dB antenna gain
>> 3 pattern offset towards 135 degrees.
>>
>> Take a look here for further explanation
>>
>> http://digined.pe1mew.nl/?How_to:Calculate_PHG_information
>>
>> The extra S after Latitude causes a green star with the
>> letter S to be displayed as the digi icon.
>>
>> Beacons 1 and 2 are identical except for the path. Beacon 1
>> has no path set so it is not transmitted beyond the local
>> digi. Beacons 2 and 3 have a path of WIDE2-2 so that the
>> beacon will be digied over two hops.
>>
>> Beacon 3 is reporting the frequency and offset (146.875-),
>> time, location and range of the local voice repeater. The
>> series of 1's indicates that time is not set
>>
>> Howzat?
>>
>> Ray vk2tv
>>
>>
>> On 23/07/10 12:53, Steve Sharp wrote:
>>> G'day Ray - Ok, I said I was new, so what is PHG apart from
>>> a TLA?
>>> Steve
>>>
>>> On 23 July 2010 12:45, Ray Wells <vk2tv at exemail.com.au
>>> <mailto:vk2tv at exemail.com.au>> wrote:
>>>
>>> Steve,
>>>
>>> Wow! Nardi is a great site and will provide good
>>> coverage of northern vk2.
>>>
>>> Just a suggestion, can you include PHG in your beacon
>>> for PHG circle display?
>>>
>>> Well done.
>>>
>>> Regards, Ray
>>>
>>>
>>>
>>> On 23/07/10 12:12, Steve Sharp wrote:
>>>> I'm building up a digi for the Summerland club who are
>>>> going to place it on Mt Nardi. http://tinyurl.com/Mt-Nardi
>>>> Now I'm the first to put my hand up and say I'll have a
>>>> go - but sadly my skill set is a little light so I
>>>> thought it best to get some feedback from people who
>>>> have more experience in this field and hopefully get it
>>>> right the first time;-)
>>>> I'm using a foxdigi and seem to be getting the desired
>>>> effect and it is repeating (most) of the packets it
>>>> receives from VK4RGC-3.
>>>> I have configured it thus, but not sure that I have the
>>>> optimum settings yet....(obviously MYCALL and the BTEXT
>>>> location will be changed for it's installation site)
>>>> ECHO ON
>>>> TXDELAY 64
>>>> GPS $GPGGA
>>>> TRace OFF
>>>> MONitor ALL
>>>> DIGIpeater ON
>>>> BEACON On EVERY 30
>>>> UNPROTO WIDE1-1 V WIDE2-2
>>>> MYCALL VK2POO-3
>>>> MYALIAS WIDE2-1
>>>> BTEXT !2814.23s/15330.09e#/FoxDigi Testing for SARC
>>>> Any tweaks?
>>>> 73 Steve VK2POO
>>>>
>>>>
>>>> _______________________________________________
>>>> OZAPRS mailing list
>>>> OZAPRS at aprs.net.au <mailto:OZAPRS at aprs.net.au>
>>>> http://lists.aprs.net.au/mailman/listinfo/ozaprs
>>>
>>>
>>> _______________________________________________
>>> OZAPRS mailing list
>>> OZAPRS at aprs.net.au <mailto:OZAPRS at aprs.net.au>
>>> http://lists.aprs.net.au/mailman/listinfo/ozaprs
>>>
>>>
>>>
>>> _______________________________________________
>>> OZAPRS mailing list
>>> OZAPRS at aprs.net.au <mailto:OZAPRS at aprs.net.au>
>>> http://lists.aprs.net.au/mailman/listinfo/ozaprs
>>>
>>
>>
>> _______________________________________________
>> OZAPRS mailing list
>> OZAPRS at aprs.net.au <mailto:OZAPRS at aprs.net.au>
>> http://lists.aprs.net.au/mailman/listinfo/ozaprs
>>
>>
>>
>> _______________________________________________
>> OZAPRS mailing list
>> OZAPRS at aprs.net.au <mailto:OZAPRS at aprs.net.au>
>> http://lists.aprs.net.au/mailman/listinfo/ozaprs
>>
>
>
> _______________________________________________
> OZAPRS mailing list
> OZAPRS at aprs.net.au <mailto:OZAPRS at aprs.net.au>
> http://lists.aprs.net.au/mailman/listinfo/ozaprs
>
>
>
> _______________________________________________
> OZAPRS mailing list
> OZAPRS at aprs.net.au
> http://lists.aprs.net.au/mailman/listinfo/ozaprs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.aprs.net.au/pipermail/ozaprs/attachments/20100810/4c22a45c/attachment.htm
More information about the OZAPRS
mailing list