shared memory variables for some instruments

[henkie]

Maybe I overlooked, after reading so many times I am probably "blind" 
What are the variables to control

- compass indication
- liquid oxygen indication
- cabin pressure indication

all on the right AUX panel


Thanks!

[lightning]

Compass=yaw
Cabin pressure=cabinAlt
LOX: not in sharedmem

[Snoopy]

LOX: not in sharedmem

That would explain why Liquid Oxygen is not included in F4to Serial. Shame though.

I am using F4toSerial for the DED, most of the gauges and LEDs. I only need to read Total Fuel and Compass with an Arduino to power these last two instruments on my Right Aux. In F4toSerial you can only use separate 7-digit blocks for the total fuel display on the Total Fuel Quantity Indicator. I have a very small OLED display. And for the wet compass, I made my own solution based on a hint from an A-10 cockpit. Both options work very nice, if only I could somehow get these two values into an Arduino. But the thought of C-programming and Visual Studio... Even looking at GitHub and forks and those things makes my mind start to slowly melt. 

[henkie]

@lightning : Thanks!
Cabin Pressure ... 
Compass ... yaw ... I had not made that connection 
LOX ...    An just for thát indicator I did a lot of work. Build a separate 115VAC 400 Hz power supply (input 24VDC), and a small stepper motor controller, mounted underneath the right side console. I did manage to get the real LOX indicator working, so I guess, I put the needle at some 4.2 at startup, and leave it there.

Adding a lot to the SharedMemoryTester and my "app", it's about time to see how my pit reacts   

@Snoopy : I also started with zero knowledge of "Windows Programming",  C# and Visual Studio. It is simply learning by doing. However, I am still an amateur. Sometimes, to get things done, I save my work, close Visual Studio, and then start Visual Studio again. I certainly am still not comfortable navigating through all the panes, there are of course more clever ways than close/start again, but it gets the job done 

Having done everything "my own way" makes that I have to do the last bits also "my own way" 

[henkie]

I am slowly going through the process of "run in" of my pit 

Minor "issue"
When I press the MAL & IND LTS button on the TEST panel, the "xmas tree" lights up 
On the left eyebrow are two indicators: "TF FAIL" and "OVRD".
In the 3D cockpit both indicators light up, but in my pit only TF FAIL lights up.
That makes sense, because in my code for handlling the "OVRD" bit is the text "TO BE IMPLEMENTED" 
I assume that "OVRD" stands for "override", but override from what
Can somebody tell me what the indicator is for (not found in the BMS docs  ) and which light bit in shared memory is allocated to this indicator

Major "issue"
I am currently up to the "step" START2. The JFS switch is held in the START2 position, and after a few seconds the RUN light comes on. I see the RPM indicator slowly move to 25%. Then you are supposed to move the throttle from minimum position a bit "forward". That does not happen when I move the throttle.
I have a "working" throttle in the Alternative Launcher ("AXIS"), and was able to set CUT-OFF, IDLE and AB.
What I noticed is that maximum AB is approx 75% of the entire slider range. BTW, I have a TUSBA2.
So, in the Alternative Laucher I see the throttle value change when I move the throttle, but in the simulation the throttle does not move at all.
Am I overlooking something essential here?  I am stuck 

[Red Dog]

If I remember right you have to activate the real throttle behaviour in the F4config? It's one of the options for those of us having real detents an our real throttle config
When that one is not activated you have yo use a keypress declared as idle detent to 'simulate' passing the detent

So 2 possibilities fo you to test
1. locate that option in F4config (I mean the old F4patch) and retry
2. locate the callback for the idle detent, assign it and press it to start the engine when JFS does its job and you want to tell BMS that you advance the throttle past the detent

Obviously option 1 is meant for you.

Bear with me it's been a long time I haven't touched all this so my memory might be slighly off

[Nikolas_A]

I did manage to get the real LOX indicator working, so I guess, I put the needle at some 4.2 at startup, and leave it there.

Or make it slowly decrease the value. With all the work you've done it would be a shame if it didn't move...

[FalconDK]

As per the bible aka https://www.xflight.de/ OVRD is related to the Manual Pitch selection and only for the D models. However, I have some old notes mentioning it is related to the Flt Control digital backup mode, so when this is activated the OVRD indicator will be on. I haven't been able to verify any of this information though.

OVRD is not in the current flightData.h file and the absence makes sense if Martins information is correct.

[henkie]

That is interesting!

When I press the MAL & IND LTS button on the TEST panel, the OVRD indicator in the displayed cockpit lights up.
Can take a picture of it as proof 

