PMDG B737-700: LEDs for A/P P/RST, A/T P/RST, FMC P/RST not working

[hermann]

*** Moved to FSUIPC7 support sub-forum ***

Hello from Austria!

As above said, LEDs for A/P P/RST, A/T P/RST, FMC P/RST are not working.

I tried these offsets: 

65F1 2 BYTE x 2 MAIN_annunAP[2] Boolean

65F3 1 BYTE MAIN_annunAP_Amber[2] Boolean

65F4 2 BYTE x 2 MAIN_annunAT[2] Boolean

65F6 1 BYTE MAIN_annunAT_Amber[2] Boolean

65F7 2 BYTE x 2 MAIN_annunFMC[2] Boolean

FSUIPC Vers 7.3.8  

 

Thanks in advance for your help

Rgds Hermann

 

Edited August 29, 2022 by John Dowson
Moved to FSUIPC7 support forum

[John Dowson]

There is not much I can do about this at the moment as the SDK for the PMDG 737-700 has still not been published, and I have received no information in SDK updates since version 3.0.25. I will take another look at the PMDG offsets but any information that you can provide is helpful - such as what is the last offset that is holding the correct information?

...maybe try the following offsets, adjusted backwards from 65FD which has been reported as MAIN_annunSPEEDBRAKE_ARMED:

65F3 2 BYTE x 2 MAIN_annunAP[2] Boolean

65F5 1 BYTE MAIN_annunAP_Amber[2] Boolean

65F6 2 BYTE x 2 MAIN_annunAT[2] Boolean

65F8 1 BYTE MAIN_annunAT_Amber[2] Boolean

65F9 2 BYTE x 2 MAIN_annunFMC[2] Boolean

65FB 1 BYTE x 2 MAIN_DisengageTestSelector[2]

i.e. adjust the offsets by 2 bytes,

It would be useful to determine the first offset that needs adjusting for this (or the last offset that is valid). It looks as if a new 2-byte variable has been added but I'm, not sure where...

John
 

[hermann]

I found out till now only:

65FD    Speedbrake armed
65FE     Speedbrake up
65F9     Main_annunc_FMC 1 Byte

The others I will try to find within the next days

[John Dowson]

Ok, I found the issue. The MAIN_annunAP_Amber[2] (65F3) and MAIN_annunAT_Amber[2] (65F6) were only allocated 1 byte each. This accounts for the 2-byte difference.
So, the correct offsets are as follows:

Quote

65F1	2	BYTE x 2	MAIN_annunAP[2]	Boolean
65F3	2	BYTE	MAIN_annunAP_Amber[2]	Boolean
65F5	2	BYTE x 2	MAIN_annunAT[2]	Boolean
65F7	2	BYTE	MAIN_annunAT_Amber[2]	Boolean
65F9	2	BYTE x 2	MAIN_annunFMC[2]	Boolean
65FB	2	BYTE x 2	MAIN_DisengageTestSelector[2]	0: 1 1: OFF 2: 2

Updated document attached.

John

 

Offset Mapping for PMDG 737-700.pdf

[hermann]

Sorry, but no lamp is lighten.

The last offset where a lamp is ok is 65F9. All others below not. 

These three lamps have an own testswitch: (1) for red and (2) for amber.  

With this switch only FMC works.

But when I use the main-test-switch for the lights, then AP and AT light, but FMC not (what for FMC is ok, I think). So I mean that AP and AT are assigned to some other lights .

[John Dowson]

46 minutes ago, hermann said:

Sorry, but no lamp is lighten.

What do you mean by this? The PMDG offsets only report state, you cannot write to them.

If the offsets are not holding the correct data, then there is nothing I can do about this - they are just populated from what is received from the FS.
I believe those offsets to now be correct, according to the SDK header file that I have, Offsets 0x65EA (MAIN_NoseWheelSteeringSwNORM) and 0x65FD (MAIN_annunSPEEDBRAKE_ARMED) are correct, and those inbetween are assigned based upon the latest NG3 SDK header file. I am not that familiar with the 737, so cannot verify those offsets (it is not clear to me what they should contain), but if there are any issues, nothing can be done until the SDK has been published, and then (assuming the SDK header file is correct - if not I will update once published) it will be an issue for PMDG.

 

