zetato

Pete, you're on the right way! At the moment I had a sure improvement after setting the delay value to 100 ms (I was expecting the opposite reducing that but.....) There are already some self changes in selection, but now AP/C functions are usables also with the "hard to convince" F1 ATR Autopilot. I'll continue to test now and then tomorrow evening, if you have some other ideas let me know Many many thanks for your effort, I sure was not able to write the Lua plugin, but reading it I understood most of what you've done! Thank also to Andy, supporting me in this tests, I know MCP is the best, but when I get M-Panel, money were not enough for the bigger brother. Anyway I'll continue to test, and sorry if will be back again to disturbe you both, you've been very kind :D If you need some test, explanation or log from me for any purpose write me immediatly! Mauro

Oh, sorry for the late, I was away. I'll try immediatly and will give you a feedback asap. Thank you both for now! :D

Ok, will do this afternoon!! Thank you :wink: Mauro

Hi Andy, happy to see that you already read this discussion. So do you think to have mode to speak directly with the software developer? Do you think is needed for me a contact with Tech support or can I wait some news from you? I'm always ready for any test, and thank you for all :wink: Mauro

Ok Pete, so like supposed the M-Panel (maybe cause a bug in the firmware) take care about the continuos V/S setting coming from F1 ATR Autopilot. I was intending "Engaging Autopilot" Yes, I think so, and the same thing happens on E-Jets from Wilco if I use the FLCH (Flight Level Change) function on the Aircraft panel, in fact, in that case on the M-Panel display, the preselection changes itself between SPD, ALT and V/S dinamically. In fact, at that moment I had no vertical mode engaged, only A/P master, I think anyway it works as "Attitude Hold" Yes, V/S and AlT are changed due to an uncontrolled pitch attitude (I was checking on second monitor the log console), but I'm not able to see the log of my keypress on COM/HDG button. Will do Pete :wink: Many thanks to your attention! In case I'll try to block it (hoping to be able), and yes, I agree that M-Panel is really a nice product, and thats the reason that is forcing me to find a way for use it also with add-on aircrafts :D Thank you for now, I'll mantain you informed about any new! Ciao Mauro

Hi Pete, here some part of the log file: In this point I'm in flight and inserting AP 444431 VRI command APMMST+ trapped as Joy 260 Btn 8 Press (On) 444462 Button changed: bRef=0, Joy=260, Btn=8, Pressed 444462 [buttons] 1=H260,8,K90,8 444462 SendKeyToFS(0000005A=[Z], KEYDOWN) ctr=0 444478 Sending WM_KEYDOWN, Key=90 (Scan code 44), Ctr=1 444509 KEYDOWN: VK=90, Waiting=0, Repeat=N, Shifts=0 444509 Macro: mouse action="F1ATRB.DLL":X8110*Xa100 444509 .. This key is programmed in FSUIPC4 'Keys' options 444509 *** EVENT: Cntrl= 65792 (0x00010100), Param= 0 (0x00000000) AUTOPILOT_ON 444509 *** EVENT: Cntrl= 66069 (0x00010215), Param= 0 (0x00000000) YAW_DAMPER_ON 444540 VRI com3 <--- DSP4 84% [to Device] 444618 *** EVENT: Cntrl= 66124 (0x0001024c), Param= 99900 (0x0001863c) AP_ALT_VAR_SET_ENGLISH 444618 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2204 (0x0000089c) AP_VS_VAR_SET_ENGLISH 444618 *** EVENT: Cntrl= 65808 (0x00010110), Param= 0 (0x00000000) AP_ALT_HOLD_ON 444852 VRI com3 <--- DSP4 84% [to Device] 444930 *** EVENT: Cntrl= 66036 (0x000101f4), Param= -3000 (0xfffff448) AP_VS_VAR_SET_ENGLISH 445117 VRI com3 <--- DSP4 84% [to Device] 445226 *** EVENT: Cntrl= 66036 (0x000101f4), Param= -3000 (0xfffff448) AP_VS_VAR_SET_ENGLISH 445445 VRI com3 <--- DSP4 84% [to Device] 445507 *** EVENT: Cntrl= 66036 (0x000101f4), Param= -3000 (0xfffff448) AP_VS_VAR_SET_ENGLISH 445726 VRI com3 <--- DSP4 84% [to Device] 445788 *** EVENT: Cntrl= 66036 (0x000101f4), Param= -3000 (0xfffff448) AP_VS_VAR_SET_ENGLISH 446022 VRI com3 <--- DSP4 83% [to Device] 446084 *** EVENT: Cntrl= 66036 (0x000101f4), Param= -3000 (0xfffff448) AP_VS_VAR_SET_ENGLISH 446318 VRI com3 <--- DSP4 83% [to Device] 446412 *** EVENT: Cntrl= 66036 (0x000101f4), Param= -3000 (0xfffff448) AP_VS_VAR_SET_ENGLISH 446630 VRI com3 <--- DSP4 83% [to Device] Note that the string AP_VS_VAR_SET_ENGLISH is always present in all the log parts when there are no other parameters to be displayed So far this point seems all ok on FSX an M-panel. Now I'll select AP/C mode on 4 way switch, and all is already ok. 460234 VRI com4 <--- FUNAPCTL [to VRI Driver] 460234 VRI com3 <--- DSP4 84% [to Device] 460374 VRI com3 <--- FUNAPCTL [to Device] 460468 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2899 (0x00000b53) AP_VS_VAR_SET_ENGLISH 460530 VRI com3 <--- SPD060 [to Device] 460733 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2806 (0x00000af6) AP_VS_VAR_SET_ENGLISH 460827 VRI com3 <--- ALT99900 [to Device] 461029 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2704 (0x00000a90) AP_VS_VAR_SET_ENGLISH 461123 VRI com3 <--- VVS+270 [to Device] 461310 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2588 (0x00000a1c) AP_VS_VAR_SET_ENGLISH 461451 VRI com3 <--- VVS+260 [to Device] Now, here in the middle I tried to preselct HDG mode pressing the COM/HDG button, but each time I released that button the "underscore" sign has moved itself below the VS indication on display. The log seems have no trace of what I tried to do. 476583 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2486 (0x000009b6) AP_VS_VAR_SET_ENGLISH 476895 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2482 (0x000009b2) AP_VS_VAR_SET_ENGLISH 477175 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2477 (0x000009ad) AP_VS_VAR_SET_ENGLISH 477425 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2472 (0x000009a8) AP_VS_VAR_SET_ENGLISH 477737 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2468 (0x000009a4) AP_VS_VAR_SET_ENGLISH 478002 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2463 (0x0000099f) AP_VS_VAR_SET_ENGLISH 478299 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2458 (0x0000099a) AP_VS_VAR_SET_ENGLISH 478579 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2453 (0x00000995) AP_VS_VAR_SET_ENGLISH 478829 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2448 (0x00000990) AP_VS_VAR_SET_ENGLISH 478876 VRI com3 <--- VVS+240 [to Device] 479125 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2444 (0x0000098c) AP_VS_VAR_SET_ENGLISH 479406 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2440 (0x00000988) AP_VS_VAR_SET_ENGLISH 479749 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2437 (0x00000985) AP_VS_VAR_SET_ENGLISH 479999 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2435 (0x00000983) AP_VS_VAR_SET_ENGLISH 480280 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2435 (0x00000983) AP_VS_VAR_SET_ENGLISH 480561 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2435 (0x00000983) AP_VS_VAR_SET_ENGLISH 480857 *** EVENT: Cntrl= 66036 (0x000101f4), Param= 2435 (0x00000983) AP_VS_VAR_SET_ENGLISH I was no able to select HDG mode at all, cause the selection was always moving to VS without give me the time to press the rotary knob. Let me know if those logs are showing something of interesting, and in case, tomorrow evening, I can retry until able to insert HDG SEL to see whats yhe log will record also after that action. Thanks. Mauro

