@nico-rast you can use the 3hc

@yoshimitsuspeed I do likewise with setting different values for each filament type by using the slicer custom gcode. I tend to use a separate line for each extruder even when a colon separator is permissable as it reduces the possibility of errors and ambiguity. I also find that using global variables and a macro is a great help.

I agree that the use of "E" and "D" can be confusing. But afaik, "E" is only used where a command has values for both axes and extruders whilst "D" is only used for commands that only apply to extruders, so that is a good way to remember.

was fixed in 3.42
Under certain conditions an extrusion-only move was executed at maximum speed instead of the requested speed

@chrishamm Right that's basically what I do. But I don't know playing around with a pretty graph until things look "flatter" bugs me 🙂 Is there was some way of knowing I'm doing it "Right"? I guess at the end of the day as long as the prints look corect its the only indicator. I doesn't help that in all the IS examples you see this clear peek none of my printers no matter how I adust them ever have pretty graphs.

@yagodajm V2. I got it, I have to invert the pin.

M558 K0 P5 C"^!io4.in" H3 F60 T6000 A10 R1.25 S0.008 B1 ; Set Z probe type/mode 9. H=Dive Height. F=Speed probe speed,

Thanks,
Justin

@goose2024 https://www.printables.com/cs/model/247305-xinkebot-orca-2-cygnus-e3d-v6-extruder-conversion-

@dc42 Hi, did any work get done on the PTC heater ?

@namenmalkav H2 is also individual motor moves for Delta and CoreXY machines. So on a CoreXY, using H2 with a G1 move for X or Y will cause only one motor to move, hence giving you 45 degree moves that you are seeing. Using H0 instead of H2 for the X and Y moves should do the trick.

@chrishamm Cool... waiting for it. 😄

i re generated all configs and nothing changed
i keep searching for the issue and find that some motors have they coils inverted
almost all my motors have that and none of my cables is inverted to work like that
so start changing cables and find that works

@jay_s_uk
Bugger... you are right.... I just tested it... 🤷 I do not know why I fall in almost every trap... 😞

Aaaand we are back! only a short downtime needed today!

@jay_s_uk Worked perfectly. Thanks

@bayvan can't say that never happened to me (-:

@Shoki said in Probing gcode G38 VS G30:

But which endstop does it sense while moving ? All of them ? I did not find a parameter to tell him which probe it needs to monitor ?

usually you do this per axis, so G1 Xnnn H4 for X, G1 Ynnn H4 and so on

@george27 have you added
M575 P1 S1 B57600
to your config.g?

How have you wired it? See https://docs.duet3d.com/en/User_manual/Connecting_hardware/Display_PanelDue

Ian

@Edkirk A description of the pins and their connector type is here: https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Roto_Toolboard#description-of-connections

I have also added them here: https://docs.duet3d.com/en/User_manual/Troubleshooting/Parts#connectors-used-on-duet-3-roto-toolboard

Ian

@dc42 thanks, I hadn't thought of this option.

@deckingman

Hi Ian. I was looking into that, as well as PID fan compensation. My part cooling fan is run off of the main board, through a CPAP tube. I also reasoned that this hotend would likely benefit from a heatsock/insulator but the Slice offering is about $50 USD.

I built this printhead purely for a promotion, so I just need it to run well enough for now to get a print or two out of it. I will work out a more efficient implementation later.