Tag Archives: Wires-X

Ham radio VoIP and K8JTK Hub DVMIS Presentations

Presentation on Ham radio VoIP (Voice over IP) modes and the K8JTK Hub Digital VoIP Multimode Interlink System which integrates many Ham radio modes, both analog and digital.

Framework

The framework I chose to use for the presentation slides is called reveal.js. It is an HTML framework meaning it will run in any HTML 5 capable browser. Looks a little better than a PowerPoint presentation.

Navigation

Useful navigation keys in the presentation. In addition to navigating with the keys below, you can swipe (tables/smartphones) or use the navigation arrows on screen in the lower right.

Toggle full screen: press [F11].

Advance to the next slide: press [n] or [SPACEBAR].

Go back to the previous slide: press [p] or press and hold the [SHIFT] key while pressing the [SPACEBAR].

Display presentation overview: [ESC] then use the arrow keys or mouse to select a slide. [ESC] again will exit overview mode.

Links

Clickable links are colored in brown text.

Presentations

Three variations are available: presentation version is viewable in a browser. Printable version for printing or saving in a different format (Chrome, Chromium, and variants compatible only). Finally a PDF version.

They may take some time to load because I left original images untouched and some were a couple MB in file size.

Slides

The presentation is around 60 minutes in length.

Version 3

Presentation version
Printable version
PDF version

This presentation was given at the following meetings:
West Chester Amateur Radio Association on 7/6/2023 & 11/7/2024

Version 2

Presentation version
Printable version
PDF version

This presentation was given at the following meetings:
West Chester Amateur Radio Association on 5/6/2021.

Version 1

Presentation version
Printable version
PDF version

This presentation was given at the following meetings:
Portage County Amateur Radio Service on 3/8/2021.

Ohio Section Journal – The Technical Coordinator – December 2020 edition

One of the responsibilities of the Technical Coordinator in the Ohio Section is to submit something for the Section Journal. The Section Journal covers Amateur Radio related things happening in and around the ARRL Ohio Section. It is published by the Section Manager Scott – N8SY and articles are submitted by cabinet members.

Once my article is published in the Journal, I will also make it available on my site with a link to the published edition.

You can receive the Journal and other Ohio Section news by joining the mailing list Scott has setup. You do not need to be a member of the ARRL, Ohio Section, or even a ham to join the mailing list. Please sign up!

If you are an ARRL member and reside in the Ohio Section, update your mailing preferences to receive Ohio Section news in your inbox. Those residing outside the section will need to use the mailing list link above.
Updating your ARRL profile will deliver news from the section where you reside (if the leadership chooses to use this method).
Go to www.arrl.org and logon.
Click Edit your Profile.
You will be taken to the Edit Your Profile page. On the first tab Edit Info, verify your Email address is correct.
Click the Edit Email Subscriptions tab.
Check the News and information from your Division Director and Section Manager box.
Click Save.

Now without further ado…


Read the full edition at:

THE TECHNICAL COORDINATOR
Jeff Kopcak – TC
k8jtk@arrl.net

DSCF5081 K8JTKHey gang,

One of the things I’ve been working on during my time at home is the Digital VoIP Multimode Interlink System (DVMIS), also called the K8JTK Hub. About a year-and-a-half ago, I came up with this bright idea to setup a system that would interlink many different ham radio VoIP (Voice over IP) modes for interoperability and experimentation. Through trials and tribulations, it’s experiencing some success, caught the interest of some nets, and a podcast.

Many digital modes sit on their own island and are restricted from crossing over to the analog world or to other digital networks. Some may say this is for quality-of-service but does nothing for interoperability or the ability to link and communicate across different systems. Original D-STAR DPLUS reflectors banned analog connections. My Hub supports ham radio experimentation by allowing hams to discover ways of utilizing a system that can link different modes. Utilization of ham radio spectrum is a priority through the use of hot spots and repeaters. Connections without RF are not a priority. Hamshack Hotline was provisioned because of use in Emergency Operation Centers. Many times, I’ve been asked about stations that don’t have access to RF hotspots or radios. They still have options including the Echolink app on Android and iOS devices, Hamshack Hotline phone which can be purchased for $30 (I’ve heard deals as low as $5 for a compatible phone), or the DudeStar app. The servers are hosted in a Chicago data center to provide resiliency against hardware, power, weather, and Internet outages, but still be fairly inexpensive.

