A320 FMGS beta 26

[jeehell]

Hello all,

Well first thank you very much Matt for the opportunity you gave here on mycockpit, I really appreciate your support!!!!! I haven't been trolling "my" new forum since Matt created it, since I intended to officialy open it in a grand way!

Now, some of you might recall the FMGS screenshot posted in another thread, and I'm now pleased to release the first beta!!! After roughly 6 months of developpment, I'm quite proud of the outcome, and I plan to add much more features!

Here the link: http://www.jeehell.org/A320FMGS_B1.zip

Link for free old AIRAC cycle from Navigraph: here (http://www.navigraph.com/www/download/LEVELD-PMDG_0609.zip)

http://www.jeehell.org/FMGS.JPG

Tell me what you think of it, knowing this is STILL just a beta :wink: but please do so in the Q&A forum, thanks!

JeeHell

[Buddym]

Hi Jeehell,


Thanks for the software! Installing it in a few minutes, can't wait to see how it runs. I am currently using VAS, so you're in good company!


BuddyM

[Buddym]

Hi again,


I had meant to ask you the other day..... when you posted pics of an FCU panel, here those oanels you made?



BuddyM

[jeehell]

Hello,

I think I forgot to state it in the readme.txt, but if you use the default FSX A321, be sure to switch off the ELACs and other default FBW, just keep the raw input on the flight control (IE: on the overhead, turn OFF ELAC1, FAC1, ELAC2 SEC2, SEC3, FAC2, but keep ON SEC1)

Buddym: if you talk about a rather old post with pics of a hardware FCU and a MCDU, then I actually designed it on computer and Schaeffer company machined it.

JeeHell

[jeehell]

Hello,

After a long silence, some news at last with a download!!
Big news is you can import SID/STAR/APPR from level-D B767 procedure files!!

So full list of what's new:
-SID/STAR/APPR files syntax a bit modified, now APPRs and STARs are in separate files.
-Procedure import from Level-D B767, see ProcImport.exe in Navdata sub-folder. (Please note that level-D format is way much more complex than mine, some legs might not be supported, like manual legs for example)
-Holding patterns (both in navdata and in-flight).
-Distance intercept. (different than radial/distance waypoint).
-Built-in magnetic variation model, using WMM2005 magnetic field model.
-V/S climb mode.
-Mach mode corrected.
-Secondary FPLN.
-DIR page: RDL IN function.
-Track display corrected in some cases. Still seems to have some problems with left turn on fly-over waypoint??
-Updated some offsets.
-Corrected bugs here and there...


Link: A320FMGS_B2.zip (http://www.jeehell.org/A320FMGS_B2.zip)

I'm still working quite hard on this project. It took me long to make what seems to be few functions, but just the magnetic variation part took me one full holiday week ^^ . In fact I intended to add more features but since they are quite complex to code, I decided to publish this version.
I've been thinking about the possibility of adding a "Terrain on ND" feature and I think I have a solution. Need to do some testing to check performance issues. I'll also implement the coastline display on the ND.

Enjoy, and tell me what you think!!

[Buddym]

Thanks once again for your work, we appreciate it very much!


BuddyM

[jjborges]

Hello,

first of all thank you so much for this fantastic A320 emulator software.

I've followed the installation instructions nut when I run the a320fmgs.exe it open everything except the ND window and the MCDU, even when I click on the button show ND or MCDU it does not show nothing, maybe I'm doing something wrong.

Kind regards,

Jose Borges

[jeehell]

Hello,

Your problem should be corrected by now, try downloading again the zip file and make sure you start from scratch (i.e. delete all previous install files).
It's my mistake, since I use a multi screen setup, the windows tried to appear on your probably non-existing second screen...
Please tell me if it's OK now.

[jjborges]

Hello there again,

now the screens appear but it looks like this:

please see attached word file.

I'm using 767 Level-D AIRAC 0907 files for database.

Kind regards,

Jose Borges

[jeehell]

Try with FS launched.
What are your system specs??? (OS, ram, GX card??)

[jjborges]

Working fine now ;)

Thanks.

Cheers Jose Borges

[Anderson/SBSP]

Great job!!! You think use FSUIPC offset to use your software with hardwares like Opencockipts, FSBUS and etc?

[jeehell]

Hi,

There are already a good numbers of offsets available, which covers most of the FCU and MCDU swithces and leds. I do use them with opencockpits without problems. Check the readme file in the archive.

[jeehell]

A little preview of the EGPWS function:

http://www.jeehell.org/EGPWS.jpg

http://www.jeehell.org/EGPWS2.jpg

I still need to tweak it a little bit as it's quite hungry in terms of CPU (even on a quadcore 2.8GHZ), but the graphic result feels not that bad to me...

I'll keep you advised on any progress..

[ANDYSMITH]

Your amazing!!

[jeehell]

Hello,

You can now download the latest beta. A320FMGS_B3.1.zip (http://www.jeehell.org/A320FMGS_B3.1.zip)
What's new:
-GPWS callouts
-EGPWS display on ND ("Terrain ahead" callouts not implemented yet)
-TCAS callouts (limited to "Traffic" x 2, "Climb" x 2 and "Descend" x 2)
-Fixed few bugs as usual (particularly the one which prevented TOD calculation)

Next things I intend to do:
-A real user guide
-Maybe Suggy Brake pressure gauge (in the standby instruments package)
-Thinking about a general aviation full glass system, G1000 or Avydine's style.
-don't know yet any ideas??


Cheers, JeeHell.

[Anderson/SBSP]

Great job!!! You think creat somenthing like that to 737NG?

[jeehell]

Thanks for the kind word, but unfortunately I do not envision to create a Boeing version. The very reason I chose Airbus is that I had the chance to spend several hours on an A320 procedure trainer as a part of my studies. And even with beforehand basic knowledge of the FMGS, I still have to study the FCOM a LOT to model systems as close to the real thing as I want. So moving to Boeing would take too much time that I don't have as a freeware designer (I also have a life and a job :shock:)

Maybe one day, in the very distant future if I ever can finish the airbus version, but I really don't want to give you false hopes ;)

[Anderson/SBSP]

OK, i understand!! But keep the airbus project live, many people need your help!!

[jeehell]

Hello,

I've just finished the English version of the user's guide, along with a new version correcting minor bugs I found during the writing of the guide.

Download here: FMGS beta 3.1 (http://www.jeehell.org/A320FMGS_B3.1.zip)

Please tell me if you have any comment!!!!

[Matt Olieman]

Nice work :) Quickly went through the manual, very nicely done :) :) :)

Thank You!!!!

Matt Olieman

[Padraig]

-Thinking about a general aviation full glass system, G1000 or Avydine's style.
-don't know yet any ideas??


Cheers, JeeHell.

First of all, very nice work. I also had a quick look thought the manual, you really have out done yourself. Nice free addon for the people of Airbus projects.

As in regards to your other statement about the GA Glass cockpit, I think the Garmin 1000 would be a good choice in my world that is!

[jeehell]

Hello,

I'm still working hard on my project, and I have just added some cool options IMHO :cool:
-Network support
-F/O PFD, ND and EFIS
-Highly improved FCU graphics
-Enhanced EGPWS

