I believe I may be missing a simple solution while using the Compact Logix Studio 5000 and the predefined totalizer block for the first time. Despite correctly configuring a REAL input, the totalizer does not work as expected. Even though I am unable to upload a screenshot, the settings include: EnableIn = 1, In = 27.5 (REAL input), Gain = 1.0, ProgProgReq = 1, ProgStartReq = 1, RTSTime = 1, EnableOut = 1, with everything else set to default. The totalizer fails to run, with both Total and RunStop remaining at 0. Any insights on resolving this issue would be greatly appreciated.
Is the totalizer part of a subroutine that is being invoked?
Steve Bailey expressed concern over the totalizer possibly being located within a subroutine that is currently being executed. Rest assured, I have thoroughly verified this and can confirm that the subroutine is fully completed and operational. In fact, I have gone the extra mile by including an on/off indicator light for further validation.
To ensure the ProgStopReq is set to 0, double check if both Stop and Start are activated. If they are both true, the totalizer function will be disabled.
According to Aardwizz, it is important to ensure that the ProgStopReq is set to zero. If both Stop and Start are activated, the totalizer will not be operational. Rest assured, ProgStopReq is indeed at zero.
To ensure historical records, I did not activate OperStartReq. It is essential to trigger this function every time the totalizer commences.
It sounds like you've set up your parameters correctly for the totalizer block. One potential issue might be related to scan time (which is what RTSTime represents). Try setting your RTSTime to 0.001 (or a similarly small value), and make sure that your programmed scan time is also set to this same rate. Additionally, remember that Studio 5000 operates on a flag-based system. So if your ProgStartReq is continuously set to 1, it won't work as the totalizer only initiates once. Try setting ProgStartReq to 0 and only triggering it to 1 momentarily when you want to start the totalizer.
It sounds like you've got all the basic configurations in place, so this can be quite confusing. One issue might be the Reset (RST) input of the totalizer block. If this input is set to '1', it will constantly reset the totalizer and it won't be able to run. Make sure that the RST input is set to '0' unless you specifically want to reset the totalizer. Additionally, verify that your ProgDone output is true before trying to run the totalizer using ProgStartReq. If ProgDone is not true, your ProgStartReq might be ignored. Those are a few main areas I suggest you check.
It sounds like you've done a good job setting everything up, but one thing to check is whether the totalizer's runtime conditions are being met. Make sure the RunStop input is consistently being set to 1 during operation, as that might be preventing it from executing properly. Additionally, double-check any tags that might control the flow of the input; sometimes there could be a logic fault upstream that’s impacting your totalizer. It might also be useful to look at the diagnostics or status bits related to the totalizer block to see if there are any error flags. Good luck!
It sounds like you've covered a lot of the basics, but I wonder if you've checked the conditions on the totalizer. Make sure that the totalizer's "EnableIn" is actually being evaluated—sometimes the logic before the totalizer may prevent it from executing if there are any conditions that aren't met or if there's an issue with the data flow. Also, double-check that the "ProgStartReq" and "ProgProgReq" are only set to 1 when you really want to start the totalization process, as they might be getting interrupted or miss an execution context. It might be worth trying to isolate the block and run a simple test to see if you can force it to recognize the input and produce a total. Good luck!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: If the totalizer is not running as expected even after configuring the settings correctly, there may be issues related to the input signal, programming logic, or block parameters that need to be investigated.
Answer: Answer: The Total and RunStop values staying at 0 could indicate that the totalizer block is not receiving the expected input signal, the programming requirements are not being met, or there are errors in the configuration parameters.
Answer: Answer: To troubleshoot problems with the totalizer, you can check the input signal, verify the programming logic, review the parameter settings, ensure all necessary requirements are met, and consider any potential compatibility issues within the Studio 5000 environment.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.