PBE 2.2... If the tug pushes the plane back by itself!

[byork 2,259]

Guys,

I've had some reports of the Pushback Express 2.2 tug pushing the aircraft back in the FBW A32NX even though you never told the tug to start the pushback.

I did a remote desktop with a user who had this problem, and I saw the problem right away.

He didn't have the latest version of WASM installed in his Community Folder.

Your WASM module should version 1.0 or later.  

If your WASM is version 0.0.0.2, things will not work.

This is how you can see your FS2Crew WASM module version number:

Left is the FS2Crew: FBW A32NX screen...  (Left Click the ABOUT box in the INFO CENTER)

Right is FS2Crew: Pushback Express... (Just open the CONFIG PANEL... gear box icon)

 

 

If you see Version 0.0.0.2, your WASM module version is old, please do this.

1. Go to your Community folder.

2. Delete: 

fs2crew-cmd-center

and:

fs2crew-data-proc

3. Run the Pushback Express installer again (latest version is 2.2C)

4. Restart Windows <--- Important!

5. Open FBW or PBE, and check the Version # again.  It should be V1.0 or later.

If WASM is still not at V1.0, send us a support ticket.

We suspect a write permission issue may have blocked our installer's attempt to update your WASM module.

 

 

Edited August 30, 2021 by byork

[Speedbird7 2]

Thanks for your help Bryan.  Both FBW Project and PBE are WASM 1.0.0.0.  I downloded the latest PBE today, installed it and rebooted Windows as advised.  But the problems still exist.  At +28 minutes the tug arrives, uncalled for, and just starts pushback.  It's a puzzle.

[byork 2,259]

Your parking brake is on?

And are you sure you're using the very latest version of the FBW?

The Dev version, not the stable version.

Edited September 21, 2021 by byork

[tbernard 0]

I have the exact same problem with the PBE 2.2C version. I performed exactly the Bryan York procedure to update  my WASM module version to v 1.0.0.0. and the the problem is still here. The tug connects and after a moment starts a slow pushback, even if I don't do anything (any action or notice) and even though my parking brakes are still set.

I have been using previous version of PBE with FBW A32NX Experimental version without issues.  
For information :
 - I uninstall previous version of PBE before upgrading to 2.2,
 - I am using the latest version of FBW EXperimental version
 - It happens at several tested airports.
 - I have no other pushback tools installed except the one installed in the flypad of the development / experimental version of FBW A32NX

[byork 2,259]

9 minutes ago, tbernard said:

I have the exact same problem with the PBE 2.2C version. I performed exactly the Bryan York procedure to update  my WASM module version to v 1.0.0.0. and the the problem is still here. The tug connects and after a moment starts a slow pushback, even if I don't do anything (any action or notice) and even though my parking brakes are still set.

I have been using previous version of PBE with FBW A32NX Experimental version without issues.  
For information :
 - I uninstall previous version of PBE before upgrading to 2.2,
 - I am using the latest version of FBW EXperimental version
 - It happens at several tested airports.
 - I have no other pushback tools installed except the one installed in the flypad of the development / experimental version of FBW A32NX

Please do a clean install of the FBW aircraft.  Manually delete it.

Install the Development version of the FBW.

Reboot your computer.

Try it at a default airport in case you're only using 3rd party ones.

Try it while in the cold and dark state.

Do not be on the Ground Services page in the FlyPad.

Edited October 4, 2021 by byork

[Math44 1]

1 hour ago, tbernard said:

I have the exact same problem with the PBE 2.2C version. I performed exactly the Bryan York procedure to update  my WASM module version to v 1.0.0.0. and the the problem is still here. The tug connects and after a moment starts a slow pushback, even if I don't do anything (any action or notice) and even though my parking brakes are still set.

I have been using previous version of PBE with FBW A32NX Experimental version without issues.  
For information :
 - I uninstall previous version of PBE before upgrading to 2.2,
 - I am using the latest version of FBW EXperimental version
 - It happens at several tested airports.
 - I have no other pushback tools installed except the one installed in the flypad of the development / experimental version of FBW A32NX

Hi

I had the same problem and each time the AI RADIO COMMUNICATIONS function in the FLIGHT ASSISTANT menu was activated.
I seem to have solved the problem by disabling it.
Be careful, sometimes you have to check that it has not reactivated!

[byork 2,259]

6 hours ago, Math44 said:

Hi

I had the same problem and each time the AI RADIO COMMUNICATIONS function in the FLIGHT ASSISTANT menu was activated.
I seem to have solved the problem by disabling it.
Be careful, sometimes you have to check that it has not reactivated!

Yes, if you have AI Co-Pilot enabled, it will trigger the pushback by itself.

Ensure AI Co-Pilot is not enabled.

 

[tbernard 0]

7 hours ago, byork said:

Yes, if you have AI Co-Pilot enabled, it will trigger the pushback by itself.

Ensure AI Co-Pilot is not enabled.

 

 

13 hours ago, Math44 said:

Hi

I had the same problem and each time the AI RADIO COMMUNICATIONS function in the FLIGHT ASSISTANT menu was activated.
I seem to have solved the problem by disabling it.
Be careful, sometimes you have to check that it has not reactivated!

Hi,

Thank you for your help. Yes, the cause of the problem is that I had 'AI RADIO COMMUNICATION' in ENABLED position. In OFF position, PBE works fine.

Thanks again. 

 

[byork 2,259]

Glad it's sorted 😉  I added this to the FAQs.

Cheers,