A320FMGS_B4.zip (http://www.jeehell.org/A320FMGS_B4.zip)

http://www.jeehell.org/FCU1.JPG
http://www.jeehell.org/ND.JPG

As usual tell me if you encounter any problem!!

JL.

[jeehell]

Hello,

A new version is now available, see http://www.jeehell.org/A320FMGS_B5.3.zip.
Quite a lot of improvements:
-PFD speed tape with VFE, Alpha protection and VLS ribbons
-Overhead panel (80% done most normal operations controls are there)
-associated systems modeled: hydraulic, electrical, bleed air, pressurization, air conditioning, fuel
-Lower ECAM SD (all pages except STATUS, as failures and cautions not yet modeled)
-Autobrakes (and triple indicator)
-Engine start (automatic and manual)
-Most FSX aircraft SHOULD work now
-FSUIPC offsets

Hope you'll have fun with it!!

JeeHell
http://www.jeehell.org/OVHD1.JPG
http://www.jeehell.org/OVHD2.JPG
http://www.jeehell.org/SD.JPG

[totalflyer]

Tried to use the link but it wouldn't work...

[t1dUs]

great :D:D
but same as totalflyer, link does't seem to work

[jeehell]

Link should be working now, sorry for that!!

[jeehell]

Hello,

Made a big correction concerning the networking which tended to conflict with WideFS. Now I use goold ole winsockets instead of named pipes, hence you need to configure IP and ports, as indicated in the updated guide.
New link: A320FMGS_B5.1.zip (http://www.jeehell.org/A320FMGS_B5.1.zip)

Enjoy!

[Devils_48]

Are you serious... WOoooooow a freeware making competition to AST and Project majenta, I just downloaded your software, and now i'm in love with you LOL

Long life to this project!! This software gonna run my homecockpit for sure Wow !!

[jeehell]

Again a new fix, concerning the networking. It's not that easy to get it working see ;)
Link: A320FMGS_B5.2.zip (http://www.jeehell.org/A320FMGS_B5.2.zip)

Devils_48, thanks for the comments, but i'll disregard the "in love with you part" sorry :mrgreen: and anyway Quebec is too far :lol:

[jeehell]

Ok againnnnn a new version, now I hope this one will last longer, but I have a team of thorough beta testers trying to replace my blood with coffee :shock::lol:
Now MCDU should accept keyboard inputs and AP can engaged via the FCU. Sorry for that...

Link:A320FMGS_B5.3.zip (http://www.jeehell.org/A320FMGS_B5.3.zip)

[coolmanak]

I've been trying out your product for a few hours now, and I must say that I'm very impressed! I think you've just saved me a lot of money (that would have gone to PMSystems)!

Thanks a lot for your HUGE contrbution to the Airbus cockpit builder community!

[spiro]

i will second that graet work jeeheel i have not tryed it yet i am reading the pdf manual but later on today iwill
thanks jeehell very good work:D:D:D:D:D:D

[jeehell]

Thank you both,
Now I know I'll never be able to truly compete with PM, but I aim at the budget builder such as myself ;)
And remember, the only for it to get better is to report any problems/suggestions you have!!

[totalflyer]

Just curious if there is any chance that this awesome looking software
would work for an aircraft in FS9?

[jeehell]

Not yet, maybe in a future version.
I have to find a workaround for some offsets which don't work in FS9.

[navedb]

Hello,

I've just finished the English version of the user's guide, along with a new version correcting minor bugs I found during the writing of the guide.

Download here: FMGS beta 3.1 (http://www.jeehell.org/A320FMGS_B3.1.zip)

Please tell me if you have any comment!!!!

The URL isn't available anymore (for the FMGS Beta 3.1)??:?:

[jeehell]

No I removed it from my server to save HD space, but I can upload it again if you really need this version, but I suggest you try the 5.3 version ?
A320FMGS_B5.3.zip (http://www.jeehell.org/A320FMGS_B5.3.zip)

[navedb]

No I removed it from my server to save HD space, but I can upload it again if you really need this version, but I suggest you try the 5.3 version ?
A320FMGS_B5.3.zip (http://www.jeehell.org/A320FMGS_B5.3.zip)

Thanks a million!

[sierra]

Hi Jeehell!

Just noticed your software, are you familiar with VAS FMC a9 version?

Quite similar than your FMGC beta 5. Both freeware, both has great potential to evolve something what sim community has waited. If you guys put your skils to same project...... huge!

Is fmgc 5 ment to be shared to how many pc computers? i mean what is the most best configuration what parts should run in same computer, if we are looking prosessing speed of things.

Just had an idea, what if we could use your fmgc and vasfmc at same time in different pc:s? now problem is that they share some offsets i guess. Mostly joystic calibration of your fmgc is conflicting with vasfmc. maybe if you take joystic calibration away from server .exe and add another joystic.exe, so we can use what we like most.

Best regards
Jarkko from Finland

[jeehell]

Hello,

of course I know VasFMC, it's a nice piece of software ;)
However I decided to go my own way to fit best my cockpit projects, as VasFMC is aiming to be way more versatile than my project: airbus/boeing, FS,X-plane, windows, linux, etc.... Whereas I only aim at airbus on FSX.

As for developing together, it's probably not possible as Vasfmc is C++ and my software is coded under Delphi, and I'm afraid I'm probably not as competent as their team when it comes to code writing. As for sharing ideas with Alex and others, I'm open to that, but I haven't been in touch with them, so well if you read this Alex, feel free to ask any questions ;)


As for network sharing, the best combination currently is to run the server on the same computer as FS, then on a second computer you can run everything else. Be careful as my software eats a lot of network resources, so you need a good LAN (best is ethernet or PLC, wifi might be not enough).
If you're lucky to have more than 2 computers, you could use one for PFD+ND and one for FCU+MCDU so you'll have more CPU ressources for the ND EGPWS option.

Shunting the FBW/AP module of my software could work if vasfmc AP could accept HDG/altitude/speed instructions from my software, and I don't think that's currently possible.

Cheers,
Jean Luc

[jeehell]

Hello all,

After a couple months of development, the Beta 6 is finally out!
Click here to download (http://www.jeehell.org/A320FMGS_B6.zip)
What's new:

-Completely reworked AP/FD & FBW from scratch. FS AP is now completely shunt! The overall should be much more realistic and smooth. Only drawback for the time being is V/DEV which is not followed on DES mode as I was reported a problem with TOD calculation (thanks Markus ;)) and it appeared that V/DEV calculation is plain wrong.
-Added Missed approach support
-Revisions of SID, STAR & APPR are now possible
-Implemented CO-RTEs, ALTN and ALTN CO-RTE possibility (you can save your FPLN as a CO-RTE for later use)
-Corrected V/S mode problems, and added FPA mode.
-Few other things...

Again, enjoy and report any problems!!

[tom19]

Hi all!

I'm new with this addon but it looks really great.

Does anyone tried it with FS9? How it might work?

Regards,

Tommi

[jeehell]

Hello,

The comptibility issues come from some FSUIPC offsets which do not work under FS9.

Thus, you may have problems with Fuel flow, Gross weight, fuel used, APU, engines start, doors and the biggest issue with N1 hold. I'm not sure FS9 can hold a %N1 setting. Now it won't harm your computer if you try, and any feedback is appreciated ;)

[tom19]

Hi!

And thanks for your reply.

I've downloaded this beta 6 and first test is on progress.
At start I found bug (or is it?) with landing lights. After I shut them down
they keeps blinking. Well, I think I have to think again that FSX.

Anyway, thank you for your great product!!

[ciccio85]

Great job!! Thanks a lot :D

But I think that if you and VAS Project work togheter, you reach and overcome PM and AST!! :razz:

And if you rebuilt this for X-Plane and Linux, wow fantastic!! :D

Another thanks ;)

[jeehell]

ciccio85: Well, it's not actually planned sorry ;)

Anyway, some people have problems with the FBW, so I added an option to remove it and use direct joystick input.
And for those who don't like the default FSX A321, I added the iFDG A320 support. See the manual for more details.

A320FMGS_B6.1.zip (http://www.jeehell.org/A320FMGS_B6.1.zip)

[sierra]

Hi,

Thanks for this software, it´s great. I have some difficulties with it.

1. autopilot is turning plane too fast (pitch and bank) or there is something wrong on my setup. ND is quite slow, is it possible to speed up refreshing speed of ND and PFD?

2. Is it possible to add server program without throttle setting option?

Like if i would like to use vasfmc and yours lower ecam? now throttle settings are messing vasfmc up. Just like starting SD.exe it would open at power on, without staring OVHD.exe. I gues Then it should only read data from fsuipc offsets from FSX

Cant start engines from OVHD program.

Is it possible to change bitmaps of PFD and ND? vasfmc is still looking bit nicer:oops: Are those even in bitmaps or just coded at opengl? Maybe possible to edit with photoshop?

I really gonna try version 6.1 at evening after work.

Best regards
And wishes all the best for future evolving of FMGS

-Jarkko

[sierra]

Hi,

I forgot to tell, i´m runnig FMGS at 2 or 3 computers, Fsx located at most powerfull pc, OS vista home premium. 2 other has XP service pack 2. Fsuipc is registered and latest version.

Are you plannig to get FLEX temp impemented at systems, so we dont need to use toga at TO.

-Jarkko

[jeehell]

1. autopilot is turning plane too fast (pitch and bank) or there is something wrong on my setup. ND is quite slow, is it possible to speed up refreshing speed of ND and PFD?

Make sure there is the line fly_by_wire = 0 (NOT =1) at the end of the [airplane_geometry] section in your aircraft.cfg file.

The ND and PFD are set to run at 20 to 30 FPS, depending on CPU usage and EGPWS option. If you turned on EGPWS, try without it.
The ND FPLN line refreshs at a rate slightly lower than the rose/arc to save CPU.

What kind of network do you use? ethernet cable or wifi? Wifi seems to be not fast enough.



2. Is it possible to add server program without throttle setting option?

Like if i would like to use vasfmc and yours lower ecam? now throttle settings are messing vasfmc up. Just like starting SD.exe it would open at power on, without staring OVHD.exe. I gues Then it should only read data from fsuipc offsets from FSX

No, the point of the FMGS (as per in the real ACFT...) is to calculate the flight parameters to follow and process them to the different modules (instruments, AP/FD, ATHR, etc...)
If you wish to run VasFMC, then the VasFMC AP will wait for data from VasFMC FMGS, and not from my FMGS...
The SD, even if a simple gauge, is directly connected to the OVHD as most functions/variables/systems do not exist in FS or are not correctly modeled. The SD would then be showing only very basic data, and some pages wouldn't ever be active.




Cant start engines from OVHD program.

Engine start requires a specific order (the same as in the real acft):
1) Electric power (either GND or APU)
2) Bleed air (either GND or APU, check the manual how to activate GND HP bleed)
3) X-Bleed valve open (or auto)
4) Fuel pumps on
5) Engine start switch on IGN
6) Engine Master 1 or 2 ON (usually ENG2 is started up first)
7) When Selected engine N1 has stabilized, select the second master ON
8 ) When both engines are good to go, Start Switch to NORM




Is it possible to change bitmaps of PFD and ND? vasfmc is still looking bit nicer Are those even in bitmaps or just coded at opengl? Maybe possible to edit with photoshop?

ND and PFD are hard coded in OpenGL (same as VasFMC I think), it allows to resize at will without losing quality, so it's not possible to edit anything.
As for VasFMC gauges looking nicer it's your taste ;) but what do you think mine lack? I could improve that...




I really gonna try version 6.1 at evening after work.
Tell me what you think, I need input from people to make it better, as it flies correctly on my setup.

As for FLEX, yes I'll definitely implement that, but I don't know when. I'm currently working hard on AP/FD/FBW.

[sierra]

Hi,

I had little time yesterday to test FMGS 6.1.
My setup: main pc has vista home premium, intel e8400 dual core processor, 4G of memory, ati HD4870 displaydriver. FSX is running frames from 25-60.

Second pc has XP professional, athlon 64 1800+ prosessor, 1G of memory, Ati 9250 display driver,

Third pc is old office pc, pentium 3 inside 1.4Ghz, xp pro 512 of memory.

Main pc runs fsx, fmgs server.exe+fbw.exe

Second pc runs PFD, ND, Upper ecam and mcdu

third pc runs OVHD+SD

Second computer is having problems...too slow, i think that is causing ati 9250 display driver wich is too old and not enough powerfull. it is causing FSX to not working correctly because of slow frame rate on this second pc. So data is not moving enoug fast to main pc. I use ethernet cable to connect pc´s. Vasfmc is running fast on this second pc.

Just ordered faster ati HD 3670 for this second pc, let´s see how it will improved speed of FMGC.

-Jarkko

[jeehell]

Hi,


Second computer is having problems...too slow, i think that is causing ati 9250 display driver wich is too old and not enough powerfull. it is causing FSX to not working correctly because of slow frame rate on this second pc. So data is not moving enoug fast to main pc. I use ethernet cable to connect pc´s. Vasfmc is running fast on this second pc.

What do you mean by "causing FSX to not working correctly"?
Could you try to run all my software on your second PC? maybe it's the networking soultion I use which is not efficient enough. If VasFMC is running OK, then my software "should" be running ok as well.

Thanks for the feedback,
Jean Luc

[sierra]

I mean fsx is slowing down moves like slide show only 5 to 10 frames per second (normally 25-60), like maybe it will wait for autopilot command from second pc wich is wery (effecting like it will send command´s to FSX, but all command´s are late so aircraft might be on different positioning (pitch and bank) as it was at point when FMGS was reading it´s values. You get what i mean?) slow cos many open windows at it (maybe this old display driver is causing that it only has 128mt of memory on board). and second pc is running 2 ftf display. Another possibility of causing slow speed on that second pc is it´s prosessor, it these several programs on it will be too much load for that?

I tryed to use all of FMGS program on same computer.... even slower. I think something is eating resources from pc.

Still vasfmc can easily setup and runned from my 3 pc setup. i really would like to be able to use your´s FMGS on my setup. I just need to figured out what is causing all these problems.

At widefs .ini i use values for wait_for_new_data=50 (normally 500) this cos vasfmc is running then smoother.
And Data scanning pol is set to 250

Best regards

-Jarkko

[jeehell]

Well if the FMGS server and the FBW are on the FS PC, FS won't wait data from any other software. Try only launching FS, FMGS server and FBW (no other clients on the network). That would confirm that, if it still is slow, then I'm affraid my software is too "big" for you CPU :-? (it's probably not as efficient as VasFMC I have to admit). You could try to launch the FMGS on an other computer (keeping the FBW on the FSX one).

When everything is running, check the task manager to see which software eats the most CPU, and if your network is saturated or not.

Keep me posted,
JeeHell

[sierra]

Hi,

I will do some more testing on different setup´s. First i have to wait that new display driver card will arrive.

I just tought that your FMGS is working close to vasfmc wich FBW is working better if your frame rate is good enough. working like if i pull the stick back to get nose up lets say 10 dec. I´m then during rotate i watch PFD if it has slow frame rate then plane at fsx is all ready 20 dec nose up, while PFD still at 10 dec before it reach same value than fsx has. This is if you have framerate too slow.

Is it PFD.exe or server wich send´s commands to fsx? of course it is going via server.exe. This could cause that if fsx is running faster than PFD, it could getting late.

[jeehell]

Hi,


I just tought that your FMGS is working close to vasfmc wich FBW is working better if your frame rate is good enough. working like if i pull the stick back to get nose up lets say 10 dec. I´m then during rotate i watch PFD if it has slow frame rate then plane at fsx is all ready 20 dec nose up, while PFD still at 10 dec before it reach same value than fsx has. This is if you have framerate too slow.

Is it PFD.exe or server wich send´s commands to fsx? of course it is going via server.exe. This could cause that if fsx is running faster than PFD, it could getting late.

The PFD, E/WD and SD send no data to the server.
The ND send data only if the EGPWS is on (which I do not recommend on slow computers, as it IS CPU consuming)
The OVHD send data to the server but not critical in terms of flight controls (only system status)
The FCU and MCDU send data only when buttons are pushed/turned.

All autopilot data are computed by the server and the AP.FBW software.

If the PFD is too slow there are 2 possibilities:
1) Your computer is not fast enough (CPU or graphic card)
2) Your network doesn't support the flow of data (Widefs + my software) which could be caused by an overflow of data (either from my software or from FSUIPC)

If your new GX card doesnt solve the problem, you could try to restore you Widefs settings to default.

[jeehell]

Hello all,

I've finished a new version, just in time for Christmas ;)
A320FMGS_B6.2.zip (http://www.jeehell.org/A320FMGS_B6.2.zip)

Here's what's new:
-N1 ratings depending on OAT and pressure altitude (real numbers from the FCOM)
-FLX take off
-FCU resizable
-MCDU lines can be moved up/down to match a physical faceplate on your hardware setup
-Border of instruments can be removed
-Quite a few bugs corrected as well.
-N1 hold is now done by my software (not by FS anymore), so it's a step toward FS9 compatibility. If someone could test, i'd appreciate!

Wish you all the best for these times of celebrations,

JeeHell

[kikigey89]

Hi,

thanks for that excellent software! Looking forward for more improvements :)
I'm using it in my A330 Cockpit (http://picasaweb.google.com/kikigey89/ProjectA330).

