Found a new one :-)

By default the SPD-Knob turns the OBS1 and can be toggled to OBS2 and ADF.

If you do so for one cycle (back to OBS1) the turn CRS-Knob (with MCP1) shows a error:

[E] *** LUA Error: R:\FSX\modules\linda/system/common.lua:9: attempt to index local 'actions' (a number value)

 

 

After Reload Lua engine CRS works normal again.

The SPD-Knob works without error.

Aha, thanks. This error is due to wrong assignments made for MCP1, it's SPD knob should be configured as normal/default SPD knob. SPD to CRS replacement makes sense only for MCP2. 

 

And one more test please: https://dl.dropboxusercontent.com/u/15957127/actions.lua

Unfortunately Alt isn't working correct.

If I tune 100 the AP Gauge shows 0010.

 

 

function A172_AP_ALT_plus (a, b, c)

 

    if c == nil then

        A172_AP_InnerKnob_plus ()

    else

        if _MCP2 () then

            ipc.writeLvar("AutopilotAltAlerter", c * 100)

            DspALT(ALT)

        else

            ipc.writeLvar("AutopilotAltAlerter", c * 10)

        end

    end

 

end

 

The wrong value was the 10 in ipc.writeLvar("AutopilotAltAlerter", c * 10)

Value  must be, even in MCP1, 100

Then it works correct.

 

 

 

The wrong value was the 10 in ipc.writeLvar("AutopilotAltAlerter", c * 10)
Value  must be, even in MCP1, 100
Then it works correct.

Oh... that means I didn't understand your previous report. 

 

So, with *100 your ALT knob works fine with correct indication on both MCP1 and AP gauge?

Sorry Alex, I apologize for not being clear enough.

Yes with *100 ALT works fine.

VVS works too

The only error is this one I posted under  #16 in this thread.

Sorry Alex, I apologize for not being clear enough.

Yes with *100 ALT works fine.

VVS works too

The only error is this one I posted under  #16 in this thread.

 

Now it's all clear, thanks for testing!

 

And that was the answer on #16: SPD knob should be configured as normal/default SPD knob. SPD to CRS replacement makes sense only for MCP2. 

 

That means, you have to change the assignments for your SPD knob - remove them or just not touch this knob.

Module updated to v1.01. 

No new features, only minor bugfixes.

Hi Artem,

the new Version has still the wrong Alt knob code for MCP1.

Factor has to be 100 not 10 as postet in #18

Oops, missed that. Thanks.

Archive is updated. 

I have both Linda 1.13 and A2A C172 installed on my rig. As a novice Linda user, I even managed to assign default FSX controls to my Saitek X52 Pro. Now, what should I do with this C172 profile except for installation procedure explained in OP?!?

 

1- Do I need to activate it thru Linda? Cuz when I select A2A C172 from Linda's drop down list nothing changes in my assignments list - only asterisks (*) appear in front of FSX controls already assigned thru Default FSX profile.

 

2- Also, I can't find default FSX control for mixture rich / lean and, therefore, assigned it thru FSUIPC. Can you tell me where it can be?

 

Can you pls advise? Thanks!

1)

press a button

This will then highlight the button in the LINDA joysticks section.

 

Assign then for your addon like you have assigned for FSX standard.

 

 

2)

same as above, but then select "Set FSX control"

A little window opens. Type then "mix" into it and it will list all functions containing mixture...you'll find lean etc also there then.

Thank you, Günter! Question no.2 solved as you recommended.

 

But some clarification needed re: question no.1. Please don't get me wrong, as you did a hard job creating an A2A C172 profile for us but what's the purpose of having this profile then, if I can create a new aircraft profile myself and assign any fsx control to it and then link it to A2A C172? What extra features/controls does it have which makes it individual for that particular aircraft?

 

Thanks again!!!

So, the question is, why we have to use modules in general?

 

Simple, as with FSX stndard functions, you could do nearly nothing.

Depends, how advanced the addon is. With the simple Carenado planes, which do just looking good, but nothing more, you can use FSX standards.

With e.g. PMDG planes, you could use maybe FSX standard for gear, but anything else will not work: no FSX fuel pumps, no starter switch, no lights, and of course no FMC button.

 

And there is a third variant: maybe with some addons, FSX standard functions work mostly, but then you have no switch sound

1.0.1> 1.0.2
changed ALT inner and outer knob behave as it wasn't correct.
Same with VS up/down

 

 

for download go to initial post #1

Thanks for your file!

 

BTW, I assigned the switch but nothing happend.

Not only your module, all fsx default switch doesn't work either.

 

I used linda module for B60T & PDMG 737 NGX and it works great but this C172...

I just copied your module to where it should be. Is there anything I must do before apply this module to a2a c172?

 

Anyway.. thanks again for your module file.