A320 FMGS B38

[jeehell]

Hi

I'm not sure how you want to use a display card with LEDs?
You're wiring the LED bar as if it was a 7 segment digit and send an "8" to it so all LEDs light up? If so, I will not add that, this is just not a "normal" operation.
I'd personnaly use a relay or an optocoupler to allow having enough current in the LED bar, using only one output as well.

JL

[tcane]

Hi

You're wiring the LED bar as if it was a 7 segment digit and send an "8" to it so all LEDs light up? If so, I will not add that, this is just not a "normal" operation.

JL

Hi,

Yes, like this and this was not my idea.
I bought last year a FCU circuit board with panels from a friend and he had bought it from someone in Spain who has well developed with a few guys and Opencockpits. In short, he stoped to build his cockpit and i get some things like this for a bargain.
Unfortunately, he had no real manual for it but only images and tables etc. In some pictures you can see that the display cards have been used for the LED bars and even in a SIOC script there are also signs of this.

I now that this are not a "normal" operation and I would be glad if it run on an ordinary master card. But unfortunately this is not so and I will probably have no choice unless you can be found in the attached images and scripts out something.
Or maybe you've got an idea how does it work with the display card and Jeehell anyway?
I think the main reason why has the guys make this so is that it is a pulse width modulation.

This pictures and the linked SIOC_Script are not from me.
If anybody need more pictures... write me a PM.

CBT-1a.jpg PCB_FCU.jpgIO-FCU-platine.jpg132_3293.jpg

SIOC_Script Dropbox link

Thanks a lot!

Regards
Florian

[jeehell]

In this case, you will have to do something like that (here only for the LVL CH bar, you'll need to adapt the code for the other bars...):

1) make an additional script which SIOC Creator will append to it's own script which will give you the jeehellware.ssi. Add something like you already wrote:
Var 1000, name LVLCH_BAR, Link IOCARD_DISPLAY, Device 1, Digit 65, Numbers 1 //(here i need more Digit´s for this)
2) Don't forget to add that additional script file into SIOC screator ...
3) For LVL CH LED in SIOC Creator, put completely random led numbers which are NOT used by your hardware (use high device numbers for example)
4) Apply the script in SIOC Creator
5) manually edit the jeehellware.txt file (it should be in hardware modules folder).
Find the LVLCH_LED variable in the jeehellware.txt and modify the script there:

Var XXXX , name LVLCH_LED, Link IOCARD_OUT, Device YYYY, Output ZZZZ //XXXX YYYY and ZZZZ will be determined by SIOC Creator
{
IF &LVLCH_LED = 0
{
&LVLCH_BAR = 0
}
ELSE
{
&LVLCH_BAR = 8
}
}
6) Recompile jeehellware.txt into jeehellware.ssi using SIOC tools I think it's in sioc config?).





Steps 5 and 6 will have to be done every time you make a change in SIOC Creator. I suggest you keep the modifications in a separate file so it's fast to copy/paste...


Regards,
JL

[tcane]

Hi JL,

wow big big thank you for your support and try to help me with this!!!!
First, i know this is really offtopic and i think it´s better if we prefer to continue the discussion in this separate thread?!
Otherwise we lose the overview here. I hope this is OK?

Florian

[Stephan Schwarz]

Hello Jean Luc,

yesterday I made the update from 37.x to the latest 38.5 ... and just want to say THANK YOU for that brilliant work.

I am now able to use my old dual core AMD PC for both sides PFDs and NDs again, the displays are no longer sluggish, really nice!

One bug (?) I see: the bar under the ND always shows "TA only" even if I am in TA/RA mode.

Again, thanks a lot!

Stephan

[jeehell]

One bug (?) I see: the bar under the ND always shows "TA only" even if I am in TA/RA mode.

Not a bug, below 700ft AGL (or 800ft don't remember), TCAS works only in TA mode.

JL

[navigator88]

Hello, Jeehell is right TA only is not a bug A320 manual reports:

The TCAS has two modes of operation:
‐ TA/RA : This mode allows the display of all intruders
‐ TA : Can be selected by:
‐ The crew, on the ATC/TCAS panel, in case of aircraft degraded performance (engine failure,
landing gear extended), or when operating near closely-spaced parallel runways, or
‐ Automatically, if TA/RA is previously selected, and:
• The windshear  message is triggered
• The stall message is triggered
• GPWS messages are triggered
• Aircraft is below 1 000 ft AGL. Consequently:
‐ All RAs are inhibited and converted into TAs
‐ TA threshold is set to TAU ≤20 s, irrespective of the aircraft’s altitude
‐ No vertical speed advisories are indicated on the PFDs
‐ “TA ONLY” is displayed on the NDs.
If windshear, stall, or GPWS messages are triggered, or aircraft below 500 ft AGL, all the TCAS
aural messages are suppressed.

I wish to say a big thanks to jeehell for the great work in constantly updating this excellent A320 software.

Cheers
Ben

[Stephan Schwarz]

Thank you for clarifying this matter!

Now I have another small issue, where I dont know exactly if it belongs to FMGS:

When I load the A319 as flight model, I have a fuel flow of 122 kg per hour, even if the engines are completely shutdown.
This is only with the A319, all other flight models from A318 to A321 work as they should.

Anybody got an idea?

Thank you
Stephan

[Miatanet]

Hi all,

I can't find the function for disconnect AP from the red button on the sidestick. Which command do I need to chose from the dropdown list in fmgsconfig.exe?

Thank you for short hint, I may be blind....

BR
STefan

[jeehell]

AP TO or AP take over