Pete Dowson

Well, I wouldn't normally, but I had a look and it was pretty easy, as PFC already placed the raw axis inputs into FSUIPC's memory (offsets 3BA8 ff, as documented in the PFC DLL doc). All I had to do was make FSUIPC's axis scan include those locations as "extra joysticks" (16 for flight controls, 17 for quadrant, 18 for trims and tiller), and make sure PFC.DLL continued to scan the axes when FSUIPC needed them in its dialogues. Regards Pete

First, why delete the previous version? The update merely involves copying the later FSUIPC.DLL fileinto your FS Modules folder. Nothing else, that is all you needed to do. It would have helped if you had said what the reasons displayed were, but I think "Access Denied" can only occur for one of several fairly basic reasons: 1) The folder is protected -- you've restricted it in the access permissions. If this were the case you would not have been able to delete FSUIPC.DLL in the first place. 2) The file you are replacing is protected. Again, this cannot be so if you have deleted it, as it isn't there to be protected! 3) The file you are replacing is actually being used! This could only be the case if (a) you haven't already deleted it after all, and (b) FS is actually still running -- you can't change parts of a program which is running. I can't think of anything else which could give you "access denied". The most likely conclusion therefore is that: 1. You have not actually deleted FSUIPC.DLL from the FS Modules folder after all, which is jolly good because you don't need to. 2. EITHER the FSUIPC.DLL already there is read-only, or FS is actually still running. To check and change the former, right-click on it in Windows Explorer and select "Properties", then look down near the bottom of the window which appears. Uncheck the "Read-only" check box. To check if FS is still running, use Ctrl_Alt_Del to bring up the Windows Task Manager, select Processes, and look through the list. FS2004 will show as FS9.EXE. If it is still there, but with nothing showing for it on the desktop, then it didn't close down properly -- forcefully end it here using the button bottom right. Regards, Pete

I've not heard of LabVIEW (now "VIs"), but FSUIPC.DLL is not a library which you can call from application programs. It is very specifically an FS module, effectively becoming part of FS once installed. If does not export any FSUIPC_ functions, as these are not usable by FS. There is a C library (a .LIB file) which I provide in the SDK. That can be linked into application programs and it does contain the FSUIPC_Open, Read and Write routines which you would need to call. However, if LabVIEW needs to call routines in DLLs then you would have to make the normally statically-bound library into a DLL first. The source is actually provided in the SDK as well, so this is entirely possible. Regards, Pete

Okaytry PFC 1.994 and FSUIPC 3.537, both now available above. Be aware that if you assign PFC axes in FSUIPC you need to disable those same ones in the PFC options (uncheck the enabling checkbox for each). The FSUIPC assignments do not override thse in PFC, unlike the Button assignments. Regards, Pete

What is "not right"? If by "this" you mean FSUIPC not liking it that your identity (as far as my program registration is concerned) has changed, why is that "not right"? FSUIPC performs the registration for both itself and WideFS (WideFS is only an extension of FSUIPC, after all). Its only way of identifying you precisely is by your entered name and email address. I prefer this to the method many payware systems use, based on your computer system, because that needs updating if you change your computer, or even enhance it significantly, and also restricts your use of the products to one PC. In my view, if you paid for my software, you can use it whereber you like. Would you really rather a more restrictive system? Well, I fail to see what is so strange, and in any case no one ever said an e-mail change was not possible. Both Simmarket and myself have done this directly, on request, for the relatively few times it has arisen. It doesn't happen that often that it's a problem. And as for information about this need, it does actually say this in the FSUIPC document, in the section early on about entering registrations: Maybe you missed this? That's fine, it is what I would advise you to do, though I would only need to replace one of the Keys -- your choice. Note that, since I am not SimMarket and have no records of your registrations, I normally ask for you to include the original notifications from SimMarket so that I can process them properly. In this case, if you've already sent details without I'll see if I can check them here anyway. Regards, Pete