1 hour ago, hermann said:

With this switch only FMC works.

But when I use the main-test-switch for the lights, then AP and AT light, but FMC not (what for FMC is ok, I think). So I mean that AP and AT are assigned to some other lights .

Maybe ask about this on the PMDG forums, but I don't think this will be supported (by PMDG) until the SDK is released, but you may get a response from another PMDG user.

John

[Djeez]

Indeed, these offsets do not work as expected, and neither do the corresponding LVar's, such as L:switch_3391_73X. It seems something is wrong at the PMDG side when exposing these states. 

-Emile.

[John Dowson]

2 hours ago, Djeez said:

Indeed, these offsets do not work as expected,

You mean that they don't hold the expected data values...

2 hours ago, Djeez said:

and neither do the corresponding LVar's, such as L:switch_3391_73X

Not sure about that one - do you mean that that also does not hold the correct value? Which switch is that? Is there a mapping of (lvar) switch number to function anywhere?

You can control the switches using the Rotor Brake controls. But I guess you know that and are trying to determine the state of these switches, no?
I'll check to see if I can see any lvars that hold the state.

John

[Djeez]

Sorry about not being clear.

The Rotor brake controls do work. My intention is to light up LEDs when the A/P, A/T, or FMC button light up and for that I need to either inspect the offsets, or the LVars.

What I see (as Hermann posted) is that the value is always 0, regardless of the state in the virtual cockpit on screen. This is for both the offset as well as the LVar, for all three (A/P, A/T, FMC).

-Emile.

[John Dowson]

Yes, that's what I (eventually) understood, but thanks for clarifying.

Sounds like it is an issue for PMDG, but as the SDK has still not yet been officially published, there is not that much that can be done at the moment.

I will take a look though, but, as I said, I'm not that familiar with the 737 at the moment and I'm not sure how to get these to light up - they flash or either remain off. I need to get more familiar with the aircraft's systems and cockpit layout anyway...

Cheers,

John

[hermann]

What I see (as Hermann posted) is that the value is always 0, regardless of the state in the virtual cockpit on screen. This is for both the offset as well as the LVar, for all three (A/P, A/T, FMC)

In the meantime I found out, that FMC button is ligting up when I use address 65F9 (1 byte)

Rgds Hermann

 

[John Dowson]

19 minutes ago, hermann said:

In the meantime I found out, that FMC button is ligting up when I use address 65F9 (1 byte)

That is as (newly) documented :

Quote

65F9

2

BYTE x 2

MAIN_annunFMC[2]

Boolean

I guess the next byte 65FA is for the copilot button. The other offsets must be correct then, just not populated correctly by PMDG.

Cheers,

John

[Djeez]

1 hour ago, hermann said:

In the meantime I found out, that FMC button is ligting up when I use address 65F9 (1 byte)

I can confirm that.

Thanks to both of you.

-Emile.

[savery999]

for me its flashing with 65F9 1 byte?

 

fixed!! I had a dual setting

 

[hermann2441]

On 9/1/2022 at 7:33 PM, John Dowson said:

That is as (newly) documented :

I guess the next byte 65FA is for the copilot button. The other offsets must be correct then, just not populated correctly by PMDG.

Cheers,

John

Hi again! 

Have you got some news from PMDG meanwhile? 

Best regards 

Hermann 

 

[John Dowson]

11 hours ago, hermann2441 said:

Have you got some news from PMDG meanwhile? 

Well, the SDK has been published so you can raise a ticket on this issue now if needed - or I guess I could do this... Are 65F1/65F2 (MAIN_annunAP) and 65F5/65F6 (MAIN_annunAT) still not populated correctly (it was commented that 65F9 holding MAIN_annunFMC was)? Please try first with the latest 737-700 version (3.0.56)  and let me know if those are working or not.

John

 

 

 

[John Dowson]

