DaveSCUSA

I want to increase/decrease the The elevator trim using the trim wheel on my Bravo. The switches dont seem to have much control thru the MSFS Controls with the wheel. I want to slow down the rate on the down and up switches. I read another post to increment/decremet the trim by 128 bips. I have tried to create two presets (dn & up). Would you please check the syntax for me. Thanks DA62_Elev_Trm_Dn#(A:Elevator Position, number) (>L:Elevator_Angle_Trim, number) (L:Elevator_Angle_Trim, number) 128 - -16383 Min (L:Elevator_Angle_Trim, number) (>A:Elevator Position, number) DA62_Elev_Trm_Up#(A:Elevator Position, number) (>L:Elevator_Angle_Trim, number) (L:Elevator_Angle_Trim, number) 128 + 16383 Max (L:Elevator_Angle_Trim, number) (>A:Elevator Position, number)

Thank you

Hello John, Though all your help, I have been able to get all keypresses for the DA62 to work. Thanks. I found the delay control ( 1152 ) you provide very helpful in controlling Keypresses when MSFS responds too quickly. Is there a Sim Variable that is set? I would like to use it in Presets if I find a command that may need it. Depends on the keypad timing. May I suggest a few items? 1. You would significantly increase the worth of FSUIPC7 for Alpha and Bravo users if you created a proprietary C510 set of presets to be offered in a paid version only. 2. To use the UI to set controls to buttons or keypresses may be enhance for users if the control search (one where the user enter the first few characters) returns the first entry at the top of the pick list. 3. Is there some way that upon start up that there could be a log option that could separate the InputEvent found and InputEvent parameter received lists from the log when a user request logging Input Events? Another words List On/Off. That way, when user debugging, the log is not too large. 4. Keypresses – Is there a way to turn on/off showing keyboard presses while continuing to show buttons & keys from other devices than the keyboard. I am realizing that most of the KEYDOWN and KEYUP entries in the log are keyboard usage to navigate around MSFS. These suggestions are to allow a user to use the log as a debugging tool while providing the ability to show all the data you need to debug FSUIPC. Thanks

Thanks John, You don't have to be so adamant. You have much more knowledge and intimacy with FSUIPC than most of your customers. If we ask dumb questions it's because we haven't a clue how simconnect works, where things are in the documentation or even most of the MSFS functionality. An example is how to read button/key log entries. If there is documentation, we can't find it. Thanks again.

Just asked for input of why there are KEYUP when I haven't pressed any keys.

Beacuse we may not understand or of continued confusion. I am confused why there are so many KEY entries with "136203 .. KeyUp received from FS but not programmed", especially with keypresses that are KEYUP with no key down. Or with keys that are not programmed in a profile. If there is a discussion on debugging (Advanced User guide) other than Lua, I've not found it. Thanks

Thanks John, You don't have to be so adamant. You have much more knowledge and intimacy with FSUIPC than most of your customers. If we ask dumb questions it's because we haven't a clue how simconnect works, where things are in the documentation or even most of the MSFS functionality. An example is how to read button/key log entries. If there is documentation, we can't find it. Cockspur C510 customers with Alpha and Bravo would be highly appreciative to know the bindings. Especially if FSUIPC was the only product to offer bindings. Thanks again.

John, You don't have to be so adamant. You have much more knowledge and intimacy with FSUIPC than most of your customers. If we ask dumb questions it's because we haven't a clue how simconnect works, where things are in the documentation or even most of the MSFS functionality. An example is how to read button/key log entries. If there is documentation, we can't find it. Thanks again.

Thanks again. Will presets be able to include Input Events?

Thanks John, I've done what you suggested. I appoligize for the misunerstanding I had over the Input Event Assignments. Chalk it up to old age. Apparently, one can't compound a keypress. When I use the UI for the Fuel Valve controls (there are 2 On and Off) only the last assignment for a keypress exists in the .ini. I have corrected it manually. When I fly the DA62, only the first keypress works. I have set the Fuel Selector entry in the apron.flt to 0. If I start on the Apron, the keypresses turn the fuel levers on but not off again. If I start on the runway, the fuel levers don't respond (turn off). Are kepresses allowed to have compound .ini entries? Thankfully all othe keypresses work (thanks to you). Perhaps I'll put the fuel off on the rear indent on the throttles in the Bravo. I would switch back to the C510 if there were presets available. Are you going to publish presets for the C510? There are many Alpha and Bravo users that would appreciate it. Thanks again. FSUIPC7.log FSUIPC7.ini myevents.txt DA62.ini

Hi agian John, I'm confused. I followed your advice. I did reconfigure the keypad using Right Ctl, Tab and letter/number to define the keys, 1 thru 12. When I assigned them to presets using the UI, the keys shown as tab+rctl+nn. They were defined in DA62.ini (see attached). However, the event logs show multiple controls executed from the key presses (see FSUIPC7.log attached). For example: 209578 *** EVENT: Cntrl= 67064 (0x000105f8), Param= 0 (0x00000000) ENGINE_MASTER_2_TOGGLE 209656 *** EVENT: Cntrl= 67565 (0x000107ed), Param= 0 (0x00000000) ORNI_BOOST_SET or 226250 *** EVENT: Cntrl= 67007 (0x000105bf), Param= 1 (0x00000001) SET_STARTER1_HELD 226328 *** EVENT: Cntrl= 66178 (0x00010282), Param= 0 (0x00000000) ATC_MENU_7 226422 *** EVENT: Cntrl= 66178 (0x00010282), Param= 0 (0x00000000) ATC_MENU_7 I really don't undeerstand now. Is there a way to use a keypress to toggle using [Key] definitions (without Lua)? An example, to execute preset DA62_RH_Fuel_Control_On with the first push and preset DA62_RH_Fuel_Control_Off with the second push. Again, thanks. DA62.ini FSUIPC7.ini FSUIPC7.log myevents.txt

Because of this, I stopped using the C510. I am using a keypad for the fuel valve, ignition switches and starters. Just now, I got it to work with DA62 presets. Is there a capability to write to an Input Event, I can then put it into a preset? Thanks

1. Easy for you when you are most intimate with FSUIPC. Sonetimes it is confusing between the FSUIPC control Alphabetic description and what is listed in MSFS controls. SPAD.neXt provides the Simevent. 2. My real question was doesn't the Shifts prevent Windows or MSFS from acting on the base key. The N as ralt+rshift+N brings up the Nav Log. 3. My question was is there an ability yet to WRITE an Input Event without using Lua? I have become quite familiar with assigning buttons and keys. 4. As above, it seems that MSFS recognizes the ralt+rshift+N combination as an N. The problem is that MSFS uses too many modifiers itself to find the combination it doesn't use. I thought I read somewhere that FSUIPC will recognize the Tab key and Windows key as modifiers. The don't work when assigning keypresses. 5. This is for output keypresses from FSUIPC. I is there any modifier for input keypresses. Many simmers want to use game keypad (which most send keyboard key combinations) for switches in MSFS. Neither Mobiflight nor spad.next will recognize these devices. Thanks

PS - Write to an Input Event without using Lua.

I stopped using the C510 and am going to fly the Diamond DA62. The C510 was too complicated. I just installed 7.4.11. I have 2 PCs on which I run MSFS. The main server has all the devices. The PC I use for testing has only a Joystick attached. There are several B: events used as well as events with two indices. I have used the SPAD.neXt event monitor (direct simconnect) to view the parameters. Is there a way yet, perhaps with 7.4.11 that one can write to an Input Event? Another item I'm experiencing is using the keypress assignments, I receive some squirrely results I think from windows. If I condigured a buttoon a mini-keypad as ralt+rshift+F1, the windows help pops up. If I configure ralt+rshift+N, a window pops up in MSFS. Aren't the shifts supposed to modify windows or MSFS keys to prevent duplication? In reading KeyboardFocus=Yes or Key Focus FSUIPC it seems these deal with keypresses sent from FSUIPC. In my ignorance, the TrapMSFSkeys entry makes no sense to me. Not sure what TrapMSFSkeys=Yes means. All I want to do is use a keypad that can send keypresses to FSUIPC (e.g. ralt+rshift+N which shows correctly in the Assignment) and only trigger that event.key or [Keys] programming. Thanks John for your time.

I contacted Cockspur and absolutely received no support. Too difficult to find the events, variables. Spend too much time trying to make it work and not flying. I'm removing the C510 and going to the DA62 Mod. It works. Cockspur basically sod it to all the Alpha and Bravo users.

Few of the standard controls work, especially if you want to see the cockpit switches move. Most of that is driven by Lvars or Input Events. An example is the battery. The C510 uses Toggle Master Battery but there is Battery On and Off which doesn't work. Developers should provide a list of simconnect events or at least add their aircraft to MobiFlight or SPAD.neXt.

Yes, I have set a button for each. Doesn't work without the battery.

Thanks I may have. Don't remember. Most of the button programming I did with the UI. I may have changed it manually. Don't think so.

