Mapping helicopter throttle

[Reco]

Hi all

I have the cowansim md500e and I am trying to map the Twist throttle.

I would like to map my z axis to idle stop ring which is "throttle cut" and map a secound range in the same axis to "twist throttle" 

I have mapped the collective, cyclic and pedals but can't seem to map the twist throttle.

For twist throttle, I have been through pitch prop settings with no luck and all the throttle settings control collective pitch Up and down

I have also tried to map  an axis to idle stop ring on the collective which in msfs2020 is throttle cut but unable to find an assignment in fsuipc 

Cheers 

Rhys

[John Dowson]

You need to determine what to use for these controls. To do this, use FSUIPC's logging facilities.
For the Twist Throttle, first try logging Axes Controls, open the logging console window (Log -> Open Console...), then twist the throttle in the VC and see if anything is logged. If so, try assigning to that. if not, try logging Input Events and again twist the throttle in the VC and see if anything is logged, and if so you can use that (I can help you in assigning an axes to an Input Event if you don't know how to do that).
If there are no standard controls or Input Events, the next thing to try is lvars - try listing them (Add-ons -> WASM -> List Lvars) to see if any look appropriate, and if so try setting it (again using the Add-ons ->WASM menu entries) and you need to determine the value range of the lvar. If there is an lvar, I can also help you assign an axis to control this if needed.

8 hours ago, Reco said:

I would like to map my z axis to idle stop ring which is "throttle cut" and map a secound range in the same axis to "twist throttle" 

Not sure I fully understand this...you cannot easily map different ranges of an axis to different controls. To do this, you would need a lua script.
Alternatively, you can just assign your axis to the twist throttle control (whatever that is!) and just send the throttle Cut control in an axis range (using the right-hand side of the axis assignment dialog).

8 hours ago, Reco said:

I have also tried to map  an axis to idle stop ring on the collective which in msfs2020 is throttle cut but unable to find an assignment in fsuipc 

Throttle Cut is a standard control and should be available for button assignments and for axes range assignments. You cannot use this control as an axis assignment as this makes no sense - axis assignments take a parameter (the axis value) but Throttle Cut takes no parameter - it is usually assigned to a button (and usually a detent button on a throttle).

Note I am currently travelling so support will be intermittent until Wednesday next week.

John

[Reco]

Thanks John,

That's given me something to work with.

Cheers

Rhys

[Reco]

Ran log and the  twist grip on the collective  shows as, throttle_incr and throttle _ decr

I have a potentiometer hooked to my collective twist grip so I set that in range 1 to throttle_incr and throttle_decr but that didn't move the twist grip.

In msfs2020 I can set the twist grip which is "set helicopter throttle axis" but not in fsuipc for some reason 

Regards

Rhys

 

[John Dowson]

Very strange that it logs the throttle inc/dec commands - but you shouldn't use these on an axis/potentiometer.
 

6 hours ago, Reco said:

In msfs2020 I can set the twist grip which is "set helicopter throttle axis" but not in fsuipc for some reason 

Not all axis that work when assigned in MSFS work when assigned by 3rd party apps - this is a known issue. For "set helicopter throttle axis", try using Helicopter Throttle Set - these are the specific 'helicopter' controls:

Quote

67526   HELICOPTER_THROTTLE_INC
67527   HELICOPTER_THROTTLE_DEC
67528   AXIS_HELICOPTER_THROTTLE_SET
67529   HELICOPTER_THROTTLE_SET
67530   HELICOPTER_THROTTLE_CUT
67531   HELICOPTER_THROTTLE_FULL
67532   HELICOPTER_THROTTLE1_INC
67533   HELICOPTER_THROTTLE1_DEC
67534   AXIS_HELICOPTER_THROTTLE1_SET
67535   HELICOPTER_THROTTLE1_SET
67536   HELICOPTER_THROTTLE1_CUT
67537   HELICOPTER_THROTTLE1_FULL
67538   HELICOPTER_THROTTLE2_INC
67539   HELICOPTER_THROTTLE2_DEC
67540   AXIS_HELICOPTER_THROTTLE2_SET
67541   HELICOPTER_THROTTLE2_SET
67542   HELICOPTER_THROTTLE2_CUT
67543   HELICOPTER_THROTTLE2_FULL
67544   AXIS_CYCLIC_LATERAL_SET
67545   AXIS_CYCLIC_LONGITUDINAL_SET
67546   CYCLIC_LATERAL_LEFT
67547   CYCLIC_LATERAL_RIGHT
67548   CYCLIC_LONGITUDINAL_DOWN
67549   CYCLIC_LONGITUDINAL_UP

If the standard controls don't work, lcheck for available Input Events and lvars.

It is difficult for me to advise on this as I don't have this aircraft, and all add-on aircraft work in different ways. Maybe try asking on the aircraft developers support forum.

You can also just assign this in MSFS - no problem mixing and matching assignments between FSUIPC and MSFS, as long as you don't have the same button/switch/axis assigned in both.

John

[John Dowson]

By the way, saw this on the flightsim forums (https://forums.flightsimulator.com/t/cowan-simulation-md-500-e-helicopter/572344/15😞

Quote

It cant be used on any of Cowan’s helos as far as I’m aware. He wasn’t able to get the code working correctly. For now, it can only be controlled with the mouse, but he’s hoping to have that addressed in the future.

 

note768×165 18.2 KB

That was quite old (for V1 in Jan 2023, but maybe worth checking if this has been fixed...

John

[Reco]

Thanks John

I have the latest version  which fixed the twist grip. I have set the twist grip via the msfs control options to 

"set helicopter throttle axis"

All other axis and swichers are assigned via fsuipc , but a couple of panel switches which log as an event don't do what they should so I have used msfs for these 

I'll have a look at  "Input Events and lvars."and do some reading on creating them

Once again thank you for your help much appreciated 

Regards

Rhys

[John Dowson]

15 hours ago, Reco said:

I'll have a look at  "Input Events and lvars."and do some reading on creating them

You don't create them - they are either provided or not. Just try listing what is available: Log -> List Input Events and Add-ons->WASM->List Lvars.

For Input Events, you can also log these in real time (Log->Input Events), so set that and then move the twist throttle and see if anything is logged.
The FSUIPC7 main window also indicates how many Input Events and Lvars are available (as well as Presets and Hvars).

15 hours ago, Reco said:

Once again thank you for your help much appreciated 

 No problem - sorry I can't help more, but its difficult not having the aircraft. I can only advise on the various techniques to try, and how to use those if you find anything.

Regards,

John

[Reco]

Hi John

Thank you.

I have a switch on the panel which registers in the log file as 

 1605063  8664 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET

Assigned that to the toggle switch on my cockpit  but doesn't work,

The aircraft pdf  has the assignments in MSFS as 

Start Pump:
The start pump switch is located on the center switch panel.
Search for “fuel p” to find TOGGLE ELECTRIC FUEL PUMPS and map it to any button/switch.

This works only thing is I have to move my toggle switch up and down for it to move the 3d cockpit switch to the up position and do the same action to move the switch down, when I set the action to release.

When I set the action to press the switch on the 3d cockpit will start flickering as if it is trying to move to the opposite position which is weird.

Rhys 

 

[John Dowson]

13 hours ago, Reco said:

I have a switch on the panel which registers in the log file as 

 1605063  8664 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET

Assigned that to the toggle switch on my cockpit  but doesn't work,

If something doesn't work as expected and you want me to help, then please attach your ini and log files (with appropriate logging activated) so that I can check your assignments. Did you also give the parameter as 1? And did you remove the assignment in MSFS if assigning in FSUIPC?

13 hours ago, Reco said:

Start Pump:
The start pump switch is located on the center switch panel.
Search for “fuel p” to find TOGGLE ELECTRIC FUEL PUMPS and map it to any button/switch.

This works only thing is I have to move my toggle switch up and down for it to move the 3d cockpit switch to the up position and do the same action to move the switch down, when I set the action to release.

How does your toggle switch work? Usually they send a button press in one direction, and a release in the other. If this is the case, then you should assign to the toggle on both press and release. However, when assigning to a toggle control for both directions, it is possible for your toggle switch to be out-of-sync with the aircraft, so it is usually better to assign to the to the set control (ELECT_FUEL_PUMP1_SET_ with a parameter of 1 in one direction and 0 in the other. But if that isn't working, use the toggle control.
Note that some toggles switches may send a different button press/release in each direction, in which case toy need to assign to both of the registered buttons.

13 hours ago, Reco said:

When I set the action to press the switch on the 3d cockpit will start flickering as if it is trying to move to the opposite position which is weird.

Not sure why its doing this...it could be due to having dual assignments which are conflicting (i.e. assigned in both MSFS and FSUIPC) or maybe you assigned on FSUIPC with Repeat...

Maybe try posting on the MobiFlight discord server, in the MSFS2020 channel. That is the place for asking for help in defining presets for assignments where standard controls don't work.
I can see there are already some presets defined for the Cowan Sim. H125, but nothing yet for the MD500e.

As I said, I cannot help much with aircraft that I do not have access to - I can only check that FSUIPC is working correctly and that you have assigned correctly - and I need to see you ini and log files for this.

John

[Reco]

Thanks John 

Here is the ini file and log file. Maybe its just a issue with the coding on the aircraft. 

 

Thanks 

Rhys 

FSUIPC7.ini FSUIPC7.log

[John Dowson]

Your files show several things...

First, please be more selective with your logging. You seem yo have activated logging for most things for some reason - only activate logging that you need and remove the rest. So, for button assignments, you usually only need logging for Buttons & Switches and Events. Remove the rest.
It is also far easier if you look at the log in real-time, so you can actually see what is happening when you press a button, To do this, open the logging console (Log->Open Console).

Looking at your files, it also seems that you have changed things while running, so it is difficult to understand some things in your log.
Initially, you had your button assignment to the ELECT_FUEL_PUMP_SET control on repeat:

Quote

...
   155031 14040 Button changed: bRef=0, Joy=0 (A), Btn=13, Pressed
   155031 14040 [Buttons] 31=RA,13,C67550,1
   155031 14040 Repeating flag set: bRef=0, Joy=0, Btn=13 (RepeatDelayCtr=1)
   155031 14040 FS Control Sent: Ctrl=67550, Param=1 ELECT_FUEL_PUMP_SET
...

but you later corrected for this:

Quote

   431609 14040 Button changed: bRef=0, Joy=0 (A), Btn=13, Pressed
   431609 14040 [Buttons] 31=PA,13,C67550,1
   431609 14040 FS Control Sent: Ctrl=67550, Param=1 ELECT_FUEL_PUMP_SET
   431640 14040 *** EVENT: Cntrl= 67550 (0x000107de), Param= 1 (0x00000001) ELECT_FUEL_PUMP_SET
 

but what I don't understand is the following controls being sent:

Quote

   431640 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   431640 14040 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET
   432062 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432109 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432109 14040 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET
   432140 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432172 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432172 14040 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET
   432203 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432234 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432234 14040 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET
   432265 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432297 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432297 14040 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET
   432344 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432359 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432359 14040 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET
   432390 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432422 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432422 14040 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET
   432469 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432500 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432500 14040 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET
   432531 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432562 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432562 14040 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET
   432594 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432625 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432625 14040 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET
   432656 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432687 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432687 14040 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET
   432719 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432750 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432750 14040 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET
   432781 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432812 14040 *** EVENT: Cntrl= 66339 (0x00010323), Param= 0 (0x00000000) TOGGLE_ELECT_FUEL_PUMP
   432812 14040 *** EVENT: Cntrl= 67052 (0x000105ec), Param= 1 (0x00000001) ELECT_FUEL_PUMP1_SET

It is these that are causing the VC switch to flicker so much. Do you have assignments in MSFS or elsewhere? If so, please remove these. Also maybe check any assistance options in MSFS - these could also be interfering if set.

Your ini file also shows a strange entry - remove this:

Quote

[Buttons]
14=ACTION|LUA|ToggleFuelPump << ERROR 9! Line ignored >>
PollInterval=25
ButtonRepeat=20,10
...

For your assignment to button/switch 13:

Quote

31=PA,13,C67550,1     -{ELECT_FUEL_PUMP_SET}-
32=UA,13,C66339,0     -{TOGGLE_ELECT_FUEL_PUMP}-

you are assigning to the set on press but the toggle on release - you should use the set with both, but with a different parameter, i.e.

Quote

31=PA,13,C67550,1     -{ELECT_FUEL_PUMP_SET}-
32=UA,13,C67550,0     -{ELECT_FUEL_PUMP_SET}-

Also, are all your button assignments using switches or sticky buttons? I ask as you are assigning all of them on press and release. This is ok for switches/sticky buttons, but not for standard/momentary buttons (which send a press quickly followed by a release). For such buttons, you would normally only assign on the press only.

For the throttle control, you can try this Input Event:

Quote

   197437 14040 InputEvent value received for 'COWANSIM_ENGINE_Throttle_1' = 0.000000

To use this, you first need to determine the range of that Input Event. To do this, activate logging for Input Events (Log->Input Events), then move the throttle in the VC through its full range, and look at the parameter range for that Input Event.
Then assign your throttle to write its value to an FSUIPC offset, and you need a lua script that monitors the offset (using event.offset) and in the handling function you calibrate the axis value to the input event value range, then send the input event to the FS using ipc.execInputEvent. I can help with such a script if needed, and if you let me know the input event parameter value range as well as your axis value range..

These assignments also look strange:

Quote

27=RA,1,CICOWANSIM_ENGINE_GOV,0.000000     -{Input Event}-
28=UA,0,CICOWANSIM_ENGINE_GOV,0.000000     -{Input Event}-

You have a repeat assignment set on press for button 1, and the same assignment on release on button 0, both sending a 0 parameter....

Also, please wait for 5-10 seconds after aircraft load before trying to do anything - FSUIPC is only fully ready once the following is logged:

Quote

...
   198109 14040 -------------------- Starting everything now ----------------------
   198109 14040 Starting WAPI....
   198109 14040   [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 1.0.4 (WASM version 1.0.5) using connection -1
   198109 14040   [INFO]: Connected to MSFS
...
   205625 10592 Lvars received: 330 L:vars & 0 H:vars now available
   205625 10592 Lvars/Hvars received - checking aircraft autos....
...

John

[Reco]

Hi john,

Thank you very much for that. I will go through and check my assignments again and take a good look at that you have pointed out. 

Cheers 

Rhys

[Reco]

I checked the log menue and saw that all events were checked so I have unticked them so when I re start I only tick what is required.

I have a small issue when I go into axis assignment, when I move the twist grip which is my Y axes fsuipc and msfs crash to desktop. 

Rhys

 

 

 

[John Dowson]

9 hours ago, Reco said:

I have a small issue when I go into axis assignment, when I move the twist grip which is my Y axes fsuipc and msfs crash to desktop. 

That doesn't sound like a small issue! Is this a new issue? You haven't mentioned this before....
Are you sure FSUIPC is crashing? If MSFS CTDs, then FSUIPC detects that MSFS is no longer available and will exit. Check your FSUIPC7.log file - it should show FSUIPC exiting normally.

[Reco]

Hi John

This is a new issue. If I go into the axis calibration menu when I move a control Fsuipc stops but msfs keeps going. 

I was hoping to send you the "input event parameter value range as well as your axis value range.. "so you could write a Lua script.

Just wondering if I should remove and reinstall fsuipc to see if that fixes it 

All the controls are working as per the windows game controller settings  

Rhys 

FSUIPC7.log

[John Dowson]

24 minutes ago, Reco said:

This is a new issue. If I go into the axis calibration menu when I move a control Fsuipc stops but msfs keeps going. 

But previously you said that MSFS crashed...

Does this happen with any axis now? What about buttons? Can you also try with a default aircraft?

26 minutes ago, Reco said:

Just wondering if I should remove and reinstall fsuipc to see if that fixes it 

That won't do anything...
Try rebooting your PC, and first check in a default / Asobo aircraft.
If you get the same issue, exit/kill FSUIPC, then rename your FSUIPC7.ini file and try again  - you will lose all your assignments/settings, but we can add them back later,
If that fixes your issue, show me / attach your renamed FSUIPC7.ini file and try with the cowansim. 

Not sure what is happening - I have never heard of an issue like this before....

[Reco]

Thanks so much for that

Renamed the ini file and with the new one everything is working as it should.

I have attached the renamed ini file

If you are still able to create a script for me I will send the input and parameter details as required. 

Thanks ever so much 

 

Rhys  

FSUIPC7 back up.ini

[Reco]

Hi 

Is this what you require 

Axis range 

-15827  to  4215

I have included a txt file for  parameter value range, hope that is what you are after.

In axis I set the range to COWANSIM_ENGINE_Throttle_1' = 0.000000

When I moved my  hardware twist grip it moved the cockpit 3d twist grip  but  in went straight to full throttle and would not roll back when a twist it back ro idle

 

Rhys 

 

 

parameter value range .txt

[John Dowson]

9 hours ago, Reco said:

Renamed the ini file and with the new one everything is working as it should.

And if you go back to using the renamed ini, do you get the issue again? Also, delete this entry, as it doesn't make much sense:

Quote

4=AU,B,0,0,ICOWANSIM_ENGINE_GOV,0.000000,ICOWANSIM_ENGINE_GOV,0.000000    -{ DIRECT: ThrottleEntering=Input Event, Leaving=Input Event }-

This entry is also strange: (due to the large range specified):

Quote

6=AV,B,5408,16224,ICOWANSIM_ENGINE_Idle_Release_1,0.000000    -{ Entering=Input Event }-

And why are you assigning to the Throttle control if this doesn't work:

Quote

3=AU,256,D,4,0,0,0    -{ DIRECT: Throttle }-

?

7 hours ago, Reco said:

Is this what you require 

Axis range 

-15827  to  4215

Are you sure that this is your axis range? According to your calibration, it is -16197 to 15378.

7 hours ago, Reco said:

I have included a txt file for  parameter value range, hope that is what you are after.

That dies NOT show the value range if the input event - it shows that he throttle is using the standard control Helicopter Throttle1 Set. Why don't you just assign your axis to this control?

7 hours ago, Reco said:

In axis I set the range to COWANSIM_ENGINE_Throttle_1' = 0.000000

What do you mean by this? And why would you want to do this? What is the range of that input event? Do you see it change when logging Input Events (Log -> Input Events) and if so what is the range?
Also, when you make any changes, please attach your updated FSUIPC7.ini.

Sorry, but the more you post the more confused I am on what you are actually trying to achieve. According to the Cowansim documentation, you just need to map the throttle axis (on  left-hand side of axis assignment panel) to Helicopter Throttle1 Set (or maybe Helicopter Throttle Set, Axis Helicopter Throttle Set or Axis Helicopter1 Throttle Set ) and the Idle Stop Ring to Throttle Cut.
I am not sure what an 'Idle Stop Ring' is, but if you want to send this to cut the throttle on the same axis, map this to be sent when entering a range in the right-hand side of the axis assignment panel.

 

[John Dowson]

Also, from the User Manual:

Quote

When flying a helicopter, you use the collective to provide power input and to go up/ down, NOT the throttle. Make sure you map the collective and throttle to a DIFFERENT axis. You do not need to adjust the throttle manually; the governor does that for you automatically. (unless the governor fails or if the breaker is pulled) Simply roll the throttle to maximum, then use the collective to fly. If you do not have a dedicated axis for the throttle, then DO NOT use it, use the mouse instead. The throttle and collective MUST have their own axis.

So throttle should stay at full, and you need to send a throttle cut to release the idle stop ring to come out of idle.

What type/style of axis is your z-axis? Is it a twist-style axis, fixed or spring-loaded, or a lever style axis? How you would assign for this depends on this - if it is a spring-loaded twist axis (which for airplanes you would normally assign to rudder and maybe steering tiller) then you would not want to assign this to an axis control (left-hand side of axis assignment) as this would mean you would have to hold it in maximum position.

But re-reading this thread, you did say that assigning to Helicopter Throttle Set didn't work (did you try Helicopter Throttle1 Set ?), and you have now assigned this in MSFS. Is this still the case? If assigned in MSFS, you should remove the axis assignment in FSUIPC.

I am confused now as to what you have working, and what you still want to assign. Can you let me know what is assigned in MSFS, what you are trying to achieve, and attach your current FSUIPC7.ini file.

Edited October 30 by John Dowson
Further info added