All this is possible through integration of open-sourced packages including: AllStarLink which is a world wide network of Amateur Radio repeaters, remote base stations and hot spots accessible to each other via the Internet and/or private IP networks. Built on an open-sourced PBX system called Asterisk, Jim Dixon – WB6NIL (SK) built the apt_rpt module emulating functionality of a repeater controller. Jonathan – G4KLX authored programs that support D-Star, DMR, System Fusion, P25, and NXDN which are utilized in MMDVM devices like most hotspots. DVSwitch is a suite of applications for provisioning and operating Amateur Radio digital voice networks maintained by Steve – N4IRS and Mike – N4IRR. The DVSwitch Mobile app was designed to operate analog and digital modes utilizing an Android phone in conjunction with server applications running on a Linux server or Raspberry Pi. The ASL to DMR documentation (groups.io account required) got me started experimenting with these applications and ultimately lead to the build out of the system. XLXD is a multiprotocol reflector server for D-STAR by Jean-Luc – LX3JL & Luc – LX1IQ. Skip – WB6YMH & others maintain thebridge, an Echolink compatible conference bridge.

Originally, hosted on 2 servers, after troubleshooting some issues, it was more reliable to host everything across 3 VPSes (Virtual Private Servers) running Debian Linux. Parts of the system can go down and individual parts will continue to function. Aside from the VPSes, a Raspberry Pi with a Northwest Digital Radio DV3000 provides D-STAR audio transcoding to the system. Wires-X is available through the use of additional remote hardware. Wires-X is proprietary to Yaesu radios and repeaters. Wires-X is not available through open-source implementations such as YSFReflector or MMDVM without additional devices. I’d like to get the DV3000s in a reliable data center but doing so is prohibitively expensive. AllStar Link is the “Hub” that provides connectivity and linking control between all networks.

