SPAD.neXt

Hi Ulrich, I don't know if this only applies to the latest beta.... I have found that if you use a bit change in a single byte offset to trigger a light state change in the Saitek BIP it doesn't work properly. As soon as the bit change is detected the light state changes but immediately changes back even though the bit hasn't changed. If you use the change in the value of a single byte offset to trigger the state change in a lamp in the BIP, it works properly.
I've also reported a problem with the iFly737 events in the beta forum.
Kind regards Mike

PLease provide a sample snippet of a bip programming that is behaving incorrectly

Hi Ulrich, I dont know how to save a snippet but this is the definition screens


The first one works
The second one fails...it momentarily lights even thought the bit remains set

...
Kind Regards Mike

This will check if bit 1 ( = 2) is set not if Bit 0 ( = 1 ) is set. Is that what you want?

Yes that is correct , I am taking the bits as ranging from Bi t0 to Bit 7
Mike

post the whole snippet please. Are there any other events bound to that plate?
Either attach the whole profile, or the device (The dropdown-arrow right of Edit Event -> Copy ) then paste the clipboard, or just open a ticket

Hi Ulrich.. this is the data for a MASTER Caution tile, for the IFLY737 using the IFLY2Fsuipc utility.
This exposes the Master caution light being on by turning on the 2nd bit of offset 9420 (bit 1 of the range 0 to 7)
Turns on:

<EventDefinition xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Trigger="VALUE">
<EventConditions xmlns="http://www.fsgs.com/SPAD">
<EventCondition ConditionComparator="IsBitSet" ConditionTargetValue="1" ConditionValueSource="FSUIPC:0000:9420" />
</EventConditions>
<EventActions xmlns="http://www.fsgs.com/SPAD">
<EventActionPlateColor Color="YELLOW" />
</EventActions>
</EventDefinition>

Turns off:
<EventDefinition xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" Trigger="VALUE">
<EventConditions xmlns="http://www.fsgs.com/SPAD">
<EventCondition ConditionComparator="IsBitNotSet" ConditionTargetValue="1" ConditionValueSource="FSUIPC:0000:9420" />
</EventConditions>
<EventActions xmlns="http://www.fsgs.com/SPAD">
<EventActionPlateColor Color="OFF" />
</EventActions>
</EventDefinition>

I cant see any difference in the expression for bit set and bit not set in the definition screen image attached..
regards Mike

Bug confirmed. fixed in Beta 3