Ax logic help.....

[ControlY0urMind]

I was asked for help on some programming, and unfortunately, I haven't ever created anything of the sort........

It is for a power meter. The client wants to trend power monitoring points at a frequency of 15 minutes. BUT, when certain points spike, they want it to go into alarm, and trigger trending at a faster rate so they can go back and see the data closer. (I.E, a power meter's amp reading goes extremely high and for a shorter amount of time and the 15 minute history ext. didn't catch it.)

If any of this makes sense.......any ideas would be greatly appreciated.

Thanks,

[NINAX]

I was asked for help on some programming, and unfortunately, I haven't ever created anything of the sort........

It is for a power meter. The client wants to trend power monitoring points at a frequency of 15 minutes. BUT, when certain points spike, they want it to go into alarm, and trigger trending at a faster rate so they can go back and see the data closer. (I.E, a power meter's amp reading goes extremely high and for a shorter amount of time and the 15 minute history ext. didn't catch it.)

If any of this makes sense.......any ideas would be greatly appreciated.

Thanks,

Use two NumericInterval extensions, one at 15 min and the other at the desired faster rate.

Use a StatusDemux- not in Alarm, the 15 min is enabled & faster rate disabled; in Alarm, the faster rate is enabled & 15 min disabled.

[checkvalve]

By the time it is in alarm you have probably missed the information that you are looking for. You would probably be better off having both trends enabled all of the time. When the point goes into alarm use a delay to disable the more granular history. That way you would have the detail for a period of time before the point went into alarm and for a period of time afterward.

I wouldn't bother disabling the 15 minute trend regardless of conditions.

[NINAX]

By the time it is in alarm you have probably missed the information that you are looking for. You would probably be better off having both trends enabled all of the time. When the point goes into alarm use a delay to disable the more granular history. That way you would have the detail for a period of time before the point went into alarm and for a period of time afterward.

I wouldn't bother disabling the 15 minute trend regardless of conditions.

If that is the case, don't use two to begin with.

[beer30]

I use both a 15 min sample period and a 1 min sample period on KWH enabled all the time.

The 15 min history will hold enough samples to cover 14 months of data so the customer can see energy usage over the past year, and is exported to PDF monthly.

The 1 min history will hold a little over 1 weeks worth of data, and is used to check any brief spikes in usage.

It may seem like a lot of data, but doesn't even scratch the surface of a properly sized and set-up Jace.