Well, I have not try WL with KAM '98 since Ver. 10.12 (WL failed to find KAM
and leaving KAM on freeze in terminal mode, and needed to reset by removing
the Lithium battery every time when tried to set up with WL).
Have you heard any body tried KAM '98 with later WL ??? Otherwise I may
have to stay with WF1B for CQWWRTTY.
73, de Jon NN5T
-----Original Message-----
From: Ron Stailey [mailto:k5dj@contesting.com]
Sent: Friday, February 25, 2000 9:49 AM
To: Jon Suehiro
Subject: RE: KAM '98 Problem
At this point Jon all I can tell ya is hang on to the KAM+ for RTTY mode,
Until we get a KAM'98 we won't be able to add support. I ll keep trying to
get one.. I guess KAM is selling them as fast as they make them..
73, de Ron K5DJ
----------------------
Negative.
Setting COM1: = 9600,N,8,1, does not work with KAM '98, I am not getting
"cmd: " prompt at all. (As I previously said I have tried
1200/2400/4800/9600 with or without "x" at the end.)
I owned KAM Plus in prior to KAM '98, and com port setting for KAM plus was
@ 1,200 bps instead of @ 2,400 bps (for KAM '98) with Hyper Terminal or
Procomm plus (of course same on PacTerm which came with Kantronics TNC).
That's why I believe the settings between KAM Plus and KAM '98 are
different. I also have KPC 3 Plus for VHF packet, and it's set to @ 2,400
bps too.
For your information, both KAM '98 and KPC 3 Plus firmware is now new
version 8.3 and this may do some effect to WL.
Your input will be appreciated to make KAM '98 work with WL, I am not
planning to use sound card for RTTY at this time.
73
-----Original Message-----
From: Ron Stailey [SMTP:k5dj@contesting.com]
Sent: Tuesday, February 22, 2000 4:25 PM
To: Jon Suehiro
Subject: Re: KAM '98 Problem
Jon, the KAM '98 is a new TNC KAM came out with a short while ago.
We haven't added support for this TNC as yet. I have written KAM to see if
we can get one so we can add support. If the same setting for a KAM+ will
work I may be able to help. Below is some info that will help you with KAM+
and WriteLog.
I personally don't have a KAM myself. We do have a good KAM+ man on staff
here is what he sent me to send all KAM+ users that are having a problem.
With a little luck maybe the setup is the same.. You may want to check with
Raj VE6RAJ to see if he can help if this doesn't work out for you.
Don't really know if Raj has a KAM '98 or not. His e-mail address is at the
end of his help info below.
73, de Ron K5DJ
---------------------------------------------------------------------------
If you have experienced trouble getting the KAM+ TNC to work with Writelog,
try the following:
The computer the TNC and Writelog all need to be configured so that they
aretalking at the same speed on the same port. If you are using a digiboard
or rocket port with coms above com 4, I suggest you first get everything
going on one of com1 to com4, and then once the Kam is configured, get the
higher com port going.
Kams can also be set to work in varios modes, i.e. TERM, HOST, NEWUSER etc.
In order for the Kam to work with Writelog it must be in TERMINAL mode.
>From Window's control panel, select system then device manager. Open the com
ports by clicking on the plus sign and select the com port where the Kam is
installed and check to make sure that the properties for this port show baud
9600, no parity, data bits 8, no parity, and flow control should be blank.
Select OK to close the system properties window.
Kam TNCs come with a basic communication package called pacterm that allows
you to set up the initial configuration. Depending on the version, get in to
HF mode and you should see a prompt that looks like this.. cmd:
If you have trouble at this point, exit pacterm and go back in to it again.
You may have to do this a few times if the Kam is in host mode.
When you see this prompt (cmd:), you can send commands directly to the Kam
to configure it the way you like. You can also issue the DISPLAY command to
see what is stored in the Kam's memory. The display command will give you a
listing of about 200 items. You can also issue the command DISPLAY R to see
what thwe settings are that effect rtty operation.
This is what you should see:
cmd:display r
ABAUD 9600
AUTOCR 0
AUTOLF ON
AUTOSTRT OFF
BITS $00
CD INTERNAL/INTERNAL
CODE AMTOR ITA2
CODE RTTY ITA2
COMMAND $03 (CTRL-C)
CRADD OFF
CRSUP ON/OFF
DIDDLE ON
ECHO ON
FLOW OFF
FILTER OFF/OFF
FSKINV ON
INTFACE TERMINAL
INVERT OFF
LFADD ON/OFF
LFSUP ON/OFF
LOWTONES OFF
MARK 2125
MAXUSERS 3/3
PARITY NONE
PMODE NONE
RBAUD 45
SHIFT 170
SPACE 2295
USOS ON
XFLOW ON
XMITECHO ON
XMITOK ON/ON
XOFF $13 (CTRL-S)
XON $11 (CTRL-Q)
Actually you won't see all of these, but you can view the additional
commands by just typing in the command name. If you need to change anything
just enter the command with the appropriate value after the command. For
example, entering ABAUD 9600 will set the start up baud rate of the Kam to
9600.
In the WRITELOG.INI file which is in the \windows folder, find the [PORTS]
section and make sure the following is in there:
COM2: = 9600,N,8,1, the last comma isn't a mistake
One of the problems with the KAM is that some software will leave the KAM in
host mode. In this case Writelog cannot initialize it. Even the
KAM software like hostmaster and pacterm won't initialize the Kam when this
happens. To prevent this from happening in the future, always shut Writelog
down first before turning the Kam off.
73, de Raj VE6RAJ <raj@logicresources.com>
After enough struggling for a couple weeks, please HELP !
WriteLog 1012 does not respond with KAM '98. Rig interface (TS950SDX) on
COM2 is working OK.
PC is Celeron 400MHz on Intel SE440BX-2 mother board with 96MB of DIMM,
running on Win98.
KAM '98 works normally with Procomm Plus, Hyper Terminal, DX4win, and
DXbase2000 @ 2400-8-n-1 (Flow control: Hardware) on Com1 (therefore KAM,
serial cable, and serial port should be OK), I set WriteLog.ini to
[Ports] COM1:=2400,n,8,1,x
In order to be successfully initialized as Host Mode, I need to remove
Lithium battery in KAM (complete reset).
Port is selected to COM1, Mode is as default (45 baud), TU type is KAM on
Rttyrite.
I can type into the Rttyrite screen, but unable to obtain command line nor
receive output. Pressing FSK-Normal does not do any thing. If I press
Port/COM1, then Host Mode initialization begins and will be lost until KAM
is completely reset again (removal of Lithium battery).
Since KAM is reset, I should be reading random characters until enter " ***
", and ENTER YOUR CALLSIGN=> line should be shown up on Rttyrite screen
after Host Mode is set, but nothing happens.
I tried WL.ini setting as COM1: 2400,n,8,1, (no x) also, but did not make
any difference.
73, Jon NN5T
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|