Hello

 

I recently bought the VR INSIGHT MCP BOEING TYPE COMBO PANEL. Unfortunately, I have some issue with the displays and PMDG 737 NGX. The software loads with fsx and everything works great apart from the MCP displays for SPD, HDG, ALT and V/S. The values on the MCP unit stays frozen without a change when I rotate the knobs. The values in the NGX mcp are working well, they do change when I rotate the knobs but VRINSIGHT MCP is all at 000. Nothings helps until now. I read the posts on the forums but there's no any solution apart. 

 

My config is as follows:

- Newest LINDA software 2.6.3.148 INSTALLED

- PMDG NGX newest modules installed in modules->lindacfg->aircraft->pmdg ngx with .lua extension (no any .def or .default shortcut)

-added EnableDataBroadcast=1 in the 737ngx_options.ini

-installed VRI software but loading LINDA only

-defined the keystrokes in LINDA only (cleared at fsx and fsuipc, no any doubled mappings)

-FSUIPC is newest and registered 

 

Thanks for any help,

Darek

I'll just add that it does not happen with fsx default a/c. I checked PMDG 747 and 777 BUT THE MCPs also stays frozen. Help, please

Also, I deleted all the other a/c modules folders, only NGX and default a/c left. And I had no any issues with power supply and simconnect, all works like a charm. But the display is not working at all. Trying all day to work this out, no results :/ There must be some solution for that. Thanks for any advices  

That's my linda config for NGX. I think the problem lies in sending data betwween ngx and mcp unit via linda scripts. Just don't know the solution

 

No expert here but you don't need the vri software.

Try removing it.

 

gb.

With or without it, it works the same. If the vri software is off, it doesn't collide with linda in any matter. The last thing I did yesterday was removing the configs for 737NGX in linda and operating the aircraft on fsx defaults. Things got inverted somehow - the mcp unit itself was working with values changed by knobs, but it had no effect on the NGX mcp. I'm getting crazy about that.  What I think, there's some problem in communication between linda and ngx modules. That's why they cannot transfer data between them. But it relates to SPD, HDG, ALT and V/S. The rest is working ok. The radios panel works great, the efis and all the buttons also, so I'm sure there must be some solution. Thanks again for an advice. Help Guenter

I did some research on the lua files. The lua programing language is relatively very simple.

 

I created my own file and for the SPD, HDG, ALT, VS it goes as follows:

 

-- MCP SPD knob

SPD1 = {

["A SHOW"] = SPD_show  ,

["A +"] = SPD_plus  ,

["A ++"] = SPD_plusfast  ,

["A -"] = SPD_minus  ,

["A --"] = SPD_minusfast  ,

["PRESS"] = empty  ,

 

}

 

 

-- MCP HDG knob

HDG1 = {

["A SHOW"] = HDG_show  ,

["A +"] = HDG_plus  ,

["A ++"] = HDG_plusfast  ,

["A -"] = HDG_minus  ,

["A --"] = HDG_minusfast  ,

["PRESS"] = Autopilot_HDG_Bug_align  ,

 

}

 

 

-- MCP ALT knob

ALT1 = {

["A SHOW"] = ALT_show  ,

["A +"] = ALT_plus  ,

["A ++"] = ALT_plusfast  ,

["A -"] = ALT_minus  ,

["A --"] = ALT_minusfast  ,

["PRESS"] = Autopilot_ALTSEL_mode  ,

 

}

 

 

-- MCP VVS knob

VVS1 = {

["A SHOW"] = VVS_show  ,

["A +"] = VVS_plus  ,

["A ++"] = VVS_plusfast  ,

["A -"] = VVS_minus  ,

["A --"] = VVS_minusfast  ,

["PRESS"] = Autopilot_VSSEL_mode  ,

 

}

 

With this file the display in the unit is working well, however mcp in ngx is frozen.

 

Inside the newest module from avsim the file shows:

 

-- MCP SPD knob

SPD1 = {

["A SHOW"] = empty  ,

["A  +"] = NGX_AP_SPD_inc  ,

["A ++"] = NGX_AP_SPD_incfast  ,

["A  -"] = NGX_AP_SPD_dec  ,

["A --"] = NGX_AP_SPD_decfast  ,

["PRESS"]  = NGX_AP_SPD_INTV  ,

}

 

 

