Pete Dowson

I thought you said you got it working, here: Now you say: So I am completely lost, again! Duh! The point of A/T is to control throttles for you. That's what it is supposed to do! This thread is so insanely confused, with no straight information in any part, I'm not surprised. I really have no idea what you've got going on there. I try to help, but you contradict yourself so often I dfon't know what is what, at all. sorry. I think it would be better you throw that junk away and buy a cheap joystick for now. Otherwise, bring it over here to my house and we'll work it out properly. I can't really continue to work like this. Regards Pete

I moved your support question to the Support Forum. You posted in one of the sub-forums. I'm trying to translate this at the moment. ... Okay: "I bought the FSPUIC3 27/12/2011 (order 919640). I use windows 7, FS2004. No problem for the download to install, for the record, everything is ok. At the opening module / FSPUIC, I get the window FSPUIC NOT registered, and therefore can use all fonctions. Have you a solution." 1. Cannot find any order numbered 919640. I have seen no order numbers in the 900000's yet. They are still 8's. And I can find no Jean François registration, only a Jean Francois with a surname beginning with M, and that was for FSUIPC4 not FSUIPC3 and dated 27/1/2012 not 27/12/2011. 2. Please tell me the actual version NUMBER. If it is not 3.998n please get the updated Installer (see Download Links subforum), and try that. 3. Did you follow the instructions for installing, and use right-click "Run As ... Administrator"? If not please do. 4. If you still have a problem, please find the Install log and the FSUIPC3 log, both in the FS Modules folder, and paste them into a message here. Regards Pete

Oh dear. FSUIPC's calibration never has and still does not know anything about 'devices'. It intercepts the controls which FS uses internally to operate the control surfaces. FSUIPC's calibration knows nothing about where the values came from -- it doesn't care. If you send FS controls to operate the surfaces, as you are doing, then those controls look the same internally to those which FS or FSUIPC assignments would make to the same controls. Regards Pete

Ah, that was nearly 18 months ago! I can't even remember things two months ago, let alone 18. I am getting old and memory seems to be the first thing to go. Or maybe it's the wine and beer. ;-). Since those little Lua programs are sending thorttle values ONLY to internal Local Variables specific to that aircraft, it is not at all surprising that no facilities applicable to axes or calibration can be used. For synchronising them you would need to test the throttle sync flag in the functions. In the throttle1 function, if the flag is set send the value to both throttles. In the throttle2 function, if the flag is set, send to neither. As listed in the list of FSUIPC offsets, the throttle sync falg (set and cleared by the hot key) is offset 0x330C bit 4 (2^4 = 16). So: Throttle1 lua then looks like ipc.writeLvar("L:AS_FADEC_0", 4096 - (9 * ipcPARAM / 4)) if logic.And(ipc.readUB(0x330C), 16) ~= 0 then ipc.writeLvar("L:AS_FADEC_1", 4096 - (9 * ipcPARAM / 4)) end[/CODE] Throttle2 lua then looks like [CODE] if logic.And(ipc.readUB(0x330C), 16) == 0 then ipc.writeLvar("L:AS_FADEC_1", 4096 - (9 * ipcPARAM / 4)) end[/CODE] Regards Pete

No key, but I'd like to register your products, so please write to me with details, to petedowson at btconnect.com. Will they be freeware? Regards Pete

You posted in the User Contributions subforum. I moved your post to this Support Forum where please post any future support questions. Sorry, but I do not understand. Perhaps you should say what version of FS it is you are using, and also the version number of FSUIPC. Both are important. When you say you "cannot see the aircraft at Mause macros", do you mean you cannot use the FSUIPC mouse macro facility on the aircraft you are using? If so then one of several things might apply: 1. You are using an old version of FSUIPC which didn't support mouse macros, or 2. You are using a version of FS which does not support mouse macros, or 3. You are using an aircraft which does not support mouse macros (like most of the default aircraft, for example), or 4. You are trying to use mouse macros on a part of the aircraft which does not support mouse macros. If this is of no help, you will certainly need to explain rather more about what you are doing, what FS, what FSUIPC, what aircraft, what gauges. Regards Pete

