|
VK1RJ > MFJ 18.06.98 11:01l 56 Lines 1905 Bytes #999 (0) @ WW
BID : 169-VK1RJ
Read: GUEST
Subj: MFJ1276 Problems with Pactor Operation
Path: DB0ZKA<HB9OS<HB9H<HB9OK<IW2FPO<IK2QCA<IK1MAP<IK2HDG<I4UKI<IK6RUY<
IW0QMN<WB0TAX<N7NEI<KO6RI<KF6EPD<VK5ASF<VK7AX<VK2TGB<VK2GJB<VK2DAA<
VK2CZR<VK1BBS
Sent: 980609/0703Z @:VK1BBS.ACT.AUS.OC #:47579 [Canberra] FBB $:169-VK1RJ
From: VK1RJ@VK1BBS.ACT.AUS.OC
To : MFJ@WW
[¯¯¯ TST HOST 1.43b, UTC diff:5, Local time: Tue Jun 09 16:29:32 1998 ®®®]
Hi there from 'down-under'. Name is Richard and location is Canberra,
Australia. I have two MFJ tnc's ... which I use for packet. The older one
is a 1278 which I have upgraded to include pactor. This device works
satisfactorily - both with a simple terminal program and with more advanced
programs like "lan-link". I find the tnc is quite useful for local (ie
around vk) pactor contacts.
The MFJ 1276 I have is much more of a problem. I have a list of the jumper
settings ... and I can receive / monitor the local pactor stations 100%. If
I make any attempt to contact them ... I get disconnected at the instant
the connect frame is sent! I am not alone in this. In response to a plea
on the packet system at least one other amateur has responded with a
similar tale of woe. The local MFJ agent doesn't want to know! An email
to MFJ brought a suggestion that I freight it to them. I feel it is
something simple. Maybe one of the jumper settings is should be reversed??
I want to talk with other owners of the MFJ 1276.
You cane send me a packet mail to
vk1rj@vk1bbs.act.aus.oc
or better still
rjenkins@alphalink.com.au
Maybe we could compare our jumper settings??
CUL
73
Richard
===========================================================================
|| Richard Jenkins ||
|| vk1rj@vk1bbs.aus.oc rjenkins@pcug.org.au ||
|| GQRP #5253 VK QRP CW #437 ||
|| ||
|| This message composed with the assistance of TSTHOST (ver 1.43) ||
===========================================================================
Read previous mail | Read next mail
| |