While integrating your software in my cockpit I discovered some FSUIPC offsets failures:
- MCDU: 69 should be BRT, 70 should be DIM. But currently 70 is BRT and DIM is N/A.
- ND FO: First bit should be CSTR, second WPT and so on. Sending 0 to the variable (all bits off) activates CSTR. First bit is WPT, second NDB and third APT. VOR is N/A.

Would be great if you check if this is a failure in your software or in my configuration.

Chris

[jeehell]

Hello,

Nice to have a project such as yours as "customers" ;)

I just checked the offsets you're talking about, and indeed BRT and DIM are inverted in the documentation, but both should work (I tested 69 and 70 and it worked?). Try again and tell me please so I can check further?

As for the FO EFIS buttons, I found out that the user guide is plain wrong :oops:
In fact you don't have to set the bits separately, but simply assign a value to the whole offset $66CF:
0:CSTR
1:WPT
2:NDB
3:VOR
4:APT

[kikigey89]

Hi,

EFIS works now with values 0 to 4 :)

But 69 is not DIM. It seems that it is left or right arrow.

Chris

[jeehell]

Ok I corrected the MCDU problem, I tested with a different version than the release B6.2, my mistake again :oops:
Here the link :A320FMGS_B6.21.zip (http://www.jeehell.org/A320FMGS_B6.21.zip).

Keep me posted if it still doesn't work :mrgreen:

[kikigey89]

Thanks! Great work :)

One mistake in the new manual:
"Cpt EFIS pushbuttons (CSTR, WPT, etc...). Set to the corresponding value:"
This is valid for FO EFIS, but not for CPT EFIS. CPT EFIS is controllable via bit setting, not value setting.

[jeehell]

Geez I need sleep:eek: It should be back in order now, thanks Chris!

Good night Gentlemen

JeeHell

[matchouz1]

Hi,

Jean-Luc, great work! I wonder if there any updates on this! Is FMGS able to run on FS9?

Thanks,

Mat

[jeehell]

Hello Mat,

I'm currently working hard on next release which should include an (hopefully) accurate VNAV model and better vertical AP modes. I hope it'll be ready in a month or so.
As for FS9, I don't know what is the degree of compatibility since I do not have FS9, but it seems some people managed to get it running, minus some systems which use FSX-only FSUIPC offsets.

Cheers,
JeeHell

[kikigey89]

I'm using it with FS9. It works so far, except those only-FSX-offsets, e.g. APU.

I had a lot of trouble with VNAV and AP and hope it will be fixed in the next release :)

[matchouz1]

Most def. Thanks for that.So you're saying you can't use the APU? Let's see what Jeehell says about the rest! Also, I was wondering if there's any chance the software might be extended to an A340 type of plane? Wouldn't that essentially imply tweaking the flight dyanmics and the ECAM screens? Looking forward to reading what you say about this!

[jeehell]

Here are the offsets used that are not compatible with FS9: Fuel flow, Gross weight, fuel used, APU, engines start, doors.

Which means that:
Fuel Flow, GW, Fuel Used and Doors won't be displayed correctly on E/WD and SD.
APU simply will not work.
Engine start seems to work?

There may be other issues that I'm not aware of.

But the biggest problem is probably not the offsets, but the tuning of flight governs in the AP/FD module. ANd I would need to be able to test myself to see if it works correctly or not.


As for the A340 version, that imply indeed tweaking the ECAMs and flight dynamics, but the FMGS part would have to be deeply reworked I guess. And I'm not even near finishing the A320 version so I don't even know myself if I'll do the 340 version...

[matchouz1]

Right no problem on the A340. Didn't know it implied so much? Thanks anyways for sharing insight into the offsets. I guess I might try moving to FSX! Don't know how that runs on a MBP though! Happy flying!

[kikigey89]

Currently I have to time to test it in my cockpit (exams at university) but in a few weeks I will take a few days to continue working and to continue testing Jeehell's FMGS.
Then I call tell you more.

[QalaMuc]

Hi Jean-Luc and everyone else,

i am experimenting on a setup with FS9, vasFMC and your A320 systems. At this moment I would like to go with vasFMC for the PFD+ND and use your FMGC for both ECAMs.
But when i have vasFMC and the FMGC Server running at the same time, they start to fight about the flight director.
On the ground, vasFMC switches it off and the FMGC server turns it on again. This happens 2-3 times per second and really wrecks up performance.

Since your simulation doesn't even utilize the FS9-FD, would it be possible for you to release it so the two can coexist in peace? ;)
Or has anyone else here already solved this problem?

Regards,
Nils

[jeehell]

Hello Nils,

Even if I removed the problem with the FD, you would probably encounter other compatibility issues between VASfmc and my FMGS server.
Since I dratsically changed the AP module for the next version, I'll see if the FD problem can be solved, but you'll have to wait a little bit for next version to test (I expect the next versions in a month, maybe less, probably more...).

[matchouz1]

Hello again,

I was wondering if the software can run with OPENCOCKPIT software, such as the MCDU or radios? Many thanks!

[kikigey89]

I'm using the OC MCDU and it works fine with Jeehell's FMGS.

[matchouz1]

Any configuration you needed to do?

[kikigey89]

Key presses are sent via IOCP to SIOC. SIOC reads out the defined variable and sends corresponding FSUIPC offsets to control FMGS.

[matchouz]

Hi,

So I know have the chance toinstall FMGS on FS9, but I have a basic question regarding installation. After reading the pdf, I've installed the whole 6.2 version like so: FS9/A320FMGS_B6 I also changed the aircraft.cfg, but don't really know how to assign this panel to an airplane (I mostly use project airbus ones)

Many thanks for the help

[kikigey89]

This is not a panel, this is a homecockpit software ;) You can display PFD, ND and ECAM on external screens with it.

Btw, Jeehell, would it be possible to program a dummy APU for FS9? FMGS should recognize if it's running on FS9 or FSX and in case that it's running on FS9 there should be a dummy function of APU (startup, elec. power, bleed air). Because of my FS9 I cannot use the APU in your FMGS but it would be great if you can implement it in the way that FMGS simulates an APU :)

Looking forward for the upcoming version :)

[jeehell]

Hello Kikigey89,

First thank you for answering other people faster than me ;)
As for the APU in FS9, yes I will do it, maybe not in the next version, as I do have currently a lot of work with the VNAV which has taken loooonnnng weeks, and will take some more before any release, so I do not wat to postpone the release too much.
But definitely in the version after that.

As a teaser, I've already done the climb profile calculation with fuel comsuption and ETE. Just need to adjust it with SPD/ALT constraints, then do it for CRZ and descent :twisted: (and if you're all nice and quiet, I'll even take the wind profile into account in the calculations, but it'll probably be for another version)

[kikigey89]

Great :) Take your time, your support and work is really great, that's the reason why I told goodbye to vasFMC ;)
I know from my own FS software (Live!Flight) how much time programming takes ;)

[matchouz1]

Hi,

Thanks for the tip. I've connected my computer running FS9 to a laptop through WIDE FS (see attached, it says I'm clearly connected to FMGS) The User Guide says I should power up if I want to see the ND etc. My first question, is where to do that in the OVHD (see pic attached for my OVHD as I see it). Some buttons such as anti-ice and the like work, and actually emulate the function on FS9, but in some others, nothing seems to happen. Is this a problem that anybody knows about?

any help would me most welcome!

Thanks,

[kikigey89]

I don't know exactly which buttons really work at this time.
But for power up, press all OFF-buttons to get them on (or auto) and connect external power.
After IRS align in MCDU the ND should work.

[matchouz1]

Right... thanks alot! I'll try this when I get home. In the meanwhile, can you tell me if the overhead is supposed to look the way it does (see attachment in previous post!). Looking at the screenshots from the user guide, I have an impression that the right-hand part of it is missing. Nor can I find the upper overhead. Also, I can't click on the light switches. Lastly, how do I activate the engine start panel? Many thanks again

[jeehell]

Hello,

Yes it seems your screen is smaller than the default OVHD size (as I use a nice 24" desktop screen, I didn't take time to check that). However you can resize it, like you would resize any window by grabbing an edge with the mouse. If the resize pointer doesn'at appear, check that when you right click on the OVHD, the "Hide border" item is not checked.

To show the upper OVHD, again with a right click then simply in the menu " Show upper OVHD".

To enable the engine start (and the auto-brake) on the OVHD, select "options" in the right-click menu then check the corresponding items.

As for buttons actions, all of them currently modelled have an effect (well maybe except the ditching one), which can be sometimes just an item added in the E/WD or on a SD system page. Of course Isolation valves or galley shedding won't have direct effect on the aircraft handling or PAX unhappy, but corresponding system pages on SD will/should have captions showing up.

For the lights, the switches are a bit tricky I have to admit, you need to click on the captions next to it. Except for the landing lights, which are really really tricky ;-), and you have to click just above (on) or below (retract) the switch or to its right (off).

Hope that was helpful,

JeeHell

[matchouz1]

Thanks JeeHell,

It did help. For the overhead, I right clicked and then deselected hide border. Upper OVHD shows very well. As for button actions, txs for the tips, I see how they work now. However, I still have a problem which you might give me a hand with? the process is this. On the laptop which I want to run the ND, PFD etc, I turn on WIDE FS (status: connected), then launch FMGS server, then, say, double click on SD or, ND. When pannel is black, right click on options, and it reads, connected to FMGS server (like in my previous print-screen attached in a previous post!). However, the problem is that the screen remains black! I've tried turning on all buttons, but nothing will do. Is there normally a process to follow?

Would sure appreciate the help as I am inpatient to try it out!

Thanks

[jeehell]

As kikigey said, on your screenshot it seems that there is no electrical source connected (meaning that APU is OFF and external PWR is not ON).

Since APU is not supported yet on FS9 version, you need to use external PWR. To do so, make sure it is availabe (green AVAIL on the PB), then click on it so it turns into a blue ON. Make sure now that bus tie is not OFF, select batteries ON if not done already, and the screens (PFD,ND,SD,EWD and MCDU) should turn on.

Cheers, JL

[matchouz1]

Hi JL

It worked! Many thanks! however, there are new issues now.

I use FS9, and in the manual, it actually says you should be able to press on buttons on the ECAM control panel located in the pedestal. However, my plane/cockpit doesn't support this. therefore, is there a way I can still control which pages I want the SD to show?

Also, I've looked through the user manual, but I can't seem to start the engines! I've checked bus tie is on and downloaded checklists to make sure I follow the procedure (i reckon it might have something to do with the air packs!) Can I kindly ask you that you quickly outline the engine start procedure...So far, I can only hit Ctrl E

Many many thanks!

[jeehell]

Hello,

To change the ECAM pages, there are keyboard shortcuts after clicking on the SD window, check chapter 6.1 in the user guide.
You can use FSUIPC commands as well, see the offset table at the end of the user guide.

How to start the engines: you need electricity, HP bleed air and fuel.
Electricity seems OK now.
HP bleed air can only be accessed through external connection as APU doesn't work in FS9. To connect the external air, click on the small "GND HP" label on the OVHD, located between RAM AIR and APU bleed pushbutons (careful to click only once, if you click twice it will disconnect...). Make sure the X-bleed valve is on OPEN. You can check the status of bleed air on the bleed page in the SD.
For the fuel, simply switch ON all the fuel pumps on the upper OVHD panel.
Now, the start sequence itself is fairly easy, you just have to switch the engine start mode selector on IGN/START, then the MASTER switches ON (usually first engine is N°2, then when engine is running you start engine N°1). When Both engines are running, put the engine mode selector back to NORM, make sure all generators and packs are running then you're good.

If you're still having troubles starting the engines, there maybe is a problem somewhere else...

JL.

[matchouz1]

Hi JL,

Again, many thanks... Yup, it seemed easy. Pressing the buttons works like a charm. I still can't figure out the engine start-up, but I'll keep on trying. Perhaps the tricky bit is clicking the GND HP. Anyway... I promise to ask a last question for a while. Now that I have things roughly up and running, I meant to ask whether there are some compatibility problems between your software and VAS-FMC. I haven't noticed much, only that I don't have a proper control of the engines thrusters. That is, even when I accelerate to below 50 % or so, nothing will happen. Only when I push the engines further will they spool up (not ideal for taxying etc...)

definitely looking forward to hearing about this. It seems I'm getting ready to go and fly!

Thanks again

[jeehell]

