A320 FMGS beta 26

Hi JL,

thanks for your quick reply. At the moment its all running on one I7 with Win7-64. For testing I just used an old Sidewinder2 joystick with 4 axis. 3 axis are gone for rudder, elv and ail. So I use one throttle axis and defined the detents for BOTH engines in your fmgs config. So I am able to move the both white N1 cycles and get the corresponding detents in the SD but no engine response. In addition, all 4 axis are defined and calibrated in FSUIPC. The original joystick controller is disabled in FS.
I tried to reinstall FSUIPC... no change. I only tested on ground and yes the engines are running ;-)

So if I run the AP/FBW exe all works fine except the THR. When I close AP/FBW it takes a couple of seconds and the engines follow the N1 target as they should and are no more stuck as before. I have to check again what happens if I check "disable FBW".

Could it be hardware related? I'm waiting on the BU0836 joystick controller from Leo Bodnar to be in my mail the next days... I will let you know if the new controller makes any difference.

If not I might consider a complete re-installation of FSX... :-(

May I ask whats the setup of the other guys who deal with the same problem? It's strange that this only happens to some of us...

Cheers,
Rob

Hi Rob,

Can you try to remove the assignments/calibration in FSUIPC (these are not used with my software, as I get joystick data directly from windows)? It might be interfering.
As for the other guys who have this problem, I don't really know their own setup, but it shouldn't be what's causing that. My only guess is it's software related, not hard. I myself use a single computer setup with a 4 axis joystick, and no troubles at all...
I'm pretty sure there is somewhere an interference between FS and my soft, which most probably comes from FSUIPC.

JL

Jeehell,
great work but I have a problem and does not know why...

On my flighsystem PC PFD and ND does not start - okay, windows works 3 years and decide to setup an additional HDD with WIN XP and FS. After install exactly the same, PFD and ND does not start.

I can recognise a short time the process in taskmanager, after there it was gone???
If I start the PFD on an old notenbook, everything works but with errors in logfile.

Here the notebook:

0 (I) Log subsystem started in elapsed time mode.
62 (i) Temporary rendering context created
62 (I) Getting OpenGL entry points and extension
62 (I)
62 (i) OpenGL rendering context information:
62 (i) Renderer : Intel 855GM
62 (i) Vendor : Intel
62 (i) Version : 1.3.0 - Build 4.14.10.4497
62 (WW) GLSL version : not supported
62 (I)
62 (i) Temporary rendering context destroyed
62 (I) Getting OpenGL entry points and extension
7953 (i) Logged fatal errors: 0, errors: 0, warnings: 1, titles: 4, infos: 6, debug info: 0
7953 (i) Log session shutdown


and here the FS PC:

0 (I) Log subsystem started in elapsed time mode.
407 (i) Temporary rendering context created
407 (I) Getting OpenGL entry points and extension
407 (I)
407 (i) OpenGL rendering context information:
407 (i) Renderer : GeForce 8400 GS/PCI/SSE2/3DNOW!
407 (i) Vendor : NVIDIA Corporation
407 (i) Version : 3.3.0
407 (i) GLSL version : 3.30 NVIDIA via Cg compiler
407 (I)


I have no idea whats going wrong. On each PC or notebook in my area it works except the flightsim PC.
Could you please help?

Hi,

I don't understand, did it work prior to new installation of windows or not, your message is no clear on that?
One possible solution is to change your video drivers. If you already use the latest ones, try to revert to older ones you know worked correctly.

JL

Hi Adonis,

Sorry I hadn't seen this thread before now, but if I'm right you already posted those bugs on the project's mantis website.

Thanks and sorry again for not seeing this earlier...

JL
PS:I moved that thread in the correct forum.

Quote:

---

Originally Posted by jeehell

Hi,

I don't understand, did it work prior to new installation of windows or not, your message is no clear on that?
One possible solution is to change your video drivers. If you already use the latest ones, try to revert to older ones you know worked correctly.

JL

---

Hi Jeehell,
with the old partition there was an old vidio driver installed, with the new partition have had installed the latest.
On both partitions the PFD and ND does not open the window. As I said, 2 seconds visible in taskmanager as a process and then off.

I haven`t posted this in any forum before, because I was sure the problem should be the old installation and tested the FMGS on several other PC`s.
But with the new installation now I`m confused. On my system there is something special - there is a NVIDIA PCIe and a ATI onboard card installed. Until now every systems ar working well.

Is there something different on PFD and ND to for example MCDU, because MCDU window will open correctly?

Hi Frank,

I'm afraid the special setup you use (mix of nVidia and ATI), might be the cause. Do you use the two video cards at the same time for multiple screen?
The MCDU being somewhat simpler than the PFD/ND, it might be a reason this one works and not the others... Also, on what video card is running the MCDU?

JL

Hi Jeehell,
the windows main screen is supplied by NVIDIA, the displays for ND and PFD are supplied by ATI. The MCDU can be opened on the main screen (NVIDIA) and can be moved to all other screens without any problems.

Is there anything I have to adjust to one of the video driver?

Maybe the startup of the windows on an ATI card is not working, but once it is running it can be moved around, can you check that?

JL

Hi Jeehell,
you are right, PFD and ND is running if ATI device is deactivated. Thanks for your support!

The good news - now I know the reason and the bad news - I have to change my sytem configuration...

Hi!
I wanted that one computer was to FMGS (5 monitors: 2xPFD/ND, SD/EWD, 2xMCDU)
I tried many solutions.
Now I already know that it must be the same card (all from ATI or all of NVIDIA). In addition, it must be cards that may have the same driver (can not be one of the newest and the other tries).
Highlights: This is not working well in WinXP. I had to use Vista.

Now I have one card on the PCI-E (GF7200) and one PCI (GeForce FX 5500).
This allows me to run 4 monitors. If I add one more the same PCI card is the whole cockpit run on one computer (FSX will run on another PC of course).

The combination of ATI and NVIDIA does not work. Even for the MCDU. It seems that the MCDU work - but try to enter something in it ... Then you can not see the changes.

Hi,


Yes hybrid setup are always tricky. I cannot afford to have that many different cards to test and debug everything...
More over, ATI cards are known to have more troubles in the handling of OpenGl, try googling "opengl AtI" to have more info on that subject. I know nvidia is more expensive but we dont get many choices here...

JL

Hi JL,

after some tests I found some bugs.
Apu - Master and Air-pressure switch only work with a switch, not with a button. Is it possible to assign in the config tool between the switches and buttons to choose?
How can I use in the MCDU and the Nd transition?
Under NavData accessing the files - Sid.txt and Star.txt, but Appr.txt.with the transition`s are not used.

A big problem is the landing. The aircraft nose is always pressed down, whether I'm flying autopilot or by hand. When I put the thrust on landing idle, the airplane falls from the sky like a stone.
I think this is a connection with the fly by wire system.
I tested with the iFDG, Pa.and Pss Airbus.
With all aircraft the same problem.

Sorry for the long list of problems.
I hope you can solve some of the problems.

At the end again a big thank you for the fantastic software.:D

Greetings from Germany

Micha

Hi,

I am not sure I understand your problem with the switches?? If I'm correct, with FMGS Config you cannot configure the APU Master as a toggle siwtch?
However I don't get what you mean by "air-pressure" switch?

Concerning the tranistions, they can be used only if they exist in the database, and not all APPR have transitions in the leveld database.

The nose down bugon landing should be corrected in next version.

regards,
JL

Hi JL,
I use in my overhead for the APU 3 buttons. Apu-start and Apu-bleed working with button`s, the blue LED stays on. When I press the button Apu master remains the blue LED is not on. With a switch it works. The button to provide the air pressure on STD, has the same problem.
It would be great if these two functions would also work with a button.

best regards

Micha

Hi Micha,


So if I understand correctly, the APU bleed and APU start work correctly with both (ON)-OFF and ON-OFF switches, but not the APU master nor the QNH STD on the EFIS is that right? I guess "air pressure on STD" is the QNH baro push button?

JL

Hello JL,

yes that is right so far, but I use buttons (only keystroke) and no switches (on and off). With switches it works, but the Apu-Master don`t work with buttons.
Only the Apu-bleed and Apu-start work correctly with pushbuttons.

Greetings Micha

Ok I wil try to correct that in next version.

JL

Hello JL,

thank you for your great support. With your software makes the home cockpit building fun.:D

Greetings Micha

Hi JL,

I haven't found a possibility to assign autopilot off and sidestick priority to the flightstick button in FMGS Config.exe. Did I miss it or is there no such possibility at the moment?

Regards

You try in "fmgs config" (joystick button):

For FCU AP:
FCU_AP1 and FCU_AP2

For sidestick priority:
CPT_APTO and FO_APTO

Hi,

The AP OFF/stick priority are labelled CPT_APTO and FO_ APTO (or very similar).
I'm quite sure they exist ;-)


Oops totom replied before me :-)
Just one thing, AP1 & 2 on the FCU should only be used for engagement of the AP. For disengagement use APTOs.
Same goes with the ATHR and the ATHRTO pb.
Cheers,
JL

