[Solved] Harware Throttle B737 via FSUIPC7

...so I think the example with the throttle lever isn't well-suited for finding this problem via the log.

I'll now look for a different offset, for example, a simple switch that has the same problem (no animation when writing to the offset), e.g., "cutoff". One axis changes the values ​​too quickly, and that makes the log too long and unwieldy.

So I'll document everything again.

Hanspeter

Posted by: @cockbit

↑

so I think the example with the throttle lever isn't well-suited for finding this problem via the log.

Why do you think that? If you correct the logging, as suggested, this will help me understand what is going on, i.e. what your lever is writing to the offset, and the resulting throttle control events. This is what I need to see. As I said, it seems to work here, although controlling both throttle 1 and throttle 2, which I also need to investigate...

Posted by: @cockbit

↑

One axis changes the values ​​too quickly, and that makes the log too long and unwieldy.

Axis changes always result in many events - this is not an issue...you can zip/compress the files if you large to attach as-is.

Posted by: @cockbit

↑

I'll now look for a different offset, for example, a simple switch that has the same problem (no animation when writing to the offset)

Better to stick to this issue at the moment. If you have other issues, such as button/switch animation not working, then that is a separate issue. Generally, this issue (i.e. no VC animation) is due to the fact that you need to use a control for the functionality, and also another control, usually a hvar, lvar or bvar, that controls the animation. It is always a good idea to check for an existing preset (MobiFLight) that is available for the assignment you want to make, and either use that or at least look at the associated calculator code / RPN which will give an insight as to what is needed.

But as I have said, the throttle control and visuals are working here for the B737max in MSFS2024 when throttle assigned to that offset (except for the throttle2 issue), so I don't understand why its not working for you, and cannot comment any further on this issue until I see your assignments (i.e. your FSUIPC7,ini file) and your logs, with the correct logging activated.

John

 Okay, I understand. I'll recreate it properly tomorrow, as you suggested.

Hanspeter

@cockbit I have looked into this further and am perplexed by this! When I assign my axis to offset 0x088C ( GENERAL ENG THROTTLE LEVER POSITION:1), then the assigned lever controls both throttles, and the visuals work. If I assign to offset 0x0924 ( GENERAL ENG THROTTLE LEVER POSITION:2), it sounds like throttle 2 is being applied, but the visuals do not work, which seems to be the issue that you are having.

But this is not an issue with FSUIPC. I don't think you can use those offsets / simvars in this way for this aircraft. This is pretty common in MSFS - many aircraft use newer control mechanisms and the older ways just don't work properly for a lot of aircraft.

There are two ways to control the throttle in the B737 Max via offsets, and both involve using Input Events.

The first method is to assign your levers to write their values to a spare/free FSUIPC offset (as a signed word), then have these offsets monitored by a lua script (which should be auto-ran), which takes these values, calibrates them to the required range, and then sets the throttle input event to these values. I have attached a lua script that does this, using offset 0xA100 and 0xA102 for throttle1 and throttle2 respectively.

The second way is to add these Input Events to offsets via the FSUIPC7.ini file (or your profile ini file if using profiles in separate files), e.g.

[InputEventOffsets]
1=ENGINE_THROTTLE_1=UW0xA030
2=ENGINE_THROTTLE_2=UW0xA032

(N.B. use [InputEventOffsets.xxx], where xxx is the profile name, if using profiles but not in separate files)

You can then assign you levers to write the values directly to those offsets, but then you also need to add the scaling to the assignment entries in your ini file - see the section Additional parameters to scale input axis values on page 42 of the Advanced User guide if you are not familiar with this feature.

If you also want the ability to disconnect the throttle, then this can also be achieved by using lua, although you would have to add this functionality yourself - it wouldn't happen automatically.

Hope that helps.

Regards,

John

P.S. Please inform your customers, both old and new, that they (most probably) require a Commercial license and not a personal one, and they should contact me about this!

Hi John

Thank you so much for your tireless help.

I think your last report made me aware of many possibilities and connections.

I need to explain what this is all about.

I'm eighty-two years young and wanted to upgrade my simulator to 2020/24. That's why I have so many questions. In the meantime, I've found a solution for myself—just for myself.

The solution is: MSFS2020 with B737MAX from Bredok3D and FSUIPC7 (the penultimate version). The latest version no longer implements these valuable assignments of the various axes and buttons (or am I mistaken?).

So, pretty much everything works perfectly.

Last March, I retired from my day job and now just focus on getting my simulator running smoothly.

I've also noticed that many hardware and software manufacturers in this industry have disappeared, leaving only their websites online.

It's the same with my clientele. Basically, I only have (wealthy) private users. But there are about five who fit your "commercial" requirements. I will definitely contact them and inform them accordingly.

Thank you very much for your valuable and expert support.

Greetings from Switzerland,
Hanspeter