A320 FMGS beta 30

Hi to all

Additionally, as I'm new here and to share my experience:

My system is more a A320/340 - Cessna hybrid than a specific type.

A320FMGS B29 (last update), fsuipc 4.827

System:
1 Pentium4 Laptop with W2k and A320FMGS-CMCDU, 1 external OC-MCDU, IOCKeysDriver,
1 Pentium4 Laptop with W2k and A320FMGS-CPFD and -CND (as the ND is too slow, I get it via tightVNC Client from the MainPC as workaround, the rate is faster),
1 Pentium4 Laptop with W2k and A320FMGS-SD,-EWD,-STBY and -FND,
1 PC CoreQuad Q8300 with w7/32Bit with A320FMGS-OVHD on two touch monitors, GForce GT620,
1 MainPC i7-3930k with w7/64Bit with A320FMGS-Server,-FPFD,-CND (transfered via tightVNC Server), FSX on three touch monitors, GForce GT220 and GT520
with the following USB HW connected:
1 FCU from CPflight, 7 Goflight modules, 1 selfmade (sm) tiller, 2 Logitech Attack3 sidestick, 1 sm speedbrake, 1 sm flaphandle, 1 sm parkbrake,
1 modified thrustmaster pedals, 2 modified saitek thrust quadrants,
1 fscockpit ECAM panel and 1 fscockpit RMP with drivers, 1 OC-ATC/TCAS panel, 1 OC-USBOutputCard with SIOC 4.01 driving selfmade Ruddertrim display,
GFdisplay driving lights of Goflight modules and selfmade EngineStart and RTO-Autobrake panels,
Outer views:
7 Pentium4 Laptop with W2k, FS2004 (better framerates), Wideview
additional Support:
1 Pentium4 Laptop with WinVista, moving maps, WOL-SW to start all computers remotely.
2 wireless Keyboards and 3 manual USB-Switch to share the keyboards with all the laptops.
1 Wired keyboard for emergency if nothing goes on anymore with wireless ;-)

The system was grown over years with old laptops which had their best days before and were out of service.
Generally, communication between all HW and SW works quite well, but the CND runs fluently only with the workaround.
Startup and properly shutdown with all the computers takes some time.
The advantage of the number of PCs, each of them does not have to calculate too much.
Today I would take only 2 Fast PCs due to the complexity.

A320FMGS B29 is very valuable to connect all the necessary systems, thanks to JL!

Regards Rémy

Hi Rémy,

Welcome onboard.

Regarding your initial post on the auto brake buttons: the offset should work, I will check that anyway when I have some time.
However, please note the three buttons will only have an effect when the brake is working correctly, that implies having hydraulic power on G and Y systems and also turning ON the A/SKID toggle switch (located just next to the A/BRK switches on the real acft).

Regards,
JL

Hi JL
Thanks for the answer. To be more precise, all systems are on, engines running and auto brake (ab) is working fine e.g. ab is max showing blue light and RTO corresponds to that. But if I change the offset state in fsuipc to ab low, your panel remains on ab max. Also if I change on your panel to e.g. ab med, the state of FSUIPC offset 78ED does not change.

Maybe I use the 4 states of offset wrongly. As I understand 78ED can have the parameters 29,30,31 or 32 (or the corresponding HEX) and a change within your panel should change the parameter, does it?

Regards Rémy

Edit 26.05.13:
Thanks JL for your hints. Finally the use of the offsets was correct and they work, I did not start the hardware connect automatically on the Test PC. I did not realized, that it is also important for the connection, and that it is not enough only to have the fsuipc connection.
Now it works fine and I can drive the A/BRK from the external device.:razz:
Regards Rémy

Hi Rémy,

The offset 78ED is only used for the switch input. To read the actual LED state, for the autobrake you need to use offsets 7393 and 7394.

