bradrcfii

yes, as I indicted, I had a working localizer. Brad

I was able to tune the radios to the proper localizer and received lateral guidance but I saw no glide slope indicator. What might I being wrong? Thanks, Brad

In FSX, I could hit a buttons on lets say the NGX CDU quickly and the display would catch up. Now with Prepared, I have to hit a button, wait for the charactor to display and then I am able to hit the next button. For example, I might put in a cost index of 55 clicking 5 and then 5 very quickly. Prepar3D will not pick up the second 5 entry. I havo wait, let it display the first 5 before I can enter the second. Is there a CFG entry for this or is this the way Prepar3d is? Thanks, Brad

Just to close out this thread....I built a new Z170 machine using the new SkyLake CPU. Created a new Homegroup and a funny thing happened, simconnect and all my remote programs including ASN and VPilot worked first try. Who knows what was stopping me with the old machine? I thought I knew what I was doing. By the way, running the Skylake at 4.8Ghz makes Prepar3d fly, pardon the pun. The irony is that I really do not need a cleint machine any more. Brad

OK got it. I will open notepad and type in the lines and save it with a .cfg extension in the coorect location, users/flight2/documents Thanks, Brad

I am going to use the same font found in the xlm file for the client config file and give that a try. I will also place the config file in the root application program folders. I am trying to get both ASN and VPilot up on the client. The ASN network doc is pretty good so I am surprised I am having so much trouble especially since i had it working for FSX. I really appreciate you guys helping. Brad

Dropbox location for simconnect data: https://www.dropbox.com/sh/tmv6mr46gnkrmng/AABYLmgWsZ3ASsg1nxbjD5T0a?dl=0 I think we have made progress. The server nstat shows port 50,000 listening but the client does not. Maybe a simconnect install issue. The ESP version will not install. What would cause simconnect to start to run on the client? Thanks, Brad

The firewalls are turned off with the exception of the router. I will try a higher port but you mention three different places. I think we might be zeroing in on the problem becuase I can only think of two places, the XML file and the CFG file on the client at users/mydocuments. Am I missing a file? thanks, Brad

Srtill no luck. Stat does not show any activity listening on port 5000 on either machines.

OK, I will put your xml file back in.

Hi Chris, I loaded your xml file. I changed one parameter from local to "global" and used port 5000. I do not know what IP address 127.0.0.1 is showing on nstat? I have my router only to use ip address starting at 10.0.0.1 to 100. 10.0.0.30 is my sim server and 10.0.0.20 is my client. I noticed that nstat does not show port 5000. The other strange item is the FSX program showing in my uninstall list from the control panel. If I try to uninstall it, I get an error. I think it was placed there by one of the simconnect.msi installation programs. The following dropbox location shows examples of all my files and sestet for both computers. https://www.dropbox.com/sh/1cuqnur0eqqkqze/AACd4dkTbiOW-uVFZAHFkJoza?dl=0 Brad

Does the order of the simsonnect installs matter. Some we updates.

The IPConfig files from both machines can be found here. https://www.dropbox.com/sh/fimci6peppmdk6l/AACOL0KncbWkIg2q16F4VBZKa?dl=0 I also show where the xml, cfg and ini files are located and what they look like. Thanks, Brad

The xml file on the server always had it's own IP address, in this case, 10.0.0.30. I have never ran an xml file on the client. Would not know where to put it. How did you come to these conclusions?

1) I made the registry change using command and rebooted both machines 2) I installed the ESPv1 MSI file. (does the order of the MSI files make a difference) 3) I reinstalled FSUIPC-WideFS now connects 4) I moved the ini file to the correct location and logging now displays. Task Manager shows this program as "SimConnect data logging" a good sign. Is there any port forwarding involved? The following link is a dropbox location showing you the files and their locations. The nstat data does not seem to show port 500 defined in the xlm and cfg files. https://www.dropbox.com/sh/fimci6peppmdk6l/AACOL0KncbWkIg2q16F4VBZKa?dl=0 Concerning Vpilot, I run the traffic proxy program on the server that connects and try to run Vpilot on the client that does not connect to the simulator. About ready to try FSINN. Thanks for your help thus far. I really appreciate it. Brad

