Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] "Test mode" logging profile should strip firmware retract GCode #167

Closed
gege2b opened this issue May 16, 2018 · 7 comments
Labels
resolved This issue has been resolved

Comments

@gege2b
Copy link

gege2b commented May 16, 2018

Hi there

If this is a feature request describe it here

"Test mode" logging profile is working fine (at least on my setup) except he doesn't strip the Firmware Retract/Unretract GCode (G10/G11 in all firmware supporting this feature, as long as I remember), so while printing in test mode, the extruder still makes the retract/recover during all the print if the firmware and the Gcode are FW_Retract-enabled

It's not really a problem if filament is unloaded (as recommanded) but still useless, avoiding them would slightly speed up the test-print time and will reduce unneeded wear on geared extruder

Version of Octolapse

Octolapse Version: 0.3.1

Version of OctoPrint

OctoPrint Version: current dev ( 9a881012e200da3e071ca41307459cfbb987fb50 )

@FormerLurker
Copy link
Owner

I'm still learning about gcode and have never seen these before, so thanks for posting the issue! It's not too difficult to add this, so I will do so! Hopefully I'll be able to work this in soon. I'll update this ticket once this is finished.

@FormerLurker
Copy link
Owner

Ug, G10 is also used for tool offsets on some firmware. G11 won't be a problem, but I'll need to handle g10 as a special case. It looks to me like G10 without a P parameter is a retract according to this.

I really wish there was a gcode standard for 3d printers!

@gege2b
Copy link
Author

gege2b commented May 16, 2018

it's tricky 🤣

agree on the G10, looking if the Pxxx is present should be enough to decide if the gcode can be stripped

@FormerLurker
Copy link
Owner

Hey, I have added initial support for firmware retract and detract, and suppression during test mode. In order for firmware retract/detract to work with retraction and zhop detection in Octolapse(strongly advised), you need to add an M207 command to your start gcode specifying the retraction length at a minimum (EG M207 S4). Octolapse supports (in theory) all of the available parameters, but they have been minimally tested since my slicer can't even handle them all :)

@FormerLurker
Copy link
Owner

Oh, I forgot to mention, this is only in the devel branch right now. I'm going to push an RC as soon as I can get some testing finished.

@gege2b
Copy link
Author

gege2b commented Jul 17, 2018

Great ! I will give it a try as soon as I can (not now, otherwise I'll stick behind my printer without doing what I'm supposed to do today 🤣 )

@FormerLurker FormerLurker added the resolved This issue has been resolved label Jul 23, 2018
@FormerLurker
Copy link
Owner

I'm closing this out since I think it works. Let me know if I should reopen it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
resolved This issue has been resolved
Projects
None yet
Development

No branches or pull requests

2 participants