Well I've never tried vasfmc along my software, but I'm pretty sure there ARE compatibility issues. Probably AP and ATHR won't be working correctly, and the only way to prevent that is either not running VASFMC or not running the FMGSserver, which means that OVHD logic, SD an E/WD won't work correctly.
I'm sorry, but since VASfmc and my software are doing the same things, they're not meant to be ran together (do you run FS9 and X-plane at the same time ;)?)

Cheers,
JL

[brynjames]

Jeehell, are you building an Airbus cockpit with your software, and if so, how about a screenshot or two? ;)

--
Bryn

[jeehell]

Well I kind of do and kind of don't :o

Right now I don't have enough room to build my dream (well I do have enough but the wife doesn't think so ;)) so building is sort of on standby. I did make an FCU with the left EFIS and a MCDU, which can be put on the desktop when I'm not programming (otherwise no place for the keyboard :roll:), there are some pics in the gallery, and I recently bought an FDS throttle in the classifieds (the old plastic version, not the metal one), which I'm currently cleaning, greasing, tightening some screws etc...

We are currently searching for a new place right now, so a part of the deal was a few sq.ft to put a small pit somewhere (probably CPT side only), but I suspect it'll be a long road before I start building anything (my area ain't exactly the cheapest part of France when it comes to real estate :( ) And actually I really enjoy the programming part so far, so I'm not in such a hurry

http://www.mycockpit.org/photopost/data/602/medium/Photo_012.jpg

http://www.mycockpit.org/photopost/data/604/medium/mcdu2_001.jpg

MCDU is from opencockpits, with a really good quality/price ratio! and the FCU is made with frontplates from schaeffer. Everything is linked to my software with opencockpits cards.

I dont have pics of the throttle, I don't have much time to work on it these days, and it still needs some refurbishing and wiring.


On the software side, I'm almost done with VNAV, even if i'ts not perfect, I can achieve good results (sometimes less than 500ft of accurracy), maybe more on this soon, but first I have holidays in the west indies 8-)

[brynjames]

That FCU is a beautiful job. Must look into your software a bit more deeply!

--
Bryn

[jeehell]

Thanks for the compliment ;)

[kikigey89]

Cannot wait for your new version.
vasFMC crashed on my online flight one hour ago and I'm very annoyed by it...
I was unable to control the aircraft anymore and I had to cancel my flight...

[kikigey89]

Hi,

any idea when it will be released? As I said, cannot wait to implement it :)
Have to plan my cockpit work a few weeks in advance because I have to do a lot of work for university...

[jeehell]

Hopefully sometime during the next couple of days :D

[jeehell]

Hello all,

The beta 7 of my A320 software is ready at last!!:D

Here what's new:

-Redesigned VNAV from scratch: calculation of the flight profile according to the OAT and weight. AS of now, TOC, TOD, SPD LIM and DECEL pseudo waypoints are calculated and displayed.
-Integrated SIOC support (other I/O can still be interfaced with FSUIPC, as before)
-Better AP/FD logic
-FBW enhanced, autotrim now functional (only if FBW is active)
-ND font size reduced
-GND HP, EXT PWR can be connected through the Add-on menu in FS
-Windows can be locked and stay on top
-A lot of smaller issues corrected

Link: http://www.jeehell.org/A320FMGS_B7.zip

As usual, feel free to report any problems encountered, I'll do my best to correct those !

JeeHell

[jeehell]

Now out, see the relevant thread :D

[kikigey89]

Nice :) But currently I have no time to implement it... :( Hopefully in the next few weeks :)

[kikigey89]

Oh my gosh! Your SIOC creator seems to be great! Have to test it, but I guess with it the implementation will be done just in a few hours!
Thank you!!!!

[dcutugno]

Hi, i would like to try your beautiful software, but in the next few days i will recieve the new PRO-M FCU from FDS, can you add support to this unit? It use the Glare 3 interface, you can ask to Peter he will provide you an sdk or all you need.
After that i will try to write an InterfaceIT .xml to use your software with those system cards and easy programming.

Good work, keep it going!

[kikigey89]

Got a problem: When starting the FMGS server, the throttle message appears. But if I click on "Show Throttle Setup" nothing happens.
Also the menu in FS for GND PWR does not appear. Tested it with FS9 and FSX...

[jeehell]

Hello,

Kikigey89: if you downloaded the file yesterday, try to download it again, I made a small correction enabling the calibration again. If it stills doesn't work, you could copy the throttle.cfg file from a previous installation, but it should work (it does now on my setup).
The items in the Addon menu do not always appear, especially if you have other addons using this facility.

dcutugno: Well I would like to do so, but I'm not even done yet with the opencockpit hardware, and I don't own the FDS FCU, so testing will quite be difficult, as I suspect the SDK they provide is for C programmers and not for Delphi, so I'm not sure I'll be able to do that. I do not feel like getting in touch with them officially to get the SDK and not implement it afterwards, seems a little awkward to me.
If you're really interested, try to get yourself in contact with them and explain the reasons, if you get me the SDK I'll be happy to at least consider it ;-)

[dcutugno]

Here it is:
Glare Software v1.6.8
Glare Integration Module API Documentation v2.00

at: http://www.tekworx.ca/downloads.html
There is a PDF where all is explained also VB activex controls, hope you can have a look, i can be your tester for fcu.

[kikigey89]

Throttle setup works now :)
But how can I achieve that there is a EXT PWR entry? Somehow I already got the RAT and GND HP entry but no EXT PWR which I need to activate all displays.

[jeehell]

dcutugno: Ok, let me have a look first, I'll keep you advised sometime in the next weeks if I can achieve anything with that, but I must warn you at first sight it seems it'll take me some time to implement that...

Kikigey89: That's weird. Do you have any other entries besides GND HP RAT and FSUIPC options?
When you start the OVHD, check that you have the entries in the menu. If not, before proceeding further for your flight, close the OVHD, wait 30s and try again. That's the best shot.
I'll look into that anyway. Maybe I could add FSUIPC offset commands for those options if you think that's useful?

[kikigey89]

Yep, your way worked. I tested it 3 times and 2 times the menu was complete. In the 3rd try just EXT PWR was there.
FSUIPC offsets would be great, then I can write a program in VB for it.
And yes, I have also other entries in there: SquawkBox (for VATSIM) and ActiGate (don't really know).

[jeehell]

OK, fsuipc offsets added to to-do list ;)

[kikigey89]

Okay, tested it again im my homecockpit.
1. How does the SIOC creator works? Assigning values is no problem, but on which computer do I have to run the creator and does it have to run all the time? I ask because I tried a lot in the last 3 hours but it did not work...
2. I just use push encoders (1 input) so I cannot configure the encoders. Can you program a feature for push encoders, that a push for less than 1 second means a push and longer than 1 second a pull? I planned to buy push/pull encoders but not in the next time.
3. Does your QNH display also supports the output "STD" and the other displays in managed mode dashes? As said, cannot try it...
4. I want to create a performance for CLS A330 (I use this aircraft in my cockpit). PERF calibration says "No aircraft.cfg file found, aborting test.". Which file does it mean and what do I have to do?

Sorry for my questions but I want to get it run :)

[Buddym]

Kiki, I love the idea of implementing the pull by holding the encoder button for over a second.

Buddy

[jeehell]

I'll try to answer those questions:

1) Maybe the user guide is not helpful enough, I wrote it quickly to release the beta sooner :oops:
Overall Process:

Run the Sioc Creator on the computer where you run the FMGS server, and run it in the same folder as the server (basically keep the folder structure I supply...). I suggest you run SIOC on that same computer.

-General Tab: I think it's pretty obvious: SIOC's IOCP server IP and port, and the folder where sioc.exe is found.

-MCDU tab: if you use the USBkeycard only. You check the various options, and follow what the warning messages tell you :-)
(if your card is on another CPU, you'll need to copy the IOCKey.ini file from SOC creator folder to IOCKey folder before clicking OK on the 2nd warning)

-FCU/EFIS tab: fill in the input/output numbers, device numbers etc as in a SIOC script.
If you want to leave out a field put -1 in the number field, just the missing encoder or P/B or LED won't work.

-When you're done, save your work then click "apply configuration" in the menu, and everything should work.


It should possible to use SIOC creator on any computer, but then you'll have to make sure
-There is a SIOC installed on that computer (it needs the SIOC compiler executable)
-After applying the configuration you 'll have to copy the jeehellware.ssi and the sioc.ini to you real "SIOC" folder
-You'll have to copy FMGSServer.iocp.ini to your FMGS server folder.

2) Long Push for pull is a good idea, I'll see how I can implement it in next version, for now you may want to leave out the encoder and script that part yourself...

3)yes, STD and dashes are supported

4)Again, I wrote the guide too quickly.
To use the PERF calculator, you need to create a new sub folder for your aircraft in the PERF folder. Let's say "A330CLS". Copy all the files and folder from the iFDGA320 folder to that folder.

delete all the files in the FLEX and profiles (keep and maybe modify by hand the CLBn1.txt, V1.txt, etc...)

Now go back to the FMGS server root. Edit the APFBWcoeff.ini
The structure of this file is much like an FS aircraft.cfg file.
In the [General] section you declare the aircraft you intend to use with the following syntax:
ACFT.X=Name where "X" is the aircraft index number and "name" the name of the folder in PERF, so you would probably declare:
ACFT.3=A330CLS

Now each aircraft has a list of APFBW coefficient, under it's corresponding [ACFT.X] section.
I suggest you copy the iFDG listand change the aircraft index. If you wish to modify those, good luck, all you need to know is that they are PID based coefficient, then lookup the internet for PID correctors.

Now launch the PERF calibration software. In the dropdown list, select A330CLS, then you're good to go!! (I hope :D)

[dcutugno]

Another problem i found is that, i have a lot of procedures in 767 format, how i can convert all of them instead of selecting one by one? They are too much to manually convert them.

I cannot use the Performance calculator, it tell aircraft.cfg not found, i followed your previous instructions.

Question: do i need the registered version of FSUIPC?
Thanks

[kikigey89]

Me, too. Cannot get it running. Neither on FS9 nor on FSX.

Batch converter would be great, too :)

I think you don't need the registered version. But for homecockpit it is always good to have the registered version to support all features.

[jeehell]

Hello guys

I found the problem with PERF calibration software, I'll modify it tomorrow if I have time.

Another hint, for SIOC creator, your SIOC installation folder should not be the default C:\program files\IOCard\SIOC, as "program files" folder is apparently protected by windows from external software writes, so I need to find out how to avoid that issue, but for the time being, install your SIOC somewhere else...

Cheers,
JL

[jeehell]

Hello,

