OneShot Timer Module Standard Settings ION7650

[Sven_Ortmann]

Hi,

i am searching for the oneshot timer module standard settings of ion 7650.

in the ION Device Template Reference is only periodic Timer Modules available.

thank you

[VictorMarincus]

The only setup register that the One-Shot Timer module has is the Duration. The default duration (delay) is 1 second. If you drag/drop any module into your framework, you'll see the default settings.

With respect to the ION Device Template Reference - check the ION Module Counts section and you'll see them ordered alphabetically. Then, depending on the device template that you have, check the corresponding section under "7650, 7550 7600, 7500" range

As well, all the information needed about the ION modules is contained in the ION Reference document.

[Sven_Ortmann]

Thank You Victor,

i want to find out why the database is growing as fast. There are only 3 ION 7650 and few Micrologic E installed at customer and the database grows about 500MB within one day.

To my mind this is too much. So every One-Shot timer in ION7650 is set to 1 sec?

e.g. 10 min Delay Tmr is set to 4 at the moment. Why is it called 10 min Delay Tmr?

thank you

[VictorMarincus · Accepted solution]

Hi Sven,

I would recommend keeping a consistent topic. You were initially asking about the default settings for the OneShot module.

Now you switched the HW topic to a software topic (more or less).

Answering your questions (off topic):

1. The module that you point in the picture is part of the default framework indeed, however please note that its input is linked to a 10-min trigger - thus the module naming.

This module, by setting its duration to 4seconds, adds this amount of delay (4sec) from the moment when it received the 10min pulse until it triggers its output. (it's all in the ION Reference)  

2. To determine the reason why the DB is growing so big, please analyse the meter's configuration and framework (use the meter's user guide to setup correctly).

          - If for eg. your sag/swell module is not configured properly you'll get a lot of events / waveforms

          - If you have for eg. 1second recording or even below that for several parameters, again, it's a good reason for DB size increase.

          - etc.