I see offsets 65F3/65F4 alternating between 0/1 when the AP annunciator is flashing orange, and 65F1/65F2 alternating between 9/1 when flashing red (and the alarm sounding), so those offset certainly seem to be working. And also offsets 65F5/65F6 alternating between 1/0 when the A/T annunciator is flashing orange. So all seems ok to me - haven't checked 65F3/65F4, but presume those are also ok.

So, the annunciator offsets for A/P P/RST, A/T P/RST, FMC P/RST all seem to be correct.

John

[hermann]

Hi John,

All of these Offsets are working ok now.

Thanks for your help

65F1 --- AP red
65F3 --- AP orange
65F5 --- AT red
65F7 --- AT orange
65F9 --- MCP (has orange only)

Rgds Hermann

[hermann]

I only have one LED for both red and orange.

Is it correct to set 65f1 to 4 byte to switch this LED  on in both cases? 

And the same with 65f5?

In the moment it works, but I hope you can confirm it.

Rgds Hermann

[John Dowson]

2 hours ago, hermann said:

Is it correct to set 65f1 to 4 byte to switch this LED  on in both cases? 

And the same with 65f5?

In the moment it works, but I hope you can confirm it.

You cannot set them - the PMDG offsets are read only. To control PMDG aircraft, use custom controls - see the following FAQ entry:

 

[hermann2441]

This is a misunderstanding:

I have a LED connected with an output connected via Mobiflight and Offset 65F1.

This LED lights when FS2020 sends 'AP red' 

I want THE SAME led to light when FS2020 sends 'AP orange' via 65F3.

So I use Offset 65F1 but with 4 bytes. 

It works perfekt but for sure I asked you, if there could be some side effects. 

Brgds Hermann 

[John Dowson]

Ah yes, sorry - that should be fine. You can treat an offset area as any size that you like, as log as toy understand what the data holdd.

John 

[John Dowson]

On 2/4/2023 at 4:56 PM, N987PL said:

but your response here is exactly why I dread posting anything.

I am sorry you feel that way, but I don't understand why you say this. Do you think I should accept any question in any post and in any sub-forum? The forums are not only for asking questions, but also a repository of previous questions people have asked to together, hopefully, with the resolution of the issue. This can then be used by others who encounter a similar issue, and if a post is properly titled and in the correct sub-forum then this can be found more easily...

I am spending almost all of my time on support these days, and around 70% of support requests have been asked before - and usually not just once but many times. The more I can reduce support, the more time I can spend on improving the software - and documentation. Maybe even one day I will get time for some recreational flying - it seems that I only fly these days fir testing or support issues....

I am (always!) trying to reduce the time I spend on support but this seems impossible - it seems that hardly anyone consults the documentation before posting, and even fewer people search the forum for similar issues. All I am trying to do is to help people to use the provided resources how they are intended to be used, and for the good of all. I do not mean to give offense or to be rude. And I can appreciate that new users to FSUIPC and to the FSUIPC forums sometimes (mostly!) don't understand how the forums work, and so I have to continually explain this to newcomers. But I do not expect to have to do this to people who have used the forum many times before....

There is also a sticky-topic in the main forum called READ BEFORE POSTING FSUIPC PROBLEM REPORT, not that anybody reads that either....

John

[Ray Lu]

Hi this is my first post and am building a 737 cockpit.  I am using Mobiflight and have been having an issue with this exact topic.  I see the offsets listed for the A/P A/T AND FMC.  I guess my problem is I really don't understand how they are supposed to be programmed in Mobiflight.  I apologize in advance if this is really dumb but could someone take a few minutes and let me know the steps to making the TEST 1 and TEST 2 switch illuminate the three indicators on my panel and how that sim delivers the alerts to my panel when they fire in the sim.

The TEST 1 and TEST 2 switch when I activate it on my panel does light the proper indicators in the sim.  And when I run a MOBIflight test all the LED's do illuminate properly.   

 

Thank you again! 

[John Dowson]

17 hours ago, Ray Lu said:

I guess my problem is I really don't understand how they are supposed to be programmed in Mobiflight. 

This is support for FSUIPC, not Mobiflight - try MobiFlight support (on Discord).

John