Peter Nachtwey
Member
What features or policy should there be for protecting
1. source code
2. binary code.
Should we have a back door to unlock the code or should the end user be forced to go back to the OEM to unlock the code and make changes. I don't want to have a back door but that will also limit our ability to help the end user in a jam.
A second issue is protecting parameters and variables from erronious writes and changes. We have a look only mode in our older software setup software. We can add that feature to our new setup software but:
1. Should we have a look only mode for the HMI?
2. Should we have a look only mode for the PLC?
Issues.
1. The customer needs to be able to move the code from one controller to another spare in the event of a failure.
2. The OEMs don't want people to copy their programs
No good deed goes unpunished. We store the source code on the motion controller in both binary and source forms. Many of you thought that saving the project on the controller ( PLC or Motion ) would be a good thing. Now I am getting hit with requests to be able to copy protect the source code AND the binary code. I can see we have put our foot in it now. The users and OEMs will have different opinions, but I would like to hear some.
1. source code
2. binary code.
Should we have a back door to unlock the code or should the end user be forced to go back to the OEM to unlock the code and make changes. I don't want to have a back door but that will also limit our ability to help the end user in a jam.
A second issue is protecting parameters and variables from erronious writes and changes. We have a look only mode in our older software setup software. We can add that feature to our new setup software but:
1. Should we have a look only mode for the HMI?
2. Should we have a look only mode for the PLC?
Issues.
1. The customer needs to be able to move the code from one controller to another spare in the event of a failure.
2. The OEMs don't want people to copy their programs
No good deed goes unpunished. We store the source code on the motion controller in both binary and source forms. Many of you thought that saving the project on the controller ( PLC or Motion ) would be a good thing. Now I am getting hit with requests to be able to copy protect the source code AND the binary code. I can see we have put our foot in it now. The users and OEMs will have different opinions, but I would like to hear some.