Jump to content
The simFlight Network Forums

Master Caution and Master Warning Lights - Bredock3d Boeing 737


Recommended Posts

Posted

I'm new to all this so forgive me if this is a very straightfoward query.  I got and registered my copy of FSUPIC today.

I wish to be able to switch off on my Bravo Trhottle Quadrant the Master Caution and Master Warning lights by pressing a button (C 144) for Caution and (C 146) for Warning.

If I go to Button & Switch Assignments - B737 (I set a profile up) I can choose the action for this button and select for FS control but it is not in the Control Sent when button pressed drop down list.

If I go to the WASIM set Lvar in the Set LVAR by ID it is in that drop down list.  Generic_Master_Caution_Active 0085 if I set this to 0 the light turns off.  Also I if set Generic_Master_Warning_Active 0086 to 0 that light turns off.

I think I have to put something in the FSUPIC.INI file to do this but I am not sure what to do?

Could someone please help me.

Thank you

David

Posted
15 hours ago, dnm1967 said:

I think I have to put something in the FSUPIC.INI file to do this but I am not sure what to do?

The easiest way to do this is to  add the lvar to an FSUIPC offset, and then assign to one of the offset toggle (or set) controls, To do this, please see the section Adding Lvars to Offsets on P44 of the advanced user guide. You can follow the example given - just update the lvar name to the one you want to use (and your profile name).
Any issues, try searching this forum before posting again (I have explained how to do this many times now...).

John

Posted (edited)

I am sorry buy I cant get this to work.

In FSUPIC7.ini file I added the following:-

[LvarOffsets.B737]
1=L:Generic_Master_Caution_Active=UB0XA000
[MacroFiles]
1=b737

I created a file B737.mrco which contains

[Macros]
1=MastCaut=0A000,1

 

i've read and re-read the manual and i thought the above would make this appear in th assignments >Control sent when button pressed, but it does not.

I can't find any other help on this so could someone please help me out.  I used to be good at this sort of thing (I'm 54 and have been programming computers since I was 11.  Unfortunately I am now not vey well and my thinking is poor due to my illness.  I have tried to work this out myself.  I am not just being lazy.  I printed both manuals out and read them.

David

Edited by dnm1967
missed detail at end out
Posted
1 hour ago, dnm1967 said:

I am sorry buy I cant get this to work.

In FSUPIC7.ini file I added the following:-

[LvarOffsets.B737]
1=L:Generic_Master_Caution_Active=UB0XA000
[MacroFiles]
1=b737

I created a file B737.mrco which contains

[Macros]
1=MastCaut=0A000,1

You are confusing two different methods. One method is to add the lvar to an offset, AND then use an offset manipulation control on that offset - you DO NOT need a macro file.
The second method is to use a macro file. If you are using a macro file, you DO NOT need to add the lvar to an offset,

So, in this case, as you are adding the lvar to an offset, just remove the macro file. Then, assign your button (or key press) to the Offset Byte Togglebits control, giving the offset value as 0xA000 (the offset you are populating), and the parameter as x1. This is EXACTLY the same as the example given on P45 of the Advanced User guide, except that you are using a different lvar name - but it is still a boolean type variable (with values 0 or 1). What is so difficult to understand about this? Can you please explain as I am getting pretty fed-up of repeating basic information when I have spend a lot of time to provide user manuals for this....

Also, please remember that you should NEVER manually change the [MacroFiles] section in your ini (as with many other sections). This is managed by FSUIPC and should never be manually changed, unless you really know what you are doing. In fact, never change anything in your ini unless advised in the documentation or by support. There is no place that says you should manually adjust this section.

Any issues, try looking at your FSUIPC7.log file. This should indicate any errors, and you can also add more logging via the FSUIPC7 Log drop-down menu. You should learn how to use these facilities and understand what is logged, to help you solve your own issues, although I am always here to help - but that should be a last resort... I have now had many many support requests like this, and, to be honest, it is becoming a bit of  a pain, as it is always the case that the manual hasn't been read or followed, and i am endlessly repeating myself. This takes time away from more useful activities, such as improving the documentation (which nobody seems to consult anyway...) and adding new functionality....

 

John

Posted (edited)

Thank you for your help so far.

Ive removed the macro file and mention in FSUPIC.INI

This now has 

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=PC,144,Cx01000A000,x00     -{offset byte set, offset A000}-
 

I'm assuming FSUPIC put this in?

I wanted set not toggle as I just want to send zero to switch light off

