request help with setting up a network for running PSX

[Rhetro]

Hello all,
I've been reading up on Hoppie's documentation with setting up a network. I'm eventually going to do a cockpit build, and want to start off with making sure I'm doing things correctly at the software end before buying the hardware, peripherals, etc.

My (limited) understanding is that according to his diagram, that the system that hosts the PSX software is the Server, and that the clients are external hardware devices (to include other computers, Raspberry pies etc, or controllers) via a router to be controlled through a router program like Hoppie's PSX Router?

I couldn't get telnet on my win 10 machine to work, so Hoppie pointed me in the direction of downloading PuTTY.
I'm now getting an id=1 on my telnet, getting a couple of 2s on my Msg in the PSx Router software. I guess this is progress ! -as i coudln't get it to work before.

what i would like to do next is purchase the FDS-B747 Pro-MX CDU and start playing with that; loading flight releases etc.

recommendations on reading assignments? Homework ? next things to consider as far as what i'll need ?

Thanks for your patience, folks
And to you, Hoppie. Thank you.

[Jeroen Hoppenbrouwers]

You're welcome!

Just to be sure: you do not need the Router. You can plug anything (such as the CDU) directly into your PC or, more common, via a hardware multiport switch. The Router can be handy for development but is very rarely a requirement.

And you can also run PSX in Client Mode on another PC, or even on the same PC. One of the two is the Server. The other(s) are Clients and will follow the Server. For many applications this by itself is priceless.

The use of TELNET (or PuTTY in raw mode) is also just a debug tool, you for sure don't need it at all when just plugging stuff together.


Hoppie

[QuadFan]

recommendations on reading assignments? Homework ? next things to consider as far as what i'll need ?

You might want to consider creating a DHCP reservation for the main system that acts as a server, or giving it a fixed IP address outside of the DHCP scope. Depending on how often you use the system, the address might expire (if the lease time is less than the interval you turn on the system for instance) and you'd have to figure out what its new IP address is.

By creating a DHCP reservation or configuring a fixed IP address, you'll always know where to connect to with your PSX clients.

If I need to clarify this, just let me know. Happy to help

[Rhetro]

Thank you, Gentlemen!

Ok:
1) An ethernet switch for the hardware -specifically the cdu in this case
just curious ? Aside from another system , what else would plug into the Ethernet switch as far as hardware ? Are there other (more robust) controllers, yoke, throttles that use the ethernet architecture? Or is everyone else just using USB related controllers?

2) lock the ip address or DHCP Reservation for server networking.

3) PuTTY for troubleshooting and debugging network assignments.

I'm guessing a second system would handle internet related online load sharing; or is PSX helped out by a second computer?

would love to take a look at what cockpit builders are using!

I'll take a look around !

cheers !!!