I have installed a Duet/Ethernet onto a Rostock Max V3 with an SE300 hotend and I'm trying to print a NASA Saturn V S-IC F-1 combustion chamber by faithfully printing the 356 lower tubes and 178 upper tubes using G2 circles over and over and over and over and over.

This part has 226,000 G2 commands in it.

I'm literally amazed that I can print a 1mm diameter circle using a 0.5mm diameter nozzle and it looks great.

I <almost> can't see the stepper motors turn as it's printing a circle.

And the extruder also seems to not be moving.

It's very impressive that the Duet can handle such teensy-tiny movements on a delta printer.

Thanks for all your work.

@exerqtor said in Advice for combined sensor and end stop wiring.:

@fcwilt

Nothings carved in stone yet, but why would NC be better?

If a wire falls off a NC switch or you have an intermittent connection it will trigger early which will stop movement safely.

If those things happen on a NO switch, it will fail to trigger when homing and you will crash your mechanics.

If you have electrically-induced noise on the endstop wires caused by stepper motor wires or a heated bed, it <may> cause the endstop to accidentally trigger. NC switches are more immune to that kind of noise.

We couldn't find any double-wide camping cots, so we bought two single-wide ones and I printed some clips to hold them together, and BANG! we had a solution for getting us off the dirt while camping.

I printed up several 1/4" thick test pieces until I thought I had the design perfect and them did 4 3" long pieces.

These turned out to be WAY too stiff to clip on, so I did an update making a thinner wall and larger opening, but this design had a wall thickness of 6.7 extrusion widths, so there was an unfilled gap in the center that made them too weak.

Adjusting the design in CAD reducing the wall thickness by 0.05" and reslicing get me a design with nicely filled-in walls that are the perfect strength to clip on and (barely) able to be removed.

#iteration

Thanks Duet team for getting my SeeMeCNC machine off Rambo and onto something I can just design/slice/print and be happy with.

@educatingsavvas
I'm not an expert on the syntax of conditional code, but something like this might work: (Assuming the sensor you want to ignore is 5)

if sensors.endstops[iterations].triggered && iterations != 5

or, right after the while skip the check for iteration 5:

if iterations == 5
  continue

@MakeStuffMakeStuff said in NC Microswitch Z Probe with 3.2.2:

what does the pull up resistor do

You have a switch connected from ground to an input pin on the CPU.

The CPU reads the voltage at the pin.

• If it's above a certain level, it returns a binary one.
• If it's below a certain value, it returns a binary zero.

When your switch is closed, it's connecting the pin to ground, and when the CPU reads the voltage at the pin, it's pretty close to zero and it returns a binary zero.

When your switch is open, the pin is not connected to anything, and is just floating around. Sometimes, the CPU will read a low voltage and STILL return a binary zero.

The "pull-up" resistor is a high-value resistor that connects to a positive voltage, so when your switch is open, it "pulls-up" the pin to a higher voltage and the CPU reads it as a high-enough voltage to return a binary one.

When your switch is closed, the resistor still tries to "pull" the pin up to a higher voltage, but the resistor's value is too large to do that and your switch wins the fight and can drive the voltage at the pin close to zero.

I'm seeing several groups attempt to make a closed-loop stepper motor controller using encoder feedback and they are all experiencing the same difficulties everyone does implementing a PID control loop.

• Large errors during speed changes.
• Unstable oscillation
• Differing error performance for long and short moves
• Differing error performance for slow and fast movements

An idea I've never spent much time on (so it's the BEST idea anyone has thought of yet!) is to NOT do PID/closed-loop control for normal movements and only use it to "close-the-loop" during recovery from errors.

The idea is that since we all love the performance of our open-loop steppers with microstepping, and we just want to recover from crashed heads or trying to step too fast causing missed steps, just enable closed-loop mode when you detect the error between actual and commanded position is larger than a setpoint.

When switching in and out of closed-loop mode you'll get blobs and errors in your print, but you had those anyway due to the missed steps that triggered the mode change in the first place.

This method would still require some motor/mechanical-system analysis and tuning, but would not come into play except when there already was an error on printing, and would only be in effect for a short time during the correction of errors phase so it would have much less change of causing catastrophic errors in position compared to a full-time PID loop running.

Anyway, it's an idea and I thought I should bring it up to the team implementing the closed-loop control stuff.

If it's a terrible idea I can live with that. I've had many.

@dc42 said in Question about the quality of the Duet software..:

If everyone using our software was prepared to pay a few £1000s for the privilege plus several £100s in annual maintenance fees, then we could no doubt afford such a team.

I've only ever bought one Duet2 and since it's likely to keep running for the rest of my printer's life I won't be sending any additional funds your way.

