@Manuel82, Hello again and, as promised, I have prepared some screenshots for you

Unfortunately, looks like users cannot upload images directly?

Can I send email these mages to you?

Failing that, suffice to say, FBW A32NX MCDU shows:

Transition Altitude 10000, RAAS shows 5000

Transition Level 10000, RAAS shows 6000

Note, values displayed in RAAS are those manually entered and saved to the profile on a previous flight which suggests these values are not getting automatically imported from the MCDU

8 hours ago, slicker55 said:

Unfortunately, looks like users cannot upload images directly?

Upload and post the link here using upload sites like for example:

WeTransfer.com

(Change it to be thru "Get a Link", NOT via email)

Cheers,

Manuel

 

@Manuel82 Thanks, here you go, 

https://we.tl/t-IMN7wmeGyT 

On 2/3/2024 at 9:05 AM, slicker55 said:

@Manuel82 Thanks, here you go, 

https://we.tl/t-IMN7wmeGyT 

Can you cross check in FS2Crew FBW Settings panel if you have the "Send RAAS Data" option ticked/checked?

Manuel

22 hours ago, Manuel82 said:

Can you cross check in FS2Crew FBW Settings panel if you have the "Send RAAS Data" option ticked/checked?

Manuel

Hello again, can confirm, using A320 profile, 'Send RAAS Data' option is checked in the Settings panel. I have prepared a screenshot and can upload it for you although, no doubt, you will take my word for it.

Just prepared a new flight... the TA and TL values displayed in RAAS are not in sync with the corresponding values set in the MCDU ... during tests, had a thought... maybe best practice to set up the MCDU before launching RAAS?

However, didn't resolve issue...

Also, and just for the record, I also tried changing the values in the MCDU (after loading RAAS) to see the new values in the MCDU would be reflected in RAAS but unfortunately they remained unchanged ....  over to you sir 🤔 

Edited February 6, 20242 yr by slicker55

Please update via the Product Manager.

We release a RAAS update today (among other updates) that should fix your issue!

 

11 hours ago, byork said:

Please update via the Product Manager.

We release a RAAS update today (among other updates) that should fix your issue!

 

Hello @byork ... thank you for looking into this issue and for providing the latest product updates

Downloaded latest version RAAS 1.9.78.0

Tested using FBWA32NX... manually set TA 6000 and TL 9000 in MCDU 

Launched RAAS (displaying Transition Altitude 4000 and Transition Level 7000) from previous flight instead of the new values set in the MCDU for this latest flight

May be doing something wrong this end ... please advise

Are you using Dev or Stable version?

6 hours ago, byork said:

Are you using Dev or Stable version?

DEV

12 hours ago, byork said:

Are you using Dev or Stable version?

FBWA32NX Development 1ad4a76 

FS2Crew: RAAS Pro for MSFS 1.9.78

Just to confirm, set up a few more flights tonight, on each occasion creating a new flight plan in Simbrief and importing to MCDU via EFB ... not loading RAAS until MCDU is fully prepared ... then comparing values in RAAS to those in the MCDU ... for me, still not syncing up?

Maybe FBW changed something in the DEV version.  Remember the DEV version changes all the time.  We'll check.

3 hours ago, byork said:

Maybe FBW changed something in the DEV version.  Remember the DEV version changes all the time.  We'll check.

Yes, OK and, once again, thanks for taking the time to look into this ...
I'll quickly mention the purpose of my tests to date has been to verify RAAS is importing values from the MCDU but there appears to be a sync issue as discussed. 
Of course, and in addition to the above, lets not forget there may be occasions when the end-user has to manually adjust the TA / TL in the MCDU.
I don't know if, in these circumstances, any changes should automatically be displayed in RAAS but if they should, there is a further issue as this is not currently happening.

I'll try to replicate...I'll be testing it again in the sim, I saw your files that you sent...sorry by the delayed answer, has been busy days.

Manuel

It appears FBW changed the variable names for the Trans Alt / Level.

We just asked them to clarify this.

Just to update you on this:  Yes, FBW changed their code for the Transition Alt Level values.  We're working with them on a solution.