Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
TinyTrak4 TEXT Mode Incoming Messages
|
I'm trying to send and receive from TinyTrak4 in text mode.? It looks like I'm successfully sending messages and I can see them appear on??However, I have never seen an incoming message displayed to the terminal.?The carrier detect LED flashes when a message is present, but I've yet to see any decoded text.? Any suggestions as to what I might be doing wrong??
The basic configuration is as described in the quick start: AMODE TEXT ABAUD 19200 |
|
Assuming you have set the RXAMP properly and your TT4 is decoding packets, the settings you should be looking at are: PKTICOM [ true | false ]??? ????Sets if received packets should be sent to the computer TEXT, DEAFTEXT, and KISS ports. PKTOCOM [ true | false ]????? Sets if generated packets should be sent to the computer TEXT, DEAFTEXT, and KISS ports. Robert Giuliano
On Saturday, May 23, 2020, 5:22:17 PM EDT, Michael Sutton <mikesutton@...> wrote:
I'm trying to send and receive from TinyTrak4 in text mode.? It looks like I'm successfully sending messages and I can see them appear on??However, I have never seen an incoming message displayed to the terminal.?The carrier detect LED flashes when a message is present, but I've yet to see any decoded text.? Any suggestions as to what I might be doing wrong?? The basic configuration is as described in the quick start: AMODE TEXT ABAUD 19200 |
|
Depending upon how you have audio feeding the TT4, you will need to make a few adjustments. The yellow?CD light is more or less a carrier?detect indicator, and not an indicator that the TT4 is actually decoding packets. If you are feeding the TT4 audio from the audio out jack of a handheld, its coming out at around speaker level, and you should turn your volume down very low, perhaps?as low as your radio can be heard before you?override the built in speaker by plugging?in the connection cable You should set the CDMODE to TONES, and try the default value for RXAMP?( 12 as I recall) if you don't see any decoded signals, set RXAMP?down to 5 and work up from there. If you are getting the audio from a 6 pin mini DIN accessory?jack, it will be coming out at line lever, nominally 1 Volt, P/P. The default RXAMP?setting should work, but remember to set CDMODE to TONES. Audio?designed?to run a speaker mic is very high level audio, and the louder you have the volume control up, the more distortion will be present, so joggle your volume and RX values and you will see data, assuming that there is anything strong enough to decode. Just because you can hear traffic, it does not mean that the signal/noise level is sufficient to decode it.? 73, Allen AF6OF On Sat, May 23, 2020 at 2:38 PM Rob Giuliano via <kb8rco=[email protected]> wrote:
|
|
I made a bit of progress. I drove closer to a digipeater and was able to see some packets. When I send a message, I hear what sounds like an acknowledge message (I must admit, I don't know APRS protocol very well and not sure when/if I get an ACK).? Should I be able to see that ACK message (assuming that is what it is) on the TinyTrak output? Thanks for the quick replies! Mike AC0LX On Sat, May 23, 2020 at 4:05 PM Allen Lord <allen@...> wrote:
|
|
Mike,
If you are using a handheld radio with your TT4, it probably does not switch back to receive fast enough after a transmission for you to hear its own digipeated traffic. Portables are designed to transmit for a few ms after you let off the PTT switch ( i.e., stop holding down the PTT switch) so that the squelch circuits in everyone's radios are not continually making horrid noises. Good for voice, not so good for data.?
Some digipeaters after hearing your packet might have enough delay for your radio to "catch up" before forwarding your original packet. It is much more likely that your TT4 will catch the second "hop" of your packet, from the second digipeater in line, which will contain your original packet plus APRS formatting stuff.
73,
Allen AF6OF -----Original Message-----
From: Michael Sutton <mikesutton@...> To: [email protected] Group Moderators <[email protected]> Sent: Sat, May 23, 2020 3:38 pm Subject: Re: [TinyTrak] TinyTrak4 TEXT Mode Incoming Messages I made a bit of progress. I drove closer to a digipeater and was able to see some packets.
When I send a message, I hear what sounds like an acknowledge message (I must admit, I don't know APRS protocol very well and not sure when/if I get an ACK).? Should I be able to see that ACK message (assuming that is what it is) on the TinyTrak output?
Thanks for the quick replies!
Mike
AC0LX
On Sat, May 23, 2020 at 4:05 PM Allen Lord <allen@...> wrote:
|
|
You need to be very specific when using the word "message".? In APRS context that is a special format for the APRS Message protocol" and the term "message" should not be used to describe the other 95% of APRS packets or position or status packets. Once you clarify that, then maybe our answers will be more clear.On Sat, May 23, 2020 at 5:22 PM Michael Sutton <mikesutton@...> wrote: I'm trying to send and receive from TinyTrak4 in text mode.? It looks like I'm successfully sending messages and I can see them appear on??However, I have never seen an incoming message displayed to the terminal.?The carrier detect LED flashes when a message is present, but I've yet to see any decoded text.? Any suggestions as to what I might be doing wrong?? |
|
Good question! I guess I don't know!? I wonder what packets?TinyTrak4 prints when in TEXT mode?? Maybe only a limited type? I think I will try and find a TNC program and experiment with that.? On Sat, May 23, 2020 at 8:42 PM Robert Bruninga <bruninga@...> wrote:
|
|
The question was directed at your question.? Your original post says: I'm trying to send and receive from TinyTrak4 in text mode.? It looks like I'm successfully sending messages and I can see them appear on??However, I have never seen an incoming message displayed to the terminal.?The carrier detect LED flashes when a message is present, but I've yet to see any decoded text.? Any suggestions as to what I might be doing wrong? I believe Bob's point (not quoted here) was referencing types of packets as opposed to a general term of "messages": ?? What type of message are you sending that is "successful"? ?? What types of messages are you expecting to see? Allen and I posted earlier specific to decoding with the TT4: 1. Specifically, I guess the most direct question would be:? Do you know you are decoding packets? ??? Of are you assuming decode because a LED flashes? ??? a) Did you set the decode parameters using MONITOR and changing RXAMP? ??????? reference: TinyTrak4 Quick Start Guide v0.7.pdf ??? b) Allen commented about using an HT and some settings. ? ? ? ? CDMODE TONES? 2. Did you verify the settings for ??? a) PKTICOM TRUE??? ??? to see received packets on the computer TEXT, DEAFTEXT, and KISS ports. ??? b) PKTOCOM TRUE ???? to see generated packets on the computer TEXT, DEAFTEXT, and KISS ports.
The setting in 2b is more for ensuring the TT4 is transmitting and what it is sending. WIth 2a set to true, everything the TT4 receives and can decode should be sent to an attached computer. You success in decoding packets makes me believe you do not have the TT4 decode settings "refined" The manual: TinyTrak4 Quick Start Guide v0.7.pdf describes how to set audio levels for decoding packets. Remember, the quoted numbers are with packets data being received, not just open squelch noise. Robert Giuliano
On Saturday, May 23, 2020, 6:39:14 PM EDT, Michael Sutton <mikesutton@...> wrote:
I made a bit of progress. I drove closer to a digipeater and was able to see some packets. When I send a message, I hear what sounds like an acknowledge message (I must admit, I don't know APRS protocol very well and not sure when/if I get an ACK).? Should I be able to see that ACK message (assuming that is what it is) on the TinyTrak output? Thanks for the quick replies! Mike AC0LX On Sat, May 23, 2020 at 4:05 PM Allen Lord <allen@...> wrote:
|
Using AMODE TEXT and having set transmit levels, I can type something in the terminal, see it transmitted through the HT and then show up on .? Here's an example of what I see on that website.?? 2020-05-23 14:40:38 MDT:?>APTT4,WIDE1-1,WIDE2-1,qAR,:hello?[Unsupported packet format] ?
Initially, I could hear other packets (on a 2nd HT) and the carrier LED blink, but I was not seeing any incoming packets.? However, I have since seen a few packets show up in the terminal from closer stations.? So maybe the issue is just SNR or the receive settings aren't tuned enough as you point out below.? I can also hear what I think are ACK packets, that I was expecting to see; however, someone else responded that maybe the timing of the?HT xmit is preventing this. Also, I'm not sure if the TinyTrak displays these types of packets in TEXT mode.
Yes, I have now seen a handful of decoded packets.? However, most of what I hear (on a 2nd HT since I can't hear the one connected to TinyTrak4) are NOT decoded.
Yes, be it sounds like this is probably worth refining a little bit to see if this improves performance.?
Yes. This setting is confirmed.?
Yes, both of these are confirmed.? However, I don't see the text that I type show up in the console, which is what I would expect based on PKTOCOM setting.
I think you are correct.? I'm tempted to believe that I'm just not receiving a strong enough signal.? I ordered an SMA adapter to try a higher gain antenna as well. My TinyTrak4 is pretty old and I was able to update the firmware to 0.72. Thank you all for your assistance! Mike AC0LX |
|
-----Original Message----- To translate this into "APRS speak" I would have said this: "When I send a PACKET, I hear what sounds like THE DIGIPEATER DIGIPEATING? IT (acks do not exist in APRS except for one case)..." "Should I be able to see the DIGIPEATED packet on the TinyTrack output?" To which allen correctly responded that many radios do not turn around fast enough from TX to RX to hear the immediate first digipeat.? The turn around time of a digi is a function of that particular digi.? If you think it is probabllysorking (you hear a packet digipeated immediately but do not display it, then that is likely what is going on and you can drive to another digi and see if you get the same result. bob |
to navigate to use esc to dismiss