Date   

locked Re: Success: QSOLogged. Keeps repeating.

HamApps Support (VK3AMA)
 

On 1/05/2021 12:39 pm, dpaschal@... wrote:
I should also mention that if I do not have JTAlert loaded, the QSO gets sent from WSJT-X to LOG4OM2 just fine.
OM (again with the non-signing)

That's your problem. You have Log4OM set to log QSOs directly from WSJT-X.

The JTAlert Help on correct Log4OM setup doesn't cover setting up Log4OM direct logging so you must have followed some other instructions to reach that end.

Turn off the logging into Log4OM direct and allow JTAlert to perform the logging and all your problems with unconfirmed logging, inaccurate B4 reporting (you haven't mentioned it, but it will be a problem) will be resolved.

de Laurie VK3AMA


locked Re: Success: QSOLogged. Keeps repeating.

dpaschal@...
 

I should also mention that if I do not have JTAlert loaded, the QSO gets sent from WSJT-X to LOG4OM2 just fine.


locked Re: Success: QSOLogged. Keeps repeating.

dpaschal@...
 

Mine was set to 5.  I set it up to 10.  When I clicked to log the QSO in WSJT-X, it never sent it to LOG4OM2 and after a few seconds, the "JTAlert : QSO to Log4OM V2 (MySql)" error message popped up again and the QSO was not in my log.


locked Re: Success: QSOLogged. Keeps repeating.

Dave Garber
 

i changed my timing in jtalert to 10 sec, not 3.  and it helped

Dave Garber
VE3WEJ / VE3IE


On Fri, Apr 30, 2021 at 9:32 PM <dpaschal@...> wrote:
I followed the setup instructions in JTAlert help file for LOG4OM2.  Now, I am getting a new error message:

JTAlert : QSO to Log4OM V2 (MySql)
Logging Warning

ERROR Message : LOG4OM V2 MySql: Unable to confirm QSO logged

NOTE: The QSO is still saved to the WSJT-X Log File.


locked Re: 2.50.1 - Callsigns window is too high!

K0GU
 
Edited

I posted on this earlier if I understand what you want. The release notes tell you why. I don't like it either but he probably has bigger fish to fry for now instead of us complaining about what are likely perceived to be cool new features by some instead of clutter for us.

Statsbar hiding: The option to hide the statusbar for windows has been
       removed. The statusbar is now always shown. This change affects the
       new Activity, Callsigns & Messaging windows introduced with 2.50.0."

--
73,  Jay  K0GU


locked Re: Success: QSOLogged. Keeps repeating.

dpaschal@...
 

I followed the setup instructions in JTAlert help file for LOG4OM2.  Now, I am getting a new error message:

JTAlert : QSO to Log4OM V2 (MySql)
Logging Warning

ERROR Message : LOG4OM V2 MySql: Unable to confirm QSO logged

NOTE: The QSO is still saved to the WSJT-X Log File.


locked Typo in Context Menus window

Jim Reisert AD1C
 

I think the choice under "Add to Wanted list" should be "Remove from Wanted List", not Ignored list.

2021-04-30_19-24-21.png

--
Jim Reisert AD1C, <jjreisert@...>, https://www.ad1c.us


locked Re: Greetings from Japan; Japanese language sound file revision request

shibata.naoki@...
 

okay, will make a text file and put my translation suggestions filein Kanji for the mentioned alert announce. note that a few phrases in Japanese alert - CQ and DXCC - are used as loaned words, just pronouncing in Japanese accents. shoild I spell in ascii or SHIFT_JIS(or maybr UTF)?
will do it over the weekend... is it okay to post a message with an attachment file?

if not appropriate, please let me know what I should do to send the file.

best 73, Nicky/JH8JNF


locked Re: Success: QSOLogged. Keeps repeating.

dpaschal@...
 

That worked.  You can close this one.  I had the "Resend WSJT-X UDP packets" enabled.


locked 2.50.1 - Callsigns window is too high!

Jim Reisert AD1C
 

Thanks for the updates in 2.50.1

In 2.50.0, I could make the bottom half of the Callsigns window shrink
to almost nothing. I can't do this in 2.50.1:

* Under Windows, "Show UTC Clock", "Show DT Median" and "Show DX Call"
are all UNCHECKED
* Under Callers, all three boxes are UNCHECKED

Yet, I'm still seeing the count of callers and a 0 next to it. I also
see the gear icon in the bottom-right corner. I have moved the
horizontal bar as far down as I can, but these fields are still
visible.

See image attached.

--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, https://www.ad1c.us


locked Re: Independent audio alert s #FT8

Pat N6PAT
 

Laurie,

I tried using the Decodes window with 2 active instances (80 and 40 meters) and it seems to only list alerts from the first instance (80 meters).  It would need to be able to list alerts from any of the active instances.

Pat


On Friday, April 30, 2021, 1:29:07 PM EDT, Laurie, VK3AMA <hamapps.support@...> wrote:




On 30/04/2021 11:08 pm, Pat N6PAT via groups.io wrote:
> The reason I ask is that with my Flex 6700 I run many instances
> simultaneously for different bands. If I could specify custom band
> specific audio alerts for wanted DX , States, etc. such as "Wanted DX
> on 10 meters" that would save me having to search each band in WSJT-X
> for the wanted DX if the time interval elapses and the wanted call
> sign disappears from the call sign window.

Try using the Decodes window. It provides a single display of decodes
from all JTAlert instances. Set it to display only Alerted decodes and
perhaps move the Band column over adjacent to the Callsign Column and if
the other data is of no interest hide those columns. End result is a
display of Callsigns and Bands of decodes generating Alerts.

de Laurie VK3AMA







locked Re: Double Click Ver 2.50.1?

Glen Jenkins WB4KTF
 

Hello Joe,
That was the problem, the 'Accept UDP requests' was NOT checked.
Now double click works.
--
Glen, WB4KTF, Austin, TX


locked Re: v2.50.1 Second or third FT8 contact logged as FT8 with FT4 sub-mode.

Ron W3RJW
 

Yes, the random nature has me thinking it's a RFI problem if that's possible.  Let me do a little more testing.  Sprinkle a few more chunks of ferrite around. 

The only thing confusing is I never had a problem like this with any other version including 2.50.0.

I'll send the log now.

73
Ron, W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.4.0 rc4, JTAlert 2.50.0, HRD Deluxe v6.7.0.323
FTdx-3000, SignaLink USB


locked Re: Double Click Ver 2.50.1?

Joe Subich, W4TV
 

In WSJTX -> Settings -> Reporting is "Accept UDP Requests" checked?

73,

... Joe, W4TV

On 2021-04-30 7:05 PM, Glen Jenkins WB4KTF wrote:
I just installed Version 2.50.1. This is the first installation of 2.50 for me as I awaited the first revision.
I seem to have everything up and running but cannot get 'Double Click' in the Callsign's Window to function to call a station.  I do have Double Click enabled, as per attached image.  What am I missing to get it activated?
--
Glen, WB4KTF, Austin, TX


locked Double Click Ver 2.50.1?

Glen Jenkins WB4KTF
 

I just installed Version 2.50.1. This is the first installation of 2.50 for me as I awaited the first revision.
I seem to have everything up and running but cannot get 'Double Click' in the Callsign's Window to function to call a station.  I do have Double Click enabled, as per attached image.  What am I missing to get it activated?
--
Glen, WB4KTF, Austin, TX


locked Re: JTAlert 2.50.1 does not receive from WSJT-X - Callsigns, Activity and Band heat windows don't open

Joe Subich, W4TV
 

As far as I can see the UDP settings and the WSJT-X program location are correct.
Enable Multicast UDP. See the "WSJT-X UDP Setup" section of the JTAlert
(Main) Help file.

It is likely that HRD is capturing the UDP port and preventing UDP
messages from reaching JT-Alert from WSJTX.

73,

... Joe, W4TV


On 2021-04-30 6:04 PM, Frode Igland wrote:
Running WSJT-X 2.3.1 and just downloaded JTAlert 2.50.1, but JTAlert does not receive decodes from WSJT-X. Everything worked fine with v2.50.0.
I am not able to open the Callsigns window, not the Activity and Band heat windows. The Decodes window opens but contains nothing.
The title bar of the Main JTAlert window shows reads the JTA version data, my call sign, my log book, etc. but it does not contain band or mode data, reading "[ ???m,, HRD6+,#1]".
After a rather long while I receive an error message telling that JTALert don't communicate with WSJT-X:
Unable to communicate with the WSJT-X process.
UDP Port : 2237
IP Address : 127.0.0.1
Values read from WSJT-X config file...
C:\Users\fi\AppData\Local\WSJT-X\WSJT-X.ini
WSJT-X Detected Instance...
Process Window Title : WSJT-X v2.3.1 by K1JT, G4WJS, and K9AN
Process Command Line : "C:\WSJT\wsjtx-2.3.1\bin\wsjtx.exe"
Decode alerts and logging will be unavailable until corrected.
As far as I can see the UDP settings and the WSJT-X program location are correct. The UDP settings have not changed since they were orignally set when I installed JTAlert several years and many versions ago.
Any ideas?
73 Frode LA6VQ


locked Re: v2.50.1 Second or third FT8 contact logged as FT8 with FT4 sub-mode.

HamApps Support (VK3AMA)
 

On 1/05/2021 6:30 am, Ron W3RJW via groups.io wrote:
I'm having a problem with 2nd or 3rd FT8 contact in a run being logged with a FT4 submode. I did not go on from there. Happened more then once after pausing to check things and then making contacts again. I also did not try any other modes yet.

I log to HRD from JTAlert. Settings as normal (removal of ADIF compliant option noted).   Did I miss something else ?
--
73
Ron, W3RJW

Send me an ADIF export of your HRD Logbook.
Send it to me direct, not via this group, to VK3AMA.HamApps [at] gmail.com
Also, use the "Help" -> "Contact Support" menu, on the main JTAlert window, to send me your JTAlert files for analysis.

The adif compliant settings removal shouldn't matter. If there was a defect I would expect all QSOs logged to be affected, not random entries. Something unusual is happening.
 
FWIW, none of the HRD users on the Test Team have reported this.

de Laurie VK3AMA


locked Re: 2.50.1

HamApps Support (VK3AMA)
 

On 1/05/2021 6:45 am, K0GU wrote:

" - Statsbar hiding: The option to hide the statusbar for windows has been
       removed. The statusbar is now always shown. This change affects the
       new Activity, Callsigns & Messaging windows introduced with 2.50.0."


I presume this is the reason I can't get rid of the line with the gear at the bottom of the call window? I had deleted it in the last version and used F2 to get to the controls.
--
73,  Jay  K0GU

Yes.

de Laurie VK3AMA


locked Re: Success: QSOLogged. Keeps repeating.

HamApps Support (VK3AMA)
 

On 1/05/2021 7:05 am, dpaschal@... wrote:
Using the new version, I keep getting the completion pop-up when I log a successful QSO.  It is getting logged once in my log but I can't stop the pop-up unless I close JTAlert and re-start it.

OM,

Sounds to me like JTAlert is getting repeated UDP QSO logged messages. Make sure you don't have the "Resend WSJT-X UDP packets" setting set to use the same port as WSJT-X (2237 typically). If its enabled, try turning it off, it is likely not needed. See the "Applications -> WSJT-X / JTDX" section of the main JTAlert Settings window. If that is not enabled, perhaps you have Log4OM mis-configured and it is reseeding the UDP packets to port 2237. The JTAlert help has simple instructions for correct LOg4OM setup.

de Laurie VK3AMA
 


locked Re: Logging Warning

HamApps Support (VK3AMA)
 

On 1/05/2021 7:52 am, Gilles beaulieu wrote:

Hi Laurie, I uploaded the newest version and worked flawlessly for a few hours. Now I'm getting a Logging Warning.

Any ideas as to where to look?

Thanks & 73

Gilles - VE3NPI


Does the QSO get logged?
If it does, that check that JTAlert is still pointing at the correct ACLog log file.

If QSOs are no longer getting logged that suggests that something has changed. Your PC protection software perhaps?

If you haven't done so already, a PC restart wont hurt.

de Laurie VK3AMA

901 - 920 of 35434