JeeHell FMGS forums

Good morning everyone,
As some of you already know, I activated the Skalarki instruments in my home cockpit last week.
Yesterday I wanted to calibrate the TQ, flaps etc. with the FMGS Config file.
When I opened the config file, two messages were displayed.
1. Access Violation at Adress 0085C424 in Module FMGS_Config.exe Write of adress 000000000.
2.Loading SkalarkiO.dll failed at 9.
After the messages, the config file opens, but when I try to calibrate the TQ, it doesn't work.
For example, it is not recognized in the Thrust LVL 1 field when I move it.
Do any of you have an idea what I can do?
Thank you very much!
Best regards Sebastian

I think the error messages are because the P3D is running.
I calibrate everything without the SIM running

Hey, thanks for your message.
That doesn't work for me.
The Skalarki instructions for calibration also say that P3D should run,if I have understood this correctly.
Does anyone else have an idea?
Or has anyone had to fix the error themselves?
Thank you guys
Greetings
Sebastian

I'm not quite sure if you read this correctly.
because when I have P3D running and I start FMGS_Config.exe, I get exactly the same messages as you and P3D goes into pause mode.
If the P3D is not running, I can program the buttons and calibrate everything correctly and when I then start P3D and FMGS (close FMGS_Config.exe) everything is set correctly

Good morning Stephan,
Okay, that's interesting.
I have a PC just for P3D.
All the instruments (Skalarki) are connected to my second PC.
Which programmes did you have open for the calibration?
Only Jeehell on both PCS and everything else really off? So Skalarki Profiler and FSUIPC?
Greetings
Sebastian

In my case, I have the P3D and the Skalarki products on the same PC.
I don't have a throttle from Skalarki - I have one from Thrustmaster.
I only have it FMGS_Config.exe open for calibration, but now I understand your problem - you can't start FSUIPC without P3D...
are you sure you need to calibrate FSUIPC? I do the calibration directly in FMGS_Config.exe and not in FUSIPC
As I wrote, if I open the FMGS_Config.exe while P3D is running, I get your message. This was the case for me right from the start (about 3 years ago)

I've tried all possible variations.
Without activating FSUiPC etc., the error message no longer appears, but the TQ is still not recognized in the FMGS config file. In the profiler it is listed as connected.
I read the skalarki tutorial again. It definitely says that all programs should be connected
It has to be something else!?
Greetings
Sebastian

I assume that you have the skalarki profiler on the p3d computer and have entered the correct IP address for the PC with the throttle.
What happens if you start FMGS_config.exe on the PC with the throttle, calibrate the values ​​there and then close the configurator again, start the p3d and skalarki profiler

Hi,
i don't know how works salarki equipments...
If Joys are connected on other pc than fsmg-config... you must execute Jeehell JOY_REMOTE application for setting and also during flight.
have you set it during setup install?
i hope this help you.
PS: no P3D runing ! sure! during FMGS_CONFIG.
best regards

Hey guys,
thanks for your efforts.
I have spoken to Skalarki support.
The support says it's a problem on the part of Jeehell
Here's another overview of my systems:
I have two Pcs.
One PC only takes care of P3D, the projectors and the sound.
The second PC takes care of all the instruments, sidesticks and monitors.
The P3D PC also runs the Jeehell and Simconnect software.
FSUIPC, Jeehell and Skalarki Profiler are on the second PC.

I believe that all instruments must be active for calibration, and they are, when I open the Skalarki Profiler. In addition, I always start Profile FMGSP&P in Skalarki and then External power on OVHD.
All instruments are from Skalarki (Glareshield, MIP, Pedestal, OVHD),
Except the sidestick is from Thrustmuster. By the way, the sidestick works in the FMGS config file. My mate Micha told me that it works because it doesn't have the dll. file, which is always displayed as an error.
If I don't start some interfaces then the Jeehell Config file opens without an error message, but the instruments still can't be calibrated, because in my opinion the connections to the interfaces are missing.
I just don't know what else to do.
Greetings Sebastian

As I understand it, the Skalarki Profiler belongs on the P3D computer and you enter the IP address of the second computer in the top right of this profiler. You enter the calibration and definition of the keys in the Jeehell Config menu on the second computer and this transfers the values ​​to the Profiler on the P3D computer.
But as I wrote, I have a different configuration and hardware and therefore it is just a "thought experiment"

