[YaesuSystemFusion] What does the HRI-200 actually do ?

I'm trying to work out what the HRI-200 is actually doing.

Fusion radios already contain a CPU, audio ADC/DAC's, a C4FM modem, AMBE+2 vocoder, a DSP (operating as the C4FM mode and vocoder) and a serial communications port for direct connection to a PC.

I could understand having a unit like the HRI-200 IF it had a network port on it that allowed it to act as a stand alone bridge between the radio and the Yaesu internet based network system. But no, a constantly connected and running PC is requi
red to act as the internet-interface/bridge/radio-controller etc, which of caused can already be plugged directly into the Fusion radio without the need of a seperate box (the HRI-200).

So what actually is the HRI-200's role in all this, what is it actually doing that the Fusion radio and PC alone couldn't already do as a pair ?

[YaesuSystemFusion] Constant WiRES-X Node Lockups [FIX]

This issue has been happening since the v1.10 WiRES-X software release; however, it has become increasing worse, even with the latest v1.11 release.

Today alone the node has locked up a 1/2 dozen times or so, while using the FTM-400DR as a link radio pointed at the repeater and connected to the "AMERICA-LINK" room.  We've now turned it off...

The lockup holds the FTM-400DR in constant transmit with no audio, no call sign data, and the hardware time out timer isn't shutting down the radio either, which keeps this hung transmitter open well past the allowed 3 minutes per FCC rules.  This morning, the transmitter was hung open for 1 hour the first time, 45 minutes the second time, and so on...  The radio, even-though it's only 5-watts is getting hot and I fear the finals will surely be burned up as these radios are not designed for this kind of work; even with that stupid fan accessories Yaesu want's to sell us.

Yaesu, if you are "TRULY" listening, we know this issue has been reported on numerous occasions, we even emailed you directly with the details you requested.  This issue MUST be fixed A.S.A.P.  If it's not going to be fixed in the next few weeks, then I fear this is the end of Yaesu System Fusion for us, as we are NOT going to continue pumping money into Yaesu test bed.

Respectfully, we request an immediate resolution to the hung transmitter issue, at the very least, a watchdog timer should be making sure the radio isn't hung in TX past the allowed 3 minutes

[YaesuSystemFusion] HRI-200 Schematic

HRI-200 Schematic

Looking for a schematic diagram for the HRI-200 to verify signal names
and pinouts of the rear panel connectors.

I've been searching the 'net but have come up empty so far.

YAESU Fusion WIRES-X HRI-200

YAESU Fusion WIRES-X HRI-200 connected

HRI-200 connected

YAESU Fusion WIRES-X HRI-200 connected

YAESU Ham Radio University 2016

Ham Radio University 2016

Pretty good video on digital modes.  In beginning Yaesu give good talk on Fusion and the products.

[YaesuSystemFusion] Re: Wires-X to Linux

First of all, Yaesu will never produce a Linux version of WiRES-X. I don't think we want them to. I suspect we'd rather add features and fix bugs rather than giving us a different version of a capability we already have. Personally, I want to see the API for the WiRES-X software. When we can't that we can have plenty of fun!

The existing WiRES-X software will never run on a Raspberry Pi or anything that doesn't use an x86 style CPU. The code is compiled for Intel, so it will never run on ARM.

I disagree with your assumptions here.  Code can be written using multi-platform toolkits that effectively makes the application natively available for Windows, Mac, Linux, etc.  How difficult this is to support depends on what the original language software was written in.  Btw.. there is ZERO reason why Yaesu couldn't cross compile their existing code to say ARM and run it on say a Rpi2 running Windows10 IoT (this MS OS exists today).  I don't know if an Rpi2 has the system resources to support Wires-X's needs (is Wires-X written to use SMP to distribute it's CPU needs vs. being single threaded) but there *are* options here.

I have heard rumors that it's possible to get the WiRES-X code on Linux running under Codeweaver. Code weaver provides .NET and Win32 support. It's paid software, but that means you get professional support and it's constantly being updated to make more Windows software run on it right out of the box.

(If you're invested, get the 14-day trial. Wait. Don't buy it. Wait longer. You will eventually start getting discounted offers.)

It would seem like a good "open source" project to port WiRES-X under Codeweaver. I for one would rather run it in a Linux (Ubuntu) environment. No Windows license needed. And with WinX on the horizon, I'm now thinking I like the idea of Windows even less.

If it was written in .NET or C#, there is a chance this will work under Wine (open source direct relative of CodeWeaver) or even natively under Linux since MS has open sourced their .NET code.  It's unclear to me if the Mono community is going to absorb this code or if some new project will emerge to support it but I think this was a smart move by MS though very very late.

