DaveSCUSA

Thank you

In searching the FSUIPC7 forum, I cannot find where ipcPARAM is set. Searching the internet, found many ipcPARAM discussions, but not where the value in the ipcPARAM is set. Could you explain, please.

You Said: What does this ('functions are executed') mean? I see no need to provide any further documentation, and you don't seem to be looking at the documentation already provided. Start with that before asking for further documentation. Why is the current documentation not sufficient? Cockpit builders have been using FSUIPC for > 15 years with the current documentation... I say you will prpbably bar me from the sire for saying this. Europe has a stronger CANCEL culture than the USA (and we're bad). Have worked allover the world in Asia as well as Eurompe and the USA. European software providers tend to put out products that are not ready (how about MSFS) and have no patience for the user. If this software was free, no one would have a complaint. But you have no idea how many FSUIPC7 users are disatified and end up using SPAD.NeXt or Mobiflight. The only reason I use FSUIPC is for the keypress functions. USA users would have no patience for the quality of documentation. You said to look in the Lua Plug-ins documentation, I certainly will. However, the two items I was looking for from ('functions are executed') was what is the sequence of strategix execution of events from.................................................. I have been using FSUIPC7 long before you took over from your father. So, 15 years is not much. Oh the hell with it, you wouldn't listen anyway. There is no overall view of the documentation other than the file names. Do you expect everyone to memorize the docs? An over view document with subject detail of the information in each documernt or an FSUIPC7 index would be helpful. I quit. If your documentation was so great, whay are there so many basic questions. As I said, if it were free, who would complain.

There is a function and a facility, I believe, that would be most helpful to users who are building a cockpit. Function - The ability to test a variable for "nil" value or empty. To find if LVars have been loaded, I tried testing an LVar for a "nil" or less than one. Obviously there is an Lua ERROR. Or setting a variable to when the LVars and Input Events are loaded. Facility - It would be most useful if there were a document that explained step by step of how all FSUIPC7 functions are executed. When Luas are loaded, when profiles are loaded, when the aircraft is loaded, when the aircraft is ready to fly. It would help some sophisticated Lua programming to know when items are available to use. The following code gets an error. if ipc.getLvarID("L:AS3000_IsLocalVarDefined") == nil or ipc.getLvarID("L:AS3000_IsLocalVarDefined") < 1 then (statements) end 99719 *** LUA Error: C:\FSUIPC7\C700_InitLVars.lua:24: attempt to call field 'getLvarID' (a nil value) Thanks

Thank you again, I've tried a couple of methods (e.g. event.control(67209,"StartLVars") --PANEL_LIGHTS_POWER_SETTING_SET or event.control(67213,"StartLVars") ELECTRICAL_EXECUTE_PROCEDURE) as they are executed after loading the aircraft - didn't work. Can you advise me of a method of executing an Lua function() after the LVars, HVars and Input events are loaded? If I'm on the ground or it's a specific aircraft, I will execute the code I want (I know how to determine ground and aircraft).

I'm fine now as I didn't read or didn't notice one needed to confirm in the keypress assignments. Thanks again.

I normally dont use Confirm. Not needed, aparently, in button assignments but needed in keypress assignments. Thanks

Hello John, I'm not at my PC so I can't "Add Files". But I do have a question if I may. I'm trying to execute an Lua function based on the routine "event.sim". It's coded event.sim(FLIGHTLOAD,"StartLVar"). I want the code to kick off when a flight is started - "Fly Now". The Lua is loaded and stops at "waiting for an event". Is this routine still available and where in the schema does it light off? Thanks

Thanks for your response. Upon assigning a button or key in the assignment UI, FSUIPC7 enters the programming in the FSUIPC7.ini file under a [Buttons] or [Keys] section. I wa talking about the <Entry Number> for each assignment. If memory serves (?????), the number had incremented by 2. Now it seems to increment by 1 starting with 0.