Putting all of this together provides a system with access to ten different networks and eight different modes! Any user on one network can communicate with users on other networks. Access is available through these nodes and connections:

  • AllStar Link: 50394
  • DMR: Brandmeister Talk Group 3172783
  • DMR: TGIF TG 31983
  • D-STAR: XLX983A (A = Analog Bridge. Pi-STAR = DCS983A, OpenSpot = XLX983A)
  • Echolink: *DVMIS* conference 600008
  • Hamshack Hotline: 94026 (*99 – TX, # – RX)
  • NXDN: TG 31983
  • P25: TG 31983
  • YSF: K8JTK-Hub 31983
  • Wires-X: K8JTK-ROOM 40680 (available upon request)

Dashboards:

Amateur Logic episode 149

Building this system has not been without problems. Luckily, I’m able to work around known issues. In order from least frustrating to most frustrating: all programs use IP addresses and ports to communicate, keeping all of that straight was a challenge initially. Using IPs allows for great flexibility utilizing network links such as private networks and VPNs. Dependency hell as a result of additions and changes to programs made a constant deployment from one day to the next an issue. XLXD changed its implementation to include YSF which then conflicted with the port used for the YSFReflector. Changing the YSFReflector port required propagation to Pi-STAR host files and OpenSpot DNS. DVSwitch has been rewritten two times since I’ve implemented it and they’ve released another round of changes. Data center provider choices resulted in issues with packet loss. Moving the servers to another provider yielded much better results. The previous provider finally acknowledged and supposedly resolved the issue a year after it was reported, and after I moved.

Use of physical hardware for D-STAR. OP25 software codec can transcode D-STAR but “you won’t be happy” to quote a post in the forums. D-STAR looooves IP addresses. DNS is great for switching IP addresses easily (like when moving data centers or spinning up different servers). However, D-STAR relies only on IP addresses. As a result, reflector IP changes take about a day to propagate to online hotspots/repeaters. Using AMBEServer with the DV3000 on a remote device resulted in very choppy audio. After some time, had the idea to move Audio Bridge to the same device as the DV3000 then use IP routing to send audio to and from AB. Worked great.

In order to compile AllStar Link from source takes a lot of time to get right and includes A LOT of dependencies. Finally, one that drove me crazy was the chan_echolink module for AllStar which provides Echolink connectivity natively to AllStar. When load testing with many connections, something was making stations sound as though they were transmitting underwater. After observing patterns, determined it was audio originating on the Hub being sent out to Echolink connections. Incoming audio from Echolink stations was OK and audio sent to all other nodes was also good. The problem seemed intermittent until I consulted groups.io and further determined chan_echolink has audio quality problems when more than three EL stations are connected simultaneously. Not ideal for a hub. Best workaround was to implement an Echolink Conference server. Then only allow chan_echolink connection to that conference server. Echolink users would then connect to the same conference server. This issue took a lot of time and a lot of hair pulling but implemented a workable solution that offers a quality system. Root cause is still unknown as an AllStar developer hadn’t chimed-in with any suggestions or possible reasons.

K8JTK Hub/DVMIS connections

The DVMIS hub hosts a couple nets. Tuesday nights at 9pm eastern, since about the first-time stay-at-home orders were put in place, is the Amateur Logic Sound Check net. The net encourages checkins to utilize as many modes as possible during the net to test equipment. If you haven’t seen the Amateur Logic podcast, it has been going for over 15 years and they release two shows monthly. The regular podcast has segments about technology and Ham Radio. “Ham College” is an educational show for those wanting to get licensed or upgrade. The guys asked me to put together a segment for the show. My segment can be found in episode 149. A huge thanks goes out to the ALTV crew and everyone checking into the net which helped me identify and resolve system issues. They’ve also been great in keeping up with all the changes over the last 9 months. At the end of December, I’ve been testing with the West Chester Amateur Radio Association – WC8VOA to add digital modes to their net on Monday evenings at 8pm.

Around the time my segment was airing on ALTV, Brandmeister did not approve of the linking method and linking to other networks. Brandmeister uses the MCC standard and they manage talkgroup IDs consisting of 3, 4, or 5 digits. 6- or 7-digit IDs are repeater IDs and user IDs respectively, and can be used however the assigned owner would like. The BM TG in the ALTV episode is now 3172783 and is correct in the listing above.

The Hub is open for all to use in testing equipment, software, or linking up with friends. I keep status updates listed on the page linked at the beginning of this article. For this and any linked system, please remember a couple practices. When keying your radio, pause a second or two to allow all links to rise, otherwise the first couple words maybe lost. Pause a minimum 3-5 seconds between transmissions to give time for links to reset and other stations to break in. Do not “tailgate.” Enjoy and join the nets to get a feel for the Interlink System’s capabilities.

Slow Scan TV has become big over the last couple years due to ARISS (Amateur Radio on the International Space Station) events. One of the longer events will have begun before OSJ publication: starting December 24 at 16:40 UTC and continue through December 31 ending at 18:15 UTC. Dates are subject to change due to ISS operational adjustments. Images will be downlinked at 145.800 MHz +/- 3 KHz for Doppler shift and the expected SSTV mode of operation is PD 120. Radio enthusiasts participating in the event can post images they receive at the ARISS SSTV Gallery at https://www.spaceflightsoftware.com/ARISS_SSTV/. After your image is posted at the gallery, you can acquire a special award by linking to https://ariss.pzk.org.pl/sstv/ and follow directions for submitting a digital copy of your received image. Even an HT can receive images from the space station. If you would like to receive images using MMSSTV on Windows, head over to my tutorial.

Congratulations to Scott Yonally – N8SY who won his election as Great Lakes Division Vice Director! Since he cannot hold more than one elected position at a time, he will be stepping down from his current Section Manager position when he assumes the Vice Director position on Jan 1. I wish him nothing but the best in his new role as he has done a lot for the Ohio Section during his tenure. We will then welcome Tom Sly – WB8LCD who will be appointed the new Section Manager for Ohio!

Thanks for reading. Happy holidays, Merry Christmas, and Happy New Year!
73… de Jeff – K8JTK

K8JTK Hub DVMIS Presentations

Presentation on the K8JTK Hub Digital VoIP Multimode Interlink System which integrates many Ham radio modes, both analog and digital.

Framework

The framework I chose to use for the presentation slides is called reveal.js. It is an HTML framework meaning it will run in any HTML 5 capable browser. Looks a little better than a PowerPoint presentation.

Navigation

Useful navigation keys in the presentation. In addition to navigating with the keys below, you can swipe (tables/smartphones) or use the navigation arrows on screen in the lower right.

Toggle full screen: press [F11].

Advance to the next slide: press [n] or [SPACEBAR].

Go back to the previous slide: press [p] or press and hold the [SHIFT] key while pressing the [SPACEBAR].

Display presentation overview: [ESC] then use the arrow keys or mouse to select a slide. [ESC] again will exit overview mode.

Links

Clickable links are colored in brown text.

Presentations

Three variations are available: presentation version is viewable in a browser. Printable version for printing or saving in a different format (Chrome, Chromium, and variants compatible only). Finally a PDF version.

They may take some time to load because I left original images untouched and some were a couple MB in file size.

Slides

The presentation is about 10 minutes in length which aired on the AmateurLogic.TV podcast on 11/13/2020 for episode 149.  It includes additional slides referenced in the video segment.

Presentation version
Printable version
PDF version

Segment:

Ohio Section Journal – The Technical Coordinator – June 2018 edition

One of the responsibilities of the Technical Coordinator in the Ohio Section is to submit something for the Section Journal. The Section Journal covers Amateur Radio related things happening in and around the ARRL Ohio Section. It is published by the Section Manager Scott – N8SY and articles are submitted by cabinet members.

Once my article is published in the Journal, I will also make it available on my site with a link to the published edition.

You can receive the Journal and other Ohio Section news by joining the mailing list Scott has setup. You do not need to be a member of the ARRL, Ohio Section, or even a ham to join the mailing list. Please sign up!

If you are an ARRL member and reside in the Ohio Section, update your mailing preferences to receive Ohio Section news in your inbox. Those residing outside the section will need to use the mailing list link above.
Updating your ARRL profile will deliver news from the section where you reside (if the leadership chooses to use this method).
Go to www.arrl.org and logon.
Click Edit your Profile.
You will be taken to the Edit Your Profile page. On the first tab Edit Info, verify your Email address is correct.
Click the Edit Email Subscriptions tab.
Check the News and information from your Division Director and Section Manager box.
Click Save.

Now without further ado…


Read the full edition at: http://arrl-ohio.org/news/2018/OSJ-Jun-18.pdf

THE TECHNICAL COORDINATOR
Jeff Kopcak – TC
k8jtk@arrl.net

DSCF5081 K8JTKHey gang,

The Wood County Amateur Radio Club (which I’m a member) has a Fusion digital net on Thursday nights. Longtime club member Phil – W8PSK, posed the question: can I operate a Wires-X node mobile from my RV?

A little background about Wires-X setups. Wires-X is part of Yaesu’s System Fusion and is a closed Internet linking system. Only Yaesu hardware is allowed. Other digital devices like the OpenSpot, DVMega, and Pi-Star are not permitted. The obvious answer, if it were a viable choice, would be to use a digital hotspot but Yaesu doesn’t allow them. Wires-X hardware requirements include: a Yaesu FTM-100D or FTM-400XD radio or Fusion repeater, Yaesu HRI-200 interface between the radio and PC, a Windows 7 or 10 PC (yes, it must be Windows machine), and an Internet connection with a global IP address. A common example of a global IP address is one provided to you by your DSL, Cable, or Fiber provider. This IP is accessible from anywhere on the Internet and (generally) unrestricted. Lastly, another radio is required to use the Wires-X node locally.

Having setup my own Wires-X node in addition to LEARA’s repeater node, my first assumption was Phil would be able to connect out from his node in the RV to any other Wires-X node, but no other node could connect to him. This theory was based on the need to open or “port forward” 7 ports from the Internet to the PC running the Wires-X software. Port forwarding is a computer networking method used to allow data to bypass a firewall which would normally block that communication. Those that run websites from their network or have access to IP cameras while away from home will have these port forwards configured in their router.

Phil planned on using his smartphone as the Internet connection to the PC. Modern Smartphones have the ability to use the cellular network to serve an Internet connection to other devices like a laptop or Raspberry Pi via Wi-Fi connection. This is labeled something like “Mobile Hotspot” or “Personal Hotspot” in the phone. Standard disclaimer: check with your provider first in case there is an extra charge for this service or bandwidth cap. Bandwidth is standard for a Voice over Internet system at about 60kpbs/connection or about 30 MB/hour/connection with constant TX/RX. Port forwarding is never allowed on consumer cell plans. The unknown was can the Wires-X software connect without the port forwarding outlined in the configuration.

I tested my theory to see if the Wires-X software functioned by modifying a known working Wires-X configuration. I closed (temporarily disabled) the forwarded ports on my network. This meant communication over those ports would now be blocked, similar to that of a cellular connection. Then restarted the Wires-X software and hoped for the best. Was my theory correct? Drumroll please… the answer was: no. Wah waaaah. Not having the required ports forwarded to the PC did not allow the software to receive data from the Wires-X network. That result almost killed any hope of Phil using Wires-X mobile in his RV.

Phil was determined and we looked further into different solutions. VPNs were an option because they can often bypass network restrictions. However, a small number of VPN providers allowed forwarding ports as part of their service. Reviews weren’t positive and VPNs tend to easily fail with unstable data connections as one might have while mobile. Not something to be messing around with while driving. It introduced another point-of-failure in this setup. Hilariously enough, there were applications that touted the ability to ‘open ports on your phone.’ These wouldn’t work because it might open ports on the phone, almost assuredly the provider was blocking any ports upstream to the phone. Verizon offers a business account which allows port forwards but there is a one-time setup cost of $500 plus the service. Yeah, no. I suggested asking in the Yahoo group. John – N9UPC, Fusion representative for Yaesu, reinforced the conclusion I came to: operating mobile wasn’t possible because wireless providers don’t provide a global IP. Though Phil posted his question in late April, oddly enough John did not give any indication to an announcement at Dayton. One solution that looked promising used AMPRNet which is block of Internet routable IP addresses for ham radio operators. It could give us the global IP address we needed. After finding out more, someone else’s data center was being used and we weren’t sure Phil would have permission to use it as well.

Sensing no way to get around the port forward restriction, an announcement came during the Fusion forum at Dayton that (we hope) will solve Phil’s problem. Yaesu is going to release an update in the coming months that will allow the FT2DR, FTM-100D, as well as the FTM-400XD to operate as a portable node. With additional cables, these radios would connect directly to a computer for Wires-X operation without the need of an HRI-200. This was created specifically for mobile setups and users who don’t have the ability to forward the necessary ports (like in a hotel). Ding, ding, ding, we have a winner!

A couple caveats: purchase of an HRI-200 is still required. To use the portable node, you still need to register on the Wires-X system which requires a serial number from an HRI-200. The portable setup will not have ‘all of the features’ of the traditional setup such as hosting a Room (round table-type node) or messaging. Purchase of two cables is required to make the necessary connections: an SCU-19 USB and CT-44 audio cable. It wasn’t clear if both are needed for the 100/400 radios. There are no plans “at this time” to integrate any other Fusion radio other than the three listed above.

It would have been nice to have a heads-up about this new option before we spent time researching a solution. I think this will solve Phil’s problem and get him mobile with Wires-X. Announcement from the Fusion form, Dayton Hamvention 2018.

Speaking of digital hotspots, my favorite has been discontinued: the openSPOT. Saw it disappeared form dealer sites just after Dayton. June 8th it was removed from the SharkRF website with an announcement that a new product was going to be introduced soon. What could it be??! If you need a digital hotspot device today, I really like the ZUMSpot with the Pi-Star software. I picked up one with a case at Dayton. More info in future articles.

The next big ham holiday, Field Day, is right around the corner. Get out and join your club or find a club to join if you’re not a member of one. It’s a great time to bring friends and get them excited about ham radio. Hams that come out get bitten by the bug to expand their station or learn a new mode. Check the Field Day Locator for operations taking place near you. Sending 10 messages over RF from your site gets you 100 points – including Winlink messages. I love to receive messages about your setup, stations operating, or social activities taking place. These can be sent via the National Traffic System (NTS) or Winlink – K8JTK at Winlink.org – to my station. Winlink post about Field Day points.

With July around the corner, two of my favorite events will be kicking-off soon. The 13 Colonies Special Event is coming up July 1 – 7, along with the RAC Canada Day Contest on July 1st only.

Thanks for reading and 73… de Jeff – K8JTK

Ohio Section Journal – The Technical Coordinator – August 2017 edition

One of the responsibilities of the Technical Coordinator in the Ohio Section is to submit something for the Section Journal. The Section Journal covers Amateur Radio related things happening in and around the ARRL Ohio Section. It is published by the Section Manager Scott – N8SY and articles are submitted by cabinet members.

Once my article is published in the Journal, I will also make it available on my site with a link to the published edition.

You can receive the Journal and other Ohio Section news by joining the mailing list Scott has setup. You do not need to be a member of the ARRL, Ohio Section, or even a ham to join the mailing list. Please sign up!

If you are an ARRL member and reside in the Ohio Section, update your mailing preferences to receive Ohio Section news in your inbox. Those residing outside the section will need to use the mailing list link above.
Updating your ARRL profile will deliver news from the section where you reside (if the leadership chooses to use this method).
Go to www.arrl.org and logon.
Click Edit your Profile.
You will be taken to the Edit Your Profile page. On the first tab Edit Info, verify your Email address is correct.
Click the Edit Email Subscriptions tab.
Check the News and information from your Division Director and Section Manager box.
Click Save.

Now without further ado…


Read the full edition at: http://arrl-ohio.org/news/OSJ-August-17.pdf

THE TECHNICAL COORDINATOR
Jeff Kopcak – TC
k8jtk@arrl.net

DSCF5081 K8JTKHey gang,

Yaesu and System Fusion. I’ve talked about it before and mentioned the DR-1X repeater promotion some time ago. My recent dealings are leaving me more disappointed in the quality of the offering. With the announcement of System Fusion II, I hope they take time to finally fix problems with their implementation.

Around the beginning of 2015, Yaesu, in an effort to get their digital mode into the ham radio market, offered a promotional deal for their Fusion repeater at a cost of $500 (~$1,700 retail). The logic behind this is the shaver and blade principal: sell the repeater for cheap and make up the cost in selling radios. The repeater is dual-mode capable (C4FM digital and analog) featuring high power (50W) transmitter, switched commercial power and battery backup, integration with an existing repeater controller, all in a standard 2U rack unit. Not only could a club or individual purchase a digital repeater for cheap, it wasn’t a requirement of the promotion to enable any of the digital Fusion features. This meant it could replace aging analog repeaters. I’ve even heard old tube repeaters were being replaced as a result. Now, I’m sure they hoped owners utilized the Fusion features but either way, the program ended up being a huge success. In the Cleveland area, there are about 10 in operation that I’m aware of. Yaesu brought affordable and a somewhat-hackable (AllStar, MMDVM) repeater package to the market.

Then came the complaints. First being the DR-1X is two FTM-400 mobile radios linked with a basic controller. For some reason, many are surprised by this setup and thought better radios should be used. This is a common design that D-STAR and DMR commercial repeaters also rely on. However, this setup had a problem; the radios used were not designed to operate high power. Either through component design or improper cooling, the radios are not capable of operating 100% duty cycle at 50W. I have not heard of this being a wide-spread problem with D-STAR and DMR repeaters running high power. Yaesu updated their promotional form and website to say “Duty cycle is 50% at 50 Watts, 100% at 20 Watts in a climate controlled environment.” To get 50 watts or more, external amplifiers are needed.

Automatic Mode Select was one of the great selling points – a single repeater could switch between digital and analog depending on the signal. But reports of repeaters in AMS where locking up in a transmit state. It was discovered when the repeater had a signal on the input (digital or analog), if another signal was detected of the opposite type, the repeater would lockup in transmit. To reset, the power had to be cycled. A work around was to set the repeater in either analog or digital only mode or install a remote power switch. To my knowledge, this was never acknowledged and was deemed to be “environmental site issues.” That might be true or related to reports of poor selectivity on the front-end of the repeater. Filters and firmware upgrades helped solve some of these issues.

Other known problems include: external controller support is complicated – at best, receive PL decode problems, repeater identifications being cut-off, and the firmware. The firmware is absurd. There are three firmware “channels” (or tracks) for the DR-1X repeater. Each completely separate and not compatible with the other – that is you cannot upgrade the repeater firmware from one channel to another. For reference, these are the 1.00b, 1.00f, and 1.10D channels. Upgrading to a newer version (on the same channel) requires taking the machine out of the cabinet, unscrew about 18 screws to access the data port inside, upgrade the firmware, and put it all back. It is nearly a two person job as the thing weights 22 lbs.

My club in Cleveland, LEARA, purchased a DR-1X. I got it on the air with some help from Bill K8SGX (a section TS). It was on the air at 20 watts in digital only mode. We didn’t have any issues. One of the club members suggested “let’s connect this to the internet.” This is where my perception of Fusion got much worse. As confirmed by Yaesu support, to directly connect an HRI-200 Wires-X node, the DR-1X must have firmware 1.10J or later. Owners with 1.00-anything firmware MUST ship the DR-1X back to Yaesu for an upgrade at owner’s expense. 22 lbs shipping plus box and insurance, it was not cheap. Specific situations may vary and return shipping is covered. They will not let you swap anything yourself because they felt upgrades where beyond most owners’ ability. Owners on the 1.10D channel just need to apply firmware upgrades.

To be fair, an RF link to the repeater can be established with any firmware version. This entails setting up a HRI-200 on a Windows PC with an additional FTM-100 or FTM-400 radio at a location with a strong signal into the repeater. This setup acts like a local user of the repeater. Transmissions from the Internet are transmitted on the repeater’s input. Local repeater transmissions are relayed to the Internet by listening to the repeater’s output frequency. LEARA decided to directly link the HRI-200 Wires-X device to the repeater. Other devices like an OpenSpot or MMDVM could be used but would not provide Wires-X access as it is a closed network.

I haven’t followed the radio issues too closely. There have been 2nd generations of two Fusion radios this far. The FT1-DR was replaced by the FT1-XDR and FTM-400 by the FTM-400XDR because the GPS chip used had problems locking on to signals. I have the FTM-400XDR and picked up a FT2DR at Dayton. Both radios work and get the job done but I’m not blown away by either radio. To put the 400 over the top, it would need to operate Fusion from both A & B sides of the radio, at the same time. I’m underwhelmed by the FT2 screen as it’s not very sharp. I’ve always found Yaesu menu groupings and labeling confusing. The much-loved bank link feature of their analog radios, such as the VX-8, is missing.

Word of warning to anyone using Yaesu Fusion radios and is especially important for repeater owners and Wires-X node operators, keep up-to-date with firmware and program updates! It has been confirmed in the Yahoo Group, every time an FT-70 radio is keyed on a Wires-X node with software version v1.2 or earlier, the Wires-X node will crash.

In addition to all these issues, no full specification has been released for Fusion or Wires-X. Meaning if Wires-X gets shutdown, all nodes are offline. With an open source specification, a new network could be developed or rolled into the FCS reflector or YSFReflector networks. In true hacker fashion, much of Fusion has been reverse engineered so it’s probably more of a reality than I know.

A Reddit posting appeared proclaiming “System Fusion II” is coming with an accompanying info graphic and FAQ posted on the Yaesu System Fusion Yahoo Group. The info graphic states ‘firmware upgrades will enable System Fusion II compatibility with all existing C4FM products.’ I gather this doesn’t mean the radio needs to be sent back to Yaesu. The FT1-(X)DR is discontinued but the FAQ reiterates all existing radios will receive a Fusion II firmware upgrade.

At the center is the new DR-2X repeater – which supposedly resolves most problems of the 1X – and includes many new features. Originally, Wires-X was not supported at all on the DR-2X. This was stated many times by Yaesu. The FAQ indicates the 2X will support the HRI-200 (direct connect) OR IMRS (Internet Multi-site Repeater link) option. It will not support both. The IMRS option sounds a lot like DMR IP Site Connect where repeaters are linked over the Internet using Talk group-like functionality. There is another promotional program offering a trade-in path from a DR-1X to a DR-2X for $300 without the site linking option and $500 with site linking. See the Yahoo Group as I don’t see this promotion information anywhere else.

DSQ (Digital Squelch, squelch code) is replaced by DG-ID (digital group ID). DSQ has caused controversy even locally because it is a global setting in the radio, not per channel. This is a real pain if two repeaters in the area choose different DSQ codes. I left it disabled on LEARA’s allowing any Fusion user to use the repeater. A DG-ID use-case example on a repeater: use the repeater locally might be DG-ID 71. To use two IMRS sites might be DG-ID 90, and all sites DG-ID 99. A DP-ID is a priority override or used for remote control of the system on the 2X only.

Fusion up to this point seems rushed, untested, and like most companies today, driven by marketing. The mentality being: ‘get it out now, fix it later.’ I really hope Yaesu gets their act together soon if they want Fusion to survive. This will likely require drastic business and management changes within the company. As I see it, Fusion survival requires fixing its perception, fixing the software issues, producing better quality devices/radios including extensive testing, and showing commitment to the community and developers by releasing protocol specifications or open-sourcing the technology.

Reddit post: https://www.reddit.com/r/amateurradio/comments/6t8t5z/yaesu_system_fusion_ii/

Yahoo Group (membership requires approval): https://groups.yahoo.com/neo/groups/YaesuSystemFusion/info

Thanks for reading and 73… de Jeff – K8JTK