Hello Mr. Jeehell,

great work -

however I´m experiencing some problems in my setup…

I´m running fs9, FMGS Server, AP/FBW and Sound modules on one machine,
all other modules on a second.

I did set the IP adress for the server on both machines.

After a while (something like 20 sec) first the EWD disconnects from server, after that the MCDU. The MCDU sometimes reconnects for a short period, EWD stays disconnected.

All other modules stay connected

OS is WIN 7 64

Does anyone have an idea what could be the problem ?

BRgds Toulouse

Hi Toulouse,

When you say they get disconnected, is it only because the FMGS server says so or it is as well visible on the related software itself (for example, pushing keys on the MCDU has strictly no effect)?

Regards,
JL

FMGS server says so and EWD + MCDU freeze on second computer. Tried disabling Firewall - same problem.

Are they freezing to the point you cannot use the right click on them?

No, I can close them with right click.

Did you check your widefs configuration? Are you running the modules as administrator? Sometimes Norton Sonar Auto Protect disables the modules. Then you need to exclude the modules from scanning.

This is really weird, the EWD uses the same TCP port than the PFD and OVHd... I think also there is a trouble elsewhere with a protection software??

Hello again,
sorry for my question on a late sunday afternoon - great forum, thank you again for so much support.
I disabled every protection - firewalls, virus scanner.