I corrected the PERF calibration problem, it should now work correctly (I updated the guide so it's a bit more explicit now)
I as well added the FSUIPC offset for the GND HP, EXT PWR and RAT, corrected a small glitch when SIOC creator was used for the MCDU.

As of SIOC creator, it won't work if you installed it in the default folder (i.e. c:\program files), as program files is a read-only protected windows folder, and SIOC creator needs to create new files in it.
So you'll have to re-install SIOC elsewhere (c:\SIOC or c:\games\SIOC will work fine ;))

The link: http://www.jeehell.org/A320FMGS_B7.1.zip

Cheers,

Jean Luc

[kikigey89]

Hi,

MCDU works now, but not the entire other stuff (3 master cards on 1 expansion card).
I saw this log.txt and opened it:

Config_SIOC ver 3.4 - By Manolo Vélez - www.opencockpits.com
Open file "JeeHellWare.txt"
00:27:33
Phase 1
.OK.

Phase 2
ERROR! - 31 -
Line: 67 Var 31, name CPT_QNH_DISP1, Link IOCARD_DISPLAY, Digit 16, Numbers 1
%FAILED%

Could this be a problem? Don't know if it's too late for me this night :D
On my computer I have 1 expansion card and 2 keys cards.
Do I have to use no device number as I have just connected 1 expansion?

[jeehell]

Hello Kiki,
Well done, another bug busted :mrgreen:
It is corrected, redownload the file http://www.jeehell.org/A320FMGS_B7.1.zip
It had nothing to do with your multiple mastercards, don't worry about them. However, you'll have to use the device Number for your mastercards (each mastercard should have a device number (sometimes called index, OC documentation is not always...explicit ) in the SIOC.ini file)

By the way, I think the FO EFIS will not work entirely, I don't remember exactly which input/output are programmed so far (gosh my memory can not memorize over 10000 lines of code :???: ) .
The next real version will have all those added, plus the OVHD (I hope).

JL

[kikigey89]

Thanks^^ I think in the next time I will find all bugs.
It's really great that I can report the bugs and you correct them instantly. Guess the last version of vasFMC is one year old...

Is the device number which I have to enter the index number of my mastercards, defined in sioc.ini? I mean the numbers 0 to 2. Last evening I aleady thought about that issue but there was no change if I entered 0, 1 or 2 as device number.

You know, I have an A330. A friend of mine is optimizing my .air and .cfg files to get a real behaviour of the real A330. He knows a lot about modifying these files. He is also trying to create real A330 performance data for your FMGS. But he has some weight problems. He said, that your software did not accept his FLEX and V speed values if a ZFW of 170t is entered.
Maybe I will give him the link to this forum so that he can describe you the issue more in detail.

[jeehell]

Well, this is really the dark side of SIOC.ini :roll:

Here what OC says:


[ MASTER=(Device index),(Type),(Number of cards),(Device number) ]

[ Device index : Index used in SIOC variable like device, this is the card used for SIOC sentence ]
[ Use 0 for only one card, for this value you not need specify Device number. If you not use DEVICE parameter in a definition in SIOC script, the default index used is 0]

[ type = 0 : Master Card Emulator ]
[ type = 1 : Master Card connected directly to parallel port ]
[ type = 2 : Master Card connected throught compatibility cable to parallel port ]
[ type = 3 : Expansion Card connected throught parallel port ]
[ type = 4 : USBExpansion Card used ]
[ type = 5 : Opencockpits MCP module ]
[ type = 6 : USBOutputs Card used ]
[ type = 7 : Opencockpits EFIS module ]
[ type = 8 : Opencockpits Radio COM module ]
[ type = 9 : Opencockpits Radio NAV module ]
[ type = 10 : Opencockpits Radio ADF module ]
[ type = 11 : Opencockpits Radio ATC module ]

[ Number of Cards = Master cards connecteds, 1 to 4 for expansion cards, 1 for a Master card directly connected or Emulator ]

[ Number of device = 0 for Emulator or first USB card detected, parallel port address, device number for specifies USBexpansion card ]

So if you're using 1 USBexpansion with 3 mastercards, I guess your declaration in SIOC.ini should be:
MASTER=0,4,3,0

And thus you won't need to specify the device index in SIOC creator.
When you used to do your own scripts, how were your inputs numbered for mastercards N°2 and 3? I cannot really test that part as I only have one Master, but the field you have to fill in SIOC creator are the same you have to fill in the CONFIG SIOC (or in notepad, if you used notepad...).

For your PERF issue, maybe there are limitations according to regular A320 ZFW inside my software, and 170t is quite heavy for an A320. I need to check how that is coded.

[kikigey89]

The are numbered continuously. The first card has input 0 to 71, the next 72 to 143 and so on.
Yep, I had it configured in exactly that way. Maybe I made a small mistake because it was very late ;) Will try it again in an hour.

[Soufiane]

I suppressed my message because it was not in the right folder

[kikigey89]

SIOC works but I don't know what I have done :D
Now I have a lot of PERF problems. I will try to create PERF data for my aircraft now before continue testing.
You said this could take up to 3 days. So have a nice weekend! :D

[jeehell]

Hello,

A new version again! I corrected the socket 10055 error that was quite annoying, and changed the climb law speed switching between IAS and mach, so the mach climb mach will be the good one related to the CI and not M.790 as before.
The FD roll bar should be smoother as well.

The link: http://www.jeehell.org/A320FMGS_B7.2.zip

Enjoy,
Jean Luc

[Soufiane]

Again you rock!!!

[jeehell]

Oh and I almost forgot, those with a FDS FCU willing to try a link with my software are welcome. I toyed around with their SDK and I probably can achive good results.
So if you're interested PM or e-mail me (jeehell "at" jeehell " dot" org )

(dcutugno you already received an e-mail ;) )


And thanks Soufiane!
JeeHell

[kikigey89]

Nice :) Got that error but I thought it might be caused by my computer ;)

Just one question for PERF tool: I ran it through last night and the entire day, but it wasn't finished and there were no results. Do I have to start FMGS server or something else? And how is the FS setup? Shall I place the aircraft on a runway?

[jeehell]

No you should only start the PERF tool. It should position the aircraft automatically as well.
Is there anything showing up in the lower page display of the PERF tool? If it's not done, maybe the data will show up at the end of the current test.
I know it's verrrryyy long, trust me I did each test several times, sometimes having a bug just before the end of the test :twisted: but it's the only way I could think of to get "accurate" data for every aircraft you wish...

JL

[kikigey89]

No, there was nothing to see... And that after approx. 21 hrs of running.

[jeehell]

Ok then it's not normal.
What test are you running?
Can you send over the content of your PERF folder?
What aircraft are you using? (payware or free? if it's free I'll try to see if it comes from the aircraft)

[kikigey89]

PERF folder is just a copy of the iFDG folder but without files in the 2 subfolders.
Aircraft is a complete mixture and for FS9: model from CLS, flight dynamics from PSS and weight and balance from Posky.
I used the aircraft.cfg from PSS with modifications of flaps, lights and contact points due to the CLS model and of course weight and balance (from Posky).

[jeehell]

OK for the aircraft, won't be able to test :(

What was the test: FLEX, CLB, CRZ or DES?
What's happening in FS? Maybe you could send a screenshot of FS and the PERF tool?
If the aircraft is stalling, you may try to increase the speed through FS map (in the "environement" menu).

[kikigey89]

The aircraft is not even moving :D There happens nothing ;)
I tried all 4 tests.

[kikigey89]

In FSX it works...

[jeehell]

Hmmm ok I will add that to the manual :roll:
Sorry for your first 21hours :oops: :twisted:

[kikigey89]

But Jeehell, I have to know if you are planning to get the FS9 and want to optimize your FMGS and especially PERF tool for it, too.
Because if not, it - unfortunately - makes no sense for me to wait your updates as I cannot use it at all...

[jeehell]

Hello,

yes I plan to make it compatible, however I don't know when it'll be so.
If you can get the perf tool to run on fsx, then I guess the profile data wont be too much different. I'll try see what i can do for the FMGS first.
If you could tell me what are the main problems exactly with fs9, i'll try see if I can fix them in the next version.

Cheers JL

[kikigey89]

Maybe I write the current aspects down why I cannot perform a complete test of your FMGS at all:
- Problem with "only push" encoders: I just own push encoders. The function that a long push is recognized as a pull would be really great.
- Right EFIS does not work if FMGS is configured with SIOC creator (you already mentioned that).
- PERF problem: Cannot get the PERF data from FS9. Don't know, if the FS9 aircraft fits with FSX. Have to try it on saturday.
- Sometimes your FMGS works with the file created by SIOC creator, sometimes not. Have to investigate it more in detail on saturday.
- Throttle problem: The throttle is recognized by your FMGS and is configured correctly. But I cannot control the thrust. If I set TOGA, N1 raises to 70 % but very slow (maybe 20 sec.). The aircraft accelerates to about 30 kts. and then N1 decreases to approx. 30 %. Have to investigate it. Maybe the problem is not caused by your FMGS.

[dcutugno]

Someone at FDS forum asked the G3 compatibility, my reply is we will test that togheter in a few days, my request to Jeehell si now that, ask to Peter D. for official reserved offsets to avoid 66C0... he will offer for free, so we can do InterfaceIt programming and don't interfere with future programs or special users setups.

[jeehell]

Kiki: I will try to address at least the throttle and the encoders issues in next realease. I cannot guarantee any time frame nor result but I'll do my best.

Dcutugno: for the offsets we'll see later on, for the moment I believe it's ok to use the offsets I provide.

JL

[jeehell]

Beta 8 is out, see the newest thread. This one is closed and merged with old ones.
JeeHell

[jeehell]

Hello guys,

The newest B8 version is out : http://www.jeehell.org/A320FMGS_B8.zip

Whats new:
-FS9 compatibility should be OK (throttle issues and APU)
-Long push can recognized as a pull if your hardware does not have a pull button on the encoders
-MCDU display fully reworked. It now has the exact characteristics of the real unit: 14 lines of 23 characters, and a new font is used (Lucida Console, it should be already present on your system)
-corrected bug with DECEL disappearing
-AP heading on ILS interception is kept until localiser is actually being captured
-DES managed speed should switch to the SPD LIM now
-DES selected speed should be kept correctly
-Right EFIS can be used with SIOC now
-You can set joystick sensitivity in the AP/FBW module
-Altitude won't change when you select +/-1000ft in ALT mode.
-DME2 is now displayed on ND
-APU door takes time to open
-FD pitch bar is now smoother

(bold lines are for you Kiki ;) )

Have fun!!

[kikigey89]

:D Great :)
Never expected that this would be done so fast. Thank you :)
I will test it tomorrow.

[jeehell]

You're lucky I could find a friend who doesn't use his FS9 anymore ;)
As for the rest, it's truly easier and much more fun than the VNAV ...

[kikigey89]

I imported the aircraft in FSX and now I am running der PERF Tool. Before I start test flying I want to have real values for my aircraft.
But I tested your FMGS yesterday eveving in a few minutes. It works with FS9 :) But I recognized some things:
- APU starts very fast. I read that realistic start up times are between 50 and 70 seconds (A318-A340), depending on environmental conditions (temperature, pressure).
- N1 of APU just reaches 99.9 % - 100 % looks better ;)
- Don't tested the cooldown of the APU but to tell you some values: An A330 APU has 100 seconds to shutdown: 15 secs of disconnecting equipment which is powered by the APU at this time and 85 secs of a real cooldown. AVAIL is still illuminated during this 100 secs.

[jeehell]

Hello,

Well i'll go for the 100% N1 and the longer start sequence.
But for the cooldown, it'll have to wait I think, not on top of the to-do list ;)
Tell me how it goes with this new version when you have time to do heavy testing, I'm waiting for all feedback!!

[kikigey89]

Sure ;) Currently PERF tool is working. I think I will test it on saturday in my cockpit.
Take your time ;)

[kikigey89]

By the way I thought a little bit about what you can improve optically.
In my opinion the PFD needs a rework. I mean font style, size, proportions of fonts and lines, etc. The other screens, too, but mainly PFD.
Don't get it wrong: it looks great at this time. But perfect is better than great :D And with a rework on the style it would come closer to perfect :)

[jeehell]

Well then I'll need you to be more specific on this one as I thought it was quite close to the original unit :?
Maybe if you can come up with a nice picture comparing the real thing and mine it would help to see what I need to change?
(it's not that I'm not willing to, don't get me wrong as well ;))
And as of the fonts, I think the current font is not great as it's simply Arial. But If you have any idea of a font I could use (preferentially freely distributable, or included in windows basic font package...)

[jeehell]

For those using Flight Deck Solutions FCU hardware, I've been testing with Davide (Dcutugno) a plugin for their Glare Software which makes the FCU almost plug'n'play compatible with my software.
The link is: http://www.jeehell.org/FDS glare.zip.

The only thing to do is launch the FDS_FCU module.exe with administrator rights at least the first time you launch it (it will register the associated dll to the glare software in the registry).
After that, you just launch the FDS Glare software and the FMGS server (as well as PFD,ND, MCDU and OVHD). You won't need the FCU or the right EFIS anymore.

Please note that it does NOT make the FDS I/O boards compatible.

[dcutugno]

I would like to thank in public Jeehell for the time and effort spent on making this module for the new g3 FCU of the FDS.
It is a great job! we are just ironing out the last few thing but almost complete, free to try it and report!

[kikigey89]

Perf tool is still running to get FLEX values :D Nice to see approx. every 10 secs. a value coming out^^

Yep, I will compare them in a picture the next days. Guess it is mainly the font type and size/proportion.
Maybe I can create my own font for the FMGS.

[kikigey89]

Found some minutes :) I hope you will not hate me for my accuracy :D
But I love your project and want to support it in every way to get it perfect :)

http://www.christophpaulus.com/files/comp.jpg