You didn't read the thread you are appending to? I aways need version numbers. "Last version" means nothing. State the number. So, exactly what version did you install? Note that the latest installer installs version 3.998n. If that isn't the one you installed, try again with that. Otherwise show me the Install Log, from the FS Modules folder. Regards Pete

Actually, i just checked, and remembered some things. What I said wasn't completely accurate. The lat/lons for the runway ends are actually computed from the runway centre lat/lon (defined in the sceneries) and the runway orientation and length. So they should be actually on the border line, or very very close. This was changed from using the defined "Starts" because n a lot of airports especially add-on ones, the starts were actually at the hold position just off the runway (and with a 90 degree or other orintation to the runway). I think this was done as a more sensible position in most cases than placing aircraft directly on the runway. But it made a mess for programs like radar contact and others which were trying to line things up for an approach. So, you should only need to adjust the position by the length of the aircraft to have it completely on the end of the runway. Add the threshold offset from the BGL and you are on the threshold. You can actually read the "Starts" from the log, the Runways.txt file. At least I think those are the literal values from the BGLs. Regards Pete

Page number? For calibration? There's a whole chapter! Please look it up in the contents list at the beginning! Pete

Not most of those I've looked at, includeing for example EGLC and EGCC and EGLL. The start points are those supplied by the BGL and where the FS airport menu would place you if you told it to start at a runway, so something is very wrong with your system somewhere. Maybe the BGLs are wrong? EGLC is just perfect on FSX. P3D must have messed up the FSX/ESP scenery files somewhere along the line. Because MakeRunways started life in about 1995 and has been developed ever since mainly by me being a sucker and acquiescing to requests from all and sundry over the years. But no more. Pete

Please forget ENTIRELY about assignment. Only look at calibration. You are NOT assigning anything at all! That's already done by the way the Elite driver works and also by the Lua plugin. You only need ot look at calibration. FORGET ASSIGNMENT! It is totally irrlevant, and you are only getting annoying referring to it all the time when I told you otherwise! Pete

So how are the Lua programs working? Sorry, I don't know them. So they aren't really being driven via a normal FS axis control. Sorry, I don't understand at all at present. Regards Pete

I mean that axis assignments are documented independently from joystick calibrations, and it explicitly states that you do not have to assign in FSUIPC to use the calibrations. How could that have ever been needed? Calibration has been present for over 10 years, assignments only 8 or so. I keep teling you you should calibrate if you want the results you seek. The documentation describes the facilities in FSUIPC. That's what it is for! Making assumptions like you see to have done is not going to allow you to get the most out of the program, which is why I suggested you review the user guide so you can appreciate the facilities offered. Oh dear. As I told you the AXIS controls do not have a reverse zone! FS itself does NOT support reverers on axes. Only FSUIPC does this.. To make a reverse zone you MUST calibrate in the 4 throttles calibration page. I'm about to give up on this. Until you've decided to calibrate there's no point continuing this. :sad: Pete

But the offset to the threshold is also provided. There's no separate position for ILS touchdown that I know of. I think it uses the threshold. The R4.CSV file you say you are using gives 400 feet as the offset for the default FSX EGLC. The accuracy will be as good as the data in the scenery. I suspect the UK2000 or Aerosoft add-on EGLC's will be more accurate. Regards Pete

FSUIPC is not a weather providing program. It does not provide any clouds and wind to disable. Regards Pete

The Lua is posting FS controls to FS. FSUIPC can calibrate those! That's the main point of intercepting the axis inputs and sending them as controls. I think you are seriously confusing axis ASSIGNMENTS and control CALIBRATION. The two are separate tabs and operate on different things. The calibration facilities have been available in FSUIPC since version 1, long before axis assignments were added! I think maybe you need to review the User Guide a little? see what FSUIPC can do for you? ;-) Pete

