Hal,
Try this:
turn off the PK232
start CT and set COM ports, multi-op etc
to get packet window up - ALT-T
turn on PK232 TNC and type ******* (Enter) until the PKT and CMD LED's come
on. You should now see a welcome message.
Type MY (your call) (Enter)
Type RESTART (Enter) You should see the CHECKSUM message appear.
Type C (DXpacketcluster node callsign) (Enter). The CON LED's should come
on and you should see the welcome message from the node. You are in
business, we hope.
Good luck!
Randy W6SW
w6sw@jps.net
-----Original Message-----
From: ct-user-admin@contesting.com
[mailto:ct-user-admin@contesting.com]On Behalf Of Hal Kennedy
Sent: Thursday, August 30, 2001 5:46 PM
To: ct-user@contesting.com
Subject: [ct-user] PK-232MBX Interface Problems
Frustration persists, but thanks to all those who have emailed privately
with good helpful suggestions. I have finally come to believe the software
is simply not finding COM1. I see no data at all in the alt-T receive
window and the TNC is totally unresponsive. The computer to TNC interface
work fine with the same computer and cable running under different software.
Does anyone know for sure that the CT shareware version (6.26) actually will
drive a TNC on one of the COM ports? Any chance v6.26 has it disabled?
Also, does anyone have any thoughts on why the software cannot/would not be
able to access COM1, or any of the other COM ports for that matter (Ive
tried several)?
Thanks,
Hal N4GG
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
_______________________________________________
ct-user mailing list
ct-user@contesting.com
ct-user-request@contesting.com Subject=unsubscribe to unsubscribe
http://lists.contesting.com/mailman/listinfo/ct-user
|