Yaesu Wires-X and FTM-100 DR Setup

This is a quick video to show some of the confusion I had when setting up my Yaesu wires X node to my radio, and how to set it up properly. Hope it helps some of you out there!
Wires node: 21606

[WIRES-X] Getting WiRES-X to work with analog and digital

I'm probably mistaken, but I thought that the new HRI-200 firmware / WiRES-X software updates would allow me to use analog AND digital when connected to an FTM-100/400. I have updated my HRI-200's firmware and the WiRES-X software without a problem... all seems to be working well. I have the HRI-200 connected to my FTM-100DR and set it to my DR-1X's frequencies, but I still can only get it to work in analog OR digital... not AUTO.

To do Auto-Auto it seems you need 1.10D on the repeater. Have not fully tested that yet and 1.10D is only aval on shipped repeaters currently

Repeater settings in Wires X 1.10 with 1.10D Repeater Firmware.

Reading the docs, there should be a 400 firmware greater than version 2.10 coming out.

In reading the pdf and seeing the screenshot, it appears that a direct cable connection between the HRI-200 and the DR-1X does in fact, enable digital operation.

[WIRES-X] Firmware update for DR-1X

A firmware update for the DR-1X Repeater. This latest firmware contains the following features, which many System Fusion repeater operators will appreciate and find useful.

• Adjustable Squelch Hysteresis

• Adjustable Squelch Tail

• CWID/Voice announcements with stripped PL Tones

  This latest firmware (MAIN Ver. 1.00m/ DSP Ver. 4.11) and the installation instruction manual are available at our website link:
  DR-1X/DR-1XE Update Software (MAIN Ver. 1.00m/ DSP Ver. 4.11) 12/25/15

  The features are usable immediately after the updated firmware is installed. If you need any assistance with the firmware update procedure, please contact our Technical Support Department. We will be pleased to assist you. 

[WIRES-X] Repeater software for C4FM wires-x linking

Is there any information about the release schedule? At the moment only analog wires linking is working with the dr1-x repeater. And the repeater does not announce the connection even though everything else works very well.

Depending on who you talk to (or read), yes and no.

I've been waiting for direct digital repeater support via direct connection for over a year and a half since it was an announced feature.  It has simply been re-announced over and over with the most recent being documentation only holding up the feature to be out in November, then on December 1st.  Of 2015 BTW, never mind 2014.

Now with V1.00d being shipped in repeaters now, it may or may not be beyond WishWare, promiseWare or VaporWare.  Don't know.  But if documentation was the reason not to put it up on the web, then how can they no ship it in the latest repeaters.  It sounds simply to be a hollow excuse to me.

But it surely has been a disappointment in the way it has been handled, Japan's secrecy on this and the repeater PA detonations, the mobile PA's/relay failure and more.  On the upside, the cost of the repeaters are low (for another week anyway), the Fusion implementation is great and the user radios are reasonably mid-range priced for the APRS, dual receive, the digital support and the folks in Commerce CA who have really tried to bridge the gap between Japan and it's USA customers.  I'm sure they are privately disgusted with Japan's intransigence to the wishes of the their USA market.

The efforts on the DV4mini side as well as other gateway projects will likely eclipse the "need" for WIRES-X and their very closed implementation, Japan only based server, and poor handling of feature requests.  While I have 2 WIRES-X boxes, I don't use them and see little improvement in how Japan will handle a better implementation for the USA.  WIRES-X is likely to falter the same as WIRES-II and WIRES before it, at least here in the USA.  If Japan were to release/allow/enable USA based WIRES-X servers, then the latency and stodgy admin issues would go away and drive more of use to truly embrace WIRES-X.

But for all my moaning, I'm solidly behind Fusion owning 2 repeaters, 2 HTs and 3 400's and a couple of HRI-200's, one still on the network as a simplex node idling for a year.

Yaesu Wires X

Overview of the Yaesu Fusion Wires X setup, using the Wires X HRI 200 interface between my computer and the radio. Connecting via the internet to the Wires server, whereby individual nodes connect to each others or can check in into Chat Rooms whereby multiple nodes can be connected. In this instance, I connect to the America Room and have a pleasant qso. Enjoy the video.

Help with wires x and FT991

This is indeed interesting as i had the ft991 and the HRI 200 and only wished to access Wires-x for personal use but was advised i needed to buy either an ftm 100 or ftm 400 to act as a node station. 

I opted for the 400 but really would like that in the car. 

I have registered with yaesu but am i allocated a frequency for the node or do i just assign one in the hri 200 settings and then input that frequency into the 991 menu as a manual input?