I have several questions and requests: 1. The keypress assignments doesn't retain the profile radio button to the next assignment as does the button0 assignment. When performing numerous assignments for an aircraft, forgetting to select the check can obviously cause issues. Could you carry the profile button forward? 2. When entering the first few letters in the control, preset, input event field, the first occurance appears at the bottom of the window. Could the first occurrence appear at the top of the window? Would save many mouse clicks. 3. The increment of the button or keypress assignments now ncrements by one (1). I seem to remember the entries were incremented by two (2). Could you change the increment to more than 1. 4. Is there a way, other than assigning to an offset, to display the LVar used with an event or input event in the log? Or, a method to select one or more LVars to display their values in the log? Thanks

PS - A question I forgot to ask. Does including an LVar in a preset define the LVar in the Sim as it does in the model behaviors?

Thank you. I have given up on the Mustang. Sometimes the key presses work sometimes they don't. I have switched to the C700 Longitude. The above toggles only work in one direction, turns the valve on but not off with the second push. I understand the above in principle. But could you explain: C700s_ANTI_COLL#(L:LIGHTING_STROBE_1) ! s0 (>L:LIGHTING_STROBE_1) 1 l0 (>K:2:STROBES_SET), I don't understand the role of S0 and I0. What number is set into the >K:2:STROBES_SET? C700s_Elec_Stby_Pwr_On#(A:ELECTRICAL MASTER BATTERY:3, bool) ! if{ 3 (>K:TOGGLE_MASTER_BATTERY) } 0 (>L:XMLVAR_STBYBattery_Test), in this case is it asking if A:ELECTRICAL MASTER BATTERY:3 is not true. These things can get kind of tricky. Thanks

Thanks for all your input, I have it working. M_LH_Fuel_On#0 (>L:switch_fuel_left, bool) (>K:TOGGLE_FUEL_VALVE_ENG1) 1 (>L:C510L_Fuel_1, Enum) M_RH_Fuel_On#0 (>L:switch_fuel_right, bool) (>K:TOGGLE_FUEL_VALVE_ENG2) 1 (>L:C510L_Fuel_2, Enum) M_LH_Fuel_Off#1 (>L:switch_fuel_left, bool) (>K:TOGGLE_FUEL_VALVE_ENG1) 0 (>L:C510L_Fuel_1, Enum) M_RH_Fuel_Off#1 (>L:switch_fuel_right bool) (>K:TOGGLE_FUEL_VALVE_ENG2) 0 (>L:C510L_Fuel_2, Enum)

Not sure what your terminology is for the logging function. In the Log drop down in the UI there is an entry for offsets. Upon opening the window, there are four boxes to enter offsets. I used two spare offsets to attach L:switch_fuel_left and L:switch_fuel_right found in the C510_interior.xml file. Both offsets x66C6 and x66C7 showed in the log as 0 value at flight initialization. When the fuel valve switches were turned on, then off in the cockpit at startup, the only entry shown in the log are two events - TOGGLE_FUEL_VALVE_ENG_1 and TOGGLE_FUEL_VALVE_ENG2. No Input Event is displayed. There are no additional offset log entries. A sample of code from the C510_interior.xml file is <LEFT_SINGLE_CODE>(L:switch_fuel_left, bool) ! (&gt;L:switch_fuel_left, bool) (>K:TOGGLE_FUEL_VALVE_ENG1)</LEFT_SINGLE_CODE>

Thanks, I found 2 LVars in the C510_interior.xml. The names are switch_fuel_left and right. I assigned each to offsets 66C6 and 66C7 and entered them in the offset log. Started the C510, exercised the fuel valves and didn't show any activity except the toggle events.

Thank you.

Thank you, I have succeeded in binding the Alpha and Bravo buttons to the C510 due to your input. In looking at all the posts, I have learned much and have finally used the profiles effectively. There are switchs that have eluded me. They are both the fuel valves in the VC located on the trottle handles. The on/off functions log only 51813 *** EVENT: Cntrl= 66494 (0x000103be), Param= 0 (0x00000000) TOGGLE_FUEL_VALVE_ENG1, 54141 *** EVENT: Cntrl= 66494 (0x000103be), Param= 0 (0x00000000) TOGGLE_FUEL_VALVE_ENG1. No other events, input events or SImvars. I added all "Fuel" LVars to myOffsets.txt with no results. Are there any other methods to discover the items that drive these fuel events? Thank you. myOffsets.txt FSUIPC7.log

