[aprssig] Alinco DR-135T - EJ41U internal modem

[Scott Miller]

Sounds like even for APRS it's not reliable in KISS mode.  And just because 
you're doing APRS doesn't mean you won't get more than one packet in the 
buffer before it gets to the client.  An OpenTracker can send up to 3 
packets back-to-back, if you have status, position, and telemetry enabled. 
Or it'll loop a test packet forever in diagnostic mode, but that's not a 
polite thing to do on 144.39.  =]

The interesting thing is that converse mode is sending more data to the 
serial port for each packet, since SSIDs are expanded and everything's 
printed in human-readable format.  If it's locking up in KISS mode but not 
converse mode, it's probably not just a buffer issue.

Scott, N1VG
http://n1vg.net/opentracker

----- Original Message ----- 
From: "Robert Bruninga" <bruninga at usna.edu>
To: <aprssig at lists.tapr.org>
Sent: Monday, October 31, 2005 9:09 AM
Subject: Re: [aprssig] Alinco DR-135T - EJ41U internal modem


> Looks like one should be skeptical of the EJ41U
>modem option in the DR-135T.

Just to keep this train on the track, there is NO
problem for using the DR-135 and its internal modem
for APRS (exactly what it was designed to do).
One packet at a time in UI mode.

What it was not designed to do was to be a full-
blown general purpose TNC able to support
bulk file transfer in connected mode requiring
multiple un-acknowledged outstanding packets at
a time and  operating in KISS mode.

So lets not jump on the bandwagon of condeming
a TNC that works perfectly for what it was designed
to do and which it has published it is designed to do
and then to condem it for not doing things it was not
designed to do and which they say it was not
designed to do.

Just a thought...

Bob




_______________________________________________
aprssig mailing list
aprssig at lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig