Hi all

I have a toggle switch which I have assigned in msfs2020 to toggle electric fuel pump.

The issue is when I flick the switch up and down it moves the on screen switch to the up postion and to turn it off I have to move the switch twice to turn it off.

I'm trying to get it so I move the switch up it turns on and when I move the switch down it turns it off.

Cheers 

Rhys

Is your hardware switch definitely two position (double trigger)? 

The reason I ask is some might have 2 physical positions but only one actual internal switch. For example the TCA BOEING YOKE has a gear switch that is only one position. It only works with a toggle assignment, gear up and gear down would not work. Toggle gear does. I use it for parking brake and it needs to be moved up and down to trigger this event. 

Hi 

Its a real toggle switch with just up and down action.

Cheers 

Rhys

I had this problem but pretty sure i found a workaround.

 

Lets say i wanted to bind the ON/OFF toggle switch to the parking brake:

Bind both the 'Parking Brake On' and also the 'Parking Brake Off' to the same switch (instead of using 'Toggle Parking Brake').

From there, I changed the action type - one being 'ON PRESS' and the other being 'ON RELEASE'

this has seemed to worked for me. not sure about you. hope this helps

Cheers 

Sam

If it really a single switch like the ones on the Honeycomb controllers,  you will need to tell MSFS to turn on the fuel pump when you press the button down, and to turn it off when you release the button.

Perhaps this is possible with the controller settings in MSFS. If not,  you have to use something like AxisAndOhs which can certainly do that.

32 minutes ago, Allard said:

If it really a single switch like the ones on the Honeycomb controllers,  you will need to tell MSFS to turn on the fuel pump when you press the button down, and to turn it off when you release the button.

Perhaps this is possible with the controller settings in MSFS. If not,  you have to use something like AxisAndOhs which can certainly do that.

I find it easiest to assign these in SPAD, but it’s also what I’ve always used for the Honeycomb Bravo. Almost nothing is defined in my sim controller profile. When I switch to the new sim I’ll probably rebuild new profiles for most again and get it all into SPAD or AAO

Cheers

I have Fsuipc. I have the cowansim md500e which has a couple of switches that I can't  assign via fsuipc but I can Assign via msfs2020.

I have always used fsuipc in fsx 

But find msfs2020 frustrating 

 

Rhys

I think it is working correctly for the way OP assigned the command. Move toggle up and down to turn on.  And move toggle up and down to turn off.

If there is a SET command for that same function (there is a SET command for parking brakes for instance), then assign the SET command instead of the toggle command. And then move the toggle up and its's on and then move the toggle down and it's off. Which is a lot more convenient.

For instance on my Warthog throttle I can just look at the left toggle switch and it's up then the parking brakes are on. If it's down then I know the parking brakes are off. I don't have to wonder while landing if I accidentally have left the parking brakes on. I just look at the switch on the Warthog.

 

But looks like what samslee9 wrote would also work if there is no SET command.

Cheers

Question,  when I assign a switch or axis in the first column  what the secound column used for 

Cheers

Rhys

2 hours ago, Reco01 said:

I have Fsuipc. I have the cowansim md500e which has a couple of switches that I can't  assign via fsuipc but I can Assign via msfs2020.

I'd be surprised if there's any native MSFS control can't be managed with FSUIPC.  What is the MSFS control?

49 minutes ago, Reco01 said:

Question,  when I assign a switch or axis in the first column  what the secound column used for

You can assign a second axis/button/key in that second column.

The second column is to assign that same command to a different button or keyboard key. It's not to assign a different command to the same key.

A different command to the same key is even easier, just create another command assignment, or even ten more, to the same button or key. This is handy to for instance reset the cockpit, outside, slew, and drone views, using the same button for all 4 functions. The reset command for the drone view is "reset drone target offset", which jumps the view back to right behind your plane's tail.

 

Hi

The control I can't bind via fsuipc are 

"Toggle electric fuel pump" 

Fsuipc log shows the event when you activate the switch. 

I asked the question regarding a another assignment for the same aircraft on the fsuipc forum and John Dawson did say that it is possible that even if fsuipc picks up an event there is no guarantee that it will work

It depends on how the coding was done when the aircraft was built 

Cheers

Rhys

On the very first day 2020 was released, I was upset about the lack of ON and OFF controls for so many Toggle commands. Imagine a real life plane with a toggle switch for parking brakes, or spare gas tank drop. There should be an on or off position clearly indicated, not a toggle. Imagine pushing the eject pilot toggle lever thinking you are preventing a sudden departure instead of causing it.

12 hours ago, Reco01 said:

The control I can't bind via fsuipc are 

"Toggle electric fuel pump" 

Fsuipc log shows the event when you activate the switch. 

I asked the question regarding a another assignment for the same aircraft on the fsuipc forum and John Dawson did say that it is possible that even if fsuipc picks up an event there is no guarantee that it will work

It depends on how the coding was done when the aircraft was built

OK...you can always assign the MSFS event to a keypress in the MSFS controls menu, and have FSUIPC send that keypress when the switch is moved.

The drawback with toggles, is that the hardware switch and the virtual (VC) switch position have to be in sync at startup, or the switch position will be opposite of the virtual switch.  'Tis easy enough to move the virtual switch to match up, but a bit kludgey.

If you can read the position of the fuel pump switch (e.g. via a panel LVar), it's better to write a short lua script to read the switch position and only send the toggle if the position matches, and then assign that lua script to the hardware switch state change.