Event Advancement

Many products are designed to enter a certain mode or perform a function after a set number of operations, as part of a maintenance strategy that is based on use rather than time in service, for example. However, if the number of operations is large (say 1,000) and the operations have an average cycle time of 2 hours, you won’t want to wait 2,000 hours just to confirm the DUT does what it is meant to.

Through accessing the back channel, BELIeVE can – by writing to a counter in memory, for example – trick the DUT into believing the event milestone has been reached. You can then verify that your products functions as intended.