ControlLogix - Accumulated operating time

dalporto

Lifetime Supporting Member
Join Date
Jun 2021
Location
Montreal, QC
Posts
258
Hi.

I need suggestions.

I want accumulate operating hours from a simple XIC condition, so I'm thinking a RTO with a 60000 or 3 600 000 preset, 1 or 2 CTU, you catch my drift. The unit can be operating for 1 hours up to 12 months non-stop, if that changes anything. I'm also looking to keep the number of operations on a breaker.

What I'm wondering is how to make sure that I don't lose the count / values on a full PLC download. I'm guessing what you're going to tell me is to make a note of the actual value and put it back after the download, or save / upload values before doing a change, but that is not always possible, and that will be lost anyway if the customer do its own changes later, even if written in the O&M.

So I'm asking if there is another way to try to not lose the values.

I remember I once did something like that with a different brand where I had another PLC on the network at a "higher level", so I had a logic that would give the value back if it was different, or lower, or zero, but this still looks kind of overkill for a stupid accumulated time counter, and more data exchange to set up.

I have the same setup here (PLC at "higher level"), so I could do something like that again, but I'd really prefer not to.

There is also a standalone InTouch HMI on that setup, maybe there is something that could be done using that?

Thanks for your suggestions.
 
Data preserve download tool....you can download logic updates but retain the tag values. You need fully licensed linx to use.
 
Take the 0 bit of the PLC clock's seconds DINT and put an ONS after it to execute an ADD instruction with a "Total_Process_Seconds" DINT tag +1 with itself. Use this tag to calculate the total operation minutes and hours using the DIV function. The MOD function is helpful for reoccurring intervals during a process. The DINT tag should keep its value when the PLC is powered off and back on as long as there's battery or capacitor backup. Clear the "Total_Process_Seconds" tag when an operation starts.

I usually create a bit tag called a "One_Second_Trigger" after the ONS that I use throughout the program for simple 1 second timer accumulators instead of using TON, TOF, or RTO instructions. I reserve those for processes that require more accurate times with a resolution less than 1 second.
 
Take the 0 bit of the PLC clock's seconds DINT and put an ONS after it to execute an ADD instruction with a "Total_Process_Seconds" DINT tag +1 with itself. Use this tag to calculate the total operation minutes and hours using the DIV function. The MOD function is helpful for reoccurring intervals during a process. The DINT tag should keep its value when the PLC is powered off and back on as long as there's battery or capacitor backup. Clear the "Total_Process_Seconds" tag when an operation starts.

I usually create a bit tag called a "One_Second_Trigger" after the ONS that I use throughout the program for simple 1 second timer accumulators instead of using TON, TOF, or RTO instructions. I reserve those for processes that require more accurate times with a resolution less than 1 second.

That doesn't address the OPs needs of retaining the value on a download...the accumulated value in your example could be hours, days, weeks old in the downloaded version.
 
That doesn't address the OPs needs of retaining the value on a download...the accumulated value in your example could be hours, days, weeks old in the downloaded version.
Oops. I read it too fast and I glanced over the "full PLC download". It looks like an external storage such as the HMI or another PLC may be the best option unless a PLC is used that separates the register or tag memory from the logic. A PLC such as the IDEC FC6A retains register values after downloading full logic updates.
 
Oops. I read it too fast and I glanced over the "full PLC download". It looks like an external storage such as the HMI or another PLC may be the best option unless a PLC is used that separates the register or tag memory from the logic. A PLC such as the IDEC FC6A retains register values after downloading full logic updates.

I'm assuming it's Rockwell with the use of XIC, CTU and RTO mnemonics. Rockwell makes a tool to download logic and preserve the tag values.
 
I have come to accept that my various PLC programs may all have data or settings or recipes or .... that I don't want to overwrite. SO I am very careful to upload, make changes, and download.

Of course, when a PLC craps out in the middle of the night, all bets are off. I'll get to explain to people the next day that their reports are probably wrong now. Very grateful I'm not working in a regulated industry.
 

Similar Topics

Why does the controllogix redundancy modules use a single mode fiber vs multimode fiber?
Replies
1
Views
86
Hello, I have two 16 point input cards and 1 16 point output card showing module faulted on my IO tree in Logix Designer. The fault code is...
Replies
7
Views
216
Hello, My associate and I are trying to sync up two ControlLogix racks (7-slot chassis) with identical modules. We are able to see the secondary...
Replies
4
Views
198
Trying to setup a message read via Ethernet. I have the path setup as 1, 1, 2, 192.168.66.10 I get an error code 1, ext err 315. I am beating...
Replies
9
Views
233
I have a redundant ControlLogix being set up. This program reads a value from a remote site which happens to be SLC PLC. Rockwell mentions SLC...
Replies
2
Views
96
Back
Top Bottom