If you need to make cables for the CAN-FD connections and don't want to solder or crimp ZH connections, I found that JST has an alternative for the cable end. They're the ZR connector.

https://www.jst-mfg.com/product/pdf/eng/eZR.pdf

These allow you to insert all of the wires at once without having to strip the insulation. Just insert and crimp, and all of the connections are made via IDC connection.

I've not known what this connector type was called, but after googling, I found it.

Digi-Key has them in the US, I'm sure they're readily available elsewhere..

Over 100mm/sec for the entire print, even the 3mm circle. I have video of it to. Crazy to watch.

I know it's a simple print, but I've been battling crappy mechanicals, only to finally make it awesome. Was getting oval holes and bumpy round corners. Now, it's a workhorse!

@bearer I know. I've been a bit crispy. My apologies to everyone. I'll post it when I get a chance.

I've been posting for quite a long time, at least years, about the same question, coming at it from different angles, trying to figure out if my problem was caused by different things each time.

What was my problem? Some call it ringing, some call it ghosting, but it didn't follow either behavior.

I was getting ripple artifacts, but they were slightly different. Sometimes it looked like the extruder was pulsing too hard, sometimes it looked like pressure advance was wrong, or I had loose belts, or too much vibration in my system. The list can go on and on.

Among other things over the years, I recently converted my Railcore to a tool changer with direct drive tools and expanded the frame to accommodate the extra hardware. This is when the print quality got really out of hand.

I basically built a new printer.

Well, the actual problem was that my XY motors were too weak. I threw on some beefier ones and my prints come out super tidy again. Can't tell the difference with prints from my Voron v0.1.

Hope that helps someone else.

It was actually really easy. Going to post a series of videos on the design and how to do it.

@gnydick NM, brain fart

@Kolbi click "Select All" check mark on list of files. Right-click, choose download.

It's not one step for all, but at least it's one step for each area.

Honestly, I feel the new version is worse in almost every way.

• There are even less buttons that can be clicked by using the space bar
• The buttons are much slower to respond, for example, clicking baby-step repeatedly is torture, you have to wait for the flash animation to finish before you can click it again
• It's clunkier, even though it looks prettier; more clicks to do the same thing
• The pop-up messages take you to the g-code console when you dismiss them

I'm being brutally honest here, this is the perfect example of form over function. I tried explaining what was needed in the RFC and warned about this kind of stuff.

The web interface should be fast, instant in response as possible given the web host, predictable, and impossible to click the wrong thing at the wrong time. It should have every single button clickable via the space bar as well as every clickable item tab-indexed.

I predicted this would be a passion project about learning a new front end library, and I was right.

Honestly, I suggest going back to square one.

Start by creating a control interfaces like this was a manufacturing machine. Oh, wait, it is!

Forget fancy menus. What do we do a lot of?

Well, when tuning and tweaking

• I want to have a g-code console and the config editor side-by-side
• give me a small mechanical control there as well
• a drop down with macros is enough, they don't need to be listed out
  • if you want to repeatedly run macros, then make a screen for that

What we don't need

• Graphs are pretty, but really, there's no reason for them to take up so much space
• The status pane is also way too big. It would work just as well as a single line along the bottom or top

I could go on and on, but I'm honestly so mad that I warned this would happen. Since updating to the latest firmware, I can't even revert to Web Control 1. Can I just re-upload it or will I have to clean up files on the SD Card?

In reality, my suggestion a long time ago was to make each of these panes a widget you can drag 'n drop and resize to make your own screens. THAT would please everyone.

As a hobbyist, I never minded slightly buggy things. It was exciting helping out projects to become better. But, I am no longer a hobbyist and use my printers professionally.

I don't want to install any more RC's just to have fixes, because almost invariably, something else is broken.

Can you please have a stable branch that is blessed and receives hot-fixes along the way? While the RC's are on a separate track for being actual Release Candidates and not things you have to install to get fixes?

This would be very beneficial to Duet customers as I'm sure they don't all want to dog-food, especially when the food is slightly spoiled 90% of the time.

As a commercial product, it just makes sense to have this release process. Frankly, it's this reason that I'm hesitant to recommend Duet products.

@samlogan87 to be fair, I've brought up the improper release practices, but to no avail. That is specifically, he won't back port fixes. It's always "oh, yeah, that's fixed in the current beta/RC." And often it's not like they're trivial breakages. Show stoppers need to be back ported to the stable branch.

I've run into this multiple times. I've resolved myself to having to just grin and bear it and stick with broken "stable" releases because I'd rather align myself with the devil I know rather than the devil I don't.

Same thing goes for baby stepping. It's woefully implemented. It's overly complicated and only works under assumed conditions. If you're running a work in progress printer with manual tweaking and tuning needed while operating, baby steps will F you up quite well. Search for my posts on the matter.

@deckingman it's all perfectly reasonable. I'm the same, all self taught. I know the challenges.

@droftarts OMG, like i18n, but even slightly nerdier. Well done.

@deckingman that's all correct. My print head is heavy because it's the E3D tool changer setup on a RailCore II. I don't want crazy speed, just a bit more torque. I was merely referring to what happens at higher voltage to see if I could benefit.

I'm not uncomfortable making changes if I know what they are. The lingo is just too casually bandied about sometimes to be sure what people mean. Give me a diagram or explicit instructions, and I can do it.

It's when it comes to terms that aren't identical to what's in the duet docs that I'm not sure. Like, what's Ve? I remember VIN, VOUT, positive, ground, etc.

I just like to be careful. I have a literal pile of duet boards that are fried in one way or another because I carried on when I wasn't sure.

@dc42 I don't have the confidence to wire things without foolproof instructions/diagrams.

For example, when I hear something like the fact that there's a common ground and I can use any of the negative terminals, makes my eyes water. I have 2-3 years of EE from high-school 30 years ago.

And I'm using tool distro board + 4 toolboards. Only heater directly connected is the bed.

@deckingman, so is it possible to run 1 PSU for the motors and 1 for everything else?

@Mandragora that's cool. I guess I can get a decent bump in performance.

I'm assuming the higher voltage will not be good for my fans that run one VIN?

Also, what about tool boards, heater cartridges, etc.?

@dc42 I plugged my info into the form and changing the voltage didn't change anything but low slip angle. I don't know how to interpret that number. I can see changing the torque also brings the number back down after increasing the voltage, but other than that, how am I supposed to use this?

@dc42 I wish I had the 1.02. I just (couple months ago) finished building out my machine with the 1.01.

Very cool about the emf tool

I see people talking about running their steppers at 48v to get crazy speed and torque. I don't see any nema 17 or even 23 motors that are spec'd for 48v.

Can someone please tell me what is going on?

@dc42 sorry, I missed that. I've used a wide array and not seen any difference. Anywhere from 1000 to 8000