ark1320

Ah, a hex mask. That makes perfect sense, I should have realized that, and it explains why the offset byte value 00000001 gets toggled to 00000000, and vice versa. Thanks John. Al

Did some experimenting to see if I could figure out how assigning an input event to an offset worked ... I assigned the input event ELECTRICAL_ExternalPower_1 as an unsigned byte to an available offset A080 in the general section ( I don't fly the Longitude so I don't have a specific profile for it ) of my FSUIPC7.ini file as shown below: [InputEventOffsets] 1=ELECTRICAL_ExternalPower_1=UB0xA080 Then in the FSUJIPC7 key assignments window I assigned the U key to toggle the bit(s) in that offset as shown below: Somewhat to my surprise this worked -- after restarting FSUIPC7 the U key did toggle the Longitude's external power on and off. I defined the offset as a byte because I thought the input event goes between 0 and 1. Although this worked, there are couple of things I'm not sure about: - I found the Parameter value of 1 is required, I assume because this external power function seems to need a circuit index of 1. Or is the Parameter being used in some other way? Maybe I missed it, but I didn't see anything in the manual that explained how the Parameter value is used in an Offset operation like this. - I think of the input event as toggling between 0 and 1. But if byte A080 holds a decimal value of 1, which would be 00000001 binary, then toggling those bits with the offset toggle bits operation would give a value of 11111110 binary, not 00000000 = 0. So not sure how this all works. Al

If it helps the investigation here, I tried both of the above (assigned a different key to each one) and they both work to toggle the Longitude's external power on and off. Al

I think that would be very useful. Al

I have no experience with the Longitude, but it seems from the log file entry for the VC button that works you need two parameters both equal to 1 to turn the ext power on. The USB key function that doesn't work seems to be using parameter values of 0 and 1 (which I think is the reason for the two entries), which turns the ext power off. The SDK shows this: So, for example I found: ipc.execCalcCode(" 1 1 (>K:2:SET_EXTERNAL_POWER) ") will turn the external power on, and ipc.execCalcCode(" 0 1 (>K:2:SET_EXTERNAL_POWER) ") will turn the external power off, where the red 1 is the circuit index value (based on the systems.cfg file entry) and the green 1 and 0 are the On & Off data values. However, I subsequently noticed there is an existing FSUIPC7 Preset called LONGITUDE TOGGLE EXTERNAL POWER SWITCH -- why not just assign a key to that (with no repeats)? Also, be aware that not all sim parking places/gates have external power available. Al

Hi John, Just curious on how you make use of the open console window as suggested above. Entries in the window go by so fast I'm not able to really see what is happening. Is there something I should be doing to make better direct use of an open console window? Or is the idea just that if it looks like maybe something happened in the console window when you activated a button or clicked with the mouse, then you should go open the log file to see if you can find something related to your action? Thanks, Al

Yes, of course! Thanks for catching that.

John, How does the control ipc.control(0x1151) work? Does it automatically detect if auto-save is active and if so, disables it. But if auto-save is disabled, the control will activate auto-save? Or do you write a 1 or 0 with the control to toggle auto-save on and off? Is there a way within a Lua script to detect if auto-save is running (active)? Thanks, Al

I added ignoreDevice=0xFFFF,0xFFFF into the [Joy Names] section of the FSUJIPC7.ini file and then reran the FSUIPC7.7.4.12 installer and started the sim. The Fulcrum yoke worked. BTW, the Logitech joystick was not plugged in, so that's why it was "missing". Al FSUIPC7.ini FSUIPC7.log InstallFSUIPC7.log

John, The above FSUIPC7.exe file you posted has fixed the Fulcrum yoke issue for me. Thank you. Does this give you the info you need, or would you still like me to go back and reinstall ver 7.4.12 and then insert IgnoreDevice=0xFFFF,0xFFFF into the [Joy Names] section of the FSUJIPC7.ini file to see if that works also? Al

For some reason the latest version of FSUIPC7 will not recognize my Fulcrum yoke, so the FSUIPC7.ini file shows "Missing Joystick". I have had this yoke for well over a year and this has not been a problem before. If I use an older version of FSUIPC7.exe the yoke works as expected. The FSUIPC7.log file shows this: 422 Product= Fulcrum One Yoke 422 Manufacturer= Vitaly [mega_mozg] Naidentsev 422 Serial Number= MMJoy2-Fulcrum-03 422 Vendor=0000, Product=0000 (Version 0.1) 422 **** Ignoring device with VendorId=0000, ProductId=0000 **** What suddenly trigger this type of problem? Older log files show the Vendor and Product 0000 Ids did not cause a problem. The complete FSUIPC7.log file is below. Thanks, Al FSUIPC7.log

Hmm... Interesting, I have been installing FSUIPC7 there for years without a problem. Until today I did not realize there were install options between using MSFS .bat and the EXE.xml file. I guess previously the installer defaulted to the EXE.xml option which I use, but now defaults to using the MSFS.bat file. I only included my MSFS.bat file above because I saw you had requested it from a previous poster -- I didn't realize that was an install option. So I have selected the EXE.xml option and all is working now, thanks very much for your help. Al

HI John. I can't get FSUJIPC7 to autostart after installing ver 7.4.12. There is no FSUIPC7 entry in my exe.xml file. MSFS.bat attached. Thanks, Al MSFS.bat

An exclamation point at the start of a line also works to indicate a FSUIPC7.ini file comment, for example: ! PY,1,C66289,0 -{SYNC_FLIGHT_DIRECTOR_PITCH}- no longer used I have been using the ! to comment FSUIPC.ini files for years, but now can't find a reference to it, and don't know where I first saw this. 🤔 The # stands out better than the ! so maybe I will replace all the ! with # to comment out whole lines, and use the ; just for inline comments as I do now. Thanks for the info, John. Al

Generally, Avars and Lvars require the > only if you are trying to write (store) a value into them. K events do usually have a > before the K. In this case I think of the > as meaning "activate" the event. Sometimes, but NOT in presets or calculator code, the > symbol will be replaced with > meaning "greater than". I'm not sure what the 60 represents in the above, but note that one radian is about 57.29 degrees, so 10 degrees is about 0.17 radians. Also, often you can change the units a variable uses, so you may be able to write the Avar (A:ELEVATOR TRIM POSITION, radians) as (A:ELEVATOR TRIM POSITION, degrees) which may be more convenient in your particular application. Al