YokeM

The fact, that I didn´t even formulate my question understandable is a good indicator to how little I know about your software and P3D. Sorry about that, I will take some more time to learn more about both. I´m trying to operate the controls in the A400M-model without having to klick on them inside of P3D. e.g.: If I click on a button in my software, the parking brake in the simulation should be put to "ON". Or the "Prop pitch 1" should be set to the given parameter.. Etc, etc.... In "offset status" is written: 3110: Operates a facility to send any ‘controls’ to Flight simulator. This works with all versions of FS & CFS. Write all 8 bytes for controls which use a value (axes and all _SET controls), but just 4 will do for ‘button’ types. This is really two 32-bit integers. The first contains the Control number (normally 65536 upwards), as seen in my FS Controls lists. The second integer is used for the parameter, such as the scaled axis value, where this is appropriate. Always write all 8 bytes in one IPC block if a parameter is used, as FSUIPC will fire the control when you write to 3110. Since version 3.40, FSUIPC-added controls (other than the offset ones) can be used via these offsets too. See the Advanced User’s Guide for a current list. So I thought I have to send a 8 byte control, even if I only use a 4 Byte integer as value. Here I´m tying to set the "Prop pitch 1" which I adressed in "n" to the parameter given in "p". This should put them into "Mini" or "RUN" (16383). It seems that I don´t understand structures enough to use them in here. Also what do you mean I should the parameter first? I Thought you need to have the control first, then the parameter. What do you mean with "3114"? If thats an offset, I can´t find it. Can you give me an example to how you would set "Prop pitch 1" to the value of 16383?

Thanks Pete, I can log them now. I tried to change them via my programm, using the offset 3110 but the change didn´t happen in P3D. Is there another way to change these or did I do something wrong? Here is what I did: FsuipcProxy* fsuipcProxy = new FsuipcProxy; int n = 65923, p = -16383; if (!FSUIPC_Write(0x3110, 8, &n, &fsuipcProxy->dwResult)) { cout << "Fehler" << endl; } if (!FSUIPC_Write(0x3110, 8, &p, &fsuipcProxy->dwResult)) { cout << "Fehler" << endl; } FSUIPC_Process(&fsuipcProxy->dwResult);

Hello Pete, sorry for my late reply. Work hit hard before christmas and now for the first time in a while, I´m able to give this little project of mine some time. As far as I can see, the creator of the simualtion model has used xml-gauges. They are inside the model-folder, but packed inside a rar file. I don´t know if P3D uses this packed files or gets them from somewhere else. Is there any way to see how this gauges are changed during the simulation or change them without clicking manualy on a panel in P3D?

Ok thank you. If I understood correctly, every event that can be displayed by the FSUIPC-logger can be addressed be an FSUIPC-offset and I just have to find the right one? Or do I have to use SimConnect to address them? Thank you. Using macros would have been the way to go if I couldn´t adress some of the panels via FSUIPC or SimConnect. If they aren´t shown in the event-logger, does that mean that SimConnect can´t address them too? I didn´t want to use SimConnect since your tool (which uses SimConnect I imagin) made my life really easy in regards of interfacing. I´m not getting any help from the add-on makers right now, but it´s a good idea to ask them.

Hey Pete, thanks for your answer :-) I almost assumed that duo to the "A400M" beeing a add-on aircraft it will be harder to get an interface for it but I still hope it can be addressed through FSUIPC-routines. I know the starting sequence it is as follows for automatic engines startup: 1 - Parking brake on. 2 - Throttle levers 1-2-3-4 Mini. // I´m ingoring this in the logging process. It is for safety reasons and of no real effect on the overall process. 3 - APU START on. 4 - APU MASTER SW. on. 5 - Rotary button ignition. 6 - Engine 1 lever RUN , wait for the stabilization of engine before the starting of engine 2. 7 - Engine 2 lever RUN , wait for the stabilization of engine before the starting of engine 3. 8 - Engine 3 lever RUN , wait for the stabilization of engine before the starting of engine 4. 9 - Engine 4 lever RUN . [Continuation log requested by user] Running inside Prepar3D v2 on Windows 7 Module base=561B0000 415103 LogOptions changed, now 20000000 00000001 // This a loop that happens every second 415119 *** EVENT: Cntrl= 65794 (0x00010102), Param= 0 (0x00000000) PAUSE_ON 415571 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 4 (0x00000004) FUEL_SELECTOR_SET 415571 *** EVENT: Cntrl= 66576 (0x00010410), Param= 5 (0x00000005) FUEL_SELECTOR_4_SET 415571 *** EVENT: Cntrl= 66523 (0x000103db), Param= 2 (0x00000002) FUEL_SELECTOR_2_SET 415571 *** EVENT: Cntrl= 66568 (0x00010408), Param= 3 (0x00000003) FUEL_SELECTOR_3_SET 415571 *** EVENT: Cntrl= 66886 (0x00010546), Param= 0 (0x00000000) BLEED_AIR_SOURCE_CONTROL_SET // loop end 418176 *** EVENT: Cntrl= 65561 (0x00010019), Param= 0 (0x00000000) PAUSE_TOGGLE 419767 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES // Step 1 427801 *** EVENT: Cntrl= 66704 (0x00010490), Param= 0 (0x00000000) APU_STARTER // Step 3 431623 *** EVENT: Cntrl= 66706 (0x00010492), Param= 1 (0x00000001) APU_GENERATOR_SWITCH_TOGGLE // Step 4 // Here should stand an ingnition starter event as described in step 5. The eventlog didn´t show anything like that. Without it the engines won´t start. // Step 6 - 9 435570 *** EVENT: Cntrl= 66300 (0x000102fc), Param= 1 (0x00000001) TOGGLE_STARTER1 438566 *** EVENT: Cntrl= 66301 (0x000102fd), Param= 1 (0x00000001) TOGGLE_STARTER2 439580 *** EVENT: Cntrl= 66302 (0x000102fe), Param= 1 (0x00000001) TOGGLE_STARTER3 441592 *** EVENT: Cntrl= 66494 (0x000103be), Param= 1 (0x00000001) TOGGLE_FUEL_VALVE_ENG1 441592 *** EVENT: Cntrl= 66303 (0x000102ff), Param= 1 (0x00000001) TOGGLE_STARTER4 444587 *** EVENT: Cntrl= 66495 (0x000103bf), Param= 1 (0x00000001) TOGGLE_FUEL_VALVE_ENG2 445617 *** EVENT: Cntrl= 66496 (0x000103c0), Param= 1 (0x00000001) TOGGLE_FUEL_VALVE_ENG3 447629 *** EVENT: Cntrl= 66497 (0x000103c1), Param= 1 (0x00000001) TOGGLE_FUEL_VALVE_ENG4 455429 *** EVENT: Cntrl= 65561 (0x00010019), Param= 0 (0x00000000) PAUSE_TOGGLE

(sorry for the bad english, I´m not a native) Hello Pete, I´m writing a programm which should be able to to handle the contolls and enviromental settings of the cargo A400M from Roland Laborie. FSUIPC is a great interface which makes communication from and to FSX really easy. While I was able to get the enviromental data I was looking for out of FSX, starting the engines is another matter. I can pull the parking brake, but while attemting to set the Engine lever to RUN I came into the problem of simply not finding the right offset or maybe I´m putting the wrong variable into the right offset. As of now I can imagin that I´m doing something wrong somewhere. Whats the right offset for this lever and what variables have to be put into it? regards YokeM