-- MCP HDG knob

HDG1 = {

["A SHOW"] = empty  ,

["A  +"] = NGX_AP_HDG_inc  ,

["A ++"] = NGX_AP_HDG_incfast  ,

["A  -"] = NGX_AP_HDG_dec  ,

["A --"] = NGX_AP_HDG_decfast  ,

["PRESS"]  = NGX_AP_HDG_BANK_toggle  ,

}

 

 

-- MCP ALT knob

ALT1 = {

["A SHOW"] = empty  ,

["A  +"] = NGX_AP_ALT_inc  ,

["A ++"] = NGX_AP_ALT_incfast  ,

["A  -"] = NGX_AP_ALT_dec  ,

["A --"] = NGX_AP_ALT_decfast  ,

["PRESS"]  = NGX_AP_ALT_INTV  ,

}

 

 

-- MCP VVS knob

VVS1 = {

["A SHOW"] = empty  ,

["A  +"] = NGX_AP_VS_inc  ,

["A ++"] = NGX_AP_VS_inc  ,

["A  -"] = NGX_AP_VS_dec  ,

["A --"] = NGX_AP_VS_dec  ,

["PRESS"]  = empty  ,

}

 

With this one the vri mcp stays frozen, however ngx mcp works well.

There's a difference with the functions naming, so the problem lies here somewhere.

Had anyone have a problem like this before?

Is it possible to assign both values for one function? I'll try to do that and inform about the results.

 

Any help greatly appreciated

Ok I'm doing fine with the LINDA scripts, sth starts to happen. I'll inform You with the results. I'm trying to synchronise the displays with ngx thanks to lua scripts for 737NGX. I'll upload the files for LINDA when I'm done. For now being the displays on VRI mcp starts work  and the NGX mcp values are changing a little bit. Next night on programming and setting the displays up Anyway, there is a problem with the actual module and functions inside, that's why they are not working as they should. Throttle on

Sorry, for not responding, but I have no idea...

The 737 modules do work without any issue here.

 

Maybe Andrew can join here some day ...

Can You please help me with that:

 

ipc.control(70022, 16384)

 

What I understand (70022) is for EVT_MCP_HEADING_SELECTOR where EVT equals NGX and is responsible for turning the hdg selector knob on the Ngx mcp

 

What is the 16384 value used for and where can I find it?

 

Thanks again

Do you really want to start over building a new module?

The old works!

 

Wouldn't it be better to solve the issues?

 

Are you sure LINDA has the correct aircraft search string?

 

 

 

 

For your question:

the 737 was the first addon module developed for LINDA.

Or better said, LINDA was initially developed for the 737.

We have produced the module after the initial release of the 737 without any SDK etc. So, many funktions are just from the gathered functions we found by ourselfes.

So, what you see is an event as you found out. And the numbers after that, are mostly just for increase or decrease a knob or press or release. That are just random(?) numbers from PMDG

