If your referring to JTAlert rather than WSJT-X, try using the Decodes Window. Each of the Wanted types, Dxcc, State, Cont, Grid, etc, have their own column and if the decode generates one or more ale

#FT8

Larry, in WSJT-X all those colours are user definable. Most colour blindness is an inability to differentiate two or three hues, others that are distinguishable can be selected. The highlights in WSJT

#FT8

Well.. Not that it right solution to help with color blindness, just a thought. The colors represent a lot of things, whether you work the operator before, New grid, New prefix, DX, someone calling/an

#FT8

Hi Larry, I'm don't understand what "A symbol that could added to or added to a colored line?" entails. Is there some specific part of the WSJT-X user interface that is causing them problems? 73 Bill

#FT8

I searched for "Color Blind" and only found 2 messages that did not answer my question. I have a friend who is Color blind to some extent and he is attempting to use WSJT-X & JT Alarm. Is there or cou

#FT8

Is the callsign in the wsjtx window showing up in jtalert? If yes then recheck user name and password for eqsl. If not then it is not hearing on 2237. Did you restart both software after making change

#FT8

Just using the native log in wsjt-x and enabled eqsl in jtalert with udp 2337 73, Barry K6ST Nevada Section Youth Coordinator ARRL (American Radio Relay League) arrl.org The national association for a

#FT8

What logging program are you using sent by my LG phone

#FT8

Attached was the jtalert error screenshot. When I changed the udp in jtlaert to 2337, and logged a qso,in wsjt-x then no error message came up. But the qso logged in wsjt-x never showed up,in eqsl. 73

#FT8

To be clear, what I am looking for is instructions to integrate jtalert with qso so when a qso is logged in wsjtx, it is automatically uploaded to Eqsl also, Thanks, 73, Barry K6ST Nevada Section Yout

#FT8

Thanks, I start wsjt x first. The error message was from jtalert I believe. 73, Barry K6ST Nevada Section Youth Coordinator ARRL (American Radio Relay League) arrl.org The national association for ama

#FT8

Roert, Is this a JT-Alert message? Which program are you starting first, WSJT-X or JT-Alert?? Neil, KN3ILZ

#FT8

I am doing something wrong. Program tells me to start up as for ft8. I press configurations and due to my past efforts, configurations is filled with many choices to select. I do not seem to get past

#FT8

Actually I never checked Log4OM but Log4OM2 does look like you can select the contest ID and it may well parse it. I just didn't think to even check for that. Mike

#FT8

N3FJP Contest loggers parse the SRX_STRING & STX_STRING fields to pull the class and sect data out or other fields depending on the Contest. If a general purpose logger like Log4OM has a selector to s

#FT8

Nope...doesn't appear there's any attempt to parse that info. Don't know what all the other loggers do but probably the same behavior I'd think. They just put in what they receive without addiontal in

#FT8

That's because that data, "contest_id", "class" & "arrl_sect" are not included in the wsjtx UDP QSO Logged message (#5) which JTAlert has always used for logging. Only the SRX_STRING & STX_STRING fiel

#FT8

That was my point...that data isn't being carried along.... Log4OMV2 also had just the 1D/1E which should be blank. That is not a signal report. Mike

#FT8

My log4om log record had only 1D or 1E etc in both the RST sent and RST received. The STX and SRX strings were all blank in every one and the contest ID was blank. maybe the insert needed the contest

#FT8

Yup...but the STX_STRING is correct....the RST_RCVD and RST_SENT are supposed to be signal reports...not contest exchange information. There is no RST for field day exchanges so it really ought to be

#FT8