adccommunitymod (AutomationDirect) asked a question.
Created Date: March 22,2016
Created By: JeffSa
**** 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 have a timer that is ticking away happily. It is past the timer preset so T.Done is on. I have an email box that sends and email once T.Done comes on. The issue I run into is that anytime I program the Do-More in run mode while T.Done is on, I get an email as if it had just come on. The timer has not reset and is still ticking away as seen in the attached image. I thought that programming in run mode did not cause the CPU to stop/start and cause rising edges. Also in that case the timer should have reset since it would have been off. Is this a bug or just normal behavior? If its normal, is there something I can put in my rung to prevent nuisance emails from being generated when I make changes to unrelated parts of my program? Thanks!
Created Date: March 22,2016
Created by: kewakl
Can you set a SENT_MEM bit with email SENT, put a N.C. SENT_MEM in the email rung.
Reset SENT_MEM with original condition FALSE/NOT CONDITION.
I realize you may have a lot of mail triggers and this could get unwieldy.
Created Date: March 22,2016
Created by: franji1
If you actually modified the EMAIL instruction as part of a RUN mode edit, the PLC will consider this a "new " instance of an EMAIL instruction, causing it to "send " in this situation.
I just want to make sure whether this is the situation or not.
Created Date: March 23,2016
Created by: JeffSa
Turns out that was what was happening. I had made some small changes to the message and when writing it, it would send that email. Tested it out and that appears to be the only case that causes an email to be generated.
Thanks for catching and explaining that!
Created Date: March 22,2016
Created by: JeffSa
I have a timer that is ticking away happily. It is past the timer preset so T.Done is on. I have an email box that sends and email once T.Done comes on.
The issue I run into is that anytime I program the Do-More in run mode while T.Done is on, I get an email as if it had just come on. The timer has not reset and is still ticking away as seen in the attached image.
I thought that programming in run mode did not cause the CPU to stop/start and cause rising edges. Also in that case the timer should have reset since it would have been off.
Is this a bug or just normal behavior? If its normal, is there something I can put in my rung to prevent nuisance emails from being generated when I make changes to unrelated parts of my program?
Thanks!