jimpad
Member
Hi all,
I will be selling my code to machine builders. To protect my code I'm planning on using the password feature of the D06, but I need to allow tech's to download new features when desired. So, I will use dnloader w/password feature (I know there are bugs w/dnloader but I've been working w/host engr and feel confident they will fix). The problem is how to prevent downloading code into other machines (copying the code). I'm thinking of developing "authorization" logic which will prevent the ladder from executing unless the tech supplies the proper key which he can only get from me. I see it like this.
1. Tech downloads logic to plc.
2. Authorization logic runs in plc and creates unique authorization "code".
3. Tech reads "code" and contacts me for authorization "key".
4. Tech inputs "key" into plc and authorization logic checks "key and allows/disallows complete ladder to execute.
I'm looking for opinions, examples, etc.
Thanks,
Jim
I will be selling my code to machine builders. To protect my code I'm planning on using the password feature of the D06, but I need to allow tech's to download new features when desired. So, I will use dnloader w/password feature (I know there are bugs w/dnloader but I've been working w/host engr and feel confident they will fix). The problem is how to prevent downloading code into other machines (copying the code). I'm thinking of developing "authorization" logic which will prevent the ladder from executing unless the tech supplies the proper key which he can only get from me. I see it like this.
1. Tech downloads logic to plc.
2. Authorization logic runs in plc and creates unique authorization "code".
3. Tech reads "code" and contacts me for authorization "key".
4. Tech inputs "key" into plc and authorization logic checks "key and allows/disallows complete ladder to execute.
I'm looking for opinions, examples, etc.
Thanks,
Jim