X-Plane 10 plugin - axis mapping

[hexpod]

Hi,

What is the correct axis mapping for a 6 dof platform?

On the attached picture you can see the axis outputs per dof.
In this example I've mapped "Effekt22 - Heading" to the yaw axis and I have made a 360 deg. turn in the simulation.

As you can notice, the yaw graphical data output is not realistic at all and is acting more like a compass input for the gauges.

how to achieve a correct yaw response when applying the force on the rudder pedals?

Thank you in advance for your concern.

[hexpod]

Hi,

Could somebody explain the purpose of pushing the "heading" data through the x-plane plugin to the motion platform??

I don't see any. It might be I am missing something.

I would like to map vertical axis, "yaw" acceleration data on the yaw axis.

The plugin is offering the heading position data which seems to be useless.

Is this a bug?

small video here:

https://vimeo.com/163338053

cheers

[sirnoname]

Heading is a gauge and used for such a instrument.
You use it for a 360° rc servo motor 0-100%.
Wich missing checkbox do give more acceleration info or forces in X-Plane?

[hexpod]

Heading is a gauge and used for such a instrument.
You use it for a 360° rc servo motor 0-100%.
Wich missing checkbox do give more acceleration info or forces in X-Plane?

Maybe the 16, (angular velocities) could be used for the correct yaw behavior.

Additionally, we could imagine to put some special effects for the flaps effect, landing gear, engine RPM vibrations etc.
I would give a try for the 13,14,

it can be, that also the 37,65,66, could be usable.

It is just a guess but it worth a try.

I can do beta - testing.

Please investigate

Best Regards.

[hexpod]

Wich missing checkbox do give more acceleration info or forces in X-Plane?

For the beginning, may I ask to add all 3 from checkbox 16?

Q is pitch P is roll R is yaw

Of course no need to make them appear in the plugin gui


Beside the new yaw accel. cue, roll and pitch accel. can be combined to already existing roll/pitch position for better realism.

I will try to find other useful telemetry later....


Best regards

P.S. everybody very welcome to join the detective team

[hexpod]

COMPLETE TELEMETRY UPDATE REQUEST

Additional accelerations:
checkbox 16 "angular accelerations" -- for realistic platform response.
checkbox 66 "nose and rear "landing gear accelerations" -- for a separate runway effects

Additional effects:
checkbox 13 flaps and speed brake travel position -- for the flaps and speed brake turbulence effect
checkbox 14 landing gear release/retract and wheel brakes -- for a dropdown/retract bump and on runway brake effect
checkbox 66 nose landing gear travel position -- for a landing gear turbulence effect
checkbox 37 engine rpm -- for ignition/shout down shake effect
checkbox 127 stall warning -- for stall shake effect

Best wishes

[sirnoname]

please check the ordering of the raw data. I am not sure about yaw, pitch and roll accelleration ordering.
Use the window as verify. You can run the new executable without X-Sim. Run as admin.

[hexpod]

please check the ordering of the raw data. I am not sure about yaw, pitch and roll accelleration ordering.
Use the window as verify. You can run the new executable without X-Sim. Run as admin.

1.)
Indeed from top to bottom now is yaw pitch roll. should be pitch roll yaw.

2.)
A great instructor station app "Control Pad", while starting, is opening frame rate data from checkbox 0.
This checkbox when checked, is blocking the transmission to the plugin.

3.)
No interferences any more from checkbox 18 - problem solved.

4.)
In some cases, while quitting some efis or autopilot apps, automatic unchecking the data transfer from checkbox 17 is stopping the data transmission to the plugin. it's annoying and confusing.

Could you please make the checkboxes used by your plugin persistent?

Otherwise, thank you! Great progress. it is starting to be exiting

Best regards.

[sirnoname]

Which checkbox? The flight indicator in the plugin window?

[hexpod]

Some apps are automatically activating the checkboxes in x-plane. Some of them while closing are also unchecking them. This can be a source of trouble.
That the case for checkbox 0 and checkbox 17 in x-plane.

You could maybe bypass the checkbox 0 as we don't need the frame rate data for the motion platform.

Making persistent the checkbox 17 would avoid the confusion and the need to activate it manually each time the app is unchecking it.

By making the checkbox persistent, I mean to give the ability to your plugin to reactivate it automatically when the user or other app is trying to close it.

In other words, if possible, some data from checkboxes has to be ignored that is the case with 0 and 18 (needed only for other apps) and some has to be maintained. (persistent) (17)

Maybe for the better reliability, the best would be to maintain all those we are going to use for the platform telemetry.

Best regards