I can't seem to figure this out. I'm always getting a pitch trim disagree no matter what trim I set it to. Weather it's the up value on the perf page, or the cg value on the init b page.

 

I don't have this issue with the Fenix Airbus. Is there something I'm missing?

Are you sure that you set the same trim value of the perf page on the trim wheel of the pedestal?

1 hour ago, polosim said:

Are you sure that you set the same trim value of the perf page on the trim wheel of the pedestal?

Yea. In my case it said .02 up on the perf page. On the init B page it said 19.5 (approximately).

 

But again, I don't have any problems in the Fenix A320

0.2up and 19.5 CG?

You can see from the example picture that these numbers don't add up at all. 0.2 up should be something like 28 CG. 19.5 CG is  2.2UP.

7 minutes ago, Farlis said:

0.2up and 19.5 CG?

You can see from the example picture that these numbers don't add up at all. 0.2 up should be something like 28 CG. 19.5 CG is  2.2UP.

Why would the Fenix airbus not have any issues, but I can't seem to get this set correctly in the fslabs Airbus. It should be the same process right?

2 hours ago, simsuper80 said:

But again, I don't have any problems in the Fenix A320

FENIX model is about the CEO and FSLABS the NEO. In the latter there is the detection through the ECAM warnings of different discrepancies such as speeds, flaps, trim settings and others, things that the CEO only detects on a smaller scale and with warnings through the TO CONF TEST.

3 hours ago, polosim said:

FENIX model is about the CEO and FSLABS the NEO. In the latter there is the detection through the ECAM warnings of different discrepancies such as speeds, flaps, trim settings and others, things that the CEO only detects on a smaller scale and with warnings through the TO CONF TEST.

Ah so there Actually is a difference? Good to know 

 

So are the stab trim values on the perf page and init B page supposed to match?

3 minutes ago, simsuper80 said:

So are the stab trim values on the perf page and init B page supposed to match?

Stab trim values on the perf page and trim wheel value must be match.

35 minutes ago, polosim said:

Stab trim values on the perf page and trim wheel value must be match.

What about the cg value on the init b page?

Are you using GSX? I find it doesn’t always load the planned cargo in. If you look at planned and actual loads in the tablet do they match?

If you’ve used trim calculations based on the planned load then this will be why they don’t match. 

As you've flown the Fenix, I guess you might have skipped the FSL tutorial? A quick skim might reveal a missing step in your pre-flight. 

Check the F/CTL ECAM, does the trim setting match the one you have set in the MCDU? The MCDU FLAPS/TRIM also needs to be calculated seperately and the EFB will do this for you.

Do you also have any of the MSFS assists enabled? One of them is auto trim which may interfere?

Trim Check (TOS1)

TOS1 also compares the trim setting entered by the crew into the Takeoff PERF page with the actual Trimmable Horizontal Stabilizer (THS) position and with the trim computed by the FAC/FMGEC/FE based on the CG value provided by the fuel management system. If an inconsistency is detected, this will trigger the F/CTL PITCH TRIM/MCDU/CG DISAGREE (A320/A330/A340)

Edited March 26Mar 26 by G MIDY

7 hours ago, simsuper80 said:

What about the cg value on the init b page?

CG value on Init B page is a Zero Fuel Weight CG not a TakeOff Weight CG .

1 hour ago, polosim said:

CG value on Init B page is a Zero Fuel Weight CG not a TakeOff Weight CG .

Indeed. The TOWCG you will find on the fuel page not the INIT B page.

4 hours ago, Farlis said:

Indeed. The TOWCG you will find on the fuel page not the INIT B page.

One thing I'm noticing is that the fslabs isn't loading the full payload that simbrief has set. For some reason the actual final weight is a bit less than the planned weight. No cargo was loaded for example, so I had to put the load in manually. 

Edited March 26Mar 26 by simsuper80