Probably a k-event. Look up the command via dev mode, behavior and the specific toggle. See the code.
Sounds like I have to do some study on k-events. Not sure how they work. Furthermore, I entered devs mode and Behaviors, but Im not sure what Im looking for. I find a WIPER_BLADES_TEMPLATE, with what looks like the code running the wipers. There are some (O:) variables (local?), but what exactly am I supposed to look for? I would need to be pushed in the right direction here.
Either one of these should work for your use case.
Aircraft Electrical Events (flightsimulator.com)
Cheers!
2 Likes
For a toggle use a pull chain ceiling mount light switch.
For multiposition flaps get something like this, 3 D print a mount, and add a long handle instead of a knob.
Im not sure what Im doing wrong.
From SPAD Im sending the ELECTRICAL_BUS_TO_CIRCUIT_CONNECTION_TOGGLE event with the params 1, 6 (bus, circuit). But nothing happens. Same with ELECTRICAL_CIRCUIT_TOGGLE and param 6.
Every other event sent is working, so no connection issue.
This is all we are doing:
<Component ID="WIPER_SWITCH" Node="SWITCH_WIPER">
<UseTemplate Name="ASOBO_ELECTRICAL_Switch_Breaker_Template">
<PART_ID>SWITCH_WIPER</PART_ID>
<NODE_ID>SWITCH_WIPER</NODE_ID>
<ANIM_NAME>SWITCH_WIPER</ANIM_NAME>
<INVERT_ANIM>True</INVERT_ANIM>
<ANIMTIP_0>WIPER (OFF)</ANIMTIP_0>
<ANIMTIP_1>WIPER (ON)</ANIMTIP_1>
<WWISE_EVENT_1>wiper_switch_on</WWISE_EVENT_1>
<WWISE_EVENT_2>wiper_switch_off</WWISE_EVENT_2>
<ANIM_LENGTH>100</ANIM_LENGTH>
<ANIM_LAG>750</ANIM_LAG>
<BUS_INDEX>1</BUS_INDEX>
<CIRCUIT_INDEX>6</CIRCUIT_INDEX>
</UseTemplate>
</Component>
Just sending a signal and setting it through the Circuit Breaker
circuit.6 = Type:CIRCUIT_XML:1 #Connections:bus.1 #Power:15, 30, 20.0 #Name:Wipers
circuit.7 = Type:CIRCUIT_XML:2 #Connections:bus.1 #Power:15, 30, 20.0 #Name:Wipers_Park_Motor
3 Likes
I am not sure what to do more. Sending
ELECTRICAL_BUS_TO_CIRCUIT_CONNECTION_TOGGLE with params 1,6 should work?
You ar mentioning circuit 7 along with 6. Should I interact with that one too?
OddâŠ
I havenât flown the Wilga in a while, let me go investigate this personally today and see if I can find a viable solution. If I canât, Iâll recode it to be a LVar for another update.
2 Likes
The Wilga needs a Flintstones livery pack.
2 Likes
Yea it definitely does. I seem to remember @twoseventy270 promising that!! 
1 Like
This is an excellent idea!
Thank you. Very much appreciated. 
Getting a LVAR would be really nice.
Got this one in the mail today. Will rebuild it to become a flaps handle. Removed the spring and got a nice resistance when moving it, without having it rebouncing. But I need to exapand its turning range, and add some micro switches to trigger the flaps stages.
2 Likes
Love it 
(jealous heart 
)
What is it? Touring car / WTCC sim shifter?
It is a handbrake for sim racing.
1 Like
If itâs a handbrake, I guess the lever drives a potentiometer.
In this case, no need to add switches for flaps stages.
Simply bind it to âFlaps Axisâ (NOT the one with â0 to 100%â).
And verify if you need to check the âReverse Axisâ box.
Perhaps youâll need to adjust sensitivity and/or other settings for this axis, but it will be less work than adding switches.
And with switches youâll be limited to X positions defined by the number of switches.
With binding to âFlaps Axisâ it will work with any plane, even with the An-2 wich have eight stages.
Well, yeah. It is using a hall sensor (measuring magnetics). But it is only indicating on half the arms movement range and alot worse now when ive extended the arms movement range. So either I need to find another magnet with the right measure (best solution, but might be hard to find) or I could install four micro controllers (or, ofcourse, a potentiometer like you suggest, might be a better solution like you say) Though, Ill give it a try to find a suitable magnet first.
I didnât suggest installing a potentiometer (especially a bad ordinary standard pot), but to use this one.
A Hall-effect sensor is already a pot, much improved. Itâs perfect.
IMHO, replacing the magnet wonât solve the problem, because the amplitude depends on the reading and restitution made by the electronics behind the sensor.
The first thing to do is to calibrate the lever under Windows, like an ordinary joystick.
If you donât have the full range under Windows, you wonât have it in MSFS.
To do this, run joy.cpl
If for some reason itâs not available, use DIView.exe for Windows calibration.
Available here:
https://heusinkveld.com/download-diview/
After calibration under Windows, restart MSFS and check the movement range (donât forget to re-initialize the settings for this axis).
Ok, you are propably right about the hall sensor. Ill do some tests and see how it behaves.
Regarding lever movement, just by removing the upper part I get double movement range on the lever. And I really want that. So I will propably need to reconfigure or swap the sensor for something else. Else I think ill get large dead zones in the lever range extremes.
Though, Ill take you suggestion and check the range in Windows before starting to rebuild.