Ed62

Hi Mark, Good news! FS-ATC Chatter is showing connected so it was probably the different IP Addresses that were causing the problem. I'm also hearing chatter related to my tuned frequency in the sim. I consider my problem solved now. Thanks very much for your help. Kind Regards, Ed PS: The chat sounds great!

Hi Mark, Yes, all the other apps are connecting to the server, but they use FSUIPC WideFS or they have there own auto connect files. This is my first attempt at using Simconnect from the client with MSFS2020. I'll double check this though, but yesterday they all connected fine. I've just gone through all my inbound and outbound rules on server and client and all seems fine. FS-ATC is allowed through the firewall on both server and client, although I have Firewall on both client and server turned off at the moment. I'll change the address on the server to match that of the simconnect.cfg on the client, maybe that's the issue. Will get back to you on how it goes. Thanks so much for your guidance. Kind Regards, Ed

Hi Mark, I tried to follow the User Guide as best I could. I will start off with the first thing I did. As per User Guide I changed the name to simconnect.cfg and pointed it towards the server hosting MSFS2020. I left the port at 500. I also left the simconnect.cfg file in the folder it was in. The first image is the changes to the simconnect.cfg. Second image is the location where it resides. Are these two items correct? https://imgur.com/M3tnoW2 https://imgur.com/73GeJgP https://imgur.com/7anTRJO I added this to simconnect.xml on server and pointed it to FS-ATC client. https://imgur.com/tqy4ihg This is where my simconnect.xml file resides on MSFS server I had though I had followed the User Guide correctly, but obviously I have made an error somewhere. Do all of these things look ok? I'm not sure of port 500, but I have opened it to incoming and outgoing on both client and server. I hope the image locations work as I was unable to use the 'Insert image from URL' button. Kind Regards, Ed

Hi, It's been such a long time since I've done anything with simconnect files. The file I altered was the simconnect.xml in the MSFS root directory as per the instructions manual that came with FS-ATC Chatter. I didn't realize there were more files in the Documents folder. I'll have a look there and see what's in there. EDIT: Pretty much all my other applications connect through WideFS. I cannot find any simconnect files in my Docyments folders.

Hi, I recently purchased FS-ATC Chatter. I've installed it on the same client that I have P2ATC installed. P2ATC connects to the simulator and works fine, although I haven't set it up to use FS-ATC Chatter yet. The problem I have is getting the FS-ATC Player to connect to the simulator. I've changed the address in the FS-ATC Simconnect.cfg folder to the address of the server that FS2020 resides on. I left the port at 500 for now as I know it's open through the firewall. Does this folder have to be placed elsewhere or does it stay in the main FS-ATC folder? I've also set sharing to the FS-ATC folder. I looked at the tutorial and it gave a location to show how to set up the Simconnect.xml file, so I added the example and changed the address to that of my client and the port to 500. I still can't get a connection to the simulator so I'm asking for a little help to solve the issue I'm having. I have lots of apps on this client connecting to the simulator so I'm quite sure it's not a network issue and pretty sure that I just need a little more clarification on how to setup simconnect correctly between client and server. Kind Regards, Ed B.

Thanks for the quick reply Dave. I'm flying the Prosim 738. It's good to see there is an easy solution. If I don't find another solution, adjusting the deviation in the config should work just fine. Kind Regards, Ed PS: I wish the trial was a little longer. I still haven't solved the PTT and Sayit keysends, but I am working on a solution for that in John Dowson's FSUIPC7 forum so I'm not looking for a response here.

Hello Everyone, I'm currently on day 8 of 10 day trial. For the most part I have only 3 issues. The one issue I noticed yesterday, due to ATC asking me to expedite my climb to a certain flight level which my Altitude tape showed I was already at the correct FL, in this case FL220. AP was also set for FL220 and EFIS was set to Standard. Glancing at the altimeter in the P2A window it still showed 29.92 and the altitude showing was FL21.565 which was 565 feet below what my PFD tape was showing. Not sure why this happened. Today the Barometric pressure from ATIS was 29.65 so on my EFIS I set 29.65, however the pressure setting in P2A did not change so I had to click on it to open the number menu, typed in 21.65 and then entered it. P2A then showed the correct pressure. During my preflight the pressure changed again, and again it did not change in the P2A screen after I made the change on my EFIS so I to entered it manually. Is it normal to have to input the pressure setting into P2A each time it changes? Shouldn't it see the pressure setting on my EFIS and change automatically in P2A just like the radio frequencies do? I'm using MFFS2020. I am using NOAA weather in P2A and I believe in Sim as well. I import my plans using Simbrief. I'm also running P2A on a client. Thanks for any help offered. I think it's probably a setting I have missed. Ed B.