Do you have a way for those of us with some extra folding money to be able to support your work financially through a donation once in a while?

@Nightreaver Cool.

You can contact me anytime for MQTT-related discussions.

I spent 4 years doing commercial MQTT implementations on tiny microcontrollers and have tens of thousands devices in the field talking all day long.

@fcwilt said in My wish : Inputs debouncing:

It's hard to believe that the firmware doesn't de-bounce the inputs - it's simple code.

This is where I mistakenly thought you were saying it was a simple job.

I apologize for my misunderstanding.

It's good to have a variety of people discussing this kind of thing. It makes for a better product for everyone.

You are all a great group of peers.
Thank you for letting me get confused at times.

ARGH!!!!!

Nevermind.

The damn filament end is stuck in the spool.

This darn MatterHackers filament has a giant hook on it so it doesn't let go of the spool and sometimes I forget to get in there with a knife and cut it off.

@fcwilt said in I could use some help:

But the homing moves were supposed to be:

a minus move
a plus move
a minus move

Based on the jogging test it should have moved:

toward the front
toward the back
toward the front

Since it's a bed-slinger in Y, isn't a PLUS move going to move the bed towards the FRONT? (Move the head towards the +y part of the bed.)

I may be confused.

@mac I see that the Duet Mini 5+ does not have on-PCB pullups on the IO pins.

You need to go to the RRF configurator and select "Active low with pullup" if you are using normally-open switches connected to ground as endstops.

Without a pullup, every time a stepper motor starts moving, your machine will start to get signals indicating the endstop switch is being pressed.

@mac There's no gurantee, but every microswitch I've ever used had common connection near the button-end of the switch and normally-open in the middle and normally-closed at the opposite end from the push button.

This would mean that you have your switch wired as normally-open.

https://forum.duet3d.com/assets/uploads/files/1655734994077-101ee1f1-2002-4042-b838-e9c4e68126bd.jpeg

From the M574 description, since you have a normally-open switch, you shold add the "!" character to your M574 lines:

For active low endstops, use type S1 and invert the input by prefixing the pin name with '!', for example M574 X1 S1 P"!xstop". Invert the input when using an NPN output inductive or capacitive sensor, or using a NO switch (not recommended, use a NC switch instead).

like this:

; Endstops
M574 X1 S1 P"!io5.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io5.in
M574 Y1 S1 P"!io6.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io6.in
M574 Z1 S1 P"!io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin io2.in

I do not know what Duet board you are using, so I don't know if you need to enable pullups yet. Let me know what board you have and I'll reply.

I can also make a video showing how you can use the DWC Object Model plugin to see if your switches are configured the right-way by using a browser and pressing the switches.

@mac said in I could use some help:

X-255? Y-255? my bed's 220 by 220! where is this coming from?

It's -225 not -255

Your bed is 220, so you need to move slightly MORE then 220 to make sure you've hit the endstop in case it's way at the other end of the travel.

So your bed is 220, move -225 and you will always hit the home switch.

@signpostman

I haven't read this entire thread so I don't know what you mean by "Is there any other way to connect my ClearPath Servos to the Duet 3 main board?"

If you have specific questions, you should probably start a new thread with those questions and I'd be happy to help.

@feynman137 Oh YEAH! I forgot you need to start it up.

Settings->General Click "Integrated plugins" tab then start it.

@feynman137 You can click on "Object model" in the lower part of the left-hand pane and expand the Network section to find it.

@corlissmedia said in Is there NO WAY to connect to DWC?????:

WiFi module is idle
WiFi module is connected to access point NETGEAR83, IP address 192.168.0.XX

OK, I get it that you removed the last two digits, although there's no reason at all to keep them secret.

So, after you get your machine to connect to your WiFi, can you connect using

http://192.168.0.XX/

in your browser?

• If not, what does the message in your browser say

Of course, replace the "XX" with your secret numbers.

@corlissmedia said in Is there NO WAY to connect to DWC?????:

WiFi module is connected to access point NETGEAR83, IP address 192.168.0.XX

OK, you should have gotten an actual IP address and not one ending in "XX"

I have NO IDEA how in the heck that could have happened.

I'm 100% baffled.

@corlissmedia OK, good to know.

Please scroll down to section 5 on THIS PAGE and let us know what you see compared to the document.

What do you get to the M552 commands as you turn off your WiFi?
What to you get from your M587 command to configure your WiFi?
What do you get to the M552 commands as you turn on your WiFi?

• Do you get "WiFi is connected to access point (whatever you access point is using for its SSID) , IP address is xxx.yyy.zzz.www?