richard.long
05-12-2017, 08:12 AM
Hi,
I have some problems starting the software across my network; typically involving having to perform restarts on different machines. Once it's running it normally behaves well.
Is there a recommended start up sequence or configuration as this process is rather cumbersome. Given that all my monitors on PC1 (PFD/ND/ECAM) are all mounted behinds panels it's a nightmare to navigate windows hidden behind the MIP?
Because of the problems I now start each machine and its software sequentially. My default start sequence, and usual problems, is:
PC0:
P3D and AS2016
FMGS Server
Manually start SKalarki Profiler (I can't automatically start this as it throws an error about not being able to find the JL default profile)
PC1 (PFDs, NDs, ECAM, ISIS, DDRMI):
FMGS Client - at this stage the startup doesn't work and it fails to connect with the server on PC0 (all displays including DDRMI remain blank). I now have to go back to PC0 and restart FMGS server. This typically works but is then followed by the aural GPWS system test rolling through all the callouts.
WideFS
Manually start SKalarki Profiler.
PC3 (MCDU displays)
FMGS Client
At this point it is often the case that I will get setup, program the MCDU and find the NDs are not displaying any navdata. I then have to restart FMGS client on PC1.
All my IP addresses are correct as the software works as expectd once all the start up drama is complete.
Any helps appreciated.
Many thanks all
Richard
I have some problems starting the software across my network; typically involving having to perform restarts on different machines. Once it's running it normally behaves well.
Is there a recommended start up sequence or configuration as this process is rather cumbersome. Given that all my monitors on PC1 (PFD/ND/ECAM) are all mounted behinds panels it's a nightmare to navigate windows hidden behind the MIP?
Because of the problems I now start each machine and its software sequentially. My default start sequence, and usual problems, is:
PC0:
P3D and AS2016
FMGS Server
Manually start SKalarki Profiler (I can't automatically start this as it throws an error about not being able to find the JL default profile)
PC1 (PFDs, NDs, ECAM, ISIS, DDRMI):
FMGS Client - at this stage the startup doesn't work and it fails to connect with the server on PC0 (all displays including DDRMI remain blank). I now have to go back to PC0 and restart FMGS server. This typically works but is then followed by the aural GPWS system test rolling through all the callouts.
WideFS
Manually start SKalarki Profiler.
PC3 (MCDU displays)
FMGS Client
At this point it is often the case that I will get setup, program the MCDU and find the NDs are not displaying any navdata. I then have to restart FMGS client on PC1.
All my IP addresses are correct as the software works as expectd once all the start up drama is complete.
Any helps appreciated.
Many thanks all
Richard