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

e/s 32 issue : #7

Open
proof0zone opened this issue Aug 23, 2024 · 24 comments
Open

e/s 32 issue : #7

proof0zone opened this issue Aug 23, 2024 · 24 comments

Comments

@proof0zone
Copy link

proof0zone commented Aug 23, 2024

Hey,
tried with a simple benchy, and keep getting this
image

@sb53systems
Copy link
Owner

Send me your G-Code File at : [email protected]

@gueee
Copy link

gueee commented Aug 24, 2024

Got the same error when hitting the Generate button.
Do you want me to send the unaltered g-code file, since there is no output yet, or is there?

@sb53systems
Copy link
Owner

Sorry for the late reply, you can send me by email the Original G-Code, I'll let you know if I discover anything.

Salim.

@sb53systems
Copy link
Owner

Restart your computer, or manually close the CMD console in Task Manager.

@sb53systems
Copy link
Owner

Is this problem still present?

@gueee
Copy link

gueee commented Sep 4, 2024

Is this problem still present?

Sorry, I couldn't find the time to retest it, but I'm going to today and will report.

@sb53systems
Copy link
Owner

Know that a new version was released today :
https://github.com/sb53systems/G-Code-Flow-Temperature-Controller/releases/tag/V1.1Beta

@Nathan22211
Copy link

I just got the issue myself today

@sb53systems
Copy link
Owner

@Nathan22211 This problem occurs with the integration of Klipper_Estimator with this script, you have to reboot your computer or close manualy all CMD Consol in the Task Manager.
image

Let me know if you manage to resolve this issue.

Best regards,
Salim

@Nathan22211
Copy link

killing the console host nor rebooting fixed it.

@Nathan22211
Copy link

I do get an error about a float needing to be an int in french before this occurs though

@sb53systems
Copy link
Owner

I do get an error about a float needing to be an int in french before this occurs though

I thought this error is fixed in the current version of the script!
If you are on the latest version and this problem persists, send me the original G-Code and a screenshot of the error message.
I'll do my best to resolve this essue.

Best reguards,
Salim

@Nathan22211
Copy link

image

tested g code: https://gist.github.com/Nathan22211/fde16d1b3ca701afc340c66b8f25c0a2

@sb53systems
Copy link
Owner

sb53systems commented Oct 3, 2024

@Nathan22211 Another script modified the G-Code before this one, the Script is not yet optimized to avoid comments added in the same line.
image
image

Try one of these solutions temporarily:

  • Use this script first.
  • Avoid comments in the same line in the other script.

I will try to solve this problem soon in the future updates.
If you need more support, contact me in Discord: sb53systems

Best reguards,
Salim

@Nathan22211
Copy link

yeah just tried it straight out of orca slicer with it being the only post script and it still errors. I am a few versions behind and on a fork so maybe I should try to use mainline

@sb53systems
Copy link
Owner

sb53systems commented Oct 3, 2024

@Nathan22211 Another solution: use flow compensation integrated into Orcaslicer
image

@sb53systems
Copy link
Owner

yeah just tried it straight out of orca slicer with it being the only post script and it still errors. I am a few versions behind and on a fork so maybe I should try to use mainline

@Nathan22211 Yeap, Forked version can cause essues, i recommend you use an official version.

@Nathan22211
Copy link

yeah just tried it with the latest mainline beta and still the same issue when running it from orca, and I'm pretty sure I turned verbose off so there shouldn't be as much of a comment issue. also it doesn't seem to find the extruder and used filament in the g code

@sb53systems
Copy link
Owner

sb53systems commented Oct 3, 2024

yeah just tried it with the latest mainline beta and still the same issue when running it from orca, and I'm pretty sure I turned verbose off so there shouldn't be as much of a comment issue. also it doesn't seem to find the extruder and used filament in the g code

Send me the original G-Code with the error screenshot

@Nathan22211
Copy link

image
Bottom Panel_GPWC_R1_ABS_1h16m.txt

@sb53systems
Copy link
Owner

From where (which parameter) this comments come from !
image
I'm using Orcaslicer v2.2.0-beta2!
image

@Nathan22211
Copy link

verbose gcode if I recall correctly. must have left it on by accident, though some other post scripts need it turned on so there's already a conflict there.

@Nathan22211
Copy link

turning verbose off fixes it but I'd definitely make it practically ignore anything after a ; in a line within the gcode blocks. some scripts, such as gradient infill, need it turned on to work properly

@sb53systems
Copy link
Owner

@Nathan22211 I will try to prepare an update as soon as possible, thank you for your contribution.
Let me know if you found otherthing to improve.

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

No branches or pull requests

4 participants