Skin Event Numbers

[Lance801]

I have a question regarding VCP Buttons.
I have noticed that a couple of the buttons I want to use have the same skin event number.
For example, "set_x_0" and "Aux1" both share "skin event number 3"
My question is: Is this going to create a conflict if I use both of these buttons on my VCP? I noticed one has PLC logic and one does not.
I also noticed that the PLC code says that the number of total Skin Event Numbers is 225 but only about 120 or so are assigned.
I have created a few new buttons of my own and have saved them to the buttons folder but they are missing the XML text as they do not have an assigned skin event number. Can I add some to the PLC code and then create an XML file to add to my custom button?

[Ken Rychlik]

Since I found out you can now skip the skin event numbers, I have the buttons directly run macro's in the system folder.
You still have to modify the skin folder, but in the button file instead of a skin, you can directly have it run a named folder.

Me keeping up with which skin called what number macro, and what number macro was for what purpose was a pain.
The only trouble with direct to the system folder option is they do not get copied into the report, so you have to keep a backup of them along with a report.

Two macro's with the same skin event will be trouble if you decide to stay with that approach.

The section below shows how to run a "macro" directly from the vcp button, but it has to be a .cnc file and not a .mac file. All of the names have to match also. This is from the button folder and what you would use instead of the skin #

<vcp_button>
<run>
<macro>c:\cncm\system\perform_tool_change.cnc</macro>
</run>
</vcp_button>

[cnckeith]

vcp manual covers this with examples as well.
https://www.centroidcnc.com/centroid_di ... manual.pdf

[grossmsj]

Since I found out you can now skip the skin event numbers, I have the buttons directly run macro's in the system folder.
You still have to modify the skin folder, but in the button file instead of a skin, you can directly have it run a named folder.

Me keeping up with which skin called what number macro, and what number macro was for what purpose was a pain.

This is a great improvement. It makes things so much easier.
Any reason I can't convert all my custom macros over (I think not)? I suspect there are some specific mfuncs that can't be converted over? Is there a list of these?

[Ken Rychlik]

Most any of them can be moved there. Just a that a normal restore report won't put them back in, so be aware of that. There are two system folders in the report.

[grossmsj]

Thank you, Ken. Since I use scripts (thanks ShawnM!) to facilitate the upgrades, I'll just make another to handle the system folders. I'll use that to restore those macros.

[ShawnM]

Thank you, Ken. Since I use scripts (thanks ShawnM!) to facilitate the upgrades, I'll just make another to handle the system folders. I'll use that to restore those macros.

I'm still working on my new script file Scott for 5.2 to grab all the needed info for a new CNC12 software install. As you know many things have been moved around and changed for 5.2 so there are many changes to my current script file for 5.1 and earlier.

For now, put all your custom macros in the C:\cncm\system folder (like 5.2 already does) and call them from there in the button xml file. If you keep them all in this folder they'll be picked up when you create a report so you dont have to worry about losing them.

[cnckeith]

yeah don't use restore report from old version on a new version of cnc12 unless you want to copy over all the old cnc12 parameters that will break the new version.