System homes but unresponsive

I've been automating a small Mill.
I keep running into problems and people here have helped - thank you.
Mesa 7i95t et al.
I've got to the point where I can click the home icons on my Gmoccapy screen and it homes all three axes.
Then I move the head onto the middle of the bed with the on screen jog buttons and load a piece of program
that is basically just a set to G54 mode and do a G0 X20 rapid flip 20mm positive on the model hence the bed should move left.
Once I have that it's just relearning g code time.
But nothing happens.
I add a growing number of lines to set things up.
Still nothing. It gets to that line, highlights it and just sits there probably waiting for something or feeding at 0 so it will never end.
I've spent most of the day trying new ideas.
This is where I've got to. What do I try next? What do I take out? What obvious thing have I missed?
What do I have to do to make it move?
Is it my code? My configuration? Is it offended at my accent? Does it just hate me? (it feels a bit like that)

G1 changed back to G0, I was trying G1 as a test and it didn't help

Does it have any spindle feedback?
Is the spindle.at-speed set to true?
Use the "show hal configuration" from the "machine" menu to watch the pins.

No spindle anything at the moment.
I have parts ready to install but I hoped to see the motion system working first.
(power relay, reversing relay and the pwm to 0-10V parts for the speed controller)
For the G0 neither of my Spindle CW or CCW outputs are setting which seems reasonable.

I was surprised to discover spindle.0.at-speed was set but it must be some sort of default as there is nothing wired.
Are there any other 'must have' items you can think of?
(I only set the S code in case it wanted it when I was starting to get desperate.)

Can you run your gcode and when stalled then

run (in a terminal)  :

halcmd show all motion. > motion.txt

( Note the . after motion )

and post motion.txt here

 

Woo, thanks for help

Not a gcode expert but I suspect a gcode issue because:

29 float OUT 0 motion.feed-inches-per-minute
29 float OUT 0 motion.feed-inches-per-second
29 bit IN FALSE motion.feed-inhibit
29 float OUT 0 motion.feed-mm-per-minute
29 float OUT 0 motion.feed-mm-per-second
29 float OUT 0 motion.feed-upm

The feed rate is set to 0

(or feed override in the GUI is set for 0)