I have been briefly glancing at the original Avsim thread which provoked this one, and I came across this: Evidently this gentleman hasn't read much about FSUIPC recently, but in case this viewpoint is a common one I should try to dispel it here. I'm not a registered member of Avsim (or I am but have forgotten my user name and password), and anyway I think it would be a mistake for me to discuss my work there rather than here. So... The "memory mapping" used in the FSUIPC interface is an illusion. The interface is designed to look like memory mapping purely for compatibility with older programs. It follows and includes the original FS6IPC interface by Adam Szofran. But hardly any of those "offsets" are actually offsets into a memory area. The reason this illusion has been maintained should be obvious. When I made FSUIPC first of all. for FS2000, I did it so that all the programs written for FS98 could be run without changes. I just ADDED new stuff, maintaining the old stuff -- in many cases the illusion started there. Even between FS98 and FS2000 the was little compatibility in terms of either the memory positions or the values there in. Along came FS2002 and the same happens again, only more so. Then FS2004. (Oh, also CFS1 and CFS2 in between those). In each case the previous illusion needs to be maintained so that existing programs can be run unchanged, and more elements added to the illusion to support new features. The state today is that pretty much ALL of the so-called "memory map" is entirely illusory. It is the software inside FSUIPC which creates that 'map'. When programs read from a 'location' FSUIPC has to act upon that and obtain the appropriate value. It does this by a variety of methods: sometimes direct access into some C++ class private data inside one of the 'black boxes' of FS DLLs, but more often by using procedural interfaces inside FS to obtain them as products. Often, for compatibility, values need calculating or converting. FSUIPC does that before returning the results. Similarly, when values are written, FSUIPC is triggered into an action to get that value known to whatever needs to know it inside FS. This, again, may be by direct access, but that is very rare these days. Many IPC writes translate into procedure calls, or even a string of them, into parts of FS to get the action accomplished. The fact that in the end it looks simply like a "memory map" does imply that there isn't much to FSUIPC. Maybe that is why several others have tried to replace it, then found it isn't actually that easy. I should probably take the misunderstanding quoted at the start of this message as a compliment, that FSUIPC has succeeded to make such a complex convoluted interface look so simple on the surface. ;-) Enough from me for now. Good flying! Pete

I'm sorry, but that is really not at all a likely addition for PFC.DLL. I really cannot understand why you'd need it. To me it would seem to be more appropriate to adjust the control effectiveness parameters in the Aircraft.CFG file. The "feel" of your controls should be set to suit the controls, surely? Because the throttle quadrants are exchangable, the levers are different on each. When PFC bring out a console with similarly exchangeable yoke and pedals I would have to extend the driver to support those too. I will make a note of your request, certainly, but it has been the only one in the many years I've provided PFC.DLL. It is far from a simple software change. Actually, thinking about it, it might be better to make PFC.DLL route the axes through to FSUIPC and let you assign them and configure them there (see the Interim release details for FSUIPC 3.536). I already do this for more advanced button programming -- I'd rather all the similar additional user facilities in my products be grouped in one place. I'll look at it that way -- keep an eye on future FSUIPC releases. Pete

I think EpicInfo only knows a few axis controls. Certainly not that one. Aren't they listed in the documentation? I'm afraid you misunderstand still. Is the SDK documentation really so obscure, and my previous messages too? It is the CONTROL NUMBER you have to write to 3110. Look that up in the List of FS controls! You first need to write the value you want for it to 3114. I have told you this before! If that is what it does, yes. Are you sure? I've never tried it. But the offset 3110 is where you send the CONTROL, not the VALUE. The value goes to 3114, first. The problem with trying to do this with EPIC soft axes is that you only have 16 bits. The control numbers for FS controls all need 32 bits, so you will have to write a value to 3114, then the upper part of the control number to 3112 then the lower part to 3110, in that order. It is writing to 3110 which triggers the action. Is LANDING_LIGHTS_SET acceptable to FS9 in its CFG? It usually deletes anything which doesn't figure in its assignments. If it is in its assignments, then why not do it there? What I don't understand is why you are making it so complicated, and seemingly ignoring the advice I give you. If you can now make the EPIC send a button event, why not simply assign the button action to the LANDING LIGHT SET control in FSUIPC, and use the parameter facility there to set a fixed value? You can have different EPIC (virtual) buttons for different fixed values. Alternatively, if you really want to use an axis, like U3, then check out the axis assignment facilities in FSUIPC 3.536 (in the Interim Versions announcement above). You would need to use 'RAW' mode to prevent the automatic Windows calibration changing the value. Please review the assistance I've been trying to provide in this thread. You seem to be missing things, judging by what you have written this time. Regards, Pete

