As a workaround, I wonder if it would work to set L:RADIO1_SERV_INT_KNOB to a non-zero value in the Q400 LINDA module at start up.  Or, failing that, setting it periodically with a timer.  I don't have FS2Crew for the Q400 so I couldn't test.  Perhaps, in the Init function, just put in

 

ipc.writeLVar("L:RADIO1_SERV_INT_KNOB", 50)

 

in the InitVars() function as a test (you'd have to find out what the valid range is for that variable...could be 0-100 or, perhaps, 0-1 or something else.  A more simple test would be, after the Q400 loads, go to the LINDA Tracer, find that variable in the left hand list and set it to see if it clears the problem.

 

Gregg,

 

I tried messing around with these settings with help from Bryan York but did not have any success.  Now as a disclaimer I have no clue what I am doing so maybe someone with a bit more knowledge can get it to work.

Hmmm...when I load up the Q400, sitting on the runway, engines and radios on, I show it set to 25.  To verify this,

• go to the LINDA Settings page
• in the right hand column of that page, select Linda Tracer
• Now, in the left column at the top, click Reload LVars list.
• In the Filter, enter RADIO1 and find RADIO1_SERV_INT_KNOB in the list.
• Now, each time you click RADIO1_SERV_INT_KNOB in the list it will show the value that it is set to in the LINDA Console window.

EDIT:  I did try monkeying with RADIO1_SERV_INT_KNOB in LINDA and I could set the value but then it would revert back to 25 after about a minute.  Visually, the switch only momentarily flips to what I set the value to and jumps back to where it was.  Valid range for that knob is 0-50 in decimal.  It seems to want to revert back to whatever the switch is set to in the cockpit.  So, I would suggest using the knob in the VC to set the value and see if that fixes the issue.  One of the oddities I've seen about the Q400 is that you can control almost anything with LINDA except the radio controls....with those, you need to use the VC.

As a workaround,

 

ipc.writeLVar("L:RADIO1_SERV_INT_KNOB", 50)

 

in the InitVars() function as a test

 

[E] *** LUA Error: ...es\linda/aircrafts/Majestic Dash 8 Q-400/actions.lua:30: attempt to call field 'writeLVar' (a nil value)

function InitVars ()

    -- uncomment to disable display
    -- AutopilotDisplayBlocked ()
    AutoDisplay = false
    ipc.sleep(100)
    --Q400_YOKE_VISIBILITY_off ()

    MJCD8_VS_Show ()
    MJCD8_ALT_Show ()
    MJCD8_HDG_Show ()
    MJCD8_SPD_Show ()

    ExtPwrTxt = 0
    ipc.set("CautAdvTest", 0)
    ipc.sleep(100)

    OnGround = ipc.readUW("0366")
	
	ipc.writeLVar("L:RADIO1_SERV_INT_KNOB", 50)
end 

 

[E] *** LUA Error: ...es\linda/aircrafts/Majestic Dash 8 Q-400/actions.lua:30: attempt to call field 'writeLVar' (a nil value)

function InitVars ()

    -- uncomment to disable display
    -- AutopilotDisplayBlocked ()
    AutoDisplay = false
    ipc.sleep(100)
    --Q400_YOKE_VISIBILITY_off ()

    MJCD8_VS_Show ()
    MJCD8_ALT_Show ()
    MJCD8_HDG_Show ()
    MJCD8_SPD_Show ()

    ExtPwrTxt = 0
    ipc.set("CautAdvTest", 0)
    ipc.sleep(100)

    OnGround = ipc.readUW("0366")
	
	ipc.writeLVar("L:RADIO1_SERV_INT_KNOB", 50)
end 

 

What does this mean?  Have you identified the problem?

No unfortunately I did not identified problem. Gregg_Seipp suggested to execute function ipc.writeLVar("L:RADIO1_SERV_INT_KNOB", 50) in InitVars function. I did that and it gives me error. That's all I wanted to say by my post.

 

And The problem start exists once MCP2 is initialized, which occurs after this function is executed.

Thanks for the clarificaiton, hopefully Scot can figure this out.

I did some investigation into controlling the Q400 radios last year. Due to the non-standard way Majestic have coded their radio implementation there is no easy way LINDA can interface with the aircraft module. I don't hold out hope for an early solution and it is not high on my priority list.

I did some investigation into controlling the Q400 radios last year. Due to the non-standard way Majestic have coded their radio implementation there is no easy way LINDA can interface with the aircraft module. I don't hold out hope for an early solution and it is not high on my priority list.

 

Scot, just wondering why this is a "low priority".  The Q400 is a very popular aircraft and FS2Crew is a very popular addon for it.  I can't think of another very serious issue with the current version of LINDA that actually prevents use of a product.  I really hope this issue can be bumped in the priority list.  thanks for your consideration on this issue.

Scot, just wondering why this is a "low priority".  The Q400 is a very popular aircraft and FS2Crew is a very popular addon for it.  I can't think of another very serious issue with the current version of LINDA that actually prevents use of a product.  I really hope this issue can be bumped in the priority list.  thanks for your consideration on this issue.

 

 

I have a number of issues with range checks and other errors to work through within the limited capacity and time I have available as the winter nights draw in. This is an issue with FS2Crew and the Q400. I don't see it as a core LINDA problem. I do have the Q400 and just purchased the FS2Crew which has yet to be updated to P3Dv3 that I am now using. When I have time to read into the Q400 (not one I know well - the Airbus is my aircraft of choice) I will look if I can find a solution but I can not make any promises.

I have a number of issues with range checks and other errors to work through within the limited capacity and time I have available as the winter nights draw in. This is an issue with FS2Crew and the Q400. I don't see it as a core LINDA problem. I do have the Q400 and just purchased the FS2Crew which has yet to be updated to P3Dv3 that I am now using. When I have time to read into the Q400 (not one I know well - the Airbus is my aircraft of choice) I will look if I can find a solution but I can not make any promises.

 

Isn't there a way to de-activate the ability to control the radios through LINDA so that the issue doesn't occur anymore? That would be at least a quick fix. Then one has to tune the radios in the VC instead of using the MCP Combo. Not ideal but better than not being able to use FS2Crew...

Isn't there a way to de-activate the ability to control the radios through LINDA so that the issue doesn't occur anymore? That would be at least a quick fix. Then one has to tune the radios in the VC instead of using the MCP Combo. Not ideal but better than not being able to use FS2Crew...

The MCP Combo radio panel is hard wired to work with the default FSX radio functions. It is that the Q400 does not use with the default radio functions and has its on working. I am not sure how disabling LINDA would work. Just don't try to change the radio using the MCP.

The MCP Combo radio panel is hard wired to work with the default FSX radio functions. It is that the Q400 does not use with the default radio functions and has its on working. I am not sure how disabling LINDA would work. Just don't try to change the radio using the MCP.

 

But the problem with FS2Crew appears without touching the MCP. The sound from the co-pilot is simply gone at some point without doing anything...

But the problem with FS2Crew appears without touching the MCP. The sound from the co-pilot is simply gone at some point without doing anything...

 

Again my question is what has this to do with LINDA?

It only appears when using LINDA!? FS2Crew works beautifully with the Q400. The audio drop-outs only happen when LINDA is started...

 

I can fly the Q400 with FS2Crew without problems when I simply quit LINDA (which obviously means I cannot use the MCP Combo)

It only appears when using LINDA!? FS2Crew works beautifully with the Q400. The audio drop-outs only happen when LINDA is started...

 

I can fly the Q400 with FS2Crew without problems when I simply quit LINDA (which obviously means I cannot use the MCP Combo)

 

OK. As soon as FS2Crew update the Q400 version for P3Dv3 I will have a look. Has this problem just appeared or is it a long standing problem?  Is it just the loss of the FO calls? Are you using a headset and is the HS button highlighted on the FS2Crew bar?