The general principle:
-Each time you push (to switch it either ON or OFF, it is a momentary switch) an A/BRK button, you put the value of that button in offset 78ED.
- If an A/BRK level is ON, it will be indicated by one of the bits of offset 7393 or 7394.
- The decel light is triggered on one bit only (7393 bit N°5), it's up to you to assign it to the correct button (the one which is ON).

Regards,
JL

Hi all,
since I have rebuild my systems from scratch, I have the a.floor problem directly after the start on the runway when pushing the thrust lervers to the maximum position. No weather engines running. All systems working fine. Does somebody have clue? Could it be something with joystick configuration?

Regards
Stefan

Hi,

I would need more information on the conditions it is happening. A.FLOOR can only be triggered when airborne normally?

JL

Hi JL,

In the latest version of fmgs I found some bugs in SD Display and PFD display.
- In SD. When I turn off the autopilot status page indicates AP Fail. It is not correct right? because it is not a fault.
- In the PFD. I have problems to get the correct display for the autoland, I always an indication of CAT 1, even if all systems are active. my problem? Using FS2004, and in approaching airports assisted in CAT3 I CAT I always see 1. But the category is not decided by the instrumentation A320?
Hope that help, or if it depends on one of my settings wrong.


Thank you very much

Daniele

Hello Daniele,

- If you disconnect the AP using the AP button on the FCU, then it is considered as a failure, because it is not the normal way to disconnect the AP/FBW. You need to disconnect AP using the AP T/O button on the side stick.
- Do you have an ovhd on a remote computer? if so it should be corrected in next version.

Regards,
JL

Hi JL,

Yes I have 2 pc, 1 for fs9-ect,etc. 1 for OVH-SD-EWD-And CPT panel.
Tanks, set the AP on the Joy ( Over-Take Button , yes?).
For the CAT problem , start the OVHD Mudule on FS-PC, Correct?

Many tanks for all.

Daniele

For the AP takeover, the best solution is to go in FMGS Config then Joystick buttons. Then select AP TO in the list.
For the CAT issue, I will probably release a new version very soon with the fix. Otherwise you can indeed run the OVHD on the FS PC.

Regards,
JL

Quote:

---

Originally Posted by jeehell

I will probably release a new version very soon with the fix.
JL

---

Hi JL,

again a tiny one... Autoland korrys are not part of light test. Maybe you want to add that. Looking forward for the new version :)

Regards,
Robert

I have a few minor problems (but maybe I'm wrong something: P): I was not able to start the engines! : D


I have a Saitek Throttle and I have configured his buttons to try to start the engines: 1 button on "ENGMASTER1," 1 to "ENGMASTER2," 1 to "SEL Normal" and 1 to "SEL Ignition".


Well, when I press SEL IGNITION I have to hold otherwise returns to NORMAL, why? The same problem I have with the keys ENGMASTER .. if you release the button, the engines return to OFF.


It would be more correct to have two buttons: one for ENGMASTER ON and another for OFF MASTER ENG, do you agree?


Another thing: I have one of the saitek switch panel that is not detected by the software (I would use it to configure some key overhead and landing gear) ... you can use it in any way?


All for now, hoping to try out the software in flight :)

Regards
Antonio

Hi,

The joystick buttons features I added are meant particularly for those who use bodnar's cards, where inputs are joystick buttons. They wire the inputs to physical switches, and so as long as the switch is held in the correct position, the input is kept ON.

Some of the actions have a "toggle mode", it is the case for the engine masters if I remember correctly (and also for almost all 2 positions toggle switches). So using "toggle mode" first press puts on ON second press on OFF then third press ON etc...

Regarding the SAITEK Switch panel, I do not know how this one works. Is it considered in FS as a usual joystick peripheral, or are there any tweaks?

regards
JL

Quote:

---

Originally Posted by jeehell

Hi,

The joystick buttons features I added are meant particularly for those who use bodnar's cards, where inputs are joystick buttons. They wire the inputs to physical switches, and so as long as the switch is held in the correct position, the input is kept ON.

