Pete Dowson

Let's see if I understand this properly. you have a switch on an add-on aircraft which is effectively a multi-position switch with 32 positions, and you are trying to "map" an analogue input value to each of these. right? Really, the facility in FSUIPC you are trying to use was never intended for such use. I'm surprised the add-on aircraft has such a control. Do you use 32 different Mouse Macros, on for each position, or what? I think you need really to explain the actual output/control dside so i can best advise. Pete

SIOC can set focus to a specific window? Pete

Really? You seem to be on your own. What are you assigning to in FSUIPC? Pete

Well that cannot be anything to do with FSUIPC, that's to do with the Migration Tool. The "disaster" FSUIPC would get into, if it thought your Sim was something other than what it said it was, would be to (a ) not provide all the correct facilities, and (b ) probably cause it to crash. No way can it affect sceneries or gauges. When it asks to find the FSX file NEVER EVER direct it to anything else! Just abort that action and let it carry on and do the P3D part of the Install. Each simhas its own section, its own action in the Installer. The reason it wants to find FSX is because your Registry says FSX is installed. If you want to get rid of that prompt you'll have to edit the Registry. Look at the Install Log produced. It tells you everything, step by step, including what the Registry says and where it says it! This is why logs are produced, so you can see what is going on! Pete

Well you can try sending a keypress using offsets 3110/3114 with the FSUIPC-added control to send a key (see the list in the Advanced User's Guide), but I think this will need FS to have the focus. Can SIOC send keypresses itself? Pete

Migration tools make a mess of attempts to provide intelligent installers which know about the FS programs. NEVER use a Migration tool to install FSUIPC. It would be disastrous in any case -- FSUIPC is different for each sim 9even each version of the sim) and will not behave correctly if you try to fool it into thinknig P3D is FSX or vice versa! You don't prompt anything to check registration. It is simply an option. If it doesn't fail the check, it passed it! If you aren't re-entering your registration then that's the same as cancelling the entries. Or did you need to change it? If so you don't "check" you enter the details. What is the actual problem you are concerned about? You don't mention one. Pete

"Custom" switches and buttons? Sorry, that sounds like you mean ones specifically for you and not related to a specific aircraft. If you really mean switches particular to the Add-On aircraft you are using, then you need to find a way to set them, whether it be by custom controls (as used by PMDG), L:Vars or mouse Macros. Or even keyboard shortcuts -- lots of add-ons spport those. If none of those facilities are supported by your add-on aircraft then you are out of luck. The picture doesn't help at all. sorry. Is it your hardware or a screen grab from the add-on? Why not just set the AddOn switches according to your hardware switches? Are you also trying to control your hardware from switches in the Addon? You were using L:Vars earlier. Are you now saying they aren't actually available? If there's no way of controlling the add-on switches or getting their states out, then I think you may need to choose a different add-on, unless the makers will add stuff for you. Er, mouse macros cannot get information OUT of the Sim! They operate like clicking the mouse, there's no way to read what the mouse does! If you mean the only way to operate the add-on switches is by mouse macors then you need to program SIOC to execute the mouse macros. If SIOC can send character strings to offsets then there's an offset to do that. If not you'd need a Lua plug-in to do it for you, based on values sent by SIOC to a user iffset (any in the range 66C0 to 66FF). Pete

Sorry, I'm not sure I understand. Are you saying that offset 0BC8 is changing correctly, but this does not operate your add-on aircraft's parking brake? If the add-on PB is only controlled via L:Var, then all you need is a little Lua plug in which has an event.offset for the offset 0BC8 calling a function which does the appropriate L:Var write. But your statement "take the Lvar 70232 to input it somehow into an offset " sounds as if you want to READ an LVar and copy it to an offset? I don't understand that bit as it doesn't seem to be right for a parking brake. Or is that just to control the LED? If so of course you can have an event on the L:Var, and write to an offset. Pete

