Log4OM

hb9fpc wrote: 26 Apr 2020, 10:21 Sorry about that. I wasn´t meant as an offense. But changing the source of information is probably something I could figure out by myself. I assumed that the advice was based on some kind of background knowledge like changes in the code etc. Obviously it wasn´t. Thanks for the support anyway. By the way: I checked and changing the info provider to hamqth in 2.5.0.0 didn´t help in my case. (Yes, I registered an acount with them as well). I went back to 2.4.0.0 and remed out the version check in config.ini. Everything is fine now. Thanks again from a supporter of your great software.

Please send me your logfile which is located at C:\Users\YOUR USER NAME\AppData\Roaming\Log4OM2\log

It should still have the 2.5.0.0 information in it which would help me identify the issue

DO NOT post it on the forum send it to me via email at g4pop (AT) arrl.net

With great help of Terry G4POP we finally could solve the mystery/problem. Thanks a lot, Terry. The solution: Either size the windows of both programs to fit the screen, or use dual monitors and seperate the windows! Background: LOG4OM 2.5.0.0 does not communicate with WSJT-X when minimized. I realized that I used the software differently in an unreflected manner, depending on the situation. Let´s assume, both programs are running with somehow overlapping windows. From time to time I minimized LOG4OM in order to work in WSJT-X. In other cases I just clicked into the WSJT-X window. I did not realize that this could affect the behaviour of LOG4OM. When working in 2.4.0.0 the communication between both programs was not affected. In 2.5.0.0. the communication would stop when I minimize LOG4OM.

The new version 2.6.1 keeps giving me problems to communicate with QRZ not as much as with 2.5.0 but it still gives problems with some contacts, I return to 2.4.0 which is perfect.

EA1IVQ wrote: 16 May 2020, 19:48 The new version 2.6.1 keeps giving me problems to communicate with QRZ not as much as with 2.5.0 but it still gives problems with some contacts, I return to 2.4.0 which is perfect.

Angel,

You have made a number of posts about your problems with QRZ, yet you have not yet taken the time to gather and detail all your information and submit a formal support request so that the team can help you get to a good resolution.

Your comments are vague without needed detail for trouble-shooting.

As many have already suggested you need to download the "current" User Guide and follow the precise suggestions for connections of WSJTx, JTDX and JTAlert ... all depending upon which of those APPs you are using. That is a starting point and then any/all information related to the manual or auto uploads to the external services including QRZ.

Please take the time and do that "gathering of information" and we will do all we can to resolve your problems.

Taking the stance you are taking is not in the least giving us an opportunity to help you.

I see that you do not like the comment, and be careful not to disregard the opposite, the program is great. If you read from the first message you will see that I have downloaded the User Guide as recommended previously, but the problem was not solved, this as you will see not only happens to me there are more affected. I think that instead of being offended if you are a developer of the program and you are interested in seeing where the problem may be, tell me that you need to see the file etc. and I send it to you without any problem.

EA1IVQ wrote: 16 May 2020, 19:48 The new version 2.6.1 keeps giving me problems to communicate with QRZ not as much as with 2.5.0 but it still gives problems with some contacts, I return to 2.4.0 which is perfect.

Communicating with QRZ in what way

1.. call lookup issues?

2. QSO upload either auto or manual?

A fuller description enables us to assist you

I use JTDX rc 150 64 bits bitand JTAlert with log4om 2 and tell you that in v 2.4.0.0 when selecting a new DX in JTDX automatically the log40m 2 shows on the main screen the data of the DX and its QRZ.com photo perfectly and instantly, but In the new v2.5.0.0 and 2.6.1.0 it fails, it does not always work or refresh correctly between one DX and another.

Windows 10 64Bits
TQSL 2.5.1

I am a QRZ.com paying member with subscription on payday.

Thanks for your interest, I can make a video if necessary.

EA1IVQ wrote: 18 May 2020, 11:11 I use JTDX rc 150 64 bits bitand JTAlert with log4om 2 and tell you that in v 2.4.0.0 when selecting a new DX in JTDX automatically the log40m 2 shows on the main screen the data of the DX and its QRZ.com photo perfectly and instantly, but In the new v2.5.0.0 and 2.6.1.0 it fails, it does not always work or refresh correctly between one DX and another.

The set up for JTAlert/JTDX changed between Log4OM version 2.4 and the 2.5 release onward. This new setup is fully documented in the latest user guide.

If you decide that you would like to use the latest version of Log4OM instead of the redundant version 2.4, then after the update please also update your Log4OM/JTDX/JTAlert settings in accordance with the instructions in the latest release of the user guide.

The latest user guide can be accesses via 'Force download' in the help/user guide menu or direct download from our web site.

I have just checked that the interface between the above programs is functioning correctly and can confirm that everything is working as it should with the settings detailed in the latest user guide.

Thank you very much I will make the direct connection of Jtdx to log4om2 as the guide says without using JTAlert.