In  th e button and switch assignments Joy #3 and button #144 is set to Offset Byte Set with offset xA000 and parameter x00

It does not work though.  When I press the switch (button) on the bravo quadrant the light does not go out?

i HAVE TRIED TO DO THIS MYSLEF

My FSUPIC.ini now has this near the end

[Buttons.B737]
PollInterval=25
ButtonRepeat=20,10
1=PC,144,Cx0100A000,x00     -{offset byte set, offset A000}-
2=PC,146,Cx0100A001,x00     -{offset byte set, offset A001}-

[LvarOffsets.B737]
1=L:Generic_Master_Caution_Active=UB0XA000
2=L:Generic_Master_Warning_Active=UB0XA001
 

The buttons do not turn the lights off though

 

Edited by dnm1967
missed detail at end out
Posted
1 hour ago, dnm1967 said:

I'm assuming FSUPIC put this in?

Of course! The ini file is where FSUIPC saves the assignments you make in the UI.

1 hour ago, dnm1967 said:

In  th e button and switch assignments Joy #3 and button #144 is set to Offset Byte Set with offset xA000 and parameter x00

Why are you using set rather than toggle (as the example I keep referring you to in the advanced user manual)? With that assignment, you are setting the lvar to 0, i.e OFF.

1 hour ago, dnm1967 said:

It does not work though.  When I press the switch (button) on the bravo quadrant the light does not go out?

But does the master caution turn off in the aircraft? That is what this assignment does. What happens to the bravo lights is another matter, and that depends on how you are controlling the bravo lights (are you using AFC Bridge? Or the FSUIPC lua scripts?)- this is a separate issue. 

1 hour ago, dnm1967 said:

The buttons do not turn the lights off though

On the Bravo or in the aircraft?

If this works when you change the lvar value using the Add Ons -> WASM -> Set Lvar... menu, it will work via an assignment. If its not working, try logging - add debug level logging to the WAPI (by adding a LogLevel parameter to the [WAPI] section of your FSUIPC7.ini - RTFM) and button & key logging in FSUIPC7 via the log menu. Then keep the logging console open so you can see what is happening when you press your assigned button.

John

 

 

Posted

Thank you for continuing to try to help me.

 

I use set as it is a switch on the bravo not a button.  I thought you were supposed to use set with switches and toggle with buttons?

The master does NOT go off in the aircraft.  If I press it with the mouse it goes off and the light goes out on the bravo.

If I set it using the Addons > WASIM > Set Lvar the light goes out in aircraft and on Bravo

I just cant get the code to work.

I've RTFM'd twice and printed out both manuals.

Im giving up on this.  being trying all day.  ill put up wirth the lights.

 

Posted
1 minute ago, dnm1967 said:

I use set as it is a switch on the bravo not a button.  I thought you were supposed to use set with switches and toggle with buttons?

You can use either. If using set, make sure you are setting to 0 for off and 1 for on. If using toggle, you can add an offset condition so it only toffles depending on the current value. If you do not understand what that means, use set.

2 minutes ago, dnm1967 said:

I just cant get the code to work.

Please:
  1. Activate debug level logging in the WAPI. To do this, add the following to the [WAPI] section of your FSUIPC7.ini file:
      LogLevel=Debug
  2. Set Log->Buttons & Keys in the FSUIPC7 menu.
  3. Load your aircraft and press the assigned button
  4. Exit FSUIPC7
  5. Show me your FSUIPC7.ini and FSUIPC7.log files.

John

Posted

Also, just check your FSUIPC7.log file. Maybe the lvar wasn't available to add to an offset once you loaded the aircraft? This can happen with complex aircraft as it can take up to a minute or longer before all lvars become available. You can adjust when FSUIPC scans for lvars by setting the LvarScanDelay WASM ini parameter to a higher value. Its default value is 5 (seconds). I  use a value of 45seconds, but some folks find that a minute or longer is needed. This depends on your system and the aircraft in question.

Please see the Advanced User guide on how/where to use/set this parameter.

John

Posted
14 hours ago, dnm1967 said:

log too big

I need to see this file. It should not be that big, but try zipping/compressing and then attach - it is a text file and should compress to a small size.

John

Posted
31 minutes ago, dnm1967 said:

Ive zipped and attached.

Do you still have debug level logging enabled for the WAPI in your FSUIPC7.ini when that log file was produced? Your log shows that the lvar information wasn't received from the WASM, and the WAPI closed its connection after 64 seconds:
     64516 21120   [INFO]: SimConnect_Close done

This is why you have no access to lvars.

 

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.