Navigation
MBCLIENT instruction storing last data
Created by: chidambaram@CCA at: 5/2/2012 12:26 PM (4 Replies)
Rating 
Thanks 0
5 Entries
| 5/2/2012 2:11 PM | |
Joined: 12/1/2009 Last visit: 2/9/2025 Posts: 672 Rating:
|
Dear chidambaram@CCA , Can you kindly give us some more information about yoursetup and used hardware? Im trying to visualise your setup, but I don't understand you properly. Thanks. |
|
Give us your feedback and show us your respect! |
|
| 5/2/2012 2:31 PM | |
|
Joined: 12/1/2009 Last visit: 2/9/2025 Posts: 672 Rating:
|
Dear chidambaram@CCA, a cable or communication failuredetection has to be realised at the MBCLIENT side. Usually there should be a timeout, if the MBSERVER is not able to reply to the MBCLIENT. Lifebeat monitoring is anotherway to monitor on the communication. A bit or counter value iscontiniously changing and the change is checkedat the MBCLIENT. Regards. |
Last edited by: TIBI68 at: 5/2/2012 2:32 PMGive us your feedback and show us your respect! |
|
| 5/3/2012 8:29 AM | |
|
Joined: 12/1/2009 Last visit: 2/9/2025 Posts: 672 Rating:
|
Dear chidambaram@CCA , If you need immediate or a very quick response to your question, you need to contact with the SIMATIC Hotline. This is a forum of userssharing theirknowledge and experienceto assist others. Most of themare not paid from Siemens, soam I. You will have to wait until somebody will reply to you. Now back to your problem: It is normal that when you disconnect your slave from the master, the last information stays within the Master. There is no automatic reset or something in case thatthe connection get's lost. While,as you said, theS7-1200 does not provide you any timeout information you have to implement a lifebeat functionality as described above.This involves theMBSEVER &MBCLIENT. Regards. |
|
Give us your feedback and show us your respect! |
|
Follow us on