Post Calibration Axix Input Value

[Hans Krohn]

Dear Pete,

I am in the process of programing motorized airbrakes for my 737 simulator. I am using an EPIC analogue chanel that I have mapped to "Spoiler" in FSUIPC. All this works fine. Now the question:

For motorized operation, I need to be able to read the Input Value (post calibration) for that axis. I saw in the FSUIPC manual that there are plenty of offsets that provide those values (3328 to 3338), but none refers to the spoiler axis. Did I overlook something? How can I get that value?

Any help is - as always - highly appreciated.

Best regards,

Hans

_______________________________

Visit my 737 simulator homepage at

http://www.hanskrohn.com

_______________________________

[Pete Dowson]

For motorized operation, I need to be able to read the Input Value (post calibration) for that axis. I saw in the FSUIPC manual that there are plenty of offsets that provide those values (3328 to 3338), but none refers to the spoiler axis. Did I overlook something?

Evidently. I used "spoiler" as my search word and soon found offset 3412.

Pete

[Hans Krohn]

Hi Pete,

thanks for the quick answer!

I had searched trough a printed document (of an older version, evaidently). I was away from the hobby for a while - amazing how much has changed in one year!

Best regards,

Hans

[Hans Krohn]

Hi Pete,

me again:

I have my spoiler axis mapped and working in FSUICP, but offset 3412 does not show me any axis movements (in FS Communicator).

I have used offset 332E for the throttle without problems.

Do you have any hint?

Best regards,

Hans

[Pete Dowson]

I have my spoiler axis mapped and working in FSUICP

What does "mapped and working" mean? You assigned it in FSUIPC, direct or via FS controls? OR do you mean you assigned it in FS and just calibrated in FSUIPC?

I have used offset 332E for the throttle without problems.

And this was "mapped" how?

Pete

[Hans Krohn]

What does "mapped and working" mean? You assigned it in FSUIPC, direct or via FS controls? OR do you mean you assigned it in FS and just calibrated in FSUIPC?

Hi Pete,

