Printable View
No I don't use hub and yes I've tried 2 or 3 other sockets.Quote:
Originally Posted by jeehell
I'll try this cleaner and I'll tell you, but I don't think it's such issue, because the joysting works every time. I'm thinking the problem maybe the wires themselves from pots to the USB card.
Anyway congratulations for this software you made, that is much better than well paid others...
Thanks for your time
HiQuote:
Originally Posted by Leonidas
I've tried another PC and it does not work. So, could you suggest me a USB card that works for sure?
Thank you
Hi,
First, I do not have any name to give you as I don't use one myself...
However, I do not think this is the right approach. You said it works in FS/FSUIPC, so it cannot be hardware related. Particularly if one of two cards works? Or maybe I misread something. I know someone who uses 4 FDS-FC1 cards with my software. So it should work.
Maybe you messed the wiring of the buttons (not axis)?
JL
What do you mean "two cards"? I have only one FDS-FC1.Quote:
Originally Posted by jeehell
May I have his email or mycockpit username in a PM?
I don't use any buttons yet, only axis.
Hi,
No need for his email, I'm the one who completed his setup...
Is the card detected under windows control panel?
If so, try to recalibrate all axis. If you don't know how to do that:
-control panel -> printers and peripherals -> game controllers properties -> advanced properties of FDS-FC1 and in one of the tabs you have a calibrate button.
It may be that the amplitude of movement is not big enough for FMGS config to detect axis movement. Which happens when axis is calibrated on the whole potentiometer course but the real movement is afterward limited to a much smaller course.
JL
Yes the card is detected, but I never calibrate it under windows... You're probably right because the movements are very small indeed. I'll try this at the afternoon.Quote:
Originally Posted by jeehell
Thank you very much!
It's OK... I thought that configuration bypasses the windows calibration. Anyway, thanks a lot for your pacience...Quote:
Originally Posted by Leonidas
Well most software get joystick data from windows itself, and its windows which calibrates the signal. Other software may use different methods (or different detection thresholds) to detect axis movements, that's probably why they detected the axis when FMGS config did not.
Anyway, the most important part is you can use the card!
Cheers,
JL
Hi JL,
I have just installed the latest update of Navigraph for Level-D and have then imported that data in the Jeehell software by starting the configure.exe on the server PC (which was successful because it did not return any errors). When I look at the MCDU start page it still says "Active Nav Data Base 15APR-16MAY", whereas I would expect it to show the current cycle 1208. Is there anything I missed to perform the update?
Thanks
Stefan
Hello,
This is normal, in fact the cycle information has to be performed manually in the CycleData.txt file found in each navdata folder.
Regards,
JL
Good morning everybody...
Why can't see "SAVE CO RTE" at "MCDU MENU" page as user guide says at p.117? I've completed INIT and FPLN pages already.
Hi,
the user guide is outdated on that one. Now, as per the real acft, you need to go to DATA page then with one of the lateral arrows DATA 2 page. There, go to PILOTS ROUTES on the right.
JL
The Advanced User Guide is also outdated, because I can't find ND\EGPWS folder and extractor.exe (p.5)?Quote:
Originally Posted by jeehell
This is not outdated. It should be there (ND\EGPWS data\EGPWS data extractor.exe).
If it's not there there was troubles during instalaltion.
JL
Hi JL,
a short bug report: :)
- When I try to save an active route I get "MCDU display problem, please report issue" after I press store active f-pln.
So I assume you are aware of that one?
the fly by wire did a major step forward with the release of the current B25. However, there are still some bugs:
- when you do full back stick, sometimes the AC still tends to stall at low speeds - in fact in these moments the alpha max limit doesnt seem to be correct/considered.
- when you bank at level flight (i.e. 5000ft) the vertical speed changes significantly. You start with zero veritcal speed... after some banking I end with a sink or climb rate up of to 1000ft/min without having touched the elevator axis.
- btw is your stick sensetivity exponential?
- the ILS mode on ND contains all the signs for TOC, TOD ... etc. I might told you that already. I just noticed it again :)
- have you taken a look at the Fuel flow in reverse been stuck at some 4 hundred something kg/h? I just would like to know if this strange behaviour has something to do with my throtte axis controller.
- I am not sure if you can trigger the "FS-replay mode"... when in replay I always hear "DONT SINK". Maybe that can be fixed with the GPWS.
Cheers and Thanks!!!
Rob
Hi Rob,
-Hopefully the Route saving will work correctly in next version. The MCDU saying "please report issue" means that it detected a bug, but not necessarily that I know why, which is why I ask people to report it ;)
-FBW still needs some work in some corner areas, however it should maintain VS=0 in level flight without troubles (unless you bank more than 33°). What FS do you use FSX or FS9?
-Stick sensitivity is linear, or at least it follows linearly the inputs sent by windows.
-I'll try to correct that for next version.
-No still haven't looked at it. But it's most probably not because of your thrust lever axis.
-Replay mode will work fine, except that my software still thinks it's flying and which triggers some warnings. Also the exterior model will show weird governs movements because the AP wants to fly it, but the replayh itself is corect (forced by FS).
Regards,
JL
Hi JL,
thanks for your reply. just some comments:
wrt FBW: I use FSX and yes I exceeded the 33deg... however I thought that does not have any effect on how the FBW works. I thought the 33deg are just the max. AP bank and that you need to hold the stick beyond 33 deg... however I thought this makes no difference to the AC trying to keep same altitude.
So I just retried it with max 33 bank: You are right... the result is way better and it works as it should. But is that the same on the real AC ; only below 33 deg???
regarding stick sensetivity... have you ever tried an exponential input definition for the stick? How is it done on a real airbus? I just noticed that I need to reduce the sensetivity for precise and small pitch ajustments to keep the VS really at zero. But then it does not seem right for bigger stick inputs on pitch. I know that many people use an exponential function for stick input for RC flying. Maybe it also improves the simulator handling and is worth a try.
FS replay mode: You got me wrong... my replay mode also works fine... I just meant all the triggered aural warning because the software thinks its still flying or even thinks its in a different phase of flying... That's why I ask if you can trigger when FSX has the replay mode active --> so YOUR software knows that its just a reply on FSX side.
Thanks!!! & Cheers
Rob
Hi again,
I quote the FCOM:
Quote:
With the sidestick at neutral, wings level, the system maintains 1 g in pitch (corrected for pitch attitude), and there is no need for the pilot to trim by changing speed or configuration. Pitch trim is automatic both in manual mode and when the autopilot is engaged. In normal turns (up to 33° of bank) the pilot does not have to make any pitch corrections once the turn is established.
I'll give it a try someday, it's not top priority yet.Quote:
Originally Posted by AirFan
I have to check in FSUIPC if this can be done or not.Quote:
Originally Posted by AirFan
Regards,
JL
Thanks for the quote , got it!!!:)
last one for today: - the overspeed sound wave is linked to the stall sound.
Regards
Rob
I cannot see how that is possible since I haven't implemented neither sounds??Quote:
Originally Posted by AirFan
Are you sure it's not FS default sounds??
JL
uhh... you are right and I am really sorry. Indeed, I tried some external sounds. :)
Wow just found this forum after only going to linkfs forever lol. Been building a a320 in my lounge for the last 6 months and to only come across this software now after searching for a cheaper alternative to magellen for so long is mind boggling. You sir Jeehell are now a god in my book and i will be following your software religously lol, havnt actually managed to get anything to work yet but man am i so happy right now lol. Thanx so much Jeehells parents for having Jeehell!!!
Hi,
well cheers mate :-)
JL
Well bruv took ur proggy for a run last night and only after bout 30 mins had mostly everything running, looks damn good, just think i need more ram is all, on 4gb there aint much left once everythings loaded lol.......but from what i see so far im very impressed, you rock bruv ....Quote:
Originally Posted by jeehell
Hi Jeehell,
have made some more flights this weekend, and I have 3 questions regarding your software:
1 - Weather request in MCDU: I can remember that this has been working some time ago, but for a couple of weeks I am now always getting the "Error" response after some time "Pending".
2 - On some of my flights I had some weird displays on the N1% and FLX Temp, e.g. it showed "33]4.0" instead of 34.0%.
3 - Is there any chance to have the real door status (e.g. of the Project Airbus aircraft) showing in the DOOR/OXY display of the SD?
Thanks and regards
Stefan
Hi Stefan,
1. Ok I will check that. Maybe the server is down.
2. Strange, will check as well.
3. I may add that later. The problem is how FS handles the doors, not very handy.
Regards,
JL
Hi Jeehell,
I am having another problem here now. I am planning a flight from LFMN to LEPA, standing in LFMN at the gate. APU running, IRS aligned, ready to start the planning of the route.
After completing the INIT page, when entering the origin + destination airport in MCDU and also some waypoints, the MCDU is not calculating any T/C or T/D, also EFOB always remains 6.2 tons (what is loaded right now), speed and altitude at all waypoints is 0 / FL0. The whole F-PLN page looks incomplete. It doesn't matter if I change the route completely, the problem persits. Of course I have restarted all Jeehell components, even restarted all PCs, and also re-installed the AIRAC from Level-D, but not chance.
Any idea of what might go wrong here?
Thanks a lot
Stefan
Hello,
this is hard to tell.
Usually, the problems comes from the MCDU being not initialized properly. Also, VNAV is not perfect and bugs can occur.
JL
Hi Stefan,
just tried LFMN to LEPA for you... also starting at the gate. I didnt have any problems. I guess it doesnt really help in detail ... but maybe its helps you in anyway to know that others dont have this particular issue :)...Of course VNAV is not perfect yet, but I still get TOC and TOD for that route.
@ JL: any chance to add the GWPS/GS korry in B26? :)
Have I said THANKS yet?!? :)
Rob
Hi Rob,
This korry is already there??
JL
Hi JL,
hm? I could not find it in the SIOC Creator... I dont talk about the overhead korries. I meant the one on the CPT & FO Main Instrument Panel... right above the ND brightness which indicates the GPWS and if you are below the GS.
Do you know which ones?
and... also just noticed that when I start my client I usually run the autostart via windows. Can I save the widefmgs.exe position in any way? my background is set black but with this window right next to an active display it creates an ugly white border even the display remains on front. know what i mean?
Cheers,
Rob
Hi Rob,Quote:
Originally Posted by AirFan
thanks for testing this one. At least we know that this has obviously nothing to do with that specific route. I will continue testing to find out any constellation that might be working.
Stefan
I have done more tests on my VNAV problem for LFMN-LEPA. It looks as if it has something to do with where the aircraft stands when the plan is setup. If I put the plane to EDDW for example, I can plan any route fine, also LFMN-LEPA is showing T/C and T/D. As soon as I put the plane to LFMN, it does not work obviously for any route.
I am using the Aerosoft scenery on FS9, maybe it has something to do with that? Obviously there is no difference whether I stand at any gate or directly at the threshold of a runway. As soon as it's LFMN, it doesn't work.
AirFan, do you use the Aerosoft scenery as well, with FS9? Next thing I will try is temporarily disable the addon scenery and try it that way.
Thanks
Stefan
Quote:
Originally Posted by stefangr
Hi Stefan,
No I dont use this scenery and I use FSX. However I doubt that it's addon scenery related. Have you tried a different Nav data set? Maybe there is something wrong with this particular airport???
Cheers,
Rob
This is weird since I use LFMN as my default starting point, so almost all tests are made from LFMN...
I really do not know what might go wrong there ?? Try with FS default scenery, who knows...
JL
Hi JL,
Hi JL,Quote:
Originally Posted by jeehell
hm? I could not find it in the SIOC Creator... I dont talk about the overhead GPWS korries. I meant the one on the CPT & FO Main Instrument Panel... right above the ND brightness which indicates the GPWS and if you are below the GS.
Do you now know which korry I mean? And what about the Autoland-korry?
and... also just noticed that when I start my client I usually run the autostarter via autostart in windows. Can I save the widefmgs.exe position in any way? my background is set black but with this window right next to an active display it creates an ugly white border even the display remains on front. know what i mean?
Cheers,
Rob
Ok I see what you mean now. I'll add this one and the autoland one someday, not in next version (too late now).
I'll see what I can do for widefmgs windows.
Regards,
JL
Again some news coming out of my testing...Quote:
Originally Posted by jeehell
It has nothing to do with the addon scenery. I deactivated it, but the problem persits.
It obviously has also nothing to do with the nav data. I installed version 1206 of Navigraph's Level-D data and imported the data into the FMGS, but the problem persits.
And now it's getting really weird. This is what I tested:
1. Started FS9, standing at LFMN. Switched on battery on OVHD, started APU, aligned IRS. In MCDU I entered LFMN/LEPA as origin/destination, aligned IRS in MCDU, added FL300 as CRZ FL, entered 55 as Cost Index, on INIT FUEL PREDICTION pressed F9 to import fuel data from FS. Then I opened F-PLN page and saw that there is no T/C, T/D, Speed Limits, no altitudes etc. Looked like this:
Attachment 6880
2. Within FS I changed airport, switched to EDDW. On MCDU T/C, T/D, Speed Limits etc. were inserted automatically. Of course the data was not accurate since the route was still LFMN/LEPA. Looked like this:
Attachment 6881
3. Within FS I changed airport again, this time to LIMJ. On MCDU T/C, T/D etc disappeared again.
I have done this with several airports. The airports that worked fine were: EDDW, EDDF, LFPG. Airports that didn't work were: LFMN, LIMJ, LIRF, LEBL, GCLP.
What I also noticed that during scenery load on FS, the MCDU inserted T/C, T/D for a short moment, but when scenery load was completed, these lines disappeared again for the airports that did not work.
My config is:
PC1: WinXP, FS9, FMGS Server + Sound module
PC2: Win7, FMGS OVHD, PDF, ND, EWD, MCDU
Maybe anyone has still an idea?
Thanks
Stefan
Still no real clue.
One thing though, the route is best calculated when it has at least a couple waypoints in it, not only DEP/ARR airports.
I did a lot of work on VNAV in next version, it will come out shortly (between today and next week), hopefully it'll correct this issue.
Regards,
JL
I also tried to add waypoints, and the MCDU accepts them but it does not calculate any heights though.
Good news that 26 is nearly on its way, so I will check my issues once the new version is out :-)
Thanks
Stefan