Re: iGATE Functioning?
|
James Ewen
Oops, sent too soon. Basic understanding of the construction of APRS packets is useful... The APRS101.pdf will help you with this. http://www.aprs.org/doc/APRS101.PDF 2020-08-18 17:17:00 EDT: KD4APP-5>APWW11,TCPIP*,qAC,T2KA:<IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>) Timestamp the APRS-IS heard the packet 2020-08-18 17:17:00 EDT: Source callsign (station sending the packet) Destination (TOCALL) used by APRS to identify the source station software in this case, APRSISCE/32 APWW11, Handled by a network connection TCPIP*, q construct (http://www.aprs-is.net/q.aspx) sent to the APRS-IS directly by a verified connection qAC, APRS-IS server that handled the packet. T2KA: Actual packet contents finally! This is determined by Lynn's software. I'm going way out on a limb here expanding the term... <IGATE,MSG_CNT=10,LOC_CNT=0,DIR_CNT=0,RF_CNT=0,DX=7*N4NE-2(45mi@196<0xb0>) IGATE is reporting information. <IGATE, Message Count MSG_CNT=10, Location Count LOC_CNT=0 Heard Direct Count DIR_CNT=0 Heard via RF Count
RF_CNT=0
Furthest station heard DX=7*N4NE-2(45mi@196<0xb0>) DX = shortened term for distance commonly used by amateur radio operators. 7* (number of time heard?) N4NE-2 (callsign of the station heard, including SSID. 45mi distance to station in miles. 196° bearing to station. The <0xb0> is the degree symbol that is being shown as a non-printable ascii hex code. So no, your station is not sending packets to N4NEQ-2 via RF (at least not as indicated by this packet.) James VE6SRV On Tue, Aug 18, 2020 at 4:31 PM James Ewen <ve6srv@...> wrote:
|
|
|