Operator Controls - limit access?

[spumco]

New build design in progress and I've got some questions about operator access to controls.

Apologies in advance for a long-winded post.

Background - machine will be a router-style thing (XYYZ) that will only be used for a few different parts, all of which are similar.
Hickory, Leadshine EL8's, CNCDepot spindle, 6-tool rack ATC... nothing exotic.

All parts will be clamped on a fixture, the fixture(s) will be located in the same place, and the part programs will all be based on a single reference point that never changes in relation to the machine coordinates.

Tools will be touched off before each use and after use (breakage check) automatically - no operator intervention save for replacing worn/broken tools.

The machine will be operated primarily by non-machinists, so I'd like to be able to 'turn off' virtually every machine control except a few functions (cycle start, stop, part clamp, etc.). I also need to enable all controls for setups and part prove-out by myself or a trained supervisor.

I understand that an operator could go in to MDI and program the machine to crash or whatever. Not worried about that... just don't want lots of inviting buttons or MPGs or similar that are easily activated by the terminally curious or bored.

Basically, I want something similar to a 'setup' keyed switch, or a 'special-mode' switch on older CNC controls used for jogging/adjustments with the doors open.

Step 1 will be to use a 4:3 monitor and turn off the VCP
Step 2 is to disable keyboard jogging and Alt-J panel pop-up
Steps 3 through XXX get murky

Option 1
On some other cnc controls I could have the machine automatically start up with an Operator profile (with all panel buttons disabled). When setup work or other admin functions were required I could restart the CNC software in an Admin profile. Both profiles are identical, except the Admin one has the panel controls functioning.

However, I've been pouring through the CNC12 manuals and I don't see anything about having different 'profiles' available. Have I overlooked something?

Option 2
All controls which are to be restricted are connected directly to Hickory inputs. And an 'admin' switch - keyed or not - is located inside the control panel. The admin switch simply turns off common power to those switches I need to inhibit. I've probably got enough inputs left on the Hickory for basic controls.

Option 3
Is there a way to have an X-keys based panel that I can turn on/off using a parameter bit?

And can I set a parameter using an input pin? (i.e. admin switch) If so, that'd be nice 'cause I could just turn key keyboard Alt-J and overlay back on without bothering with an x-keys.

I'd welcome any ideas regarding the above, whether hardware or software-based.

Thanks

[Ken Rychlik]

I would suggest removing most of the buttons in the vcp. Any command you would want to use can be pulled up in a macro, or done in the mdi. Just have a few basic buttons for homing, measure tool, and whatever suits the purpose.

The screen change could be done with a different skin file for the vcp. Load the admin skin file to work on things, and load the user skin file to give them less buttons to mess with. Same machine setup with two vcp skins.

If it homes with sensors, and has soft limits, that would prevent them from crashing the machine using the mdi.

Wizard settings can make the arrow jog buttons work or not be enabled.

Having password access to the Wizard might help you, but I don't know if that's an option.

Whenever they mess something up, restore report gets it back easily. I put a flash drive with a report zip tied in the controller of each machine.