RXCLUS Mantis - Issues

0000018: Error "Can't open COM port" in version 8.5b

Sun, 02 Sep 2012 22:18:06 +0200

This error may be displayed at program start if one (or more) COM port is enabled to communicate with a TNC or for CAT.

0000017: Some valid IOTA references can't be entered

Thu, 23 Aug 2012 15:05:43 +0200

In Options - Extras - Link callsigns to IOTA references, some valid IOTA references can't be entered.

0000016: Skimmer spots not identified as DX-spots

Thu, 23 Aug 2012 15:01:39 +0200

When connected to a skimmer node (for example telnet.reversebeacon.net:7000), DX spots are displayed in the Monitor window, but not in the DX and Alarm windows.

0000014: Error “Your IOTA.DAT seems to be corrupted, can´t start RXCLUS”

Sun, 29 May 2011 13:49:33 +0200

since I downloaded the latest version, 8.5 and replaced my old 8.4b or whichever I am at every new attempt to start the program, I am met by “ Your IOTA.DAT seems to be corrupted, can´t start RXCLUS”

This means that I have to reload the program EVERY time I try to open it, before being able to use it.

It never happened with the previous versions, 8.4b and backwards......

SM0xxx

0000012: Option "Same priority for LoTW and paper QSL's" not working properly

Sun, 17 Apr 2011 21:05:39 +0200

When selecting "Same priority for LoTW and paper QSL's", a new country for me (no Paper QSL or LoTW confirmation) shows the spot in "red" color, instead of "magenta".

CT1xxx

0000011: CAT frequency setting in RTTY inadequate when using FSK keying

Sun, 17 Apr 2011 18:08:27 +0200

Bei folgendem Spot:

DX de K4GMH: 14088.0 HZ1PS RTTY Peter Jeddah 1809Z L

wurde Frequenz/Mode auf 14087.0 USB eingestellt. Da ich FSK mache, sind's für mich in diesem Fall zwei Handgriffe mehr: QRG auf 14088 stellen und Mode auf RTTY.

DL4xxx / 02.03.2011

*** Summary in English:

By clicking on the spot above the frequency was set to 14087.0 USB. As I'm using FSK I have to manually change this to 14088 RTTY.

0000010: DXCC import fails if the ADIF file includes binary data

Sun, 10 Apr 2011 21:13:00 +0200

DXCC import fails if the ADIF file includes binary data, which happens (at least) with Logic 8.

0000007: CAT non working with some Icom models (not specific to V8.5)

Wed, 30 Mar 2011 21:21:03 +0200

This issue is not specific to V8.5 but could never be fixed since CAT support was implemented in RXCLUS.
CAT works OK with some Icom models, like IC-756 Pro III,765,970 or 7400, but several users reported problems with other models: IC-706MK2G, IC-756PRO or R-75.
Unfortunately, the only 2 Icom radios I have access to work as expected, so it's very difficult to explain why it does not work with others, considering that all Icon's are supposed to use the same protocol...
I reproduce below some reports received about this issue.
If somebody having this problem is ready to seriously cooperate with me (=make tests, report results in detail, try new versions,.), he is welcome to contact me.

0000004: Wrong sunrise/sunset times for DX

Sun, 09 Jan 2011 20:05:30 +0100

The Sunrise & sunset time of the "DX" are wrong, I just tried to check JA e
3D2...

0000008: Date and time displayed in US format on Windows 7

Fri, 07 Jan 2011 10:56:19 +0100

Date and time are displayed using the US format on non US Windows 7 installations.

0000002: Wrong QTF displayed

Wed, 05 Jan 2011 15:43:55 +0100

Habe die neue Beta-Version installiert. LOTW-Import funktioniert, auch macht alles einen schönen Eindruck. Die Antennenrichtung zum DX-Spot ist jedoch meist 188° und „fehlerhaft“.

0000006: Deleted DXCC entities imported erroneously as ZS8

Mon, 03 Jan 2011 20:56:43 +0100

The "Import LoTW report" fonctions (both "local" and "ARRL") can add erroneously credits to ZS8 (or the last entry in the DXCC database) if:
- your LoTW file contains confirmations for deleted entities;
- those entities were not already added to your personal DXCC database.

0000001: Incorrect ADIF numbers

Sun, 02 Jan 2011 23:34:49 +0100

I’m trying with the last rxclus 8.5beta1 and when I import all my log in ADIF format, I found a problem with the new PJs.

I have paper QSL for PJ7 and PJ6 only, and looking at the statistics I can see in my case as Paper confirmed all QSOs with PJ4 Curaçao, and only Worked all PJ7 Sint Martin.

I think, there a error in the ADIF numbers for this two entities PJ4 <> PJ7.

I’m using Logger32 and the entity code for the new PJs are the same as the related in the ARRL web:

----------------------------------------------------------------------------
This information is provided, in advance, to those who use the DXCC assigned country/entity codes for programming software:

517 – Curacao
518 – Sint Maarten
519 – Saba and St. Eustatius
520 - Bonaire
----------------------------------------------------------------------------