other font (maybe I can create one?)
blue font and blue symbols have to be brighter (light blue?)
background in tapes has to be darkened
no white border on left side of speed and altitude tape and on bottom of heading tape
values on speed and altitude tape have to be on the left side of the tape
values on heading tape has to touch the bottom
30° values on heading tape (and on ND rose!) have to be bigger (18, 21, etc.)
VS indicator has to be smaller
blue triangle for selected speed has to be bigger
bank triangle has to be smaller
bank lines are small rectangles
colors of artifical horizon (blue and brown) have to be darker
the 4 yellow lines and the radio altitude in the brown part has to be really yellow
inner vertical part of these yellow/black rectangles in artifical horizon (don't know their name) have to be longer in vertical direction
wrong proportion of pitch angles on artifical horizon
numbers on artifical horizon has to be bigger and the distance to the corresponding lines has to be bigger
short lines on course tape for 5° (185°, 195°, etc.) have to be shorter (just a bit)
I think most lines have to be thicker
vertical line between OP DES and NAV on FMA is shorter than the others
all FMA lines have to be positioned more to the right

[jeehell]

Found some minutes :) I hope you will not hate me for my accuracy :D


Haha too late ;):lol:

Ok I'll try to correct those graphical inconveniences. Just for my info, is that a 330 display or 320? if it's a 330 one are you sure it's identical to the 320?

As for the blue/brown of the artificial horizon, I think there are different colors depending on the DU type (older CRTs and newer LCDs for example). Maybe I'll add an option to set the RGB value of each color? What do you think of that?

For the font, we definitely need a new one ;) It has to be a true type font (.ttf format). If you agree to create one and make it freely available through my software it would be greatly appreciated!!
I could add an option to change the font as well, but I'm afraid not using a preset font might "damage" the overall rendering (i.e. texts not aligned properly, overlapping other part of the display).

Cheers,
JL

[kikigey89]

It's an A330 as I thought both are the same. But now I compared A330 to A320. The only differences are, that the FMA line of A320 is not shorter.
Second thing is that the VS tape differs completely. Your VS indicator looks more like an A330 indicator. Maybe the PFD style is depending on the age of the aircraft. Maybe newer A320 have an other style than older?
But I don't really care at this time how your VS indicator will look like ;)

I tested the PFD on 4 different TFTs and on all the colors looked the same. Are you using a CRT? RGB option would be nice.

Sure, I will try to get a good software for creating fonts.
I will inform you if there's anything new on this.

[kikigey89]

Yep, found some pictures where the A320 VS indicator look like the one of the A330.
So there are different versions of the PFD.

[jeehell]

So there are different versions of the PFD.
That's what I meant with CRT or LCD type of real unit, the LCD are the latest hardware Airbus has produced (on the A320 it is easily recognisable as the corner of the EIS screens are either round or square depending on the display technology, I don't what they did regarding the A330s?)

I think I will change the default colors, but create the possibility to change the RGB of each color used (not that many: black, green, 2 types of blue, gray, white, yellow, red, magenta, amber, and brown I think).
As for the proportions/size I will do my best.
Tell me if you can create a font, it seems to be not that easy ?

JeeHell

[kikigey89]

My A330 is D-ALPI which was build in 2007. It has TFT screens.

Main problem is to get a freeware editor...

[kikigey89]

Hi,

unfortunately I had to cancel Perf tool after approx. 40 hours because my computer had some problems... But no problem with your software.
Perf tool takes definitely too long. After 40 hours it was at 6000 ft and I saw in the files that it increases up to 14000 ft?
I think it will be better if the tool just records every 10 degrees and every second FLEX degree. The values in-between can be created by a spline interpolation.
So it can be 5 times faster!

I found a tool for font creating and it seems that it is working properly. Maybe I can send you a first font file this evening for testing.
It won't be near to the Airbus font but it should be a test if my created font is working with your FMGS. If it works, I will start to create the real font.
Please tell me, where I can send the font!

Chris

[jeehell]

Hi,

For the PERF problem, I know it's long but it's not exactly linear.I actually use the interval they give int he A320 FCOM. I'll see if I can easily add an accuracy setting to increase the interval between 2 measures.

For your font, you can send it to my e-mail "jeehell #at# jeehell.org"

JL

[kikigey89]

That's the reason why I said take a spline.
Maybe it is a little bit complicated to program as you have to solve some matrices but all in all I think you will get a result of +/- 0,2 % N1 I think with just a few values.
That accuracy should be enough.

[kikigey89]

I tested it around 1,5 hours and found a lot of problems:

Cannot set both QNH decimal points in SIOC creator. No setting box appears if clicking on the graphic.
EFIS "Long push=pull" is not saved. If I click again on the encoder, the option box is unchecked.
Right EFIS is still INOP.
Mectric Alt is INOP.
If I push the EFIS QNH encoder, no "STD" is displayed.
Direction of encoders is not working. I have some encoders which need a "-1" that the value goes in the other direction. Or am I making a mistake by entering "-1"? How can I set a direction?
Sepearte thrust levers would be nice.
If I press APU Start before the flap is open, I can see N1 increasing if the flap comes open, then N1 goes down to 0 % and N1 increases again. APU comes available. Just optical issue.
Both PFDs have less than 1 fps! It's unflyable.
SD: Fuel used is INOP. Maybe just FSX function?
Sometimes I got I lot of error messages from FMGS server: "Access violation at address 004FE6CF in module 'FMGS Server.exe'. Read of address 00000074."


Is there any moment when your FMGS has no control of flight controls? I wrote my own FBW software to use my gameport joysticks with sidestick priority. Even if AP was disconnected I got control problems. When I closed your AP/FBW program it worked. Unchecking your own FBW function did not solve the problem. I think your AP/FBW and my FBW have some trouble with each other.
So if there is any time, when your software has no control of the flight controls I would be nice if it could write a FSUIPC value. So my software could recognize if it is allowed to control or not.

Unfortunately it was unflyable today... Also got problems with AP which shot me into low earth orbit :D (Maybe performance?)

[kikigey89]

Got another problem: After starting MCDU and SD on both appeared the message " '' is not a valid boolean value.".
Tried to restart it but without success.

[jeehell]

Hello,

I'm away for the weekend, I'll check all those problems when I have a better computer than my iPhone ;)

JeeHell

[JehanLucques]

Hi Kikigey.
I had the same trouble.
Check if the version of MCDU and FMGS server are the same and updated.

Regards
JeanLucques

[jeehell]

Hello,

I will check all your SIOC problems with my hardware, and correct the SIOC creator issues (decimal points, long push, encoder direction which should be 1 or -1 as you did).
By the way, just to be sure, STD is achieved by pulling (or long pushing ;) ) the encoder.
Metric Alt is not yet available at all, and not planned for the next release. Unless a lot of russian simmers beg for it ;)
Separate thrust:I will see if I can easily add that in next release, without being too unrealistic (for example, engine failures and all are not yet planned, but the LVR ASYNC will be displayed)


PFDs: maybe it is because of FSUIPC if they are on a network (which is the case on your sim I guess). Check if FSUIPC updates frequently enough, maybe your network is in cause (some Wifi adaptaters seem not to work correctly with FSUIPC, I had the case and it is documented in wideclient documentation if I recall correctly). On my setup, I can launch FSX and the whole suite without fps problems.

SD: yes I think the fuel used offset is FSX only, I'll see if I can find a workaround.

"Access violation" and "not valid boolean" errors : hard to tell why, I guess some part of my code is not clean and tries to read an address in memory already freed... If you have any idea when it happens the most frequently?

FBW troubles: well for the time being, the FBW module ALWAYS has control over the govern offsets. In AP mode, it is obvious why, in manual mode, the FBW maintain a path (i.e. FPA and roll angle) so it needs to use the governs at all times as well. If you check 'no FBW' then the software applies the joystick input to the offset, with the sensitivity correction as well. I will try to see if I can leave completely alone the governs' offsets if you use 'no fbw' option, but if you want to use my manual mode, that won't be possible.
If you tell me exactly what you need for your own software, maybe we can find a workaround?

For the last AP issue, what was the phase of flight?

[kikigey89]

@JehanLucques:
Maybe I started the wrong FMGS server. My 2 folders of an old and the new version are named almost identical... Will check it the next time.

@ jeehell:
Metric Alt and seperate thrust levers are not important ;) I just wrote down what might be a bug or could be interesting.

PFD: Yep, I'm running it via network. Will check if there is any solution on that.
I noticed the access violation after my flight. So I cannot tell you, when it appeared. Maybe I can perform some test flights the next weekend and pay attention when it appears.

My FBW software writes aileron, elevator, rudder and brake values. If you could add an option where I can turn the raw joystick input off it would be great. Then you could add a FSUIPC offset where I can read if your software has control of the flight controls. So if AP is active there could be a "1" for blocked controls. If your FBW or joystick input is active, there should be a "1", too, for blocked controls. Just if FBW and raw input is off, there should be a "0". In that case my own software would set the controls.
So I would turn your FBW and raw input off to use my own FBW software. When I activate the AP, the offset is set to "1" and my software knows 'now I have no further control because AP is active' (or your FBW/raw input is active) and my software will write no further values so that your software has full authority.

It was initial climb. I rotated, retracted the gear, flew a few hundred feets manually and then engaged the AP for initial climb to 5000 ft. I engaged OP CLB and the pitch angle increased for a VS of around 8000 ft/min. Maybe the problem is caused by the missing of real aircraft performance and/or the presence of my FBW software.

[dcutugno]

Hi, i would like to see this implementation, i suggest you to make all instruments in one openGL window that we can expand over multi monitors if we want.
The benefit of this would be we can use the display transfer feature in our bus! Like expanded mode in Project Magenta, where you open the window maximize that open the menu and select witch instrument to display.

[jeehell]

Hi,

This one is quite difficult for the moment. In the (far) future, I plan to mix the PFD and ND in one exe and the SD and EWD in another one, so switching will be possible, but for the time being it is not possible. I have some CPU limitations with the openGL component I use which I haven't been able to bypass yet.
If you really need the switching thing, I could perhaps do some tweaking such as "physically" moving the ND window where the PFD window is and vice versa?

Anyway, it'll be in a few versions at least, not in next version which is due very soon I hope (with the latest bug you had corrected)

Cheers,
JeeHell

[dcutugno]

If you really need the switching thing, I could perhaps do some tweaking such as "physically" moving the ND window where the PFD window is and vice versa?
JeeHell

It would be a nice trick i think and can work, we could try.

[jeehell]

Okay, I'll see what I can do in a future release. For the time being, the beta 9 is out, see the new topic.

JeeHell

[jeehell]

Hello all,

The beta 9 is out, check it out here: http://www.jeehell.org/A320FMGS_B9.zip

What's new:
-New font for all DUs, a big thank to Christoph Paulus (aka Kikigey89)!!!! (you have to manually install the airbusfmgs.ttf font in your c:\windows\font folder). You have to set the font for each DU separately (see in the options of each DU).
-PFD layout reworked
-N1 swing corrected
-Seatbelt and No Smoking signs for FS9
-FPLN point sequencing when several pseudo waypoints between ACFT and Active Point
-APPR phase activated when overflying DECEL pseudo waypoint
-PERF pages change when flight phase changes
-FO EFIS NAV1 and NAV2 bug corrected
-Joystick input is directly sent to FS when FBW is deactivated and AP is disengaged. An offset is available to know when joystick is "free"
-FDS FCU glare 3 integration (check FDS_Glare folder)


Again thank you Christoph for the font!

Have fun,
JeeHell

[PanosDrak]

ok nice to see that finally you changed the font and made many other changes!!! keep up the good work mate

[kikigey89]

Looks really cool :) I'm proud of myself :D But nevertheless the font isn't finished. If I get new pictures of the MCDU I will improve my font.
Just one issue: If I want to select the font in both PFDs, a message appears which says that no font is installed. So I cannot change the font.
But if I restart the PFD, my Airbus font is active, don't know why. But it's good that it has changed itself :P

Currently I am not able to test in my cockpit because I disassembled my MCDU to make a board which will carry all the buttons.
I think this will take up to a month. But tomorrow I want to test your FMGS with FSX and FSX's A321 to get an idea of how it should work :D
After that I will perform the same flight in FS9 to tell you, where the problems are.

[kikigey89]

Hi to all who are reading this ;)

