Sure, this is just a suggestion. AP VS behaviour is much more important than this ;)
Printable View
Sure, this is just a suggestion. AP VS behaviour is much more important than this ;)
Hello,
Ok B10 was probably a mistake ;-)
http://www.jeehell.org/A320FMGS_B11.zip
Now B11 is out, and a lot of bugs should be gone:
-Flight profile computation if FPLN DISCONTINUITY is present
-FOB under FS9
-Auto-trim when on ground
-Pseudo waypoints messing with the NAV mode
-Hopefully the big problem causing AP/FBW instability under FS9
-PERF TO page showing wrong RWY
-FO PFD now saves hide border/lock position/always on top settings
-MCDU 'green' error...
-Glide slope should be followed much better until touchdown. I still recommend flaring under manual control.
-Added more options and pages from the DATA page on the MCDU (POS,IRS and GPS monitor). When in flight, you can align the IRS in ATT mode through the MCDU IRS MONITOR page (the HDG you enter will not be used, only the real HDG, HDG and position drift will be taken into account later)
-OVHD graphics can now be changed. They are in the folder OVHD\Graphics. Only restriction: you need to keep the same size (size, not proportion) and position of switches!!
-I included the iFDG A320 I use in the package. The aircraft.cfg file has already been modified to suit the FMGS software, so only copy to your aircraft folder.
Have fun!
Hi,
maybe not a mistake but a bugfull release ;) But it seems that all this bugs are away :)
Currently I'm on a testflight and it works perfectly until now.
Just one issue at this time: FO PFD shows "ATT" and no artifical horizon.
Chris
First of all thank you for this nice flight this evening with your FMGS! It was my first complete flight (including LOC and GS) with it.
There was no major bug! Just a few things:
- The SD error ("'-9223372036854775808' is not a valid integer value.") is still there and occurs also if FS is not paused.
- Reaching CRZ ALT "CRZ ALT" was displayed on PFD but the white border around it was also displayed in the space below CRZ ALT. But there is no message which could get a border.
- GW is available in MCDU but not on SD
- Actions of AP could be a little bit smoother (pax comfort)
- GS was perfect (!!!) but there were some problems capturing the LOC. The aircraft turned left and right until the LOC was captured.
Hello!
Well great news!!
- I will look into the SD error, it never happened to me yet... Any idea on what might triggers it? (flight phase, action on FCU or OVHD ??)
- CRZ ALT: I need to check if the white box should appear when engagement of an armed mode happens.
- Ok will correct that
- AP smoother:It's on the lsit as well
- LOC*:How many times did it turn to fully capture? Usually, it should overshoot at most once, the second time it should follow correctly the LOC. Maybe your speed was a bit too fast? (I recommend speed less than 220knots)
Cheers,
JL
Hi,
No idea. Most time I recognized that some messages poped up in the background. I will try to find out when it happes.
My speed was around 200 knots. I think my aircraft made around 5 or 6 turns.
Ok, 5-6 turns is way too much. I will see if I can do anything...
My train to university was cancelled so I decided to stay at home today :D
So I have time to perform a second testflight today.
Chris
Hi,
my second testflight was... let me say not as good as the first one :D The entire vertical stuff was never doing what I want it to do. First I made a lot of screenshots of that but then I noticed that the only thing which was different to my first testflight was, that I deactivated the FBW. So I activated it on descent and it seemed to work! But nevertheless the GS and LOC was not captured, maybe due to my overall bad approach. Maybe you can check if this happens, too, if you deactivate FBW. I wanted to test it on another flight but after entering origin and destination for this new flight IRS alignment was lost and CPT ND got an error message: "Access violation at address 00404F87 in module 'ND.exe'. Read of address 00000002.". I had to reset my computer because it had a complete crash with this message.
By the way the SD error message did not appear again.
Some other things:
- As far as I know from my cockpit visits (A320) and from Wilco series, airway and waypoint can also be entered in the format "airway/waypoint", e.g. "T207/BATEL".
- On SD appears only the left front door if opened. The others do not appear as open even there open in FS.
- Is there a RWY mode yet on take-off?
- Fuel used is not available (I think it's a FS9 problem)
- Suddenly MCDU has set a new CRZ ALT... (FL340 instead of my entered FL230)
- Push to level of did not work. VS was still 700 ft/min.
- As far as I know the ILS APP gets active if I activate the approach phase in MCDU and not if I select an approach route.
- VOR DME on ND: if decimal place is 0, the zero does not appear. Example: Instead of 45.0 only "45" is displayed.
- Still some graphical issues concerning the flightpath lines on ND.
Hello,
Ok I will check that FBW thing.
When you tried a second flight, you didn't restart the FMGS server? I think it is safer to do so for the moment, probably some messy code somewhere...
- AWY syntax: never heard of that, I'll check thanks.
- SD doors page: FSUIPC offset for doors is not exactly exhaustive...
- no RWY mode yet on TO
- indeed fuel used is not available in FS9. I'll see if I can add an accurate fuel calculation based on instantaneous fuel flow.
- MCDU CRZ ALT: I never had this error. From my code point of view (;)) the only way to get this in the MCDU is to increase the FCU altitude above the CRZ level, which is normal.
- Level off: I will check/correct that
- This is actually obscure in the FCOM, I need to read it more carefully
- DME decimal: will correct that ;)
- ND curves: this is a very old bug, but very tedious code there. If I am in the mood someday...
Thanks for the report,
JL
Ah ok, I will do this the next time ;)
I am not quite sure with the AWY thing but I think this exists in reality. I know it from Wilco series MCDU and last summer after a flight in an A320 I visited the cockpit and together with the captain I entered the next flight and I am pretty sure that this procedure was the same I know from Wilco series.
Btw, do you have "Prof. McDoo" A320 MCDU trainer? I got this from an Airbus pilot but the CD does not work here...
Hopefully I can get this thing running.
Never heard of this prof mcdoo, but I know there is a FMGS trainer available on various torrent providers.
For the AWY, I'm doing my homework right now ;)
JL
I read in the manual of this MCDU trainer that this software is for pilot training before training in the simulator. On the pictures I see that the MCDU is well done and full of pages. I think it would be a nice source to fill your MCDU. But somehow my computer does not recognize the CD...
For the AWY input, it seems it depends on the version of MCDU software (honeywell or thales). Since I have a manual for the Thales MCDU, that's the version I replicated.
And it seems there is no such way to enter an AWY.
However, on the trainer I have which is honeywell, in the LAT REV page you can only insert one AWY/WPT at a time, with the syntax you wrote.
If you could confirm that?
Yes, I think this is it! Thank you for this information :)
Hello dear beta testers ;)
The latest version is available: http://www.jeehell.org/A320FMGS_B12.zip.
What's new:
-Sound Module, run separately now. All implemented sounds should work correctly every time now (not once every few flights...)
-EXPED and LOC functions on FCU
-Runways appear on the ND
-E/WD and SD values out of range are displayed in amber
-Autobrake and ground spoilers logic should work correctly now
-Flaps logic should be good now (levers on position 1 either gives 1 or 1+F as per the real ACFT ops)
-Fuel Used and Fuel Data Link under FS9 now operationnal
-DECEL point sets managed speed at Vapp
-ND turns should be correct for every turns
-Corrected more bugs on the VNAV calculation.
-AP enhanced:
-ATHR is now homemade and no longer FS (some bugs with FSare gone, some new are probably here now)
-Oscillations especially at lows speeds and high angle of attacks should be less brutal
-ALT* mode will no longer make the ACFT take 3000ft/min or more, it should be a smooth transition between CLB/DES and ALT*
-LOC should not overshoot more than once if intercepted below 220kts and at more than 10nm DME from threshold.
-Enhanced LAND, FLARE and ROLL OUT modes: the aircraft will now flare, idle thrust, and try to align on the runway heading.
-Trim on ground will no longer move
-Embryo of alpha and overspeed protections: the FBW will give nose down/up instructions. However, it is far from perfect and accurate at the time
-Christoph modified the FMGS SCREEN font to correct the minute symbol on the ND chrono, so don't forget to reinstall that font!
-The user guide is up to date, and from now on, new or corrected items are marked with a red on green arrow.
I feel the software has now reached a point where it is really flyable. Still some stability issues but I really think there has been much progress the past few months.
As usual, your feedback is welcome and much appreciated!
Jeehell
Hello,
A small update to correct really annoying bugs:
http://www.jeehell.org/A320FMGS_B12.1.zip
Corrected the Managed mode and FLEX issues, as well as small glitches on the EWD and SD displays.
Cheers,
JeeHell
Hi,
I had some time to perform a test again. Some issues:
- "Invalid pointer operation" (see screenshot)
- NDs were acting up. They calculated around 3000 NM to the next WPT and they were full of dummy WPTs (see screenshots). But guidance was working properly. Maybe it's just a display problem.
- Sound module played sounds on initial climb ("Terrain! Pull up!" and altitude was counting up ("10, 20, 30 ... 1000, 2500"))
- AP disconnect sound would be nice (maybe just a feature with a dummy file, so the user can replace it by his own file)
- EXPED INOP
- If rotating around 135 kts alpha floor gets active because according to the FMGS I am below stall speed (around 160 kts)
Screenshot file: http://www.christophpaulus.com/files/fmgs_121.zip
Hello,
The ND displays seems to have e new big bug which found its way in somehow, very weird.
For the stall at rotation, what was your flaps setting? I had a bug in FS9, where I selected flaps 2, the aircraft in FS had the correct setting but the FMGS software didn't get it right, except when in outside view (really weird bug).
I will look into all those bugs.
The AP disconnect sound: no problem to put a dummy file if I cannot find a way to replicate it (free of copyrights of course), and I will try to add it in next version.*
JL
Thanks :)
My flap settings is 1+F and it is correctly shown on the EWD.
But I don't know why the stall speed is set so high. The aircraft is completely flyable at 135 kts.
Chris
I get it now, it's not the FS problem but comes more or less from my software...
The problem is, FS doesn't provide that much data concerning stall speed. FSUIPC only gives two offsets: clean stall speed and full flaps stall speed, and no variations according to the weight... So, I had to improvise...
I will see what I can do about it, but meanwhile I recommend Flap 2 for TO ;)
JL
Hello,
The only way I could reproduce the ND bug was with DME INTERCEPT points on STARs . If you could confirm that? (or maybe give me the route details you so I can confirm myself).
Hi,
I wanted to fly from EDDL to EDDW via MEVEL L179 OSN R15 BASUM T820 PIXUR.
I've done some modifications and some testing, I haven't had that error anymore.
I couldn't quite repeat the problem, and I think I may have put an old file in the package which caused the bug.
Anyway, this version has been tested on several routes, including yours, and everything is clean.
here is the link: http://www.jeehell.org/A320FMGS_B12.2.zip
If you could make even just a quick test to confirm the ND works, it would be great!!
Cheers,
Jean Luc
Works perfect until now (climb) :)
Only thing is that the chrono on FO ND is INOP.
Chris
Okay, I'm back on ground. There were no problems with ND but just a few other things:
- Chrono on FO ND is INOP (already said that)
- Chrono text is wider than its background if time is more than 9:59 (9:59 fits, 10:00 is too wide)
- When I selected EXPED, speed was set to 340. Why?
- On approach the FMGS was unable to hold my selected VS -2000. I descended with -600 ft/min and suddenly the aircraft began to climb. See screenhot: http://www.christophpaulus.com/files/fmgs.jpg
- Border around LAND on FMA is not wide enough. The border just frames the 2nd column and not the 2nd and the 3rd for LAND mode
I'll correct the ND (frame and FO side) in next version and the LAND border.
EXPED function is supposed to get the best climb or descent gradient (not V/S apparently) according to your phsase.
So if you're in climb mode (actually if the FCU alt window is set above the actual altitude) then the speed target becomes green dot.
If you're in descent mode (if the FCU alt window is set below the actual altitude) then the speed target becomes MMO/VNE.
Thats's what I understand from the A320 FCOM.
Concerning the V/S issue, I'll look into it as well. This mode is really a headache, always disturbed by other things.
By the way, next time you post a screenshot, leave more of you wallpaper exposed ;)
Cheers,
Jean Luc
Hmm, ok. From videos I know for e.g. an emergency descend you select FL100, pull the thrust levers back to idle and press EXPED.
Will do this :D
And now down to TV, Germany will play in about 40 minutes ;)
Chris
Hello,
The latest version is available:
http://www.jeehell.org/A320FMGS_B13.zip
What's new in B13:
-Corrected some more VNAV bugs...
-MCDU FPLN page will show dashes when necessary data has not been entered
-Stall speed calculation reworked. I don't use FS anymore, there is a file in the PERF folder of each aircraft to set the vairous Stall speeds (Vs1g.txt)
-MCDU Perf Pages reworked: now F,S and O speeds are shown, RWY shift and THS added. The THR red/Acc altitudes and VApp are auto-inserted and can be overriden manually.
-MCDU Airport key functionnal
-NO SID, NO STAR and NO APPR features added in the MCDU.
-PFD design reworked
-AP2 logic, however there's no way yet to engage both AP during approach.
-AP/FD logic during TO phase
-SIOC creator now features the tabs for the OVHD and other new things
-Master Warning and Master Caution logic is at its beginning:
*AP Take Over button and ATHR instinctive disconnect buttons available as both offsets and keyboard shortcuts, see the documentation.
*Disconnecting the AP or the ATHR through the FCU will raise MC or MW alerts.
-New sounds can be played: Cavalry Charge, Single Chime, SeatBelts, No Smoking. However, I couldn't find any redistributable version of these, so you'll have to overwrite the files I provide with your favorite sounds...
-ATHR can be disarmed during APPR phase.
Cheers,
Jean Luc
Thank You JL!
I'm going straight now to make a flight!
Regards
a320231
Hello,
first time here and trying to install this great FMGS!!! Everything runs smooth apart from the throttle axis setup. I get a "current axis position = 0" when trying to set it up. I have the CH flightsim yoke, and throttle quadrant installed. Operating system is WinXP. What am I doing wrong?
Any piece of advice would be greatly appreciated :-)
Many thanks in advance,
Nikos
Hi Nico and welcome you to our group!
In order to set-up throttles you must have the FS run..
So, start your fs..select your plane...minimise it and then setup the throttles!
HI all,
I've translated a beginner's guide to my software from French to English, check the "First Steps.pdf" file. I've updated the archive, it's the same link for the download.
Cheers,
JL
Hi,
first bug report of today. After 3 hours of flight from EDDL (Düsseldorf, Germany) to LGKO (Kos, Greece) I have just discovered a few minor bugs:
- APU GEN is shown as ON after starting the server but it is OFF. You notice it after starting the APU and switching off the EXT PWR (it's gonna be dark :D). A double click on the korry solves the problem (OFF, then ON).
- Distance to waypoints on ND has no decimals.
- G-Load on SD: I think there is a rounding problem. On a stationary flight 0.9 is displayed, just sometimes 1.0.
- Chrono on ND: At 1h04 I noticed that there is no minute symbol but a second symbol after 04. At 1h18 there was a correct minute symbol.
- Chrono background should be smaller in width and a bit darker.
- Grey background of N2 value on startup should be a bit darker as well.
- Cabin temp: I set it to 21°C but the entire flight the cabin was at warm 30°C :D
- Rwy was not displayed correctly on ND. See screenshot where I am on an (almost) straight approach but the runway on ND has another heading.
Attachment 3982- After disconnecting the AP via the AP button on FCU the disconnect sound was played in a loop until I restarted the server after landing.
- Overlapping on EDW after landing.
Attachment 3983- Is the underline of LDG LDG GEAR on EWD correct?
Attachment 3984
Hi,
I will try to correct most of them quickly, hopefully by wednesday. A few remarks though:
- I'm not sure distance to wpt on ND has decimals, I will check that
- RWY HDG on ND: I'm not sure yet, but it might come from the difference between AIRAC database and FS database, since magnetic variations must have changed between the two...
- AP disconnect sound: this is not a bug, now you have to disconnect AP throught the "takeover button", which is the red button on the joystick on the real ACFT. Here, it is simulated either by an FUSUIPC offset, or by keyboard shortcut "A" whith FCU window focused. Same goes for the ATHR, better to disconnect it via "T" key.
If you forget and use the FCU "AP" or "ATHR", you can press respectively "W" or "C" to suppress the aural warning/ECAM messages.
Cheers,
JL
Thanks for the information! I will use the correct disconnection in about 3 hours on the approach to Düsseldorf ;)
Worked properly :)
Here comes the second report:
- EFOB calculated to 0 until I enter approach data. Is the approach data neccessary for the calculation?
- MCDU: Distance to T/C changes every 10 seconds for about 0,5 second. See screenshot.
Attachment 3985- I discovered that cabin temperature goes up and down the entire flight. From my set 21°C up to 34°C.
- AP DISC sound played sometimes 3 times and sometimes 4 times.
- On descent cabin pressure was down to LDG ELEV at FL130. Realistic?
But again no big error or something like that :) Great :)
Thanks for the report.
I will look at the EFOB error, it shouldn't be needed of course to enter the appraoch data, it should just increase the accuracy of the estimations.
I know for the T/C issue already, but cannot find what causes it...
The temperature problem seems to be caused by the packs. After engine start, try switch both packs off and on again.
The AP DISC sound should play for 1.5 seconds if you don't push the MW button.
Cabin pressure is not exactly accurate for the moment. I will try to enhance that in the next major release.
Cheers,
JL
Thanks for the info :)
I send the pictures of your FMGS in my cockpit (http://picasaweb.google.com/kikigey8...68200935976370) to a friend who will participate on my summer event and he cannot wait to fly with your FMGS ;) He says it is looking sooooo cool :)