Skip to main content

Happy new year..

Probably a belated one, 2011 is already on the 9th day today. Nothing much interesting happening I guess since last October since I didn't post anything. Anyway, listed are the latest things (happening or in my hands :).

  • I've bought a Kenwood TM-D710A, replacing my TM-V71A/OT2/Nuvi350 setup in my pickup. 
  • TM-V71A is now my main 2m/70cm radio in my shack, I wasn't able to monitor or transmit on 2m/70cm bands for quite a while. I had the FT60R connected to the only base antenna that I've installed and it was connected to a TT4/APRS and acted as fill-in digipeater and TNC interface to my igate. The shack setup is now has TM-V71A, band B as data and band A is free for me to monitor any local conversation on the repeaters or simplex channels while not missing any data coming into the other band.
  • FT-60R is now temporarily retired until I can find a new task for it. Few of us were talking about satellites communication, probably now the right time to go forward with it. Found lot of hams are using FT-60R for it. Now, the raw materials are readily available.. need to find the 'urge' to start working on it :)
  • In the CarPC world, I've 'upgraded' my CarPC setup, it is running on solid state drive (SSD) now, after I had a harddrive failure, I believe upgrading to SSD is necessary. I'm trying to migrate the frontend from Centrafuse to RideRunner since RR has nicer support for my HDR (HD Radio).
  • Work-wise, I'm still stuck doing SAP development. But then again, I'm not going to venture out doing something else. I will eat, sleep, walk & program .. ABAP :) Office is busy doing an upgrade exercise, they're going to upgrade both the CRM & R/3 to the latest packages and I believe I'll be the last in the chain as usual :) Nothing unusual though .. 


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.