Topics created by JKaechler

yup that should do it. there are extra steps if you need 5v logic. someone here tested it and saw 1v when triggered in its default mode.

Happy to help.

Are you saying that the probe works when homing but not when doing G29?

Double check these guides

https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

@jkaechler said in Hotend woes and heater faults:

In your collective experience, would I be better off with a Y-splitter arrangement like the Prometheus hotend, or the 2 in 1 out arrangement like the cyclops?

I defenitely want a single nozzle arrangement.

Although I have no direct experience of any Y splitter type, my vote would be for a 2 in one out arrangement but it kind of depends on how the "Y" splitter type works. If it's like the Prusa MMU then I believe you have to retract one filament before inserting another. Given the dangers of drawing molten filament back up into the heat break, then I'd have thought the safest thing to do would be to let the hot end partially cool. All that would mean tool changes will take some time. On the other hand, with a 2 in 1 out hot end the "unused" filament will be kept at print temperature for extended periods of time, and if the filament is PLA, then it will hydrolyse (become more and more runny). So when you come to use it, you'll need to firstly purge 20mm or so. On balance, I would still favour that over completely unloading one filament and loading another. Just my twopence worth............

In config.g you'll need to define the type of switch and it's location.
In your homing files you'll need to remove the G30 command to probe Z and replace it with a G1 S1 Z move to seek the endstop switch.

You can also remove the references to G31 and M558 from config.g if you won't be using the probe at all for things like mesh compensation (G29)

https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Homing_Z_using_a_Z_min_endstop_switch

@JKaechler Did you ever made it work? I have the same issue

Is your IR sensor the older sort with through-hole phototransistor and IR diodes, or the new sort with surface mount ones? If it's the older sort, then you have probably had a collision and one of those components has been bent into a different position. If it's the newer sort, then perhaps it has developed a fault.

I meant did you mean the second line to use Z0, not the first.

You can write your own macro to do that and put it in the /macros folder of the SD card. The first 4 user-defined macros appear on the Control page of PanelDue.

@dc42
Ah, thank you for the clarification. Now that i know what I am looking at it makes much more sense.

It's the 2.02a zip tbat contains the new version of DuetWiFiServer.

You can also use the F2 parameter in your M563 tool definition command to tell the firmware that the print cooling fan is fan 2 when that tool is selected.

@JKaechler try M201 X500 Y500. If homing works this way, then you need to set that on homing and create a macro to restore accelerations to their initial values (1000 in your case).

Here's my homex.g (Y is analogous).

M400 ; make sure everything has stopped before we make changes M915 P0:1 S3 F0 R0 ; configure stall detection M574 X1 Y1 S3 ; set endstops to use motor stall M913 X50 Y50 ; reduce motor current to 50% to prevent belts slipping M201 X500 ; reduce acceleration to avoid false triggering G91 ; use relative positioning ; X or Y is homed at this point, now home the other axis G1 S1 X-325 F4000 ; move towards axis minimum G1 X5 ; move away from home M400 ; make sure everything has stopped before we reset the motor currents M913 X100 Y100 ; motor currents back to 100% G90 ; back to absolute positioning M574 X1 Y1 S1 M98 Pset_accel.g ; restore acceleration values

set_accel.g restores the acceleration values and has the following contents:

M201 X2000 Y2000 Z100 E9000 ; Accelerations (mm/s^2)