50% may still be too much. If you really want it to stall out you should find the lowest possible current that still allows the motors to move. You might also need to reduce acceleration during homing as well.

https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing#Section_Configuring_stall_detection

Stall detection on the Z axis is honestly just as hard to get working as sensorless homing on the Z axis. Since the moves for homing are typically slow it makes it hard to really trigger. But you can test it by tuning your M915 parameters.

I'm not 100% sure it's even active during a G30 probe. @dc42 would have to answer that.

It's easy enough to test though. Have you tried to make the Z axis stall by hand with stall detection configured?

i can use a remote desktop session to see the duet interface. the spaghetti plugin is automated. it will pause or shut down a print on its own if there is a problem.

https://www.thespaghettidetective.com/

That got it working! Thanks for the suggestion.

BTW: flashing the firmware with BOSSA on a Mac worked without a hitch.

Crossover belt option seems good, but difficult to implement.
So, to start out, since both Y steppers are already wired in a series harness, they will simply be plugged into the Y driver.

Thanks David for the answers.

Getting an answer for a problem like this on a Sunday... Guess this is why i'm at my 5th board from you guys 😉 Much appreciated

@Veti I changed the config for the fan, works brilliant, thank you. Fan off macro deleted!

I have used DC's values as I can only find 100k 4700 in the marlin config,

Ok if DC42 says so I will start to reconsider my usb interface 🙂

I will not be able to use the web interface as the process is automated, is there a way to use this file transfer to the SD card without the web interface ?
with HTML requests I suppose ?

Also, the ethernet port of the RPI is already used for internet connexion, is it possible to use a dual ethernet port extension such as the ethernetberry to connect the Duet ?

Thank you

@randyl said in Multiple independent Z motor Z sync issue:

Veti,

Added E0, did the trick...

Many Thanks!👍

I presume you mean you added E3 to the M584 command.

I know I didn't select a tool, I just think this is a bad user experience, just a big nono in UI/UX design to flood the screen with identical error messages

Well, it looks like I'll have to wait for the firmware update. I posted the last reply too soon, and should have run the test first. The changes to Fusion's post worked fine, and the beginning of the output is as follows:

;1001
;T1 D=6.35 CR=0 - ZMIN=0.501 - FLAT END MILL
G90
G21

;ADAPTIVE1
M5
M291 P"Insert Tool 1, D=6.35" R"Tool Change" S2
T1
G28
M98 P"g28post.g"
M3 S10000
G54

Same problem. I also changed it to put the M291 command directly in the GCode file instead of calling a macro. Same problem. Bummer!

It's unlikely that you damaged anything.

@bearer,that's a good point, but I just tested without ground connection and the test button does shut the power.

Possibly it simulates unbalance by sending current from L after the current transformer back to N before the current transformer, but I don't know for sure.

@dc42, yes, this is a good point. Doubling the copper thickness doesn't double the solder.

Thanks, this worked perfectly, just adding the F0:1:4:6 to the end of the existing M563 line. Awesome!

Thanks DC42, was heater 1 as I assumed (hotend). I have swapped out the pt100 sensor and will try again once I get a chance to put rest of printer back together.

Looks like the main reason to use multiple inputs to a trigger is to have all the endstops trigger an emergency stop. Maybe we should use a separate GCode command for that.

And then there's this idea ... Sounds like the real solution, then you can rework M581 to your heart's content.

@rod-todkill said in Duet for 350 Degrees Celsius Printer:

Im a little confused as to which one I would need or both ?

I'm a little confused about what you're asking. Are you referring to the PT100 and thermocouple mentioned in the linked thread?

Have you read the documentation for each?
https://duet3d.dozuki.com/Wiki/Connecting_PT100_temperature_sensors
https://duet3d.dozuki.com/Wiki/Connecting_thermocouples

Or the comparison of thermal sensors?
https://duet3d.dozuki.com/Wiki/Temperature_sensors

If you've read those and still have some confusion, come back and ask a more specific question.

In general though there isn't anything about the Duet that would stop you from printing high temperatures. It's capable of controlling all the hardware needed to achieve high temp prints.

E3D is now selling hotends and print beds suitable for high temperature applications, including water cooled options for use inside a heated enclosure. They would work very well with the Duet.

https://e3d-online.com/high-temperature-heated-beds
https://e3d-online.com/high-temperature-heater-cartridges
https://e3d-online.com/duet-pt100-daughterboard
https://e3d-online.com/pt100-temperature-sensor
https://e3d-online.com/v6-plated-copper-heater-block
https://e3d-online.com/plated-copper-nozzles-v6
https://e3d-online.com/titan-aqua

Taking a 10mm cube as an example, using a 20 tooth pulley would mean either 50 or 100 full steps per side. Using a 16 tooth pulley would mean either 62.5 of 125 full steps per side. So in that example, the 16 tooth pulley with a 1.8 degree motor would rely on microstepping for positional accuracy (because 10mm equates to 62.5 full steps).

@deckingman, I think that even in the first example it relies on microstepping because the corner ends are not necessarily on full step boundary. This also applies to the Z axis, even if you use 'magic numbers' your layers can be on a fraction on a full step.

(would be nice if the Duet would be full step aware, e.g. round to full step on idling, allowing to round to full step on homing, etc. This has several advantages such as less stepper noise on idling, less chance of step mismatch between two Z motors, etc).

@mlaustin6 said in Cura 4 barely extruding:

I had it set to 1.75mm, and it somehow reverted back to 2.85.

If you use Cura long enough, this is bound to happen to you. Very common problem.