foldynl / qlog Goto Github PK

Hi,

I tried to compile QLog on an older IBM-T60 laptop. The laptop is running 'Debian bullseye 32bit'.

After starting QLog I get this message:

t60@lenovo-t60 ~/Software/QLog/QLog $ ./qlog
Hash collision!!! Fatal error!!
08:13:04.720 [WARNING ][ ] => QObject::killTimer: Timers cannot be stopped from another thread [(null):(null):0]
08:13:04.720 [WARNING ][ ] => QObject::~QObject: Timers cannot be stopped from another thread [(null):(null):0]
08:13:04.720 [WARNING ][ ] => QObject::killTimer: Timers cannot be stopped from another thread [(null):(null):0]
08:13:04.720 [WARNING ][ ] => QObject::~QObject: Timers cannot be stopped from another thread [(null):(null):0]
t60@lenovo-t60 ~/Software/QLog/QLog $

Where could I start troubleshooting?

Here is the compiler log and the debug log.

_compiler.zip
_debug.zip

After logging a QSO the transmit power is taken from the tab "My Station" / "Power". Since for some bands (6m, 60m) the transmit power is limited, the content of the column "TX PWR" must be corrected in these cases. Or you have to change the field "Power" in the tab "My Station" before.

With CQRLog a manual correction of the transmit power is also necessary here.

You could leave it like this, introduce a band-dependent power setting, or take the transmit power from the rig.

When trying to compile QLog under Kubuntu 21.10 I encountered the following problems.

• the package "qt5-default" could not be installed.
  A search on the internet showed that the package is not available in the package sources in Debian bullseye and from Ubuntu 21.04 on. As a replacement for "qt5-default" you can install these packages "qtbase5-dev qtchooser qt5-qmake qtbase5-dev-tools".

• after downloading the source code from Github, the directory "/res/flags" is empty. The missing files have to be copied there from "foldynl/QLog-Flags".

Afterwards the compile process runs through.

73, Wolfgang
DL2KI

When entering long profile names, the Rig Widged becomes very wide, even if only a short profile name is visible.

Perhaps it would make more sense to provide a separate line for the profile drop-down menu and place the "Band Changer" and "Mode" drop-down menus below it.

After switching the VFO "A/B" on the K2 (different frequencies), the frequency display in the "Rig" window of QLog does not change.

Since the rig/rotator is usually connected after starting QLog, it might be easier for operation to move the checkboxes from the "Equipment" menu to the 'Rig' / 'Rotator' widgets, or to place an additional checkbox or buttons here.

Example:

In case the transmit power is not taken over by the rig (PA, transverter, ...), it would be useful if you could set a default transmit power in the rig profiles.

Based on DL2KI comment:

The "Bandmap" window cannot be displayed narrower. The left margin between the window border and the frequency could be reduced. Furthermore, the length of the lines between the frequency scale and the call signs.This, and an adjustable font size, could improve the flexibility of the window width.

In the tab "Station" the fields "Callsign" and "Gridsquare" in the "Dark" theme appear empty after selecting the profile, although contents are available. The content is only visible after clicking into the field.

QLog generates a high processor load when DX-Cluster is switched on. With 'telnet.reversebeacon.net:7300' I measured up to 25%.
With the same settings it is with CQRLog up to approx. 6%.

If a call is entered in the 'Callsign' field that has already been worked, the previous QSO's appear in the QSO table.

In the 'New QSO' area of the main window some data (Name, QTH, Locator, Cont, ITU, CQ, State) appear to the callsign, which are obviously taken over from the last QSO, because the data are displayed even if the 'Callbook' is switched off. The name is taken from 'name', the QTH from 'qth'. It would probably be better here to display data from 'name_intl' and 'qth_intl', as these fields tend to be displayed as the default in the QSO table.

As far as I can see, the data of the fields 'comment_intl' and 'notes_intl' or 'darc_dok' are not taken from the last QSO.

