John Dowson

I've also just noticed that your are reading the lvar AB_AP_HDGTRK twice, into variables AB_hdgtrk and AB_drift. You never use the latter. Also the function DspHDG isn't defined, so the script can be simplified to: require "socket" lastTime = 0; function AB_HDG_plus () currentTime = socket.gettime()*1000 difference = currentTime - lastTime lastTime = currentTime if (difference > 200 and difference < 2000) then delta = 10 else delta = 1 end AB_hdgtrk = ipc.readLvar("AB_AP_HDGTRK") if AB_hdgtrk == 0 then LVarSet = "AB_AP_HDG_Select" else LVarSet = "AB_AP_TRK_set" end LVarGet = round(ipc.readLvar(LVarSet)) AddVar = LVarGet + delta if AddVar > 359 then AddVar = 0 end ipc.writeLvar(LVarSet, AddVar) end event.flag(1, "AB_HDG_plus")

You should review basic lua programming! Merging the code I gave into your function gives this: require "socket" lastTime = 0; function AB_HDG_plus () currentTime = socket.gettime()*1000 difference = currentTime - lastTime lastTime = currentTime if (difference > 200 and difference < 2000) then delta = 10 else delta = 1 end AB_hdgtrk = ipc.readLvar("AB_AP_HDGTRK") AB_drift = round(ipc.readLvar("AB_AP_HDGTRK")) if AB_hdgtrk == 0 then LVarSet = "AB_AP_HDG_Select" else LVarSet = "AB_AP_TRK_set" end LVarGet = round(ipc.readLvar(LVarSet)) AddVar = LVarGet + delta if AddVar > 359 then AddVar = 0 end DspHDG(AddVar) ipc.writeLvar(LVarSet, AddVar) end event.flag(1, "AB_HDG_plus") John

To get you going, here's a short lua script that will adjust a delta value depending upon the time since last activated - it requires the lua socket package which you will need to download and install if using FSUIPC5: require "socket" lastTime = 0; function myTimer(flag) currentTime = socket.gettime()*1000 ipc.log("Current time is " .. currentTime .. ", lasTime is " .. lastTime) difference = currentTime - lastTime if (difference > 200 and difference < 1000) then delta = 10 else delta = 1 end ipc.log("Delta is " .. delta .. " (difference=" .. difference .. ")") lastTime = currentTime end event.flag(1, "myTimer") You can use the logic in this script in the first script you posted (dump the second) - should be reasonably straightforward (hopefully!). John

event.timer calls a function after the interval specified, it doesn't return anything. In your case, it will call a function called 'deg1', which isn't defined. What you need to do is to save the current time whenever you increment. Then, the next time your function is called, you can compare the previously saved 'current time', and adjust your reading delta accordingly. John

Hi, sorry for the late reply, but I don't understand what you you are trying to do (I was hoping someone else would jump in on this one!). If you cannot achieve what you want by using the right hand side of the Axis Assignment tab, which allows you to send controls when the an axis range is entered or exited (and also optionally on conditions by manually editing the ini), then you will need to look into using a lua program. Such a program should auto-run and monitor the throttle axis using the event.control function. In this you can maintain state and perform any action required depending on the throttle value and current state. John

First, check that you have controllers disabled in the sim. If not please disable and try again. If your problem persists, please post your ini file.

In your [Auto.Concorde] section you need 1=Lua IAS Display

