-
Notifications
You must be signed in to change notification settings - Fork 0
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
Zupfe & Octoapp conflicting? #4
Comments
OctoApp dev here :) I started adding these Gcode commands in a pre-processing script to send notifications during the print. It's valid Gcode, so I'm a bit surprised this causes issues. Happy to help to troubleshoot this :) In the meantime, downgrading to the OctoApp plugin to release 2.0.10 by installing the plugin in OctoPrint's plugin manager from this URL will "solve" the issue: |
Hi, I checked by adding the instruction "M118 E1 OCTOAPP_DISABLE_LAYER_MAXIC" on a gcode file and uploaded it to ZupFe, and also to an OctoPrint instance and it loads correctly into ZupFe. Could you upload one of your files here please ? |
This file is processed by the plugin |
I confirm that ZupFe fails to load properly the content of the file since there is too much failed gcode instructions found. In fact, i have set a 10% threshold for invalid gcode and since OctoApp adds gcode, in reaches this threshold. The gcode file provided by Christian will be useful to fix ZupFe and implement those missing valid gcode. |
Hello @crysxd, when you inject commands into the gcode from your plugin, did you check whether line endings are CR, LF or CRLF ? By inspecting your provided file, it seems that there is a combination of CRLF and LF where I suppose the original file is LF. |
Hi @glennerichall! That's correct, I always insert |
Oh it was but it will be fixed it in zupfe as this should not be. Thank you. |
We all love our CRLF and LF :D That caused me some trouble in the past as well. Thanks for sorting this out! |
@romanr9999 I have fixed some gcode parsing errors in v1.3.54. Could you confirm that it does not conflict anymore with Octoapp ? |
I noticed lately (not sure when this started) that I can't see files on Zupfe cause when loading it gives me a "xxxxx.gcode is not a G-Code file".
I also noticed that the first line on my gcode files reads "M118 E1 OCTOAPP_DISABLE_LAYER_MAXIC" and that lines makes Zupfe to give the error.
I tried commenting that line, but it get written again immediately, so I also disabled OctoApp and then Zupfe reads the file with no problem.
Am I doing something wrong or they do conflict with each other????
The text was updated successfully, but these errors were encountered: