All of lore.kernel.org
 help / color / mirror / Atom feed
* Trouble connecting to KPC3P-8.3-HM$
@ 2007-02-09 22:02 don
  2007-02-10 16:47 ` don
  0 siblings, 1 reply; 5+ messages in thread
From: don @ 2007-02-09 22:02 UTC (permalink / raw)
  To: linux-hams

Hi.  I am new to this (sort of).  I have a new SignaLink sound card
modem and a laptop running Ubuntu.  I can talk to our local node a
little, but it seems to stop responding.  I wonder if my system is
doing something wrong.

There are logs attached from sessions, here is what happened:

I changed my ID to just "KE7JVS", the program still adds "-0" to that.
I also modified the code very slightly so the log data all goes to a
syslog file (changed 2 printfs into logprintf).

When I connected today, it took the "L" command and also "R 16" and
showed me the header and message contents.

When I tried to send a message (to "N8GFO"), it prompted for a subject,
but then didn't take any contents.  I gave up and disconnected.

The second time I connected, after trying the "Help" command, I tried
again to send.  This time I waited longer, and there was a prompt
for the message. 

	I first sent the subject at 13:12:55
	It didn't prompt for the message until 13:14:13, 78 sec later.

Then I sent a few lines of message.  It looks like the BBS never took
most of them.  If I red things right, it may have taken packet #6.
After about 12 min. I disconnected.

The 2 attached files are from these two accesses.

Yes I've been in contact with the Ctrl. Op.  I also asked him to send a
message to the BBS while I leave my setup running and logging.

73
Don KE7JVS

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Trouble connecting to KPC3P-8.3-HM$
  2007-02-09 22:02 Trouble connecting to KPC3P-8.3-HM$ don
@ 2007-02-10 16:47 ` don
  2007-02-10 21:39   ` bud Thompson
  0 siblings, 1 reply; 5+ messages in thread
From: don @ 2007-02-10 16:47 UTC (permalink / raw)
  To: linux-hams

The Ctrl. Op. figured it out by listening to my signal.  The default
soundmodem.conf has txdelay=150 (ms).  Apparently this is too short at
least for local systems.  Increasing it to 500 fixed things nicely.

He said you should be able to hear a distinct start up part of the
transmission "buzzzzzzzsqwak".  

-- 
Don

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Trouble connecting to KPC3P-8.3-HM$
  2007-02-10 16:47 ` don
@ 2007-02-10 21:39   ` bud Thompson
  2007-02-12 19:39     ` don
  0 siblings, 1 reply; 5+ messages in thread
From: bud Thompson @ 2007-02-10 21:39 UTC (permalink / raw)
  To: don; +Cc: linux-hams

Don - On 1200b VHF packet 500ms is quite long for a TXD.  When used with a 
firmware-based TNC such as a KPC3 such long TXD values are only required by 
the oldest of old radios with coil/armature relays for change-over from 
TX/RX on one end or the other of the link.

If the two radios on the link are more modern with solid state change over 
(or even more modern fast-switching relays - such as reeds, etc.) then 500ms 
TXD is wasting a lot of channel time in terms of optimization.

Keeping in mind that I've had zero experience with sound card packet -

If the radios on the link are modern - no T/R relays, etc, - then the need 
for such a long TXD may be a function of the sound card interface, or the 
relationship between the sound card packet program and the processor speed - 
The "buzzzzzzzsqwak" is the "diddle" (alternating 1s and 0s) being sent 
prior to data being sent so that (1) the TX can come up to full power, and 
(2) the receiver end can be changed from TX to RX and the link get 
synchronized.)

At 1200b with modern radios and firmware-based TNCs a TXD > 250ms is seldom 
required.  TXD of 200-250 is often realized where S/N is good.

73,

bud N0IA



----- Original Message ----- 
From: "don" <don_reid@comcast.net>
To: <linux-hams@vger.kernel.org>
Sent: Saturday, February 10, 2007 11:47
Subject: Re: Trouble connecting to KPC3P-8.3-HM$


> The Ctrl. Op. figured it out by listening to my signal.  The default
> soundmodem.conf has txdelay=150 (ms).  Apparently this is too short at
> least for local systems.  Increasing it to 500 fixed things nicely.
>
> He said you should be able to hear a distinct start up part of the
> transmission "buzzzzzzzsqwak".
>
> -- 
> Don
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Trouble connecting to KPC3P-8.3-HM$
  2007-02-10 21:39   ` bud Thompson
@ 2007-02-12 19:39     ` don
  0 siblings, 0 replies; 5+ messages in thread
From: don @ 2007-02-12 19:39 UTC (permalink / raw)
  To: bud Thompson; +Cc: linux-hams

Thanks for the info.

