Pete Dowson

Yes, I see no difference. There's an option for 4 or 6 digit Lat/Lon values. Why did you think there was any difference? And what is the difference between: 1 220516 Time Stamp 2 A validity - A-ok, V-invalid 3 5133.82 current Latitude 4 N North/South 5 00042.24 current Longitude 6 W East/West 7 173.8 Speed in knots 8 231.8 True course 9 130694 Date Stamp 10 004.2 Variation 11 W East/West 12 *70 checksum and: 1 = UTC of position fix 2 = Data status (V=navigation receiver warning) 3 = Latitude of fix 4 = N or S 5 = Longitude of fix 6 = E or W 7 = Speed over ground in knots 8 = Track made good in degrees True 9 = UT date 10 = Magnetic variation degrees (Easterly var. subtracts from true course) 11 = E or W 12 = Checksum Are you seeing something I'm not? Pete

What? Where? No, neither. Sorry, I'm lost. FSUIPC settings are saved in the INI file. They are never "lost". If you want to unplug devices and plug them in differently or in a different order, then you need to use the Joy Letter methods in FSUIPC to identify the devices by name and GUID. Otherwise they will get mixed up. But i've no idea what you mean by "reset" here. I can't begin to guess how you are getting so confused. The GUID is probably the only way of re-identifying a device if it moves. Where do you get all this misunderstanding from?? :sad: Pete

I just checked. FSUIPC4 does provide all of this. What do you think is missing? The last copy of the NMEA specs i used was 3.0. Not sure what's different in 3.01. Pete

All IDENT does is make the transponder send a different signal which causes the ATC blip to go bright or glow longer on screen, so the controller can ID you. If you fly on-line the different programs (FSInn, Ivap and Squawkbox) have their own different ways for you to do this so you'd need to handle it accordingly. if you don't fly on line then there is no consequence. All you might see on the transponder is some longer lighting of the "transmit" light. That's up to you to engineer locally. The on-line programs also need you to tell them "off/standby" or "on/modeC" etc. Pete

Ah, you should have said. Sorry, I do not memorise all of this data and would not recognise if fields were different. The GPS facilities in FSUIPC4 and GPSout date back at least 10 years. No, I can't see that without bringing up the older spec to compare it with. Which fields are added? Hopefully these are at the end? What happens to older programs or devices which don't know about these? I use the GPS facilities with Jeppesen FliteMap and it is still working well with the RMC I send. Yes, please, I'd like such a cable. But what iPad program do I need and why is it not backward compatible? Pete

Yes, of course. generally it is better to use the dialogues as they are designed to make it obvious -- but that doesn't seem to work in your case as you hadn't spotted the dual mixture assignment, the cause of your woes! Well, sorry! I thought i was being very explicit. Look, this was the Mixture problem I clearly highlighted: [Axes] 1=0Y,256,D,13,0,0,0 13=3Z,1,D,6,0,0,0 That's 2 (TWO) separate hardware levers applied to the mixture -- one to "mixture" (the all engine mixture control) and one to "mixture1" (the engine 1 mixture) In case you are still none the wiser, 0Y is the Y axis on device 0 and device 0 is defined in the [joynames] section, thus: 0=Saitek Pro Flight Quadrant 3Z is the Z axis on device 3: 3=Saitek Pro Flight Quadrant Just delete the one you don't want!!! Pete

I've no idea what "NEMA" is, but FSUIPC4's GPS facility already supports the NMEA RMC sentence, as does its predecessor GPSout.DLL. Regards Pete

Sorry, but i don't really know anyone using PFC gear except myself. I am near the NW but I am not mobile (I am an RP sufferer). What are you anticipating will be problematic? There's not much to it all ... providing the hardware is working okay the setting up is mostly just installing. The PFC gear i know about is fairly pre-defined functionality-wise so really needs no configuring. Regards Pete

Do you have a gauge which has all this? Or are you building hardware for this? Because FS itself only has the 4 numbers you can change. No other transponder functions at all. How do you select which of the 4 you are setting? Is it one of those which simply cycles left to right or right to left? Whatever way that works you could certainly easily program that in a small Lua plug-in which puts together the transponder value as you press the numbers and writes the resulting value back to the FS offset for transponder code (a 16 bit value holding the code in Binary-Coded decimal form -- i.e. 0x1234 for code 1234). You can't do it very easily using standard FS controls as they inc/dec each digit -- 8 separate controls. It can be done with those but it would be a real mess. The VFR reset button could be a simple assignment to an FSUIPC Offset Word Set control to the 2-byte transponder offset of 0x1200. (The offset is 0x0354). Regards Pete

This is just the initialisation. didn't you try loading different aircraft? Please do that. Leave that logging enabled, and try loading different aircraft please. Looking at the simple initialisation part you have got: 2777 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) This is where SimConnect responds okay to the opening of the link from FSUIPC. Then FSUIPC makes all its requests for data: 2777 Initialising SimConnect data requests now 2777 FSUIPC Menu entry added 2824 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FLIGHTS\OTHER\FLTSIM.FLT 2824 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR That's the initial Flight loaded, with the Aircreation aerolite. (Did you never create your own default flight at all -- it is rare one ses an installation still using defaults!) Here's the initial value of the aircraft name -- all values start off as zero until filled in by Simconnect. 3058 Monitor IPC:3D00 (AsciiZ) = [0]"" But there's never even a name supplied for the Aerolite! Then it looks like you select a weather theme and an aircraft: 20593 Weather Mode now = Theme 29563 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\FeelThere ERJ145XR v2\erj145frtxr.AIR 81823 Weather Mode now = Custom But still never anything from SimConnect about the aircraft! Can you tell me what is happening for the 102 seconds here? 183848 Sim stopped: average frame rate for last 30 secs = 6.8 fps And this is the inevitable result -- a null (zero) aircraft name: 189729 Aircraft="" Something is seriously wrong with the FSX installation if SimConnect is not supplying such essential data. This is what I get in my log with that otion set: 6453 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 6453 Initialising SimConnect data requests now 6453 FSUIPC Menu entry added 6563 \\LEFT\FSPLANS\738 EGCC Cold and Dark.FLT 6563 \\LEFT\FSX\SimObjects\Airplanes\B737_800\Boeing737-800.AIR That's my default flight loading, before reaching the "fly now" etc selection menu. 6875 Monitor IPC:3D00 (AsciiZ) = [0]"" The aircraft name is not filled in yet, as in your case. I change aircraft via the FS selector: 29907 \\LEFT\FSX\SimObjects\Airplanes\Beech_King_Air_350\Beech_King_Air_350.AIR and then, after it loads and I press "Fly Now", everything kicks off: 45766 System time = 03/07/2012 11:15:51, Simulator time = 11:15:12 (10:15Z) 48500 Aircraft="Beech King Air 350" 48563 Monitor IPC:3D00 (AsciiZ) = [18]"Beech King Air 350" 48563 SimRead: 3D00="TITLE" (TITLE is the name of the variable in SimConnect) STR256: "Beech King Air 350" 60328 Starting everything now ... 61719 Advanced Weather Interface Enabled Those last two lines are the inidication that FSUIPC is happy about its relationship with SimConnect, that everything is working. If those are not occurring in your log, after where you chop it off for your messages, then FSUIPC is actually not doing much at all thereafter. It cannot. I can only think of three ways of proceeding, but first, please re-test but with a few aircraft changes -- also Flights as well. I assume you have somne flights saved? Show me the log please with more going on, AND please ALWAYS close FSX down before getting the Log, so it is a complete log not a fragment. Then there are three things to try (one at a time, of course): 1. Get a SimConnect log too. Please see the FAQ subforum for a thread on how to do this. The files will now be getting quite big, so Zip them up and send to petedowson@btconnect.com. 2. Remove the FSX.CFG file before loading FSX so that it generates a new one. (Just rename the original, don't lose it so you can restore it later). 3. If all that fails try uninstalling and reinstalling the SP2 update (or FSX Acceleration if that's what is installed), in an attempt to repair SimConnect. The other thing that is worrying is how inconsistent the problem appears to be -- you report that it suddenly started doing this, then one day it was okay, but then not. Since the software itself isn't changing this does suggest some problem with the hardware -- maybe it is mis-loading FSX sometimes due to memory or disk problems, or suffering some sort of interference from other software of sufficient privilege, like drivers or virus checkers. How you'd look for and eliminate such things I don't know, i'm afraid. But I'd be very suspicious and might consider a fresh start. Regards Pete

Button assignments and Keypress assignments will use the non-specific settings where not actually overridden by profile-specific settings. However, axis assignments and calibrations are not. The complete set for a profile must either be profile specific or general, not a mix. The reason is sanity. Whereas buttons and keypresses only matter when actually pressed or switched, axes are actively polled and values acted upon all the time. It not only makes no sense polling axes not intended to be used for a specific profile, but the general assignments may conflict with specific ones. It just gets too dodgy and difficult to work out what is going on if you have a mix for always-active controls. The best bet is for you to do the general common axis assignments and calibrate them before assigning profiles, then you can use the settings already made each time before adding others. An alternative is of course editing the INI file, block copying the relevant sections. But this is rarely necessary for axes. Regards Pete

Well, not that this is necessarily directly connected, but there are some very odd calibrations Most of the calibrations look like you've left most of the settings to default rather than followed the recommendations and calibration steps in the User Guide. But these entries look like mistakes:which probably need correcting: [JoystickCalibration] Aileron=-16380,0,0,0 -- ailerons one side, nothing the other? Throttle1=-16384,-16384,-15970,16383 -- no "No Reverse Zone" option set, but idle set at full reverse position Throttle2=-16384,-16384,-15159,16383 -- ditto! [JoystickCalibration.Twin engine turbine] Aileron=-16384,0,0,16383 Elevator=-16380,0,0,16380 Rudder=-16384,0,0,16383 -- no dead central xzone at all on any main controls? Throttle=-16384,16384 -- generic throttle calibrated as well as 4 separate ones!!? Throttle1=-4096,0,0,16384 -- no idle zone on any throttle! Why 4 for a twin engine profile? Throttle2=-4096,0,0,16384 Throttle3=-4096,0,0,16384 Throttle4=-4096,0,0,16384 PropPitch1=-4096,0,0,16384 -- 4 prop pitch controls calibrate, but no neutral (feathered) zone? PropPitch2=-4096,0,0,16384 PropPitch3=-4096,0,0,16384 PropPitch4=-4096,0,0,16384 [JoystickCalibration.Twin engine turboprop] Aileron=-16380,0,0,0 -- again one-sided ailerons? Throttle=-16380,16380 -- generic throttle as well as separate throttles? PropPitch=0,0 -- zero proppitch rasnge? [JoystickCalibration.Single engine jet] Aileron=-16380,0,0,16380 -- All controls with no central zone defined? Elevator=-16380,0,0,16380 Rudder=-16380,0,0,16380 [JoystickCalibration.Twin engine jet] Throttle=-16380,16380 -- Generic throttles as well as separate throttles? Throttle1=-16384,-16384,-16384,16383 Throttle2=-16384,-16384,-15159,16383 [JoystickCalibration.Twin engine piston aircraft] Elevator=0,0,0,0 -- no elevator on these aircraft? Calibrated with no range at all? Throttle=-16380,16380 -- Generic throttle as well as separate throttles? Throttle1=-16380,-512,512,16380/32 Throttle2=-16380,-512,512,16380/32 Mixture1=-16384,1408,1408,16383/32 Mixture2=-16384,-273,-273,16383/32 [JoystickCalibration.Beech King Air 350 Paint1] Throttle=-16380,16380 -- Generic throttle as well as separate throttles? Throttle1=-16384,-16384,-16384,16383 -- no "No Reverse Zone" option set, but idle set at full reverse position Throttle2=-16384,-16384,-15159,16383 -- ditto [/CODE] It is especially worrying when multiple actions are allowed for the same FS control surface. Having the generic all-engine throttle calibrated as well as the separate ones is not outright wrong, but it may give unwanted results if you are not caredful in assignments. Onto assignments now. I'm ignoring everything not Mixture related: [CODE] [Axes] 1=0Y,256,D,13,0,0,0 13=3Z,1,D,6,0,0,0 [/CODE] Aha, I think we found the culprit already! Here you have a Generic all-engine mixture assigned to axis 3Z and an engine 1 mixture assigned to axis 0Y. conflicts will ensue! Your C172, unless you specifically choose the Cessna Skyhawk 172SP Paint4 (which has been assigned to the single engine piston aircraft Profile, which should be okay), then this will suffer. (If you want all C172's in that profile, change the entry in the Profile list to 1=Skyhawk 172, or something similar which will encompass them all, and change "ShortAircraftNameOk=No" to "ShortaircraftNameOk=substring", in the [General] section). Also, i see no P51 listed in any of the Proiles, so this too will use these default assignments, so suffer the same problem. [CODE] [Axes.Twin engine turbine] 6=1V,256,D,6,0,0,0 Ok. [Axes.Single engine piston aircraft] 13=3Z,256,D,6,0,0,0 Ok. [Axes.Single engine jet] 13=3Z,256,D,6,0,0,0 Ok. [Axes.Twin engine jet] 13=3Z,256,D,13,0,0,0 Ok. [Axes.Twin engine piston aircraft] 1=0Y,256,D,13,0,0,0 2=0Z,256,D,14,0,0,0 Ok. [Axes.Beech King Air 350 Paint1] 1=0Y,256,D,14,0,0,0 2=0Z,256,D,14,0,0,0 Two assignments to mixture 2, none to mixture1 [Axes.four engine piston] 7=1V,256,D,6,0,0,0 Ok. [Axes.Twin engine turboprop] 1=0Y,256,D,13,0,0,0 2=0Z,256,D,14,0,0,0 Ok. [/CODE] I think you need to take a little more care when making assignments. Dual assignments will almost always cause conflicts. Regards Pete

Shouldn't matter, but WideClient is now up to version 6.972. WideServer doesn't change much if at all, but WideClient has gone through a lot of updates because of its support for the developing Lua libraries. See the Download Links subforum. Regards Pete

Best to just paste them into a message anyway. I can't see why any of those aircraft titles would upset FSUIPC at all. but something is going wrong, maybe with SimConnect -- which, as I said , is what supplies the aircraft title. Did the FSUIPC log file show the Aircraft="" line again? Have you tried simply reloading the aircraft at all when this happens? There is even a control for it which you can assign. And you could try changing to a different aircraft then back again, in an attempt to determine what on Earth is going on. But first, please go to FSUIPC4's logging tab, and on the right-hand side enter 3D00 in the offset column in the top line, and in the Type column select "AsciiZ" from the drop down list. Below check "normal log" then OK out. This will then log whatever it is SimConnect is providing by way of an aircraft name each time it changes. Show me any logs after you get the problem. Pete

I assume, then, you meant "I do not have FSUIPC registered" rather than "I do not have FSUIPC installed", which seems to contradict all the rest. I cannot reproduce this behaviour here, on FSX, with the current version of FSUIPC4 (4.939), and nothing has changed in this area in FSUIPC4 since the currently supported version was released (4.827 is the oldest still supported). And FSUIPC3 doesn't have a mouse look facility, so I'm really not sure how I can help you. Please state the version of FS (FS9 or FSX, maybe?) and that of FSUIPC. Maybe it's something in an old version? In which case you should either update or remove FSUIPC. Regards Pete

Well, the symptoms match the missing aircraft name. Did you check the ERJ's Aircraft.CFG file as I suggested? That's where the aircfraft names are -- in the "title=" lines i think. If you can't figure it out show me that file. Well, the software isn't changing by itself, so either your files are changing or you have faulty disk and/or memory. [LATER] I've just done some testing with an Aircraft.CFG file containing an empty "title" parameter, and I cannot see how such an aircraft can be loaded because the FS selection of the aircraft is based on that title. So I'm worried that the culprit CFG file has got some unusual title whih isn't being read correctly by either SimConnect (which is where FSUIPC gets it) or by FSUIPC itself. So, please could you shown me the relevant Aircraft CFG file? Thanks Regards Pete

Sounds like dual assignment. Check that it hasn't become reassigned in FS. If you've disabled all controllers in FS, show me your FSUIPC INI file from the Modules folder. Als check that you are using an up to date supported version of FSUIPC - 3.999 for FS9 or 4.827 for FSX, or later (the latest interim releases in the Download Links subforum are 3.999r and 4.839). Regards Pete

Mouse look mode can be switch on and off using assigned FSUIPC controls, or via the standard FS method of holding the space bar down too. The facility for it to be enabled when holding the middle button down is an "extra" facility enabled by default, but never was the prime method. Please do review the documentation for this -- currently item 2 in the "Changes" document. Pete

Please update to a supported version - 4.827 is the current main release, and there's a 4.839 in the Download Links subforum which you can apply after running the 4.827 installer. Then we'll have a look if you still have any problems. Also try to remember what else you changed -- you say "I today updated the PMDG 737 ngx SP1.c and now FSUPIC no longer responds", But of course the PMDG aircraft does not use FSUIPC and can have no influence upon it except possibly to prevent it loading, which appears not to be the case. So something else changed. Looking at the Log, this is very suspicious: 1078871 Aircraft="" You appear to have an aircraft with no name, and therefore no way of identifying a specifc profile -- this is why you can't make it profile-specific. The aircraft is defined as one in this folder: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\FeelThere ERJ135LR v2 Maybe your AIRCRAFT.CFG file in that folder has been corrupted? Without a name you cannot assign specific settings. I'm not sure how FSUIPC will behave either -- it's never happened before! It is something I'll check -- but meanwhile try to fix your aircraft files. Regards Pete

Ah, thanks! Never occurred to me! ;-) (I used to write software for fax machines!) So, I assume the question relates to game controller devices. In which case the answer depends on where and how he is assigning the devices: The choices are: * Assign in FSX, don't use FSUIPC * Assign in FSX, calibrate in FSUIPC * Assign in FSUIPC to FS controls, don't calibrate in FSUIPC * Assign in FSUIPC to FS controls, calibrate in FSUIPC * Assign in FSUIPC "direct to FSUIPC calibration", and calibrate in FSUIPC. The first two need the device recognised and "setup" in FSX. The others don't, and in fact doing so could cause conflicts. Hope that answers the question I've assumed. Regards Pete

I've moved your support question to the Support Forum, otherwise it won't get answered! That's nonsense. As far as I'm aware iFly do not use FSUIPC, so the version is not relevant. If they do have any problem with compatibility then they should contact me for resolution, and no one has. You cannot. The earliest supported version is 3.999 and the current interim update is 3.999r. See the Download Links subforum where you can update. Pete

In that case it certainly isn't due to anything FSUIPC itself is doing. The crash is actually happening whilst FSUIPC is waiting for SimConnect to return, and since FSUIPC won't be starting any device threads for an unregistered install, it isn't actually doing anything at that time. I've no idea why it should only crash when FSUIPC is installed -- as I said a while back it can only be due to the different timing of events or memory arrangements. One last thing you could try is removing the FSX.CFG file from its place in your AppData Microsoft FSX folder so that FSX makes another and reverts to defaults. If that stops the CTDs it becomes a matter of elimination to see which settings in the original CFG may be responsible. One of the things which can crash FSX is a corrupt WX file asociated with the default Flight. This ternds to affect FS more with FSUIPC installed because it requests weather from SimConnect so forcing the latter to decode the WX file. However, FSUIPC doesn't (cannot) request weather until after the SimConnection is made, so it doesn't seem that's a likely cause. Well, that certainly seems to be pretty conclusive in terms of what it is related to. But "why?" is the question. I wonder if the way it isn't working is actually part of the problem. Have you disabled it in Windows device manager to stop drivers being loaded for it? Regards Pete

Sorry, how is FSUIPC related to fax? FSUIPC is a module which runs inside Flight Simulator. Pete

Yes, though it isn't so much disabled as simpy ignored (except of course in the FSUIPC assignments tab). Unless you have things assigned in FS as well, only those assignments pertinent to the current aircraft or profile are active. Regards Pete

For common button actions you would be better off making them non-specific. Are aircraft A and Aircraft B variations of the same aircraft? Are there assignments which must be different between them? If not, choose an abbreviated name for them both and edit the INI file to use that instead, enuring that "ShortAircraftNameOk=substring" is set in the [General] section. You should also think about using Profiles instead. If none of this, then just copy and paste the settings you want duplicated in the INI file. Regards Pete