John Dowson

First, your ini file is a bit of a mess....for comments in ini files, you need to use either ';' or '#', not '//' or '!' characters - see https://www.w3schools.io/file/ini-comments-syntax/. From the Advanced User guide: Try removing it from your Community folder to see if that makes a difference. I don't have the 738 (or the MaddogX), but can check with the PMDG 737 later... John

float - a double would be 64-bits. FLT32 is what is used in FSUIPC's offset monitoring facilities and is not a language data type. I don't use C#, but maybe try: public Offset<float> Engine1fuelUsed = new Offset<float>(0x090C);// Engine 1

Again the log file you posted is useless - please always post full logs. You can try with lua - take a look at the HidDemo.lua script provided: copy it to your FSUIPC7 installation folder, update the Vendor and Product names and add it to the [Auto] section of your FSUIPC7.ini file (see the Advanced User guide for further details on how to auto-start lua scripts, if needed). Once that is up and running, see if the virtual flags are recognised in the button assignments panel. Possibly. If you can work out what this is (any documentation with the device? Or PFC support?) then it may be possible to send this via lua.

This version is quite old now - the current and only supported version is 7.3.19. Please update. Also check that you are using the latest version of the PMDG 737, which is 3.0.65. I have not had that issue. You should first verify if FSUIPC7 is receiving the PMDG data. To do this, add the following to the [General] section of your FSUIPC7.ini file: TestOptions=x400 If the PMDG offsets are enabled and working, you should see the following lines logged in your FSUIPC7.log file: If the offsets are enabled but no client data is received, then the PMDG SDK broadcasts are not enabled. If this is the case, double-check you have enabled broadcasting in the 737_Options.ini file in the correct location for your installation (see the PMDG SDK document). If it is enabled then you need PMDG support - check their support forums. If FSUIPC7 is receiving PMDG broadcasts, then you can try logging that PMDG offset (and others) using FSUIPC7's offset logging facilities to see if the updated values are logged. If so, your issue is probably with your MobiFlight set-up and you should ask about this on their discord support channel. John

The license has been updated - sorry for the delay.

It is a 32-bit float (as documented), not an integer, so I suspect that you are reading them incorrectly - monitor them as FLT32. Just checked in the PMDG 737 and they seem to be working correctly, starting at 0 and increasing: Of course, only two offset changing as there are inly two engines. John

How can I possibly answer that? Yes. These may or may not hold the correct value - try monitoring those offsets, using FSUIPC's offset monitoring facilitis, as you fly and see if the values increase from 0... If they don't work, you can use the PMDG offsets (from the Offset Mapping for PMDG 737 document - should also apply to the 738): 6494 4 FLT32 FUEL_QtyCenter LBS 6498 4 FLT32 FUEL_QtyLeft LBS 649C 4 FLT32 FUEL_QtyRight LBS You would need to initially read and save the quantities at the start of the flight, and then whenever you want to know how much fuel has been used simply read them again and subtract that number from the initial values.

If it is a joystick type HID device then it should be recognised by FSUIPC7 and can be assigned there. However, I cannot tell as you are only posting continuation logs, not full log files that include the joystick scanning section. Remove the PFChid64.dll, start MSFS/FSUIPC7, set logging for Buttons & Keys, press a few of the buttons on the PFC430 and see of the buttons are recognised. If so, they can be programmed, if not then it is just not possible. If it is recognsed as another HID type device, it may be possible to control via lua using the com library. No. that means nothing to me. If you have installed any specific drivers for this device, you should also remove them and let windows install the generic HID joystick drivers, which is what FSUIPC would need to be able to use the device as a generic joystick type HID device.

I will ask Pete about this when he returns from his holidays (next week) to see if anything can be done, but if not, and for now, you will just have to use your work-around.

I've just noticed that you already reported this back in January here: Pete has already replied to this in that post: So I'm afraid there is nothing I can do about this - try asking PFC. John

