Mouse Macro works on Toggle but not push button

[apetrowsky]

The following mouse macro toggles the autopilot on/off on a Wilco ERJ 145.

[Macros]

Module="ERJ_main.GAU"

1=AP

1.1=RXd4a10*X8bcc

It works perfectly when I assign it to a toggle switch on my Thrustmaster Warthog throttle but when I assign it to a push button it cycles to on/off in a single push. I've tried adding the parameters 11 and 17, I've also tried assigning "do nothing" to the release cycle. Nothing seems to work.

thanks in advance for any insight.

[Pete Dowson]

It works perfectly when I assign it to a toggle switch on my Thrustmaster Warthog throttle but when I assign it to a push button it cycles to on/off in a single push. I've tried adding the parameters 11 and 17, I've also tried assigning "do nothing" to the release cycle. Nothing seems to work.

The only reason I can think for that to be the case is that you are assigning it to both "Press" and "Release". That's the only difference between a toggle switch and a normal button. If you assign to both press and release you'd have to hold the button down (i.e. not release it) to stop the release action occurring as well as the press. A toggle switch only sends one change (press or release) each time you toggle it!

Just delete the assignment to the button release.

Not sure what you mean by "I've also tried assigning "do nothing" to the release cycle" but evidently you did that wrong. And why assign anything at all on release? If nothing is assigned to 'release' then nothing will occur on release.

Pete

[apetrowsky]

Pete

I did not assign actions to both the "Press" and "Release", but I did do more investigation based upon your input. Holding down the button has no effect but if I assign the macro to "Press" it will turn off the autopilot (AP) but pressing again will not turn the AP back on. If I assign the macro to "Release" it will turn the AP on but pressing it again will not turn the AP back off.

Now this is what is very strange - the button I am presently referring to is number 26 on the Throttle (Autopilot Engage/Disengage). If I assign this macro to "Press" on button 21 (L/G WRN), it works perfectly - press it once it turns the AP on, press it again it turns the AP off. I turned off the joystick in FS9 to assure no other actions were tied to button 26, I completely remove FSUPIC, cleaned out the registry, deleted all FSUPIC files in the modules folder, re-installed FSUPIC, - it did not fix the problem. I also verified using the Target script editor that buttons 26 and 21 send exactly the same signals (1 on Press, 0 on release). Is there somewhere else I can look that might be storing old data for button 26? Tony

[Pete Dowson]

I did not assign actions to both the "Press" and "Release", but I did do more investigation based upon your input. Holding down the button has no effect but if I assign the macro to "Press" it will turn off the autopilot (AP) but pressing again will not turn the AP back on. If I assign the macro to "Release" it will turn the AP on but pressing it again will not turn the AP back off.

Now this is what is very strange - the button I am presently referring to is number 26 on the Throttle (Autopilot Engage/Disengage).

Do you have any software drivers installed for this device? If the button is not also assigned in FS (and you say you checked this), it ceretainly sounds like something else you have installed to doing it.

Turn on Button and Event logging options in the FSUIPC Logging tab. This will show precisely what is happening.

Pete

[apetrowsky]

Pete

Problem solved-thought you might like to know the cause. In the ERJ Configuration Utility there is a Tab labeled "Joystick". There is an option under this Tab to assign an "Autopilot quick disconnect button". Button 26 was assigned this function. As a result, it was sending a double signal to the autopilot when Button 26 was pressed. I cleared this assignment and everything works as designed. Thank you for your help, the logging option helped me to look elsewhere for the cause of the problem. This is a great program!

Tony

[Pete Dowson]

Problem solved-thought you might like to know the cause.

Yes, thanks for the explanation.

Pete