I do not assign any axis within FS9, only in FSUICP. I even deleted the joystick entries in FS9.cfg. By "mapped" I mean that I assign my analogue axis in FSUICP to the Spoiler Axis (checked the box: via FSUICP, not the one that says "direct to FS". Both the joystick asignment and Joystick calibration windows in FSUICP show input values when I move the lever of my spoiler, and it gives the expected result in FS9 (i.e. raising and lowering the speed brakes).

But within FS Communicator - when I use offset 3412, I don't get any values while moving the axix.

As I said, I used the same method for the throttle, and I can see that it works (i.e. input values showing) within FS Communicator.

Best regards,

Hans

[Pete Dowson]

I do not assign any axis within FS9, only in FSUICP. I even deleted the joystick entries in FS9.cfg. By "mapped" I mean that I assign my analogue axis in FSUICP to the Spoiler Axis (checked the box: via FSUICP, not the one that says "direct to FS". Both the joystick asignment and Joystick calibration windows in FSUICP show input values when I move the lever of my spoiler, and it gives the expected result in FS9 (i.e. raising and lowering the speed brakes).

Okay. I'll check this -- are you disconnecting the axis using the bit in offset 341A? For these new offsets I've a feeling that, for efficiency, I only copy the values here when they are actually needed -- i.e. when they are disconnected so they can be processed before being copied to their normal place.

If you are not disconnecting these axes, can I ask why you are reading these copies rather than the real values (i.e. 0BD0 for spoiler, 088C etc for throttle? The only reason the copies were provided was to allow "fly-by-wire" or fault interference, by manipulating the values between input and application. If you only want the application, why not use the actual values instead of the copies?

If you really need 3412 (etc -- I'm sure all of the added batch, 3412 - 3418, will be programmed in the same way) active all the time I'll look to see how easy it is, but it would be nice to know the reason.

Regards

Pete

[Hans Krohn]

Dear Pete,

no, I am not disconecting the spoiler or throttle axis via offset 341A.

Reason for using 3412: My spoiler lever is motorized. After touchdown, I want the lever to move automatically to the full up position. My understanding is that offset 0BD0 is not (only) controlled by the movement of a joystick axis, but also directly by FS9 - which after touchdown will set the offset to max value. So I need an offset that only shows the value directly from the joystick axis (for position information).

My idea is to let my control program (EPIC+FS Communicator) compare the values of 0BD0 and 3412. If a difference between the two is detected (i.e. lever is in ARM position and FS sets 0BD0 to max. value), a clutch engages and a motor moves the lever to the full down position. This is why I need one offset that tells me where FS9 wants the lever to be and one offset that tells me where the lever actually is at that very moment.

I used this type of programing very succsessfully on my motorized throttle, which beautifully follows inputs from the Autothrottle of the Project Magenta MCP.

I hope my explanation was sufficiently clear... :?

Did I understand correctly that 3412 would produce values if I first disconnect the axis via 341A? If that's true, I could simply include a temporary disconnect in my program (during the time the lever is moved by the motor).

Regards,

Hans

[Pete Dowson]

Reason for using 3412: My spoiler lever is motorized. After touchdown, I want the lever to move automatically to the full up position. My understanding is that offset 0BD0 is not (only) controlled by the movement of a joystick axis, but also directly by FS9 - which after touchdown will set the offset to max value. So I need an offset that only shows the value directly from the joystick axis (for position information).

My idea is to let my control program (EPIC+FS Communicator) compare the values of 0BD0 and 3412. If a difference between the two is detected (i.e. lever is in ARM position and FS sets 0BD0 to max. value), a clutch engages and a motor moves the lever to the full down position. This is why I need one offset that tells me where FS9 wants the lever to be and one offset that tells me where the lever actually is at that very moment.

Oh, Right. I see.

Did I understand correctly that 3412 would produce values if I first disconnect the axis via 341A?

Yes, it certainly worked fine that way when it was tested. I don't use the facility myself.

If that's true, I could simply include a temporary disconnect in my program (during the time the lever is moved by the motor).

Well, okay -- in fact I seem to recall that's the more usual way of effecting motor control of axes in any case. But i'll also take a look at changing those new offsets to behave more like the old ones, too. I don't really remember why I implemented them differently now. ;-)

Regards

Pete

[Hans Krohn]

i'll also take a look at changing those new offsets to behave more like the old ones

Hi Pete,

that is good to hear - it will certainly make my task easier.

When do you think this change might be implemented? And how can I find out about it? My email is cockpit@hanskrohn.com, if you want to drop me a line...

Best regards,

Hans

[Pete Dowson]

i'll also take a look at changing those new offsets to behave more like the old ones

...

that is good to hear - it will certainly make my task easier.

When do you think this change might be implemented? And how can I find out about it? My email is cockpit@hanskrohn.com, if you want to drop me a line...

Sorry, I cannot really undertake to do notifications that way, but the Date in the title of the "Downloads" announcements is always changed when I've uploaded a new increment. So please, just check now and then for the next one -- the change you want WILL be in the next incremental update.

If it is only FS9 you need it for, at present, then I can build the FSUIPC3 increment tomorrow and upload it. For FSX it will have to wait till next week as I am partially through some other serious changes and cannot release an increment so soon. Let me know.

Regards

Pete

[Hans Krohn]

Dear Pete,

still using FS9 only...

I really appreciate your help. Thanks a lot!

Best regards,

Hans

[Pete Dowson]

still using FS9 only...

Okay. I'll upload an update to the "Other Downloads" announcement sometime tomorrow (Wednesday). I'm afraid I won't have time to test this change here, but it is quite straight-forward. Let me know if it is all okay.

Pete

[Hans Krohn]

Dear Pete,

got it. Thanks again!

Testing will most likely be done over the weekend. I will report here on the results.

All the best,

Hans

[Hans Krohn]

Hi Pete,

... could not wait until the weekend! :D

I can confirm that offset 3412 now produces values without disconnecting the spoiler axix via 341A.

Thanks again for your great support!

Best regards,

Hans

[Pete Dowson]

... could not wait until the weekend! :D

I can confirm that offset 3412 now produces values without disconnecting the spoiler axix via 341A.

Good, thanks!

Pete