FYI I run an old Windows 7 PC and have no issues with latest WSJTX, JTAlert or the .Net components needed. Don’t assume that someone says it will not work that it won’t. May be other reasons unknown t

Glen I never use the spot list - I have DXMaps set to default to the map format and it works a treat. Just now it is quiet in the UK but NA is pretty busy: https://www.dxmaps.com/spots/mapg.php?Lan=E&

#HamSpots

Bob First off I suspect this is nothing to do with JTAlert - more a WSJT-X? query - their support is at: https://groups.io/g/WSJTX You may want to expand on the question you ask. Are you using WSJT-X

See message posted yesterday - version 2.50.2 has the solution - issue with MS upgrade Tom GM8MJV

The IP address is set in WSJTX - Settings - Reporting Tab. JTAlert gets the details from wsjtx Tom GM8MJV

Dan Suggest you do a manual check to find a couple that have not come through and then see what they have in common - maybe you have a date restriction in JTA, different mode e.g. ssb/cw where jta is

Randy If you want fire over the file to me via e-mail - address ok in QTZ - will play and see what is what - It really should be straight forward Regards Tom GM8MJV

Randy I suspect its this step Changing the name MAY have renamed the file: wsjtx_log.166144.20210515191035.adi When you look at the listing in Open Log Directory does it show the extension? In the fol

Randy Want to expand further - ‘wont recognise’ is a bit vague - does aclog not recognise it? Wsjt_x? If it is an adi file and put in correct location it will work (pretty sure eqsl/lotw generate adi

Looks like you don’t have comms between wsjt-x and JTAltert - the ????m in the header - that should show the band you are on - ??? means no comms. Take Log4OM OUT of the equation - it ay be clashing o

At a guess - try updating wsjt-x to 2.4rc3 - wonder if wsjt-x has hit the ‘will not work after xxx. date. Tom GM8MJV

Sorry Dave It will not work - Laurie has been in touch with Christo (Author of MSHV) pointing out areas needing tidied up but he has refused to make changes. He will happily support new modes develope

#HamSpots

Norman You could just (under your own ID) run wsjt-x from desktop, then JTAlert from desktop - it will take the batch file and DXLab Suite out of the equation. The other thing to check if are you runn

Norman UN-Tick the 'Resend WSJT-X UDP Packets' in JTalert. JTA will automatically work out the settings - having that option ticked will cause a loop. Tom GM8MJV

Lot of playing - now seems to be working ok. I have no idea what I had wrong but all freq’s seem to match up. Thanks for letting me know it should do it - that allowed me to move forward Tom

#FT8

Hmm I have wsjtx -> Setting -> Freq - Station info Band Offset 13cms -2,174.000 000 On main wsjt screen select 13cms from pull down - Freq Box shows 146.985 (ok it is in red as that is a beacon I am l

#FT8

Thanks Laurie & Mike Will post over on wsjtx Tom GM8MJV

#FT8

Dave MSHV and JTAlert - how did you manage that? - I was under the belief that JTAlert does not support MSHV due to MSHV not being standard on the UDP messages. Tom GM8MJV

All Not sure if this can be fixed/worked around - will depend I suspect on UDP message content Testing a 13cm (2320) system - wsjt-x allows me to enter transverter offset so it knows what to set the r

#FT8

Which version of JTAlert are you running? Tom GM8MJV