G10 P2 X57 Y0 U-57 S0 R0 set tool offsets and temperatures M563 P2 S"Duplicate" D0:1 H1:2 X0:3 F0:2 元:6 tool 2 uses both extruders, hot end heaters and fans, and maps X to both X and U Create a tool that prints 2 copies of the object using both carriages G10 P1 S0 R0 set initial tool 0 active and standby temperatures to 0C G10 P1 X0 Y0.5 Z-.05 set tool 0 axis offsets Moved Y from 0.6 M563 P1 S"Right" D1 H2 X3 F2 L6 define tool 1 G10 P0 S0 R0 set initial tool 0 active and standby temperatures to 0C To go back and try to consolidate some important info. It's hard for me to give this the attention it needs with everything else I have going on but I will try to keep posting info here as I'm not even exactly sure what specific bug/improvement requests are needed to properly address these issues. external perimeters extrusion width = 0.76mm generated by PrusaSlicer 2.6.0-alpha5+win64 on at 17:46:12 UTC Is there something I can do about this on the firmware/Duet side of things? It seems to me like P2 should switch both to active and heating. The issue seems to be that the earlier G10 S240 P2, and M568 codes don't switch Heater 1 and Heater 2 into active mode so only the active heater starts heating. As soon as it gets to the T2 command T1 starts heating and in this case since it was already at 220 everything started fine. In this example I had everything set to 220 before starting the print and first layer temp of 240. I haven't paid close enough attention but I think I remember it waiting to heat sometimes, but last time as I was watching it did not, it went straight to printing. If I have say T0/heater 1 active and T1 in standby or off when I start the print the new M568 command does set temp for T2 H1 and H2 however T1/H1 stays in standby. This is leaving me with another annoying issue though and I think it might be more related to Prusa Slicer but I am wondering if there is anything I can do about it. It is easy enough to just select T0 or T1 then start. I still haven't gotten around to figuring out what's going wrong when I have T2 duplicate selected before starting a print. I am slowly trying to work through issues in order of biggest priority and time likely required to solve. I haven't tried sliding both to the same setting at the same time to see if I could increase or decrease flow on both extruders at the same time but if I set one at 99 and one at 101, or if I set one at zero and the other at 200 there is no change in extrusion. Or at least the don't give independent control. So M567 does not override M221.ĭoes this mean that M221 does something different than the sliders in the web interface do? Or is there something else preventing my extrusion sliders from functioning properly? Because if I move those while printing in duplicate mode IE tool 2 the sliders don't do anything. Then, if the move is a normal printing move (not an extruder-only move) it multiplies those values by the extrusion factors set by M221. To calculate the required extrusion, assuming that the G1 command only has a single E value, RRF first applies the M567 mix ratio to get the requested extrusion on each extruder. I guess if that like the sliders is overridden by M567 then I guess using M567 via the console would be the best current working solution? This makes no said in Optimizing IDEX machine and Prusa said in Optimizing IDEX machine and Prusa Slicer: If M563 says use both extruders why aren't both extruders just driven by the E Gcode by default?Īnd or if someone decide that M567 is the required way to achieve that then why would it override the extrusion adjustment sliders? Locking the two together with M56 and disabling the extrusion factor seems redundant and overly complicated. I just don't understand why there isn't a base option that allows both extruders to extrude the Gcode defined amount with the extrusion factor slider functioning normally. I also don't understand why it has the extruders defined in M563 telling it to use both extruders, yet only one drives without M567. It seems like M568 overrides the extrusion factors sliders in the status panel which is nonsensical. I am very confused by how this all works out. Not only would it suck going into the firmware and calculating that every time I start a print but it also means I can't tweak on the fly. Would be pretty disappointed if that is the best solution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |