John Dowson

Yes - Byte x 2 means two single bytes, each byte containing a boolean (1/0) value. You would normally read each byte separately. That offset holds three states, as specified in the document: 0: CLOSED 1: OPEN (dim) 2: IN TRANSIT (highlighted) Other byte offsets also hold multiple states - check the Notes column in the PMDG Offset mapping document. It is a 1 byte value, but not a boolean - a single byte can hold up to 256 values (usually 0-255 when unsigned but -128 to +127 if signed). John

You really need to post your FSUIPC7.ini and FSUIPC7.log files if you have such problems. However, there are currently many issues since the SY10 update. There is a beta available that fixes some of these issues, but not all, available here: There are still some issues with axes assignments. At the moment, if you have assigned an axis using 'Send to FS as normal axis' and have also calibrated in FSUIPC, then this causes errors. For such axis assignments, you have remove/delete the calibration. John

No need to post logs if its working...

FSUIPC is not compatible with any version of XPlane - you need XPUIPC which is from a different developer. John

Did you try setting the FSUIPC7.exe compatibility property setting 'Run this program as administrator' ?

@Cloud8.5 Your files show that you are using an old and unsupported version of FSUIPC7 - 7.3.6. The current released version is 7.3.8, and the latest beta with the SU10 fixes is 7.3.9h. Please update to the latest beta (available from the Announcements sub-forum) and try again, then post if you have issues. John

@amicodepla Sorry, made the same mistake again - had the parking brake set! The toe brakes work both when assigned to send direct to fsuipc calibration and calibrated, and also when assigned as send to fs without calibration. There is one strange thing with your toe brake assignments: You are scaling with '*-1' to reverse. But, as you are assigning to FSUIPC7 calibration, you shouldn't do this - you should reverse in the calibration panel. Can you remove those '*-1' and calibrate to reverse instead and try again. Also, check that the parking brake is released!

I will check this as well.... Checked this and none of the toe brake assignments seem to be working with the C172. I can also check if directly updating the Brake Left/Right Position has any effect... Id it possible to apply the toe brakes in the VC with the mouse? Would be helpful if that was possible (so that I can monitor values), but doesn't seem so...

Checked this now and still working fine...

Yes, should be the same...but you could possibly have been using the DC-6...! As I say, always better to specify the aircraft, as well as the provider.

Ok, I will check this in the PMDG - presume you mean the 737-700? Better to specify the exact aircraft to avoid confusion. Anyway, I only have the 737-700 from PMDG, and don't have the Fenix, so will check in that. I will check this as well.... John

Now I am confused....are you saying that you are not using profiles? Thats fine if you only fly one aircraft, but is really needed, especially in MSFS, if using various aircraft. You have now set the profile aircraft name to 'FBW' - this will not catch the FBW aircraft as that string is not in the name, and so your general assignments that will be used. And as the A320ParkBrake.lua is only started in the profile, it won't be started. Do you want to use profiles or not? I really suggest you do, if you have any intention of using any other aircraft with FSUIPC7. Decide on that, and then we can correct your FSUIPC7.ini accordingly. John Sorry, missed this: I think only the Steering Set axis is exposed via SimConnect, but will check....

@Chad P Btw, when you create a profile (not based on an existing profile) you are asked id you want to import the general axis assignments. If you say yes, then the general axis assignments are copied to a profile-specific one. If you say no, an empty profile axes section is created. Your ini shows the profile but no profile axes section, which is why you are having these issues. I cannot see how this can happen unless you manually deleted this section from the ini. If you didn't do this, have you any idea how this happened? I have tried to reproduce but can't... John

This should certainly not happen...but your FSUIPC7.ini file is rather strange. You are using an FBW profile, but have no axis section for that profile. They are probably 'disappearing' as you have the profile-specific checkbox checked and there are no axis defined for that profile. You also have your LeftBrake assigned, but not the RightBrake. Can you please try the attached FSUIPC7.ini. In this version, I have duplicated your axis assignments to your profile, as well as simplifying your profile aircraft names to a simple substring 'Airbus A320neo'. Try this ini, and add your RightBrake. You should also load another aircraft and add the RightBrake assignment to your nin0profile axis assignments, so that when you create other profiles it will get imported. I see you are also using the A320ParkBrake.lua - is that working for you? I ask as I have had reports that this is no linger working, but have not had time to look into this yet... John FSUIPC7.ini

They really shouldn't... can you show me your FSUIPC7.ini file and an FSUIPC7.log generated with logging for Buttons & Keys and Events activated - load your aircraft, press an assigned button/switch or two, then exit.

You will find that in the Utils folder of your FSUIPC7 installation. What do you mean by this? Your assignments are stored in the FSUIPC7.ini file, and possibly another .ini file under the Profiles sub-folder if using 'profiles in separate files'. If you change the installation location, you will need to copy across from your original installation folder. Bur these files are not touched when you re-install,

Also I see you are still using 7.3.8 - you need to use the latest FSUIPC7 beta, currently 7.3.9h, with SU10 - available here: John

Try the development version then... I will look at this, when I have time (i.e. maybe in a couple of days), but as FBW does not even support the development version. I doubt there is much I can do... John

If you want/need to calibrate, try assigning with 'send direct to FSUIPC7 calibration'. 7.3.9h mainly contains fixes relating to lvar/hvar discovery and loading and shouldn't affect any axes assignments (i.e. no changes there). John

Did they work in the previous version (and what was that version)? Can you try 7.3.9h (latest beta) and if you still have issues, show me your FSUIPC7.ini and FSUIPC7.log files, the latter generated with Axes Controls logging activated, load your aircraft, release the parking brake and push each toe brake through its full range, then exit FSUIPC7. As for the A320 parking brake script, I will look into that. Could it be that the toe brakes weren't working as the parking brake was set due to this issue? John

Yes, I know - it is the SU10 release / SDK 0.9.3 release that has broken certain things, and you need to review your axes assignments accordingly for the moment... What does thus mean? I need to see your FSUIPC7.log file as well as your FSUIPC7.ini to start with.... John

You are posting in a topic that is over 11 years old, and in a forum that is not for FSUIPC7. For ALL FSUIPC7 issues, please use the FSUIPC7 sub-forum. There are quite a few issues since the SU10 release, some have been fixed and others are under investigation still. I suggest you download the latest beta, available here: Is FSUIPC7 running? I am locking this topic now - for further assistance, please use the FSUIPC7 syb-forum. John

There are a few issues at the moment since the SU10 release.... How are your buttons assigned? If using lvars/hvars, then these are currently not working in 7.3.8 with SU10. There is a beta available that fixes thiis alonf with a few other issues, available here: Axis assignments don't drop, so there must be something else going on...there are various issues with axes assignments since SU10, which I am still investigating. For the time being, make sure that you have either assigned with 'send Direct to FSUIPC calibration' and have calibrated, or have assigned to 'send to FS as normal axis' but with no calibration (remove/delete if you have calibrated with this option, as that is known to cause issues). It WAS working...the SU10 release has broken many things in the SDK, especially with SimConnect. There are issues after every major SDK update. A full trial license is ALWAYS available, and I recomend that you try the software BEFORE you buy, as it says on the SimMarket sales page: As it is a digital downloaded product (with no on-line license verification), once a license is issued it cannot be revoked. This is why there are no refunds, and you are expected to try the product before purchasing to see if it is suitable for your needs. FSUIPC7 is very powerful, and essential for many home cockpit builders but it is certainly not suitable for everyone, John

Strange, but that is a problem with MSFS...you could try setting the FSUIPC7.exe compatibility property setting 'Run this program as administrator' if you are always going to run with admin privileges, Regards, John

That is correct - it is grayed-out once assigned unless you click the Clear button. Same here - most axes I have tried are working ok when assigned to 'Send direct to FSUIPC calibration' and calibrating, and also when assigning with 'Send to FS as normal axis' and removing any calibration. The only axis I have so far (haven't checked all!) found that is not working is Axis Mixture Set which always gives errors regardless. However, this is an undocumented axis in MSFS so there is not much I can do - I will probably remove this. I have been mainly working on WASM/lvar loading issues today, and have just released an updated beta 7.3.9h, so can all users with issues please update to that (see Announcements sub-forum). I will come back to looking at the axes issues tomorrow, and will review the comments again and do more testing. If you post on issues, PLEASE state which aircraft you are using, how you have assigned - either direct to calibration or send to FS as normal axis, and if using the latter please double check that you have no calibration settings as doing this no longer works. As I have mentioned before, best to check the the calibration section in the FSUIPC7.ini (either general or your profile specific section) and check that there are no entries for the axes you are using - for example, I have noticed that removing toe brake calibration can still leave zero calibration entries which currently need to be manually removed. Also maybe post your ini (and profile ini, if using) so I can check your assignments. I can test in all default aircraft and several add-ons (but by no means all!). For example, I have the JF PA28 and the throttle axis is working ok in that for me, so @Cloud8.5 must be assigning or calibrating incorrectly (show me your FSUIPC7.ini!). Until tomorrow... John