Enhancement Request: Don't start operation for a tool if it will hit soft limits about iosender HOT 4 OPEN

However, it would be preferable if ioSender checked the operation was possible prior to starting it.

I have no plans to add sanity checks on running gcode in the sender, IMO too much work for little gain.

from iosender.

@R-Ronald You can run your program in check mode and controller itself will do all sanity according to current setup and position.
What would be helpful from IoSender side - clear readable execution results report with execution results, error codes, last executed program line and content, execution time, any intervention by user, like pause, feed override events with timestamp and effective program string etc.
Unix-stile log file with supporting window in GUI looks good for me.

from iosender.

You can run your program in check mode and controller itself will do all sanity according to current setup and position.

This is not good enough when there are tool changes involved that is likely to change offsets that check mode cannot know anything about.

from iosender.

i.e., before you actually go far enough to generate the offset for the tool in a specific operation, check mode is missing data about how the Z axis will need to move.

from iosender.