its a wearied problem

Hood,
I just tried Daniel's XML on my development machine running Ver. 062, and a G0 X300 command runs at the speed set by the FRO slider.  It most assuredly is not running at the XML set velocity of 1500 (IIRC) units/min.  With my standard XML and the 1024 screen, it does not respond to FRO speed.  Something is wrong, IMO, with Daniel's XML.

Best to All,
John Champlain
www.picengrave.com

The FRO slider will act on this when FRO goes lower than 100% as Rapid is Locked to FRO on General Config.
It does seem that it is doing a G1 move when it should be a G0 though. I had only been looking to see if the initial MDI move was very slow as Daniel had stated and had not looked at motor tuning.
Why the G0 are being treated as G1 moves I am not sure, cant seem to find any reason for that, when I get some time I will make a duplicate xml and see if it happens with it.
Hood

i had a play with settings yesterday if I set the initialization string to say f400 g80 it move all axis at f400 if I use the MDI screen first before I load a gcode as I haven't mounted the home swithes yet. if I hit ref all home after setting home location the problem is gone. so what I will do is set initialization string to f400 g80 for now, when I have home swithes mounted I will just hit ref all home then if I type a move into the MDI screen there will be no problem. this was what I did with old machine that's way I only found this problem now.