The system is activated and operated from the user's workstation. This program sets up the STCC and collects data from it during runs. For these operations as well as post run data review with TimeScan, no other changes are required. Minimum and per-event. Each event call is a single line of C code.
Actual overhead is target computer and compiler dependent.
VTrace works in these systems as long as VME access is provided and a spare VME slot is available. There is even specific and enhanced support for Mercury systems. A custom mode is defined that allows modules to use the Raceway clock for event timestamping. This is even more accurate than using the native VTrace timer. This mode works well when there aren't a large number of Mercury processors storing lots of events and there isn't significant VME bus contention.