Hi,
The last version is 38.5.
You can get the full install here:
http://www.jeehell.org/A320FMGS_B38.5.exe
there are auto updates after the full install.
Regards,
JL
Printable View
Hi,
The last version is 38.5.
You can get the full install here:
http://www.jeehell.org/A320FMGS_B38.5.exe
there are auto updates after the full install.
Regards,
JL
Hi JL,
THX for the immediate support!
I now installed B38.5 (sry for my mistake, yesterday it was still 38.4) and allowed the Updater to install the additional update on all three PCs.
On my secondary PC the MCDUs, EWD and SD are running. Now the MCDUs ar working as usual. But there was no way to start the SD and the EWD, they donīt appear in the task bar as well. I made a fresh install of B38.5 without the update and now all displays are running.
One special thing of my config: While all other PCs run Win7 64Bit, the secondary PC uses Vista 32Bit. I will soon switch to another Win7 64Bit, so no need to solve the problem for me, if this is the cause.
I will report, if the missing update on the secondary PC leads to any problems.
Regards Rainer
HI Rainer,
DO you run the starter using admin rights on all PCs? it may be the reason.
It is really best to always use the same version on all computers, very strange things may occur otherwise...
Regards,
JL
Hi JL,
affirmative, as admin on all PCs, the only thing is, that I canīt assign admin rights to the EIS.exe, the SD.exe and the EWD.exe on the Vista-PC (on the Win7-PCs its possible and I did so). So perhaps a Vista problem? If so, donīt invest Your time in solving that, I think its my part to switch to Win7 (or 10, when itīs out) soon. But as described: the problem occurs only after the update.
Regards an THX again
Rainer
If you run the software manually (i.e. without the starter), it's been a long time since there no longer any SD.exe, EWD.exe etc... The 6 EIS display (PFDs/NDs/SD/EWD) have been replaced by a single EIS.exe file. This file must be run with the correct parameter to determine which display it actually represents (the physical display, i.e. the display at a physical position in the cockpit). This allows easy EIS reconfiguration (PFD/ND XFR etc).
The installer should install shortcuts (called PFD, ND, SD etc) which link to the EIS.exe with the correct launch parameter. Windows allows you to force admin right on a shortcut as well (at least 7 and most probably vista as well).
Regards,
JL
Thanks JL -- flaps 3 seems to have been fixed. I will have to do further testing.
Other things I am also testing --
1. T/O with FD not armed
FCOM 4.05.30 p5 "NO FLIGHT DIRECTOR TAKEOFF"
If a takeoff is initiated without FDs, the system responds as follow:
There are no FD bars.
There is no A/THR arming.
There is no guidance available.
The target speed on the PFD is that selected on the FCU or is defaulted to 100 kt.
Setting the thrust levers to the CL detent does not activate A/THR.
Note: Do not engage the autothrust prior to selecting a target speed on the FCU.
----
2. Autobrake disarm with one brake pedal, or speedbrake/spoilers disarm after landing.
Quote:
Originally Posted by OmniAtlas
Hi Omniatlas,
Confirm this issue read in Fcom..
Have you been able to test this setup with FMGS?Quote:
Originally Posted by immaging
I will also try a take off without V2 input.
Hi JL,Quote:
Originally Posted by jeehell
well, my fault, as you say, EWD and SD are shortcuts only, thatīs the same in my installation.
In fact I cannot assign admin rights neither to these shortcuts not to the EIS.exe, it is greyed in Properties/Compatibility. I can set the checkmark in Properties/Shortcut/Erweitert/Als Administrator ausführen (-dont know the term of english Windows-), but that doesnīt change anything. Seems to be a problem of (perhaps only my?) Vista, I installed the EWD and SD on my primary (Win7-) PC, there all is working fine even after the autoupdate. There admin rights in Properties/Compatibility are also greyed, but different to the situation on the Vista PC the boxes for admin rights are checked.
As I will change to Win 7 soon on all my PCs no need to solve the problem for me.
Regards Rainer
Hi
this may not be a problem with admin rights. What video card do you have? is it old? do you have drivers up to date or not?
Regards,
JL
This may be the problem: in this PC are two MSI R5450-MD1GH (Radeon HD 5450 LP HDMI 1024MB DDR3), and you got me ;) not updating the drivers (never change...). I will try that.Quote:
Originally Posted by jeehell
I will maybe have to make a separate EIS for old and new drivers, I had to change a few things in OpenGL graphics display to adapt to these new drivers... Keep me posted if updating drivers does no good.
I can confirm this logic works correctly. Autobrake will disarm when you also disarm the spoilers.Quote:
Originally Posted by OmniAtlas
I will continue my testing with
1. Take off with no FD engaged (early testing indicates A/THR arms in FMGS, contrary to the FCOM)
2. Take off with no V2 MCDU input
Hi JH, Hi Guys,
JH: Have you noticed my last post with SIOC Creator problem? I have a saved config file for the SIOC Creator, but it lost every time my saved options for the F/O MCDU (IDX) and the enabled Ruder and Switchingpanel.
Made a 10 Minutes Video in my HC from a nice flight from EDDH to EDDN with a nice sunset and Jeehell... :mrgreen: https://youtu.be/XU-XVQL2550
Hi JL,Quote:
Originally Posted by jeehell
I think I got it:
I made the update of the graphics driver (now: 13.251.0.0), but that didnīt result in any change.
Next step I copied only the EIS.exe of B38.5 before the autoupdate into A320FMGS/EIS, and this works. Comparing the two EIS.exe I realised, that the "old" one shows version number 1.0.0.0 and a size of 5,00 MB in Properties/Details, while the "new" one does not show a version number and has a size of only 2,88 MB. Seems the Autoupdate had a problem with downloading EIS.exe.
I deinstalled A320FMGS on the Vista-PC, erased the complete folder, made a new clean install of B38.5. Next step I cancelled the Autoupdate and started the Updater.exe manually with right click and "Execute as Administrator". Now the EIS.exe shows version number 0.38.0.0 product version number 1.0.0.0 size 5,18 MB - and it works!
I assume, it was not a display driver problem, but a problem of Vista to download the EIS.exe with admin rights from the Updater.exe. And that all in spite of UAC off. Windows...
Thanks for your help!
Regards Rainer
Hi tcane,
very nice video and very nice HC! ;) Do you use Prepar3D or FSX? And what add-ons do you have installed?
Thanks and a nice weekend!
Best regards,
Bon
Hi Bon,
thanks and glad you like!
Itīs Prepar3D 2.5 with ORBX Products (GLOBAL BASE, GLOBAL VECTOR, GLOBAL openLC Europe), ASN and GSX... i got also the REX4 Texture Direct with Softclouds but it was there not installed yet. Itīs the default Cloud Engine from P3D... Since yesterday I have installed the textures and it's even a bit better. ;)
Hi,Quote:
Originally Posted by tcane
I'll try to have a look soon.
JL
Hi,Quote:
Originally Posted by jeehell
very nice and no stress! Big thanks for this... and again for your hard work with the Bug fixes and innovations! :smile:
Florian
Hi again,
i have again maybe a stupid question.
I would like to assigned the SPD HDG etc. writing surface in the FCU. But i have a little problem because i use LED-BARS for this which are controlled with an Opencockpits display card. Another way is Unfortunately not possible. But the SIOC-Creator supports only the outputs from a Master or Outputcard. Is there a any chance to use it with my Displaycard? Maybe you can add a support for this in your next update?
I have try to write a Script for this and insert to the SIOC Creator. But it seems like this would not work... also there is a problem with the LAT ALT LVL/CH LED... because there is only one Output for this intended?!
Here is the Script that i have written and insertet to the SIOC_Creator:
"Var 1000, name LVLCH_LED, Link IOCARD_DISPLAY, Device 1, Digit 65, Numbers 1 (here i need more Digitīs for this)
Var 1001, name HDG_LED, Link IOCARD_DISPLAY, Device 1, Digit 79, Numbers 1
Var 1002, name TK_LED, Link IOCARD_DISPLAY, Device 1, Digit 64, Numbers 1
Var 1003, name SPD_LED, Link IOCARD_DISPLAY, Device 1, Digit 77, Numbers 1
Var 1004, name MACH_LED, Link IOCARD_DISPLAY, Device 1, Digit 78, Numbers 1
Var 1005, name HDGVS_LED, Link IOCARD_DISPLAY, Device 1, Digit 66, Numbers 1
Var 1006, name TKFPA_LED, Link IOCARD_DISPLAY, Device 1, Digit 67, Numbers 1
Var 1007, name VS_LED, Link IOCARD_DISPLAY, Device 1, Digit 70, Numbers 1
Var 1008, name FPA_LED, Link IOCARD_DISPLAY, Device 1, Digit 71, Numbers 1"
Maybe you JL or somebody can help me with this?
Big thank you in advance!
Regards Florian
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
Hi,Quote:
Originally Posted by jeehell
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. ;)
Attachment 10060 Attachment 10061Attachment 10062Attachment 10063
SIOC_Script Dropbox link
Thanks a lot!
Regards
Florian
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
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
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
Not a bug, below 700ft AGL (or 800ft don't remember), TCAS works only in TA mode.Quote:
Originally Posted by Stephan Schwarz
JL
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
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
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
AP TO or AP take over
Thank you JL.Quote:
Originally Posted by jeehell
Great support, as always.
Best regards
Stefan
Why if i start the FMGS server without FSX running it doesn't scans a nd build the scenery database? not needed anymore?
Hi JL
Please help me with a weird issue I have for long time.
Every time I should restart starterFSX several times, in order for OVHD logic and sometimes FCU to start.
I use FDS card for OVHD, CPFlight FCU, both connected to server PC and I run StarterFSX as Admin.
Regards
PS Why should I press twice the EXT PWR button in order to change its function? (ON-AVAIL and vice versa)
@Davide: not necessary anymore
@Leonidas: no idea, I do not have any issue. For the EXT PWR, how did you configure it?
JL
Via ITCreator. I've tried toggle mode too... Maybe both are the same problem, because while OVHD doesn't start, EXT PWR button lights up when I sellect the addon, but doesn't work...Quote:
Originally Posted by jeehell
Thank you,Quote:
Originally Posted by jeehell
Another problem i found in the FDS MCU module the dislpay dimmer don't work, can you have a look?
jL said he would look at this when he has time.Quote:
Originally Posted by dcutugno
New TOC hockey stick implementation with the newest release? I never noticed this before :)
Also I see JL has reworked the DEPART and ARRIVAL pages with more information.
Jeehell, i'm reporting this old bug again, seems the fmgs have problem with the LFBO AFRIC5B departure, it start an infinite leg on the ND at about 147 to South and back. Also at ABLAK fix on route to LFMN it start to go aroundin circle , this happens if you don't insert a rwy approach, nobody have this problem?
Try this route :
LFBO AFRIC5B AFRIC G39 FJR UL127 ROVOT UY373 ABLAK STAR LFMN
Hi all,
sorry for that stupid question:
any New Installation Way at P3D v2.5 to insert the A320 Model of Jeehell?
Regards
Andy