I'm afraid I don't know anything about SIOC at all (nor LINDA, for that matter). So the lines of parameters for SIOC are just gibberish to me. For the standard FS parking brake you either need to use the controls, as assigned normally in Fs or in FSUIPC to buttons or switches, or you need to write to the Parking Brake offset (in the latter case, FSUIPC sends the controls for you). You have the correct offset 0BC8 and I assume you are writing the correct values -- a 16-bit (2 byte) word of 0 for off and 32767 (hex 7FFF) for on? But you should check that this is indeed happening by Monitoring the offset, as type U16, using the Monitoring facilities in the Logging Tab (right-hand side). If you are writing them correctly but it isn't working in the add-on aircraft you are using check again with a default aircraft. Maybe the creators of that add-on have done their own thing. If you are not getting the values written, then I'm afraid you need to talk to someone who knows about SIOC. If they are being written but then being overwritten, you have some conflicting setting or driver. Pete

I don't know what P3Dv3's ATC window needs. You could test with a plug-in using the Lua function ipc.keypress which doesn't change focus, and with ipc.keypressplus which allows you to change focus to FS and return it.to whence it came. Personally I would never use the default ATC. I'm currently a Radar Contact user, but looking with interest at ProATC-X. Pete

Sounds like you network connection isn't sustained. You aren't using WiFi are you -- that's usually a no-no with Simconnect? And why not run ASN on the FS PC? Never any problem here. BTW You should realise that I really cannot support SimConnect or ASN? I have enough to do with my own products! Pete

Almost all applications for FSX or P3D use SimConnect. If you have a problem with FSUIPC this is the place. If it is with another SimConnect application you need their support. I cannot support other applications! How do you know "SimConnect gets disconnected from ASM?". Why don't you ask ASN support? ASN does not use or need FSUIPC. Is you laptop also running FS? Are you sure you don't have a Networking problem? Because SimConnect is used in a huge way by any add-on which needs it. You are logging every single time any variable requested by any SimConnect client changes. That's the way it works! Pete

All Logging facilities are there for everyone. This is because the unregistered version still operates as an interface for applications and much of the logging is to help get those working correctly. Pete

He must have enabled it on the Logging Tab in the FSUIPC options. Just go back there and uncheck that option! Pete

Can you report this discrepancy to L-M on their Forum please? I'm not sure I understand the problem as well as you so you would be the best source. [LATER] Ah, I see you have reported it already. Thank you! Pete

The things I would call "drivers" are those that read the USB data and write to FS. Windows itself does not know about FS and certainly does not know about the things the panel is used for. The software which knows that is called the "driver". it isn't the low level standard Windows HID driver, I know that -- FSUIPC uses that for plug-in Lua programs using the HID functions in the COM library. My utility "HidScanner" uses it to read all the details of the HID device's configuration. Aha, so you found it after all! Well done. But it doesn't "send calls via SimConnect to the device's driver". SimConnect is its interface to FS, in the same way as SPAD uses FSUIPC. The Saitek FSX driver will use the Windows HID interface, the one I was just talking about. That's all a question for Saitke I think. You should be able to stop it. Maybe you can run SaiPanels again and disable it there? I know with GoFlight devices you can disable some things in their driver (but again not all). Can't you drive the display panels with SPAD as well, or does it only handle inputs? Surely there must be many users in the same situation? Pete

Just reverse the brakes in the Calibration tab. There's a little check box for this. It is also described in the FSUIPC user guide, which is your place for reference when it is "all new" to you! Pete

Good, though you said you did. Pete

Strange. They all appear to be 250 degrees out. If you add 250 degrees they would be correct by the look of it. But P3Dv3 should NOT (must not) be different. This is a regular Simconnect value, tye one named WISKEY COMPASS INDICATION DEGREES. You need to report it so it will get fixed! If you Monitor offset 02CC in FSUIPC, as type FLT64, then it will show the readouts FSUIPC is receiving from SimConnect. It is not changed by FSUIPC, simply copied as it is into the offset. . Sorry I don't understand what you mean. Offset 02CC gives the compass value in degrees, as it says. Where are you expecting 3600 or 36000 or anything different? The offset is a double float value occupying 64 bits (8 bytes), exactly as documented. Pete

The internal names for the controls, and the ones used in FSUIPC (and logged if you enable event logging) are the same no matter which aircraft is used, i.e For generic all-engine action: Mixture lean Mixture rich These are the ones default assigned by FS to keyboard combinations. For specific engines the names are MixtureN lean MixtureN rich where N is the engine number, 1-4. You can get the same results with Axis controls of course. Mixture set with parameter 0 = lean, 16383 = rich MixtureN set the same Axis mixture set would have parameters -16384 for lean, +16383 for rich Axis mixtureN set the same Also repeated use of Mixture decrement or Mixture increment controls would eventually do the same thing, when the value reaches the extremes, as would writing the extreme values directly to the correct FSUIPC offsets, which would be the way hardware interfacing via SIOC or many other interface cards would probably work. Come to think of it, if your lever is latching and programmed to repeat whilst "pressed", and assigned to an increment or decrement control, it might well take 2-3 seconds to reach the value which moved the cutoff/idle starter lever. Pete

Three big errors: 1. You do NOT add a "LuaFiles" section. FSUIPC does that automatically. It is not a user-editable section at all, it is just the way FSUIPC keeps track of assignments, in Buttons, Keys or Axes sections to Lua plug-ins. 2. The [Auto] sections are for Macros and Lua plugins. Please please do refer to the section entitled Automatic running of Macros and Lua plugins in the FSUIPC4 advanced users guide. FSUIPC has no way to understand what it is you mean by 1=display_vals2=ipcDebug3=record to csv because those are all in the wrong format. It would think they are Macro filenames, but with the contained macro name missing (it should folow a : character, as shown in the example). Lua plugins are run by the Lua command as shown in the documentation. 3. The supplied ipcDebug lua package s NOT usable on its own. It is automatically preloaded when you use the LuaDebug control. It is very rarely used these days as FSUIPC now has a more automatic Lua/ Debug/Trace option, enabled in its Logging Tab. ---------------------------- Please do not rush in trying to use things before looking them up. Pete

I don't know Saitek devices like this, but the panel will be a standard HID device for sure. But there must be some driver which is interfacing to FS and sending the correct controls. And it doesn't get installed with Windows, so it must have got onto your system at some time beforehand. An INF file would have been installed which links the USB-obtaned identification of the device to the driver and Windows would automatically associate them from that. Yes. You don't want two drivers trying to do the same thing. I wrote a program called HidScanner which was made to provide Lua programmers with enough information to write their own HID driver plug-ins using the HID functions in FSUIPC's COM library. Try that. You'll find it in the Download Links subforum -- useful programs thread I think. I assume you've tried uninstalling the device and driver from the Windows device manager? That would be my first step. Then just try using SPAD. Otherwise, if nothing else, perhaps either SPAD or Saitek support forums might help? Pete

Hmm. You can log events in FSUIPC to see what is happening, but whilst that shows the controls passing through which are doing it, it cannot identify the source. So you'd need to look. For instance, are you assigning in FSUIPC but still also have controllers enabled in FS? Do you have multiple assignments in FSUIPC? Maybe the lever is actually not a latch but a momentary on-off, like a button, but you have assigned the parking brake control to both "push" and "release"? Or perhaps this throttle quadrant came with its own driving software which is trying to do the job and you've added unnecessary extra control assignments? I can't really hazard many more guesses without knowing what you have installed or what you've done. This sounds like the same sort of thing as above, though where or what is delaying 2-3 seconds I can't guess at all. Are you sure there's no software or driver involved other than FSUIPC or FS assignments? No normal assignments will "wait 2-3 seconds"! No, FS uses precisely those controls for the fuel idle/cutoff valve controls for jets too. Sorry, I don't understand this comment. What "one"? Pete

Sorry, I don't understand what you are doing. Yes, in a properly programmed 737 cockpit you'd need toe brake pressure to set and release the parking brake -- it just acts like a latch to keep the pressure on. I have this programmed in my cockpit because I have written my own code to do it. You could do it yourself using a Lua plug-in program. But most folks don't bother. They are just happy enough to set and release the parking brake with a lever or switch. There's nothing in FS which operates the "real" way. Why not try just assigning to the Parking brakes control? BTW It isn't only 737s -- many aircraft have the sort of parking brake which is really just a latch which holds the toe brake pressure on. Even a Cessna light aircraft one works like that. The 737 is in no way unique. I don't know what you are doing to make that happen. The fuel lever "idle" is set by the "mixture rich" control, and the fuel cut is set by the "mixture lean" control. It sounds like something you are running is re-sending "mixture rich". Sorry, but I don't know Linda at all. I think they have their own support. Pete

I don't think any version supports Elite. You need to contact Elite support. Pete