Alhard Horstmann

Hi Pete, now its 11 years ago and I come back to this issue. I run two FlightSim PCs and tried on both to start FSX MPL mode. The LOG file filenames, I will attach, starts with the prefix F3 and F4. The F3 LOG shows the version where FSUIPC stops working, and the F4 LOG shows the version where I can control FSX. The F3 LOG stops after this line : " 101479 Aircraft="Cessna Skyhawk 172SP Paint1" and continues when I stop FSX. The F3 FSUIPC Version is 4.969 and the F4 FSUIPC Version is 4.97 Both systems are WIN7 , both FS are the same FSX version. What is the reason for this different behaviour? How can I troubleshoot? thanks Alhard F3 FSUIPC4_mpl.log F4 FSUIPC4_mpl.log

Hello Pete, good to have you back. How was the trip to the US? Thanks for your advises. Normally I check the versions. Sorry. I think disabling controllers in the sim could solve the problem. Normally I never disable the controllers in the controller disable box. I delete all assignments in the standard FSX controller assignments. I will follow your advises and report again. Alhard

Hi All, I used Joystick Letters and it is still NOT working. What more infos do you need? Please help.

Thanks Stefan, I will try Alhard

Hi Pete, I coded a rotary encoder for trim wheel purpose with FSUIPC like this: --------------------------------- [Buttons] !2=;Änderung wegen TrimWheel 170728 ButtonRepeat=20,10 PollInterval=10 3=CP(+0,6)0,7,Cx43000BC0,xC0010100 ; ELEV_TRIM Sword Decr 4=CP(+0,6)0,7,Cx43000BC0,xC0010100 ; ELEV_TRIM Sword Decr 1=CP(+0,7)0,6,Cx33000BC0,x3FFF0100 ; ELEV_TRIM Sword Incr 2=CP(+0,7)0,6,Cx33000BC0,x3FFF0100 ; ELEV_TRIM Sword Incr -------------------------------- It worked for some days perfect. I could move the trim wheel, sitting on a rotary encoder, and the plane followed the control. Now , when I move the trim wheel, the throttle move back to a 50% position. I am not aware, that I changed anything relevant to this problem. The standard controller assignment in FSX is NOT used. I reloaded my FSX and the C172, and always the same effect: moving trim wheel , moving thottle axis. Here is the log file, see attachment and remarks below: Remarks to the LOG files. From line 97189 on I move the throttle and mixture. Then in line 127032 I connected the USB encoder trim wheel. I moved the trime wheel and suddenly in line 127203 the AXIS_THROTTLE_SET was moved. I disconnected and connected the USB encoder just for test purpose. The behaviour is still there with USB encoder permanent connected. What did I do wrong? What shall I check additionally? Thanks Alhard FSUIPC4.log

Yes there is. I will try. Alhard

Thanks for your quick response. I think, you have a lot to do after vacation time. Yes, I tried a lot with the Simconnect SDK, but as I am not very experienced with C++ programming, I am looking for a quick solution wtih a VB frame program to start with.

Pete, thanks for your hint. I remember I used it some years ago and it works today with FSX also. But I suppose, you are reading the weather info via FSX offsets. I need a program, which reads the current weather info via SimConnect Calls like SimConnect_WeatherRequestObservationAtStation Do you have an idea? best regards Alhard

Hi Pete, I do not want to program myself a little Add-On for reading the current (!) FSX weather. Do you know about a small program , which reads the current METAR out of FSX ? How can I use FSUIPC ? With FS-Interrogate I found a first step. Here I found a thread http://www.fsdeveloper.com/forum/threads/simconnect-weather.5254/ but the add-on is no more available. thanks Alhard

Great thanks, Pete. There is nothing outstanding for now. I really appreciated, as ever, your strong and prompt help and I learned a lot. All the Best! regards Alhard, using FSUIPC since more than 10 years.

Result with P3D. I tested with default Maule. All Door toggle works fine with offset togglebits 15. It doesn't work with TOGGLE_AIRCRAFT_EXIT parameter 15 for all doors, but single doors with par 1,2,3. So for P3D, which is for now not my favourite Sim, I have a solution . regards Alhard

In addition I will test it now on P3D. OK? Alhard