The sim was off and I am running Windows 7. I disabled IPv6 on both machines and in my router. I am not sure what you mean to do by "manually disable" firewall service. I did close the windows firewall service in the task manager. I made sure the firewall is turned off in the control panel as well. I just realized that i am not getting debug data. I have the simconnect.ini file with the console set to =1 yet I am receiving nothing. I changed the port to 500 in both files since that is what I used running FSX. NSTAT with the sim running. 10.0.0.20 is the client machine. Microsoft Windows [Version 6.1.7601] Copyright © 2009 Microsoft Corporation. All rights reserved. C:\Users\Brad>netstat -an Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:80 0.0.0.0:0 LISTENING TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:445 0.0.0.0:0 LISTENING TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING TCP 0.0.0.0:47984 0.0.0.0:0 LISTENING TCP 0.0.0.0:47989 0.0.0.0:0 LISTENING TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING TCP 0.0.0.0:49158 0.0.0.0:0 LISTENING TCP 0.0.0.0:49167 0.0.0.0:0 LISTENING TCP 0.0.0.0:49185 0.0.0.0:0 LISTENING TCP 10.0.0.30:139 0.0.0.0:0 LISTENING TCP 10.0.0.30:445 10.0.0.20:49155 ESTABLISHED TCP 10.0.0.30:49155 10.0.0.20:49158 ESTABLISHED TCP 10.0.0.30:49243 66.150.99.92:80 TIME_WAIT TCP 127.0.0.1:7789 0.0.0.0:0 LISTENING TCP 127.0.0.1:7789 127.0.0.1:49168 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49169 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49173 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49174 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49175 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49176 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49177 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49178 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49179 ESTABLISHED TCP 127.0.0.1:9990 0.0.0.0:0 LISTENING TCP 127.0.0.1:23401 0.0.0.0:0 LISTENING TCP 127.0.0.1:49168 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49169 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49173 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49174 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49175 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49176 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49177 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49178 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49179 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49181 127.0.0.1:65001 ESTABLISHED TCP 127.0.0.1:65000 0.0.0.0:0 LISTENING TCP 127.0.0.1:65001 0.0.0.0:0 LISTENING TCP 127.0.0.1:65001 127.0.0.1:49181 ESTABLISHED TCP [::]:80 [::]:0 LISTENING TCP [::]:135 [::]:0 LISTENING TCP [::]:445 [::]:0 LISTENING TCP [::]:2869 [::]:0 LISTENING TCP [::]:5357 [::]:0 LISTENING TCP [::]:49152 [::]:0 LISTENING TCP [::]:49153 [::]:0 LISTENING TCP [::]:49154 [::]:0 LISTENING TCP [::]:49155 [::]:0 LISTENING TCP [::]:49158 [::]:0 LISTENING TCP [::]:49167 [::]:0 LISTENING TCP [::]:49185 [::]:0 LISTENING UDP 0.0.0.0:500 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:4500 *:* UDP 0.0.0.0:5355 *:* UDP 0.0.0.0:61600 *:* UDP 0.0.0.0:63773 *:* UDP 0.0.0.0:63775 *:* UDP 0.0.0.0:63777 *:* UDP 0.0.0.0:63845 *:* UDP 0.0.0.0:63853 *:* UDP 10.0.0.30:137 *:* UDP 10.0.0.30:138 *:* UDP 10.0.0.30:1900 *:* UDP 10.0.0.30:5353 *:* UDP 10.0.0.30:50002 *:* UDP 127.0.0.1:1900 *:* UDP 127.0.0.1:44301 *:* UDP 127.0.0.1:48200 *:* UDP 127.0.0.1:48201 *:* UDP 127.0.0.1:48202 *:* UDP 127.0.0.1:50003 *:* UDP 127.0.0.1:52454 *:* UDP 127.0.0.1:56832 *:* UDP 127.0.0.1:56833 *:* UDP 127.0.0.1:56834 *:* UDP 127.0.0.1:60674 *:* UDP 127.0.0.1:63846 *:* UDP 127.0.0.1:63847 *:* UDP 127.0.0.1:63852 *:* UDP 127.0.0.1:65000 *:* UDP [::]:500 *:* UDP [::]:3702 *:* UDP [::]:3702 *:* UDP [::]:3702 *:* UDP [::]:3702 *:* UDP [::]:4500 *:* UDP [::]:63774 *:* UDP [::]:63776 *:* UDP [::]:63778 *:* UDP [::]:63854 *:* UDP [::1]:1900 *:* UDP [::1]:5353 *:* UDP [::1]:50001 *:* C:\Users\Brad>

