https://lms.onnocenter.or.id/wiki/index.php?action=history&feed=atom&title=AX.25%3A_TinyTrack4_Digipeater 2026-04-20T07:08:46Z Revision history for this page on the wiki MediaWiki 1.45.1 https://lms.onnocenter.or.id/wiki/index.php?title=AX.25:_TinyTrack4_Digipeater&diff=38753&oldid=prev 2013-11-16T10:45:49Z

<p>New page: 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...</p> <p><b>New page</b></p><div> TinyTrak4 as fill-in digipeater<br /> 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 &quot;Bermuda&quot; area of Sg Buloh to the digipeater-to-be somewhere at Genting. Since I&#039;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.<br /> <br /> 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&#039;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.<br /> <br /> 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:<br /> <br /> 300 is FALSE<br /> TXTDISP is FALSE<br /> NODISP is FALSE<br /> PPATHING is FALSE<br /> DMSDISP is FALSE<br /> MICETMV is FALSE<br /> ENTS is FALSE<br /> TELHIRES is FALSE<br /> TELVOLT is TRUE<br /> TELTEMP is TRUE<br /> PREEMPT is FALSE<br /> DIGIID is TRUE<br /> TOSV is FALSE<br /> TALT is TRUE<br /> TIMESTAMP is TRUE<br /> TIMEHMS is TRUE<br /> SBEN is FALSE<br /> TSWPT is TRUE<br /> AMODE is TEXT<br /> BMODE is TEXT<br /> ABAUD is 19200<br /> BBAUD is 4800<br /> SSIDROUTE is 0<br /> ALTNET is APTT4<br /> MYCALL is 9W2TPT-4<br /> DIGI1 is WIDE1-1<br /> DIGI2 is WIDE2-1<br /> DIGI3 is<br /> PPATH1ST is<br /> PPATH2ND is<br /> TSTATUS is Digipeater SgBuloh<br /> BTEXT is &gt;Digipeater SgBuloh<br /> BPERIOD is 900<br /> TXD is 60<br /> PERSIST is 65<br /> SLOTTIME is 15<br /> QUIET is 10<br /> CDMODE is TONES<br /> CDLEVEL is 12<br /> TXLEVEL is 128<br /> TXTWIST is 50<br /> RXAMP is 13<br /> GWAYLEN is 9<br /> GWAYMODE is NMEA<br /> LOCATION is 0312.8666N 10133.4500E<br /> GALT is 1000<br /> TSYMCODE is #<br /> TSYMTABLE is S<br /> STATUSRATE is 1<br /> PPERIOD is 600<br /> SBSSPEED is 5<br /> SBFSPEED is 60<br /> SBSPERIOD is 1800<br /> SBFPERIOD is 90<br /> SBTANGLE is 27<br /> SBTSLOPE is 255<br /> SBTTIME is 5<br /> MICEMESSAGE is 0<br /> TSOFFSET is 17<br /> TDAO is 0<br /> TPROTOCOL is APRS<br /> TPERIOD is 1200<br /> ALIAS1 is WIDE1-1<br /> ALIAS2 is<br /> ALIAS3 is<br /> DUPETIME is 30<br /> FILTERCALL is<br /> <br /> Update: aprs.fi doesn&#039;t like the beacon text w/o &#039;&gt;&#039;, so, added it manually to the beacon text line.. don&#039;t see this with Tracker2 though.<br /> <br /> Update 2: According to Byon, the only required parameter to enable the digipeater is the ALIAS1. The rest are just supporting parameters.<br /> <br /> ==Referensi==<br /> <br /> * http://9m2tpt.blogspot.com/2009/05/tinytrak4-as-fill-in-digipeater.html</div>

Onnowpurbo