Dayton Frequencies

The guys in MA spurred me on to do this… I should have thought of it prior.

For 2013 at Dayton this year.

Expect NXDN on these frequencies.

VHF – 147.555
VHF – 145.28
UHF – 441.000

All simplex, most likely run no RAN (squelch set to carrier or none), however I know the guys from MA on the 145.28 will be on RAN 1

Have fun, I can’t make it this year due to family commitments.

Alan

Updated listing of currently connected sites.

Current list of linked systems, frequencies and RAN codes.

  • I – Atlanta, GA – 442.025+, RAN 1
  • I – Atlanta, GA – 443.050+, RAN 1
  • I – Cleveland, OH – 444.45625+, RAN 1
  • I – Tampa, FL – 444.425+, RAN 1
  • I – New Port Richey, FL – 442.7625+, RAN 1
  • I – South Lansing, MI – 443.250+, RAN 5
  • I – Toronto, ONT – 443.050+, RAN 1
  • I – Taunton, MA – 145.280-, RAN 1
  • I – Swansea, MA – 145.320-, RAN 1
  • I – Pinckney, MI – 146.500 +1.000mhz, RAN 47
  • I – Seattle, WA – ?? (coming online soon)
  • K – Venice, FL – 444.100+, RAN 1
  • K – Orlando, FL – 442.0375+, RAN 1
  • K – Lakeland, FL – 146.655-, RAN 1
  • K – Bristol, CT – 449.975-, RAN 1
  • K – Bristol, CT – 145.220-, RAN 1 (off net until further notice)
  • K – Johnson City, TX
  • K – Greensboro, FL – 147.390+, RAN 1
  • K – Tallahassee, FL – 444.175+, RAN 1
  • K – Milwaukee, WI – 444.750+, RAN 1
  • K – Ankara, Turkey – 145.775-, RAN 1
  • K – Vancouver, BC
  • K – Searcy, AR – 146.655-, RAN 1
  • K – Searcy, AR – 444.500+, RAN 1

New Reflector online

Image

After some issues with our prior provider, I just bit the bullet and got a slice of a virtual server online for real…

This is an image of the last 24 hours of bandwidth usage since I got all the repeaters and other reflectors moved over to it… :)…

We’ll see now what a standard month brings so we can gauge utilization.

Bandwidth

Kenwood Info

When adding a Kenwood repeater to the network… 2 things are required.

a) you MUST turn off the Over the Air Alias on both the repeater and any users radios.  If you don’t, there is a better than 50% chance that NO icom radio will hear your call which can be pretty frustrating when you’re on a WW linked system.

b) your repeater MUST run Very Narrow on the Digital side.  Icom does not support 12.5khz digital, only 6.25 and so the 2 systems are not compatible unless they both are set for 6.25khz… this is a Kenwood repeater setting btw.

Tallahassee, FL now online!

Ok, so it’s probably time that I created some form of table of who’s what, where :)…

We just brought up a new Kenwood site today on VHF and Norm in Tallahassee will be adding a UHF site to that a bit later.

Current list of linked systems, frequencies and RAN codes.

  • I – Atlanta, GA – 442.025+, RAN 1
  • I – Atlanta, GA – 443.050+, RAN 1
  • I – Cleveland, OH – 444.45625+, RAN 1
  • I – Tampa, FL – 444.425+, RAN 1
  • I – New Port Richey, FL – 442.7625+, RAN 1
  • I – South Lansing, MI – 443.250+, RAN 5
  • I – Toronto, ONT – 443.050+, RAN 1
  • I – Taunton, MA – 145.280-, RAN 1
  • I – Swansea, MA – 145.320-, RAN 1
  • I – Pinckney, MI – 146.500 +1.000mhz, RAN 47
  • I – Seattle, WA – ?? (coming online soon)
  • K – Venice, FL – 444.100+, RAN 1
  • K – Orlando, FL – 442.0375+, RAN 1
  • K – Lakeland, FL – 146.655-, RAN 1
  • K – Bristol, CT – 449.975-, RAN 1
  • K – Bristol, CT – 145.220-, RAN 1 (off net until further notice)
  • K – Johnson City, TX
  • K – Greensboro, FL – 147.390+, RAN 1
  • K – Tallahassee, FL – 444.175+, RAN 1
  • K – Milwaukee, WI – 444.750+, RAN 1
  • K – Ankara, Turkey – 145.775-, RAN 1
  • K – Vancouver, BC
  • K – Searcy, AR – 146.655-, RAN 1
  • K – Searcy, AR – 444.500+, RAN 1

Yet another *FIRST*!

This morning we conducted a little test.  A Kenwood Repeater, connected to a 4G Wireless router, all external IP addresses are private and will not accept incoming port forward requests.

We successfully connected the Kenwood to the WW NXDN network and carried on a conversation. :).

Stealth IP now works on the Kenwood NXREF…. yeah, no more VPN, no more static IP address, no more 15 IP limit.  I think we’ve now shattered all the barriers …

Alan

Added Turkey – Yes, the Country

Today we brought up a club in Turkey onto the WW NXDN network.  This proved that we can do Kenwoods without a VPN, and it proved that we can make them work over multiple hops.  I still think there is a gremlin or two to be worked out but Say Hi to The gang from Turkey.

Hi Alan,

Thank you very much for your great effort. I think we did :-))

I’m attaching the photos  again. You can use them on your blog

(nxdninfo.com ) if you want.

The names and callsigns:

from left to right

Cengiz. TB2BBG.

Cemal TA2AW

Serhat TA2ANK

Serdar TA3AS

Tahir TA2T

Our Club name is ANTRAK.

I’ll always remember your help and your friendship.

Best Regards,

Serdar

 

The guys from Turkey

Seems I always forget one detail :)

For those that are looking to join in the fun.

We’re trying to allow for keeping local traffic local and net traffic on the net.  In order to do that I’ve built a way to filter on Talk Group (Kenwood calls this Group ID).  If you have TG 65000 programmed in your HT or Mobile and you key up, you will go out over the net side, if you have any other TG selected, you will stay local to your repeater.  The opposite is true as well.  The net won’t invade your local QSO until the NXREF sees no activity for a programmable amount of time, then it will allow net traffic back on the repeater.  You can force this to happen immediately if the NXREF see’s the 65000 TG transmitted.

Also to better separate us out.  For now we are all on RAN 1.  I can translate RAN’s on the Icom side, I can’t yet on the Kenwood side.

So bottom line,

To get on the net, takes RAN 1, TG 65000, any other RAN or TG and you’ll just be talking on your local repeater.