1/7/2015 12:42 PM | |
Joined: 2/26/2009 Last visit: 9/11/2024 Posts: 22 Rating: (0) |
Hello All, During testing commisioning of my project I get the message: "ISO ind. Ethernet -> Switched to Master mode (no-time master on bus)"I tried to find the reason for this message but could find the reason why it keeps coming. Even when i check the checkbox "Send once" by Process controlling messages, the messages keep coming once every minute. The OS Server is configured as Time Master and the AS as an Time Slave. I also configured the CP card. See the attachment. In the manuals I read instructions for configuring time syncronisatie with a CP1613, but i'm using a IE General (onboard network interface). I also check that the application "CCTMTImeSync.exe" where listed in the WinCC Startup list and also where running. In chapter 11.1.8 of the manual: Process Control System PCS7 V7.0 Operator Station https://support.automation.siemens.com/WW/llisapi.dll?func=cslib.csinfo&lang=en&objid=24449737&caller=viewThere are the following requirements for time syncronisation: Time synchronization via the plant bus requires one of the following interfaces:
The interface cards provide the following options: Our configuration uses a IE General, in current versions of PCS7 this isn't a problem but was it in the past? I downloaded the project from a ES to the OS server and the first thing i tried is to checked the Access point to besure the correct interface is selected. Anyone ideas what i should check/try? So that I can narrow it down my search. Thanks (again) |
Last edited by: EJG at: 1/8/2015 1:54 PMThe License isssue is not related to the this message. Greetings, |
|
1/13/2015 7:39 AM | |
Posts: 32 Rating: (4) |
Hi EJG, have a look hereTime synchronization in the automation environment It's a collection of manuals, FAQ, and applications about the topic of time synchronisation. Maybe you find a solution there. Regards
|
This contribution was helpful to1 thankful Users |
1/28/2015 8:24 AM | |
Joined: 2/26/2009 Last visit: 9/11/2024 Posts: 22 Rating: (0) |
Yesterday I have checked the online values of these internal tags:
I don't know why the are not one of the 4 options you give. In the WinCC help I found that the message I get on the WinCC Station has the message number 1012016. (See attachement for the Process Control Messages) Any idea's? AttachmentMsg number 1012016 - Overview of the Process Control Message.pdf (168 Downloads) |
Greetings, |
|
1/29/2015 2:25 PM | |
Joined: 5/18/2006 Last visit: 10/21/2020 Posts: 170 Rating: (64) |
As Ralfiniostated, the values for the @TimeSyncDevice1State and@TimeSyncDevice2State are the Tag Status not the value. However, looks like your using PCS 7 V7.0. In that version one can not read text values from tag management (by hovering over tag while in Runtime). You must either lay the tag down in a graphic (use IO Field set to string/text data type) or remotely (like with OPC Scout). The status value of 80 just means the tag is getting data but that data could be one of the 4 messages I mentioned in my previous post. Still need to know the value of tag to make sure Time Sync is working properly (which I suspect it isn't since you're getting message every minute). The second tag status of 4C just means that you didn't configurethe second access point for time sync, so 4C is correct What I think is happening is the OS is becoming Active Master (hence the message you are seeing but something is bumping out of Active Master to what (Standby Master, Slave), I don't know. Then the OS tries to resume Active Master and generates the alarm again. Once it becomes the Active Master it generates the message but then gets bumped out again, repeating the cycle. If it stays Active Master the alarm should not get regenerated. cabreytj |
This contribution was helpful to1 thankful Users |
8/15/2017 7:54 AM | |
Joined: 6/19/2017 Last visit: 9/6/2024 Posts: 8175 Rating: (172) |
New question published by dagaik is split to a separate thread with the subject What can be the solution or method how to understand what the reason for bumping?. Best regards |
Follow us on