I´ll have to check Fritz´s suggestion - I´m using the starter program to call the modules.

I´ll try to start the modules separate, as administrator (i´m logged in as as such anyway, but this has given me problems before).

Strange however, it´s only these two modules, for the MCDU the FO´side shows the same behavior. All other modules work fine.

Hello,

The latest beta is out : http://www.jeehell.org/A320FMGS_B21.zip.

What's new:
-Added some hydraulic systems warnings
-CLR, RCL, STS and EMER CANC buttons for the ECAM are now operative.
-Updated I/O modules (SIOC, FSUIPC and FDS)
-Added CPFlight FCU module
-PFD Altitude alert logic (when ACFT is near the FCU selected altitude)

Cheers,

JL

Hello mr. jeehell,

first i want to thank you for doing very good and very hard work.

And now i have more questions, but i prefere to start only with the followed one:

i have just yesterday installed your software, and until now i didn't get it ro work. So i thought it is a good idea to contact you. i try now to follow your tutorial written in the user's guide. When i fill out the flight plan as you described, the mcdu don't show the speed and the attitude on the right of each waypoints.

i am using your software on same pc as fsx. My system is intel q6600 with four cores on 3.60 ghz graphiccard nvidia geforce 8800x and 2GB of RAM.

Please tell me, what i am doing wrong. After that i will ask for the next problems like joystick problems.

Hello CaptainBon,

The first obvious reason is you have'nt filled out completely the MCDU, especially the INIT A and the INIT B pages. Also the Perf page is important.

Cheers,
JL

Hi JL,

Thanks for the new version. Looking very nice. Excellent!
But I have a little problem with the 2nd Init page on the MCDU where you punch in the weights. For some reason I cant access it, saying "not allowed". The A/C is still on ground and the problem is not new with version 21. I also had it in the previous versions. Same for the Flex Temp. If I punch in, let's say 15 degrees, it gives me a "not allowed". Any idea, what could be the reason? How is the logic to be able to access the INIT B page? On INIT A departure/destination, Flt level & IRS has been set and aligned.

What I also noticed... if you set any alt or speed contrains for any waypoint, it takes up to a couple of minutes until the updated magenta constrains show up at the F-PLN page. Sometimes the F-PLN page doesnt update the constrains at all. However, on the ND they are instantly updated and shown for each w/p.

and... last but not least... do you plan to keep up to date wrt FSUIPC 4.7 in any of your upcoming versions?

Thanks for your great support!

Cheers,
Rob

Hello Rob,

INIT B page is only accessible when the engines are shut down, that's most probably why you get an "NOT ALLOWED" message. There is an option in the ..\FMGS Server\PERF\PA320\Aircraft.ini file called INITBaccessible: put yes if you want to keep the page accessible event though it's not realistic.

As for the FLX temp, 15°C seems way much too low. The Flex temperature has to be to over ISA temperature +29°C or over current temperature.

Cosntraints on FPLN: yes I have to rework that part, I don't know when though.

FSUIPC V4.7: not compatible for the time, I still don't know why, I need to do more testing.

Cheers,
JL

Hi JL,

what a quick reply! I am just wondering how you handle your everyday life with extra workload!? :-) Really Great Support! Your hints are very helpful an reasonable. I didnt know about the link to the running engines and the flx temps. Thanks.

I asked about updating FSUIPC, because a friend wanted to try it on 2 Pcs. However, we are not aware of any option to get a registry key for the "old" FSUIPC 4.6 version. As far as I know, if you buy a key for FSUIPC 4.7 including widefs you wont be able to use it with the out-dated 4.60 version.
Last night I also tried to use the unregistered 4.7. On ground I didnt notice any trouble. But when you kick in the autopilot, the A/C starts pitching up rapidly way beyond alpha stall and you lose control. I tried it twice... both times I had the same reaction. But I am sure you know about it already :)

thanks buddy,
Rob

Hello again,

Well not always easy to keep up with questions, but I do my best ;)

As for FSUIPC V4.7, I have no idea why it won't work. I Use the same offsets for FS2004 and FSX, and for several versions of FSUIPC now, and since V4.7 it won't work anymore with the pitch control!! I asked P. Dowson but he says he didn't change anything concerning that... So I need to do more tests and find out exactly what changed.
However, I always thought that a valid FSUIPC key works with all versions of the intended FS, so a FSX key works with all FSUIPC FSX versions?? Did you give it a try?

JL

Hey JL,

unfortuantly, I can't simply try since I also use the unregistered 4.6 version. I wouldn't hasitate to get a key for 4.7+Widefs if I would know for sure that the new 4.7 keys also work for 4.6 and the corresponding previous widefs version. But if it doesnt work, there is no reason to buy it at this point of time.

Have a nice weekend!

@ EVERYBODY: If anybody bought a key for the new FSUIPC 4.7 version, please try to use this key for the previous 4.6 version and let me know if the new keys are compatible with older versions of FSUIPC. Thanks to one who has the time & chance of trying and letting me know if it works :)

Cheers,
Rob

just so you know, an unregistered version of FSUIPC should work as well with my software, so you could try deleting all files in FSX/modules folder and try with a fresh new V4.6 version.

JL

I know... as I said, I already use the unregistered 4.6 module with your software on my pc and its working great!. But a friend has a set-up 2 pc network and we wanted to try it with widefs which we dont have, yet. But then we come to the issue with the newer 4.7 keys and the updated widefs version... we dont spend 45€ for a 4.7 FSUIPC version with widefs, when we already know that 4.7 doesnt work for what we want it... well, I guess we have to wait for the fix of the pitch problem wrt to 4.7 and then get the 4.7 and widefs bundle to try the networking options :) Looking forward!

Rob