If that file is not present, the default/in-built assignments/macros are used, and a message is logged just to say that that file cannot be found. Yes - you add your own macros to that file to overwrite/change the default action - see the PFChidDLL User guide for details. However, the macro names are not being logged and you are only getting write errors. I can't really help with this, as my knowledge on PFC equipment/drivers is limited. I will ask Pete about this (as well as your issues with the com device in your other post. Unfortunately he is on holiday this week, so this won't be until next week.

Are they not just a press and a release? Or are these 2 pulses phase-shifted? If so, see the Advanced User guide pm page 22: I suggest you read that chapter anyway, If they are really sending two presses, maybe try adding a condition on the button flag, as this would be set on the first press and cleared on the second. And if all else fails. you can always use lua to act on every other button press.

You can try the following offsets which hold the GENERAL ENG FUEL USED SINCE START indexed simvar for 4 engines: 0x090C. 0x09A4, 0x0A3C. 0x0AD4

Please see the provided documentation.

No point attaching then....

What ini file? Can you please attach that. As I said, not owning or being familiar with PFC devices or the driver, it is very difficult for me to advise in this. However, I will take a look further tomorrow to see if I can see anything. Are you using the updated driver that Pete provided a short while ago (2-3 months) so that the radio stack could be recognised when using MSFS / FSUIPC7?

As your question is related to FSUIPC7 / MSFS, please use the sub-forum for this. I have moved your post to this sub-forum. Your FSUIPC7.log file shows that you did not load an aircraft and get ready-to-fly. Please do this and try again - I think this maybe a pre-requisite before assigning to PFC hardware, but not sure.... It won't - control of such devices is pre-programmed in the dll, and can be overwritten using the PFC.mcro file, which you seem to be using: Please attach that file also if it contains anything, but I suspect it is empty.... You also seem to be using an older version of the PFChid64.dll, 5.141 - the latest version is 5.143, so please update and ret with that version. The PFChid User Guide also says: So the dll hasn't been tested on your device as far as I am aware, The error messages in your log are strange and worrying as well... I suggest you read the User Guide and try again, with an aircraft loaded, and set some logging options for your PFC device, mainly LogMacroNames=Yes This should hopefully show you the macro names called when you press the buttons, which you can override in the PFC.mcro file if needed.

As you are using an unregistered version, so no devices/joysticks will be scanned and there are no facilities for assignments. Assignment functionality is only available in the registered version. You can try the trial license (currently expired, I will update tomorrow) but if elite support say they need to update the driver then this probably won't work wither, but you are welcome to try.

But why would you want to use them when not in flight? This is just how those presets work. As I have said, I cannot help with individual presets, I just provide the mechanism to assign to presets and have these sent to the FS for action. I consider this topic closed. If you want to discuss the FBW presets, please do this on either the FBW or MobiFlight discord channels.

I moved your post to the FSUIPC7 support sub-forum - please take care to post in the correct forum for your issue / product. I think your issue maybe aircraft dependent - and certainly dependent on the FS you are using. As this dll is FS-agnostic, I cannot change its behavior for a specific FS or aircraft. In fact, I only provide these dlls and cannot provide any more information than that is given in the provided User Guide, sorry. However, the User Guide does say: so you should be able to re-program the buttons to do this - I do not fully understand when you say "but since the PFC hardware uses that button in the hardware to switch between the flight timer and standby frequency (as it does in the real aircraft unit) it causes problems with the hardware", as the User Guide also says: So if you re-program the action in FSUIPC, the default action should be bypassed. John

What problem are you referring to? Not sure what that version is, but always a good idea to check and install the patches if applicable - SP1 and SP2, if they are not included in the DVD version. So, your issue is that your throttle axis is nit recognised? Can this be seen in FSX? Can you please show me your FSUIPC4.log and FSUIPC4.ini files.

Yes...! Glad you got it working...

👍

I will update tomorrow....

I really can't say as I don't fully understand what you are asking, but I doubt it very much - FSUIPC is not a platform to implement aircraft models. That is a completely different layer which I know nothing about, sorry. If you are modelling the A320, I suggest you talk to FBW or take a look at their work, and join their Discord server, John