Page 1 of 1

Blackbox addition

Posted: Sun Apr 17, 2011 10:02 pm
by MadJosch
First, thanks for constantly improving the features of blackbox.

Here are two small addition I suggest:
- in case of bigger and more complex blackbox files it would be handy to add comments and remarks.
- add a timer for events (e.g. event triggered after x secs/mins elapsed or event action occurs after a delay of x secs/mins)

thank you


Re: Blackbox addition

Posted: Mon Apr 18, 2011 10:20 pm
by Konny
The timer for events is a cool idea, I put that on the todo-list. Actually both variants (delayed event and trigger after x secs flighttime) should be pretty easy to implement.

The possibility to add comments is already given as the blackbox is a standard xml-file. You can add one using <!-- comment --> anywhere between the xml-tags. Here's a little example:

Code: Select all

     <!-- log landing lights on -->
     <event var="landinglights" value="1" method="equal" multiple="1" text="landing lights turned on!" />
     <!-- log landing lights off -->
     <event var="landinglights" value="0" method="equal" multiple="1" text="landing lights turned off!" />
Maybe I should add that to the wiki article, too.

Re: Blackbox addition

Posted: Mon Apr 18, 2011 11:36 pm
by MadJosch
Thanks a lot. I wasn't aware that the comments are already available.

While editing the xml I got another idea for a new event trigger: the status of the passenger signs (seat belts and no smoking)

Re: Blackbox addition

Posted: Mon May 02, 2011 3:25 pm
by MadJosch
And again another idea:

Conditions should be invertable (negateable).

Code: Select all

<event var="flightstate" value="3" method="not" multiple="0" />
means event triggered when it is NOT in flightstate 3 ("landed")
Maybe you find a better way to implement. It's just a suggestion.

Re: Blackbox addition

Posted: Tue May 03, 2011 3:33 pm
by alasizon
MadJosch wrote:Maybe you find a better way to implement.
For me, I've always just set the flightstate to where the event would occur naturally.

Perhaps if you could show me exactly what you'd use this for, maybe I would understand the use for it better.

As a suggestion: Trigger using a set key combination

Re: Blackbox addition

Posted: Wed May 04, 2011 2:19 pm
by MadJosch
I understand it is hard to see what I mean when the event is standing alone.
My intension is that this event is a part of a combination event.

Code: Select all

<combination text="Speed check" sound="voice/check_your_speed.wav" multiple="0" >
    <event var="altitudestd" value="12000" method="less" />
    <event var="altitudestd" value="10000" method="greater" />
    <event var="ias" value="250" method="greater" multiple="0" />

    <event var="aircrafttype" value="B744" method="equal"  />

This would play a reminder for the airspeed of a B744 between FL100 and FL120.
But what if I would exclude especially one type of aircraft? Let's say I want this check for ALL aircraft EXCEPT the B744?
By inverting the above event all work would be done.
It would be a waste of time to write combined events for all other aircraft (on positive logic), rather than to write one exception.

This is just an example. I think there would be much more occasions where a negation would be handy.