Skip to main content

TinyTrak4 as fill-in digipeater

I was thinking, why do I need to power on my PC when someone already gated the packets out to the net. What I want to do is to escalate/repeat packets sent by APRS stations from "Bermuda" area of Sg Buloh to the digipeater-to-be somewhere at Genting. Since I've Argendata Tracker2 already, I was thinking, why not try the Byonic TinyTrack4 and have it run in standalone mode and acts as a digipeater. So, ordered mine through 9W2PD (bulk order) and received it early of the week.

The hardest part for me is to set the TT4 to recognise incoming packets. When I received the TT4, I could not get it to recognise any packet, so put off by it .. I didn't touch it for few days (+ the busy days debugging BSP/ABAP Object/middleware and stuff related to work that it). To get it working with my FT-60R HT, I need to set the SQL all the way counterclock wise (off), set the volume to 25%, RXAMP and CDCODE and CDLEVEL as the configuration shown below.

My configuration is: Tinytrack4 + Yaesu FT-60R, configuration as I put into the software (Alpha 0.51 firmware), the important fields to get the digipeater working are in bold:

300 is FALSE
TXTDISP is FALSE
NODISP is FALSE
PPATHING is FALSE
DMSDISP is FALSE
MICETMV is FALSE
ENTS is FALSE
TELHIRES is FALSE
TELVOLT is TRUE
TELTEMP is TRUE
PREEMPT is FALSE
DIGIID is TRUE
TOSV is FALSE
TALT is TRUE
TIMESTAMP is TRUE
TIMEHMS is TRUE
SBEN is FALSE
TSWPT is TRUE
AMODE is TEXT
BMODE is TEXT
ABAUD is 19200
BBAUD is 4800
SSIDROUTE is 0
ALTNET is APTT4
MYCALL is 9W2TPT-4
DIGI1 is WIDE1-1
DIGI2 is WIDE2-1
DIGI3 is
PPATH1ST is
PPATH2ND is
TSTATUS is Digipeater SgBuloh
BTEXT is >Digipeater SgBuloh
BPERIOD is 900
TXD is 60
PERSIST is 65
SLOTTIME is 15
QUIET is 10
CDMODE is TONES
CDLEVEL is 12
TXLEVEL is 128
TXTWIST is 50
RXAMP is 13
GWAYLEN is 9
GWAYMODE is NMEA
LOCATION is 0312.8666N 10133.4500E
GALT is 1000
TSYMCODE is #
TSYMTABLE is S
STATUSRATE is 1
PPERIOD is 600
SBSSPEED is 5
SBFSPEED is 60
SBSPERIOD is 1800
SBFPERIOD is 90
SBTANGLE is 27
SBTSLOPE is 255
SBTTIME is 5
MICEMESSAGE is 0
TSOFFSET is 17
TDAO is 0
TPROTOCOL is APRS
TPERIOD is 1200
ALIAS1 is WIDE1-1
ALIAS2 is
ALIAS3 is
DUPETIME is 30
FILTERCALL is

Update: aprs.fi doesn't like the beacon text w/o '>', so, added it manually to the beacon text line.. don't see this with Tracker2 though.

Update 2: According to Byon, the only required parameter to enable the digipeater is the ALIAS1. The rest are just supporting parameters.

Comments

renato said…
Hy,
I'm professor at Federal Fluminense University in Niteroi City near 15Km of Rio de Janeiro City. Ou group's researchers will install the Igate and two digipeaters for weather monitoring. Last year we observed the tragedy in the Bumba comunity where people dyed. In the moment I coordenate the group of entusiasts andresearchers for initial struture for APRS weather monitoring. I have tree TT4, one complete station of university but the configuration of TT4 for Igate is the real problem. It's possible to help-me? Thanks and sorry for may english.
PU1RGS
Renato Barcellos
pu1rgs@gmail.com
renato@vm.uff.br
EDUARDO said…
Hi,
I have a tt4, firmware v.0.6 and i need to configuration of tt4 Digipeater. Dou you have the file "settings.txt" ? Tank you for attention. My e-mail is adcas@br.inter.net.
Respectfully,

Eduardo- PU2YYP
EDUARDO said…
Hy, I have the TT4, and i need configuration to tt4 in DigiPeater. Dou you have the file "settings.txt" ?
Tank´s for attention,
Respectfully,

Eduardo PU2YYP

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.