Printable View
Hallo All,
Update to the last version yesterday. Thanks Jean-Luc for your great work and add the ruder trim and switch panel. Nice one! ;)
My problem with the crashing Prepare 3D when I launch the jeeheel Server and displayed not connected but connected clients still be there.
Here is again a video. Now with the crash when I start the FMGS-Server! http://youtu.be/kYBYStYIG3o
Regards
Florian
Hi JH. After many re-installs I eventually lost both client PC's so have gone back to B34 which works fine. I have them both installed side by side now. I'm not using UAC on any of the machines but I will try and re-install with admin and let you know.
Hello JL,
no criticism on 38.3, everything seems to run fine and stable on the ground but I have to check the systems completely via a test flight yet. And thank you for the Power-On LED assignment, it's great and solved some minor problems!!!:)
I have three wishes for a future version:
- It would be fantastic to implement the Cabin Alt and Temp 1-3 control on the overhead panel via potentiometers - like the dim control potis for PFD, ND, EWD and SD. As far as I know they are controlled via potis in the real aircraft.
- When I turn on the APU master switch on the overhead panel, the APU page on the SD doesn't appear. I have to call it manually by the APU switch on the ECAM control. Is that like in the real A320? Don't know exactly but I think so.
- An actual offset list for download.
Congrats to that great software and thank you again for your superb work, Jean-Luc! ;)
Kind regards,
Bon
Hallo again,
Made a one hour testflight. And got two issues.
Regarding rework of the navdata loading. Erase old .bin files from the navdata folder on the server. After this start the server and let create the new .bin files. Copied this files into my two clients in the navdata folder. Can programming and track a route with the waypoints in the MCDU, ND etc.
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.
I hope someone can help me with this. :,(((
Hi Tcane,
Just put an update for the VOR/NDB/FIX/ARPT issue.
The other issue is more probably linked to graphics card / drivers...
Best regards,
JL
Hi JL,
does there also an offset exist for the new Power-On output assignment? And if yes, what are the values for?
Thank you.
Kind regards,
Bon
Bon please see the "help" sticky thread for the offet list. http://www.mycockpit.org/forums/showthread.php?t=27527
You're looking for the battery offset which is used to know if power is on.
JL
Hi Jean Luc,
Thanks for your update!
Is the update "On Air"? Start the FMGS but there comes no autoupdate Popup...
Yes it should be there??
JL
That is Strange! There was no autoupdate on all three machines... I will Test it this afternoon again and give you a notice.
For safty: Do you have maybe a link with a complete install file?
Greetings
Florian
Tcane is right, theres no auto-update available on all PCs...
Bon
Hi Jeehell,
there is no update available so far, when I run the updater, it appears :service under maintanance...
Ben
Hmm, also strange:
Yesterday I've installed 38.3 and tested a short startup. Worked so far.
Today I started the hole system like every day... and there seems to be no connection between FMGSServer and FMGS clients any more. But WideFS recognizes all three WideClients.
All input assignments in iitcreator are correct and able to be tested in iitcreator, so all output assignments are, all poti and switch assignments in FMGSConfig are there and working, network recognizes all PCs with their right IPs, "StarterFSX" brings no error message - but when I choose "ExtPwr" in FSX, there's no light on the Overhead panel, and there's also no light on the virtual OVHD display. Also strange: I cannot move any virtual switch on the OVHD display software. In short: there's power available for the hole system, everything stays dark.
I have tried three hours without success and don't know what's wrong. I've changed nothing. Any hints?
Best regards,
Bon
Hi Bon
I had the same behavior today with one of the two clients. Then I started the client software as administrator. And it worked - like discussed many times here. Have you tried this?
Regards
Adrian
Hello Adrian,
yes, I know this behaviour and I always start all software parts as administrator. BTW: the hole system is Win7.
But many thanks for your input. I remember that this special problem also occured in B37.4 when I've implemented the PDF, ND and EWD/SD dim poti control via hardware (FDS FC-1 card). When I disconnected all the dim potis from all three FC-1 cards, it worked again. Maybe this is the same issue in B38.3 but I have to test that yet. Now I have to work. I don't think it's a problem in FMGS but with the FC-1 card connection via hardware connect. Mysterious. Will reply.
Best regards,
Bon
B38.3 -- no TCAS alerts on IVAO for some strange reason even with TCAS TFC set to ALL, TCAS mode to TA/RA.
Traffic shows up on IVAP client internal TCAS.
Hallo Jl, Hallo Guys,
Got some similar issues like the other guys. Start again a one hour trip, after 20 minutes the Hardware FCU (Connected on a OC Mastercard with SIOC) stop to work. Recognized no inputs or outputs. It seems to be, thats are the same or similar issue like Bon... respectively my problem with no working OC Card some time ago... In the last version the problem has gone...
With the non-function autoupdate was already mentioned.
Off course i start all clients and server as admin! ;)
King regards
Florian
Hello everybody
Today, I flew two legs (LSZH-LSGG-LSZH) with B38.3. And now I also discovered the 'disconnection problem' as reported here as well. I was running two clients. Only the client with PFD, ND, and MCDU on it disconnected twice. The other client with EWD, SD, standby instruments, and HW drivers for FDS and Skalarki never disconnected.
Here are some extracts from the logs I attached.
I started the simulator on 17:10:03 as can be seen in log logNDB.txt
Then I started the 'PFD/ND/MCDU' client SW (IP 192.168.1.91) without 'administrator rights'. According to the logNDB.txt the client connected but then an error occurred and it disconnects as shown below:Code:*17:10:03* Navdata module launched Server
*17:10:03*
*17:10:06*
*17:10:06* Navdata1:
*17:10:06* -ARPTliste:15336
*17:10:06* -NavaidListe:18198
*17:10:06* -FIXliste:183324
*17:10:06* -AWYsegments:97152
*17:10:06* -MarkerList:2545
*17:10:06*
*17:10:06* Navdata2:
*17:10:06* -ARPTliste:15165
*17:10:06* -NavaidListe:18211
*17:10:06* -FIXliste:180118
*17:10:06* -AWYsegments:96338
*17:10:06* -MarkerList:2574
*17:10:06*
*17:10:06* server started on port:8006
...
I stopped the client SW and restarted the SW with administrator privileges. I also started the 'Standby/HW' client (IP 192.168.1.93) with administrator privileges. Then the logNDB.txt shows this:Code:...
*17:10:49* Client connected: 192.168.1.91
*17:10:50* Client connected: 192.168.1.91
*17:11:01* Client Disconnected: 192.168.1.91
*17:11:02* Client error 10053
*17:11:02* Client Disconnected: 192.168.1.91
...
On the WideFMGSserver screen only the connection of the clients started with administrator privileges are visible. Following the extract:Code:...
*17:11:13* Client connected: 192.168.1.91
*17:11:22* Client connected: 192.168.1.91
*17:11:26* Client connected: 192.168.1.91
*17:11:48* Client connected: 192.168.1.93
...
After more than one hour of flying (it happened during takeoff in LSGG), the 'PFD/ND/MCDU' client stopped working. All three displays were 'frozen'. So I stopped the client SW and restarted it with administrator privileges. The logNDB.txt shows the following entries:Code:WideFMGS server Log.
port 8003:192.168.1.91 connected
port 8004:192.168.1.91 connected
port 8005:192.168.1.91 connected
port 8003:192.168.1.93 connected
port 8005:192.168.1.93 connected
port 8004:192.168.1.93 connected
Please note that the client error reported (10053) is exactly the same one as when I started the client SW without administrator privileges.Code:...
*18:21:08* Client Disconnected: 192.168.1.91
*18:21:09* Client Disconnected: 192.168.1.91
*18:21:09* Client error 10053
*18:21:09* Client Disconnected: 192.168.1.91
*18:21:25* Client connected: 192.168.1.91
*18:21:37* Client connected: 192.168.1.91
*18:21:39* Client connected: 192.168.1.91
...
And the WideFMGSserver shows this:
The next client communication problem of the 'PFD/ND/MCDU' client was after 20 minutes. So the time was much shorter between the 1st and the 2nd crash than between the initial start and the 1st crash. The following extract shows the rest of the logNDB.txt entries:Code:...
port 8003:192.168.1.91 disconnected
port 8004:192.168.1.91 error
port 8004:192.168.1.91 disconnected
port 8005:192.168.1.91 disconnected
Fpln OnError
port 8003:192.168.1.91 connected
port 8004:192.168.1.91 connected
port 8005:192.168.1.91 connected
...
Code:...
*18:40:12* Client Disconnected: 192.168.1.91
*18:40:12* Client Disconnected: 192.168.1.91
*18:40:12* Client error 10053
*18:40:12* Client Disconnected: 192.168.1.91
*18:40:28* Client connected: 192.168.1.91
*18:40:38* Client connected: 192.168.1.91
*18:40:42* Client connected: 192.168.1.91
*19:00:02*
*19:00:02* Module stopped normally
And the corresponding entries of the WideFMGSserver log:
I also have to mention that my 'PFD/ND/MCDU' client runs at 100% CPU (which seems normal according to the discussions I followed). Hence, it may not have enough CPU time to run the communication 'on-time' (this is my speculation :wink:). The 'Standby/HW' client has the same HW as the 'PFD/ND/MCDU' client, but the CPU runs at 40-60% only. Therefore, it might be interesting to here from you all, if only the 'max CPU' client disconnects or if it happens to 'any' client.Code:...
port 8003:192.168.1.91 disconnected
port 8004:192.168.1.91 error
port 8004:192.168.1.91 disconnected
port -1: error
port 8005:192.168.1.91 disconnected
Fpln OnError
port 8003:192.168.1.91 connected
port 8004:192.168.1.91 connected
port 8005:192.168.1.91 connected
I apologize for the very long report. But I hope that this can help to sort out the root cause of the communication problem. Many thanks to all of you for being so active in this forum!
Adrian
Hi all,
I just come back from a short test flight after updating to the latest version and I flew from LSGG to LSZH without any issues, no disconects, all went fine and was exciting as always. Thank you again JL for that outstanding software.
Using Skalarki HW and FSX with four PC systems.
Best regards
Stefan
Hi Buentead (and the others with disconnects...)
It's possible that too much CPU strain could make the client disconnect .This is to "save" the server from waiting too long transmitting data it removes the lagging client, otherwise the whole network would suffer lag. I'll try to increase the delay before it "cuts" the connection.
I can't say much more than sizing the computer correctly to run the PFD and ND which are heavy CPU users.
You can try to reduce the PFD/ND loads by adding these 4 lines in the PFD.ini and ND.ini files (put the 4 lines in the 2 files, do not put the ND lines only in the ND.ini...):
PFDminDelay=0.1
PFDmaxDelay=0.3
NDminDelay=0.1
NDmaxDelay=0.3
(the default values are 0.04 and 0.2)
You should also refrain from using the EGPWS as it adds CPU usage.
A multi core CPU is best (ideally core i7 or similar...).
Regards,
JL
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
Hi JL,Quote:
Originally Posted by tcane
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?
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
Hi JLQuote:
Originally Posted by jeehell
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
Stefan, the files are created by the FMGS Server in C:\A320FMGS\Navdata (default installation folder).
JL
Quote:
Originally Posted by anzabon
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
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
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?
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?
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
Okay, I've tried to get B38.3 working again but with a fifth Win7 PC only for the MCDU to reduce CPU load on the PFD/ND PC.
Started as administrator, power on, system okay (still without the non-function buttons CSTR, WPT etc), APU started, IRS aligned, MCDU programmed, taxied to RWY and took off, 7 minutes fun in the skies......... then no reaction on the PFD/ND any more! Flight cancelled mid-air! :roll:
Now I have only the PFD and ND software on a clean and powerful computer, a fast and stable network but the disconnections still appear. What has changed to the previous version? I'll not make any tests with 38.3 any more and will drive 37 until a new one is out. Takes too much time to spin around.
Best regards,
Bon
@Mike,
The old download link doesn't work any more. I have the old B37 exe on an usb stick but it's not here at home. Have to look for it on Monday.
Hi Bon,
that would be cool if I could have the B37.
Many thanks in advanced!
Would be nice if JH could find the problem
It's such a nice and good software!
If any help is required please let me know!!
Hi,
The latest version is out.
http://jeehell.org/A320FMGS_B38.4.exe
I have no idea what may cause the network issues. Lots of people dont have those, so I can only guess something is wrong with the setups of those who have that issue. It could be a lot of different things:
- Anti virus
- admin rights
- router issues
- firewall issues
- port conflict with other software
- various things I will never think of...
(this might be a key linked to the error 10053 one of you had:
http://www.altn.com/Support/FAQ/FAQR...mber=KBA-01510
http://support.microsoft.com/kb/204594
)
Regards,
JL
JL,
once again thank you for your hard work, we appreciate that very much!
You are our hero! I will test 38.4 asap.
I wish you and all other guys here a nice weekend!
Bon
I don't have any issues with connectivity..but then again I am just running from one computer at the moment.
Test flight with 38.4 and everything is ok, even the autolanding (it was sluggish before due to scenery complexity turn to max, decreasing this allowed FMGS to sync with the aircraft).
Thanks again JL, we know you are only a one man team.
Dear JL,
I just would like to thank you for your hard work....
Hi JLQuote:
Originally Posted by jeehell
thank you for your quick response and for that great software which brings my sim alive. I found out and now it is working.
Regards
Stefan
For all those having black screens with latest update:
It seems the updater missed the auto update for 38.4....
Try installing that one :
http://www.jeehell.org/A320FMGS_B38.4.exe
then do the auto update...
JL
Hi all,
JH thanks for the new version I've tried now but I still have no NDB, VOR APRT or WPT on the remote PC's
I've tried serveral WIN 7 64B pc's and all have the same issue. If I start the ND on the FSX computer where the
server is running I can see all the NDB, VOR APRT and WPT...
The actions I did:
removed the anti virus software
turned off the fire wall
disconnected the router
but no luck....
I'Ve tried the default port configuration and I saw a error on Port 8005
**12:3:42.720**port 8005:192.168.0.163 connected
**12:3:42.720** fmaps send timeout.
**12:3:55.125**port 8005:192.168.0.167 connected
**12:3:55.125** fmaps send timeout.
after this I've changed the ports to
9610, 9613, 9621 and 9622 because they should be free accoding to the internet steatments
I did start everything but still the same issue no NDB, VOR APRT or WPT.
Here my error logs:
*****WideFMGSserver started at:13:55:48.156
**14:1:35.802** port 9610:192.168.0.167 connected
**14:1:35.803** port 9613:192.168.0.167 connected
**14:1:35.803** port 9621:192.168.0.167 connected
**14:2:44.755** port 9610:192.168.0.163 connected
**14:2:44.755** fmaps send timeout.
**14:2:44.756** port 9613:192.168.0.163 connected
**14:2:44.756** port 9621:192.168.0.163 connected
First CLient PC
*****WideFMGS client started at:14:1:29.142
Create result:1
Host IP: 192.168.0.10
**14:1:30.534** Port 9622: connected
**14:1:33.576** Port 9621: connected
**14:1:33.576** Port 9610: connected
**14:1:33.576** Port 9613: connected
Second Client PC
*****WideFMGS client started at:14:4:3.338
Create result:1
Host IP: 192.168.0.10
**14:4:4.648** Port 9622: connected
**14:4:7.487** Port 9621: connected
**14:4:7.690** Port 9610: connected
**14:4:7.690** Port 9613: connected
ANd NAV Data Log
*13:55:49* Navdata module launched Server
*13:55:49*
*13:55:51*
*13:55:51* Navdata1:
*13:55:51* -ARPTliste:15372
*13:55:51* -NavaidListe:18180
*13:55:51* -FIXliste:186502
*13:55:51* -AWYsegments:97710
*13:55:51* -MarkerList:2505
*13:55:51*
*13:55:51* Navdata2:
*13:55:51* -ARPTliste:15372
*13:55:51* -NavaidListe:18180
*13:55:51* -FIXliste:186502
*13:55:51* -AWYsegments:97710
*13:55:51* -MarkerList:2505
*13:55:51*
*13:55:51* server started on port:9622
*14:01:32* Client connected: 192.168.0.167
*14:01:34* Client connected: 192.168.0.167
*14:02:41* Client connected: 192.168.0.163
*14:02:43* Client connected: 192.168.0.163
*14:02:43* Client connected: 192.168.0.163
Can someone help me with this? What do I wrong here?
Many thanks in advanced!
Mike
forgot the say that the rest is working absolutely perfect!
Maybe something is wrong on the remote pc's FSscenery.cfg
that's the content:
[Scenery]
scenery.cfg=C:\ProgramData\Microsoft\FSX\scenery.cfg
FSfolder=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X
AerosoftPath=C:\Users\STH\AppData\Roaming\JeeHellWare
ip=192.168.0.10
and the log says:
*14:01:29* Navdata module launched WideFMGS
*14:01:29* NavDB files not found!
Maybe here is the problem?
Thank's again ;)