Assigning switches using Local panel variables (lvars) for the Milviz Bell uh1 redux (FSX)

[John Dowson]

13 hours ago, Reco said:

the throttle now moves in the correct direction but I won't rotate back to  idle 

Activate the logging in the lua script (remove comment characters from 'ipc.log' line) and add offset logging for offset 66D0, then test and show me your FSUIPC4.log & FSUIPC4.ini files. For the test, first move the throttle from idle to full and back again, and then exit FSX/FSUIPC4 before attaching the files.

John

[Reco]

Hi 

Here are the two files, hopefully I have captured the correct data for you

I know you mentioned  invalid button assignments in the dodsim -{}- They are assigned and work. I wonder if it is the event file that I am using that the buttons don't show up like the in Milviz MD530 and the Bell U-1C.

Cheers 

Rhys 

FSUIPC4.1.log FSUIPC4.ini

[John Dowson]

13 hours ago, Reco said:

Here are the two files, hopefully I have captured the correct data for you

No, you did not set the correct logging., You have activated lua debug logging - I did not request this and it is not needed, please remove this. As I said, you just need to uncomment the 'ipc.log' line entry in the BellUH1Throttle.lua file. You also did not add the offset logging, and the log file shows no movement in the throttle (or the lua debug logging is not showing this).

You also forcibly closed the log and started a new one. Please don't do this.

Please set the logging as requested and show me those files again. Please exit FSX/FSUIPC before attaching logs, and do not request a new log file..

John

[Reco]

Hi John

Thank you for your help and please forgive me if I am making things frustrating for you which is not my intention. Between my dyslexia and a ADHD I am as frustrated with  figuring this out as you are as I try to implement your instructions 

here is the Lua script with the ipc,log uncomment out but I just not sure in the text where to add the offset logging for offset 66D0

 

local ThrottleOffset = 0x66D0

function throttleControl(offset, value)
   -- Calibrate value from range -16384 - +16384 to 0-100
  -- NB if the lvar range is fifferent, change this, e.g. if the range is 0-1, use
  --        newValue = (value + 16384) / 32768
  newValue = (16384 - value) / 327.68
  ipc.log("Throttle axis value is " .. value .. " resulting in lvar value " .. newValue)
  
  -- send value to lvar
  ipc.writeLvar("L:UH1_THROTTLE", newValue)
  
end

event.offset(ThrottleOffset, "SD", "throttleControl")

--ipc.log("Milviz Bell uh1 redux ThrottleCollective-handling lua now running")

 

Regards 

Rhys 

[John Dowson]

11 hours ago, Reco said:

I just not sure in the text where to add the offset logging for offset 66D0

Offset logging is done via the right-hand side of the FSUIPC logging tab. However, you don't actually need that as the lua script logging is sufficient, as that will log any offsetchanges.

Please also remove the comment characters from the other ipc.log statement:

11 hours ago, Reco said:

--ipc.log("Milviz Bell uh1 redux ThrottleCollective-handling lua now running")

 

[Reco]

Hi John

Ok here is the latest log file. This one does show throttle axis value and Lvar value which I hope is what you are after

 

Cheers 

Rhys 

FSUIPC4.log

[John Dowson]

Your log shows only one value being logged from your axis. I have no  idea why your axis is not updating offset 66D0 when it is being moved.
We need to determine why your axis is not writing its value to that offset.
For the time being, can you stop that lua from running - just remove it from you [Auto] or profilw-specific [Auto..Bell UH-1C] section, whichever one you are using.
then add offset monitoring to offset 66D0 using the right-hand side of FSUIPC's logging tab, as S32. Then load your aircraft and movr your throttle slowly from idle to full throttle and then back again, exit and attach both your log and ini files.

Strange that this was previously working correctly, but just reversed.

On 11/14/2025 at 11:53 PM, Reco said:

I know you mentioned  invalid button assignments in the dodsim -{}- They are assigned and work. I wonder if it is the event file that I am using that the buttons don't show up like the in Milviz MD530 and the Bell U-1C.

They are probably fine and look to be using FSUIPC-added controls or custom controls. They looked strange to me as there was no comment generated, but maybe FSUIPC4 does not auto-generate comments for such controls, like it does in other versions. I have not used FSUIPC5 / FSX for many years now and forget the differences in this compared to later versions.

John

[Reco]

Hi 

Log file now shows changes. As per the last post I removed [Auto..Bell UH-1C] section but nothing showed up in the log so I reinstated it I did get data 

 

Cheers 

Rhys  

FSUIPC4.ini FSUIPC4.log

[John Dowson]

The usual value range for an axis is -16384 to +16383. The value range for the axis you are using (as show in the log is -16306 to 3000.
So the minimum value (-16306) is ok, resulting in a max thrust (as your axis is reversed) of 88,76%. But the max value (3000) will only result in a minimum thrust value if around 41%.

You can try two things:
1. Try calibrating your axis in windows game controllers to see if you can get the full range for he axis values.
2. If you cannot get the full range of values, just calibrate the script to the range of values your axis produces. So with a range of 16306 to 3000., in the lua script change:

  newValue = (16384 - value) / 327.6

to

  newValue = (3000 - value) / 193.06

 

[Reco]

Hi John

Thank you very much, that worked throttle works as it should 

I appreciate all your help on this topic 

Best wishes 

Rhys