Dear Ken:
Some observations from last weekends CQ-WPX Contest.
(1)
Radio Control in TS-850 has a little problem since long time; it
did not work correctly with 9.27 and today with the free CT version
9.89 that old problem is still there.
VFO-A, K1EA on 21022 ctrl-Enter, Band-Map shows:
21022.0 K1EA #1623
VFO-A, K3WW on 21027 ctrl-Enter, Band-Map shows:
21022.0 K1EA #1623
21027.0 K3WW #1623
still all ok. Now I switch to VFO-B.
VFO-B, DK2OY on 21015 ctrl-Enter, Band-Map now shows:
21022.0 K1EA #1623
21027.0 K3WW #1623
21015.0 DK2OY #1625
DK2OY should be at the top of the list not at the end.
VFO-B, DK3GI on 21018 ctrl-Enter, Band-Map now shows:
21022.0 K1EA #1623
21027.0 K3WW #1623
21015.0 DK2OY #1625
21018.0 DK3GI #1626
So the two VFOs are read correctly but sorted into two separate
lists, first spots from VFO A, then VFO B. When packet
spots come in, they tend to be aligned with the VFO-A
spots. When tuning the dial, the frequency cursor is hopping
around like crazy and you can't really tune up and down
the band. This is rather irritating.
(2)
I found a new effect with 9.89 which I cannot remember from
earlier versions. I call CQ on a frequency with the
RIT on. The display reads 21033.2 and my RIT is at +0.2.
A spot comes in and I jump there with Alt-F4. When I return
to my original frequency with Alt-F4, the new readout is
21033.4. So through the jump, I added 200 Hz to my TX
frequency. Next time I am at 21033.6, 21033.8 etc. I got
into some frequency fights last weekend because I thought
somebody had stomped on my frequency, hi hi.
(3)
I put some spots out though CT's Alt-F3 function last weekend.
Three times I had some mysterious comment added by CT (QSX something).
7030.8 UA9OA 25-May-2003 2120Z <dl6rai>
7047.0 PQ2Q 25-May-2003 2113Z QSX O <dl6rai>
7040.7 EY7AF 25-May-2003 2110Z <dl6rai>
7044.2 IS0OMH 25-May-2003 2110Z <dl6rai>
7001.8 HG4I 25-May-2003 2059Z <dl6rai>
7020.6 UX8IX 25-May-2003 1808Z QSX KN13 - IO7CQ TEST <dl6rai>
7041.8 UA9AFO 25-May-2003 1800Z <dl6rai>
7046.5 EA/LW9DA 25-May-2003 1800Z <dl6rai>
7018.4 SV5/DL3DRN 25-May-2003 1755Z QSX 9@9S <dl6rai>
7009.4 EU1SA 25-May-2003 1752Z <dl6rai>
7008.0 RU9CK 25-May-2003 1751Z <dl6rai>
7002.2 JH1AEP 25-May-2003 1750Z <dl6rai>
7003.1 SU9NC 25-May-2003 1750Z <dl6rai>
7018.8 SV5/DL3DRN 25-May-2003 1700Z <dl6rai>
7044.0 TA3DD 25-May-2003 1658Z <dl6rai>
7030.6 OI4PM 25-May-2003 1657Z <dl6rai>
7022.9 4X0X 25-May-2003 1655Z <dl6rai>
7028.3 RU0AW 25-May-2003 1655Z <dl6rai>
7009.0 9K9X 25-May-2003 1643Z <dl6rai>
7007.6 DK1NO 25-May-2003 1640Z <dl6rai>
(4)
Our contest location has two stations. Station B has the TNC, while station A
is the main station with access to all antennas. The TNC is a DRSI card built
into the PC of Station B. The two PCs are networked using NETTSR.EXE.
Station B can send and receive packet spots fine.
Station A can receive packet spots fine (the DRSI is configured as a remote TNC
there), however it cannot transmit anything. Whatever Station A puts into the
packet window simply disappears without ever being sent out on packet.
This problem has been in CT for a long time, I believe it came up after
the compiler change on 9.27.
Maybe you'll find time to fix some of them. I'll be glad to give you a hand
beta testing new versions. Keep up the good work! Just recently we operated
CT on a portable QTH and the time was inadvertently set to the year 2024.
So I can assure you now that CT will even be working 20 years from today
(if you still have hardware to run it on).
73 Ben, DL6RAI
--
[] Bernhard Buettner (Ben)
[] Mail: Schmidweg 17, 85609 Dornach, Germany
[] Internet: ct@dl6rai.muc.de
[] Packet: DL6RAI @ DB0AAB.#BAY.DEU.EU
|