That leads me to believe OVRD is still present, otherwise how can Falcon4 else light up that indicator

[FalconDK]

I managed to locate information about the OVRD light after finding a main flight manual it is possible to search in, https://info.publicintelligence.net/HAF-F16.pdf. Previously I only had a scanned version. Below are extracts from the manual and the OVRD light is indeed related to the D model aircraft and not to the manual pitch selection. You can find the related sections in the manual by searching 'ovrd'

NOSEWHEEL STEERING (NWS) SYSTEM
Either cockpit can control the NWS. Control is
accomplished by means of an NWS control button/
indicator located in both cockpits just aft of the stick.
Depressing the button/indicator transfers control of
the NWS; the indicator illuminates green in the
cockpit which has control. Control then remains in
that cockpit even if the engine is shut down and/or
electrical power is removed. NWS can only be
engaged and operated from the cockpit which has
control. When NWS is selected, the NWS light
illuminates green in both cockpits. The aft stick
paddle switch allows immediate override of the
forward cockpit if the STICK CONTROL switch on
the TEST switch panel is in AFT; the NWS control
button/indicator in the aft cockpit and OVRD light
illuminates. The front cockpit paddle switch cannot
override the aft cockpit regardless of the position of
the STICK CONTROL switch. With the AIR
REFUEL switch in OPEN, NWS can be engaged or
disengaged  from either cockpit without using the
paddle switch regardless of which cockpit has control.

STICK CONTROL OPERATION
With the STICK CONTROL switch in FWD, the stick
indicator  displays  the  word FWD.  Depressing  the
forward  cockpit  paddle  switch  locks  out  the  rear
cockpit  stick,  rudder,  and  MPO  commands.  The
OVRD light in both cockpits illuminates indicating
override  is  activated.  Depressing  the  rear  cockpit
paddle switch has no effect on the forward cockpit
controls.
With the STICK CONTROL switch in AFT, the stick
indicator  displays  the  word  AFT.  Depressing  the
rear  cockpit  paddle  switch,  PX III   with  the  ASIU
switch  OFF  or  the ASIU  STICK CONT  switch  in
FLIGHT, locks out the forward cockpit stick, rudder,
and MPO commands and transfers control of NWS to
the rear cockpit. The OVRD  light in both cockpits
illuminates,  indicating  override  is  activated.  De
pressing the forward cockpit paddle switch has no
effect on the rear cockpit controls.

Stick OVRD Lights D
Refer to figure 1-90. The stick OVRD lights, located
on the forward and rear cockpit instrument panels,
illuminate when the paddle switch is used to take
control.

[henkie]

Excellent research work @FalconDK 

So, would it be a "bug" in Falcon4 that with the MAL & IND LTS button on the TEST panel, OVRD on the left eyebrow lights up   If there is no bit in "flight data.h" for OVRD, how does Falcon4 light up the indicator?

For my pit, it does not matter / is not relevant, but I have the indicator wired, so I would love to see it light up when the MAL & IND LTS button is pressed 

[FalconDK]

For me it seems like a bug it lights up in Falcon 4. We will need the BMS developers to chime in how they have programmed it.

If you do your own code it should be possible to add the OVRD light to the button press function/commands directly and not have it rely on a shared memory variable.

[Nigel]

Henk,
As read above, unless you are building a two seat D model or an MLU, you should not have an OVRD indicator. If you have one, its probably because a lot of MLU conversion leftover parts were floating around and available. Look on xflight .de and read up on the eyebrow indicators and also look at the TEST panel and ZEROIZE pics. The D model has an extra switch called "STICK CONTROL" which allows the GIB to fly the jet. Also there is the NWS button where the Zeroize/Voice Inhibit Panel is (look on xflight) and it activates NWS on the ground.. In my old trainer, I had acquired all the panels for a D model so I built mine as the front seat. I hardwired it so that if you activated the proper switches, the OVRD would light but it's all static. There are no D models in SHMEM for BMS or DCS so the OVRD lamp shouldnt come on when testing MAL and IND unless you hardwire it.
Oh, and I also had a MISC panel with an OVRD indicator and it is also obsolete except for MLU which has it but its not used. So basically forget it's there if possible but with the amount of OCD all us piutbuilders have, I doubt thats possible.

[henkie]

   @Nigel
The list of things to do is still long enough.
But OVRD is added at the bottom.
When the MAL & IND LTS button on the TEST panel is pressed, my own software "senses" that and makes sure that, besides the workz of BMS, OVRD is also lit. I did not wire it just for nothing