Delta14Sierra

Problem resolved. Thank you so much for sharing your expertise.

John, Thank you for your assistance. From my FSUIPC7.log (see attached): 281 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1) After rebooting, ALT-F still does not open FSUIPC7. If I ALT-TAB while in MSFS, I can see that FSUIPC7 is running and connected to MSFS (see attached image). FSUIPC7.log

I installed FSUIPC 7.4.11, but noticed that I was unable to access the user interface via ALT-F. Thinking there might be an issue with it, I reinstalled 7.4.10, making sure my user registration info was correct, but still have the same problem. FSUIPC splash screen appears when loading MSFS, but ALT-F does not bring up the FSUIPC User Interface. Furthermore, if I ALT-TAB, FSUIPC shows that it is connected to MSFS, but it is greyed out. What do I need to do to gain access again to the FSUIPC user interface? Have a great day! Thank you.

John, Thank you so much for that instructional insight which now removes the period when it is the fourth character. But then I found that my GF-166 display was showing 00.0 - 09.9 when the cockpit DME shows 0.0 - 9.9. So I applied your insight and included an elseif statement which now also strips the leading zero. function Distance1(offset,value) -- NM1 if (string.byte(value, 4) == 46) then -- is 4th character a period (46)? miles1 = string.sub(value, 1, 3) elseif (string.byte(value, 1) == 48) then -- is leading character a zero (48)? miles1 = string.format("%1.1f",value) else miles1 = value end prevswitch = -1 -- updates Distance end There probably is another way to strip the leading zero, but this replicates the cockpit DME on my GF-166 which is what I was hoping to accomplish. Thank you for sharing your expertise. Dan

I thought had a solution, but after testing, it did not work.

I am using a Goflight GF-166 as a DME which includes the following Lua script... function Distance1(offset,value) if (value <= "100") then miles1 = string.format("%3.1f",value) else miles1 = string.format("%s",value) end prevswitch = -1 -- updates Distance end event.offset(0x0C29,"STR",4,"Distance1") -- DME1 Distance When less than 100 miles, miles1 displays both miles and tenths/mile (e.g., 0.5 7.5 10.5 99.9 ), as it should. However, when more than 100 miles, miles1 displays just the miles as a whole number, but the decimal point remains (e.g., 100. 105. 115. ). Is there a way to rid of the decimal point altogether when more than 100 miles?

Thank you!

FYI...Download link is showing FSUIPC7 v7.4.3, but install says it is FSUIPC v7.4.2.

John, Thank you so much for your kind assistance. I have BU0836X-2.lua working and am focusing on getting it dialed in before I work on ButtonBox.lua. In FSUIPC.ini, I have added the line: IgnoreThese=H.10, H.11, H.12, H.13, H.14, H.15, H.16, H.17, H.18, H.19 It correlates with the 5 rotary encoders on this board. However, I am finding it a challenge in Button & Switch Assignments to differentiate between which is fast and which is slow. No matter how fast or slow I turn the rotary, it seems to be finicky as to which button number it provides me for assignment. Here is what I currently have, but I have also tried flipping the fast and slow button assignments in each rotational direction. 132=P64,17,C1027,0 -{vor1 obi inc fast}- 133=P64,16,C65663,0 -{VOR1_OBI_INC}- 134=P64,15,C65662,0 -{VOR1_OBI_DEC}- 135=P64,14,C1026,0 -{vor1 obi dec fast}- Either way, I get an inconsistent response between fast and slow movement of the VOR...sometimes fast adjustment when turning slow, and slow adjustment when turning fast. My assumption is that this has to do with the FastTimeLimit = 60 and Pollrate = 20 settings. I have been trying different values (increasing the FastTimeLimit, and decreasing the Pollrate), but I am struggling to find a sweet spot. I have been making adjustments to BU0836X-2.lua while in FS2020, but I just am not getting any feel for whether I am adjusting in the right direction. Any insight as to make this process easier would be most appreciated. Once again, thank you for bearing with me. Have a great day! Dan

John, I made the offset change to the second script and tried the various VID/PID values. I ran each script separately. I do not find the message "Could Not Open HID" (I assume it would appear in the INI file), nor does Logging Lua Plugins or Logging Lua Separately produce any error messages for either of the rotary scripts. Where do I find the new fast/slow virtual buttons? Thank you for your patience and kind assistance. Dan FSUIPC7.ini FSUIPC7.log

John, Thank you so much for your prompt reply and direction. I have added the [Auto] section along with Lua entries and corrected the <MISSING JOYSTICK> entries/associations in FSUIPC.ini. I have also tried using both 0 and 1 for the Device number of each board in their respective Lua scripts. However, I still do not get the intended outcome with the rotaries. Furthermore, when I add the IgnoreThese entry under [Buttons], I get no response at all from the rotaries in Buttons & Switches Assignments. Observation: While troubleshooting, I noticed that although one of my encoders is wired on the ButtonBox board to B21 and B22, yet it shows up in FSUIPC as J.20 and J.21. The same pattern applies to the rest of my encoders. Is this because FSUIPC starts numbering with 0 rather than 1, or could this be part of my issue? Using the Bodnar Encoder Configuration application, I have set up the connected encoders as 1:2 with a 56ms Pulse Width. Any further insight would be most appreciated.

John, I am stuck in trying to implement the rotaries.lua on 2 Leo Bodnar boards with a total of 11 rotary encoders. I renamed the rotaries.lua script to reflect each of the Bodnar boards (BU0836X-2.lua & ButtonBox.lua; see attached). I adjusted the Vendor/Product/Rotaries parameters to reflect the specifics of each board (5 encoders with BU0836X-2; 6 encoders with ButtonBox), however, I am uncertain if I have the correct Device number for each board (I also have another BU0836X-1, but it does not have any encoders assigned to it). The boards show up in both FSUIPC.log and FSUIPC.ini (see attached). However, I do not see any change in speed when turning the encoders. When I include IgnoreThese=H.10, H.11, H.12, H.13, H.14, H.15, H.16, H.17, H.18, H.19, J.20, J.21,J.22,J.23,J.24,J.25,J.26,J.27,J.28,J.29.J.30,J.31 under [Buttons], each of the rotary encoders no longer show any interaction under Button & Switch Assignments in FSUIPC and I am unable to reassign the encoders to their respective assignments. I am at a loss and am trusting you could help me sort this out. Respectfully, Dan FSUIPC7.log FSUIPC7.ini BU0836X-2.lua ButtonBox.lua

I have simplified things to the following which works just as I had hoped. Again, thank you, everyone! function VS_Hold(offset, value) if (value > 9900) then value = 65536 - value value = "-"..value end gfd.SetDisplay(GF166, ID, 0, value) end event.offset(0x07F2, "SW", "VS_Hold")

Thank you, everyone! Works both as UD and SW. I have left it as SW. Blessed Easter! You made my day!

In Lua, I am able to get the ascent value of the AP Vertical Speed Hold Var (0x07F2) to display correctly in the left window of my GoFlight GF166 (see Lua script below) However, when adjusting for a descent value, I get a value of 65436 for -100, and that value reduces by 100 for each subsequent negative value (e.g., 65436, 65336, 65236, etc.). How do I get the negative value to display correctly (e.g., -100, -200, -300, etc.)? Any help would be most appreciated. function VS_Hold(offset, value) gfd.SetDisplay(GF166, 1, 0, string.format("%4.0f",value)) end event.offset(0x07F2, "UD", "VS_Hold")