Thankyou number40fan and whosrdaddy

I chose the IR Probe as it appeared to be the easiest setup on my hot end.

Best regards,
Tim

Yes, 2A

Fair enough. Sounds like a simple python program to mimic the temperature plotting bit of the web sever would be the way forward, and hope the update frequency catches the spike if present. I'll keep this in mind and put it on the 'to tackle later' shelf unless it becomes more critical.

A bit of topic but not too far IMO:

How about connecting 4 motors on a single (external) driver? To maintain the needed voltage same, would it work connecting 2 pairs in series and then those pairs parallel?

Just poundering the simplest way to make my bed move with 4 motors.

Thanks for the reply. It works

thank you..
I have e-mailed them at think3dprint3d,, to info@duet3d.com..

great board by the way.. nice smooth movement while it lasted..

You can connect the two Y motors to the Z motor connectors and connect the single Z motor to the Y motor connector. Then use the M584 command in config.g to swap the Y and Z drivers over.

For power supply sizing see https://duet3d.com/wiki/Choosing_the_power_supply.

That will be ok as long as the switches are break-before-make. I think most microswitches are. However, it's probably not necessarily if you use the normally closed contacts.

I don't know the Bltouch, but it's a good idea to test a new Z probe. Deploy it and check that the value displayed in the Z probe box in DWC is close to zero. Then trigger it and check that the value rises to around 1000.

In your deployprobe.g file, you might need to add a G4 delay command after the M280 command, to give the probe time to deploy.

Yeah, they didn't until I took the components off the board. I wanted to avoid normally open. The 10kOhm appears to be right on the limit of what the duet decides is off. Strip the components off and you can use normally open or closed.

Thanks for the help. I am new to this all. I am coming from delta and repeater firmware. so it is not even close to what I am used to.bed and hot ends go in this week so hopefully by Saturday I can get a first print. I also need to find a way to adjust the timing on the leadscrews. I think they are off from about 5-10mm from each other. that will level everything out.

Thanks for that info David

Yes, I think that would be the best thing to do.

You can connect external drivers, or motors with built-in drivers, to the pins on the expansion connector. It's simplest to connect the step+ and dir+ pins to one of the sets of step and dir pins on the expansion connector and connect step- and dir- to ground. Connect enable+ to +3.3V and enable- to the corresponding EN pin on the expansion connector.

Do not connect external drivers to the step/dir/en test points on the Duet.

Discussed here: https://www.duet3d.com/forum/thread.php?id=1668

I can only say that my endstops appear to be doing their thing, but I've had my suspicions regarding their "reaction time." I've actually been meaning to check the alignment of the sensor and the tap on carriage, as the endstop switches didn't seem that accurately assembled.

Yep! Got some activity. I Can start working on the JSON response now. Thank you.

Yes, but it will be brighter when you turn the bed heater on.

You have to create those two files yourself, which you can do in the System Files Editor of Duet Web Control.

If you have a popup blocker configured in your browser, disable it when running the configuration tool.

Awesome. I'll probably be ordering one of those in the somewhat near future.

Thanks again.

@number40fan:

; Tool definitions
M106 P1 H-1
M563 P0 D0 H1 F0

Is what I have that lets S3D control them part fan.

Thank you sir, this worked, either on it's own, or together with me resetting the main process in S3D, as I was typing my last answer and saw the answer that it should work on it's own when plugged in to Fan0, I remembered a bug that keeps popping up in S3D once in a while, where a change made to a process doesn't get applied at times, no matter what setting you set it to, like say stopping a print at certain height, it remains there, even that you have removed the height restriction later on etc… simply removing and recalling the process clears the issue... no idea why, don't ask 🙂

Anyway, they work now, thank you!