nach meinem Verständnis, gehört der Skalarki Profiler auf den P3D Rechner und du gibst, in diesem Profiler, oben rechts die IP-Adresse des zweiten Rechner ein. Die Kalibrierung und Defintion der Tasten gibst du im Jeehell Config-Menu auf dem zweiten Rechner ein und dieser überträgt die Werte an den Profiler auf dem P3D-Rechner.
Aber wie geschrieben, ich habe eine andere Konfiguration und Hardware und daher ist es nur ein "Gedankenspiel"

Hello

The calibration in FMGS Config must be done with the rest of my software closed, so do not run starter app for instance.
You can (and probably need to) run P3D during calibration.
FSUIPC requires an additional application if you want to use it remotely, it is called WideFS (not to confuse with wideFMGS).
Marcin is a funny guy, his hardware is hardly plug and play compared to some other manufacturers and his profiler is a total pain in the back for many people. For instance, my software does NOT use FSUIPC, you also don’t need FSUIPC support checked in my software for Skalarki. But his profiler requires FSUIPC link to work, and nobody knows why…

Hello Jean,
Thank you very much for your message.
At this moment I'm sitting in front of my systems in the cockpit.
I followed your advice and only P3D runs on my P3D PC, my second PC only runs WideFS and the skalarki profiler.
The skalarki profiler shows me that everything is connected except the aircraft interface (Hardware Connect -no)
The good news is that when I open the Jeehell Config file I no longer get an error message.
The bad news. I think that because the Aircraft Interface is not connected, the FMGS profile in the skalarki profiler is not loaded and I have no chance of booting up my instruments with the external power.
For example, in the config file my TQ is still not recognized when I move it.
Any idea what's going wrong here?
Greetings Sebastian

did you point your skalarki profiler to the IP of your PC where FMGS Config is running? that should be ideally 127.0.0.1 as it is a local connection (on the same machine). Did you run the profile in skalarki profiler anyway even if hardware connect is not detected?
Sometimes the axis are not auto detected though they are present in the dropdown list for each axis?

Hey Jean,
thank you so much !
It works
The IP address was correct, that wasn't the problem.
BUT: I now know exactly what you mean when people sometimes go mad with the Skalarki Profiler.
The Aircraft Interface was not connected in the Skalarki Profiler, everything else was connected.
I tried your hint and ran the FMGS profile in the Skalarki profiler, although it didn't connect.
Then I opened the Jeehell config file and the TQ and flaps were recognised when moving.
The SpeedBrakes not yet, but I'll have to analyse that separately.
Thanks again for all your efforts.
Especially because I'm still new, I really appreciate it.
Best regards and have a nice evening!
Sebastian

Hello folks,
I did the full calibration of the TQ yesterday. It worked without any problems.
However, there are difficulties with the flaps and speed brakes:
The flaps are recognised in the FMGS Config file, but as soon as the window for calibrating the individual stages opens, the values do not change or only change occasionally if the flaps are set to ‘0’.
The speed brakes are not recognised at all.
I contacted Skalarki support today and they asked me to check in the profiler whether the values change when the instruments are moved.
The flaps as well as the speed brakes show value changes.
What could I do so that the flaps and speed brakes can be fully calibrated in the FMGS config file?
Thank you Guys.
Best Regards
Sebastian

did you put a non zero error zone, and not too big either? try with 5% at first.
Also try to find the axis manually for teh spoilers, maybe the detected range is not enough for auto detection.

Hello Sebastian
Did you install the FLAPS panel and SPOILER panel software when installing FMGS and are they open?
Then you would have to close them - I had a similar problem and JeanLuc wrote this to me

Good morning everyone,
Thank you very much for your messages.
@ JL - I have tried the 5% on the flaps. Unfortunately the values still don't change, except sometimes in the 0-1 level range.
I have also increased the percentage in small steps, even then nothing changes.
What exactly do you mean by ‘Find the axle manually for the spoilers?
Do you have any other idea what the problem could be?

@Balu69 - I have no programmes open during calibration, except P3D, Skalarki Profiler, FS WIDE and Jeehell Config file.

Greetings
Sebastian

The axis are listed in a drop-down menu, so you can try each axis individually (select them, then click calibrate to check if it's the right axis).

Hey JL,
thanks for your message.
I have tried it this way.
When I select the axis for the flaps in the drop down I get to the detailed menu for the calibration. No values change in the individual levels when moving the flaps.
For the speed brakes, I cannot select an axis at all in the drop-down menu. In the drop-down menu I can only find instruments that have already been calibrated, such as the sidestick C/S and the TQ.
Accordingly, flaps and speed brakes unfortunately do not yet work.
Greetings
Sebastian

out of curiosity, have you tried moving the spoiler levers when calibrating the flaps?
idf that does no make a difference, the problem is on skalarki side.