Networked PC help

[adampoconnor]

Hello,

The way that I have my simulator I MUST use Pilot Edge on a networked PC. I use FSUIPC and WideServer with WideClient and everything is the latest version. On the client PC I have installed as ONLY PilotEdge, and on the FSX PC I selected the correct option on the install program. The issue arises when I try to connect. It says SimConnect can not connect or something like that. I have installed the included simconnect file with the installer on the client PC but I am lost. Any help?

Thanks,
Adam

[wmburns]

The SimConnect file defines the TCP/IP IP addresses of the "partners" and port #'s to use. The configuration on all of the PC's need to match to work. It's easy to make a mistake as XML isn't the easiest thing to understand.

It might help us help you to post a diagram of your system. It should include PC names, IP address (only the last .# if worried about others seeing). Also important to include the intended TCP/IP port number's since these also have to match.

Include the SimConnect files as well.

There are also tools posted online to check the syntax of the file. However the tools won't help if the basic "design" isn't right.

[Keith Smith]

PilotEdge is a simconnect client. For it to work in a distributed fashion, you need to ensure the client configuration file (simconnect.cfg) is correct, and that it's in the correct location. I would recommend putting it in the 'global' location (My Documents) rather than the PE folder itself. If the PE client is launched in a certain way, the 'local' file won't be found. That's why the global location is the way to go.

On the server, you need to have the simconnect.xml file setup to tell the server which ports should be used for listening, how many clients to allow, the type of network connection, etc.

Why is it that you must have PE running on a separate machine to the main sim?

[adampoconnor]

The SimConnect file defines the TCP/IP IP addresses of the "partners" and port #'s to use. The configuration on all of the PC's need to match to work. It's easy to make a mistake as XML isn't the easiest thing to understand.

It might help us help you to post a diagram of your system. It should include PC names, IP address (only the last .# if worried about others seeing). Also important to include the intended TCP/IP port number's since these also have to match.

Include the SimConnect files as well.

There are also tools posted online to check the syntax of the file. However the tools won't help if the basic "design" isn't right.

I will try both of your suggestions

Keith,

It is important because my simulator consists of 4 machines. The main FSX machine provides simulator sounds, one machine powers the left cockpit with displays and is my communication machine. Another machine powers the right side of the cockpit and the GPWS sounds for my aircraft. The 4th machine powers my FMS and lower displays. The computers are all networked together. This is why I need PE on a Seperate machine. Also, is it possible that one day PE would use the FSUIPC WideServer/WideClient systems?

Adam

[adampoconnor]

UNable to get it to work. I have found an alternative method for now.

[Keith Smith]

Sorry I couldn't help more, but we don't provide direct support for setting up the SimConnect portion of the configuration. The software will install the client-only piece, or the sim-only piece at your request, but the actual configuration of SimConnect is left to you. It takes a lot of attention to detail to get it running in a distributed fashion.