About the position update - have you analyzed my code at all ?

It is your responsiibility to update Mach variables  - it is your plugin which is supposed to create motion according to given trajectory and report back the result ( as position).

Once uoy update position, you will also get tool view updated.

Thank! I've read most of your code and I solved the problem.

About th M3 stop - Well, I do not understand what you really mean.

I have put in this line a breakpoint and M3 arrive in this line only when have read the last line of GCode. it is correctly?

Thanks
Marco

ps. I have another question but i think you kill me!

hello!

my question: what is the relationship between kernel velicity, ExternalPulseRates, motor velocity, ExBufferHi and ExTime?
i don't understand what values ​​should I put...

thanks
Marco

finalizeMoves() is called when Mach finishes your Gcode processing - so it is correct behaviour.

About:  ExternalPulseRates, motor velocity, ExBufferHi and ExTime - these are configuration variables for your plugin. All these settings are independent. Most were described in my plugin.
 ExternalPulseRates - your max step signal frequency
 ExBufferHi - max lookahead buffer for movements
 ExTime - tyime slice for single motion record ( time period with constant speed data records you get from trajectory)
 motor velocity - this describes CNC machine movement constrains

I have a new question  

whene home function is called by M3?

regards
Marco

No idea - but this you can easily debug and trace producing such code.

But - M3 is related to spindle control - whay do you ask about homing ( which is something different)

I have in my CNC a three homing sensors and I have no idea how to handle them.
I use my homing sensors as inputs?

when I push "REF ALL HOME" in a GUI, What does this mean?

No idea - but this you can easily debug and trace producing such code.

I have inserted a breakpoint in home function, but this is never called!

Well, home function is being called once you tell Mach  to home axis.
The basic idea is that you configure your inputs as "home inputs" so Mach knows which inputs to use when executing home procedure

Ok, i have enabled home input and and i have pushed REF ALL HOME button, but motors do not move...

The bad news is that once you make motion plugin you have to code the homing motion yourself - Mach will not do it for you. See my code - I had to calculate everything myself and send my own motion commands to my hardware controller.

See Home() function in the plugin template - it is called for homeing