These are the Support Forums for FSUIPC and related products.

These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.

Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.

Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE

Aerostar 600 Honeyc...
 
Notifications
Clear all

Aerostar 600 Honeycomb Bravo

Posts: 2
Registered
Topic starter
(@sesanchez)
Joined: 3 days ago

I have a registered version of FSUIPC, Honeycomb Alpha, Bravo and Charlie. When I try to configure the A2A Aerostar in FSUIPC in MSFS2020, I can configure the throttles just fine. When I try to configure the props, They are reversed, so I go into the axis calibration. Select the Prop 1 box, then click on Reverse. When I try to set the max and min, windows will just ding like the button is not valid. "Sometimes" and I have not been able to find out why, when I close FSUIPC and go back in, it'll let me configure min and max, but then the levers when coming down, will only reach like half the travel and then jump to the feather position.

Same for the mixture levers

What am I doing wrong?


3 Replies
Posts: 347
Moderator
(@fsuipc-support)
Joined: 10 months ago

This behavior is generally caused by having bad values in the calibration. To resolve this, please reset the calibration and re-calibrate. To do this, first click Reset to clear the current calibration, that Set and re-calibrate.

When you calibrate, make sure the min value is always less than the max.

If you still get issues, please show me / attach your FSUIPC7.ini file.


Reply
Posts: 2
Registered
Topic starter
(@sesanchez)
Joined: 3 days ago

Thank you. I ended up deleting the INI file and recreating it. Even after calibration it was still doing the same


Reply
Posts: 353
Admin
(@fsuipc)
Joined: 1 year ago

Posted by: @sesanchez

Even after calibration it was still doing the same

But, as I said, it is bad calibration that causes this issue, and you need to delete the calibration and re-calibrate. If it was doing the same, you are not calibrating correctly. See the documentation on how to calibrate if it is not obvious, but just always make sure that the max and min values are correct, as well as any null zone if using.

Deleting the ini is a bit drastic as you lose all your assignments.


Reply