Adri1

John, Sorry for my late reply. great ! your settings work perfectly ! I start to see how it works now. thanks a lot for your great support as usually ! BR Adrien

John, Alright, thanks, i thought wrong with Lvar. For me it was a better way to access to aicraft parameters with more options and work only by writting the goods values, but i didn t see that like a second/third strategy in case of standard control and preset don't work and where is not as simple as "just write the good value" in some case Ok I have finally used the standard control and it works ! I have some difficulties with some switchs like "landing light left and right ans nose light" where i don't fine the goods controls for indepent switch yet (i can do it via Lvar but I get the bad behaviour on virtual button), Maybe i have to take a look on presets controls and mobiflight preset now. I will take a look in aircraft code too, just for my personnal information Thanks a lot ! Br Adrien

John, Finally, this issue is not really closed, sorry. Lvar seems to work now and well mapped with my button box. But, even if lvar are well updated, (proof by value change when I list lvar from WASM), in the cockpit nothing happen for some virtuals buttons (ie: BCN STRB NAV etc) and work for some others (anti ice knob). This it s not just a fail on virtual button annimation because nothing happen on the virtual lights in the simulator too. I will transmit you my logs at the end of the day Thanks ! Adrien

John, I have just restart right now my simulator and now lvar work... I don't know by which way it work but it work. I haven't set anything more than what you ask about logs. thanks a lots for your support ! BR Adrien

Hello John, I need some support to use lvar in FSUIPC7. I have already use this kind of variable in the past but for now I cannot success to use them. I have create a profil for my 787-10 aircraft and I would like to use only Lvar. But I don't know why, it doesn't work. please find my .init file. it's strange because I can see the events with the good parameters and offset in the logs (so button works well) and well assigneted. I can set the lvar by the tool "set lvar" (so this is the good offset) but lvar doesn't work via my button... My FSUIPC folder is installed in my Simulator folder do you have an idea ? thanks ! Adrien FSUIPC7.ini

Hi John, Ok after some investigations, It looks like that my Anti-virus have blocked a file of FSUIPC... I didn't notify it yesterday. I have unblock it and now all seems to work and buttons assignements are well save in the .init... thanks Avira for headache 😠 but I keep watching on it to be sure that is well that. Thanks a lot for your help in any case ! BR Adrien

Hello, I need help for set correctly Lvariables for default A320. I have read attentively (I believed :D), the avanced users guide and try by myself to set 4 locals variables and attribute them to my buttonbox on 4 simples switchs. but I'm facing to 2 problems. -The first one is that assignements to my button are not save by FSUIPC and reseted when I restart FS2020 -The second one is that, set the Lvariable seems doesn't work. so, what I have do is: 1) enable WASM 2) look for the name of Lvariables by dump Lvar values and found the name: LIGHTING_LANDING_2 LIGHTING_LANDING_3 LANDING_2_Retracted LANDING_3_Retracted 3) set the local variables offset in .init and define them as unsigned byte type : [LvarOffsets] 0=L:LIGHTING_LANDING_2=UB0xA000 1=L:LIGHTING_LANDING_3=UB0xA001 2=L:LANDING_2_Retracted=UB0xA002 3=L:LANDING_3_Retracted=UB0xA003 4) in FSUIPC, I have assigned my switchs with parameters "Offset Byte set" 5) attach the offset A000, A001 etc to my buttons 6) set the parameters (0x01 0x02 etc) I can see in log that parameters are well sended to simulator with the good offsets but nothing happen. I don't know where I'm wrong. Find in attached file my .ini Thanks for your help ! BR Adrien FSUIPC7.ini

Hi John, good news !! it works perfectly with this version !! let me know if you need again some informations .init .log etc ... thanks a lot for your great support !! Adrien

Hello Byronb I use basic gray encoders ky-040 + MCP23017 IO expander + arduino Leonardo, not Leo Bodnar. Adrien

Hi John, Ok ! if i can do something to help you let me know ! Br Adrien

