Pete Dowson

SB4? I thought that was only for FSX and used Simconnect, not FSUIPC? Anyway, WideFS documentation cannot help with other programs, only with WideFS. If SB4 doesn't say why it "cannot find FSUIPC" then you may need to contact SB4 support, or at least read SB4's documentation instead. I wouldn't know what they meant by that. If WideClient is running it looks like FSUIPC even with no connection. Maybe they don't like the version number or something. If you want me to check the WideFS part, show me these files: FSUIPC.LOG and WideServer.LOG from the FS9 folder. WideClient.LOG from the WideClient folder on the client PC. Regards Pete

Only on the 4 throttles page. But the generic single throttle on page 1 provides no reverse. It is merely a copy of the normal FS throttle. There is no point leaving space for reverse there! Only for forward thrust. I've no idea what you are doing. Are you using the single throttle on Page 1 or the multiple throttles on Page 3? You CANNOT USE BOTH for the same axes, they will conflict! It will be a complete mess! If you want to use a single throttle lever for multiple engines and with a reverse zone on the axis please just follow the instructions in the documentation for doing this. That entails mapping the single throttle, on Page 1, to the 4 throttles (using the checkbox). You do NOT calibrate the page 1 throttle at all! Pete

In that case I do not understand what could be wrong. The install log shows you installed FSUIPC okay. You ARE running FSX as the same logged-on user as the one you used to install it, aren't you? Otherwise it will likely not see you as registered correctly. If that isn't the problem, please ZIP the Install log, the FSUIPC.LOG and the FSUIPC.KEY files (all from the FSX Modules folder) and attach them to an email to me at petedowson@btconnect.com. BTW, you said "Bought my reg.key nov. 24, 2008". Could I ask what happened that you failed to report your problem for 6 weeks? Regards Pete

FS9 and before or FSX/ESP? You need to say. Before FSX the N1 setting isn't supported via any offsets. Use the controls (AP N1 REF INC and DEC). If you want to do this by program, use offset 3110. In FSX and ESP the N1 setting is at 07FA and the hold button for it is 07F4. What does the SPD ref switch do? To find out what controls are associated with which panel actions, simply enable FSUIPC's event logging, then operate the controls with the mouse or whatever and look in the log to see which controls, if any, were sent. Regards Pete

Found it. Apologies. Will be fixed in next increment. Let me catch up with my 3 days of accumulated messages and questions first, then I'll fix it. [LATER] Okay, fixed in 4.418, now available. Looks like it only ever affected version 4.417, not any of the many other versions since you last updated! Regards Pete

No way, no. All you need to do it put Wideclient into the Startup folder on your client PC. then it is always running and will connect and disconnect to FS when needed. Your program will connect to it just as if it were FS itself. There are no programs with WideFs clients built in. Only one client is allowed per client PC. All communication for each PC is channelled through one link no matter how many client programs there are on a PC. It is much more efficient that way, believe me. the data needs of most client programs are similar. On FSX, FSMap uses SimConnect I believe. It uses FSUIPC on FS9, so it will presumably be able to use WideFS for a network. Pete

What? This: By "system date, set on the PC" I mean the DATE (day, month, year, you know? Like today is 11th January 2009?) that your PC has set. Look at the clock, probably in your system tray, bottom right-hand corner of screen normally. Click on it, read the date. If it is wrong, correct it! If you don't understand that there's a date and time set on your PC, it is most likely that this is the problem. You've probably not set it correctly! I'm afraid I am away from now till Thursday, 15th January. A family funeral to attend. Regards Pete

Wonder why not process the THROTTLE DECR and INCR key events themselves, then? FS itself converts F2 and F3 into those in any case, if the default assignments are left. It would seem more normal to utilise the controls rather than specific key presses which can be re-assigned, normally. Regards Pete

What about the earlier lines? Please don't delete them. 1.Does the signature check correctly (right click on the DLL, select Properties-Signature, and details on the signature when selected). 2.When registering in the Installer, did you enter every part i.e. name, address, key) EXACTLY as supplied -- not just the key? In 99.9% of such cases folks have simply entered their name differently! If so, delete the KEY file and re-install to re-register. 3.Is your system date, set on the PC, before the date of your purchase? Is so, correct it. An earlier date, preceding purchase, invalidates the key. BTW, by deleting the first few lines from the log you hide the version number of FSUIPC. I always need that! I would also prefer to see the Install Log, which for registration is more relevant than the FSUIPC4 run-time log. Regards Pete

As stated clearly in the FSUIPC user documentation, in the section about registration, the name and address are used to identify you, uniquely, so you can't have FSUIPC and WideFS registered to two different people at the same time. SimMarket would have resolved this for you quicker than I -- especially if i was away on holiday or something -- as they deal with all matters to do with registration quite efficiently. However, as you have already sent me the details (just received) I can make a new FSUIPC key to match your WideFS key. You will then have to delete the FSUIPC.KEY file from the FS Modules folder and re-register both. Regards Pete

