<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD>
<BODY
style="WORD-WRAP: break-word; khtml-nbsp-mode: space; khtml-line-break: after-white-space">
<DIV dir=ltr align=left><SPAN class=953425021-30122005><FONT face=Arial
color=#0000ff size=2>Not all USB/serial problems are Windows-specific. The
problem I have with the OpenTracker and USB is that devices using bulk endpoints
have absolutely no latency guarantees. Even if your converter properly
carries all signals to and from the serial device, things can still get really
screwy in the time domain. You have to remember that USB is a host-driven,
polled interface. Even if the device has data to send, it can't do
anything except wait for an IN token from the host.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=953425021-30122005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=953425021-30122005><FONT face=Arial
color=#0000ff size=2>Scott</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=953425021-30122005><FONT face=Arial
color=#0000ff size=2>N1VG</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> aprssig-bounces@lists.tapr.org
[mailto:aprssig-bounces@lists.tapr.org] <B>On Behalf Of </B>Jason
Winningham<BR><B>Sent:</B> Friday, December 30, 2005 12:09 PM<BR><B>To:</B>
TAPR APRS Mailing List<BR><B>Subject:</B> Re: [aprssig] RE: MacAPRS +
D7a<BR></FONT><BR></DIV>
<DIV></DIV><BR>
<DIV>
<DIV>On Dec 30, 2005, at 12:54 PM, KC2MMi wrote:</DIV><BR
class=Apple-interchange-newline>
<BLOCKQUOTE type="cite">
<P style="MARGIN: 0px">
<BLOCKQUOTE type="cite">
<P style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica" face=Helvetica
size=3>Been trying to get my new D7 working with my new
Powerbook.</FONT></P>
<P style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica" face=Helvetica
size=3>I am using a</FONT></P>
<P style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica" face=Helvetica
size=3>USB->Serial converter that shows up as /dev/tty.usbserial0
.</FONT></P></BLOCKQUOTE>
<P></P>
<P style="MIN-HEIGHT: 14px; MARGIN: 0px; FONT: 12px Helvetica"><BR></P>
<P style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica" face=Helvetica
size=3>I'd MOST STRONGLY suggest that first you try using the radio with a
Wintel PC</FONT></P>
<P style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica" face=Helvetica
size=3>(sorry) that has a real hardware serial port on it. In the Wintel
world we see a</FONT></P>
<P style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica" face=Helvetica
size=3>lot of problems caused by USB/Serial adapters that simply don't work
100%</FONT></P>
<P style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica" face=Helvetica
size=3>properly. The fastest way to make sure that your cable & radio
configuration are</FONT></P>
<P style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica" face=Helvetica
size=3>correct, is to try them on a machine that has a real serial port so
that is</FONT></P>
<P style="MARGIN: 0px"><FONT style="FONT: 12px Helvetica" face=Helvetica
size=3>simply not an issue.</FONT></P></BLOCKQUOTE></DIV><BR>
<DIV><BR class=khtml-block-placeholder></DIV>
<DIV>These usb/serial problems are largely confined to wintel boxes. If he
were trying to get it to work on a windoze box your suggestion has much merit,
but he isn't.</DIV>
<DIV><BR class=khtml-block-placeholder></DIV>
<DIV>If the device has Mac OS X drivers, it's probably gonna work. I'm going
to go out on a limb and guess he's got a Keyspan device (because of the device
special file name), in which case he's in good shape. I rate a Mac with a
Keyspan serial adapter as being just as good as a wintel box with a hardware
serial port.</DIV>
<DIV><BR class=khtml-block-placeholder></DIV>
<DIV>If you happen to have a computer with a real hardware serial port handy,
fine, go test with it, but I wouldn't go to a whole lot of trouble to get one,
especially if you haven't checked these things yet:</DIV>
<DIV><BR class=khtml-block-placeholder></DIV>
<BLOCKQUOTE type="cite">
<DIV style="MARGIN: 0px">Other problems: Plain defective cables, even from
Kenwood. Or pins2/3 cross</DIV>
<DIV style="MARGIN: 0px">wired, triple check the pin outs and cables if they
are home wired. Then swap</DIV>
<DIV style="MARGIN: 0px">pins 2/3 and try again anyway, the diagrams and
nomenclature are often unclear.</DIV></BLOCKQUOTE><BR>
<DIV>Yep, check all these things at least twice.</DIV>
<DIV><BR class=khtml-block-placeholder></DIV>
<DIV>It would be terribly convenient if there was another ham in your
neighborhood with a working cable you could borrow for a few minutes.</DIV>
<DIV><BR class=khtml-block-placeholder></DIV>
<DIV>-Jason</DIV>
<DIV>kg4wsv</DIV>
<DIV><BR class=khtml-block-placeholder></DIV></BLOCKQUOTE></BODY></HTML>