¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Turning off telemetry channels with MTT4B?


 

I am using a MTT4B as a fill-in digi, NOLEN. It sends the telemetry channels, even though they are not in use, and I haven't found the appropriate setting to turn them off. A minor use of bandwidth, but I would like to clean this up. The NODISP turns the lines on and off for the display, but does not have any effect on the transmission.


 

If you are referring to BText messages that include temperature and voltage, you must remove the ^T and/or ^V portion of the BTEXT.

The NODISP comment in the manual has nothing to do with Telemetry, OTHER THAN the display uses the digital input lines that are reported.
? ?If NODISP is TRUE and the digital states will depend on the display usage of those pins.? You cannot connect anything external to that header.

Regular Telemetry reports are sent at TPERIOD intervals.
? ?A setting of Zero will disable telemetry reports.??
? ?This should be your FIX

-------
Robert Giuliano
KB8RCO


 

I almost forgot, TSTAT is another way of appending telemetry to position reports, again with ^{input} (like ^T and ^V).
You must remove the ^T and/or ^V portion of the TSTAT.

-------
Robert Giuliano
KB8RCO


 

Thanks, but those are already turned off. This is the packet which is being sent:

2023-08-17 09:38:53 CDT: NOLEN>APTT4,W1ARN-1*,K4UAN-3*,WIDE2*,qAR,KQ4BUD-10:T#006,110,105,089,085,084,00000011

Attached is a capture of how it turns up on APRS.FI


 

If you post the MTT4 config, it would help.
Why are some packets on aprs.fi showing:
???? 2023-08-17 14:34:23 EDT: >APTT4,WIDE2-2,qAR,:!3556.54N108643.72W#PHG2547/EM65?de?WA4SCA
?? type: location
???format: uncompressed
???srccallsign: NOLEN
???dstcallsign: APTT4
???latitude: 35.942333333333 ¡ã
???longitude: -86.728666666667 ¡ã
???symboltable: 1
???symbolcode: #
???messaging: 0
???posresolution: 18.52 m
???posambiguity: 0
???comment: EM65?de?WA4SCA
???phg: 2547


While others show:
????? 2023-08-17 14:37:43 EDT: >3UUV5T,WIDE2-2,qAR,:'rGdl?<0x1c>#1'"6o}MTT4B?-=Last?Chance?Digi=-|4

?? type: location
???format: mice
???srccallsign: NOLEN
???dstcallsign: 3UUV5T
???latitude: 35.942333333333 ¡ã
???longitude: -86.728666666667 ¡ã
???course: 0 ¡ã
???speed: 0 km/h
???altitude: 270 m
???symboltable: 1
???symbolcode: #
???mbits: 011
???posresolution: 18.52 m
???posambiguity: 0
???comment: 'MTT4B?-=Last?Chance?Digi=-|4


Are you switching between 2 banks?? Or are there 2 devices running with the same CALLSIGN and SSID=0?
In one case, the packet is sent as text (uncompressed), and the second case, it is sent in Mic-E format

Robert Giuliano
KB8RCO



On Thursday, August 17, 2023 at 01:14:25 PM EDT, Alan WA4SCA <apbiddle@...> wrote:


Thanks, but those are already turned off.? This is the packet which is being sent:

2023-08-17 09:38:53 CDT: NOLEN>APTT4,W1ARN-1*,K4UAN-3*,WIDE2*,qAR,KQ4BUD-10:T#006,110,105,089,085,084,00000011

Attached is a capture of how it turns up on APRS.FI









 

One device, one bank.

BANK is 0
P300 is FALSE
TXTDISP is FALSE
NODISP is FALSE
PPATHING is FALSE
DMSDISP is FALSE
MICETMV is TRUE
ENTS is FALSE
TELHIRES is FALSE
TELVOLT is FALSE
TELTEMP is FALSE
PREEMPT is FALSE
DIGIID is TRUE
WXPOS is FALSE
TELREAD is FALSE
FRAWDISP is FALSE
HRAWDISP is FALSE
WYPTXT is FALSE
PKTICOM is TRUE
PKTOCOM is FALSE
RPATHDISP is FALSE
LEDS is TRUE
PAVPEN is FALSE
DEC96 is FALSE
DDIST is FALSE
HEADERLN is FALSE
DMETRIC is FALSE
SOFTRST is FALSE
MSGCMD is FALSE
MSGCAP is FALSE
LRNTPS is FALSE
GPSCHK is FALSE
INTCLK is FALSE
DECSTAT is FALSE
DIGIMY is FALSE
HIPWR is FALSE
TOSV is FALSE
TALT is TRUE
TSPEED is FALSE
TIMESTAMP is TRUE
TIMEHMS is TRUE
SBEN is FALSE
TSWPT is FALSE
AMODE is TEXT
BMODE is GPS
ABAUD is 19200
BBAUD is 4800
BNKMODE is 0
SSIDROUTE is 0
ALTNET is APTT4
MYCALL is NOLEN
PATH1 is WIDE2-2
PATH2 is
PATH3 is
TSTAT is MTT4B -=Last Chance Digi=-
BTEXT is !3556.54N108643.72W#PHG2547/EM65 de WA4SCA
BPERIOD is 595
TXD is 40
MTXD is 10
PERSIST is 65
SLOTTIME is 65
QUIET is 10
TRNKMODE is 0
CDMODE is TONES
CDLEVEL is 15
TXLEVEL is 128
TXTWIST is 50
RXAMP is 5
GWAYLEN is 9
GWAYMODE is NMEA
GRELAYBITS is 1
GRELAYRATE is 0
GKRELAY is 0
LOCATION is 3556.5400N 08643.7200W
GALT is 270
TSYMCODE is #
TSYMTABLE is 1
STATUSRATE is 1
PPERIOD is 1800
MPPERIOD is 0
SBSSPEED is 5
SBFSPEED is 60
SBSPERIOD is 1800
SBFPERIOD is 90
SBTANGLE is 27
SBTSLOPE is 255
SBTTIME is 5
MMSG is 4
TSOFFSET is 17
TDAO is 0
TPROTOCOL is MIC-E
TPSWITCH is 0
TPERIOD is 1800
TVOLTTWK is 128
TTEMPTWK is 128
WPERIOD is 0
ALIAS1 is WIDE1
ALIAS2 is WIDE2
ALIAS3 is
DUPETIME is 20
FILTERCALL is
TXFREQ is 144.390
RXFREQ is 144.390
RXSQUELCH is 0
RXMODE is 2


 

So the TSAT (TSTAT is MTT4B -=Last Chance Digi=-) is the message that is in Mic-E format.? Must be due to MICETMV is TRUE.
It always send the telemetry data right after the Mic-E packet.

But the reason you are transmitting telemetry is this setting:
???? TPERIOD is 1800

TPERIOD [ seconds ]

?

Sets the time in seconds between transmissions of a telemetry report. A setting of 0 will disable telemetry reports. The analog voltages sent in order are JP5, JP4, JP3, JP2, JP1. If TELVOLT and/or TELTEMP is true, those will be sent first, followed by JP5, and the rest, up to a total of 5

-------
Robert Giuliano
KB8RCO


 

Robert,

Thanks for the help, and the clear explanation. I am embarrassed I missed that. ;)

TNK es 73s,

Alan
WA4SCA