Timelapse Enforce Position issue with 0.91
Hi there,
I was super happy to read about the enforce position feature in the 0.91 update.
So immediately gave it a shot! Put position to 150x150 and started printing. After first layer the printhead moved to the position, stayed there a bit and moved back to the part to print. But then suddenly the extruder reversed a good 10cm before it started to print.
This happened on every layer until I cancelled. Printer moved to picture position, and back and then the extruder reversed the filament out of the printhead at full speed....
does not happen if I do normal timelapse for each layer without enforcing position...
any ideas? Any details I can provide you with?
Keep up the good work with Repetier Server! Love this software the enhancements to the touch ui are very nice!
Kind Regards
I was super happy to read about the enforce position feature in the 0.91 update.
So immediately gave it a shot! Put position to 150x150 and started printing. After first layer the printhead moved to the position, stayed there a bit and moved back to the part to print. But then suddenly the extruder reversed a good 10cm before it started to print.
This happened on every layer until I cancelled. Printer moved to picture position, and back and then the extruder reversed the filament out of the printhead at full speed....
does not happen if I do normal timelapse for each layer without enforcing position...
any ideas? Any details I can provide you with?
Keep up the good work with Repetier Server! Love this software the enhancements to the touch ui are very nice!
Kind Regards
Comments
It goes to Photo position, returns to print part, retracts about 50mm and then resumes printing. Any other ideas?
https://www.youtube.com/watch?v=ckbzS5plnw0
To test M400 send some long slow moves and then
M400
M114
If you see coordinates in log before move is finished M400 was ignored.
We send 24 M400 to flood input buffer so if we receive a ok we know moves are through. This means ultimaker buffer must be smaller then 24 * Nxxx M400*23 which will be at least 13 byte so 24*13 = 312 byte. Not sure how much Ultimaker buffers, but marlin does normally only 127 byte in input queue. Also it is more important that host would not send them according to his queue size, so guess size is not the problem. Only if M400 does wait for end of moves or not. More exactly server checks marlin.xml and sends this command
so you can even modify it if does not work.