Microsoft Windows [Version 6.1.7601] Copyright © 2009 Microsoft Corporation. All rights reserved. C:\Users\Brad>netstat -an Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:80 0.0.0.0:0 LISTENING TCP 0.0.0.0:135 0.0.0.0:0 LISTENING TCP 0.0.0.0:445 0.0.0.0:0 LISTENING TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING TCP 0.0.0.0:47984 0.0.0.0:0 LISTENING TCP 0.0.0.0:47989 0.0.0.0:0 LISTENING TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING TCP 0.0.0.0:49158 0.0.0.0:0 LISTENING TCP 0.0.0.0:49165 0.0.0.0:0 LISTENING TCP 0.0.0.0:49185 0.0.0.0:0 LISTENING TCP 10.0.0.30:139 0.0.0.0:0 LISTENING TCP 10.0.0.30:49225 23.48.107.31:80 TIME_WAIT TCP 10.0.0.30:49226 23.48.107.32:80 TIME_WAIT TCP 10.0.0.30:49227 23.48.107.31:80 TIME_WAIT TCP 10.0.0.30:49228 23.48.107.32:80 TIME_WAIT TCP 10.0.0.30:49229 23.48.107.31:80 TIME_WAIT TCP 10.0.0.30:49230 23.48.107.31:80 TIME_WAIT TCP 10.0.0.30:49231 23.48.107.32:80 TIME_WAIT TCP 10.0.0.30:49232 96.17.164.144:80 TIME_WAIT TCP 10.0.0.30:49233 96.17.164.144:80 TIME_WAIT TCP 10.0.0.30:49234 96.17.164.144:80 TIME_WAIT TCP 10.0.0.30:49235 216.206.30.43:80 TIME_WAIT TCP 127.0.0.1:7789 0.0.0.0:0 LISTENING TCP 127.0.0.1:7789 127.0.0.1:49168 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49172 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49173 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49174 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49175 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49176 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49177 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49178 ESTABLISHED TCP 127.0.0.1:7789 127.0.0.1:49179 ESTABLISHED TCP 127.0.0.1:9990 0.0.0.0:0 LISTENING TCP 127.0.0.1:23401 0.0.0.0:0 LISTENING TCP 127.0.0.1:49168 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49172 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49173 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49174 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49175 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49176 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49177 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49178 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49179 127.0.0.1:7789 ESTABLISHED TCP 127.0.0.1:49181 127.0.0.1:65001 ESTABLISHED TCP 127.0.0.1:65000 0.0.0.0:0 LISTENING TCP 127.0.0.1:65001 0.0.0.0:0 LISTENING TCP 127.0.0.1:65001 127.0.0.1:49181 ESTABLISHED TCP [::]:80 [::]:0 LISTENING TCP [::]:135 [::]:0 LISTENING TCP [::]:445 [::]:0 LISTENING TCP [::]:2869 [::]:0 LISTENING TCP [::]:5357 [::]:0 LISTENING TCP [::]:49152 [::]:0 LISTENING TCP [::]:49153 [::]:0 LISTENING TCP [::]:49154 [::]:0 LISTENING TCP [::]:49155 [::]:0 LISTENING TCP [::]:49158 [::]:0 LISTENING TCP [::]:49165 [::]:0 LISTENING TCP [::]:49185 [::]:0 LISTENING TCP [fe80::6c6c:aebf:ca03:a406%17]:445 [fe80::9503:fed9:67a8:a1c0%17]:5245 8 ESTABLISHED UDP 0.0.0.0:500 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:3702 *:* UDP 0.0.0.0:4500 *:* UDP 0.0.0.0:5355 *:* UDP 0.0.0.0:50979 *:* UDP 0.0.0.0:56426 *:* UDP 0.0.0.0:58890 *:* UDP 0.0.0.0:58892 *:* UDP 0.0.0.0:62253 *:* UDP 10.0.0.30:137 *:* UDP 10.0.0.30:138 *:* UDP 10.0.0.30:1900 *:* UDP 10.0.0.30:5353 *:* UDP 10.0.0.30:63903 *:* UDP 127.0.0.1:1900 *:* UDP 127.0.0.1:44301 *:* UDP 127.0.0.1:48200 *:* UDP 127.0.0.1:48201 *:* UDP 127.0.0.1:48202 *:* UDP 127.0.0.1:50978 *:* UDP 127.0.0.1:56427 *:* UDP 127.0.0.1:56428 *:* UDP 127.0.0.1:56429 *:* UDP 127.0.0.1:56430 *:* UDP 127.0.0.1:56431 *:* UDP 127.0.0.1:59774 *:* UDP 127.0.0.1:63904 *:* UDP 127.0.0.1:63937 *:* UDP 127.0.0.1:65000 *:* UDP [::]:500 *:* UDP [::]:3702 *:* UDP [::]:3702 *:* UDP [::]:3702 *:* UDP [::]:3702 *:* UDP [::]:4500 *:* UDP [::]:5355 *:* UDP [::]:50980 *:* UDP [::]:58891 *:* UDP [::]:58893 *:* UDP [::1]:1900 *:* UDP [::1]:5353 *:* UDP [::1]:63902 *:* UDP [fe80::6c6c:aebf:ca03:a406%17]:1900 *:* UDP [fe80::6c6c:aebf:ca03:a406%17]:63901 *:* C:\Users\Brad>