Some of the actions have a "toggle mode", it is the case for the engine masters if I remember correctly (and also for almost all 2 positions toggle switches). So using "toggle mode" first press puts on ON second press on OFF then third press ON etc...

---

Hi JL, ok i will look for "toggle mode" and i will try to start engine holding "Ingnition" and press the Engine start button ;)

Quote:

---

Regarding the SAITEK Switch panel, I do not know how this one works. Is it considered in FS as a usual joystick peripheral, or are there any tweaks?

regards
JL

---

in fact the switch panel is not recognized as a joystick, not even by the simulator.
saitek releases a driver that connects with FSUIPC, I will try to find a way to detect it as a joystick. maybe I can ask saitek ..

Regards
Antonio

Hi JL and all,
regarding Saitek Swith Panel, i found the SPAD drivers for Saitek Panels...
This evening (italian time) i will try it ;)

Download - Tools for Flight Simulator - Home of the SPAD

Quote:

---

Originally Posted by asessa

Hi JL, ok i will look for "toggle mode" and i will try to start engine holding "Ingnition" and press the Engine start button ;)

---

Hi JL, ENG1MASTER don't have TOGGLE option :(

Ok I will add that in next version...

JL

Good evening,
I decided to put a third PC into my network with FMGS client software (downloaded from page 42). When updater is run I receive "login incorrect". Firewall is disabled, but has never been a problem anyway. I tried the search function on this forum, but couldn´t find anything (so I hope this hasn´t been dealt with before, if so, a line with the link would do and my excuse).
Greetings Toulouse

Quote:

---

Originally Posted by jeehell

Hi,

I would need more information on the conditions it is happening. A.FLOOR can only be triggered when airborne normally?

JL

---

Hi JL,
I am not airborne. From the stand it ends in an looping, looks cool.... All is working fine untill I start moving the thrust levers to the maximum position, checked it already without REX and it does the same. taxiing works fine. Ecam says all green. I will check tomorrow again and will take a movie. Sorry for the late responds, I was away a few days .

Regards
Stefan

Hi,

@Toulouse: please try using this version of updater.exe:
http://www.jeehell.org/updater.exe (I changed the server on which I store updates, and haven't change the updater contained in the installer, so not your fault ;-) ).

@Stefan: I'll wait for your movie, I cannot reproduce your issue.

Regards,
JL

Hello JL, last night I made ​​a small flight to test my HC.
I was able to start the engines using the "inverse" of the ENGMASTER (waiting for the toggle mode).


Your suite seems to work really well;)


I noticed, however, these small problems:


1. There is always the word "ILS APP" on the ND , but it should be displayed only with the APPR PHASE active
2. I can not save the position of PFD even though I have selected Lock Position
3. standby instrument ISIS is always active, even if I close it. Also I can not set "show minimized" window on the standby
4. If I active the landing lights, by pressing "L" on the keyboard, this will turn off after a few seconds.
5. The Saitek Switch Panel is not detected by the software with the SPAD drivers (maybe it needs an additional module?).



All for now, on Wednesday I will make a new flight (this time on ivao) and another test.


greetings
Antonio

Hi Antonio,

1. Weird, it should have been corrected. Try to update using http://www.jeehell.org/Updater.exe (put it inside FMGS root folder to overwrite the old one).
2. You did do a right click -> Save as Normal position?
3. Can you explain this one I'm affraid I did not g et it
4. The lights can only be set through my software (eventually with hardware) but the normal FS shortcuts are not usable.
5. I do not know how SPAD works... I will try to have a look, but I cannot make any promise on that...

Regards,
JL

Quote:

---

Originally Posted by jeehell

Hi,

@Toulouse: please try using this version of updater.exe:
http://www.jeehell.org/updater.exe (I changed the server on which I store updates, and haven't change the updater contained in the installer, so not your fault ;-) ).


