Is there anyway to see when the printer has actually executed the gcode command?
I'm using Octoprint with my MK4 and am monitoring prints on a gcode viewer to see the live progress. I'm using the octoprint.comm.protocol.gcode.sent hook to send the gcode commands to the viewer which works well but is always displaying commands slightly in the future of where the printer actually is.
I believe that this is because when Octoprint sends the command to the printer, the command goes into the command buffer and is executed sometime later, but the gcode viewer is setup to show that as soon as the gcode sent hook is fired, it should be updating the print accordingly with the new gcode line.
I did not get better results using the Octoprint "gcode received" hook either, so I am wondering if there is some custom firmware or any workarounds that anyone has found to get a closer approximation of when each gcode command is actually done being executed by the printer, and not just sent to the printer for processing