Pete, I missed to send the aircraft.cfg of the Beaver in my virgin PC: [exits] number_of_exits=3 exit.0=0.4 // (0=Main 1=Cargo 2=Emergency) exit.1=0.4 // (0=Main 1=Cargo 2=Emergency) exit.2=0.4 // (0=Main 1=Cargo 2=Emergency) Alhard

Hi Pete, I tested now the behaviour on a very new Windows an FSX installation. I call it my "virgin" test PC. Attached is the complete log file. The behaviour of the Beaver is always still opening/closing ONE door only. My objectiv is, to assign ONE button (individual selected) to toggle Opening/Closing ALL (!) doors. In my Simmer group, which I moderate, all want to have this feature. As FS Control " TOGGLE_AIRCRAFT_EXIT " is unfortunately not working on my 2 systems, I was looking for an alternative = KEYPRESSES. PLease check the log file and please tell me also why always the ATC_MENU_CLOSE function is operated. I checked all button assignments in FSX and in FSUIPC, but I can't find any assignment to this function. Thanks and best regards Alhard Problem Open Doors FSUIPC4.log

Hello Pete, I enabled the logging and attached are my results. There are still some question marks. Please give advise for more tests. Have a pleasant Easter Weekend. Thanks, Alhard Tests Close-Open Doors FSUIPC.txt

Hi Pete , thanks for your extensive explanations. Regarding your activities, don't be forced by my questions to respond shortly and deeply, Just tell me, "I will respond later" . That would be fair. I am retired and I have time. So now I will use the Event logging for my investigations. And yes, I also have some experience with LUA. And yes, I will update. :-) regards Alhard PS: Do you know that Erlangen, where I live, is the twin city of Stoke-on-Trent

Hi Pete, I am sorry , I am stuck My specs: WIN7-64PRO, FSX SP2, FSUIPC Version is 4.965, Aircraft: default C172, I wrote this macro again following your advise [Macros] 1=OpenAllDoors 1.1=W3367=0 PT,0,K69,9 -{Key press: shft+E}- 1.2=W3367=0 PT,0,K49,8 -{Key press: 1}- 1.3=W3367=0 PT,0,K50,8 -{Key press: 2}- But the macro doesn't appear. Then I tried with button "offset byte togglebits" The assignment whether 15 or 3, still opens left door only (and toggles) : My C172 aircraft.cfg shows this [exits] number_of_exits=2 exit.0=0.4 // (0=Main 1=Passenger) exit.1=0.4 // (0=Main 1=Passenger) 26=PT,6,Cx0D003367,x0F -{offset byte togglebits, offset 3367}- or 26=PT,6,Cx0D003367,x03 -{offset byte togglebits, offset 3367}- I tried it also with the FSX default DeHavilland_Beaver_DHC2 with 4 doors [exits] number_of_exits = 3 exit.0 = 0.4 // (0=Main 1=Cargo 2=Emergency) exit.1 = 0.4 // (0=Main 1=Cargo 2=Emergency) exit.2 = 0.4 // (0=Main 1=Cargo 2=Emergency) with the button offset 3367, just one (left) door opens. Sorry and regards Alhard

Great thanks, Pete, That is exactly what I wanted to know. I will shortly reconfigure my FSUIPC and A/C .CFG and then I will report. regards Alhard

Thanks Pete for your quick response. I am sorry, but there are still problems: My FSX SP2, FSUIPC Version is 4.964, Aircraft: default C172, Here are my remarks: 1. There is no "Offset byte clear" , I used for now "Offset byte clrbits" 2. With these button assignments, only left door opens and closes. 6=PT,6,Cx09003367,x0F -{offset byte clrbits, offset 3367}- 7=PT,0,Cx01003367,x0F -{offset byte set, offset 3367}- When I open right door with shE-2 sequence and try to close with button PT,6 then left door opens. 3. I now assigned to button PT,13 the reedited macro "AAOpen" [Macros] 1=OpenAlDoors 1.1=K69,9 -{Key press: shft+E}- 1.2=K49,8 -{Key press: 1}- 1.3=K50,8 -{Key press: 2}- see here: 8=PT,13,CM1:1,0 -{Macro AAOpen: OpenAlDoors: OpenAlDoors: OpenAlDoors}- Now both doors toggle open/close. That's fine. But I need to use the condition "W3367=0" as written before. How can I include this condition in my macro? 4. With your proposal to use the button offset assignment I have to assign at least two buttons for opening and close. As I understood, is the door opening procedure a "toggle" function, so I can easily use the macro assignment. I need the conditional macro, cause some people can open one door only by the "Sh-E" sequence and then I want to close the doors conditionally. I hope I made my problem clear. regards Alhard