Thank you Pete, as soon as I'm able to perform some tests will record a log for the few moments the problem appears and then I'll post to have your opinion :wink: I'm already in contact with Andy from VRI (I know he reads this forum too), and he suggested me to contact you, but anyway, a "brain conjunction" maybe will found something interesting also for other users with similar add-on issues :D See you soon!

Pete, what I'm trying to tell (apologize for my bad English), is that if I select HDG on M-Panel AP/C section, than I press the knob to activate, it works well, but just a little later, moving, or also without moving the knob to change hdg, often, the selection on the M-Panel changes itself from HDG mode to SPD mode or VS mode, apparently depends from which manouvre the airplane is performing, the values on FSX panel are correct, but if I'm rotating the knob to change heading, and the selection move itself on M-panel on Speed, the result is that I'm thinking to continue to change heading, but if I do not look at M-panel in that moment, I'm in fact changing the speeed request. I know that, but maybe this could be the only solution, and I'd like to try. Sure it works perfectly with default airplanes, and I know this is a F1 ATR Panel issue, I'm just trying to have the best possibility to use this hardware also with my add-on aircraft. Thats not the point, I can simply not refer to the M-Panel display regarding non matching value, but what I'd like to optain, is a way to avoid that M-Panel is forced (by some feedback signal from F1 ATR gauge I suppose) to change itself mode during the normal use. Please, let me know if this is what is possible to do with the filter commands, and it's not only a way to avoid to display the values of parameters but without any effect on the signals are forcing the selections on M.Panel. Really thank you. Mauro

Hi Pete, this is the first time for me in this forum, and I'm writing cause having some troubles trying to use my VRI M-Panel whit some add-on aircraft using the new facilities of your FSUIPC 4.60 (updated to 4.61). Speaking for example about F1 ATR72 FSX version, it seems to be not a problem to program all the autopilot functions in the button/switches section of FSUIPC, especially using the mouse macro function (the only way for some panels), but the broblem arise during the use of the programmed functions. In particular using the keys of the AP/C section of M-Panel, it happens that, for example, if I select HDG and press the rotary, the function is selected, but when I'm turning the knob to change hdg value, something from FSX came back to the panel changing my function selection that become itself SPD or maybe VS, so its impossible for me to have a steady selection of the vertical modes to operate correctly. Leaving apart the problem of the misleading of the indicated value for som parameters (I knew that possibility from VRI docs), what I'd like to find, is a way to filter maybe via FSUIPC this feedback from the simulator that is actually forcing an undesired "self preselection". I'd like to specify that if I use simply programmable keys of my Logitech G11 keyboard, all the mouse macros of FSUIPC works very well and without any problem, so I Know it's not a problem of your perfect module, but of the "closed source" program of the F1 autopilot gauge VS VRI panel, but at the moment I'm trying all the ways. I already wrote to Andy, and he saw similar problems during his tests, but had no solution from the VRI side, so suggested me to ask you if some trick is possible from FSUIPC side. If some log is needed to investigate I'll send you asap. Thank you in advance. Mauro