Regards,
JL

---

Hi,
could you please recheck the link. The file cannot be found on ther server.
Thank´s for your trouble....

The correct link has an uppercase letter, sorry:
http://www.jeehell.org/Updater.exe

Hi JL

Quote:

---

Originally Posted by jeehell

1. Weird, it should have been corrected. Try to update using http://www.jeehell.org/Updater.exe (put it inside FMGS root folder to overwrite the old one).

---

Ok , i will update it this evening, thanks

Quote:

---

Originally Posted by jeehell

Hi Antonio,
2. You did do a right click -> Save as Normal position?

---

Yes i did it but nothing change .... :(

Quote:

---

Originally Posted by jeehell

Hi Antonio,
3. Can you explain this one I'm affraid I did not g et it

---

From the Stby panel i opened ISIS and i put it in a position on the monitor, but i decide to don't use it... but anytime i start your software, ISIS was always displayed (and i have to close it).

Quote:

---

Originally Posted by jeehell

Hi Antonio,
4. The lights can only be set through my software (eventually with hardware) but the normal FS shortcuts are not usable.
5. I do not know how SPAD works... I will try to have a look, but I cannot make any promise on that...

---

OK , Can i use FSUIPC macro/offset together your suite?

Regards

You can use FSUIPC of course, just refer to my user guide to check the offsets to use.

JL

Quote:

---

Originally Posted by jeehell

You can use FSUIPC of course, just refer to my user guide to check the offsets to use.

JL

---

Ok , i'll try

Hi JL, somehow it worked today, no a.floor came up and I finished a start and landing on LSZH :-). What I did was loading the FSX A320 and then the FMGS A320 (--> Thank you Stefan for the tip :-) ). Again great job JL !!! Cheers Stefan

Hello,

The latest version is available. The automatic update is available, and a full package is online here:
http://www.jeehell.org/A320FMGS_B30.exe

I added Alternate (with and without reduced protections) and direct laws, as well as a few Faults messages on the EWD regarding the ELAC/SEC/FAC/Fuel pumps.
I also corrected a few bugs.

Best regards,
JL

Hello JL,

thanks. One important issue which prevents me to fully test the new version... after takeoff the T.O. INHIBIT remains on for the entire flight. So I cant "play" with the faults. But after a quick round I like the new thrust controller and the TCAS :)Need more time though for testing... what else did you change as you did not attach the new readme for b30 as usually... ;)

And a general question: In Overspeed you cant turn off the bell when pushing MW korry? Is that correct? And now in b30 you miss the BRK FAN/HOT korry in the light test but you added the autoland :)

I wont have a chance to test until weekend. So I will feedback later on. However, thanks alot and best regards to you!
Rob

Hi,

I did not change much apart from what I stated in my previous post. Mainly internal things (bugs and stuff like that).
I will try to have a look at this TO inhibit thing, this is strange.

The overspeed warning cannot be silenced, as in the real acft.

I'll add the BRKFAN to the lights test list. if you find other lights which are not lit up...

Regards,
JL

Great news, i will update this evening.

ps
Yesterday i tried to update but i've "already up to date" . I noticed the "ILS APP" message was still always displayed.

Regards
Antonio

Quote:

---

Originally Posted by jeehell

Hi,

I will try to have a look at this TO inhibit thing, this is strange.

---

Can anybody please confirm my issue that TO INHIBIT remains on for the entire flight? Or please drop a line if you do not have the issue.

@JL, here are some thing in general not related with new B30:

- WPTs mode on EFIS still shows WPTs with reference of AC position, so when in PLAN mode you might not see any WPTs when further away from AC.
- The estimated arrvial time to next WPT displayed on ND is incorrect and not updated correctly
- when entering a flight plan the times given in the MCDU are very nervous/changing the values at the beginning...up to the point you remove the last disCon.
- the position for TOC, TOD, DECEL etc. are not updated on ND when i.e. entering a direct and changing the FLTPLN
- Batteries should discharge
- APU should burn fuel

