Jump to content

zhensanmao

Members
 View Profile  See their activity

  • Content Count

    72

  • Donations

    $0.00 

  • Joined

  • Last visited

Posts posted by zhensanmao

  10. Posted

    Been thinking about the text and graphics of this document for the past few days, translated it countless times, but I really don't know how. This step is very confusing and unclear. My Logitech flight switch panel and flight multifunction panel do not work with the FWB320 of the MSFS2020. Is there a more detailed explanation?

  11. Posted · Edited by zhensanmao

    我在 simmarket 上购买了 LORBY - AXIS 和 OHS V2 FSX P3D MSFS，我下载了 vritolorbyaaobridge，我的 VRInsight MCP Combo II 现在完美支持 MSFS2020 中的 FWB320。非常感谢！
    我还有两个外设，罗技飞行开关面板，飞行多面板。
    我卸载了MSFS_Plugin_x64_Software（罗技驱动），启动sim，启动AAO。启动webapi，在Hardware下拉菜单中，勾选“saitek planel enabled”和“Ignore simelectric power”选项，并关闭EPM。结果，起落架、襟翼和所有电灯开关都失效了。. 我该怎么办？
    另外我想改一下罗技飞行开关面板、飞行多面板上的一些按键的用途，比如FWB320上的启动APU、雨刷开关、禁止吸烟、系好安全带等。支持告诉我可以转在 MIDI 模式下，但没有告诉我进入“全局 MIDI 模式”或“飞机 MIDI 模式”？或者我是否必须安装 SPAD.neXt 才能正常工作。谁能帮帮我，让我的罗技飞行开关面板和飞行多面板在MSFS2020中实现FWB320的起落架收起、襟翼收起和各种灯开关。谢谢
     

  12. Posted

    I started using FCU and MCPII in 2014 and LINDA helped me a lot. Because VRInsight stopped the driver update from July 2016, FCU and MCPII could not be used for a long time, and then I found Linda, so lucky. It works fine. But recently suddenly found that when the FCU and MCPII turn the knob, the data for altitude and heading jumps, and sometimes the data is reversed. Found joeherwig's article in Linda Support, I'm trying to buy a precision electrical contact cleaner. Remove the hex screws for the FCU, MCPII, and LINDA panels. Remove the panel and spray the cleaner on the knob. Strange things happened. Knob data results are very smooth. Much smoother than before. So I suggest. In my case, don't rush to replace the knob. Best to try an electronic cleaner first, since I didn't get a Kontakt 60, I used the alternative Lectro Kleen,. Many thanks to joeherwig for sharing.

    • Upvote 1

  13. Posted · Edited by ScotFlieger

    56 minutes ago, ScotFlieger said:

    I am not sure there is much more I can do to help. Without visibility of the Lvars, Hvars and .EVTs some functions will not work. I suggest you wait for the next LINDA module release and improvements in the FBW A32NX. Both are being worked on but this is a new environment for many of us. I am learning all the time and am pushing to support users in the near future.

    @ScotFlieger

    Many thanks to ScotFlieger. I'm eagerly looking forward to the new version of Linda for the FWB A320

  14. Posted

    41 minutes ago, ScotFlieger said:

    That is correct. Repeat earlier check by clicking on Reload LUA Engine after at least waiting one minute after FSUIPC7 started.

    Nothing has changed. Now the heading, speed, altitude, lift rate and BARO of the FCU are normal, and any other buttons cannot be mapped to the aircraft

  15. Posted

    21 minutes ago, ScotFlieger said:

    This indicates that FSUIPC7 is not finding any Lvars (zero of zero = 0/0). I suggest you need to add the LvarScanDelay=60 to your FSUIPC_WASM.INI file. See FSUIPC7 for Advanced Users document Page 45/46 on where to find this .INI file.

    Please accept my apologises but I will not download the files you sent from the VIP website for personal security reasons.

    "Is that right？”

    FSUIPC_WASM

    [General]
    ; LogLevel: Disable, Info, Debug, Trace, Enable
    LogLevel=Info
    ; LogType: File, Console, Both
    LogType=File
    ; StartEventNo: this must be the same as defined in the FSUIPC7.ini file
    StartEventNo=0x1FFF0
    ; LvarUpdateFrequency: frequency to update internal lvar values list and set in CDA
    ; Accept values: Off, 6Hz, Second, Frame, VisualFrame. If using 'Off', update timer must be active in a client
    LvarUpdateFrequency=6Hz
    LvarScanDelay=60   

     

     

     

    thanks

  17. Posted

    2 hours ago, ScotFlieger said:

    @zhensanmao just received an email from you with nothing attached. Nothing else received since yesterday. The questions above can be answered in text on this forum. No more emails needed. 

    the values under Lua Variables  (  0/0 )         Entering XMLVAR_Autopilot in the Lvar Filter box, nothing happens

  19. Posted

    41 minutes ago, ScotFlieger said:

    @zhensanmao just received an email from you with nothing attached. Nothing else received since yesterday. The questions above can be answered in text on this forum. No more emails needed. 

    I have 4 attachments with the email, one of which is a video. I start MS2020 first, then start LINDA, and then start FSUIPC7.CLICK ON RELOAD LUAENGINE, RANHOU CLICK ON LINDA TRACER.LINDA CONSOLE after a minute, the scroll bar keeps turning for 3 minutes. I don't see the values under variables. Then click on reload lvars list, then enter XMLVAR_Autopilot in the Lvar Filter box, there is no LVAR listed。Maybe I'm doing it wrong

  20. Posted

    19 minutes ago, ScotFlieger said:

    @zhensanmao thank you for the latest emailed logs. They are now showing me what I need to see.

    The problem is associated with the Lvars XMLVAR_Autopilot_Altitude_Increment which is either not present or returning a nil value. There will be a fix for this in the next module release.

    I would ask you to do some checks for me.

    • Click on Reload LUA Engine and wait until LINDA reports ready.
    • Click on LINDA Tracer.
    • What are the values under Lua Variables (eg. 1135/1135).
    • Click on Reload Lvars List.
    • What are the values now?
    • Enter XMLVAR_Autopilot in Lvar Filter box.
    • Is the above Lvars listed?

    There is basically nothing I can do for you now. You will need to wait for the module to be updated. The ALTSTEP errors can be ignored - select Debug Level less than VERBOSE and close Console.

    OK

  21. Posted · Edited by ScotFlieger

    9 hours ago, zhensanmao said:

    Hi @ScotFlieger

     

    Thank you very much, I will try again, I will reply to the email as soon as possible

     

    10 hours ago, ScotFlieger said:

    Hi @zhensanmao, thank you for your report and the log files. There are a number of problems that I can see.

    You need to turn on Fault Diagnosis Mode by clicking Maintenance and the large button at the bottom. Also in LINDA Console ensure VERBOSE logging (not DEBUG) is selected. Debug gives too much data.

    Whenever you have a problem with LINDA look at the Console window and FSUIPC7.log. If you see any lines starting "*** LUA Error" then the LINDA LUA code will stop running and nothing will work correctly.

    The errors I can see suggest that FSUIPC7 has not scanned all Lvars. There is an issue with MSFS2020 that causes a delay in preparing the Lvars for FSUIPC7 to read. This is mentioned in the FSUIPC Setup annex in the LINDA 4.1.x Release Notes. You need to add an entry to FSUIPC_WASM.INI under [GENERAL] for LvarScanDelay=45 (or 60). I recommend that you Start MSFS, then LINDA, wait at least a minute and then start FSUIPC 7.2.15. LINDA Tracer should list over 1200 Lvars if the load is correct.

    There is another issue with using a third-party livery like Air China. There is an entry need to made to the FSUIPC_WASM.INI file to change how FSUIPC7 model matches (see FSUIPC Support website). For testing purposes I recommend that you load the basic FBW A32NX Neo livery.

    Finally, the A32NX module 0.10.2 has problems with the APU functions. These are currently being worked on and will be in the next release.

    Please re-run the Fault Diagnosis test and email me the new logs.

    According to your requirements, click Maintenance, open failure mode, select (VERBOSE), and add LvarScanDelay=60 under [GENERAL] of FSUIPC7.INI. Start MSFS first, then LINDA, and then FSUIPC 7.2.15 a minute later. Load the basic FBW A32NX Neo livery. Rerun the troubleshooting tests. Email you now, thanks

  22. Posted · Edited by ScotFlieger

    10 hours ago, ScotFlieger said:

    Hi @zhensanmao, thank you for your report and the log files. There are a number of problems that I can see.

    You need to turn on Fault Diagnosis Mode by clicking Maintenance and the large button at the bottom. Also in LINDA Console ensure VERBOSE logging (not DEBUG) is selected. Debug gives too much data.

    Whenever you have a problem with LINDA look at the Console window and FSUIPC7.log. If you see any lines starting "*** LUA Error" then the LINDA LUA code will stop running and nothing will work correctly.

    The errors I can see suggest that FSUIPC7 has not scanned all Lvars. There is an issue with MSFS2020 that causes a delay in preparing the Lvars for FSUIPC7 to read. This is mentioned in the FSUIPC Setup annex in the LINDA 4.1.x Release Notes. You need to add an entry to FSUIPC_WASM.INI under [GENERAL] for LvarScanDelay=45 (or 60). I recommend that you Start MSFS, then LINDA, wait at least a minute and then start FSUIPC 7.2.15. LINDA Tracer should list over 1200 Lvars if the load is correct.

    There is another issue with using a third-party livery like Air China. There is an entry need to made to the FSUIPC_WASM.INI file to change how FSUIPC7 model matches (see FSUIPC Support website). For testing purposes I recommend that you load the basic FBW A32NX Neo livery.

    Finally, the A32NX module 0.10.2 has problems with the APU functions. These are currently being worked on and will be in the next release.

    Please re-run the Fault Diagnosis test and email me the new logs.

    Hi @ScotFlieger

     

    Thank you very much, I will try again, I will reply to the email as soon as possible

  23. Posted

    4 hours ago, ScotFlieger said:

    我再次需要查看日志。“它不起作用”是不够的。我猜不出来。请阅读并遵循 LINDA 支持下的故障诊断程序。

    FSUIPC7 读取可用 Lvar 存在延迟，启动顺序可能会导致问题。请阅读 LINDA 4.1.x 的最新版本说明，尤其是那些使用 FSUIPC7.INI LvarScanDelay= 的说明，应该设置为 45 或 60 秒。我正在启动 MSFS 并加载飞机，并在启动 FSUIPC7 之前等待至少一分钟。每当我更改任何内容时，我都会单击重新加载 LUA 引擎以确保一切就绪。您是否尝试使用任何肝脏？您下载了哪个版本的 FBW？

    最后，我会提醒您，FBW A320NX 模块 0.10.2 是一项非常正在进行中的工作。Joe 和我正在努力为用户扩展和更新它。FBW 也在开发中，并非一切都像我们预期的那样工作。

    对于正常飞行，我建议使用 P3Dv5.3 和 Aerosoft/FSLabs A320。

    Recently flying MSFS2020 (1.22.20), using FWB A320 (0.74), the problem now is, install LINDA 4.1.2, install FSUIPC 7.2.15 and register, install A32nx-LINDA-aircraft-module 0.10.2. Hardware VRI FCU altitude, speed, heading, elevation rate knobs work fine, but ND MODE and ND RANGE knobs don't work. The key settings of the hardware TCA Q-ENG are all invalid, including lighting and APU. Please support!

     

    I have emailed you the log file, thank you very much and joe for your hard work

     

  24. Posted

    On 2/3/2022 at 11:53 PM, ScotFlieger said:

    Problem with selecting MSFS Default aircraft profile fixed in LINDA 4.1.2. See Downloads.

     

    @ScotFlieger

    Hi old friend

    I installed LINDA 4.1.2, installed FSUIPC 7.2.15 and it's registered, installed A32nx-LINDA-aircraft-module 0.10.2, but,  it doesn't work, all the peripheral hardware switch buttons don't work , I am particularly concerned about how the APU MASTER\START\BLEED button of FWB320 should be set

  25. Posted

    On 1/7/2022 at 6:33 AM, jlively said:

    I am using the PMDG 737ngxu.  All of the buttons work correctly.  I can move the screen to the CDU. I just can't get the size right.. 

    Where is the screen of CDUll generated

×
×
  • Create New...