Re: [foxboro] XP reboot causes Time to Jump 7 hours ahead
- From: "Landry, Dwayne" <rdlandry@xxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 29 Aug 2012 08:59:29 -0400
Another situation where the time will change even if you are all 8.X and MTK
and BTK are setup and running correctly is if you have a XP box that is running
stand alone and not connected to the mesh. If this box runs long enough without
seeing a time server it will become a time server and send out time pulses. If
you plug this box into the mesh while it's powered up there is a good chance
that it will broadcast a time pulse which will change the time to its time then
almost immediately the MTK will correct it. Even though it only changes it for
a fraction of a second the damage it done. You're historians will now have a
future time stamped value in it. Make sure you never plug a box into the mesh
that is already powered up or if you do, make absolutely sure that its time
matches your system time.
Dwayne Landry
PPG Industries Inc.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Boulay, Russ
Sent: Wednesday, August 29, 2012 6:51 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] XP reboot causes Time to Jump 7 hours ahead
With the Mesh you define two MTK AW's (MTK and BMTK) in System Definition as
defined on the system by the /usr/fox/sp/tk.cfg file
When these two stations are alive...no "jump ball" takes place when MTK is
relinquished.
Only in the absence of both stations will another get the chance for takeover.
On Mesh ...systems can run local timezone only when system time has been
selected for UTC (vs. IATIME)
When this is the case there is no issues with time being passed from Mesh to
Node .
However, if a system is configured for local timezone (Pacific Standard Time)
and has inadvertently been configured for IATIME.....this can cause the
described issue as the UTC compensation is missing.
Whenever running IATIME on the Mesh...you must select the GMT timezone
(Edinburgh, London..etc)
Mesh supports running the local TZ when UTC is configured on the system...time
will pass thru an ATS....to Nodebus systems running GMT with no issues.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Ken Heywood
Sent: Wednesday, August 29, 2012 7:21 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] XP reboot causes Time to Jump 7 hours ahead
I discovered several years ago on a mixed XP 7.X/UNIX 6.X system that the time
really depends upon the box that is the Master Timekeeper. As explained to me
by TAC at the time, when you shutdown or reboot the current master timekeeper,
another box takes over. It's non-deterministic. There is no way of knowing
which box will become master. Now, Windows likes local time zone while UNIX
runs GMT. So, if your current XP box is the Master and you shut it down, one of
the UNIX boxes may try to take over. If it does, then you will get a jump in
the system time (unless you are running all boxes on GMT). The fix, as told to
me, is to run all boxes on GMT. There may be some magic in the mesh system now,
but I'm not aware of any.
Thank You,
Ken Heywood
Calibration Laboratory Manager
PROCESS CONTROL SERVICES, INC.
Established in 1983
http://www.processcontrolservices.com
mailto:KHeywood@xxxxxxxxxxxxxxxxxxxxxxxxxx
Telephone: 734-453-0620
Wireless: 508-241-2040
===============================================
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Brian Long
Sent: Tuesday, August 28, 2012 4:13 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] XP reboot causes Time to Jump 7 hours ahead
Yes, we've had a similar issue before, in our case MESH side DCS time was ok,
AIM time was not and Nodebus side time changed. We needed to update/quickfix
AIM and the BTK was not set. (Either was never set or SysDef wacked it). We
hold our breath every time we restart and make sure
everyone knows the time may change. Our MTK and BTK are both MESH boxes.
Hope the info helps.
Brian Long
Arkansas Kraft
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process Systems
(formerly The Foxboro Company). Use the info you obtain here at your own risks.
Read http://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
*** 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 email comes from a division of the Invensys
Group, owned by Invensys plc, which is a company registered in England and
Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X
7AW (Registered number 166023). For a list of European legal entities within
the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx.
You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail
reception@xxxxxxxxxxxxx This e-mail and any attachments thereto may be subject
to the terms of any agreements between Invensys (and/or its subsidiaries and
affiliates) and the recipient (and/or its subsidiaries and affiliates).
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://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 mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://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
Other related posts:
