fixed FMC channel status not syncronized on CPG join

[FalcoGer]

The FMC channels are not syncronized when the CPG joins. For him it's always all channels on, except for NOE, no matter what the status is for the pilot.

To reproduce

1. Pilot enters aircraft
2. Start A/C
3. Disable FMC channels, for example pitch, roll, yaw and collective
4. CPG joins
5. CPG sees all channels in default configuration
6. Any changes toggle on both sides so that they're always not in sync, ie. if the CPG turns something off it turns it on again for the pilot.

Tracks attached.

server-PLT-fmc-sync_no-points-and-route_wipers-moving-no-input.trk

client-CPG-fmc-sync_no-points-and-route_wipers-moving-no-input.trk

Edited September 4, 2022 by FalcoGer

[Floyd1212]

There used to be a related bug when the CPG would join the aircraft after it was already started, and would then go to enable the laser on the WPN > UTIL page at L6, and this would enable NOE for the pilot, which is also at L6 of a different page.

Not sure if this bug still exists, as I have been flying missions with "hot" aircraft recently to avoid these kinds of things.

[FalcoGer]

I don't think it's related. when joining, it just assumes the FMC to be in some state, and it's never synced to begin with.

Either way, I don't think button presses should be syncronized to begin with. It should be the intent sent to the aircraft that should be syncronized. If CPG sends "FMC Coll OFF", then that should be sent to the pilot, not "L4 pressed"

related, but closed.

 

Edited September 4, 2022 by FalcoGer

[Floyd1212]

Right, I think they are related in that a button press by the CPG can toggle a setting seen by the PLT, instead of actually synchronizing the intent of the button press.  Maybe not "related" so much as another example of similar behavior happening out of sync between the PLT and CPG.

[Swift.]

Slightly related is what we noticed last night, that if the pilot not on the controls presses the FMC disengage button, it will disengage the FMC and show a caution only for the pilot not on the controls. 

If he then re-engages the FMC it will disengage for the pilot on the controls.

 

So basically the state of the FMC isn't being synced, just the MFD presses, toggling on will cause toggle off in the other cockpit.

[BIGNEWY]

This has been reported. 

thanks