Hello everyone,

 

Is it possible to use LINDA 2.X and MCP Combo 1, or not at all ?

 

Thanks for you answer.

Pretty sure that's what my rig is.  Works good...though the knobs jump around.

 

Gregg

Hi Fensa

 

LINDA 2.5 should work with the original MCP but only limited testing has been completed. Some MCP users have reported a couple of problems that are difficult to diagnose and impossible for me to test.

 

LINDA 1.13 is stable and works well with the MCP so if your set up is working I recommend you stay with it.

I use 2.0 with mine with no issues...other than the aforementioned knobs issue.

 

Gregg

2.5 fixes the knobs (if I'm allowed to say that).

 

 

2.5 fixes the knobs (if I'm allowed to say that).

 

Now you have my attention.

2.5 fixes the knobs (if I'm allowed to say that).

 

I installed it.  My unit is a SeriealFP V.2/Jet-Liner, which I'm assuming is a 1.0 combo?  Tried the knobs and they're as jumpy as ever.  So far as I can see, everything else is working fine.

 

Gregg

Hi Gregg

 

No, the original MCP looks like this.

 

The knobs can be jumpy due to interactions between the input and display update rate and how fast you rotate them.

No, the original MCP looks like this.

 

The knobs can be jumpy due to interactions between the input and display update rate and how fast you rotate them.

 

Yeah...that's the one.  To mitigate the issue, I created some cheap and sleezy functions that I use for some knobs.  Still, not perfect but substantially better in terms of jumping.

 

Gregg

function Malibu_HDG_inc ()
    ipc.control(65879, 0)
    ipc.sleep(40)
    c = ipc.readUW("07CC")
    sync_hdg = round(c * 360 / 65536)
    DspHDG(sync_hdg)
end

function Malibu_HDG_fastinc ()

    for i = 1, 10 do
        ipc.control(65879, 0)
    end
    ipc.sleep(40)
    c = ipc.readUW("07CC")
    sync_hdg = round(c * 360 / 65536)
    DspHDG(sync_hdg)
end

function Malibu_HDG_dec ()
    ipc.control(65880, 0)
    ipc.sleep(40)
    c = ipc.readUW("07CC")
    sync_hdg = round(c * 360 / 65536)
    DspHDG(sync_hdg)
end

function Malibu_HDG_fastdec ()

    for i = 1, 10 do
        ipc.control(65880, 0)
    end
    ipc.sleep(40)
    c = ipc.readUW("07CC")
    sync_hdg = round(c * 360 / 65536)
    DspHDG(sync_hdg)
end

Actually, is there any way you can point me to where I could find the default function for tuning frequency/transponder tuning?  Perhaps, I can customize it for my needs. 

Have a look into:

 

"\Modules\linda\libs\lib-fallback.lua"

 

or 

 

"\Modules\linda\system\common.lua"

 

 

In one of these two you'll find something. But transponder could also be very addon dependen and must not be a standard function.

Thanks Guenter.  I'll try some things.

Hi Gregg

 

The default spd/hdg/alt/vss functions that your wish to overwrite are in lib-fallback.lua. If you place your functions with the same name (ie. HDG_dec) in the new user.lua file in \fsx\modules\linda\aircrafts\{your aircraft name} then this will override the default functions.  It will also avoid modifying the base aircraft module and will not be overwritten with the next LINDA update.

 

The default radio functions are in common.lua (ie. Default_XPND_select).  These functions can be called from your functions but can not be loaded through the GUI to a specific button.  Your will need to edit your config-mcl.lua file (with care).  Again I strongly recommend to do not amend common.lua; instead put any functions in user.lua.

 

Andrew

Interesting...

 

I was monkeying around in my Malibu Mirage module and added a sleep function to the loop...

function Malibu_HDG_fastinc ()

    for i = 1, 10 do
        ipc.control(65879, 0)
        ipc.sleep(0)
    end
    c = ipc.readUW("07CC")
    sync_hdg = round(c * 360 / 65536)
    DspHDG(sync_hdg)
end

What happened was very, very interesting.  I moved my knob and watched the heading bug continue to move after I stopped moving the knob.  So the clicks are buffered.  The ipc.sleep(0) must have a built in delay (perhaps a sync to an interrupt or a minimum value).  Doing it this way, I very seldom see a jump...though the knob moves significantly slower.  Perhaps there's a way to tweak it.  Still pondering this.

 

 

The default spd/hdg/alt/vss functions that your wish to overwrite are in lib-fallback.lua. If you place your functions with the same name (ie. HDG_dec) in the new user.lua file in \fsx\modules\linda\aircrafts\{your aircraft name} then this will override the default functions. It will also avoid modifying the base aircraft module and will not be overwritten with the next LINDA update.



The default radio functions are in common.lua (ie. Default_XPND_select). These functions can be called from your functions but can not be loaded through the GUI to a specific button. Your will need to edit your config-mcl.lua file (with care). Again I strongly recommend to do not amend common.lua; instead put any functions in user.lua.



Andrew

 

Hi Andrew,

 

I'm just studying the code for now and using it for ideas for a particular airplane's module.  If I can make it work well in a global sense then I'll figure out whether to mod the airplanes individually or make a global change like you suggest.

 

Question.  Where's the mechanism that decides which function to call...inc or inc_fast?  Is that in compiled code?

 

Gregg