But from my point of view this would make sense, because then you could reuse the contents completely or partially. Especially with 'Comment' and 'My Notes' it is often useful to be able to fall back on the information from the last QSO.

For the fields 'Age', 'E-Mail' and 'URL' it also seems to me to be useful, because these data remain relatively constant.

based on DL2KI comment:

"RST Sent", "RST Rcvd", "QSL Sent", "QSL Rcvd", ...

The columns each contain a few characters of data, but the headings make them unnecessarily wide. In addition, the translation of the column headings in other languages is often longer (in German, at least, this is the case). It would therefore be worth considering whether the column headings should be shortened to the necessary size and generally left in English. Personally, I prefer to use the English version at present.

Example: "RSTs", "RSTr", "QSLs", QSLr", ...

In this way, a revision of all headings and column contents could improve the flexibility of the window sizes.

If multi-line 'Notes' are entered, the penultimate line is displayed in the QSO table in the 'Notes' field.

It would probably make more sense to change the text orientation in the field so that line 1 of the multi-line notes is displayed.

After turning on RIT or XIT on the tranceiver, both offsets are displayed in the Rig window if they are set <> 0 on the TRX.
However, the displayed offsets are always the same for RIT and XIT, even if only RIT or only XIT are switched on.

Based on some tests (Discussions / Show and tell) I suspect that the data transfer from 'rigctl' partly does not work.

In the case of "Elecraft K2" this could be due to a too fast "poll rate". In the case of the "K3", the display "VFO A" in the "Rig" window remains after switching the VFO A/B.

For further tests I am gladly available (except 20.03 to 27.03).

In the tab "Modes" you find 20 modes. Obviously the classic modes "CW", "LSB", "USB", "RTTY", "DATA" are missing. All available modes are "Disabled" for me, because they are not used.

This leads to the fact that when logging a CW QSO the mode cannot be selected in the QSO window. Whether an automatic takeover of the mode from the rig into the menu fields "Mode" / "Submode cannot be checked.

In "Discussions - Import of ADIF data from other programs " you wrote:

Therefore I decides to implement following algorithm.

If QLog imports ADIF file with NAME field then it is saved to QLog's NAME_INTL field (without any conversion), because it can contain , incorrectly, UTF-8 characters from source application.

QLog tries to remap accents string to accent-less string and save it to NAME field. This field is marked as NAME (ASCII) and it is strictly used for ADI export.

When I save two test QSO's, the names and QTH's are saved in the NAME / NAME_INTL and QTH / QTH_INTL fields as described above.

See the first two log entries.

Then in QLog I deleted the existing log and re-imported the current ADI file from CQRLog. Now here you can see that the import of the fields NAME / NAME_INTL and QTH / QTH_INTL is not done as described above.

Most of the NAME_INTL and QTH_INTL fields are empty.

Discussed in #44

If "Connect Rig" is selected when the rig is powered off, a warning message will appear after about 24s.

If "Connect Rig" is selected and then "Connect Rig" is switched off again after a few seconds, the user interface freezes. After about 20s the same warning message as above appears.

From my point of view it would be better to do without this technical warning message. You could program it internally so that there is simply no visible reaction and the checkbox "Connect Rig" is deactivated in the background.

If the software does not react after "Connect Rig", the user will search for the cause himself and find out that the rig is not powered on or the connection cable is not plugged in. At best, an informative, non-technical warning message could be displayed, e.g. "Cannot connect rig", or similar.

• In the DX cluster I mainly use "telnet.reversebeacon.net:7000" for CW. For users who prefer other DX clusters, it would be useful to store some "DXC Server address" entries so that you can select them from the menu.

• For example, if one enters an incorrect "telnet.xreversebeacon.net:7000" entry in the field, and then deletes the "x" by pressing the "DEL" key, the entire entry is deleted.

• The input field for the "DXC Server address" is narrow when empty. If you enter "telnet.reversebeacon.net:7000" there and then press "Connect", the input field remains narrow and does not adapt in width to the content. This only happens when you confirm the entry of the "DXC Server address" with "Enter".

