FlasForge Adventurer 3 machine start gcode fix #6282

[GabrielJanucik]

Description

For every project in FlashForge Adventurer 3 printer custom line was created on the edge of print field making sliced project impossible to print (line was out of plate). Default gcode for machine has been changed around 3 months ago. I have removed new code and now default start gcode is the same as provided in offical Adv3 manual. Code has been tested on my machine before push.

Screenshots/Recordings/Graphs

Tests

Tested with calibration and custom files on linux (Ubuntu 22.04) and printed.

[SoftFever]

LGTM
Thanks

[RikshaDriver]

@GabrielJanucik I am the author of ALL the Adventurer 3 parameters added into OrcaSlicer thus far. This change was added to allow a pre-extrusion as the printer needs it.

FYI, the print is not actually out of plate as the printable area is larger than the quoted 150x150mm dimensions, but Flashprint will complain it is. This is likely what you're seeing.

If you wish to change anything, adjust the Y -75 values to something like Y -74.5

@SoftFever please revert this change

[GabrielJanucik]

@RikshaDriver but pre-extrusion is always added anyway on any custom objects. I agree that it doesn't appear on calibration prints and understand that is needed.

EDIT: I also saw people complaining about this bug few times on FlashForge users Fb groups. Sometimes there were other people giving them advice to edit that start code but sometimes I was the first one.

Here is preview of benchy sliced with mine changes and there is pre-extrusion/skirt around the object.

[SoftFever]

@RikshaDriver but pre-extrusion is always added anyway on any custom objects. I agree that it doesn't appear on calibration prints and understand that is needed.

EDIT: I also saw people complaining about this bug few times on FlashForge users Fb groups. Sometimes there were other people giving them advice to edit that start code but sometimes I was the first one.

Yeah, some people prefer skirt others prefer custom prime line.

Back to the original issue.
By right, Y-75 should be a valid coordinate per machine's definition.
It's might be a bug in their firmware.

I agree with @RikshaDriver here that changing it to Y-74.5 is a good idea.
@GabrielJanucik What do you think?

[GabrielJanucik]

@SoftFever I think that now I understand it, at least more so I agree with that. Do you want me to create new PR with revert and value change?

[SoftFever]

@SoftFever I think that now I understand it, at least more so I agree with that. Do you want me to create new PR with revert and value change?

Yes, a new PR is appreciated!

[GabrielJanucik]

New PR created #6744