Skip to main content

HF portable antenna + looking for antenna analyser now

I've just got the HF portable antenna, the Buddistick that I ordered but I'm yet to try it out. My current QTH is surrounded by small hills and I guess its really restrict me from getting a good reception. I've tried it before with my dipole and what I could hear was only audio from the neighbour country, most probably no band opening on the time I did my monitoring?? Oh well, since I've the Yaesu FC-40, I should go for a long wire way I guess. I will try that later on .. my wife is going to Port Dickson and hopefully I can tag along and have a balcony facing the open sea. 

Anyway, I've received a not so good audio report lately when working out the usual repeater. There was lot of crackling noise together with my audio as what my friend said and usually I received them with load of crackling noise too. So, my base is out of commission right now, I've installed a temporary Slim-Jim antenna, just good for monitoring the VHF band at the moment. I'm really looking to invest on Antenna Analyzer now. I've put my eyes on the MFJ-259B. I was thinking of getting it from the UK, I'm going for a two week stint back at the main office in February but the price there is really killing me. I was quoted a £199 for the unit. Tried to order the unit from Universal Radio and get it shipped to my friend who is coming back in early Feb but I've just got an email saying that they're out of stock and it takes 2-3 weeks to get it shipped out. Guess the best thing to do is to cancel the order .. and my next try is to get it from R&L Electronics... hopefully they'll have it in stock and could manage to deliver it to my friend before he fly home.

Comments

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 svxlink.de 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:

http://www.o2help.co.uk/router-change-dns/

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.