Hi John, please, find in enclose my .init so regarding index of 5 encoders : Working encoder : 56 & 57 Not working encoder 64 & 65 66 & 67 68 & 69 70 & 71 so now, I perform the following tests (PB =push button, ENC : encoder) Enc: 56 & 57 -> AP VS inc/dc => ok PB: 58 -> barometric Std Pressure => ok PB: 59 -> Speed slot index => ok PB: 60 -> Heading slot index set => ok PB:61 ->Altitude slot index set => ok PB:62 ->VS slot index set => ok ID 63 is free (nothing is wired) Enc : 64 & 65 => not assigned (because no barometric inc/dec variable is available) Enc : 66 & 67 => AP Speed inc/dc => NOK Enc : 68 & 69 => Heading Bug inc/dec => NOK Enc : 70 & 71 => AP Alt inc/dc => NOK so this is my main settings. if I try to assign Enc : 64 & 65 to ADF 1 inc/dec to test => NOK so it seems that the issue appears for ID > 62 (maybe 63 I don't know). I can connect a push button to test ID 63 (next week) if it can help you. Thanks ! BR Adrien FSUIPC7.ini

Hi john, Thanks a lots !, yes, I should see at least when they are trigged. In fact FSUIPC seems doesnt save the assignement. I have look again my own code and my debug log, I see anything different between the working encoder and not working encoder except the ID of course. And what about the maximal ID number that FSUIPC could take in account ? Because i just see something strange, if I assigne a push button (a real push button) with a lower ID than my not working (and working) encoders to these variables, it work ! Maybe there is an issue with max ID numbers. Thanks a lot for your support ! BR Adrien

Hi john, Ok i will attach .init this weekend, And yes my bad !! It is VS not MACH for working encoder, so it's normal. But as you can see ALT doesn't seem to be assigned... here is the point. Ok for button ID 82 and 80, it is strange because my encoders send for example IDs 75 and 76 or 77 and 78 but IDs is always "n" for one direction and "n+1" for the other direction... BR Adrien

Hi John, You have seen right, after "window" parameters removed, GUI work again ! So i have success to save all logs ! (find in enclosed) what i have been done is : 1) open MFS2020 2) choose an airport for departure, and then start simulation with A320 3) after simulation loaded and having take place in cockpit, I have open FSUIPC GUI and go into button and switches menu 4) first, I have rotate the working encoder to assign it to "AP_MACH_VAR_DEC", click on ok to save, and repeat the process for "AP_MACH_VAR_INC" 5) in second time I have rotate the not working encoder to assign it to "AP_ALT_VAR_DEC" and "AP_ALT_VAR_INC" with the same process than the working encoder 6) Nothing about the not working encoder seems to work after have tried the assignments 7) I came back to main menu Thanks a lot for your support ! Adrien Logs.zip

Hello John, Sorry, for my late reply but I encountered another issue since the last MFS2020 update... now I cannot open FSUIPC GUI buttons menu assignment (and I think, the others menus too) when Flight simulator is running. If I click on FSUIPC icon to show GUI, icon disappears and nothing happen. So I cannot do anything for now about logs. I think you will update FSUIPC in few days so i wait for your release to continue my buttonbox investigation 🙂 Thanks ! BR Adrien

i'm using an A320. but it's strange because with the working encoders I can set all variable of AP... so it doesn't come from a not standard control

Hello John, Thanks a lot for your support ! ok, understood about +100 offset. CW /CCW : I just mean clockwise and counterclockwise to indicate my rotatory direction, but anyway it's not important. Yes I mean by 1 press and 0 release. find in attached my .init. I cannot send you any picture or full log, they are too big. Logs.txt is not the full log, I have skipped some of them to reduce file size and I had some comments inside. hope it can help... Thanks ! Adrien FSUIPC7.ini logs.txt

Hello ! I'm facing to a strange issue with FSUIPC7 that i don't really understand. Well, i have bought FSUIPC7 for MFS2020 a few weeks ago, in order to bind my own button box to FS2020. All work fine (or almost) except 4 of my 5 encoders... . So here is the point: I would like to bind my encoders to AP x var inc / dec (x = alt/hdg/vs etc). Each direction event of encoders is see like a push button. For example, for my first encoder, if I turn it in CW, my software send button 52 = 1,0,1,0 etc.. and if I turn it in CCW it send button 51 = 1,0,1,0 etc... . All of encoders works like that. On FSUIPC side, all of my encoders events are well logged in the FSUIPC log interface. But when after binding to a AP_x_Var_dec/incr, 4 of my encoders event are not visible anymore in the log interface and nothing move into the cockpit. Only the 5th encoder event is well logged and is able to set the AP target value... . Moreover, if for exemple, my working encoder is binded on AP_alt_var_dec / incr and then I swap this variable to bind it on a not working encoders it doesn't work too. So we can conclude that it come from my software, but if i run my own debug interface i cannot see any issue, and FSUIPC7 see my encoders events before binding them, so i cannot really believed that it come from my software. Morover, if I bind them directly into MFS2020, all work ! I dont really understand. Another stuff is that all of my swichs/push button/encoder ID are see by FSUIPC with the button ID from my SW + offset of 100. For example, my software send button 42 = 1 then FSUIPC see button 142 = 1, maybe it's normal, i dont know. Thanks a lot for your support !! BR Adrien