| |
PA2AGA > HDDIG 10.10.99 06:53l 209 Lines 6418 Bytes #-9724 (0) @ EU
BID : HD_99_255A
Read: GUEST
Subj: HamDigitalDigest 99/255A
Path: DB0AAB<DB0PV<DB0MAK<OK0PKL<OK0PPR<OK0PPL<OK0POK<OK0PAB<HA5OB<HA3PG<
SV1AAW<EA7URC<PE0MAR<PI8VNW
Sent: 991010/0101Z @:PI8VNW.#ZH2.NLD.EU #:6999 [HvHolland] FBB7.00g $:HD_99_255
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA21019 ; Sat, 09 Oct 99 20:43:59 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
id AA00016307 ; Sat, 09 Oct 99 22:26:28 MET
Date: Sat, 09 Oct 99 22:25:03 MET
Message-Id: <hd_99_255A>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 99/255A
X-BBS-Msg-Type: B
Ham-Digital Digest Sat, 9 Oct 99 Volume 99 : Issue 255
Today's Topics:
DX-Net
Help with Kam+ (3 msgs)
Help with MIC-E Protocol Spec please
Japanese packet radio hinted at on TAPR site.
Kam Plus firmware available
MFJ-1278
PACTOR or AMTOR
Remote dialup via ham 2m etc? (8 msgs)
Special event DX - centenary of Anglo Boer War
Wtd: DX NET Program
Send Replies or notes for publication to: <Ham-Digital@UCSD.Edu>
Send subscription requests to: <Ham-Digital-REQUEST@UCSD.Edu>
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the Ham-Digital Digest are available
(by FTP only) from ftp.UCSD.Edu in directory "mailarchives/ham-digital".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
Loop-Detect: Ham-Digital:99/255
----------------------------------------------------------------------
Date: Fri, 08 Oct 1999 22:09:19 GMT
From: "Dale Hagert" <dhagert@mn.mediaone.net>
Subject: DX-Net
DX-Net is now available, both DOS and Linux version at the DX Net web site.
Thanks
Dale W0IR
>.
------------------------------
Date: Sat, 09 Oct 1999 02:17:06 GMT
From: Frank Hoonhout <fhoonhout@home.com>
Subject: Help with Kam+
I have a weird problem with my KAM+
version is 7.1
When I use any mode (RTTY, AMTOR, PACKET, GTOR) with either KaGold or
Hyper terminal and start sending characters, after 3 min of continuous
transmission the KAM+ unkeys the transmitter, even though the XMIT LED
is still red! If I hit the transmitter button on the HF rig, it
continues on transmiting just fine.
I have tested into a dummy load and it does the same thing. The only
way to reset the KAM+ is to hit the <ESC> and wait for it to unkey.
This happens over and over again. Always at the same time interval.
Is there a setting that is wrong? Or is my TNC bad?
Frank...
KJ7DZ
>.
------------------------------
Date: Fri, 8 Oct 1999 21:19:03 -0500
From: "Rick Ruhl" <ricker@cssincorp.com>
Subject: Help with Kam+
That's called the watchdog timer, you can set a jumper in the KAM to turn it
off.
--
Rick Ruhl
President, Creative Services Software
http://www.cssincorp.com
Frank Hoonhout wrote in message <37FEA5F6.1E1AE6C0@home.com>...
>I have a weird problem with my KAM+
>version is 7.1
>
>When I use any mode (RTTY, AMTOR, PACKET, GTOR) with either KaGold or
>Hyper terminal and start sending characters, after 3 min of continuous
>transmission the KAM+ unkeys the transmitter, even though the XMIT LED
>is still red! If I hit the transmitter button on the HF rig, it
>continues on transmiting just fine.
>
> I have tested into a dummy load and it does the same thing. The only
>way to reset the KAM+ is to hit the <ESC> and wait for it to unkey.
>This happens over and over again. Always at the same time interval.
>
>Is there a setting that is wrong? Or is my TNC bad?
>
>Frank...
>KJ7DZ
>
>.
------------------------------
Date: Sat, 09 Oct 1999 04:32:58 GMT
From: Frank Hoonhout <fhoonhout@home.com>
Subject: Help with Kam+
Thanks I found it. Now it works just fine.
Frank...
Rick Ruhl wrote:
> That's called the watchdog timer, you can set a jumper in the KAM to turn it
> off.
>
> --
> Rick Ruhl
> President, Creative Services Software
> http://www.cssincorp.com
>
> Frank Hoonhout wrote in message <37FEA5F6.1E1AE6C0@home.com>...
> >I have a weird problem with my KAM+
> >version is 7.1
> >
> >When I use any mode (RTTY, AMTOR, PACKET, GTOR) with either KaGold or
> >Hyper terminal and start sending characters, after 3 min of continuous
> >transmission the KAM+ unkeys the transmitter, even though the XMIT LED
> >is still red! If I hit the transmitter button on the HF rig, it
> >continues on transmiting just fine.
> >
> > I have tested into a dummy load and it does the same thing. The only
> >way to reset the KAM+ is to hit the <ESC> and wait for it to unkey.
> >This happens over and over again. Always at the same time interval.
> >
> >Is there a setting that is wrong? Or is my TNC bad?
> >
> >Frank...
> >KJ7DZ
> >
>.
------------------------------
Date: Sat, 9 Oct 1999 12:21:08 +0100
From: Ian Wade <ian@dowrmain.demon.co.uk>
Subject: Help with MIC-E Protocol Spec please
I've been reading through the MIC-E protocol spec (Crosswell/Parsons,
Jun97/Dec98), and there are a few things I don't understand:
1. I believe Fig 2 shows the destination address encoding *as it is
transmitted* That is, a protocol analyzer would display the bits as
shown in the diagram. (Correct?)
When the receiving TNC processes this address, it shifts each octet one
bit right, and presents the result to the user. [E.g. an ordinary (non-
MIC-E) callsign letter "A" (41hex) is transmitted as 82hex, then
converted back to 41hex at the receiving end by the TNC].
This leads to my confusion, regarding the ASCII value table containing
the "Lat digit, Message/N/W/L Bit = 0" etc columns. I don't understand
how this table relates in any way to the transmitted/received data.
To take a real example, the first octet in Fig 2 contains Ar1DDDD0. If
message bit A is zero, and DDDD is 0011 (BCD digit "3"), the transmitted
bits are 00100110 (=26hex). At the receiving end the TNC shifts the
field one bit right, giving 13hex.
My questions, then:
a. How does 13hex relate to anything in the ASCII value table?
b. Does the receiving TNC actually output 13hex for (what it thinks is)
a callsign character? (It's a non-printing character).
c. Have I missed the point entirely?
2. What is the BCD encoding for a position ambiguity space character?
3. What are "custom" messages and where is the custom message bit
encoded?
To be continued in digest: hd_99_255B
Read previous mail | Read next mail
| |