Go ahead. The order is irrelevant to FSUIPC, excepting the new[Profile ...] sections, the order of which would determine the order they are listed in the popup selection menu. Within each section the ordering is also irrelevant, as each line is accessed by its keyword or number -- but of course for Buttons and Keys the numerical order of those keys determines the actionable order (but the order in the file does not). Regards Pete

You can only calibrate flaps on an axis -- i.e. a lever -- there is no such thing as calibration of a toggle switch or button! Buttons and switches are either on or off, there's no "calibration" possible! "Calibrate" means to align some action or meaning with a value being read. There are no values being read from a switch other than "on" or "off"! All you can do with a toggle, assuming it has two contacts (on up, one down) is to assign Flaps Inc to one direction and Flaps Dec to the other. Forget flap calibration altogether. If only one position is recognised, then you'd need two switches or buttrons, one to raise flaps, one to lower them. The lever you haven't got which you appear to want to calibrate!!! Please refer to button and switch assignments for buttons and switches, and only refer to lever and axis calibrations for levers and axes! Pete

Have you asked for help on the Squawkbox Forums. I'm not sure this is the best place. Right, but SB4 doesn't use FSUIPC or WideFS. No you cannot, I'm afraid. SB4 is purely a SimConnect client program, there is no FSUIPC interface in it at all. I expect it is a problem with installing SimConnect on your client. You have done this, haven't you? You do need the Deluxe edition of FSX for this, as you don't get remote SimConnect facilities with the basic version. Once you've done that it is a matter of getting your SimConnect.CFG file, installed in the Client, matching the SimConnect.xml file on the Server. I'm sure there must be some documentation for all this with SB4? Regards Pete

That's all very well, but they should consider cockpit builders and hardware use when they make these designs. So, let us in on this method so others can benefit, please. Well it is so easy in only a few lines I will do it for you here, for one of the functions: i = 0 while i < 5 do ipc.keypress(113) ipc.sleep(500) i = i + 1 end Save that into the Modules folder as, say, Reverse.Lua, then assign your button press to "Lua reverse" (reload buttons first to get the Lua files re-scanned). You will need to adjust the sleep time to make it work at the speed you need -- the 500 is half a second between each repeat. Okay, but let us know here, too, please. Regards Pete

Sorry, I've no idea how you've assigned things differently for PMDG 737s so much from anything else that it's a mess. I don't see that re-installing them would help anything, as the aircraft themselves do not read any buttons or joystick axes directly. It is all done by FS itself, or FSUIPC where you've used that for assignments. If you want to start again with FSUIPC just delete the FSUIPC INI file. If yu want to start again with FS delete its CFG file. Regards Pete

Strange. I've no idea what they are doing. Seems a bit limited in usefulness. Try enabling FSUIPC's Even and Axis logging (Logging tab left hand side) and see what gets through when you are doing these things. There must surely be a better way? If it is operating reverse by reverse pitch of the props, why isn't reversing the prop pitch using that axis working? Odd too, as keypresses only get queued up in the message queue. If they read them, they read them. If they don't they sit in the queue. Not at all nice to do the way all this is programmed. I'd rather look for the "correct" way. Have you asked the folks that built the aircraft for a solution? It must surely be something they've thought of -- some way to use their aircraft with hardware. Oh, BTW, you could quite easily do what you want using a Lua plug-in for FSUIPC. Have you looked at that possibility at all? Regards Pete

Wouldn't prop reversal be done by -ve prop pitch axis values, not throttle? Doesn't that reverse the blades? FSUIPC does support negative prop pitch too. Just program it for once then edit the INI file to make it do it n times. But don't use KeyStrokes for this -- use the proper FS control. Or does this add-on aircraft intercept the F2 and F3 keystrokes themselves? F2 is just "Throttle Dec" and F3 is "Throttle Inc" -- the same, in fact, as the 3 and 9 keys on the Numeric Keypad. I assume they must be intercepting either the keystrokes or the FS controls -- more likely the latter. If the controls go through to FS they operate the same as an axis input would do. No need. Simply do 0 =P3,20,K113,8 1 =P3,20,K113,8 2 =P3,20,K113,8 3 =P3,20,K113,8 4 =P3,20,K113,8 5 =U3,20,K114,8 6 =U3,20,K114,8 7 =U3,20,K114,8 8 =U3,20,K114,8 9 =U3,20,K114,8 except, providing the controls work, change the K113,8 and K114,8 parts to C65602,0 and C65598,0 respectively. Those are the controls which those keypresses are converted to in FS's assignments. It's really not worth adding a special facility for repeats as there's not a lot of use for them in general. Sequences of different controls or keypresses are needed at times, so using the multiple entry technique for repeats is sufficient. Note that once you do something like this in the INI, FSUIPC won't let you edit that button in the on-line options. It would be too easy to get into a mess, and I didn't want to over-complicate the dialogues for minority uses. Regards Pete

