adccommunitymod (AutomationDirect) asked a question.
Created Date: June 29,2013
Created By: AZRoger
**** 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'm having intermittent but frequent occurrences of bad "Sent " time stamps in emails generated by IB-711, ECEMAIL. Examples follow Message: Msg07 06/27/13 at 19:02:2 Stopped. 00669447 Secs - 1859 HHHT. with Sent time stamp: Thu 6/27/2013 12:00 AM Message: Msg06 08/09/12 at 15:24:4 Started. 00436211 Secs - 1211 HHHT. with Sent time stamp: Thu 8/9/2012 3:00 PM Message: Msg06 06/26/12 at 12:11:2 Started. 00390233 Secs - 1083 HHHT. with Sent time stamp: Tue 6/26/2012 12:00 PM The message part of the I-Box is "Msg06 " _date:us " at " _time:24 ": " V7766:BS " Started. " V3120:DB " Secs - " V3122:B " HHHT. " (The :D at left is actually a : followed by a D.) What is consistent between all these messages is that the V7766:BS term is one digit instead of 2. I don't see how the message content should interfere with the header of the email constructed by the I-Box. But something is causing the problem. I think I can avoid the problem by only sending messages when V7766 is greater than 10. But that seems really hokey. Is there a better solution?
Created Date: June 29,2013
Created by: Do-more PE
The sent time can be set by the sending device or the mail server depending on how the mail server is configured. Most likely if the PLC time is correct, is the mail server that has the wrong time.
Created Date: June 30,2013
Created by: AZRoger
OK. I went through 174 email messages that were sent by the PLC to my email account dating from May of 2011 until now.
100 had correct Sent Times. 74 had incorrect Sent Times. That's 43 percent of all emails have the wrong Sent Times.
All of the wrong ones were sent less than 10 seconds after the minute change according to the text in the body of the message.
The three examples shown in the first post are taken from the list of 74 bad ones.
Most (but not all) of the bad messages are Msg07 Generator Stopped messages. These are triggered based on the clock in the PLC CPU. These most often occur at 7:02:00 PM when the generator is programmed to shut off. The generator also shuts off at other times when power comes back on. Those messages have the correct Sent Time.
I can't imagine that my SMTP server would randomly switch between it assigning the Sent Time and the email sender setting the Sent Time. And further that it would be lucky enough to hit only the ones sent within the first 10 seconds of each minute. And further still that it would always think that its time was on an even hour. And still further that it would only mess up messages sent from my PLC.
If you send me an email address, I can forward some of the bad ones so you can examine their headers and/or have my PLC send you a few bad messages directly. They 're really easy to generate. If you want me to create a special sequence of test emails to demonstrate the problem, let me know.
Created Date: July 01,2013
Created by: Do-more PE
Please get in touch with technical support and be prepared to send in your projects.
Created Date: June 29,2013
Created by: AZRoger
I'm having intermittent but frequent occurrences of bad "Sent " time stamps in emails generated by IB-711, ECEMAIL. Examples follow
Message: Msg07 06/27/13 at 19:02:2 Stopped. 00669447 Secs - 1859 HHHT. with Sent time stamp: Thu 6/27/2013 12:00 AM
Message: Msg06 08/09/12 at 15:24:4 Started. 00436211 Secs - 1211 HHHT. with Sent time stamp: Thu 8/9/2012 3:00 PM
Message: Msg06 06/26/12 at 12:11:2 Started. 00390233 Secs - 1083 HHHT. with Sent time stamp: Tue 6/26/2012 12:00 PM
The message part of the I-Box is
"Msg06 " _date:us " at " _time:24 ": " V7766:BS " Started. " V3120:DB " Secs - " V3122:B " HHHT. " (The :D at left is actually a : followed by a D.)
What is consistent between all these messages is that the V7766:BS term is one digit instead of 2.
I don't see how the message content should interfere with the header of the email constructed by the I-Box. But something is causing the problem.
I think I can avoid the problem by only sending messages when V7766 is greater than 10. But that seems really hokey.
Is there a better solution?