|
Re: Stats tracking problem
Bob
Apparently I misread which PC was on which release. The only way I am going to be able to get a handle on this is with your actual logbook of an extract thereof. So, can you make an ADIF extract of your logbook (a small sample, or the whole thing if you like) that I can load into an empty logbook and duplicate the problem (tell me what to click where). Send zipped to k4cy@.... SeventyThree(s).
On January 31, 2020 at 2:56 PM Paul Ormandy <paulzl4tt@...> wrote:
|
|
|
|
Re: Stats tracking problem
Paul Ormandy
Hi Bob,
Thanks for the prompt reply. My L32 version shows 3.50.406, so the fix on 3.50.405 should have been implemented? There are no new updates showing. Vy 73, Paul
|
|
|
|
Welcome to Nigeria ...
Bob
Anyone using the timex.usg.edu or rolex.usg.edu NTP time servers today, they are both close to 5 seconds off. The joys of living in the Third World. SeventyThree(s).
|
|
|
|
Re: Stats tracking problem
Bob
From the release notes distributed with each auto-update. SeventyThree(s).
Version 3.50.405
Addresses a reported problem where importing QSOs from an ADIF file does not calculate statistics correctly
|
|
|
|
Stats tracking problem
Paul Ormandy
Hi,
Have a weird problem with L32. It is installed on 1 x desktop PC and 1 x laptop. The laptop is the one with the issue. The laptop's logbook was populated with an ADIF from the desktop. I am running 3.50.391 on the desktop and 3.50.406 on the laptop. The problem is missing confirmed entity modes in the Worked/Confirmed window and incorrect stats in the relevant Awards page. For example, I have a QSL from 4K5D 20m PSK31, which is correctly displayed in the Logbook and Previous QSOs window as verified but not showing at all in Worked/Confirmed window, i.e. if I click on the 20M DIG slot in the Worked/Confirmed window for 4K, it doesn't show 4K5D at all but does show unverified 4K6OF in FT8 mode. I ran Recalculate Statistics but the problem persists. Further checking showed that the problem lies with PSK31 QSOs. Some are appearing correctly but many are not. PSK31 is selected to be included in Stats in the Bands & Modes window. Maybe something happened in one of the updates?? Cheers, Paul
|
|
|
|
Re: Logger32 and CAT access for other software
Bob
If Log4OM works for you, I'd recommend you use it. SeventyThree(s).
On January 30, 2020 at 4:16 AM sp7ewl@... wrote:
|
|
|
|
Logger32 and CAT access for other software
sp7ewl@...
ello everyone I have been using Logger32 from the very beginning and I value this logger very much. Currently, after changing the radio to FFTX 5000 (previously I used TS590S, which had CAT after RS232 and USB) I have a problem sharing CAT FTDX5000 with several programs. It mainly uses Logger32, WSJT-X (JTDX), and the SDRPlus program - working as a panoramic adapter. All these programs use CAT. With WSJT-X (JTDX) and SDRPlus there is no problem because they can use OmniRig at the same time - unfortunately Logger32 does not have the ability to use OmniRig, you need to disable access to CAT. Recently I tested the Log4OM v2 login program, which has the ability to use OmniRig and all of the mentioned programs using OmniRig work very well at the same time. None of my splitters and other programs that let me share COM did not work properly as CAT from my FTDX5500 is connected to RigExpert TI-8 and is on virtual COM. Below is a screenshot from three monitors showing how it all works with Omnirig. If you were tempted to adapt Logger32 to use OmniRig it would be great. Old trees are not replanted and that's why I'm looking for such a possibility.
|
|
|
|
Re: autolog in QSO Entry window
Bob
When you type a callsign into the Logbook Entry Window (example: W1PR), you will see USA - Concord NH appear at the left side of the upper status bar. So far, so good, Logger32 knows you're in Country #291 and when you enter the callsign into the Logbook (by typing ENTER) that will be recorded in the DXCC field. Default reports is a little more complicated. Click TOOLS | SETUP BANDS & MODES. What you see is a skeleton BandPlan. You must customize this to your operating preference. If you look at the 5th column you will see the default report (both sent and received) for each band and mode. So, back to the beginning, enter the call W1PR, type TAB (this should put the focus in the SENT field). TAB again. Seeing as you didn't enter a report, the default is entered. OK now? SeventyThree(s).
On January 29, 2020 at 11:13 AM w1pr@... wrote:
|
|
|
|
Re: autolog in QSO Entry window
Hi Paul
The default reports are tucked away in the Tools à Setup Bands and Modes (5th column):
DXCC countries are automatically looked up from prefixes and shown on-screen as we are logging stations, and they are saved with the QSO info by default (I think). There is an option – somewhere! - to display either the DXCC country code or its name in the log pane. Is that what you mean?
As one of the keen DXers who has requested several of the many user-configurable options we have in Logger32, I wish to apologise to Bob and all of you using Logger32, for contributing to the bewildering number of right-click and menu options available. Still, it’s better than all of you having to use the program the same way as me!
73 Gary ZL2iFB
From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of w1pr@...
I am new to Logger 32. I thought that there was a way for the program to autolog the Country and Report entries in the QSO Entry window, as well as have default sent/receive reports for individual modes, but I can't find how to enable these features in the Help file. Can anybody tell me what I am missing? TNX.
|
|
|
|
autolog in QSO Entry window
Paul - W1PR
I am new to Logger 32. I thought that there was a way for the program to autolog the Country and Report entries in the QSO Entry window, as well as have default sent/receive reports for individual modes, but I can't find how to enable these features in the Help file. Can anybody tell me what I am missing? TNX.
73 de Paul W1PR
|
|
|
|
Re: COM port config for CW machine
Bob
When using the Software configuration of the CW Machine, DTR is used for CW and RTS is used for PTT. Two applications can not open/share the same serial port. SeventyThree(s).
On January 29, 2020 at 9:38 AM Matthias Bellmann <Dk4wd@...> wrote:
|
|
|
|
COM port config for CW machine
Matthias Bellmann
After long time trying to get cw machine running i found out, that CWType app is doing its job, when the keying line is set to RTS. CW Machinedoes not give me the opportunity to config it this way. Whatg can i do?
|
|
|
|
Re: Export distance field
Panos
Very thank you Bob 73
|
|
|
|
Re: Export distance field
Bob
On January 28, 2020 at 7:20 AM Panos <sv1grn@...> wrote:
|
|
|
|
Export distance field
Panos
Hi to all. The exported adif files doesn't contain the distance field. Is there any solution since I want this information? Thanks 73
|
|
|
|
Re: Fldigi - Logger Issue
ei3fw <craigrobinson@...>
Hi Nick & Wolf, Rolling back to Fldigi Version 4.0.4 seems to
have made the problem go away. Correct mode (PSK31 or 63 or whatever) and
correct reports are being logged in Logger 32 so all is good
again. 73
|
|
|
|
Re: LBP2 - Na3P - WSJT-X
Bob
... or current one. 73.
On January 26, 2020 at 11:56 AM Barry Lyons <gm4gif@...> wrote:
|
|
|
|
Re: LBP2 - Na3P - WSJT-X
Barry GM4GIF
...... could be worse Bob, she could be comparing notes with your previous ! Cheers Barry / gm4gif
|
|
|
|
Re: Display State names when transferring for wsjt?
Bob
The gridsquares, as logged by WSJT, should be logged in Logger32 along with the rest of the fluff in the UDP messages. If you use the WSJT with the Logger32 auto-logging (no mouse click needed) option, or JTDX, Logger32 can/will look up the STATE and everything else you needed to know automatically. SeventyThree(s).
On January 26, 2020 at 11:19 AM Marvin Stern <marbern@...> wrote:
|
|
|
|
Re: LBP2 - Na3P - WSJT-X
Jim K2QB
LOL.....nice one Bob!
Jim K2QB
|
|
|