But the Log clearly shows you writing 0x81 for "all off" -- the 1 bit is setting ADF on. You need to write 0x00 or 0x80 to set all off. You are explicitly turning ADF on every time you turn something else off! There is no way FSUIPC or FS is setting this bit -- either you are setting it, or it is something to do with WideFS. Can you run directly on the FS PC? Otherwise you may need to use Logging in WideClient to see what you are doing, exactly. Regards Pete

There is no difference as far as WideFS is concerned between wireless and wired. The key points are the same in both cases -- either no firewall (I use the firewall in my router for protection from outside my local network) or FS and WideClient, ports 8002 and 9002 allowed, and ideally all PCs in the same workgroup (otherwise the broadcasting doesn't work and you have to use explicit parameters to make the links). Regards Pete

Sorry, I never received them. Maybe you got the email address incorrect? Otherwise they must have been swallowed up in my ISP's spam cruncher somehow. If your program is freeware then there's no problem. if you are masking a profit from it then there should be some agreement between us on licensing. Please do try emailing me again: petedowson@btconnect.com. Normally, if you don't get a reply within a few hours, I didn't receive it. I do reply to all genuine emails I receive -- only spam and phishing attempts are deleted. There will be delays when I'm on holiday or (as next Monday-Wednesday, away at a funeral), as I never go near the Internet then. Thank you very much! Regards Pete

Don't add any folders. If your CFS doesn't include the usual FS-type folders and files then it is probably CFS3. CFS3 is not based on FS and has nothing in common with it which can allow many FS type add-ons to work -- especially it doesn't allow for any add-in modules such as FSUIPC. Only CFS1 and CFS2 were based on and retained the original FS structure and facilities. Regards Pete

I don't think that can be FSUIPC because it has no idea what view you are using, nor does it care. In fact it isn't involved at all. From what you say it sounds like a bad aircraft panel configuration. Try a different aircraft. Review the panel stuff for the aircraft giving you problems. If it is one of the more advanced aircraft, like those from PMDG, it might be that one of their DLL's isn't being loaded by SimConnect. If it only happens with a specific aircraft, you need to talk to their support. Also, whenever you want any support for any of my programs I always need you to state the actual version number. Just saying "latest" is meaningless to me. The latest you saw on some web site some place, or what? I provide version numbers, clearly so I can identify versions, Please use them. And if you believe it was okay with a previous version, you need to state that version number too. Regards Pete

In FSX, or before? In FSX it is definitely Zulu. All of the date and time stuff are Zulu except where explicitly marked as local (0238, 0239, 0244, 0245, 024A). In FS9 and earlier versions I wouldn't be so sure, but I think the same. I'd have to experiment with it to find out. Not such a "quick one" then, eh? ;-) Regards Pete

I've implemented a "spoofing" or "override" facility for most offsets FSUIPC reads from FSX -- by no means all. Those which involve some substantial re-working by FSUIPC have been avoided. The ocde is rather complex and i don't want to mess it up or slow it down. But I think it will handle all the stuff you want. FSUIPC4 is still reading the originals, but when they are being overridden then the 2real" values are being stored, ready to restore to the offsets when your program relinqishes control of the offset or times out. There are some uses that still get the originals: 1. GPSout still sees the "real" FSX values for the stuff it needs. 2. A Lua plug in which applies overrides can still read the originals. #2 has a special use. You can write a Lua plug in to read a value, manipulate it, and make it available in the original offset just as if it had come from FS. and being internal (an FSX thread) it can do this almost as fast as FSX is running (it simply isn't given such a high priority). I'll email to you the interim FSUIPC4 update, plus details of how to apply the facility, and the Lua example of changing values on the fly. Regards Pete

Now that I know you mean FS2004 with FSUIPC3, I tried things here, and they work fine, so I suspect it is either something you are doing, or possibly some function of the aircraft panel you are using. To eliminate the latter, try a default aircraft with default panel. It doesn't happen here with the default aircraft. Also, this area has been unchanged in FSUIPC3 now for many years and through several versions of FS -- I'm sure it would have been noticed before. So obviously I need to see the logging I mentioned, and I definitely need to know whether this is a default aircraft/panel or not. Just for your information here's the logging from my testing, with added comments: 338391 Monitor IPC:3122 (U8) = 128 ___the 128 (x80) bit is COM1. Either COM1 or COM2 sounds are always enabled. 403547 WRITE0 3122, 1 bytes: 10 ___the 16 (x10) bit is NAV1. Here I turn it on. 403578 Monitor IPC:3122 (U8) = 144 ___128 + 16 = 144 (x90), both NAV1 and COM1 are on. 410703 WRITE0 3122, 1 bytes: 00 ___Here I turn NAV1 off. 410750 Monitor IPC:3122 (U8) = 0 ___The offset reads what I wrote, until ... 410875 Monitor IPC:3122 (U8) = 128 ___... the next read-out from FS, showing the COM1 flag still, of course. Note that the IPC Read/Write logging is in hexadecimal whilst the Monitor logs in decimal. Regards Pete