A320 FMGS B31

Hi Stefan,

Why would you think it is an issue? It says "if you installed a new senery". It's just a reminder...
As said already on the forum, the navdbapp scans the FS scenery to adjsut ILS data (localizer/glide antenas position/angles etc...). However FS protects the scenery files when it is running, so you need to shut FS to allow the scenery scan.

Regards,
JL

Anyone know how accurate the 'Low' 'Med' 'High' brake settings and their effects are on ground landing distance are compared to real life?

Quote:

---

Originally Posted by jeehell

Hi Rob,

Currently, the hardware handling of trim wheeks is very difficult. As you saw by yourself, there is no easy way to maintain synch between the FMGS server and hardware. Right now manual input is not taken into account by the software (it won't disconnect the AP or freeze the autotrim).
You can for now just replicate the value of FS trim on your Wheel to animate them.

JL

---

I was planning to purchase the Skalarki A320 automated throttle -- are the functions not fully compatible (specific to this model) as you have mentioned at this stage?

Quote:

---

Originally Posted by OmniAtlas

Anyone know how accurate the 'Low' 'Med' 'High' brake settings and their effects are on ground landing distance are compared to real life?

---

Yes, I compared it. There is a problem with that?

Quote:

---

Originally Posted by OmniAtlas

I was planning to purchase the Skalarki A320 automated throttle -- are the functions not fully compatible (specific to this model) as you have mentioned at this stage?

---

You'll have to contact Marcin directly for that info...

Quote:

---

Originally Posted by ToTom

Yes, I compared it. There is a problem with that?

---

I wanted to test it out myself...how did you do that?

Quote:

---

Originally Posted by OmniAtlas

I wanted to test it out myself...how did you do that?

---

Reference data are needed.
You need to use a program that saves data from braking.
And then you have to compare. ;)


I checked the brake long ago, in January 2012.
Then I did a short report. But it is outdated now.
FMGS not using braking force (as the offset value), but keeps constant deceleration.

ben,
as i reported u in PM in the past the skalarki TQ works as it should: the trim input sends values to FMGS but as JL said trim is just not implemented in the soft right now.
the motorized wheels works as they should with values showed synched with FMGS values...marcin made the update i suggested and now the wheels move as expected simulating the autotrim working.
for the time being everything is correct...at least from a "visual" point of view.
cheers
filippo

Quote:

---

Originally Posted by ToTom

Reference data are needed.
You need to use a program that saves data from braking.
And then you have to compare. ;)


I checked the brake long ago, in January 2012.
Then I did a short report. But it is outdated now.
FMGS not using braking force (as the offset value), but keeps constant deceleration.

---

Thank you totom, your study was very informative.

There is an ifly 737NG cockpit edition video utilizing some sort of external program -- http://www.youtube.com/watch?v=jDS9hjxWcg8 (go to 18 minutes); do you all have any idea what that program may be?

Quote:

---

Originally Posted by filippoporcari

for the time being everything is correct...at least from a "visual" point of view.
cheers
filippo

---

Thank you Filippo -- I hope to make the investment soon and hopefully there will be continual improvements between FMGS and hardware throttles.