Delaying motion enable after machine-on

The machine I've been working with requires some time (about 6 seconds) for self-sensing commutation before any user control is accepted. I'm trying to figure out how to account for this between the UI (Axis currently, custom UI later) and HAL.

The sequence I'd like to have is as follows:
1. E-stop is reset (External signal connected to physical switch, also connected to UI)
2. Machine control is powered on (UI button or external switch), BUT a message like "Wait for initialization" is displayed and NO MOTION is possible until external signals from the drives meet certain criteria (commutation complete, no fault, etc)
3. Message is cleared and homing can then be performed. When complete the machine is ready to use

Is what I'm trying to do possible? It's like I need the "power on" UI button to go into an intermediate state while initializing then be completely active when done.

I mentioned that eventually this should have a custom UI so I'm not set on having it work with Axis if it's too much trouble.

I gave Andy's suggestion a try with the following:
Testing it in AXIS sim, it correctly prevents jogging via the UI for 7 seconds. It does _not_ prevent homing.

I'm not satisfied with the message output facility either. It lumps them all down in the bottom right corner with the rest of the error messages. Maybe if there was a way to clear them it would be acceptable.

I'm going to rethink this. It's close but not quite what I'm going for.

Actually, enabling the amps with e-stop release could work. I'm going to think about safety implications, but so far nothing obvious springs to mind.

I'll try your other suggestion this evening, and play around with some other ideas.

Thanks.

Just a thought. If you added a screen text value, I think you would be able to change its contents (or just hide it) in the screen handler. I'm not sure how axis does it but i've done similar stuff in gmoccappy's python screen handler. Create a pin in the handler and send the value of interest to it and use it to change the screen.

What happens internally when you click the UI "machine on" button in Axis? Can it be intercepted?

That sounds like it has some merit. I'm not quite to the UI point yet so I'll tuck this tidbit away.