Today I had just time for testing the FMGS in FSX with default FSX's A321. I spend around 5-6 hours on disigning my new pedestal. Picture here: http://picasaweb.google.com/kikigey89/ProjectA330#5468985195423395362.
Now to my bug and improvement report:


Background color should be the same on all DUs. Especially PFD background is complete black, the others have a light black. Check that all have the same background color (light black looks good!).
An option for realtime alignment of the IRS would be nice.
INIT page is accessible every time. I think in reality it's only accessible on ground.
No distance values to destination in MCDU.
VS does not fit in FMA space (see screenshot).
ILS APP was activated in cruise, don't know why.
As far as I know the name is transition level instead of transition altitude (APP page, MCDU; only for descent, on climb it's transition altitude).
If all bugs are corrected, an ALT button instead of the EXPED button would be nice for A330 (for the future).
Wrong ILS frequency displayed on PFD. I had to set it manually in the MCDU but on PFD the wrong frequency was shown.
ILS CRS cannot be changed in MCDU.
Airports are not visible on MCDU. As far as I know the departure an destination airport are always visible.
Discovered a lot of circles on ND (see screenshot).


And know the biggest bug: I had some problems with OP CLB, OP DES and Alt hold. The aircraft was luffing a lot, sometimes up to +/- 10°. I made a video, available on http://www.christophpaulus.com/files/fmgs.avi.
Another problem was when I selected 30000 ft (was on 28000 ft) the pitch extremly increased and I got a VS of around 14000 ft/min... After a few seconds the pitch decreased and the aircraft descended because I have been shot up to 31000 ft. But the VS mode works good, there are just a few problems if I change the VS. Then the aircraft starts to luffing again but stabilizes after a few seconds.

Maybe you could use the built-in AP of FS? I think this would solve a lot of vertical mode problems. You could use it for altitude hold and for VS operations. Maybe you can also realize OP CLB and OP DES via FS VS mode. I think vasFMC uses this, too, and this works almost perfect and smooth.
I saw that the values on the FCU in FSX are changed if I change them in your FMGS. But no AP was active yet, just A/THR. I guess you have realized the SPD hold function via FS?

Chris

[dcutugno]

I also can't change the font in PFDs, another small glicth is i had to delete all the config in the subfolders 'cause the screens was out of view and mcdu was not visible, i think you have saved your screen configuration then distribuited the fmgs.
Just to let you know a first user can go crazy...

[jeehell]

Hello Christoph,

Nice design for your pedestal!



Background color should be the same on all DUs. Especially PFD background is complete black, the others have a light black. Check that all have the same background color (light black looks good!).

Yep I noticed that, I'll put the light black (sounds weird ;)) back.



An option for realtime alignment of the IRS would be nice.

Are you reading my mind? I've started programming the ADIRS yesterday!!



INIT page is accessible every time. I think in reality it's only accessible on ground.

I let this "bug" intentionally, as a way to supervisor a few thing for debug, but I don't need it anymore, I'll try not to forget this one.



No distance values to destination in MCDU.

I'll correct that




VS does not fit in FMA space (see screenshot).

Damn font larger than Arial ;)




ILS APP was activated in cruise, don't know why.

The approach type appears when you enter the APPR (and STAR) in the MCDU. I need to check exactly how it works on the real unit.




As far as I know the name is transition level instead of transition altitude (APP page, MCDU; only for descent, on climb it's transition altitude).

I've just checked on my MCDU documentation, and it remains labeled as transition altitude...
I guess the FMGS computes the transition FL from the transition altitude and the selected QNH, I'll check that.




If all bugs are corrected, an ALT button instead of the EXPED button would be nice for A330 (for the future).

The exped button is inop for the time being.
What is the purpose of the ALT button on the A330? (it does not exist on the A320)




Wrong ILS frequency displayed on PFD. I had to set it manually in the MCDU but on PFD the wrong frequency was shown.

Yes autotune is not implemented yet. As for the PFD frequency, I'll check and correct.



ILS CRS cannot be changed in MCDU.

As in the real A320 I think. I'll check.




Airports are not visible on MCDU. As far as I know the departure an destination airport are always visible.

Well the DEP and DEST runways are not yet implemented, not such an easy one. I'll see what I can do.




Discovered a lot of circles on ND (see screenshot).

Yes, an old bug, but had not bothered to correct it yet.
I'll see if I can correct this one and the wrong circles on some turns as well.




And know the biggest bug: I had some problems with OP CLB, OP DES and Alt hold. The aircraft was luffing a lot, sometimes up to +/- 10°. I made a video, available on http://www.christophpaulus.com/files/fmgs.avi.
Another problem was when I selected 30000 ft (was on 28000 ft) the pitch extremly increased and I got a VS of around 14000 ft/min... After a few seconds the pitch decreased and the aircraft descended because I have been shot up to 31000 ft. But the VS mode works good, there are just a few problems if I change the VS. Then the aircraft starts to luffing again but stabilizes after a few seconds.

I might be faulty on this one, I haven't changed the AP/FBW coefficients for a long time concerning the default A321, I probably need to tune them again.
If you want to try again, use the iFDG coeffs.




Maybe you could use the built-in AP of FS? I think this would solve a lot of vertical mode problems. You could use it for altitude hold and for VS operations. Maybe you can also realize OP CLB and OP DES via FS VS mode. I think vasFMC uses this, too, and this works almost perfect and smooth.
I saw that the values on the FCU in FSX are changed if I change them in your FMGS. But no AP was active yet, just A/THR. I guess you have realized the SPD hold function via FS?

In the early design I used the FS AP but it is really not a realistic way to do it in my opinion: I couldn't maintain a selected speed with the A/THR maintaining a constant N1 (A/THR in thrust mode), and so the A/THR would increase/decrease N1 and the VS/FPA was not exactly right (either to big or too small...).
I nonetheless use the FS ATHR as you said, but only when in SPD mode (in ALT, V/S or ILS mode), not when in THR mode (i.e. in CLB or OP CLB mode). But I wish I could not use FS at all, their ATHR is quite slow to react sometimes I think.

Anyway, try with the ifdg coefficients, and tell me if it's still bad. I'll try to make better coeff for the default A321 in next version.

By the way, why don't you use the anitaliasing? the DUs would look better I think?

[jeehell]

Hello Davide,

I've been told for the PFD font. If you try to change it, close the PFD and start again it should work. I'll correct that in next version.
For the windows not appearing, maybe you tried to use your old configuration file. I changed the format of this one to add the font function, that's probably why.

Do you have better results with the FDS module now? If you still have bugs, advise me ;)

[kikigey89]

Hi,

as far as I know the ALT button is just for the altitude hold function. The EXPED function is missing in the A330/A340.

You are the master of your software and you know, what's intentionally and what's not. And you know more about the MCDU. I just noticed some things where I thought they might be wrong. So just forget these things where you know, that you are right :) I write everything down that I discover and post it here.
Same with FS AP: I was just wondering why you are not using this function. But your N1 hold is great, I hope someday everything will work properly and N1 will not go up and down the entire time in cruise (SPD mode) like in vasFMC. That was very funny at our winter event. We were working in shifts and if you were in bed in the upper floor, you could hear the engines spooling up and down :D
I hope your FMGS will work with my aircraft and with FS9 until my planned summer event in mid of august. At least 120 hours non-stop on VATSIM - Great :)

I will try it again with iFDG coefficients. Maybe not tomorrow because I planned to go gliding. I haven't been in air for 3 weeks and I need to go flying :D But it should rain tomorrow...

It's a good question why I am not using antialiasing... I think I just forgot it. I have some problems with AA on my cockpit computers and I need some time to solve that issue to get AA in the cockpit. So the view of the display here on my home computer was as normal as in the cockpit :P

[kikigey89]

Back from the airfield I tested the entire config with iFDG coeff. and it worked almost perfect!
In OP CLB the aircraft was luffing just a litte bit (+/- 2°) and in cruise it was completely stable :)
Tomorrow a test in FS9 with iFDG is coming up.

[jeehell]

Good :)

I toyed around the coeffs today, and I'm quite happy. It seems the iFDG coeffs work pretty good with the default FSX A321, so it might mean that those coefficients are "generic", for this range of aircraft (probably fits the B737, and even bigger aircraft as well).
I found out that the OPCLB coeffs can be enhanced, try those values:
OPCLBiasKp=0.005
OPCLBiasTd=10

With these, I almost had no swing at all during normal climb!

Cheers,
JeeHell

[kikigey89]

Great :) Will test it this evening.

If this works, I maybe have to edit this values for my A332 so it will be great, if you can explain them in your manual.
So I can pay attention to the behaviour that will change by this value instead of monitoring the entire behaviour.

[dcutugno]

Hi, found some bugs, cruise set at fl270 near fl250 aircraft start a nose up attitude of 3000vs loosing speed and engines spooling at MCT i think, this happened until altitude captured at level 270.

Another thing is at 10.000ft aircraft set VS at 0 to accelerate but i think a reduction to 1000 or 1500 will be better.

MCDU screen sometimes is not going up with the flight plan so i have to push button fpln to bring it up(so the white waypoint is at 2nd rlsk.

Edited the values as you said for coefficient, used FS9 and ifdg model all is stable.

Can't have time to test FCU, but will do.

[jeehell]

Hello,

Yes those are bugs/limitations, I will try to correct them. The VNAV model is not yet perfect.

Good to hear the AP/FBW works Ok, it has been a long run :D


kiki: I will add a few lines in the manual for the tuning of coefficients.

[kikigey89]

Thanks :)

I found some time to test it in FS9 and it works perfectly :)
Okay, except those FSUIPC offsets that are not supported by FS9 and except the reported bugs. But the VNAV was brilliant with these new coefficients.
I think most flight problems are caused by this values which have to be adapt for every aircraft.

In the MCDU there is a small bug: I enter a direct but if pressing "Insert" the direct isn't inserted. Just on the second try it works.

[jeehell]

Okay good to hear.

For the "insert twice" bug, I found the problem already, and will be corrected in next version ;)
I just need to work on your new font, and I will soon release a new version (next week probably, won't be home for the weekend...)

Cheers, JL

[kikigey89]

:) No problem, I'm planning to build my new pedestal on friday/saturday

[jeehell]

Hello,

The version B10 is now available:
http://www.jeehell.org/A320FMGS_B10.zip

Whats new:
-New fonts for all DUs:MCDU and EIS separately, a big thank to Christoph Paulus!!!! (you have to manually install both fonts in your c:\windows\font folder). You have to set the font for each DU separately (see in the options of each DU).
-ADIRS
-FPLN bug having to do every modification twice corrected.
-FPLN sequencing with pseudo waypoints should work better.
-Descent managed speed will be more stable (less movements in pitch).

As usual, you're free to report your problems!!!:mrgreen:

Cheers,

JeeHell

[jeehell]

Thread closed, new version is available, see the new thread!

[ANDYSMITH]

you are well on your way to converting me to a bus driver. never thought I'd say that out loud.

Andy Smith

[jeehell]

The first step is to admit you were born a bus driver. Then you tell your family, and finally the shame will turn into pride ;)

[kikigey89]

It looks great in my cockpit! But I found one bug:
The window options of the FO PFD window (hide border, always on top and lock position) are not saved and after restart I have to check these 3 manually again.

The framerate problem is caused by my cockpit computers. If I run just 1 PFD without NDs the framerate is approx. 10 fps. The more windows I open (second PFD, NDs) the more the framerate is decreasing. I will look for a new computer.

You added this FSUIPC offset where I can read the state of the FBW module but I need an option where I can turnoff the entire module so that my software can take full control. And for this I need a value where I can read if your FMGS has control (in my case by AP) or not.

Example: I turnoff the entire input-module by a checkbox or something else. Then I start my FBW software. We are on ground so AP is off and because the input-module is offline the value (lets call it X) is 0. My software knows that your FMGS has no control. Then I take off with my software and shortly after initial climb I activate the AP. Then X changes to 1 and my software knows that your FMGS has control and my software will stand by.
X should also be 1 if the input-module is active. It doesn't matter if FBW or raw input is choosen but your software has control. X should only be 0 if AP is off and no input-module of your software is controlling the aircraft.

[jeehell]

Hello Chris,

I will correct the FO PFD issue.

For your FBW problem:
Maybe we do not understand each other on this one :) but right now here is how the software works:

