A320 FMGS B49

Quote:

---

Originally Posted by jeehell

You did not understand what I mean.
I know where the "discrepancy" is, it is a different OpenGL environment. Due to to newer openGL specs, I now have to update to this new environment or all users with recent graphics card may get troubles... I could use the old specs until now, but I think it's time now to move one... Unless everybody is having issues, which does not seem to be the case unfortunately for you...

---

haha Copied that JL :)
I think its time to upgrade the hardware for future updates
Thanks and Happy New Year !

Quote:

---

Originally Posted by Fritz

Have checked the autotrimm checkbox in the skalarki profiler. It wasn't disabled. I updated to B49.1 but the Trimm-wheels still not work. I did not find a checkbox in the FMGS Server Config. Where should it be in 49.1? Does anyone have the same problem with the skalarki TQ?

---

No. I checked my Skalarki TQ and its working with B49.1. I did not changed anything in Skalarki Profiler or FMGS config. Just worked on...

Quote:

---

Originally Posted by capt_pero

...my Skalarki TQ and its working with B49.1. I did not changed anything in Skalarki Profiler or FMGS config. Just worked on...

---

Same here but I own TQ version 2015. So I don't know if there have been any changes within the Profiler / USB Controller since Version 2012.
Regards
René

Thanks to capt_pero and romeow for the feedback.

Strange, because the Windows Update, I had to reinstall the USB driver manually.
In the Skalarki Profiler, IO Test, I can test the trim wheels and there they move.
The driver should probably not be the reason why.
Unfortunately, I do not have the predecessor version of the Skalarki Profiler, because the versions are always overwritten.
The installation file have no versioning. Did not consider this.
I have to go back to B48 then.
Would be a pity, because I like the corteManager4JH.

Hello happy new year:)
...i have a strange problem in my b49. When a start thw asn2016 the fmgs freezes every 3 seg. If i star the fmgs after the asn2016 sometimes is all ok.
i think that is some issue with the injection os weather in fmgs. In wrx folder there is 9 files .dat , and they are allways change. This is normal?
regards
Frederico
'

Yes, I am frustrated with Windows 10 as well. With updates it removes all unsigned drivers. Cockpit Concept drivers are unsigned and has to be reinstalled everytime.

Hello,


Happy new year everybody !! ;)


About Skalarki TQ 2012 issue (I've got one too) :
Il seems not to be a JeeHell B49.1 issue.

I recently made a test with the new Skalarki Profiler 5.0.1460.1000 :
>>> Stepper motor TQ 2012 doesn't work in flight.
>>> I tried to test it in Skalarki Profiler settings : Stepper motor doesn't work.


I just deleted the 5.0.1460.1000 Profiler and went back to 5.0.1440.1000 :
>>> Stepper motor TQ 2012 works in Skalarki Profiler settings.
>>> Not tested in flight yet, will do this in the next hours...


Can you test and confirm (or not) this ?


Regards,
Michel

Hello OmniAtlas,
Same issue with Skalarki drivers...
This is a specific Windows 10 security protection.
You can press SHIFT key when restarting Windows 10.
This will call troubleshooting menu, then you will get a specific menu screen.
With F7 key (with French version but maybe the same with English version), you should be able to deactivate this W10 feature.
I think W10 will keep your settings in memory for the further updates...

Regards,
Michel

Happy new year for all.

Hi Jean Luc,

in Beta 49.1 I have the problem with EGT needles too. I found a solution, first start the fmgs server on a dedicated computer and after this I start the SD and EWD on the MIP-Computer.

But I found another small problem. If the engine mode selector is set to normal the left EGT needle is visible. If I switch to IGN all is OK.

See the two screenshots. But it is not a big problem.

http://www.mycockpit.org/forums/atta...id=12557&stc=1

http://www.mycockpit.org/forums/atta...id=12558&stc=1

I'm testing today your Beta 49.1 with Corte4Jeehell Manger, works perfect!
Great job.

Regards Dieter

Quote:

---

Originally Posted by Mitch95

Hello,

Happy new year everybody !! :wink:

About Skalarki TQ 2012 issue (I've got one too) :
Il seems not to be a JeeHell B49.1 issue.

I recently made a test with the new Skalarki Profiler 5.0.1460.1000 :
>>> Stepper motor TQ 2012 doesn't work in flight.
>>> I tried to test it in Skalarki Profiler settings : Stepper motor doesn't work.

I just deleted the 5.0.1460.1000 Profiler and went back to 5.0.1440.1000 :
>>> Stepper motor TQ 2012 works in Skalarki Profiler settings.
>>> Not tested in flight yet, will do this in the next hours...


Can you test and confirm (or not) this ?


Regards,
Michel

---

Hello Michel,

I can confirm this. With version 5.0.1440.1000 the trim wheels works during the flight. Not with 5.0.1460.1000. This proves that it is not caused by JeeHell FMGS B49.1. I have also noticed that in version 5.0.1440.1000 the communication with WideFS is not working properly.

http://www.mycockpit.org/forums/atta...id=12559&stc=1
WideFS is necessary for the profiler if the Skalarki hardware is connected to a dedicated computer.
In version 5.0.1440.1000, the thrust does not go to idle when set the lever to idle on landing. With version 5.0.1460.1000 WideFS connects correctly and the thrust returned to idle.
Finally, I know the cause of my issue, which I have had for several weeks. But since not many use this configuration, it has probably noticed no further. Thanks for your help. I hope that Skalarki fixes the profiler soon.