[SOLVED at the moment] COM1/2 selector?

[Keith Smith]

I just downloaded the aircraft, very excited about it. I'll be flying it online on PilotEdge and really need to have working Com1/2 selector, like the CRJ-200 had.

 

Is there a provision for selecting the COM radio (should manipulate the same datarefs that the standard xplane audio panel will manipulate?). I see the VHF1/2 selector on the panel, but one of them is inop, and the other doesn't appear to have the effect that I thought it would.

 

Edited December 17, 2012 by Japo32

[Cameron]

Hi, Keith,

 

Have you checked out pages 33 and 40 of the manual?

 

I just loaded this up in sim and put frequencies in on both COM panels. So long as I had the switch for VHF1 or 2 flipped up, I could hear what I was expecting.

[Japo32]

They suppose to be working. I am using the normal datarefs for them... The only issue is that in xplane people cannot activate both coms to be heared same time (in the real plane yes) Try that. switch one and the other switch it off.

[Keith Smith]

Thanks guys, I tried it briefly with one switch at a time prior to my first post and didn't see the result I was expecting. I will delve more deeply and let you know what I discover. I will also check the manual. Can't wait to dive into this airplane tonight.

Edited December 16, 2012 by Keith Smith

[Keith Smith]

Verified I can receive the ATIS on either radio by selecting the VHF1/2 switches appropriately. The generic XP panel must be doing something different in terms of datarefs, because the PilotEdge plugin is detecting that you'd like to xmit on COM2 when using the generic panel. Again, I think the XP panel is probably setting more datarefs or using slightly different values. I'll debug it further and find out.

This is not a bug with the JS31, as such, I just need to find out how it's setting those values. Any chance the VHF1/2/PA selector (presumably the TX selecting) will become active, as it was in the CRJ?

My issue right now is that if someone selects to receive on VHF1 _and_ VHF2, it's not clear which one should be considered to be the TX radio (which is why if you have a system that allows both to be selected, I think you need the option to pick a TX radio, such as the VHF1/2/PA knob just below those switches).

Edited December 16, 2012 by Keith Smith

[Japo32]

the problem is that audio panel datarefs are not very complex. if i could find the datarefs to transmit, i could include them.

[Keith Smith]

Thanks, I will post more detail on the data refs and save you some time.

[KAPTEJNLN]

well i was a bit diserpointed to find that com 1 nav 1 and SQ code cant be set whit goflight device i can only set the QNH.. as well as the altitude bug is the only thing that dosent work of the mcp pro.. i know i still use the buttons in the plane but i also fly online and its easyer in a hurry to use hardware for numbes then frome the plane.. hope ther could be a solution.. i tryeid as well by selecting buttons in the x-plane to try se if that would work but dident.. also i noticed a wired thing about com1 as when you adjust it inside the plane 3 rotation buttons are rotating the button number 3 can´t be used only rotates when you rotate the button for the com1      

[zoltron_rulez]

well i was a bit diserpointed to find that com 1 nav 1 and SQ code cant be set whit goflight device i can only set the QNH.. as well as the altitude bug is the only thing that dosent work of the mcp pro.. i know i still use the buttons in the plane but i also fly online and its easyer in a hurry to use hardware for numbes then frome the plane.. hope ther could be a solution.. i tryeid as well by selecting buttons in the x-plane to try se if that would work but dident.. also i noticed a wired thing about com1 as when you adjust it inside the plane 3 rotation buttons are rotating the button number 3 can´t be used only rotates when you rotate the button for the com1      

Same is true for NAV frequencies. Is there fix for this?

 

lk

[Japo32]

As said with the Saitek panels, I don't own all the hardware that users have. It would be imposible, not just becasue the price of all of them but also the space. Even If I would have them I wouldn't know how to start to give support to them programming.

 

But what I can do, and it is done, is to publish the custom datarefs to let someone program your devices and share with you the plugin to make them work.

[zoltron_rulez]

As said with the Saitek panels, I don't own all the hardware that users have. It would be imposible, not just becasue the price of all of them but also the space. Even If I would have them I wouldn't know how to start to give support to them programming.

 

But what I can do, and it is done, is to publish the custom datarefs to let someone program your devices and share with you the plugin to make them work.

Javier,

 

Thank you for your response. Actually, these are GoFlight modules and use the famous Sandy's GoFlight plugin.

 

Nevertheless, if your aircraft uses X-Plane datarefs for NAV and COM there's absolutely no reason you need to own any type of hardware. Your aircraft will work out of the box as long as "your" plugin doesn't do something extraordinary, or uses other datarefs. ie. If your plugin plays by the rules of the SDK correctly, everything is dandy. That's the whole idea about an SDK.

 

I did simple test,- the GoFlight modules work fine with the Cessna 172, even with the CRJ-200 that you released. Next, I have loaded the Jetstream (beautiful aircraft btw) and disabled the plugin for it. Guess what, ... the GoFlight modules work. So clearly, the Jetstream plugin is most likely the cause of the problem.

 

I do understand, if you do not have the hardware we have to test against, it is hard to catch these problems. Unfortunately, the Jetstream plugin is doing something that is reseting the NAV and COM frequencies preventing the GoFlight plugin to work correctly or vice versa. Not to point fingers, but since I never had a problem with the GoFlight plugin on all aircrafts I used it on (and it is writen by the author of the SDK), the problem most likely lies in the Jetstream plugin.

 

Javier, can you please have a look how you're dealing w/ these datarefs.

 

Kind Regards,

 

Luke

Edited January 3, 2013 by zoltron_rulez

[Cameron]

Nevertheless, if your aircraft uses X-Plane datarefs for NAV and COM there's absolutely no reason you need to own any type of hardware. Your aircraft will work out of the box as long as "your" plugin doesn't do something extraordinary, or uses other datarefs. ie. If your plugin plays by the rules of the SDK correctly, everything is dandy. That's the whole idea about an SDK.

 

I'm not sure what you're talking about here, Luke. The SDK has rules to follow to build and develop plug-ins which expand the features of X-Plane. 

 

This aircraft uses other datarefs than what GoFlight is looking for due to various reasons. This is why the plug-in is not working for you. More discussion on this has already taken place here: http://forums.x-pilot.com/index.php/topic/4317-incompatibility-with-saitek-panels/

[zoltron_rulez]

I'm not sure what you're talking about here, Luke. The SDK has rules to follow to build and develop plug-ins which expand the features of X-Plane. 

 

This aircraft uses other datarefs than what GoFlight is looking for due to various reasons. This is why the plug-in is not working for you. More discussion on this has already taken place here: http://forums.x-pilot.com/index.php/topic/4317-incompatibility-with-saitek-panels/

What I meant to say, it is possible to create plugins that do not play nice by the rules with other plugins or X-Plane. Nevertheless, if you're using a custom data ref, that explains it,- bummer. Thanks for this thread, I will have a look at it.

Edited January 3, 2013 by zoltron_rulez

[Japo32]

as said in the saitek panels post:

 

 

For the 1.02 version of the plane I have included two yoke menus where the people can deactivate the radios and altitude selection with plugin and can manage them with hardware radios. 

 

Also I have included another yoke menu to make possible assign joystick axis inside the Jetstream once loaded. But still will be necesary to exit from another plane if people don't want loose mixture and propeller assignations.