Solution:

First of all, the Event Counter feature of ADAM-4018M just recording the value and time while the signal exceeds the High Alarm limit or goes below the Low Alarm. In other words, this feature can't think as a pure "pulse counter". However, you can download and analysis those raw data to achieve your goal. For example, assume the High Alarm limit is 3V. Time 1 : 1.8 V Time 2 : 2.2 V Time 3 : 3.5 V --> Event Count 1 : 3.5 V, Time 3 Time 4 : 2.7 V Time 5 : 0.0 V Time 6 : 2.3 V Time 7 : 3.5 V --> Event Count 2 : 3.5 V, Time 7 Time 8 : 4.2 V --> Event Count 3 : 4.2 V, Time 8 Time 9 : 3.6 V --> Event Count 4 : 3.6 V, Time 9 Time 10 : 1.5 V Time 11 : 3.7 V --> Event Count 5 : 3.7 V, Time 11 Time 12 : 1.5 V . . . After analysis you will see 3 pulse occurred during the sampling period (Time 1 to Time 12). However, if the ADAM-4018M is set to event log mode and all 8 channels are enabled, the module will begin to scan data from CH0 to CH7. When CH0 data is compared to the high/low limit and find this value is outside the range, the data and the time would be recorded into memory. If the module is scanning data from CH0 and the input value of CH1 is outside the alarm limit range, this event of the CH1 will not be recorded. Therefore some alarm events could be lost.