I was trying to solve the issues with the old one, but nothing happened. I thought it might be better to start from the very beginning to identify what's wrong. The problem lies somewhere in the actions.lua. When the file is clear the values on the mcp change, nut NGX mcp stays frozen. The fsx default one works well since it's using some fallbacked actions (I don't know where to find them) but only with the default fsx airplanes - the mcp on the default aircraft is cooperating with the vr insinght mcp. When I use the module 3.4 the VRI stays frozen, but the NGX mcp values are changing. I decided to create a script that changes one value, ex. SPD and try to synchronise that one with vri mcp. After that I try to add HDG, ALT and VS and at the very end - I'll add that scripts to the 3.4 module.

 

The problem is like that:

My NGX mcp shows that for default - SPD=100//HDG=000//ALT=10000//VS remains blank since it's not activated of course.

My VRI combo shows all vaules at zero: SPD=000//HDG=000//ALT=00000//VS=000

What I'm trying to do is to show the same vaules at the VRI mcp cause they do not synchronise when the module is loaded.

At the beginning of the script - 'initvars' I've got:

ngx_spd = 0

ngx_hdg = 0

ngx_alt = 0

ngx_vvs = 0

 

I tried to do sth like that to change the vaules on the vri display

 

ngx_spd = ipc.readLvar("L:ngx_SPDwindow")

ngx_hdg = ipc.readLvar("L:ngx_HDGwindow")

ngx_alt = ipc.readLvar("L:ngx_ALTwindow")

ngx_vvs = ipc.readLvar("L:ngx_VVSwindow")

but it doesn't work

 

As I understand these are used later for the following functions which are responsible for showing what's on the vri display:

 

function InitDsp ()

NGX_AP_SPD_show ()

NGX_AP_HDG_show ()

NGX_AP_ALT_show ()

NGX_AP_VS_show ()

end

 

This one is the main function for creatin what's on the vri display for the SPD

and the DspSPD is the LINDA function which actually sends the data to the VRI SPD display

 

function NGX_AP_SPD_show ()

ipc.sleep(50)

ngx_spd = ipc.readLvar("L:ngx_SPDwindow")

if ngx_spd < 0 then ngx_spd = 0 end

DspSPD(ngx_spd)

end

 

Something is not working here. At the very beginning the ngx_spd is set to 0, here it reads the ngx display, so it goes for two values set. An is it possible that the value for speed is less than 0 (maybe for reverse thrust, I'm not sure about that)?

 

I keeps me fighting the third day and I'm going a little bit crazy about that.

Thanks for reading this Guenter, maybe You can find some more advices for me

I know that LINDA is a fantastic app and I have to find the clue

I wrote sth like that:

 

function InitVars ()

   ngx_spd = ipc.readLvar("L:ngx_SPDwindow")

end

 

function InitDsp ()

    NGX_AP_SPD_show ()

end

 

function NGX_AP_SPD_show ()

    ipc.sleep(50)

    DspSPD(ngx_spd)

end

 

but the VRI display is not responding. I'm just wondering: if I write ngx_spd = 100, should the VRI display show this value of 100 or anythin else I put there, let's say 731?

Ok after long hours of script changing I got that (I modified this in the actions.lua module):

 

function InitVars ()

    ngx_spd = 100

    ngx_hdg = 100

    ngx_alt = 100

    ngx_vvs = 0

end

 

function InitDsp ()

    NGX_AP_SPD_show ()

    NGX_AP_HDG_show ()

    NGX_AP_ALT_show ()

    NGX_AP_VS_show ()

end

 

function NGX_AP_SPD_show ()

    ipc.sleep(50)

        ngx_SPD = ipc.readLvar("L:ngx_SPDwindow")

    DspSPD(ngx_spd)

end

 

function NGX_AP_HDG_show ()

    ipc.sleep(50)

    ngx_hdg = ipc.readLvar("L:ngx_HDGwindow")

    DspHDG(ngx_hdg)

end

 

function NGX_AP_ALT_show ()

    ipc.sleep(50)

    DspALT(ngx_alt)

end

 

When I change the init vars the VRI MCP display shows both the fixed values of 100 and reads the heading from NGX - ngx_hdg = ipc.readLvar("L:ngx_HDGwindow")

 

The thing is that with this script:

 

function NGX_AP_SPD_inc ()

    ipc.control(70016, 16384)

    NGX_AP_SPD_show ()

end

 

function NGX_AP_SPD_incfast ()

    local i

    for i = 1, 4 do ipc.control(70016, 16384) end

    NGX_AP_SPD_show ()

end

 

function NGX_AP_SPD_dec ()

    ipc.control(70016, 8192)

    NGX_AP_SPD_show ()

end

 

function NGX_AP_SPD_decfast ()

    local i

    for i = 1, 4 do ipc.control(70016, 8192) end

    NGX_AP_SPD_show ()

end

 

the values are not changing, only the knobs are rotating. The 8192 and 16384 may be responsible for rotating the knob only, but not for changing the values on the VRI display.

 

Am I right?

You know that you have to put the functions into the function "Timer" that they will show up in the displays permanent?

 

as example:

 

--------------------------

 

function NGX_AP_ALT_show ()

    ipc.sleep(50)

    DspALT(ngx_alt)

end

 

function Timer ()

    NGX_AP_ALT_show ()

end

 

--------------------------

 

and yes, there are control parameters for just rotating the knob and some for the function itself ...