The "millisecond" field is actually tenths of a second and that field is in the
Historian's message data.
The printer appended the field to the printed message. The historian query
returns it as a separate field. The application program using the messages
would need to append the fields.
Best,
Alex
_____________________________________________________________________________________
Alex Johnson | Schneider Electric | Invensys | United States | System
Architect, Next Generation Systems
Phone: +1 713 329 8472 | Fax: +1 713 329 1700
Email: alexander.johnson@xxxxxxxxxxxxxxxxxxxxxx | Site:
www.schneider-electric.com | Address: 10900 Equity Drive, 77041 Houston, TX,
United States
*** Please consider the environment before printing this e-mail
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Vipul.Vijay@xxxxxxx
Sent: Wednesday, March 15, 2017 11:03 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] COMM10 Module vs Historian Timestamp accuracy
Dear All,
We are facing an issue where Timestamp accuracy of Historian Alarm
Messages & that of COMM10 (LP) Module is different, latter being more accurate.
Recently we had migration of Alarm Management System (AMS) from LP (COMM 10)
based to Historian based (via ODBC).
But after that we observed, COMM10 modules were giving "millisecond" also in
the "TIMESTAMP" field of alarm line but same is not available in Historian
Alarm line.
Please suggest some solution !!!!
Regards,
Vipul Vijay | DTA-CES | Instrumentation |
----------------------------------------------------------------------------------------------
Reliance Industries Limited | Refinery Division | Jamnagar | Gujarat | India |
| (O) 288 40 15338 | Mob : 091-8128687053 | vipul.vijay@xxxxxxx
"Confidentiality Warning: This message and any attachments are intended only
for the use of the intended recipient(s).
are confidential and may be privileged. If you are not the intended recipient.
you are hereby notified that any review. re-transmission. conversion to hard
copy. copying. circulation or other use of this message and any attachments is
strictly prohibited. If you are not the intended recipient. please notify the
sender immediately by return email.
and delete this message and any attachments from your system.
Virus Warning: Although the company has taken reasonable precautions to ensure
no viruses are present in this email.
The company cannot accept responsibility for any loss or damage arising from
the use of this email or attachment."
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any associated or attached
files, is intended solely for the individual or entity to which it is
addressed. This e-mail is confidential and may well also be legally privileged.
If you have received it in error, you are on notice of its status. Please
notify the sender immediately by reply e-mail and then delete this message from
your system. Please do not copy it or use it for any purposes, or disclose its
contents to any other person.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
