A320 FMGS beta 26

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,

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.

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

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

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

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

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!

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.

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

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

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

--
Bryn

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/d.../Photo_012.jpg

http://www.mycockpit.org/photopost/d.../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-)

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

--
Bryn

Thanks for the compliment ;)

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

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

Hopefully sometime during the next couple of days :D

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

Now out, see the relevant thread :D

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

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

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!

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

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

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.

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.

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?

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

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

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

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

Buddy

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)

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

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.

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

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

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?

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

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.

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

Here what OC says:

Code:

---

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