Yes, but those are from this input: 105082 WRITE0 089A, 2 bytes: 34 E8 105082 WRITE0 0932, 2 bytes: 34 E8 0xE834 = -6092. So the values are passing directly through. why aren't you calibrating? The whole point of calibrating is to match the axis inputs actually obtained to the range required in FS. Don't you use calibration at all? Obviously, if the input is only giving -6092 to +16383 you would need to scale in the Lua to get -16384 to +16383 without calibrating. But calibration would do that for you. And in calibration you'd have the choice of NRZ (no reverse zone) or calibrating a reverse zone if the aircraft you are using supports reversing axes (Airbus doesn't usually). Regards Pete

Both calibrated then? Have you thought of using the calibration sync facility so you still use both throttle levers but they calibrate at several points to give the same values lined up? wuld be more realistic I think. The old hot key facility merely tries to copy what's happeing on throttle 1 to the others and ignores your throttle levers. If you want to stick to the hot key method, please make a brief lof for each aircraft where you engage the sync and move just throttle 1. Enable axis logging. Keep the test short or the log will be unmanageable. Regards Pete

I need to know exactly how you are assigning and calibrating for these aircraft. Well calibrated throttles will normally still have slight differences in postion for the same thrust. But I thought FADEC type thorttles had only certain detente ranges or positions which selected a particular thrust mode, so accuracy of position is far less important, surely? Pete

It sounds like you need different controls. Do a log with axis events enables so we can see the figures being sent. Just move the throttle a little then back to where you think idle should be. If you used option 2, idle should be at the full reverse point, not at any detente. For a detente use option 1. Pete

Which option, the hot key one or the calibration one? All the hot key one does is ignore all throttle axis inputs except #1 and copies the value from that to all the others. Without knowing what you are doing and how the aircraft are using the controls or whatever, I couldn't really say. Regards Pete

Well, you could calibrate idle at any point. That's the idea of calibration, to match the input to the needed output. alternatively, if you just don't want to use the reverse zone on the throttles, just insert lines such as this before the "ipc.control" lines: if val < 0 then val = 0 end val = (val * 2) - 16384 If you want to use the reverse zone as part of normal throttle movement, so that full reverse = idle, use this line instead: val = (val * 1.6) - 9830.4 Pete

OOOPS! I see the error. This ipc.readSD[0x0574] should be ipc.readSD(0x0574) I think I need new glasses! The square and curved brackets looks too similar to me on my screen! Sorry. Pete

Just abbreviating your extensive log to the few unique lines, the offsets it is writing are WRITE0 089A, 2 bytes: 00 00 WRITE0 088E, 2 bytes: A4 01 WRITE0 0890, 2 bytes: 00 40 WRITE0 0BBA, 2 bytes: 20 08 WRITE0 0932, 2 bytes: A9 F3 WRITE0 0928, 2 bytes: AA 3A[/CODE] 089A = Throttle 1 088E = Prop pitch 1 0890 = Mixture 1 0932 = Throttle 2 0926 = Prop pitch 2 0928 = Mixture 2 0BBA = Rudder If it's only the throttles you are worried about it should be easy enough to use [b]event.intercept [/b]in a Lua plugin, for the two throttle offsets, and send the inputs you are getting as FS controls instead. [CODE] function throttle1(offset, val) ipc.control(66420,val) end function throttle2(offset, val) ipc.control(66423,val) end event.intercept(0x089A, "SW", "throttle1") event.intercept(0x0932, "SW", "throttle2") [/CODE] Save as, for example "throttles.lua" in the FS modules folder and add [Auto] 1=Lua throttles to the FSUIPC INI file. If you only want it to operate for a sepcific aircraft or profile use [Auto.<name>] instead. Note that the Elite program is probably sending values -4096 to + 16383, assuming it has a reverse renage. This isn't right for those controls, so you'd need to calibrate in FSUIPC. Alternatively you could scale the vlaues in the Lua above quite easily. You could also use the ThrottleN_SET controls instead if you wanted reverse without FSUIPC calibration. Regards Pete

Yes. I've not yet met any direct use of IPv6. I think some of it is hidden behind aliasses in order to maintain compatibility with older programs and settings. I doubt if it really will ever see use for local IP addresses in a local network, as there are ample for local use in IPv4 -- they can be the same on every separate local network as those IP addresses aren't used over the 'net. Regards Pete