Jump to content

Trying to understand the engine


Recommended Posts

Posted

I am using the TM Warthog controller (Z-axis) as my throttle control. Until recently I was using the locking mechanism of the TM Warthog to bind both left and right throttle together. With the throttles locked together if I throttle all the way back the M-2000 throttle would stop at the engine-idle point.

 

Recently I unlocked them so I only would have to manipulate the right one. Now if I throttle back the engine will cross over the engine-idle point and into to the engine cut-off point. The reason for this is that at the zero position (all the way back) now translates to the M-2000 as the engine cut-off. For some reason this was not happening when I had them both locked together but this does not make sense as the left throttle is not bound to anything at all.

 

In trying to work this out I even got myself into a situation where I could only move the Mirage throttle within the confines of the engine cut-off to the engine-idle point, and no farther.

 

I would also like to mention that I do not have buttons 29 or 30 on the throttle bound to anything (which is what is used on the A-10C to shut off the engines). Not that the M-2000C appears to have anything like this but I thought it might be helpful.

--Maulkin

 

 

Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars

Posted
The reason for this is that at the zero position (all the way back) now translates to the M-2000 as the engine cut-off.
Which version are you using? I tried in 1.5.2 release and Open Alpha 2.01, there is no such thing as engine cut-off when throttle is 0. Did you activate the fuel pumps?

 

If I understand correctly, you only remove the throttle interlock and now you're observing a difference?

Maybe your throttle has an issue, you should check the axis response using the axis tune applet and see if moving (or not) the left throttle makes any difference.

Posted (edited)

I have only tested this using ver 1.5.2. I have also tested the axis out of the sim as well as within using the axis modifiers in the control panel and didn't see any issues.

 

What I found also odd is that it seems to interact with buttons 29/30 even though they are not bound to anything because when I perform a cold start to advance the throttle after rpm's get to 11% I have to put the TM warthog into the idle position (button 29/30) and then take it out of the idle position. This occurs with with the throttle lock engaged or not.

 

With the A-10C module this all behaves normally which tells me the TM Warthog is performing correctly.

Edited by Maulkin

--Maulkin

 

 

Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars

Posted

I'd suggest a DCS repair, none of this seem normal.

I don't use the idle detent at all, here's how I start the engine (I'm not going into details): throttle 0, pumps and vent ON, push ignition. At 11% RPM, push throttle a bit then go back to throttle 0.

 

Did you try that sequence without using the throttle axis at all (i.e. using Num keys)?

Posted (edited)

OK I think I figured it out!

 

Before I had said that buttong 29 and 30 (which represent the engine cutoff on the TM warthog Throttle controller) were not bound to anything but after testing it again I discovered that in fact button 30 (engine cutoff for left engine) was in fact bound to engine shutdown on the M-2000.

 

So what does this mean?

 

My initial condition was that my left and right throttle were unlocked (mechanically) from eachother and I had put the left throttle into the shutdown position just to keep it out of the way while I used the right throttle to control the M-2000 throttel. This means that the engine shutdown command was being sent to the M-2000 *all the time*. This is interpreted by the M-2000 to mean that the full traversal of the M-2000 is opened up. So if I throttled back to far it would traverse into the engine-shutdown region of the M-2000 throttle and cut the engines.

 

I have since rebound engine shutdown from button 30 (left engine shutdown) to button 29 (right engine shutdown) and it is now working more predictably since I use the right throttle to control the M-2000 throttle, but there is one more thing:

 

When you engage engine shutdown, as I said before, it will open up the full traversal of the M-2000 throttle, but only while the engine is in shutdown mode. Once the shutdown is complete it *should* close off the engine shutdown part of the M-2000 throttle traversal and you can restart the engine. But every once in a while I would get stuck in the small margin of throttle traversal on the M-2000 which composed of the engine cutoff. This means I could never start the engines again. I even tried binding the "engine startup" which is by default not bound to anything and sometimes it would boot me out of that engine cutoff region but most times it would do nothing at all. I think it came down to timing. So if this is the case we have a race condition and no one likes those.....

 

My recommendation to Razbam is this:

The M-2000 needs to operate similar to the way the A-10C throttles work.

Edited by Maulkin

--Maulkin

 

 

Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars

Posted

Not sure I understand why you wish to split the throttle. Now you have to take your hand off the right throttle to use the buttons located on the left throttle (Pinky, etc) which is set in the cut off position.

 

It's quite possible I misunderstood something in your original post.

[sIGPIC][/sIGPIC]

i7 10700K OC 5.1GHZ / 500GB SSD & 1TB M:2 & 4TB HDD / MSI Gaming MB / GTX 1080 / 32GB RAM / Win 10 / TrackIR 4 Pro / CH Pedals / TM Warthog

Posted
Not sure I understand why you wish to split the throttle. Now you have to take your hand off the right throttle to use the buttons located on the left throttle (Pinky, etc) which is set in the cut off position.

 

It's quite possible I misunderstood something in your original post.

 

I split the throttle because I don't need the left side for anything. I find with the left side in the shutdown position it is actually easier to access the switch and single button on there. The fact that it was also activating button-30 and shutting down the engine was not intentional so I have moved it to button-29 now. This way if I move the right hand throttle to the shutdown position I will get the desired result, but even with this modification I have seen the above mentioned error condition occur where my traverse would be stuck int the "cutoff" area of the M-2000 throttle and I would be unable to start the engine as a result. But that situation is harder to get into now that I am not accidentally activating it by using button-30

 

Sorry for the confusion and even as I have been trying to describe this I have felt it is very confusing. I have been tempted to make a video to help explain it and I still might need to if I was to raise this a a bug report.

--Maulkin

 

 

Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars

Posted

OK, I see. It's a preference with respect to throttle control since it's a single engine just operate a single throttle lever.

 

Thanks for the clarification.

[sIGPIC][/sIGPIC]

i7 10700K OC 5.1GHZ / 500GB SSD & 1TB M:2 & 4TB HDD / MSI Gaming MB / GTX 1080 / 32GB RAM / Win 10 / TrackIR 4 Pro / CH Pedals / TM Warthog

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...