Hi John, still testing. Noticed in your reply, you provided your C510 profile. I saw how you had DontLogThese= included. I also assume the DontLogTheseIE= may be included. [Profile.C510] DontLogThese=65962,66523,65568,67197,66071,67072,66030,67073,67226 DontLogTheseIE=ENGINE_Throttle_1,ENGINE_Throttle_2 1=C510 Cockspur I believe I have made my situation too complicated. Programming in the profiles and Lua event.buttons, event.keypresses, conditions. I'm going to just use C510.ini for input. If I can figure ou the combinations of events, input events and Lvars to drive the C510. Do you use the Alpha and Bravo with your C510. If so, could you show a few entries that work? Specifically, when I turn my Alpha battery switch on - cockpit remains dark. Turn the battery on via Air manager, turns on. AVN PWR doesn't turn on with the Alpha, works with Air Manager. Also, no joy with the Alternators. The Air Manage code for the above is contained in file C510_AM.Lua. Non-working, just to display code. Please can you give me some examples from your setup to help me thru this. Thanks C510.ini FSUIPC7.ini myevents.txt FSUIPC7.log C510_AM.Lua

Thanks John, I became familiar with Air Manager. Their code is in Lua. I use it to test (there is a C510 panel). Variables, Events. I use FSUIPC7 for it's keypress capability. I noticed the DontLogThese in the profile. Got the button/keypress programming to work. Now struggling wit the keypress to Lua. No need to answer this post. I'll start a new topic after further testing. Thanks again

Today I found maybe i messed up as the profiles in the Profiles folder weren't working. Not sure why. I moved the button definitions to the FSUIPC7.ini file outside the profile and seemed to work with some bugs. I'll test more tomorrow. Thanks

Hi John, Sorry I haven't answered. I'm still struggling with communicating with the C510. I changed the communication to button and kepress programming in the profile C510.ini. The entries, for the most part, exercise presets. Nothing seems to work. Can't see a log entry to show that a profile is used. I'll be testing more tomorrow. I'll move the programming back to the FSUIPC7.ini. I moved the switches off the Luas to the profile programming for the Alpha, Bravo and Keypad. As I said, nothing seems to work. The events show in the log. I am also using a C510 panel from Air Manager I downloaded and tested on a tablet. It works fine. I used the same MSFS Events and Variables that AM uses. An example, the battery, AV, Alt1 and Alt2 switches on the Alpha. The AM switches turn the PFD and MFD turns on (also the cockpit animation). The Alpha switches do not. I also turned on the buttons and keys log functions but don't know how to interpret the log entries. I am not near a PC right now (my phone). After I yest tomorrow, I'll send FSUIPC7 files. Thanks

You are right, Cockspur vs. Asobo. Oversight during copy and I changed them. As far as the coding of >K: and >A:, I was using events.txt for examples: PA24_250_Pitot_Heat_Off#1 (>K:PITOT_HEAT_OFF) PA24_250_Pitot_Heat_On#1 (>K:PITOT_HEAT_ON) PA24_250_Primer_Prime#1 (>K:TOGGLE_PRIMER1) Please let me know where and how to use ENGINE_Starter_1<;FLOAT64> or ENGINE_Ignition_1<;FLOAT64>. I know how to assign the input events in the Assignment UI to a keypress but don't see how to use the key to press to on and the second press to off. As I said, I use input techniques by hardware unit. E.g. Honeycomb Alpha switches uses the button assignments to FSUIPC controls. For the keypad, I prefer to use Presets. One to tie one key to other keypresses and, two, to perform (variable) x == if { condition } to know if the previous press was on or off. I find once you use preset, then fs control assignment, then hardcode a keypress in FSUIPC7.ini, one loses track of where a button or keypress is defined and assigned for the hardware units. Where else can one manipulate input events, e.g. add or subtract a value to an input event. The Cockspur C510 input to modify the brightness of the panel light is input event LIGHTING_PANEL_1. The brightness of the Display is input event LIGHTING_POTENTIOMETER_30. Both have values 0 to 100. I have two rotary switches on the keypad left or right rotation. Each click sends a key combination. I want to change the value of the above input events by 10, left - 10, right + 10. Can't figure out how to do it in FSUIPC other than an Lua. Mobiflight and Air Manager both can manipulate input events but can't take keypad/keypress input. FSUIPC does a great job with keypresses but how to manipulate input events. Thanks, John.

PS - I'm not using ATC menu on or off in a preset. I have a button on one throttle handle to toggle the menu. The presets are to send ATC_MENU_0 to 9 commands to MSFS. The above url states that the ATC_MENU_x commands work. If I push button 1 (to send an ATC Menu command) button 2 will send ATC_MENU_0 and clear button 1. If button 2 is pushed and button 1 hasn't been pushed, button 2 will engage the starter for the left engine. Once released, then the starter is shut down. Also, the starter will shut down after 20 seconds or when N1 reaches a certain value.