N1XDS
ÆS Ø
- Joined
- Nov 3, 2004
- Messages
- 2,014
Sent you an email.
- Status
Sent you an email.
As one of the Taunton guys that is heavily involved with three of the eastern Mass iDAS/NXDN repeaters, I can confirm that all of our repeater infrastructure is Icom based, so we can only do 6.25. Nearly all of our users have Icom mobiles/handhelds. Myself and one other guy have some Kenwood radios to go along with our Icom radios (I prefer my Kenwood NX-210 over the Icom handheld, but prefer the Icom mobiles over the NX-700).
I found these NXDN postings here on RR while doing some research toward our linking project. Our Taunton site has internet access, but Plymouth and Swansea do not. We have the Icom linking boards for our repeaters and plan to attempt to shoot an internet connection to the other sites via microwave linking (We have some Ubuiquiti equipment to try.). We are amenable to IP linking the Taunton iDAS repeater in with you guys, since that site has internet now. I'd be more than happy to speak to whomever is leading this linking project across the states.
John
N1OTY
I've replied to John and given him the information... We hope to see him soon on the Icom side of the WW NXDN net
... If anyone else is interested... drop me a line. We've got lots of things in the works around this topic. Same of for Kenwood... I'm actively working to bridge the 2 via IP.
Alan
We will be discussing this tomorrow night at our meeting. I've already forwarded the details via email to one of our railroad radio techs that maintain this equipment. We plan to bring the 145.28 repeater in Taunton online quickly. The other two sites do not have internet access, though we have acquired some Ubuiquiti 5.8 Ghz linking equipment and plan to try shooting an IP connection to the other sites. We'll see.
John
N1OTY
John
N1OTY
John,
The guys in Michigan that I'm working with are IP experts... If you like I can put you in touch with them. They may have some ideas on your p2p shots that you are doing?
Drop me a note and I'll share their contact info with you.
Thanks and if you have any questions, don't hesitate to ask.
Alan
kd8jgn
Member
I'm one of the guys from Michigan. Be more than happy to help.
Sent from my PC36100 using Tapatalk 2
Sent from my PC36100 using Tapatalk 2
We got Michigan on the WW NXDN net late last night. So far we have the following.
Atlanta
Tampa
Vancouver, BC
Toronto/Niagara
Lansing, MI
This weekend, we are currently slated to work on Eastern Mass, Northern RI - if all goes well, we should have those guys up online with us.
On the Kenwood side I should have a a repeater for development in a couple of weeks. As soon as I get that, we should have the Kenwood side online and can start work on the IP protocol side.
On that side today we have
Connecticut
Texas
and also Vancouver, BC
It's a small network, but it's taking shape and growing... Any fence setters, feel free to drop me a line.
Alan - W7QO
Atlanta, GA
Atlanta
Tampa
Vancouver, BC
Toronto/Niagara
Lansing, MI
This weekend, we are currently slated to work on Eastern Mass, Northern RI - if all goes well, we should have those guys up online with us.
On the Kenwood side I should have a a repeater for development in a couple of weeks. As soon as I get that, we should have the Kenwood side online and can start work on the IP protocol side.
On that side today we have
Connecticut
Texas
and also Vancouver, BC
It's a small network, but it's taking shape and growing... Any fence setters, feel free to drop me a line.
Alan - W7QO
Atlanta, GA
A bit of information for those not familiar with what we are doing.
A month or so ago, I started working on a way to over come some of the challenges that we have with linking multiple sites together via NXDN. While both Kenwood and Icom offer a solution, it's very limited and non-flexible. I'm talking multi-site conventional linking as there is really little benefit to any form of trunking with Ham radio.
As a result I've created a small piece of software that can really run anywhere. It allows multiple repeaters to be connected together and it handles all the *reflecting* of data between them. This still requires the Icom hardware and linking card, but it then extends those features to get beyond the 15 IP limit that it has.
I've also driven into the software on my side the following features along with, to the best of my knowledge, the first time some of these have been done with NXDN...
First - created a standalone NXDN reflector that supports up to 200 IP addresses (that's conservative and if we *ever* allow one to have that many we need to be shot!)... These NXREF's as we call them can also be clustered, and the software fully supports both a fixed and a dynamic method for adding new sites to each.
First - created a standalone NXDN reflector that can cross NAT and private/public address schemes, does not require port forwarding and still functions appropriately. This also allows for dynamic IP address schemes. It's also been testing on the major networks 4G wireless for the IP connectivity. (I have a mobile NXDN repeater that I drive around with along with a cradlepoint router and 4G wireless FOB and it stays connected to the NXREF and the WW NXDN network.)
First - enabled in the NXDN reflector, parts of the Icom NXDN multi site conventional protocol to be translated. This includes RAN translation on an IP by IP basis, both from and too. This allows for a new site coming onto the network that may not be using a common RAN to have it's RAN translated to the WW NXDN RAN and back. We'll be doing something similar with TG and if needed UID's.
First - enabled an NXDN GPS to APRS gateway, this allows for limited relay of GPS data from the NXDN network to the ARPS network. This is a very early implementation and will need lots more work. I just threw it together one evening and got it basically working.
hehe - and to think they said it couldn't be done…
This is open to all, and if you'd like more information, just drop me a message or email.
Thanks,
Alan Adamson - W7QO
Atlanta, GA
A month or so ago, I started working on a way to over come some of the challenges that we have with linking multiple sites together via NXDN. While both Kenwood and Icom offer a solution, it's very limited and non-flexible. I'm talking multi-site conventional linking as there is really little benefit to any form of trunking with Ham radio.
As a result I've created a small piece of software that can really run anywhere. It allows multiple repeaters to be connected together and it handles all the *reflecting* of data between them. This still requires the Icom hardware and linking card, but it then extends those features to get beyond the 15 IP limit that it has.
I've also driven into the software on my side the following features along with, to the best of my knowledge, the first time some of these have been done with NXDN
...First - created a standalone NXDN reflector that supports up to 200 IP addresses (that's conservative and if we *ever* allow one to have that many we need to be shot!)... These NXREF's as we call them can also be clustered, and the software fully supports both a fixed and a dynamic method for adding new sites to each.
First - created a standalone NXDN reflector that can cross NAT and private/public address schemes, does not require port forwarding and still functions appropriately. This also allows for dynamic IP address schemes. It's also been testing on the major networks 4G wireless for the IP connectivity. (I have a mobile NXDN repeater that I drive around with along with a cradlepoint router and 4G wireless FOB and it stays connected to the NXREF and the WW NXDN network
.)First - enabled in the NXDN reflector, parts of the Icom NXDN multi site conventional protocol to be translated. This includes RAN translation on an IP by IP basis, both from and too. This allows for a new site coming onto the network that may not be using a common RAN to have it's RAN translated to the WW NXDN RAN and back. We'll be doing something similar with TG and if needed UID's.
First - enabled an NXDN GPS to APRS gateway, this allows for limited relay of GPS data from the NXDN network to the ARPS network. This is a very early implementation and will need lots more work. I just threw it together one evening and got it basically working.
hehe - and to think they said it couldn't be done
…This is open to all, and if you'd like more information, just drop me a message or email.
Thanks,
Alan Adamson - W7QO
Atlanta, GA
N1XDS
ÆS Ø
- Joined
- Nov 3, 2004
- Messages
- 2,014
AB3AI,
There is two NXDN repeater systems in Lakeland which are:
N4KEG: 146.655- 146.055 RPTR tone PL/Ran 127.3 or Ran: 60 mixed mode WBFM and NXDN.
N4AMC: 442.275+ 447.425 RPTR tone Pl: 127.3 or Ran 60 mixed mode WBFM OR NXDN.
Also program Riverview as well:
NI4CE: 442.425+ 447.425 Ran: 1 NXDN only
NI4CE is popular with the locals who use this frequency during the day sometimes at night time. I use this system as well! System is currently linked to Atlanta, British Columbia and some other states. Also check out the NI4CE website at: West Central Florida Group, Inc - NI4CE Big Stick Repeater System
Also this website link below has all the NXDN systems for ham radio use:
https://docs.google.com/spreadsheet/ccc?key=0AreH921lr18cdDhpdFAxX2lERjZ1Rmw3QlB5NWZ0X0E#gid=0
Since my last post. The Little NXDN WW net has grown some. ...
So far we are as follows
Icom side
Atlanta, GA (2 repeaters, and my entire test environment )
Tampa, FL (1 repeater with the potential for 2 more pending hardware upgrades)
Cleveland, OH
Toronto/Niagara, CA/NY
Vancouver, BC (includes an analog bridge to their local 2mtr FM repeater as well, while waiting for new hardware to put up the Mixed solution)
South Lansing, MI
Taunton, MA (1 repeater with the potential for 2 more in Swansee, and Plymouth to come on line as they are able)
Icom in the works (mostly pending hardware delivery)
Hawaii
Kenwood side (should be linked via an analog bridge, while development on the digital to digital takes place)
LakeLand, FL
Eastern Connecticut
Texas
Vancouver, BC ( is paralleled with the Icom side for now)
Kenwood soon to be
Tallahassee, FL
Normally, you need a fixed public IP address to do this, but on the Icom side, I've created a way to do it over private or dynamic IP addresses, so if you have pretty much any form of internet, including the wireless type (clear, major cell, etc), we can get you linked in really easy. This also completely allows a repeater to be tasked as a mobile repeater... I used one with a Cradlepoint router, and 4G wireless FOB from Verizon/ATT/Tmobile, etc and it works just great...
I've recently completely the ability to keep local calls local and Wan on the Wan while Local is active. This was an essential thing to do... Next up with channelized calls either individual or group.
This is an interesting challenge in that I'm working with a protocol that isn't documented anywhere, doesn't match any of the published information on NXDN and is completely diverse between Kenwood and Icom.... Good thing I started early as that has really paid off.
Please PM or email me for specifics if you'd like.
Alan
...So far we are as follows
Icom side
Atlanta, GA (2 repeaters, and my entire test environment
)Tampa, FL (1 repeater with the potential for 2 more pending hardware upgrades)
Cleveland, OH
Toronto/Niagara, CA/NY
Vancouver, BC (includes an analog bridge to their local 2mtr FM repeater as well, while waiting for new hardware to put up the Mixed solution)
South Lansing, MI
Taunton, MA (1 repeater with the potential for 2 more in Swansee, and Plymouth to come on line as they are able)
Icom in the works (mostly pending hardware delivery)
Hawaii
Kenwood side (should be linked via an analog bridge, while development on the digital to digital takes place)
LakeLand, FL
Eastern Connecticut
Texas
Vancouver, BC ( is paralleled with the Icom side for now)
Kenwood soon to be
Tallahassee, FL
Normally, you need a fixed public IP address to do this, but on the Icom side, I've created a way to do it over private or dynamic IP addresses, so if you have pretty much any form of internet, including the wireless type (clear, major cell, etc), we can get you linked in really easy. This also completely allows a repeater to be tasked as a mobile repeater... I used one with a Cradlepoint router, and 4G wireless FOB from Verizon/ATT/Tmobile, etc and it works just great...
I've recently completely the ability to keep local calls local and Wan on the Wan while Local is active. This was an essential thing to do... Next up with channelized calls either individual or group.
This is an interesting challenge in that I'm working with a protocol that isn't documented anywhere, doesn't match any of the published information on NXDN and is completely diverse between Kenwood and Icom.... Good thing I started early as that has really paid off.
Please PM or email me for specifics if you'd like.
Alan
Icom and Kenwood on WW NXDN Net
I've succeeded in putting both the Kenwood NXDN net and the Icom NXDN together, digital end to end.
I've also got a basic reflector functional on the Kenwood side, it still need a bit more work before it's prime time, but it for sure is going to do away with the VPN requirement that stands currently. It should also allow up to 200 IP address per reflector (and they are cluster/nest able).
...
We should also have Turkey and Hawaii up here shortly... Hawaii is coming up on Icom and Turkey is coming up on Kenwood.
We are about to go *international*... Ok, I suppose we are there already as we Toronto and Vancouver up already.... But this makes it legitimate!
Alan
I've succeeded in putting both the Kenwood NXDN net and the Icom NXDN together, digital end to end.
I've also got a basic reflector functional on the Kenwood side, it still need a bit more work before it's prime time, but it for sure is going to do away with the VPN requirement that stands currently. It should also allow up to 200 IP address per reflector (and they are cluster/nest able).
...We should also have Turkey and Hawaii up here shortly... Hawaii is coming up on Icom and Turkey is coming up on Kenwood.
We are about to go *international*... Ok, I suppose we are there already as we Toronto and Vancouver up already
.... But this makes it legitimate!Alan
They are pretty similar in price and features... NOTE, you do not need the nxr700/800's from kenwood, the 710/810's are perfectly adequate for ham use.
Similar size, similar features, similar quality. It's really a ford/chevy question.
I prefer the integration of the IP board in the Icom to the Kenwoods external box, but it's really sixes.
The kenwood does offer one feature that the icom does not, however the two are not interoperable with this feature either and that's the use of 12.5khz spaced digital (9600 baud digital) vs. 6.25khz space (4800 baud) which both are compatible with. On a by channel basis, you have to pick one or the other too btw.
There are plenty of Icoms on ebay, so check there.... either the module if you want to save some money or the rack unit will work just fine.
Alan
I loaded the NXDN reflector on the first intercontinental computer today... If all goes well, we should have Turkey on the WW NXDN net on Wednesday. This is a first in a variety of ways.
a) it's a Kenwood repeater and we aren't going to use a VPN
b) it's going to run with static IP addresses for now, but that will change once we move some features over from the Icom version
c) it will be connected to the first Kenwood NXREF in the wild, and will be the first repeater connected there (all the others are running on a vpn to a dedicated NXREF there)
d) it will bridge the VPN version and the non-VPN version of the 2 NXREF's that are running currently
e) it will be the first intercontinental version, contact, link, etc via a homogeneous NXDN setup
I'm optimistic and I really want to get away from the requirement for a VPN on the Kenwood side. If this proves out, we've also conquered the 15 IP address limit and it will allow for around 100-200 IP addresses per NXREF (very conservative - the NXREF's are clusterable/nestable if wanted).
On the Icom side, Hawaii has their equipment and are working on getting it assembled and functional As soon as that happens, we should have Hawaii up and functional as well.
Lots of thing happening on the WW NXDN net
Alan
a) it's a Kenwood repeater and we aren't going to use a VPN
b) it's going to run with static IP addresses for now, but that will change once we move some features over from the Icom version
c) it will be connected to the first Kenwood NXREF in the wild, and will be the first repeater connected there (all the others are running on a vpn to a dedicated NXREF there)
d) it will bridge the VPN version and the non-VPN version of the 2 NXREF's that are running currently
e) it will be the first intercontinental version, contact, link, etc via a homogeneous NXDN setup
I'm optimistic and I really want to get away from the requirement for a VPN on the Kenwood side. If this proves out, we've also conquered the 15 IP address limit and it will allow for around 100-200 IP addresses per NXREF (very conservative - the NXREF's are clusterable/nestable if wanted).
On the Icom side, Hawaii has their equipment and are working on getting it assembled and functional As soon as that happens, we should have Hawaii up and functional as well.
Lots of thing happening on the WW NXDN net
Alan
I also put this together to help capture some of the information associate with the WW NXDN network and Amateur Radio...
NXDNINFO | NXDN and its application to Amateur Radio.
Alan
NXDNINFO | NXDN and its application to Amateur Radio.
Alan
Re: New NXDN (iDAS) Repeater in SE Michigan
We're in the process of building out our new dual-band mixed-mode ICOM iDAS (NXDN) system here in Pinckney, Michigan; which is very close to Hell; north of Ann Arbor...
146.500 MHz. +1.00 WFM (25.0 kHz.) DPL 047 / RAN 47 (SNPR)
442.675 MHz. +5.00 WFM (25.0 kHz.) DPL 047 / RAN 47 (Coordinated)
This repeater system supports: IRLP, EchoLink, and AllStar Link as well as the NXDN Worldwide Network via talkgroup 65000. At this time, coverage is limited until the weather breaks this spring/summer; then the tower work can begin.
The system hardware is an ICOM IC-FR5000 & IC-FR6000 with UC-FR5000 iDAS Network Controller Cards and SCOM 7330 Repeater Controller.
When programming radios for this system, please setup two separate channels, one as mixed-mode/analog transmit and the other as mixed-mode/digital transmit. For the Worldwide NXDN talkgroups, radio ID's should begin as 26Rxx; where "R" is you're region in the state. If you are from another state, you should use you already assigned/chosen radio ID number from your home state.
For those interested in adding NXDN systems here in Michigan, here is what I propose as a setup for various talkgroups that can be standardized throughout the state. I've already chose to implement this plan on our system as it closely follows the statewide radio system used by public-safety officials and most amateurs in Michigan should be familiar with this plan.
Statewide Talkgroups (Proposed):
26000 - Michigan Statewide All Call
26001 through 26084 - Reserved for Local Countywide Talkgroups
26085 - Michigan Statewide ARES/RACES Network
26086 - Michigan Statewide MICON/NWS/SkyWarn Weather Network
26087 through 26100 - Reserved for future Statewide Talkgroups
26101 - Region 1 (Southeast - Ann Arbor / Jackson and surrounding areas)
26202 - Region 2 (Southeast - Detroit Metro and surrounding areas)
26303 - Region 3 (Thumb - Flint, Bay City, Saginaw and surrounding areas)
26505 - Region 5 (Southwest - Kalamazoo and surrounding areas)
26606 - Region 6 (Western - Grand Rapids and surrounding areas)
26707 - Region 7 (Northern - Lower Peninsula includes Roscommon and surrounding areas)
26808 - Region 8 (Upper Peninsula)
Local Talkgroups (Proposed):
The format is: 26 (FIPS Code) followed a "Zero" and finally, the Michigan County Code where the repeater is located. See examples below:
26025 - Genesee County All Call
26033 - Ingham County All Call
26038 - Jackson County All Call
26047 - Livingston County All Call
26081 - Washtenaw County All Call
26082 - Wayne County All Call
26063 - Oakland County All Call
26078 - Shiawassee County All Call
While this is a relatively new exploration in amateur radio, NXDN has ALLOT to offer over the MotoTRBO systems. First is the cost, equipment is generally about 1/2 the cost of MotoTRBO equipment and can be purchased from either Kenwood OR ICOM. For conventional usage (analog/digital), there are seamless integrated. Second, the ability to support analog and digital together in one repeater, WITHOUT the need for additional software upgrades from Motorola. Following on the heals of this comment, NXDN, at least the ICOM repeaters allow for dynamic mixed-mode operation AND the ability to still access the IP network connections. From all documentation I can find on MotoTRBO, you now must choose either analog OR digital when using the IP Site Connect interface on the back of the repeater; this simple isn't the case with NXDN, although on limitation on this is that the carrier MUST drop prior to switching modes. This is a minor issue, but never-the-less, it allows amateur radio groups to begin implementation of a digital repeater system while still maintaining their current analog system and functionality; thus it doesn't force ALL of your systems users to purchase a digital radio right off the bat (a huge advantage over D-Star and MotoTRBO). Finally, software, easy to come by, cheaper to buy and with NXDN being an open platform now, the sky is the limit when it comes to ideas for software development... Ham's should love that idea.
Also, for those interested in ARES/RACES/SkyWarn or other Search and Rescue and Public-Safety operations; ICOM has introduced a GPS Speaker-Microphone called the "RedHawk SA"... It currently only supports the iDAS radios in analog mode; however, in a few short months, it will also support NXDN digital. This device is an excellent add on for Amateur Radio.
If you're not familiar with it, please see these links:
RedHawk SA - Icom America
RedHawk SA GPS Speaker Mic with LCD - YouTube
We're testing them here and they are simply an awesome add-on and the audio sounds excellent as well...
In conclusion, I have to say that I was a huge supporter of MotoTRBO early on; however, given the direction that technology is headed in, and NXDN's forward thinking methodology into where narrowbanding and where digital radio is heading, I think the Japanese engineers are headed in the right direction and with MotoTRBO still not officially backed by the FCC as an approved format, it seems to me that NXDN is exactly what D-Star should have been; NXDN uses the AMBE 2+ vocoder where as the D-Star platform does not, NXDN has forward error correct, D-Star does not; no more "R2D2" and terrible sounding digital audio (it's still digital, but it's good sounding digital) and with it only using 6.25 kHz. of bandwidth, this mode will allow for a greater number of users to experiment and install their own systems, it'll add roaming abilities, true-interoperabilty regardless of users buying Kenwood or ICOM and is afforable for even the most thrifty of Amateur Radio operators. With tough economic times, this is one reason that U.S. and Canadian railroads have adopted the NXDN platform moving forward; cost, technology, interoperability between brands, and no Mother M hawking over each and every radio sale, software license, etc. And by the way, ALL current NXDN radios can be reverted to WFM through firmware as can the MotoTRBO radios; you'll just need the right tools to do it, but the radio will work with ALL current repeaters in your area that haven't converted; so you're not buying a radio for just this technology, you're buying a good commercial quality radio for ALL of your Amateur Radio adventures (except HF of course)...
NXDN, check it out if you haven't already!
We're in the process of building out our new dual-band mixed-mode ICOM iDAS (NXDN) system here in Pinckney, Michigan; which is very close to Hell; north of Ann Arbor...
146.500 MHz. +1.00 WFM (25.0 kHz.) DPL 047 / RAN 47 (SNPR)
442.675 MHz. +5.00 WFM (25.0 kHz.) DPL 047 / RAN 47 (Coordinated)
This repeater system supports: IRLP, EchoLink, and AllStar Link as well as the NXDN Worldwide Network via talkgroup 65000. At this time, coverage is limited until the weather breaks this spring/summer; then the tower work can begin.
The system hardware is an ICOM IC-FR5000 & IC-FR6000 with UC-FR5000 iDAS Network Controller Cards and SCOM 7330 Repeater Controller.
When programming radios for this system, please setup two separate channels, one as mixed-mode/analog transmit and the other as mixed-mode/digital transmit. For the Worldwide NXDN talkgroups, radio ID's should begin as 26Rxx; where "R" is you're region in the state. If you are from another state, you should use you already assigned/chosen radio ID number from your home state.
For those interested in adding NXDN systems here in Michigan, here is what I propose as a setup for various talkgroups that can be standardized throughout the state. I've already chose to implement this plan on our system as it closely follows the statewide radio system used by public-safety officials and most amateurs in Michigan should be familiar with this plan.
Statewide Talkgroups (Proposed):
26000 - Michigan Statewide All Call
26001 through 26084 - Reserved for Local Countywide Talkgroups
26085 - Michigan Statewide ARES/RACES Network
26086 - Michigan Statewide MICON/NWS/SkyWarn Weather Network
26087 through 26100 - Reserved for future Statewide Talkgroups
26101 - Region 1 (Southeast - Ann Arbor / Jackson and surrounding areas)
26202 - Region 2 (Southeast - Detroit Metro and surrounding areas)
26303 - Region 3 (Thumb - Flint, Bay City, Saginaw and surrounding areas)
26505 - Region 5 (Southwest - Kalamazoo and surrounding areas)
26606 - Region 6 (Western - Grand Rapids and surrounding areas)
26707 - Region 7 (Northern - Lower Peninsula includes Roscommon and surrounding areas)
26808 - Region 8 (Upper Peninsula)
Local Talkgroups (Proposed):
The format is: 26 (FIPS Code) followed a "Zero" and finally, the Michigan County Code where the repeater is located. See examples below:
26025 - Genesee County All Call
26033 - Ingham County All Call
26038 - Jackson County All Call
26047 - Livingston County All Call
26081 - Washtenaw County All Call
26082 - Wayne County All Call
26063 - Oakland County All Call
26078 - Shiawassee County All Call
While this is a relatively new exploration in amateur radio, NXDN has ALLOT to offer over the MotoTRBO systems. First is the cost, equipment is generally about 1/2 the cost of MotoTRBO equipment and can be purchased from either Kenwood OR ICOM. For conventional usage (analog/digital), there are seamless integrated. Second, the ability to support analog and digital together in one repeater, WITHOUT the need for additional software upgrades from Motorola. Following on the heals of this comment, NXDN, at least the ICOM repeaters allow for dynamic mixed-mode operation AND the ability to still access the IP network connections. From all documentation I can find on MotoTRBO, you now must choose either analog OR digital when using the IP Site Connect interface on the back of the repeater; this simple isn't the case with NXDN, although on limitation on this is that the carrier MUST drop prior to switching modes. This is a minor issue, but never-the-less, it allows amateur radio groups to begin implementation of a digital repeater system while still maintaining their current analog system and functionality; thus it doesn't force ALL of your systems users to purchase a digital radio right off the bat (a huge advantage over D-Star and MotoTRBO). Finally, software, easy to come by, cheaper to buy and with NXDN being an open platform now, the sky is the limit when it comes to ideas for software development... Ham's should love that idea.
Also, for those interested in ARES/RACES/SkyWarn or other Search and Rescue and Public-Safety operations; ICOM has introduced a GPS Speaker-Microphone called the "RedHawk SA"... It currently only supports the iDAS radios in analog mode; however, in a few short months, it will also support NXDN digital. This device is an excellent add on for Amateur Radio.
If you're not familiar with it, please see these links:
RedHawk SA - Icom America
RedHawk SA GPS Speaker Mic with LCD - YouTube
We're testing them here and they are simply an awesome add-on and the audio sounds excellent as well...
In conclusion, I have to say that I was a huge supporter of MotoTRBO early on; however, given the direction that technology is headed in, and NXDN's forward thinking methodology into where narrowbanding and where digital radio is heading, I think the Japanese engineers are headed in the right direction and with MotoTRBO still not officially backed by the FCC as an approved format, it seems to me that NXDN is exactly what D-Star should have been; NXDN uses the AMBE 2+ vocoder where as the D-Star platform does not, NXDN has forward error correct, D-Star does not; no more "R2D2" and terrible sounding digital audio (it's still digital, but it's good sounding digital) and with it only using 6.25 kHz. of bandwidth, this mode will allow for a greater number of users to experiment and install their own systems, it'll add roaming abilities, true-interoperabilty regardless of users buying Kenwood or ICOM and is afforable for even the most thrifty of Amateur Radio operators. With tough economic times, this is one reason that U.S. and Canadian railroads have adopted the NXDN platform moving forward; cost, technology, interoperability between brands, and no Mother M hawking over each and every radio sale, software license, etc. And by the way, ALL current NXDN radios can be reverted to WFM through firmware as can the MotoTRBO radios; you'll just need the right tools to do it, but the radio will work with ALL current repeaters in your area that haven't converted; so you're not buying a radio for just this technology, you're buying a good commercial quality radio for ALL of your Amateur Radio adventures (except HF of course)...
NXDN, check it out if you haven't already!
Last edited:
kd8jgn
Member
I've got the other NXDN repeater in Michigan. We should meet up sometime.
- Status
Similar threads
