A320 FMGS B35

[filippoporcari]

hi jl,
since latest update i don't have any trim wheels motion (skalarki hardware which was working before) i checked on SD f-ctl page and the trim values remained at 0.0 for the entire flight...it was changing values before.
btw the autotrim seemed to work because i hand flew circuits very well there is just no trim value changing.
do u confirm this?

....had my first hardwareconnect crash today...just restarted it...
i cannot change port5 to 8002 because that port is used by widefs and since i'm a nerd in port communication just left it at 8007...any other value we can safely try?

all the best
fil

[filippoporcari]

sorry jl,
forgot to report that also left and right brake pressure readouts on skalarki triple gauge are missing since then...don't have installed soft triple gauge so cannot check if the output is missing everywhere.
the ACCU PRESS is there instead
cheers
fil

[OmniAtlas]

Ah fixed my problem - had installed 35.4 by mistake, latest version is 35.7.

[jeehell]

You have almost every ports between 1 and 65535, that's a lot of ports to try...
You could opt for ports below 8000 or for the 9000 range as well...

The triple brake only work when in ALTN BRK mode (green HYD LO PR). In normal conditions, you only have the ACCU PRESS at the max.


JL

[filippoporcari]

ok for the ports thx...told u i'm a nerd at that!

about brakes: i know its logic jl the point is that with engines not running (green system not pressurized) when u set parking brakes the L and R indicator should indicate max...it was working before...not now.

what about trim indication?

[jeehell]

Hi,

The latest update is available on the auto updater or here:
http://www.jeehell.org/A320FMGS_B35.7.exe


Fil, the trim should be corrected in that version, if Marcin also updated his soft.

Regards,
JL

[filippoporcari]

hi all,
thx jl...after today's update the trim is back! now just marcin needs some work to perfectly sincronize it.

btw i'm actually flying and see for the first time both PFDs lagging a lot...did u change something in that area? or is it a local prob?
thx
fil

[buentead]

If one is using WideClient, e.g. to run TopCat on a separate PC, I suggest not to use port 8002 (instead of 8007) as this is used by WideFS of FSUIPC by default (and it also uses 9002).

I changed the port 8007 to 8107 for the time being. A 1st short flight is looking good. But more testing is required.

Regards
Adrian

[filippoporcari]

ouch!!! i'm using 9002 now! that could be the reason for the lagging?

[buentead]

@fil: Yes, it might well be. When I used port 8002 first and started WideFMGS client, the WideFS server was reporting "connected and then waiting for client" continuously.

@JL: With port set to 8107 (instead of 8007) the HardwareConnect crashed again. Please find attached the event log. I used the latest updates from your server (I assume it's 35.7).

Thanks
Adrian