Results 1 to 13 of 14
Thread: FX40 Lead Lag Runtime Object
-
03-01-2010, 12:29 PM #1
Professional Member
- Join Date
- Apr 2008
- Location
- Louisiana
- Posts
- 231
FX40 Lead Lag Runtime Object
When using the LeadLagRuntime object in the kitControl pallete what types of data can be linked to the Runtime A and Runtime B slots. I have tried linking pump status and enable commands with no luck. Thanks.
-
03-01-2010, 04:27 PM #2
Professional Member
- Join Date
- Jun 2009
- Location
- StL, MO
- Posts
- 532
These are time inputs. Add a runtime totalization to the pump status and then link the accumulated time to Runtime A/B/C...
UA LU 562
-
03-02-2010, 11:45 AM #3
Professional Member
- Join Date
- Apr 2008
- Location
- Louisiana
- Posts
- 231
Cannot find a runtime totalization object in the kitControl pallette.
-
03-02-2010, 11:57 AM #4
copy/paste from the help
DiscreteTotalizerExt is a control point extension for accumulating runtime and change of state counts on binary or enum values. Two actions are available to clear (zero) accumulated totals, ResetChangeOfStateCount and ResetElapsedActiveTime.
The DiscreteTotalizerExt is available in the Extensions folder of the control palette.
-
03-02-2010, 11:59 AM #5
Professional Member
- Join Date
- Apr 2008
- Location
- Louisiana
- Posts
- 231
When trying to drag and drop onto wire sheet I get this error message:
Drop failed.
Illegal parent "baja:folder" for child "control: DiscreteTotalizerExt".
-
03-02-2010, 12:16 PM #6
-
03-02-2010, 12:54 PM #7
You'll have to composite out these values to be able to link them to anything on the wiresheet.
RealEyes
Realize
RealLies!

-
03-02-2010, 01:20 PM #8
Professional Member
- Join Date
- Apr 2008
- Location
- Louisiana
- Posts
- 231
Ok so I figured it out. If you go to the point for the pump status in point extension manager and the click on the box for totalization it automatically adds the discrete totalizer ext to the point. Then you can link this value to the runtime slot on the lead/lag runtime object. It is functioning properly, but whichever pump is not being called for is showing an alarm state in the lead/lag runtime object. I am bringing both pump statuses into an "OR" block and then taking that output to the in slot for feedback in the lead/lag runtime object. Is this correct?? Also what value should I use for Max Runtime??
-
03-02-2010, 07:48 PM #9
Professional Member
- Join Date
- Jun 2009
- Location
- StL, MO
- Posts
- 532
An alarm is generated when the "Feedback Delay" timer expires and the Feedback does not have a status. By default, that timer is 5 seconds. I'm guessing that's your alarm issue.
Or block is correct.
Max Runtime? How often do you want the pumps to switch?UA LU 562
-
03-03-2010, 08:14 AM #10
Professional Member
- Join Date
- Apr 2008
- Location
- Louisiana
- Posts
- 231
I thought that the pumps were switched to maintain equal runtime?? If that is the case what is the need for max runtime??
-
03-03-2010, 08:24 AM #11
Banned
- Join Date
- Mar 2006
- Posts
- 3,641
I just use a calenderschedule to rotate the "X" day of the month/ "X" TOD..and then manually create the failover logic and alarming with standard pallette objects.
Its not as pretty as a custom PO, but it works without all the custom java background mojo. Once you have it made and tested you have it forever to paste in as needed.
-
03-03-2010, 05:54 PM #12
Professional Member
- Join Date
- Jan 2007
- Posts
- 156
That is the amount of continuous accumulated runtime that makes it switch loads. Meaning if your load is on continuously, after that period of time has elapsed it will shift to the other load. When it first starts a load it starts the one with the least runtime.
Not everything that can be counted counts, and not every thing that counts can be counted - Albert Einstein
-
03-03-2010, 06:50 PM #13
Professional Member*
- Join Date
- Feb 2005
- Posts
- 555
Now that you have it working I would encourage you to test the failure and see if you like how it acts. Unless something has changed if you get a feed back failure it will continiously switch between outputs ever so many seconds(what ever you delay is) Although it works id didn't like that fact and did as Freddy and wrote my own logic.


Reply With Quote
