A320 FMGS beta 26

[jeehell]

Hi,

Rob: I did not notice this issue from FLX to CL, I'll check again sometimes. Concerning the drawn route, yes sometimes there is a small error in the arc calculation, I might redo that someday when I can get a better navdata with ARING 424 legs, but for now, we'll have to live with it...


Patrick: I don't have the right answer taken out of the FCOM. Though I'm pretty sure SFCC single failure is no problem for the auto retraction of flaps, as both SFCC receive airspeed/ange of attack info from the ADIRUs. Only thing, the flaps/slats will move at half speed. They also do not explicit which ADIRU is for which SFCC, though Airbus is quite known to be redundant, I'd say SFCC gets ADR1&3 and SFCC receives ADR2&3, and they must switch internally from one ADR to the other in case of ADR malfunction (it does not cover the abnormal indications, only the plain failure...) OR the ADR Switching solves that as well. Could be a question to post in a tech forum


Cheers,
JL

[AirFan]

Hi,

I solved the mentioned ATHR disconnect issue. After a complete new install and reconfiguration my problem was gone.I have still no clue what cause this problem... Now it works as it should

Thanks JL!

Rob

[adonismartinez]

Regarding the SFCC question, if you lose one ADR1 at takeoff you will receive the ECAM and you will have to switch to ADR3, and set the malfunctioning one to OFF. Im not sure if a computer reset can be applied to reset the bad ADR. Now consider the scenario of a dual failure of the ADRs : this means Alternate law, with protections lost with a possible unreliable speed emergency if the third one fails. In that case the ADR 1+2+3 Fault procedure on FCOM 3 is a veeeery elaborated-step-procedure which mainly suggest to use your GPS information to get a speed and altitude and solve the problem. Not going deep into it , your PFD will display a backup scale for the Airspeed and a dashed altitude indication with an "estimated" value. IF Airbus did this, maybe an in-flight solution for a failed ADR is not possible, just turn it off.

In the speed tape,(in a normal scenario) the FAC will compute the high and low speed warnings, the F and S speeds are based on the flap leveler position, so what about it the logic for the auto retraction remains more in the flap leveler rater than the SFCC computer?

Best regards
Adonis

[sacramento]

Error.jpgHi:
First off all, congratulations for your software...
I have a problem with the configuration off my joystick, that is a Microsoft Sidewinder...
When i try calibrate the joystick the apllication freeze, and sort a lot of strange thinks, like i try to show you in the attached images...something wrong?

Thanks

[jeehell]

Hello Sacramento,

I'm sorry but I can not read the error message in your screenshot. What does it say exactly?

Also, did you install hardware support for SIOC, FDS or CPflight?

JL

[sacramento]

Hi JL...

Thanks for your reply...
Yes i had install hardware support for Sioc, FDS etc etc...

The error in the image is:
Floating Point Division by zero

[jeehell]

If you do not use any hardware from opencockpit, FDS or CPflight, remove the hardwaremodules folder. Chances are good it comes from that. If you use some of the hardware, inside the folder, you can remove the DLLs which are not related to the hardware you use.
For example, if you use FDS hardware, keep JeehllIIT.DLL and interfaceIT.DLL, and remove all other DLL.

Also, the error you mention, at what precise time does it start happening? After clicking a "set" button?

[sacramento]

Ok...This evening i go do that you mention...exclude the hardware modules...
is a strange procedure, the application, such as it is frozen for a few seconds, and then breaks free, but then freeze again, and after a while then get the error I mentioned

[jeehell]

If removing the DLLs work, maybe you can also test to see which one(s) triggers the error?

[sacramento]

Yes...if the error continues, after remove the Dll's i go see which one trigger the error!

Thanks