Differences

This shows you the differences between two versions of the page.

--- info:misc:aprs_telemetry_info_dec_2009 [2009/12/14 11:52] – tomgee
+++ info:misc:aprs_telemetry_info_dec_2009 [2009/12/21 21:56] (current) – tomgee
@@ Line 20: / Line 20: @@
    {
 	static char count;
 	if (value > 999) value = 999;
 	count = 0;
+        // first get the MSD (hundreds)
 	while (value >= 100)
 	{
@@ Line 30: / Line 29: @@
 	}
 	ax25sendByte(count + 48);
+        // now, get the middle digit, the tens
 	count = 0;
 	while (value >= 10)
@@ Line 38: / Line 37: @@
 	}
 	ax25sendByte(count + 48);
+        // what's left is the units
 	ax25sendByte(value + 48);
 	return;
    }
+===== TT4 Text Mode =====
+Yes, you can think of TEXT mode as like KISS mode, but where the TT4
+handles all the AX.25 UI wrapping.  In TEXT sending, you just pass in
+the data you want sent, an the TT4 handles all the formatting with
+callsigns you pre-set.
+The goal with TEXT mode was to make it look like a normal TNC in
+converse/monitor mode.  So when you send packets in TEXT mode, you
+just pass in the string to send, terminated with a carriage return,
+like this:
+>Hello
+When you receive packets in text mode, they look like a monitored packet:
+N6ABC>APRS,WIDE1-1:>Hello
+Byon
+On Sat, Dec 12, 2009 at 10:32 AM, tomgle <tomgle@...> wrote:
+> I've been trying to find info about the Text mode while I wait for a TT4 to
+arrive. I understand KISS mode requires protocol formatting with call sign,
+framing etc and TEXT mode does not. Does this imply that TEXT mode is really a
+KISS frame where all the protocol wrapping is done under the covers? This
+therefore may mean that you don't have to worry about callsign ID since it's
+picking up the callsign info from the TT4 stored variables?  I read a lot of
+back messages and also the manual but have not come up with an answer. Of course
+if I had real hardware I would just try it and see what comes out of the device
+but in the meantime I'm trying to read as much as I can.