Hello,
Three times already I had to reset the time on my DeltaV Pro Plus because the time continous to lag (by like 4 minutes) behind my company time.
I am using Set/Synchronize Network Time tool to reset the time each time. But we do have PI server setup as our Historian.
Any help on why each time I set the time and a few days or weeks later the DeltaV lags the time on my company time computer by like 4 minutes. One time it was behind by like 9 minutes.
Thank you,
You should configure your DeltaV network to synchronize with your enterprise time server using the instructions found in the books on line article "Synchronize time with and external network". By the way, a recent post by Bob Huba states that using the 'Set/Synchronize Network Time tool' should NOT be used to set DeltaV sytem time. (community.emerson.com/.../8537.aspx)
www3.emersonprocess.com/.../t_synchronize_time_with_an_external_network.html
Synchronize time with an external network
This section explains how to synchronize the time on your DeltaV System with an external network--a plant-wide network for example.
Requirements:
•The workstation that is to synchronize with the time server must have network access to that server. For example, if the time server is only accessible via the plant LAN, the workstation must have a plant LAN connection.
•The time source must adhere to Network Time Protocol (NTP).
To set up the network, follow these steps:
1.From DeltaV Explorer, select Remote Network under the ProfessionalPLUS workstation or Application Station.
2.From the context menu, select Properties. The Remote Network Properties dialog appears.
Note:
It is not necessary to select Enable Remote Network for time synchronization to work.
3.Select the Advanced tab on the Remote Network Properties dialog.
4.Enter the IP address of the plant-wide master into the Master Time Server field.
5.If your network has a backup time server, enter its IP address in the Backup Time Server field.
6.Open the properties dialog for the Physical network.
7.On the System Time tab Master Time Server field, browse to the DeltaV node configured to communicate with the plant-wide Master Time Server. This is the ProfessionalPLUS or Application workstation whose Remote Network you selected in step 1.
8.If you are using a backup time server, browse to it in the Backup Time Server field.
9.Download the changed setup data on the ProfessionalPLUS workstation.
In reply to Youssef.El-Bahtimy:
Thank you so much Youssef,
I would like to use our PI server NTP as the master time server in for our DeltaV network. This way we are in time sync with PI at all times. Now I am manually setting the time on DeltaV with whatever the time is on PI, and this is causing confusion cause now PI or DeltaV is lagging and we don't know.
I need to confirm if our ProPlus has a plant lan connection. PI is on the plant lan switch.
Thanks
In reply to DCS Newbie:
You shouldn't have to use the ProPlus as the link to the PI NTP server. You should be able to use the Application Station that is feeding data to the PI server as the link to the external NTP server. Just make sure you set it correctly for the Master Time Server on the network properties.
In reply to Brian Atkinson:
Thank you Brian,
So I should follow the steps on my Application Station as Youssef mentioned?
It depends on which workstations have connections to the same network as the PI server. It is possible to have both PRO+ and Application stations acting as Timeservers for the DV network (Master and Backup), with Remote network NTP connections to the external NTP Server (so long as the NTP server is reachable by IP).
There is some configuration required on the NTP server side if it is a Windows Server, by default Windows Servers do not acts as a NTP server, requiring modifications to the registry to enable the servicing of NTP clients
In reply to AdrianOffield:
Thank you Adrianofffield
I need to make sure our PI server is configured to service NTP clients before synchronizing DeltaV time to PI sever.
How does you PI server keep time? Does it tie into a corporate time server? If so, I would recommend both DeltaV and PI exist at the same NTP level, rather than DeltaV being subordinate to PI. This way, you eliminate a dependancy of DeltaV on PI for this function.
In reply to LostEngineer0: