adccommunitymod (AutomationDirect) asked a question.
Productivity Suite timers acting up?
Created Date: April 19,2017
Created By: Mr0624
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
I recently noticed that when I use the timer in one of my ladders, it does not activate my =Preset variable when the timer reaches the preset, but rather after it has past the preset value. Attached is a screenshot of what it looks like AFTER it has passed the preset value. Why would this occur?
Created Date: April 19,2017
Created by: Mr0624
I recently noticed that when I use the timer in one of my ladders, it does not activate my =Preset variable when the timer reaches the preset, but rather after it has past the preset value. Attached is a screenshot of what it looks like AFTER it has passed the preset value.
Why would this occur?
Created Date: April 20,2017
Created by: Ridgeline Mach
Your "end lower " tag is being used in two places in the TMR instruction, any reason why? I'm not completely certain, but that may be the reason for erratic behavior.
Created Date: April 20,2017
Created by: kewakl
^
For a proof:
make a test project.
add two TMRs.
configure the first timer to use unique tags for each = Preset and > Preset
configure the second timer to use the a SINGLE TAG for = Preset and > Preset
setup a Bit Histogram to monitor all the configured = Preset and > Preset tags
I configured both timers to SECONDS. this is the bit histogram output - as well as ascii-art allows
____________
timers.EN _______| |____________
__
timer1.EQ_DN ____________________| |_________
_________
timer1.GRT_DN _______________________|
_________
timer2.EQ_GRT_DN _______________________|
EDIT: The forum still munges leading spaces within CODE tags. https://en.wiktionary.org/wiki/munge#English Listitem #1
EDIT: STILL CANNOT UPLOAD ANY TYPE OF FILE : forum software says EVERY FILE IS AN INVALID FILETYPE
Odd, since I use this laptop for EVERYTHING ELSE!
Created Date: April 20,2017
Created by: Mike Nash
I don't have the software loaded and could not find the software manual for the instructions elsewhere. But are you saying the timers can't give a single output for>= (greater than or equal to)? That would be, odd.
Created Date: April 20,2017
Created by: Ridgeline Mach
Unless the software makers assumed that those would always be defined as separate bits. I know the = bit is only true when the timer equals the time. So, if your time base is small, it may be only seen in one scan. It appears it may make sense to have a greater than or equal to bit, also. AKA a .DN bit!
Created Date: April 20,2017
Created by: kewakl
@mikenash According to the Bit Histogram......
I may need to indicate SW and FW revs.
EDIT: CPU P3-550, SW 1.10.1(1) FW 1.1.15.97
Created Date: April 25,2017
Created by: Levi G
You could put a NC contact on the "Time Up " rung with the same tag as in "=Preset " (in your case tag "End Lower ") This has worked for me with a productivity 2000.