clehmann
Member
Hi guys, I would have thought this was a simple part of my program, but it seems that things are not going as I would have thought. All I'm doing is attempting to record run hours for various motors in a plant. I'm using a DFB that does all the motor control and includes a recycling 1sec timer that triggers a "count up" block to record seconds, then another for minutes once the seconds reach 60, etc. I recently implemented code to record the total runtime at midnight and compare it with the total runtime from 24 hrs ago to create a daily run hours tag for the operators. To my surprise, motors that were certainly running for 24hrs straight were only showing 23.4 hrs....??? I've since contacted Schneider for some advice, but I thought I'd bounce it off you guys as well. The memory in the PLC is less than half full and the scan times in the processor status are in the 7-9ms range.
I did do a test yesterday where I ran a stopwatch for 5 min and compared it to a motor runtime that had been running the whole time and the PLC only recorded 4m 52s! (2% error consistent with the daily run hrs figure) Has anyone else experienced timers that do not run for the amount of time they claim to? Any idea the source? And how to resolve it?
I'm working with a Schneider Premium PLC with Advantys remote I/O and programming in Unity Pro 4.0.
Thanks to everyone for your thoughts,
Chad
I did do a test yesterday where I ran a stopwatch for 5 min and compared it to a motor runtime that had been running the whole time and the PLC only recorded 4m 52s! (2% error consistent with the daily run hrs figure) Has anyone else experienced timers that do not run for the amount of time they claim to? Any idea the source? And how to resolve it?
I'm working with a Schneider Premium PLC with Advantys remote I/O and programming in Unity Pro 4.0.
Thanks to everyone for your thoughts,
Chad