IXEG B737-300 hardware interface plugin

[roarkr]

Hi,

 

I am quite new to X-Plane development environment, but have now started up development of a plugin to interface a specific hardware vendors cockpit modules( MCP, COM, NAV, ADF, etc.) 

The development goes OK, but i am a little confused about the usage of default dataRefs and Commands and the specific IXEG datarefs and commands. Coming from the FSX/P3D/PMDG world, I find the usage of some default datarefs and some addon specific dataref a little confusing. But, so far I have mangaged to get the MCP module almost working, but lack information about the following dataRefs/command.

For the Flight director annunciators I am using 

("ixeg/733/MCP/mcp_plt_fd_ann");

       ("ixeg/733/MCP/mcp_cplt_fd_ann");

without any luck. They seem to not work at all.

 

For the MCP's CRS_A, IAS/MACH, HDG, ALT, VS and CRS_B 7-segment displays I am displaying the values

in the hardware when turing the rotaries and then set these values to the corresponding datarRef

All , but the vvi-dial_fmp works fine.

("sim/cockpit/radios/nav1_obs_degm");

      ("sim/cockpit2/autopilot/airspeed_dial_kts_mach");

       ("sim/cockpit2/autopilot/heading_dial_deg_mag_pilot");

       ("sim/cockpit2/autopilot/altitude_dial_ft");

       ("sim/cockpit2/autopilot/vvi_dial_fpm");

       ("sim/cockpit/radios/nav2_obs_degm2");

 

 Can anyone tell me if the dataRefs I am having problem with can be changed to some others?

 

I have used DataRef tools to see if I miss something, but so far I have had no luck.

 

 

[roarkr]

I found the dataRefs for the FD_A and FD_B annunciators after some more dataRef search.

 

They are not dataRefs with the "defaul"t ixeg's annunciator _ann ending:

 

ixeg/733/mcp/fd_maser_cp

 

ixeg/733/mcp/fd_maser/pt

 

 

DataRef for the VS display on the MCP is still a mystery for me

Edited December 25, 2016 by roarkr

[teplo]

I use ArdSim to create  IXEG 733 MCP panel. I use string  13 0 ixeg/733//MCP/mcp_a_comm_ann to display switching A/P ENGAGE CMD A in out_1.cfg. But it don't work. The strings 

14 0 ixeg/733/MCP/mcp_b_comm_ann

15 0 ixeg/733/MCP/mcp_a_cws_ann

16 0 ixeg/733/MCP/mcp_b_cws_ann

work fine. Please help someone who understand with this question.

[ridgenj]

Has anyone have been able to interface the FDS MCP and CDU?

Sent from my iPhone using Tapatalk

[mmerelles]

all required datarefs and custom commands are documented on the aircraft documentation folder under the file '2-interface guide.pdf'.

 

It is very helpful also to install xplane plugin dataref editor (free) to monitor, edit the different datarefs values for throubleshooting, testing purposes. Will help you to speed up the process.

 

hope this helps