Event Detectors
My efforts over the last couple of weeks have been focused on preparing our 64/128 Channel Event Detector products for LXI compliance testing. While the compliance testing effort is interesting enough, it is actually the features of the Event Detector itself that I would like to focus on. We can discuss LXI compliance testing in a couple of weeks after I return from the LXI plugfest in Irvine, California.
The Event Detector is by no means a new product. We have been shipping the MA203 Event Detector M-module in both VXI and PXI systems since 1999. In fact, to date the MA203 install-base resides at over 430 units. This new offering of Ethernet Event Detectors consists of the same MA203 M-Modules integrated into an EM405-8 carrier in either a 64 or 128 channel configuration.
The Event Detector works by sampling all channels in parallel and selectively storing the samples along with a 31-bit timestamp into a FIFO. At every period of the programmable sample clock, the event detector samples all channels in parallel. It then compares the sample with the previous stored value and determines if any of the watched inputs have toggled. If an input has changed, the entire sample is stored along with the timestamp. The process repeats at a rate of up to 5MHz. The Event Detector features a highly programmable sample clock and the capability to use an external clock of up to 5MHz. It also includes per-channel programmable input thresholds of up to 25 volts, programmable debounce logic, and extensive triggering utilities for synchronization.
The key feature of the Event Detector is the ability to store samples only when one or more of the watched inputs have change. This provides real-time data compression and takes the burden off software to recognize and determine the interesting part of an acquisition. We call this “Data Abstraction.”
At Autotestcon in September, we demonstrated the 128 Channel Event Detector with a game that required users to press a sequence of buttons to cause events. When a user started the game, the Event Detector began continuously sampling all 128 channels at 5MHz. Events occured when a user pressed one of the toggle buttons during the game. Each play of the game typically lasted about 3 seconds. We kept statistics during the show and after three days, we had sampled a total of 14 minutes and 59.91 seconds. In that time, we received a total of 791 events and transferred across the network a total of 10.04 kilobytes (including timestamps). In stark contrast, if we would have used a standard Data Acquisition module that stores every sample at 5MHz, we would have transferred 25.14 gigabytes. In addition, a large amount of processing power would have been required to monitor the data to find the events. This example is a clear illustration of the advantages of the Event Detector and its ability to perform data abstraction. The contrast of the amount of data as compared to a continuously sampling data acquisition module is remarkable.
In just over a week we will obtain LXI compliance on the 64 and 128 Event Detectors. Beyond that, we plan to continue advancing this technology and adding products that compliment this functionality as well as our entire product line.
The Event Detector is by no means a new product. We have been shipping the MA203 Event Detector M-module in both VXI and PXI systems since 1999. In fact, to date the MA203 install-base resides at over 430 units. This new offering of Ethernet Event Detectors consists of the same MA203 M-Modules integrated into an EM405-8 carrier in either a 64 or 128 channel configuration.
The Event Detector works by sampling all channels in parallel and selectively storing the samples along with a 31-bit timestamp into a FIFO. At every period of the programmable sample clock, the event detector samples all channels in parallel. It then compares the sample with the previous stored value and determines if any of the watched inputs have toggled. If an input has changed, the entire sample is stored along with the timestamp. The process repeats at a rate of up to 5MHz. The Event Detector features a highly programmable sample clock and the capability to use an external clock of up to 5MHz. It also includes per-channel programmable input thresholds of up to 25 volts, programmable debounce logic, and extensive triggering utilities for synchronization.
The key feature of the Event Detector is the ability to store samples only when one or more of the watched inputs have change. This provides real-time data compression and takes the burden off software to recognize and determine the interesting part of an acquisition. We call this “Data Abstraction.”
At Autotestcon in September, we demonstrated the 128 Channel Event Detector with a game that required users to press a sequence of buttons to cause events. When a user started the game, the Event Detector began continuously sampling all 128 channels at 5MHz. Events occured when a user pressed one of the toggle buttons during the game. Each play of the game typically lasted about 3 seconds. We kept statistics during the show and after three days, we had sampled a total of 14 minutes and 59.91 seconds. In that time, we received a total of 791 events and transferred across the network a total of 10.04 kilobytes (including timestamps). In stark contrast, if we would have used a standard Data Acquisition module that stores every sample at 5MHz, we would have transferred 25.14 gigabytes. In addition, a large amount of processing power would have been required to monitor the data to find the events. This example is a clear illustration of the advantages of the Event Detector and its ability to perform data abstraction. The contrast of the amount of data as compared to a continuously sampling data acquisition module is remarkable.
In just over a week we will obtain LXI compliance on the 64 and 128 Event Detectors. Beyond that, we plan to continue advancing this technology and adding products that compliment this functionality as well as our entire product line.
posted by David Clark at
8:29 PM
0 Comments:
Post a Comment
<< Home