On Sat, Feb 10, 2007 at 04:39:51PM -0500, bud Thompson wrote:
> Don - On 1200b VHF packet 500ms is quite long for a TXD.  When used with a 
> firmware-based TNC such as a KPC3 such long TXD values are only required by 
> the oldest of old radios with coil/armature relays for change-over from 
> TX/RX on one end or the other of the link.

The radios on both ends are quite new.

> At 1200b with modern radios and firmware-based TNCs a TXD > 250ms is seldom 
> required.  TXD of 200-250 is often realized where S/N is good.

250 seems to work mostly but a few packets don't get seen.  300 is as
good as 500 was.

I'll double check on what equipment is on the other end.

-- 
Don

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re:  Trouble connecting to KPC3P-8.3-HM$
@ 2007-02-09 22:08 don
  0 siblings, 0 replies; 5+ messages in thread
From: don @ 2007-02-09 22:08 UTC (permalink / raw)
  To: linux-hams

[-- Attachment #1: Type: text/plain, Size: 36 bytes --]

Sorry, I forgot to attach the logs.

[-- Attachment #2: log1 --]
[-- Type: text/plain, Size: 3078 bytes --]

Feb  9 13:06:49 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 SABM+  
Feb  9 13:06:51 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 UA-  
Feb  9 13:06:52 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I00^ pid=F0 [KPC3P-8.3-HM$] 99823 BYTES AVAILABLE THERE ARE 2 MESSAGES NUMBERED 16-17 ENTER COMMAND:  B,J,K,L,R,S, or Help >  
Feb  9 13:06:55 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR1v  
Feb  9 13:06:56 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR0+  
Feb  9 13:06:56 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR1-  
Feb  9 13:07:09 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I10^ pid=F0 L  
Feb  9 13:07:12 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I11^ pid=F0 MSG#  ST SIZE  TO     FROM   DATE               SUBJECT 16    B  79    GSRMC  N8GFO  01/29/2007 18:56:34  test message for gsrmc  
Feb  9 13:07:12 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I12^ pid=F0  cat bull ENTER COMMAND:  B,J,K,L,R,S, or Help >  
Feb  9 13:07:15 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR3v  
Feb  9 13:07:17 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR1+  
Feb  9 13:07:17 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR3-  
Feb  9 13:07:19 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I31^ pid=F0 r 16  
Feb  9 13:07:23 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I23^ pid=F0 MSG#16 01/29/2007 18:56:34 FROM N8GFO TO GSRMC SUBJECT: test message for gsrmc cat bull PATH: K7CVO testing a message bulletin   
Feb  9 13:07:23 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I24^ pid=F0 for how to read me. ENTER COMMAND:  B,J,K,L,R,S, or Help >  
Feb  9 13:07:26 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5v  
Feb  9 13:07:38 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I52^ pid=F0 s N8GFO  
Feb  9 13:07:42 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I35^ pid=F0 99798 BYTES AVAILABLE SUBJECT:   
Feb  9 13:07:45 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR6v  
Feb  9 13:07:48 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR3+  
Feb  9 13:07:48 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR6-  
Feb  9 13:07:51 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I63^ pid=F0 Test responce, it works  
Feb  9 13:08:00 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I64+ pid=F0 .  
Feb  9 13:08:00 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR6+  
Feb  9 13:08:18 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR6+  
Feb  9 13:08:45 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR6+  
Feb  9 13:09:22 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR6+  
Feb  9 13:10:07 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR6+  
Feb  9 13:10:26 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 DISC+  
Feb  9 13:10:35 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 DISC+  
Feb  9 13:10:36 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 UA-  

[-- Attachment #3: log2 --]
[-- Type: text/plain, Size: 14764 bytes --]

Feb  9 13:10:59 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 SABM+  
Feb  9 13:11:09 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 SABM+  
Feb  9 13:11:29 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 SABM+  
Feb  9 13:11:30 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 UA-  
Feb  9 13:11:31 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I00^ pid=F0 [KPC3P-8.3-HM$] 99823 BYTES AVAILABLE THERE ARE 2 MESSAGES NUMBERED 16-17 ENTER COMMAND:  B,J,K,L,R,S, or Help >  
Feb  9 13:11:34 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR1v  
Feb  9 13:11:39 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I10^ pid=F0 L  
Feb  9 13:11:49 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR1+  
Feb  9 13:11:52 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR0-  
Feb  9 13:11:52 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I10^ pid=F0 L  
Feb  9 13:11:56 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I11^ pid=F0 MSG#  ST SIZE  TO     FROM   DATE               SUBJECT 16    B  79    GSRMC  N8GFO  01/29/2007 18:56:34  test message for gsrmc  
Feb  9 13:11:56 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I12^ pid=F0  cat bull ENTER COMMAND:  B,J,K,L,R,S, or Help >  
Feb  9 13:11:59 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR3v  
Feb  9 13:12:02 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR3+  
Feb  9 13:12:04 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR1-  
Feb  9 13:12:07 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I31^ pid=F0 Help  
Feb  9 13:12:11 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I23^ pid=F0 B(ye)         PBBS WILL DISCONNECT J(heard)      CALLSIGNS WITH DAYSTAMP J S(hort)     HEARD CALLSIGNS ONLY J L(ong)      CALLSI  
Feb  9 13:12:12 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I24^ pid=F0 GNS WITH DAYSTAMP AND VIAS L [x [y]] [;] LIST MESSAGES x THRU y YOU CAN READ L <|> call    LIST MESSAGES FROM OR TO CALL LB       
Feb  9 13:12:12 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I25^ pid=F0        LIST BULLETINS LC [cat]      LIST CA  
Feb  9 13:12:14 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR6v  
Feb  9 13:12:16 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I26^ pid=F0 TEGORIES LL n          LIST LAST n MESSAGES LM(ine)       LIST UNREAD MESSAGES ADDRESSED TO YOU LO [+|-]      LISTING ORDER LT    
Feb  9 13:12:17 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I27^ pid=F0           LIST TRAFFIC LTn           DISPLAY LOCATION TEXT n=1-4 K(ill) n      DELETE MESSAGE NUMBER n KM(ine)       DELETE ALL   
Feb  9 13:12:18 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I20^ pid=F0 READ MESSAGES ADDRESSED TO YOU R(ead) n      
Feb  9 13:12:19 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR1v  
Feb  9 13:12:23 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I21^ pid=F0   DISPLAY MESSAGE NUMBER n RH n          DISPLAY MESSAGE n WITH HEADERS RM(ine)       READ ALL MESSAGES ADDRESSED TO YOU S(end)   
Feb  9 13:12:24 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I22^ pid=F0 call   SEND MESSAGE TO callsign S[B|P|T] call SEND BULLETIN, PRIVATE, or TRAFFIC ENTER COMMAND:  B,J,K,L,R,S, or Help >  
Feb  9 13:12:26 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR3v  
Feb  9 13:12:40 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I32^ pid=F0 S N8GFO  
Feb  9 13:12:44 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I33^ pid=F0 99798 BYTES AVAILABLE SUBJECT:   
Feb  9 13:12:47 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR4v  
Feb  9 13:12:49 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR3+  
Feb  9 13:12:49 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR4-  
Feb  9 13:12:54 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR3+  
Feb  9 13:12:54 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR4-  
Feb  9 13:12:55 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I43^ pid=F0 Reply to test message  
Feb  9 13:13:04 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR4+  
Feb  9 13:13:23 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR4+  
Feb  9 13:13:27 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR3-  
Feb  9 13:13:27 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I43^ pid=F0 Reply to test message  
Feb  9 13:13:36 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR4+  
Feb  9 13:13:38 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR3-  
Feb  9 13:13:38 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I43^ pid=F0 Reply to test message  
Feb  9 13:13:48 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR4+  
Feb  9 13:13:49 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR3-  
Feb  9 13:13:49 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I43^ pid=F0 Reply to test message  
Feb  9 13:13:58 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR4+  
Feb  9 13:14:00 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR3-  
Feb  9 13:14:00 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I43^ pid=F0 Reply to test message  
Feb  9 13:14:09 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR4+  
Feb  9 13:14:10 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR3-  
Feb  9 13:14:10 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I43^ pid=F0 Reply to test message  
Feb  9 13:14:13 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 I44^ pid=F0 ENTER MESSAGE 19--END WITH CTRL-Z OR /EX ON A SINGLE LINE  
Feb  9 13:14:16 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5v  
Feb  9 13:14:17 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR4+  
Feb  9 13:14:17 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5-  
Feb  9 13:14:20 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:14:21 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR4-  
Feb  9 13:14:23 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR4+  
Feb  9 13:14:23 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5-  
Feb  9 13:14:27 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR4+  
Feb  9 13:14:27 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5-  
Feb  9 13:14:39 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I54^ pid=F0 This is to show I can send messsages too.  
Feb  9 13:14:41 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR5-  
Feb  9 13:14:51 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I55^ pid=F0 It sure takes a long time after the subject.  
Feb  9 13:15:00 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:15:01 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I56+ pid=F0 Is the BBS doing something?  
Feb  9 13:15:17 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:15:19 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR5-  
Feb  9 13:15:19 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I55^ pid=F0 It sure takes a long time after the subject.  
Feb  9 13:15:19 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I56+ pid=F0 Is the BBS doing something?  
Feb  9 13:15:21 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 REJ5-  
Feb  9 13:15:21 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I55^ pid=F0 It sure takes a long time after the subject.  
Feb  9 13:15:22 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I56+ pid=F0 Is the BBS doing something?  
Feb  9 13:15:30 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:15:48 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:16:15 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:16:19 localhost soundmodem[16220]: Rx: fm K7CVO-0 to ID-0 UI  pid=F0 K7CVO/R K7CVO-1/B  
Feb  9 13:16:50 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:17:35 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:18:07 localhost soundmodem[16220]: Rx: fm K7CVO-0 to BEACON-0 UI  pid=F0 Benton Co. ARES, Corvallis, mbox is -1  
Feb  9 13:18:28 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:19:31 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:20:20 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR5+  
Feb  9 13:20:20 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5-  
Feb  9 13:20:26 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR5+  
Feb  9 13:20:26 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5-  
Feb  9 13:20:42 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:20:45 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR5-  
Feb  9 13:20:45 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I55^ pid=F0 It sure takes a long time after the subject.  
Feb  9 13:20:45 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I56+ pid=F0 Is the BBS doing something?  
Feb  9 13:20:54 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:20:56 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR5-  
Feb  9 13:20:56 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I55^ pid=F0 It sure takes a long time after the subject.  
Feb  9 13:20:57 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I56+ pid=F0 Is the BBS doing something?  
Feb  9 13:21:05 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:21:23 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:21:49 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:21:52 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR5-  
Feb  9 13:21:52 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I55^ pid=F0 It sure takes a long time after the subject.  
Feb  9 13:21:52 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I56+ pid=F0 Is the BBS doing something?  
Feb  9 13:22:00 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:22:03 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR5-  
Feb  9 13:22:03 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I55^ pid=F0 It sure takes a long time after the subject.  
Feb  9 13:22:04 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I56+ pid=F0 Is the BBS doing something?  
Feb  9 13:22:06 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR5-  
Feb  9 13:22:06 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I55^ pid=F0 It sure takes a long time after the subject.  
Feb  9 13:22:09 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I56+ pid=F0 Is the BBS doing something?  
Feb  9 13:22:15 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:22:18 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR5-  
Feb  9 13:22:18 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I55^ pid=F0 It sure takes a long time after the subject.  
Feb  9 13:22:18 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I56+ pid=F0 Is the BBS doing something?  
Feb  9 13:22:27 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:22:44 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:22:46 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR5-  
Feb  9 13:22:46 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I55^ pid=F0 It sure takes a long time after the subject.  
Feb  9 13:22:46 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I56+ pid=F0 Is the BBS doing something?  
Feb  9 13:22:49 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR6-  
Feb  9 13:22:49 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I56^ pid=F0 Is the BBS doing something?  
Feb  9 13:22:49 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I57+ pid=F0 I thought it would just take the message a store it.  
Feb  9 13:22:58 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:23:16 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:23:42 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:23:44 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR6-  
Feb  9 13:23:44 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I56^ pid=F0 Is the BBS doing something?  
Feb  9 13:23:45 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I57+ pid=F0 I thought it would just take the message a store it.  
Feb  9 13:23:53 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:23:55 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR6-  
Feb  9 13:23:55 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I56^ pid=F0 Is the BBS doing something?  
Feb  9 13:23:56 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 I57+ pid=F0 I thought it would just take the message a store it.  
Feb  9 13:24:04 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:24:22 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:24:49 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:25:25 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:26:09 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 RR5+  
Feb  9 13:26:30 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 DISC+  
Feb  9 13:27:23 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 DISC+  
Feb  9 13:27:59 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 DISC+  
Feb  9 13:28:43 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 DISC+  
Feb  9 13:28:55 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR6+  
Feb  9 13:28:55 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 DM-  
Feb  9 13:29:01 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR6+  
Feb  9 13:29:01 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 DM-  
Feb  9 13:29:06 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR6+  
Feb  9 13:29:06 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 DM-  
Feb  9 13:29:10 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR6+  
Feb  9 13:29:10 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 DM-  
Feb  9 13:29:15 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 RR6+  
Feb  9 13:29:15 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 DM-  
Feb  9 13:29:37 localhost soundmodem[16220]: Tx: fm KE7JVS-0 to K7CVO-1 DISC+  
Feb  9 13:29:39 localhost soundmodem[16220]: Rx: fm K7CVO-1 to KE7JVS-0 DM-  
Feb  9 13:29:56 localhost soundmodem[16220]: Rx: fm K7CVO-0 to ID-0 UI  pid=F0 K7CVO/R K7CVO-1/B  

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2007-02-12 19:39 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-02-09 22:02 Trouble connecting to KPC3P-8.3-HM$ don
2007-02-10 16:47 ` don
2007-02-10 21:39   ` bud Thompson
2007-02-12 19:39     ` don
2007-02-09 22:08 don

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.