Hardware Dongle to WC8

[LarsK]

Yeah, that's right there is a Hardware dongle for the WC8! I was wondering how to lock some software I'm developing (VB6) to a single WC board. (One license/one board)
Then I thought about the temp sensor. As we know it has a genuine romcode. So, I just ask the WC for Temp1 romcode. Result like: "28BD5CBF0300"
If good = licensed, bad = exit So, I implement the serial check for "my" Dongle in the software. You can even mold the temp sensor in a potting if needed.
 

 

[CAI_Support]

Hi Lars,
 
In our later firmware, there is a PLC command, "protected", once you entered that into PLC code, the PLC code will no longer displayed.  You can overwrite it with your new code, but you can not read the PLC program any more.

 

[LarsK]

Yes, that's a nice option.
I have a older version, so I was not aware of that. :unsure:
Still, with my solution, the user can do whatever he want's with the WC and the dongle will work when needed.

 

[CAI_Support]

Lars,
 
You are right.  With older firmware, your method works.  I know shipping cost from Norway to USA is high. If you ever have chance to send them back for firmware update, we will update them for you.

 

[az1324]

Couldn't you use the MAC address?

 

[LarsK]

Yes, but then I have to know the spesific mac adress before compiling the software. And, if the user changes the computer, I need to make a new update.
Using a temp sensor the user can use it where he want's, but still he can only use it on one computer at the time.
If I have sold 100 licenses, I just add the rom code for the 100 temp sensors inside my software.
When sold, I just update the software with more rom codes at the next update.

 

[rossw]

Yes, but then I have to know the spesific mac adress before compiling the software. And, if the user changes the computer, I need to make a new update.
Using a temp sensor the user can use it where he want's, but still he can only use it on one computer at the time.
If I have sold 100 licenses, I just add the rom code for the 100 temp sensors inside my software.
When sold, I just update the software with more rom codes at the next update.

 
Smarter again may be to use a webset.  Send the ID to your server and return an appropriate response.
Then you update YOUR side. You can enable or disable without having to update everyone elses code, it's scalable, and better yet, you can turn someone OFF without having to access their code.

 

[LarsK]

Nice idea, I have to dig into that option!

 

[rossw]

Nice idea, I have to dig into that option!

 
I shouldn't give away too many secrets... but if you get clever, you can have more features in your code and only enable the ones your customer has paid for.
It means if they want extra option (x), you don't have to change the code, you just change the response your server sends back, and let your (existing) code do the extra functions. Makes upgrades and keeping track of versions heaps easier. (But it does assume your WC is able to access the server. There are ways around that too, which I will leave to your imagination)

 

[LarsK]

I have choosen to stay with the Dongle solution. I have a db in my software containing all licensed dongles. Due to the issue that many users may will be seldom or newer online this solution serves me best.
I have done some intensive test's, and the dongle seems quite foolproof. Also I will protect my software with anti debugging/unpacking tools. (I'm quite good in reverse engineering...)
Here is a pic showing the license part of the program:
 

 

[az1324]

Proxy server that rewrites the dongle ID with a valid one?