John Dowson

Did you add the simvar AUTOPILOT HEADING LOCK DIR to that offset via the myoffsets.txt file? Do you see the following entry in your FSUIPC7.log file: ? Please attach files, not pictures.

By default, in your FSUIPC7 installation folder... John

Do you have any issues with that script?

First, you posted in the User Contributions sub-forum where it explicitly states NOT for support requests. I have moved your post to the main support forum What do you mean by shortcuts? Why not just assign to the standard controls? Or if the aircraft comes with an SDK and/or custom controls, you can try using them. Is this an add-on aircraft, and if so by who? If you look in your FSUIPC Documents folder, you will see a text file that contains a list if all available controls - open that in an editor and search for the controls you need. They are all available from the assignments drop-down menu. e.g. for heading try: 65880 HEADING_BUG_DEC 65879 HEADING_BUG_INC and/or the FSUIPC added controls (see Advanced User guide p 29) 1024 Heading Bug Dec Fast (–10) 1025 Heading Bug Inc Fast (+10) There are similar controls for SPD and ALT. John

Not 100% sure, but it will probably be missed, but this depends when the event flag on the button press is cleared - either when the function is called (in which case the 2nd button press will be registered) or when the function is finished (in which case it will be missed). I think its the latter, but should be easy to write a simple test lua to clarify if needed. Anyway, the function should really finish before the second button press, and you can also use button repeats. John

You have been using the trial license since April. If you want to continue using FSUIPC7, please buy a license. I have stopped providing one available to download as this is being abused by people, like you, who are continually using the trial license instead of purchasing. Your request is therefore denied. John

Finally... No. Have you enabled and configured/calibrated these? Please read the PFC.dll documentation: Please ALWAYS check the documentation before posting. I do not have any PFC devices - any questions you ask I will just read the provided documentation for an answer. It will save us both time if you read the documentation before posting for support. John

I have sent you both a trial license via PM. John

No, the function will complete,

No you did not... The PFCcom64.dll file should be in your FSUIPC7 installation folder, not in a sub-folder. it is not in the correct location.... It also looks like you have saved the FSUIPC7.key file as FSUIPC7.key.txt - please check and correct this, This is probably also related to your windows explorer settings which you should change... Please also change your windows explorer settings to show the extensions of known file types. This will help you to identify your files when needed. This is explained both in the FSUIPC7 installation and registration manual and in the 'If you cannot see the DLL...' text document under your PFCDLL folder.

ok, didn't know it was called that! No idea what could have caused this, but not FSUIPC.

Yes, but use your profile name ([Auto,xxx] where xxx is your profile name) or if not using profiles then just [Auto]. Please read the documentation - how to auto-start luas is explained there - as well as most other functionality! John

Your log shows: Why have you installed the hid/usb driver and not the com/serial driver? Please remove that and install the pfccom64.dll driver. I think you also need a registered version of FSUIPC7 - although not sure.... Do you not have a license? If not, try the trial one attached - just save it to your FSUIPC7 installation folder. Also, please only attach files after you have exited FSUIPC7, not while it is still running. John

Trial licenses sent via PM. John

Rather than using offset 0x07CC for the heading,, it is better to add the AUTOPILOT HEADING LOCK DIR simvar to a different offset, so that this doesn't trigger the default behavior associated with that offset. To do this, you need to use the myoffsets.txt file. Create this file (in your FSUIPC7 installation folder) if it doesn't exist, and then add the following line: 0xA000, 2, AUTOPILOT HEADING LOCK DIR, F64, degrees This will add that simvar to offset 0xA000. You can change this to another free-to-use offset if already using this one. you then need to change/update your VB code to use this offset for the heading. Then you will need a simple lua script to update the heading when this offset changes value. The script should be auto-started using your profile-specific [Auto.xxx] section, e.g. [Auto.FBW-A32NX] 1=Lua FBW-Heading The lua file (also attached) is straight-forward, and just sends the offset value using the appropriate control, when the offset value changes: FBW-Heading.lua Please try this and let me know if you have any issues. John