Hi Pete, here is another question. My task is to write a macro for one button to open all doors. I read your examples in advanced programmer doc, but I failed. Here is what I wrote first to test my sequence for the button "PT,0" : ; if both doors are open 16=W3367=3 PT,0,K69,9 -{Key press: shft+E}- 17=W3367=3 PT,0,K49,8 -{Key press: 1}- 18=W3367=3 PT,0,K50,8 -{Key press: 2}- ; if both doors are closed 19=W3367=0 PT,0,K69,9 -{Key press: shft+E}- 20=W3367=0 PT,0,K49,8 -{Key press: 1}- 21=W3367=0 PT,0,K50,8 -{Key press: 2}- ; if door 1 is open, then close 22=W3367=1 PT,0,K69,9 -{Key press: shft+E}- 23=W3367=1 PT,0,K49,8 -{Key press: 1}- ; if door 2 is open, then close 24=W3367=2 PT,0,K69,9 -{Key press: shft+E}- 25=W3367=2 PT,0,K50,8 -{Key press: 2}- This sequence works fine. Now I tried to create a macro control like this: Entry in INI file: [MacroFiles] 1=AAOpen 2=AAPM GC Macro file AAOpen: [Macros] 1=OpenAlDoors 1.1 W3367=0 PT,0,K69,9 -{Key press: shft+E}- 1.2 W3367=0 PT,0,K49,8 -{Key press: 1}- 1.3 W3367=0 PT,0,K50,8 -{Key press: 2}- Macro file AAPM GC (just for test purpose) [Macros] 1=MAP Capt=C2999,1 2=NAV Capt=C2999,2 3=VOR Capt=C2999,3 The macro from your example "PM GC" is displayed correctly in the FS controls list. My macro doesn't appear. What is wrong? Please help. Thanks, Alhard

Hi Pete, thanks a lot!! That's exactly what I wanted to know. It would be great, if you would write a "white paper" about all these "secrets". Cause there are a lot of rumors about FS9/FSX interfaces. I think many of my IT collegues and Simmers are interested in these facts as well. But I know, you have other priorities :-) Alhard

Hi Pete, As I am currently very interested in the deeper functionality of FSUIPC and Simconnect, I may ask you, if you know about some documentation like a "white paper" about these topics. My interest, as an IT man, goes to some questions like: How gets FSUIPC access to the FSX data? How gets Simconnect access to FSX data? What protocols are used (TCP IP, named Pipes, Queues, etc) ? What roles are LVARS playing? What roles are the OFFSETS playing? How is the "cooperation" between both access modes ? Thanks, regards Alhard

Yes SPAD is very flexible in programming the Saitek devices. I am now in contact with the developper and since yesterday night, the Offsets for the Airbus are available in Beta version for Betatesters.Btw.: the Forum is here http://www.fsgs.com/forum/ Have a look in the Video to be seen in the forum. and I would be happy if other Wilco Airbus pilots give me a short feedback about their Saitek configuration with FSUIPC and SPAD.neXt. Alhard

Thanks for that clarification, Pete Misunderstanding: I ment SPAD does not yet handle offsets for the Wilco Airbus. I found that term in one of your documents. May be wrong. I ment the function behind an offset.

Hello Pete, I want to connect my Saitek devices to the Wilco/Feelthere Airbusses. This is a wish since years. So fact is for now, there is a pretty good documentation about all (!) the Wilco A320 offsets including the software from Erich Marciano "FSUIPC Exporter". And there is a new software called SPAD.neXt which connects the Saitek devices in a clever way to all FSX standard aircrafts, using FSUIPC functions and also LVARS, no Offsets. Unfortunately the Airbus doesn't provide the offsets as LVARS. And unfortunately the Saitek devices with all their buttons and displays do not appear in FSUIPC. Now my question: can I create LVARS with LUA programming or with other solutions ? I didn' find any example in your FSUIPC SDK. How did you create the tokens for iFLY or PMDG aircrafts ? thanks Alhard