Skip to main content

Getting your WX station out to RF using weewx + aprx

I have been using my WH1080 since two years ago and it is still working great until few days ago when I found out that the anemometer doesn't seem to give any reading anymore. Anyway, other than that, everything still working just fine.

I have been experimenting with Raspberry Pi for quite sometime and I've moved my WX and aprx along with few local server apps into Raspberry Pi (previously on my router running OpenWRT). Anyway, for this post, I'm going to guide you on how to get the WX data into RF without a need of the Internet connection after the first setup.

What needed?

1. Raspberry Pi, I'm using raspbian. I'm not going in details on how to set it up. By now you should've been able to get this up and running.
2. weewx software, more information can be found in Installation guide can be found here:
3. A weewx extension that I've adopted from cwxn extension so it could produce an aprx ready beacon file can be found here: weewx2aprx-0.1.tgz
4. Aprx package which can be found here (prepackaged):

After you've got everything installed, the weewx and aprx package. You can install the weewx2aprx extension, to do this, just use the following command:

wee_extension --install weewx2aprx-0.1.tgz

You need to edit the /etc/weewx/weewx.conf. Toward the end of the configuration file, there is a new section created by the above extension installer. Edit as required, the necessary fields are the lat, lon and the note.

# Options for extension 'aprx'
    lat = 0312.81N
    note = "WH1080+weewx+aprx Sg Buloh, Malaysia"
    symbol = /_
    lon = 10133.17E
    filename = /var/tmp/aprx_wx.txt 
Change the above to suite your preference and rerun the weewx's service by issuing the following commands:

$ sudo /etc/init.d/weewx stop 
$ sudo /etc/init.d/weewx start 

Edit your /etc/aprx.conf file and add the following information under the beacon, change the callsign as necessary :

        beaconmode radio
        beacon srccall 9M2TPT-13 \                                             
              via WIDE1-1,WIDE2-2 \                                            
              file /var/tmp/aprx_wx.txt

 That should be it.


Anonymous said…

It works like an absolute charm. At last a solution that works well. Thank you so much for this.


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.