> Hi Torsten,
>
> Here's a dumb question. Many of these flip-flop variants require a clock.
> What is expected to serve as a clock signal in our system? Would this
> typically be the output of another filter or flip flop? It doesn't make
> sense in this context to imagine an actual time value. :-) And I don't
> think we provide a clock "signal" that rises and falls at some particular
> rate. This all sounds really low level, but I suppose there is no harm in
> adding it if the "if/then/else" structure parsing the section tags doesn't
> become to unwieldy.
Hi Curt,
the clock for the flip flops that require one is driven by a property. Its up
to the user of the system to provide the clock "signal". This does not
necessarily have to be a periodic signal. It just tells the flip flop:
"Evaluate the input signals exactly _NOW_".
To be more precise, the clock is the result of a condition evaluation. If you
want to remember the state of the landing-gear switch exactly at the moment
when the sun hits the horizon, you'd use something like this:
<flipflop>
<type>D</type>
<D>
<property>/controls/gear/gear-down</property>
</D>
<clock>
<greater-than>
<property>/sim/time/sun-angle-rad</property>
<value>1.57</value>
</greater-than>
</clock>
<output>/some/property</output>
</flipflop>
(whatever this might be good for)
I hope this answers your question,
Torsten
------------------------------------------------------------------------------
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
