Reading value of pin in g code

It can't be stopping at line 4. It is executing line 8.

LinuxCNC supports two sorts of parameters (what might be called variables in an actual programming language, which G-code probably isn't).

#4 is a conventional mumerical parameter
#<myvariable> is a named parameter, an extension to the G-code standard supported by LinuxCNC
#<_myvariable> is a named paramter with global scope (which means that it has a value which can be used outside of the subroutine it is defined in)
#<4> is a named parameter. It will not necessarily have the same value as #4
#<_4> is another named parameter with global scope. It can have a different value to both #4 and #<4>

Can you attach the G-code file, so far we have only seen it as a screen-shot.

Can you have a halmeter look at the actual value of motion.digital-in-11 (and 12, and 13) rather than assuming that the HAL net is working?

Did you increase the number of digital inputs in the loadrt motmod line?

Can you insert a (debug, line-no #5399) before each "if" to see what the actual value being used is?