Yes, I am running the latest version of FSUIPC however my WideFS will not connect. Brad

Still no luck making this work. Here is a dropbox link that shows all the files and installations. https://www.dropbox.com/sh/twah6gqq83ctg45/AAB-tIJQuAnG-y7x5AbkWb2wa?dl=0 Please let me know if you spot something wrong. Thanks, Brad

My current xml file. Is the first line required? <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="SimConnect" version="1,0"> <Descr>SimConnect</Descr> <Filename>SimConnect.xml</Filename> <Disabled>False</Disabled> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>IPv4</Protocol> <Scope>Global</Scope> <MaxClients>64</MaxClients> <Address>10.0.0.30</Address> <Port>5000</Port> <MaxRecvSize>4096</MaxRecvSize> <DisableNagle>False</DisableNagle> </SimConnect.Comm> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>Auto</Protocol> <Scope>local</Scope> >/SimConnect.comm> <SimBase.Documents>

This in the client, right?

Does this SimConnect.xml file look correct? I receive the following error when I try to open the xml file. The address is my server's IP address. I am not sure about the port number. It was 500 in FSX and the example file shows 5000. Error SimConnect Server Configuration SimConect.xml False False IPv4 global 64 10.0.0.30 5000 False Auto local >/Simconnect.com> SimConnect.xml file follows: ?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="SimConnect" version="1,0"> <Descr>SimConnect Server Configuration</Descr> <Filename>SimConnect.xml</Filename> <Disabled>False</Disabled> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>IPv4</Protocol> <Scope>global</Scope> <MaxClients>64</MaxClients> <Address>10.0.0.30</Address> <Port>5000</Port> </SimConnect.Comm> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>Auto</Protocol> <Scope>local</Scope> >/Simconnect.com> <SimBase.Documents>

I am trying to get the Vpilot Vatsim client running on a client machine. I was able to do this in FSX. What I am not sure about in Prepare3d are the Simconnect installations. I beleive there were three in FSX. I am currently running version 10.0.61259.0 of Simconnect. The weird thing is that the MSI installed an 12Gb FSX application I can see in my uninstall programs list. That is strange? I installed the .msi program from the FSX-SP2-XPACK folder found in the "resist" folder. The FSX program I am seeing might be acceleration. Should I remove it. In the end, I am looking for instructions in how to make simconnect so I can use third party programs running on the client designed for simconnect. Thanks, Brad

You wren correct. Thanks Pete.

When I try to enter an airport such as KRKS, the R is not displayed when I hit the key. The keyboard works fine in note pad and I have tried two keyboards.' Any ideas? Thanks,