Results 71 to 80 of 308
Thread: A320 FMGS B35
-
08-31-2014, 09:45 AM #71
- Join Date
- Sep 2013
- Location
- Speyer, Germany
- Posts
- 191
Re: A320 FMGS B35
I also have a problem with the Thrust levers since the new version is installed: I have setup both levers in the FMGS Config tool and the detents are recognized correctly, but when I push the levers forward, the engine shows no reaction (the upper ECAM display shows the movement and detents correctly). Any ideas? I have already deleted the AControls and JoySW files, but no changes ...
Regards,
Stephan
-
08-31-2014, 02:15 PM #72
Re: A320 FMGS B35
Hi Stephan
i Set the detent 2000 for toga and flex, 1000 for clb, 2 for idle.
This may help.
BR
stefan
-
08-31-2014, 02:36 PM #73
- Join Date
- Sep 2013
- Location
- Speyer, Germany
- Posts
- 191
Re: A320 FMGS B35
You mean the error zones for each detent? Will try this and report again!
Thx
Stephan
EDIT: that does not work,too my thrust levers are driving a 10k pot on an Arcaze board; I need to have an error zone of at least 2000. Maybe I should add that the complete setup is still working with my B33 backup!
-
09-01-2014, 07:14 AM #74
- Join Date
- Sep 2013
- Location
- Speyer, Germany
- Posts
- 191
Re: A320 FMGS B35
I have uploaded a video to show the detents are recognised corretly, but no power goes to the engines.
http://youtu.be/Gm606FSYCx0
Would be great if anyone has an idea!
Regards
Stephan
-
09-02-2014, 04:20 AM #75
- Join Date
- Mar 2008
- Location
- France,Nice
- Posts
- 2,652
Re: A320 FMGS B35
Stefan, this usually hapens if you have not the AP/FBW running. Or if the connection to FSUIPC/simconnect has failed somewhere.
Try manually closing FSXconnect and the APFBW and running them manually.
JL
-
09-02-2014, 05:53 AM #76
- Join Date
- Sep 2013
- Location
- Speyer, Germany
- Posts
- 191
Re: A320 FMGS B35
Thank you Jean Luc, but this did not solve the problem either what I found out now: when I move my levers from FLX/MCT to CL detent, the engines N1 goes to 85.0% .... I have reconfigured the throttle axis again, but no success.
-
09-03-2014, 05:09 AM #77
- Join Date
- Mar 2008
- Location
- France,Nice
- Posts
- 2,652
Re: A320 FMGS B35
Hi,
this could be the result of overlapping detent (if the error zone around the detent is so big that it overlaps the error zone of the next detent).
JL
-
09-03-2014, 05:29 AM #78
- Join Date
- Oct 2010
- Location
- Poland/Europe
- Posts
- 4
Re: A320 FMGS B35
Hi all,
I had the same problem on my setup. All seemed OK, but no engine reaction. Only, when I switched to TOGA, engines were spinning but just for few seconds.
I noticed, that this problem appeared after using Updater. So, I decided to revert to previous version (B35.1 full installer).
When I did it, all come back to normal.
Maybe this will help Stephan.
IMHO, JeeHell FMGS is the best software available on the market now and I always recommend this software to our cockpits.
One weak point is Updater module, sometimes it generates problems, I mean, it makes that all modules are not in the same version.
Therefore, I always do the backup upon new full installer release, so I have the reference point
Kind Regards
Tomasz
-
Post Thanks / Like - 0 Thanks, 1 Likes, 0 DislikesLeonidas liked this post
-
09-03-2014, 06:05 AM #79
- Join Date
- Sep 2013
- Location
- Speyer, Germany
- Posts
- 191
Re: A320 FMGS B35
Thank you, Tomasz, glad to see that I am not the only one
As I wrote before, I have a backup of my B33.? Version, which is running perfectly with the exactly same setup and configuration.
I will try the B35.1 without updates and report back!
Thanks so far, also to JL !
Stephan
EDIT: that was the solution! Thx Tomasz! Please let me know when you found a way to update to the latest version without having this issue.
-
09-03-2014, 03:19 PM #80
- Join Date
- Oct 2010
- Location
- Poland/Europe
- Posts
- 4
Re: A320 FMGS B35
In fact the only solution for now, is to keep watching Updater window during update, if You notice some extraordinary delay during update of any file, You can assume that this module was not fully updated, but Updater module will consider this file as updated. If You see such an issue, simply kill Updater.exe process inside task manager.
Then restart Updater
This is very simple (and brutal ) solution, but it works.....
....at least for me.
I would like to repeat, that this small issue is meaningless, considering the quality of whole software package
Kind Regards
Tomasz
Womans in your city for night
JH startup on Client PC