No one is saying anyone screwed up Terry, isn't the point of these forums to report bugs, I haven't seen anyone demand a fix unless you are getting it in private, a simple workaround is all that most people seem to want I am sure a fix will come in due time, And yes WSJT is a major part of the hobby...

That must be why mine isn't working, I have my WSJT names slice A slice B ect as the are for different slices on my flex, so how can we work around this,

Thanks
Trevor
EI2GLB

That would be it then, I haven't renewed my sub In a few years,

Thanks for the help,

73
Trevor
EI2GLB

Hi All

Anyone have any idea why I can't see the Bio picture on the right hand side??

I get the QRZ data but no picture, I tried changed primary source but no joy,

I use QRZ and HamQTH,

Thanks
Trevor
EI2GLB

Seems like this is one of the main bugs at present I also have this issue, but only using WSJT-X 2.1.2 using an older 2.1.0 that is modified it works correctly??


I just set everything to run as admin as I hadn't previously and it made no difference for me,


Trevor
EI2GLB

I can't attach the log file here so I will email it directly,

Thanks
Trevor
EI2GLB

I saved the log file from that window and did a search and no sign of MESSAGE_LISTENER in it??

G4POP wrote: ↑

17 Jan 2020, 18:05

Message listner is a udp inbound service in the conndctions menu, set one up to listen to the port causing the issue and watch the realtime log window in the help menu

I can find no reference to MESSAGE_LISTENER in my complete log file and that includes the port that works, here is a section of the file that references a station I am calling but his call does not enter the callsign box in Log4om 17:49:39.252 Debug: [#=z3kID5hlOqeRk$dRRNo3sYrI=][MoveNext] : ##### U...

Not that would be listening to UDP ports,

WSJT-X 2.1.2 wont work when its open on its own with Log4om, I'm only opening the 2nd program to test them side by side,

I have it set that way Terry

WSJT-X is on port 2334
Bot is on port 2333

Log4OM is set to listen to both,

I'm trying to find error's in the log file but it's not making any sense to me