Separate names with a comma.
Mine only works if you have the 240VAC heated bed though :-)
Amazing work. I really wish E3D has this as a standard option for the HT beds.
Good point, then of course all need to be remeasured. In practice I have found I end up needing to change them all, referenced to P0 more than...
I like that in RRF3 I can do this: ; Tool Offsets - All offsets are set relative to T0 G10 P0 X23.00 Y41.00 Z-5.41 G10 P1 X{tools[0].offsets[0]...
So the difference was interleaving vs grouping the M950/M106 calls, that is super strange, probably one for @dc42 or posting an issue for RRF if...
@Adam Haile attached, but please keep in mind it's WIP as I am still bringing it fully up for RRF3 so don't assume everything else works. I did...
My tfreeX.g files do indeed have the M106 call in them to turn off the fan and my tpostX.g has the M106 R2 command to restore the fan. If you...
This is usually because the PCF fans haven’t been associated with the tools using the M563 command in the config. Could that be your issue? I...
@Rene actually re-reading your note, are you saying that what you do is set all tools to active on startup of the machine (presumably with the...
This is related to the unfinished nature of the profile if I recall, I was in the middle of a RRF2 to RRF3 migration (I am on 3 now). I seem to...
Attached. However please note this was more about fleshing out the structure than actually having workable settings. From what I understand @Greg...
That ooze issue looks like a general bug (nothing to do with the G10 support), I'm going to report that after some more testing.
The ooze prevention value should only be used if ooze prevention is turned on, just to check, did you actually have it enabled? You'll see a bit...
I am reproducing the issue where there are more G10 commands inserted automatically if you don't have your own G10 temperature commands in the...
I will check that, however if you put in your own G10 commands to set the temperature it should then not insert any automatically.\ Do you have...
Are user defined variables likely to make it into 3.2?
The pull request has been merged! It is now also available in the latest PrusaSlicer alpha so you don’t need to compile yourself....
I had ordered the 16T 3mm pully from JUGETEK on Aliexpress because it stated clearly it had a 3mm bore however what they sent me is clearly 1/8”...
I'd have to look deeper but even then I vaguely recall that it was supposed to restore the Z height on the next move. I just exported G-code from...
Which slicer are you generating the g-code with? Does the next move after the tool change include a Z coordinate or just the XY?
