Re: TT$ config for Pat ax25?
Sorry about not explicitly stating how the TT4 was being used.
I have been using it as a mobile TX/RX iGate and fill-in Digi when combined with APRX on a Pi W Zero.? Worked well.
For the current application all I want is the Kiss TNC to use with Pat Winlink client on 2m.? Ideally I would set bank 0 to my APRS duties, and bank 1 to use for occasional 2m packet/Winlink.
Do I need to initialize the Kiss TNC from my /etc/default/ax25 config?? Or is it all good to go once setup in TT4 config?
|
Re: TT$ config for Pat ax25?
Peter,
Could you amplify a bit on your application? For instance, if you are using the TT4 as a tracker, you must set PPeriod ( The rate at which it sends transmissions, default is zero) Generally, PPeriod is set at 120 (seconds) If you don't have a GPS plugged in that is generating a valid position report, it will not send a position report. You can disable the GPS validation by setting TOSV to FALSE, and it will send the default position somewhere around Madagascar I believe, otherwise, you need to manually enter your position.?
73,
Allen AF6OF
-----Original Message-----
From: Peter VE7PPE <ve7ppe@...>
To: [email protected]
Sent: Thu, Apr 1, 2021 5:45 pm
Subject: [TinyTrak] TT$ config for Pat ax25?
Anybody have a working set of configs for using a TT4 with Debian linux SBC?
Been working on this too long, when "everyone" says its plug and play. Reflashed V0.72 software, been through all the parameters a zillion times. Rechecked /etc/default/ax25 &/etc/ax25/axports.? Tried it on another laptop.
#1 issue right now is that I can't get the TT4 to transmit from my IC-2300H. When I calibrate the TT4, it turns the PTT on, but otherwise doesn't.? JP8 is open, though tried both settings. Does the TT4 Kiss TNC need to be given commands from /etc/default/ax.25 like Restore, On, etc?? I thought that everything is set in the configuration, but could be wrong.
I have ~40 years experience with computers, sysadmin/Ops, cli, AI, etc and find this very frustrating.? Got to be something simple.
Any help would be much appreciated.
|
Anybody have a working set of configs for using a TT4 with Debian linux SBC?
Been working on this too long, when "everyone" says its plug and play. Reflashed V0.72 software, been through all the parameters a zillion times. Rechecked /etc/default/ax25 &/etc/ax25/axports.? Tried it on another laptop.
#1 issue right now is that I can't get the TT4 to transmit from my IC-2300H. When I calibrate the TT4, it turns the PTT on, but otherwise doesn't.? JP8 is open, though tried both settings. Does the TT4 Kiss TNC need to be given commands from /etc/default/ax.25 like Restore, On, etc?? I thought that everything is set in the configuration, but could be wrong.
I have ~40 years experience with computers, sysadmin/Ops, cli, AI, etc and find this very frustrating.? Got to be something simple.
Any help would be much appreciated.
|
Re: Accidentally sent break to TT4 in bootloader - Borked?
Tried both sending file with minicom and using cat xxxx644.TT4 > /dev/ttyUSB0 as ??? poured out.? Using cat, the file seemed to upload, but TT4 remained borked.
Only thing that worked was Wine & the config.exe program
|
Re: Accidentally sent break to TT4 in bootloader - Borked?
Got my TT4 back via Wine & config software.? Only tricky part was finding the correct comm port.? It is located under ~/.wine/dosdevices.? Look for the ln to appropriate /dev/ttyUSBxx port
Now to see if it behaves any better with Pat to access 2m Winlink
Thanks for the guidance.
|
Re: Anyone using the display board - if so can you share your build and tell us how you use it in a vehicle?
HI,
I have a display but it shows only " TT4 Alpha v0.68 1284"
How can I see my GPS position?
Is there any manual for using this display?
73,
Corneliu YO4AUL
|
Re: Accidentally sent break to TT4 in bootloader - Borked?
The Config tool is a good bet.? I think it just looks for the ? and does the rest.
If that doesn't work, it looks like it the TT4 is looking for input.
Try just sending the file in minicom while the TT4 is sending question marks .
On Thursday, April 1, 2021, 3:59:31 PM EDT, Peter VE7PPE <ve7ppe@...> wrote:
Thanks for the tips.
Issue right now is that I can't even get into the bootloader via minicom.? Just keeps pouring out ??? with leds lit like a Christmas tree
Will try the "official" configuration utility under Wine and see if that helps to debork my TT4
|
Re: Accidentally sent break to TT4 in bootloader - Borked?
Thanks for the tips.
Issue right now is that I can't even get into the bootloader via minicom.? Just keeps pouring out ??? with leds lit like a Christmas tree
Will try the "official" configuration utility under Wine and see if that helps to debork my TT4
|
Re: Accidentally sent break to TT4 in bootloader - Borked?
I've used minicom in LInux and noticed that the data appears to be sent too fast.
I had similar issues with TeraTerm until I found that you can put in a "NewLine Delay".
I just checked and you can try this in minicom as well.? It is in Terminal Settings
? <Ctrl>A T D
In TeraTerm, the value of 1 worked well.? I have not tried this in minicom.
Also, If you have WINE installed, the configuration program will run in Wine.?
I think TeraTerm does as well.
All 3 are worth trying.
On Thursday, April 1, 2021, 3:17:29 PM EDT, Peter VE7PPE <ve7ppe@...> wrote:
My TT4 (V1.2b with 644 chip) has been behaving really weird lately.? Using Minicom in linux to reconfigure with 19200 8N1 no flow.
Once in config, it coughs up partial/truncated responses, locks up after a few lines of input, etc.
Decided best thing was to backup config and reflash the software to start fresh.? Went into bootloader, checked the version.? Then attempted to upload the 644.TT4 file.? In the process, I accidentally hit ctl-A F instead of S, which then cause both green & yellow leds to? stop flashing and stay on with a steady stream of ????? emanating from the Minicom terminal.
Unplugged power and repowered up, both leds light up and the ????? continue to pour out of the TT4.? Can't seem to access the bootloader to try and reload the software.
Please note that I do not have access to any Windows equipped computers, all Linux or FreeBSD
Any ideas or suggestions?
|
Accidentally sent break to TT4 in bootloader - Borked?
My TT4 (V1.2b with 644 chip) has been behaving really weird lately.? Using Minicom in linux to reconfigure with 19200 8N1 no flow.
Once in config, it coughs up partial/truncated responses, locks up after a few lines of input, etc.
Decided best thing was to backup config and reflash the software to start fresh.? Went into bootloader, checked the version.? Then attempted to upload the 644.TT4 file.? In the process, I accidentally hit ctl-A F instead of S, which then cause both green & yellow leds to? stop flashing and stay on with a steady stream of ????? emanating from the Minicom terminal.
Unplugged power and repowered up, both leds light up and the ????? continue to pour out of the TT4.? Can't seem to access the bootloader to try and reload the software.
Please note that I do not have access to any Windows equipped computers, all Linux or FreeBSD
Any ideas or suggestions?
|
I am moving this to the regular Groups.IO discussion because it is getting into questions that others may have as well. Everyone benefits!
First I'll answer you question: The? ALIAS# does not contain callsigns of people you want to DIGI.? It contains text that, when matched to path elements, will be DIGI'ed. As I read the manual and have read on the discussions, the TT4 can be used with things as simple as ALIAS1 WIDE and it will DIGI all packets following the WIDEn-N path elements.? That means if you use ALIAS1 as WIDE, then any packet heard by your TT4 will be DIGI'ed if they have the common WIDE1-1,WIDE2-1 path elements (not just your co-offroaders).
Because the algorithm is used 'in general', it will also respond to anyone using WIDE7-7 (or other high repeat rate). So I personally, prefer to limit the WIDEn-N parameters my TT4 responds to by specifying
? ALIAS1 WIDE1
? ALIAS2 WIDE2 This will still provide the DIGI action for normal users but won't encourage those with with high DIGI counts - it ignores them.
For your situation, I believe the recommendation is to setup your TT4 connected to the Kenwood as a fill-in DIGI:
?? ALIAS1 WIDE1
Encourage your fellow offroaders (and you) to use the normal path of WIDE1-1, WIDE2-1 (or WIDE2-2 if you need another hop) on their HTs. I believe that is the default for many HTs.
?? PATH1 WIDE1-1 ?? PATH2 WIDE2-1
BACKGROUND: In previous message exchanges, there was a concern about someone using Cliff's callsign for APRS.? Upon further investigation it appeared Cliff had PERIOD > 0 and so his TT4 was transmitting Telemetry packets.? Cliff didn't realize that?while in KISS mode communicating with an attached device, the TT4 could continue the other functions.
This led to the question on DIGI below.
On Thursday, April 1, 2021, 1:02:51 PM EDT, Cliff Hall <cliffdhall@...> wrote:
That is great. I didn't think I could use DIGI at the same time, but now that I know, I have friends that I offroad with that use cheap handhelds for their APRS in their trucks. So I could set DIGI mode and add their call signs as ALIAS# and TT4 would repeat them out over my higher power Kenwood, cool! For my own handheld on hikes could I add my call sign to an ALIAS#?? Or does APRSDroid sending that same call sign (different ssid) through preclude that, I don't want to create a flood of packets. I have to reread the TT4 manual cover to cover again, missed the concurrent operation when I set it up, must be 4 years ago.
Cliff
|
Re: Monitoring a TT4 digipeater's packet translation
Thanks for all the great information everyone. I'm going to absorb it then have a tinker.?
Regards Andrew, N1ACW --
When I want to monitor the output of a TT4/MTT4BT device, I am not just interested in how the TT4 is handling things, but rather, how the local infrastructure is dealing with the packets I generate. Because my own receiver can't always switch back from transmit to receive fast enough, I use a separate receiver connected to a soundcard modem. I Like Packet Engine Pro, and UZ7HO's packet decoder software. They are either cheap or free, which also appeals to me, but I would (And did)? happily purchase the full edition of Packet Engine Pro.
73,
Allen AF6OF
-----Original Message-----
From: Rob Giuliano via <kb8rco= [email protected]>
To: [email protected] < [email protected]>
Sent: Wed, Mar 31, 2021 4:44 pm
Subject: Re: [TinyTrak] Monitoring a TT4 digipeater's packet translation
First, uses its own password, not the APRS-IS passcode used for APRS clients.
Second, you should not recommend online passcode generators.
? The APRS-IS system? is very specific on the passcode - remember, if this is abused, we will lose the system we depend on!
?? clearly states:
passcode=computed passcode for your callsign. -1 is used for
receive-only. It is the responsibility of each software author
to provide the proper passcode to their individual users on a request basis. This is to aid in
keeping APRS-IS restricted to amateur radio use only.
While the algorithm to generate the passcode is available
from some open-source locations, I will not publish it here. If you are an
Amateur Radio operator writing software for APRS-IS, contact me directly for the
algorithm; otherwise, contact the software author for your passcode.
Keep in mind that is NOT really a good measure for determining your DIGI efforts.
gets its feeds from the APRS-IS system which only captures the FIRST received packet.
So you station could be DIGI'ing several packets, but those packets are also received by other station or directly into APRS-IS.? If so, they will not show any infomration about your station.?
I don't remember if Allen's method works.??the firmware manual for
?? PKTOCOM - Sets if generated packets should be sent to the computer TEXT, DEAFTEXT, and KISS ports.
but these aren't exactly "generated" packets, although the TT4 may alter the packet before sending it on.? I just don't remember if the TT4 passes ougoing DIGI through to the computer.
The sure way of checking is with another receiver (RTL dongle or scanner and a sound card would work) with just a simple terminal program to display the decoded packets.? Setup near to the TT4 with a decent antenna should show the raw incoming and outgoing packets, with the path so you can see if it matches your ALIAS.? Then pretty much the next entry should have a line for the TT4 DIGI output of that packet.?
On Wednesday, March 31, 2021, 5:12:53 PM EDT, Gil Smith < tinytrak@...> wrote:
Look up your callsign in , and look at raw packets?? Helped me fix some issues with my wx install as I fine-tuned some format errors.
You need to log in to see the raw, I believe.? Should get your password from official sources, but I have heard of callsign-to-password translators floating around or buried in the occasional source code repo.
----- Original message -----
Subject: [TinyTrak] Monitoring a TT4 digipeater's packet translation
Date: Wednesday, March 31, 2021 11:23 AM
Hello all,
Sorry for this dumb newbie question. I have set up my TT4 as a local WIDE1 fill-in digipeater. I'm curious what's being translated and digipeated, so I have the TT4 connected to a serial terminal. I see packets being received, of course.
I'm a curious person, and I'd really like to see what comes in in the raw and how it is going to be repeated, again in the raw with the APRS headers. Is there a way to monitor this?
Many thanks, and I apologise if this has been asked a thousand times. I couldn't find anything like this in the group.
Andrew, N1ACW
--
|
Re: Monitoring a TT4 digipeater's packet translation
I like the AGW products as well.? I find the most helpful product is
the AGWmonitor.? Being able to monitor the packets with AGWmonitor anywhere on the network and
getting a simple mheard list can be quite helpful in troubleshooting issues.
Personally, my favorite soundcard TNC is Direwolf.? WB2OSZ has a good product and excellent support. I really like his version for the Pi, but also his handling of the PTT within the CM108 and CM119 USB sound cards.? I worked with a few people on Direwolf's telemetry using perl and python scripts - very powerful!
Robert Giuliano KB8RCO
On Wednesday, March 31, 2021, 11:30:25 PM EDT, vhsproducts via groups.io <vhsproducts@...> wrote:
When I want to monitor the output of a TT4/MTT4BT device, I am not just interested in how the TT4 is handling things, but rather, how the local infrastructure is dealing with the packets I generate. Because my own receiver can't always switch back from transmit to receive fast enough, I use a separate receiver connected to a soundcard modem. I Like Packet Engine Pro, and UZ7HO's packet decoder software. They are either cheap or free, which also appeals to me, but I would (And did)? happily purchase the full edition of Packet Engine Pro.
73,
Allen AF6OF
-----Original Message-----
From: Rob Giuliano via groups.io <kb8rco@...>
To: [email protected] < [email protected]>
Sent: Wed, Mar 31, 2021 4:44 pm
Subject: Re: [TinyTrak] Monitoring a TT4 digipeater's packet translation
First, aprs.fi uses its own password, not the APRS-IS passcode used for APRS clients.
Second, you should not recommend online passcode generators.
? The APRS-IS system? is very specific on the passcode - remember, if this is abused, we will lose the system we depend on!
?? clearly states:
passcode=computed passcode for your callsign. -1 is used for
receive-only. It is the responsibility of each software author
to provide the proper passcode to their individual users on a request basis. This is to aid in
keeping APRS-IS restricted to amateur radio use only.
While the algorithm to generate the passcode is available
from some open-source locations, I will not publish it here. If you are an
Amateur Radio operator writing software for APRS-IS, contact me directly for the
algorithm; otherwise, contact the software author for your passcode.
Keep in mind that aprs.fi is NOT really a good measure for determining your DIGI efforts.
APRS.FI gets its feeds from the APRS-IS system which only captures the FIRST received packet.
So you station could be DIGI'ing several packets, but those packets are also received by other station or directly into APRS-IS.? If so, they will not show any infomration about your station.?
I don't remember if Allen's method works.??the firmware manual for
?? PKTOCOM - Sets if generated packets should be sent to the computer TEXT, DEAFTEXT, and KISS ports.
but these aren't exactly "generated" packets, although the TT4 may alter the packet before sending it on.? I just don't remember if the TT4 passes ougoing DIGI through to the computer.
The sure way of checking is with another receiver (RTL dongle or scanner and a sound card would work) with just a simple terminal program to display the decoded packets.? Setup near to the TT4 with a decent antenna should show the raw incoming and outgoing packets, with the path so you can see if it matches your ALIAS.? Then pretty much the next entry should have a line for the TT4 DIGI output of that packet.?
On Wednesday, March 31, 2021, 5:12:53 PM EDT, Gil Smith <tinytrak@...> wrote:
Look up your callsign in aprs.fi, and look at raw packets?? Helped me fix some issues with my wx install as I fine-tuned some format errors.
You need to log in to see the raw, I believe.? Should get your password from official sources, but I have heard of callsign-to-password translators floating around or buried in the occasional source code repo.
----- Original message -----
Subject: [TinyTrak] Monitoring a TT4 digipeater's packet translation
Date: Wednesday, March 31, 2021 11:23 AM
Hello all,
Sorry for this dumb newbie question. I have set up my TT4 as a local WIDE1 fill-in digipeater. I'm curious what's being translated and digipeated, so I have the TT4 connected to a serial terminal. I see packets being received, of course.
I'm a curious person, and I'd really like to see what comes in in the raw and how it is going to be repeated, again in the raw with the APRS headers. Is there a way to monitor this?
Many thanks, and I apologise if this has been asked a thousand times. I couldn't find anything like this in the group.
Andrew, N1ACW
--
|
Re: Monitoring a TT4 digipeater's packet translation
When I want to monitor the output of a TT4/MTT4BT device, I am not just interested in how the TT4 is handling things, but rather, how the local infrastructure is dealing with the packets I generate. Because my own receiver can't always switch back from transmit to receive fast enough, I use a separate receiver connected to a soundcard modem. I Like Packet Engine Pro, and UZ7HO's packet decoder software. They are either cheap or free, which also appeals to me, but I would (And did)? happily purchase the full edition of Packet Engine Pro.
73,
Allen AF6OF
-----Original Message-----
From: Rob Giuliano via groups.io <kb8rco@...>
To: [email protected] < [email protected]>
Sent: Wed, Mar 31, 2021 4:44 pm
Subject: Re: [TinyTrak] Monitoring a TT4 digipeater's packet translation
First, aprs.fi uses its own password, not the APRS-IS passcode used for APRS clients.
Second, you should not recommend online passcode generators.
? The APRS-IS system? is very specific on the passcode - remember, if this is abused, we will lose the system we depend on!
?? clearly states:
passcode=computed passcode for your callsign. -1 is used for
receive-only. It is the responsibility of each software author
to provide the proper passcode to their individual users on a request basis. This is to aid in
keeping APRS-IS restricted to amateur radio use only.
While the algorithm to generate the passcode is available
from some open-source locations, I will not publish it here. If you are an
Amateur Radio operator writing software for APRS-IS, contact me directly for the
algorithm; otherwise, contact the software author for your passcode.
Keep in mind that aprs.fi is NOT really a good measure for determining your DIGI efforts.
APRS.FI gets its feeds from the APRS-IS system which only captures the FIRST received packet.
So you station could be DIGI'ing several packets, but those packets are also received by other station or directly into APRS-IS.? If so, they will not show any infomration about your station.?
I don't remember if Allen's method works.??the firmware manual for
?? PKTOCOM - Sets if generated packets should be sent to the computer TEXT, DEAFTEXT, and KISS ports.
but these aren't exactly "generated" packets, although the TT4 may alter the packet before sending it on.? I just don't remember if the TT4 passes ougoing DIGI through to the computer.
The sure way of checking is with another receiver (RTL dongle or scanner and a sound card would work) with just a simple terminal program to display the decoded packets.? Setup near to the TT4 with a decent antenna should show the raw incoming and outgoing packets, with the path so you can see if it matches your ALIAS.? Then pretty much the next entry should have a line for the TT4 DIGI output of that packet.?
On Wednesday, March 31, 2021, 5:12:53 PM EDT, Gil Smith <tinytrak@...> wrote:
Look up your callsign in aprs.fi, and look at raw packets?? Helped me fix some issues with my wx install as I fine-tuned some format errors.
You need to log in to see the raw, I believe.? Should get your password from official sources, but I have heard of callsign-to-password translators floating around or buried in the occasional source code repo.
----- Original message -----
Subject: [TinyTrak] Monitoring a TT4 digipeater's packet translation
Date: Wednesday, March 31, 2021 11:23 AM
Hello all,
Sorry for this dumb newbie question. I have set up my TT4 as a local WIDE1 fill-in digipeater. I'm curious what's being translated and digipeated, so I have the TT4 connected to a serial terminal. I see packets being received, of course.
I'm a curious person, and I'd really like to see what comes in in the raw and how it is going to be repeated, again in the raw with the APRS headers. Is there a way to monitor this?
Many thanks, and I apologise if this has been asked a thousand times. I couldn't find anything like this in the group.
Andrew, N1ACW
--
|
Re: Monitoring a TT4 digipeater's packet translation
First, aprs.fi uses its own password, not the APRS-IS passcode used for APRS clients.
Second, you should not recommend online passcode generators. ? The APRS-IS system? is very specific on the passcode - remember, if this is abused, we will lose the system we depend on!
?? clearly states: passcode=computed passcode for your callsign. -1 is used for
receive-only. It is the responsibility of each software author
to provide the proper passcode to their individual users on a request basis. This is to aid in
keeping APRS-IS restricted to amateur radio use only.
While the algorithm to generate the passcode is available
from some open-source locations, I will not publish it here. If you are an
Amateur Radio operator writing software for APRS-IS, contact me directly for the
algorithm; otherwise, contact the software author for your passcode.
Keep in mind that aprs.fi is NOT really a good measure for determining your DIGI efforts. APRS.FI gets its feeds from the APRS-IS system which only captures the FIRST received packet. So you station could be DIGI'ing several packets, but those packets are also received by other station or directly into APRS-IS.? If so, they will not show any infomration about your station.?
I don't remember if Allen's method works.??the firmware manual for
?? PKTOCOM - Sets if generated packets should be sent to the computer TEXT, DEAFTEXT, and KISS ports.
but these aren't exactly "generated" packets, although the TT4 may alter the packet before sending it on.? I just don't remember if the TT4 passes ougoing DIGI through to the computer.
The sure way of checking is with another receiver (RTL dongle or scanner and a sound card would work) with just a simple terminal program to display the decoded packets.? Setup near to the TT4 with a decent antenna should show the raw incoming and outgoing packets, with the path so you can see if it matches your ALIAS.? Then pretty much the next entry should have a line for the TT4 DIGI output of that packet.?
On Wednesday, March 31, 2021, 5:12:53 PM EDT, Gil Smith <tinytrak@...> wrote:
Look up your callsign in aprs.fi, and look at raw packets?? Helped me fix some issues with my wx install as I fine-tuned some format errors.
You need to log in to see the raw, I believe.? Should get your password from official sources, but I have heard of callsign-to-password translators floating around or buried in the occasional source code repo.
----- Original message -----
Subject: [TinyTrak] Monitoring a TT4 digipeater's packet translation
Date: Wednesday, March 31, 2021 11:23 AM
Hello all,
Sorry for this dumb newbie question. I have set up my TT4 as a local WIDE1 fill-in digipeater. I'm curious what's being translated and digipeated, so I have the TT4 connected to a serial terminal. I see packets being received, of course.
I'm a curious person, and I'd really like to see what comes in in the raw and how it is going to be repeated, again in the raw with the APRS headers. Is there a way to monitor this?
Many thanks, and I apologise if this has been asked a thousand times. I couldn't find anything like this in the group.
Andrew, N1ACW
--
|
Re: Monitoring a TT4 digipeater's packet translation
Andrew,
Not a dumb question at all! In fact, I had to pour through the manuals to find what I believe to be the answer. Setting PKTOCOM to True should cause anything that the TT4 originates to be echoed out the serial port when the port is designated as TEXT, DEAFTEXT, or KISS. If I am wrong, you are entitled to a refund of the entire two cents that you paid for my opinion.
73,
Allen AF6OF
-----Original Message-----
From: Andrew Watson <aldcwatson@...>
To: [email protected]
Sent: Wed, Mar 31, 2021 11:23 am
Subject: [TinyTrak] Monitoring a TT4 digipeater's packet translation
Hello all,
Sorry for this dumb newbie question. I have set up my TT4 as a local WIDE1 fill-in digipeater. I'm curious what's being translated and digipeated, so I have the TT4 connected to a serial terminal. I see packets being received, of course.
I'm a curious person, and I'd really like to see what comes in in the raw and how it is going to be repeated, again in the raw with the APRS headers. Is there a way to monitor this?
Many thanks, and I apologise if this has been asked a thousand times. I couldn't find anything like this in the group.
Andrew, N1ACW
--
|
Re: Monitoring a TT4 digipeater's packet translation
Look up your callsign in aprs.fi, and look at raw packets?? Helped me fix some issues with my wx install as I fine-tuned some format errors.
You need to log in to see the raw, I believe.? Should get your password from official sources, but I have heard of callsign-to-password translators floating around or buried in the occasional source code repo.
----- Original message -----
Subject: [TinyTrak] Monitoring a TT4 digipeater's packet translation
Date: Wednesday, March 31, 2021 11:23 AM
Hello all,
Sorry for this dumb newbie question. I have set up my TT4 as a local WIDE1 fill-in digipeater. I'm curious what's being translated and digipeated, so I have the TT4 connected to a serial terminal. I see packets being received, of course.
I'm a curious person, and I'd really like to see what comes in in the raw and how it is going to be repeated, again in the raw with the APRS headers. Is there a way to monitor this?
Many thanks, and I apologise if this has been asked a thousand times. I couldn't find anything like this in the group.
Andrew, N1ACW
--
|
Monitoring a TT4 digipeater's packet translation
Hello all,
Sorry for this dumb newbie question. I have set up my TT4 as a local WIDE1 fill-in digipeater. I'm curious what's being translated and digipeated, so I have the TT4 connected to a serial terminal. I see packets being received, of course.
I'm a curious person, and I'd really like to see what comes in in the raw and how it is going to be repeated, again in the raw with the APRS headers. Is there a way to monitor this?
Many thanks, and I apologise if this has been asked a thousand times. I couldn't find anything like this in the group.
Andrew, N1ACW
--
|
I have only successfully used the TinyTrak4 for digipeater purposes. The very informed and knowledgeable folks in this group told me how to do it. I'd have to go back and look at my settings, but I think the 4 is the only one that does that. Obviously I could be wrong.
Lee Besing, N5NTG
210-771-7075
San Antonio TX
-----Original Message----- From: "David Marquez Rosado via groups.io" <kp4dmr@...> To: [email protected]Sent: Sun, 28 Mar 2021 7:58 PM Subject: [TinyTrak] TT3 plus digipeater Hello, greetings to everyone in the group, if anyone knows how to configure the Tinytrak3 plus for digipeater I can't do it, any help I would appreciate it .... 73 '
|
The TT3 has no receive capability so cznnot be used as a DIGI. A DIGI will receive a packet, determine if there are path elements unused, then repeat tgat packet. Key element us receiving.
On Sun, Mar 28, 2021 at 20:58, David Marquez Rosado via groups.io <kp4dmr@...> wrote: Hello, greetings to everyone in the group, if anyone knows how to configure the Tinytrak3 plus for digipeater I can't do it, any help I would appreciate it .... 73 '
|
Andrew Watson
Lee Besing