This Article is about the limit of Events the Fluke-1736 and Fluke-1738 and what the internal memory can support.
The number of events per logging session:
41kB disk space per Waveshape recording.
58kB disk space per RMS Profile.
100kB total disk space for both event recordings per event.
If recording of 2 events overlap, then only 1 recording is stored. So, considering the min and max amount of space per session in events data pool are 100 - 1000 event recordings per logging session without overlapping event recordings.
How many Events can be stored?
Short answer is up to 1000 or even more events plus recordings - depending on session configuration and distance between events.
Long answer is in 173x we have 2 memory pools: one (500 MB) for logging sessions, one (1 GB) for events and their recordings. When a logging session is being configured then - depending on duration and averaging intervals - it will occupy a percentage of the session pool. The same percentage is reserved in event pool, but at least 10 MB and not more than 100 MB. The size of one event is (48 bites), the size of its recordings (waveshape + RMS profile) is 100 kB so up to ~1000 events plus recordings can be stored. If the distance between events is less than 10 s then recordings may be shared between events. In this case more events can be stored.
When most of the event pool is consumed then there is not enough space for a recording (100 kB) but events (48 bites) still can be stored so usually the last stored events don’t have recordings. There is no priority between event types: if the user enters a limit for Inrush Current that is too low then it may happen that it eats up all event memory. When later a dip occurs then it cannot be stored anymore. So, seems for non-overlapping event data its 1000, but with overlap its higher.