|
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
--
|
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
--
|
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
--
|
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
--
|
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
--
|
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
--
|
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
--
|
Andrew Watson