Fake Pilot Posted December 23, 2024 Report Posted December 23, 2024 (edited) *** Moved to FSUIPC7 / MSFS support sub-forum *** Hi All I have a CPFlight MCP & EFIS and I'm trying to use Offsets to connect it to and old version of Prosim. Below is the Offset from the 'Mapping for PMDG737-700 document that's installed with FSUIPC 7 EFIS CONTROL PANELS 65BC 2 BYTE x 2 EFIS_ModeSel[2] 0: APP 1: VOR 2: MAP 3: PLAN Am I right in saying that this line means there are 2 bytes to be used for the MODE Selector, 65BC & 65BD? And what is the 0 1 2 3 for? Is that the bit number, meaning APP would be entered as 65BC.0? Many Thanks Ian. Edited December 23, 2024 by John Dowson Moved to FSUIPC7 support forum
John Dowson Posted December 23, 2024 Report Posted December 23, 2024 1 hour ago, Fake Pilot said: Am I right in saying that this line means there are 2 bytes to be used for the MODE Selector, 65BC & 65BD? Yes, 1-byte for each EFIS mode selector switch. There are two EFIS panels, no? So there is one byte per panel. 1 hour ago, Fake Pilot said: And what is the 0 1 2 3 for? Is that the bit number, meaning APP would be entered as 65BC.0? No, they are the byte values, so each byte will hold one of those values representing the position of the switch in that panel.
Fake Pilot Posted December 24, 2024 Author Report Posted December 24, 2024 Thanks for your reply. Do you know where I can find the remaining EFIS offsets? The document doesn't list the EFIS push buttons. WXR, STA, FPV, STD etc etc. Regards.
John Dowson Posted December 24, 2024 Report Posted December 24, 2024 21 minutes ago, Fake Pilot said: Do you know where I can find the remaining EFIS offsets? The document doesn't list the EFIS push buttons. WXR, STA, FPV, STD etc etc. There is no state to the push buttons, they just trigger custom controls: #define EVT_EFIS_CPT_WXR (THIRD_PARTY_EVENT_ID_MIN + 369) #define EVT_EFIS_CPT_STA (THIRD_PARTY_EVENT_ID_MIN + 370) #define EVT_EFIS_CPT_WPT (THIRD_PARTY_EVENT_ID_MIN + 371) #define EVT_EFIS_CPT_ARPT (THIRD_PARTY_EVENT_ID_MIN + 372) #define EVT_EFIS_CPT_DATA (THIRD_PARTY_EVENT_ID_MIN + 373) #define EVT_EFIS_CPT_POS (THIRD_PARTY_EVENT_ID_MIN + 374) #define EVT_EFIS_CPT_TERR (THIRD_PARTY_EVENT_ID_MIN + 375) #define EVT_EFIS_CPT_LAST EVT_EFIS_CPT_TERR ... #define EVT_EFIS_FO_WXR (THIRD_PARTY_EVENT_ID_MIN + 425) #define EVT_EFIS_FO_STA (THIRD_PARTY_EVENT_ID_MIN + 426) #define EVT_EFIS_FO_WPT (THIRD_PARTY_EVENT_ID_MIN + 427) #define EVT_EFIS_FO_ARPT (THIRD_PARTY_EVENT_ID_MIN + 428) #define EVT_EFIS_FO_DATA (THIRD_PARTY_EVENT_ID_MIN + 429) #define EVT_EFIS_FO_POS (THIRD_PARTY_EVENT_ID_MIN + 430) #define EVT_EFIS_FO_TERR (THIRD_PARTY_EVENT_ID_MIN + 431) #define EVT_EFIS_FO_LAST EVT_EFIS_FO_TERR See the FAQ section on how to use PMDG custom controls: John
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now