Discussed in #48

If you press "Connect Rig" with the transceiver is powered off, QLog GUI freezes. After about 24 seconds a window "QLog Warning" appears - "Rig Error: Open Connection Error - Communication timed out".

In "CQRLog" the switching of the two powered off rigs is possible without the GUI freezing. In the window "TRX Control" the frequency "0" is then displayed. The operation of the GUI is still possible.

Maybe an error handling can be added to this action to prevent the GUI from freezing.

The Band Changer in the Rig Widget does not work for me.
No band selection is offered.

QLog can also be used with a rig without CAT interface. For this purpose a rig profile with Hamlib Model 1 (dummy) can be used.

It would be desirable to be able to switch the frequency range in the bandmap (when DX cluster is running) with the drop-down list in the rig widget in this mode.

Currently, the switch can only be made by clicking on a corresponding entry in the DX-Cluster widget.

Based on DL2KI comment:

The "Rig" window could be supplemented with small buttons for direct band switching and for switching between 2 rigs

20:32:12.586 [WARNING ][qlog.core.qrz.runtime] => processing a new request but the previous one hasn't been completed yet !!! [virtual void QRZ::queryCallsign(QString):../QLog/core/QRZ.cpp:68]

TX power is taken from a rig but if the rig behind PA then the value is incorrect

When switching on the 60m band, the band start is displayed in the band map at 5.102 kHz. In the IARU, region 1, the band start is at 5.3515 kHz.

If network rig is connected then QLog crashes.

Depending on the QSO window width setting, long DXCC country names are truncated.

One could also set the info widget wider, but this would be at the expense of the display in the neighboring windows.

Maybe the font size of the country names could be reduced in general or the font size could be adjusted to the width of the info widget. Another possibility might be to make the few long country names shorter already when importing the DXCC country list.

Example: 'Federal Republic of Germany' --> "F.R. of Germany".

I use a 21.5 inch monitor with 1920 x 1080 pixel resolution.

If the rig is switched off while the QLog is running, this warning message appears after approx. 46s.

And the color of the rig profile in the "Rig Widget" changes from green to red.

If the rig is switched off while the QLog is running, and then the "Connect Rig" checkbox is manually deactivated, the GUI freezes. After about 46s the same warning message as above will appear, and the color of the rig profile in the "Rig Widget" changes from green to red.

Again, it seems to me that internal "transparent" error handling without a technical warning message would make more sense. At best, one could display an informative, non-technical warning message. e.g. "Connection to rig interrupted", or similar.

Also, the time duration for the detection of these states seems to me to be too long.

fix typo:

networt -> network

It is a static text now. Would it be possible to get a current VFO from hamlib?

is it possible to obtain Rig TX/RX offsets from Hamlib?

In some cases it may be useful to be able to select an additional 'Starts With' condition.

12:55:13.930 [WARNING ][ ] => QImage::pixelColor: coordinate (696,952) out of range [(null):(null):0]
12:55:13.930 [WARNING ][ ] => QImage::setPixelColor: color is invalid [(null):(null):0]

If the transceiver is powered off while it and the DX cluster are connected, the DX cluster will continue to run. If a command is sent to the rig, e.g. click on a call in the bandmap, the QLog GUI freezes.

In this case after some seconds two windows "QLog Warning" appear - "Rig Error: Set Frequency Error - Invalid Parameter" and "Rig Error: Get Frequency Error - Communication Timeout".

Maybe you can also add some error handling here to prevent the GUI from freezing and disable "Connect Rig".

If a running rig is powered off in CQRLog, the frequency display in the "TRX control" window jumps to "0" after about 12 seconds. After switching on the transceiver again the correct frequency appears after approx. 1 second again in the window "TRX Control" and CQRLog continues to run normally.

After opening the window "Settings, Equipment, Rigs", 5 Data Bits are given as default.
In my opinion 8 data bits would be more useful as default.