Your comments are extremely small and difficult to read - can you please try and post them as plain text in future. Please read the documentation on how to use presets, in the Advanced User guide, in the WASM section. Presets are made available via the mobiflight events.txt file, and you can also define your own in a file called myevents.txt. They are loaded automatically and available for assignment when you select/check the Select for Preset checkbox. The events.txt file is the MF file at the time of release, so is always slightly out-of-date compared with those available on the MF HubHop site. If you want to use a newer preset, you can download the events.txt file from the MF HubHob site and use that to replace the one in your FSUIPC7 installation folder. This is all explained in the provided documentation for FSUIPC7.

You have to do more than that. As i said, please read the provided documentation on how to configure FSUIPC to use the PFC driver - the PFC DLL User Guide. Once you have read that and configured correctly, if you still have problems then please show me/attach your FSUIPC7.ini file, FSUIPC7.log file and PFCcom64.ini and PFCcom64.log files. But there is no point in attaching these until you have at least read the documentation and tried to configure this yourself.

Isn't it obvious: ?

Have you installed and configured the PFC serial driver for FSUIPC (available from fsuipc.com)? If not, please do that - and make sure that you have read the documentation...

Can you explain what you want to achieve? As I said, you can use either the Heading Bug inc dec controls, or the custom events. You will need a lua script that uses the A32NX.FCU_HDG_SET control, via calculator code, if you want to use an offset to control the heading bug. If you can let me know exactly want you are trying to do, I will look into it, but probably tomorrow now. John

What is AAU2? What weight data from FSUIPC are you using? Have you tried monitoring the weight offsets used, to see if they hold the correct data? I have checked a few of these offsets and they seem correct in the 787-10: 0x1400: PAYLOAD STATION WEIGHT:1 - 170.0 0x1420: PAYLOAD STATION NAME:1 - "Pilot" 0x1430: PAYLOAD STATION WEIGHT:2 - 170.0 0x1450: PAYLOAD STATION NAME:2 - "Co-Pilot" ... 0x30C0: TOTAL WEIGHT: - 440876.40625 0x30C8: TOTAL WEIGHT - 13702.8886714 Not sure why they would say this. Nothing has changed in FSUIPC as far as the weight data is concerned. If this occurred after an aircraft update, it will be the aircraft update that caused this. If you need further assistance, please provide more information, i.e. which offsets are being used

I can only seem to change the heading with the Heading Bug Inc/Dec controls. The fast versions of these controls do not work either. Both the fast versions of these controls and writing to offset 07CC use the Heading Bug Set control - this control doesn't seem to be working in the FBW A320. However, it is probably better to use the FBW custom events (or presets). These events are provided in a file called flybywire-aircraft-a320-neo.evt located in your EventFiles subdirectory. Copy or move this file to your FSUIPC7 installation folder (i.e. up one level) to use. Once installed, you will have the following custom events that you can use for the FCU heading: A32NX.FCU_HDG_INC A32NX.FCU_HDG_DEC A32NX.FCU_HDG_SET A32NX.FCU_HDG_PUSH A32NX.FCU_HDG_PULL If you want to control the heading via offset 07CC, you would need a lua script to monitor this offset and send the value (when changed) to the sim using the A32NX.FCU_HDG_SET event, or, probably easier, using calculator code. If you want to do it this way, let me know and I can look into providing a script for you.

You have additional logging activated - check and clear your Log->Custom value. Looks like logging for custom value x10 (all simconnect events) The DontLogThese ini parameter only applies to standard event logging,

No, its read-only... Ok, that is strange What version of FSUIPC7 are you using? Make sure you are using the latest version, 7.3.21: 0x07CE 2 AUTOPILOT HEADING LOCK DIR:3 Responded Autopilot target heading value, as degrees*65536/360 Not sure when that was added but was quite a while ago... As I said, I am no A320 expert, but I can take a look for you tomorrow and report back. John

Which version of the FBW A32NX are you using? I am no expert for the A320, but I think this can depend on the AP mode (managed or selected). If the Autopilot Heading lock is set (offset 0x07C8) then you cannot update this value. You could try offset 0x07CE (target heading), or look at the available MF presets to see what they use to control the AP heading value, and use that - either the preset directly or the lvar (or whatever the preset is using). I will update the title and maybe some other FBW users can help.