OEM questions

[cncdrive]

Does UCCNC have plans to be able to compile macros to protect teh macro code ?

We did not plan to do it.

Is there a way to link macro operations to teh device serial number so that they will not run with any device other than teh registered device ?

Well, you can read the serial number field and do something or not do something based on the number.

Are there any plans for safety functions like door switches and safety lockout switches as well as password protection on startup ??

Door switches can be added for example to limit inputs.
I know you mean to slowdown the spindle etc. when the door is opened, but that is not allowed in the EU. I'm not sure what the safety standards say about it in the US.

The password protection in my opinion is not a good idea. I see the lots of emails and phone calls coming in about how to fix forgotten password issues.

How about a function to limit operations until teh machine is homed ??

I don't think we will put it in the core anytime soon. But ofcourse plugins could do limitations, e.g. a plugin could cancel the Cycle start if not homed etc.

[Robertspark]

it is possible to call the device serial number via field #906.

hence via plugin you could call the serial number and then link it to a product actvation code which will limit use of the code.
why not call the macros via plugin? using:

Informplugin()
Function: object Informplugin(string Pluginfilename, object Message)
Description: This function sends data to one plugin. The Pluginfilename
parameter defines the name of the plugin to send the message to and the
parameter is an object and the return value is also an object.
Example:
string teststr = "Hello Plugintest.dll...";
object Returnvalue = exec.Informplugin("Plugintest.dll",
(object)teststr);
if (Returnvalue is string)
{
string str = Returnvalue as string;
MessageBox.Show(exec.mainform, "Return message was: " + str);
}

you can then have macros which just call
M7500.txt
Informplugin(lockedMacro.dll, M7500)
have the macro wait for the return string value, which will advise the macro action is complete before proceeding

and you plugin does a sort of checksum on the device serial + an activation code, and implements the code

[cncdrive]

That would require lots of codes to be rewritten, so we will not do that now for sure.
We think the more important is to upgrade the motion planner to S-curve.
Once we will reach a stable state in the current test release then we will start working on that and meanwhile all other developments will be frozen.
And it will probably take months to finish.