-
Notifications
You must be signed in to change notification settings - Fork 15
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
GXplugin script for a two-nozzle printer. #3
Comments
Hi KeltE Did you already contributed a fix for this or you need help with the gcode manipulation? |
Hello! Unfortunately, I do not have the appropriate skills. Then yes please help. I made a Flashforge dreamer NX for the Cura profile which is now part of Cura 4.9. And as a side project, I also made a profile concept for Flashforge Dreamer. As testing revealed, Cura adds the T0 command to the G-code of the two-tool printer before starting G-code. Flashforge Dreamer Gcode start With my profile. Many thanks! |
The printer you have supports/uses the .gx file extension? If yes, I can try to detect this instruction when you select the .gx mode and drop that particular g-code. |
Sorry @KeltE I see you already can work with the GXWriter and the other printers. That is great then! I can detect for this model and make it work. For me to test can you tell me how I add the printer in Cura? If you have the profiles I apreciate! |
Since Dreamer NX is part of Cura 4.9 then I have other profiles made around it. Must copy the Dreamer profile on my github page to the Recourses directory. And your profile may no longer be visible under Cura 4.9 at Flashforge. I recommend changing the manufacturer's name a bit (for example Flashforge1). |
Hey Ronoaldo, I was wondering if there is already some progress on this |
Hi @StevenVDurm , unfortunately no. I had done some planning but could not start coding/testing as my Finder got a nozzle issue, so I'm avoiding doing changes before fixing that part. |
Thank you for letting me know. |
Hello!
Because on dual-nozzle printers, Cura adds the Gcode T0 command before it starts, and the printer recognizes it as an invalid code. Is it possible to make a script that checks before the start of Gcode T0 for existence and if necessary removes it? And would that be possible at all?
Many thanks! Egon
The text was updated successfully, but these errors were encountered: