7/8/2013 8:30 AM | |
Posts: 153 Rating: (2) |
thanks for sharing your broad expriences |
7/8/2013 10:19 AM | |
Joined: 11/21/2007 Last visit: 9/25/2024 Posts: 2325 Rating: (308) |
Thanks AMAZINGAHMEDfor initiating this post. We all are sometimes torn between ethics and practical realities of doing business. I agree with AMAZINGAHMEDthat many time customer is unwilling to pay even after work has been completed or forces you to do extra work not initially agreed without compensating for the same. We have suffered many times like this. However we are lucky to be in a field where the customer will need us again sometime if we have done a good job. PersonallyI believe in never setting a CPU password. However I often "KNOW_HOW_PROTECT" critial SCL and SCL blocks to prevent any accidental changes.. In fact we always prefer that the customer understads how the software has been written and can make minor changes with instruction on phone / Remote Desktop so that we do not have to rush an engineer everytime for minor issues. Of late i am seeing many chinese supplied machines in our country. Invariably these are password protected and customers do not have either the password or Software copy. I know many customers behave un-ethically .. but if we also behave the same way then what is the difference ??? Still there is a genuine need to protect our know how. One of the best ways to protect the software from being copied is to link it with MMC serial no as suggested by AMAZINGAHMED.Although even this too is not too difficult to unlock for person well versed in SIMATIC programming. There are some better know how protection features in the new S7-1500. I have yet to try the same.. Cheers Navnag |
Last edited by: Navnag at: 7/8/2013 10:23 AMThere is no such thing as the last bug in a program |
|
This contribution was helpful to2 thankful Users |
Follow us on