M600 color change on Neptune 3 (standard) #53
Comments
|
I wasn't in the room when it hit the M600 line I tried on my EN3, but if it had ran the command correctly, there wouldn't have been any filament available to continue. Instead what seemed to happen is it just ignored the M600 command and continued printing. |
|
Mine goes through the routine, it's just that it locks up and won't resume when I hit continue/resume on both octoprint and the dwin screen. M0 worked but it seemed like it didn't extrude after it continued. I need to pursue this a little deeper or I'm totally switching to klipper 😆 |
|
Just curious, what FW version are you running now? I think you mentioned an update in one of your vids, but can't recall offhand. |
|
I'm curious why the operation of resuming printing after pausing is unable to extrude. What firmware version do you use? In the latest beta version, I tried to add M0 to gcode to pause. Click the screen to resume printing.
…---Original---
From: ***@***.***>
Date: Tue, Dec 13, 2022 03:02 AM
To: ***@***.***>;
Cc: ***@***.***>;
Subject: Re: [NARUTOfzr/Neptune_3] M600 color change on Neptune 3 (standard)(Issue #53)
Mine goes through the routine, it's just that it locks up and won't resume when I hit continue/resume on both octoprint and the dwin screen. M0 worked but it seemed like it didn't extrude after it continued. I need to pursue this a little deeper or I'm totally switching to klipper 😆
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
I ran into the issues described on earlier versions of 1.0.5 and 1.0.3 and had to restart the printer if I tried to pause it, but the latest version of 1.0.5 has M0 working smoothly in my experience. However the load/unload buttons seemed to introduce an additional Z height offset that wasn't removed, so I stuck with manually opening the extruder gear to get things to work. Ignoring any changes that need to be made to accomodate the screen (if I remember right a few user confirmation screens in the default DGUS firmware are disabled[1][2], though there is still a definition for a filament change page that might work[3]?), the comment needs to be removed on this line[0] in order for Marlin to try handle and M600 calls. [1] https://github.com/NARUTOfzr/Neptune_3/blob/main/Source%20Code/ZNP_F401_Marlin-Beta/Marlin/src/lcd/extui/dgus/DGUSScreenHandler.cpp#L85 |
|
I'm using 1.0.5 beta, but I modified it a little (I have the forked version in my repository). I only tried to use M0 once, I was more curious about getting M600 to work properly from Octoprint. It will not resume from Octoprint or from the Dwin screen. |
Thanks! I'll take a look into that this weekend. |
|
Has there been any progress on getting m600 working? |
|
Are there any updates? |
|
This machine has been discontinued for over a year. The only way to get
updates will be from community firmware or switching to klipper
Phil T.
The Feral Engineer
www.theferalengineer.com
Catnip contributions 🐱🐱
https://paypal.me/timpsonmusicllc
…On Sat, Nov 30, 2024, 1:18 PM Ok 2.0 ***@***.***> wrote:
Are there any updates?
—
Reply to this email directly, view it on GitHub
<#53 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARUZ2LIP3ZHHKMYNS6ETXHT2DH6QPAVCNFSM6AAAAABSYYSE4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBZGEZTCNZTHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I'm trying to set up M600 for color changes between layers, running programs from Octoprint. The M600 command will work to position the tool head and unload the filament, but nothing I try will make it resume. I tried using M0 and it will pause and resume with that, but it doesn't seem to finish the print correctly.
I wish the firmware on the Neptune 3 Pro were the same as the one on the Neptune 3. It would be nice to be able to run marlin 2.1.1, like the Neptune 3 Pro is running, instead of 2.0.9.3.
The text was updated successfully, but these errors were encountered: