Hello Guys,
I use TWO pieces of HAL P-38 in one computer and I receive and send QTCs
without problem on both TNCs.
Probably you have not configured SHIFT-F8 till F11 keys as QRV, QSL, etc.
buffers for QTC's.
Remember also to include "%E" command to stop transmitting.
See, my buffers are as follows and all traffics (RX and TX) are right:
SHIFT-F8 %RQSL QTC'S TNX DE SN7N%R%E
SHIFT-F9 %RI'M READY, GA DE SN7N%R%E
SHIFT-F10 %RHW COPIED?%R%E
SHIFT-F11 %RARE U READY?%R%E
I hope it helps.
GL and see you all in the WAE.
Pawel, SP7PS (SN7N in contests)
----- Original Message -----
From: Don Hill <aa5au@msn.com>
To: WriteLog Reflector <Writelog@contesting.com>
Sent: Friday, November 10, 2000 3:20 AM
Subject: [WriteLog] QTC problem with DXP-38
>
> I've been practicing sending and receiving QTC's on both of my
> radios/computers for tomorrow's upcoming WAE RTTY contest.
>
> I am finding that WriteLog does not send QTC's with a DXP-38 as
> the TNC. It works fine with a PK232.
>
> Can someone with a DXP-38 (or perhaps any HAL TNC) please confirm this?
>
> This is easily done. Log 10 bogus QSO's. Enter the callsign of the
> 11th QSO in the entry window. Hit ALT-S, hit the Xmit QTC's button.
>
> What I am finding is that WriteLog sends the first line with the QTC
> number OK and starts the first QTC. It sends the date, callsign and
> begins to send the serial number on the first QTC, but stops and
> only sends diddles from then on. Tried it several times.
>
> Not what I wanted to find less than 24 hours before the contest, but
> I can easily switch the PK232 to the rate station and relegate the DXP-38
> to the multiplier station. As a fact, I'm doing this immediately.
>
> Thanks!
> Don Hill, AA5AU
> http://www.geocities.com/aa5au/
>
>
>
>
>
> --
> WWW: http://www.writelog.com/
> Submissions: writelog@contesting.com
> Administrative requests: writelog-REQUEST@contesting.com
> Problems: owner-writelog@contesting.com
>
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|