FSBUS network help
 

hi to al all
i hope you can help me with my FSBUS network, icant get it
to work as it should,here is a step by step guide to
what I did and please correct me where I am going wrong.


1. This is where I started --Start--control panel--maintenance--system--hardware--devices and continued on to the ports from there to the FSBUS port which is "USB serial communication"on PC2
I continued to change the port settings to COM4 and exited then I went on to PC3 and changed the FSBUS to COM4. Both COMS are connected then I started a test to see if it was working. In
PC2 I have the overhead configuration and in PC3 is the radios and TQ and FMC. The FSBUS USB connection, I had in PC2 and changed it to PC3 and it seems that whatever PC has FSBUS USB connection will work but the other computers that are NOT connected directly into the FSBUS connection will not work over the network.

2. Here is the software for each of the computers on the network which is all connected to a LAN HUB.All seems to be working okay judging by the Project Magenta software as this is working very well
over the 3 computers and windows xp pro and service pack 1.
Computer 1 -- FS2004--FSUIPC--PM IP 169.254.212.101
Computer 2 -- PM--WIDEFS--FSBUS IP 169.254.255.92
Computer 3 -- PM--WIDEFS--FSBUS IP 169.254.141.167
I changed the IP on the FSBUS broadcast to the FS PC and no luck ..


3. All versions of software for the flight simulator are right up to date except for FSBUS which 2.2.1.the cocipt systems i got from symulatory and or full working ..just no over my network

please please help

kevin

Hi Kevin,

all I can see right now is that your broadcast address should be set to: 169.254.255.255. This is to address all PCs within xour network IP
range: 169.254.

Don´t forget to run FSclient too on the clients and configure the FSclient.ini according to the docs.


Hope this helps

Best regards

Peter

Hi Kevin,

unfortunately the FSBus docs aren´t that exhaustive but in order to help you I propose you first describe your setup:

which PC running which software and what should happen where.

From your first post unfortunaltely I don´t get a clear pichture what your setup is alike.

Here a few steps which must be done and checked OK before going on into details.

1.) Do all PC "see" eachother ?? meaning: can you ping them OK?

2.) If yes: How many FSBus Com boards do you have and to which PC are they connected to?

3.) What PM software runs on your server (FS PC)??

Best rgds


Peter

HI peter

thanks again

1.) Do all PC "see" eachother ?? meaning: can you ping them OK?

well peter yes i say so in windows XP pro in the view network i can
see all the PCs on the network sim1,sim2,sim3 and all shows up on all PCs,and my PM software works over all 3 PCs


2.) If yes: How many FSBus Com boards do you have and to which PC are they connected to?

peter there is just one com board connected to the sim2 PCs and into
that com gose 4 leads 1 is the overhead and 2 in the FMC/CDU 3is
TQ and 4 is the radios


3.) What PM software runs on your server (FS PC)??

peter On sim1 is FS2004/FSUIPC/PM MCP/FSBUS but not used/CH yoke
software/
On sim2/WIDEFS/PM SYSTEMS/PM COCKPIT/FSBUS to run overhead/
On sim3/WIDEFS/PM CDU/PM COCKPIT/FUBUS to run fmc TQ radios/

this is my setup peter and thank you again for helping me out, i hope you can see some thing thats not right with my setup

Hi Kevin,

ok now I see what your setup is like.
It´s recommendable to run FSBus on the FS server as this is the easiest setup. As an example take my setup:

PC1 = Server with FS2004 + FSBUSrouter (connected via com1)+ PM MCP + 747 MCP (aerosoft)
Here FSBUS runs the radios You don´t need another PC for it.

Pc2 = PFD / ND + FsBusclient + WideFS

PC3 = PM CDU + SA_WXR + PM Upper / Lower Eicas (using PFD twice)+ FSBusclient + WideFs

PC4 = PMsystems + WideFS + FSBUSclient

Start with running your server + FSBusrouter and configure FSBusrouter to control the radios in FS2004.

If that works start a second PC and configure the FSclient ini.
If you control your hardware by Offsets / setting Bits and / or Bytes it should work flawlessly.
Only in case you send Keyboard commands from the FSBusrouter to an application running on a client you have to set a client ID in each of the FSclient ini.
Further you need to make sure in such case that the window of the addressed application is active before sending the keyboard command.
(See also FSBus command "W"
This is just to get you started. More details will follow after those steps have been successfully passed.

Good luck

Best rgds

Peter

thank you peter

I moved the FSBUS to the main FS PC "sim1" on the com is shows as COM4 i changed to to COM1 and as befour it work fine for the overhead .. its the the next bit of hardware i like to get working
TQ/FMC/RADIOS.

peter --If that works start a second PC and configure the FSclient ini.If you control your hardware by Offsets / setting Bits and / or Bytes it should work flawlessly.

what do i do with the ini file what is to be put in there or you on about the client ID as IP address?
peter can you explane to me sorry for going step by step

Hi Kevin,

the Fsclient.ini looks like this:

[FSClient]
CID=1

[CDU]
TopWindowChar = "c"
Executable = "c:\Programme\CDU\cdu.exe"
WorkingDirectory = "c:\Programme\CDU"
Activate = 1
Terminate = 1
FSBUS_Background=1

FSclient can start applications like as above the PM CDU (FMC).
If you are using different PCs and like to control apps there, each FSclient should get a different CID.
It is advisable to let FSClient start and terminate the programs you like to control remotely by FSBus. (pse see example above.

Let´s get the radios controlled first:

Since the radios are contained in FS2004 you only need to define your rotaries and route them to the corresponding FS destination.
Same applies for reading the Freq. displays.

I´ll attach hereto my FSb2 and FSIF: ini file for reference. You may want to try this out as it is working fine with me. Just align the hardware to your set up. Meaning just change the controller ID the rows and subs to match your hardware setup and you´re done.

Hope this will get you a piece further.

BTW which FSBus version are you using?? Classic or NG? Or mixed?

Best rgds

Peter

hi peter

the FSBUC version i got is 2.2.1 it was sent with the overhead and the TQ/CDU/RADIOS. all pre configured all i had to do was install the files fsbus and fsfi ini i did it all. i send you the files
maybe you mite see some in them . as for the Fsclient.ini it looks ok.

Hi Kevin,

the latest software is version 2.43 dated March 18th, 2006.
You should first update the FSBussoftware before we go on.

Best rgds

Peter

hi peter

i was told by symulatory to only use 2.2.1 version with that hardware i have so it looks like i am in a jam ...:heul:

Hi Kevin,

never mind, let´s go on with 2.2.1
FSBus router has to be run on the FS PC (server.
Fsclient.exe + FSclient ini is to be run on every client you need to control or read something.
The FSclient ID is just a number starting from 1. So for 3 client you should grant the FSclient Ids 1 (client 1); 2 on client 2; 3 on client 3.
That numbering has nothing to do with the IP address.

The ID 0 (zero) is the server (in our case the FS 2004 PC) where FSBus is running.

On top of this it is mandatory that WideFS client is running on every client PC and WideFS server is running in the FS2004 Modules folder.
But this is the case I believe otherwise your PM software wouldn´t run properly.

In order to get the radios up and running i propose you take my example FSB2 settings and modify them to match your hardware setup.

That should do the trick. It should run immediately as the radios reside inside of FS2004 on the server where FSBus is running. No network is in the game for this.
Please let me have your findings.

Best rgds

Peter