A320 FMGS B38

[janinp]

Hi JH,
No disconnects on my side.
Can you reproduce the inability to switch stby frequency when on vhf2 or nav2. This happens on both CPT and FO RMP panels (fscockpit hardware) since new version.
Thanks a lot.

Pierre

[anzabon]

... But i can´t see the VOR´s, NDB´s, WPT´s, ARPT on the ND when i push one of this buttons in the FCU. Have anybody also the same problem?
Sorry for the "stupid" question but have i done something wrong now???

The other thing is, that the ND/PFD/MCDU CPT. MCDU F/O and ECAM DISPLAY freezes after ca. 50 minutes complete. I got this Displays on one Computer.
ND/PFD/ECAM/MCDU CPT. are connected to a graphicscard and a TRIPLE HEAD TO GO.
MCDU FO are connected to the onboard graphicscard.
The ND and PFD for the F/O are on another client PC and still works continue without problems.
...

Hi JL,
this morning the 38.3 system worked again (very mysterious) but with the known difficulties. Before startup I've added the four lines to the PDF and ND ini's as described in your last post.
- no effects on the ND when pushing WPT, ARPT, VORD, NDB or CSTR on the FCU (like tcane described some days ago, too)
- CPT PFD/ND client disconnected after 15 minutes on the ground without any inputs in the system, only APU started. And I don't use EPGWS.

All software has been started as administrator, all PCs are multicore-i7 with Windows 7. I don't know what's wrong with 38.3 on my really fast system...
Now I've rolled back to 37.4 and everything runs fine and stable. Unfortunately without my beloved API Power On output feature, the extended ECAM switching and the great Rudder Trim feature

Best regards,
Bon

EDIT:
In case of too much CPU loads on the PFD/ND computers... in my system there are three clients: PC2 with PFD+ND+MCDU CPT, PC3 with PFD+ND+MCDU F/O, PC4 with ECAM+OVHD.
I have another PC available to remove the MCDUs from the PFD+ND clients. Is it possible to run both MCDUs on one machine?

[tcane]

Hallo all again,

Maybe somebody or you Jl knows whats going on with this strange issue?!
Here is again a small video with the P3D crash when i launch the Jeehell-Server. http://youtu.be/TimYAU3mFic
The strange thing is, that when P3D crashes (bing sound and blue mouse ball) the client´s displayed as connected. O.o You see the green connection after crashing.
When P3d doesn´t crash after starting the server, the client´s displayed not as connected but they are connected and works. Like there: http://youtu.be/jO1VVO9kDfc

I´m made an downgrade now, because i had a online flight this evening. Update then if there a new update out.

King regards
Florian

[Miatanet]

Hi all,

The latest version is available.
http://www.jeehell.org/A320FMGS_B38.3.exe (I skipped 38.2...).

What's new:
-Greatly enhanced ADIRUs logic
-Added SWITCHING panel selectors (ATT HDG / AIR DATA / DMC / ECAM ND XFR) in SIOC, FDS and CockpitSonic interface. Skalarki will probably arrive soon with an update of the profiler from Marcin.
-Reworked navdata loading:
*Navdata is computed from Aerosoft format to a direct format by the FMGS Server after each AIRAC cycle update
*This process creates .bin files in the Navdata folder (ARPT.bin,FIX.bin, etc)
*These files must be copied on your client computers in the same navdata folder
*If you change scenery or else, you need to delete the files on the server computer to re-generate them (then copy them again).
*If you update the airac cylce manually into navdata\navdata1 and navdata2 folders, you'll have to erase the bin files manually as well.


@Urs: this website is not mine, it is an unofficial one from Ben on this forum.

Regards,
JL

Hi JL

do not understand what bin files are created. Just did the NavData update to new circle but no bin files are created by Aerosoft in the navdata folder. My MCDU^s still have the old circle active. Where do I get the .bin files?

BR
Stefan

[jeehell]

Stefan, the files are created by the FMGS Server in C:\A320FMGS\Navdata (default installation folder).

JL

[AirbusMike]

