[OZAPRS] Beacon Intervals - Reminder

Andrew Rich (Home) vk4tec at tech-software.net
Sun Aug 30 10:50:15 EST 2009

Yep thats down right irresponsible 

Seeing 1200 baud takes some seconds to send.

Andrew Rich 
Airways Technical Officer Grade 4
Surveillance - RADAR ADS-B
Amateur Radio Callsign VK4TEC
email: vk4tec at tech-software.net
web: www.tech-software.net
  ----- Original Message ----- 
  From: Geoff Gatward 
  To: 'Australian APRS Users' 
  Sent: Sunday, August 30, 2009 9:14 AM
  Subject: [OZAPRS] Beacon Intervals - Reminder



  It seems that there are a group of users in the Central Coast/Newcastle region that have set a new standard for APRS trackers, using a THREE second beacon interval.  (Three callsigns have been noted doing this during initial investigations into the failure of the VK2RTZ-1 digipeater - not sure yet if this is related)


  PLEASE make sure that your beacon interval is set to NO LESS THAN 60 seconds.


  3 seconds does two things, both VERY bad.

  a.       Saturates the frequency locally so nobody else in simplex range can send their own beacons

  b.      Saturates the input of the receiving digipeaters so that nobody else in the digi coverage area can send their own beacons


  If you are in the area and notice anyone configured in this way, PLEASE ask them to change their setup.

  The configuration guidelines implemented NATIONALLY can be found here:   http://aprs.net.au/vhf_guidelines.php




  Geoff  VK2XJG



  OZAPRS mailing list
  OZAPRS at aprs.net.au


  No virus found in this incoming message.
  Checked by AVG - www.avg.com 
  Version: 8.5.409 / Virus Database: 270.13.71/2334 - Release Date: 08/29/09 17:51:00
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.aprs.net.au/pipermail/ozaprs/attachments/20090830/96d1d41f/attachment.htm 

More information about the Ozaprs mailing list