Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Access Violation
26-11-2021, 03:36 PM, (This post was last modified: 26-11-2021, 03:45 PM by KE4BCN.)
#1
Access Violation
Hi Jordi when using JTDX and Swisslog I started getting this error see attachments. It happens when I click on a callsign in JTDX and Swisslolog does it's lookup of the call sign. If I close Swisslog and reopen all is well. I am using Windows 11. It does not do it all the time.


Attached Files Thumbnail(s)
       
Reply
27-11-2021, 12:04 PM, (This post was last modified: 27-11-2021, 12:04 PM by EA3GCV.)
#2
RE: Access Violation
Hello,

Please send me screenshots of the REPORT tab in the JTDX Setup and also the WSJT-X UDP configuration in Swisslog. It's also VERY important you add exceptions to Swislsog and JTDX in your antivirus and also to the executables file in your firewall. Otherwise it will be looking out all the traffic, slowing down all the process or causing errors.

Best 73
Jordi, EA3GCV
Current developer of Swisslog
Reply
28-11-2021, 05:40 PM,
#3
RE: Access Violation
Hi Jordi here are the screen shots you asked for.


Attached Files Thumbnail(s)
       
Reply
02-12-2021, 12:43 AM, (This post was last modified: 02-12-2021, 12:44 AM by EA3GCV.)
#4
RE: Access Violation
Hi,

Your setup is wrong. JTDX is sending info on port 2237 and you have configured Swisslog to read from port 2334. Set 2237 here. Forwarding is only needed if you want to broadcast the same UDP packets received by Swisslog on main instance into another software (such as GridTracker). If  this is not your case, disable forwarding.

73
Jordi, EA3GCV
Current developer of Swisslog
Reply
02-12-2021, 01:25 PM, (This post was last modified: 02-12-2021, 01:33 PM by KE4BCN.)
#5
RE: Access Violation
Hi Jordi the reason for using port 2334 is that I also use JTAlert. Do your recommend a different port? Thanks


Attached Files Thumbnail(s)
   
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)