A320 FMGS Compatible with Cockpitsonic FCU/EFIS/AUTOBRAKES/ RADIO.......

[jeehell]

Hi Henrik,

I tried to add the sidesticks to the EHID module.
http://www.jeehell.org/EHIDmodule.dll

Please put that DLL inside your "FMGS\hardware modules" folder.
You need to run FMGS Config first then calibrate your stick in that software just as you would with any ordinary joystick.

Please report your findings.

Regards,
JL

[Jerec]

Hey JL!

Just back from my holidays and i see, that you were busy as a bee in my absence.
I just tested the the new dll and it seems to bee working, although my new Sidestick is in maintanence due to an upset PTT-Button.
But i can report the following things at this time:

1. Brake left and right are both accepted and can be completely calibrated.
2. Rudder Axis is not recognized, although many left/right pushes on the axis (perhaps not yet implemented?)

When i get my stick back (hopefully this week), i will directly report testing results as well. But at this time, many many thanks for your efforts!

btw: are PTT/Takeoverbutton already in?

Regards

Henrik

[jeehell]

Hi,

The rudder input should be working though. Can you give me a log from EHID software as for the sidestick? Maybe the variable ID in EHID SDk is wrong...

The PTT is not supported, as my software does not handle any COM functions.
The AP takeover button should work correctly.

Waiting for your further testing.

JL

[Jerec]

Good morning!

I just created a new logfile with only movement of the rudders, link same as above.
Is perhaps there another point, that could cause no recognition? As i start the CONFIG-tool, at once the brake is assigned to an axis, whereever clicked. Perhaps is there a low threshold of recognition of an axis, which causes, that no other axis is detected?
I hope, that the stick is coming back these days...

Regards

Henrik

[jeehell]

Hello Henrik,

Thanks for the log.
Apparently I was right, their SDK is sometimes wrong.
Try again the dll (same link as above also.

Also, if it does not work, please run the complete software suite (even if no axis are configured).
Then go in the hardwareconnect appliaction (one of the red icons) and turn the loggins function on (only main function and the inputs). And play ariund with rudder/brakes. Then paste the log content here.

regards,
JL

[Jerec]

Good morning!

Sorry, i couldnt answer yesterday after the test, because i were away from the pc. But i could test the new dll...

Just two words: IT WORKS!

Brakes and rudder are now fully configured and can be used in flight. Nice feeling!
I suggest for Cockpitsonicproducts an errorzone round about 500, because of the heavy-duty construction it will be tricky to get the perfect zero point directly. First testflight was successful! Perhaps i can state the results of the stick-testing these days.
Sometimes its a little bit tricky to get the correct axis to the rudder, because the software often sets the brakeaxis to the rudder, because they are very sensitive and Konfig recognizes them as the "to be set axis". Perhaps the sense-threshold in Konfig could be set a little higher? That would cause much less wrong sets.

Nicer work and thanx for your quick help!

Regards Henrik

[jeehell]

Hi,

Ok good to hear that.

Regarding the sensitivity, I cannot do much, the axis should be triggered when you move the axis of more than 30% of the total course, which is already a big movement in theory...

Keep me posted for the stick.
Regards,
JL

[Jerec]

Hi JL,

yesterday i got back my flightstick and today i found the time for testing. Unfortunatly, the stick is not recognized.
So i have created a new logfile (link as above) with only stick-values:

1. Aileron
2. Elevator
3. PTT-button
4. Takeoverbutton

Perhaps there are the same errors in the SDK as for the rudder...

Regards and have a nice holiday!

Henrik

[jeehell]

Hi,

I'm away on holyday until Nov.1st. I'll have a look then.

Regards,
JL

[jeehell]

Hi,

I've changed a few things in the module. Please have a try (still the same link as usual), and keep me posted.

Best regards,
JL