Printer head collides with print on completion
This is with the just replace 4-3-4 firmware and slicer 2-4-0, so perhaps the issue has been resolved already by a more recent release.
When the printer finishes a job, the printer head returns to xyz=0. On this occasion the printer collided with the print while doing so with such force that it pushed the printer bed out of position and scratched the model. Fortunately neither seems to be seriously damaged, but it could easily be imagined. 
The build plate is textured steel spring plate.
After the print completed, filament leaked out of the nozzle directly onto the print platform. Again, it doesn't look like there's any damage, but I'm confident this behavior is undesired.
I apologise if this issue has been reported and resolved; but I didn't feel like patching up and reprinting a four day print just to see if it's fixed.
RE: Printer head collides with print on completion
Which version of Prusaslicer was used ? Maybe download the latest version and reslice.....
Texy
RE: Printer head collides with print on completion
Maybe I am mistaken here but I doubt this has anything to do with the firmware. All printer movements should be part of the g-code (which you can open with a text editor yourself, it is plain text), including the end moves. I would check what "end"-g-code you have in your slicer and if that is the same to what you have when you re-install the slicer with stock settings.
Mk3s MMU2s, Voron 0.1, Voron 2.4
RE: Printer head collides with print on completion
@Thejiral There was an older version of the firmware that didnt play well with PS 2.4 and did exactly this (v4.3.2 iirc). There are several posts on here and github about it. Updating to the latest firmware fixed it though.
As 4.2.4 is the latest I am wondering if there has been a regression in the latest latest though. Would be useful to see/duplicate with a smaller print with PS2.4 and then update to PS2.5 to see if that resolves it.
If not then it might need reporting on github.
It would also be worth the original poster saving the project file, zipping it up and attaching it here so that the end gcode can be checked to see if anything is out of place.
RE: Printer head collides with print on completion
@Thejiral There was an older version of the firmware that didnt play well with PS 2.4 and did exactly this (v4.3.2 iirc). There are several posts on here and github about it. Updating to the latest firmware fixed it though.
As 4.2.4 is the latest I am wondering if there has been a regression in the latest latest though. Would be useful to see/duplicate with a smaller print with PS2.4 and then update to PS2.5 to see if that resolves it.
If not then it might need reporting on github.
It would also be worth the original poster saving the project file, zipping it up and attaching it here so that the end gcode can be checked to see if anything is out of place.
The old firmware only looked at the last 10k for end g-code. The new slicer produces more than that, so the old firmware missed some of the end g-code. This often resulted in not parking the head in the right position after printing. The newer firmware looks at the last 20k. This was in the release notes for 4.3.4
Support for PrusaSlicer 2.4
The PrusaSlicer 2.4 is currently in the beta stage and you can read more about its new features here. Some of the changes introduced in version 2.4 have a direct impact on the firmware and in order to work correctly, the developers had to make some adjustments.
Starting with version 2.4, the G-codes have a larger allocation for the context information, which is located at the end of the G-code. Previously, it was enough to read the last 10 KB, however now it is necessary to extend the search for the last 20 KB (similar to the MK3 family). Thanks to this adjustment the printer is now able to correctly read the type of the filament, its usage and display it correctly on the print preview screen.
Regards,
Mark