Hi, do you mean that you are programming the button ok, but then this is not working in the sim? Your button assignments look ok, all assigned to a profile called 'Single Prop No Two', which is just for the 'Mooney Acclaim With G1000'. You have no general assignments. If its not working for that aircraft, can you activate 'Button and Key operations' logging and 'Events (non-axis controls)' logging from the FSUIPC logging tab. Activate a programmed button and post your log file. Your files show only 1 throttle quadrant connected. Which mans that you have controllers enabled? This is generally a bad idea and can cause issues - you should either assign in the sim or assign in fsuipc (see page 33 of user manual). If you disable controllers in P3D, you can assign your hat to the sims 'Pan View' axis in the Axis Assignment tab (with 'Send to FS as normal axis'). Also try a general assignment to see if that works, as opposed to a profile specific assignment (although both should work, of course). A couple of tips (not related to your problem): - manual set AutoAssignLetters to Yes in your ini file (or assign letters to your devices) - see 'Joy Letters' section of User manual, page 21. This will prevent possible USB problems if you re-connect to a different hub - try adding ShortAircraftNamesOK=Substring to the [General] section of your ine. You can then adjust you profile assignment section to something like 1=Mooney Acclaim which would then cover all variants (see appendix 2 on page 53 of Advanced manual John

Yes, paid/licensed version is required to run lua scripts.

Hi Ray, of course - just add to the [Auto] section of your ini (or the [Auto.<profile>] section if profile specific. See p40 of the Advanced User manual. ...ah, but just noticed that you are referring to P3Dv3 not v4, so presume for FSUIPC4, no? Not 100% sure when this was implemented so this feature may or may not be available - check your FSUIPC4 user manual.

Hi Gundars, that is a long time ago! I'm afraid I can't help much with your question - Pete will be back in 2 weeks or so and may possible remember the problem to which you are referring. However, you should just go to the download links page and download the latest FSUIPC3 version (for FS9 and earlier): If you are now using a different sim and require FSUIPC4 or FSUIPC5 then you will require a new license. Cheers, John

Hi Stephanev, glad its working for you - and wow - that is a great set-up you have there!

Hi Dave, could you post your FSUIPC5 log, ini and JoyScan files please. Which Goflight modules are you running, and are you sure that they are being loaded? Cheers, John

As Ray says, this is going to take some time, especially with Pete being away. Its not an LM issue, it seems to be a timing issue in FSUIPC and I can't replicate in a debug version, so its tricky to track down. Just reduce AI traffic for the time being. I will post when I find more info. John

Hi Scott, 'DIRECT' means you selected the action 'Send direct FSUIPC Calibration'. The calibration you have set for the Ailerons is as follows: Aileron=-16103,-1152,-1090,16249 Your 'null' zone (around neutral) is -1152,-1090, which is very small (62). Try re-calibrating this in the 'Joystick Calibration' tab. John

oh, and the FSUIPC5.JoyScan.csv after a successful start please.

Could you also provide the FSUIPC5.log file for this as well please. John

Hi, looks like you have some serious USB problems...! If you run without FSUIPC, can you assign your joystick axis/buttons in P3D (or in any other program)? Can you try the HidScanner utility, available from Unplug your devices and reboot first before reconnecting them, then try the HidScanner to see if that recognises your devices correctly. I'm pretty sure you've done this already, but also check the device manager on your usb hubs/devices to see if any errors or conflicts are reported. Cheers, John

Hi Ray, I started with RC4 to try and reproduce the crash but didn't get too far and switched to trying with FSAIS instead, but still no joy. I can go back to trying with RC4 - can you provide more details on how to re-create the crash you get with this? Thanks, John

Which one? The rudder? Your image shows you have the centre/null zone set at 331. This should be a range (usually something like -512, 512). You also have no calibration for your throttle. Which axis again? If the axis is reversed, you need to check the 'Rev' box for that axis in the calibration page. Please read the calibration section of the User Guide for details on how to assign and calibrate your axis. If you requite any further help, please give more information (axis? aircraft?) and post your ini and log files, not screen shots - these don't tell me much. Thanks, John

Hi Luke, this is next on my list, after we have got to the bottom of the current problems with AI Traffic/Radar Contact crashing P3d/FSUIPC. I'll get back to you on this once I've had some time to look into it in detail. Cheers, John

What sim are you using? What version of FSUIPC? Can you also check that you have your controllers disabled in your sim. Then if you are still having issues, please provide more details (which axis, sim, aircraft, etc) and also post both your ini and log files (from your FSUIPC installation directory).

Hi Ray, ok, thanks for the added info. I'll ramp-up the AI once I've installed. I'll report back if/when I find something, though it might take me a few days to get around to this, unfortunately.

Now I'm back, I'm going to install both AIM (I've been meaning to do this for a while now anyway) and RC4, one at a time and together, and see if I can reproduce. Once I can do that, I can see if the exception can be handled in FSUIPC.

Hi Bill, this is not really the correct forum for such requests. However, for the Saiteck/Logitech multi and switch panels, you could either use maxx's free SPAD: Saitek Panels Advanced Driver (Go to http://fstools.weebly.com) or the payware Spad.next advanced driver package (https://www.spadnext.com/home.html), which works with or without FSUIPC. Cheers, John