Skip to main content

9M4GPT - Yaesu Wires-X + Fusion System, and DV4 Mini too

Over the past few days last week, I spent some of my time setting up my Wires-X. Thanks to 9M2FRI/PA3FRI (OM Martin) who brought the HRI-200 from Netherlands. To prepare the Wires-X, I've bought myself an FTM100DR to be the gateway radio, FT2DR, a handheld so I could test it easily. I've my FTM400DR for quite sometime and that is my main radio in one of my car.

My current gateway setup, FTM100DR + HRI-200.

As of now, my Wires-X node is set to be in an analog mode. Reason being, there is no digital DR1X repeater available locally right now and the HRI-200 couldn't be set to do AMS AUTO.

The Wires-X running on my Windows 10 PC. Look for MY-9M4GPT node 14060 or Room MY-KL-9M4GPT. Someone will probably waiting for you to make a contact from all over the world.

I did my very first test in C4FM across the continent with VK4GO (OM Art from Australia) this morning. For some reason, the voice coming in from the internet to RF was quite soft when it was on analog. I need to take another look at how this Wires-X being setup. The quality in C4FM was excellent and this is my first real QSO in digital mode. I am looking forward to have a digital repeater and Wires-X set up in KL. I have no idea when this can be materialised but hopefully soon.

BTW. I have ordered a DV4 Mini last week and am currently waiting for it to arrive. Ordered mine from Wireless Holdings LLC in US since I couldn't get hold of one from their main distributor in Germany. The dongle seems to be like a hot cake, snapped in no time when they've them in stock. I will probably using my newly arrived Raspi2 along with the dongle for the hotspot setup. It will probably running on DMR, just need to wait for my DMR radio to be ordered of the Internet.


Popular posts from this blog

Raspberry Pi + svxlink = Low power echolink node

What is the easiest way to get echolink node up and running on raspberry pi? Surely, get a premade image which has everything inside. I've created one image which can fit into 2GB SD card for this, just follow the following steps to get it up and running:

For hardware, you need to have the following:
Raspberry Pi for sure, with a minimum 4GB SD cardA USB echolink interface, can be commercially sourced or DIY. There are many DIY schematics out there that you could follow.  Here is the configuration on how to get the things working together, courtesy of website:

For software:
Download the following prepared image from google drive, it is based on raspbian-2015-02-16 image and has pre-installed svxlink-14.08. raspi-wheezy-svxlink.img.zipUnzip the file and copy it to your SD card using the following instructions that can be found here.Boot up the RasPi, if you do not have an HDMI monitor, you may want to access the RasPi from your terminal emulator (putty or the like), connec…

Configuring TechniColor TG784N V3 (Maxis issued broadband router) to use different DNS servers

Previous write up deleted. It seems to change the DNS servers in as shown on the status, but it does not really work.

Check the following website, this seems to work:

This can be done from the WEB GUI too, go into the following configuration path:

In my example above, I'm using paid service unblock-us instead of google public DNS servers.

Debugging DMEE

I've come across many posting on the Internet (via google search), people asking on how to debug a DMEE for payment program. One of the few suggestion was to create a user exit just before the node that we would like to debug and put our breakpoint there. It seems that SAP has built-in this feature without needing us to create a user exit (available in ECC 6, have no idea if this is available on prior releases). Here is how you can put your breakpoint without any coding.

1. Display your DMEE tree using transaction: DMEE_DEBUG.

2. Click on the node that you would like to debug.
3. Go to conditions tab, you could see the Set Breakpoint button. Click to set.

4. Run the SAPFPAYM and specified the payment run date/id, payment format etc. SAP will stop at the node which you point your breakpoint at, as in 2.
5. To remove your breakpoint, just run the DMEE_DEBUG again, there is an option to delete all own breakpoints or all.