Only the throttle quadrant is expected to change according to aircraft type. The main flight controls are not aircraft-specific! But there are no response curves for throttle quadrant axes, only the main flight controls! Regards Pete

Well, actually they are simply quadratic or cubic calcluations. Easier (quicker) to compute and just as effective for the sorts of numbers we deal with here. They are actually pre-computed and tabulated for fast lookup and application. They are simply referred to as "response curves" in the PFC driver, "slopes" in FSUIPC. I would never have recognised them by the name "expo" I'm afraid. ;-) Okay. The response curve number is saved in the INI file. It's part of the first number in lines like: Elevator=341,1,0,16,56,68,116,255 Rudder=357,2,0,28,49,60,97,255 Here I can see Elevator is using curve #5 and Rudder #6. It's in bits 4-7. Regards, Pete

If there's been no software change, then it must be a hardware problem. However, first just re-check the FS assignments first. In particular, in FS's Options-Controls-Sensitivities check that the sensitivity slider is full right and the null zone slider full left. Sometimes I think FS2004 changes those. There's no calibration program within FS9. When you select calibration in FS is takes you out to the standard Windows calibration. If, indeed, that does show things are okay, but it doesn't respond correctly in FS9, then the most likely problem is the FS sensitivity setting as mentioned above. How do you assign a pedal to the yoke? They are two separate devices, right? Have you registered FSUIPC and used it to do things with the joystick? If not then FSUIPC won't be touching it at all. If so, and you have been messing with it and don't know what you've done, just start again -- delete the FSUIPC.INI file from your FS Modules folder so that it starts with no options set and no joysticks calibrated. However, note that, unless you are using the Axis Assignments in the interim version (3.536), FSUIPC does not deal with joystick axes as such, only with FS axis controls. So if the right brake was being handled through FSUIPC, this would not also mean the throttle was too. When you re-assigned the pedal axis and got the same result you actually more or less proved it couldn't be FSUIPC and very likely is not FS either. One last thing to check in FS is that you haven't got multiple assignments for the same axis or control, in the different joysticks list. In FS's Options-Controls-Assignments, select each joystick device in turn, via the drop-down, and check the entire list of axis assignments for each. Regards Pete

Only on your main PC? It is only the WideServer.DLL which instals into FS. The WideClient.EXE you use on your other PC(s). Did you look inside the ZIP? There's a document called "WideFS.doc" (and a PDF version which will read in Adobe Acrobat). There are hardly any steps in any case, especially if you are running WinXP on both PCs. Please see the step-by-step guide provided. Look under the heading "Installation" Regards Pete

I'm afraid I know nothing about your hardware. I thought the Hagstrom stuff were keyboard emulators. If it connects to a COM port I assume it has it's own driver software? You'd need to consult the documentation. The "right direction" to find out about controlling PM software is the PM website, http://www.projectmagenta.com. There's a section there with documentation (including FSUIPC offsets for PM, if that is how your Hagstrom driver works). Additionally you will find a Support group there which can operate as a web Forum or an email newsgroup. Try there, I'm sure there will be others using similar hardware. As well as not knowing the Hagstrom stuff, I must admit to know knowing much about PMs "synoptics" -- there are none for the 737. :-( Sorry, I have no idea what drives your serial connection. Certainly nothing of mine. Surely it comes with some driver or other and documentation? If it interfaces only to FSUIPC, then it will to WideFS as well. Regards, Pete

ActiveSky and FSMeteo both run very well over WideFS. I've always used them that way. BTW, in your earlier message you said ... but I'm afraid I've no idea what you mean by that. What has FSUIPC and WideFS got to do with scenery? Why? Just install WideServer.DLL into FS's Module folder, then run WideClient on another PC on your Network. If both PCs are running WinXP and the network is working and not blocked by firewalls then, with the latest version of WideFS, that's all you need to do with WideFS. Why do you want to delve into all the technical stuff? It says right at the beginning what to do. Pete

