Feel free to post what you've changed as a sanity check. Once you see your existing M584 command in config.g it should be apparent on how it works. Choosing a new drive letter and assigning a driver number to it.

Thanks for all the input. I got everything up and running. So thanks to all who helped me with this problem.

@Nxt-1 said in Battling sources of vibration and noise:

And if you have time to spare you could try out all things possible with the trinamic chips in software?

I havent really tried anything here, AFAIK you can only tune some parameters aiding in standstill noise with the drivers on a Duet 2. (which isn't an issue here) Correct me if I am wrong

The Duet 2 uses TMC2660 drivers, that don't have stealthChop, which would be the big thing to try.
Unless you set something different they should have defaulted to spreadCycle, which makes them much quieter than something like an Allegro or TI driver...
Although you might get different results changing that parameter, fixed off-time tends to be nasty (it can give some really unpleasant resonant noise), but its worth testing the 0-2 values for D.

M569 :
https://duet3d.dozuki.com/Wiki/Gcode#Section_M569_Set_motor_driver_direction_enable_polarity_and_step_pulse_timing

I once got someone to try replacing resistors on an Allegro step-stick... you don't want to hear a printer with drivers that run at 16kHz.
People were upset from about 50 feet away.

I've got a nice (and relatively cheap) BLDC servo, I still need to test it and see what sort of noise it makes...

@deckingman that explains what happened. I was having trouble with the part cooling fans early in the install, turned out I didn't crimp the wire correctly on, and I was messing with the config files.

I remember changing that section in config trying to get the fan working, and now you showed me what it affected lol.

Appreciate the help fixing it. Now I see myself looking at the smart effector, instead of the nozzle tip piezo sensor, this hobby is never ending lol

Hi
dsl for my English I translate I speak French 🙂
I myself created an idex machine,
and, i found the fastest solution for me to work with, prusaslicer or cura, i have to create 3 machines, an idex, a copy, a mirror with different bed sizes
in the first I have, idex _ T0 T1
second copy_ T0 T1 deactivate T2 activate
third mirror _ T0 T1 T2 deactivate T3 activate

@Fickert Looks good.

The Motor Control Problem resolved! ( interns of calibration and successful machine move ) ( But I still need your valuable help on bed calibration Should I open a new thread?)

Thank you very much for all your contribution.

Solution: I have just upgraded to the latest beta Firmware and DWC.

Conclusion:
But the configuration remains as (P 2-3-4) I was using. The recommended P 5-6-7-8 values causing problems. If it is not an issue with "Duet 2 Wifi r.104" It is something with the firmware I believe.

The Problem with recommended configuration P-values causing missing steps and noisy move. Each axis even the same amount moves command, they move different distances.

By the accidentally found settings and new Firmware update problem is over!

So this is the code that is working so far:

; Drives M569 P5 S0 R0 T3:3:5:0; Extruder drive 0 goes Forward M569 P2 S1 R0 T2.5:2.5:6:6; X: A drive 1 goes Forward M569 P3 S1 R0 T2.5:2.5:6:6; Y: B drive 2 goes Forward M569 P4 S1 R0 T2.5:2.5:6:6; Z: C physical drive 3 goes Forward M584 X6 Y7 Z8 E5; set drive mapping M350 X1 Y1 Z1 E1 I1; configure microstepping without interpolation M92 X114.29 Y114.29 Z114.29 E274.00 ; set steps per mm (400/140) * 40 = 114.2857 ;; 400 step per rev ;; 140 mm one rev pulley ;;1:40 ratio gearbox

@T3P3Tony said in My Joystick jog control:

@deckingman cool! I did not test the "processing" part with triggers but did a quick macro to confirm it reported properly with/without a print running.

@T3P3Tony - I guess we can be fairly confident that it'll work then. I posted the actual code on the other thread. The reason for two threads is that the first is about help with conditional gcode and this one is more about the hardware and the application in practice. But feel free to merge them if you think that would be better.

Start here for the basics

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

And here for the specifics of corexy

https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCoreXYPrinter

I have printers with the top of the lead screws constrained and not constrained. It depends on the lead screw and the setup. If the lead screws are already slightly warped which is not uncommon constraining the top can cause more issues. If they're straight and you line everything up correctly you'll be fine with constraining the top

@T3P3Tony

You're welcome. This forum was very helpful in getting a few of the details sorted out with the controller... as I dive into deeper I'm sure I will have more questions!

Hi again,

The geared steppers have an odd gearbox ratio of 5 & 2/11 (about 5.18) to 1.

The normal advice about printing using layer heights which allow using whole steps for the Z axis is a bit tricky to apply given that ratio.

A layer height of about 0.193 instead of 0.200 is about as good as you are going to get.

The banding has changed quite a bit BUT it is still there.

Curious.

Frederick

Nimble again but using 0.193 layer height.jpg

I hasten to add my thanks to @T3P3Tony who helped me out on the hardware side as well!

@Mirage said in 3 independent Z motors:

@Phaedrux Yeah, that's it, I must be lazy... 😉

You can't help it if you don't "get it"

There is a huge difference between being proficient with a CAD package and being proficient at design, and not everyone can differentiate between the two very separate skills, and many confuse being able to carry out one of them as automatically being proficient at the other, when nothing could be further from the truth

@mosesbuckwalter said in Duet 2 Wifi With Gigabot Thermocouple Issue:

The heater section of my config.g looks like this
; Heaters
M305 P1 X100
M305 P1 X101
M305 P0 X102
M305 P0 X103

You can't set a single heater to use 2 channels. For example, the M305 P1 X101 command will cancel the M305 P1 X100 command.

Unless the thermocouple board is the older version, you need to use X150 and X151, not X100 and X101. The image on the Printed Solid page shows the newer version, which uses MAX31856 chips, but the text incorrectly says that it uses MAX31855.

@Veti They should be comparable, most voron designs are based on a PL-08N2 which has a 8 mm rated distance (0-7mm reliable).

The Omron M5Q-LT is the default for the switchwire and i happen to have 5 lying around from another project which has a range of 5mm (+-10%, 0-4mm range)

There accurate between there normal operating temperature, -20 to 70c

There all comparable to normal NPN sensors, these just are 10-24V rated so there connected to one of the fan slots and hooked up to the probe-in slot with a diode to protect that pin from any 24V feedback

@Phaedrux
a verry expensive roll of genetic filament 🤣

@kstra It uses the CoreXY motion system from e3d 🙂 unfortunately still waiting for some parts so it might take a while for it to be finished