Skip to main content

Standalone digipeater & igate? I like the idea!!!

While browsing product availability at argendata website, I came across a daughterboard design for ot+ and wrt54gl. Hey, that could be an interesting mini project that I could take.. I've wrt54gl laying around collecting dust, it was supposedly my backup & working as WDS client for my home office but it doesn't work reliably .. so it was replaced by a Buffalo WHR-G125 instead.

I don't have an OT+, but I've TinyTrack4 that is connected to a PC running UI-VIEW32. Following the K6DBG website below, I could try to connect the TT4 via serial port.

Linksys built few WRT54G series of wireless routers with additional 10-pin header which we could use. This header gives a two TTL input/output ports. In order to convert this TTL signal, I need a MAX232 chip...

I will start this little project within this few days and see if I can get it anywhere.. now I can spare the old DELL PC that I bought to run UIVEW + sound card based interface for other usage ..

The guide to add serial ports to the router could be found here:

Update 1: The internal .. RS232 interface ready ..

Update 2: I couldn't fit TT4 inside the casing .. added one DB9 to the front/face of the wrt54gl. There is one that should go to the side but will add it later on.

Update 3: Software wise, I've loaded OpenWRT/X-WRT Kamikaze (with disabled GUI interface) and APRS4R .. I need to configure it though.. that'll be the hard part I guess.

Update 4: Finally, it is up and running, some more photos to share:

Update 5: There seems to be a problem with the router running out of memory or something else, after running for a day, it just stuck there.. and not igate-ing any packets. Need to look into the log and see what happened.

Update 6: Solved this by having a cron job which kills the aprs4r process in every four hours.


Mohd Zahri said…

I am planning to make either the Asus or Linksys Igate Project as well.


de 9W2DYE
Anonymous said…
Is your setup still active?
Let me know
va3ita (at) rac (.d.o.t.) ca

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.