Hi JL,
this morning the 38.3 system worked again (very mysterious) but with the known difficulties. Before startup I've added the four lines to the PDF and ND ini's as described in your last post.
- no effects on the ND when pushing WPT, ARPT, VORD, NDB or CSTR on the FCU (like tcane described some days ago, too)
- CPT PFD/ND client disconnected after 15 minutes on the ground without any inputs in the system, only APU started. And I don't use EPGWS.

All software has been started as administrator, all PCs are multicore-i7 with Windows 7. I don't know what's wrong with 38.3 on my really fast system...
Now I've rolled back to 37.4 and everything runs fine and stable. Unfortunately without my beloved API Power On output feature, the extended ECAM switching and the great Rudder Trim feature

Best regards,
Bon

EDIT:
In case of too much CPU loads on the PFD/ND computers... in my system there are three clients: PC2 with PFD+ND+MCDU CPT, PC3 with PFD+ND+MCDU F/O, PC4 with ECAM+OVHD.
I have another PC available to remove the MCDUs from the PFD+ND clients. Is it possible to run both MCDUs on one machine?

Hi all,

I do have the same issue like Bon, and I have only the MCDU and one ND running on a powerful notebook
Here my logs..

Client PC i7 8GB RAM 3 GHZ

FSscenery

[Scenery]
scenery.cfg=
FSfolder=
AerosoftPath=C:\Dokumente und Einstellungen\Mike\Anwendungsdaten\JeeHellWare
ip=192.168.0.10

logndb
*16:52:50* Navdata module launched WideFMGS
*16:52:50* NavDB files not found!

Main SIM PC

FSscenery

[Scenery]
scenery.cfg=C:\Users\Mike\AppData\Roaming\Microsoft\FSX\scenery.cfg
FSfolder=D:\FSX\
AerosoftPath=C:\Users\Mike\AppData\Roaming\JeeHellWare
ip=127.0.0.1

logndb

*16:46:36* Navdata module launched Server
*16:46:36*
*16:46:39*
*16:46:39* Navdata1:
*16:46:39* -ARPTliste:15372
*16:46:39* -NavaidListe:18180
*16:46:39* -FIXliste:186502
*16:46:39* -AWYsegments:97710
*16:46:39* -MarkerList:2505
*16:46:39*
*16:46:39* Navdata2:
*16:46:39* -ARPTliste:15372
*16:46:39* -NavaidListe:18180
*16:46:39* -FIXliste:186502
*16:46:39* -AWYsegments:97710
*16:46:39* -MarkerList:2505
*16:46:39*
*16:46:39* server started on port:8013
*16:46:39* Client connected: 192.168.0.167
*16:53:07* Client connected: 192.168.0.12
*16:53:13* Client connected: 192.168.0.12
*16:53:13* Client connected: 192.168.0.12
*16:59:45* Client error 10053
*16:59:45* Client Disconnected: 192.168.0.167
*17:00:30* Client connected: 192.168.0.167
*17:21:40* Client error 10053
*17:21:40* Client Disconnected: 192.168.0.167
*17:22:25* Client error 10053
*17:22:25* Client Disconnected: 192.168.0.12

Would by very nice if someone can help me/us

Thanks Mike

[anzabon]

Gentlemen,
let's be patient. I'm very sure, JL is already working on the problems and will offer a solution
@ Mike: Downgrading to B37.4 was the interim solution for me.

Kind regards,
Bon

[Leonidas]

Hi
My OVHD Logic (FDS card) and FCU (CPFlight) don't work the first time I run the starter, neither the second. I must close the starter, then rerun it for the third time, in order for the OVHD and FCU to work. Weird, why?

[EdwardInBeijing]

Hi JH, Tried the admin trick and it worked! Simple things, wierd though that other installs didn't need it. Have updated to latest versions and all seems good.

Just one thing now and I'm sure it's simple, there is no nav app to build the nav data, in the install, did I not install something important?

[AirbusMike]

Dear Bon,

ok, I will...
I'm new here and I cant't find the B37.4 download.
Can you tell me where I can find it?

Many thanks!

Mike