Dear Rakesh... I ONLY noticed on 3 AIN Blocks that we were testing.. I assume ALL Blocks will have the same effect.. But if you have GPS time sync, the DCS time should not deviate more than 30 seconds from GPS time... And time-sync normally occurs at mid-night every night... God knows best.. Best regards.. Hizamri On 4/25/2014 10:22 AM, RAKESH DASH wrote: > Hizamri, > When you say blocks, do you mean logic blocks ? > Can we avoid this negative time stamp in synchronization ? > Any learning's from past of similar issue ? > Regards, > Rakesh > On 25-Apr-2014 7:40 AM, "Hizamri Johari" <hizamri@xxxxxxxxxxxxx> wrote: > >> Dear Rakesh >> >> I have tested this on a test station... >> >> I changed the time backward to a few minutes.. I notice the blocks >> become not responsive until the original time is reached.. >> >> May be the DCS stations time were faster about 3 minutes from GPS time.. >> >> God knows best.. >> Best regards.. >> Hizamri >> >> >> On 4/25/2014 1:24 AM, RAKESH DASH wrote: >>> Hi, >>> It so happened that all controllers & workstation lost GPS signal from >>> AW1001 workstation. This happened at 00:00:00 hrs. During this period >>> the historian got hanged & the operator workstation became very slow. The >>> synchronisation was back at 00:03:00 & historian came back to normalcy >>> automatically by 00:10:00. Can someone suggest if GPS can cause such sort >>> of problem ? >>> Please share ur views. I m stuck & don't know how to avoid it happening >>> again. >>> Rgds, >>> Rakes Dash >>> >>> >>> >>> >>> _______________________________________________________________________ >>> 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 >> >> > > > > _______________________________________________________________________ > 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