|
Re: seem a bug previous QSO
Bob
Oliver, I think you are hallucinating. You are already in the Previous QSOs window where you can see all QSOs with the station. Why open another window to see all the QSOs? SeventyThree(s).
|
||
|
|
||
|
seem a bug previous QSO
F4FQH Olivier
Hi Bob and all Seem there is a bug or deleted function in the previous QSO
windows Before, when we clicked on a QSO, another log windows opened with all
QSO. Now when i click, there is nothing that
open. Checked on a 2nd logger and it’s the same
issue. or i missed something Thanks 73s Olivier F4FQH
|
||
|
|
||
|
Re: Name missing in L32Lookups
Bob
Rick, those were my observations (maybe a year ago). Today, I have no idea. Apparently others see different results. C'set la vie. Que sera, sera. SeventyThree(s).
|
||
|
|
||
|
Re: Name missing in L32Lookups
Rick Ellison
For me in JTDX the name works but in WSJT the name is not working for me.. I have tried transferring the First name only or First and Last but it still does not get transferred..
73 Rick N2AMG
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Damian M0BKV via groups.io
Yes Bob mine is working fine. Its just my brain is a bit dodgy tonight. 73
|
||
|
|
||
|
Re: Name missing in L32Lookups
Bob
Damian, a word of advice from the 'Colonies' ... Just say, "I rebooted, and it's working again". SeventyThree(s).
|
||
|
|
||
|
Re: Name missing in L32Lookups
Yes Bob mine is working fine. Its just my brain is a bit dodgy tonight. 73
|
||
|
|
||
|
Re: Name missing in L32Lookups
Bob
I'll take that as notification that WSJT no longer drops TxEnable prematurely. Thanks, SeventyThree(s).
|
||
|
|
||
|
Re: Name missing in L32Lookups
I've been using WSJT-w all day on varies bands and the name is transferred every time. Phil I use the 'Transfer First Name' otherwise the picture is as Bobs Fields to transfer picture. Make sure the program Creation Date for the L32Lookups application in the L32Lookups folder is 20/07/2020. My problem earlier was I had changed something stupid earlier this evening. Damian
|
||
|
|
||
|
Re: Name missing in L32Lookups
Bob
All as expected here. for a faux SSB QSO. My WSJT-X tests were a very long time ago, and no I have never used the manual log QSO button. 73.
|
||
|
|
||
|
Re: Name missing in L32Lookups
This is the 2nd time today I'm apologising. Bob, Rik I'm sorry there is nothing wrong. I do not know what I'm talking about, as usual. I obviously did something stupid and stopped the transfer. Just wasted an entire evening chasing my tail. Going to bed embarrassed.
|
||
|
|
||
|
Re: Macros split CW
Serge Bykovsky
Arturo.
Here is FT1000mp. Will try RCP later. Thank you and Bob, Serge Ra6ydx Вы писали 21 июля 2020 г., 0:34:15:
|
||
|
|
||
|
Re: Name missing in L32Lookups
Phill Morris (G6EES)
Bob
My settings are the same as your screenshot but the name still doesn't get stored.
I assume the on-air test you did of WSJTX resulted in the automatic store of the QSO (ie you didn't press Enter to store the QSO)
Phill G6EES
-----------------------
Phill.morris
07771 504738
-------- Original message --------
From: Bob <k4cy@...>
Date: 20/07/2020 22:33 (GMT+00:00)
To: hamlogger@groups.io, "Damian M0BKV via groups.io" <damianm0bkv@...>
Subject: Re: [hamlogger] Name missing in L32Lookups
... but it does work. and I just tested it. Check your setup options on the Logger32 QRZ Lookup window. SeventyThree(s)
|
||
|
|
||
|
Re: Macros split CW
Arturo LU6ETB
Hi Serge,
I use following one in a TS-850
$command FR1;$ $command MD#mode#;$ $command FT1;FB#split 01#;$ $command FR0;FT1;$
By changing 01 you add macros for another splits
Hopefully this is what you are looking for.
In the Help under “MACROs, Hot Keys and Programmable Buttons” you Will find aditional info
73 de Arturo, LU6ETB
Enviado desde Correo para Windows 10
De: Bob
As split settings and split operation is not confined to CW. There are several 'split' macros on the Radio Control Panel that can be applied to any/all modes. SeventyThree(s).
> On 07/19/2020 5:52 PM Serge Bykovsky via groups.io <datatelecom@...> wrote: > > > Please > > Who knows how to implement split shift in CW macros command? UP1 > f.e.g. > > I often use destination control of my radio (remote) and it should be useful. > > Thank you, > > Serge Ra6ydx > > P.S. Digi shift macroses are in the help file section I see. But no more > for CW mode. Sorry > > >
|
||
|
|
||
|
Re: Name missing in L32Lookups
Bob
... but it does work. and I just tested it. Check your setup options on the Logger32 QRZ Lookup window. SeventyThree(s)
|
||
|
|
||
|
Re: Name missing in L32Lookups
Bob
Phil, I think you'll find the when using WSJT none of the additional information is logged. As I explained, when Logger32 detects TxElable being dropped, it clears the Logbook Entry Window. Because WSJT drops TxEnable prematurely, there is no additional information to be logged. SeventyThree(s).
PS. If you find a single additional field (that does not originate from WSJT) being logged then my theory is proven to be bullshit.
|
||
|
|
||
|
Re: Name missing in L32Lookups
Thanks Bob, Poor old Winston Churchill got blamed for the cockup. All he wanted to do was go through the back door, he meant well, rip Winnie. However your WSIT-X explanation of the problem doesn't explain the fact that if you're not using any Data mode but SSB or CW Rik's Lookup App that gets all the QRZ.COM information about the contact OK and displays it in your 'Internet Callsign Lookup' Popup window refuses to transfer it when you click on the Popup Window.
|
||
|
|
||
|
Re: Name missing in L32Lookups
Phill Morris (G6EES)
Bob
Like WSJTX, JTDX has its advantages, but it also has numerous problems (i also belong to the JTDX groups.io and many users wouldn't say its any better!)
The missing name data in the log does appear to be restricted to the use of automatic logging with WSJTX and doesn't appear to be a problem when the QSO is 'manually' logged (by pressing Enter).
As for the TxEnable point you describe, why is it that L32 (together with L32Lookup)
does copy the name data from QRZ and correctly places it in the L32 log entry window etc, but when the QSO is completed (even with the final 73 exchange in WSJTX) then L32 only copies some of the data from the L32 Log Entry window into the log (ie everything
apart from the name). Why would the TxEnable play a part in only some of the data being stored?
Surely if TxEnable were the issue then no data would be stored in the log, rather than missing some parts of the data (ie name) that L32 has already been given?
Phill G6EES
-----------------------
Phill.morris
07771 504738
-------- Original message --------
From: Bob <k4cy@...>
Date: 20/07/2020 21:46 (GMT+00:00)
To: hamlogger@groups.io, "Damian M0BKV via groups.io" <damianm0bkv@...>
Subject: Re: [hamlogger] Name missing in L32Lookups
Damian, to quote a former First Lord of the Admiralty, and architect of the
Gallipoli Campaign (that cost 250,000 lives), "Two Countries
separated by a common language". Huh, what did you say?
I don't use WSJT for several reasons. One being (when last tested), it would turn off TxEnable before the end of a QSO (it wouldn't wait for that final 73 or
initiate any retries to try and get it). In response to this, Logger32 clears the Logbook Entry Window. So, if/when a message is received to log the QSO, the name has already been erased from the Logbook Entry Window. JTDX does not exhibit this annoying behavior,
and is without reservation/hesitation my recommended mode d'jour engine.
This has been the subject of numerous threads on the reflector. SeventyThree(s).
|
||
|
|
||
|
Re: Name missing in L32Lookups
Bob
Damian, to quote a former First Lord of the Admiralty, and architect of the
Gallipoli Campaign (that cost 250,000 lives), "Two Countries separated by a common language". Huh, what did you say?
I don't use WSJT for several reasons. One being (when last tested), it would turn off TxEnable before the end of a QSO (it wouldn't wait for that final 73 or initiate any retries to try and get it). In response to this, Logger32 clears the Logbook Entry Window. So, if/when a message is received to log the QSO, the name has already been erased from the Logbook Entry Window. JTDX does not exhibit this annoying behavior, and is without reservation/hesitation my recommended mode d'jour engine.
This has been the subject of numerous threads on the reflector. SeventyThree(s).
|
||
|
|
||
|
Re: Name missing in L32Lookups
Rick Ellison
As explained to me by Bob.. Yes… If you are logging anything else the name functions correctly and is logged. It is just from WSJT that it does not work correctly. If you use JTDX it is supposed to work correctly. I have not tried that yet today..
73 Rick
From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Damian M0BKV via groups.io
Just to recap. Your update solved the Name issue but now nothing transfers apart from everything being transfered when WSIT-X does it (automatically) during its logging process.
|
||
|
|
||
|
Re: Name missing in L32Lookups
Just to recap. Your update solved the Name issue but now nothing transfers apart from everything being transfered when WSIT-X does it (automatically) during its logging process.
|
||
|
|