OK

Thank you, Please see my answer to this post in the post titled "C510 Button Switch Dilemma". There are files there that demonstrate the issue. The FSUIPC7.ini has log Events and Input Events turned on. May take me a few minutes to reply in that post.

I did reread your posts and ensured I applied as best I could.

Sorry to bother you again. But I am still struggling with the C510 button and switch assignments. Even after reading and applying all the replys you have provided, it seems the binding still don't work. I'm sure it's the aircraft and not FSUIPC7, but I can seem to get a handle on why. I tested the bindings using a simple Mad Catz V.1 Stick. The button assignments are contained in the attached C510.ini. I have attached 3 log files: 1. VC Start FSUIPC7.log, the C510 startup using the virtual cockpit switches 2. VC Shut Down FSUIPC7.log, the C510 shut down sequence using the virtual cockpit switches 3. Joystick Buttons FSUIPC7.log, the C510 startup using the Mad Catz V.1 Stick The events register in the log with the joystick as well as the virtual cockpit. But the joystick events do not start the aircraft. I have a limited number of buttons, so I tried to start only 1 engine with the joustick. I'm not asking you to check my work or assignments, I'm trying to find out why this aircraft does not react to the joystick buttons. Are there other debug options I should be using? If so could you point me to any documentation that will show how? There are no presets in Mobiflight for the C510, prehaps no one has found how to preset what events that willl work. As this is the only business jet to use the G1000 suite I can find, I would really like to find out how to bind this aircrafts controls. The axes work fine. I can fly this aircraft as along as I start on the runway. Thanks for your time, I know it's limited. VC Start FSUIPC7.log VC Shut Down FSUIPC7.log Joystick Buttons FSUIPC7.log FSUIPC7.ini C510.ini

PS - I did add both simvars to offsets. I also added the lights simvars to offsets to avoid bit manipulation. I use offsets to toggle events from mom switches push on and then push off.

Thank you, This was not an initial binding for a keypress.

1. For your information: In attempting to use Input Events with Key programming I followed the documnetation on Page 25. It can also be a Lua plug-in reference: L<file#>:<action> Where the File number refers to the [LuaFiles] list in the INI, and the action is one of these letters: R=Run, K=Kill, S=Set, C=Clear, T=Toggle, D=Debug Alternatively, it can be a preset name or the name of an Input Event, in which case it takes the form: P<PresetName> for presets, and L< Input Event name> for Input Events For Input Events: <Entry number> = <Action><Joy#>,<Btn#>,CI<Input Event Name>,<parameter> 17 I kept getting errors on the line 4=W0AF8<1 220,24,LFUEL_Cutoff_Crossfeed_1,0.000000 -{tab+\|key: Press=Input Event }- I had to use the assignments to find the control should have been "I". 2. Question about MSFS Variable Offsets: The DA62 Mod uses the Fuel Tank Selector to exercise the left and right fuel valves as defined: FUEL TANK SELECTOR:index - Which tank the indexed selector is set to. The index is the selector to check (from 1 to 4), and the return value will be the Fuel Tank Selected. The DA62 uses: FUEL TANK SELECTOR:1 The Left Main is selected (19) FUEL TANK SELECTOR:2 The Right Main is selected (20) In the FSUIPC7 Offsets Status there is listed: 0x0AF8 2 FUEL TANK SELECTOR:1 0x2054 4 TURB ENG TANK SELECTOR:1 0x2154 4 TURB ENG TANK SELECTOR:2-4 0x3880 4 RECIP ENG FUEL TANK SELECTOR:1 0x37C0 4 RECIP ENG FUEL TANK SELECTOR:2-4 There is no FUEL TANK SELECTOR:2. Shouldn't there be SELECTOR:2 thru :4 with offsets listed? I use the offsets to determine if the switch is on or off. The Turb and Recip offsets are not recognized by the DA62. I suppose I could create an offset from the variable, but should npt these offsets be avalable?

Also, having difficulty with offset conditions with keyless programming in the C510.ini. I want to toggle the starter keypress based on its variable.