if offset $66D9 is 0 the AP/FBW module has control (whether because AP or FBW is ON)
if offset $66D9 is 1 the AP/FBW module does NOT have control: FS receives directly the joystick input, without any intermediary (so AP and FBW are both OFF)

the offset $66D8 allows you to switch FBW ON/OFF without having to click the checkbox, but I did change the handlign of the joystick in the AP/FBW module: with AP OFF and FBW OFF, my software sends nothing to FS.

[kikigey89]

Alright, thanks, that's exactly what I need.
Maybe I'm a little bit confused by all those FBW, joystick and AP things :P

[kikigey89]

What came to my mind what is important for my homecockpit:
I need to transfer the sounds on another computer than the FMGS server (flightsim) computer.
So it is possible for you to add a sound application which communicates with FMGS server and plays the sounds on another external computer?

[jeehell]

Hello,

I had this idea already, but I haven't had the time to implement it yet. Since at least one more person is interested, I guess it's a nice one ;-)
Maybe not in next version, as it seems B10 is quite not as stable as it should, I will soon release B11 to correct some big bugs.

JL

[kikigey89]

Thanks :)
For the use of your FMGS at my summer event in mid august this is very important but more important are some new bugs in B10.
I made a testflight an hour ago but had to cancel it on approch due the AP and ATHR problems.
The aircraft was luffing again but at a long period of time. One period took about approx. 30-45 secs. Don't know if it's caused by the coefficinets as before or by a problem in the software itself. Furthermore after activating the AP my VS increased dramatically and I got a stall. I recognized this VS problem in OP CLB, OP DES and when VS is set manually. All the times I overshot my selected flight level by 2000-3000 ft. This happens on climb and descent. Record of VS was 13500 ft/min :D
I used iFDG A320 with the same overall config as in my test with B9.

Some other problems, errors and suggestions:

Landing weight lower than ZFW (MCDU)
SD error: "'-9223372036854775808' is not a valid integer value." (I think this occurs if FS is paused)
Status page on SD would be nice
EFOB calculated to -1.4? (Fuel available at least for 2 testflights)
Pitch trim increases during taxi
MCDU sets new CRZ ALT to FL240 but FL230 was entered and selected
Moving of VOR and ADF needles would be nice (as in real and like in vasFMC)
MCDU: Arrival time was calculated to 00:02 UTC which is about 12 hours after my estimated landing time :D
GW in FS9


But nevertheless: Thank you for that software and for working so hard on it! :)
I made some screenshots for you: http://www.christophpaulus.com/files/fmgs_screenshots.zip

[jeehell]

The aircraft was luffing again but at a long period of time. One period took about approx. 30-45 secs. Don't know if it's caused by the coefficinets as before or by a problem in the software itself. Furthermore after activating the AP my VS increased dramatically and I got a stall. I recognized this VS problem in OP CLB, OP DES and when VS is set manually. All the times I overshot my selected flight level by 2000-3000 ft. This happens on climb and descent. Record of VS was 13500 ft/min :D
I used iFDG A320 with the same overall config as in my test with B9.

That's weird. Have you ever had that in previous versions?

For all of the other problems, I have already identified them and corrected most of them. I hope the new version will be out this week!

Only the VOR/ADF needles, what do you mean by "moving of the needles"?

JL.

[kikigey89]

No, B9 was perfect. I will take a look on the config if something's wrong there. Maybe I can perform a second test this evening.

I mean that the needles are not fixed and pointing exactly to the VOR or NDB. As in real the heading to the station is deviating a little bit by some degrees.
So the needle is not pointing at let me say 240° (which is the correct heading) but a few seconds on 238° then maybe some secs on 241° one sec an 237° a few on 240° and so on.

[jeehell]

Ok I see for the needles, but I think we have some more important suff going on such as pitch problems ;)
By the way, I think I pinned that problem, but what is weird is that it should have occured on earlier version as well, I think it is related to FS9 version of FSUIPC which doesnt "protect" the offsets the same way as in FSX...

[kikigey89]

Sure, this is just a suggestion. AP VS behaviour is much more important than this ;)

[jeehell]

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!

[kikigey89]

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

[kikigey89]

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.

[jeehell]

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

[kikigey89]

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.

[jeehell]

Ok, 5-6 turns is way too much. I will see if I can do anything...

[kikigey89]

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

[kikigey89]

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.

[jeehell]

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

[kikigey89]

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.

[kikigey89]

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.

[jeehell]

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

[kikigey89]

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...

[jeehell]

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?

[kikigey89]

Yes, I think this is it! Thank you for this information :)

[jeehell]

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

[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

[kikigey89]

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

[jeehell]

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

[kikigey89]

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

[jeehell]

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

[jeehell]

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).

[kikigey89]

Hi,

I wanted to fly from EDDL to EDDW via MEVEL L179 OSN R15 BASUM T820 PIXUR.

[jeehell]

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

[kikigey89]

Works perfect until now (climb) :)
Only thing is that the chrono on FO ND is INOP.

Chris

[kikigey89]

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

[jeehell]

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

[kikigey89]

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

[jeehell]

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

[a320231]

Thank You JL!

I'm going straight now to make a flight!

Regards

a320231

[Nikos Oikonomidis]

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

[a320231]

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!

[jeehell]

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

[kikigey89]

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.
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.
3983
Is the underline of LDG LDG GEAR on EWD correct?
3984

[jeehell]

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

[kikigey89]

Thanks for the information! I will use the correct disconnection in about 3 hours on the approach to Düsseldorf ;)

[kikigey89]

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.
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 :)

[jeehell]

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

[kikigey89]

Thanks for the info :)

I send the pictures of your FMGS in my cockpit (http://picasaweb.google.com/kikigey89/ProjectA330#5490468200935976370) 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 :)

[jeehell]

Yes Nice pictures!!

[kikigey89]

Hi,

another helpful feature would be if the DUs could be moved pixel by pixel with the arrow keys even if the border is hidden.
4 other keys for adjusting the width and height of the window (bigger and smaller) would be nice, too.

Chris

[jeehell]

Hi all,

B13.1 is out:
http://www.jeehell.org/A320FMGS_B13.1.zip

What's new:
-Corrected some more VNAV bugs...
-Green Dot Speed Calculation (new file GDspeed.txt in perf fodlers)
-Landing capabilities logic and triple click sound
-All DUs and instruments panels can be moved/resized with arrows (arrows: move, SHIFT+arrows: resize, MCDU CTRL+arrows: move)
-V/S and FPA can be armed in APPR mode. Additionnaly, Reversions from GS to V/S or FPA should work.
-PACKs OFF after engine start will go ON automatically again now.
-APU GEN OFF when korry says ON corrected
-MC and MW pushbuttons can popup on FCU if option is checked.
-Starter.exe software: in the starter.ini file, choose which software you want to run (and eventually close) simultaneously. You can even add external programs with their directory path. The icon is an aircraft, not to get ti mixed up with others executables...
-EFOB 000 corrected
-ECAM messages overlapping corrected
-Thrust Lock, AP & ATHR disconnect logic corrected a bit.

Enjoy,

Jean Luc

[jeehell]

If you downloaded the file before this post, download it again, I made small corrections on the SD and FCU/EFIS which reacted weirdly to keys or mousewheel down...

Cheers,
JL

[kikigey89]

Hi,

after 20 minutes of an eventless flight I decided to make it more interesting: ENG 1 fail :D
I discovered that the thrust control gets problems if one engine is off. The control just knows IDLE and TOGA in this case. Not just in A/THR but also with manual control. This caused a hard landing in Berlin :D

3988

You can see that thrust is set at 49,9 % but it is over 87 % and still increasing.

Some other minor bugs:

MCDU: Continuous swap between these two conditions in about 0,2 seconds.
3989
After entering a direct the holding circle wasn't deleted.
3990
On descent, the active mode was DES. Then ALT* came up and somehow DES was engaged (below ALT* in blue). Just a few feet above the planned altitude ALT was engaged and seconds later activated. Why was DES engaged?


Chris

[jeehell]

Hi,

Hey who said engine failure where implemented yet anyway :x ;-)
By the way, if you had a failure on eng N°2, you wouldn't have had this problem, so plan your failures accordingly now please ;)

I plan to add the thrust lever N°2 in one of the next major release. I don't know when exactly. If I have time in july, otherwise it will have to wait since I'll be on holliday for 2 weeks in August...
I'm a bit ahead of my previous schedules, I already started working on failures and ECAM messages, so who knows?

For the other issues I will look at that.

[kikigey89]

Alright :D I planned an engine failure on my first event-flight, so good to know :D

Great to hear of the ECAM messages :)

[DLH9KA]

Hi,

first of all Great piece of work!
However I have a question regarding the ND.
I'm running it on 3PC'S
On the first the FS itself with the Server, FBW etc.....
On the second the PFD/ND and the MCDU and FCU
And on the third the EWD/SD and OVHD logic.

Now my Problem is, that the ND.exe needs over 50% CPU usage sometimes even up to 90 whereas PFD MCDU FCU etc....need far far less of CPU!
Problem is that with this high amoung used by the ND the rest runs slow as well as the ND itself!
If I switch on Airports on the ND the FPS of it drop like **** as well for VOR's etc!
Is there a solution to minimize the amount of CPU needed by it?
PFD and all the rest don't even use 10% CPU but ND eats it all away thus dropping frames and performance of the rest!
For information, I'm using a P4 3,2 GHz machine for ND etc and Other software like SIm-Avionics etc run very smooth.

Kind Regards, Patrick

[jeehell]

Hi,

First thanks for your interest in my software ;-)
Now concerning the ND, yes it really needs a lot of CPU for the moment, as it has to calculate the position of all FPLN WPTs and place them on the screen. I haven't found a way to reduce that CPU usage yet. However, if you have a multi-core processor available, it will work better, as it will limit the ND to one core, leaving the other software to different cores.
Maybe try to reduce the priority of the ND process through the task manager. Maybe there are software that can do that better as well.
By the way did you turn ON the EGPWS? if yes, try to turning it OFF, this one really eats up CPU!!

Regards,
JL

[Atomic_Sheep]

Hi Jee, firstly, I'd like to say how greatful I am that you are making all your hard work publicly available! I d/l it yesterday and have been playing around with it and have managed to get most things working and I'd like to say that it's certainly impressive what you've managed to do!

I do however have one question. I hope I've installed everything correctly. When I startup the airbus for the first time using ground power, I turn everything on i.e. the whole all lights off logic I think it's called. I set ADR's to NAV mode, turn on the APU although it shouldn't make any difference as far as I can tell in the way of enabling the IRS to get aligned which is what I'm having the difficulties with. I select the LFBO/LFMN flight as per your tutorial and then click Align IRS but I don't seem to get anything happening. I'm not entirely sure what is going on. This is what my EWD is showing (refer to attached image)

4031.

Looks like it says AUTO FL AP OFF on top of each other

I can't really understand what the error is, but as you can see, neither is it stating that the IRS is being aligned/showing the countdown to the IRS alignmnet being complete. The ND is backing this up by remaining red after some time, so it looks like it certainly isn't liking something I'm doing.

As I said, I'm not sure whether I might have installed something improperly which is what is causing the problem but considering the fact that I was initially getting an error in the MCDU when I installed all the files into the nav folders and had to try a few things i.e. install them into that folder in other folders and just getting the naked files into the nav folder, I finally was able to get the MCDU to recognise the LFBO/LFMN selection and get the Align IRS option to work, so I think I must have got the installation right now.

So basically, I'm unable to align the IRS for some reason and I'm not sure whether I'm getting a bug in terms of that EWD reading.

EDIT: It's working now so don't worry about it. I think I just wasn't waiting the full 10 minutes. I timed 10 minutes this time and it was all good. Impatient!

However the issue of the overlapping text is still there and I also believe I might have found a tiny bug... when I was trying to fly from LFBO/LFMN as per tutorial, when I enter FL190 for the cruise altitude, I got the result "NOT ALLOWED" but typing 190 is fine. Isn't it supposed to accept both FL190 and 190?

And also, just out of curiosity... when you enter the radio navigation frequencies, should you be able to enter for example TOU/117.80 rather than just TOU? I don't know how the real airbus works in this department but if I were designing a plane, I'd have the pilots insert TOU/117.80 just make sure that the pilot is looking at the correct corresponding frequencies and VOR name. But I don't know how it's mean to be, just asking.