Getting rid of the 'File incomplete' message by changing '#define END_FILE_SECTION' in firmware?
 

Getting rid of the 'File incomplete' message by changing '#define END_FILE_SECTION' in firmware?  

  RSS
wybren.c
(@wybren-c)
New Member

Hey all,

I am slicing with IdeaMaker for a Prusa Mk3 and I get the 'File incomplete' warning every single time. The prints work fine, but it is an extra button click and when the SD card file is actually corrupted I won't know till the print actually fails.

The reason I get this message is most probably due to IM adding a lot of lines at the end of each gcode. It seems the Prusa firmware checks the last 20000 bytes of gcode to look for the 'M84' command, and these 20000 bytes are now filled with other data.

Line 111: https://github.com/prusa3d/Prusa-Firmware/blob/MK3/Firmware/variants/1_75mm_MK3-EINSy10a-E3Dv6full.h

One solution is to get rid of those extra lines IM adds, I am proposing that at the Raise3D forum. The other solution is to manually change this value from 20000 to a value large enough to include the M84 line. Is it possible for a user to change this in the firmware?

Best Answer by tam.a:

I think I found the culprit. I'm just running a test print now to see if there is anything odd but it has stopped the "File incomplete". Uncheck these 2 settings shown below.

This topic was modified 1 year ago by wybren.c
Posted : 19/06/2019 9:44 am
bobstro
(@bobstro)
Illustrious Member
Posted by: wybren.c

[...] The reason I get this message is most probably due to IM adding a lot of lines at the end of each gcode. It seems the Prusa firmware checks the last 20000 bytes of gcode to look for the 'M84' command, and these 20000 bytes are now filled with other data.

Ah, interesting. I posted previously about this same issue. I found that removing the extra code worked, but never knew why. It sounds like running the IdeaMaker gcode through a post-processing script to either remove those lines or simply move the end gcode to the very end is a temporary work-around.

As to the big chunk of ASCII-encoded binary that IdeaMaker embeds: My understanding is that it is to support some auto-restart and other features of the Raise 3D printers. They may not be too open to the idea of removing it, but perhaps they'll include a simple option to turn it off. IdeaMaker is undergoing some rapid development. While it's still my #3 slicer, a few improvements may move it up. Their supports and automatic adaptive layer heights are very good. It's unfortunately not open source, but it's a very nice free slicer.

My notes and disclaimers on 3D printing and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan...
Posted : 19/06/2019 12:52 pm
tam.a
(@tam-a)
New Member

I think I found the culprit. I'm just running a test print now to see if there is anything odd but it has stopped the "File incomplete". Uncheck these 2 settings shown below.

Posted : 03/07/2020 12:03 pm
bobstro
(@bobstro)
Illustrious Member

I think that's a new feature in ideaMaker. I'm no longer getting the message since updating to the latest release.

My notes and disclaimers on 3D printing and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan...
Posted : 03/07/2020 2:55 pm
tam.a
(@tam-a)
New Member

Ah. The only reason I posted was because I was getting the same problem until I discovered those settings where they are both checked in Chris's ideamaker profiles.

Posted : 04/07/2020 8:39 am
bobstro
(@bobstro)
Illustrious Member

Raise 3D is doing a lot of work on ideaMaker and have some interesting ideas of their own. Definitely check out their forums. They're very responsive.

My notes and disclaimers on 3D printing and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan...
Posted : 04/07/2020 3:06 pm
wybren.c
(@wybren-c)
New Member

@tam-a

Wow thanks! This has been a small issue for a long time, apparently it has been fixed somewhere in the last updates, but I wasn't aware. Thank you for informing me!

Posted : 06/07/2020 8:09 am
Share:

Please Login or Register