Does anyone have a (spreadsheet) tool that can provide an assessment of the projected/ use of data capacity for a system?
There is information in the Help around "SCADAPack x7x Hardware manual> Specifications" and more information in "SCADAPack Operations Technical Reference > SCADAPack x70 Memory Capacity > Object Database and Event Pool Memory > Object Database memory" but I was interested in a tool that could assist in determining rate of event memory consumption, particularly where comms to a RTU was interrupted for a period thus preventing data/ event upload to the SCADA.
Solved! Go to Solution.
Isn't the calculation simply a division?
i.e. if you configure 'Maximum Event Storage' as 40,000, and you have 4 events per second... then you can run without overflow for up to 10,000 seconds.
If you have 100 events per second, then you can run without overflow for up to 400 seconds.
If you want a spreadsheet that tells you how many events per second you're going to be generating, then that's impossible. It will depend on what you're doing. How often you run the pump, how often the level / flow / cat counter changes...
You could pin it as a 'worst-case'... say 10 events per second... which seems like a pretty active system. That will allow for 4,000 seconds, or just under 1 hour.
If you have the Maximum Event Storage set to a smaller number, like 5000, then that will allow proportionally less time before event overflow.
I always like to set this to a really high value. BUT... you need to consider how much of your bandwidth this may potentially take up once network comms are restored. If you have 40000 events, then this will be several MEGABYTES of network traffic... which on a shoe-string radio network might cause problems... and re-transmits etc will only make the network traffic burden increase.
Isn't the calculation simply a division?
i.e. if you configure 'Maximum Event Storage' as 40,000, and you have 4 events per second... then you can run without overflow for up to 10,000 seconds.
If you have 100 events per second, then you can run without overflow for up to 400 seconds.
If you want a spreadsheet that tells you how many events per second you're going to be generating, then that's impossible. It will depend on what you're doing. How often you run the pump, how often the level / flow / cat counter changes...
You could pin it as a 'worst-case'... say 10 events per second... which seems like a pretty active system. That will allow for 4,000 seconds, or just under 1 hour.
If you have the Maximum Event Storage set to a smaller number, like 5000, then that will allow proportionally less time before event overflow.
I always like to set this to a really high value. BUT... you need to consider how much of your bandwidth this may potentially take up once network comms are restored. If you have 40000 events, then this will be several MEGABYTES of network traffic... which on a shoe-string radio network might cause problems... and re-transmits etc will only make the network traffic burden increase.
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!