The firewall on my Internet router should help keep outsiders out. The computers inside are all mine, and i don't want to block myself, at all. ;-) Well, I think the FS process is called FS9.EXE isn't it? Check the process list (ctrl_alt_del). But it still seems most odd to me that you give unlimited permission to all and sundry to interface to a program on your server, rather than saying who is allowed to access it. Surely the latter is a much more normal thing to do? A server services those with permission, doesn't it? It's set by the Port parameter. The default is 8002 I think. Neither if you use IPX/SPX, then it's SPX (sequential). If you default to TCP/IP it is whichever of those is sequentially guaranteed, not the one which allows stuff to arrive in random order. Regards Pete

You should really have told SimMarket beforehand and they would have matched it for you. However, as it is, if you send the receipts for both registrations to me at petedowson@btconnect.com I can replace the older FSUIPC one, then you can start again (delete the FSUIPC.KEY file from the FS Modules folder) and register both with your new address. Regards, Pete

No, not yet. First, have you assigned the axis you want to use a the Reverser lever to the main FS Mixture? Do this is FS's own assignments. Make sure it is working for the mixture first. Only then go into FSUIPC's options and set the Reverser action. As an alternative, if you wish, you can try the latest Interim version of FSUIPC (3.536, available above). In the new version you can actually assign axes directly in FSUIPC. For the Reverser you can choose to assign your axis for direct operation into FSUIPC's Calibrations of the reverser. If you do this, be sure not to also assign the same axis to anything in FS. Regards, Pete

Phew. Strange. Glad you sorted itthanks for letting me know! Pete

What is "expo" please? As far as I know I am saving everything you set in the dialogues? What is this "expo"? I have nothing called that. Maybe that's the problem, you want something not yet implemented? Can you also tell me what version of PFC.DLL you are using? It maybe something already fixed. If not the latest, available above, perhaps you could try that first, please (1.993). Regards, Pete

I don't really know -- I'd need to find out about the firewall in Windows Help. Did you look? I always disable the Windows firewall entirely, as it gets in the way of most of my Network needs. However, I would have thought that you don't enable connections TO something in your PC, but FROM something outside your PC? It doesn't make much sense to me otherwise. It is "specific permission to come aboard" you are granting, surely, not "anyone can come and mess with my Flight Simulator". If Windows Firewall needs specific permissions for programs, then the one asking for access is WideClient.exe. For specific Windows help, especially with Networks, you may be better off asking in the FS2004 Forum. Katy Pluta visits there and has been of great help in these matters before. Regards, Pete

If it was sending data then the calibrations screens would show the movement. If you wish to investigate further, you can enable some of the logging (in the Test page) -- the lowest level actually logs everything sen on the COM port. Alternatively you can get the freeware utility "PORTMON" from http://www.systeminternals.com and actually monitor the serial port at the lower level interface in Windows. It sounds as if you may need support from PFC. Regards, Pete

When you say "I have done that", could you please spell out exactly what you have done? I can't guess, sorry. Tell me what you want to achieve and what you've done and what you see. Regards, Pete

No. FSUIPC doesn't have any affect on instrument panels, or any other graphics come to that. In fact if it isn't even registered it is doing nothing at all until some application wants to use it. Something else has gone wrong with your installation. First of all, check that the VoxATC install hasn't done something strange. Regards, Pete

As I am sure it says on the page where you bought it, I think they aim to send it within 24 hours. Obviously, unlike the other products you have bought, the SimMarket place is actually operated by human beings. ;-) If you are not happy I am sorry, but it isn't any use coming here. This is for technical support. Try the SimMarket 'problem' ticket system, after the 24 hours. Pete

Sorry, what do you mean by "only two values"? I don't know what you are reading which shows the number of "values", whatever that means? The LENGTH I think is 2 bytes -- i.e. it is a 16-bit value, the build number of the MCP.EXE file, when it is running. Pete