DaveSCUSA

Thank you John, I guess I ignore the calc code error. I will test each switch in detail and provide you details. Thank you for your time. I have, in some cases, reassigned the keys with the UI. Is the Air Manager information valuable?

Hello John again, I understand the effort you have to make to analyze these items. Highly appreciated. As I ama retired systems engineer, I am most disappointed in myselfI can't seem to move ahead. I have spent six months trying to get all these buttons and keys to work with the C510 in my home built cockpit (the Diamond DA62 seems to work fine). I use Air Manager as a contributor created the full C510 cockpit using Simconnect. I had several [ERROR]: Error setting Client Data Calculator Code entries in the FSUIPC7 log. One was 51922 [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '1 (>K:MASTER_BATTERY_OFF) 0 (>A:ELECTRICAL MASTER BATTERY, bool)'. I removed the variable and will test this afternoon. The SDK says the battery variable can be set but it's the only item I can see that may be in error. However, I also received this error: 52141 [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '0 (>K:ELECT_FUEL_PUMP1_SET)' and can't understand why the error as the SDK description shows the event is correct. 1. Can you describe what these errors mean? They happen during the loading of MSFS 2. Canu you help with the Pump Set error. 3. I also pulling my hair out (I am bald) with buttons/keys working or not working (not the same button/key working and then not working). The key master battery works and shows in the cockpit but the avionics switch doesn't. The code between the two is shown in Air Manager Lua (Not too different in concept from FSUIPC7). I just use Air Manager as a test tool when I'm starting from cold and in the landing view (outside the cockpit. The code for the battery and avionics are (using Simconnect): --BATTERY function callback_batt(position) if position == 0 then switch_set_position(sw_batt, 1) fs2020_event("MASTER_BATTERY_ON") elseif position == 1 then switch_set_position(sw_batt, 0) fs2020_event("MASTER_BATTERY_OFF") end end sw_batt = switch_add("sw_big_rd_middle.png", "sw_big_rd_up.png", 180, 58, 45, 119, callback_batt) function ss_batt(batt_on) if batt_on then switch_set_position(sw_batt, 1) else switch_set_position(sw_batt, 0) end end fs2020_variable_subscribe("ELECTRICAL MASTER BATTERY", "Bool", ss_batt) --AVIONICS function callback_avion(position) if position == 0 then switch_set_position(sw_avion, 1) fs2020_event("AVIONICS_MASTER_SET", 1) elseif position == 1 then switch_set_position(sw_avion, 0) fs2020_event("AVIONICS_MASTER_SET", 0) end end sw_avion = switch_add("sw_big_dwn.png", "sw_big_up.png", 382, 59, 45, 114, callback_avion) function ss_avion(avion_on) if avion_on then switch_set_position(sw_avion, 1) else switch_set_position(sw_avion, 0) end end fs2020_variable_subscribe("AVIONICS MASTER SWITCH", "Bool", ss_avion) FSUIPC7.ini FSUIPC7.log C510.ini myevents.txt

PS - You have stated you didn't have RPN documentation and didn't know where to find. Burried in MSFS documentation. RPN Syntax.pdf

I was referring to your use of the RPN Stacking S0 I0 as in: (L:FSUIPC_C510_Ignition_1, Number) s0 l0 0 > if{ 0 (>L:FSUIPC_C510_Ignition_1) 1 (>B:ENGINE_Ignition_1_Toggle) } Instead of the variable L:FSUIPC_C510_Ignition_1 directly: (L:FSUIPC_C510_Ignition_1, Number) > 0 if{ 0 (>L:FSUIPC_C510_Ignition_1) 1 (>B:ENGINE_Ignition_1_Toggle) }

I execute from "C:\Users\dhsim\FSUIPC7\FSUIPC7.ini". The "C:\Users\dhsim\Desktop\MSFS\FSUIPC7\FSUIPC7.ini" location is a folder shared among 2 PCs to share files. Was writing from memory. It was the Project Magenta button. I revisited the post. I had forgotten the applicability. I would like to ask why is stacking used? Not just using the variables.

Hi John, I'm having a few problems understanding assignments and profiles and how to fix the problems. After an update, I wanted to change the C510 Profile. MSFS wasn't appearing to find the Cockspur C510 Profile and exercising the assignments. I decided to try to start over without reassigning the buttons and keypresses. I took out any reference to the C510 profile in the FSUIPC7.ini and renale the C510.ini file in the Profiles folder. 1. After starting MSFS and an attempt to add a new profile and new Bravo Parking Brake button assignments, the assignments did not ask for a new profile (the profile radio button was pressed). The button assignment screen showed the C510 profile at the top although the profile entry was remove from the FSUIPC7.ini file and the profile .ini file was renamed to TestC510.ini. 2. At the time of assigning buttons, the controls redio button and the preset radio button was grayed out. The PMDG and InputEvent redio buttons were available (I wanted to change the preset assignments). As a further test, I tried reassinging a keypress which had no restriction. Have you added any presets or button assignments for the C510 starter buttons and or the Fuel Valve buttons on the throttles (left and right)? Could you share whatever you have working. I'm having difficulty finding the binding for those switches, a combination of events and inputevents. Another item, please. Can you add a choice to not list the InputEvents in the log when choosing the InputEvent logging of assignments? Thanks FSUIPC7.ini FSUIPC7.log C510.ini

Thanks, I did allow the trojan in the security. I have to disallow it now. I'll try it now.

PS - The confusing thing, I bet for many of us, is that I have the firewall and defender off (too many resources used). I scan at midnight. With all that off, Windows still killed it. ???

Thanks, can you put it at the top like the "Trial License" post? At least it will be seen as a person creates a new topic.

You were right and I was wrong. I found (not easy) your work around and I installed 7.4.11. Thanks. Perhaps you could put the work around in its own post.

Hello John, Like many, I receive a virus message with ver. 3.4. I have windows firewall and defender shut off. The router has a firewall that recognizes my IP address for a legitimate return of a request. My Chrome download still shows a virus with the download. Running Ver 3.4.12 on the server and Ver 3.4.11 on the client. I downloaded the 3.4 executable (FSUIPC7.exe) from the forum. I now receive the following error: 7914593 [ERROR]: **** The installed WASM version is 1.0.2 while the WAPI is expecting WASM version 1.0.3. Please update the WASM module as this may cause issues. Perhaps there isn't an issue with Windows Defender. I am running Windows 11 on my server and Windows 10 on my client and FSUIPC7 on both. The firewall and defender are off on both pcs. The message from the client is: 8729454 [INFO]: **** Starting FSUIPC7 WASM Interface (WAPI) version 1.0.4 (WASM version 1.0.3) using connection -1 VFSUIPC7.log FSUIPC7.log

PS Do all (A:, (K:, (L: entries require a >? Can your recommend a document that explains? I had a tutorial for syntax in FSX gauges, but can't find it. The XML there is fairly straightforward, but the RPN needed explanation which I had. Wonder why MSFS had to make it so difficult to understand

Thanks John, I used the wrong variable. Using ELEVATOR TRIM POSITION, radians instead to down -60 (-10°) to up 60 (10°). Perhaps I'll split the presets with a delay between. I realized after I said it that presets can't manipulate Input Events. Are you going to provide the C510 Input Events / Events you find to the public?

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