regarding b30: I tried an autoland. It did not crash but it did not touch down symetrically with both MLGs. Looked strange. Coincidence or did you touch the flare mode? And the 2 APs did not disconnect automatically after landing. Or is that due to my bug with T.O. inhibit which I had twice last night?

and an idea for two tools:

1. You use the GS/LOC data from X-plane. As you know this sometimes does not really match the position in FSX/FS9 very precise. I know some airports where the aircraft does not land any near to the centerline or you see an offset of the PAPI lights during approach. i guess you know the issue...
So is it possible to create a simple tool where you can select the data of a runway/airport and slightly shift the the GS/LOC data to match it with the scenery? So i.e. you can enter a lateral shift of 50 meters left and 20 meters down the runway for the GS?? What do you think? Then the ILS really brings you down correctly.

2. Do you plan a sort of instructor station where you can load an aircraft state or a position relative to an airport for doing a quick approach... stuff like that?

Regards,
Robert

Hi Robert,

Quote:

---

Originally Posted by AirFan

Can anybody please confirm my issue that TO INHIBIT remains on for the entire flight? Or please drop a line if you do not have the issue.

---

In my 2 flights i didn't have this problem (last version of B29).

Quote:

---

regarding b30: I tried an autoland. It did not crash but it did not touch down symetrically with both MLGs. Looked strange. Coincidence or did you touch the flare mode? And the 2 APs did not disconnect automatically after landing. Or is that due to my bug with T.O. inhibit which I had twice last night?

---

I tried an autoland on the rwy 34L at FCO and aircraft land very well.
In wich airport did you test it ? (so i can test the same condition)

Quote:

---

2. Do you plan a sort of instructor station where you can load an aircraft state or a position relative to an airport for doing a quick approach... stuff like that?

---

This is a good idea!
But i think solve bug is the priority now :)

ah... I forgot one thing in my previous post. Regarding the light test: How about including the FCU/EFIS in the light test. So you read the eights on every display and all lights are on? As far as I know thats the real deal.
regards
Robert

@ asessa: Thanks for your feedback. I did not have the TO inhibit thing in B29... but after install of B30. So I refere to B30 not B29.
Regarding autoland -> weird. In my case the ACFT always crashed during landing in B29. Last night I gave it a try with B30 and it did not crash but it looked abit strange. Thanks anyways.

Ah ok, i will update to B30 this evening so tomorow i will report you ;)
Regardings autoland : did you set all in APPR PHASE page in mcdu ?

Hi

@Antonio: the ILS APP message is displayed as long as an ILS approach is entered in the FPLN, whether you actually are in APP phase or not.

@Rob:
Yes most of these little bugs are already on my list of things to correct.
Regarding the tool to update the database: this is an interesting idea, but I need to think about it to make it right.
As for the instructor station, I already thought about it of course. But I'm not rushing things in that direction, because having a fully functionnal instructor station means people would use my software in a professional environment and I do not want that to happen.

The autoland issue is weird. Did you have any X-wind? as for AP not disconnecting, I suspect it is linked to the TO inhibit. The FMGS did not transition from TO to CLB mode it seems. It could be a bug. How did you perform your takeoff? FDs on and SRS and RWY TRK green on the FMA?


The FCU should be in the test mode sequence. What hardware do you use for the FCU?




regards,
JL

Quote:

---

Originally Posted by jeehell

Hi

@Antonio: the ILS APP message is displayed as long as an ILS approach is entered in the FPLN, whether you actually are in APP phase or not.

regards,
JL

---

JL, i think this is not correct.
I'm not very sure but ILS APP message could be showed only when APPR PHASE is active and an ILS approach was choose.

I searched for that a lot in different manuals, and I'm 99% sure this is not related to FMGS phase but only FPLN entry.